Profilometer Terrain Measurement System

Form / Attachment / Pricing Sheet

This document outlines the "Threshold Rank" for requirements related to the opportunity. It defines that a product will not be a sufficient solution if all requirements are not met to at least a "Threshold" level. Requirements marked with an asterisk (*) have an "Objective" and are further categorized into "Vital" or "Critical" ranks.

• Threshold Rank: All requirements must meet this level for a sufficient solution.
• Objective Requirements: Marked with an asterisk (*), these contribute to vital or critical ranks.
• Vital Rank: Requirements that increase usefulness and performance when met. All requirements within this category are of equal importance.
• Critical Rank: Requirements that significantly increase usefulness and performance when met. All requirements within this category are of equal importance.
• The document lists specific requirement identifiers (e.g., REQ-PM-01, REQ-SR-04, REQ-DR-02) under each rank category.

Bidders must use this document to understand the criticality of each requirement. Proposals should clearly indicate where each requirement is addressed. Meeting "Threshold" level requirements is mandatory for a sufficient solution, while meeting "Objective" requirements (Vital and Critical) will significantly enhance the product's performance and usefulness, impacting evaluation and selection.

Solicitation / RFP / RFQ

This solicitation is for the procurement of an ATC Profilometer, a highly mobile off-road test course and terrain measurement system. The system will consist of a prime mover (rugged off-road capable vehicle) and data collection hardware and software. The primary purpose is to measure inputs into vehicles under test, particularly in soft soil conditions.

• ATC Profilometer System: Includes a prime mover, micro-terrain measurement (scanning) instrumentation, and an Inertial Navigation System (INS) for position and orientation.

• Data Collection System: Utilizes an INS with a high-grade Inertial Measurement Unit (IMU) and differential Global Positioning System (GPS).

• Software Package: An end-to-end software package for system control, processing, and data analysis.

• Deliverables: Includes the Profilometer system (Item 0001) and a Contract Data Requirements List (CDRLs) (Item 0002).

• Contract Type: Firm Fixed Price for both Item 0001 and Item 0002.

• Period of Performance: 365 Calendar Days from the date of award.

• Estimated Value: Not explicitly stated in the provided pages.

• Offer Due Date: April 20, 2026, 10:00 AM Local Time.

• Submission Method: Electronic via email, with specific formatting and page limitations for Technical, Past Performance, Cost/Price, and Certifications/Representations volumes.

• Evaluation Factors: Technical (significantly more important), Past Performance (equally important to Cost/Price), and Cost/Price. An "Acceptable" rating is required for all factors.

• Key Deadlines: Offer due date is April 20, 2026.

• Set Aside: This acquisition is set aside for Small Business.

• NAICS Code: 334519 (Size Standard: 1250 employees).

• The solicitation includes numerous FAR and DFARS clauses covering various aspects of contract performance, payment, security, and compliance.

• Offerors must be registered in the System for Award Management (SAM).

• Specific requirements for cyber incident reporting, safeguarding covered defense information, and NIST SP 800-171 compliance are detailed.

Form / Attachment / Pricing Sheet

This document, DD Form 1423-1 (Contract Data Requirements List), specifies the data items required from the contractor as part of the contract. It outlines what documentation and deliverables are expected beyond the primary goods or services.

• Data Item Number and Title: Identifies specific documents or data sets required (e.g., Delivery Schedule).
• Contract Reference: Links the data item to specific sections of the contract or SOW (e.g., C.4 and C.3.2.1).
• Remarks: Provides detailed instructions and context for the data item. For the 'Delivery Schedule' data item, this includes:
  • A description of the system to be delivered (mobile off-road test course and terrain measurement system).
  • Requirements for complete system documentation (operations, software instructions, maintenance).
  • A 12-month supply of the system after contract award.
  • A requirement for a delivery schedule outlined by PWS sections C.3.2.
  • The first delivery schedule is due no later than 20 days after award, with subsequent updates as necessary.
