Inactive

SOURCES SOUGHT NOTICE Joint Light Tactical Vehicle (JLTV) Data Logging for Predictive Logistics 1. Overview: The desired Predictive Logistics system capability shall demonstrate the performance charac... SOURCES SOUGHT NOTICE Joint Light Tactical Vehicle (JLTV) Data Logging for Predictive Logistics 1. Overview: The desired Predictive Logistics system capability shall demonstrate the performance characteristics detailed below. Safety- System shall provide recommendation on the collection of data that supports driver/occupant safety. System shall demonstrate how data collection can be used to avoid accidents such as rollovers or oversteering or notify the operator of unsafe driving habits. Predictive Logistics-Use vehicle data and the collection of vehicle data to make informed and proactive decisions on part replacement or deferred scheduled maintenance. System shall gather, store and distribute data that supports fleet performance metrics such as fuel efficiency, DTCs, battery metrics, downtime. System shall be capable of proposing and providing a complete list of metrics with current on-platform sensors. In addition to proposing and providing a complete list of metrics with additional on-board sensors. FRACAS-System shall collect, store and distribute data that supports Failure Reporting, Analysis, and Corrective Action System (FRACAS). System shall demonstrate how data collection can be used to identify failures and the associated failure modes. The data collected should be tagged with a corresponding time for future analysis. A data slot for the current terrain the vehicle is operating on should also be available. The information requested in this announcement is being sought for informational planning purposes only and does not constitute a request for proposal or a commitment by the Government in any way. All information is to be furnished at no cost or obligation to the Government. There is no solicitation available at this time. 2. JLTV Program Overview: The JLTV Family of Vehicles (FoV) is comprised of two variants: a four-seat and a two-seat, a companion trailer, and associated kits. The four-seat variant vehicle platforms include the General Purpose (GP), the Heavy Guns Carrier (HGC), and the Close Combat Weapons Carrier (CCWC). The two-seat variant has one base vehicle platform which is referred to as a Utility (UTL) vehicle. Each vehicle platform will be configured through the installation of mission packages as defined in Annex K of the JLTV Purchase Description (PD). 3. Clarification of this Request: This is a Market Survey and not a Request for Proposal (RFP) or an announcement of a forthcoming solicitation. No solicitation document exists at this time nor will responders be placed on a solicitation mailing list. Providing a response to this notice is completely voluntary and no reimbursement will be made for any costs associated with providing information in response to this market survey or any follow-on requests for information. The Government will not rank submittals or provide any reply to interested firms. 4. Scope of Work (SOW): The objective of this effort is market research of potential data logging systems that support predictive logistics. There is currently no existing SOW for this effort, however, the information below may be used as general SOW inputs to assist with answering the questions in the “Questionnaire” section of this document: The supplier shall provide JLTV Installation Kits which have been manufactured in accordance with the requirements and specifications contained in the JLTV Installation Kit Technical Data Package (TDP). The TDP can be made available to interested suppliers upon request. 5. Disclaimer: a. The Government is not obligated to protect unmarked data. The Government is not obligated to protect like data in possession of third parties, or, for data which is afterwards placed in the public domain by the Contractor or by third parties through no fault of the Government. In the event the Government needs to reproduce the protected data for distribution purposes between Governmental offices, all data will be reproduced with restrictive markings. Prior to receiving copies of protected information, Government personnel will sign a Non-Disclosure Agreement (NDA). The signed NDA alerts personnel of the proprietary nature of the information being provided and the Government’s obligations to protect such information. b. This is not a pre-solicitation notice or RFP nor will a contract be awarded from this announcement. c. Participation in this survey is wholly voluntary on the part of the Contractor and no reimbursements will be made for costs associated with its participation in the survey. d. Information provided regarding the Government’s potential contracting strategy and the composition of support and products contained in an actual contract issued for the USG’s prospective requirements is subject to change. e. Data submitted to the Government will not be returned but will be archived as part of the survey’s historical records. The Government does not owe a response to any Contractor who submits information to this survey. f. Participation in this Market Survey is neither mandatory nor is it requisite to being deemed responsive to a future RFP that might materialize as a result of USG anticipated life cycle requirements. 6. Proprietary Information: The Government acknowledges its statutory and regulatory obligations under the Federal Acquisition Regulation (18 U.S.C. §1905) to protect confidential information provided to the Government. Pursuant to this statute the Government is willing to accept any trade secrets or proprietary restrictions placed upon qualifying data forwarded in response to this survey and to protect such information from unauthorized disclosure, subject to the following: a. Qualifying data must be clearly marked TRADE SECRETS or PROPRIETARY and be accompanied by explanatory text stating the rationale to protect the information. b. Only mark the specific data that is a trade secret or proprietary. c. Do not mark data that is already in the public domain or is already in possession of the Government or third parties on an unclassified basis. d. Proprietary data transmitted electronically must have the TRADE SECRETS or PROPRIETARY markings on both the cover of the transmittal e-mail as well as at the beginning of the file. Proprietary information contained within the correspondence shall use the markings: “PROPRIETARY INFORMATION BEGINS” and “PROPRIETARY INFORMATION ENDS.” 7. Instructions for Completing Questionnaire: Organizations who deem themselves qualified and who would be interested in competing for such a contract are asked to complete the questionnaire contained in Section 9 below and provide written responses electronically via email to Guadalupe Garcia, Contract Specialist, at guadalupe.r.garcia27.civ@army.mil. The Government will not accept any telephone inquiries or comments regarding this survey – NO EXCEPTIONS. All questions, comments, and/or concerns must be included in your survey response. Additionally, Mr. Garcia will not schedule personal visits for the purpose of discussing this announcement. Emails or phone calls requesting personal visits will not receive a reply. The Government may release questions (and the respective answers) asked by Industry in response to this survey at its discretion. 8. Response Format: Responses shall be provided electronically in Microsoft (MS) Office 2013 or Adobe Portable Document Format (PDF) compatible format. For files in PDF format, scanners should be set to 200 dots per inch. All MS Word files shall be based upon the use of standard 8.5 x 11 inch paper with a minimum font size of 8 point and with a minimum of 1 inch margins. Schedules, drawings and other documents more appropriate to larger paper may be formatted no larger than 11 x 17 inch paper. All spreadsheets must be in Microsoft Excel format and include all formulas, function, macros, computations, or equations used to compute the proposed amounts. For each workbook, all rows, columns, cells, and worksheets must be visible. Zero height and zero width rows and columns in worksheets are not acceptable. Worksheet cells formatted with the font color equal to the fill color are unacceptable. If workbooks or worksheets are password protected then the passwords must be provided. Responses shall not contain citations for or active links to live internet sites or pages. You may use multiple email messages if necessary. The subject line must include the message number (e.g., 1 of 3, 2 of 3, and 3 of 3), organization name, and “Response to JLTV PL Market Survey” (Example: Response to JLTV PL Market Survey, JPO JLTV PCO, and Message 1 of 1). 9. Questionnaire: Interested organizations are asked to complete the following questionnaire and provide electronic responses back to Mr. Guadalupe Garcia, no later than 0400 PM EST, March 07, 2023. If desired, responses may solely address the question number so as not to repeat the question in each response. Please spell out acronyms in their first instance. Clearly mark any confidential information per the accompanying market survey guidance. Please answer all of the questions in this Questionnaire. Avoid using “Not-Applicable” type answers. Generic What is your company’s expertise area? What are some benefits you forecast with implementing your solution? What are the challenges with integrating a 3rd party data collection system onto a vehicle? Will your proposed solution come as a standalone kit or use sensors and technology integrated with current systems? Will you be customizing a system already fielded or creating a new system specifically for this application? What is the weight associated with the additional hardware for your system? What size profiles will your hardware fit into? What communications network does your system operate on? [J1939?] What is the level maintenance required by the maintainer? What fleet size will you need to get adequate data? What is the Technology Readiness Level (TRL) of your product? How did you verify this information? Sensors 12. How can you implement accelerometers to detect unsafe conditions for the occupants (unsafe g forces, vibrations, etc.)? 13. How can you implement accelerometers to detect unsafe conditions for the vehicle (rollovers, oversteering, approaching safe vehicle operating limits)? 14. What method do you plan to collect data from the sensors? 15. Is there a limit to the number of sensors you can add to the system? 16. How can your system integrate with sensors that are already present? 17. How can you consolidate sensors to collect data efficiently? Collection Method 18. What method do you use for data collection? 19. Do you use a standard sample rate? Would this change for each sensor type? 21. How does your system handle errors/flaggable events that occur in between sample rates? 22. Can your system support variable sample rates? 23. What method of data storage will be used? Will the data overwrite itself to conserve space? 24. What ways can your system aggregate data during and after collection? Data Distribution 25. What format can your system read and write data to? 26. What data export infrastructure will your system use? Can it be done manually as well as automatically? 27. What hardware will be necessary for data to be exported from your system? 28. Can the data distribution be turned on and off manually or remotely? 29. Where is the data exported to? Is there a limit to the sources the data can be exported to? 30. Who has access to the data while it is being collected? Who has access to the data after it is analyzed? Analysis 31. How can your data collection system be used to support FRACAS efforts? 32. What support will your company provide in the way of recommendations as a result of the data analysis? 33. What failure mode data would you need access to make informed analysis? 34. Is there a minimum amount of data you would need to start effective analysis and provide meaningful recommendations? Software 35. Does the data in your system, and your system as a whole, have any resiliencies to cyber-attacks? 36. How will your system handle software updates? 37. Subsystem Specific 38. What data can be collected to monitor fuel efficiency? 39. What data can be collected to monitor shift points? 40. What data can be combined to create a driver safety profile? Cutting Edge 41. What new technologies can you implement into this system to increase capability? 42. Do predictive algorithms fall within your company capability? 43. What is the modularity availability to allow for senor swaps as new technologies are developed? 44. Does your system have Artificial Intelligence data analysis capabilities? Does your solution use an open architecture? If so, what sensors/technologies can be integrated from other companies?