12A IDV Type 12B Award Type Components shall also review the following two data elements to address high-priority DoD data items: 6E Multiple or Single Award IDC 8K EPA-Designated Product(s) 8L Recovered Material Clauses 10M Solicitation Procedures Step 5: Perform root-cause analysis and document the field as inaccurate. If the field is found to be inaccurate or inappropriately incomplete (based on the definitions outlined in Step 1 and provided in Exhibit B), perform root cause analysis, including the contracting officer for the action (as appropriate). When the root cause has been determined, the error shall be documented with the appropriate root cause (listed in Exhibit B [DOCUMENT LINK]) and a corrective action plan shall be provided where the target goal is not achieved and a routine schedule for addressing any repetitive errors. Corrective actions should attempt to address the root cause of the error in order to minimize the possibility of the error to reoccur; just the immediate fix of a data error. not Corrective Actions might include, but are not limited to: Improving core processes, to include improvements in collecting the source data in the contract writing system Recommendations for alterations to the validation rules contained within the contract writing system or FPDS or interfaces between each system Required Policy Training / Awareness Performance Metrics for Contracting Offices It is noted that some of the required data elements to be reviewed are completed in FPDS CARs by FPDS itself based on information from other authoritative sources (e.g., CCR or previous CARs submitted by other contracting offices). Associated errors found during Procurement Data V&V should be highlighted in the reports submitted to DPAP/PDI, as well as reported to the FPDS Helpdesk as soon as possible (as necessary) to affect their correction. Upon documentation of the (1) error, (2) root cause of Step 6: Correct errors. inaccuracy, and (3) corrective action plan, perform the correction actions to the CARs with errors using the FPDS system privilege. If not correcting a systemic “CORRECT” error across the Component or Department, these corrections should be accomplished as in the hierarchy of organizations / offices as the CORRECT privilege “low” Component’s
12A IDV Type 12B Award Type Components shall also review the following two data elements to address high-priority DoD data items: 6E Multiple or Single Award IDC 8K EPA-Designated Product(s) 8L Recovered Material Clauses 10M Solicitation Procedures Step 5: Perform root-cause analysis and document the field as inaccurate. If the field is found to be inaccurate or inappropriately incomplete (based on the definitions outlined in Step 1 and provided in Exhibit B), perform root cause analysis, including the contracting officer for the action (as appropriate). When the root cause has been determined, the error shall be documented with the appropriate root cause (listed in Exhibit B [DOCUMENT LINK]) and a corrective action plan shall be provided where the target goal is not achieved and a routine schedule for addressing any repetitive errors. Corrective actions should attempt to address the root cause of the error in order to minimize the possibility of the error to reoccur; not just the immediate fix of a data error. Corrective Actions might include, but are not limited to: Improving core processes, to include improvements in collecting the source data in the contract writing system Recommendations for alterations to the validation rules contained within the contract writing system or FPDS or interfaces between each system Required Policy Training / Awareness Performance Metrics for Contracting Offices It is noted that some of the required data elements to be reviewed are completed in FPDS CARs by FPDS itself based on information from other authoritative sources (e.g., CCR or previous CARs submitted by other contracting offices). Associated errors found during Procurement Data V&V should be highlighted in the reports submitted to DPAP/PDI, as well as reported to the FPDS Helpdesk as soon as possible (as necessary) to affect their correction. Step 6: Correct errors. Upon documentation of the (1) error, (2) root cause of inaccuracy, and (3) corrective action plan, perform the correction actions to the CARs with errors using the FPDS “CORRECT” system privilege. If not correcting a systemic error across the Component or Department, these corrections should be accomplished as “low” in the Component’s hierarchy of organizations / offices as the CORRECT privilege