Project Deliverables

Establishes the project deliverable definition and the basic deliverable structure of components and items that represent the systems, sub-systems and end material to be engineered and delivered. This is the entry point of the IFS Project Deliverables design phase, capturing item numbers, item names/descriptions, general information and default values before parts and quantities are added.

Enriches the basic deliverable structure with part information and quantities to produce the project deliverable detailed structure. Items representing material get engineering, inventory and/or purchase parts created new, copied from PDM/product/item structures, or generated via item configuration; No Part items are also supported. Completing the detailed structure enables the planning phase.

Plans the work required to realize each deliverable item by creating planning items connected to project activities, and generates the material plan for manufacture and purchase. A deliverable item can carry many planning items (e.g. manufacture, purchase, install, ship); the calculate required material option builds shop order, purchase, project MRP and MRP plan lines that peg to supply.

Manages the engineering/design documentation tied to project deliverables using IFS Document Management document packages, which group documents, connect to a project activity, and track weighted average progress against milestone profiles. Document revisions are registered, connected to business objects (parts, activities), routed for electronic approval and released, providing the document-side of project deliverables.

IFS Document Management holds each deliverable as a document title with one or more revisions moving through Preliminary, Approval In Progress, Approved, Released and Obsolete, where an approval routing of named electronic signatories must complete before release. Deliverable sets are assembled as document structures and document packages, the latter reporting weighted average progress against milestones and connectable to a project activity. Technical data package and contract data requirements list are contract constructs rather than IFS objects: they are realised with document classes, approval routings, packages, and the Document Distribution Assistant whose distribution history is the delivery record.