Log In   View a printable version of the current page.
Exchange Maintenance Schedule (ER)
Added by Jeffrey Wix, last edited by Jeffrey Wix on Mar 15, 2007  (view change)
Labels: 
(None)


Exchange Maintenance Schedule

Project Stage

Stage Name Valid  
0 Portfolio requirements  
1 Conception of need  
2 Outline feasibility  
3 Substantive feasibility  
4 Outline conceptual design  
5 Full conceptual design  
6 Coordinated design and procurement  
7 Production information  
8 Construction  
9 Operation and maintenance
10 Disposal  

Overview

The scope of this exchange requirement is to support the exchange of information concerning maintenance schedules.
A maintenance schedule is a type of work schedule in which the work tasks that are scheduled are specifically related the assets that are to be maintained. That is, the maintenance schedule will describe all the maintenance tasks that must be undertaken and the actual dates on which work is scheduled to be done.
Additionally, a maintenance schedule may define required resources to perform tasks in terms of the skills or capabilities required and/or in terms of specific actors.
For a maintenance schedule, the following information will be needed:

  • The maintenance tasks that are to be undertaken with, for each task:
    • Identity of the task (using the general form of identification or breakdown structure adopted for the project)
    • The name of the task (i.e. how it will be shown in a chart)
    • Any further useful description (which may be provided if required).
    • Whether the task is a milestone or has a scheduled duration.
    • Time related information about the task including earliest/latest start dates, earliest/latest finish dates, scheduled start/finish dates, actual start/finish dates. The extent of time related information specified depends on whether the baseline schedule or actual concept schedule is applied.
    • Available float times for the task.
  • The assets on which the work is done

For schedule time, two schedule concepts are identified. These relate to respectively a planned or baseline schedule in which schedule times are proposed and an actual schedule in which times actually taken are retrospectively entered into the schedule. The concepts are:

Concept 1: Baseline Schedule
Includes earliest, latest and scheduled start and finish times. Float times may also be included. Actual start and finish times are excluded together with other values that are dependant on start or finish time.

Concept 2: Actual Schedule
Actual start and finish times are included, earliest, latest and scheduled start/finish times may be adjusted according to circumstances. Float times may also be adjusted. Remaining time for a task may be identified.

Note that it is expected that a baseline schedule will have been created before the actual schedule is composed so that there can be a comparison of actual versus proposed performance.

Information Requirements

Context Description
Precursor Entities that are to be subject to maintenance schedulingare already defined as assets. This means that the er_exchange_asset exchange requirement provisions will have been satisfied.
It is also expected that a maintenance plan will also have been defined through the exchange requirement er_exchange_maintenance_plan. This will facilitate prior identification of tasks. Where this has been done, tasks identified in the maintenance plan can be promoted to the maintenance schedule. However, it is not a mandatory precondition of a maintenance schedule that a maintenance plan should have been defined.
Maintenance Schedule Provides for the capture of all information that defines the maintenance schedule.
Nest Allows tasks to be contained (nested) within other tasks.
Resource Defines resources that may be associated with a task in a work schedule.
1 - Maintenance Schedule - Exchange Maintenance Schedule (ER) (Information Delivery Manual (IDM))
2 - Nest - Exchange Maintenance Schedule (ER) (Information Delivery Manual (IDM))
3 - Resource - Exchange Maintenance Schedule (ER) (Information Delivery Manual (IDM))

Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.1.3 Build:#408 Jan 23, 2006) - Bug/feature request - Contact Administrators