JTC TRS Q and A Matrix FINAL.pdf

General 1

Question Number Reference (CLIN, SOW, P-Spec, etc.)

Question / Comment Answer

001 Technical Data Package (TDP), to include drawings, current operational production software baseline (especially IOS/Host, Training Management System) , scenarios, Interface Control Documents

Does the Government own the technical data package (TDP) for the JTC-TRS or at a minimum, have Government Purpose Rights? If so, when will the TDP be made available to vendors?

Tech Data Package was sent out via bidders' library…you will need to specify what you feel is still missing.

002 N/A Can the government provide the appropriate CDRLs and DIDs? Posted on beta.sam.gov 003 Software Data Base H

Clauses pg 66, Para H001

Please provide Section J Attachment 7

Asset List posted via bidder's library.

PWS 2

(CLIN, SOW, P-Spec, etc.)

Question / Comment Answer

001 PWS, Section 2 The CDRLs table previously in section 2 has been deleted in the updated PWS.

Can you provide an updated complete list of CDRLs for the program including SCARS specific CDRLs identified in Appendix C of the PWS?

CDRLs are posted on beta.sam.gov

002 PWS, Section 3.12, JTC TRS Device Transition

The requirements in this section apply to commercial variants listed in Attachment 7 (2 domes, 4 desktop and 2 portable systems) and mandates installation of the "latest JTC TRS operational software baseline" on these devices.

Please clarify what is meant by "latest" software baseline -is this the baseline that exists prior to contract award, or is it the newly-proposed JTC TRS software baseline with any alternative software?

If the latter case, how would incompatibilities between the proposed software baseline and existing commercial variant hardware be addressed?

The "latest" software baseline would be the newly-proposed baseline. If a newly proposed JTC TRS software baseline is proposed, the expectation would be to wait until the newly proposed software baseline ECP process is complete on the existing JTC TRS devices before converting the commercial variants to the newly-proposed baseline. This PWS paragraph will be updated to clarify expectations on the conversion process. A new paragraph in PWS Section 3.15 will address JTC TRS Device Transition activiites.

003 PWS, Section 3.12, JTC TRS Device Transition

The requirements in this section apply to commercial variants listed in Attachment 7 (2 domes, 4 desktop and 2 portable systems) and mandates installation of the "latest JTC TRS operational software baseline" on these devices.

If a JTC TRS software baseline that contains alternative software components as compared to the current baseline is proposed, wouldn't this new JTC TRS Operational Software baseline need to be installed on all existing JTC TRS devices, not just the commercial variants?

If not, would two separate JTC TRS software baselines (current and proposed) need to be maintained and updated by the TSSC, and would two separate cybersecurity accreditations need to be maintained as well?

Yes, if a newly proposed JTC TRS software baseline is proposed, the expectation would be to wait until the newly proposed software baseline ECP process is complete on the existing JTC TRS devices before converting the commercial variants to the newly-proposed baseline. This PWS paragraph will be updated to clarify expectations on the conversion process. A new paragraph in PWS Section

3.15 will address JTC TRS Device Transition activiites.

PWS 3

004 PWS 3.12.2 JTAGSS

Device Transition

Will AFRL continue to develop/provide GOT Software for the JTAGSS over the course of the contract, or will all Software development/maintenance be transferred to the contractor?

AFRL will continue GOTS software support for several GOTS softwares. The full list of their support items will be provided prior to JTAGSS transition

005 PWS 3.13.5.4.3 Program Inventories and Audits

Where is ramp up contract transition pricing for teardown and reassembly? Any pricing in regards to ramp up contract transition? Inventories for all sites? Packaging and shipping where applicable?

1. The goal is to have the current contractor move the TSSC device and AFRL move the JTAGSS device; if necessary, so their would be no pricing for teardown and reassembly.

2. Pricing for contract transition…There will be a Ramp up CLIN included.

3. Inventories for all sites...no, only the GFE assets

4. Packaging and shipping...to move the GFE? If so, then no, we can have current contractor move the TSSC devices and AFRL move the JTAGSS device .

006 PWS 3.8.2.2 Cybersecurity and System Security Plans

"The contractor shall review and assist with implementing applicable directives to support the SSP and Cyber Policy Plans for the JTC TRS and JTAGSS enclaves."

Will an approved SSP already be generated and available for the JTAGSS system by contract award?

Yes, JTAGSS SSP will be available at time of transition

007 PWS, formerly section 2.0 Questions related to the JTAGSS device CDRLs:

1) If a CDRL does not currently exist for the JTAGSS devices, would the requirements for the CDRL to be submitted or updated be waived, or would a suitable CDRL need to be generated as a new document?

2) If suitable (new) CDRLs would need to be generated, where should the effort/cost for these new documents be captured with respect to the CLINs and Pricing Matrix?

No, the JTAGSS CDRLs in the Bidders library for those currently available. Any needed JTAGSS CDRLs would need to be generated, and would be priced via a Data CLIN in the Price Matrix. AFRL is on contract for more CDRLs than were included in the Bidder's Library. the full list of CDRLs will be provided prior to JTAGSS transition.

008 PWS 3.2 Systems Engineering (SE)

Paragraph 3.2 references the DID for a SEMP [DI-SESS- 81785, System Engineering Master Plan (SEMP)], but a SEMP was not listed in the CDRL list in the table in the previously released PWS Section 2.3. Is the SEMP a deliverable requirement?

Yes, the SEMP is included in the CDRLs, which will be posted on beta.sam.gov

PWS 4

009 PWS 3.4.3 Modification Testing

3.4.3 System changes must also be capable of using

current created training and mission rehearsal scenarios at each simulator location.

