Minnesota Department of Transportation

Work Package
Creation and
Maintenance Process

Prepared by: Project Management Unit, Office Project Management Technical Support
3/9/2015

Minnesota Department of Transportation

395 John Ireland Boulevard
Saint Paul, Minnesota 55155

Phone: 800-657-3774
800-627-3529 (TTY, Voice, ASCII)
www.mndot.gov
Work Package Creation and Maintenance Page 1 of 23
Updated 20150309

TABLE OF CONTENTS
1.0 General Information .........................................................................................................................................2

2.0 Process Summary .............................................................................................................................................2

2.1 Creating a Work Package .............................................................................................................................2

2.2 Updating a Work Package ............................................................................................................................3

3.0 Developing Work Packages ..............................................................................................................................3

4.0 Developing Templates ......................................................................................................................................8

5.0 Updating Released Work Packages and Templates ..........................................................................................8

6.0 Appendix.........................................................................................................................................................11

6.1 Work Package and Template Frequently Asked Questions .......................................................................11

6.2 Version Control ..........................................................................................................................................12

6.3 Activity ID Prefix .........................................................................................................................................13

6.4 QA/QC Form ...............................................................................................................................................22

6.5 P6 Enterprise Comment and Change Form ................................................................................................23

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 2 of 23
Updated 20150309

1.0 GENERAL INFORMATION

The purpose of this document is to outline the process for P6 work package/template development and maintenance
to promote consistency in the creation, release, and communication of P6 work packages and templates.

A work package is a group of activities to generate specific project deliverables for a functional group or work type.

A template is a group of work packages. Templates are a tool used by schedulers to expedite schedule creation and
are only developed for frequently used processes. All templates must be approved by the Template Group.

Frequently Asked Questions regarding Work Packages and Templates are summarized in Appendix 6.1.

2.0 PROCESS SUMMARY

2.1 CREATING A WORK PACKAGE

See Section 3.0 for process details and work package creation responsibilities.

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 3 of 23
Updated 20150309

2.2 UPDATING A WORK PACKAGE

See Section 5.0 for process details and work package creation responsibilities.

3.0 DEVELOPING WORK PACKAGES

This section details the steps implemented to create a work package.

1. Determine need for work package

PM or Functional Group requests a new work package to the SSC.

The work package must be a node in the Master WBS in P6. If the work package is approved for creation
and it is not a node in the Master WBS, the node must be added to the WBS.

If a node is to be created, SSC submits P6 Enterprise Comment and Change Form for consideration with
the following information:

Threshold criteria for the work package

A list of related work packages/templates that may be impacted by the creation of the work package

2. Approve work package creation

Core Team will determine if work package needs to go to Template Group for approval. If approved, a
scheduler is assigned to develop the work package. If the work package is not approved, SSC will inform
the PM or Functional Group why the work package will not be created.

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 4 of 23
Updated 20150309
3. Create work package shell

Scheduler requests Admin to create work package shell in Preliminary Templates – Work Packages node
(PRELIM.TMPLT or TMPLTWP) of P6.

Scheduler provides a work package name. The work package name must be in conformance with the
authoritative WBS. If the authoritative WBS does not have a node for the package, the authoritative WBS
will be modified to incorporate the new work package.

Admin will assign an alphanumeric template number using the following naming convention:

TMPLXXXX-P: TMPL indicates that it is a work package, XXXX is a numeric field assigned by
Admin, -P indicates that the work package is in the preliminary node and has not gone through the
QA/QC process.

4. Create preliminary work package

Scheduler works with functional groups to identify the activities and the logical sequence between them.

A project champion will be assigned from the Functional Group. Scheduler will update the P6 Project Code
MnDOT WPkg Champion. If the champion is not identified as a project code value, notify Admin to have
that person added to the list. “MnDOT Version Control” notebook topic will also hold the name of the
work package champion.

Scheduler will evaluate related work packages that may be impacted by the creation of the work package
and submit a P6 Enterprise change request for the required updates.

Identify activities and logic needed to represent the work. Care should be taken that the total number of
activities in a work package does not make it too cumbersome for activity owners to update in Team
Member.

Activity level constraints, lags, and leads are not allowed in the work packages. All activities, except
dissolvable milestones, will have the appropriate code value assigned to “MnDOT Functional Group”.

The Activity ID alphanumeric naming convention is:

AAAXXXX: AAA is a prefix based on the WBS name and XXXX is a numeric field.

For example: LAY1040 Prepare Preliminary Geometric Layout & Profile

See Appendix 6.3 for the three letter prefix and associated work packages.

5. Populate the activity duration and owners

Scheduler works with the functional group to determine each activity’s duration and owner.

Activities should generally be in the 5-20 day range. However, activities can fall outside of these thresholds
as long as there is a clear deliverable represented and there is the appropriate amount of detail to manage
the work.

Activity duration on a work package will be based on the most likely number of days the activity would
take on an average project. Durations can be scaled during the baselining process.

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 5 of 23
Updated 20150309
6. Create dissolvable milestones

Scheduler will determine the relationships that connect to other work packages and templates and identify
these relationships in the work package using dissolvable milestones.

Dissolvable milestones will be in a WBS node titled “Dissolvable Milestone (Dissolve after relationship
linked & remove node from WBS)”.

Dissolvable Milestones will use the following Activity ID naming convention:

ZZZAAAXXX: ZZZ indicates that it is a dissolvable milestone and AAAXXX is the Activity ID
the milestone is linking to.

