industry
The contract is availability, not job count.
Sustainment of platforms and support equipment, where configuration, clearance and traceability decide what can be done and by whom.
what is different here
Readiness sets the schedule.
-
Clearance and site access bind as hard as trade skill
The right technician for the task may not be the right technician for the location. Access approvals, escort requirements and currency all narrow the pool before competence does.
in Etaprise → assignment gated on access and currency, not only trade
-
A part fitted has to trace to a baseline
Serialised items move between platforms and depots. If the record of what is fitted where drifts from the configuration baseline, the paperwork problem arrives later than the maintenance one.
in Etaprise → serial-level fitment history against the asset
-
Deep maintenance competes with operational readiness
Scheduled deep work takes a platform out for a long window, while the availability target is measured over the same period.
in Etaprise → planned downtime visible against the availability commitment
On site
the setup
The modules that carry most of the weight here.
The other eleven are still there. Sector setup changes which forms attach to a job, which certifications gate an assignment, and what a closed job has to prove, not which software you are running.
what a rollout looks like
In order, and with honest timings.
Configuration control and personnel constraints have to be right before scheduling means anything. This sequence establishes what is being maintained and who may touch it, then puts the work against it.
-
weeks 1–3
Asset structure and baselines
Platforms, sub-assemblies and support equipment with serials and the configuration they are held against, because every later record hangs off this structure.
-
weeks 2–5
Personnel, currency and access
Trade authorisations, currency dates and the site access each person holds, loaded so that an assignment cannot be made to someone who cannot lawfully carry it out.
-
weeks 4–8
Maintenance programme and parts
Scheduled servicing, deep maintenance windows and serialised issue and fitment, so what was consumed and what was installed is recorded as the task is done.
-
ongoing
Availability reporting
Downtime attributed to cause, planned windows separated from unplanned, and the maintenance record behind each period the contract is assessed over.
questions from this sector
The objections we hear, answered plainly.
Hosting location and environment are a customer decision, and accreditation is assessed against your environment and your security authority, not granted by a vendor claim. We will tell you what the software does and how it is deployed; we will not tell you it arrives pre-approved for your programme.
Yes. Access approvals and currency are held per person and per site and are treated as hard constraints alongside trade competence, so the scheduler does not offer a technician who would be turned away at the gate.
Serialised items are recorded as they are issued, fitted and removed, against the asset and the task that moved them, so the as-maintained record can be reconciled to the baseline. The authoritative baseline usually remains in your configuration system; this keeps the field activity traceable to it.
Then utilisation is the wrong thing to optimise. Work is prioritised by what it returns to service and when, planned downtime is separated from unplanned, and the schedule can be read as its effect on readiness rather than as a queue length.
further reading
Further reading
Bring us one platform and its tasks.
A maintenance programme and the constraints on who may work it. We will schedule against both.
Book a demoother industries