The current SAF/CGF, MACE, does not effectively support this. There are always minor things that don't seem to carry over in missions. If a list of scenarios to be maintained is provided, this requirement can be effectively estimated (as "system changes" would include updating the scenarios).

Updates should be designed to work with site scenarios in mind. It is inevitable that something the TSSC changes will impact a sites scenarios. Those issues will be remediated via the help desk. We do not intend to manage the scenarios used at each site, that is up to the site operator to maintain.

010 PWS 3.8.2.2 Cybersecurity and System Security Plans

Will a test plan for CS System Security Testing already be in place and available at contract award for the JTAGSS system? (Assuming it will already have an ATO)

There will be no System Security Test Plan, but all Cybersecurity policy plans will be available at JTAGSS transition

011 PWS 3.8.2.1 Architecture Analysis

PWS 3.8.2.1 reads: "The contractor shall complete an architecture analysis for each JTC TRS and JTAGGS training device configuration defining CS boundaries and data flows, and support the implementation of security controls and countermeasures for JTC TRS and JTAGSS training devices. Changes to initial configuration must be submitted to the Simulations Configuration Working Group for approval prior to fielding."

Will boundaries and data flows including any supporting documentation already be in place and available at contract award for the JTAGGS system assuming JTAGSS will already have an ATO by contract award?

Yes, all will be available at time of JTAGSS transition

012 PWS 1.2 Scope, Price Matrix, Draft CLINs

PWS section 1.2 states: "The JTC TRS Program will continue to procure, field and support upgradeable mission simulation systems (JTC TRS and JTAGSS)…", yet the Price Matrix and Draft CLINs document do not contain production CLINs or pricing for JTAGSS device production.

Will additional JTAGSS devices be procured under this effort, or does this program only provide continuing sustainment for already-fielded JTAGSS devices?

No additional JTAGSS device procurement is planned for this contract. JTAGSS will be a sustainment effort only.

PWS 5

013 PWS 3.10.6 Paragraph 3.10.6 states: "The contractor shall initiate DMO certification testing not later than 30 days after receiving Authority to Operate (ATO) for JTAGSS devices."

It was our understanding that JTAGSS devices had already achieved ATO or at least would achieve ATO prior to initiation of this contract. Also, DMO certification testing requires generation, submittal and approval of associated test plans in advance of initiating certification testing activities - this plan generation and approval process typically taking more than 30 days.

What is the current/expected status of the JTAGSS device with respect to ATO? Has (or will) a DMO certification test plan already been generated prior to contract award?

Current AFRL ATO will not be valid for WNS. A new ATO will be appliedfor under the JTC TRS contract. Only DMO cert testing initiation is required within 30 days

014 Attachment 1- JTC_TRS_PWS_PWS.pdf.

Appendix B: Database Development Requirements Section B-2 Required Training Databases.

How many of the “1. Specific Databases” currently exist and are installed or are available for installation on the JTC TRS? The table lists four as “original” plus 36 others.

All exist and are available for installation

015 Attachment 1- JTC_TRS_PWS_PWS.pdf.

Appendix B: Database Development Requirements Section B-2 Required Training Databases.

How many of the “2. Generic Databases” currently exist and are installed or are available for installation on the JTC

TRS?

All exist and are available for installation

016 Attachment 1- JTC_TRS_PWS_PWS.pdf, Appendix B: Database Development Requirements B-1 Database Requirements, Section B-2 Required Training Databases.

Do the existing databases in Section B-2 meet the requirements as stated in Sections B-1 and B-2?

Yes.

017 Attachment 1- JTC_TRS_PWS_PWS.pdf, Appendix B: Database Development Requirements

Assuming there is a requirement for database development and or integration for the JTC-TRS Program, under what CLIN are we to price this effort?

They will be priced via ECP

PWS 6

018 PWS 3.13.3.1 TSSC

Continual Support Actions

Within each CLS Reporting period over 30% of the reported defects are software related. Does the current TSSC have the responsibility to fix the existing software issues in the system?

Yes. Current TSSC will fix or resolve all current discrepancies prior to close-out

019 PWS Are the additional domes/desktop/portable systems part of the basic FFP or will they be requested and quoted after award?

Systems will be priced via Price Matrix, as Pre-Priced Options (PPOs)

020 PWS Are there any requirements to produce a prototype dome within 60 days of award? This was mentioned in the Industry Day slides but is not specified in the PWS.

No. Production ready device is needed within 180 days of contract transition

021 PWS There is no specified location for the TSSC. We envision a core team in Dayton, OH, but would like to leverage CLS and cybersecurity expertise from our primary development center. Does the government forsee specific TSSC work tied to a specific location?

No.

022 PWS Does the government forsee ongoing AFRL participation in future upgrades, DR corrections, or functionality improvments?

No. AFRL support will cease after JTAGSS transition (March 2021)

023 PWS, pg 28, Para 3.10.6.7

Will the government provide the contact information for the contractors listed in the Associate Contractor Agreement Section of the PWS?

No.

024 PWS, pg 28, Para 3.10.6.6

Our interpretation of the TAA requirements outlined in the PWS are not required until after contract award?

Any TAA would be after contract transition.

025 PWS, pg 34, Para 3.13.3 Is there a TSSC history available for evaluating TSSC tasking? (Engineering Service Memorandum, Engineering Change Proposal, etc.)

List of exisitng 1067's will be added to bidders' library

026 PWS, pg 43, Para 3.15.5 When will the recompetition data library be available and how can we access it?

Current recompetition library is the bidders' library

027 PWS, pg 23, Para 3.8.2.5 P-Spec, pg 82, Appendix H

