In-service support & Maintenance

An on-site service agreement between a service provider and a customer for the comprehensive service of a computer system or a network in the State of Victoria, consisting of both hardware and software, in return for an annual service fee. This is a "best effort" agreement which relies upon the goodwill of both the service provider and the customer to do the best by each other, and therefore does not contain the strong concepts such as "measure of performance" and "minimum performance levels" and "maximum down time" etc.

This contingency plan is designed for system outage. It describes the system, its related systems and their inter-dependencies. It shows how to calculate the risk factor based on the operational risk model and assists in describing three types of trigger, time-based or management-based. It promotes 2 types of strategy, a general strategy and strategies particular to the trigger.

Daily Backup Logbook designed for the year 2004. Alternating Friday. International planning worksheet.

A simplified documentation plan for a set of network manuals as per AS/NZS 4258:1994. International planning worksheet (AS/NZS4258)

This register is for the issue of keys out of the key cabinet to allow temporary access and includes the rules for control of this process. Very useful for areas of increased security such as the computer room. International security document.

An on-site service agreement for a computer system or a network in the State of Western Australia, in return for an annual service fee. Smaller system, no penalties. Australian legal agreement.

SLA executed in the State of Western Australia for a key computer system or network, in return for an annual service fee. Larger system, penalties apply. Australian legal agreement.

The purpose of this SLA (prepared for a provider of IT services to clients with major servers and large networks and executed in the Australian Capital Territory) is to formalise instructions to the service provider to deliver agreed support services at specific levels of support and at an agreed cost to the client. In order to do that, the agreement must describe clearly the system being supported (inclusions and exclusions), the type of support being provided, and the expected time frames.

This current requirements model is designed for a disaster recovery plan for a mainframe, but could also be used for basic housing when planning to implement a new system.

• Standards - Disaster recovery planning

The maintenance control book records a series of checklists to ensure that the maintenance is carried out on temporally generated schedules. It includes the weekly maintenance schedule, the monthly maintenance schedule, the yearly maintenance schedule and the daily, as required and constant vigilance maintenance schedule.