QA PEREGRINE.pdf

Q# Section /Page Question Answer

Q-01 1.3

Can the government please clarify the page count? Should the detailed past performance references requested in section

1.3 be included in the 6-page technical capabilities statement or the 5-page description of similar services appendix?

Responses shall be limited to thirteen (13) pages with an additional uncounted cover page.

Section 1.7, items f, g, and h should be addressed in a six (6) page Technical Capabilities Statement. Administrative Items a-e may be included in an uncounted cover page to the 6-page Technical Capabilities Statement. Section 1.7 items j, k, l, and m shall be addressed in an additional 2 pages in the Technical Capabilities Statement. The Description of Similar Services (Section 1.7.i) shall be addressed in an additional five (5) page appendix.

This results in a total page count of 13 pages, not counting the Technical Capabilities Statement cover page

Q-02 1.3

-Will the government consider capabilities statements that are "Controlled Unclassified Information" CUI? Given the nature of government classified work and detailed relevant work, we recommend accepting CUI statements describing relevant contract experience at a minimum. Many government organizations will not allow their past performance to be referenced at anything less than CUI or For Official Use Only

(FOUO).

-Furthermore, if the Government would like detailed experience at the classified level (particularly for Space Intelligence Community delivery and execution, we recommend permitting TS//SCI submissions.

Yes, CUI is acceptable for Source Sought responses. The Government may permit TS/SCI submissions for prototype and production contract proposals, but CUI is sufficient for the Source Sought.

Q-03

Performance Enhanced Real-time Ground Environment (PEREGRINE) Sentry Can you add me to your industry day for the enclosed RFI or any Industry Day.

If the Government hosts an Industry Day, details will be provided in the announcement.

Q-04 1.7(h)

Paragraph 1.7(h) invites teaming arrangements. Does SDA anticipate that the 18-month prototype awardee will also receive the production OTA, or will the production award be competed? If it is competed, may the team composition change between the prototype and production phases?

The Government has not identified a final acquisition strategy for the production effort at this time.

Q-05

How will SDA divide roles between the platform integrator and the third-party application developers (3PADs)? Can a 3PAD also be a subcontractor on the integrator team?

The PEREGRINE Sentry contractor is responsible for leading integration of mission applications with the framework in collaboration with application contractors. Applications contractors are responsible for supporting integration of their mission applications with the framework. PEREGRINE Sentry and mission application contractors are responsible for supporting enterprise integration efforts which are led by the enterprise integration team.

3PADs can be a subcontractor on the PEREGRINE Sentry contract with appropriate mitigation.

Q-06

Which legacy applications and ground systems fall under the "do no harm" transition? Will SDA share an inventory with interfaces and operational availability requirements?

Do no harm refers to not adversely impacting the legacy ground system development or operations. SDA will share technical data in the bidder's library, and performance requirements will be included in the solicitation.

Q-07 What acceptance criteria will SDA use to judge that a transition did no harm? Does the government expect the

At the top level the metric is achieving mission continuity during the transition period, and achieving as good as, or better, integrator to propose the metrics?

functional and performance requirements.

Q-08

Does SDA have a preferred modeling language, toolchain, or repository (for example, SysML v2)? Will the government own the model, or will the integrator deliver it as a data item?

The contractor is free to choose their MBSE tool but must be able to export the model in a standard form that can be ingested by other MBSE tools. The Government has not decided on the MBSE tool suite ownership strategy. Responses to this sources sought notice may include recommendations related to MBSE tools.

Q-09

Who owns the authoritative source of truth (ASOT) model under the government enterprise systems engineering and integration governance, and how will the integrator's model connect to it?

The Government owns the ground system ASOT. The PEREGRINE Sentry contractor is responsible for maintaining the ground system ASOT. The Enterprise Integrator may ingest the ground system ASOT into an Enterprise model. The PEREGRINE Sentry contractor will be responsible for supporting the Enterprise Integrator.

Q-10 Will 3PADs onboard against the model, for example through model-based interface definitions? If so, at what stage?

The Government’s expectation is that 3PADs onboard with the actual APIs with sample code that is made available to 3PADs in a developer portal, or other mechanism.

Q-11

Does SDA expect the integrator to hold the continuous ATO across all tenants? Or will the government authorizing official keep it, with the integrator running the RMF process?

The PEREGRINE Sentry contractor is responsible for instantiating the processes and technical capabilities that enable a cATO. A cATO is enabled by Contractor collaboration with the Government cyber security team to establish, monitor and maintain the necessary processes and technical capabilities, such as CDE and GSF static and dynamic cyber scanning and assessment automation.

Q-12 1.9 Paragraph 1.9 states that SDA is considering an Industry Day.

When does SDA expect to

If the Government hosts an industry day details will be provided in the announcement.

announce it, and when does it expect to release the prototype solicitation?

Q-13

Will participation in the Industry Day or the prototype solicitation depend on having submitted a response to this sources sought? May a company that does not respond by October 23 still participate?

If the Government hosts an industry day details will be provided in the announcement and will not depend on responses to the sources sought.

Q-14

Does SDA anticipate that the prime contractor's scope will include procurement and provisioning of contractor-furnished physical infrastructure such as edge compute/servers, storage, networking, rack/power equipment, peripherals, and associated spares?

No

Q-15

If so, may that contractor-furnished hardware supply scope be performed through subcontractors or small-business product suppliers, provided the prime retains responsibility for security, integration, configuration, and overall performance?

N/A

Q-16

Does SDA anticipate establishing any specific small-business subcontracting expectations or reporting requirements for the prototype and/or follow-on production effort?

The Government has not identified a final acquisition strategy at this time. Responses to this sources sought notice may include recommendations related to small business subcontracting or reporting requirements.

Q-17

Does the six-page limit apply only to the technical capabilities statement, with the requested five-page appendix excluded from that count?

Responses shall be limited to thirteen (13) pages with an additional uncounted cover page.

Section 1.7, items f, g, and h should be addressed in a six (6) page Technical Capabilities Statement. Administrative Items a-e may be included in an uncounted cover page to the 6-page Technical Capabilities

Statement. Section 1.7 items j, k, l, and m shall be addressed in an additional 2 pages in the Technical Capabilities Statement. The Description of Similar Services (Section 1.7.i) shall be addressed in an additional five (5) page appendix.

This results in a total page count of 13 pages, not counting the Technical Capabilities Statement cover page

Q-18

What level of detail does SDA expect for the required Secret/TS-SCI personnel, TS FCL, and JWICS capability statements at this Sources Sought stage?

A statement stating whether you currently have appropriate staff cleared at the TS level available to support the PEREGRINE Sentry contract, and whether you currently have, or do not have, a

TS FCL.

Q-19

Can SDA clarify the contemplated OCI boundary, specifically which types of mission-application development or integration work might be incompatible with serving as the PEREGRINE Sentry prime?

The PEREGRINE Sentry prime may be precluded from performing or competing for all mission applications that are, or will be, deployed on the PEREGRINE Sentry framework if an OCI cannot be mitigated.

Mission application developers may participate as subcontractors on the PEREGRINE Sentry contract with appropriate mitigation.

Q-20

Will the PEREGRINE Sentry prime be prohibited from developing, owning, or subcontracting for mission applications integrated into the ecosystem, or only from holding direct mission application contracts?

The PEREGRINE Sentry prime may be prohibited from participating in mission application contracts as either a prime or a subcontractor if an OCI cannot be mitigated.

Q-21

Can SDA clarify whether prior SDA/PWSA ground, mission app, MBSE, cyber, or SE&I support creates an OCI for potential primes or teammates?

Mission application developers may participate as subcontractors with appropriate mitigation. Prior mission application, MBSE, cyber or SE&I work does not create an OCI unless prior activities directly supported development of the

PEREGRINE Sentry acquisition materials.

Q-22

What is the expected boundary between the PEREGRINE Sentry lead platform integrator, existing ground segment contractors, 3PAD developers, and the government enterprise SE&I team?

The PEREGRINE Sentry contractor is responsible for leading integration of mission applications with the framework in collaboration with application contractors. Applications contractors are responsible for supporting integration of their mission applications with the framework. PEREGRINE Sentry and mission application contractors are responsible for supporting enterprise integration efforts which are led by the enterprise integration team.

Q-23

What legacy ground applications are expected to transition during the 18-month prototype, and what does “do no harm” mean in terms of operational availability, rollback, accreditation, and mission assurance?

No mission applications will be transitioned from the legacy system during the 18-month prototype. During the 18-month prototype the contractor must demonstrate on-boarding and hosting of a contractor supplied surrogate mission application.

"Do no Harm" means do not adversely impact the legacy ground system development and operational activities.

Q-24

Will SDA provide the existing MBSE model, architecture artifacts, interface control documents, and configuration management baseline as Government Furnished Information?

Yes, the Government will provide this data for the legacy system.

Q-25

Does SDA expect the performer to build a new CDE/software factory, operate an existing one, or integrate with an existing SDA/DoD software factory?

The Government anticipates the contractor will build a new CDE and GSF that is tailored to SDA's ground processing needs.

However, the Government also expects the contractor to leverage prior Government investments, from across DoW and IC communities.

Q-26

What C2E cloud environments, on-prem footprints, operations centers, and edge compute locations are in scope for the prototype?

The prototype is limited to IL5 (CUI) and IL6 (Secret) cloud environments.

Q-27

At contract award, must the prime already possess a Top Secret FCL, JWICS access, and cleared staff, or is there a transition period to establish the required classified processing capability?

For the production contract, the prime must be able to handle, store and process data at the TS/SCI level at contract award.

Q-28

Will SDA identify the required cross-domain solution baseline, target networks, classification domains, and coalition/FVEY connectivity requirements?

The PEREGRINE Sentry CDS is between IL5 and IL6.

Q-29

Is the government expecting the contractor to achieve a new cATO, support an existing authorization boundary, or provide compliance telemetry into a government-managed cATO process?

The Government expects the contractor to achieve a new cATO.

Q-30

How many third-party application developers are expected during the prototype, and what onboarding throughput should industry assume?

No Third-party application developer (3PAD) onboarding throughput is required during the prototype beyond demonstration of onboarding and hosting one contractor-supplied surrogate mission application. The Government will provide 3PAD bidding assumptions in the production contract solicitation.

Q-31

What level of fidelity is required for the simulation and telemetry/mission data emulation environment, and will representative data sets be provided?

Operationally representative tracking data flows, with operational message formats and data rates are required. The Government will not provide representative data sets as GFE.

Q-32

Are AI/ML and MLOps capabilities required during the prototype, or should they be architected for future production scaling?

MLOps capabilities are required during the prototype.

Q-33 Does Tier 1/2/3 service desk support begin during the prototype, or only during the production phase?

Tier 1/2/3 service desk support is not required for the prototype.

Q-34

Is SDA open to hybrid CLIN structures, such as FFP milestones for defined deliverables plus cost-reimbursable or T&M surge support for emergent integration issues?

The prototype OTA will be FFP.

The Government has not determined CLIN types for the production contract at this time.

Q-35

What prototype milestones does SDA anticipate for the FFP OTA, and what objective acceptance criteria will trigger payment?

This information will be included in the prototype OTA solicitation.

Q-36 What criteria will SDA use to determine successful prototype completion and transition to the follow-on production OTA?

This information will be included in the prototype OTA solicitation.

Q-37

Is SDA considering any small business participation goals, teaming preferences, or evaluation credit for small business/academic partnerships?

The Government has not identified a final acquisition strategy at this time. Responses to this sources sought notice may include recommendations related to small business subcontracting or reporting requirements.

Q-38

How should respondents assess whether the effort can be accomplished commercially, given the classified, mission-critical, and multi-level security requirements?

The effort cannot be accomplished commercially.

The Government requires a Government-owned solution.

However, the Government anticipates offerors will propose re-use or leveraging of prior Government framework and software factory investments along with other COTS and FOSS technologies.

Q-39

Will SDA hold Industry Day before or after reviewing sources sought responses, and will one-on-one sessions be offered?

If the Government hosts an industry day details will be provided in the announcement.

Q-40

Section 1.10 states the Government is evaluating an OCI approach for the prime.

Beyond the potential restriction on mission-application contracts, what other categories of current or prior work, if any, does SDA expect to treat as conflicting for the PEREGRINE Sentry prime, and what mitigation approaches (e.g., firewalls, divestiture, subcontract limitations) would SDA consider acceptable?

Instructions related to OCIs and evaluation of mitigation approaches will be included in the future solicitation.

Q-41 Will SDA assess OCI at the contract, business unit, legal entity or corporate enterprise level?

Instructions related to OCIs and evaluation of mitigation approaches will be included in the future solicitation.

Q-42

Would the Section 1.10 restriction on mission applications extend to future PWSA ground segment work, such as sustainment, modernization or follow-on ground efforts? How will SDA separate the integrator's responsibilities from third-party application developers for development, integration and operational support?

The PEREGRINE Sentry prime contractor is precluded from competing for or performing mission application development contracts if an OCI cannot be mitigated. The PEREGRINE Sentry contractor is responsible for leading and supporting mission application integration into the framework in collaboration with application developers. Sustainment of mission applications will initially be performed by the original application developer.

Q-43

How will responsibilities be divided between the PEREGRINE Sentry integrator, the current PWSA ground integrator (Ground Management and Integration), and the Government's enterprise SE&I team during the prototype and the transition? Will the current ground provider support the parallel-operations period?

The PEREGRINE Sentry contractor is responsible for leading and supporting mission application integration into the PEREGRINE Sentry framework in collaboration with application developers. The PEREGRINE Sentry contractor will also collaborate with the GMI contractor during the parallel operations period.

Q-44

What Government-furnished equipment and information does SDA expect to provide:

C2E cloud accounts, existing ATO packages and inheritable controls, cross-domain solutions, MBSE models, configuration management tools and source code? Which items does SDA expect to be contractor-furnished?

GFE includes the C2E cloud environments, current GMI system technical data and software that may be useful for re-use or leveraging for the PEREGRINE Sentry contract;

such as APIs, external interfaces, RMF packages, and the CDS.

GFE also will include CAC cards and tokens required to gain access to the AWS secret environment management console. This is not an exhaustive list of all GFE, and offerors are advised to identify desired GFE in their proposals.

Q-45

To size the transition, can SDA share the number of legacy applications and services to migrate, their hosting (cloud vs.

on-premises), the number of Operations Centers and security domains, and the expected number of third-party developers onboarded per year at full implementation?

PEREGRINE Sentry is a cloud-native framework, and the legacy system will be a cloud-native system as well when the transition is performed. There are 10-15 legacy mission applications and two operations centers. The Government will provide bidding assumptions in the PEREGRINE Sentry production contract RFP regarding the number of third-party developers to be on-boarded each year.

Q-46

Which C2E cloud service providers and impact levels (e.g., IL5, IL6, Top Secret) are in scope? Will the Government or the contractor hold the cloud accounts and bear consumption costs under the FinOps model?

Initially, cloud environment impact levels are IL5 and IL6.

Q-47

For the NSA-approved cross-domain solution (CUI to SECRET): will SDA provide the CDS as GFE or expect the contractor to procure and accredit it? Is TS/SCI-level cross-domain connectivity anticipated?

The Government will provide the tech data for the current CDS, but the contractor will be responsible for implementing the PEREGRINE Sentry CDS. Initially, only a IL5 to IL6 CDS is required.

Q-48

For the continuous ATO, who is the Authorizing Official? Does an existing PWSA ground ATO baseline exist that the GSF and CDE are expected to inherit?

The SDA AO is the Authorizing Official. The PEREGRINE Sentry GSF and CDE are a new system so the contractor is responsible for achieving the PEREGRINE Sentry ATO(s) and cannot inherit the current system's ATO.

Q-49

Which MBSE tools and modeling standards (e.g., Cameo/SysML v1 or v2) and which Government CM tools must the contractor integrate with as the authoritative source of truth?

The contractor is free to choose their MBSE tool but must be able to export the model in a standard form that can be ingested by other MBSE tools.

Q-50

What data rights does SDA expect in the ground segment framework, CDE and developer tooling (e.g., Unlimited, Government Purpose)? May offerors propose existing commercial or proprietary platform components, and on what license terms?

The Government expects unlimited or Government Purpose Rights as a minimum.

Offerors may propose COTS, FOSS, or GOTS products with appropriate licensing. The Government will not accept proprietary solutions or components that preclude or inhibit the Government's ability to transfer to another future developer.

Q-51

Which Coalition and FVEY partners and classification levels must the MLS foundation support at initial and full capability?

The system should be architectured to enable rapid configurability to support any future Government directed coalition.

Q-52

Section 1.7(g) requires the prime to hold a Top Secret FCL with JWICS access. Would a major teammate's cleared facility satisfy this for portions of the work, and what share of the work does SDA expect at the TS/SCI level?

Yes, a major teammate’s cleared facility would satisfy this requirement. The share of work at the TS/SCI level will be identified in the solicitation.

Q-53

What performance criteria or exit milestones will inform the decision to move from the 18-month prototype OTA to the production OTA (e.g., applications migrated, onboarding time, availability, cATO achieved)?

The Government has not identified a final acquisition strategy for the production effort at this time.

Q-54

What is the anticipated timeline for an Industry Day, draft solicitation and award? Will SDA award directly or through a consortium, and is it considering on-ramps, multiple prototype awards or phased competition?

If the Government hosts an industry day details will be provided in the announcement.

Q-55 General (security requirements)

Must the prime hold a Top Secret Facility Clearance with JWICS-enabled access at the time of Sources Sought response, at prototype award, or before classified performance begins? Would the Government consider a small-business prime whose classified processing and storage occurs at a cleared teammate's facility, or sponsor a Facility Clearance for a non-traditional prime?

The prime must hold a Top Secret Facility Clearance with JWICS-enabled access at the time of production contract award.

Q-56 Para. 1.10

Paragraph 1.10 contemplates precluding the prime from "mission applications integrated into the PEREGRINE Sentry ecosystem." Does that preclusion extend to simulation, telemetry-emulation and test tooling, and to subcontractors or teammates of the prime who are also Third-Party Application Developers (3PADs)?

Simulation, emulation and test tooling are common services that may be provided by both mission application developers and the PEREGRINE Sentry prime.

Mission application developers may participate as subcontractors on the PEREGRINE Sentry contract with appropriate mitigation.

Q-57 General

(acquisition approach)

Does SDA anticipate a small-business set-aside, small-business participation goals, or a non-traditional defense contractor requirement under 10 U.S.C. 4022 for the prototype

OTA?

Responses to this sources sought notice may include recommendations related to small business subcontracting or reporting requirements.

Q-58

General (High- Fidelity

Simulation and Telemetry/Mission

Data Emulation Environment)

Is the High-Fidelity Simulation and Telemetry/Mission Data Emulation Environment anticipated as Government-furnished, contractor-provided, or a hybrid? May contractor-provided commercial simulation software be proposed with rights asserted under the OTA?

Contractor provided. The contractor may choose or propose to re-use or leverage existing Government-owned capabilities, but this is a contractor decision. The contractor may propose COTS products, but all technologies must be deployed in the GOCO CDE and be transferable to future contractors with appropriate licensing terms.

Q-59 General (legacy transition / "do no harm")

Will the Government release the inventory of legacy ground applications, the current 3PAD count and interface specifications before the solicitation, so respondents can size the "do no harm" transition?

The Government will release the legacy ground application inventory, number of anticipated 3PADs, and other technical documentation with the production contract solicitation.

Q-60 Para. 1.9

Will the Industry Day referenced in paragraph 1.9 occur before the October 23 response date, and if after, will the response date move?

If the Government hosts an industry day details will be provided in the announcement.

Q-61 General

(acquisition approach)

Is the 18-month prototype OTA anticipated as a single award, and does the Government intend to award the follow-on production OTA without further competition under 10 U.S.C.

4022(f)?

The prototype OTA will be a single award. The Government has not identified a final acquisition strategy for the production contract at this time. Responses to this sources sought notice may include recommendations related to the Production contract.

Q-62 Para. 1.7

Do the six pages include the administrative items in 1.7(a)–

(e) and (g)–(m), or only the technical capability statement in 1.7(f)? May the five-page appendix include past-performance tables?

Responses shall be limited to thirteen (13) pages with an additional uncounted cover page.

Section 1.7, items f, g, and h should be addressed in a six (6) page Technical Capabilities Statement. Administrative Items a-e may be included in an uncounted cover page to the 6-page Technical Capabilities Statement. Section 1.7 items j, k, l, and m shall be addressed in an additional 2 pages in the

Technical Capabilities Statement. The Description of Similar Services (Section 1.7.i) shall be addressed in an additional five (5) page appendix.

This results in a total page count of 13 pages, not counting the Technical Capabilities Statement cover page

Q-63 Section 1.10

Does the contemplated OCI restriction prohibiting the prime contractor from developing mission applications apply to subcontractors/teaming partners?

Mission application contractors may participate as subcontractors with appropriate mitigation.

Q-64 Page 2 - Second to last paragraph

Is the subsequent 3-year production contract anticipated to be a sole-source follow-on award to the successful 18-month prototype OTA performer, or will there be a separate competitive evaluation prior to production award?

The Government has not identified a final acquisition strategy for the production contract at this time. Responses to this sources sought notice may include recommendations related to the Production contract.

Q-65 Introduction (Page 2)

Will the Government confirm that the allowable response limit consists of up to 6 pages for the Technical Capabilities statement package plus up to 5 pages for the Appendix of similar services, for a total submission limit not to exceed 11 pages?

Responses shall be limited to thirteen (13) pages with an additional uncounted cover page.

Section 1.7, items f, g, and h should be addressed in a six (6) page Technical Capabilities Statement. Administrative Items a-e may be included in an uncounted cover page to the 6-page Technical Capabilities Statement. Section 1.7 items j, k, l, and m shall be addressed in an additional 2 pages in the Technical Capabilities Statement. The Description of Similar Services (Section 1.7.i) shall be addressed in an additional five (5) page appendix.

This results in a total page count of 13 pages, not counting the Technical Capabilities Statement

Q-66 Section 1.7.a-e

Are administrative details (cover page, CAGE code, DUNS, company info) included in the primary 6-page limit, or may they be submitted as a separate cover page?

Section 1.7 administrative items a-e may be submitted as a separate cover page

Q-67 Security

Requirements (Page 2)

Is active JWICS-enabled processing capability required at exact time of award, or will the Government grant a grace period post-award to establish specific accredited connections at the contractor's facility?

Would the Government consider allowing the requirement be met through a DCSA-accredited contracted facility or a teaming partner's facility?

The ability to handle, process and store TS/SCI data is required at production contract award.

Q-68 Section 1.7.h and Section 1.9

In light of the potential Industry Day mentioned in Section 1.9 and the Government's interest in teaming arrangements (Section 1.7.h), will the Government publish an Interested Vendors / Parties List on SAM.gov to enable potential primes and subcontractors to connect?

If the Government hosts an industry day details will be provided in the announcement.

Q-69 Bullet 1 What functions are expected to be completed by "Edge Compute" devices?

Edge compute is not an immediate PEREGRINE Sentry requirement. However, the Government is interested in the potential to support future edge compute solutions for tactical warfighters.

Q-70

How does the schedule for PEREGRINE Sentry relate to the schedule for the T3 Ground System Development (GSD) program?

PEREGRINE Sentry will execute in parallel with the T3 GSD contract.

Operations will eventually transition from the T3 GSD system to the PEREGRINE Sentry system. The Government anticipates a period where both the PEREGRINE Sentry and T3 GSD systems are running in parallel prior to completing the transition.

Q-71

How does the government intend to leverage hybrid deployments across on-prem and cloud? What workloads or functions are expected to be run on what infrastructure?

For the production contract, the Government anticipates deploying a hub and spoke architecture with the bulk of the day-to-day processing performed in the cloud, and sufficient processing capabilities deployed on-prem at the Ops Centers to enable mission continuity if connection to the cloud environment is disrupted.

Q-72 Paragraph 2

What integration scope is the "lead platform integrator" described in the Sources Sought responsible for vis-a-vis the T3PI contractor?

The PEREGRINE Sentry contractor is responsible for leading integration of mission apps with the framework, in collaboration with 3PADs and leading integration of other ground resources (e.g. GEPs) with the ground processing system in collaboration with the relevant developers. The T3PI, or other enterprise integrator, is responsible for leading enterprise and mission level integration (e.g., integration between ground and space segments). The PEREGRINE Sentry contractor is responsible for supporting enterprise level integration efforts.

Q-73

Will 3rd Party application development within PEREGRINE Sentry focus solely on ground applications or will it include deployment to BMC3 modules?

PEREGRINE Sentry will support ground applications only.

Q-74 Does the 18-month prototype phase need to demonstrate cloud, on-prem, hybrid, and edge deployment capabilities?

The 18-month prototype scope is only focused on developing the cloud-native GSF and CDE.

However, the GSF and CDE should be developed with an eye toward a future production contract requirement to support a hub-spoke architecture with an on-prem footprint also.

Q-75 N/A - Acquisition strategy question

After the market research/sources sought phase, will the acquisition proceed via the STEC BAA or will Peregrine Sentry be a standalone OTA acquisition?

It is anticipated the PEREGRINE Sentry prototype will proceed via a standalone OTA acquisition.

The Government has not identified a final acquisition strategy for the production contract at this time.

Q-76 N/A

Are there specific requirements for Edge Compute beyond both Operational centers in Grand Forks and Huntsville?

The initial PEREGRINE Sentry contract has no edge compute requirements beyond the Operational Centers. However, the Government is interested in understanding options for future support to tactical warfighters and edge compute environments.

Q-77 Core Capabilities, Bullet 1

How does the definition of high fidelity simulation change from prototype to the follow-on Production contract? Can the government define "high fidelity simulation" specifically?

High fidelity means operationally representative data flows, with operational message formats and data rates. During the prototype the Government expects the contractor to generate operationally representative data flows using simulation tools. During the follow-on contract the Government expects actual data to be available. The Contractor should be able to augment the test capabilities with the ability to play back real data during testing.

Q-78 Core Capabilities, Bullet 6

What is the total NTE page count? Instructions state 6 page core competency, 5 page Appendix, do the other bullets in section 1.7 align to the 6 page core competency section or are those additional? For example, the bullet " j) Industry standard contract line-item number (CLIN) arrangements best suited for these services". Is the discussion for bullet j included in the 6 page Core Competency response? We recommend allowing 6 pages for bullet f)

Responses shall be limited to thirteen (13) pages with an additional uncounted cover page.

Section 1.7, items f, g, and h should be addressed in a six (6) page Technical Capabilities Statement. Administrative Items a-e may be included in an uncounted cover page to the 6-page Technical Capabilities Statement. Section 1.7 items j, k, l, and m shall be addressed in an additional 2 pages in the Technical Capabilities Statement. The Description of only. Industry would likely need all 6 pages to explain Technical Capabilities. The other administrative discussion points for j,k,l,m we recommend a NTE 2 additional pages.

Similar Services (Section 1.7.i) shall be addressed in an additional five (5) page appendix.

This results in a total page count of 13 pages, not counting the Technical Capabilities Statement