Has an automated methodology for executing the monthly Cyber package/remote scanning at the fielded simulator sites been established? If so, is that exact procedure expected to be continued? If so, will that procedure be made available during the proposal effort?

Yes, there is a methodology for site cyber personnel (ISSO) to conduct scanning. There is no remote scanning requirement for the contractor There will be an automated process going forward, but it will not be available during proposal

028 PWS, pg 13, Para 3.2.1 PWS, pg 55, Appendix C

Has any SCARS capability/architecture been designed and built into the JTC TRS or JTAGSS?

Yes for JTC TRS.

029 PWS, pg 56, Appendix C PWS, pg 56, Section 4

Has any SCARS On-Premise Equipment been implemented at any JTC TRS or JTAGSS locations?

Yes for JTC TRS (at Dome device sites)

030 PWS, pg 30, Para 3.12 Please provide Section J, Attachment 11 – Asset List PWS will be updated to reflect Asset List as Attachment 7

031 PWS 6.0 Priced Upgrade Requirement

Will DACAS be included in the PSpec to enable accurate pricing per requirements in the PWS Section 6?

No. It was listed in the PWS to support DACAS as a PPO.

(CLIN, SOW, P-Spec, etc.)

Question / Comment Answer

001 PSpec 3.5.4.2 PSpec 3.5.4.2: Touch-screen communications equipment displays shall be accompanied by a compatible connector(s) for connection of any style of trainee headset or handset. The connector shall be appropriate for the radios being emulated. An M55116/1-03 5-pin connector is an example of a standard connector.

This requirement was one of the reasons the communication simulation was changed to an

ASTi solution at OU&E (2016). Suggest adding 3.5.4.2 as a SET requirement.

SET will be updated to add this requirement

002 Spec Paragraph 3.9.2.1.1, DMO MP Standards

The current JTC TRS baseline implements specific standards and capabilities inclusive of

CAF DMO MP-14 through MP-19.

Are these capabilities still required for the follow-on devices procured under this contract? If so, how will these capabilities be assessed?

We are not going to test DMO, it will be a requirement that is managed throughout the life of the contract, we will continue to make DMO updates.

003 Spec, Appendix G, Intro Paragraph

This paragraph states "JTC TRS DT upgrades will use existing student stations used by equipped units where possible." What does this mean?

This will be removed from P-Spec

004 Spec, Appendix G, Intro Paragraph

This paragraph states "The JTC TRS portable/deployable will utilize small flat or mildly curved computer monitors, 2D projectors, and a 3D head mounted display to permit training on all TAC and CFF tasks."

Are all 3 visual solutions (monitors, projector and HMD) required to be provided as standard equipment with the Portable devices?

The paragraph will be revised to state "The JTC TRS portable/deployable will utilize small flat or mildly curved computer monitors, 2D projectors, and/or a 3D head mounted display to permit training on all TAC and CFF tasks."

005 Spec, Appendix G, G.1.7.4 The paragraphs after this requirement appear to be missing headings (G.1.8 - G.1.12)

P-Spec will be updated to correct this issue.

006 Spec, Appendix G, G.4.1.3.2 This paragraph states that the Portable Display System "must be capable of using a projected flat screen display".

Are flat panel LED or LCD based displays also acceptable, or must all flat screen solutions utilize projectors? Should this read flat panel or projected display?

P-Spec will be updated to state flat panel or projected display.

007 Spec, Appendix H - Remote Scanning and Patching

The remote scanning and patching requirements are not included in the Section M

SET test plans.

If alternate JTC TRS baseline configurations are proposed, how will these requirements be verified?

This will not be tested during SET

008 Spec, Appendix H - Remote Scanning and Patching

In the current JTC TRS configuration, remote scanning and patching features are supported by a separate Cybersecurity Server housed in a separate "SCARS Rack".

Should the SCARS rack and Cybersecurity server be considered as part of the JTC TRS baseline, and should they be also provided with the follow-on device deliveries?

SCARS and the CSS should be part of the deliveries.

009 Spec, paragraphs 3.3.3.2 and 3.3.3.3

These requirements appear to be missing in this spec revision.

Paragraph 3.3.3 covers all the necessary requirements.

010 Spec Paragraph 3.7.6 and subparagraphs.

This section states that the JTAC instructor station sections become applicable when the respective CLIN(s) have been awarded.

Please clarify - the JTAC instructor hardware is not part of the JTC TRS standard Dome baseline and should not be included in the production unit pricing for these systems?

This is a part of the baseline, it should be included in any ACC deliverable drawing package and in the active revs of the drawing package. Instructor stations should be included.

011 Spec Paragraph 3.10.1.2.2 Is an uninterruptable power supply required with all JTC TRS device configurations, including the portable system?

UPS is not required for portables

012 Spec Paragraphs 3.13.4.1.4, 3.13.4.1.5, 3.13.4.1.6

These paragraphs provide specific requirement for Emergency Power Off (EPO) switches. Are EPOs required with all JTC TRS device configurations, including the portable systems?

EPO is not required for portables

013 Spec Appendix G, Paragraphs G.4.1.4 through G.4.1.18

These visual display requirements appear to apply to a multi-channel large scale dome display configuration. Please verify if these requirements would also apply to the desktop and portable display configurations.

These do not apply to desktop or portable configurations

014 PSpec - 3.7.3.1.10 (SAR);

3.7.3.1.9 and 3.7.3.1.11

(ROVER)

The PSpec calls out Rover and SAR capability but there is not SET to test this requirement.

Recommend including testing of these specifications with the SET.

Rover and SAR will be added to the SET

015 Spec missing Will a Performance Specification be provided for the portable system?

No. P-Spec is a combined Family of Systems (FoS) spec, including the portables

016 Spec - Confusion on applicability between dome, desktop and portable requirements

The Family of Systems approach to requirements can lead to some confusion on applicability of the requirements e.g. Spec

3.7.6 (JTAC Instructor Station) - is it applicable to domes, desktops and portables?

Perhaps having a table with applicability columns for dome, desktop and portable will help clarify the intent while still having a single requirements document.

We want a family of systems with a common set of hardware/software and the performance requirements are common for most of the systems.

017 P-SPEC Does the product baseline as defined within the Bidders' Library meet the requirements of the P-Spec.

Yes

Pricing Matrix 10

(CLIN, SOW, P-Spec, etc.)

Question / Comment Answer

001 Attachment 3, Draft Price Matrix

The AFSOC EME package contents are listed twice. From the related pricing, we assume that the second list should refer to the SOCOM configuration, versus the AFSOC configuration.

If so, also please verify the SOCOM configuration is identical to the AFSOC configuration with respect to EME types and quantities required.

Corrected; Should be SOCOM

002 Attachment 3, Draft Price Matrix

CLIN Series 6000 requests annual software license costs for dome, desktop and portable JTC TRS configurations.

If alternate software baseline components are proposed for follow-on devices to be delivered under this program, should these license renewals include renewal of the current software configuration licenses for already-fielded systems in addition to the new (alternate) software licenses for the newly-fielded devices under this program?

If so, we suggest that these costs be broken out in this manner, as software license upgrade costs are dependent on the specific software configuration and would therefore vary for currently-fielded versus newly-fielded devices.

All software, both the new solution and the legacy, will be required to be kept current until all devices have been coverted from current to the new baseline.

CLIN Series 6000 will be upated to include pricing options for the current and new (alternate) software licenses for the JTC TRS Dome, Desktop and Portable. This way we can exercise the CLINs based on the number of months needed for each configuration in relation to the device conversion date from the current to the new baseline.

Also, the price of any software suite for a new device should be included in the production CLINs of a device.

003 Attachment 3, Draft Price Matrix

CLIN series 8400 requests transition pricing for dome, desktop, and portable systems.

Should transition costs for all previously-fielded systems of each respective type be provided here, or only for those systems identified as commercial variants in the asset list?

Yes. PWS and CLIN structure will be updated to reflect.

Pricing Matrix 11

004 Attachment 3, Draft Price Matrix

Cybersecurity Support costs for CLINs 7000 - 7700 are requested on a per-year basis versus a per-device/per-year basis.

Should the additional per device cyber be included in this

CLIN?

In this case, how should additional cybersecurity costs related to as-yet to be delivered new devices be bid?

Should they be bid here or under Help Desk (per device)?

What is the expected ramp-up of new device deliveries?

Cyber costs should not increase per unit. We have type ATOs, and the government is working to simplify it even further to one ATO that covers both the dome and DT.

005 Draft Price Matrix For the Basic contract, Cell Z11 list the Cyber Security Support price and the footnote (2) (cell W34) states "(2) Cell Z11 represents the price of annual Cyber Security Support for all JTC TRS program. CLIN 7000 will be awarded with the basic contract. "

Is the intent of the pricing sought to include JTAGGS Cyber Security Support or just the Cyber Security Support effort for the JTC TRS components?

Yes, as it stands this includes JTAGGS.

006 Draft Price Matrix Price Matrix - Contract Options worksheet, CLIN 8400, Note 6 states:

"(6) The initial option for Software Enhancements will specifically exercise CLIN 8400. Option can be exercised more than once in a calendar year. All future options will be exercised as new FFP CLINs (i.e. 8401, 8402, etc.)"

Is this leftover from a previous version? There is no CLIN for Software Enhancements in the latest Draft Price Matrix.

Corrected; SW from previous verion, should be deleted.

007 Draft Price Matrix Price Matrix - Contract Options, CLIN 8400, Note 6 states:

"(7) The initial option for System Transitions will specifically exercise CLIN 8500. Option can be exercised more than once in a calendar year. All future options will be exercised as new FFP CLINs (i.e. 8501, 8502, etc.)"

There is no CLIN 8500, perhaps it should say CLIN 8400

Corrected

008 Draft Price Matrix "CLIN Series 8000 - Training, Relocation/Intrabase Moves, Software Enhancements", however there is no sub CLIN for "Software Enhancements"

Corrected

Pricing Matrix 12

009 Draft Price Matrix CLIN 8400 is for system transition. We assume it references the Device transitions as referenced in the PWS section 3.12. CLIN 8400 does not list the JTAGGS devices.

Yes; a JTAGSS transition CLIN will also be added.

010 Draft Price Matrix Where should we bid the contract ramp up and ramp down transition efforts?

PWS Section 3.15.2 has Ramp Down activities. Will update the PWS and add a CLIN to capture ramp up activities.

011 Price Matrix, Draft CLINs CLIN series 8000 covers training for what is assumed as all devices on the program. While training packages exist for current JTC TRS-based devices (domes and desktops), we are uncertain whether training materials for the JTAGSS devices are available to support these training sessions.

Does a JTAGSS training package exist, or would it need to be developed by the government or the contractor?

Unsure if JTAGSS has a training plan, if there is one, it would be provided by AFRL. Still need to research.

012 Draft Price Matrix, Tab 1 Cells E11 and E20 - should these be unit prices for the associated dome and desktop devices, or should these reflect the full price at the quantities requested (2 and 10, respectively)?

Full quantities. Unit prices should be reflected on the "Contract Options" Tab.

