ICM Draft RFP Comments and Questions Submission - Responses Posted to SAM.pdf

Question/C omment

Page and Section

Reference Questions Answers

Attachment 0001

Draft ICM Statement of Work (SOW)

Is Attachment 0002 (Draft Information Collection Applications Requirements - 9 June 2022 DRAFT Version 10.9) the same file described in Attachment 0001 as the PRD from Nov 2021?

Yes. A finalized draft ICM performance requirements document will be available in

AUG 2023.

Attachment 0002 Draft ICM App Requirements

(CUI) The Draft Information Collection Applications Requirements document specifically names several required "structured data columns" that comprise the baseline format for a digital Information Collection Management template. Is this meant to dictate the data structures, the user interface, or both of the commercial product? Or is it merely sufficient to allow the user to customize templates to meet the baseline format requirement and address unit TTPs?

The "structured data columns" are meant to dictate both the data structure and user interface. In the case of data structure, required data needs to be stored properly to meet Intelligence Product requirements. In the case of the user interface, data needs to be presented to the user in such a way to allow them to utilize the system effectively. There will be freedom in the specific design of the template, but the required fields must be maintained.

Attachment 0002 Draft ICM App Requirements

(CUI) The Draft Information Collection Applications Requirements document has several sub-requirements (e.g. 1.1 and 1.2) that require the COTS software to exchange information with a "data fabric." Do these requirements specifically mean the already-established intelligence data fabric and/or the CPCE Tactical Data Fabric?

This is in reference to the Mission Command Tactical Data Fabric, which at this time is not available for integration. The core of this requirement is to allow the ICM App flexibility of integration as new data sources come online.

Attachment 0002

Draft ICM App Requirements

(CUI) Will the Government provide the list of specific Intelligence Community data and governance standards and their associated standards documents required to be supported per requirement 1.1?

Yes. The government will provide the list of specific Intelligence Community Data and Governance Standards with the formal RFP.

Attachment 0003 Total Evaluated Price (TEP) Worksheet

Will the Government please clarify the purpose of requiring 'ranges' of software licenses under "OPTIONAL Unlimited Enterprise SW License"? Unlimited implies no set number.

The "ranges" on the TEP work sheet will be deleted. For the Unlimited Enterprise SW license approach, there should be No ranges. Unlimited Enterprise allows the government to deploy as many copies of the vendor's software to as many locations as it needs. There are no predefined restrictions or limitations associated with the Enterprise license approach.

Attachment 0001

Draft ICM Statement of Work (SOW)

What is the expected time duration between the completion of all testing activities and the start of fielding?

We are looking at 12-18 months from the time the contract is awarded until we begin fielding. Time from completion of Test to fielding should be 3-4 months.

DRFP

Has the Government already designated a lead systems integrator? If so, who is the lead systems integrator? Would the awarded bidder be considered the Lead Systems Integrator for this Product?

These apps should work independently other than the direct required interfaces needed as provided in the SV-1/SV-6. The updated PRD will also list out how these interfaces should be leveraged to support meeting the requirements. The Government Interop team will also support this effort.

Attachment 0001 Draft ICM Statement of Work (SOW)

3.11.2 DEVOPS: requirements which exceed standard practice of a commercial product drive significant costs for OEM vendors and thereby drive up pricing to the Government---diluting one of the key benefits of a commercial product. Is the Government willing to consider innovative hybrid approaches whereby elements of DEVOPS are subject to differing cycles? For example, hot fixes and patches would be handled under the standard commercial maintenance program for the core product and non-standard activities like enhancements, integrations, and add-on development are conducted under seperate terms.

Yes. This topic can be further discussed with Government reps.

Attachment 0001

Draft ICM Statement of Work (SOW)

Regarding statement in draft PWS ICM Technical Test Para 3.1: "The Contractor shall provide all necessary software licenses, materials, and incidental support required to execute an ICM Technical Test as detailed in the below paragraphs." Will the Government provide all software licenses for Government systems being tested?

Yes. The Government systems being tested will be available in an integration lab.

Attachment 0001

Draft ICM Statement of Work (SOW)

Regarding statement in draft PWS Para 3.0 ICM Programmic: "The Contractor shall designate a program manager", does the Government require this program manager to be on site? No. However, a rep should be available during major events.

Attachment 0001

Draft ICM Statement of Work (SOW)

Regarding draft PWS para 3.1.3 ICM Technical Test Execution: "Test location support and any other meetings requiring in person support." How does the Government intend for the awardee to recover the costs for these travel expenses? Are these costs expected be recovered via a separate CLIN for ODCs/Travel expenses?

The vendor is compensated for their travel to events as part of the individual Test related CLINs. There is not a separate CLIN to refund vendor travel.

Attachment 0001

Draft ICM Statement of Work (SOW)

In draft PWS para 3.1.1 ICM Technical Test Preparations: When the Government "determines the scope of the Technical Test" will this be provided in writing to the awardee and will it include which GOVT Systems (HW) and Versions (SW) to be tested?

The scope of the Technical Test will be determined by the requirements defined in the final PRD.