For example: ZZZPLN9000 will tie to the activity Prepare 90% Plans

Dissolvable Milestone Activity Name will match actual activity name in the template/work package to aid
in connecting the relationships. The name will be modified to indicate either pred/succ and include
relationship type and template/work package in which the activity resides in.

For Example: Succ: Prepare Preliminary Geometric Layout & Profile (FF) (Project Template)
indicates that the activity in the work package will have the successor activity LAY1040 Prepare
Preliminary Geometric Layout & Profile from the Project Template with a finish-finish
relationship.

If the logic is conditional, that information should also be included in the activity name.

For Example: If EDD2 is needed, Succ: Prepare & Submit EDD 2 (FS) (Environmental Due
Diligence 2))

Scheduler will link relationships between temporary activities and work package activities.

Each dissolvable milestone will have an open end that will get linked to the permanent activity.

Dissolvable milestones may be duplicated if they represent multiple relationship types. In this case, the
Activity ID will be modified to include a “-1” as a suffix. For example, if the same dissolvable milestone is
both a predecessor and successor to an activity in the work package, it must be created twice.

7. Update the preliminary work package

Scheduler will review the PPMS Network Activity Manual to compare predecessors, successors,
thresholds, work tasks, functional groups for the work package to the equivalent activity in the PPMS
Manual.

Schedulers will identify calendars, functional group roles, and budgeted units (Role Hours) for activities.
See RD-00-03 Calendar Dictionary for calendar information. See PD-00-08_Role Loading for information
on role loading.

Scheduler will obtain RD-00-09 Work Package Dictionary information and include it in the appropriate
notebook topics and codes in P6 for the work package.

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 6 of 23
Updated 20150309
The following items will be included in the Work Package Dictionary:
WBS Node: Authoritative WBS node for work package
Work Package Name: Authoritative WBS node name
Work Package ID: 8 digit alpha-numeric code assigned by Admin
Organization and Functional Group: Contact information for the functional group/office
that is responsible for this work package.
Threshold Criteria: An explanation of why and when this work package is needed in a
project schedule.
Deliverable(s): An explanation of the deliverable(s) produced by this work package.
Notes: Any additional guidance the responsible person/office would like to provide.
Gantt Chart: A pdf of the Template/Work Package Printout layout.
Activity Owners: Ownership assignment guidance so the appropriate Team Member user is
assigned to each activity.

8. Approve preliminary work package

Scheduler will obtain buy-in from the functional group on activities, duration, activity owner and logic.

9. Populate the roles and role hours

Scheduler will work with the functional group to estimate roles and role hours needed on each activity.

Activities in a work package will be role loaded based on estimated hours required to complete the work
and appropriate roles from the role tree for a typical project. The estimated hours worked will be added as
Budgeted Units and duration is added for the anticipated number of days it will take to complete the
activity.

The work package/template may be loaded with generic roles and estimated budget units (hours) if the
functional group requests a starting point for finalizing the roles loading for the work package. Admin will
update the work package with generic roles and role hours if it is required.

Admin created a master spreadsheet tool to facilitate role loading of P6 schedules. See RD-00-
10_Process Used to Develop Role Loaded Templates for additional information on the empirical
method used.
a. Scheduler and Admin will review the work package activities to determine initial roles, role hours
and durations using the role loading tool. See RD-00-10_Process Used to Develop Role Loaded
Templates.doc and Role Loading an Activity Section in the appendix of PD-00-08_Role Loading.
b. Scheduler will review the generic roles, role hours and durations with the functional group
responsible for the work package/template.
c. Scheduler will update the roles, role hours and durations in the work package/template. See Role
Loading an Activity Section in the appendix of PD-00-08_Role Loading

10. Scheduler will obtain buy-in from the Functional Group on role estimates

Scheduler will insert date of approval under the MnDOT WPKG Functional Group Accepted UDF.

Scheduler populates the Description in the Project Notebook topic with appropriate guidance information.

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 7 of 23
Updated 20150309
11. Update Work Package Dictionary

Scheduler submits Work Package Dictionary data (outlined in step 5f) to Admin.

Admin will update the Work Package Dictionary.

12. Obtain Core Team Approval

Scheduler and Functional Group present the completed work package to the Core Team.

Scheduler contacts Admin Team to get on the Core Team agenda.

Scheduler will provide printouts of the Work Package Dictionary information and the following layout
reports: MnDOT Work Package Review Gantt Chart (activity layout), MnDOT Work Package Role Hour
Review (resource assignments layout), and MnDOT Role Review by Role (Functional group style report).

Scheduler and Functional Group update work package to resolve Core Team comments.

Scheduler will present related work packages that may be impacted by the creation of the work package.

13. Submit work package for quality control/quality assurance (QC/QA) check

Scheduler notifies Admin that work package is ready for quality control check and provides Admin with
pdfs of the following layout reports: MnDOT Work Package Review Gantt Chart (activity layout). MnDOT
Work Package Role Hour Review (resource assignments layout). See FM-00-02_QC-QA checks for work
packages.docx for QC/QA checklist.

Scheduler updates work package to resolve QC Team comments.

Admin will perform QA check.

Scheduler updates work package to resolve QA Team comments.

Scheduler notifies Admin that all comments are resolved and work package is ready to be issued.

14. Admin approves work package

Admin will confirm all changes have been addressed.

