Exporting to Microsoft Project
You can export a capability pattern or delivery process as an XML file that can be opened in Microsoft Project. This XML file contains links to specific pages in the original method library.
About this task
All non-suppressed activities (at any level in the hierarchy) and tasks are exported as Microsoft Project tasks. If the element has children in the work breakdown structure (WBS), it is exported as summary tasks in Microsoft Project.
Dependencies in the work breakdown structure are carried over to Microsoft Project. If there are circular dependencies in work breakdown structure, Microsoft Project issues a warning but accepts the circular dependencies.
Roles are exported as Microsoft Project resources. They are connected to tasks or summary tasks as follows:
- If a task is not suppressed, the primary and additional performer roles are associated with it.
- If an activity has all of its children suppressed, the primary and additional performers of all of its suppressed children are assigned to it. This activity exports as a Microsoft Project task because it has no children.
The following elements are exported:
- Work Products
- Activities
- Tasks
- Milestones
- Roles
| MEC element | MSP element |
|---|---|
| Activity | Task |
| Milestone | Task |
| Task | Task |
| Role | Resource |
| Work Product | Text field |
Microsoft Project sets the start and end dates for the project. You need to adjust them after the export has completed by using Microsoft Project. For additional Microsoft Project settings, see Setting up Microsoft Project for Engineering Method Composer processes.
To export to Microsoft Project: