Aircraft maintenance learning · worked examples
Aircraft maintenance, one traceable decision at a time
Learn aircraft configuration, component life and maintenance planning through a connected worked-example fleet and practical ACM and Aviation journeys.
For technicians, planners, engineers and records teams. Start with J00 to produce an aircraft identity sheet in five minutes. Reading and browser practice use a fictional TRAIN fleet.
Historical reference: Manage 9.2.197, Aviation 9.2.15 and ACM 9.2.25. Select the terminology for the installed product before applying a documented procedure.
All add-on learning · Aviation fundamentals · ACM fundamentals · Schematic guided tours
The worked-example fleet
TRAIN-SITE / TRAIN-ORG. Model → build position → eligible part → serialized engine → installation history → meter readings → maintenance work. A model describes allowable configuration; a serialized asset identifies one physical component.
| Aircraft | Model | Engine | Open work |
|---|---|---|---|
| TRAIN-AC-001 | TRAIN-TWIN-A | TRAIN-ENG-001 | TRAIN-WO-001: Engine change approaching; late usage correction |
| TRAIN-AC-002 | TRAIN-TWIN-B | TRAIN-ENG-002 | TRAIN-WO-002: Variant B; excluded from TRAIN-NOTICE-001 |
| TRAIN-AC-003 | TRAIN-TWIN-A | TRAIN-ENG-003 | TRAIN-WO-003: Open discrepancy; candidate receipt awaits inspection |
Start here
J00 · Find an aircraft and explain its current state
Beginner · Technician · 10–15 min (planning estimate)
fewer wrong-aircraft, wrong-part, and wrong-time assumptions. No maintenance or airworthiness conclusion should be drawn from one status colour.
Prerequisites: Start here. verified aircraft/equipment or Assets (CM) viewing; prepared fixture; read-only training role.
Worked example: one aircraft, installed engines/pump, a historical timestamp, one open maintenance item.
Documented applications: ACM — Assets (CM); Aviation — Aircraft and Equipment.
- Choose the ACM or Aviation terminology track. In Assets (CM), or Aircraft and Equipment, filter the prepared TRAIN site and search for TRAIN-AC-001. In this browser example, select the aircraft in the fleet diagram.
- Read the asset number TRAIN-AC-001, serial TRAIN-AIRFRAME-001 and model TRAIN-TWIN-A. The asset number identifies the record; the serial identifies the physical article; the model describes allowable configuration.
- Open the installed hierarchy and follow the LEFT-ENGINE position to TRAIN-ENG-001. Compare its part TRAIN-PART-ENG-A with its unique serial TRAIN-SERIAL-ENG-001.
- Check the current-versus-historical timestamp, location TRAIN-HANGAR and linked work TRAIN-WO-001. Read meter units separately: FH means flight hours and FC means flight cycles.
- Write an identity sheet containing the site, aircraft, installed engine, position, observation time and open work. In a training system reopen both parent and child to verify the reciprocal relationship.
Negative case and recovery
similar serials, wrong site, historical rather than current view, and a restricted role. Teach the learner to detect each mismatch rather than claim missing records.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
a compact identity sheet with correct IDs, current versus historical timestamp, child relationships, meter timestamp, and linked work record. Include an annotated real screen capture.
Explain: Which identifier names the physical engine, and which names its interchangeable part?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
Everyday maintenance
J04 · Reconcile aircraft and component life
Intermediate · Records specialist · 30–45 min (planning estimate)
reconcile usage and avoid maintenance decisions based on an incorrect component total. Aviation meter definitions, ACM direct readings.
Prerequisites: J02. verified meter setup, initial/anchor readings, installed-history calculation, and supported correction actions; J02.
Worked example: the independent meter oracle above, including separate FH and FC readings with precise times.
Documented applications: ACM — Assets (CM) / meter readings; Aviation — Aircraft and Equipment / meter readings.
- Use the baseline at 2026-10-01 00:00 UTC: airframe 1,000 FH / 500 FC; engine A 400 FH / 250 FC. Keep total lifetime separate from time since overhaul.
- Add flight TRAIN-F1 at 2026-10-02 10:00 UTC: +2.5 FH / +1 FC. Add TRAIN-F2 at 2026-10-03 10:00 UTC: +1.5 FH / +1 FC. The airframe is 1,004 / 502 and engine A is 404 / 252.
- Record the swap at 2026-10-04 10:00 UTC. Engine A leaves the aircraft; engine B starts with its own 250 FH / 120 FC. Preserve the removal and installation anchors.
- Add TRAIN-F3 at 2026-10-05 10:00 UTC: +3 FH / +2 FC. Use the independent worksheet to calculate each lifetime, then compare fresh persisted totals if running in the training system.
- In a separate correction branch, add +0.5 FH / +1 FC to TRAIN-F2 before the swap. The removed engine A receives the historical increment; engine B does not. Explain each changed total.
Negative case and recovery
actual versus delta confusion, hours-versus-cycles mix-up, duplicate ingestion, out-of-order data, and the installation/removal boundary. Test correction behavior in a separate branch; do not promise that all bad readings are automatically rejected.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
source readings, meter type/unit, direct/derived totals, install offsets, calculation worksheet, and final persisted values.
Explain: Which engine receives a correction dated before the swap?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
J07 · Record a discrepancy and manage an authorized deferral
Advanced · Maintenance controller · 30–45 min (planning estimate)
preserve accountability for work intentionally postponed. ACM deferral workflow, ACM deferral statuses, Aviation deferral codes.
Prerequisites: J00. verified Flight Log Book/discrepancy/deferral capability and role controls; a documented synthetic training policy. Offer separate ACM and Aviation instructions.
Worked example: one fictional non-critical discrepancy, a corrective work order, training deferral criteria/period, and a second open discrepancy for comparison. No real dispatch or MEL authorization is implied.
Documented applications: ACM — Flight Log Book; Aviation — Flight Log Book.
- record the issue, create the linked corrective work, inspect applicability and permitted deferral details, activate the training deferral with the appropriate role, review the revised due information, complete corrective work, and verify the linked records close as expected.
Negative case and recovery
no permitted deferral, expired deferral, second active deferral, closed/completed work order, missing authority, and another unresolved discrepancy. A deferred issue must not imply the aircraft is released.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
discrepancy, deferral, work order, reason, dates/meters, role, status history, and relationship to the remaining aircraft issues.
Explain: What other open discrepancy remains after this deferral?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
J08 · Execute maintenance with material traceability
Intermediate · Technician · 35–50 min (planning estimate)
make execution cost and material provenance explainable. Do not treat a manually entered attachment as a validated certificate or assume qualified sign-off exists. Work execution and actuals, Inventory traceability.
Prerequisites: J05. authorized training work order, verified actuals/material issue functions, required inventory and role setup. Receiving/inspection and certificate fields are optional capability branches.
Worked example: work order from J05/J06, replacement rotable, consumable batch, tool, labour entry, and a watermarked sample inspection/receipt document.
Documented applications: ACM — Work Order Tracking; Aviation — Work Orders.
- review the work scope and safety references, issue the intended material, record labour/material/tool actuals and a fictional finding, associate required evidence, and complete the configured review/status steps.
Negative case and recovery
unavailable stock, wrong serial/batch, restricted storeroom, an item awaiting inspection, missing documentation, or incomplete child work. Identify which constraints are enforced and which require a process checklist.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
work status/history, actuals, inventory issue/return references, serial/batch linkage, attachment identifiers, remaining work, and reviewer action where configured.
Explain: Which serial and issue record explain the material consumed?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
J09 · Receive, inspect, and quarantine a replacement component
Intermediate · Stores · 25–40 min (planning estimate)
expose component provenance and receipt-quality exceptions before installation. Tracking receipt of a certificate is not independent validation of its authenticity. Inspecting parts.
Prerequisites: J00. verified Receiving and Inspection branch, approved training receipt/order data, and isolated stores. If unavailable, show the narrower supported receiving process without copying Aviation-specific screens.
Worked example: one accepted serialized component, one discrepant component, their fictional receipt documents, inspection and quarantine locations, and a consumable batch.
Documented applications: ACM — Receiving; Aviation — Receiving and Inspection.
- receive by serial or batch as appropriate, review age/life details where supported, record inspection, accept one item, and quarantine the discrepant item for disposition review.
Negative case and recovery
mismatched serial/document, missing certificate information, wrong quantity, or nonconformity. Test actual issue/installation controls without claiming quarantine automatically enforces every restriction.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
source order/receipt line, serial/batch, inspection result, certificate receipt indicator if available, nonconformity, current location/status, and inventory impact.
Explain: Which receipt evidence permits the part to leave inspection?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
Configuration and traceability
J01 · Model an allowable aircraft configuration
Beginner · Configuration engineer · 30–45 min (planning estimate)
make configuration policy explicit and reproducible before operating on individual aircraft. ACM models, Aviation models.
Prerequisites: J00. model/build-position/revision functions and suitable training permissions; J00.
Worked example: fictional twin-engine model; variant A/B; serialized engine and pump positions; nonserialized fastener quantity; eligible and ineligible part references.
Documented applications: ACM — Models; Aviation — Models.
- build the small hierarchy, associate permissible parts/items, configure the variant difference, link a meter and maintenance reference where supported, create a dated revision, and explain reference model versus physical aircraft build.
Negative case and recovery
missing required position, incorrect quantity, ineligible part, and a future-dated revision. Do not assume that editing a draft immediately changes the active validation basis.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
model/configuration/revision IDs, effective dates, active revision, position hierarchy, quantity rule, and allowed-part records. Show the baseline diagram and actual application tree together.
Explain: How does the allowable model differ from the installed aircraft?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
J02 · Build an aircraft from serialized rotables
Intermediate · Records specialist · 25–40 min (planning estimate)
trace each physical component independently of its interchangeable part number. Installing in build positions.
Prerequisites: J01. verified CM asset/equipment creation and installation workflow; active model fixture from J01 or instructor-prepared equivalent.
Worked example: aircraft serial, separate engine/pump serials, part/item master references, stores locations, baseline meter values, installation timestamps.
Documented applications: ACM — Assets (CM); Aviation — Aircraft and Equipment.
- establish serialized records, associate the aircraft/model, install eligible children into the intended positions, and distinguish consumable quantity from serialized identity.
- Use the documented receiving route if that is the chosen supported entry path.
Negative case and recovery
a serial already assigned elsewhere, wrong part family, wrong variant, or ambiguous installation time. Record what the installed system actually enforces.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
reopen both parent and child; verify reciprocal relationship, position, location, serial, installation date, and baseline meter linkage. Re-read the history after saving rather than rely on a confirmation toast.
Explain: Do the aircraft and engine agree on the installation position and time?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
J03 · Diagnose and resolve a configuration exception
Intermediate · Configuration engineer · 20–35 min (planning estimate)
explain why a build is nonconforming and demonstrate the correction. A BDI pass is not a regulatory release-to-service decision. IBM BDI behavior and status.
Prerequisites: J02. BDI available and healthy; model and physical-build baseline; permission to validate a training hierarchy.
Worked example: one deliberately introduced error per branch: missing mandatory item, incompatible part, or incorrect nonserialized quantity.
Documented applications: ACM — Assets (CM) / BDI; Aviation — Aircraft and Equipment / BDI.
- capture a known baseline, introduce the controlled exception through supported training actions, run the installed validation action, interpret the actual problem message, correct the underlying issue, and validate again.
- Compare an alternative configuration only where supported and never silently apply it as a shortcut.
Negative case and recovery
stale validation time, BDI unavailable, non-active revision, and a pending asynchronous action. Treat “validation requested” as different from “result verified.”
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
model/revision, validation timestamps, actual problem code and text, affected position, repair action, and subsequent result. Include job status when generated work is part of the outcome.
Explain: Is the validation timestamp later than the change it is meant to validate?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
Planning and compliance
J05 · Turn upcoming maintenance into traceable work
Intermediate · Planner · 30–45 min (planning estimate)
connect planning signals to executable work before deadlines are missed. Aviation task-card configuration, ACM maintenance-plan requirements.
Prerequisites: J04. verified PM/master PM or task-card/master-task-card workflow; configured due logic; functioning generation services; J04.
Worked example: one calendar task and one FH task, synthetic warning/alert/due values, job plan/card, and a known utilization history.
Documented applications: ACM — Preventive Maintenance; Aviation — Task Cards.
- inspect applicable work, explain the trigger and next due calculation, advance training usage into the configured threshold, generate or observe generation of the work order, and inspect the resulting scope and asset linkage.
Negative case and recovery
inactive task, wrong effectivity, missing job plan/card, already-generated work, and a background job still queued. Verify whether repeated processing produces the expected existing record or new occurrence; do not assume idempotency.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
task applicability, last completion/baseline, next due calculation, alert/warning state, generated work ID, generation completion, and absence of unintended duplicate work.
Explain: How would you detect a duplicate generation request?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
J06 · Plan a coordinated maintenance visit
Intermediate · Planner · 30–45 min (planning estimate)
expose constraints before a visit begins and reduce repeated setup. Do not claim optimization without a configured scheduling capability. Work Packages, Work Package revisions.
Prerequisites: J05. verified Work Packages for the full track; otherwise an explicitly simpler supported work-order hierarchy lesson. MRO capacity or graphical scheduling is an optional separate gate.
Worked example: one aircraft, two scheduled tasks, one corrective task, a maintenance window, repair location, labour/craft requirements, materials, and tools.
Documented applications: ACM — Work Order Tracking; Aviation — Work Packages.
- group related work, verify aircraft and location, review dependencies and shortages, generate work, inspect the resulting hierarchy, and prepare a realistic handoff to execution.
Negative case and recovery
task for another aircraft, missing materials, overlapping resource demand where scheduling is supported, incomplete background generation, and revision after work has started. For Work Packages, demonstrate the supported additional-work route rather than pretend every revision stays editable.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
selected task/work IDs, package revision, time window, planned requirements, generation result, child hierarchy, and unresolved constraints.
Explain: What constraint is still unresolved before the visit?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
J11 · Assess a technical notice and prove task applicability
Advanced · Engineering assessor · 45–60 min (planning estimate)
provide a defensible explanation of which training assets require work and why. This teaches recordkeeping, not a legal determination of airworthiness. ACM technical records, Aviation technical publications.
Prerequisites: J01, J05. verified Technical Records (CM) or Technical Publications route; Engineering Assessment Orders only if available. Use the actual product’s applicability and embodiment fields.
Worked example: fictional `TRAIN-NOTICE-001`; two variants; three serials with one deliberately outside effectivity; one component installation; dated maintenance requirements.
Documented applications: ACM — Technical Records (CM); Aviation — Technical Publications.
- enter the training notice and its source, define affected model/part/position/serial criteria, perform assessment where available, create the supported work requirements, execute the sample obligation, and inspect the affected-asset and completion records.
Negative case and recovery
excluded serial, wrong variant, inactive notice, superseding notice, component transfer, or changed effectivity after prior embodiment. A task’s existence is not proof of applicability or completion.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
applicability decision per asset, source revision, generated task/PM and work records, method/status of completion, and excluded assets with reasons. Check related records manually after changes where automatic propagation is not documented or verified.
Explain: Why is the excluded serial outside this notice?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
J12 · Revise a maintenance programme without losing control
Expert · Programme engineer · 45–75 min (planning estimate)
make programme changes understandable and traceable before fleet-wide use. An application status does not confer external authority approval. Maintenance planning documents, Maintenance Task Library.
Prerequisites: J05, J11. verified MTL/OMP/revision/check functions, configured training workflow, and version-specific documentation. This is a capability-dependent extension, not an assumed ACM/Aviation equivalence.
Worked example: a short synthetic import of three tasks, defined crafts/zones, one deliberate invalid reference, two programme revisions, and distinct aircraft effectivity.
Documented applications: ACM — Maintenance-plan requirements; Aviation — Maintenance Task Library / OMP.
- import and inspect errors, repair the fixture/reference issue, validate the library revision, associate the programme and tasks, demonstrate a small check relationship, compare revisions, and inspect which aircraft/tasks changed.
Negative case and recovery
undefined skill, incomplete import, overlapping or conflicting programme association, an inapplicable aircraft, and premature activation. Never manufacture regulator approval or use a real manufacturer MPD without rights and authorization.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
import result/error resolution, library revision, programme revision, effectivity, task frequencies, check composition, and resulting task/work records.
Explain: Which aircraft are affected by the new programme revision?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
Complex operational scenarios
J10 · Replace an engine and preserve its complete history
Advanced · Maintenance engineer · 45–60 min (planning estimate)
preserve the maintenance and life identity of both engines across a high-value change. ACM install/remove, Aviation installation through work orders.
Prerequisites: J03, J04, J08. supported install/remove through work order, serial tracking, meter-offset/history behavior, a valid replacement, and known BDI operation; J03/J04/J08. Off-wing task automation is optional and separately verified.
Worked example: engine A and B from the meter oracle, aircraft position, swap work order, repair location, historical meter readings, and separate engine maintenance requirements.
Documented applications: ACM — Assets (CM) / installation and removal; Aviation — Aircraft and Equipment / installation and removal.
- Read J04 and retain the before-swap aircraft and engine totals, the current model revision and the LEFT-ENGINE position. Verify the replacement part is eligible for TRAIN-TWIN-A and its receipt is accepted.
- Under the authorized installation/removal action linked to TRAIN-WO-001, remove engine A at the recorded UTC timestamp and move it to TRAIN-REPAIR. Preserve its 404 FH / 252 FC lifetime.
- Install engine B at the same position with its independent 250 FH / 120 FC baseline. Inspect both the aircraft hierarchy and engine history after save. Do not copy engine A’s lifetime into B.
- Request configuration validation through the installed BDI action. Wait for the resulting timestamp and any related work-processing job to finish; a submitted request alone is incomplete.
- Add the post-swap flight. Reopen both engines and compare A = 404 / 252, B = 253 / 122, airframe = 1,007 / 504. Record any difference rather than adjusting the expected answer to the system.
- Repeat the historical-correction branch separately. Preserve the before/after usage history, work linkage, component custody, validation results and remaining maintenance obligations.
Negative case and recovery
wrong engine variant, installation preceding removal, incorrect offset, already-installed replacement, incomplete off-wing work, or backdated usage. Do not automatically reset lifetime totals or copy the old engine’s life to the replacement.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
before/after hierarchy, both serial histories, work linkage, removed-engine location, old/new life totals, maintenance applicability, and BDI timestamp/result.
Explain: Why must the replacement engine keep its own lifetime baseline?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
J13 · Resolve a fleet maintenance conflict and defend the outcome
Expert · Maintenance controller · 60–90 min (planning estimate)
demonstrate integrated decision quality and record coherence. The ending is a verified training-system state and a review checklist, never an autonomous declaration that an aircraft is safe to fly.
Prerequisites: J03, J04, J05, J08, J10, J11. completed core journeys; only include optional functions that have their own verified capabilities. Provide ACM-oriented and Aviation-oriented manifests rather than a fictional universal workflow.
Worked example: three fictional aircraft, two configuration variants, a shared spare, an engine change, an approaching maintenance threshold, a discrepancy, a pending receipt inspection, a notice with limited effectivity, and one late usage correction.
Documented applications: ACM — Configuration, meters and work orders; Aviation — Configuration, meters and work packages.
- Build an exception register for TRAIN-AC-001, TRAIN-AC-002 and TRAIN-AC-003 using the configuration, work, receipt and usage cards in the fleet challenge. Record the timestamp behind each conclusion.
- Reject the tempting TRAIN-PART-ENG-B spare for the variant A aircraft; reject an uninspected receipt as usable stock. These are worked-example policy decisions; determine actual enforcement separately in the installed system.
- Plan the supported engine change for TRAIN-AC-001, keep the variant B component for TRAIN-AC-002, and record TRAIN-AC-003’s unresolved discrepancy. A maintenance plan does not release any aircraft.
- Reconcile the late pre-swap usage correction with J04. Attribute it to engine A’s installation history, preserve engine B’s independent baseline, and invalidate any derived validation state older than the change.
- Trace applicable TRAIN-NOTICE-001 work to the affected variant A serials. Record why the variant B aircraft is excluded and check existing work before generating another occurrence.
- Export the local decision worksheet. A later training-system run needs separate ACM/Aviation execution manifests, real record IDs, fresh read-backs, negative-path recovery and independent review before it can be marked executed.
Negative case and recovery
a tempting but incompatible spare, unverified receipt, mistaken serial applicability, a green but stale BDI result, unresolved deferral, duplicate work generation, and historical usage affecting the removed engine.
Keep a separate TRAIN branch for each negative case. In a training system, re-read the affected records before retrying; only reset or cancel isolated records within the agreed permission scope.
Evidence to retain
per-aircraft configuration and open-work state, per-engine life reconciliation, material custody, applicable/excluded tasks, role/status history, all background outcomes, and a final exception register. Trace every conclusion to a record and timestamp.
Explain: Which rejected alternative looked convenient, and why is its evidence insufficient?
Authored lesson. Training-system execution, persisted record IDs, authenticated screenshots and recording are pending.
Independent life worksheet
Assumption: 1:1 inheritance in the installed interval. Baseline: airframe 1,000 FH / 500 FC; A 400 / 250. Flights +2.5 / +1 and +1.5 / +1. Swap to B at 250 / 120. Later flight +3 / +2.
| Record | Normal FH / FC | Historical correction +0.5 FH / +1 FC |
|---|---|---|
| Airframe | 1007 / 504 | 1007.5 / 505 |
| Removed engine A | 404 / 252 | 404.5 / 253 |
| Installed engine B | 253 / 122 | 253 / 122 |
Use and evidence scope
Content 2026-10-18.1. Reviewed 2026-10-18. Browser exercises and offline worksheets perform no Maximo transactions. The model teaches record coherence, not maintenance approval or release to service. Revalidate application, action, role and configuration capabilities in the training environment before a practical run.