Admin updates the MnDOT Version Control notebook topic in P6 that QC and QA have been completed.
(See Section 6.2)

15. Work package is released for use

Scheduler coordinates with Admin to update impacted work packages and/or insert revised work package
into impacted templates. (See Section 5.0)

Admin will remove the “–P” from the Project ID and move the work package into the Authoritative Work
Package Template (AUTH.WRKPKG.TMPLT) node of the EPS.

Admin team will confirm the version control information is acceptable (See Section 6.2) and upload the
work package to the authoritative node.

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 8 of 23
Updated 20150309
Admin will send an email to Extended Core Team notifying them that a new work package has been
released.

16. Work package is presented at Extended Core Team meeting

Admin will schedule presentation of work package at Extended Core Team meeting.

Scheduler and Functional Group will present the approved work package at the Extended Core Team
meeting. The work package champion and associated SSC staff will prepare the material to be presented.

4.0 DEVELOPING TEMPLATES

Templates will be developed following the process outlined for work packages in Section 3.0 with the following
exceptions:

1. If the need for a new template is identified, it must receive approval by the P6 Core Team or template
group before being developed.

2. Scheduler requests Admin to create work package shell in Preliminary Templates – templates node
(PRELIM.TMPLT, TMPLTPR) of P6

a. Admin will assign an alphanumeric template number using the following naming convention:

TEMPXXXX-P: TEMP indicates that it is a Template, XXXX is a numeric field assigned by

Admin, _P indicates that the work package is in the preliminary node and has not gone through the
QA/QC process

3. The template champion may have to coordinate the efforts of multiple functional groups.

5.0 UPDATING RELEASED WORK PACKAGES AND

TEMPLATES
Changes to work packages will not be made without the approval of the functional group owning the work package.

Changes to templates will not be made without the approval of the P6 Core Team or template group. The process to
update a work package or template is:

1. Submit request to updating release work package/template

SSC, PM or functional group will identify which work packages/templates need to be updated and notify
Admin.

SSC will create a list of related work packages and templates that will be impacted from the updates made
to the work package/template. The list will be given to Core team before the work package/template
revisions are presented to Core Team.

SSC downloads the P6 Enterprise Comment and Change Form from the P6 website. See Appendix 6.5 for
sample form.

SSC will complete the top portion of the form and submits the form to Admin.

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 9 of 23
Updated 20150309
Admin will register the comment in the comment log and store the form on the N drive at P6 Comment Log
using the following naming convention: YYYY-ZZZZZ.

Where YYYY = is the sequential log number, ZZZZZZ = Description of request.

2. Present the P6 Enterprise Comment and Change Form for consideration

Admin will present the P6 Enterprise Comment and Change Form to the Core Team/P6 Template Group
for approval.

Admin will document the resolution on the comment form, resolve the comment in the work
package/template and update the comment log information.

Admin will return a completed copy of the P6 Enterprise Comment and Change Form to SSC.

Minor corrections in activity coding and logic ties within the work package/template do not need to be
presented to the Core Team/P6 Template Group for approval.

Addition of activities, changes in duration, and dissolvable milestone modifications will be presented to
Core Team and/or Template Group.

If approved, a scheduler is assigned to update the work package/template. If work package/template is not
approved, SSC will inform PM or Functional Group why the work package/template will not be updated.

3. Copy work package/template into preliminary node (PRELIM.TMPLTPR or PRELIM.TMPLTWP).

Scheduler will request Admin place a copy of work package/template in the preliminary node.

Admin copies the requested work package/template. This retains the MnDOT notebook topics for version
control.

Do not cut the work package/template from the authoritative node. The work package/template must
remain available for use until the changes have been approved.

Admin re-names Project ID Suffix to –P indicating that the work package/template is being modified,
updates responsible manager to “Preliminary Templates”, and verifies P6 Project Status is “Inactive”

4. Scheduler updates the work package/template incorporating requested changes

Scheduler makes the necessary changes to the work package/template in the preliminary node in P6.

Scheduler confirms updates made to incorporate the requested changes are acceptable to the person
requesting the changes.

Scheduler reviews other work packages that may be impacted by the changes and updates the appropriate
work packages/templates.

Scheduler records the changes incorporated and the date the Functional Group approved the changes in
MnDOT Version Control notebook topic. (See Section 6.2)

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 10 of 23
Updated 20150309
5. Scheduler submits the work package/template to Admin for QC/QA.

Admin completes QA/QC on the revised work package/template. (See Section 6.4 for QA/QC Form)

Scheduler resolves all QC/QA comments and returns work package/template to Admin.

6. Approve updated work package/template

Admin confirms changes have been made and updates the MnDOT Version Control notebook topic.

7. Work package/template is released for use.

When QA is verified as complete, Admin will confirm the version control information is acceptable (See
Section 6.2), archive the work package/template in the authoritative node and replace it with the revised
work package.

Note a work package/template will be archived each time a new version is authorized. Admin will evaluate
the number of archives within P6 and export (XER) the older archived work package/template versions if
necessary. The XER files will be maintained on the N Drive at N:\OPMTS Project Management\Project
Management Unit\P6 Implementation\Admin Archive\Work Package Archiving.

To archive a work package/template:

Admin will export .xer of “–A” Project ID within Archive node (ADMINARCH, TMPLT-AUTH)
to avoid duplication.

1. Select “File; Export”

2. Export to N: Drive Folder called “Work Package Archive”

