220308_JLTV-FoV_RFP_QAs.pdf

PDF 93 KB Posted

Attached to
Joint Light Tactical Vehicle (JLTV) Family of Vehicles (FoV) Follow-On
Solicitation number
W56HZV-20-R-0072-JLTV-FoV_RFP_QAs
Issued by

About this file

This document contains government responses to industry questions on a solicitation for the Joint Light Tactical Vehicle (JLTV) Family of Vehicles (FoV) Follow-On program. The Department of the Army Materiel Command TACOM Life Cycle Management Command posted responses to clarify requirements around vehicle processors, boot sequences, virtual machines, documentation standards, legacy data, and pricing matrices. Offerors were directed to amend proposal sections and contract data requirement lists based on the questions and answers provided. Key details included clarification that each vehicle processor require a unique password, boot and initialization sequences must enable user interaction within set timeframes, legacy performance data and models could not be shared due to lack of data rights, and the correct contract line item for earned value management was identified.

View the file

Other files

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

ID Subject / RFP Reference Question Government Response

1 VRTECH BIOS password/ PDFOV-X-146 Clarification. Does each fielded VRTEC processor need a unique password?

Each VRTECH shall have a unique password prior to Government acceptance.

2 VRTECH shall boot/load/execute/ PDFOV-X-147 Does this mean a secure boot up?

Yes. The Government is not specifying the technical approach, but a method to allow only trusted software to execute including during the boot process.

3 VRTECH RTOS/ PDFOV-X-103

Does this mean starting boot sequence or full boot sequence?

As long as the engine is able to run or glow module delay initiated within 10 seconds the requirement has been met.

6 VRTECH VM#1/ PDFOV-X-44 Does this mean only initiate or full boot up in 30 sec?

As long as the user is able to interact with the management functions within 30 seconds the requirement has been met.

8 VRTECH VM#2/ PDFOV-X-139

Need to clarify that the wired/wirelessly export and display is not a part of each power-up automatic update sequence. These actions will be operator initiated.

PDFOV-X-36 requires maintainer or administrator authentication prior to data transfer and is therefore not an automatic update sequence.

9 C.2.1.1.1.2.11.1

When referencing the most recent ISO/IEC/IEE 15289 (fourth edition 2019-07), it was found the specification ends with section 10.74. The requirement in C.2.1.1.1.2.11.1 references sections 10.77, 10.75, 10.76, 10.88, 10.77 (a second time), 10.79, 10.80 none of which are in the document. In another example, section 10.42 (software interface description) is not a correct reference, 10.42 is the Project Management plan and software interface document is not in the standard. Can the USG please clarify the version of the standard that should be referenced or clarify the sections of ISO/IEC/IEEE 15289 that desired for each deliverable of documentation?

The SOW references the 3rd edition 2017-06 of

ISO/IEC/IEEE 15289.

10 CDRL B031

To save time and effort in FEA meshing, can USG provide the original legacy FEA models of JLTV variants?

The Government does not have data rights suitable to release the requested legacy information.

11 Attachment 0113 Can USG provide the legacy input data for JLTV?

The Government does not have data rights suitable to release the requested legacy information.

12 Attachment 0114 Can USG provide the lagacy data developed for JLTV?

The Government does not have data rights suitable to release the requested legacy information.

13 L.2.2.5 Can the USG provide the Link to the correct address for classified submission?

Requests shall be submitted to the following email address: usarmy.detroit.acc.mbx.dta-jltvfoc@army.mil

15 B008

Referencing CDRL B008 the CDRL requires submission IAW C.2.1.1.1.4.10. There is no C.2.1.1.1.4.10, is this a typo and should the reference read C.2.1.1.1.2.10 as is indicated in Block 5?

Section C reference should be C.2.1.1.1.2.10. Block 16 of CDRL B008 will be amended.

16 L-28

SoW Section C.3.1.5 (pg. 124) indicates that EVMS is only required for STS work directives; but, Section L-28 (pg.

272) does not indicate this. Would the Government please confirm that the only CLIN for which an EVMS is required is CLIN xx26 – Systems Technical Support?

EVMS applies to cost type efforts IAW DFARS 252.234-7001 and 252.234-7002 . As a result, Section C.3.1.5 was moved to C.1.4.4 and the SOW to CLIN Crosswalk under Attachment 0170 has been updated.

17 L-28 Must the requirements of L-28 be met at proposal submission? If so, would the Government please advise what volume this documentation be associated with?

Section L.4.4 will be amended to clarify L-28.

18 L.4.5 through L.4.8

