Define the core project information that will be inherited by all Work Packages.
2. Project Team Leadership
Name the key project leaders. These are informational and will appear in SOP exports.
Additional Team Members (optional)
3. Required Sign-Off Roles
Superintendent and Foreman are required. Add other roles as needed for your project structure.
Optional Additional Roles
4. Work Package Types
Enable the WP types your project will use. Add any special rules and the roles required to approve WO completion.
5. Governance & WP Numbering
Define how Work Packages are formatted, sized, and issued on this project. The choices here decide how the Work Package Creator behaves for every package.
Use ## for counter, [Sector] [TYPE] as variables
Hold Ctrl (Cmd on Mac) to select multiple.
Examples:
By Sector / Area β one package per physical area, e.g. all work in Sector 1P, Level 2 chase.
By Discipline β separate packages per trade, e.g. Electrical wire-pull vs Mechanical install.
By Phase / Sequence β follow the build order, e.g. rough-in β wire pull β terminations.
By Resource Availability β size to a crew/equipment window, e.g. one boom-lift crew's week.
How will Work Packages use disciplines?
Decide whether a single package can carry more than one discipline (e.g. a chiller skid needing Mechanical install + Electrical wire-pull + Tech terminations), or whether each discipline gets its own package. This drives whether the Creator shows per-discipline scope sections and the Split by Discipline button.
Comma-separated. These appear as scope sections and instance suffixes in the Creator.
"Choose per package" lets the planner build a large multi-discipline package and split it later.
Work Package sizing
A Work Package should be a manageable, trackable chunk of work β typically a 1β2 week assignment. The Creator warns the planner when a package exceeds the ceiling so it can be broken down.
Sets the split threshold automatically; choose Custom to enter your own.
Auto-set from the size above (editable). The Creator flags packages over this so they can be split.
6. Quality & Inspection Strategy
Establish project-wide quality expectations that cascade to every Work Package.
7. Tracking & Commissioning Platforms
Select the tools used for construction tracking and commissioning. These can be the same or different systems.
8. Construction Sequence
Comes pre-sequenced with a typical install flow. Drag the β Ώ handle to reorder steps, edit labels inline, add a QC hold gate, or remove any step.
9. Release Gate Constraints
Constraints are readiness items that must be cleared before a WP can be issued.
Standard AWP Constraints (Vol II Β§2.3.2)
Custom Constraints (Optional)
10. Engineering Sources & References
Link to key documents and systems that WP authors will reference.
π Work Package Creation
Complete the SOP Configuration first to enable Work Package creation. Once the SOP is finished, the full creator loads here with your project defaults pre-populated.
