From OrganicDesign Wiki
| This procedure is incomplete. Go here for all incomplete procedures. |
|
| This article describes a procedure which forms a part of the organisation's day-to-day running. See the procedures category for a complete list. This procedure defines the steps required to prepare a new wiki organisation based system for a client or project, it should be printed and used as a guide for initial discussion with the client. This is really a job rather than a procedure because it involves many roles and work sessions to complete, but until we have proper workflow in place I suggest we make everything procedures for now. |
|
1 Preparation and Administrative
To begin with the process we need to know a few things. If there is a well-written business plan the information can be taken from there but experience shows that in most cases the organisation is in need of more clarity and structure, thus the process of setting up a new organisational system is equivalent to defining the organisation for the first time. Some questions that need to be clarified are:
1.1 Work Agreement
- What are the clear values that are being worked toward by all parties involved? Is there a work agreement?
- The work agreement should contain the values (terms and conditions) agreed upon and the scope of the work agreed to, so it is like a quote.
- What are the needs of the client organisation? What are the organisational goals the system needs to help fulfil?
- Who is filling which roles in implementing wiki organisation?
1.2 Current State
- What is the organisation currently doing, that is, which tasks is it performing and which roles are being filled, what are the departments?
- What is the current state of organisation and what is missing for wiki organisation to be implemented?
1.3 Financial
- The work agreement should be used to get quotes from competing teams to ensure that a decision to commit resource and time is based on a clear understanding of value delivered and the process rules out corruption. In this process it may become clear that the offered solution is not what is sought after by the client, which is better to find out at the beginning
2 Map existing organisation
- Once requirements are known, compare existing setup with the template. This done done by filling in an company/system article
- The organisational system is prepared in parallel with the existing one to minimise disruption, activity and content is moved across in phases.
3 Move existing domains
4 Set up LAN
- Internet account
- Phone solution? VOIP options?
- What is the connection like? Speed, reliability?
The general idea for hardware is to get good standard equipment, but be protected against failure by having good procedures in place for handling data restoration or hardware replacement and installation.
- Router: (Lynksys WAG54GP or similar)
- LAN: Gbit ethernet is practical cost, preferably use optical cable not copper
- Server box (Standard server box (make sure it is a stock BIOS and parts etc)
- Workstations (1 per office worker)
- Laptops (1 per agent in the field)
- Sources of good quality hardware
- Site hardening available
4.1 Install Server(s)
| This article describes a procedure which forms a part of the organisation's day-to-day running. See the procedures category for a complete list. The Install a new server procedure defines the steps required to prepare a new computer or VPS for use as a server for the organisation. |
|
Some places will want to have both a LAN server and a web server, others will be happy serving the wiki directly from the LAN server.
- Firewall (just linux default utils are fine)
- Email (IMAP running on internal server, procedures for setting up a new client etc)
- Backup (an automatic LAN server to web server backup exchange over SCP, plus a manual staff procedure on to optical media for larger files and for testing that backups are ok)
- Shared files and documents (samba is best because it's well supported in linux and best not to be purposely difficult to windows users)
- Wiki
- IRC channels (or use freenet until we can set up our own on our servers)
4.2 Install Workstations
|
| This article describes a procedure which forms a part of the organisation's day-to-day running. See the procedures category for a complete list. The Install a new workstation procedure describes the setting up a new computer as a workstation for the organisation. The machine will be installed with the Ubuntu operating system and exhibit a select list of applications required for the organisations day-to-day requirements. |
|
- Firefox
- Thunderbird
- Open Office
- Pidgin
5 Import articles and templates
6 Refine and Extend Structure
- Map roles & procedures, resources (especially those which are bookable), knowledge base, best practices etc
- Create specific portals (see Wikipedia:Enterprise portal for the meaning of portal here)
- Create templates (ones that represent organisational entities) and their forms
7 Train staff in system usage
8 What info we need from the client
When a new server is set up for a client we will need them to configure some settings for their domain-name (unless it's a new domain and they want us to take care of registration, in which case we just need to know the domain(s) that require registration). Here's the info needed in the former case.
- Full company name: For invoicing and domain-name registration
- Primary domain name: (eg. abc.com)
- Sub domains: (eg. www, wiki, crm, files)
- Email addresses: (a list of email addresses required for the domain, and whether each is a POP box, or should forward to an existing address)
You will need to ask your domain provider to set up an A record for each sub-domain pointing to 64.79.219.166
