Introduction and Overview
Introduction and Overview
The aim of this document is to provide an overview of the usage and functionality of Agility, discussing the standard forms that are delivered with the standard Agility application.
Overview
Agility contains all the capabilities necessary to set up and run a simple but comprehensive maintenance planning and control system for both planned and non-planned tasks. Work Orders are produced when required to initiate jobs. Extensive plant, task, and fault histories are automatically maintained. A wealth of standard management reports is available, including forward projections along with graphical presentations of performance, overdue task reports and extensive fault reporting.
The core of Agility is the Equipment Register. This can be accessed by using the Equipment Code, through a hierarchical tree structure, or through any significant element of data associated with an equipment item.
The Equipment Register contains all the standing data for each item of equipment. Recording such information as downtime, and costs for both Labour and materials, by type of work. It also contains on a job by job basis a summary of every job performed on each item, so instant plant histories are always available at the "touch of a button".
The structure of the Equipment Register is such that it is very easy to compare the relative performance of like items of plant. To aggregate the activities on a number of items to form an overall performance view of a factory, building, etc., comprising many individual equipment items at different levels.
Work Orders for non-planned tasks, e.g. breakdowns are available instantly and those for planned tasks are available on a call off basis.
Planned tasks within Agility can be scheduled according to a variety of different “cycle” patterns. The available “cycles” are as follows:-
Cycles of days
Cycles of weeks
Cycles of calendar months
Cycles of calendar years
It is also possible to create schedules with either of the following criteria:-
Tasks required on demand
Once only incidents
Planned work can have either an “infinite” life span or it can be restricted to a specific number of occurrences thus giving it a “finite” life span.
