4 CDR Workflow CapabilityCreate, Approve, Assign, Reassign, Return, Accept, Resolve and Close a CDRQuery & View CDRsTrack progress of a CDRCapture comments on a CDRnotifications sent to interested parties (Initiator, Reviewing Official, Assignee, & Back-ups)Provide Back-up capability for CDR participantsReminders are sent after defined periods due tonon–responseRecords audit/status information for entire processDriven by CDR RoleCDR role may be granted to government employees and support contractors with the Contract roleVendors can not obtain CDR roleThese are VERY High-level. Each one of these explodes into many detailed functional requirementsCDR Business Rules…

5 CDR Business RulesAuthorized users may Create, Approve, Assign, Reassign, Return, Accept, Resolve and Close a CDRGovernment users and Support Contractors must be granted the CDR rolesVendors have no access to CDRsDeficiencies are selected from a defined listDeficiency text may be addedIndependent relationship between CDR participants enforced (Exception - Reviewing Official can also act as the Assignee)All CDR participants must be EDA users (Initiator, Reviewing Official, & Assignee)CDRs require approval prior to assignment (by Reviewing Official)CDRs require assignment to either the ACO or PCO/Buyer as indicated on the contractDays aged begins after approval and stops at closeContract document is not required to be posted in EDA in order to create a CDRThese are VERY High-level. Each one of these explodes into many detailed functional requirementsCDR Participants…

6 CDR Participants and FunctionThe CDR Workflow process requires actions by the following participants:Initiator – The person who creates the CDR based on errors found within a contract. Typically this has been a DFAS contracting specialist, a DCMA quality assurance specialist or any financial personnel.Auto-CDR Initiator – The EDA user responsible for administering all auto-CDRs generated by the auto-CDR system and EDA for a specific C/S/A. Typically this person is the Initiator, responsible for reassigning CDRs/auto-CDRs, closing CDRs/auto-CDRs, and creating manual CDRs. All CDR notifications normally routed to the initiator will go to this user.Auto-CDR System – Interfacing system responsible for delivering the XML contract deficiency data used by EDA to generate Auto-CDRs for a specific C/S/A.Note: Auto-CDR System User, auto-CDR Administrator, auto-CDR Initiator and auto- CDR Reviewing Official must all belong to the same specific C/S/A.

7 CDR Participants and Function – Con’tThe CDR Workflow process requires actions by the following participants:Reviewing Official – The person responsible for approving CDRs that are created for a particular C/S/A. The reviewing official is in charge of validating the accuracy of the CDR. Typically this is a supervisor to the initiator.Auto-CDR Reviewing Official - The person responsible for validating and approving all the auto-CDRs generated by an auto-CDR system for a particular C/S/A.Assignee – The person responsible for resolving the deficiencies within a CDR. Typically this is an Admin Contracting Officer (ACO) or Procurement Contracting Officer (PCO/Buyer) related to the contract based on the contract’s Admin DoDAAC or Issue DoDAAC. The CDR POC of the CDR office (DoDAAC) may also be an assignee.

8 CDR Participants and Function – Con’tThe following participants monitor CDR activities and will intercedeas necessary:Primary CDR POC – The office’s primary CDR POC as defined in the C/S/A within EDA. CDR POCs may be assigned CDRs to resolve or delegate within office.Alternate CDR POC – The office’s alternate CDR POC as defined in the C/S/A within EDA. CDR POCs may be assigned CDRs to resolve or delegate within office.CDR POC (Mgmt Level) – CDR POC at the C/S/A Management Level. Typically this person acts as a backup to the CDR POC and receives notification of delinquent/escalated CDRs.CDR Administrator – Government user responsible for setting up the CDR structure and maintaining it overtime. This person is typically the DFAS executive/or appointee to EDA.Auto-CDR Administrator - Government users who administers the auto-CDR environment for a specific C/S/A. This person is responsible for setting up the auto-CDR Initiator and auto-CDR Reviewing Official for a specific C/S/A and maintaining them over time. (See EDA Users Guide for Auto-CDR C/S/A Setup instructions)In General, the CDR Flow…

