W9124R24R0004_RFP_EXHIBIT_A_CDRLS.pdf
PDF 1 MB Posted
- Solicitation number
- W9124R-24-R-0004
About this file
This document is a Contract Data Requirements List (DD Form 1423) that specifies the data item requirements for contract W9124R-24-R-0004 for Yuma Proving Ground Mission Test Support Services.
The key details are: The contract requires the contractor to provide a Position Description data item (DI-MGMT-81991 tailored) as needed. This data item is categorized as "OTHER" and supports the Materiel Test Support Services (MTSS) system. The contractor must submit the Position Description data item within 60 days after contract award, and then as required thereafter. The Government will review and provide comments within 3 business days, and the contractor shall revise and resubmit within 1 business day if required. The data item shall be submitted via encrypted email to the Contracting Officer Representative and Procuring Contracting Officer.
View the file
Other files
Show all 41
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.
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 |
| DI: |
| Click on this button to attach a file(s).: |
| A. CONTRACT LINE ITEM NUMBER: 0006,1006 ,2006 |
| exhibit: A |
| 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: MTSS |
| ContractNum: TBD |
| Contractor: TBD |
| 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 |
| titleDataItem: Key Personnel Identification/Substitution |
| titleDataItem: Recall Roster |
| titleDataItem: Continuous Process Improvement |
| titleDataItem: Weekly Performance |
| titleDataItem: Cost Allocations Report (CIMS) |
| titleDataItem: Manning |
| titleDataItem: Cost Accounting Reports |
| titleDataItem: Quality Control |
| titleDataItem: Quality Deficiency Report |
| titleDataItem: Procurement Report |
| titleDataItem: New Employee Clearance Report |
| titleDataItem: Departing Employee Clearance Report |
| titleDataItem: Physical Security Plan |
| titleDataItem: Key Control |
| titleDataItem: Accident Report |
| titleDataItem: Safety Training Plan |
| titleDataItem: Range Safety Standard Operating Procedure |
| titleDataItem: Training, Qualification, and Certification |
| titleDataItem: Training Report |
| titleDataItem: Travel Report |
| titleDataItem: Contingency Plan |
| titleDataItem: Property Management System Procedures (PMSP) |
| titleDataItem: Government Furnished Property Annual Inventory |
| titleDataItem: Final Government Furnished Property Inventory |
| titleDataItem: Government Furnished Property Activity Report |
| titleDataItem: Government Owned Vehicles / NTV Utilization Report |
| titleDataItem: Position Description |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: Weekly Performance Report |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: N/A |
| subtitle: Quality Manual (QM) |
| 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: Government Property (GP), CAP, Inventory and Usage Re |
| subtitle: Government Property (GP), CAP, Inventory and Usage Re |
| subtitle: Government Property (GP), CAP, Inventory and Usage Re |
| subtitle: Government Property (GP), CAP, Inventory and Usage Re |
| subtitle: N/A |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-81834A |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-81834A |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-81996 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-81991 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-FNCL-80165A |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-81991 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-FNCL-80165A |
| 4. AUTHORITY (Data Acquisition Document Number): DI-QCIC-81722 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-QCIC-80736 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-80441D |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MISC-81419 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MISC-81419 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-82189 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-82188 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-82188 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-SAFT-82193 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-SAFT-80589 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-SESS-81521 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-82350 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MISC-81366 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-SAFT-82193 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-80004A |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-80442(T) |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-80442 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-80442 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MISC-81107 |
| 4. AUTHORITY (Data Acquisition Document Number): DI-MGMT-81991 |
| contractRef: PWS 1.4.10 |
| contractRef: PWS 1.4.11 |
| contractRef: PWS 1.6.5 |
| contractRef: PWS 1.6.11 |
| contractRef: PWS 1.6.12 |
| contractRef: PWS 1.6.14 |
| contractRef: PWS 1.6.15 |
| contractRef: PWS 1.7.1 |
| contractRef: PWS 1.7.2 |
| contractRef: PWS 1.9.4 |
| contractRef: PWS 1.10.4 |
| contractRef: PWS 1.10.10 |
| contractRef: PWS 1.10.13 |
| contractRef: PWS 1.10.14 |
| contractRef: PWS 1.16 |
| contractRef: PWS 1.17.2 |
| contractRef: PWS 1.17.4 |
| contractRef: PWS 1.22.5 |
| contractRef: PWS 1.22.6 |
| contractRef: PWS 1.23.4 |
| contractRef: PWS 1.24 |
| contractRef: PWS 3.1.5 |
| contractRef: PWS 3.1.15 |
| contractRef: PWS 3.1.17 |
| contractRef: PWS 3.1.20 |
| contractRef: 3.2.2 |
| contractRef: 1.16.17 |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| reqOffice: ATEC/YPG |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 7. DD 250 REQUIREMENT: LT |
| 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: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: B |
| 9. DISTRIBUTION STATEMENT REQUIRED: B |
| 9. DISTRIBUTION STATEMENT REQUIRED: B |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: A |
| 9. DISTRIBUTION STATEMENT REQUIRED: A |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: C |
| 9. DISTRIBUTION STATEMENT REQUIRED: B |
| 9. DISTRIBUTION STATEMENT REQUIRED: B |
| 9. DISTRIBUTION STATEMENT REQUIRED: B |
| 9. DISTRIBUTION STATEMENT REQUIRED: B |
| 9. DISTRIBUTION STATEMENT REQUIRED: B |
| 9. DISTRIBUTION STATEMENT REQUIRED: B |
| freq: ASREQ |
| freq: ASREQ |
| freq: ASREQ |
| freq: Weekly |
| freq: WKLY |
| freq: Bi-WKLY |
| freq: Bi-WKLY |
| freq: ONE/R |
| freq: As REQD |
| freq: MTHLY |
| freq: WKLY |
| freq: WKLY |
| freq: AS REQD |
| freq: AS REQD |
| freq: AS REQD |
| freq: ASREQ |
| freq: ASREQ |
| freq: ANNLY |
| freq: MTHLY |
| freq: MTHLY |
| freq: ASREQ |
| freq: SEE BLOCK 16 |
| freq: SEE BLOCK 16 |
| freq: SEE BLOCK 16 |
| freq: SEE BLOCK 16 |
| freq: WKLY |
| freq: AS REQD |
| asOfDate: N/A |
| asOfDate: 2024-07-03 |
| 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: See attached |
| 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: 30 Days Prior to Performance |
| dateFirstSub: 30 Days Prior to Performance |
| dateFirstSub: 5 DARO |
| dateFirstSub: COB 2nd BD ARO |
| dateFirstSub: ARO |
| dateFirstSub: ARO |
| dateFirstSub: ARO |
| dateFirstSub: 30 days ARO |
| dateFirstSub: SEE BLK 16 |
| dateFirstSub: SEE BLK 16 |
| dateFirstSub: See BLK 16 |
| dateFirstSub: See BLK 16 |
| dateFirstSub: SEE BLOCK 16 |
| dateFirstSub: SEE BLOCK 16 |
| dateFirstSub: SEE BLOCK 16 |
| dateFirstSub: See block 16 |
| dateFirstSub: SEE BLK 16 |
| dateFirstSub: SEE BLK 16 |
| dateFirstSub: SEE BLOCK 16 |
| dateFirstSub: SEE BLOCK 16 |
| dateFirstSub: See block 16 |
| dateFirstSub: SEE BLOCK 16 |
| dateFirstSub: SEE BLOCK 16 |
| dateFirstSub: SEE BLOCK 16 |
| dateFirstSub: SEE BLOCK 16 |
| dateFirstSub: WKLY |
| dateFirstSub: 60 days ARO |
| dateSubseqSub: 30 Days Prior to Substitution |
| dateSubseqSub: 30 Days Prior to Substitution |
| dateSubseqSub: ASREQ |
| dateSubseqSub: COB 2nd BD Weekly |
| dateSubseqSub: Weekly |
| dateSubseqSub: Bi-WKLY |
| dateSubseqSub: Bi-WKLY |
| dateSubseqSub: ASREQ |
| dateSubseqSub: As REQD |
| dateSubseqSub: MTHLY |
| dateSubseqSub: See BLK 16 |
| dateSubseqSub: See BLK 16 |
| dateSubseqSub: AS REQD |
| dateSubseqSub: AS REQD |
| dateSubseqSub: AS REQD |
| dateSubseqSub: ASREQ |
| dateSubseqSub: ASREQ |
| dateSubseqSub: ANNLY |
| dateSubseqSub: MTHLY |
| dateSubseqSub: MTHLY |
| dateSubseqSub: ASREQ |
| dateSubseqSub: AS REQD |
| dateSubseqSub: SEE BLOCK 16 |
| dateSubseqSub: SEE BLOCK 16 |
| dateSubseqSub: SEE BLOCK 16 |
| dateSubseqSub: WKLY |
| dateSubseqSub: AS REQD |
| 16. REMARKS: BLKS 10: ASREQ = As Required |
BLK 12: Provide the first submission 30 Days Prior to Performance. The Government will provide either approval or comments within 5 business days after delivery of CDRL. If no response is received from the Government, approval is assumed after this timing. The KTR shall have 3 days to respond to any comments. Upon receipt of re-delivery, the Government timing remains the same.
13: 30 Days Prior to Substitution
BLK 14 A: Submission shall be via electronic mail (e-mail) to the contract COR and Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
IAW with DI-MGMT-81834A contractor format is acceptable.
Ensure data is complete for the following positions:
• Contract Manager
• Alternate Contract Manager
• Safety Manager
16. REMARKS: BLK 10:
ASREQ = As Required BLKS 12: 5 Days after receipt of an order under the contract.
BLKS 13: ASREQ = As Required
BLK 14 A.: Submission shall be via electronic mail (e-mail) to the contract COR, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.
IAW with DI-MGMT-81834A contractor format is acceptable as long as it is in excel and editable.
Ensure data is complete for the following:
The Contractor shall provide name, address, and telephone number for both the designated and alternate representative(s) to the KO and COR within 5 business days following contract award (Deliverable R-02). The Contractor shall verbally notify the KO and COR of changes as they occur and provide written changes no later than 24 hours after effective date of the change. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: Contractor format is acceptable and shall be delivered as a PDF.
BLK 8: The report shall be submitted 30 days after full contract performance. CORs will review and provide feedback 5 calendar days following receipt of initial submission. The contractor shall address all issues within 14 calendar days following receipt feedback. Upon COR approval, the PCO shall provide the contractor with a documented notification of QPP approval. Following initial Government approval, the contractor shall submit any modifications to the Quality Control Plan to the CORs for approval in accordance with the initial approval process in this CDRL. The Government will provide comments within 10 business days after signature of Modification P00004. The contractor shall then address Government comments within 30 business days.
BLK 10: ONE/R = One Time with Revisions
BLK 13: ASREQ = As Required
BLK 14 A.: Submission shall be via electronic mail (e-mail) to the contract COR, and Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: DI-MGMT-81991 is tailored as follows:
Paragraph 1 - Delete Figure 1, 2 and 3.
Contractor format is acceptable as long as it is in excel and editable.
Paragraph 2.5 - DELETE.
Paragraph 2.6 - Replace Figure 1,2,3 for MTSS Figures Paragraph 2.7 through 3.3 - DELETE.
Ensure data includes the following:
Labor data (direct, indirect, maintenance, etc.), and other cost (procurement & sub-contract costs), shall be made available in cost center, account code, and overall summary formats to the COR and the Budget Officer. Reports shall be submitted by COB the second business day of each week.
Block 14 - Submission shall be via electronic mail (e-mail) to the contract COR, Budget Officer, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil. Email submissions to the Budget Officer should be sent to usarmy.ypg.atec.list.rm-mission-budget@army.mil.
16. REMARKS:
DI-FNCL-80165A is tailored as follows:
Paragraph 2 - Delete The Cost Breakdown Structure Summary Report shall be prepared using the DD Form 2417, See Figure 1. Replace with: The Cost Allocation Report shall be web-based and in contractor’s format.
Government provided format via CIMS website.
Ensure data includes the following:
Labor cost data shall be uploaded to the Resource Management system no later than 1300 hours the second business day of each week utilizing the following fields: Date of performance, Receiving Cost Object 1 (WBS Element), Receiving Cost Object 2 (Internal Order), Contract Number, Work Order Number (PWS paragraph), Sub-CLIN, ACRN, Wage Determination Code, Employee ID, Employee First Name, Employee Middle Name, Employee Last Name, Regular Hours or Overtime Hours.
BLK 8: The Government will review and provide comments no later than three business days from receipt of IMS. The contractor shall revise and resubmit within one business days of receipt of Government comments, if required.
BLKS 10: WKLY = Weekly BLKS 13: Labor – no later than 1300 hrs on 2nd business day of each week. Non-Labor – no later than 1300 hrs on the 3rd business day of each week.
BLK 14 A: Submission shall be via CIMS (web based). In the event of web suite unavailability contact the Budget Officer, the COR and Procuring Contracting Officer. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil. Email submissions to the Budget Officer should be sent to usarmy.ypg.atec.list.rm-mission-budget@army.mil.
16. REMARKS: DI-MGMT-81991 is tailored as follows:
Paragraph 1 - Delete Figure 1, 2 and 3.
Contractor format is acceptable as long as it is in excel and editable.
Ensure data includes the following:
A level of effort report titled “BI-Weekly Manning” shall be made available to the COR in a spreadsheet format. Each functional area’s manning as it appears at the end of the two-week cycle will be reported with each bi-weekly invoice (by COB the first Tuesday of the following cycle). The report is to distinguish between personnel assigned to an area, cross-utilized from/to an area, and those in an inactive status. The attached notes will describe the reasons for changes, the inactive category each inactive employee is being carried in and give a heads-up on projected changes. Organization structure will be submitted during the Phase-in (see sections 1.25) and updated as needed throughout the contract. A phone roster shall be submitted in excel format quarterly.
BLK 8: The Government will review and provide comments no later than three business days from receipt of IMS. The contractor shall revise and resubmit within one business days of receipt of Government comments, if required.
BLKS 10: WKLY = Weekly BLKS 13: By COB the second business day of each week BLK 14 A: Submission shall be via electronic mail (e-mail) to the contract COR, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: DI-FNCL-80165A is tailored as follows:
Paragraph 2 - Delete The Cost Breakdown Structure Summary Report shall be prepared using the DD Form 2417, See Figure 1. Replace with: The Cost Allocation Report shall be web-based and in contractor’s format.
Contractor format is acceptable as long as it is in excel and editable.
Ensure data includes the following:
The Contractor shall provide roll-up and detail reports in a spreadsheet format which substantiates each BI-weekly invoice, due by COB the first Tuesday of the following cycle.
BLK 8: The Government will review and provide comments no later than three business days from receipt. The contractor shall revise and resubmit within one business days of receipt of Government comments, if required.
BLKS 10: Bi-WKLY = Bi-Weekly BLKS 13: Due by COB on 2nd business day bi- week.
BLK 14 A: Submission shall be via electronic mail (e-mail) to the contract COR, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: BLK 4: DI-QCIC-81722 is tailored to the following:
Use and Relationship is revised
Inspection Program - Included shall be a quality control inspection program covering all general and specific tasks included in the contract scope of work. It shall specify tasks or areas to be inspected on a scheduled or unscheduled basis, the manner in which inspections are to be conducted, the titles of the individuals who will perform the inspections, and the percentage of the work that will be inspected on a recurring basis. In developing this inspection program, the Contractor shall identify the key activities and associated characteristics in each process that have a significant influence on specific services and provide for methods for evaluation of the selected characteristics.
Deficiency Identification - The QCP shall include a method of identifying deficiencies in the quality of services performed before the level of performance becomes unacceptable as defined in the PRS. This shall contain processes for corrective action without dependence upon Government direction. The Contractor shall report significant events having negative test mission impact.
Deficiency Correction - The program shall contain process control and process performance measurement procedures that shall include how the Contractor shall implement preventive corrective actions. The Contractor shall demonstrate that it has designed quality into the delivery of services thereby mitigating the risk(s) associated with delivery of deficient or nonconforming services.
Documentation and Enforcement - The QCP shall include a method of documenting and enforcing quality control operations of both prime contractor and subcontractor work, including inspection and testing.
Trend Analysis - The QCP shall include a method of performing trend analysis and assessments through the use of metrics.
Surveillance Methods - The QCP shall contain specific surveillance techniques for all contract services. The surveillance methods shall be comprehensive and adaptable to the reporting system of the plan.
Contractor format is acceptable as long as it is submitted in pdf.
BLK 8: CORs will review and provide feedback 30 calendar days following receipt of initial submission. The contractor shall address all issues within 14 calendar days following receipt feedback. Upon COR approval, the PCO shall provide the contractor with a documented notification of QCP approval. Following initial Government approval, the contractor shall submit any modifications to the Quality Control Plan to the CORs for approval in accordance with the initial approval process in this CDRL. The Government will provide comments within 10 business days after signature of Modification P00004. The contractor shall then address Government comments within 30 business days.
BLK 10: ONE/R = One Time with Revisions
BLK 13: ASREQ = As Required
BLK 14 A.: Submission shall be via electronic mail (e-mail) to the contract COR, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: The reporting system shall include Quality Deficiency Reports (QDR’s). Initial notification of a QDR will be reported via an email to the COR office NLT COB on the next business day (Deliverable R-07). Reports will include the five (5) W’s (What happened, Where did it happen, When did it happen, Who the POC is, and What mitigating/corrective action is being taken). The initial focus will be on timeliness; therefore, a report will not be delayed if the answer to one of the W’s is missing. A finalized, printable QDR will be made available to the CORs’ office within three (3) business days of deficiency identification.
Contractor format is acceptable as long as it is submitted on excel and editable or CVS.
BLKS 10: AS REQD = As Required
BLK 12: Initial notification NLT COB next business day. Finalized Report within 3 business days of occurrence. The Government will provide either approval or comments within 5 business days after delivery of CDRL. If no response is received from the Government, approval is assumed after this timing. The KTR shall have 5 days to respond to any comments. Upon receipt of re-delivery, the Government timing remains the same.
BLKS 13: AS REQD = As Required.
BLK 14 A.: Submission shall be via electronic mail (e-mail) to the contract COR, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: Contractor format is acceptable if it is submitted via editable excel. The Contractor shall provide a monthly report (Excel or CSV) to the COR by the 5th business day of each month (CDRL A010) that details all procurements for the previous month. The report shall include:
• Purchase Authorization Number
• Contractor Purchase Order (PO) Number
• Total dollar amount
• WBS number
• PWS paragraph name and number or Cost Center (if references PWS)
• Account ID
• Vendor Name
• Description of Items purchased
• Government Funder name
• CFE Yes or No
The contractor shall also include all Contractor Furnished Property (CFP) procurements as well as noted in the PWS at 4.1.
BLK 10: MTHLY = Monthly
BLK 12: The report shall be submitted the 5th day of each month.
BLK 13: MTHLY = Monthly
BLK 14 A.: Submission shall be via electronic mail (e-mail) to the contract COR, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: BLK 4: DI-MISC-81419 is tailored as follows:
Paragraph 10.2.1 – Deleted Paragraph 10.2.2 - Deleted Paragraph 10.2.4 – Deleted
Ensure to include the following:
A complete list of all new personnel shall be forwarded on a weekly basis, (Tuesdays by COB) (Deliverable R-09) to the Intelligence and Security Office with the following information (spreadsheet format): Name, social security number, job position, security clearance, investigation closed date, eligibility date, continuous evaluation date (other or deferred investigation)..
BLK 12: The Government will provide either approval or comments within 3 business day after delivery of CDRL. If no response is received from the Government, approval is assumed after this timing. The KTR shall have 1 day to respond to any comments. Upon receipt of re-delivery, the Government timing remains the same.
IAW DI-MISC-81419 Contractor format is acceptable as long as it is submitted on excel and editable.
BLK 13: Due by COB Tuesday weekly.
BLK 14 A: Submission shall be via electronic mail (e-mail) to the contract COR, YPG Intel and Security Office, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the YPG Intel and Security office should be sent to usarmy.ypg.atec.mbx.intelligence-and-security-office@army.mil. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: BLK 4: DI-MISC-81419 is tailored as follows:
Paragraph 10.2.1 – Deleted Paragraph 10.2.2 - Deleted Paragraph 10.2.4 – Deleted
Ensure to include the following:
All out-processing contractor employee CAC’s must be collected by the Contractor prior to COB on the last day the employee has cleared the installation. The contractor’s Out-Processing form and collected CACs shall be submitted to CORs on a weekly basis, Tuesdays by COB for revocation in the Mission Partner Identity Credentials and Access Management (MP ICAM) system. A COR will return collected CACs to responsible Govt. office The Intelligence and Security Office shall be notified of departing employees on a weekly clearance report for removal of security access.
BLK 12: The Government will provide either approval or comments within 3 business day after delivery of CDRL. If no response is received from the Government, approval is assumed after this timing. The KTR shall have 1 day to respond to any comments. Upon receipt of re-delivery, the Government timing remains the same.
IAW DI-MISC-81419 Contractor format is acceptable as long as it is submitted on excel and editable.
BLK 13: Due by COB Tuesday weekly.
BLK 14 A: Submission shall be via electronic mail (e-mail) to the contract COR, YPG Intel and Security Office, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the YPG Intel and Security office should be sent to usarmy.ypg.atec.mbx.intelligence-and-security-office@army.mil. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: BLK 4: DI-MGMT-82189 is tailored as follows:
Paragraph 2.1 C(5) replace with the following:
The Contractor shall develop and implement a Physical Security Plan IAW guidance contained in AR 190-13 (The Army Physical Security Program), AR 190-51 (Security of Unclassified Army Property), AR 190-11 (Physical Security of Arms, Ammunitions, and Explosives) and DOD 5100.76M (Physical Security of Sensitive Conventional AAE).
Ensure that the plan includes:
The Physical Security Plan shall include all government property and equipment furnished for the performance of the contract. The plan shall describe how the Contractor will prevent unauthorized access, vandalism, pilferage, larceny, and arson to all property and equipment that is provided for the performance of this contract. The Government shall not be responsible for damage to Contractor or contractor’s personnel’s supplies, materials, equipment, and property (personal or company provided) that are damaged or destroyed by fire, theft, vandalism, accidental means, or natural disaster.
The Contractor shall be responsible for keys provided by the Government. Keys shall not be duplicated except as authorized by USAYPG's Keys/Locks Custodian, nor shall they be used by unauthorized personnel. Procedures for safeguarding keys shall be included in the Physical Security Plan, and in compliance with AR 190-51, Appendix D
Contractor format is acceptable as long as it is submitted in pdf.
BLK 10: AS REQD = As Required
BLK 12: The Contractor shall submit the plan at the post-award conference or 30 calendar days prior to contract full performance, whichever comes first. The Government will make final review and request changes or provide acceptance of the Physical Security Plan. CORs will have 5 business days to review and provide comments to the KTR. The KTR shall have 5 days to respond to any comments. In the event changes are required, the Contractor shall submit changes to the Physical Security Plan to the Contracting Officer NLT 10 calendar days prior to the effective date of the change. The contractor shall not implement any changes without prior written approval of the Contracting Officer. Upon receipt of re-delivery, the Government timing remains the same.
BLK 13: AS REQD = As Required
BLK 14 A: Submission shall be via electronic mail (e-mail) to the contract COR, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: BLK 4: DI-MGMT-82188 is tailored as follows:
Paragraph 2.1 – Delete Paragraph 2.2 – Delete Paragraph 2.3 – Delete
Add:
The Contractor shall report any occurrence of duplicated, misplaced, or lost keys to the COR within 2 hours after discovery of occurrence and submit a finalized written report to the COR by close of business the next workday (Deliverable R-11). The written report shall provide complete details relating to duplication, misplaced key, or loss.
Contractor format is acceptable.
BLKS 10: AS REQD = As Required
BLK 12: Initial notification within 2 hours after discovery. Finalized report by COB next business day. The Government will provide either approval or comments within 3 business days after delivery of CDRL. If no response is received from the Government, approval is assumed after this timing. The KTR shall have 3 days to respond to any comments. Upon receipt of re-delivery, the Government timing remains the same.
BLKS 13: WEKLY = Weekly
BLK 14 A: Submission shall be via electronic mail (e-mail) to the contract COR, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: BLK 4: DI-MGMT-82188 is tailored as follows:
Paragraph 1: Format is deleted and replaced with: Contractor format is acceptable.
Figure 1 is deleted.
Ensure that the report:
Contractor shall comply with the reporting requirements of AR 385-40 and YPGR 385-1. Written reports for accident classes “A” through “D” shall be sent to USAYPG Safety Office, with a copy furnished to the COR. Immediate verbal notification (as required for class “A” and “B” accidents) will also be made to the same points of contact. For accidents beneath the formal reporting criteria (nonfatal injuries provided they do not result in a day or more time loss or are accompanied by property damage exceeding $4,999.99). The Contractor shall use their own form.
Notification to the USAYPG Command Group, Senior Commander’s, and the COR’s Office for all Commanders Critical Incident Review (CCIR) is required within the time limits established IAW USAYPG Commander’s Policy Statement No. 1M – USAYPG CCIR and Serious Information Reporting (SIR) Requirements
BLK 10: As REQD = As Required
BLK 12: The report shall be submitted 24 hours after incident. CORs will have 30 days to approve or reject the submission. Any COR requested revision of the report will be resubmitted within 7 days of CORs initial request for revision. The revisions will be reviewed within the same time frames as listed above.
BLK 13: AS REQD = As Required
BLK 14 A: Submission shall be via electronic mail (e-mail) to the contract COR, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: BLK 4: DI-SAFT-82193 is tailored as follows:
ADD: 1.19.1 The Contractor shall develop and implement a Safety Program IAW Occupational Safety and Health Act (OSHA), American National Standard Institute (ANSI), 29 CFR 1910.120, American Welding Society (AWS), USAYPG’s YP-YTRO-P-1000 SOP, YPGR 385-1, AR 385, AR 600-55, and AR 200-1 for the safety and well-being of personnel.
Ensure that the plan:
The plan shall incorporate the policies set forth in the 6.1M coded publications having titles containing the words: Protection, Prevention, Safety, and Certification. The plan shall:
• Meet applicable state and federal hazardous material regulations.
• Meet applicable state and federal environmental regulations.
• Contain pre-established incident handling and reporting procedures.
Contractor format is acceptable as long as it is submitted in pdf.
BLK 8: The Government will review and provide comments to technical manuals no later than thirty (30) business days from receipt. The Contractor shall revise and resubmit within fifteen (15) days after receipt of Government comments, if required. The material shall be delivered as a Microsoft Word (or compatible) document.
BLK 13: ASREQ = As Required. It shall be submitted to the KO ten (10) business days prior to commencing full performance (Deliverable P-05). Revisions shall be submitted three (3) business days prior to implementation.
BLK 14 A: Submission shall be via electronic mail (e-mail) to the contract COR, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: DI-SAFT-80589 is tailored as follows:
Contractor format is acceptable but shall be submitted as a PDF.
The Contractor shall develop and maintain their own range safety Standard Operating Procedure’s (SOP) subordinate to USAYPG’s YPY-RO-P-1000. In the event of a discrepancy, USAYPG’s YP-YTRO-P-1000 SOP takes precedence. The SOP shall be submitted to the KO and COR 30 calendar days after contract full performance.
BLK 10: ASREQ – As Required
BLK 12: Date of First Submittal is 30 Days after the required date for reaching Full Operational Capability. The Government will provide either approval or comments within 14 business days after delivery of CDRL. If no response is received from the Government, approval is assumed after this timing. The KTR shall have 14 days to respond to any comments. Upon receipt of re-delivery, the Government timing remains the same.
BLK 13: ASREQ = As Required
BLK 14 A: Submission shall be via electronic mail (e-mail) to the contract COR, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: DI-SESS-81521 is edited with the following:
Ensure that the plan includes the following:
This plan shall include, as a minimum:
• A detailed description of how the Contractor plans to establish and ensure a fully qualified work force throughout the life of the contract.
• Specific milestones, frequencies, or intervals as to when any training, qualification, or certification will occur.
• Specific methods and procedures as to how the training, qualification, or certification will be accomplished to include Plans of Instruction (POIs).
• Specific areas in which the training, qualification, or certification will be accomplished. Plan must include training in Combat Trafficking in Persons.
• The extent or level to which the training, qualification, or certification will be accomplished.
• The anticipated number and position of those personnel that will require training, qualification, or certification.
• The number and position of those personnel that will conduct training, qualification, and certification.
Contractor format is acceptable as long as it is submitted in pdf.
BLK 10: ANNLY = Annually
BLK 12: Date of First Submittal is 30 Days prior to reaching Full Operational Capability. The Government will provide either approval or comments within 3 business days after delivery of CDRL. If no response is received from the Government, approval is assumed after this timing. The KTR shall have 14 days to respond to any comments. Upon receipt of re-delivery, the Government timing remains the same.
BLK 13: ANNLY = Annually
BLK 14 A: Submission shall be via electronic mail (e-mail) to the contract COR, Procuring Contracting Officer, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite. Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: DI-MGMT-82350 shall be edited as follows:
Use/Relationship shall be replaced with the following:
The Contractor shall maintain history of training (Mandated, Internal and Certifications) in a database. A training report shall be submitted to the COR office by the 5th business day of the month.
Ensure that the report includes the following:
The Report shall be cumulative and shall include but not limited to reporting time period, queries by data field, and contain data that demonstrates compliance as follows:
• Government Mandated Annual Training – Training name, number of employees on contract, number of employees that have completed the training, number of employees that have not met the requirement, percentage of training completed year to date.
• Contractor Internal Annual Training - Training name, number of employees on contract, number of employees that have completed the training, number of employees that have not met the requirement, percentage of training completed year to date.
• Certifications for job specific requirements (e.g., COMPTIA Security+, Welding, Ammo)
• - Cert. Name, number of employees requiring certification and number of employees certified.
Contractor format is acceptable but must be in excel and editable.
BLK 4: The Report shall be cumulative and shall include but not limited to reporting time period, queries by data field, and contain data that demonstrates compliance as follows:
• Government Mandated Annual Training – Training name, number of employees on contract, number of employees that have completed the training, number of employees that have not met the requirement, percentage of training completed year to date.
• Contractor Internal Annual Training - Training name, number of employees on contract, number of employees that have completed the training, number of employees that have not met the requirement, percentage of training completed year to date.
• Certifications for job specific requirements (e.g., COMPTIA Security+, Welding, Ammo)
• - Cert. Name, number of employees requiring certification and number of employees certified.
BLK 10: MTHLY = Monthly
BLK 12: The report shall be submitted by the 5th business day of every month. CORs will have 5 days to approve or reject the submission. Any COR requested revision of the report will be resubmitted within 7 days of CORs initial request for revision. The revisions will be reviewed within the same time frames as listed above.
BLK 13: MTHLY = Monthly
BLK 14 A: Email submissions to the COR should be sent to USARMY YPG ATEC Mailbox YTC Contracting Branch (usarmy.ypg.atec.mbx.ytc-contracting-branch@army.mil). Email submissions to the PCO should be sent to amanda.m.ramirez24.civ@army.mil.
16. REMARKS: DI-MISC-81366…
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 .