scope:

This Procedure applies to:

• Director, Maintenance

• Director, Supply Chain

• Director, Finance

• Director, Safety and Environment

• Director, Assurance and Safety

• Director, Major Projects and Investment

• Director, Information Systems

• Heads of Asset Management

• Head of Asset Knowledge

• Head of Operations Planning

• Head of Major Stations

• Asset Managers/Infrastructure Contracts Managers

• Business Development Managers

• Zone Heads of Projects

• Zone Financial Controllers

- and all their staff involved with asset maintenance and renewal (including the management and reimbursement of contractors providing such services), maintaining asset data bases and the production and procurement of new contracts. It also covers the upkeep and future development of the MIMS system. NOTE: The Infrastructure Contracts Managers' (ICM) organisation was due to be reorganised by 23 April 2000 when the ICM title changed to "Asset Manager". In this Procedure both titles are used (AM/ICM) and the title that is in use on the zone concerned shall be that which is deemed to apply.

Initially MIMS (Release 2.1) will only apply to the IMC2000 infrastructure maintenance contracts and Operations Property contracts and this is reflected in this issue of this Procedure. Future releases of MIMS will extend its application and this Procedure will be re-issued to encompass the new/changed responsibilities.

MIMS shall not be applied to existing RT1A and IMC2 infrastructure maintenance contracts unless they are converted to IMC2000.

Purpose

As part of Railtrack's Asset Management Programme MIMS is being progressively introduced as a system for managing and recording asset maintenance, enhancement and renewal activities.

For the configuration and use of MIMS a suite of Process Operating Policies (POPs) and MIMS Operating Policies (MOPs) have been produced and these are contained within a computerised Knowledge Base available to users on line.

This Procedure mandates the use of the MIMS system and sets out the roles and responsibilities for its implementation, use, subsequent upkeep of the Knowledge Base, and revision of the enshrined task schedules to take account of changed or new maintenance standards.