12 Create Auto-CDRCreateAuto-CDRs are created by EDA from XML data sent from an interfacing auto-CDR System. As contract deficiencies are discovered , auto-CDR request are sent to EDA for data validation and auto-CDR creation.Note: Auto-CDR requests that fail validation will be recorded and returned to the auto-CDR system for correction by the system or the C/S/A designated auto-CDR administrator.EDA Generates an Auto-CDR:Routed to Auto-CDR Reviewing Official for approvalMust have the Auto-CDR reviewing official roleMust be in specific C/S/A office to approveApproved Auto-CDR enters the CDR Workflow in the ‘INITIATED’ state. Begins CDR Workflow & AuditNote: Auto-CDRs begin with ‘A’ and are viewable, queriable and processed like manual CDRs in the CDR Workflow.CreateACO/PCO are required to be users.Create Manual CDR…

13 Create Manual CDR Initiator creates a CDREnters Deficiency information into EDAEDA Pre-populates (if applicable)Selects & Finds AssigneeIndicated on contract (ACO or PCO/Buyer)Assignee must be an EDA user, have the PCO/Buyer, ACO or CDR roleSelects Reviewing OfficialMust be in initiator’s office to approveMust have the CDR reviewing official roleNote: Contract document is not required to be posted in EDA in order to create a CDR.Initiator options…ADDEDA saves & submits CDR,Notifies Reviewing Official for approval,Begins CDR Workflow & AuditCANCELNothing is kept, transaction is terminatedCreateACO/PCO are required to be users.Options to Add a CDR…

19 Find a PCO/Buyer by DoDAAC/OfficeCreateEDA displays PCO/Buyer users and CDR POCs (Primary/Alternate) for the entered ISSUE DoDAAC.SelectAssignee“FIND” is based on the ISSUE DoDAACPre-populated from entry screenThis “Find Assignee” option utilizing the DoDAAC is RecommendedEDA references and displays assignee candidates for CDR assignment based on C/S/A DoDAAC offices/organizations as defined by the communities and user roles. Each C/S/A defines/establishes how best to assign within their organizations.CDR Orgs are associated with DoDAACs and have a Primary and Alternate CDR POCs responsible to resolve CDRs. Users obtain ACO or PCO/Buyer roles from their EDA POCs“Find Assignee” Options…

21 “Find Assignee” by C/S/ACreateEDA displays Users with the proper role (PCO/Buyer or ACO) and CDR Orgs CDR POCs for the selected C/S/A.SelectAssigneeOnce Assignee selected, information will pre-populate the form (as shown)Find Assignee by Name…

22 “Find Assignee” by NameCreateName search returns users with the ACO or PCO/Buyer role that matches the entered name criteria.Click “Switch to Name Search”Enter Name CriteriaLAST, FIRSTFull or Partial EntryClick “List Users by Name”SelectAssigneeEDA displays Users with the proper role (PCO/Buyer or ACO) and CDR POCs for entered name criteria.Office/DoDAAC is not used in this search.Find ACO by DoDAAC…

23 Find a ACO by DoDAAC/OfficeCreateEDA displays ACO users and CDR POCs (Primary/Alternate) for the entered ADMIN DoDAAC.SelectAssignee“FIND” is based on the ADMIN DoDAACPre-populated from entry screenThis “Find Assignee” option utilizing the DoDAAC is RecommendedEDA references and displays assignee candidates for CDR assignment based on C/S/A DoDAAC offices/organizations as defined by the communities and user roles. Each C/S/A defines/establishes how best to assign within their organizations.CDR Orgs are associated with DoDAACs and have a Primary and Alternate CDR POCs responsible to resolve CDRs. Users obtain ACO or PCO/Buyer roles from their EDA POC.Find DCMA ACO…

24 Find an ACO in DCMA CreateDCMA offers a look-up tool for identification of the DCMA ACOs. Use DCMA’s eTool – Contract Management Team (CMT) to identify the CURRENT ACO for CDR assignmentClick “Find in DCMA”to Identify ACOSearch by…Contract NumberCAGEDoDAACOr RoleTake Identified ACO Name & Search EDA by Name…

25 Find a DCMA ACO by DoDAAC/OfficeCreateDCMA DoDAAC starts with ‘S’ and ends in ‘A’EDA recognizes a DCMA DoDAAC and offers a “Office” SearchEnter DCMA ACO Name identified by DCMASelectAssigneeComplete Assignment…

