To define the operating parameters for a planned maintenance contract

The operating boundaries for contracts linked to a specific programme are defined across a number of parameterised control areas. Of particular note is the Enable Date Variations attribute, which will automatically track instances where the start or end dates linked to components within an active contract - phases, phase assets, works orders, or tasks - are adjusted, triggering a related variation record to capture the impact on the delivery timeline.

The procedure to define the operating parameters for a planned maintenance contract is as follows:

Prerequisite procedural steps are covered separately in the topics To create a new planned maintenance contract and To allocate devolved budget figures to a planned maintenance contract. Refer to these before proceeding to step 2.
With the New Contract (Step 3) window in current focus, establish the operating parameters applicable to the planned maintenance contract.
Where it is permitted for a single appointment to cover several days, activate the Allow appointments to span days tick box provided.
Using the Appointment mechanism drop-down field, select the resourcing schedule that is supported by the contractor e.g. Civica Housing Diaries, Click Field Service Edge, Kirona Xmbrace DRS, etc. 1.
Where the contractor is not permitted to apply variations to SOR tasks included on a repair works order, activate the No variation tick box provided.
Complete the order values and quantity thresholds applicable to the planned maintenance contract as described in the table below.
Select the Authorisation model for the planned maintenance contract, reflecting the required levels of authorisation to be granted by different stakeholders in response to contract deviations.
Activate the Enable date variations attribute to trigger timeline variations arising from date revisions applied to related contract entities.
Click on Next. The New Contract (Step 4) window is displayed, ready to assign the contract definition. This requisite step is covered separately in the topic To configure the planned maintenance contract definition.

Note

1 To assess a contractor's availability, all diary information is either stored internally within a 'Civica Housing Diary', or obtained from an external dynamic resourcing schedule, often used to optimise mobile field workforce activities.

Field	Description	Additional Notes
Minimum Order Value	The minimum single order value accepted by a contractor and based on the published cost of the work.	None
Maximum Order Value	The maximum single order value awarded to a contractor, based on the published cost of the work.	None
Maximum Variation Value	The maximum value by which an order can vary against the published cost of the work.	None
Maximum Variation %	The maximum variation by percentage that an order can differ from the published cost of the work.	None
Maximum In Progress Value	The total permitted value of concurrent orders currently in progress that can be undertaken by a contractor, based on the actual cost of each order.	The additional calculated field Actual In Progress Value is used as a tracking mechanism for this contract parameter.
Maximum In Progress Jobs	The total permitted number of concurrent jobs currently in progress that can be undertaken by a contractor at any one time.	The additional calculated field Actual In Progress Jobs is used as a tracking mechanism for this contract parameter.
Maximum Contract Value	The total value of concurrent orders permitted for a contract based on the actual cost of each order.	The additional calculated field Contract Value To Date is used as a tracking mechanism for this contract parameter.

See related topics...

Planned maintenance contract management overview

To create a new planned maintenance contract

To allocate devolved budget figures to a planned maintenance contract

To configure the planned maintenance contract definition