Maintenance Planning

Planning and balancing maintenance resources (Maintenance Persons and Tool/Equipment) against work demand using the Maintenance Planning Board (MPB), Resource Navigator, resource groups with finite/infinite capacity, and calendars to produce a feasible, capacity-constrained schedule.

Planning material and spare parts demand for maintenance work using object part lists, detached spare part lists (kits), material lines on Work Orders / PM actions, and cross-references to IFS/Inventory for balances, prices and suppliers, including material availability constraints in scheduling.

Defining and managing the scope of maintenance work through PM actions/plans, Work Orders and Work Order Structures, Work Tasks and PM Work Lists, task cards and work list requirements, so that packaged, repeatable maintenance scopes can be prepared, released and executed.

Assigning criticality to equipment objects and using it to prioritize maintenance work - critical work is derived from work type, object criticality and priority, defined in Work Order PM Basic Data and used to prioritize scheduling of critical work in the MPB.

Route-based infrared thermography and ultrasonic or partial discharge surveys of the electrical and mechanical infrastructure, planned in IFS Cloud as condition-based PM Actions and executed as survey Work Orders. Delta-T and ultrasonic readings are captured as Measurement / Parameter values with thermograms attached as Documents, and actionable findings become prioritised corrective Work Orders. Measurement history then feeds the condition-based PM forecast so survey and repair intervals reflect real asset condition.

Proves, before any planned intervention, that the affected component can be isolated and maintained without interrupting IT operations. The power and cooling distribution paths are mapped onto the IFS Cloud Functional Object structure, loss of redundancy during the window is modelled against load and capacity limits, and the outcome is recorded as a controlled Document linked to the change and Work Order. The agreed window is written back as an Operational Plan maintenance window so IFS scheduling will not permit obstructive work outside it.

Runs the preventive and predictive maintenance programme for a live 24x7 data centre using IFS Cloud EAM and Planning & Scheduling Optimization. PM Plans generate Work Orders from calendar, event or condition criteria; work value is set from Work Type, Object Criticality, Task Priority and Event so critical-infrastructure work outranks routine tasks; and Operational Plan maintenance windows block obstructive work outside agreed periods. MPS Cluster IDs group assets that must be shut down together so the number of maintenance stoppages is minimised.

Governs the forecasting, reservation and release of power, cooling, floor space and floor-loading capacity across white space and supporting plant in IFS Cloud. Design envelopes and live headroom are held against the Functional Object hierarchy (site, data hall, room, cage, cabinet) with Measurement / Parameter readings interfaced from DCIM and BMS, so no deployment consumes headroom before its capacity request is approved. Approved reservations then drive PM review, Project demand for expansion and long-lead Purchase Order triggers.

Defines and maintains the interval-based maintenance programs that drive planned maintenance for serialised platforms in IFS Cloud, where a maintenance program is assigned per part number with maintenance groups reflecting different operational conditions, and a maintenance plan holds maintenance codes with intervals against operational parameters and calendar time. Due calculation works through the serial maintenance plan using the value since overhaul of the operational parameter, and creates a pending maintenance event when the calculated due date falls inside the days forewarning. For plant and equipment the equivalent construct is the PM action, a revision-controlled template that generates work orders by Calendar, Event, Condition or Manual methods.

Runs the cyclical condition survey of the building fabric and M&E elements, grades and costs the findings, and converts them into a multi-year lifecycle replacement and backlog plan in IFS Cloud. Approved years of the plan are released as Projects and Work Orders, and revised remaining-life data is written back to the asset register so the next survey starts from a maintained baseline. This is the client-side capital planning view, distinct from contractor PPM delivery.

Runs the estate-wide energy and carbon cycle for an integrated FM portfolio, from metered consumption through to statutory disclosure. Consumption is captured as Measurement / Parameter values against the Functional Object hierarchy in IFS Enterprise Asset Management and consolidated in IFS Cloud Sustainability Management, which provides a KPI library, planning and a centralised data source. The output feeds the GHG inventory, the SECR disclosure and the ESOS compliance notification.