26 Assignment Complete CreateOnce Assignee is selected from one of the “Find Assignee” options, the information is pre-populated on the CDR entry form to continue the entry process.Select Reviewing Official…

27 Reviewing Official SelectionCreateFind CDR Reviewing Official …EDA will only display valid users with the EDA “Reviewing Official” (RO) Role within the initiator’s C/S/A for selectionACO/PCO are required to be users.Click drop-downto select the Reviewing OfficialDocument Deficiencies…

30 Deficiency CustomizationCreateSelected Deficiency Customization…After Selecting Deficiencies,Additional text may be inserted to further clarifyAdded DepartmentACO/PCO are required to be users.Added Fax numberModification Capabilities

31 Notification is sent to Reviewing OfficialCreate CDR - continuedCreateCompleted Form…ACO/PCO are required to be users.Notification is sent to Reviewing OfficialApproval Notification…Click “Add CDR…”

32 Approval NotificationApproveSUBJECT: New CDR Control #G409:FA…sent to the Reviewing OfficialNext Actions -Approve or ReturnDirect links to CDRIdentifies INITIATOR & addressACO/PCO are required to be users.EDA User GuideCDR ProcessEDA Help DeskContact informationApproval Reminder…

33 Approval Reminder Approve …sent to the Reviewing Official View CDR… RFrom: CDR AdministratorSent: Fri 8/21/ :44 PMTo: <Reviewing Official>CC: <Initiator>Subject: Reminder <x> - New CDR Control # : GS1518Importance: HighThis message was system generated. Please DO NOT REPLY to this .<Reviewing Official >,This is a reminder that Contract Deficiency Report #G1518:1 has been awaiting approval for <y> days. If you do not take action on this CDR within <y> days (by 08/24/2008) as described below, then another reminder will be sent. You may view and take action on this CDR within EDA by clicking one of the links below:Username/Password access: https://ushrsebs004.disa.usgs.eds.com:643/pls/user/cdr.display?pControl=G1518 Certificate/CAC access: https://ushrsebs004.disa.usgs.eds.com/pls/cert/cdr.display?pControl=G1518Once in EDA you may:* Approve the CDR for resolution processing or* Return the CDR to the initiator.If you have trouble approving or rejecting this CDR then you may contact another reviewing official within your organization to process this CDR. Contact your EDA POC for assistance in locating another reviewing official. For ASSISTANCE regarding this CDR, please contact Bandit Warner, the initiator of the CDR atPlease refer to the EDA User's Guide for guidance on the CDR process.https://ushrsebs004.disa.usgs.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: , or DSN: , or by at (Subject: EDA Assistance).…sent to the Reviewing OfficialSUBJECT: Reminder <x> New CDR Control # : GS07F0341MDirect links to CDRApproval Reminders:Every ‘3’ DaysIncrements CountView CDR…Indicates elapsed durationACO/PCO are required to be users.Next Actions -Approve or Return

34 View CDR View Click “Add Comment…” or “View History”Adding comments is restricted to theCDR Participants/BackupsNo Modifications may occur on the CDRACO/PCO are required to be users.Links to view participant contact information

39 Reject CDRApproveRRejectReviewing Official reviews CDR and if invalid/incorrect, Rejects it to return it to the Initiator.EDA Notifies Initiator of rejectionInitiator can…REASSIGNCLOSEEDA:Updates CDRCaptures CommentsContinues Workflow/AuditReminds Initiator and Backups (as necessary)Initiator may reassign or start-over with Contract Deficiency entry process and approval if changes are required.Reject

41 Reject Reminder Reject …sent to the Initiator Let’s APPROVE the CDR… RFrom: CDR AdministratorSent: <Date sent>To: <Initiator>CC: <Reviewing Official>Subject: Reminder <x> - Returned CDR Control # G1523:1Importance: HighThis message was system generated. Please DO NOT REPLY to this<Initiator >,This is a reminder that Contract Deficiency Report #G1523:1 has been awaiting review for<3> days. This CDR has been returned to you by Dude A Big Dog. A comment explaining the reason for the return is attached to the CDR. You may view and take action on this CDR within EDA by clicking one of the links below:Username/Password access: https://ushrsebs004.disa.usgs.eds.com:643/pls/user/cdr.display?pControl=G1523Certificate/CAC access: https://ushrsebs004.disa.usgs.eds.com:443/pls/cert/cdr.display?pControl=G1523Once in EDA you may:* Reassign the CDR and resubmit it for approval or* Close the CDR if it was created in error.Please refer to the EDA User's Guide for guidance on the CDR process.https://ushrsebs004.disa.usgs.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: , or DSN: , or by at (Subject: EDA Assistance).…sent to the InitiatorIncrements CountReject Reminders:Every ‘3’ DaysIndicates elapsed durationNext Actions -Reassign or CloseDirect links to CDRLet’s APPROVE the CDR…

