(Pre-Solic) 20161011 - Revised Pre-Solic Notice Q&As.docx

DOCX document 45 KB Posted

Attached to
ADVANCED ANALYTICS TECHNICAL SOLUTION (AATS)
Solicitation number
N65236-16-R-0001
Issued by

View the file

Other files

File Type Posted
20170511 - Updated Solicitation QAs (#19 - #55).docx DOCX document
Amendment 0001 (As Issued).pdf PDF
RFP Attach 12 - Wage Determination.pdf PDF
Amend 3 - RFP Attach 4A (Rev 2) - Prime Pricing Model.xlsx XLSX spreadsheet
(Pre-Solic) 20161128 - Draft - Solic Attach 8.xlsx XLSX spreadsheet
Amendment 0003 (As Issued).pdf PDF
Amend 3 - RFP Exhib A (Rev 2) - CDRLs.pdf PDF
20170505 - Updated Solicitation Q&As (#10 - #18).docx DOCX document
RFP Attach 1A - Ref Info Sheet - Summary Data.pdf PDF
Amend 3 - RFP Attach 4B (Rev 2) - Sub Pricing Model.xlsx XLSX spreadsheet
Amend 2 - RFP Attach 2 (Rev) - Past Perform Quest (Word Format).docx DOCX document
RFP Attach 11 - Quality Assurance SurveillancePlan.pdf PDF
(Pre-Solic) 20161116 - Pre-Solic Conference Agenda.docx DOCX document
RFP Attach 13 - Delivery Order 0001 Statement of Work.pdf PDF
Amendment 0002 (As Issued).pdf PDF
RFP Attach 7 - PWS Section 3.2 Compliance Cklist.xlsx XLSX spreadsheet
Amend 2 - RFP Attach 16 - AATS Ontology Sample (Zip).zip ZIP file
(Pre-Solic) 20170217 - Draft Solic Q&A Update.docx DOCX document
Amend 2 - RFP Attach 14 (Rev) - Cross Ref CLIN to PWS Section.docx DOCX document
(Pre-Solic) 20170412 - Draft Solic Q&A Update.docx DOCX document
RFP Attach 5 - Small Bus Subcontr Plan Matrix.xls XLS spreadsheet
(Pre-Solic) 20161128 - Draft Solicitation.pdf PDF
20170503 - Solicitation Q&As for Posting.docx DOCX document
(Pre-Solic) 20161208 - Pre-Solic Conf Attendees.docx DOCX document
RFP Attach 8 - AATS Software Ftnality in DIL Environ.xlsx XLSX spreadsheet
(Pre-Solic) 20161128 - Draft - Solic Attach 7.xlsx XLSX spreadsheet
(Pre-Solic) 20161116 - Special Notice - Pre-Solicitation Conference.pdf PDF
(Pre-Solic) 20170403 - Revised Draft Solicitation.docx.mcgn5pg.partial —
RFP Attach 10 - DD254 - Contr Security Classific Spec.pdf PDF
RFP Attach 3 - Small Business Participation Data.pdf PDF
(Pre-Solic) 20161205 - Industry Day - Pre-Solic Conference Slides.pptx PPTX presentation
(Pre-Solic) Draft of RFP Attach 6 - IAS Hardware and Software Info.xlsx XLSX spreadsheet
RFP Attach 15 - Software Licensing Disclosure.pdf PDF
(Pre-Solic) Supplies and Svcs - Graphic.docx DOCX document
(Pre-Solic) 20170404 - Draft Solic of 3 April 2017 - Q&A Update.docx DOCX document
(Pre-Solic) 20161128 - Draft Solic Attach 9.xlsx XLSX spreadsheet
RFP N65236-16-R-0001 - As Issued.pdf PDF
RFP Attach 2 - Past Performance Questionnaire.pdf PDF
RFP Attach 9 - AATS Software Capabil Matrix.xlsx XLSX spreadsheet
RFP Attach 6 - IAS Hardware and Software Info.xlsx XLSX spreadsheet
RFP Attach 1B - Ref Info Sheet - Contract Specific Data.pdf PDF
Show all 41

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Advanced Analytics Technical Solution Pre-Solicitation Notice Questions and Answers

Updated– 11 October 2016

*Note – The Government has focused on answering questions that may impact a contractor's ability to respond to this pre-solicitation notice. If a contractor believes that Government's responses are insufficient, resulting in their inability to respond to this pre-solicitation notice, please advise the Contract Specialist via email.

1. Question: Is this pre-solicitation notice associated with the Request for Information (RFI) entitled “USMC Intelligence Analysis System Advanced Analytics Capability” and posted to the Federal Business Opportunities (FedBizOpps) website on 8 April 2015

Answer: Yes, this notice is associated with the RFI posted to the FedBizOpps website on 8 April 2015.

2. Question: How can a company provide a non-developmental item (NDI) without some developmental work to adapt it to the Marine Corps data needs?

Answer: In accordance with Federal Acquisition Regulation (FAR) 2.101, a “Non-developmental item” includes the following:

(1) Any previously developed item of supply used exclusively for governmental purposes by a Federal agency, a State or local government, or a foreign government with which the United States has a mutual defense cooperation agreement;

(2) Any item described in paragraph (1) of this definition that requires only minor modification or modifications of a type customarily available in the commercial marketplace in order to meet the requirements of the procuring department or agency; or

(3) Any item of supply being produced that does not meet the requirements of paragraph (1) or (2) solely because the item is not yet in use.

3. Question: What response is the Government seeking by 7 October 2016?

Answer: As stated in the pre-solicitation notice, the Government is inviting potential offerors to submit information on the following:

• A narrative description explaining the projected AATS software product's ability to support the following: (a) the intelligence cycle, including data entry, map display, search, analysis, collaboration, and production; (b) the intelligence analyst operating in a disconnected, intermittent, and low-bandwidth (DIL) network environment; (c) management of ontologies within the AATS; and (d) development of third-party plug-ins to the AATS software.

• A description of how the projected AATS software product satisfies the commercial item (CI) definition or non-developmental item (NDI) definition in Federal Acquisition Regulation (FAR) 2.101. For example, show that projected AATS software product is an NDI item and was previously developed and used exclusively for governmental purposes by a Federal agency, a State or local government, or a foreign government with which the United States has a mutual defense cooperation agreement.

• A description of instances where the projected AATS software product has been previously integrated and deployed together in a production environment to perform support for the intelligence cycle, support for the intelligence analyst operating in a DIL network environment; support for management of ontologies within the AATS; and support for development of third-party plug-ins to the AATS software.

4. Question: As the solicitation is full and open competition, please clarify the statement in the announcement that says, “The applicable NAICS code is 511210 with a size standard of $38.5 Million.”

Answer: This procurement will be conducted using full and open competitive procedures, and the applicable NAICS code is 511210 with a size standard of $38.5 Million. The NAICS code and size standard may impact teaming and subcontracting arrangements.

5. Question: How will responses to the multi-step advisory notice be submitted as the only options within SPAWAR E-Commerce are “Ask Question”, “Close”, “Subscribe” and “View Bidders List”. Are responses to be submitted via the “Ask Question” selection?

Answer: Responses shall be submitted to the SPAWAR e-Commerce website. Respondent may use the “Ask Question” feature and submit their response as an attached document.

6. Question: Will this be a 5 year award, or a base period and options to make up the 5 years total?

Answer: The Government anticipates a single award, indefinite delivery/indefinite quantity (IDIQ) supply and services contract with a five-year ordering period.

7. Question: Must a potential offeror submit a response to this RFI by 7 October 2016 in order to compete on the procurement when it is officially released?

Answer: A response to the pre-solicitation notice is not required in order to submit a response to the official RFP. SPAWARSYSCEN Atlantic is utilizing the Advisory Multi-Step Process (See FAR 15.202) in order to advise prospective offerors about their potential to be viable competitors and permit potential offerors to make informed decisions about whether to participate in this acquisition.

8. Question: Does the Government have a timeframe of when it would like to make an award for this support to begin?

Answer: Although subject to change, the projected contract award date is third quarter fiscal year 2018.

9. Question: Will the Government allow a non-vendor to purchase and provide the platform of choice as turnover for GFE?

Answer: The Government will review each contractor response to the synopsis/advisory notice and advise on the viability of the planned approach.

10. Question: Is a non-vendor services provider permitted to purchase software as an ODC?

Answer: The Government will review each contractor response to the synopsis/advisory notice and advise on the viability of the planned approach.

11. Question: Will the government consider a small percentage of non-NDI analytic software components that have been tested and proven to be part of a larger proposed NDI AATS?

Answer: In accordance with the definition of non-developmental items at FAR 2.101, the AATS may include minor modifications or modifications of a type customarily available in the commercial marketplace. The Government will review each vendor response to the synopsis/advisory notice and advise on the viability of the planned approach.

12. Question: Will the Government allow for the contractor to provide a NDI AATS on day one of award and be able to complete all integration efforts within a 12 Month period?

Answer: The delivered AATS software shall fully satisfy the requirements of PWS section 3.2 upon delivery.

13. Question: Does the Government anticipate the RFP to be a solution based solicitation that will ask offerers to provide sample software of their proposed solution? Will oral boards or software demonstrations be part of the RFP evaluation criteria?

Answer: Offerors will not be required to provide sample software or participate in an oral board; however, the Government is considering software demonstrations as part of the evaluation criteria.

14. Question: What is the anticipated AATS RFP release date?

Answer: Although subject to change, the estimated RFP release date is second quarter fiscal year 2017.

15. Question: What are the Accreditation requirements that the Government expects the contractor to perform? Are these Accreditation requirements accounted for in the Government’s “Notional Estimated Supplies and Services” graphic that was presented as an attachment?

Answer: PWS section 3.4.6 contains cyber security and information assurance requirements. These requirements are accounted for in Section B, CLIN 0004 (OEM/SME Support Services).

16. Question: Is this Draft PWS considered Step 1 of the multi-step advisory process which will be followed by, Step 2: Industry Day and Step 3: RFP Release?

Answer: Although this is subject to change, the Government anticipates conducting an Industry Day in the first quarter fiscal year 2017 and issuing the RFP in second quarter fiscal year 2017.

17. Question: The response instructions listed on the SPAWAR e-Commerce website limit offeror responses to six pages. Would the Government allow a cover page to be included outside of the six-page limit?

Answer: Responses to the multi-step advisory process shall be limited to six pages. This includes the cover page, if one is provided.

18. Question: The data entry requirements do not contain any requirements for deleting objects, etc. Does this mean that once an object, etc. is created, the only way to remove it from normal query/view processes is to mark it as archived? Also, same question, but related to properties whose values are set for an object?

Answer: The PWS requirements, as currently written, are designed to favor preserving a history of changes to data over deleting data. The Government will consider potential clarification of the PWS requirements.

19. Question: PWS Paragraph 3.2.5.1.2, line 529 - Is this meant to indicate that the contractor needs to inform the Government of the contractor’s ontology implementation requirements (i.e., structures required by the contractor’s ontology management tools)?

Answer: PWS Paragraph 3.2.5.1.2 is meant to indicate that if the Government provided AATS ontology must meet certain structural requirements in order to be correctly imported into the contractor’s AATS and provide the capability defined in the PWS, then the contractor shall provide the Government with those structural requirements and provide any necessary materials for compliance with those requirements.

20. Question: PWS Paragraph 3.2.5.1.5, line 544 - Please confirm that the word “either” in this requirement should be interpreted as “both” (i.e., the system needs to be able to update the ontology both via UI and import, vs one or the other).

Answer: The Government confirms that this interpretation is correct. The system needs to be able to update the ontology both via UI and import. The PWS will be revised at a later date.

21. Question: PWS Paragraph3.2.5.2.2.1, line 657 - Tagging: Please define what it means to “tag” an object.

Answer: Tagging an Object refers to the ability for the user to identify an Object by name in a document, and to have the software reduce the number of manual steps required to create an Object by that name, or reduce the number of manual steps required to associate the identified Object with an existing Object in the AATS database. The PWS will be revised at a later date.

22. Question: PWS Paragraph 3.2.5.5, line 865 - Please define what is meant by “standing” queries.

Answer: Standing queries are user-defined queries that are executed by the AATS at periodic intervals without user intervention.

23. Question: PWS Paragraph 3.2.5.5, line 883 - Please elaborate on what is meant by “learn from interaction with search results… to improve relevance of search results”.

Answer: This requirement refers to the analysis of user behavior to improve search relevance; one example of improving search relevance is a recommender algorithm based on user searches and clicks.

24. Question: PWS Paragraph 3.2.5.6, line 969 - Recommendations for Objects: Please clarify what is meant by “recommendations.” This term is not used in any of the subordinate paragraphs.

Answer: This requirement refers to the ability of the AATS to identify non-obvious relationships between Objects, and to “suggest” or “recommend” that the user investigate those Objects as well as the Object under direct user review.

25. Question: PWS Paragraph 3.2.5.8, line 1112 - Intelligence journal timestamps for objects: What is meant by an object being “conducted”?

Answer: The requirement should read, “The integrated intelligence journal shall record the timestamp at which all Objects are processed, created, and updated.” The PWS will be revised at a later date.

26. Question: PWS Paragraph 3.2.5.9.5.10, line 1244 - Export target lists: What is meant by “dynamic report types” (i.e., are these just predefined report templates that are populated at report-generation time, or are there other requirements)?

Answer: “Dynamic report types” are predefined report templates that are populated at report-generation time (see PWS Section 3.2.5.9.3). The PWS will be revised at a later date.

27. Question: PWS Paragraph 3.2.12.2 line 1396 - Analytical framework: Please clarify what is meant by “without the need for developing extensive API calls for data matching a particular query/filter set.”

Answer: This statement refers to the ability to operate on data without the cost of transporting data to and from the database via API calls for data.

28. Question: PWS Paragraph 3.2.5.12.2.2 - Streaming analytics: Please clarify what is meant by processing incoming data in a “streaming manner.”

Answer: Processing incoming data in a “streaming manner” means performing near real-time computations on data streaming from data sources (for example, sensors); it also refers to the ability to operate on data as it enters the system rather than via execution of a batch process.

29. Question: PWS Paragraph 3.2.5.12.2.5, line 1416 - Store intermediate results: The requirement is to “store intermediate results in a temporary, non-user-visible location.” What is the intended purpose of storing data in a temporary location that is not visible to users?

Answer: Intermediate results are only useful to the automated analytic process that produced the results; therefore, storing data in a location that is not visible to users prevents users from potentially drawing erroneous conclusions from data not intended for use outside of the automated analytic process.

30. Question: PWS Paragraph 3.2.5.12.2.11, line 1433 - User feedback to externally-developed analytic output: Please explain what is meant by “feedback.”

Answer: Feedback from the users provides a mechanism for the externally developed analytic algorithm to adapt and potentially provide better results. Feedback can be binary (thumbs up/down), graded (Likert scale), etc.

31. Question: PWS Paragraph 3.2.5.13.3, line 1479, - ICISM tags: The requirement uses the term “reliability.” Should this be “releasability”?

Answer: The requirement should read, “The software shall be capable of sending data to web services, via web applications with the use of ICISM tags for classification and releasability.” The PWS will be revised at a later date.

32. Question: PWS Paragraph 3.2.5.15.1, line 1569 - Cataloging imagery: Please provide more details on what is meant by “cataloging” imagery (and video).

Answer: Cataloging imagery involves extracting metadata from the imagery (or video) and providing a search capability of the imagery (or video) according to a user-selected metadata field.

33. Question: PWS Paragraph 3.2.6.17.5, line 1606 - Display selected object attributes: What is meant by “first” in the requirement that “all associated attribute values shall be displayed first” (i.e., the attributes values will be displayed before what other data)?

Answer: “First” means before any other attributes that belong to the same Object.

34. Question: Can the government please provide the expected time required to complete the multi-step advisory process.?

Answer: Although subject to change, the Government anticipates sending written notice to each respondent within four weeks after the response cutoff date.

35. Question: Are the following required/of interest?: (a) Analytic for video processing, (b) Analytic for processing audio, (c) Speech to text capability, (d) Optical Character Recognition (OCR) capability, and (e) Translation from foreign languages to English?

Answer: As indicated in PWS section 1.1, the Government is seeking an AATS that supports the activities and intent of each phase of the analyst’s workflow, and reduces manual effort through application of advanced analytics technologies.

36. Question: Will all ingested data be in English? If not, what languages need to be supported?

Answer: At present, the PWS does not identify specific language requirements. The PWS may be revised at a later date to clarify.

37. Question - Should the response to Special Notice/Request for Information (RFI) number N65236_SNOTE_000D7D9A posted to the Federal Business Opportunities (FedBizOpps) website on 4 October 2016 be separate from the response to the Pre-solicitation Notice posted to the FedBizOpps website on 16 September 2016. Also, does the Special Notice/RFI response count against the page limitation established for the Pre-Solicitation Notice?

Answer – A separate response is requested for the Special Notice/RFI posted to the FedBizOpps website on 4 October 2016 and the Pre-Solicitation Notice posted to the FedBizOpps website on 16 September 2016. Additionally, responses to the Special Notice/RFI will not count against the page limitation established for the Pre-solicitation Notice response.

38. Question: May responders “Submit Unsolicited Proposals” in response to this Pre-solicitation?

Answer: As stated in the Pre-Solicitation Notice posted to the FedBizOpps website on 16 September 2016, the Navy is not currently seeking proposals and will not accept unsolicited proposals.

File details come from the government source that posted it.