Early access — content in review
Free checklist

Resources / Outline: Primavera P6

Primavera P6 for Maintenance and Turnaround Scheduling — Course Outline

DRAFT · unverified

Status: DRAFT v0.1 outline | Unverified until owner sign-off. Follows Playbook DRAFT v0.2 (rule 1 transactions-plus-sources, rule 5 no invented facts, rule 6 employer conflict of interest). Audience: Both, Mechanical and Instrumentation & Electrical (I&E). Mainly schedulers and turnaround (TA) planners. Prerequisites: Flagship course scheduling module, or equivalent experience TBD: owner to confirm Time: TBD: owner to supply Product version and edition covered: TBD: owner to supply, e.g., the Primavera P6 edition and version. Features may differ by edition.

Source status (read first)

The approved source set for this batch covers SAP Plant Maintenance (SAP PM), preventive maintenance (PM) and maintenance planning only. It contains no Primavera P6 documentation. So:

  • Every Primavera P6 feature, menu, view, field or file format named below is marked [UNVERIFIED: product feature, no source]. Each must be confirmed in Oracle's official documentation for the edition taught, with a citation, before the lesson ships TBD: owner to supply source.
  • Lessons describe scheduling concepts (tasks, durations, dependencies, resources, baselines, progress). They make no claims about how the product implements them.
  • No claim is made that SAP PM and Primavera P6 integrate directly. How data moves between them is TBD: owner to supply.

Employer rule: Built from public sources and general industry knowledge only. [EMPLOYER REVIEW: owner to check that no lesson, example file or template mirrors any employer's internal scheduling standard, project templates, codes or reports.]

Trademarks: Oracle and Primavera are trademarks of Oracle and/or its affiliates. The Planner's Bench is not affiliated with or endorsed by Oracle. [UNVERIFIED: owner or attorney to confirm the trademark wording.]

Lesson P1: When to use a scheduling tool alongside SAP PM

  • Outcomes: Explain what a project scheduling tool adds to SAP PM for turnarounds and large jobs. Decide when the weekly schedule in SAP PM is enough.
  • Step 1: Compare the two.
    • What to do: Compare routine weekly scheduling from the order and operation list with turnaround or project scheduling, which needs logic between jobs and a critical path.
    • SAP transactions: IW37N, Change Orders and Operations; CM25, Capacity Leveling - Variable
    • Sources: [map E] SAP Community, Standard SAP Plant Maintenance Reports; [S16] SAP Learning, Configure Work Centers; [S17] Doc Palmer, planning and scheduling principles. Primavera P6 side: [UNVERIFIED: product feature, no source].
    • Craft notes: none, craft-neutral.

Lesson P2: Getting maintenance work into the schedule

  • Outcomes: Prepare an order and operation list from SAP PM as input to a schedule. Map orders and operations to schedule tasks.
  • Step 1: Prepare the work list.
    • What to do: Pull the turnaround or project orders and operations, with work center, planned hours and equipment. How you export the list depends on your system and site TBD: owner to supply.
    • SAP transactions: IW37N, Change Orders and Operations; IW39, Display PM Orders (list)
    • Sources: [map E]
    • Craft notes: Keep Mechanical, Instrumentation and Electrical work centers separate so resources can be assigned by craft.
  • Step 2: Bring it into Primavera P6.
    • What to do: Create one task per operation (or per order, if your site schedules at that level), keeping the order and operation numbers so progress can be matched back. Import method: [UNVERIFIED: product feature, no source] TBD: owner to supply.
    • SAP transactions: none (non-SAP step)
    • Sources: none in approved set [UNVERIFIED: product feature, no source] TBD: owner to supply Oracle documentation
    • Craft notes: none.

Lesson P3: Durations, dependencies and the critical path

  • Outcomes: Set task durations from planned hours and crew size. Link tasks in the right order. Identify the critical path.
  • Step 1: Set durations and link tasks.
    • What to do: Convert planned hours to durations using crew size. Link tasks in the order the work must happen, for example isolate, open, repair, close, test, restore. How the product shows the critical path: [UNVERIFIED: product feature, no source].
    • SAP transactions: none (non-SAP step)
    • Sources: estimating from planned hours: [S19] Doc Palmer, math of planning and scheduling. Critical path concept: [UNVERIFIED: no public source yet] TBD: owner to supply. Product: TBD: owner to supply Oracle documentation.
    • Craft notes: Show the Electrical isolation and restoration tasks and the I&E test tasks explicitly, so handoffs are visible in the logic.

Lesson P4: Resources, crafts and calendars

  • Outcomes: Assign craft resources to tasks. Spot over-allocation and level it.
  • Step 1: Assign crafts and check loading.
    • What to do: Set up one resource per craft or crew, with working time that matches your shift pattern. Assign them to tasks and check for over-allocation. Product features for calendars and leveling: [UNVERIFIED: product feature, no source].
    • SAP transactions: IR03, Display Work Center (for crafts and capacity)
    • Sources: [map B]; [S16]; product: TBD: owner to supply Oracle documentation
    • Craft notes: I&E specialists and electrical testers are often few in number, so check their loading first Unverified.

Lesson P5: Baseline, progress and recovery

  • Outcomes: Save a baseline before execution. Update progress daily. Compare actual to plan and re-plan.
  • Step 1: Baseline and update.
    • What to do: Freeze the approved schedule as a baseline. Update percent complete or remaining duration daily from the field. Match actual hours to SAP PM confirmations.
    • SAP transactions: IW41, Individual Time Confirmation; IW47, Confirmation List
    • Sources: [map H] / [S22] SAP Learning, Confirming Notifications and Orders; product baseline and progress features: [UNVERIFIED: product feature, no source] TBD: owner to supply
    • Craft notes: none beyond earlier lessons.

Lesson P6: Reporting to the turnaround team

  • Outcomes: Produce a daily look-ahead and a progress summary for supervisors and Operations.
  • Step 1: Build the daily reports.
    • What to do: Filter the next 1–2 days of work by craft and area. Summarize progress against the baseline. Report and view options: [UNVERIFIED: product feature, no source].
    • SAP transactions: none (non-SAP step)
    • Sources: TBD: owner to supply Oracle documentation
    • Craft notes: Give each craft its own look-ahead.

Lesson P7: Organizing a turnaround project structure

  • Outcomes: Group turnaround activities so each unit, area and craft can see its own work. Keep the structure simple enough to update daily.
  • Step 1: Choose a grouping scheme.
    • What to do: Decide how to group activities, for example by unit, area, equipment and craft, and how order and operation numbers are carried so progress can be matched back to SAP PM. How Primavera P6 supports structures and coding: [UNVERIFIED: product feature, no source] TBD: owner to supply Oracle documentation.
    • SAP transactions: IH01, Functional Location Structure (to mirror the plant hierarchy, if useful)
    • Sources: [map E] SAP Community, Standard SAP Plant Maintenance Reports; product: TBD: owner to supply Oracle documentation
    • Craft notes: A craft grouping lets Mechanical, Instrumentation and Electrical supervisors each filter their own work.
    • [EMPLOYER REVIEW: owner to make sure the grouping scheme taught isn't an employer's internal coding structure.]
  • Backlog Tracker and Weekly Scheduling Board (../templates/)
  • Example schedule file TBD: owner to supply, fictional data only

Disclaimer

Adapt to your site's SAP configuration, scheduling standards and procedures. Not affiliated with or endorsed by SAP SE or Oracle. SAP and SAP PM are trademarks of SAP SE. © TBD: owner to supply year [PLACEHOLDER: legal entity].

Sources

Verification log

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

Esc to close · powered by a static index