TMIT CDRLs Exhibits A_B_D_F_(Q-A)_ (update) - Clean Version.pdf

DD FORM 1423-1, FEB 2001

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

The public reporting burden for this collection of information is estimated to average 110 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 the Department of Defense, Executive Services (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 of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

D MISC

Trackless Mobile Infantry Targets (TMIT)

A001 Technical Report-Study or Services Spectrum Data

DI-MISC-80508B PWS Para 3.1.12 PM TRASYS (PMM 130)

DD

N/A D

See Blk 16

See Blk 16

N/A

PCO 1 0 1

COR 1 0 1

RTPD 1 0 1

3 0 3

16. REMARKS

Blk 7: The contractor shall initiate a zero cost receiving report in the Wide Area Workflow (WAWF) module in Procurement Integrated Enterprise Environment (PIEE) immediately after submitting the data in accordance with Blk 14. A WAWF receiving report is required for every data item submission (initial and subsequent submission) to the Government.

Blk 8: Final acceptance of the data deliverable is accomplished through Government approval of the WAWF receiving report after timely delivery of the approved data deliverable. Such acceptance does not constitute a waiver of any Government entitlements regarding data rights, including but not limited to DFARS 252.227-7037.

If data deliverables are rejected by the Government, then the Contractor shall submit a revision within 2 working days.

Blk 9: Only unclassified information shall be included in each report. Typical reports are not expected to contain controlled unclassified information (CUI). However, in the event that the report contains CUI, it must be marked and distributed in accordance with DODI

5200.48 and the below instructions. The DD Form 1423-1 must provide the applicable CUI marking as required. The deliverable shall be appropriately marked with the applicable CUI marking(s), and the following information:

See Continuation Page

Adobe Professional 8.0

Form Approved 0MB No. 0704-0188 0MB Approval Expires 20221130

Directorate collection

I

(1 Data Item)

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page of Pages

D MISC

Trackless Mobile Infantry Targets (TMIT)

Controlled By: USMC Controlled By: MARCORSYSCOM, PM TRASYS CUI Category: CTI, EXPT (Expt ONLY if Export Controlled CTI) Distribution Statement: D POC: TMIT Project Officer, (407) 381-8762

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (CTI) (10 Aug 2023). Other requests must be referred to PM TRASYS, 12211 Science Dr, Orlando, FL 32826-3275.

Export Controlled CTI shall also be marked with a WARNING LABEL per DoDI 5230.24 as follows:

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Control Reform Act of 2018 (Title 50, U.S.C., Chapter 58, Sec. 4801-4852). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

The CDRL shall be provided electronically. CUI transmitted via email must be encrypted in transmission or may be delivered via the DoD SAFE website https://safe.apps.mil/ provided the check box that reads “Encrypt every file (REQUIRED FOR CUI, PII and PHI)” is selected. If requested by the Government, hard copies shall be delivered on a CD-ROM, DVD, or native media in Microsoft Office 2013 or newer file format. All data shall be provided in an editable and non-protected format using MS Office products (Word, Excel, Power Point, Visio), or other form as mutually agreed upon for a specific deliverables.

Blk 10: Spectrum data shall be submitted by the Contractor in accordance with paragraph 3.1.12 of the Trackless Mobile Infantry Targets (TMIT) Performance Work Statement (PWS), and shall be submitted not later than 10 calendar days after contract award.

Blk 12: Spectrum data shall be submitted by the Contractor in accordance with paragraph 3.1.12 of the TMIT PWS not later than 10 calendar days after contract award.

Blk 14: Unless otherwise specified, the Government prefers that all unclassified data deliverables (initial, draft, final, update, etc.) be distributed electronically to the addressees listed in Block 14.a. Three primary methods may be used to deliver data to the Government (in order of preference):

1. Distribute unclassified data deliverable(s) that are not further restricted in their dissemination to the Government personnel specified in Block 14.a via email, such as Outlook. The data deliverable would be an attachment in this case.

2. Distribute the unclassified data deliverable(s) to the Government personnel specified in Block 14.a via DoD SAFE (Secure Access File Exchange) (https://safe.apps.mil/). DoD SAFE shall be used for unclassified data submissions with a single electronic file attachment or combined electronic file attachment size that exceeds 15 MB, and for any unclassified data submission that contains Controlled Unclassified Information (CUI), where an approved, secure communications systems or systems that utilizes protective measures such as Public Key Infrastructure or transport layer security (e.g., https) is not available for use.

3. Distribution of unclassified data deliverables that cannot be transmitted electronically shall be accomplished via shipment of the data deliverable(s) to the Government personnel specified in Block 14.a. CUI information and material may be transmitted via first class mail, parcel post, or bulk shipments.

The contractor remains responsible for the timely submission of the CDRL regardless of the method of transmission it elects.

Blk14a: Additional Addressees may be provided at the Post Award Conference and updated by the Government on an as needed basis. Reproducible copy refers to the electronic file.

1011 I I I I

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 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, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302. 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 form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No.

listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

1009, 2009, 3009, 4009 & 5009 A

X-MGMT

I A002 DOD Risk Management Framework (RMF) Package

Deliverables

DI-MGMT-82001NT (See Block 16) I 3.1.13 PM TRASYS (PMM 130)

DD ASREQ See Blk 16

A See Block 16

0 See Blk 16

Blk 4: (tailoring) DID requirements amended by paragraph as follows: COR 1 0 1

ENG 1 0 1

3 .1.2 System Security Plan (SSP). The SSP shall contain at a minimum, System ISSM 1 0 1 Information, Mission Description, Concept of Operations (CONOPS), APdM-E 1 0 1 Environment, Operating and Computing Environment, Physical Security Measures, Facilities Descriptions, Threat Analysis, System Architecture Description, Components, Control Implementation Status, Configurations, Accreditation Boundaries, Connection Process Guide (CPG) Compliant Network Diagrams, External Interfaces and Data Flow, Internal Data Flow, Contingency Plan, Incident Response Plan, User Descriptions and Clearances, Security Roles, Hardware Lists, Software Lists, Ports, Protocols, and Services (PPS), Configuration Management Plan, Information System Continuous Monitoring Plan, and A&A Tasks and Milestones. The SSP shall be approved and signed by the ISSM, User Rep, and Program Manager (PM). In addition to being contained in the SSP, the following items shall be delivered in a MCCAST importable format: Accreditation Boundaries, Hardware Lists, Software Lists, and PPS List.

3 .1.3 Assessment and Authorization (A&A) Project Plan. Disregard this section

3.1.4. Collaboration Brief. Disregard this section

3.1.5. RMF Implementation Plan. The RMF Implementation Plan, also known as "Control Implementation Spreadsheet" shall be delivered in a MCCAST importable format and shall include the following information at a minimum for each applicable control: Allocated Control ID, Authorization Package Name, Control Implementation Status, and Implementation Details. The Control Implementation Status shall define which IA Controls will be 'Implemented', 'Inherited', Planned, or 'Not Applicable'. The Control Implementation Spreadsheet must be approved before moving forward with IA Control Implementation.

3 .1.6. PIT Implementation Plan (PIP). Disregard this section.

See Continuation Page

4 0 4

1 3

(1 Data Item)

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

16. REMARKS (Continued)

Page of Pages

1009, 2009, 3009, 4009 & 5009 I A I X-MGMT

I I

3.1.7. Security Assessment Plan (SAP). The SAP shall be delivered in Microsoft Office 2016 compatible electronic media format. The IA Test Plan shall define all required Vulnerability Scans, Security Technical Implementation Guides (STIGs), Security Readiness Guides (SRGs), Secure Content Automation Protocol (SCAP) benchmarks, and other IA Controls or Security Overlays to be applied to the System. The IA Test Plan shall be approved by the ISSM and SCV prior to RMF Step 4 Validation.

3.1.8 PIT Designation Request. Disregard this section.

3.1.9 PIT Designation Brief. Disregard this section.

3.1.10. Plan of Action and Milestones (POA&M). The POA&M be delivered in a MCCAST importable format (.csv) for initial review and submitted via MCCAST POAM for the final submission. The POA&M shall be considered a 'living' document and shall regularly be updated throughout the entire lifecycle of the System through Decommission. The POA&M shall contain all Not Applicable (N/A) IA Controls, All Non-Compliant IA Controls, and all Non-compliant Vulnerability Findings as identified in the Vulnerability Scans, STIGs, SRGs, and SCAP Benchmarks. At a minimum, the POA&M shall be updated on annual basis following updated vulnerability scans.

3 .1.12. Vulnerability Scans. In accordance with the approved SAP the System shall be scanned using Assured Compliance Assessment Solution (ACAS). ACAS shall be updated with the latest signatures and scanning engines prior to the execution of each vulnerability scan. At a minimum, vulnerability scans shall be conducted annually against the System. Non-compliant findings shall be documented in the System POA&M on an annual basis. At a minimum, vulnerability scans files (.nessus format) shall uploaded into the RMF package (MCCAST).

3.1.13. Security Technical Implementation Guides (STIGs), Security Readiness Guides (SRGs), Secure Content Automation Protocol (SCAP) Benchmarks. In accordance with the approved SAP, the System shall be hardened using the required and approved STIGs, SRGs, SCAP Benchmarks, and other approved hardening tools. Non-compliant STIG, SRG, SCAP Benchmark, and other findings shall be documented in the System POA&M on an annual basis. Updates to the STIGs, SRGs, and SCAP Benchmarks are released on a monthly, quarterly, and yearly basis. Updates to the STIGs, SRGs, and SCAP Benchmarks shall be implemented into the System as they are released or during the next major software release. Non-compliant STIG, SRG, and SCAP Benchmark findings shall be documented in the System POA&M on an annual basis. STIG, SRG, and SCAP Benchmark artifacts shall be provided in a format approved by the DAA, NAO, AO, or ISSM. STIG, SRG, and SCAP Benchmark artifacts shall be handled in accordance with the System's classification level. At a minimum, STIG, SRG, and SCAP Benchmark artifacts (.ckl format) shall uploaded into the RMF package (MCCAST).

3.1.14. Scorecard. Disregard this section.

3.1.15. Contingency Plan. The Contingency Plan shall use the approved DAA, NAO, AO, or ISSM format. The Contingency Plan shall be submitted in conjunction with the SSP. The Contingency Plan shall be approved and signed by the ISSM.

All other sections of the DID apply.

Blk 7: The contractor shall initiate a zero cost receiving report in the Wide Area Workflow (WA WF) module in Procurement Integrated Enterprise Environment (PIEE) immediately after submitting the data in accordance with Blk 14. A WA WF receiving report is required for every data item submission (initial and subsequent submission) to the Government.

Blk 8: Untimely or deficient delivery of data deliverables may serve as the basis for withholding contract payments. The Government will notify the Contractor of its decision to accept or reject the data deliverables presented by the Contractor for inspection and acceptance by the Government. Final acceptance of the data deliverable is accomplished through Government approval of the WA WF receiving report after timely delivery of the approved data deliverable. Such acceptance does not constitute a waiver of any Government entitlements regarding data rights, including but not limited to DF ARS 252.227-703 7. If the data deliverable is rejected, the Government will notify the Contractor of the reason(s) for rejection. If the delivery of data does not conform to contract requirements, is untimely, or did not take place, then formal notification will be provided to the Contractor by written notice from the Contracting Officer. In addition to providing the reasons why the data deliverable was not accepted, the Contracting Officer may direct the Contractor to correct the deficiencies, replace the non-conforming data deliverable, or, when permitted by the contract, elect to receive an equitable adjustment in contract price in lieu of correction or replacement.

See Continuation Page

_2 ___ 3_

(1 Data Item)

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

16. REMARKS (Continued)

Page of Pages

1009, 2009, 3009, 4009 & 5009 I A I X-MGMT

I I If data deliverables are rejected by the Government, then the Contractor shall submit a revision within 2 working days.

Blk 9: Only unclassified information shall be included in each report. Typical reports are not expected to contain controlled unclassified information (CUI). However, in the event that the report contains CUI, it must be marked and distributed in accordance with DoDI

5200.48 and the below instructions. The deliverable shall be appropriately marked with the applicable CUI marking(s), export control statements, and distribution statements in accordance with the MCSC INFORMATION SYSTEMS CYBERSECURITY Security Classification Guide.

Controlled by: United States Marine Corps Controlled by: MARCORSYSCOM, PM TRASYS CUI Category: CTI, ISVI, OPSEC Distribution Statement: D POC: TMIT Project Officer, (407) 381-8762

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Vulnerability Information) (10 Aug 2023). Other requests must be referred to PM TRASYS, 12211 Science Dr, Orlando, FL 32826-3275.

The CORL shall be provided electronically. CUI transmitted via email must be encrypted in transmission or may be delivered via the DoD SAFE website https://safe.apps.mil/ provided the check box that reads "Encrypt every file (REQUIRED FOR CUI, PII and PHI)" is selected. If requested by the Government, hard copies shall be delivered on a CD-ROM, DVD, or native media in Microsoft Office 2013 or newer file format. All data shall be provided in an editable and non-protected format using MS Office products (Word, Excel, Power Point, Visio ), or other form as mutually agreed upon for a specific deliverables.

Blk 12: Initial submission of the DOD Risk Management Framework shall be provided at Post Award Conference to support interim authorization to test (IATT) determination. Initial submission shall include at a minimum the Vulnerability Scans (DID section 3.1.12), STIGs, SRGs, and SCAP Benchmarks (DID Section 3.1.13), the Accreditation Boundaries, Hardware Lists, Software Lists, and PPS List (DID Section 3.1.2), and the IATT Request (DID Section 3.1.1). The contractor shall incorporate any required changes based on Government comments and resubmit 2 working days after receipt of comments. This review cycle shall continue until the Contractor receives acceptance from the Government. In the event that the last calendar day falls on a Saturday, Sunday, or a Federal Holiday, the next Government business day will be considered the last calendar day.

Blk 13: Subsequent submissions of the DOD Risk Management Framework shall be provided as required in support ofRMF accreditation/maintenance and are identified in the PWS or DID. The contractor shall incorporate any required changes based on Government comments and resubmit 2 working days after receipt of comments. This review cycle shall continue until the Contractor receives acceptance from the Government. In the event that the last calendar day falls on a Saturday, Sunday, or a Federal Holiday, the next Government business day will be considered the last calendar day.

Blk 14: Block 14: All submissions shall be delivered electronically in an editable electronic format that is compatible with Microsoft Office products. All submissions shall utilize the following document naming standard CUI_pMTRASYS_ <System Accronym> _ <System MCCAST Version>_ <Document Title>_ <Submission Date (YYYYMMDD)>.<file extension> (i.e.

CUI _pMTRASYS _ DVTE _ v2.x.x.x _SSP _ 20230621.docx). Deliverable submissions shall be marked, handled, and delivered in accordance with the procedures and guidelines detailed in DoDI 5200.48. The contractor shall submit data in the form of attachments, via the MCCAST package or encrypted DoD SAFE to the addressees in the CORL distribution list. DoD SAFE is located at https://safe.apps.mil. DoD SAFE is a file transfer service that can be used within the .mil domain to transfer files up to 8Gb in size. In order to use the DoD SAFE service, the contractor will need to have a Government issued Common Access Card (CAC). If the contractor does not have a Government issued CAC, the Contractor may notify the COR, who can initiate a "Request for Drop Off'' through DoD SAFE to the non-Government CAC user for a file transfer up to 8Gb.

Block 14a: Additional Addressees will be provided at the Post Award Conference and updated by the Government on an as needed basis.

_3 ___ 3_

Blk 12: Initial submission of the DOD Risk Management Framework shall be provided at Post Award Conference to support interim authorization to test (IATT) determination. The contractor shall incorporate any required changes based on Government comments and resubmit 2 working days after receipt of comments. This review cycle shall continue until the Contractor receives acceptance from the Government. In the event that the last calendar day falls on a Saturday, Sunday, or a Federal Holiday, the next Government business day will be considered the last calendar day.

Blk 13: Subsequent submissions of the DOD Risk Management Framework shall be provided as required in support of RMF accreditation/maintenance and are identified in the PWS or DID. The contractor shall incorporate any required changes based on Government comments and resubmit 2 working days after receipt of comments. This review cycle shall continue until the Contractor receives acceptance from the Government. In the event that the last calendar day falls on a Saturday, Sunday, or a Federal Holiday, the next Government business day will be considered the last calendar day.

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

The public reporting burden for this collection of information is estimated to average 110 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 the Department of Defense, Executive Services (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 of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

B MGMT

Trackless Mobile Infantry Targets (TMIT)

B00A Briefing Material

DI-MGMT-81605 See Blk 16 PM TRASYS (PMM 130)

DD

A See Blk 16

ASREQ

N/A

See Blk 16

N/A

PCO 1 0 1

COR 1 0 1

RTPD 1 0 1

3 0 3

Blk 5: PWS paragraphs 3.1.10.8.1 - 3.1.10.8.4.

Blk 7: The contractor shall initiate a zero cost receiving report in the Wide Area Workflow (WAWF) module in Procurement Integrated Enterprise Environment (PIEE) immediately after submitting the data in accordance with Blk 14. A WAWF receiving report is required for every data item submission (initial and subsequent submission) to the Government.

Blk 8: Untimely or deficient delivery of data deliverables may serve as the basis for withholding contract payments. The Government will notify the Contractor of its decision to accept or reject the data deliverables presented by the Contractor for inspection and acceptance by the Government. Final acceptance of the data deliverable is accomplished through Government approval of the WAWF receiving report after timely delivery of the approved data deliverable. Such acceptance does not constitute a waiver of any Government entitlements regarding data rights, including but not limited to DFARS 252.227-7037. If the data deliverable is rejected, the Government will notify the Contractor of the reason(s) for rejection. If the delivery of data does not conform to contract requirements, is untimely, or did not take place, then formal notification will be provided to the Contractor by written notice from the Contracting Officer. In addition to providing the reasons why the data deliverable was not accepted, the Contracting Officer may direct the Contractor to correct the deficiencies, replace the non-conforming data deliverable, or, when permitted by the contract, elect to receive an equitable adjustment in contract price in lieu of correction or replacement.

If data deliverables are rejected by the Government, then the Contractor shall submit a revision within 1 working day.

Blk 9: Only unclassified information shall be included in each report. Typical reports are not expected to contain controlled unclassified information (CUI). However, in the event that the report contains CUI, it must be marked and distributed in accordance with DODI

5200.48 and the below instructions. The DD Form 1423-1 must provide the applicable CUI marking as required. The deliverable shall be appropriately marked with the applicable CUI marking(s), and the following information:

See Continuation Page

Adobe Professional 8.0

1009, 2009, 3009, 4009 & 5009

1 2

Form Approved 0MB No. 0704-0188 0MB Approval Expires 20221130

Directorate collection

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page of Pages

B MGMT

Trackless Mobile Infantry Targets (TMIT)

Controlled By: USMC Controlled By: MARCORSYSCOM, PM TRASYS CUI Category: OPSEC Limited Dissemination Controls: FEDCON POC: TMIT Project Officer, (407) 381-8762

The CDRL shall be provided electronically. CUI transmitted via email must be encrypted in transmission or may be delivered via the DoD SAFE website "https://safe.apps.mil/" provided the check box that reads “Encrypt every file (REQUIRED FOR CUI, PII and PHI)” is selected. If requested by the Government, hard copies shall be delivered on a CD-ROM, DVD, or native media in Microsoft Office 2013 or newer file format. All data shall be provided in an editable and non-protected format using MS Office products (Word, Excel, Power Point, Visio), or other form as mutually agreed upon for a specific deliverables.

Blk 10: TMIT Briefing Materials shall be submitted by the Contractor in accordance with paragraphs 3.1.10.8.1 - 3.1.10.8.4 of the Trackless Mobile Infantry Targets (TMIT) Performance Work Statement (PWS) not less than 5 working days prior to a covered event.

Blk 12: The initial TMIT Briefing Material shall be submitted no later than 5 calendar days prior to the Post Award Conference identified in paragraphs 3.1.10.8.1 - 3.1.10.8.4 of the TMIT PWS.

Blk 14: Unless otherwise specified, the Government prefers that all unclassified data deliverables (initial, draft, final, update, etc.) be distributed electronically to the addressees listed in Block 14.a. Three primary methods may be used to deliver data to the Government (in order of preference):

1. Distribute unclassified data deliverable(s) that are not further restricted in their dissemination to the Government personnel specified in Block 14.a via email, such as Outlook. The data deliverable would be an attachment in this case.

2. Distribute the unclassified data deliverable(s) to the Government personnel specified in Block 14.a via DoD SAFE (Secure Access File Exchange) (https://safe.apps.mil/). DoD SAFE shall be used for unclassified data submissions with a single electronic file attachment or combined electronic file attachment size that exceeds 15 MB, and for any unclassified data submission that contains Controlled Unclassified Information (CUI), where an approved, secure communications systems or systems that utilizes protective measures such as Public Key Infrastructure or transport layer security (e.g., https) is not available for use.

3. Distribution of unclassified data deliverables that cannot be transmitted electronically shall be accomplished via shipment of the data deliverable(s) to the Government personnel specified in Block 14.a. CUI information and material may be transmitted via first class mail, parcel post, or bulk shipments.

The contractor remains responsible for the timely submission of the CDRL regardless of the method of transmission it elects.

Blk14a: Additional Addressees may be provided at the Post Award Conference and updated by the Government on an as needed basis. Draft and Reproducible copy refers to the electronic file.

1009, 2009, 3009, 4009 & 5009

2 2

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

The public reporting burden for this collection of information is estimated to average 110 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 the Department of Defense, Executive Services (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 of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

B MISC

Trackless Mobile Infantry Targets (TMIT)

B001 Contractor’s Progress, Status and Management Report

DI-MGMT-81928 PWS Para 3.1.5.6, 3.1.8, 3.1.10.2 PM TRASYS (PMM 130)

DD

N/A See Blk 16

MTHLY

EOM

N/A

PCO 1 0 1

COR 1 0 1

RTPD 1 0 1

3 0 3

Blk 4: (Tailoring)

- Paragraph 2.4 is deleted.

- Paragraph 2.5(a.) Travel (Off-Site Support) will include the following information:

Table of completed Off-Site training with the following fields: Supporting Site, Supported Unit, Supported Location, Travel Start, Support Start, Support End, Travel End.

Table of upcoming Off-Site training with the same information as above.

- Paragraph 2.6: Contractor's personnel roster shall contain the following information:

Organization, Last First, Rnk/Pos, Billet/Location, Phone, E-mail

- Paragraph 2.7: The requirement to produce Figures 1 and 2 is deleted.

- Paragraph 2.8.a: The title shall be "Trackless Mobile Infantry Targets (TMIT) Support Services."

Blk 7: The contractor shall initiate a zero cost receiving report in the Wide Area Workflow (WAWF) module in Procurement Integrated Enterprise Environment (PIEE) immediately after submitting the data in accordance with Blk 14. A WAWF receiving report is required for every data item submission (initial and subsequent submission) to the Government.

Blk 8: Untimely or deficient delivery of data deliverables may serve as the basis for withholding contract payments. The Government will notify the Contractor of its decision to accept or reject the data deliverables presented by the Contractor for inspection and acceptance by the Government. Final acceptance of the data deliverable is accomplished through Government approval of the WAWF receiving report after timely delivery of the approved data deliverable. Such acceptance does not constitute a waiver of any Government entitlements regarding data rights, including but not limited to DFARS 252.227-7037. If the data deliverable is rejected, the Government will notify the Contractor of the reason(s) for rejection. If the delivery of data does not conform to contract requirements, is untimely, or did not take place, then formal notification will be provided to the Contractor by written notice from the Contracting Officer. In addition to providing the reasons why the data deliverable was not accepted, the Contracting Officer may direct the Contractor to correct the deficiencies, replace the non-conforming data deliverable, or, when permitted by the contract, elect to receive an equitable adjustment in contract price in lieu of correction or replacement.

If data deliverables are rejected by the Government, then the Contractor shall submit a revision within 2 working days.

See Continuation Page

Adobe Professional 8.0

1009, 2009, 3009, 4009 & 5009

1 2

Form Approved 0MB No. 0704-0188 0MB Approval Expires 20221130

Directorate collection

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page of Pages

B MISC

Trackless Mobile Infantry Targets (TMIT)

Blk 9: Only unclassified information shall be included in each report. Typical reports are not expected to contain controlled unclassified information (CUI). However, in the event that the report contains CUI, it must be marked and distributed in accordance with DODI 5200.48 and the below instructions. The DD Form 1423-1 must provide the applicable CUI marking as required. The deliverable shall be appropriately marked with the applicable CUI marking(s), and the following information:

Controlled By: USMC Controlled By: MARCORSYSCOM, PM TRASYS CUI Category: OPSEC Limited Dissemination Controls: FEDCON POC: TMIT Project Officer, (407) 381-8762

The CDRL shall be provided electronically. CUI transmitted via email must be encrypted in transmission or may be delivered via the DoD SAFE website "https://safe.apps.mil/" provided the check box that reads “Encrypt every file (REQUIRED FOR CUI, PII and PHI)” is selected. If requested by the Government, hard copies shall be delivered on a CD-ROM, DVD, or native media in Microsoft Office 2013 or newer file format. All data shall be provided in an editable and non-protected format using MS Office products (Word, Excel, Power Point, Visio), or other form as mutually agreed upon for a specific deliverables.

Blk 10: Contractor’s Progress, Status and Management Reports shall be submitted by the Contractor in accordance with paragraphs 3.1.5.6, 3.1.8,

3.1.10.2 of the Trackless Mobile Infantry Targets (TMIT) Performance Work Statement (PWS), and not more than 5 working days after the last day of each calendar month.

Blk 12: The initial Contractor’s Progress, Status and Management Report shall be submitted in accordance with paragraphs 3.1.5.6, 3.1.8, 3.1.10.2 of the TMIT PWS, and not more than 5 working days after the first complete calendar month of contract performance (e.g., if contract award is 10 January, then the first full calendar month of contract performance is February, and the report is due no more than 5 working days after the last day of February).

Blk 14: Unless otherwise specified, the Government prefers that all unclassified data deliverables (initial, draft, final, update, etc.) be distributed electronically to the addressees listed in Block 14.a. Three primary methods may be used to deliver data to the Government (in order of preference):

1. Distribute unclassified data deliverable(s) that are not further restricted in their dissemination to the Government personnel specified in Block 14.a via email, such as Outlook. The data deliverable would be an attachment in this case.

2. Distribute the unclassified data deliverable(s) to the Government personnel specified in Block 14.a via DoD SAFE (Secure Access File Exchange) (https://safe.apps.mil/). DoD SAFE shall be used for unclassified data submissions with a single electronic file attachment or combined electronic file attachment size that exceeds 15 MB, and for any unclassified data submission that contains Controlled Unclassified Information (CUI), where an approved, secure communications systems or systems that utilizes protective measures such as Public Key Infrastructure or transport layer security (e.g., https) is not available for use.

3. Distribution of unclassified data deliverables that cannot be transmitted electronically shall be accomplished via shipment of the data deliverable(s) to the Government personnel specified in Block 14.a. CUI information and material may be transmitted via first class mail, parcel post, or bulk shipments.

The contractor remains responsible for the timely submission of the CDRL regardless of the method of transmission it elects.

Blk14a: Additional Addressees may be provided at the Post Award Conference and updated by the Government on an as needed basis. Reproducible copy refers to the electronic file.

1009, 2009, 3009, 4009 & 5009

2 2

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

The public reporting burden for this collection of information is estimated to average 110 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 the Department of Defense, Executive Services (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 of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

B MGMT

Trackless Mobile Infantry Targets (TMIT)

B002

2. TITLE OF DATA ITEM

Accident Incident Report

DI-MGMT-82188 PWS Para 3.1.6.1 PM TRASYS (PMM 130)

DD

A See Blk 16

ASREQ

N/A

See Blk 16

N/A

PCO 1 0 1

COR 1 0 1

RTPD 1 0 1

Local Government Rep 1 0 1

4 0 4

Blk 4: (Tailoring) - Figure 1, referred to in paragraph 1 and 2 of DI-MGMT-82188, is replaced with the MCSC Mishap Form of the base contract. Refer to DoDM 5200.01-V3, Enclosure (6), Appendix 1, Figure 2 (Report of Security Incident Inquiry or Investigation) with respect to reports with security implications.

Blk 7: The contractor shall initiate a zero cost receiving report in the Wide Area Workflow (WAWF) module in Procurement Integrated Enterprise Environment (PIEE) immediately after submitting the data in accordance with Blk 14. A WAWF receiving report is required for every data item submission (initial and subsequent submission) to the Government.

Blk 8: Untimely or deficient delivery of data deliverables may serve as the basis for withholding contract payments. The Government will notify the Contractor of its decision to accept or reject the data deliverables presented by the Contractor for inspection and acceptance by the Government. Final acceptance of the data deliverable is accomplished through Government approval of the WAWF receiving report after timely delivery of the approved data deliverable. Such acceptance does not constitute a waiver of any Government entitlements regarding data rights, including but not limited to DFARS 252.227-7037. If the data deliverable is rejected, the Government will notify the Contractor of the reason(s) for rejection. If the delivery of data does not conform to contract requirements, is untimely, or did not take place, then formal notification will be provided to the Contractor by written notice from the Contracting Officer. In addition to providing the reasons why the data deliverable was not accepted, the Contracting Officer may direct the Contractor to correct the deficiencies, replace the non-conforming data deliverable, or, when permitted by the contract, elect to receive an equitable adjustment in contract price in lieu of correction or replacement.

If data deliverables are rejected by the Government, then the Contractor shall submit a revision within 2 working days.

Blk 9: Only unclassified information shall be included in each report. Typical reports are not expected to contain controlled unclassified information (CUI). However, in the event that the report contains CUI, it must be marked and distributed in accordance with DODI

5200.48 and the below instructions. The DD Form 1423-1 must provide the applicable CUI marking as required. The deliverable shall be appropriately marked with the applicable CUI marking(s), and the following information:

See Continuation Page

Adobe Professional 8.0

1009, 2009, 3009, 4009 & 5009

1 2

Form Approved 0MB No. 0704-0188 0MB Approval Expires 20221130

Directorate collection

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page of Pages

B MGMT

Trackless Mobile Infantry Targets (TMIT)

Controlled By: USMC Controlled By: MARCORSYSCOM, PM TRASYS CUI Category: OPSEC Limited Dissemination Controls: FEDCON POC: TMIT Project Officer, (407) 381-8762

The CDRL shall be provided electronically. CUI transmitted via email must be encrypted in transmission or may be delivered via the DoD SAFE website "https://safe.apps.mil/" provided the check box that reads “Encrypt every file (REQUIRED FOR CUI, PII and PHI)” is selected. If requested by the Government, hard copies shall be delivered on a CD-ROM, DVD, or native media in Microsoft Office 2013 or newer file format. All data shall be provided in an editable and non-protected format using MS Office products (Word, Excel, Power Point, Visio), or other form as mutually agreed upon for a specific deliverables.

Blk 10: Accident Mishap Reports shall be submitted by the Contractor in accordance with paragraph 3.1.6.1 of the Trackless Mobile Infantry Targets (TMIT) Performance Work Statement (PWS) for reportable accidents/incidents as they occur throughout the period of performance.

Blk 12: The initial Accident Mishap Reports shall be submitted by the Contractor in accordance with paragraph 3.1.6.1 of the TMIT PWS.

Blk 14: Unless otherwise specified, the Government prefers that all unclassified data deliverables (initial, draft, final, update, etc.) be distributed electronically to the addressees listed in Block 14.a. Three primary methods may be used to deliver data to the Government (in order of preference):

1. Distribute unclassified data deliverable(s) that are not further restricted in their dissemination to the Government personnel specified in Block 14.a via email, such as Outlook. The data deliverable would be an attachment in this case.

2. Distribute the unclassified data deliverable(s) to the Government personnel specified in Block 14.a via DoD SAFE (Secure Access File Exchange) (https://safe.apps.mil/). DoD SAFE shall be used for unclassified data submissions with a single electronic file attachment or combined electronic file attachment size that exceeds 15 MB, and for any unclassified data submission that contains Controlled Unclassified Information (CUI), where an approved, secure communications systems or systems that utilizes protective measures such as Public Key Infrastructure or transport layer security (e.g., https) is not available for use.

3. Distribution of unclassified data deliverables that cannot be transmitted electronically shall be accomplished via shipment of the data deliverable(s) to the Government personnel specified in Block 14.a. CUI information and material may be transmitted via first class mail, parcel post, or bulk shipments.

The contractor remains responsible for the timely submission of the CDRL regardless of the method of transmission it elects.

Blk14a: Additional Addressees may be provided at the Post Award Conference and updated by the Government on an as needed basis. Draft and Reproducible copy refers to the electronic file.

1009, 2009, 3009, 4009 & 5009

2 2

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

The public reporting burden for this collection of information is estimated to average 110 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 the Department of Defense, Executive Services (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 of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

B SAFT

Trackless Mobile Infantry Targets (TMIT)

B003 Safety Assessment Report

DI-SAFT-80102C PWS Para 3.1.6.2 PM TRASYS (PMM 130)

DD

N/A See Blk 16

See Blk 16

N/A

See Blk 16

See Blk 16

PCO 1 0 1

COR 1 0 1

RTPD 1 0 1

3 0 3

Blk 7: The contractor shall initiate a zero cost receiving report in the Wide Area Workflow (WAWF) module in Procurement Integrated Enterprise Environment (PIEE) immediately after submitting the data in accordance with Blk 14. A WAWF receiving report is required for every data item submission (initial and subsequent submission) to the Government.

Blk 8: Untimely or deficient delivery of data deliverables may serve as the basis for withholding contract payments. The Government will notify the Contractor of its decision to accept or reject the data deliverables presented by the Contractor for inspection and acceptance by the Government. Final acceptance of the data deliverable is accomplished through Government approval of the WAWF receiving report after timely delivery of the approved data deliverable. Such acceptance does not constitute a waiver of any Government entitlements regarding data rights, including but not limited to DFARS 252.227-7037. If the data deliverable is rejected, the Government will notify the Contractor of the reason(s) for rejection. If the delivery of data does not conform to contract requirements, is untimely, or did not take place, then formal notification will be provided to the Contractor by written notice from the Contracting Officer. In addition to providing the reasons why the data deliverable was not accepted, the Contracting Officer may direct the Contractor to correct the deficiencies, replace the non-conforming data deliverable, or, when permitted by the contract, elect to receive an equitable adjustment in contract price in lieu of correction or replacement.

If data deliverables are rejected by the Government, then the Contractor shall submit a revision within 1 working day.

Blk 9: Only unclassified information shall be included in each report. Typical reports are not expected to contain controlled unclassified information (CUI). However, in the event that the report contains CUI, it must be marked and distributed in accordance with DODI

5200.48 and the below instructions. The DD Form 1423-1 must provide the applicable CUI marking as required. The deliverable shall be appropriately marked with the applicable CUI marking(s), and the following information:

See Continuation Page

Adobe Professional 8.0

1 2

Form Approved 0MB No. 0704-0188 0MB Approval Expires 20221130

Directorate collection

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page of Pages

B SAFT

Trackless Mobile Infantry Targets (TMIT)

Controlled By: USMC Controlled By: MARCORSYSCOM, PM TRASYS CUI Category: OPSEC Limited Dissemination Controls: FEDCON POC: TMIT Project Officer, (407) 381-8762

The CDRL shall be provided electronically. CUI transmitted via email must be encrypted in transmission or may be delivered via the DoD SAFE website "https://safe.apps.mil/" provided the check box that reads “Encrypt every file (REQUIRED FOR CUI, PII and PHI)” is selected.