Early access — content in review
Free checklist

Resources / Simulator scenarios

The Planner's Bench — Practice Simulator Scenarios

DRAFT · unverified

Status: DRAFT | Unverified until owner sign-off. Format follows The Planner's Bench playbook DRAFT v0.2, which is still awaiting owner approval. Terms: PM = Plant Maintenance; TECO = technical completion (technically completed status); I&E = Instrumentation and Electrical These are guided paper scenarios, not a live system. All data is made up and labeled 'Example data'. Screen-level field names aren't sourced: TBD: owner to supply.

Scenario IW31: Create a maintenance order

Setup: Example data: a made-up pump equipment record with a task list. Real IDs: TBD: owner to supply.

Steps

  1. Open IW31 and enter the order data and reference object. Screen fields: TBD: owner to supply.
    • SAP transactions: IW31
    • Sources: [S11]
  2. Reference the task list and enter the dates. The operations are copied over.
    • SAP transactions: IW31
    • Sources: [S3][S11]
  3. Review each operation: work center, hours, duration, number of people, control key. Adjust in IW32 if needed.
    • SAP transactions: IW32
    • Sources: [S11]
  4. Assign components. Stock items create reservations, and non-stock items create purchase requisitions (PRs).
    • SAP transactions: IW32
    • Sources: [S12]

Expected result: An order exists with its operations copied from the task list, stock components reserved, and PRs for non-stock items [S3][S11][S12].

Common mistakes

  • Typing operations by hand instead of referencing the task list [S3].
  • Using an order for routine PM that should come from the plan [S11].

Scenario IP10: Start (schedule) a maintenance plan

Setup: Example data: a made-up single-cycle transmitter calibration plan (IP41) with a 90-day cycle.

Steps

  1. Open IP10 for the plan and start it. Start date field details: TBD: owner to supply.
    • SAP transactions: IP10
    • Sources: [S10]
  2. Check the call horizon. With 80% on a 90-day cycle, the call comes after 72 days Unverified.
    • SAP transactions: IP10
    • Sources: [S9]
  3. Review the scheduled dates.
    • SAP transactions: IP19, Scheduling Overview and Simulation; IP24, Scheduling Overview List Display
    • Sources: [S10]
  4. Confirm that ongoing scheduling runs through deadline monitoring.
    • SAP transactions: IP30, Deadline Monitoring (program RISTRA20); IP30H, Mass Schedule Maintenance Plans (newer releases only) Unverified
    • Sources: [S8][S10]

Expected result: The plan is scheduled, call dates are visible in IP19/IP24, and call objects are created when they fall due [S9][S10].

Common mistakes

  • Never starting the plan: no call objects are ever created [S10].
  • Setting a call horizon too late for material lead time [S9].

Scenario IW41: Individual time confirmation

Setup: Example data: a released, made-up pump PM order with two operations.

Steps

  1. Open IW41 for the order and operation. Field layout: TBD: owner to supply.
    • SAP transactions: IW41
    • Sources: [S22]
  2. Enter the work center, the person, start and finish, and any readings. I&E variant: on a transmitter calibration order, enter the as-found and as-left values [S23][S7].
    • SAP transactions: IW41
    • Sources: [S23]
  3. Confirm one operation partially, then confirm the other finally.
    • SAP transactions: IW41
    • Sources: [S23]
  4. Check the order status: partially confirmed until all required operations are finally confirmed.
    • SAP transactions: IW33
    • Sources: [S23][map I]

Expected result: The confirmations are recorded and the order status reflects partial or final confirmation [S23].

Common mistakes

  • Setting TECO before all labor is confirmed [S14].
  • Leaving out readings such as vibration or as-found values [S23][S7].

Public sources

Verification log

  • Verified by: [owner] | Date: [ ] | Notes: [ ]

Esc to close · powered by a static index