42 No Modifications may occur on the CDR.Approve CDRApproveReviewing Official May…Approve orRejectClick “Approve…” or“Reject…”No Modifications may occur on the CDR.

43 Approving CDRApproveClick “Confirm Approval…”Enter a commentUpon approval by the Reviewing Official, the CDR is sent to the Assignee.In this example, the CDR is sent/routed to the ACO Identified.Assignment Notification…

44 Assignment NotificationAssigned CDR Control #G1523:1…sent to the AssigneeThis message was system generated. Please DO NOT REPLY to this<Assignee >,Contract Deficiency Report #G1523:1 has been assigned to you for resolution In order to prevent delays in paying contractor invoices, it is imperative that you take action on this CDR within 3 days (by 08/24/2008) as described below.You may view and take action on this CDR within EDA by clicking one of the links below:Username/Password access :https://ushrsebs004.disa.usgs.eds.com:643/pls/user/cdr.display?pControl=G1523Certificate/CAC access: https://ushrsebs004.disa.usgs.eds.com:443/pls/cert/cdr.display?pControl=G1523Once in EDA you may:* accept the CDR to indicate you are working to resolve it* reassign it to the appropriate ACO or PCO/Buyer, or CDR POC* return it to the initiator indicating it was assigned to the wrong person* or resolve the CDR.For ASSISTANCE regarding this CDR, please contact Bandit Warner, the initiator of the CDR atPlease refer to the EDA User's Guide for guidance on the CDR process.https://ushrsebs004.disa.usgs.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: , or DSN: , or by at (Subject: EDA Assistance).Direct links to CDRNext Actions - Accept, Reassign,Return or ResolveACO/PCO are required to be users.Identifies INITIATOR & addressEDA User GuideCDR ProcessIf ASSIGNED to PCO/Buyer, ACO is cc’d.Assignment Reminder…

45 First Assignment ReminderFrom: CDR AdministratorSent: Fri 11/10/ :44 PMTo: <Assignee>Cc: <CDR POC>, <Alt CDR POC>, <Initiator>Subject: Reminder 1 - Assigned CDR Control # G1519:1Importance: High<Assignee>,This is a reminder that Contract Deficiency Report #G1519:1 has been assigned to you for resolution and has been waiting for action by you for 3 days. If you do not take action on this CDR within 7 days (by 08/28/2008) as described below, then the next notification will escalate to your manager. You may view and take action on this CDR within EDA by clicking one of the links below:Username/Password access: https://ushrsebs004.disa.usgs.eds.com:643/pls/user/cdr.display?pControl=G1519Certificate/CAC access: https://ushrsebs004.disa.usgs.eds.com:443/pls/cert/cdr.display?pControl=G1519Once in EDA you may:* accept the CDR to indicate you are working to resolve it* reassign it to the appropriate ACO, PCO/Buyer, or CDR POC* return it to the initiator indicating it was assigned to the wrong person* or resolve the CDR.For ASSISTANCE regarding this CDR, please contact Bandit Warner, the initiator of the CDR atPlease refer to the EDA User's Guide for guidance on the CDR process.https://ushrsebs004.disa.usgs.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: , or DSN: , or by at (Subject: EDA Assistance).…sent to the AssigneeCc’s CDR POCsBased on C/S/A structureIncrements CountIndicates date of escalationDirect links to CDRNext Actions - Accept, Reassign, Return or ResolveACO/PCO are required to be users.Identifies INITIATOR& addressEDA User GuideCDR ProcessFirst Assignment Reminder:‘3’ DaysSubsequent Assignment Reminder…

