A Customer Specific Requirement has 6 main phases which are as follows:
| Registration | Prompt logging of a Customer Specific Request after reception and Submitting it for pre-Approval |
|---|
| Pending Pre-Approval | Rules for the Approval process have been implemented by each GBU where a CSR can be automatically approved, be assigned to a User to approve or rejected, or be assigned to a group of Users. |
|---|
| Assessment | After the CSR is pre-approved, it is assigned to a User or a group of Users to be assessed. Depending on the type of Requirement, different assessments may need to be performed (Analytical, Industrial, Supply-Chain). Once the assessment is complete the user must provide a Global Feasibility Conclusion. |
|---|
| Approval Pending | Rules for the Approval process have been implemented by each GBU where a CSR can be automatically approved, be assigned to a User to approve or rejected, or be assigned to a group of Users. |
|---|
| Under Implementation | Ater (final) Approval, the Customer Specific Requirement implementation is tracked. |
|---|
| Active | Once the implementation is complete, a Customer Specific Requirement becomes (and stays) Active, until it is no longer relevant and can be deactivated. |
|---|
