Attch_0025_ACWS_Cost_and_SW_Data_Rptg_Plan_2016_05_06.xls
XLS spreadsheet 2 MB Posted
- Attached to
- IT AND TELECOM- OTHER IT AND TELECOMMUNICATIONS
- Solicitation number
- W52P1J16R0058
About this file
Attachment 0025 COST DATA SUMMARY REPORT
View the file
Other files
Show 40 more
Latest 50 of 97 listed here. See the rest on GovTribe.
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
Cover
Important Note
| 6 May 2016: The following documents have been updated and included for your use: | |
| 1) | Resource Distribution Table (RDT), ACWS System - Contract Plan; |
| 2) | RDT Training Briefing from CAPE / DCARC for use with item 1) above; |
| 3) | Government Work Breakdown Structure (WBS) with mapping to the CSDR Plan |
ACWS Investment Pg 1(CSDR Plan)
COST AND SOFTWARE DATA REPORTING PLAN Form Approved OMB No. 0704-0188 The public reporting burden for this collection of information is estimated to average 8 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.
PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.
| 1. MAJOR PROGRAM | a. NAME: | Army Contract Writing System | |||||||||||||||
| b. PHASE/MILESTONE | c. PRIME MISSION PRODUCT | 2. WBS SYSTEM TYPE | 3. SUBMISSION TYPE | 4. CURRENT SUBMISSION DATE (YYYYMMDD) | 5. LAST APPROVED PLAN DATE (YYYYMMDD) | ||||||||||||
| X | Pre-A | B | C-FRP | Army Contract Writing System Increment 1 Investment | Automated Information System | X | INITIAL | ||||||||||
| A | C-LRIP | O&S | CHANGE | 20151028 | |||||||||||||
| 6a. POINT OF CONTACT (POC) NAME AND ADDRESS (Include ZIP Code) | 6b. TELEPHONE NUMBER (Include Area Code) | 6c. FAX NUMBER (Include Area Code) | 6d. E-MAIL ADDRESS | ||||||||||||||
| Kim Reid | (703) 545-9061 | kim.g.reid.civ@mail.mil | |||||||||||||||
| 7. PLAN TYPE | 8. PREPARING ORGANIZATION | 9a. CONTRACTOR NAME/ADDRESS | 9b. CONTRACT NUMBER | 9c. APPROPRIATION | 10. APPROVED PLAN NUMBER | ||||||||||||
| PROGRAM | X | CONTRACT (PRIME) | i. PERFORMING ORGANIZATION | ii. DIVISION | TBD | X | RDT&E | A-15-L-C1 | |||||||||
| CONTRACT (SUB) | PEO EIS | TBD | X | PROCUREMENT | |||||||||||||
| O&M | |||||||||||||||||
| 11. WBS ELEMENT CODE | 12. | ||||||||||||||||
| WBS REPORTING ELEMENTS | 13. REPORTS REQUIRED | ||||||||||||||||
| (X if applicable) | DD 1921-3 (CBDR): | ||||||||||||||||
| X | |||||||||||||||||
| a. PROGRAM/ | |||||||||||||||||
| CONTRACT/ SUBCONTRACT | b. CONTRACT/ | ||||||||||||||||
| SUBCONTRACT | a. CWBS | ||||||||||||||||
| DICTIONARY | b. DD 1921 | ||||||||||||||||
| (CDSR) | c. DD 1921-1 | ||||||||||||||||
| (FCHR) | d. DD 1921-2 | ||||||||||||||||
| (PCR) | e. DD 1921-5 | ||||||||||||||||
| (SFCHR) | f. SRDR |
FORMATS
| 1.0 | 1.0 | Army Contract Writing System (ACWS) Investment | X | X | X | X | |||||
| 1.1 | 1.1 | Prime Mission Product | X | X | X | X | |||||
| 1.1.1 | 1.1.1 | Custom Application Software | X | X | X | X | |||||
| 1.1.1 | 1.1.1.1 | Custom Application Software Hardware | X | X | X | X | |||||
| 1.1.1 | 1.1.1.1.x | Build 1..N | X | X | X | X | |||||
| 1.1.1 | 1.1.1.2 | Custom Application Software Software | X | X | X | X | |||||
| 1.1.1 | 1.1.1.2.x | Build 1..N | X | X | X | X | |||||
| 1.1.1 | 1.1.1.3 | Custom Application Software Integration, Assembly, Test and Checkout | X | X | X | X | |||||
| 1.1.1 | 1.1.1.3.x | Build 1..N | X | X | X | X | |||||
| 1.1.2 | 1.1.2 | Enterprise Service Element | X | X | X | X | |||||
| 1.1.2 | 1.1.2.1 | Enterprise Service Element Hardware | X | X | X | X | |||||
| 1.1.2 | 1.1.2.1.x | Build 1..N | X | X | X | X | |||||
| 1.1.2 | 1.1.2.2 | Enterprise Service Element Software | X | X | X | X | |||||
| 1.1.2 | 1.1.2.2.x | Build 1..N | X | X | X | X | |||||
| 1.1.2 | 1.1.2.3 | Enterprise Service Element Integration, Assembly, Test and Checkout | X | X | X | X | |||||
| 1.1.2 | 1.1.2.3.x | Build 1..N | X | X | X | X | |||||
| 1.1.3 | 1.1.3 | Enterprise Information System | X | X | X | X | |||||
| 1.1.3 | 1.1.3.1 | Enterprise Information System Hardware | X | X | X | X | |||||
| 1.1.3 | 1.1.3.1.x | Build 1..N | X | X | X | X | |||||
| 1.1.3 | 1.1.3.2 | Enterprise Information System Software | X | X | X | X | |||||
| 1.1.3 | 1.1.3.2.x | Build 1..N | X | X | X | X | |||||
| 1.1.3 | 1.1.3.3 | Enterprise Information System Integration, Assembly, Test and Checkout | X | X | X | X | |||||
| 1.1.3 | 1.1.3.3.x | Build 1..N | X | X | X | X | |||||
| 1.1.4 | 1.1.4 | External System Interface Development | X | X | X | X | |||||
| 1.1.4 | 1.1.4.1 | External System Interface Development Hardware | X | X | X | X | |||||
| 1.1.4 | 1.1.4.1.x | Build 1..N | X | X | X | X | |||||
| 1.1.4 | 1.1.4.2 | External System Interface Development Software | X | X | X | X | |||||
| 1.1.4 | 1.1.4.2.x | Build 1..N | X | X | X | X | |||||
| 1.1.4 | 1.1.4.3 | Enterprise Service Element Integration, Assembly, Test and Checkout | X | X | X | X | |||||
| 1.1.4 | 1.1.4.3.x | Build 1..N | X | X | X | X | |||||
| 1.1.5 | 1.1.5 | AIS Platform Hardware | X | X | X | ||||||
| 1.1.5 | 1.1.5.x | Build 1..N | X | X | X | X | |||||
| 1.1.6 | 1.1.6 | System Level Integration | X | X | X | X | |||||
| 1.1.6 | 1.1.6.x | Build 1..N | X | X | X | X | |||||
| 1.2 | 1.2 | System Engineering | X | X | X | X | |||||
| DD FORM 2794, MAY 2011 | PREVIOUS EDITION IS OBSOLETE | ||||||||||
| 11. WBS ELEMENT CODE | 12. | ||||||||||
| WBS REPORTING ELEMENTS | 13. REPORTS REQUIRED | ||||||||||
| (X if applicable) | DD 1921-3 (CBDR): | ||||||||||
| X | |||||||||||
| a. PROGRAM/ | |||||||||||
| CONTRACT/ SUBCONTRACT | b. CONTRACT/ | ||||||||||
| SUBCONTRACT | a. CWBS | ||||||||||
| DICTIONARY | b. DD 1921 | ||||||||||
| (CDSR) | c. DD 1921-1 | ||||||||||
| (FCHR) | d. DD 1921-2 | ||||||||||
| (PCR) | e. DD 1921-5 | ||||||||||
| (SFCHR) | f. SRDR |
FORMATS
| 1.2.1 | 1.2.1 | Contractor System Engineering | X | X | |||
| 1.2.1 | 1.2.1.1 | Management and Planning | X | X | |||
| 1.2.1 | 1.2.1.2 | Solution Development & Design | X | X | |||
| 1.3.1 | 1.3 | Program Management | X | X | X | X | |
| 1.4 | 1.4 | Change Management | X | X | X | ||
| 1.4.1 | 1.4.1 | Change Management Planning | X | X | X | ||
| 1.4.2 | 1.4.2 | Change Management Tools | X | X | X | ||
| 1.5 | 1.5 | System Test and Evaluation | X | X | X | ||
| 1.5.1 | 1.5.1 | Development Test and Evaluation | X | X | X | ||
| 1.5.2 | 1.5.2 | Operational Test and Evaluation Support | X | X | X | ||
| 1.5.3 | 1.5.3 | Human System Integration Support | X | X | X | ||
| 1.5.4 | 1.5.4 | Test and Evaluation Support | X | X | X | ||
| 1.5.5 | 1.5.5 | Test Facilities | X | X | X | ||
| 1.5.6 | 1.5.6 | Test Tools | X | X | X | ||
| 1.6 | 1.6 | Training | X | X | X | ||
| 1.7 | 1.7 | Data | X | X | X | ||
| 1.7.1 | 1.7.1 | Technical Publications | X | X | |||
| 1.7.2 | 1.7.2 | Engineering Data | X | X | |||
| 1.7.3 | 1.7.3 | Management Data | X | X | |||
| 1.7.4 | 1.7.4 | Support Data | X | X | |||
| 1.7.5 | 1.7.5 | Data Depository | X | X | |||
| 1.8 | 1.8 | Peculiar Support Equipment | X | N/A | |||
| 1.9 | 1.9 | Common Support Equipment | X | N/A | |||
| 1.10 | 1.10 | Operational/Site Activation | X | X | X | ||
| 1.10.1 | 1.10.1 | Deployment Hardware and Software | X | X | X | ||
| 1.10.2 | 1.10.2 | User Documentation | X | X | X | ||
| 1.10.3 | 1.10.3 | Site Activation | X | X | X | ||
| 1.10.4 | 1.10.4 | User Training | X | X | X | ||
| 1.10.5 | 1.10.5 | Data Migration | X | X | X | ||
| 1.10.6 | 1.10.6 | Management/Engineering Support | X | X | X | ||
| 1.10.7 | 1.10.7 | Interim Logistics Support | X | X | X | ||
| 1.11 | 1.11 | Industrial Facilities | X | X | X | ||
| 1.12 | 1.12 | Initial Spares and Repair Parts | X | N/A | |||
| 1.13 | 1.13 | Not Applicable | |||||
| 1.14 | 1.14 | Not Applicable | |||||
| 1.15 | 1.15 | Other (Facilities and Mega Data Centers) | X | X | X | ||
| Subtotal Cost | X | ||||||
| Reporting Contractor G&A | X | ||||||
| Reporting Contractor Undistributed Budget | X | ||||||
| Reporting Contractor Management Reserve | X | ||||||
| Reporting Contractor FCCM | X | ||||||
| Total Cost | X | ||||||
| Reporting Contractor Profit/Loss or Fee | X | ||||||
| Total Price | X | ||||||
| DD FORM 2794, MAY 2011 | PREVIOUS EDITION IS OBSOLETE |
ACWS Investment Pg 2(CSDR Plan)
| 14. CSDR SUBMISSION DATES | ||||||
| a. | ||||||
| SUBMISSION | b. | |||||
| FORM(S) | c. | |||||
| EVENT | d. AS OF DATE | e. DUE DATE | ||||
| (YYYYMMDD) | (YYYYMMDD) | |||||
| CWBS Dictionary | CWBS Dictionary - 60 days after Contract Award | TBD | TBD | |||
| 1921, 1921-1 | Initial Report - 60 days after Contract Award | TBD | TBD | |||
| SRDR Initial | Risk Reduction Dev SRDR - Due 60 days after TO 001 Award | TBD | TBD | |||
| 1921, 1921-1 | Interim Cost Report - Due 90 before MS B | TBD | TBD | |||
| SRDR Final | Risk Reduction Dev SRDR - Due 60 days after TO 001 Completion | TBD | TBD | |||
| SRDR Initial | Build X Dev SRDR - Due 60 days after TO XX Award | TBD | TBD | |||
| SRDR Final | Build X Dev SRDR - Due 60 days after Software Delivery | TBD | TBD | |||
| SRDR Initial | Build X Dev SRDR - Due 60 days after TO XX Award | TBD | TBD | |||
| SRDR Final | Build X Dev SRDR - Due 60 days after Software Delivery | TBD | TBD | |||
| SRDR Initial | Build X Dev SRDR - Due 60 days after TO XX Award | TBD | TBD | |||
| SRDR Final | Build X Dev SRDR - Due 60 days after Software Delivery | TBD | TBD | |||
| 1921, 1921-1 | Annual Cost Report | TBD | TBD | |||
| 1921, 1921-1 | Annual Cost Report | TBD | TBD | |||
| 1921, 1921-1 | Annual Cost Report | TBD | TBD | |||
| 1921, 1921-1 | Annual Cost Report | TBD | TBD | |||
| 1921, 1921-1 | Annual Cost Report | TBD | TBD | |||
| 1921, 1921-1 | Final Cost Report | TBD | TBD | |||
| DD FORM 2794 (PAGE 2), MAY 2011 | PREVIOUS EDITION IS OBSOLETE | |||||
| 15. REMARKS | ||||||
| Special Instructions | ||||||
| 1. | NON-RECURRING/RECURRING DEFINITIONS: | |||||
| The contractor will utilize the specific definitions and requirements in the CSDR Manual (DoD 5000.04-M-1) and the definitions in the DIDs for the forms 1921, 1921-1, and 1921-2 to segregate Recurring and Nonrecurring costs discretely and not as an aggregate. Refinements or expansions to these definitions are TBD pending the pre-contract or post contract award conference. | ||||||
| 2. | COST ACCOUNTING STANDARDS (CAS) DISCLOSURE STATEMENT: | |||||
| Describe significant accounting changes from previous accounting period in the Remarks section of the reports, if applicable. | ||||||
| 3. | DD Form 1921-3 Contractor Business Data Report: | |||||
| a. | The Contractor Business Data Report is prepared by and for the business entity (e.g., business unit, segment, or site) responsible for submitting the Forward Pricing Rate Proposal (FPRP) representing the basis for Forward Pricing Rate Agreement (FPRA) negotiations with the government. | |||||
| b. | Reports are submitted annually at the end of the contractor's fiscal year. | |||||
| c. | Data for Future Years should be reflective of the number of years contained in the most current document, i.e., the FPRP or the FPRA. If the document applies to more than three future years, attach additional future year sheets as required. In the absence of these documents, estimates should be provided for three future years. | |||||
| Software Special Instructions | ||||||
| Software Reporting and Dates | ||||||
| The Software Resource Data Reports (SRDRs) identified in section in Section 14b and 14c will be subject to change pending the proposed development strategy by the contractor. The contractor will be required to provide an SRDR submission for each individual build, increment, release, etc. that is identified in the approved development strategy. Upon contract award the CSDR plan will be revised to ensure the submission events reflect development strategy. | ||||||
| DD FORM 2794 (PAGE 2), MAY 2011 | PREVIOUS EDITION IS OBSOLETE |
ACWS Sustainment Pg1(CSDR Plan)
COST AND SOFTWARE DATA REPORTING PLAN Form Approved OMB No. 0704-0188 The public reporting burden for this collection of information is estimated to average 8 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.
PLEASE DO NOT RETURN YOUR COMPLETED FORM TO THE ABOVE ORGANIZATION.
| 1. MAJOR PROGRAM | a. NAME: | Army Contract Writing System | |||||||||||||||
| b. PHASE/MILESTONE | c. PRIME MISSION PRODUCT | 2. WBS SYSTEM TYPE | 3. SUBMISSION TYPE | 4. CURRENT SUBMISSION DATE (YYYYMMDD) | 5. LAST APPROVED PLAN DATE (YYYYMMDD) | ||||||||||||
| X | Pre-A | B | C-FRP | Army Contract Writing System Increment 1 Sustainment | Automated Information System | X | INITIAL | ||||||||||
| A | C-LRIP | O&S | CHANGE | 20151028 | |||||||||||||
| 6a. POINT OF CONTACT (POC) NAME AND ADDRESS (Include ZIP Code) | 6b. TELEPHONE NUMBER (Include Area Code) | 6c. FAX NUMBER (Include Area Code) | 6d. E-MAIL ADDRESS | ||||||||||||||
| Kim Reid | (703) 545-9061 | kim.g.reid.civ@mail.mil | |||||||||||||||
| 7. PLAN TYPE | 8. PREPARING ORGANIZATION | 9a. CONTRACTOR NAME/ADDRESS | 9b. CONTRACT NUMBER | 9c. APPROPRIATION | 10. APPROVED PLAN NUMBER | ||||||||||||
| PROGRAM | X | CONTRACT (PRIME) | i. PERFORMING ORGANIZATION | ii. DIVISION | TBD | RDT&E | A-15-L-C2 | ||||||||||
| CONTRACT (SUB) | PEO EIS | TBD | PROCUREMENT | ||||||||||||||
| X | O&M | ||||||||||||||||
| 11. WBS ELEMENT CODE | 12. | ||||||||||||||||
| WBS REPORTING ELEMENTS | 13. REPORTS REQUIRED | ||||||||||||||||
| (X if applicable) | DD 1921-3 (CBDR): | ||||||||||||||||
| X | |||||||||||||||||
| a. PROGRAM/ | |||||||||||||||||
| CONTRACT/ SUBCONTRACT | b. CONTRACT/ | ||||||||||||||||
| SUBCONTRACT | a. CWBS | ||||||||||||||||
| DICTIONARY | b. DD 1921 | ||||||||||||||||
| (CDSR) | c. DD 1921-1 | ||||||||||||||||
| (FCHR) | d. DD 1921-2 | ||||||||||||||||
| (PCR) | e. DD 1921-5 | ||||||||||||||||
| (SFCHR) | f. SRDR |
FORMATS
| 2.0 | 2.0 | AIS Sustainment Effort | X | X | X | |||||
| 2.1 | 2.1 | Unit Level Manpower | X | X | X | |||||
| 2.2 | 2.2 | Unit Level Operations | X | X | X | |||||
| 2.3 | 2,3 | Hardware Maintenance | X | X | X | |||||
| 2.4 | 2.4 | Sustaining Support | X | X | X | |||||
| 2.4.1 | 2.4.1 | System-specific Training | X | X | X | |||||
| 2.4.2 | 2.4.2 | Support Equipment Replacement and Repair | X | X | X | |||||
| 2.4.3 | 2.4.3 | Sustaining/Systems Engineering | X | X | X | |||||
| 2.4.3 | 2.4.3.1 | Systems Engineering | X | X | ||||||
| 2.4.3 | 2.4.3.2 | Sustaining Engineering | X | X | ||||||
| 2.4.4 | 2.4.4 | Program Management | X | X | X | |||||
| 2.4.4 | 2.4.4.1 | Program Management | X | X | ||||||
| 2.4.4 | 2.4.4.2 | Change Management | X | X | ||||||
| 2.4.5 | 2.4.5 | Information Systems | X | X | X | |||||
| 2.4.5 | 2.4.5.1 | Tech Refresh | X | X | X | |||||
| 2.4.5 | 2.4.5.2 | License Fees (Software) | X | X | X | |||||
| 2.4.5 | 2.4.5.3 | System Support | X | X | X | |||||
| 2.4.5 | 2.4.5.3.1 | Help Desk | X | X | X | X | ||||
| 2.4.5 | 2.4.5.3.1.1 | Tier 1 | X | X | X | X | ||||
| 2.4.5 | 2.4.5.3.1.2 | Tier 2 | X | X | X | X | ||||
| 2.4.5 | 2.4.5.3.1.3 | Tier 3 | X | X | X | X | ||||
| 2.4.5 | 2.4.5.3.2 | System and Database Administration | X | X | X | |||||
| 2.4.5 | 2.4.5.3.3 | Follow-on User Training | X | X | X | |||||
| 2.4.5 | 2.4.5.3.4 | Accreditation (Recurring) | X | X | X | |||||
| 2.4.5 | 2.4.5.3.5 | Independent Verification and Validation (IV&V) | X | X | X | |||||
| 2.4.6 | 2.4.6 | Data and Technical Publications | X | X | X | |||||
| 2.4.7 | 2.4.7 | Simulator Operations | X | X | X | |||||
| 2.4.8 | 2.4.8 | Data Maintenance (Management) | X | X | ||||||
| 2.4.9 | 2.4.9 | Other Sustaining Support | X | X | X | X | ||||
| 2.5 | 2.5 | Continuing System Improvements | X | X | X | |||||
| 2.5.1 | 2.5.1 | Hardware Modifications | X | X | X | |||||
| 2.5.2 | 2.5.2 | Software Modification/Maintenance | X | X | X | |||||
| 2.5.2 | 2.5.2.1 | Software Modification | X | X | X | X | ||||
| 2.5.2 | 2.5.2.2 | Software Maintenance | X | X | X | X | ||||
| DD FORM 2794, MAY 2011 | PREVIOUS EDITION IS OBSOLETE | |||||||||
| 11. WBS ELEMENT CODE | 12. | |||||||||
| WBS REPORTING ELEMENTS | 13. REPORTS REQUIRED | |||||||||
| (X if applicable) | DD 1921-3 (CBDR): | |||||||||
| X | ||||||||||
| a. PROGRAM/ | ||||||||||
| CONTRACT/ SUBCONTRACT | b. CONTRACT/ | |||||||||
| SUBCONTRACT | a. CWBS | |||||||||
| DICTIONARY | b. DD 1921 | |||||||||
| (CDSR) | c. DD 1921-1 | |||||||||
| (FCHR) | d. DD 1921-2 | |||||||||
| (PCR) | e. DD 1921-5 | |||||||||
| (SFCHR) | f. SRDR |
FORMATS
| Subtotal Cost | X | ||
| Reporting Contractor G&A | X | ||
| Reporting Contractor Undistributed Budget | X | ||
| Reporting Contractor Management Reserve | X | ||
| Reporting Contractor FCCM | X | ||
| Total Cost | X | ||
| Reporting Contractor Profit/Loss or Fee | X | ||
| Total Price | X | ||
| DD FORM 2794, MAY 2011 | PREVIOUS EDITION IS OBSOLETE |
ACWS Sustainment Pg2(CSDR Plan)
| 14. CSDR SUBMISSION DATES | ||||||
| a. | ||||||
| SUBMISSION | b. | |||||
| FORM(S) | c. | |||||
| EVENT | d. AS OF DATE | e. DUE DATE | ||||
| (YYYYMMDD) | (YYYYMMDD) | |||||
| 1 | CWBS Dictionary | CWBS Dictionary - Contract Award | TBD | TBD | ||
| 2 | 1921, 1921-5 | Annual CCDR | TBD | TBD | ||
| 3 | SRDR Final | Annual Maintenance SRDR | TBD | TBD | ||
| 4 | 1921, 1921-5 | Annual CCDR | TBD | TBD | ||
| 5 | SRDR Final | Annual Maintenance SRDR | TBD | TBD | ||
| 6 | 1921, 1921-5 | Annual CCDR | TBD | TBD | ||
| 7 | SRDR Final | Annual Maintenance SRDR | TBD | TBD | ||
| 8 | 1921, 1921-5 | Annual CCDR | TBD | TBD | ||
| 9 | SRDR Final | Annual Maintenance SRDR | TBD | TBD | ||
| 10 | 1921, 1921-5 | Final Maintenance CCDR | TBD | TBD | ||
| 11 | SRDR Final | Final Maintenance SRDR | TBD | TBD | ||
| 15. REMARKS | ||||||
| Special Instructions | ||||||
| 1. | NON-RECURRING/RECURRING DEFINITIONS: | |||||
| The contractor will utilize the specific definitions and requirements in the CSDR Manual (DoD 5000.04-M-1) and the definitions in the DIDs for the forms 1921, 1921-1, and 1921-2 to segregate Recurring and Nonrecurring costs discretely and not as an aggregate. Refinements or expansions to these definitions are TBD pending the pre-contract or post contract award conference. | ||||||
| 2. | COST ACCOUNTING STANDARDS (CAS) DISCLOSURE STATEMENT: | |||||
| Describe significant accounting changes from previous accounting period in the Remarks section of the reports, if applicable. | ||||||
| 3. | DD Form 1921-3 Contractor Business Data Report: | |||||
| a. | The Contractor Business Data Report is prepared by and for the business entity (e.g., business unit, segment, or site) responsible for submitting the Forward Pricing Rate Proposal (FPRP) representing the basis for Forward Pricing Rate Agreement (FPRA) negotiations with the government. | |||||
| b. | Reports are submitted annually at the end of the contractor's fiscal year. | |||||
| c. | Data for Future Years should be reflective of the number of years contained in the most current document, i.e., the FPRP or the FPRA. If the document applies to more than three future years, attach additional future year sheets as required. In the absence of these documents, estimates should be provided for three future years. | |||||
| Software Maintenance Special Instructions | ||||||
| CR/DR | ||||||
| The contractor will report the number and age of change requests and discrepancy reports by the level of complexity as identified by the contractor. Also, the contractor must define each level of complexity in the data dictionary. | ||||||
| DD FORM 2794 (PAGE 2), MAY 2011 | PREVIOUS EDITION IS OBSOLETE |
ACWS Government Work Breakdown Structure (WBS)
The ACWS Government Work Breakdown Structure (WBS) has been developed in accordance with MIL-STD-881C, Appendix K, Automated Information Systems (AIS) and the DoD AIS Economic Analysis Guide, Appendix B. The WBS construct frames the ACWS acquisition (development and procurement) and Operation & Support (O&S) (sustainment) activities and sets the basis from which program planning and cost estimates will be developed. It is to be used as a reference for the contractor in developing the Contractor WBS (CWBS) and Cost and Software Data Reporting (CSDR) Plan. It is acknowledged that the Government WBS and Government CSDR Plan elements are not the same; hence the inclusion of the mapping of the Government WBS element to the Government CSDR Plan WBS element. The contractor may recommend modifications to the CSDR Plan.
Govt WBS Element
Govt CSDR Plan WBS Element
Title
Description
1.0
1.0
Army Contract Writing System (ACWS) Investment
(MIL-STD-881C)
ACWS Automated Information System (AIS). The set of enterprise elements, equipment (hardware), software, legacy systems, users, business rules, data, and facilities required to develop and/or configure, test, and deploy ACWS.
1.1
1.1
Prime Mission Product
The hardware, software, and associated effort used to analyze, design, integrate, and test all elements.
1.1.1
1.1.1
Custom Application Software 1…n
This element includes all the hardware, software, and associated effort needed to analyze, design, build, and test a custom-only (no COTS) software application, at the system developer’s site, to fulfill a capability gap not implemented within procured software packages. (COTS, combined with custom software is captured under Enterprise Service Element Software Item (1...n), WBS 1.1.2). Excludes, for example, software development necessary for external system interfaces (see WBS 1.1.4).
1.1.1.1
1.1.1.x
Custom Application Software Hardware
This element includes all the associated hardware equipment needed to analyze, design, build, and test the "custom application software" element at the system developer’s site to fulfill a capability gap not captured by the procured software packages. Use lower levels to identify individual hardware items (servers, routers, etc.). Includes, for example, development and test hardware. Excludes, for example, deployment hardware at each operational site.
1.1.1.2
1.1.1.x
Custom Application Software Component
This element includes the custom application software to be developed. For each custom application software element to be developed, insert a description of the element here. Note that this item is currently a placeholder for custom application software and will be replaced once custom applications are identified as a result of engineering and architecture analysis and design. See note 1.
1.1.1.3
1.1.1.x
Custom Application Software Integration, Assembly, Test, and Checkout
This element includes the Subsystem Software Integration, Assembly, Test and Checkout for custom components, specifically, the effort and material associated with integrating and testing subsystem software items and hardware of an individual (or group of) subsystem software application that have undergone individual Item qualification test.
Excludes, for example, Software development efforts necessary for external system interfaces.
1.1.2
1.1.2
Enterprise Service Element 1…n
This element includes all the hardware, software, and associated effort needed for developing functionality or software services. These elements are considered unassociated, loosely coupled units of functionality that do not have calls to each other embedded in them. These services can be integrated or used by several organizations, even if their respective client systems are substantially different.
Includes, for example, reports; interfaces; configurations; extensions; forms; workflow; enterprise service management (monitoring, fault management); service discovery; metadata discovery; mediation; service security; content discovery and delivery; federated search; enterprise catalog service; data source integration; text collaboration (chat, instant messaging); white boarding and annotation; application sharing; application broadcasting; virtual spaces; identity management.
1.1.2.1
1.1.2.x
Enterprise Service Element Hardware
This element includes all the hardware needed for developing functionality or software services that are unassociated, loosely coupled units of functionality that do not have any calls to each other embedded in them. These services can be integrated or used by several organizations, even if their respective client systems are substantially different.
1.1.2.2
1.1.2.x
Enterprise Service Element Software
This element includes all the software needed for developing functionality or software services that are unassociated, loosely coupled units of functionality that do not have any calls to each other embedded in them. These services can be integrated or used by several organizations, even if their respective client systems are substantially different.
See note 2.
1.1.2.3
1.1.2.x
Enterprise Service Element Integration, Assembly, Test, and Checkout
This element includes all the associated efforts needed for developing functionality or software services that are unassociated, loosely coupled units of functionality that do not have any calls to each other embedded in them. These services can be integrated or used by several organizations, even if their respective client systems are substantially different.
1.1.3
1.1.3
Enterprise Information Systems 1…n
This element includes all the hardware equipment and effort to plan, analyze, design, build, and test functionality(s) of an enterprise information system that uses an integrated database to support typical business processes within business/functional areas and consistent information access across areas and systems. Includes, for example, enterprise resource planning, enterprise data warehouse, data mart, and operational data store. Excludes, for example: general ledger, accounts payable, revenue and accounts receivable, funds control and budgetary accounting, cost management, financial reporting, and real property inventory and management.
1.1.3.1
1.1.3.x
Business Area Hardware
This element includes all the associated hardware equipment needed at the system developer’s facility for planning, analyzing, designing, building, and testing functionalities that can be attributed, in whole or in-part, to a specific functional/business area or module within the EIS system. Use lower levels to identify individual hardware items. Includes, for example, development and test hardware. Excludes, for example: deployment hardware at each operational site.
1.1.3.2
1.1.3.x
Business Area Software
This element includes all the associated effort needed at the system developer’s facility for planning, analyzing, designing, building, and testing functionalities that can be attributed, in whole or in-part, to a specific functional/business area or module within the EIS system. See note 3.
1.1.3.3
1.1.3.x
Business Area Integration, Assembly, Test, and Checkout
The element includes the effort and material associated with integrating and testing the required software and hardware of an individual (or group of) Business Area Element(s).
1.1.4
1.1.4
External System Interface Development 1…n
The hardware equipment, software, and effort necessary for developing the set of software artifacts (threads, reports, queries, or scripts, or data export schemas) for a specific ACWS external system interface. Use lower levels to identify each specific external system interface that must be developed or modified.
Includes, for example, Design of the interface specification and the development of the interface. Excludes, for example: Data Migration/Cleansing NOTE: An external system interface is required for proper transmission of data and/or control between the AIS solution and separate systems for which a mutual dependency exists.
1.1.4.1
1.1.4.x
External Interface Hardware
The hardware equipment necessary for developing the set of software artifacts (threads, reports, queries, or scripts, or data export schemas) for a specific ACWS external system interface.
1.1.4.2
1.1.4.x
External Interface Software
The software necessary for developing the set of software artifacts (threads, reports, queries, or scripts, or data export schemas) for a specific ACWS external system interface. See note 4.
1.1.4.3
1.1.4.x
External Interface Integration, Assembly, Test, and Checkout
The other efforts necessary for developing the set of software artifacts (threads, reports, queries, or scripts, or data export schemas) for a specific ACWS external system interface.
1.1.5
1.1.5
AIS Platform Hardware
This element includes all effort and equipment to develop a hardware system to host the deliverable ACWS software.
1.1.6
1.1.6
System Level Integration
This element includes all effort and equipment to assemble, integrate, and test all elements as a whole at the system developer’s facility.
1.2
1.2
System Engineering
This element identifies the technical and management efforts of directing and controlling the integrated engineering effort of ACWS. Includes, for example, effort to define the system and the integrated planning and control of the technical program efforts of design engineering, specialty engineering, production engineering, and integrated test planning; effort associated with developing the Systems Engineering Management Plan (SEMP); effort to transform an operational need or statement of deficiency into a description of system requirements and a preferred system configuration; technical planning and control effort for planning, monitoring, measuring, evaluating, directing, and re-planning the management of the technical program; all “ility” programs, where applicable: value engineering, configuration management, Human Systems Integration (Human Factors Engineering; Personnel; Habitability; Manpower; Training; Environment, Safety and Occupational Health; Survivability), vulnerability, maintainability, reliability, standardization, system analysis, logistic support analysis, etc.; technical baseline management and event based technical reviews with independent subject matter expertise participation; cross product IPT integration; survivability/vulnerability analysis; and System of Systems (SoS) and System Level architecting, modeling and simulation, verification and validation and external interface definition and management. Excludes, for example, actual design engineering and the production engineering directly related to the WBS element with which it is associated.
1.2.1
1.2.1
Contractor System Engineering
Specific System Engineering (see 1.2) activities to be performed by a system engineering contractor. The contractor will provide its own sub-elements under this WBS element.
1.2.2
Not included in Government CSDR Plan WBS
Government System Engineering
Specific System Engineering (see 1.2) activities to be performed and/or managed directly by the Government.
1.3
1.3
Program Management
The business and administrative planning, organizing, directing, coordinating, controlling, and approval actions designated to accomplish overall program objectives, which are not associated with specific hardware elements and are not included in systems engineering. Includes, for example:
a. Cost, schedule, performance measurement management, warranty administration, contract management, data management, vendor liaison, subcontract management, etc.
b. Support element management, defined as the logistics tasks management effort and technical control, and the business management of the support elements. The logistics management function encompasses the support evaluation and supportability assurance required to produce an affordable and supportable defense materiel system.
c. Planning and management of all the functions of logistics. Examples are: maintenance support planning and support facilities planning; other support requirements determination; support equipment requirements determination; supply support; packaging, handling, storage, and transportation; provisioning requirements determination and planning; training system requirements determination; computer resource determination; organizational, intermediate, and depot maintenance determination management; and data management.
1.3.1
1.3
Government Program Management
This element includes specific Program Management (see 1.3) activities to be performed and/or managed directly by the Government.
1.3.2
1.3
Contractor Program Management
This element includes specific Program Management (see 1.2) activities to be performed by a system engineering and/or development contractor. The contractor will provide its own sub-elements under this WBS element.
1.4
1.4
Change Management
This element includes the process and activities necessary for managing organizational change. Change management encompasses planning, oversight or governance, project management, testing and implementation. Change management is a structured approach to shifting/transitioning individuals, teams, and organizations from a current state to a desired future state. It is an organizational process aimed at helping employees to accept and embrace changes in their current business environment. In project management, change management refers to a project management process where changes to a project are formally introduced and approved.
1.4.1
1.4.1
Change Management Planning
This element includes identification of the sequence of steps or activities that a change management team or project leader would follow to apply change management to a project. The objective of change management in this context is to ensure that standardized methods and procedures are used for efficient and prompt handling of all changes to control IT infrastructure, in order to minimize the number and impact of any related incidents upon service. Changes in the IT infrastructure may arise reactively in response to problems or externally imposed requirements, e.g. legislative changes, or proactively from seeking improved efficiency and effectiveness or to enable or reflect business initiatives, or from programs, projects, or service improvement initiatives.
1.4.2
1.4.2
Change Management Tools
This element includes tools used to perform change management.
1.5
1.5
System Test and Evaluation
This element included the use of pilot, prototype, production, or specifically fabricated hardware/ software to obtain or validate engineering data on ACWS during the developmental phase (normally funded from RDT&E) of the program. It also includes all effort associated with the development of any specialized tools or data in support of the system level test program. Includes, for example:
a. Detailed planning, conduct, support, data reduction and reports (excluding the contract data requirements list data) from such testing, and test articles that are functionally configured to represent and test subsystems/components of the defense materiel end item being developed or produced
b. Design and production of models, specimens, fixtures and instrumentation NOTE: Test articles that are functionally configured to represent and test the complete defense materiel end item being developed or produced, are excluded from this WBS element.
Excludes, for example, all formal and informal testing up through the subsystem level, which can be associated with the hardware/software element acceptance testing. Note that these excluded efforts are to be included with the appropriate hardware or software elements.
1.5.1
1.5.1
Development Test and Evaluation
This element includes the development test and evaluation activities conducted to evaluate design approaches, validate analytical models, quantify contract technical performance and manufacturing quality measure progress in system engineering design and development, minimize design risks, predict integrated system operational performance (effectiveness and suitability) in the intended environment, and identify system problems (or deficiencies) to allow for early and timely resolution or correction. Decision-makers use DT&E results to minimize design risk, whereas OT&E evaluated military utility, and system effectiveness and suitability. DT&E usually includes SI testing.
1.5.2
1.5.2
Operational Test and Evaluation
This element includes the operational test and evaluation activities conducted to validate the utility of the system to the user. The goal of OT&E is to evaluate operational effectiveness, suitability, and survivability of a DoD system. OT&E provides decision-makers with an independent, credible, clear, comprehensive, and valid evaluation. The OTAs have different levels of test events: Limited User Test (LUT), System Assessment (SA), and Operational Assessment (OA) in addition to the normal IOT&E and FOT&E. Each DT&E team maybe involved in supporting each event. These test events are managed by the Operational Test Agency (OTA). OTE events are conducted in as realistic an operational environment as possible to estimate the prospective system's utility. In addition, operational test and evaluation provides information on organization, personnel requirements, doctrine, and tactics.
1.5.3
1.5.3
Human Systems Integration Labs (SILs)
This element includes establishing a lab environment that can be used in testing a new development, or in teaching personnel how to operate or maintain a system. A "SIL" refers to a facilities designed to test the performance and compatibility of components, subsystems and systems when they are integrated with other systems or functions.
1.5.4
1.5.4
Test and Evaluation Support
This element includes the personnel resources required to perform the activities identified in elements 1.5.1 to 1.5.3. Key areas to be addressed include survivability, reliability, interoperability, and Human System Integration.
1.5.5
1.5.5
Test Facilities
This element includes the facilities designed to test the performance and compatibility of components, sub-systems, or systems when they are integrated with other functions or systems. Facilities include building(s), hardware, data, power, air-conditioning, connections, necessary T&E support services, and all other considerations at one or more physical sites to enable testing as planned.
1.5.6
1.5.6
Test Tools
This element includes the tools associated with performing any tests.
1.5.7
1.5.4
Test and Evaluation Travel
This element includes any travel associated with Government test support.
1.6
1.6
Training
This element includes the delivery of training services, devices, accessories, aids, equipment, and parts used to facilitate instruction through which personnel will learn to operate and maintain the system with maximum efficiency. Includes, for example, all effort associated with the design, development, and production of deliverable training equipment and its associated software as well as the execution of training services. Excludes, for example, overall planning, management, and task analysis in the WBS elements for systems engineering and program management.
1.6.1
1.6
Equipment
This element includes the delivery of distinct end items of training equipment required to meet specific training objectives. Includes, for example, operational trainers, maintenance trainers, and other items such as cutaways, mock-ups, and models (e.g., Operational Instructional Equipment, Maintainer Instructional Equipment).
1.6.2
1.6
Services
This element includes the delivery of training services, accessories, and aids necessary to accomplish the objectives of training. Includes, for example:
a. Training course materials; contractor-conducted training (in-plant and service training); and the materials and curriculum required to design, execute, and produce a contractor developed training program. (e.g., Operator Instructional Software, Maintainer Instructional Software)
b. Materiel, courses, and associated documentation (primarily the computer software, courses and training aids) Excludes, for example: Deliverable training data associated with the WBS element support data.
1.6.3
1.6
Facilities
This element is not applicable to the projected ACWS solution. This element identifies the special construction necessary to accomplish training objectives. Includes, for example, modification or rehabilitation of existing training facilities and infrastructure used to accomplish training objectives. Excludes, for example: installed equipment used to acquaint the trainee with the system or establish trainee proficiency; and the brick and mortar-type facilities identified as industrial facilities.
1.7
1.7
Data
This element includes the deliverable data required to be listed on a contract data requirements list, DD Form 1423. Includes, for example:
a. Only such effort that can be reduced or avoided if the data item is eliminated
b. Government-peculiar data; acquiring, assembling, reproducing, packaging and shipping the data
c. Transforming data into Government format, reproducing and shipping data identical to that used by the contractor but in a different format.
1.7.1
1.7.1
Technical Publications
This element includes technical data formatted into a technical document. Data may be presented in any form regardless of the form or method of recording. Includes, for example, program documents, operation and maintenance instructions, parts lists or parts breakdown, and related technical information or procedures exclusive of administrative procedures; and data item descriptions (DIDs).
1.7.2
1.7.2
Engineering Data
This element includes recorded scientific or technical information (regardless of the form or method of recording) and computer software documentation. Engineering data defines and documents an engineering design or product configuration (sufficient to allow duplication of the original items) and is used to support production, engineering, and logistics activities. Includes, for example, all final plans, procedures, reports, and documentation pertaining to systems, subsystems, computer, and computer resource programs, component engineering, operational testing, human factors, reliability, availability, and maintainability, and other engineering analysis; and technical data package (re-procurement package), which includes all engineering drawings, associated lists, process descriptions, and other documents defining physical geometry, material composition, and performance procedures.
1.7.3
1.7.3
Management Data
This element includes the data items necessary for configuration management, cost, schedule, contractual data management, program management, etc., required by the Government. Includes, for example, contractor cost reports, cost performance reports, contract funds status reports, schedules, milestones, networks, integrated support plans.
1.7.4
1.7.4
Support Data
The data items designed to document support planning in accordance with functional categories. Includes, for example, Supply; general maintenance plans and reports; training data; transportation, handling, storage, and packaging information; facilities data; data to support the provisioning process and all other support data; and software supportability planning and software support transition planning documents. Program Management team should identify the products within this element at the next lowest (level 3) WBS level. (Note that no placeholder products have so far been identified for this element.)
1.7.5
1.7.5
Data Depository
This element includes the entity, including storage requirements, designated to act as custodian to maintain a master engineering specification and establish a drawing repository service for Government approved documents that are the property of the U.S. Government. As custodian for the Government, the repository, authorized by approved change orders, maintains master documents at the latest approved revision level. This distinct entity may hold electronic or hard copy data. Includes, for example, all effort necessary to maintain documents. Excludes, for example: all similar effort in support of its engineering and production activities.
1.8
1.8
Peculiar Support Equipment
This includes the design, development, and production of deliverable items and associated software required to support and maintain the system or portions of the system while the system is not directly engaged in the performance of its mission, and which are not common support equipment. Includes, for example: vehicles, equipment, tools, etc., used to fuel, service, transport, hoist, repair, overhaul, assemble, disassemble, test, inspect, or otherwise maintain mission equipment; any production of duplicate or modified factory test or tooling equipment delivered to the Government for use in maintaining the system; and any additional equipment or software required to maintain or modify the software portions of the system. Excludes, for example: overall planning, management and task analysis functions inherent in the WBS elements for Systems Engineering and Program Management; and common support equipment, presently in the DoD inventory or commercially available, bought by the using command, not by the acquiring command.
1.8.1
1.8
Test and Measurement Equipment
This element includes the peculiar or unique testing and measurement equipment that allows an operator or maintenance function to evaluate operational conditions of a system or equipment by performing specific diagnostics, screening, or quality assurance effort at an organizational, intermediate, or depot level of equipment support. Includes, for example, test measurement and diagnostic equipment, precision measuring equipment, automatic test equipment, manual test equipment, automatic test systems, test program sets, appropriate interconnect devices, automated load modules, firmware and support hardware . Used at all levels of maintenance; and packages or similar items to be diagnosed using automatic test equipment.
1.8.2
1.8
Support and Handling Equipment
This element includes tools and handling equipment used for support of the mission system. Includes, for example, ground support equipment, vehicular support equipment, powered support equipment, non-powered support equipment, munitions material handling equipment, material handling equipment, and software support equipment (hardware and software).
1.9
1.9
Common Support Equipment
This element includes the items required to support and maintain the system or portions of the system while not directly engaged in the performance of its mission, and which are presently in the DoD inventory for support of other systems. Includes, for example, acquisition of additional quantities of this equipment needed to support the item; and all efforts required to assure the availability of this equipment to support the item.
1.9.1
1.9
Test and Measurement Equipment
This element includes the common testing and measurement equipment that allows an operator or maintenance function to evaluate operational conditions of a system or equipment by performing specific diagnostics, screening, or quality assurance effort at an organizational, intermediate, or depot level of equipment support. Includes, for example, test measurement and diagnostic equipment, precision measuring equipment, automatic test equipment, manual test equipment, automatic test systems, test program sets, appropriate interconnect devices, automated load modules, firmware and support hardware . Used at all levels of maintenance; and packages or similar items to be diagnosed using automatic test equipment.
1.9.2
1.9
Support and Handling Equipment
This element includes the tools and handling equipment used for support of the mission system. Includes, for example, ground support equipment, vehicular support equipment, powered support equipment, non-powered support equipment, munitions material handling equipment, material handling equipment, and software support equipment (hardware/software).
1.10
1.10
Operational/Site Activation
This element includes all deployment hardware and software, user documentation, site survey, site activation, user training, data migration, management/engineering support, and interim logistics support to achieve operational status.
1.10.1
1.10.1
Deployment Hardware and Software
This element includes all deployment software, user documentation, site survey, site activation, user training, data migration, management/engineering support, and interim logistics support to achieve operational status; and all deployment hardware to achieve operational status.
1.10.2
1.10.2
User Documentation
This element includes the development of user documents, tutorials, online help, etc. that describe each feature of the new system being deployed and assists the user in realizing these features.
1.10.3
1.10.3
Site Activation
This element includes the preparation of a site to perform its assigned or intended function.
1.10.4
1.10.4
User Training
This element includes providing training to end users to successfully make the transition to the newly deployed hardware and software. This includes setting training goals, creating a training plan, assessing the end user needs and training delivery methods and creating and delivering the training program to all end users. The training should cover all aspects of the newly deployed hardware and software and related processes and policies.
1.10.5
1.10.5
Data Migration
This element includes the transferring data between storage types, formats, or systems. Data from legacy systems is mapped to the new system and includes data extraction and data loading, relating old formats to the new system formats and requirements, data verification to determine whether data was accurately and completely translated. Any areas of disparity should be identified and fixed.
1.10.6
1.10.6
Management/Engineering Support
This element includes the technical and management efforts of directing and controlling the integrated engineering effort of the system for the given site.
Includes, for example, effort to define the system and the integrated planning and control of the technical program efforts of design engineering, specialty engineering, production engineering, and integrated test planning; effort to transform an operational need or statement of deficiency into a description of system requirements and a preferred system configuration; technical planning and control effort for planning, monitoring, measuring, evaluating, directing, and re-planning the management of the technical program; all 'ility programs, where applicable: value engineering, configuration management, Human Systems Integration (Human factors engineering; Personnel; Habitability; Manpower; Training; Environment, Safety and Occupational Health; Survivability), vulnerability, maintainability, reliability, standardization, system analysis, logistic support analysis, etc.; technical baseline management and event based technical reviews with independent subject matter expertise participation; cross product IPT integration; survivability/vulnerability analysis; and System of Systems (SoS) and System Level Architecting, modeling and simulation, verification and validation and external interface definition and management.
1.10.7
1.10.7
Interim Logistics Support
This element includes labor, material, and assets used in providing temporary logistics support for the deployed service delivery sites until long-term operations and maintenance capability is established.
1.11
1.11
Industrial Facilities
This element includes the construction, conversion, or expansion of industrial facilities for production, inventory, and contractor depot maintenance required when that service is for the operation of the system. Includes, for example, equipment acquisition or modernization, where applicable; maintenance of these facilities or equipment; and industrial facilities for hazardous waste management to satisfy environmental standards. Excludes, for example: capital equipment.
1.11.1
1.11
Construction/Conversion/Expansion
This element includes the real estate and preparation of system peculiar industrial facilities for production, inventory, depot maintenance, and other related activities.
1.11.2
1.11
Equipment Acquisition or Modernization
This element includes the production equipment acquisition, modernization, or transferal of equipment for the system. This pertains to Government owned and leased equipment under facilities contract.
1.11.3
1.11
Maintenance (Industrial Facilities)
This element includes the maintenance, preservation, and repair of industrial facilities and equipment.
1.12
1.12
Initial Spares and Repair Parts
This element includes the delivery of spare components, assemblies, and subassemblies used for initial replacement purposes in the materiel system equipment end item. Includes, for example, repairable spares (repairable) and repair parts required as initial stockage to support and maintain newly fielded systems or subsystems during the initial…
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 .