46 Subsequent Assignment Reminder:Subsequent ReminderRAssignReminder <x> Assigned CDR Control #G1519:1…sent to the AssigneeFrom: CDR AdministratorSent: Fri 10/15/ :44 PMTo: <Assignee>Cc: <CDR POC>, <Alt CDR POC>, <Mgmt Lvl CDR POC>, <Initiator>Subject: Reminder <2> - Assigned CDR Control # : G1519:1Importance: HighThis message was system generated. Please DO NOT REPLY to this .<Assignee>,This is a reminder that Contract Deficiency Report #G1519:1 has been assigned to you for resolution and has been waiting for action by you for 10 days If you do not take action on this CDR within 7 days (by 08/28/2008) as described below, then another reminder will be sent. You may view and take action on this CDR within EDA by clicking one of the links below:Username/Password access: https://ushrsebs004.disa.usgs.eds.com:643/pls/user/cdr.display?pControl=G1519Certificate/CAC access: https://ushrsebs004.disa.usgs.eds.com:443/pls/cert/cdr.display?pControl=G1519Once in EDA you may:* accept the CDR to indicate you are working to resolve it* reassign it to the appropriate ACO, PCO/Buyer, or CDR POC* return it to the initiator indicating it was assigned to the wrong person* or resolve the CDR.For ASSISTANCE regarding this CDR, please contact Bandit Warner, the initiator of the CDR atPlease refer to the EDA User's Guide for guidance on the CDR process.https://ushrsebs004.disa.usgs.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: , or DSN: , or by at (Subject: EDA Assistance).cc’s CDR POCs & Mgmt Lvl CDR POCs based on C/S/A structureIncrements CountIndicates elapseddurationIndicates dateof escalationDirect Links to CDRACO/PCO are required to be users.Next Actions - Accept,Reassign, Return orResolveIdentifies INITIATOR& addressEDA User GuideCDR ProcessQuick look at History…Subsequent Assignment Reminder:Every ‘7’ Days

47 History of CDR View Next Action…Assignee’s Status ChangeACO/PCO are required to be users.Responsible forNext ActionCaptured information:Date/TimeActioned byEventCommentsNext Action…Assignee’s

51 Return Notification …sent to the Initiator Return Return Reminder…Return CDR Control #G1523:1…sent to the InitiatorFrom: CDR AdministratorSent: Fri 11/5/ :44 PMTo: <Initiator>Cc: <Assignee> <CDR POC> <Alt CDR POC>Subject: Returned CDR # G1523:1<Initiator>,This message was system generated. Please DO NOT REPLY to this .Bandit Warner,Contract Deficiency Report #G1523:1 is awaiting your review before it can be assigned for resolution. This CDR has been returned to you by Dude A Big Dog. A comment explaining the reason for the return is attached to the CDR You may view and take action on this CDR within EDA by clicking one of the links below:Username/Password access: https://ushrsebs004.disa.usgs.eds.com:643/pls/user/cdr.display?pControl=G1523Certificate/CAC access: https://ushrsebs004.disa.usgs.eds.com:443/pls/cert/cdr.display?pControl=G1523Once in EDA you may:* Reassign the CDR and resubmit it for approval or* Close the CDR if it was created in error.Please refer to the EDA User's Guide for guidance on the CDR process.https://ushrsebs004.disa.usgs.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: , or DSN: , or by at (Subject: EDA Assistance).Identifies who returnedACO/PCO are required to be users.Next ActionsReassign or CloseDirect links to CDRRequiring ActionUser Guide LinkReturn Reminder…

52 Return Reminder Return …sent to the Initiator Let’s REASSIGN the CDR…Reminder <x> Return CDR Control #G1523:1…sent to the InitiatorFrom: CDR AdministratorSent: Fri 10/5/ :44 PMTo: <Initiator>Cc: <Reviewing Official> <Assignee> <CDR POC> <Alt CDR POC>Subject: Reminder <x> Returned CDR # 65672: GS07F0341MImportance: High<Initiator>,This message was system generated. Please DO NOT REPLY to this .Bandit Warner,This is a reminder that Contract Deficiency Report #G1523:1 has been awaiting review for 3 days. This CDR has been returned to you by Dude A Big Dog. A comment explaining the reason for the return is attached to the CDR. You may view and take action on this CDR within EDA by clicking one of the links below:Username/Password access: https://ushrsebs004.disa.usgs.eds.com:643/pls/user/cdr.display?pControl=G1523Certificate/CAC access: https://ushrsebs004.disa.usgs.eds.com:443/pls/cert/cdr.display?pControl=G1523Once in EDA you may:* Reassign the CDR and resubmit it for approval or* Close the CDR if it was created in error.Please refer to the EDA User's Guide for guidance on the CDR process.https://ushrsebs004.disa.usgs.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: , or DSN: , or by at (Subject: EDA Assistance).cc’s CDR POCs & MgtLvl CDR POCsIncrements CountACO/PCO are required to be users.Direct Linksto CDRNext ActionsReassign, CloseEDA User GuideCDR ProcessLet’s REASSIGN the CDR…Return Reminder:Every ‘3’ Days