3. Update Log within Work Package Archive folder on the N drive

Admin moves old authoritative work package/template to archive node (ADMINARCH, TMPLT-
AUTH) in P6

1. Select “Cut” on Authoritative template EPS node (AUTH.WRKPKG.TMPLT) and

“Paste” it into the Work Package Archive (ADMINARCH, TMPLT-AUTH)

2. Re-name Project ID Suffix to –A

3. Add the date on which it was moved to the archive node to the project name (e.g.
20150109)

4. Open the work package and change Responsible Manager to “Admin Archive”

Admin replaces Authoritative work package/template from Preliminary node (PRELIM.TMPLT,

TMPLTWP)

1. Select “Cut” on finalized work package within Preliminary Templates node

(PRELIM.TMPLT, TMPLTWP) and “Paste” the work package into Authoritative node
(AUTH.WRKPKG.TMPLT)

2. Change Responsible Manager to “Authoritative Templates”

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 11 of 23
Updated 20150309
3. Add Notebook Topic for MnDOT Version Control on authoritative template as follows:
(–Name - Date –“Moved from Preliminary into Authoritative Node” (Example: John
Smith 1/1/2015 Moved from Preliminary into Authoritative Node))

4. Update UDF MnDOT Template/WPkg Version Date to the date the template/work
package was moved from the preliminary to the authoritative node.

8. Work package/template is presented at Extended Core Team meeting

Admin will schedule presentation of work package/template at Extended Core Team meeting.

Scheduler and Functional Group will present the approved work package at the Extended Core Team
meeting. The work package champion and associated SSC staff will prepare the material to be presented.

6.0 APPENDIX

6.1 WORK PACKAGE AND TEMPLATE

FREQUENTLY ASKED QUESTIONS

What is the Difference between a work package and template?

A work package is a group of activities required to produce a deliverable for a project. For example, if a project
requires replacing a bridge, the PM will pick the “New Bridge” work package. The P6 schedule is created by
combining different work packages.

A template is a combination of frequently used work packages. Templates are used to minimize the amount of time
it takes a scheduler to create a new schedule.

How do I find the work packages and templates?

RD-00-09 P6 Work Package Dictionary provides a list of all existing and undeveloped work packages and
templates. The Work Package Dictionary provides a description of each work package, when to use the work
package, deliverable, and functional group responsible for the work package.

All of the work packages are also shown in the Master Work Breakdown Structure.

What is a Dissolvable Milestone?

A dissolvable milestone is a temporary activity that tells the SSC scheduler how to connect the work package to the
templates and other work packages (see PD_10-01 Schedule Creation and Baseline document appendix “Adding a
Work Package”). Once the schedule is built, these milestones disappear.

The dissolvable milestones also help Project Managers understand how the work package connects into schedule,
without having to be a P6 expert

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 12 of 23
Updated 20150309
How do I include the work package in my schedule?
For new projects, fill out the Schedule Initiation form on the Project Management Website. The form allows you to
select the work packages you need for your project.

For projects with existing schedules, The Project Manager will work with the functional groups to determine if a
new work package needs to be added. The SSC will only update schedules if requested by the Project Manager.

Can I Modify the Templates and Work Packages for a project?

Use the standard templates and work packages as much as possible for consistency, reporting, auditing and working
across multiple functional groups.

You can modify templates and work packages to meet project specific needs, but with the following limitations:

 The standard Master Work Breakdown Structure (WBS) cannot be changed or modified without approval
of the P6 Core team or Template Group, but additional work packages or nodes below the WBS may be
added.
 Master WBS nodes must not be deleted. Schedulers will use the “hide if empty” checkbox in the group
and sort window of P6 if you do not want them to show up on the layouts.
 Do not modify a functional group (District or CO) work package without consulting the owner of the
work package.
 Any new activities need to be added by the SSC in accordance with P6 Schedule Creation and Baseline
Process.

Can I make my own templates for use?

No, consistent work package and template formatting is required for reporting and auditing. If a new template or
work package is required, contact your SSC. The SSC can create and propose new templates and work packages
using the process outline in this document to a statewide committee for consideration. Each new template will go
through a QC/QA process for consistency with the P6 enterprise system before implementation.

Are the work packages compatible with PPMS type schedules?

Yes, but the dissolvable milestones were not developed for easy incorporation into PPMS type schedules. The PM
and SSC will need to determine the appropriate links if using a PPMS schedule.

What if the templates/work packages are wrong?

Contact your SSC immediately. The SSC will provide the comments back to the P6 Administration team so the
template and work package can be corrected. The P6 Administration team will work with the functional office and
statewide groups to make the corrections following the process in this document.

6.2 VERSION CONTROL

After the modifications to the work package/template are complete, the version date (‘‘MnDOT Template / WPkg
Version Date Column) of the work package/template will be updated to include the latest date of the revisions. The

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 13 of 23
Updated 20150309
notebook topic ‘MnDOT Version Control’ must include the scheduler’s name responsible for the changes, the date
the change was made, and a summary of the modifications.

Version Control Process

Once the work package/template has been approved, the following version control documentation process must be
followed.

1. Update the MnDOT version control notebook topic.

a. Write the name of the work package/template owner and the date that the work package was accepted.
b. Write the scheduler’s name and date when the work package was built into P6.
c. Capture any further modifications in the same convention.