Attachment 0001 Draft ICM Statement of Work (SOW)

In draft PWS para 3.4.1.1 NIPR RMF Self-Assessment Support: WRT "FSE Guides." Would the Government specify what FSE means?

Field Support Engineer Guide which can be replaced by Administration Guide that details instruction on how to troubleshoot the system for commonly encountered problems and/or set up the system in a fresh installation scenario. This is to cover aspects of the system beyond the scope of a general user.

Attachment 0001 Draft ICM Statement of Work (SOW)

Regarding Government statement in draft PWS in par 3.6.1.1 RMF Self-Assessment Support "The Contractor shall deliver the following system artifact documentation via JWICS no later than 15 business days after receipt of order IAW CDRL B002 (DI-MGMT-82001) DOD RMF Package Deliverables." Will the Government ensure JWICS access is provided and is it assumed that JWICS access will be only conducted within Government facilities?

Yes, the Government will facilitate JWICS access and would be done only on Government facilities.

Attachment 0001 Draft ICM Statement of Work (SOW)

Regarding draft PWS para 1.1 Background statement: "The PM IS&A ICM Intel Application will consist of digital components that must be compatible and able to synchronize with select (like data field) components of aligned other applications (i.e. Intel Support to Targeting Application and the All-Source II Application)." Will the Government provide the select (like data field) components?

Yes. The select components we desire interop with will be defined in the final PRD and System View documents. The select components will be available in the integration lab.

Attachment 0002

Draft ICM App Requirements

(CUI) Does the Government envision an automated MCOO? Or, will the Government accept a MCOO being created manually?

A MCOO is not required for the ICM App. However, the vendor will have the requirement to produce MIL-STD 2525 compliant tactical graphics on a map.

17 DRFP, A. Executive Summary, Paragraph 6

Has a DD 254 for this requirement been prepared, or is one being considered, and what classification applies to this requirement?

Yes. The current SOW and PRD requires SCI, Collateral, US Collateral, Unified Action Partner, Mission Partner Environment.

18 DRFP, B.

Anticipated CLIN Structure

Request the Government provide mapping from Attachment 0001 PWS sections directly to DRFP, Section B Anticipated CLIN Structure. This will be updated and released with the final RFP.

DRFP: D. Basis of Award (Section M), C. Evaluation Approach, 1.

Technical Factor,

a. SUBFACTOR 1 – Product Demonstration

Will Appendix A Product Demonstration Event Plan be made available before the release of the RFP for industry review and comment?

The Product Demonstration Plan will be released with the final RFP package. Industry will be allotted as specific amount of time thereafter to submit questions on the RFP and supporting documents.

Attachment 0001

Draft ICM Statement of Work (SOW)

COTS OEMs provide their commercial products with standard maintenance programs. Requirements which require the OEM to alter or enhance these maintenance programs can drive significant costs. Are the requirements in 3.11.2 DEVOPS intended to apply to the core commercial product, or only to custom development, integrations, and enhancements?

Both. However, major changes that are out of scope will be done through an official Engineering Change Proposal.

Attachment 0002

Draft ICM App Requirements

(CUI) Does the Government envsion the need for a wargaming or modeling & simulation capability as a requiurement to build and/or define enemy COAs (most dangerous, most probable, etc.)?

No, Wargaming or Modeling & Simulation Capability will not be a requirement of the ICM app. COAs will be developed on other systems and that data will be used to perform task within ICM.

attachment 2, Page 4-5

Compatability What interoperability metrics are desired? How does data flow into and out of each of these? As a vendor who is currently not on contract, how can the govn provide additional resolution? WMTS, WMS, USMTF, KML, GEOJSON, etc etc. How will this be defined? What is the metric for success here?

Success of interoperability will be determined during Technical Tests. The exact formats/schemas/PPS will be defined in the System View documents and provided to the contractor with the official RFP release.

attachment 2, Page 5-7

IC group permissions Is this Army only or are we expected to integrate with an Air Force or National Geospatial-Intelligence Agency authentication system? Or the Joint environment?

No, you are not expected to integrate with Air Force, National Geospatial-Intelligence Agency authentication system at this time. The only requirement is that a user is not precluded from opening a browser and going to a separate website. The user will define future requirements and may be considered if necessary.

Attachment 2 Overall TTPs There is reference to the TTPs change for Information Collection. Is there a current TTP that is being used as a template as standard and then additional deviations?

Yes, we reference <ATP2-01.3> as a standard template. From that template deviations from doctrine are made to the template to account for data fields needed to meet other requirements from user feedback.

Attachment 3;

CLIN Pricing

CLIN Pricing There is reference to the TTPs change for Information Collection. Is there a current TTP that is being used as a template as standard and then additional deviations?

Yes, we reference <ATP2-01.3> as a standard template. From that template deviations from doctrine are made to the template to account for data fields needed to meet other requirements from user feedback.

26 Attachment 3;

CLIN Pricing

CLIN Pricing Is the hosting done on the government environment or by the vendor? Government Environment

Sheet1