PM programmes, acquisition requests and activity reports

Three objects formalise the relationship between the maintenance contractor and the asset owner: the PM programme (what will be done in the period), the RIA (what must be bought to do it) and the activity report (what was done). Each follows an approval circuit, typically contractor then asset owner (see the Companies and contracts chapter).

PM programmes (Maintenance > PM programmes)

Methods engineers create the month's or year's programme for a site (and a contract): occurrences of the active preventive plans within the period are computed automatically — chained calendar due dates, meter-based due dates estimated from the last 90 days of consumption (marked *) — with the discipline and estimated hours. Each line can be included or excluded, moved, annotated; Recalculate lines refreshes the due dates without losing these choices.

Submit for approval starts the circuit configured for the PM programme target; without a circuit, the programme is approved directly. Once approved, Release work orders issues the work orders of the included lines (preventive type, planned due date, contract), and Create parts RIA computes the parts needs of the task lists involved minus the site's stock. The Program.RestrictGeneration setting reserves the nightly generation to plans outside programmes: programmed plans are only issued at release.

Acquisition requests (Stock > Acquisition requests (RIA))

A RIA groups catalogue or free part lines (quantity, unit, estimated cost), with a justification and a needed-by date. It is submitted to the Acquisition request circuit, then marked ordered (order reference) and finally received into a warehouse: quantities enter stock through receipt movements referenced by the RIA number.

Activity reports (Reliability > Activity reports)

A report covers a period (daily, weekly, monthly, quarterly, half-yearly, annual) for a site, consolidated or per discipline. Its figures are computed: work orders created, completed, closed, open and overdue at period end, estimated and actual hours, downtime, failures, parts cost, requests, permits, readings, SCADA alerts, KPIs (availability, MTBF, MTTR, preventive ratio, schedule compliance), breakdowns by discipline and type, worst-performing equipment, list of completed work orders with the crew. The author completes the summary, highlights, issues and next actions, then submits: the Activity report circuit chains for example CSR → contractor's operations management → asset owner. The PDF includes everything with signature boxes.

Consolidated weekly and monthly reports are created automatically as drafts (Reports.AutoWeekly, Reports.AutoMonthly, and Reports.AutoDaily for the daily one) and notified to planners.