Computing System Roadmap

i. Contents

  1. Preparation and planning
  2. Preparation and planning
    - existing services provided by external organisations
  3. Estimated cost and time-line
  4. Research; create required tools and configurations; build test system
  5. Software profile compatibility; installation and configuration details
  6. Issues people have found when testing software applications
  7. Manual file format conversion
  8. Software and licencing
  9. Internet connectivity
  10. Further services required from external organisations
  11. Specify hardware to be bought
  12. Install network
  13. Obtain hardware
  14. Build and configure hardware
  15. Configure file server software
  16. Configure firewall and NAT router software
  17. Configure mail server software
  18. Configure other network hardware
  19. User training
  20. Configure workstation hardware
  21. Configure workstation software
  22. Configure print servers
  23. Backup strategy
  24. Other peripherals
  25. Final system testing and potential troubleshooting
  26. Installation - workstation transition order
  27. On-going IT support
  28. Documentation
  29. Warranty
  30. Further useful functionality on hold until the future
  31. Areas of importance not addressed by this plan
  32. Changes / work completed after the last quote

Introduction

Intentions

This document describes a roadmap for implementing a computing system involving a file server and printers, accessible from any number of workstations situated throughout an organisation, by any number of people using any of those workstations.

Most software applications are installed on each workstation, with some installed just on a a single computer (the file server) and accessed by the system's users from the workstations; users identify themselves to the system using individual username and password and, assuming they are allowed access, are presented with an environment that can be both standardised and tailored on a per-user and per-machine basis - they will see a 'desktop' of standard icons representing software applications and be able to make use of private and shared disk space for storing data. Users can be members of groups, and the environment tailored on a per-group basis. Each workstation will have uninterrupted Internet access. Each user will have their own email address to which Internet email can be delivered and access to communal printers. Each user's data will be backed-up automatically every night.

Points beginning with an asterisk ('*') indicate a request for information from the organisation for whom this is being implemented, or tasks for them to perform.