• Delivery Information: Specifies the recipient (Dominic Fonseca, US Army Aberdeen Test Center) and contact details.

This form is crucial for bidders to understand the full scope of contractual obligations beyond the core product or service. It details the specific documentation, reporting, and scheduling requirements that will be part of the contract, impacting proposal preparation and overall contract management. Bidders must ensure they can meet these data delivery requirements.

Form / Attachment / Pricing Sheet

This document is a Contract Data Requirements List (CDRL) that specifies the data items required from the contractor. It outlines the requirements for operational/maintenance manuals and training.

• Data Item: Operational/Maintenance Manuals and Training (Item D).
• Authority: 52.212-7001.
• Contract Reference: C.3.2.3.6.
• Frequency: One (1) Time submission.
• Remarks (Item 16): Details the vendor's responsibilities for developing and providing system operation and maintenance training. This includes classroom instruction, written materials, hands-on operation, training for users/operators and local maintainers, and local support maintenance training with system documents for troubleshooting, diagnostics, fault isolation, calibration, adjustments, removal/replacement procedures, and use of built-in test equipment.

This CDRL highlights the critical training and documentation deliverables expected from the contractor. Bidders should carefully review the remarks section to understand the scope and depth of the required training and manual development, as this will be a significant part of the contract performance.

Form / Attachment / Pricing Sheet

This document is a Contract Data Requirements List (CDRL) detailing a specific data item required for a contract. It outlines the "Final System Test" data item, which is a deliverable for the government.

• Data Item Title: Final System Test
• Contract Reference: C.3.2.4.1
• Authority: FAR 9.308-2
• Description of Work: The final system test will be conducted on ATC test courses, measuring performance across various terrains and obstacles. The results will be compared to existing measurements to ensure scanning accuracy and data capturability. The system hardware will undergo vibration testing as per MIL-STD-810H.
• Areas of Focus: Includes verification of sensor performance, data communications, integration results, user interface operation, data processing tools, and resultant information.
• Submission: A "One (1) Time" submission is required, with the first submission date to be determined based on the remarks (Block 16).

This CDRL specifies a critical data deliverable related to system testing. Bidders should review the detailed requirements for the "Final System Test" to understand the scope of testing, performance parameters to be verified, and the specific areas of focus. This information is crucial for understanding the technical requirements and expected outcomes of the system being procured.

Form / Attachment / Pricing Sheet

This document, DD Form 1423-1 (Contract Data Requirements List), specifies data items required by the government from a contractor. It outlines the specific data deliverables, their titles, and associated requirements for a particular contract line item.

• Data Item Title: "Initial System Test" is listed as both the System/Item and Subtitle.
• Authority: The acquisition is authorized under "2.4.1:8".
• Contract Reference: "2.4.1:8" is also noted as the contract reference.
• Requiring Office: Not specified.
• Frequency: "One (1) Time" delivery is required.
• Submission: The first submission is due by "See blk 16" (Remarks).
• Remarks: The initial system test involves verifying the system's ability to capture a 3D profile of test course features. The software must control the prime mover and process data. Scan results will be compared with existing measurements. Areas of focus include sensor performance, data communication, sensor integration, user interface, data processing tools, and prime mover operation over terrain.
• Distribution: Specifies "Final" and "Draft" copies are to be distributed to a specified addressee (block 14).

This form details a specific data deliverable, the "Initial System Test," which is crucial for understanding the performance verification and data collection requirements associated with the contract. Bidders should review the "Areas of focus" in the remarks section to understand the scope and objectives of this test, which will inform their technical approach and proposal development.

Form / Attachment / Pricing Sheet

This document, DD Form 1423-1, is a Contract Data Requirements List (CDRL). It specifies the data items required from a contractor as part of a contract. This particular entry details a "Design Review".