2. Update the ‘MnDOT Template/ WPkgVersion Date’ column to include the most recent date the work
package/template has been revised and moved into the authoritative node. Note: This must match the date
in the ‘MnDOT Version Control’ notebook topic of when the work package was moved from the
Preliminary Node to the Authoritative Node.

6.3 ACTIVITY ID PREFIX

Activity WBS Node Work Package Work Package or Functional Group
ID Name or Template Name
Prefix Template
Project ID
ACC Agreement TEMPMODA Project Template Co-op Agreements
Cooperative TMPL3056 Cooperative Construction Agreement
Construction
ADA Americans with TEMPMAIN Maintenance Plan ADA Unit
Disabilities Act TEMPMINA Minor Project Template
TEMPMODE Project Template
TMPL1416 ADA Recommendations
ADM Admin TEMPCMBP Cable Median Barrier Plan Letting
TEMPLAND Landscaping Plan Coordination
TEMPMAIN Maintenance Plan
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL2000 Process A
TMPL2001 Process B
TMPL2002 Process B Complex
TMPL2003 Prequalification (Tech Proposal)
TMPL2004 Process B PODI
ADR Agreement TEMODA Project Template Project
Detour TMPL3058 Detour Agreement Management
AIR Air Quality TMPL1330 Air Quality Analysis Ops Env. Model &
Analysis Test
ARR Agreements TMPL1421 Railroad Bridge Agreement Modal Planning
Railroad TMPL1422 Railroad Flagging Agreement Div. Freight &
TMPL1423 Railroad Track Relocation Agreement Commercial
AUT Agreements TEMPMODA Project Template OLM R.E. &
Utility TMPL1424 Utility Agreement Policy Dev. Utility
Agr & Permit
BCL Barrier Cross TEMPCMBP Cable Median Barrier Plan Districts Design
Overs

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 14 of 23
Updated 20150309
Activity WBS Node Work Package Work Package or Functional Group
ID Name or Template Name
Prefix Template
Project ID
BDS Blowing and TMPL1417 Blowing and Drifting Snow Control Construction &
Drifting Snow Ops Road Veg.
Mgmt
BFR Bridge TMPL1500 New Bridge OM & RR.
Foundation TMPL1501 Consultant Bridge Design (Prelim & Final Geotech
Recommendatio TMPL1502 Consultant) Engineering
ns TMPL1508 Bridge Substructure Widening
BHL Bridge TMPL1500 New Bridge Bridge Office
Hydraulics TMPL1501 Consultant Bridge Design (Prelim & Final Bridge Hydraulics
TMPL1502 Consultant)
TMPL1506 Consultant Bridge Design (Final Only
Consultant)
Culvert

