ECO process and roles
- 07 Nov 2022
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
ECO process and roles
- Updated on 07 Nov 2022
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Roles control access rights to information Sovelia.
Some parts of the interface are also role based. For example, creation functions are not visible to viewers and workflow charts only visible to the relevant roles.
The following roles are setup in the Sovelia Template for Engineering change orders:
Role | Description | Access rights |
|---|---|---|
Change initiator | Create ECOs and assign them to designers. Often this role is combined with Change designer. Also, at least a product data viewer role is required to give visibility to product data. | Create ECOs and promote them to status Assigned. View ECOs at all states. |
Change designer | Edit ECOs and link changed product data. Complete the ECO to forward it to approval. | The Designer role is required to carry out the changes to product data. Edit ECO information at status Assigned. Promote to Completed. View ECOs at all states. |
Change approver | Approve the ECO to status Approved. The Production approver role is also required as related product data must be approved to In production first. | Edit ECO information as status Completed. Promote ECO to status Approved. Demote to Assigned. View ECOs at all states. |
Change releaser | Release the ECO to inform relevant parties of the change. | Edit ECO information as status Approved. Promote ECO to Released and Closed. |
| Viewer - Change orders | View ECOs. | View ECOs at all states. |
| Viewer Released - Change orders | View released ECOs. | View ECOs at status Released. |
The following chart described the ECO process:
Was this article helpful?