Projects

  Table of Contents

• Permissions
• Defining and Executing Project Work
• Reusing Released Procedures
• Converting a Project to a Procedure

A project is a one-off execution that does not require a released procedure. Projects are useful for prototypes, experimental builds, corrective work, and other tasks whose process must develop while the work is underway.

Unlike a work order, a project can begin without completing the procedure review and release process. Use a procedure and work order when the process is repeatable and requires revision-controlled instructions.

Projects are both editable like a procedure and actionable like a work order. For example definition blocks like part requirements are both alterable and fulfillable.

Permissions

Projects allow work to proceed without an approved procedure, so access is controlled by dedicated permissions. An organization can limit who may create or execute projects or disable projects entirely.

Defining and Executing Project Work

A project combines process definition and execution in one place. It supports the same kinds of definition blocks used by procedure steps, along with comments, task ownership, queues, scheduling, timeline planning, and a Kanban view.

This allows a team to add or refine work as a prototype develops while retaining an execution record of the tasks performed.

Reusing Released Procedures

A project may embed a released procedure when part of the work already has a controlled process. The embedded work uses the released procedure while the surrounding project remains flexible.

Converting a Project to a Procedure

Select the conversion action on the project overview to create a draft procedure from the project. The resulting draft follows the standard review and approval process before it can become the default for new work orders.