Where possible this document intends (though doesn't quite yet succeed) to map the order in which events will take place, the time estimated for each point to reach completion and the costs involved. As often as possible feedback will be provided of the stage the proceedings are at and any other information upon request.

A word of caution...

It is important to build into the computing system capacity for future change, especially in areas of computing that can require significant alteration in its architecture. One such software application that has significantly differing requirements to the software described herein is digital video editing. If you know of any planned use of this system that hasn't been taken into account thus far then please identify it as soon as possible.

As the proposed system will affect everyone who uses computers within the organisation, you should show everyone the 'preparation and planning' section of this document and provide forum for them to discuss it and feed back to those implementing it.

Because of the scope of this plan in addressing every conceivable computing ramification (to our current abilities), every piece of software being used within the organisation needs to be made known, likewise that which is planned to be used in the future that isn't already being addressed by this roadmap; every format that existing information is stored in must be made known; basically, every information input to and output from the organisation, and every process that takes place with information within the organisation, and communication within and without the organisation, that pertains to computing, must be brought to light and catered for.
In terms of software used, this roadmap presents a delicately balanced, finely matched group of applciations that have been picked to work as well together and with the underlying operating systems as possible. For this reason, if unforeseen software applications, for example, are introduced late in the planning stage it can present greater problems than if they are known about earlier on.

When this computing system is agreed upon, you must be sure you have read this document carefully and checked that every aspect of the transition has been addressed. Any new activity required, after this roadmap has been agreed upon, that is not described in this roadmap, may cost extra. Failing to make light of user data requiring transition from old to new computing system could potentially result in data loss; this document represents all data and systems requiring transition, if they are not represented in this document then it should be assumed they are not known about.

The reponsibility for checking that all such data and systems are represented within this document lies with you, the organisation.

Some terms explained

Notes

Preparation and planning

total time: ? hours

Analysis of your existing computing environment so as to understand the new computing environment required to update it and how to make the transition

Preparation and planning - existing services provided by external organisations

documenting these helps us further understand what is currently going on in the organisation and allows us to consider what can be replaced

Estimated cost and time-line

Research; create required tools and configurations; build test system

total time: ? hours

prior to work at the organisation

at the organisation, and if possible, for prototyping, so staff learn the new software sooner, and can test software and have input into its configuration

Software profile compatibility; installation and configuration details

This section has moved to the seperate document sw-compatibility.html because the width of its table was messing with the width of this whole document

Issues people have found when testing software applications

It is important that people report any issues they are experiencing that appear when testing software we're proposing to use that could prevent them from using it. We will keep track of such issues here.

OpenOffice's bug tracking database can be searched from http://www.openoffice.org/issues/query.cgi
Mozilla's bug tracking database can be searched from http://bugzilla.mozilla.org/query.cgi
Other software's bug reporting and discussion either takes place on mailing lists or not publicly atall.

component

reporter

summary

details

example filename / URI

workaround / fix

severity

status

time taken (testing; researching; communicating)

OpenOffice Writer


table alignment issues

MSWord and RTF export filter wrong table formatting - fixed in 643c and/or CVS

Table formatting messed up when importing from MS Word

Inconsistent behaviour when adjusting table column widths






OpenOffice Writer


how to interface with a MySQL database



there's this (PDF) guide




OpenOffice Writer


duplicates of table cell spanning page break

table cells spanning multipe pages

table cells/rows can not continue over a page boundary

Table in writer can't split cells at page break

long table cells disappear at the bottom of the page






OpenOffice Writer

...

no word count for selection of text

Issue 1793


Issue 4568 has a macro that we could incorporate as something like Tools -> Word Count.


waiting to hear if people want this

13 mins

OpenOffice Writer

...

word count is too hidden


something like File -> Properties -> Statistics -> Word Count

add menu option and/or toolbar button


needs me to implement this











Manual file format conversion

total time: ? hours

Software and licencing

total time: ? hours / total cost of licencing: £? + £? per year

Internet connectivity

total time: ? hours / total cost of connection: £260 + £79.99 per month (about £960 per year)

Further services required from external organisations

Specify hardware to be bought

total time: ? hours / total cost of computer equipment: perhaps £1979.50 (this needs a little amending to reflect price changes) / total cost of networking equipment: perhaps £226
(Definitive hardware costs will not be given as they're subject to so much change. Costs given where second-hand components are expected to be sourced are costs for buying new. Add £133 for more future-proofed tape backup option. Various delivery charges will need to be added, they cannot be calculated in advance as they change if items are out of stock and need re-ordering or ordering from different suppliers.)

Install network

total time: ? hours

Obtain hardware

Build and configure hardware

total time: ? hours

Configure file server software

total time: 8 hours

Configure firewall, NAT router software and optionally DHCP server

total time: 15 mins

Configure mail server software

total time: ? hours

Configure other network hardware

total time: 2 hours

User training

total time: ? hours

Configure workstation hardware

total time: 11 minutes per workstation X ? workstations = ? hours

Configure workstation software

total time: ? minutes + (? minutes per workstation X ? workstations) = ? hours

Configure print servers

total time: 5 minutes per print server X ? print servers = ? minutes

Backup strategy

Other peripherals

total time: ? minutes

are there other existing peripherals to be incorporated into the system? if so they will each involve some configuration

Final system testing and potential troubleshooting

total time: 10 hours?

Installation - workstation transition order

Before installation begins, the file server will be available on the network and staff can copy their private data to it before it is wiped from their workstation. Installation will take place one workstation at a time, in logical groups. We can loan you a machine so that each member of staff has a workstation whilst their's is being transitioned, so there should be little inconvenience. During the transition the existing system will operate alongside the new system as much as is practicable. People will continue with the existing system until their workstation is transitioned, where-upon they will switch to logging into the server; any additional collaborative features provided by the new system will not be fully functional until all people have transitioned to the new system, yet at the same time none of the old functionality will be lost, so nobodoy misses out on anything, again reducing inconvenience.

Installation can take place in the order most convenient to all of us. Please give feedback as to the following suggested transition:

On-going IT support

total time: ? hours

Documentation

total time: ? hours

everything that can be, should be documented

Warranty

Further useful functionality on hold until the future

Areas of importance not addressed by this plan

Changes / Work completed after the last quote