Result or Product of this Process
| Round Rectangle |
|---|
|
This process enables project managers to self report current project status. |
| Deck of Cards |
|---|
|
| Card |
|---|
| - The primary actor for this process is the Project Manager
- No other actors actively work with this process. All actors benefit from regular and accurate updates to projects
- No other processes are spawned from this process
|
| Card |
|---|
|  Image Removed |
| Card |
|---|
| The project manager is responsible for timely updates. |
|
e-Builder Instructions
The project manager opens and completes the Project Manager's Update form
Project managers use this process to update the status of their project. The process displays the most recent update information on the same page used to update project information and allows the use of a "sleep timer" to set an interval for the next PMU update to appear in your court. See the Step Instructions tab for detailed instructions, including how to use this process to only update the Project Status that is located on the Details page. |
| Deck of Cards |
|---|
|
| Card |
|---|
| - Project managers use this process to provide project updates at regular intervals. Updates should include confirming or updating the current project status, the estimate at Completion, and pertinent details about the project.
- The project manager will be asked to enter their name as part of the update. This is considered signing the update.
- The PM submitted date will be filled in when the Submit step is taken.
- The process will start (spawn) a new process for your next update whenever the project status is something other than "Complete". Use the automatically started process located "In your Court" for subsequent updates.
- By using the automatically started process your most recent update will display on the left side of the page while you complete the current update on the right side. (See the Start Step instructions)
| Note |
|---|
When creating the first project manager update for a project the Submit action will move the process to the PM Update Status.For only the first update, it is necessary to take the Submit action second time from the PM Update Status step. |
| Gliffy Diagram |
|---|
| border | true |
|---|
| chrome | min |
|---|
| size | 300 |
|---|
| name | First Time Flow |
|---|
|
|
| Card |
|---|
|  Image Added
|
| Card |
|---|
| | Note |
|---|
Please note: Is this a One-Off or the Last Update is a great option for DAILY UPDATES. Answer Yes if you wish only to update the Project Status on the Details page or if this is the last detailed update for which you wish to use the sleep timer functionality. When the Yes option is used, in both instances above, no new spawned processes will occur. If you have used the Yes option, and at a later date, you want another PMU and the option to use the sleep timer simply start a new instance of the process. |
| Section |
|---|
| Column |
|---|
| Instructions - Using the drop-down menu, choose the Current Project Status.
- Enter the Current Project Update (by PM). Note that the text box for this is expandable
by dragging the bottom right corner of the text box. This is a required field. - Enter the Current PM Estimate at Completion.
- Add a photo (if desired) to be included in the Current Photo field.
- Please enter your name in the Project Manager field. This action simulates affixing your signature to the information.
- The PM Submitted Date will be the date on which you take the Submit action.
- "Is this the Last Update?" Choosing "Yes" will end all the current PMUa process session. If you need to create a new update you can always start a new PMUa process for the project. Note: if you do restart you will need to run the task through 2x just as you did the first time for full feature set to work.
- In the Project Schedule Updated? Field indicate if the project schedule has been updated. (Yes, No, N/A)
- Enter Schedule Notes. This text box is also expandable.
- Click the Submit button.*
*Submit from the PM Update Status step if this is the first PMU for the project. If the PMU is not ready to Submit use the Save Draft button to save your work and return to complete and submit the PMU at a later date. |
|
| Section |
|---|
Start| Cloak |
|---|
- The Initiator has an opportunity to enter information into the Current Project Status, Current Project Update (by PM), Project/Drawing Stage, EHS Update, FE Update, FIS/Signage Update, IS&T/Security Update, SPT Update, Current SF, Current PM Estimate at Completion, Room(s) Affected, Current Photo, Project Manager, PM Submitted Date, Is this a One-Off or the Last Update?. These fields will be updated to the projects details page.
- When the Submit action is taken the next step is Report Generation.
|
Timer set <=1?| Cloak |
|---|
- This is an e-Builder conditional.
- No user interaction is required.
- This step evaluates if the initiator set the Remind me in days to 1 or less and send it back to them if True
- The process continues if the value is >1 (note the value must be a whole number as the instructions explain to the user)
|
Set Timer to a whole # > 1 e.g. 5,10| Cloak |
|---|
- This is an e-Builder user step
- The initiator ends up on this step if they do not follow the directions provided and provide a whole # > 1
- The initiator is given additional, clear instructions to change the value to a whole # > 1
- The user submits this process and it goes back the the prior conditional to ensure the user complied with the instructions
|
Report Generation| Cloak |
|---|
- This is an e-Builder system step.
- No user interaction is required.
- This step evaluates if this is the first time a PMU has been generated for this project and routes the process accordingly.
|
PM Status Report| Cloak |
|---|
- This is a mail merge step.
- No user interaction is required.
- This step produces a hard copy of the PMU from a template.
|
PM Update Status| Cloak |
|---|
- This is an update step completed by the project manager.
- See the instructions for the Start Step. Project managers complete the same fields in this step.
|
Subs or Punchlist?| Cloak |
|---|
- This is a conditional that is looking for a status setting of Substantially Complete or Punchlist
- If either is true then a mail merge is generated (Punchlist Notification)
- the process then moves to the conditional "Project Active" step
|
PM Closeout status?| Cloak |
|---|
- This is a conditional that is looking for a status setting of PM Closeout
- the process then moves to the conditional "CRSP Project" step
|
CRSP Project?| Cloak |
|---|
- This is a conditional that is looking for a project type setting of CRSP
- If true then a mail merge is generated (CRSP AA Notification)
- If false then a mail merge is generated (AA/PM 14.2 Status)
- In either scenario , the process then moves to the conditional " Project Active" step
|
Accounting Closeout Status?| Cloak |
|---|
- This is a conditional that is looking for a status setting Accounting Closeout
- If true then a mail merge is generated (Accounting Close)
- If false then a mail merge is generated (Document Closeout)
- In either scenario , the process then moves to the conditional " Project Active" step
|
Project Active| Cloak |
|---|
- This step determines if the project status is Active.
- If it is no longer active no new update process will be started.
- No user interaction is required.
- No instructions are needed for this step.
|
Last PM Update?| Cloak |
|---|
- This conditional checks if the Is this the Last Update? field is answered as Yes.
- If True the next step is Finish
- If False the next step is PMU Release Timer
|
Spawn New Update| Cloak |
|---|
- This step starts a new PMU process to be used for the next PMU.
- No user interaction is required.
- The new process will be placed in the project manager's court and may remain there until needed. It will contain information from the previous update for reference.
|
Finish |
|
|
...
