Attachment_0045_PPMx_Characteristics.xlsx
XLSX spreadsheet 55 KB Posted
- Attached to
- Optionally Manned Fighting Vehicle (OMFV) Draft Request for Proposal (RFP) W56HZV-22-R-0026
- Solicitation number
- W56HZV-22-R-0026
About this file
This document contains a draft request for proposal for an Optionally Manned Fighting Vehicle program and related attachment providing characteristics for prognostics and predictive maintenance systems. The Army is seeking design, prototype build, and test services. Interested parties must submit any comments on the draft RFP and associated documents by May 2, 2022 using the provided comment resolution matrices. The draft RFP and certain attachments contain controlled unclassified information or classified details, and interested offerors must follow the instructions provided to request copies of these documents. The RFP relates to the Army's Optionally Manned Fighting Vehicle program to develop new ground combat vehicle prototypes.
View the file
Other files
Show all 49
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Cover
| Attachment 0045 |
| Prognostics/Predictive Maintenance (PPMx) Characteristics |
| Solicitation Number: W56HZV-22-R-0026 |
| Date: 29 March 2022 |
| Revision No.: 000 |
| Distribution Statement A: Approved for public release; distribution is unlimited. |
| SECURITY NOTICE: Contractor responses to the data requirements are likely to be at the Controlled Unclassified Information (CUI) level. |
| All CUI responses should be marked with the following CUI Designation Indicator and Distribution Statement: |
Controlled by: the name of the Offeror company (not required if identified in the letterhead) Controlled by: identification of the office creating the document CUI Category(ies): CTI, EXPT Distribution Statement: D POC: name and phone number or email of POC
DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors; Specific Authority: DoDM 5200.01 and DoDM 5200.45, date of determination is: 26 December 2018. Other requests for this document shall be referred to the attention of the PM Maneuver Combat Systems (MCS) Security Manager at: Program Executive Office Ground Combat Systems (PEO GCS), ATTN: SFAE-GCS-M, 6501 East Eleven Mile Road, Detroit Arsenal, MI 48397-5000.
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 Administration Act of 1979 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.
Change Log
| Revision # | Date | Change Description |
| 000 | 3/29/22 | a. Base Document |
(add additional rows as necessary)
Capability
| Sensor Name | Advanced Diagnostics and Prognostics | Vehicle Systems | |||||||||||||||||
| VHMS | CBM | PROGNOSTICS | BIT/BITE | Data Storage | Data Rate | Automatic Birth Records | Vehicle Performance | Drivetrain | Powertrain | Braking | Fuel Consumption | Processing Unit | Weapon System | Sensor Location | Interface Standard | Data Measurement | MOSA Compliant | Data Frequency |
| Y/N | Y/N | Y/N | Y/N | # of days | Units | Y/N | Y/N | Y/N | Y/N | Y/N | Y/N | Y/N | Y/N | Y/N | bits/second | ||||
| **Example** Transmission Oil level/Viscosity | Y | Y | Y | Y | 145 Days | 10 bits/second, 0.5 MB/year | Y | Y | Y | N | N | N | N | N | Main VHMS system | SAE-J1939 | |||
| PGN 65272 | Oil level/ Viscosity | Y | 11 bits/second |
| Instructions/Notes: |
| The Contractor shall tailor system sensor information as required by their proposed solution. |
| VHMS (Vehicle Health Management System): Yes/No - Does the sensor feed data to the VHMS? |
| CBM (Condition Based Maintenance): Yes/No - Does the sensor feed data to the CBM systems? |
| Prognostics: Yes/No - Does the sensor feed data to the prognostic systems? |
| BIT/BITE (Built-In-Test/Built-In-Test-Equipment): Yes/No - Does the sensor feed data to the BIT/BITE on the platform? |
| Data Storage: Expressed in number of days. |
| Data Rate: Units (e.g. bits/second, MB/year) determined by Contractor. |
| Automatic Birth Records: Yes/No - Are the data records automatically dated without user input? |
| Vehicle Systems: Vehicle Performance, Drivetrain, Powertrain, Braking, Fuel Consumption, Electrical, Processing Unit, and Weapon System are notional. |
| Sensor Location: Where is the sensor located? |
| Interface Standard: identification for data format. Specifications and standards may be applied, or references to HWCI/CWCIs. |
| Data Measurement: Units/measurement of data to be collected such as pressure, vibration, temperature, level, viscosity, etc. |
| MOSA Compliant: Yes/No - Is the sensor documented for use in OSMP and identified in alignment with applicable standards? |
| Data Frequency: Expressed in bits/second |
image1.png
File details come from the government source that posted it. Updated .