Transcript
00:06
A change order, also known as an ECO, is a component of the change management process
00:11
that controls the release of new designs or changes to those designs.
00:16
The result and purpose of a change order is to release the designs, items, and files.
00:22
Throughout the change order's workflow, the change order details are defined,
00:26
and the changes are made to the affected items and files.
00:30
These changes are approved and then released.
00:33
Note that using a change order within Vault is not a requirement.
00:37
You can still change the lifecycle states of files and items manually outside of the change order process.
00:43
The change orders object's details, in its dialog box,
00:47
provide a record of the why, how, and when changes were made.
00:52
Change order details are captured in the Vault's Change Order dialog box.
00:57
Here is an example of a Change Order dialog box in Vault
01:00
which provides a record of the why, how, and when changes were made.
01:04
The General tab displays the change order's properties.
01:08
The Records tab displays the list of files and items associated with the change order.
01:13
The Comments tab contains the comments, attachments, and markups provided throughout the workflow.
01:20
The Files tab lists all the files attached to the change order.
01:24
And associated items are displayed in the associated items subtab.
01:29
The files can also be viewed from the Preview pane.
01:33
The Routing tab displays the routing list used to determine the user's roles
01:38
throughout the states of a change order workflow process.
01:42
And the Status tab shows, in yellow, the current lifecycle state of the change order.
01:48
The change order's creation and approval process starts with a change order being created,
01:53
either as a result of a new product design or from a change request initiated outside the Vault.
02:00
An individual with the role of change administrator
02:03
will assign the change order work to someone with the role of responsible engineer.
02:08
The responsible engineer's work will then be reviewed by reviewers and approvers.
02:14
The approvers will either approve the change order or reject it for rework or cancellation.
02:20
The state's shown of create, open, work, review, approved, and closed are the change order's states
02:28
as it progresses through the change order process.
02:32
The change order process just described aligns with the change order workflow built within Vault,
02:37
with the change order states previously mentioned.
02:40
This workflow cannot be changed,
02:42
except for a configuration of an added check state before the review state.
02:47
Note that this change order workflow is separate from the lifecycle states of files and items
02:53
that may have states, such as work in progress, for review, and released.
03:01
The change order object's details provides a record of the why, how, and when changes were made.
03:07
These change order details are captured in the Vault's Change Order dialog box
03:12
that can be accessed in the Preview pane, as shown here,
03:18
or by double clicking on the Change Order object.
03:22
Here is an example of a Change Order dialog box.
03:26
The General tab displays the properties of a change order.
03:29
Here, we have the change order number, the change order state,
03:34
the change order title, and detailed description.
03:37
These fields are filled in when the change order is created.
03:41
The Records tab displays the list of files or items associated with or affected by the change order.
03:48
The Comments tab contains the details of the change order's decisions
03:52
in the form of comments, attachments, and markups.
03:56
And then the Files tab lists all the files attached to the change order.
04:01
Any associated items are displayed in the associated items subtab,
04:05
and then the files can be displayed in the Viewer for review purposes, as shown here.
04:16
And moving along, the Routing tab displays the routing list used to control
04:20
which users are notified when a change order moves to a specific state.
04:24
The Status tab shows the current lifecycle state of the change order in yellow.
04:29
The current state here is Create, with the remaining states shown in blue.
00:06
A change order, also known as an ECO, is a component of the change management process
00:11
that controls the release of new designs or changes to those designs.
00:16
The result and purpose of a change order is to release the designs, items, and files.
00:22
Throughout the change order's workflow, the change order details are defined,
00:26
and the changes are made to the affected items and files.
00:30
These changes are approved and then released.
00:33
Note that using a change order within Vault is not a requirement.
00:37
You can still change the lifecycle states of files and items manually outside of the change order process.
00:43
The change orders object's details, in its dialog box,
00:47
provide a record of the why, how, and when changes were made.
00:52
Change order details are captured in the Vault's Change Order dialog box.
00:57
Here is an example of a Change Order dialog box in Vault
01:00
which provides a record of the why, how, and when changes were made.
01:04
The General tab displays the change order's properties.
01:08
The Records tab displays the list of files and items associated with the change order.
01:13
The Comments tab contains the comments, attachments, and markups provided throughout the workflow.
01:20
The Files tab lists all the files attached to the change order.
01:24
And associated items are displayed in the associated items subtab.
01:29
The files can also be viewed from the Preview pane.
01:33
The Routing tab displays the routing list used to determine the user's roles
01:38
throughout the states of a change order workflow process.
01:42
And the Status tab shows, in yellow, the current lifecycle state of the change order.
01:48
The change order's creation and approval process starts with a change order being created,
01:53
either as a result of a new product design or from a change request initiated outside the Vault.
02:00
An individual with the role of change administrator
02:03
will assign the change order work to someone with the role of responsible engineer.
02:08
The responsible engineer's work will then be reviewed by reviewers and approvers.
02:14
The approvers will either approve the change order or reject it for rework or cancellation.
02:20
The state's shown of create, open, work, review, approved, and closed are the change order's states
02:28
as it progresses through the change order process.
02:32
The change order process just described aligns with the change order workflow built within Vault,
02:37
with the change order states previously mentioned.
02:40
This workflow cannot be changed,
02:42
except for a configuration of an added check state before the review state.
02:47
Note that this change order workflow is separate from the lifecycle states of files and items
02:53
that may have states, such as work in progress, for review, and released.
03:01
The change order object's details provides a record of the why, how, and when changes were made.
03:07
These change order details are captured in the Vault's Change Order dialog box
03:12
that can be accessed in the Preview pane, as shown here,
03:18
or by double clicking on the Change Order object.
03:22
Here is an example of a Change Order dialog box.
03:26
The General tab displays the properties of a change order.
03:29
Here, we have the change order number, the change order state,
03:34
the change order title, and detailed description.
03:37
These fields are filled in when the change order is created.
03:41
The Records tab displays the list of files or items associated with or affected by the change order.
03:48
The Comments tab contains the details of the change order's decisions
03:52
in the form of comments, attachments, and markups.
03:56
And then the Files tab lists all the files attached to the change order.
04:01
Any associated items are displayed in the associated items subtab,
04:05
and then the files can be displayed in the Viewer for review purposes, as shown here.
04:16
And moving along, the Routing tab displays the routing list used to control
04:20
which users are notified when a change order moves to a specific state.
04:24
The Status tab shows the current lifecycle state of the change order in yellow.
04:29
The current state here is Create, with the remaining states shown in blue.
