|
|
| Line 1: |
Line 1: |
| − | ;Current
| + | |
| − | *Tidy up Comms WS, it is not functional
| |
| − | *Sort out login details rendering
| |
| − | **[[Milan/Resources/Account Details|Account Details]]
| |
| − | *Accounts
| |
| − | *Set up Media fields
| |
| − | **[[Milan/Resources/Media|Media Content]]
| |
| − | *Set up URL fields
| |
| − | *Group examples together into portal, or something
| |
| − | *Enter notes for IT Support ws
| |
| − | *Begin work on business template for IT Support
| |
| − | *Enter accounts, make sure there are no errors
| |
| − | *Synchronise spreadie content/wiki ws's, ensure proper connection
| |
| − | *Tying in files, for instance from install-list
| |
| − | ;Todo
| |
| − | *Milan/Stock Control
| |
| − | *Milan/Budgeting
| |
| − | *Milan/Potential Management
| |
| − | *Milan/Content Management
| |
| − | **Web portal for IT Support
| |
| − | **Web portal for Milan Blog
| |
| − | **Design/Content/Name
| |
| − | ;Done
| |
| − | *Set up accounts WS
| |
| − | ----
| |
| − | <table class=document-code><tr><td>
| |
| − | '''This todo list is regarding the things that need to be done to my organisational system itself.'''
| |
| − | </table>
| |
| − | #Goals
| |
| − | *Note: Merge/Integrate from Director list
| |
| − | *Move from database entry form to wiki articles
| |
| − | *Email customer data to technician when he grabs the system
| |
| − | *Dry runs through process to ensure hitch-free transition, achieving reuse of customer data and capturing job info. Move toward pasting contact details and job info into invoice template
| |
| − | #General Process
| |
| − | (applies to all sub-goals)
| |
| − | *Set up or tidy up category
| |
| − | *Create template which gives a starting point to deal with category
| |
| − | *Link into main page
| |
| − | *Dry run through the process
| |
| − | *Potentially: Custom form by [[Requests|Aran]]
| |
| − | *Tie-in roles processes
| |
| − | *Implement (train and document)
| |
| − | #General Organisation
| |
| − | *Time: 4hrs
| |
| − | *Process Aran todo list
| |
| − | *Categories
| |
| − | Try and get everything categorised, not maintained in manual lists. Link to the categories
| |
| − | from the main page. eg. Instead of the [[CGS Roles]] article, link directly to the
| |
| − | [[:Category:CGS Roles]] category article instead.
| |
| − | *Add yourselves as clients
| |
| − | You should add yourselves so that you can manage your own resources, knowledge and repairs in
| |
| − | the same way you do for you customers. Eg. You should be able to reach the info about the Bunta
| |
| − | (CGS), Grunta (Milan) and network setup etc through the same process as you would for looking
| |
| − | up any client.
| |
| − | #Callouts
| |
| − | *Time: 2hrs
| |
| − | *Telephone interview form
| |
| − | *Technician form for callouts
| |
| − | *[[Paranoia Bag]]
| |
| − | *Admin processing callout forms
| |
| − | *Tie in to accounts
| |
| − | *Callout pricing/quotes info
| |
| − | #Accounts
| |
| − | *Time: 12hrs
| |
| − | *Track CGS expenses
| |
| − | *Timelog (Admin via spreadsheet)
| |
| − | *Accounts receivable - begin with tracking callouts
| |
| − | *Open Invoices
| |
| − | see [[Category talk:CGS Open Invoices]]
| |
| − | Make the invoice template into an article
| |
| − | Make all invoices articles and categorise those in "Open Invoices" and "Paid Invoices"
| |
| − | Once you've done that you won't need to categorise the client in "Open Invoices" anymore.
| |
| − | *Budgets
| |
| − | *Info for bonus schemes
| |
| − | *Reports
| |
| − | **Daily tally
| |
| − | **Weekly tally
| |
| − | **Monthly tally
| |
| − | **Tally formula
| |
| − | **Tie in stock
| |
| − | #Quotes and Computer Systems
| |
| − | *Time: 4hrs
| |
| − | *Specifications and warranty info article
| |
| − | *Quotes template (tie in install list)
| |
| − | *Custom-form w/drop-down boxes of components, auto-add prices
| |
| − | *Quotes followup process
| |
| − | #Stock Control
| |
| − | *Time: 10hrs
| |
| − | *Orders category and articles
| |
| − | *Email orders to suppliers
| |
| − | *Stock arrives: add orders to stock
| |
| − | *Tie in to accounts/tally when stock is sold
| |
| − | *Generate price list from stock list
| |
| − | *Monitor stock levels using stock article
| |
| − | *Hardware Classes
| |
| − | Create categories for ''kinds'' (classes) of hardware and assign your resources to those cats,
| |
| − | so you can have info, links, how-to's etc for those kinds of things. eg. Removable storage,
| |
| − | Media, Routers, wireless, LAN, Monitors... can all have general info.
| |
| − | *Warranty
| |
| − | I noticed some warranty comments cropping up - that's an important one that we haven't talked
| |
| − | about before. To handle these best you should actually have an article for each warrenty which
| |
| − | contains links to all the resources under warr. and the start/end of the period. These articles
| |
| − | are of course in a warranty cat and each affected client and resource link to their associated
| |
| − | warranty article. That's also where you would include links to any relevent supplier warr info
| |
| − | for the products - sometimes there's associated events here because clients sometimes need to
| |
| − | fill out forms to be elegible.
| |
| − | ;Stock Control notes - from manager WS
| |
| − | *create existing suppliers email list
| |
| − | *pipe CGS Stock Control category onto CGS Admin Homepage
| |
| − | *when a part is ordered, it is added to a table under the appropriate supplier, then when the stock arrives, the table is moved to the "in stock" category
| |
| − | *Quotes template/form
| |
| − | *Booking-in template/form
| |
| − | *Callout template/form
| |
| − | #Filing
| |
| − | *Time: 4hrs
| |
| − | *Business data backup
| |
| − | **Wiki
| |
| − | **Drivers
| |
| − | **Old business files
| |
| − | **Org structure
| |
| − | *Maintain install list
| |
| − | *Weekly update process
| |
| − | **Drivers
| |
| − | **CGS Technician CD
| |
| − | *Drivers Store
| |
| − | *Move file-based org-structures in to Wiki
| |
| − | The main top level entries of your org in the wiki will be categories page and main home page.
| |
| − | Put large files into htdocs, you can still use the current org struct for things that have to
| |
| − | be files like media and installs, but use wiki cats and lists to organise links to them.
| |
| − | #CGS Portal
| |
| − | *Time: 2hrs
| |
| − | *Review functionality and tie in with new categories, etc.
| |
| − | *Dry run through various processes using portal as a starting point
| |
| − | #Roles creation and commitment
| |
| − | *Time: 2hrs + 2hr meeting
| |
| − | *Set up or tidy up roles
| |
| − | *Tie in QTree way into workspaces
| |
| − | *Worklog/Schedule
| |
| − | The admin should be using worklog regularly thoughout the day so that it can be used for
| |
| − | scheduling easily. This allows the time-based articles such as [[daily]], [[weekly]],
| |
| − | [[monthly]] to be connected in to time consistently. Keep the next one or two regular items in
| |
| − | schedule/worklog. Eg. create roles specially for problem-solving/notion and book them some
| |
| − | sessions to work on the CGS structure/idea/questions etc...
| |
| − | **Regular Tasks
| |
| − | **see [[Talk:CGS Weekly Tasks]]
| |
| − | **This Todo needs to receive regular attention.
| |
| − | **Callouts
| |
| − | **Lunch
| |
| − | **Return
| |
| − | **Processes (check todo)
| |
| − | *Meeting: Roles commitment
| |
| − | *Implement (document + train)
| |
| − | #Summary
| |
| − | *Total time required: 42hrs +-4hrs
| |
| − | *Plus time for Aran to create customised forms (awaiting confirmation/estimate)
| |