Establishes and runs the written distribution integrity management programme required by 49 CFR 192 Subpart P on top of the IFS Cloud asset register. System knowledge is held on Linear Assets and Functional Objects, threats are evidenced from leak, corrosion, patrol and excavation-damage history, and the resulting risk-reduction measures are released as Maintenance Plans and Work Orders. Performance measures are aggregated from Work Order and Fault Report outcomes for the annual PHMSA submission.

Runs the gas transmission integrity management programme required by 49 CFR 192 Subpart O against the IFS Cloud linear asset model. Covered HCA segments are flagged on Linear Assets, baseline and reassessment plans are scheduled as Maintenance Plans, and anomalies found during assessment drive remediation Work Orders inside the mandated response clocks. Assessment results, management-of-change and quality-assurance evidence are retained as linked Documents.

The shared analytical engine beneath DIMP and TIMP: gathers and integrates pipeline attribute data, classifies threats into the ASME B31.8S categories, scores a threat register and pushes the resulting rank back onto IFS Cloud Linear Asset segments as Criticality. Accepted risk-reduction activities leave the process as Maintenance Plans and Work Orders, closing the loop between analysis and field execution.

Covers converting the configured PPM regime into a dated, resourced annual maintenance plan and then optimising the resulting visits into efficient engineer routes. Tasks of differing frequencies are consolidated into visits, visits are levelled against labour capacity and statutory due dates, and journeys are sequenced to reduce travel while protecting compliance windows. The output is the annual planner the client signs off and the work order pipeline the mobile workforce executes against.

Manages the lifecycle integrity of producing, injection and suspended wells by representing wells and their barrier elements in the IFS Cloud asset structure and driving periodic barrier verification through Maintenance Plans and Work Orders. Annulus pressure, subsurface safety valve tests and barrier element inspections are captured as Measurements against the well object, evaluated against defined limits, and exceptions raised as Fault Reports. Degraded barriers escalate to remedial Work Orders or a controlled shut-in, with the full evidence trail retained in IFS Document Management.

Establishes condition-based maintenance across production-critical assets by defining condition parameters in IFS Cloud, ingesting vibration, temperature, oil analysis and process data from CBM and SCADA sources as Measurements, and evaluating them against alarm limits. Limit breaches and adverse trends automatically generate condition-based Work Orders ahead of functional failure. Executed interventions are reviewed against the original prediction so alarm limits and models are tuned, moving the fleet from calendar-based PM toward evidence-driven intervention.

Plans a refinery, gas plant or offshore turnaround (TA) in IFS Cloud from scope call-off through to a hard scope freeze and baselined schedule. The turnaround is registered as a Maintenance Event that drives PM Action generation, and mirrored as a Project with a WBS of Project Activities for cost, schedule and progress control. Scope candidates are drawn from due PM Actions, deferred Work Orders, Fault Reports and inspection recommendations, then challenged, ranked and frozen against the Functional Object hierarchy.

Runs a risk-based inspection programme for fixed equipment and piping using API RP 580 and API RP 581 methodology, where risk is assessed as the product of probability of failure and consequence of failure and used to prioritise and schedule inspection. IFS Cloud carries the resulting inspection plan as PM Actions and Work Orders against the Functional Objects, with condition data captured as Measurements and integrity operating window excursions raised as Fault Reports. The RBI analysis itself, including corrosion loops and damage mechanism registers, has no standard IFS Cloud object and is normally held in a specialist integrity data management system.

Establishes the maintenance strategy for oil and gas assets using RCM as defined by SAE JA1011 and JA1012, supported by FMECA to the MIL-STD-1629A method for criticality ranking. The resulting task selection is loaded into IFS Cloud as revision-controlled PM Actions and maintenance plans against Functional Objects, and the failure data captured on Work Orders and Fault Reports is coded to the ISO 14224 taxonomy so the strategy can be reviewed on evidence. The FMECA worksheet itself has no standard IFS Cloud object.

Periodic and online monitoring of oil-filled power transformers, load tap changers and bushings using dissolved gas analysis and oil quality testing to detect incipient faults before failure. In IFS Cloud the sampling cycle is driven by Preventive Maintenance Actions against each transformer Functional Object or Serial Object, lab results are stored as Measurements against the object, and diagnostic exceedances raise Fault Reports that drive engineering assessment and corrective Work Orders. The resulting gas and oil history becomes the transformer health record used for risk ranking and replacement planning.

