Contractor validation

Government Verification

Contractor validation

The contractor should be required to validate that the TDP and associated elements conform to the contractual requirements. In those instances where materiel has been developed or produced, the contractor shall validate that the TDP and associated elements accurately depict the materiel developed or produced under the contract. Use of the TDP in producing, inspecting, and testing satisfactory materiel is considered acceptable evidence that the validation requirement has been met. When specified in the contract or purchase order, the contractor's validation shall be documented in a TDP validation report.

Validation by Contractor Physical Configuration Audit (PCA) or Verification Reviews

The NATO/NATO nations may require the contractor to validate the TDP through PCAs, Configuration Item Verification Reviews (CIVR), or by other methods through specific work tasks in the statement of work of the contract or purchase order. Unless such tasks are included in the contract or purchase order, the method of validation shall remain the contractor's option.

TDP Validation Report

A TDP validation report is used by the NATO/NATO nations to review the procedures and evaluate the results of the contractor's validation of the TDP as conforming to the data requirements in the contract or purchase order.

Government Verification

Digital Data Product Acceptance

The unique aspect of CALS digital data deliverables is that they will be subject to inspection and acceptance on several levels. The lowest level of acceptance is the data content and format. The acceptance process at this level is identical to acceptance of the data product provided on paper. This level of acceptance will be accomplished by viewing the data either through use of a computer video screen or by viewing a paper printout of the data product. The next level of acceptance is adherence to the specified CALS data exchange format. This will usually be compliant with the CALS standardization documents or other national or international data exchange standards. This level of acceptance may be aided by automated tools. The next level of acceptance is applied to the MIL-STD-1840 digital data format if it has been specified. Again, automated tools may be used to verify compliance. Finally, the physical media may have acceptance criteria to be applied. This level of acceptance will not be used if data has been formally delivered by the CITIS. The means of inspection to be used should be provided to the contractor as soon as these means have been determined. Any or all levels of acceptance may be performed at the contractor's facility or at a NATO/NATO nations facility, as required. In addition to digital data acceptance, CITIS requires that additional acceptance requirements be applied.

CITIS Acceptance

Acceptance of the service and the CITIS Contract Line Item Number (CLIN), if utilized, is a verification that the contractor has provided the service as specified. The CITIS functional requirements are defined by MIL-STD-974 and the particular statement of work. A checklist of CITIS functional requirements may be prepared to assist in tracking contractor compliance. These functional requirements may include service availability, maintenance response, provision for core information functions, provision for value-added information functions, and the like. Assurances of adequate acceptance testing for CITIS should be obtained via contractor demonstration of the service. The test should include demonstration of functional capabilities and verification that the CITIS will handle the data required without alteration of the data product. Such a test is not required for each delivery but may be rerun if major maintenance has been accomplished or if the sending or receiving systems have been changed enough to warrant an additional test. If specific test data are deemed necessary for adequate testing of a CITIS, that test data should be provided and results reviewed on-site at a customer facility. On-line access service should be accepted when it is demonstrated that a person with proper authorization can perform the contractually required core and value-added functions from a terminal or workstation at the customer's facility or as otherwise agreed. Electronic data transfer service acceptance should occur when a single instance of transfer of the specific deliverable type can be achieved including successful download of data into the customer's system when contractually required. This data may be real product data or test data, as appropriate.

CALSIP Acceptance

The original contracts baseline requirements for CALS-compliant product(s) are subject to change and redefinition, by mutual agreement, throughout the duration of the contract. The NATO/NATO nations verifies and controls, in part, the adequacy of the CALS product change and redefinition process via the approval of the original and revision(s) of the CALS Implementation Plan (CALSIP) along with the final acceptance of the CALSIP at contract completion.