Proposal Sections L.4.5 - L.4.8 appear to fit as a 3-level sequencing within the Administrative Volume 4 after L.4.4.5.

Would the government consider specifying these as the following sequence: Small Business Subcontracting Plan (L.4.4.6); Facility Clearance (L.4.4.7); Cost Accounting System (L.4.4.8); Assertion of Restrictions (L.4.4.9)?

Alternatively, please provide further instruction on how and where to meet these requirements since they fall outside the defined volume structure and no other alternative has been provided.

The items in L.4.5 through L.4.8 should be submitted as part of the Administrative Volume.

SECTION L – Instructions, conditions, and notices to offerors L..2.1 Proposal Content L..2.1.1

L.2.1.2 EXSUM

Questions submitted prior to Release 3 and the Final RFP Release asking for clarification on the page limit indicated a revised, unlimited page count for Volume 4:

Administrative. However, the FINAL RFP still requires the 6-page limit.

Will the USG consider making Volume 4: Administrative unlimited in page count?

Section L.2.1.1 will be amended to change page limit of Volume 4: Administrative Volume from 6 pages to Unlimited.

Section L.2.1.2 will be amended to remove reference to the Adminstrative Volume page limit, however, the Proposal Executive Summary page limit of 3 pages will remain.

20 L.4.3.2(c):

The USG did not update this information. We believe the Tab is “Contract Cost Price Summary” and the Cell is “N56, please confirm.

Tab is “Contract Cost Price Summary” and the Cell is “N56." Gov't will amend L.4.3.2(c) to incorporate this change.

C.2.1.2.2.3 B024

By order of precedence can it be assumed that the 120 day requirement for submission of the HSIPP in C.2.1.2.2.3 supercedes the B024 requirement of the HSIPP initial submission of 60 days ACA?

120 calendar days after contract award. CDRL B024 will be amended to change block 16 from 60 days ACA to 120 calendar days ACA.

C.2.1.2.2.3 B024

Can the original JLTV HSIPP be provided by the USG so that it only needs to be modified for ECPs?

No HSIPP exists under the current JLTV production contract.

23 C.2.1.1.1.2.2.2

CREO Config files question.

Will these CREO files be provided?

Creo ModelCHECK Creo_Configs Materials Symbols

These files are available for release and can be delivered via DoD SAFE. Please submit request with your name, email, company, and Cage Code to: usarmy.detroit.acc.mbx.dta-jltvfoc@army.mil

24 H.5.3.2 Please clarify which attachment "Attachment XXX" refers to.

Attachment 0180 - Specifically Negotiated License Agreement TDP and CSP Purchase Option.

Amendment will be issued to update section H.5.3.2.

26 C.2.1.1.1.2.11.2 Please calrify whcih version of CMMC is required, Version

1.0 or Version 2.0.

CMMC is not required at contract award and should not be included in the offerors proposal, however, CMMC is anticipated to be a future requirement and would be incorporated into the contract via modification. C.2.1.1.1.2.11.2 will be amended to clarify this requirement.

C.2.1.1.1.2.11.20 B038

Software Assurance Evaluation Report - B038 - Block 4 calls out DI-IPSC-82248A but that item does not exist when searched for. Item DI-IPSC-82249A "Software Assurance Evaluation Report (SAER)" does exist. Please confirm that Block 4 of B038 should call out DI-IPSC- 82249A or please provide a copy of DI-IPSC-82248A if that is the correct Authority.

The correct DID is DI-IPSC-82249A. Gov't will amend CDRL B038, Block 4 to make this correction.

29 E.6

The contractor shall provide a separate data submission to support Government Analysis for each specified Analysis requirement IAW Attachment 0101 - JLTV Purchase Description (JLTV PD).

(CDRL E006, Analysis Requirements). Will the governement provide an updated Exhibit E that includes CDRL E006 Analysis requirements? Right now it appears that CDRL E005 is duplicated on pages 8 and 9 of Exhibit E.

Exhibit E will be amended to correct this.

30 Attachment 0170 - Pricing Matrix

Kit Quanity Summary Tab - Row 27 UTL. Drawing 19207_12602472_G does not identify the MBIK Modular Equipment Enclosure (MEE#2) - Expansion Kit for the UTL variant. However, the Kit Quantity Summary Tab in Attachment 170 shows potential quantities for the UTL variant. Additionally, there is not a kit drawing to support pricing for the UTL variant in the TDP. Will the government provide the correct Kit drawing for the UTL variant?

There is no MBIK for the UTL. There is only an MBIK for the GP and HGC.

Sheet1

File details come from the government source that posted it. Updated .