Programmatic shift from purely calendar-based maintenance to condition-based and predictive maintenance across transmission and distribution assets, using inspection findings, test results, online monitors and operating data to decide what work is done and when. In IFS Cloud the programme is built on Measurements and condition rules against Functional Objects that generate Work Orders only when a condition threshold or predicted failure risk is reached, with asset Criticality determining the response. The resulting risk view is used to reallocate maintenance spend and to feed asset investment planning.

Turning condition, age, duty and failure data into an asset health index per asset class, combining it with consequence of failure to produce a risk score, and using that score to rank maintenance, refurbishment and replacement investment across the T&D portfolio. In IFS Cloud the inputs are already resident - inspection Measurements/Parameters, Fault Report history and Work Order cost against Functional Objects, Serial Objects and Linear Asset segments, with Criticality carrying the consequence dimension - and the scored output drives PM regime changes, corrective work prioritisation and the capital project pipeline. The framework is the CIGRE and ISO 55000 model in which risk is probability of failure multiplied by consequence of failure, expressed through an asset health index.

Converts inspection findings and cycle policy into the annual vegetation work plan and dispatches contractor line-clearance crews against it. In IFS Cloud the plan is carried by Maintenance Plan / PM Action and Work Orders against Linear Asset spans, while contractor capacity, unit rates and settlement run through Supplier Agreement and Purchase Order. Completion tracking supports the FAC-003-5 R7 obligation to complete 100% of the annual vegetation work plan.

Bundles outage-dependent maintenance, capital and inspection work into approved outage windows, obtains the operational and reliability approvals, and executes the clearance and tagging that protects the workforce. IFS Cloud holds the outage request, the bundled Work Orders and Work Tasks, the controlled clearance documents and the as-left asset record; switching authority and device operation remain with system operations. The process must also support late cancellation or recall of outages when system conditions change.

Turns machine telematics into maintenance demand. Hour meters, fuel data, fault codes and location are ingested from OEM and third-party providers over the ISO 15143-3 (AEMP 2.0) fleet data interface and posted as measurements against IFS Cloud Equipment Object parameters. When a measured value falls outside acceptable limits, the connected PM Action generates a Work Order automatically.

Assess the condition of distribution assets (desktop scoring from age/material/break history plus field techniques such as coupon sampling, CCTV for large mains, and inspection findings) and score criticality as likelihood-of-failure x consequence-of-failure, following EPA asset management practice where critical assets are those with high failure risk and major consequences. The resulting risk matrix drives maintenance strategy, inspection frequency, and the renewal candidate list.

Translate risk and condition intelligence into a funded multi-year renewal and replacement program: forecast remaining useful life and renewal needs by cohort, prioritize candidates from the risk register, bundle work into projects coordinated with paving/other-utility programs, evaluate repair-vs-replace economics, and maintain the capital improvement plan and its funding view. EPA asset management practice centers on planning maintenance/repair/replacement and funding it sustainably; IFS positions Asset Investment Planning for exactly this decision layer.

Moves high-criticality plant assets off fixed-interval PM and onto condition. Vibration, bearing temperature, motor current, pump efficiency and seal condition are captured as Measurements against the Functional or Serial Object in IFS Cloud, evaluated against alarm and alert limits, and used to raise a corrective Work Order only when the asset condition warrants it. IFS positions predictive maintenance as a data and sensor driven forecast of equipment failure before it occurs, so the utility reduces unplanned downtime and extends asset life.

Plans and delivers the periodic outage of a treatment train, digester, clarifier, filter bank or major pumping station where the plant must stay in permit compliance while an asset is out of service. Scope is built from deferred corrective work, condition findings and statutory inspections, held as a Maintenance Event with linked Work Orders and managed against a Project with Project Activities for schedule and cost. Long-lead materials, contractors and bypass arrangements are secured before the shutdown window is approved.

The plant baselines energy consumption by process area, identifies and appraises energy conservation measures, and delivers them as IFS Cloud Projects or Work Orders with measured savings tracked afterwards. Energy consumption is recorded against Functional Objects as Measurement / Parameter data so aeration, pumping and sludge processing loads can be attributed and trended. EPA guidance treats energy as the largest controllable cost of providing water and wastewater services, which makes this a recurring optimisation cycle rather than a one-off project.