Online Systems Plan

Below is a simplified representation of the new website & online services that are envisioned and being discussed here. Click on the diagram and you'll be able to access links to the specific topics on this blog. These links to topics & examples will expand as this project/blog develops.

Please add your suggestions or queries about the online services to be available and how these systems will work (i.e. be accessed, integrated, etc).

Online Systems Principles & Guidelines

(1) That the services & capability developed & made available will be through systems that have the flexibility to serve various purposes and requirements. i.e. The solutions deployed should be able to serve all areas & allow different customization. E.g. All current & future IAT-related websites will be able to be created on the same application and take advantage of the same services.

(2) That the systems are fully-integrated where it makes sense (e.g. calendar & form functionality with the website) but also modular wherever possible (e.g. e-learning & intranet capability separate from the website but readily linked from it). This will allow maximum flexibility in terms of usage, development and future solution-replacement, while enabling a seamless user experience.

(3) That each system has clearly identified purposes & audiences. Hence, there will also be an evident delineation of content and services. E.g. The intranet will serve the information & service requirements of existing staff while the IAT website will serve prospective staff. Duplication will be avoided through effective interfacing of systems.

(4) All delivered solutions to be scalable, extensible and customizable where possible - to allow extended or new types of usage in the future.

(5) The website is to act as a portal/gateway to all online services without impeding their ability to function independently.

(6) All developed online capability should enable advanced usage by expert staff but be designed for simple usage by all staff.

(7) The new systems developed will incorporate (or readily allow through "plug-in" extension) as much functionality as is necessary to enable all likely future requirements even if these are not deployed when first released. This will allow the systems to "switch on" these "hidden" capabilities at a later date, rather than requiring development changes to production systems.

(8) Open, widely-used & modern technology that is accessible to everyone to be preferred to proprietary or custom systems.

(9) Technology costs of systems & contractual vendor arrangements to be minimized or avoided if possible.