TE C DD1423_BTSS_27Jan2026.pdf

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" delete continuation delete continuation delete continuation delete continuation delete continuation delete continuation

Block 12: NLT Day 10 After Phase-in = No later than end working day 10 after Contract Phase-in.

Block 13: MO, 10th Day = By the 10th working day of each month

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 Executive Summary. Contractor format is acceptable.

a. Highlights of reported month's activities, including problems encountered and efforts to continually improve performance.

b. Projected Activities.

16.2 Progress and Historical.

a. TO-RFP Summation. Provide the following information or all requirements that were issued during the fiscal year (FY).

1. TO-RFP Number

2. TO-RFP Title

3. Government POC

4. Contractor POC

5. Purchasing POC

6. TO-RFP Issued

7. TOP Due Date

8. TOP Submitted

9. Amount Estimated

10. Amount Approved

11. Remarks

12. Amount Funded

13. Date Approved

b. TO-RFP Status Report. Provide the following information for each tasking that was active during the reporting period.

1. TO-RFP Number and Title

2. Government Initiator / POC

3. Contractor POC

4. Date Tasking was Initiated

5. Date of TOP Submission

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraphs 1.2.5 and 3.1.1 and FAR 52.245-1, and eliminating requirements in the DID not applicable to the Property Management Plan.

Block 10: ASREQ = As Required

Block 12: 30DAC = 30 Days After Contract Award

Block 13: ASREQ = As Required, if changes occur after Government approval

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil

PA: TBD

Block 16: Remarks / Preparation Instructions: Contractor format is acceptable.

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraphs 5.1.1 and 5.2.2.

Block 10: ASREQ = As Required

Block 12: First TOP required within seven (7) calendar days of Contractor receipt of SOW and Task Order Request for Proposal (TO-RFP).

Block 13: ASREQ = Contractor TOP submission within 7 calendar days of SOW/TO-RFP receipt.

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 The Contractor shall provide one of the following TOP formats: a TOP or an Immediate Resource Requirement (IRR).

16.2 The TOP shall be submitted to the Government (MICC and COR) as one document consisting of a cover letter, technical approach (e.g., Power Point, Memorandum, cost attachments) identified by the TO-RFP number and title.

a. The TOP combines streamlined procedures (technical approach) with thorough coverage of essential tasks and resources with estimated costs.

b. An IRR does not include slides and consists of a formal letter detailing the need for immediate support pending development of a TOP and the IRR cost. This format should only be used to request immediate support for a new TO-RFP.

16.3 How to accomplish the requirement Task Order Proposal (TOP):

a. Technical Approach

1. Describe the proposed methodology, procedures, and plans to accomplish the requirement

2. List the milestone and deliverable schedule

3. Staffing

4. List potential problems and recommended solutions

5. List actions or situations requiring Government action

6. List exceptions to the Government requirement

7. Estimated Cost Summary

b. Address the following, when applicable:

1. Property administration

2. Safety and Security (including computer viruses) measures

3. Maintenance of GFP and post test repair of equipment and instrumentation to operational status

4. Communication capabilities and procedures

5. Data collection and data management

6. Physical and COMSEC security measures

16. REMARKS: Block 4: Tailored to requirements as specified in PWS Paragraph 5.2.1.1. Format shall be Contractor format that is acceptable to USG.

Block 12: Upon completion of the first full week after contract award.

Block 13: Weekly thereafter, by completion of the third working day.

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil TO: TBD, Based on TO-RFP

Block 16: Remarks / Preparation Instructions:

16.1 General. The report shall be a concise summary of all significant activities for the weekly reporting period.

16.2 Format. The report shall be submitted electronically in Adobe PDF or Microsoft Word format.

16.3 Content. The report shall be clearly marked with the Task Order number and title, and shall contain, at a minimum, the following sections:

16.3.1 Reporting Period: The start and end date of the week covered by the report.

16.3.2 Summary of Activities Performed: A summary of the work accomplished and milestones achieved during the reporting period, referenced against the approved Task Order schedule.

16.3.3 Performance and Schedule Status: An assessment of the Task Order's status (e.g., Green/On-Schedule, Yellow/At-Risk, Red/Behind-Schedule) with a brief rationale. Any deviation from the established schedule shall be explained.