53 Reassign CDR REASSIGN…Reassign CDR to another ASSIGNEE who will be responsible for resolving the stated deficiency.Click “Reassign…”Days aged clock continuesNew Assignment…

55 Reassign Business RulesCDR ReassignAssignee (ACO or PCO/Buyer), Reviewing Official & Initiator can REASSIGNAssignee or Reviewing Official can RETURN…comment requiredFind Assignee to include search capability into the current C/S/A structure and also indicates Primary CDR POC and Alternate CDR POC capacity within Office.Carbon Copy ACO when PCO/Buyer is assigned a CDRReassign a RESOLVED CDR to a new person requires Approval by Reviewing OfficialACOs and PCO/Buyers should reassign the CDR to an individual user within their Office. Requires no approval. (Delegation)CDRs reassigned to CDR POCs will trigger a notification to the optional group .Activity is captured in audit trailAssignment Notification…

56 Assignment NotificationAssigned CDR Control #G1521:1…sent to the AssigneeThis message was system generated. Please DO NOT REPLY to this .Shelby A Puppydog,Contract Deficiency Report #G1521:1 has been assigned to you for resolution In order to prevent delays in paying contractor invoices, it is imperative that you take action on this CDR within 3 days (by 08/24/2008) as described below.You may view and take action on this CDR within EDA by clicking one of the links below:Username/Password access: https://ushrsebs004.disa.usgs.eds.com:643/pls/user/cdr.display?pControl=G1521Certificate/CAC access: https://ushrsebs004.disa.usgs.eds.com:443/pls/cert/cdr.display?pControl=G1521Once in EDA you may:* accept the CDR to indicate you are working to resolve it* reassign it to the appropriate ACO or PCO/Buyer, or CDR POC* return it to the initiator indicating it was assigned to the wrong person* or resolve the CDR.For ASSISTANCE regarding this CDR, please contact Bandit Warner, the initiator of the CDR atPlease refer to the EDA User's Guide for guidance on the CDR process.https://ushrsebs004.disa.usgs.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: , or DSN: , or by at (Subject: EDA Assistance).Direct Linksto CDRNext Actions - Accept, Reassign,Return or ResolveACO/PCO are required to be users.INITIATOR &addressEDA User GuideCDR ProcessIf ASSIGNED to PCO/ Buyer, ACO is cc’d.Assignment Reminder…EDA Help DeskContact information

57 First Assignment Reminder…sent to the AssigneeFrom: CDR AdministratorSent: Fri 11/5/ :44 PMTo: <Assignee>Cc: <Primary CDR POC>, <Alt. CDR POC>, <Initiator>Subject: Reminder 1 - Assigned CDR Control # : FA860704DImportance: High<Assignee>,This message was system generated. Please DO NOT REPLY to this .This is a reminder that Contract Deficiency Report #G1519:1 has been assigned to you for resolution and has been waiting for action by you for 3 days. If you do not take action on this CDR within 7 days (by 08/28/2008) as described below, then the next notification will escalate to your manager. You may view and take action on this CDR within EDA by clicking one of the links below:Username/Password access: https://ushrsebs004.disa.usgs.eds.com:643/pls/user/cdr.display?pControl=G1519Certificate/CAC access: https://ushrsebs004.disa.usgs.eds.com:443/pls/cert/cdr.display?pControl=G1519Once in EDA you may:* accept the CDR to indicate you are working to resolve it* reassign it to the appropriate ACO, PCO/Buyer, or CDR POC* return it to the initiator indicating it was assigned to the wrong person* or resolve the CDR.For ASSISTANCE regarding this CDR, please contact Bandit Warner, the initiator of the CDR atPlease refer to the EDA User's Guide for guidance on the CDR process.https://ushrsebs004.disa.usgs.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: , or DSN: , or by at (Subject: EDA Assistance).cc’s CDR POCsBased on C/S/A structureIncrements CountIndicates date of escalationDirect Links to CDRACO/PCO are required to be users.Next Actions - Accept,Reassign, Return or ResolveIdentifies INITIATOR & addressEDA User GuideCDR ProcessSubsequent Assignment Reminder…First Assignment Reminder:‘3’ Days

