MODIFICATION
70 -- All-Source Analytical Environment (ASAE)
- Notice Date
- 2/18/2015
- Notice Type
- Modification/Amendment
- NAICS
- 511210
— Software Publishers
- Contracting Office
- Other Defense Agencies, U.S. Special Operations Command, Headquarters Procurement Division, 7701 Tampa Point Blvd, MacDill AFB, Florida, 33621-5323
- ZIP Code
- 33621-5323
- Solicitation Number
- H92222-15-R-0004
- Archive Date
- 3/18/2015
- Point of Contact
- Michael J. Hawkins, Phone: 8138267047
- E-Mail Address
-
michael.hawkins4@socom.mil
(michael.hawkins4@socom.mil)
- Small Business Set-Aside
- N/A
- Description
- The following questions were received and answers are being provided. Q1: Has the government considered funding the demo phases for the selected vendors? A1: The Government considered this option but elected not to fund the demo phases. Q2: Will the government supply the DCGS-SOF Data Layer Design Document and the DCGS-SOF UI API? A2: DCGS-SOF Data Layer consists of MarkLogic (Index and database), NetOwl (Entity Extraction), and MetaCarta (Geo-location). DCGS-SOF UI API is available upon request per the directions posted on FBO. Q3: The phrase "will" is not allowed in the response - can an offeror state its roadmap for future capabilities that are natural expansions of the delivered capabilities? A3: The offeror is expected to have a solution to integrate. If the offeror wants to propose future expansions/enhancements, that is acceptable. Q4: What are the parameters of the demonstration environment (machine power, processing, storage, memory, etc...)? A4: The Government will provide a separate commercially-hosted, virtual cloud environment for each vendor. During the demonstration phase if it is deemed necessary to increase any of the parameters of the cloud instance, it is strongly recommended that the offeror immediately notify the Government of the requested change(s). Q5: The previous Q&A stated that geospatial requirements would be deleted from the final RFP -- the demonstration plan still has geospatial requirements. A5: See revised Attachment 2, FRD and Attachment 3, Demonstration Plan posted in Amendment 0002: revised Req. # 3.16 and removed section 3.g. (renumbered subsequent sections accordingly) and sample scenario to delete inadvertent geospatial requirement artifacts. Q6: Can you provide the context (Provide support for various Replication Topologies such as, but not limited to; hub-spoke & peer-peer)? A6: The backend architecture automatically provides for data replication to various locations. The ASAE solution must have the ability to store/save analytical view and associated data in the database to allow for replication and retrieval by other users. Q7: Can you define what is meant by - "Provide behavioral analysis capability" and what is the expectation as it relates to the demonstration scenario? A7: The observable relationship of behavior to the environment. In the Demonstration Plan, a sample scenario was provided. During the Usability Demonstration, analysts will be provided a different scenario to determine if they can identify insurgent activity using the proposed ASAE software tool. Q8: Please define - "Provide Multi-iterative analysis capability". A8: A general class of iterative methods introduced for solving positive definite linear systems. These methods use two or more different iterative techniques and each of them reduces the error by a constant factor in a different subspace. Q9: Please define - "Provide persistent and metadata searches". A9: Persistent search is a method of searching where the query is given first and the information for the results is then acquired vice acquiring the results and then executing the query. Metadata search is the ability to discover relevant information based on the metadata of a document. Q10: Please elaborate on the meaning of "Provide pattern matching and analysis capability". A10: See revised Attachment 2, FRD posted in Amendment 0002: corrected Req. # 3.5 to read "Provide pattern recognition and analysis capability", which is defined as the ability to recognize patterns and regularities in the data and the analysis of the data. Q11: Who is responsible for the "metadata tagging of products created"? Isn't the SDL already doing this? A11: When an analyst creates a product, in this case from the ASAE solution, there are metadata fields that only the analyst will know the answer to. The analyst should be prompted to enter the information when saving. This metadata should be saved with the product. Q12: Does the Government expect the DCGS-SOF ASAE Software Tool to meet every requirement listed in the FRD once the integration is completed and ready to go into production? A12: As outlined in the RFP, the Government requires all of the KPP's, all of the requirements in the Advanced Analytics category, and at least 90 of the remaining 100 requirements in the FRD to be met initially. The Government is acceptable to receiving a Plan of Action & Milestone for the requirements that aren't met initially. This can be discussed at the contract kickoff meeting. Q13: It is possible to have a concept of operations that allows for the sharing of repositories without any loss of security, data pedigree, etc. The KPP 4 language is restrictive. Will the Government consider a re-wording like "local copies of information can be maintained for performance, but master data will remain in the SOF Data Layer"? A13: No. The ASAE solution is expected to be integrated into the existing architecture and User Interface, not spawn off into its own environment. The User Interface physically resides on the SDL database server so there are no performance issues. The Government does not wish nor anticipate having additional databases or data stores to meet this KPP. The vendor has full access to the underlying database. Q14: Will the Government consider flexibility on KPP 6? A14: No. The disconnected technology that DCGS-SOF uses has been proven for a couple of years in several exercises around the world on multiple networks. Q15: Can the offeror assume that in any given year that the Government will only purchase either CLIN 0002 & 0003 or CLIN 0004 & 0005? So, at most the Government will purchase CLIN 0001, one Enterprise-wide license, and four renewal Enterprise-wide licenses, is this correct? A15: Offerors can assume that in year 1, only CLIN 0001 (initial integration) and CLIN 0002 or CLIN 0003 (enterprise-wide license or disconnected server license) would be ordered. In years 2 through 5, any combination of CLINs 0002 - 0005 could be ordered depending on when the ASAE software is required for the first time at new locations or disconnected servers and when the initial licenses purchased under CLINs 0002 or 0003 come up for renewal. Q16: When filling out either CLIN 0002 or 0004 on the Total Evaluated Price Worksheet, can the offeror assume that the Government has already purchased one network license and the values for 2-5 networks and 5+ networks is the difference between a single network cost and the additional cost required to support additional networks? Or, will the Government simply take the number in the 2-5 networks/5+networks and multiply it by the number of networks that the Government desires to purchase as described in Attachment 9 (Section M) paragraph M.2.3.1? A16: See Revised Attachment 8, Total Evaluated Price Worksheet posted in Amendment 0002. The Government will evaluate the unit prices provided for CLINs 0002 and 0004 and will take the unit prices provided for CLINs 0003 and 0005 and multiply them by the pre-selected quantity of licenses for evaluation purposes. Upon contract award and depending on networks required, a delivery order against CLIN 0002 would be made for quantity 1 at the 2, 3, or 4 network unit price. If 8 networks were required, the delivery order against CLIN 0002 would be made for quantity 2 at the 4 network unit price, etc. Depending on disconnected licenses required, a delivery order against CLIN 0003 would be made for the required quantity. *NOTE* The ASAE ad hoc training will already be covered under CLIN 0002 so it is not required under CLIN 0003. When it comes time to renew the licenses ordered under CLIN 0002 or CLIN 0003, a delivery order(s) against CLINs 0004 and 0005 would be made at the appropriate quantities. Again, the ASAE ad hoc training will already be covered under CLIN 0004 so it is not required under CLIN 0005.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/ODA/USSOCOM/SOAL-KB/H92222-15-R-0004/listing.html)
- Record
- SN03645332-W 20150220/150218235407-def4874f11dfca6fba8f6614b7bcffc7 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |