on - edited on by
VIVEK - vkulanda
Previous Article
Once your Deliverable document has been reviewed by peers and you have uploaded a final version with the consolidated feedback collected during the review, it is time to initiate an Approval Request.
Only Deliverable documents need to be approved. Other document types, such as Support Material, or Reference material do not require an approval. Contractual documents, if requiring approval are handled through other means. A Milestone Completion Certificate (MCC) approval by your customer representative can also be handled through DCP but this is submitted via the MCC submission capability in the Delivery Management functional area.
A Deliverable document is a document created per the scope defined in the contractual agreement (e.g. low-level design, security report, design recommendation, …).
Make sure to be acquainted with the Advanced services policies and processes, especially the AS Deliverables Review and Storage Process.
Only the Author of the document can submit a document for approval. An Owner of the document (acting as a proxy for the author) can also submit a document for approval.
The document needs to be in the Draft state before the 'Submit for Approval' action becomes enabled.
An approval consists of 2 steps:
All deliverable documents have to go through 2 steps:
- Internal approval: The internal approval should be done by a Cisco employee (or contractor working on behalf of Cisco -red badge-) that is deemed having authority or responsibility on the overall customer engagement (the project) and is in accordance with the current organizational policies and procedures. As a minimum 1 person should approve internally. It is possible to have more than 1 approve the document.
Documents that are machine-created such as stability audit reports ... and that do not have significant manual input, can skip step 1 - the internal approval - and can go directly to step 2 - the customer acceptance -. - Customer acceptance: The customer acceptance should be done by a Customer representative. The person will accept the document on behalf of the customer company. This is your evidence that the deliverable was completed and delivered per the contractual agreement. Same here: it is possible to have more than 1 customer representative invited to accept the deliverable document. Please note that for the customer's ID to be added to the approval request, a valid CCO ID for that customer contact person needs to exist in the CPR tool. The URL for CPR tool is listed at the bottom of the Visibility tab of the content.
To submit a document for approval, select the document from the table grid by checking the check-box on the left-end of the record-line and click on the 'submit for approval' 
action in the action pane on the right-end of the table-grid. This will open the 'Request approval/acceptance' pane.
Select your invitees with the user selection component that allows you to either search or select from your aggregated contact list and/or contact-groups. A detailed explanation of the user selection component is provided in Updating Extended Properties via Properties Pane.
At any time during the approval process you can change the invitee list as long as they have not yet submitted their vote.
Note: You can invite both at the same time: the Cisco representative that will approve your deliverable document internally in step 1 and the customer representative that is going to accept the document on behalf of the customer in step 2. If you do so, the DCP system will first send an invitation to the Cisco representative and only when the document is (fully) approved internally, only then an invitation will be send to the customer representative.
Alternatively you can just invite the Cisco representatives for step 1: the internal approval, then initiate the approval and when the document is internally approved you can then add the customer representatives to continue with step 2: the customer acceptance.
If you only add Customer representatives, without Cisco representatives, when you 'Submit' for approval, the approval process will skip step 1 and go directly to step 2: Customer acceptance.
Choose a date to give sufficient time to the approvers to provide their vote. The 'Approve by' date is the last day that all invited approvers can submit their vote. After that date, the 'vote' buttons will be disabled.
At any time during the approval you can change the date to a later date if needed.
You can provide an extra comment. This is optional. This comment will be visible to the invitees.
Click 'Submit' to initiate the approval process. Once submitted DCP will send an action request email to first the internal Cisco invitees. When fully approved internally, DCP will send the action request email to the external customer invitees.
Related articles :
Table of Content
Previous Article