• Data Item Title: Design Review
• Subtitle: Design Review 2.3.1:6
• Requirement: A technical review to ensure a system can proceed into fabrication, demonstration, and test, meeting stated performance requirements.
• Vendor Responsibility: The vendor shall conduct the design review.
• Focus Areas: The review will assess the system's final design as captured in product specifications and detailed design documentation. Specific areas of focus include:
  • Detailed specifications of selected sensors' performance parameters.
  • Detailed interface specifications of selected sensors and the recording system.
  • Detailed sensor integration plan (if any) for the selected sensors' data.
  • Detailed sensor to prime mover integration plan.
  • Detailed user interface description.
  • Selection of the prime mover.
• Scheduling: The design review shall be scheduled by the vendor prior to the integration of the scanning system into the prime mover.
• Frequency: As many as required.

This form outlines a critical deliverable for the contractor: a design review. Bidders should understand the scope and objectives of this review, including the specific areas of focus and the vendor's responsibility for scheduling and conducting it. This information is crucial for understanding the technical expectations and project milestones.

Quality Assurance Surveillance Plan (QASP)

This document outlines the government's procedures for monitoring contractor performance to ensure it meets contract standards. It details what will be monitored, how, by whom, and how results will be documented. The QASP is a government-developed tool to assess contractor performance and is not part of the contract itself, nor does it duplicate the contractor's Quality Control Plan. Its goal is to ensure early identification and resolution of performance issues.

• Program/Project Manager (PM): Provides program oversight, nominates the COR, and supports COR assessment activities.

• Contracting Officer (KO): Ensures contract compliance, safeguards government interests, and makes the final performance assessment. (Assigned KO: Todd Strasavich, ACC-APG)

• Contracting Officer’s Representative (COR): Provides continuous technical oversight using the QASP, maintains a Quality Assurance file, reports performance problems to the KO, and provides annual performance assessments. The COR is the primary tool for documenting contractor performance.

• Surveillance Matrix (Attachment 1): Lists performance objectives and standards, detailing the method of surveillance the COR will use.

• Performance Objectives: Define desired outcomes.

• Performance Standards: Define the level of service required.

• Inspection Methodology: Defines how, when, and what will be assessed.

• Excellent / Outstanding: Meets and exceeds requirements.

• Very Good: Meets requirements and exceeds some.

• Satisfactory: Meets requirements with minor problems.

• Marginal: Does not meet some requirements; corrective actions are insufficient.

• Unsatisfactory: Does not meet most requirements; recovery unlikely.

• Performance Assessment Report (PAR): Used for overall performance evaluation.

• Customer Complaint Form: Records and tracks customer complaints.

• Corrective Action Report (CAR): Documents deficiencies and required corrective actions.

• Design Review: Verifying sensor specifications, interface specifications, sensor fusion plans, integration plans, user interface descriptions, and prime mover selection against SOW requirements.

• Initial System Test: Demonstrating sensor performance, data communications, sensor fusion results, system integration, user interface operation, and evaluating data processing tools and output.

• Final System Test: Verifying sensor performance, data communications, sensor fusion, system integration, user interface operation, and evaluating data processing tools and output.

Form / Attachment / Pricing Sheet

This document is an Excel spreadsheet serving as a cost breakout sheet for the Profilometer system. It is intended for bidders to provide pricing details.

• Total Price for System: A field to enter the overall system cost.
• Total Price for Threshold Requirement: A designated area to input the total price for the threshold level of the requirement.
• Price Breakout for Objective level requirement: This section requires bidders to price out only the difference between the threshold and objective requirements for specific listed Objective REQs (REQ-PM-01, REQ-PM-04, REQ-PM-07, REQ-SR-03 through REQ-SR-14, REQ-SR-17 through REQ-SR-19, REQ-SR-21, REQ-DR-02, REQ-DR-04, REQ-DR-06, REQ-DR-07).

Bidders must use this sheet to detail their pricing structure, specifically differentiating costs between threshold and objective requirements for the listed components. Accurate completion is crucial for proposal submission and evaluation.