CSEA_Govt_Response_to_Industry_Questions_II.pdf

Tracker # Page # Section/

Paragraph Question/Comment Proposed Action/Change Answer

76 91 3.1.9 Quantify the content of Non-SSDS related software versus the SSDS software resource library (GFP Item)?

Clarify the delineation and intent of keeping separate the two referenced sets of software.

Non-SSDS Contract Related versus the SSDS software resource library.

The Government requirement will ensure there is separation between SSDS software and non-SSDS software, and that deliveries of SSDS releases and Builds do not contain any non-SSDS software.

77 96 3.1.14 Would the government be willing to entertain incremental development approach including IPRs as an alternative to the traditional waterfall milestones (SDR/PDR/CDR)?

Reword section to allow for incrementatal development with IPRs.

The Government requirement states the Contractor shall complete all identified TRM events, entrance and exit criteria, and all deliverables as indicated in the SOW.

78 General General When will the SSDS source code, simulation tools, engineering notebooks, and requirements be released to the bidders library?

Release GFI with updated draft RFP. SSDS source code: Provided.

Simulation tools: Will not be provided in the Bidder Library.

Engineering notebooks: Samples of ENBs are in the Bidder Library.

Requirements: The Bidder Library contains the requirements documentation.

79 77 3.1.6 The RFP states, "Furthermore, the Contractor shall address emergent Navy mandates, such as Navy Cybersecurity CYBERSAFE." How will cost, schedule, and technical impact due to new mandates be handled by the program?

Recommend adding, "New mandates will be analyzed for cost, schedule, and technical impact. The Contractor and Customer will negotiate the appropriate solution."

The Government will review the concerns provided from Industry and will update the tasking language where it is deemed appropriate for the RFP.

80 110 3.2.2.3 Software Engineering Are releases every 6 months required for every platform configuration?

Clarify software build plan and terminology. Each release should be applicable to all platform configuration as a superset. The specific requirements of the anticipated activites will be tasked via Technical Instructions.

81 111 3.2.2.3.1 Software Modeling Please provide a definition of software component level as it applies to the system model.

Clarify software build plan and terminology. The Government will update the applicable language in the RFP.

82 100 3.2.1 Is there any existing IP granted to the incumbenet in the software. If so, how does the government intend to provide to a new provider?

Please clarify GFI will be provided with rights of use dictated per the markings on the documents.

83 119 3.2.2.3.12 Please describe how and when the computer program generation equipment, test fixtures, and any other GFM will be transitioned to the CSEA contractor to support the required build, test, and integration?

Please clarify A complete list of GFI will be provided in Section J of the RFP.

84 Section C, 3.1.9 Plese explain the following staement: "The software provided and developed under this contract is only for use by the Contractor in the development of the SSDS and all other uses are prohibited unless approved by the Program Office and Contracting Officer."

The statement as provided in the draft RFP will be retained as written.

85 General Information we have collected suggests Johns Hopkins University Applied Physics Laboratory (APL) performs a dual role, providing SSDS technical leadership to the US Navy as well as peforming a principal development role for SSDS systems engineering and development. Providing a performance modeling and systems engineering role in support of the SSDS PSEA Raytheon IDS. For purposes of the pending SSDS competition, how will APL fire wall itself from the incumbant SSDS PSEA Raytheon IDS in order to independently and equally support all SSDS CSEA bidders?

Clarify the APL proposal team firewall approach.

APL does not support the PSEA Contractor. APL supports the Government as the Technical Direction Agent (TDA)

86 3.3.2.2.1 Performance Analysis

The draft RFP states the Contractor shall upgrade system M&S tools in support of SSDS multi-mission performance analysis. Will the system M&S tools and representrative threat scenarios be provided as part of the final RFP?

Provide system M&S tools (e.g. models) to industry:

1. Simulation models and data relevant to demonstrating current performance of SSDS on relevant platforms which can serve as a benchmark for comparative analysis.

2. Simulation models and/or data related to future capabilities such as EASR or SEWIP Block II.

The SSDS ICS M&S Strategy and Plan will be provided in the Bidder Library. Additionally, a complete list of GFI will be provided in Section J of the RFP.

87 3.3.2.2.1 Performance Analysis

The draft RFP states the Contractor shall execute statsitical performance runs of the SSDS design against Compliance and Assessment cases. Can SSDS performance analysis results for versions of SSDS MK 2 currently under development be provided to bidders?

Provide SSDS performance analysis results to industry:

1. Performance analysis results presented as part of SSDS Mk2 program reviews such as PDR and CDR relevant to AAW and SUW self-defense missions especially as it pertains to Pra.

2. Data related to key subsystem/element performance such as

a. Radar sensitivity/probability of detection data for the SPQ-9B, SPS-49A, SPS-48G,and DBR radars

b. Time of flight and probability of kill data for NSSMS and RAM missile systems and CIWS Mk 15 weapon system

c. Organic sensor AMR and CEC composite track data for a single threat

3. Data to characterize relevant threats and scenarios for surface and air self-defense missions such as

a. Threat trajectory and relevant environmental data

Performance information necessary for development and test will be available post contract award.

88 3.2.2.2.2 Critical Experimentation and Performance Analysis

The draft RFP states the Contractor shall work with the Government to conduct critical experiments in order to refine the potential performance of SSDS integrated with new subsystems or capabilities. We expect that new capability development will be driven by threat complexity and the ability of the SSDS to pace those threats. Can representative threat information be provided to bidders?

Provide SSDS threat information, both current and anticipated.

Threat information is classified higher than this solictation can handle, so no information of this type will be provided.

89 Section H Does the government intend to include DFARS Clause 252.226-7001 as part of the contract?

Include DFARS Clause 252.226-7001 0

90 3.3.3.1.1.1.2 EASR Capability for SSDS

The draft RFP states that SSDS requirements for incorporating EASR are provided in the SIRD. Will detailed performance and inteface requirements be included?

Provide:

1. Simulation models and data relevant to identifying targeted EASR performance and integration into SSDS MK2 for targeted Amphibious and Carrier platforms.

2. Any interface simulators/stimulators targeted for use during early program capabilities testing and evaluation.

EASR is a concurrently developing system, the design and performance artifacts are not yet available.

91 Bidder Library The Build 9 source code was removed from the bidder's library index. The SOW introduction requies the winning bidder to assume responsibilty for in-service computer maintenance of Build 9. If the government is not going to deliver the Build 9 source code to bidders will the requirement for maintaining Build 9 be removed.

Request delivery of build 9 source code, makefiles, and dependancies

Build 9 software is only associated with Level of Effort tasking (i.e., in-service maintenance). Build 9 software will only be delivered post contract award.

92 Bidder Library The Build 9 source code was removed from the bidder's library index. Does the government intend on deliverying the Build 9 source code to bidders?

Request delivery of build 9 source code, makefiles, and dependancies

Build 9 software is only associated with Level of Effort tasking (i.e., in-service maintenance). Build 9 software will only be delivered post contract award.

93 Bidder Library When will remainder of the bidder library documents be provided?

A complete list of GFI will be provided in Section J of the RFP.

GOVERNMENT RESPONSES TO SSDS CSEA PRE-SOLICITATION #N00024-17-R-5152

- In the event of a conflict between the RFP and the Government responses to the Draft RFP questions, the RFP will govern.