{ "version": "2026-08-29.1", "reviewed": "2026-08-29", "route": "/guides/maintenance-planner.html", "scope": "A local work-package record checklist for industrial maintenance planning. It checks whether twelve editorial record fields are represented; it does not judge technical adequacy, approve a procedure, permit execution, or replace employer and site controls.", "source_facts": { "doe_std_1050": { "label": "DOE-STD-1050-93", "url": "https://www.energy.gov/ehss/articles/doe-std-1050-93", "publisher": "U.S. Department of Energy", "source_type": "archived DOE technical standard page", "context": "Planning, scheduling and coordination of maintenance at DOE nuclear facilities.", "fact": "The guide describes work-package planning that identifies technical and administrative requirements and provides materials, tools and support activities needed for maintenance work.", "boundary": "Nuclear-facility context; archived and cancelled; not presented as general law or a universal industrial requirement." }, "doe_om_release_3": { "label": "Operations and Maintenance Best Practices Guide, Release 3.0", "url": "https://www.energy.gov/sites/default/files/2020/04/f74/omguide_complete_w-eo-disclaimer.pdf", "publisher": "U.S. Department of Energy", "source_type": "federal O&M guidance", "context": "Operational-efficiency guidance for energy managers and O&M practitioners.", "fact": "The guide discusses work-order records, technical documentation, parts and materials, labor and cost tracking, condition information and feedback through O&M records and CMMS use.", "boundary": "Guidance and examples, not a site-specific maintenance procedure or a substitute for current manufacturer and employer requirements." }, "osha_1910_147": { "label": "OSHA 29 CFR 1910.147", "url": "https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.147", "publisher": "Occupational Safety and Health Administration", "source_type": "U.S. general-industry regulation", "context": "Control of hazardous energy during covered servicing and maintenance.", "fact": "For covered work, employers establish the energy-control program and use procedures addressing shutdown, isolation, device control and verification, with training, inspection and employee responsibilities.", "boundary": "Applicability and compliance remain the employer's and site's responsibility. A checklist reference is not an energy-control procedure." }, "sap_preparation": { "label": "SAP Help: Preparation", "url": "https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/e72f747389b340229f7fa343975bfa57/2d5abd04981a4c44bd137bb8d7c3f749.html", "publisher": "SAP", "source_type": "product documentation", "context": "Preparation phase in phase-based maintenance processing.", "fact": "SAP describes planners grouping maintenance work, selecting a concrete time period and checking resources, spare parts and services before scheduling.", "boundary": "Describes SAP product workflow, not a universal maintenance method or evidence that a local order is adequate." }, "sap_order_planning": { "label": "SAP Help: Planning of an Order", "url": "https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/efc7922405fd4d56b7571930c5eaa798/48a9b8535c39b44ce10000000a174cb4.html", "publisher": "SAP", "source_type": "product documentation", "context": "Advance planning functions for maintenance orders.", "fact": "SAP lists operations, relationships, material planning, permits, capacity planning, scheduling, cost estimation and partner data among order-planning functions, while noting that companies define their own planning steps.", "boundary": "Feature documentation; available fields and workflow depend on edition, configuration and local process." }, "sap_process_order": { "label": "SAP Help: Process Maintenance Order", "url": "https://help.sap.com/docs/SAP_S4HANA_CLOUD/2dfa044a255f49e89a3050daf3c61c11/a30f265788fcbb61e10000000a4450e5.html", "publisher": "SAP", "source_type": "product documentation", "context": "Maintenance-order creation and change by a maintenance planner.", "fact": "SAP documents order information including dates, location, operations and suboperations, planned materials, services, capacity, costs and production resources or tools.", "boundary": "Product documentation, not an endorsement, occupation definition or complete work-package standard." }, "sap_maintenance_order": { "label": "SAP Help: Maintenance Order", "url": "https://help.sap.com/docs/SAP_ERP/b4174aff4a234ed5be928a10c60997fb/d784b8535c39b44ce10000000a174cb4.html", "publisher": "SAP", "source_type": "product documentation", "context": "Maintenance-order processing and history.", "fact": "SAP describes internal or external order processing and transfer of order data into maintenance history for evaluation and future planning.", "boundary": "Product workflow context; record quality still depends on local definitions, configuration and use." } }, "editorial_fields": [ { "id": "asset_context", "field": "Asset and work context", "record_prompt": "Record the asset or functional location, work request, current condition and why the intervention is being planned.", "evidence_example": "Asset ID, location, request reference and condition note", "editorial_reason": "Anchors the package to a specific local record before detailed planning begins.", "source_keys": [ "doe_std_1050", "sap_process_order" ] }, { "id": "scope_boundaries", "field": "Scope and boundaries", "record_prompt": "State the intended result, included equipment, exclusions and interfaces with adjacent work.", "evidence_example": "Scope statement with inclusions, exclusions and interfaces", "editorial_reason": "Keeps a completeness check tied to a bounded work package rather than a broad task label.", "source_keys": [ "doe_std_1050", "sap_process_order" ] }, { "id": "steps_sequence", "field": "Operations and sequence", "record_prompt": "List the planned operations, suboperations, dependencies and hold points at the level needed for local review.", "evidence_example": "Numbered operations, dependencies and hold points", "editorial_reason": "Turns the scope into a reviewable sequence without claiming that the sequence is technically approved.", "source_keys": [ "doe_std_1050", "sap_order_planning", "sap_process_order" ] }, { "id": "people_time", "field": "Roles, capacity and duration", "record_prompt": "Record responsible roles, estimated effort, work-centre or contractor needs and planned duration.", "evidence_example": "Role or craft, headcount, labour hours and duration", "editorial_reason": "Makes resource assumptions visible for local planning review; it does not assess any person.", "source_keys": [ "doe_std_1050", "sap_order_planning", "sap_process_order" ] }, { "id": "materials_services", "field": "Materials, spares and services", "record_prompt": "List stock and non-stock materials, quantities, services, availability evidence and substitutions needing review.", "evidence_example": "Part numbers, quantities, reservations, service scope and availability", "editorial_reason": "Separates planned demand from an assumption that items will be available when needed.", "source_keys": [ "doe_std_1050", "sap_preparation", "sap_order_planning", "sap_process_order" ] }, { "id": "tools_equipment", "field": "Tools and test equipment", "record_prompt": "Identify special tools, lifting or access equipment, test instruments and relevant status records.", "evidence_example": "Tool list, test-equipment IDs and applicable status references", "editorial_reason": "Surfaces equipment dependencies for review without validating suitability or condition.", "source_keys": [ "doe_std_1050", "sap_process_order" ] }, { "id": "technical_references", "field": "Technical references", "record_prompt": "Link the current drawings, manuals, specifications, task lists and change references used to prepare the package.", "evidence_example": "Document IDs, revisions, task-list reference and change record", "editorial_reason": "Makes the information basis traceable and exposes missing or stale references for local review.", "source_keys": [ "doe_std_1050", "doe_om_release_3", "sap_process_order" ] }, { "id": "hazardous_energy", "field": "Hazards and energy-control references", "record_prompt": "Identify applicable site hazard reviews and reference the employer's current energy-control procedure where covered work may involve hazardous energy.", "evidence_example": "Hazard-review ID and site-controlled procedure reference", "editorial_reason": "Records where controlled site information is found; this field is not the procedure and does not determine applicability.", "source_keys": [ "osha_1910_147", "doe_std_1050" ] }, { "id": "permits_coordination", "field": "Permits and coordination", "record_prompt": "List permit references, operations interfaces, contractor interfaces, notifications and supporting activities needing coordination.", "evidence_example": "Permit IDs, coordination owner, notification list and support request", "editorial_reason": "Makes administrative dependencies visible while leaving decisions and approvals with responsible site processes.", "source_keys": [ "doe_std_1050", "sap_order_planning" ] }, { "id": "schedule_access", "field": "Schedule, access and dependencies", "record_prompt": "Record the requested window, access constraints, outage or operating condition, predecessors and resource availability checks.", "evidence_example": "Planning window, access note, system condition and dependency list", "editorial_reason": "Connects the work package to a feasible review window without dispatching or releasing it.", "source_keys": [ "doe_std_1050", "sap_preparation", "sap_order_planning" ] }, { "id": "acceptance_restore", "field": "Checks, acceptance and restoration", "record_prompt": "Define the planned inspection or test evidence, acceptance criteria, restoration checks and responsible local review points.", "evidence_example": "Test reference, acceptance criteria, restoration checklist and reviewer", "editorial_reason": "Ensures completion evidence is planned while keeping technical acceptance in local procedures.", "source_keys": [ "doe_std_1050", "osha_1910_147" ] }, { "id": "history_closeout", "field": "History, feedback and closeout", "record_prompt": "Specify the completion records, actual labour and materials, findings, follow-up actions and history update expected after the work.", "evidence_example": "Closeout fields, findings log, follow-up owner and history destination", "editorial_reason": "Preserves a feedback path for evaluation and future planning rather than treating closure as a blank status change.", "source_keys": [ "doe_om_release_3", "sap_maintenance_order" ] } ], "editorial_logic": { "classification": "Inzonex editorial completeness logic", "rules": [ { "minimum_complete": 0, "maximum_complete": 0, "state": "draft record set", "message": "No checklist field has been marked as represented in the local record set." }, { "minimum_complete": 1, "maximum_complete": 11, "state": "records need review", "message": "Some checklist fields are represented, but one or more record areas still need local review." }, { "minimum_complete": 12, "maximum_complete": 12, "state": "record set ready for local review", "message": "All twelve checklist fields are represented for local review; field presence does not establish technical adequacy." } ], "boundary": "The count measures field presence only. It does not permit execution, validate technical content, make personnel judgments or replace employer and site processes." } }