CAR Crash Analysis TEMPCMBP Cable Median Barrier Plan Districts Traffic
Report Control
CFR Culvert TMPL1506 Culvert OM & RR Geotech
Foundation Engineering
Recommendatio
ns
CGP Coast Guard TMPL1354 Section 9 (Coast Guard) Permit Bridge Office
Permit Preliminary Bridge
CRU Cultural TEMPCMBPT Cable Median Barrier PlanProject Pre-Construction
Resource Unit EMPMODAT TemplateCultural Resources - Work Cultural Resources
MPL1302TMP Package 1 Full Section 106 - All Federal
L1304TMPL13 AgenciesCultural Resources - Work
02C Package 2 FHWA FundsCultural Resources
- Work Package 3 State Level Review
(State Funds Only)
CSP Contaminated TMPL1319 Contaminated Materials Management Construction &
Materials Special Provisions Ops Cont. Mat. MT
Management
Special
Provisions
CTX CATEX TEMPCMBP Cable Median Barrier Plan Pre-Construction
TEMPMAIN Maintenance Plan Env. Assessment
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL1334 Categorical Exclusion (Non-Programmatic)
TMPL1336 Categorical Exclusion - Programmatic
CVL Civil Rights TEMPCMBP Cable Median Barrier Plan OPM & TS Project
TEMPLAND Landscaping Plan Delivery Letting
TEMPMAIN Maintenance Plan Coordination
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL2000 Process A
TMPL2001 Process B
TMPL2002 Process B Complex
TMPL2003 Prequalification (Tech Proposal)
TMPL2004 Process B PODI
TMPL2005 Design Build

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 15 of 23
Updated 20150309
Activity WBS Node Work Package Work Package or Functional Group
ID Name or Template Name
Prefix Template
Project ID
DME Design Memo/ TEMPMODA Project Template OPM & TS Design
Design TMPL3026 Design Memo/Design Exception Support Geometric
Exceptions Des. Sup.
DSB Design Build TMPL2005 Design Build OPM & TS Design
Build
EAW Environmental TMPL1338 Environmental Assessment Pre-Construction
Assessment (EA)/Environmental Assessment Worksheet Env. Assessment
Worksheet (EAW)
EDD Environmental TEMPMODA Project Template Construction &
Due Diligence TMPL1306 Environmental Due Diligence 1 Ops Cont. Mat. MT
TMPL1308 Environmental Due Diligence 2
TMPL1310 Environmental Due Diligence 3
EIS Environmental TMPL1340 Environmental Impact Statement (EIS) Pre-Construction
Impact Env. Assessment
Statement
ENM Early TEMPCMBP Cable Median Barrier Plan Districts Project
Notification TEMPMAIN Maintenance Plan Management
Memo TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL3006 Early Notification Memo
ESA Environmental TEMPMODA Project Template Construction &
Site Assessment TMPL1312 Environmental Site Assessment (Phase I & Ops Cont. Mat. MT
TMPL1313 II) Acquisition
TMPL1314 Environmental Site Assessment (Phase I &
II) Early Acquisition
Environmental Site Assessment (Phase I &
II) No Acquisition
EST Estimating TEMPCMBPT Cable Median Barrier PlanLandscaping OPM & TS Project
EMPLANDTE PlanMaintenance PlanMinor Project Delivery Eng. Cost
MPMAINTEM TemplateProject TemplateProcess AProcess & Estimate
PMINATEMP BProcess B ComplexPrequalification (Tech
MODATMPL2 Proposal)Process B PODIDesign Build
000TMPL2001
TMPL2002TM
PL2003TMPL2
004TMPL2005
FBP Final Bridge TMPL1500 New Bridge Bridge Office Final
Plans TMPL1501 Consultant Bridge Design (Prelim & Final Bridge
TMPL1502 Consultant)
TMPL1508 Consultant Bridge Design (Final Only
Consultant)
Bridge Substructure Widening
FCP Final Culvert TMPL1506 Culvert Bridge Office Final
Plans Bridge
FDB Final Design TEMPSCOP Scoping Template Districts Project
Baseline Management
FDR Foundation TMPL1414 Foundation Recommendations OM & RR Geotech
Recommendatio Engineering
ns
FRP Final Repair TMPL1503 Bridge Preservation Bridge Office Final
Plans TMPL1504 Bridge Redeck Bridge

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 16 of 23
Updated 20150309
Activity WBS Node Work Package Work Package or Functional Group
ID Name or Template Name
Prefix Template
Project ID
GEO Geotechnical TEMPCMBP Cable Median Barrier Plan OM & RR Geotech
Report Engineering
HYD Hydraulics TEMPCMBP Cable Median Barrier Plan Districts
TEMPMODA Project Template Hydraulics/WRE
TMPL3038 Hydraulics Design
HSB Historic Bridge TMPL1509 Historic Bridge Study Bridge Office
Study
IAR Interstate Access TEMPMODA Project Template Districts Traffic
Request TMPL3022 Interstate Access Request
ICE Interstate TEMPMODA Project Template Districts Traffic
Control TMPL3018 Intersection Control Evaluation
Evaluation
LAY Staff Approved TEMPMODA Project Template Districts Project
Layout TMPL3024 Staff Approved Layout Management
LGA Lighting TEMPMINA Minor Project Template Districts Lighting
Agreement TMPL1376 Lighting Agreement
LIM Right of Way TEMPMODA Project Template Districts Design
Construction TMPL3028 RW Construction Limits
Limits
LMR Land TEMPCMBPT Cable Median Barrier PlanLandscaping OLM R.E. &
Management EMPLANDTE PlanMaintenance PlanMinor Project Policy Dev Purch
Right of Way MPMAINTEM TemplateProject TemplateProcess BProcess & Relocation
PMINATEMP B ComplexPrequalification (Tech
MODATMPL2 Proposal)Process B PODIDesign Build
001TMPL2002
TMPL2003TM
PL2004TMPL2
005
LMU Land TEMPCMBP Cable Median Barrier Plan OLM R.E. &
Management TEMPLAND Landscaping Plan Policy Dev. Utility
Utilities TEMPMINA Minor Project Template Agr & Permit
TEMPMODA Project Template
TMPL2001 Process B
TMPL2002 Process B Complex
TMPL2003 Prequalification (Tech Proposal)
TMPL2004 Process B PODI
TMPL2005 Design Build
LSP Landscape Plan TEMPLAND Landscaping Plan Pre-Construction
Env. Plan & Design
MDR Material Design TEMPMAIN Maintenance Plan OM & RR
Recommendatio TEMPMODA Project Template Pavement
ns TMPL3034 Material Design Recommendations (MDR) Engineering
MNC Municipal TEMPMODA Project Template Districts Project
Consent TMPL3030 Municipal Consent Management
TMPL3032 Municipal Consent (Appeal Process)

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 17 of 23
Updated 20150309
Activity WBS Node Work Package Work Package or Functional Group
ID Name or Template Name
Prefix Template
Project ID
MS_ Milestone TEMPCMBP Cable Median Barrier Plan Districts Project
TEMPLAND Landscaping Plan Management
TEMPMAIN Minor Project Template
TEMPMINA Maintenance Plan
TEMPMODA Project Template
TEMPSCOP Scoping Template
TMPL1600 Fee Acquisition
TMPL1610 Acquisition (Metro)
TMPL1630 Temporary Right to Construct
TMPL3000 Milestones (Design)
MSY Mussel Survey TMPL1349 Mussel Survey Pre-Construction
Env. Assessment
NAD No Association TMPL1317 No Association Determination Construction &
Determination Ops Cont. Mat. MT
NOI Noise Analysis TMPL1328 Noise Analysis Construction &
Ops Env. Model &
Test
NPP NPDES Permit TEMPCMBPT Cable Median Barrier PlanLandscaping Districts
EMPLANDTE PlanProject TemplateNPDES Stormwater Hydraulics/WRE
MPMODATMP Discharge Permit
L1346
OPM Ongoing Project TEMPCMBP Cable Median Barrier Plan Districts Project
Management TEMPMAIN Maintenance Plan Management
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL3002 Project Management
PBP Preliminary TMPL1500 New Bridge Bridge Office
Bridge Plans TMPL1501 Consultant Bridge Design (Prelim & Final Preliminary Bridge
TMPL1502 Consultant)
TMPL1508 Consultant Bridge Design (Final Only
Consultant)
Bridge Substructure Widening
PHU Phase I Update TMPL1315 Phase I Update Construction &
TMPL1316 Phase II Update Ops. Cont. Mat.
MT
PLN Plan TEMPCMBP Cable Median Barrier Plan Districts Design
TEMPMAIN Maintenance Plan
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL3040 Road Plans
PMM Project TEMPCMBP Cable Median Barrier Plan Districts Project
Maintenance TEMPMAIN Maintenance Plan Management
Plan TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL3002 Project Management
PND Stormwater TEMPMODA Project Template Districts
Design TMPL3036 Stormwater Treatment Design Hydraulics/WRE

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 18 of 23
Updated 20150309
Activity WBS Node Work Package Work Package or Functional Group
ID Name or Template Name
Prefix Template
Project ID
PRO Prepare Special TEMPCMBP Cable Median Barrier Plan Districts Project
Provisions TEMPLAND Landscaping Plan Management
TEMPMAIN Maintenance Plan
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL3052 Special Provisions
PRS Plan Review/ TEMPCMBPT Cable Median Barrier PlanLandscaping OPM & TS Project
Signatures EMPLANDTE PlanMaintenance PlanMinor Project Delivery Design
MPMAINTEM TemplateProject TemplateProcess AProcess Services
PMINATEMP BProcess B ComplexPrequalification (Tech
MODATMPL2 Proposal)Process B PODI
000TMPL2001
TMPL2002TM
PL2003TMPL2
004
PWP Public Waters TEMPMODA Project Template Districts
Permit TMPL1350 DNR Public Waters Permit Hydraulics/WRE
RAP Response Action TMPL1318 Response Action Plans Construction &
Plans Ops Cont. Mat. MT
RDP Direct Purchase TMPL1600 Fee Acquisition OLM R.E. &
TMPL1610 Acquisition (Metro) Policy Dev. Purch
TMPL1630 Temporary Right to Construct & Relocation
RED Condemnation TMPL1600 Fee Acquisition OLM R.E. &
TMPL1610 Acquisition (Metro) Policy Dev.
RFR Request & TEMPCMBP Cable Median Barrier Plan Construction &
Obtain Files TEMPMINA Minor Project Template Ops Cont. Mat. MT
From Regulator TMPL1305 Regulatory File Review
RHB Rehabilitation TMPL1503 Bridge Preservation Bridge Office
TMPL1504 Bridge Redeck Bridge
TMPL1508 Bridge Substructure Widening Construction
RMA Regulated TMPL1326 Regulated Materials Buildings Construction &
Materials Ops Reg. Mat. MT
Buildings
RMT Regulated TMPL1326 Regulated Materials Buildings Construction &
Materials TMPL1327 Regulated Materials Bridge Ops Reg. Mat. MT
RPR Receive and TMPL1600 Fee Acquisition OLM R.E. &
Distribute Right TMPL1630 Temporary Right to Construct Policy Dev.
of Way Package TMPL1640 Commissioner's Orders