013 Draft Price Matrix, Tab 1 The prior version of the price matrix had cost entries for 3 month transition periods for Program Management and Cybersecurity Support. Why were these removed? Is there still a ramp-up period concurrent with the ramp-down of the current contract?

Yes, there is a ramp-up period concurrent with the ramp-down of the current contract? Will update the PWS and add a CLIN to capture ramp up activities.

014 Draft Price Matrix, Tab 1 If there is no transition period and associated cost entries per the answer to the previous question, where should contract ramp-up transition costs be bid? These would include testing, teardown, shipment, reinstallation and retest of the TSSC devices as part of their relocation to ta new facility. It would also include survey and inventory of each fielded device at all locations.

Intent is to have current contractor and AFRL teardown, ship, and reassemble their respective devices to the new

TSSC.

015 Draft Price Matrix, Tab 1 The CLIN Series 5000 CLS entries for CY'21 on this tab appear to overlap with similar entries for CY'21 CLS (Dome, Desktop, Portable and JTAGSS) on the tab 2 of this worksheet. What is the relationship between these corresponding cell entries on Tabs 1 and 2? Does the government expect that the cost entries for these items would be the same on Tab 1 and Tab2?

Correct, these would be the same.

Pricing Matrix 13

016 Draft Price Matrix, Tab 1 The CLIN Series 6000 Software Sustainment entries for CY'21 on this tab appear to overlap with similar entries for CY'21 Software Sustainment (Dome, Desktop, Portable and JTAGSS) on the tab 2 of this worksheet. What is the relationship between these corresponding cell entries on Tabs 1 and 2? Does the government expect that the cost entries for these items would be the same on Tab 1 and Tab2?

Correct, these would be the same.

017 Draft Price Matrix, Tab 1 The CLIN Series 7000 (Cybersecurity) and CLIN Series 8000 (System Transition) entries for CY'21 on this tab appear to overlap with similar entries for CY'21 items on the tab 2 of this worksheet. What is the relationship between these corresponding cell entries on Tabs 1 and 2? Does the government expect that the cost entries for these items would be the same on Tab 1 and Tab2?

Correct, these would be the same.

018 Draft Price Matrix Should the year one (CY'21) Cybersecurity costs include the costs associated with recertifying all devices cybersecurity baselines if alternate baseline components affecting the cybersecurity posture or device boundary diagrams are proposed? Should the cost to update the cybersecurity packages also be included in the CY'21 estimates?

If and alternate baseline is proposed, yes the 7000 series scope could cover those cost.

019 Draft Price Matrix, Tab 2 Why is system transition pricing (CLIN Series 8400) requested for all years of the proposed program? Wouldn't system transitions need to be completed within the first year or two years, to avoid a need to sustain and maintain cybersecurity for multiple baselines for each JTC TRS device type?

In the event more systems are purchsed outside of this contract with the same baseline. The USG would like the means to transition that system under the JTC TRS baseline. This may occur after the first two years of transitioning the system under the current contract.

020 Draft Price Matrix Should the year one (CY'21) and potentially additional years' CLS costs include the additional costs and effort associated with supporting and sustaining two device configurations (current and proposed, if different) during the system transition period?

All systems will need to be sustained regardless of the baseline. Proposed accordingly.

021 Attachment 3_Draft Price Matrix.xlsx, Price Matrix - Basic Contract Sheet, Note

(3) Cell R35

Should the following: "(3) CLIN 0002 will be awarded with the basic contract." reference CLIN 6000 (Dome Software Sustainment)?

Amended

Pricing Matrix 14

022 Attachment 3_Draft Price Matrix.xlsx, Price Matrix - Basic Contract Sheet, Contract Options Sheet

There appears to be a conflict between Note 4, Cell B37 (Basic Contract Sheet) "(4) CLINs 1000 will be awarded with the basic contract and will include the purchase, delivery, installation and related costs of 2 devices. " and note 4, Cell B 68 on the Contract Options Sheet. "(4) Initial option exercise will specifically exercise CLIN 1000, 1100, and 1200. Any future options will be exercised through a new CLIN (i.e. 1001, 1101, 1201 etc.)

Language Amended

023 Attachment 3_Draft Price Matrix.xlsx, Price Matrix - Contract Options Sheet, Note (5)

Please clarify/modify the note which states that two separate purchases [most likely separated by months] during a fiscal year will qualify for the anticipated lower price associated with a single larger purchase? E.g., a purchase of 8 systems in January 2021 and 3 additional systems in September 2021 (11 total in CY21) is not the same a purchasing 11 systems in either January or September 2021. The reason companies can provide volume discounts on pricing for larger orders are due to the efficiencies gained. Two separate purchases, entails two separate ordering processes for the vendor, two separate assembly and integration processes, two separate sets of tests, shipping, delivery and installation. Therefore, unless the two CLINS were exercised with near simultaneity, two purchases of 8 and 3 in the same CY should be priced as Qty. 5-10 for the 8 and Qty. 3 for the 3.

Noted

024 Attachment 3_Draft Price Matrix.xlsx, Price Matrix - Contract Options Sheet

The section containing cells E59 – L61 is titled “Desktop System Delivery and Installation. Should this be titled “Portable Unit Delivery and Installation?”

Amended.

025 Attachment 3_Draft Price Matrix.xlsx, Price Matrix - Contract Options Sheet

Please confirm there are OCONUS deliveries for the Portable Units. Please list locations/countries for the deliveries.

Confirmed

Pricing Matrix

Are there any requirements for suppliers to use Collective Bargining Agreement or Service Contract Act rates for CLS & TSSC employees; if CBA' s are in place, please provide the CBAs for each location?

No CBA's that the USG is aware of, the SCA will apply.

Minimum Rates and Fringe will have to be collected from the DOL.

PWS 6.1 / Pricing Matrix

Is the government updating the pricing matrix to include the option pricing for the Digitally Aided Close Air Support Option No

Attachments 15

(CLIN, SOW, P-Spec, etc.)

Question / Comment Answer

001 Attachment 11 Section L Draft, Paragraph 2.3.2.1 (SET Requirements)

This section states: "Solutions deviating from ASTi and/or DIScover will be tested in a desktop environment. " Issue:

If proposed JTC TRS solutions incorporate an alternate simulated Comms solution (i.e. other than the current ASTi-based solution), these may not meet the increased set of simulated comms requirements unique to the dome environment. These include the requirement to interface with multiple trainee-supplied military headsets and handsets, and the requirement to support multi-channel communications for multiple trainees, instructors and role-players within the JTC TRS dome device environment.

This was a particularly challenging set of requirements during the original dome device acceptance and JTAC MOA certification activities, where implementation and integration issues related to an alternate comms subsystem solution ultimately necessitated replacement with the current ASTi solution. Recommendation: If an alternate simulated comms solution is proposed for the JTC TRS follow-on devices, this solution should be tested in a dome environment, versus a desktop environment, to ensure the solution will meet the increased set of comms requirements

The JTC TRS Program understands that testing this capability on a desktop presents a level of risk. However, in order to have a competitive source selection, the program must set the conditions to allow industry to provide solutions the differ from a baseline, which currently contains proprietary software the the government has no control of.

002 Attachment 11 Section L Draft, Paragraph 2.3.2.1

Are the Assumptions Matrix and Technical Risk Matrix specified by Section L, Paragraph 2.3.2.1 included in the page limit for Volume II. Should it be incorporated into the Volume II narrative or can they be provided as appendices to Volume II?

Included in the page limit for Volume II

003 Attachment 11 Section L Draft, Paragraph 2.3.2.2

Is the Technical Risk Matrix specified by Section L, Paragraph 2.3.2.2 included in the page limit for Volume II.

Should it be incorporated into the Volume II narrative or can they be provided as appendices to Volume II?

Included in the page limit for Volume II

004 Attachment 11 Section L Draft, 2.3.2.1

Deviations from MACE, as a SAF, does not impact visual imaging and should not require Dome testing. Reconsider deviations from MACE needing to be tested in a Dome for this requirement.

The Program prefers to maintain ALL components of the current JTC TRS software baseline because significant investment has been made to ensure the system meets the P-spec and CAF DMO requirements. The testing requirement has been adjusted to help facilitate increassed competition, however the program can only accept a certain level of risk when considering alternative software components.

Attachments 16

005 Attachment 11 Section L Draft Attachment 12 Section M Draft

Why was the requirement to maintain GOTS software removed from the technical volume (Section L and M requirements)?

Strategy revised after first RFP DRAFT

006 General and Attachment 11 Section L Draft, Paragraph 2.3.2.1 (SET Requirements)

Recommend testing all EME in the Dome environment to ensure compatibility with 6 DOF requirement. Any deviation from the hardware that is inside the Dome should require testing in the Dome environment to ensure compatibility with the 6 DOF tracking system.

The JTC TRS Program understands that testing this capability on a desktop presents a level of risk. However, in order to have a competitive source selection, the program must set the conditions to allow industry to provide solutions the differ from a baseline, which currently contains proprietary software the the government has no control of.

Section L, Para 2.3.2.1

Paragraph states that solutions which differ from ASTI or Discover will be tested in a desktop environment. however, Appendix M1 - M6 does not delineate between a desktop test / verification of software integration if simply replacing DisCover, and a full dome scenario testing for replacing the visual engine or SAF. Will the USAF reduce the SET requirements for the desktop verification to test requirements which only validate software integration?”

The requirements are the requirements. The only differientiation is whether the SET takes place on a desktop or in a dome, base on what part of the software baseline is modified. SET Test Requirements outline which P-Spec items need to be tested for dome or DT.

Section L Attachment 10 pg 8, Para 2.3.2.1

Will the government provide a complete functional description of the Qauntadyn DIScover software utilized as part of this program?

Referenced in Software User Manual and SDD in Bidders' Library

Section L Attachment 11 pg 9, Para 2.3.2.2

To ensure fair and equal competition, is the government going to provide a standard licensing price for all offerors to utilize for the DIScover software? No.

010 Attachment 7-Asset List_05 Nov Update.pdf

There is no color key for this document. What does the red font represent?

AFSOC are the red font items

011 Attachment 7-Asset List_05 Nov Update.pdf

It appears that page 2 is a list of current locations for fielded systems, and page 3 may be a list of systems to be fielded during this contract. Can you confirm, please?

Page 3 are transition assets that are currently fielded and will be brought under JTC TRS contract sustainment

012 Attachment 7-Asset List_05 Nov Update.pdf

If page 3 contains the locations and quantities of systems to be delivered, the quantities and locations do not align with the quantities and locations (CONUS/OCONUS) provided in Attachment 3_Draft Price Matrix. Can you clarify, please?

Page 3 are transition assets that are currently fielded and will be brought under JTC TRS contract sustainment

Attachments 17

013 Attachment 7-Asset List_05 Nov Update.pdf

Assuming page 2 contains a listing of currently fielded systems, page 3 contains the list of to be fielded systems, it appears there is a requirement to produce and field 16 JTAGSS, plus reposition one for the TSSC. While this is consistent with requirements in the PWS, it is not consistent with Draft Sections L & M, nor the Draft Price Matrix. Please clarify.

The JTAGSS are already fielded at their operational locations. The TSSC unit will be relocated to the offeror's designated TSSC site

Scenarios 18

(CLIN, SOW, P-Spec, etc.)

Question / Comment Answer

001 M-1: G.24, G.27 Why are IG requirements sometimes not listed for the DT? JTC TRS is a family of systems which shall employ a common software baseline. The IG will be common across all configurations, unless noted differently.

002 M-1: G29 to G.34 Night scene (unaided) should be applicable to the DT? The DT should be capable of producing the same night scenes as the Dome systems. The reason it is not identified is that the JFS ESC Accreditation Requirement for night requires use of a trainee worn NVG or simulated device to accomplish the night training tasks.

003 M-1:G43, G44 The channel sync requirements should not be listed for the DTs, no channel sync needed and no blending required.

Requirement will be removed from the SET

004 M-3: S1.2 Does this requirement need to be done over SATCOM - if so then there is a cyphertext (CT) requirement implied. Will this be added to the SET requirements?

Yes. SET requirement will be updated.

005 M-4 Scenario 2, S2.7, S2.8 Why is illumination not required for the DT? The DT should be capable of producing illumination during night scenes as the Dome systems. The reason it is not identified is that the JFS ESC Accreditation Requirement for night requires use of a trainee worn NVG or simulated device to accomplish the night training tasks.

006 SET requirements Highlighting some aspects of the SET criteria that may have been overlooked:

a) Spec 3.3.3.6 was part of the original SET (2015), but not included now

b) G.1.3f4 and G.1.3f5 not included in the SET, but all other G.1.3f are included

SET criteria will be reviewed for needed updates

Scenarios 19

007 SET requirements Since the original Spec (rev. 8.0) there have been a number of updates to the Spec (current implemented Spec shall be at Rev. 9.5). The existing SET is almost identical to the original SET in 2015 and doesn't include many of the new additions to the Spec. that are important to determine the baseline configuration capability e.g.:

- configurable channels

- radio frequency scan capability

- digital and analog noise interference to the ROVER feed

- ROVER visual spectrum

- Tactical Chat

- Auto latch VRSG to master entity

- Synthetic Aperture Radar (SAR) capability at IOS

- JTAC instructor station (dome instructor)

- Have Quick Jamming

- Exercise IDs for Distributed Synchronized Playback

- Selectable dome compass

This information will be added to the P-Spec.

008 SET requirements The SET approach to determine applicability between DT and Domes is based on a software criteria only. A significant driver of performance also includes hardware.

Some of the HW requirements are currently not being tested in the DT based on just having MACE and VRSG e.g.:

- visual display performance and alignment (to include blending software),

- 1 IOS to multiple student communications (to include comm plan setup),

- EME e.g. M4, IZLID Recommend HW changes in these areas require testing in the dome.

In order to have a competitive source selection, the program must set the conditions to allow industry to provide solutions the differ from a baseline, which currently contains proprietary software that the government has no control of.

Bidder's Library 20

(CLIN, SOW, P-Spec, etc.)

Question / Comment Answer

001 Bidders' Library Bidder's Library The software baseline from the reprocurement package lists Q-Fires applications. Is Q- Fires a required element of the preferred soluton?

No.

002 In \Bidders Library\JTC TRS Bidders Library SVD docs\QD03830R-6015-

A012_JTC TRS SVD-

signed.pdf Section 3.6 Installation Instructions

Section 3.6 Installation Instructions Software is installed on each device prior to delivery. Any installation instructions, for software, cyber security updates or maintenance, shall be provided to the device maintainer/operator as needed by the TSSC.

Q: Can the above referenced installation instructions for software be provided during the RFP phase?

Yes, updated SVD can be provided with the installation instructions

003 In \Bidders Library\JTC TRS Bidders Library SVD docs\QD03830R-6015-

A012_JTC TRS SVD-

signed.pdf

The following configuration files are listed as part of the JTCTRS software package:

- MACE configuration files -IOS RADAR configuration files -System Startup and configuration files -IOS station files -System Startup and configuration SW -VRSG Configuration files

Q: Is there any cold start procedures for JTCTRS, if yes, can they be available?

Q: Are the above JTCTRS software configuration packages available to industry during the SET period?

An updated SVD (A012) will provide the instructions to load the software package. A013 disk with executables will be reloaded into bidder's library for cold start procedures, to be used with CDRL A013

004 In Bidders Library Q: Will the drawings and documentation (such as the JTCTRS Operation And Maintenance Manual) be available in source format so that it can be updated and edited as necessary to document changes.

Yes, after contract close-out

005 In Bidders Library There are no documented installation procedures for JTC TRS as part of the bidders library.

Q: Is the software installed using coldstart procedures or software images?

Q: Can either the coldstart procedures or software images be available in the bidders library prior to RFP?

Software installed using cold start procedures. An updated SVD (A012) will provide the instructions to load the software package. A013 disk with executables will be reloaded into bidder's library for cold start procedures, to be used with CDRL A013

Draft RFP 1 - QD 21

Question Number

Reference (CLIN, SOW, P-Spec, etc.)

Question / Comment Answer

001 Instructions to Offerors Really Section L

JTAGSS Footprint. Will facility layout drawings be available for the JTAGSS? JTAGSS Training Facility Report posted as part JTAGSS CDRLs

002 Instructions to Offerors Really Section L

2.3.222 Evidence of capability to manage and maintain GOTS software code.

What is the current list of GOTS Software?

JTAGSS Computer Software Product and Software Design Document CDRLs released on DOD Safe and in TSA III site

003 Performance Specification Is there a Performance Specification for Portable systems? Yes, JTC TRS Performance Specification released as Attachment 2 of Draft RFP

004 Performance Specification Is there a Performance Specification for JTAGSS systems? Yes, JTAGSS Performance Specification released as Attachment 2 of Draft RFP

005 Performance Work Statement

Are all design CDRLs for JTAGSS and the Portable available? Such as drawings, O&M, SVD, test procedures, design criteria data.

JTAGSS design CDRLs released on DOD Safe and in TSA III site; Portable is still being developed

006 Performance Work Statement

3.4.3 ...new Operational Utility Evaluation, gain JFS ESC Sim Accreditation...

This is a change from current practice and may result in greater time span between software updates getting to the user. Is the intent to have an OUE after every major software update or to perform a Design Acceptance Test (DAT) instead?

Accredidation and OUE will not be required for every update/mod

007 Performance Work Statement

3.4.3 System changes must also be capable of using current created training and mission rehearsal scenarios at each simulator location.

The current SAF/CGF, MACE, does not effectively support this. There are always minor things that don't seem to carry over in missions. If a list of scenarios to be maintained is provided, this requirement can be effectively estimated (as "system changes" would include updating the scenarios)

Help desk will fix any bugs, we are not maintaining common scenarios

008 Performance Work Statement

3.8.2.1 System Security Plan (SSP)

Will an approved SSP already be generated and available for the JTAGSS system by contract award?

Approved JTAGSS SSP will be generated prior to JTAGSS transition

009 Performance Work Statement

Section 3.8.2.2 System Security Testing Will a test plan for CS System Security Testing already be in place and available at contract award for the JTAGSS system? (Assuming it will already have an ATO)

No Sys Sec. Test plan. All CS policy plans will be available at JTAGSS transition

010 Performance Work Statement

Section 3.8.3 Architecture Analysis Will boundaries and data flows including any supporting documentation already be in place and available at contract award for the JTAGGS system assuming JTAGSS will already have an ATO by contract award?

Yes, at time of JTAGSS transition

011 Performance Work Statement

Section 3.10.6 Distributed Mission Operations (DMO). Last sentence:

"The contractor shall initiate DMO certification testing not later than 30 days after receiving Authority to Operate (ATO) for JTAGSS devices".

Can the contractor assume the JTAGGS will have an approved ATO prior to contract award?

Current AFRL ATO will not be valid for WNS. A new ATO will be appliedfor under our contract. Only DMO cert testing initiation is required within 30 days.

Draft RFP 1 - QD 22

012 Performance Work Statement

Section 3.8.1.1 Software Assurance Is it the intent of the government that the contractor perform Source Code Analysis on JTAGSS software that was developed by AFRL? And is it the intent of the government that the contractor remediate any findings to AFRL developed applications?

AFRL will provide an initial GOTS software assurance evaluation as part of the transition to WNS. The JTC TRS will then submit that certification to the OTI authorizing official (AO) for approval. The contractor will sumit to the JTC TRS program office a source code accrediation for any major release to the established GOTS baseline. If there are any source code vulnerabilities, the contractor will assist in the redmediation of those items before placing the major release into production.

013 PWS 3.12.2 - Will AFRL continue to develop/provide GOT Software for the JTAGSS over the course of the contract, or will all Software development/maintenance be transferred to the contractor?

AFRL will continue GOTS software support for several GOTS softwares. The full list of their support items will be provided prior to JTAGSS transition

014 PWS 3.13.2.5 Helpdesk … "No less than 8 hours per duty day ... at all duty locations, worldwide".

Is the intent to have the helpdesk support all locations (worldwide) for their respective duty days? i.e. support Kadena for 8 hours as well as Tacoma for 8 hrs?

That is correct. 8 hours per duty day, all locations

015 Draft CLINs, Price Matrix TSSC CLS and SW sustainment CLINS are on a per-device type basis, while cybersecurity is not. There is a recurring element of CyberSecurity support that is a function of the types and numbers of devices fielded. Also Cyber for JTAGGS will differ from JTC TRS. Suggest Cyber CLINS be broken out by device types, or at least split between JTC TRS baseline devices and JTAGSS.

Cyber costs should not increase per unit. We have type ATOs, and we are working to simplify it even further to one ATO that covers both the dome and DT. ISSO performs the monthly scans at each site, so there should not be a per unit cost.

016 Draft CLINs Will Cybersecurity Support costs for CLINs 7000 - 7700 be billed on a per device basis, or a per-year basis? If per-year, how should additional cybersecurity costs related to as-yet to be delivered new devices be bid?

Cyber is a yearly price. Cyber should NOT be per device.

017 Price Matrix, PWS 3.13.3.8 The Price Matrix includes inputs for Software Enhancements (CLIN 8200), with no nomenclature or quantities listed. How should these be priced? Would this CLIN just cover the integration, testing and deployment efforts to provide the semi-annual software updated called out in PWS 3.13.3.8, or is it intended to also cover the development efforts for future software upgrades and feature enhancements? If the latter, how would this be bounded, in the absence of specific requirements for these future upgrades?

Requirement removed

018 Price Matrix, PWS 3.13.3.9 Can this CLIN be modified to allows software enhancements for JTC TRS-based devices (domes, desktops and portables) to be bid separately from JTAGSS-related software enhancements?

Requirement removed

Draft RFP 1 - QD 23

019 Price Matrix, PWS 3.12.2, Draft CLINs

What is the intent of the System Transition CLIN? How does this differ from Contract Transition? Should the JTAGSS devices be included in the pricing matrix for this CLIN, since JTAGSS device transition is identified in PWS paragraph 3.12.2?

JTC TRS system/contract transition requirements are the same and will be added to PWS Section 3.15.