58 Subsequent Reminder Assign …sent to the Assignee Let’s ACCEPT the CDR…Reminder <x> Assigned CDR Control #G1519:1…sent to the AssigneeFrom: CDR AdministratorSent: Fri 11/5/ :44 PMTo: <Assignee>Cc: <Primary CDR POC>, <Alt. CDR POC>, <Mgmt Lvl CDR POC>, <Initiator>Subject: Reminder <x> - Assigned CDR Control # G1519:1Importance: HighThis message was system generated. Please DO NOT REPLY to this .<Assignee>,This is a reminder that Contract Deficiency Report #G1519:1 has been assigned to you for resolution and has been waiting for action by you for 10 days If you do not take action on this CDR within 7 days (by 08/28/2008) as described below, then another reminder will be sent. You may view and take action on this CDR within EDA by clicking one of the links below:Username/Password access: https://ushrsebs004.disa.usgs.eds.com:643/pls/user/cdr.display?pControl=G1519Certificate/CAC access: https://ushrsebs004.disa.usgs.eds.com:443/pls/cert/cdr.display?pControl=G1519Once in EDA you may:* accept the CDR to indicate you are working to resolve it* reassign it to the appropriate ACO, PCO/Buyer, or CDR POC* return it to the initiator indicating it was assigned to the wrong person* or resolve the CDR.For ASSISTANCE regarding this CDR, please contact Bandit Warner, the initiator of the CDR atPlease refer to the EDA User's Guide for guidance on the CDR process.https://ushrsebs004.disa.usgs.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: , or DSN: , or by at (Subject: EDA Assistance).cc’s CDR POCs & MgmtLevel CDR POCsBased on C/S/A structureIncrements CountIndicates dateof escalationIndicates elapseddurationDirect Links to CDRACO/PCO are required to be users.Next Actions - Accept,Reassign, Return or ResolveIdentifies INITIATOR & addressEDA User Guide CDR ProcessLet’s ACCEPT the CDR…Subsequent Assignment Reminder:Every ‘7’ Days

62 Accept Reminder Accept Quick look at History… R …sent to the AssigneeAccept Reminder <x> CDR Control #G…sent to the AssigneeThis message was system generated. Please DO NOT REPLY to this .<Assignee>,This is a reminder that Contract Deficiency Report #G435:4-123 has been accepted by you and has been waiting for action by you for 15 days. If you do not take action on this CDR within 15 days (by 12/02/2006) as described below, then another reminder will be sent. You may view and take action on this CDR within EDA by clicking one of the links below:Username/Password access: https://ushrsebs004.vahrn.us.eds.com:643/pls/user/cdr.display?pControl=G435Certificate/CAC access:Once in EDA you may:* Resolve the CDR to indicate that you have reached a resolution.* Reassign it to the appropriate ACO or PCO/Buyer (or responsible Contract Specialist if applicable).For ASSISTANCE regarding this CDR, please contact Army Armyinit, the initiator of the CDR atPlease refer to the EDA User's Guide for guidance on the CDR process.https://ushrsebs004.vahrn.us.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: , or DSN: , or by (Subject: EDA Assistance).cc’s CDR POCs & MgmtLevel CDR POCsBased on C/S/A structureDirect links to CDRRequiring ActionValidNext ActionsReassign orResolveResolve w/commentACO/PCO are required to be users.User GuideLinkAccept Reminder:Every ‘15’ DaysQuick look at History…

