Build Work Packages

What are Build Work Packages?

A Build Work Package is comprised of a single or group of related tasks that are required to be performed in order to produce a required element of the Project delivery. Project on Demand offers the ability to define, allocate and execute Build Work Packages which are placed directly into the Phase Progression.

Build Work Packages can be managed through the Build Work Package Management Tool, the Tool can be accessed by clicking Open Tool through the associated "Define Build Work Packages" Goal in the Execution Phase of Phase Progression

Note: Accessing the Build Work Package Management Tool through an associated Goal on the Phase Progression will automatically set that Goal's Status to In Progress if it is currently in a Status of Not Started.

Once defined the Phase Progression will have an option to View individual Build Work Packages that is accessible to any User with View Permission on the Build Work Package Management Tool.

How should they be used?

The Build Work Package management process within Project on Demand is as follows:

Project Management Process Step Action within Project on Demand
1 Identify and record the work package. Create a new Build Work Package.
2 Allocate work package. Allocate Build Work Package to a User.
3 Update progress of work package. Allocated User updates Completion % based on progress.
3 Complete execution of work package. Allocated User completes the execution.

Build Work Package Properties

Name Description Possible Values
ID Unique Work Package reference number. Number - Generated by the application.
Title Title of the Build Work Package. Text.
Description Full description of the Build Work Package. Text.
Objective Full description of the objective associated with the Build Work Package. Text.
Forecast Time Forecast amount of days to execute the Build Work Package. Number. (0 - 1000000000.00).
Completion % Percent of the Build Work Package completed. Number. (0 - 100.00).
Dependencies Dependencies associated with the Build Work Package. List of Build Work Package Dependencies.
Execution Notes Notes added during Execution. Text.

Build Work Package Dependency Properties

Name Description Possible Values
ID Unique Work Package Dependency reference number. Number - Generated by the application.
Description Full description of the Dependency. Text.

Managing

The Build Work Package Management Tool can be used to Create, Edit, Allocate, Import and Remove Build Work Packages. The Executing of Build Work Packages is done by the allocated User on the Project Dashboard through either the Phase Progression or the "Internal Action" generated.

Build Work Packages displayed are sorted in ascending order by Status then ID and paged to 25 items per page.

Additional properties can be displayed by using the row details feature of the DataGrid.

Creating a new Build Work Package

Clicking on the New button will display a child window so a new Build Work Package can be recorded.

Dependencies can be created and removed using the New and Remove buttons respectively. Individual Dependencies can be edited using the "Inline Editing" feature of the DataGrid.

Once all properties are set the new Build Work Package can be saved by clicking the Save button at the bottom of the child window. If any validation errors are encountered they will display at the bottom of the child window and must be rectified before the new Build Work Package can be successfully saved.

Upon successful completion of creating a new Build Work Package the child window will close, a success message will display at the bottom of the application and the newly created Build Work Package will be selected in the DataGrid.

If the Cancel button is clicked, the child window will close and nothing will be saved.

Editing a Build Work Package

Selecting a Build Work Package and clicking on the Edit button will display a child window so the Build Work Package can be edited. Alternatively the row can be double-clicked to perform the same action.

Note: A confirmation window will be displayed asking for confirmation to continue when attempting to edit a Build Work Package that has already been allocated.

Dependencies can be created and removed using the New and Remove buttons respectively. Individual Dependencies can be edited using the "Inline Editing" feature of the DataGrid.

Once all necessary changes have been made the Build Work Package can be saved by clicking the Save button at the bottom of the child window. If any validation errors are encountered they will display at the bottom of the child window and must be rectified before the Build Work Package can be successfully saved.

Upon successful completion of the editing process the child window will close and a success message will display at the bottom of the application.

If the Cancel button is clicked, the child window will close and any changes will be cancelled.

Allocating a Build Work Package

A Build Work Package can be allocated to a User with Project access or set to a text reference of an "external" user. If allocated to a User they will be able to Execute the Build Work Package on their Project Dashboard via the Phase Progression or Pending Actions. If the Build Work Package is allocated to an "external" user referenced by text in the Responsibility Of property then the Build Work Package will allow Execution to any Users with Edit Permission on the Build Work Package Management Tool.

Selecting a Build Work Package and clicking on the Allocate button will display a child window so the Build Work Package can be allocated.

The Responsibility Of property of a Build Work Package can be set to reference a User or text. If a User is selected from the drop-down any previously entered text will be removed and vice versa. If a User is selected for allocation, an "Internal Action" will be created for them in order to Execute the Build Work Package.

A Due Date can be selected from the calendar, this value will set the Review Date and Due Date properties of the "Internal Action" that is generated by the application for the Execution of the Build Work Package.

Once the Responsibility Of and Due Date properties have been set set the Build Work Package can be sent out/marked for Execution by clicking the Allocate button. Upon successful completion the child window will close, an "Internal Action" will be created for any selected User and a success message will display at the bottom of the application. An email will be sent to any User selected notifying them they have an outstanding Build Work Package Execution to complete.

If the Cancel button is clicked, the child window will close and any changes will be cancelled.

Removing a Build Work Package

Selecting the Build Work Package to remove and clicking on the Remove button will display a removal confirmation window. If Cancel is clicked the confirmation window will close and the Build Work Package will not be removed. If Yes is clicked the selected Build Work Package will be removed and a successful removal message will be displayed at the bottom of the application.

If the last Build Work Package on a page is removed the DataGrid will navigate to the previous page upon successful removal.

Executing a Build Work Package

Allocated Users can Execute a Build Work Package via the Phase Progression by clicking the Build Work Package to display the context menu then clicking the Execute option. Alternatively the "Internal Action" generated by the application will be displayed in the allocated Users Pending Actions and can be Executed by selecting the Action and clicking the Execute button or double clicking the Action itself in the DataGrid.

Build Work Packages allocated to an "external" user by setting the Responsibility Of property to a text reference will need to be Executed by a User with Edit Permission on the Build Work Package Management Tool. The procedure detailed above via the Phase Progression can be used to Execute these Build Work Packages.

Once an Execute option has been clicked a child window will display so the Build Work Package can be executed.

The Completion % can be edited and any Execution Notes can be recorded in the text box provided.

Any changes made can be saved for future completion by clicking the Save button, this will close the child window, display a success message at the bottom of the application but will not complete the Build Work Package Execution so futher changes can be made at a later time.

Clicking the Complete button will complete the Execution process, this will close the child window, any associated generated Action will be set to Completed and a success message will display at the bottom of the application.

If the Cancel button is clicked, the child window will close and any changes will be lost.

Importing Build Work Packages

Clicking the Import button will display the Import Build Work Packages child window.

In order to view and import Build Work Packages from another Project, a Project must be selected from the "Import from Project" drop-down at the top. The drop-down is populated with any Projects that have Build Work Packages identified.

From the Import button there are two options for importing Build Work Packages:

Import All - Import all Build Work Packages returned with the current search criteria. Please note: Build Work Packages on all returned pages will be imported.

Import Selected - Import any currently displayed Build Work Packages that have been checked in the Import column of the DataGrid. To check all Build Work Packages use the Check All button at the bottom of the child window.

Upon successful import the Import Build Work Packages child window will close, a success message will be displayed at the bottom of the application and the last of the newly imported Build Work Packages will be selected.

Concurrency Control

The Build Work Packages implement optimistic concurrency control.