RRL Relocation TMPL1650 Relocation Districts Right of

Way
RTT Right of Way TMPL1600 Fee Acquisition Districts Right of
Titles TMPL1610 Acquisition (Metro) Way
TMPL1630 Temporary Right to Construct
RVL Right of Way TMPL1600TM Fee AcquisitionAcquisition OLM R.E & Policy
Valuations PL1610TMPL1 (Metro)Temporary Right to Construct Dev. Appraisal
630 Mgmt
RWP Right of Way TMPL1600 Fee Acquisition Districts Right of
Package TMPL1610 Acquisition (Metro) Way
TMPL1630 Temporary Right to Construct
TMPL1640 Commissioner's Orders

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 19 of 23
Updated 20150309
Activity WBS Node Work Package Work Package or Functional Group
ID Name or Template Name
Prefix Template
Project ID
SAT Signal TEMPMINA Minor Project Template Districts Signals
Agreement TMPL1377 Signal Agreement
SAW Environmental TMPL1332 Environmental Assessment Worksheet Pre-Construction
Assessment (EAW) State Env. Assessment
Worksheet
SDE Surveys Design TEMPCMBP Cable Median Barrier Plan Districts Surveys
TEMPLAND Landscaping Plan
TEMPMAIN Maintenance Plan
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL3014 Design Surveys
SDL Surveys District TEMPMODA Project Template Districts Surveys
Land TMPL3012 District Land Surveys
SFF Section 4 F TMPL1419 Section 4(f) Coordination Districts Project
Management
SGC Surveys TMPL1400 Geodetic Control Surveys OLM Survey &
Geodetic Control Mapping Geodetic
Unit
SGN Signing Plan TEMPCMBP Cable Median Barrier Plan Districts Signing
TEMPMAIN Maintenance Plan
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL1339 Signing Plan
SPB Surveys TMPL1402 Photogrammetric Basemap OLM Survey &
Photogrammetric Mapping
Basemap Photogrammetric
SPC Surveys Project TMPL1401 Project Control Surveys Districts Surveys
Control
SPS Special TEMPCMBP Cable Median Barrier Plan OPM & TS Project
Provisions TEMPLAND Landscaping Plan Delivery Special
TEMPMAIN Maintenance Plan Provisions
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL2000 Process A
TMPL2001 Process B
TMPL2002 Process B Complex
TMPL2003 Prequalification (Tech Proposal)
TMPL2004 Process B PODI
SSF Section 6(f) TMPL1420 Section 6(f) Coordination Districts Project
Management
STR Structures TMPL1500 New Bridge Bridge Office
TMPL1501 Consultant Bridge Design (Prelim & Final Preliminary Bridge
TMPL1502 Consultant)
TMPL1506 Consultant Bridge Design (Final Only
Consultant)
Culvert
SUE Subsurface TMPL1379 Subsurface Utility Engineering (SUE) Districts District
Utility Utilities
Engineering

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 20 of 23
Updated 20150309
Activity WBS Node Work Package Work Package or Functional Group
ID Name or Template Name
Prefix Template
Project ID
SUR Survey Request TEMPCMBP Cable Median Barrier Plan Districts Project
TEMPMAIN Maintenance Plan Management
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL3010 Surveys
TCP Traffic Control TEMPCMBP Cable Median Barrier Plan Districts Traffic
Plan TEMPLAND Landscaping Plan Control
TEMPMAIN Maintenance Plan
TEMPMODA Project Template
TMPL3044 Traffic Control/ Detour/ Staging Plan
TES Threatened & TEMPMODA Project Template Pre-Construction
Endangered TMPL1370 Section 7 Determination [Threatened & Env. Assessment
Species TMPL1701 Endangered Species] - No Effect
TMPL1702 Section 7 Determination [Threatened &
Endangered Species] - May Affect
Section 7 Determination [Threatened &
Endangered Species] - Formal Consultation
TFC Traffic Counts TMPL1375 Traffic Counts Districts Traffic
TLT Traffic Lighting TEMPMAIN Maintenance Plan Districts Lighting
Plan TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL1335 Lighting Plan
TMP Transportation TEMPCMBP Cable Median Barrier Plan Districts Project
Management TEMPLAND Landscaping Plan Management
Plan TEMPMAIN Maintenance Plan
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL3020 Transportation Management Plan (TMP)
TMS Traffic TEMPMAIN Maintenance Plan Districts Traffic
Monitoring TEMPMINA Minor Project Template Management
System TEMPMODA Project Template
TMPL3048 TMS Plan
TPM Transportation TEMPMODA Project Template Districts Traffic
Pavement TMPL3046 Pavement Marking Plan
Marking plan
TRF Traffic Forecasts TEMPMODAT Project TemplateTraffic Forecasts Modal Planning
MPL3016 Div. Transportation
TSG Transportation TEMPMAIN Maintenance Plan Districts Signals
Signal Plan TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL1351 Signal Plan
TTT Time and Traffic TEMPCMBP Cable Median Barrier Plan Districts
TEMPMAIN Maintenance Plan Construction
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL3050 Time and Traffic

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 21 of 23
Updated 20150309
Activity WBS Node Work Package Work Package or Functional Group
ID Name or Template Name
Prefix Template
Project ID
TUR Turn in TEMPCMBP Cable Median Barrier Plan Districts Project
TEMPLAND Landscaping Plan Management
TEMPMAIN Maintenance Plan
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL3054 Project Turn In
UTI Utility TEMPCMBP Cable Median Barrier Plan Districts District
Information TEMPLAND Landscaping Plan Utilities
Meetings TEMPMAIN Maintenance Plan
TEMPMINA Minor Project Template
TEMPMODA Project Template
TMPL1425 Utility Coordination
VEA Value TMPL1407 Value Engineering OPM & TS Design
Engineering Support Value Eng.
Unit
VGT Vegetation TMPL1368 Vegetation Review Construction &
Review Ops Road Veg.
Mgmt
VIS Visual Impact TMPL1409 Visual Impact Assessment Pre-Construction
Assessment Env. Plan & Design
VQM Visual Quality TMPL1408 Visual Quality Management Plan Pre-Construction
Management Env. Plan & Design
WDP Watershed TEMPCMBP Cable Median Barrier Plan Districts
District Permit TEMPLAND Landscaping Plan Hydraulics/WRE
TEMPMODA Project Template
TMPL1352 Watershed District Permit
WRE Water Resource TEMPMODA Project Template Districts
Engineering TMPL3042 Hydraulics/ WRE Plans Hydraulics/WRE
Plans
WTL Wetlands TEMPMAIN Maintenance Plan Districts
Delineate TEMPMODA Project Template Hydraulics/WRE
TMPL1348 Wetland Delineations (Metro)
TMPL3008 Wetland Delineations
WTP Wetland/WCA TEMPMODAT Project TemplateWetland/WCA & Aquatic Districts
& Aquatic TMPL1355 Resources (404/401/Section 10) Hydraulics/WRE
Resources

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 22 of 23
Updated 20150309

6.4 QA/QC FORM

This form is available in Word Format at FM-00-02_QC-QA checks for work packages.docx

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx
Work Package Creation and Maintenance Page 23 of 23
Updated 20150309

6.5 P6 ENTERPRISE COMMENT AND CHANGE

FORM
This form is available in Word Format at FM-00-04_P6 Enterprise Comment and Change Form.docx

N:\OPMTS Project Management\Project Management Unit\P6 Implementation\Documents\ProcessDocuments\PD-00-07_Work Package

Creation and Maintenance Process.docx