16.3.4 Issues, Risks, and Accomplishments:

a. A description of any problems, risks, or issues encountered during the week that may impact cost, schedule, or performance.

b. A summary of proposed or implemented solutions for any identified issues.

c. A highlight of any significant accomplishments.

d. Additional spreadsheets will be provided for any TO-RFP/Task Order Proposal (TOP) requests to track specific costs.

16.3.5 Planned Activities for Next Reporting Period: A brief description of the work planned for the upcoming week.

16.3.6 Provide a power point that includes: Staffing per labor category, timelines, position, number of personnel per labor category

16.3.7 Labor Hours Expended: A summary of the total labor hours expended on the Task Order during the reporting period, broken down by labor category

16. REMARKS: Block 4: Tailored to requirements as specified in PWS Paragraph 1.10.1.

Block 12: At contract award, no later than five (5) business days after.

Block 13: Quarterly thereafter.

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil KO: Lucy Bonner, lucy.u.bonner.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 General. The Emergency Contact List shall be accurate and kept current at all times. Any changes to personnel or contact information shall be submitted to the Government in an updated version of the list per the frequency requirements.

16.2 Format. The list shall be submitted electronically in a searchable Adobe PDF format.

16.3 Content. The list shall be clearly titled and dated. It must provide the following information for each individual identified as Key Personnel in PWS 1.10 and any other personnel the Contractor designates as essential for emergency contact:

a. Full Name

b. Contract Title / Role (e.g., Program Manager, Security Manager etc.)

c. Primary Contact Telephone Number (Must be monitored 24/7/365)

d. Alternate/Secondary Contact Telephone Number

e. Official Email Address

16.4. Key personnel includes the Program Manager, Test Task Leads, and key leaders of the major sections/divisions within the Contractor organization operating at Fort Hood, Fort Bliss, and Fort Bragg.

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraph 1.26.1.6

Block 12: No later than the 5th working day after Phase-in ends

Block 13: Monthly thereafter, no later than the 5th working day after the reporting month ends

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 The Contractor shall conduct a monthly inventory of items maintained in the Sensitive Items Storage Area or other secured areas. Inventory will be signed by a minimum of two people and shall be posted in the Sensitive Items Storage Area and other secured areas where sensitive items are secured. Contractor format is acceptable but shall contain the following information as a minimum.

a. Nomenclature of item

b. Serial number of item

c. Names/Signatures of personnel conducting the inventory

d. Date of the inventory

e. Quantity on Hand

16.2 The Contractor shall maintain positive accountability and ensure storage IAW AR 190-51 for Sensitive Items deployed in support of specific TO-RFPs. For the duration of each deployment, the Contractor shall submit a Sensitive Items Report twice daily not later than 1000 hours and 1700 hours central time. Contractor format is acceptable but shall contain the following information as a minimum.

a. TO-RFP effort being supported

b. Location of TAR being supported

c. Date/Time of Report

d. Names/Signatures of personnel conducting the inventory (must be at least two).

e. Serial number inventory of all sensitive items

f. Physical location of sensitive items, for example, building/room number of storage facility or name of individual signed for the equipment at the time of the inventory.

g. Reconciliation Statement: A section reconciling the current inventory with the previous month's report, accounting for any items received or turned in during the reporting period.

h. Certification Statement: The following statement must be included above the signature block: "I certify that a 100% physical inventory of all sensitive items was conducted on [date of inventory] and that this report is a true and accurate reflection of that inventory. All items are accounted for in accordance with AR 190-11."

i. Discrepancy Report: If applicable, a section detailing any discrepancies discovered during the inventory, the immediate corrective actions taken, and the status of any formal LDD reports submitted. If no discrepancies were found, this section shall state, "No discrepancies noted."

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraphs 5.2.1.1 and 5.2.2

Block 12: No later than the 5th working day after the end of the first quarter of contract performance

Block 13: Quarterly thereafter, no later than the 5th working day after the reporting quarter ends

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 The deliverable shall provide a spreadsheet containing the following actual expenditures for each TO-RFP for each quarter. The revision report shall be provided by the 5th day following the end of each quarter. The revision report shall include:

