Attachment 15 CDRLS.pdf
PDF 377 KB Posted
- Solicitation number
- HC108426R0004
- Issued by
-
Defense Information Systems Agency
About this file
This document is a PDF display error message rather than a federal contract opportunity file. The document contains only technical instructions for Adobe Reader users who are unable to view the PDF properly, along with links to upgrade Adobe Reader software. It does not contain any contract information, solicitation details, requirements, timelines, pricing terms, or other substantive contracting data. No actionable contract information is present in this file.
View the file
Other files
Show all 43
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Please wait...
If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.
You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.
For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
DATA ITEM DESCRIPTION
Title: Government Property (GP) Inventory Report Number: DI-MGMT-80441D Approval Date: 20200609 AMSC Number: 10184 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: MDA Project Number: MGMT-2020-012 Applicable Forms: None
Use/Relationship: The Government Property (GP) Inventory Report enables the contractor to periodically provide to the Department of Defense (DoD) Service or Agency an inventory listing of GP (i.e., both Government Furnished Property (GFP) and Contractor Acquired Property (CAP)) in the contractor’s possession (to include subcontractors) by contract.
This Data Item Description (DID) is applicable to all contracts where GP will be furnished by the Government (i.e., GFP) or acquired, fabricated, or otherwise provided by a contractor (i.e., CAP) in performance of a contract.
This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.
This DID supersedes DI-MGMT-80441C.
Requirements:
1. Reference documents. None.
2. Format. The report shall be in an electronic .xls or .xlsx compatible format.
3. Content. The report shall contain the following column headers (i.e., data fields):
A. Contract Number B. Agency or Service Asset Identification Number (GFP Only) C. Contractor Asset Identification Number D. Item Description E. Manufacturer Part Number F. Manufacturer Model Number G. Manufacturer Serial Number H. National Stock Number (NSN) (if applicable) I. Quantity J. Unit of Measure K. Unit Acquisition Cost L. Unique Item Identifier (if registered in the Item Unique Identification (IUID) Registry;
GFP only) M. Asset Location N. Asset Sub-Location (if applicable) O. Type of Government Property (i.e., Government Furnished Property (GFP) or
Contractor Acquired Property (CAP) P. Classification of Government Property (i.e., Communication Security (COMSEC), Equipment (EQP), Material (MAT), Special Test Equipment (STE), or Special Tooling
Source: https://assist.dla.mil -- Downloaded: 2025-03-17T16:35Z Check the source to verify that this is the current version before use.
DI-MGMT-80441D
(ST))
Q. Date of Last Physical Inventory R. Federal Condition Code
END OF DI-MGMT-80441D
Source: https://assist.dla.mil -- Downloaded: 2025-03-17T16:35Z Check the source to verify that this is the current version before use.
AMSC Number: 10184 Limitation: N/A
Requirements:
Property Management Plan
Table of Contents
Section Page
1. Introduction
2. Scope
3. Purpose
4. Process Ownership
5. Life Cycle Outcomes
Outcome 1 – Acquisition
Outcome 2 – Receiving
Outcome 3 – Records
Outcome 4 – Physical Inventory
Outcome 5 – Subcontractor Control
Outcome 6 – Reports
Outcome 7 – Relief of Stewardship
Outcome 8 – Utilization
Outcome 9 – Maintenance
Outcome 10 – Property Closeout
6. Procedures
7. Self-Assessment
8. Best Practices, Industry Leading Practices, Standards (Optional)
9. Unique Requirements (Optional)
10. Reference Documents
1. INTRODUCTION
Optional – state responsibilities, contractual requirements, industry leading practices (ILP), voluntary consensus standards (VCS), customary commercial practices, and continuous process improvement methods used in property management system.
Note any self-assessments at regular intervals and independent organization performing.
State how property is managed and who is responsible. State functional roles.
2. SCOPE
This document applies to property managed by the Contractor. Describe the Contractor’s Property Management System that will be used to monitor and track property accountable to Government contracts. In cases where a subcontractor is a supplier to a prime contractor, this is the primary Property Plan that will be submitted and will be in effect for applicable subcontracts.
4. PROCESS OWNERSHIP
Note the Property Management organization responsible for maintaining and improving the property management processes and for supporting implementations. Note the point of contacts and roles/responsibilities.
State frequency that property management plan will be reviewed periodically and updated as necessary.
5. LIFE CYCLE OUTCOMES
The outcomes are grouped into the property lifecycle, as follows:
The Acquisition lifecycle phase includes:
Acquisition (Outcome 1)
Receiving (Outcome 2)
The Use lifecycle phase includes:
Physical Inventory (Outcome 4)
Subcontractor Control (Outcome 5)
Utilization (Outcome 8)
Maintenance (Outcome 9)
The Disposition lifecycle phase includes:
Relief of Stewardship (Outcome 7)
Property Closeout (Outcome 10)
Records (Outcome 3) and Reports (Outcome 6) apply to all three lifecycle phases.
Outcome 1 – ACQUISITION
Detail how the contractor will ensure that acquisitions are contractually authorized and consistent with its engineering, production planning, and material management operations. The Government may furnish property or may authorize the contractor to acquire property for the performance of a contract, the costs of which are allowable, reasonable, or allocable to the contract as a direct cost. Property furnished by the Government will be listed in the contract, GFP Module Attachments/Shipments or other authorizing documents. For contractor acquired property (CAP) describe method used to deliver CAP to the Government. Any CAP used in the performance of the contract after delivery is furnished as GFP.
Outcome 2 – RECEIVING
Note how the contractor will ensure controlled receipt for all property. Establish how sites or employees will process and provide information to the Property Manager for identifying items received for purpose of creating a record for and managing Government property. In addition, a process will be established for recording and managing materials. The methods chosen will be validated and concurred with by the appropriate Government Property Management organization and Government Property Administrator (PA). A process will be established to record the receipt of incoming shipments, including a process to report any discrepancies, or damage, through the appropriate channels back to the sender or shipper, and Government PA as required by terms of the contract and FAR 52.245-1.
IDENTIFICATION. The contractor will apply an indication of ownership and identification number using a machine-readable system to customer owned tooling, test equipment, and equipment, where practical. This identification method will be controlled by Property Management and will be used as the basis for establishing accountable stewardship records of managed property. Department of Defense (DoD) Unique Identification (UID) of Government Property will be applied and reported consistent with the requirements of the contract.
Outcome 3 – RECORDS
Property Management System Records
The contractor will establish a property management system to maintain complete, current, and accurate auditable records for property accountable under Government stewardship. Describe methods to record custodial updates such as location changes within a site and record last physical inventory dates in the records. Each property management record will contain at a minimum the following information, unless otherwise authorized:
· The name, part number and description, National Stock Number (if needed for additional item identification tracking and/or disposition), and other data elements as necessary and required in accordance with the terms and conditions of the contract
· Quantity received or fabricated, issued, and balance-on-hand
· Unit Acquisition Cost (actual or estimated)
· Unique-item identifier or equivalent (if available and necessary for individual
· tracking
· Unit of measure
· Accountable contract number or equivalent code designation.
· Location (as a minimum site)
· Disposition
· Posting reference and date of transactions
· Date placed in service (if required in accordance with the terms and conditions of the contract)
Material Records
Describe the material management system for the accountability and control of any production and engineering material. Where the DFARS MMAS clause is in the contract, indicate compliance with applicable accounting and clause requirements. The contractor may maintain, in lieu of system property records, a file of appropriately cross-referenced documents evidencing receipt, issue, and use of material issued for immediate consumption when appropriate and approved by the Government PA.
Sensitive Property Records
Records of sensitive property will be clearly marked to indicate the basis for the designation as sensitive property. Examples include weapons (record serial numbers), ammunition, narcotics, explosives, radioactive material, hazardous material, hazardous waste, and precious metals.
Outcome 4 - PHYSICAL INVENTORY
Indicate the frequency and process that will be used to conduct and record physical inventories of Government/Customer property on a periodic basis and upon contract completion or termination as required in accordance with Site Specific Procedures. Ensure process to inventory property provides evidence of person conducting inventory and date as backup documentation. Describe both physical inventory of equipment and cycle counting/inventory of material as applicable.
Outcome 5 - SUBCONTRACTOR CONTROL
The Prime contractor will require subcontractors, who possess or manage Government/Customer property, to adequately manage, care for and maintain the property in accordance with the provisions of the subcontract/purchase order/administrative contract. The Prime contractor will ensure that appropriate language and clauses are delineated in the subcontract, purchase order, administrative contract, or internal work order to mutually protect the interest of the Government, Customer and the prime contractor. The prime contractor will ensure that contractually required reports include Subcontractor supplied data as necessary. Each will determine whether to use the Subcontractor records as the stewardship records, or to establish duplicate records in the appropriate prime Contractor Property System. Detail Property Management or its designee plan to perform subcontractor analysis when required. Initial reviews of the Subcontractor should include review of any or all the Subcontractor’s property plan, procedures, Government issued approval letters, and any self-assessments. Controls must be established for subcontractor validation and evidence of physical inventor of Government/Customer property accountable to the prime contractors. Contractor Property management personnel or its designee may visit those entities that demonstrate any of the following:
●Non-responsiveness to contract provisions
●A significant amount of property
●A high incidence of Loss (including damage, or destruction)
●An inadequate Government property management plan/system
●An inadequate self-assessment report
●Ineffective processes to accurately account for property
Prime Contractors will require subcontractors to report a loss, including damage, or destruction of property in their possession in accordance with the terms and conditions delineated in the contractual arrangement, and prior to closure of the subcontract, purchase order, administrative contract, or internal work order. Prior to the close-out of the subcontract(s) or purchase order(s) requiring the use of Subcontractor held Government/Customer property, the prime contractor will coordinate the transfer to follow-on orders, its return, or disposal. All loss, including damage or destruction liability cases will be resolved prior to subcontract, purchase order, administrative contract, or internal work order closure.
Outcome 6 – REPORTS
Describe processes and responsibility to ensure contractually required reports of Government/Customer property are submitted accurately and in a timely manner. Processes will be established to create and provide as required the following types of reports:
●Reports of Discrepancies
●Loss, including damage and destruction reports*
●Reports of physical inventory results
●Reports of audits and self-assessment results
●Reports of corrective actions
●Annual listing of DISA property (GFP or CAP), including last inventory date and other property related reports as required by the contract.
1. Preparation of the following reports will be handled by gathering information from the different sites and compiling the information into the format required.
a. Property Management reports property accountable to DISA contracts incorporating the Government Property Clause and Financial Reporting of Government-Owned/Contractor-Held Property Clause no later than 31 October annually.
b. Annual Update to the DoD Property (UID) Registry
2. Reference (Internal procedure(s)) for additional information on this subject.
3. Loss Reporting refer to procedure or process and timelines for reporting loss or damage.
4. Discrepancy Reporting
Outcome 7 - RELIEF OF STEWARDSHIP
Relief of Stewardship Responsibility
The Contractor will describe processes to evaluate and report excess property to the Government when it is no longer required to fulfill contractual obligations. Relief of Stewardship responsibility will take place when:
a. Property is disposed in accordance with contract instructions
b. Consumed or expended during contract performance
c. Processed through an inventory adjustment
d. Delivered or shipped under Government instructions
e. Relieved of liability through a Loss, including, Damage or Destruction Report
f. Processed as production scrap (unusable material resulting from production, engineering, operations and maintenance, repair, and research and development contract activities).
g. Transferred to fulfill another contract’s requirements
h. Credit the costs of Contractor-acquired property (material only) to the losing contract, and debit the gaining contract with the corresponding cost, when such material is needed for use on another contract with Government approval unless approved MMIAS system.
i. Processed through PCARSS disposal instructions
j. Abandoned in accordance with contract terms Individual contracts should address the disposition of aircraft parts or should be disposed of upon direction of the Plant Clearance Officer.
Production Scrap Process
As applicable, describe types of anticipated scrap materials, as well as the processes to disposition production scrap in accordance with cost accounting processes, and contractual requirements. Where proceeds are attributed to general overhead accounts, disposal may occur without customer approval in accordance with its own internal scrap procedures. However, customer owned scrap that requires demilitarization or is sensitive or hazardous in nature (including precious metals in raw or bulk form) or detailed in the contract shall be submitted on an inventory disposal schedule to the customer. Periodically, the contractor may issue a formal or informal bid for scrap sales in accordance with Property Management procedures. In addition, the contractor may contract with a third party for the collection, separating and processing of scrap. Net proceeds from a scrap sale will be handled in a manner consistent with disclosed cost accounting practices Government-owned property, other than that resulting from production scrap, that has been expended (no longer has value in its current form), may be submitted on an Inventory Disposal Schedule. Scrap (other than production scrap) should be reported by “lot” along with metal content, estimated weight and estimated value. Particular attention should be paid to the following:
Sensitive items
Hazardous materials or wastes
Classified or otherwise controlled items
Precious or strategic metals
Characteristics or components dangerous to public health or safety.
Such scrap property may require physical segregation, unique disposal processing or separate plant clearance or customer reporting.
Removal of Government Markings
If property is not returned to the Government, the contractor will ensure removal of any markings identifying the property as U.S. Government-owned property prior to its disposal.
PCARSS Submission Requirements
The contractor will describe processes to submit inventory disposal schedules to the Plant Clearance Officer no later than –
(i) 30 days following the contractor’s determination that a Government property item is no longer required for performance of a contract.
(ii) 60 days, or such longer period as may be approved by the Plant Clearance Officer, following completion of contract deliveries or performance: or
(iii) 120 days, or such longer period as may be approved by the Termination Contracting Officer following contract termination in whole or in part.
The Plant Clearance Officer shall provide the contractor disposition instructions for property identified on an acceptable inventory disposal schedule within 120 days. Failure to provide disposition instructions by this date may entitle the contractor to storage or equitable adjustment.
Outcome 8 – UTILIZATION
Describe controls and systems in place to ensure Government/Customer property, whether furnished or acquired, will only be used for the purpose for which it was acquired or as authorized. When necessary, detail process for requesting use on rent-free, non-interference use is requested, or for commercial use in accordance with FAR 52.245-9. Property is utilized and or consumed to its maximum capacity and declared excess when no longer contractually required for retention. Property is moved and stored with proper contractual authority, adequate protection, appropriate documentation, and prompt record updates.
Outcome 9 – MAINTENANCE
The contractor will provide a maintenance program designed to the degree necessary to ensure the optimum useful life of property in its possession. Maintenance is not required for items in disposal. It includes the determination of the need for, and the performance of, maintenance, rehabilitation, and the recording of work accomplished. The four major types of maintenance are Routine Repair and Adjustment, Preventive Maintenance, Emergency Repair, and Calibration. The contractor will disclose and report to the Government Property Administrator the need for replacement or capital rehabilitation.
Outcome 10 – PROPERTY CLOSEOUT
Describe steps to be taken upon to track end of period of performance or notification of contract completion or termination, detail how the following actions will be promptly performed:
1. Physically inventory property sufficient for disposal purposes unless waived by the Customer
2. Screen for reutilization, purchasing and excess Investigate, report, and resolve loss, including theft, damage, and destruction cases*.
3. Report excess/residual Government/Customer property or follow contractual disposal instructions.
4. Comply with disposal instructions.
5. Submit property closeout certification.
6. PROCEDURES
Describe processes the contractor will employ to maintain, and periodically assess procedures necessary to ensure the effectiveness of its property management system.
8. SELF-ASSESSMENT
Detail how the contractor will perform risk-assessments at the appropriate independent personal at the entity level to evaluate the effectiveness and efficiency of its property management system. This risk-assessment should be utilized to determine the outcomes to review. Self-Assessments should be performed, and results made available to the Government/Customer upon request. As a result of these self-assessments, improvements may be made, and significant deficiencies corrected and documented. The contractor should develop, maintain, and publish metrics to measure the performance of the property management system. Data collected for the metrics is typically be used to compare to the standards and will represent the actual level of performance. The metrics are also be used to provide insight for managing property and to provide information for use in identifying process improvements.
9. PROPERTY MANAGEMENT SYSTEMS
List the systems the contractor uses such as databases and information to establish and maintain accountable records to include any interfaces to other systems used to manage Government, Customer and contractor owned property.
10. BEST PRACTICES, INDUSTRY LEADING PRACTICES, STANDARDS
1. The philosophy for best practices and Industry leading practices (ILP) is specifically referenced in FAR 45.103, General. It states that "Agencies shall allow and encourage contractors to use voluntary consensus standards and industry leading practices and standards to manage Government property in their possession.
2. Voluntary consensus standards and Industry leading practices, or customary commercial practices are continuously reviewed to assure the prevailing practices that bring a best value approach for property management are understood.
3. The contractor’s goal is to balance the cost of property management with the risk of property loss and adapt its property management systems to address changing external requirements and business conditions.
4. Where Standards or Industry Benchmarks do not exist, the contractor will establish and implement new concepts that support our property management philosophy.
(ILPs & Standards that your company uses may be included in your Plan here or in your procedures.)
Example of Standards that may be used in property management system:
ASTM E2279, Standard for Establishing the Guiding Principles for Property Management
ASTM E2135, Terminology for Property and Asset Management
ASTM E2221, Standard Practice for Administrative Control of Property
ASTM E2132, Standard Practice for Physical Inventory of Durable, Moveable Property
ASTM E2452, Standard for Equipment Management Process Maturity (EMPM) Model
ASTM E2811, Standard Practice for Management of Low-Risk Property (LRP)
ASTM E2936-13 Standard Guide for Contractor Self-Assessment for U.S. Government
Property Management Systems
11. UNIQUE REQUIREMENTS
Some contracts may have unique records management, reporting and demilitarization requirements that are outside our normal property management practices, i.e., Commercial Asset Visibility (CAV), Air Force Equipment Management System (AFEMS), COMSEC property etc. In these cases, the activities associated with these unique requirements.
Other References:
FAR Part 1.102, Statement of the Guiding Principles for the Acquisition System
FAR 52.245-1 Government Property
DoD 252.242-7005 Contractor Business Systems
DoD 252.242-7004 Material Management and Accounting System
DoD 252.245-7003 Contractor Property Management System Administration
DoD 252.211-7007 Reporting of Government Furnished Property
The DoD Guide for Evaluation of Uniquely Identified Items DoD UID web site:
http://www.acq.osd.mil/dpap/pdi/uid/
PREVIOUS EDITION MAY BE USED.
DD FORM 1423, FEB 2024
Page of
INSTRUCTIONS FOR COMPLETING DD FORM 1423
(See DoDM 5010.12 for detailed instructions.)
DD FORM 1423, FEB 2024
Page of
CONTRACT DATA REQUIREMENTS LIST
C. CATEGORY:
14. DISTRIBUTION
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES Draft Final Reg Repro
16. REMARKS
14. DISTRIBUTION
15.TOTAL
Image of arrow pointing towards totals
FOR GOVERNMENT PERSONNEL
Item A. Self-explanatory.
Item B. Self-explanatory.
Item C. Mark (X) appropriate category: TDP - Technical Data Package; TM - Technical Manual; Other - other category of data, such as "Provisioning," "Configuration Management," etc.
Item D. Enter name of system/item being acquired that data will support (e.g., Mission Design Series (MDS) designator).
Item E. Self-explanatory (to be filled in after contract award).
Item F. Self-explanatory (to be filled in after contract award).
Item G. Name of preparer of CDRL.
Item H. Date CDRL was prepared and signature of preparer of CDRL.
Item I. Name of CDRL approval authority.
Item J. Date CDRL was approved and signature of CDRL approval authority.
Item 1. See DFARS Subpart 204.71 for proper numbering. To add or delete additional data items, point and click the plus or minus sign to the right of Block J.
Item 2. Enter title as it appears on data acquisition document cited in Item 4.
Item 3. Enter subtitle of data item for further definition of data item (optional entry).
Item 4. Identify only one Data Acquisition Document No. If a single work task generates more than one deliverable data product, prepare a separate data item for each deliverable data product.
Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work/Performance Work Statement paragraph number).
Item 6. Enter technical office responsible for ensuring adequacy of the data item.
Item 7. Specify requirement for inspection/acceptance of the data item by the Government.
Item 8. Specify requirement for approval of a draft before preparation of the final data item.
Item 9. For technical data and computer software, specify the contractor's requirement to mark the appropriate distribution statement on the technical data or computer software (ref. DoDI 5230.24).
Item 10. Specify number of times data items are to be delivered.
Item 11. Specify as-of date of data item, when applicable.
Item 12. Specify when first submittal is required.
Item 13. Specify when subsequent submittals are required, when applicable.
Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.
Item 15. Enter total number of draft/final copies to be delivered.
Item 16. Use for additional/clarifying information for Items 1 through 15. Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in Item 14; Desired medium for delivery of the data item.
Identify for which data item additional remarks are provided. When tailoring the Data Acquisition Document invoked in Item 4, identify which portions of that Document are being tailored.
Identify any referenced attachments to the form. Attachments can be added using the button at the bottom of page 1.
FOR THE CONTRACTOR
Item 17. Specify appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.
a. Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort (production, development, testing, and administration) but which is required by DD Form 1423.
Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with Government requirements, and the administration and other expenses related to reproducing and delivering such data items to the Government.
b. Group II. Definition - Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, or quality of the data item.
Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.
c. Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, and quality of the data item.
Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and delivering such data item to the Government.
d. Group IV. Definition - Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.
Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.
Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the Government of that item of data.
These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government’s rights to use the data shall be governed by the pertinent provisions of the contract.
9.0.0.2.20120627.2.874785 DD Form 1423, "Contract Data Requirements List"
| CurrentPage: |
| PageCount: |
| Select Classification from drop-down list.: 1 |
| CUI Indicator Information: |
| Click on this button to attach a file(s).: |
| A. CONTRACT LINE ITEM NUMBER: 0001 |
| exhibit: |
| C. CATEGORY: Select for "TDP.": 0 |
| C. CATEGORY: Select for "TM.": 0 |
| C. CATEGORY: Select for "OTHER.": 1 |
| C. CATEGORY: Enter specification for "Other.": |
| System: Enterprise Storage Solutions IV |
| ContractNum: |
| Contractor: |
| 1. DATA ITEM NUMBER: A001 |
| 1. DATA ITEM NUMBER: A002 |
| 1. DATA ITEM NUMBER: A003 |
| 1. DATA ITEM NUMBER: A004 |
| 1. DATA ITEM NUMBER: A005 |
| 1. DATA ITEM NUMBER: A006 |
| 1. DATA ITEM NUMBER: A007 |
| 1. DATA ITEM NUMBER: A008 |
| 1. DATA ITEM NUMBER: A009 |
| 1. DATA ITEM NUMBER: A010 |
| 1. DATA ITEM NUMBER: A011 |
| 1. DATA ITEM NUMBER: A012 |
| 1. DATA ITEM NUMBER: A013 |
| 1. DATA ITEM NUMBER: A014 |
| 1. DATA ITEM NUMBER: A015 |
| 1. DATA ITEM NUMBER: A016 |
| 1. DATA ITEM NUMBER: A017 |
| 1. DATA ITEM NUMBER: A018 |
| 1. DATA ITEM NUMBER: A019 |
| 1. DATA ITEM NUMBER: A020 |
| 1. DATA ITEM NUMBER: A021 |
| 1. DATA ITEM NUMBER: A022 |
| 1. DATA ITEM NUMBER: A023 |
| 1. DATA ITEM NUMBER: A024 |
| 1. DATA ITEM NUMBER: A025 |
| 1. DATA ITEM NUMBER: A026 |
| 1. DATA ITEM NUMBER: A027 |
| 1. DATA ITEM NUMBER: A028 |
| titleDataItem: Technical Documentation |
| titleDataItem: Technical Training Plan |
| titleDataItem: Escalation Procedures |
| titleDataItem: Monthly Remedial Maintenance Report |
| titleDataItem: Preventive Maintenance Schedule |
| titleDataItem: Root Cause Analysis /After Action Report |
| titleDataItem: Equipment Report |
| titleDataItem: Change Management Plan |
| titleDataItem: Monthly Configuration Report |
| titleDataItem: Monthly Asset Management Report |
| titleDataItem: Monthly Inventory Report (Physical Level) |
| titleDataItem: Weekly Order Summary Report |
| titleDataItem: Monthly Incident Summary Report |
| titleDataItem: Ad Hoc Reports |
| titleDataItem: Monthly Metered Usage Billing Report |
| titleDataItem: Incoming Strategy Plan (Written) |
| titleDataItem: Exit Strategy Plan |
| titleDataItem: Final Supply Chain Risk Management (SCRM) Plan |
| titleDataItem: SCRM Plan Updates |
| titleDataItem: Technical Data Rights (List of Hardware/Software) |
| titleDataItem: Government Furnished Property (GFP) Inventory |
| titleDataItem: Property Management Plan |
| titleDataItem: Final GFP Disposition Notification |
| titleDataItem: Monthly Non-Disclosure Agreement Status Report |
| titleDataItem: DoDM 8140.03 Compliance Report |
| titleDataItem: Affirmation of Whistleblower Rights Notification |
| titleDataItem: Facility Clearance Sponsorship Report |
| titleDataItem: TESA/ASSA Accreditation Documentation |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-80441D |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-82241 |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| 4. AUTHORITY (Data Acquisition Document Number): Contractor Format |
| contractRef: PWS 6.2.4 |
| contractRef: PWS 6.2.5 |
| contractRef: PWS 6.5.4.1 |
| contractRef: PWS 6.5.6 |
| contractRef: PWS 6.5.7 |
| contractRef: PWS 6.5.8 |
| contractRef: PWS 6.6.1.4 |
| contractRef: PWS 6.7.2 |
| contractRef: PWS 6.7.3 |
| contractRef: PWS 6.7.5 |
| contractRef: PWS 6.8.1 |
| contractRef: PWS 6.8.2 |
| contractRef: PWS 6.8.3 |
| contractRef: PWS 6.8.4 |
| contractRef: PWS 6.8.5 |
| contractRef: PWS 6.15.1.1 |
| contractRef: PWS 6.15.1.2 |
| contractRef: PWS 6.17.1 |
| contractRef: PWS 6.17.2 |
| contractRef: PWS 6.18 |
| contractRef: PWS 12.1.2 |
| contractRef: PWS 12.1.3 / DITCO Instruction H9 |
| contractRef: PWS 12.3 / DITCO Instruction H9 |
| contractRef: PWS 13.1 |
| contractRef: PWS 13.5.1 |
| contractRef: PWS 13.5.4 |
| contractRef: PWS 6.11.2 |
| contractRef: PWS 6.16 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| reqOffice: HaC (J9) J-9331 |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 7. DD 250 REQUIREMENT: XX |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 8. APPROVAL CODE : N/A |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| 9. DISTRIBUTION STATEMENT REQUIRED: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: ONE/R |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: ANNLY |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: See Block 16 |
| freq: AS REQ |
| freq: AS REQ |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| asOfDate: N/A |
| dateFirstSub: 30DAC |
| dateFirstSub: 30DAC |
| dateFirstSub: 30DAC |
| dateFirstSub: EOM |
| dateFirstSub: 90DAC |
| dateFirstSub: ASREQ |
| dateFirstSub: ASREQ |
| dateFirstSub: ASREQ |
| dateFirstSub: EOM |
| dateFirstSub: EOM |
| dateFirstSub: EOM |
| dateFirstSub: EOW |
| dateFirstSub: EOM |
| dateFirstSub: ASREQ |
| dateFirstSub: EOM |
| dateFirstSub: 60DAC |
| dateFirstSub: See Block 16 |
| dateFirstSub: 10 DAC |
| dateFirstSub: ASREQ |
| dateFirstSub: 60DAC |
| dateFirstSub: See Block 16 |
| dateFirstSub: See Block 16 |
| dateFirstSub: See Block 16 |
| dateFirstSub: 7DAC |
| dateFirstSub: See Block 16 |
| dateFirstSub: See Block 16 |
| dateFirstSub: See Block 16 |
| dateFirstSub: See Block 16 |
| dateSubseqSub: ASREQ |
| dateSubseqSub: ASREQ |
| dateSubseqSub: EOQ |
| dateSubseqSub: EOM |
| dateSubseqSub: 10DACM |
| dateSubseqSub: ASREQ |
| dateSubseqSub: ASREQ |
| dateSubseqSub: ASREQ |
| dateSubseqSub: EOM |
| dateSubseqSub: EOM |
| dateSubseqSub: EOM |
| dateSubseqSub: EOW |
| dateSubseqSub: EOM |
| dateSubseqSub: ASREQ |
| dateSubseqSub: EOM |
| dateSubseqSub: N/A |
| dateSubseqSub: N/A |
| dateSubseqSub: N/A |
| dateSubseqSub: ASREQ |
| dateSubseqSub: N/A |
| dateSubseqSub: ANNLY |
| dateSubseqSub: See Block 16 |
| dateSubseqSub: See Block 16 |
| dateSubseqSub: EOM |
| dateSubseqSub: See Block 16 |
| dateSubseqSub: See Block 16 |
| dateSubseqSub: See Block 16 |
| dateSubseqSub: See Block 16 |
| 16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval. |
Block 10: Frequency, 30 calendar days after contract award and when updates to the technical documentation become available.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered Not Separately Priced (NSP)
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, 30 calendar days after contract award and as new hardware is introduced to the storage environment Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, 30 Days after contract award and quarterly thereafter.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, Monthly, within five business days after the previous month end.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, 90 calendar days after contract award and with modifications.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, Within five business days after an outage or incident.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, No less than five calendar days prior to equipment delivery.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, Within five business days after OEM notification of EOL or supportability issues.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, Monthly, within five business days after the previous month end.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, Monthly, within five business days after the previous month end.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, Monthly, within five business days after the previous month end.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, Weekly Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, Monthly, within five business days after the previous month end.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, When requested by the Government.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, Monthly, within five business days after the previous month end.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, Within 60 calendar days after contract award.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10, 12: Frequency, Within 30 days after the start date of the contract base year four or within 30 days receiving a notice of termination, whichever comes first.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: This CDRL is for the Final SCRM Plan to be delivered post-award. This is separate from the Draft SCRM Plan which is required to be submitted with the proposal for evaluation purposes. The Final SCRM Plan should incorporate any feedback or final negotiations and represent the definitive plan for contract execution.
Block 12: Within 10 business days after contract award.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, Within five business days after a change that impacts any CNSSI 1253 security controls.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 10: Frequency, Within 60 calendar days after contract award.
Block 14: Distribution, 14 (a) disa.meade.j-9.list.compute-ops-hc331@mail.mil and Contracting Officer Representative listed in PWS and additional DITCO text.
Block 17: Data deliverables are encompassed in overarching performance and are considered NSP.
16. REMARKS: Block 9: Distribution is listed in Block 14 data below. No secondary distribution is authorized without Government approval.
Block 12: 30 days prior to the end of the period of performance.
Block 14: Distribution, 14 (a)…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .