Industry-Day Questions_ao20250513.pdf

PDF 253 KB Posted

Attached to
Sources Sought for P3I Industry Day
Solicitation number
P3I-25-0002
Issued by

About this file

This document contains a comprehensive set of questions and answers from an Industry Day event for the Tactical Intelligence Ground Station (TIGS) System of Systems (SoS) contract. The document reveals key details about a planned Multi-Award Indefinite Delivery/Indefinite Quantity (MAIDIQ) contract aimed at developing and producing various TIGS variants over a 25-year lifecycle with an estimated $950M ceiling.

Key highlights include: the contract will cover TIGS, Talladega, and Daytona variants, with a focus on ground-based systems that may include future aerial/tethered options; the first task order will likely involve finalizing the TIGS v2 design based on a prototype developed by a Federally Funded Research and Development Center (FFRDC); software will be at TS/SCI-level with 2-year refresh cycles, while hardware will have 5-year refresh cycles; Government-Furnished Equipment (GFE) will include Army common equipment like vehicles, generators, and environmental control units. The government has not yet determined the number of contract awards, small business requirements, or specific task order structures, and is seeking industry input to refine the acquisition strategy.

View the file

Other files

File Type Posted
Industry Day Final Agenda_TIGS IDIQ _Final for Distro.pdf PDF
RFI P3I.pdf PDF

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

Industry Day Questions

Q: When you say “maximize Army common equipment” (slide 3), will you provide GFE or potential GFE that might be applicable?

A: Yes, Army common equipment will be provided as GFE when applicable and may consistent of the following, but not limited to vehicles, generators, and environmental control units (ECUs).

Q: Is intent to be 100% ground based or are there aerial/tethered options as well?

A: Currently ground based, but aerial/tethered options could be part of future requirements

Q: End customer is Theater echelon and higher (1st Space, MDTF, TSEG). Is there a CONOPS where it supports a BCT? (OBJ KPP2)

A: Currently, the only CONOPS that have developed by the Capability Developer (CAPDEV) are for the Space Control Planning Team and Space Control Company.

Q: Will support of lowest frequency bands continue to be developed by Army labs or made a task order on this IDIQ?

A: Both. The program office may continue to explore options with Army labs and/or issue task orders under this IDIQ. This will be situation dependent.

Q: Is production of systems at TS-level required? With S/W? Without S/W?

A: Currently, it is not anticipated that hardware production would be at the TS-level since the system is primarily COTS based. The S/W is currently at the TS/SCI-level and will require appropriate facilities for integration, testing, and/or further S/W development and/or S/W sustainment.

Q: Why should industry invest in to compete against an incumbent with a functional prototype? What is the opportunity? (contract award is 6-9 months from first 2 produced)

A: The TIGS v2 prototype was designed by an FFRDC. The 1st task order on the MAIDIQ contract will likely be final design for the TIGS v2 variant. All technical data provided as part of the prototype will be provided to the MAIDIQ contract vendor pool to bid on the final TIGS v2 design. As discussed during Industry Day, the dates provided in the fielding schedule are draft and will be dependent on award timeline of the MAIDIQ contract.

Q: Can you explain difference from acquisition perspective between v1 and v2?

Looks like prototype v2 is prior to Draft RFP for MAIDIQ – if so – what is purpose of the MAIDIQ?

A: TIGS v1 was designed and delivered as an Engineering and Manufacturing Development (EMD) fieldable test article. The program is not going into full rate production on the TIGS v1 variant. TIGS v2 is the next variant of the TIGS SoS, providing a more tactical form factor. The TIGS v2 prototype was designed by an FFRDC in limited quantities to reduce risk and elicit feedback from the User community.

The TIGS v2 prototypes will be issued to the field for a defined timeframe and is intended for User assessment and feedback on the final TIGS v2 design. The purpose of the MAIDIQ contract is to design and produce any TIGS SoS variant (v2, v3, v4 etc.).

As defined during Industry Day, the TIGS SoS has a 25-year life cycle, under which the TIGS SoS will undergo continuous design, development, product and fielding to pace the threat, technology, and the operational environment. Given a 10-year ordering period on the MAIDIQ contract and the estimated ~$950M ceiling, the system will undergo several iterations and enhancements during the contract period.

Q: Are effects or existing GFE available or will industry be responsible for creating effects for each prototype?

A: Effects do exist and will be provided as GFE. The intent of Pre-Planned Product Improvements (P3I) is to provide scope for development of future effects as determined by the IC and/or combatant commands. Army common equipment will be provided as GFE when applicable and may consistent of the following, but not limited to vehicles, generators, and environmental control units (ECUs).

Q: Do you anticipate 1 prototype from 1 vendor or more? If so, how many? What is timeline for bakeoff?

A: The TIGS v2 prototype was designed by an FFRDC in limited quantities to reduce risk and elicit feedback from the User community. Additional TIGS v2 prototypes will not be produced on the MAIDIQ contract. The 1st task order on the MAIDIQ contract will likely be final design and development of the final TIGS v2 variant. Additional TIGS SoS variant prototypes (ex. TIGS v3, v4, Talladega v3, etc.) may be awarded on the MAIDIQ contract based on operational requirements and changes in threat and technology.

Q: How many vendors will be on MAIDIQ?

A: Unknown at this time. The results of Industry Day and subsequent market research will determine number of IDIQ awards.

Q: What weight do you place on CMOSS? Not in KPPs. Mentioned on only 2 slides.

A: CMOSS is a system maturation that is tracked on the technology roadmap in the mid/long term. If/when a CMOSS requirement is codified, it will be awarded as a task order on the MAIDIQ with its own evaluation criteria.

Q: Can these slides be provided to each company at TS level?

A: Yes, if you provide a JWICS email address the government will provide the TS level TIGS SoS Program Overview brief. Please send JWICS email address to Ernest Snyder ernest.l.snyder2.civ@army.mil and Michael Kruger Michael.p.kruger.ctr@army.mil.

Q: Is the Army lab also developing the institutional trainer?

A: No. The institutional trainer is being developed under another contract.

Q: How many TIGS v2 Prototype will be delivered in FY25?

A: The plan is to issue a minimum of one (1) TIGS v2 Prototypes to 1st Space Brigade, Multi-Domain Task Force-1 (MDTF-1), MDTF-2, and MDTF-3 for a total of four (4).

Q: Will TIGS v2 be at the SCI//SAP level?

A: No. It will be at the TS/SCI-level.

Q: How many awards on the MAIDIQ?

A: Unknown at this time. The results of Industry Day and subsequent market research will determine number of IDIQ awards.

Q: Will tech specs from prototype come out on Draft RFP?

A: Yes, the technical documentation from the TIGS v2 Prototype will be provided as part of a Bidder’s Library with the task order Draft RFP for TIGS v2.

Q: What # of awards are planned for the multi-award contract?

A: Unknown at this time. The results of Industry Day and subsequent market research will determine number of IDIQ awards.

Q: What additional info will be shared on the V2 SDR capability? Would like to understand processing and form/fit/function drives.

A: The technical documentation from the TIGS v2 Prototype will be provided as part of a Bidder’s Library with the task order Draft RFP for TIGS v2.

Q: Is institutional trainer used to train TIGS v1 or v2?

A: The institutional trainer will focus on space operations foundational training and will incorporate operations and sustainment training modules for the TIGSv1 SoS. TIGSv1-specific modules will consist of computer-based training for limited operations, troubleshooting, and field-level maintenance activities. As additional TIGS SoS variants

(ex. TIGS v2, Talladega v2, TIGS v3, etc.) are added to TIGS SoS, additional training modules will be developed and incorporated as instructional schedules permit.

Q: As this is an MAIDIQ does that imply that there will be competition among vendors for each task order?

A: Yes.

Q: Is contract for TIGS, Talladega, & Daytona?

A: Yes, TIGS, Talladega, and Daytona comprise the TIGS SoS. Task orders under the MAIDIQ contract will be executed within the scope of the MAIDIQ (ex. production, design, prototyping, etc.) for all variants of the TIGS SoS.

Q: Will design be required to use 3rd party IP?

A: The Government expects to provide ICDs as GFI for any integration/federation requirements with 3rd party devices. The government expects Government Purpose Rights as a minimum for all technical data and architecture for TIGS SoS variants.

Q: Will a copy of the performance specification be made available?

A: Yes, all applicable technical documentation, to include a performance specification, will be provided as part of a Bidder’s Library with each individual task order RFP.

Q: Will a copy of the CSB memorandum be provided for review?

A: Yes, if applicable, the CSB memorandum will be provided with the base MAIDIQ contract award and/or subsequent task orders.

Q: Will future trainers (L, V or C) be procured under this contract?

A: Yes, the scope of this MAIDIQ includes future trainer development and production.

Q: Would the Government consider a live TO with the MAIDIQ to bring both awards to the left?

A: The Government welcomes all recommendations on contract structure and type as the program continues to shape its acquisition and contract strategies. Please send recommendations via unclassified or JWICS email to Ernest Snyder ernest.l.snyder2.civ@army.mil or ernest.l.snyder.civ@army.ic.gov and Michael Kruger Michael.p.kruger.ctr@army.mil or Michael.p.kruger.ctr@army.ic.gov.

Q: How does the Government intend to structure task order RFPs under the

MATOC?

A: Unknown at this time. The results of Industry Day and subsequent market research will determine task order structure. The Government welcomes all recommendations on contract structure and type as the program continues to shape its acquisition and contract strategies. Please send recommendations via unclassified or JWICS email to Ernest Snyder ernest.l.snyder2.civ@army.mil or ernest.l.snyder.civ@army.ic.gov and Michael Kruger Michael.p.kruger.ctr@army.mil or Michael.p.kruger.ctr@army.ic.gov.

Q: What are the planned on and off ramp processes and criteria for the MATOC?

A: Unknown at this time. The Government is still assessing on and off ramp criteria & process. The Government welcomes all recommendations as the program continues to shape its acquisition and contract strategies. Please send recommendations via unclassified or JWICS email to Ernest Snyder ernest.l.snyder2.civ@army.mil or ernest.l.snyder.civ@army.ic.gov and Michael Kruger Michael.p.kruger.ctr@army.mil or Michael.p.kruger.ctr@army.ic.gov.

Q: How many initial awards does the Government anticipate?

A: Unknown at this time. The results of Industry Day and subsequent market research will determine number of IDIQ awards.

Q: Will the Government require teams be established at the IDIQ level?

A: No. The Government does not intend to restrict teaming at the IDIQ level.

Q: Does the Government anticipate small business requirement pools at the IDIQ level?

A: No. If the Government determines to structure the MAIDIQ into pools, the Government does not intend for separate small business pools.

Q: What small business requirements does the Government anticipate at the task order and IDIQ level?

A: Unknown at this time. The results of Industry Day and subsequent market research will determine what/if small business requirements will be required under the MAIDIQ and task order level.

Q: What impact to the acquisition strategy does the Government anticipate from the current administration push towards commercial procurements?

A: None.

Q: Does the Government anticipate changes to the acquisition plan based on the current focus on OTAs to accelerate procurement?

A: No, the Government does not anticipate a change to the current contract strategy, which is a FAR-based MAIDIQ contract.

Q: Under the PoR construct, how does the Government intend to keep pace with emergent threats and requirements? Would the Government consider a prime integrator task order?

A: The Government has relationships with the Intelligence Community (IC) as well as inputs from the User community (i.e. MDTFs & 1st Space Bde), who influence threat priorities, system enhancements, and operational requirements. Additionally, there are other program stakeholders (ex. defense laboratories, academia, FFRDCs, other defense agencies and departments, other contract actions, etc.) that help shape threat priorities and requirements. The Government will take the suggestion of a prime integrator task order under advisement.

Q: Does the Government anticipate leveraging other contracts within PEO IEW&S to achieve software development goals to avoid duplication of effort?

A: Leveraging other PEO IEW&S contracts is unknown at this time. The Government does leverage other program stakeholders (ex. defense laboratories, academia, FFRDCs, other defense agencies and departments, other contract actions, etc.) to achieve software development goals to avoid duplication of effort and achieve synergy between services. The Government has established TTAs with several stakeholders for software provided as GFI/E for PdL TSS use.

Q: How do the software scope elements align with the AIS@P IDIQ?

A: Undetermined at this time.

Q: Would the Government consider faster hardware and software refresh cycles to keep pace with industry advancements and emergent enemy tech capabilities?

A: Yes. As identified at Industry Day, the refresh cycle for software is 2 years and for hardware is 5 years. With that being said, the program does intend to assess yearly baseline enhancements, upgrades, modifications, etc.

Q: Will a library be made available or reading room with architecture diagrams, technical data packages, interface control documents, etc. between now and DRFP for design?

A: Undetermined at this time. As the Government continues to release RFIs for this contract action, the program will consider releasing relevant technical documentation as part of the RFI process to enhance industry responses.

Q: How does the Government envision including DDIC & EMCON requirements for operations when establishing cloud requirements?

A: The government needs more time to assess this question and will provide a response at a later time.

Q: What bandwidth limitations should be part of the considerations and are infil and exfil part of design?

A: The government needs more time to assess this question and will provide a response at a later time.

Q: Does the Government anticipate oral presentations for proposals at either the IDIQ or task order level?

A: The Government will take this suggestion under advisement as we continue to finalize the contract strategy.

Q: Will the government require tech demos at the IDIQ or task order level?

A: Undetermined at this time.

Q: Will the Government permit dynamic teaming at the task order level?

A: Undetermined at this time. The government needs more time to assess this question and will provide a response at a later time.

Q: How quickly does the Government intend to award task orders from RFP release to award?

A: Task order award timeline is undefined at this time. The goal of awarding a MAIDIQ contract is to expedite the task order award process.

Q: What are the operator requirements? How big is team? Space requirements for team?

A: The government needs more time to respond to this question and will provide a response at a later time.

Q: Will mobile platform be part of contract or provided?

A: All Army vehicle platforms will be provided as GFE.

Q: Has the open architecture framework been established and SDK available or is the creation of the open architecture part of the continuous development cycle?

A: A formal open architecture has not been established. An SDK will not be available at the onset of Contract award. It is the desire of TSS to establish a framework as a part of the development cycle once prototypes prove to be employable in operations.

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