Data Correlation Fusion RFI QA.pdf

Question Answer

(U) Is the final paper a total of 10 pages across the classifications or is it 10 pages total to include both class and unclass?

(U) 10 pages Unclass/3 pages classified

(U) Is this considered a new start and if not, who is the incumbent? (U) New Start

(U) Is having experience in integrating capability into CCIC2S a requirement in order to be successful or will the government provide SME support to assist the contractor?

(U) The Government will provide SME support to assist the contractor during CCIC2S integration activities.

(U) Does the government have an acquisition schedule in place and if so, could the government share the key dates?

(U) Acquisition schedule is currently being processed and will be provided at a future date.

(U) Will the Government allow for SECRET level submissions via a JWICS/CWAM network and if so, could the Government please provide a high-side email address for submittal? In order to highlight our most relevant experiences and expertise, we would like to discuss programs and capabilities in a classified writeup. However, we do not have SIPR comms and are unable to submit via SIPRnet. We do have SCI-level comms and could submit via JWICS/CWAN if the Government would allow.

(U) You can submit Secret level to Mr. Michael Maule's gold account. Should be in the global registry

(U) Could the Government extend the RFI response deadline to 12/19? Under normal circumstances, a 30-day RFI response window is highly appropriate, however in this case, many of our key technical writers are taking some time off during the week of 11/25 to observe the Thanksgiving holiday.

( U) Government is not willing to modify the timeline for information at this time.

(U) What is the CCIC2S graphical interface? What do the users like about it and what deficiencies does it have?

(U) We have Enterprise Workstations (EWSs) and Thin Clients to view MW data at Correlation Centers: and Strategic Forward User locations use Zero Clients to display PDS-M data on their workstation monitors. Users are trained to use the system and have no complaints about it. No deficiencies with the "GUI". We will provide bidders library content at a later date to more completely describe the current CCIC2S GUI source code and applicable documentation.

(U) What network connections already exist in CCIC2S? (e.g. RTS, EM4, IBS, UDL, DATABAHN, Link 16)

(U) DISA MPLS TCP/IP circuits and Milstar/AEHF survivable circuits. Global Summary Messages (GSMs) are received over Glabal Summary Networks via Sensor

Survivable Data Network (SSDN)(both DISA TCP/IP and Milstar/AEHF), Survivable Correlated Data Network (SCDN)(both DISA TCP/IP and Milstar/AEHF),S2E2, GCNM, IBS-A (UHF) to Tactical Receive Segment (TRS) for Theater Data Enterprise Messaging 5 (EM5) for Missle Warning Net Server (MWNS) outgoing data (future

Capability) SDIN SIPRNet (for SA PDS-Ms) Global Data Integration (GDI) over SIPRNet. Is this being used elsewhere for MW/MT? Don't think it is used anywhere else currently. External ATOMS message from MDA/C2BMC global in approximately September 2025.

(U) Is there a desire for a contractor to establish additional data connections, or only provide algorithms for data flows over existing connections?

(U) The specific scope of this contract effort does NOT include any additional data connection efforts. The scope of this effort is to focus on specific contract scope/ requirements surrounding Correlation/ Fusion algorithms within the Near Real-time processing of the CCIC2S operational system.

(U) Will messages be used internally to CCIC2S or be messaged out, who are the downstream users?

(U) Messages will be used internally by existing CCIC2S users to include Strategic Forwarf Users at some poiint: however, they will not be messaged out over additional tactical data links, but MWNS GSIN data is pushed out over SIPR.

(U) What deficiencies currently exist with respect to message processing?

(U) No deficiencies related to messaging. Existing message processing deficiencies are the responsibility of the Sustainment and Operational Community. The scope of this effortwill however include requirements to provide proper message data evaluations and as required message data processing specifically for fully effective

Correlation/Fusion results.

(U) What deficiencies currently exist with respect to existing fusion algorithms? (U) There are no existing Fusion algorithms, therefore no DRs.

(U) What is the existing hardware for deploying software solutions? Ia a hardware expansion required, or a software-only solution of interest?

(U) Integration into the CCIC2S boundary is required with the applicable HW and SW deployment solution(S) maintaining current program operational processes. It is anticipated that contract technical performance requirements will require design solution driving additional HW scaling for applicable database, logging, cares, SW, etc. in order to assure comprehensive system design solution success with acceptable performance Risk/Issues being reduced in a reasonable amount of time.

Sheet1