a. TO-RFP Number

b. Prior Quarter Performance Summary: A summary of all work accomplished, milestones met, and deliverables submitted during the previous quarter, compared against the approved TO schedule.

c. Overall Summary to include funding summary-incurred cost, percentage spent, and total estimated cost etc.

d. Dates/Quarter

e. Actual labor hours per month per labor category and dates

f. Actual reimbursable to include fuel, supplies, GSA supplies, travel etc.

g. Actual ITR to include software, licenses, cell phone etc.

h. Actual MILSTRIP to include, shipping costs, repair parts etc.

i. Historical Summary

j. Next Quarter Forecast: A summary of major planned activities, milestones, and anticipated challenges for the upcoming quarter.

k. Staffing

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraphs 5.2.6.6, 5.2.7.2, and Part 3

Block 12: A joint inventory of Government-furnished property must be completed within fourteen (14) days after the contract effective date (see PWS 3.1.2).

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil PA: Antonio Sanchez, antonio.m.sanchez.civ@army.mil PBO: Aaron Buhrer, aaron.e.buhrer.civ@army.mil

Block 16: Remarks / Preparation Instructions:

Government and Contractor use of the GFP Module of Procurement Integrated Enterprise Environment (PIEE) (https://piee.eb.mil/), for all GFP provided is established at PWS Part 3. Use of PIEE and the required system inputs, is required for the initial report and annual inventory actions.

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraph 1.24

Block 12: Timeframes for submission vary for the individual training as established herein.

Block 13: No less than annually, as specified for each individual required training.

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 Provide the number of contract personnel as of the last working day of each month.

16.2 Of the number provided in paragraph 10.1 above, provide a breakdown of personnel that have completed the following training, by training course and date of completion via Contractor format:

a. Anti-Terrorism (AT) Level I. The Contractor shall submit an electronic copy of all training certificates to the COR. New contractor employees must complete this training within 30 calendar days of their reporting for duty. All contractor employees must complete annual AT Level I training. Training can be accessed at http://jko.jten.mil.

b. OPSEC Training. Per AR 530-1, Operations Security, new contractor employees must complete Level I OPSEC training within 30 calendar days of their reporting for duty. All contractor employees must complete annual OPSEC awareness training https://securityawareness.usalearning.gov/opsec/index.htm.

c. Nondisclosure Agreement (NDA) Completion and Release of ATEC Test and Evaluation Data and Information Training. All contractor employees must receive the Release of ATEC Test and Evaluation Data and Information Training and sign a NDA within the first 5 working days of employment. All employees must complete refresher training and resign a NDA annually. The Program of Instruction (POI) and NDA will be provided by the Government.

d. ATEC Security Education and Awareness Training (SEAT). All employees must receive ATEC SEAT within 30 calendar days of employment and receive annual refresher training. The Government will provide the Program of Instruction (POI).

e. Information Assurance (IA). All contractor employees must complete the appropriate IA training commensurate with their designated level of information access/responsibilities prior obtaining LAN access. All employees must complete annual IA refresher training. Training is available at https:// https://cs.signal.army.mil/.

f. Threat Awareness and Reporting Program (TARP). All employees must receive initial TARP training within 30 calendar days of employment and receive annual refresher training IAW AR 381-12 https://learn.atis.army.mil/moodle/.

g. iWATCH Training. iWATCH training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. The Government will provide the POI. This training must be completed within 30 calendar days of employment. All Contractor employees will receive annual refresher training. https://jkodirect.jten.mil.

h. Global Combat Support System (GCSS)-Army (GTRAX). Training shall be completed within 30 calendar days of employment and any refresher required thereafter. http://www.gcss.army.mil/GTRAC/Account/Login.aspx.

i. PIEE (GFP Module) Contractor employees, including subcontractors, performing services under this

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraph 1.26.1.5.1

Block 12: Timeframes for submission vary for the individual training as established herein.

Block 13: No less than annually, as specified for each individual required training.

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 General. The report must be 100% accurate and reflect a complete accounting of all hazardous materials and waste under the Contractor's control.

16.2 Format. The report shall be submitted electronically in a non-editable Adobe PDF format and must be digitally signed by the Contractor's designated Environmental Compliance Officer (ECO) or the Program Manager.

16.3 Content. The report shall be clearly titled with the contract number, contractor name, and the reporting period. It shall be divided into the following sections:

16.3.1 Hazardous Materials Inventory: A detailed, itemized list of all hazardous materials on hand. Each line item must include, at a minimum:

a. NSN

b. Nomenclature

c. Manufacturer

d. Unit of Issue

e. Quantity at the beginning of the month

f. Quantity received during the month

g. Quantity on hand at the end of the month

h. Material Safety Data Sheet (MSDS) number

i. Location of the hazardous material

16.3.2 Hazardous Waste Summary: A summary of all hazardous waste generated during the reporting period, including:

a. Type of Waste Stream (e.g., used solvents, contaminated rags)

b. Quantity accumulated during the period.

c. Current quantity in storage awaiting disposal.

d. Date(s) and manifest number(s) for any waste turned in for disposal during the period.

16.3.3 Spill / Release Incident Report Summary: A summary of any hazardous material spills or releases that occurred during the reporting period. Note: This section is for summarizing events that have already been immediately reported per installation policy. It shall include:

a. Date of incident

b. Material and quantity released

c. A brief description of the corrective action taken

d. Id no incidents occurred, shall state, "No spills or releases occurred during the reporting period"

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraph 5.2.5.5

Block 12: The Contractor shall submit the required report by the end of the third quarter of each Government fiscal year (FY).

Block 13: Annually, by the end of the third quarter of each FY.

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 The Contractor shall provide a current IT Inventory of all laptops, desk tops, printers, towers (mini or small form factor), monitors, and mobile phones. This report complements the GFE & CAP Report (A008) by providing specific technical data not captured in A008.

The inventory shall include locations outside of Fort Hood, TX with the following information:

a. Number of laptops in use and not in use

b. Number of desktop in use and not in use

c. Number of printers in use and not in use

d. Number of monitors in use and not in use

e. Number of towers in use and not in use

f. Manufacturer and model number of each item

g. Number of items to be turned-in

h. Date purchased

i. Number of mobile phones in use and not in use

j. Any other equipment considered IT.

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraphs 1.6.9, 1.6.9.1 and 1.7

Block 10: ASREQ = as required pending Contractor update throughout contract performance

Block 12: The Contractor shall submit within 90 days of contract award

Block 13: As required pending Contractor update to the SOP throughout contract performance

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 The Contractor shall provide an OPSEC SOP IAW Army Regulations 530-1,2-3a (3) and the Physical Security SOP IAW all OEC policies, ATEC, III Corps, and Fort Cavazos Physical Security procedures and regulations and all other DoD facility or installations. Contractor MS Office format is acceptable.

16.2 The OPSEC SOP shall include a training plan that incorporates an initial OPSEC brief, continuous awareness, and annual OPSEC training. The SOP shall describe its responsibilities, and its measures.

16.3 The Physical Security SOP shall contain to both internal and external attack situations. It shall address the below critical elements with Emergency Evacuation, Safeguarding Classified Information, Reporting Bomb Threats, Demands, and Other Acts of Terrorism, Key Control, Access to Forward Test Centers, Night Visions Devices, and Sensitive Item Storage:

a. Deterrence

b. Detection

c. Response

d. Recovery

e. Instructions

16.4 Compliance: A statement confirming the Contractor's commitment to comply with all applicable installation-specific security policies and procedures (e.g., OEC Memorandum 190-2 as cited in PWS 1.6.3).

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraph 5.2.12

Block 12: The Contractor shall submit by the 5th day after the end of the first quarter of contract performance

Block 13: The Contractor shall provide the GCSS-ARMY repair parts inventory listing to the Government not later than the 5th day of each FY quarter.

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil G4 Logistics Officer: Brian Pennington, brian.l.pennington2.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 General. The report shall be a complete and accurate accounting of all repair parts in the Contractor's possession that are Government property or are intended for use on Government property.

16.2 Format. The report shall be submitted electronically in a sortable Microsoft Excel format. A Memorandum For Record (MFR) shall be attached as the cover letter of the Inventory Listing identifying any discrepancies or issues.

16.3 Content. The report shall be clearly titled with the contract number and the "as of" date for the inventory. It shall contain two sections:

16.3.1 Inventory Summary: A header section providing a high-level overview, including:

a. Total Number of Line Items

b. Total Quantity of Items

c. Total Value of Inventory

d. A summary of any parts that have fallen below the established reorder point.

16.3.2 Detailed Inventory Roster: A detailed list where each row represents a distinct part number. The roster must include, at a minimum, the following data columns:

a. National Stock Number (NSN), if applicable

b. Part Number

c. Item Nomenclature (Description)

d. Unit of Issue (e.g., EA, BX, FT)

e. Unit Price

f. Quantity on Hand

g. Condition Code (e.g., Serviceable, Unserviceable-Repairable)

h. Total Value (Quantity x Unit Price)

i. Physical Location (e.g., Warehouse, Shelf, Bin number)

j. Reorder Point/Level

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraph 5.2.10.3

Block 12: The Contractor shall submit by the 5th day after completion of the first month of contract performance

Block 13: Monthly, by the 5th day after the end of the reporting month

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil G4 Logistics Ordinance Officer: CW4 Demetrius Bolden, demetris.l.bolden.mil@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 General. The Contractor shall provide an equipment utilization report for each month IAW AR 710-2. The Contractor will utilize GSA Fleet for selected management actions of NTVs (vehicles and commercial trailers).

16.2 Format. The report shall be submitted electronically in a sortable Microsoft Excel format.

16.3 Content. The verification email shall be clearly titled with the contract number, deliverable name (Monthly GSA Fleet Data Upload Verification), and the reporting period (e.g., "For the month of January 2026"). The body of the email shall serve as a formal certification and must include the following statements:

a. Certification of Data Upload: A statement certifying that the monthly NTV data update into GSA Fleet has been completed for the specified reporting period.

b. Confirmation of Data Sources: A statement attesting that mileage and maintenance data from GCSS-A, and fuel quantities and costs from the Government-provided DLA fuel report, have been fully and accurately entered into the GSA Fleet system.

c. Confirmation of Data Accuracy: A statement confirming that all NTV administrative data within the GSA Fleet system (e.g., disposals, license plate information) is current and accurate.

d. Confirmation of Recall Status: A statement confirming that the status of any open vehicle recalls has been updated in the system upon completion of the recall maintenance.

e. Signature: The email must be sent from, or include the digital signature of, the Contractor's Program Manager or designated Site Lead, confirming the accuracy and completeness of the certification.

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraph 5.2.8.3

Block 12: The Contractor shall submit by the 5th day after completion of the first quarter of contract performance

Block 13: Quarterly, by the 5th day after the end of the reporting quarter

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil G4 APO: Aaron Buhrer, aaron.e.buhrer.civ@army.mil MICC APO: Antonio Sanchez, antonio.m.sanchez.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 General. The Contractor shall provide an a report addressing Property Management requirements and status of the Inventory Management List (IML)

16.2 Format. The report shall be submitted electronically in a sortable Microsoft Excel format.

16.3 Content. The report shall be clearly titled with the contract number and the reporting period. It shall include, at a minimum, the following data columns for each line item of inventory:

a. Part Number / National Stock Number (NSN)

b. Item Nomenclature (Description)

c. Unit of Issue (e.g., EA, BX, RL)

d. Unit Price

e. Quantity on Hand (at the end of the reporting period)

f. Reorder Point / Minimum Stock Level

g. Maximum Stock Level

h. Quantity Consumed During Quarter

i. Average Monthly Consumption (calculated over the previous 12 months, or period of performance if shorter)

j. On-Order Status: (Quantity currently on order from a supplier and expected receipt date)

k. Flag for Items Below Reorder Point: (A visual indicator, e.g., "YES" or cell highlighted in yellow, for any item where the Quantity on Hand is at or below the Reorder Point).

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraph 1.20

Block 12: The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. Notification shall occur within 24 hours of Contractor knowledge of an OCI with the required plan submitted within 2 calendar days of notification.

Block 13: Any subsequent OCI notification shall follow the time frame established at Block 12

Block 14: Distribution Information

Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 General. The OCI Mitigation Plan shall be a self-contained document that is clear, concise, and provides sufficient detail to demonstrate the Contractor's full compliance with its obligations under FAR Subpart 9.5.

16.2 Format. Notification and Contractor Plan are Contractor's format, using MS Office or Adobe PDF.

16.3 Content. The OCI Mitigation Plan shall, at a minimum, include the following sections:

a. OCI Identification Process: A description of the Contractor’s systematic process for identifying potential or actual OCIs related to this contract at the prime and all subcontractor levels. This shall include a review of all corporate relationships and all current and planned work that may create "impaired objectivity," "biased ground rules," or "unequal access to information" conflicts.

b. Disclosure of Potential Conflicts: This section must affirmatively disclose any and all known potential or actual OCIs that exist at the time of plan submission. If no conflicts are identified, the plan must affirmatively state that a thorough review was conducted and no OCIs were found.

c. Detailed Mitigation Strategies: For each potential or actual OCI disclosed, provide a detailed, actionable mitigation strategy. This strategy must be more than a general statement of intent. It must describe the specific structural and procedural arrangements that will be implemented. Examples include, but are not limited to:

d. Firewalls: A detailed description of the organizational and procedural "firewall" separating conflicted employees or business units from contract performance. This includes reporting structures, separate physical locations, and restricted access to data.

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraphs 1.5.1 and 1.7

Block 10: ASREQ = As required, if Contractor changes occur after original Government acceptance of QCP

Block 12: Contractor plan required within 30 Days of contract award

Block 13: Any proposed changes to the accepted QCP are required to be resubmitted for acceptance by the Contracting Officer no later than 30 calendar days prior to the anticipated change and before implementation by the Contractor. The timeline set forth at 1.5.1 applies for review and acceptance for proposed changes

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption. The submissions shall be prepared and delivered in current Microsoft Office software suite.

KO: Lucy Bonner, lucy.u.bonner.civ@army.mil COR: Cynthia Pacheco, cynthia.r.pacheco.civ@army.mil

Block 16: Remarks / Preparation Instructions:

16.1 General. The Contractor shall provide an a Plan addressing, at a minimum, the elements at PWS 1.5.1(a) through (h) and 1.7.

16.2 Format. Contractor's format, using MS Office or Adobe PDF.

16.3 Content. The QPP shall, at a minimum, include the following sections:

a. Quality Organization and Authority: An organizational chart and narrative describing the quality structure. It must identify the Quality Manager by title and affirm that this individual has the authority and organizational independence to identify deficiencies and require corrective action, reporting directly to a level of management that is not directly responsible for executing the work.

b. Performance Monitoring: A detailed description of the surveillance methods the Contractor will use to monitor performance. This shall be detailed in a Quality Control Matrix that includes, at a minimum:

(1) The PWS requirement to be monitored.

(2) The performance standard from the PWS.

(3) The specific surveillance method to be used (e.g., 100% inspection, random sampling, periodic surveillance).

(4) The frequency of surveillance.

(5) The title of the individual responsible for conducting the surveillance.

c. Deficiency Correction Process: A description of the systematic process for documenting and correcting deficiencies. This must include:

(1) The use of Corrective Action Reports (CARs) to formally document any non-conforming service.

16. REMARKS: Block 4: Tailored to require content as specified in PWS Paragraph 1.22

Block 10: ASREQ = As required, if Contractor changes occur after original Government acceptance of Safety Plan

Block 12: The Contractor shall submit the Safety Plan immediately at contract award.

Block 13: Any proposed changes or revisions to the accepted Safety Plan shall be submitted ten (10) days prior to the effective date of the change. and are required to be resubmitted for acceptance by the Contracting Officer no later than 30 calendar days prior to the anticipated change and before implementation by the Contractor.

Block 14: Distribution Information Submission shall be via electronic mail (e-mail) to the POCs identified, and encrypted with a minimum of 128 bit encryption.