71 Resolve Reminder Resolve …sent to Initiator Close CDR… R User GuideResolved Reminder <x> CDR Control #G1524:1From: CDR AdministratorSent: Fri 11/5/ :44 PMTo: <Initiator>Cc: <Assignee> <Primary CDR POC>>, <Alt CDR POC>Subject: Resolved CDR # G1524:1This message was system generated. Please DO NOT REPLY to this .<Initiator>,This is a reminder that Contract Deficiency Report #G1524:1 has been resolved and has been awaiting review for 3 days. Your review is required in order to close this CDR. A comment detailing the resolution is attached to the CDR. You may view and take action on this CDR within EDA by clicking one of the links below:Username/Password access: https://ushrsebs004.disa.usgs.eds.com:643/pls/user/cdr.display?pControl=G1524Certificate/CAC access: https://ushrsebs004.disa.usgs.eds.com:443/pls/cert/cdr.display?pControl=G1524Once in EDA you may:* Reassign the CDR for further resolution processing or* Close the CDR indicating it is complete.Please refer to the EDA User's Guide for guidance on the CDR process.https://ushrsebs004.disa.usgs.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: , or DSN: , or by at (Subject: EDA Assistance).…sent to InitiatorDirect Linksto CDRACO/PCO are required to be users.Next ActionsReassignCloseUser GuideLink to CDR ProcessResolve Reminder:Every ‘3’ DaysClose CDR…

73 Click “Close…” or “Return…”Close CDR OptionsCloseInitiator Reviews ResolutionClick “Close…” or “Return…”or “Reassign…”RETURN…Return original CDR to the SAME ASSIGNEE.No additional approvalREASSIGN…Reassign original CDR to the a DIFFERENT ASSIGNEE. Approval requiredCLOSE…CDR resolved. Indicate closures. The deficiency life ends.RETURN…

74 Click “Confirm Return…”Return CDRReturnClick “Return…”Click “Confirm Return…”Enter a commentRETURN…Return original CDR to the SAME ASSIGNEE.(No changes or new deficiencies can be added)No Additional approval is requiredReturn Notification…

75 Return Notification Return …sent to Assignee REASSIGN CDR…Return CDR Control #G409:FA…sent to AssigneeFrom: CDR AdministratorSent: Fri 3/5/ :44 PMTo: <Assignee>Cc: <Initiator>, <Primary CDR POC>, <Alt CDR POC>Subject: Returned CDR # 65672: W91YTV0<Initiator>,Contract Deficiency Report # 65672: W91YTV0 has been assigned to you for resolution. This CDR has been returned to you by <Initiator>. A comment explaining the reason for the return is attached to the CDR.You may view this CDR within EDA by clicking on one of the links below:Username/Password access: https://eda2.ogden.disa.mil/pls/user/cdr.display_cdr?control=65672Certificate/CAC access: https://eda2.ogden.disa.mil/pls/cert/cdr.display_cdr?control=65672Once in EDA you may- reassign the CDR and resubmit it for approval or- Resolve the CDR.Please refer to the EDA Users guide for guidance on the CDR process. https://ushrsebs004.vahrn.us.eds.com:643/users_guide/documents/cdr/cdr001_Index.htmlFor all other inquiries, please contact the EDA Help Desk at: (866) , (801) or DSN: , or with at: (EDA Assistance).Identifies who returnedDirect Links to CDREDA User GuideCDR ProcessNext ActionsReassignResolveREASSIGN CDR…

76 Reassign CDR Additional approval is required.Click “Reassign…”REASSIGN…Reassign original CDR to the a DIFFERENT ASSIGNEE.(No changes or new deficiencies can be added)Additional approval is required.CDR is sent to Reviewing Official for approval of new assignment.REASSIGN CDR…

80 History of CDR View At this point, the deficiency life ends.StatusChangeNONext ActionClosed CDRs continue to be viewable.Closed CDRs are not deleted.Note: Closed unapproved CDRs are deleted.(You may wish to use Advanced Search to exclude close CDR)Captured information:Date/TimeActioned byEventCommentsLet’s look at CDR Query…

84 No Modifications may occur on the CDRView CDRViewClick “View History”No Modifications may occur on the CDRACO/PCO are required to be users.CDR Query Result Set…

85 CDR Query Result View CDR Query Result Page…Sample shownDisplays available CDR informationDownloadResultSetAdda specificCDRInformation on size of query and PageSort on ColumnGeneral CapabilitiesACO/PCO are required to be users.Note: Sort on column is only available if results fit on one page.

86 CDR Query Result View CDR Query Result Page…Sample shownDisplays available CDR informationLinkto theContractCDRHistoryCDR - Unique Control NumberACO/PCO are required to be users.Extra Help and Documentation…