General Information
Parameters in blue are inherited from the project SOP. Fill the rest for this package.
Cannot move to Issued or beyond until all constraints are cleared.
WP number builds automatically from these scope fields + the WP type (per the SOP naming format):
from SOP types
Acumatica cost codes
Assetsi
Every work package is based on one or more assets from the Micron DB. Search by asset ID, or paste a column of IDs straight from Excel, to add each asset this package covers. The Micron DB is read-only — nothing you do here changes it.
| Asset ID | Note (what this asset is / why it's in scope) |
|---|
Scope & Worki
Enter the work as ordered steps — added in sequence, the way the crew performs them.
from the SOP construction sequence
Material Listi
Structured bill of materials. Feeds kitting and the delivery forecast. Unit is from the Acumatica unit list.
| Qty | Unit | Description |
|---|
Drawings & Attachments
| Document / Drawing | Rev | Link / Note |
|---|
Kitting & Material Movement (MIMO)
scheduled material-move date & time
Constraints — Release Readinessi
Per AWP, a package is not released to the field until every constraint is Cleared or N/A. If a constraint reopens after release, status drops to Issue (Hold).
| Constraint | Status | Comment |
|---|
Quality, Inspection & Hold Points
Inherited from the SOP. A Hold Point stops work until inspection sign-off; a Witness Point is offered for inspection but work may proceed if declined.
Approvals & Sign-offs
Per the AWP IWP checklist. A package should be signed by these roles before release.
| Role | Name | Date | Signed |
|---|
Closeout
Completed at QC / Closed — captures as-built reality and lessons learned.