(Pre-Solic) 20170217 - Draft Solic Q&A Update.docx

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

Updated – 17 February 2017 (New Questions #62 - #78)

1. Q: What is the value of a software development plan for a COTS/NDI Solution?

A: The Government is asking for an already existing software development plan which proves that the offeror has a repeatable process for the software that already exists.

2. Q: Factor G evaluation: Are you planning for people to build first again? (Meaning this is not an off the shelf solution you are asking people to build a specific, specialized software package for limited potential resale to others…In this economy that is a big ask that will limit competition B&P dollars aren’t what they used to be, and may likely result in a less effective capability as people strive to control their upfront spend. One winner and the others left with empty spend.)

A: It must be an already existing capability.

3. Q: Does SPAWAR expect to procure 100% NDI software for AATS: or is some development acceptable for year 1, CLIN 1 Factor A?

A: Yes, the Government expects to procure 100% NDI and/or CI. Please see PWS.

4. Q: Has the government’s market research determined that there is not a commercial, vertically-integrated, proprietary tool that meets 100% of their requirements as a single tool?

A: The Government’s market research has determined that there are multiple commercial solutions that could be integrated into IAS that meet the Government’s requirement.

5. Q: While the Government intends to award DO1 concurrently with contract award, how long after the contract award will the contractor be expected to deliver the solution?

A: Within 90 days after date of contract award.

6. Q: Define soon after contract award from the CI and NDI intent slide.

A: 90 days. If additional clarification is needed, please submit question(s) through proper channels.

7. Q: Will users have the opportunity to assess the offered solutions during phase 2?

A: The Government will have appropriate user representation.

8. Q: Since the disconnected client and IW server are so critical to the mission, will the Government consider field demonstrations with the users for the Factor G phase 2 evaluation?

A: No

9. Q: How will the DIL’s requirement be assessed during demonstration?

A: Demonstration instructions and requirements will be provided with the invitation.

10. Q: Will the Government allow for field testing of the DIL replication capability?

11. Q: If the requirement is to deploy a tested and accredited system in one year, shouldn’t Factor G be weighted much more than all the others?

A: Refer to the PWS and Sections L&M.

12. Q: Is the intent of putting a services company in front of this acquisition to ensure stability with the baseline especially over 5 years? Have you considered two purchases, one for product and a separate acquisition for services? You could get services off of GSA.

A: As part of the acquisition planning the Government determined this requirement includes both product and services.

13. Q: How much time will be given between being invited to demonstration and the date of the demonstration (how much lead time will be given for the demo)?

A: Twenty Ten calendar days from getting the demonstration invitation and details.

14. Q: Will the demonstration data be made available prior to the demonstration, including the RDF for the ontology?

A: Yes, it will come with the invitation.

15. Q: When would Factor G demonstrations take place, and where?

A: Twenty Ten calendar days after receiving demonstration invitation and details, and at SPAWAR Atlantic facilities Charleston.

16. Q: What will the notification time be for demonstration?

A: Twenty Ten calendar days after receiving demonstration invitation and details.

17. Q: If a company is selected to move to Phase 2, how much time will the company get to prepare before the demonstration is due?

A: Twenty Ten calendar days after receiving demonstration invitation and details.

18. Q: When will the ontology be provided?

A: It will come with the invitation.

19. Q: In the case of interface standards, what are the preferred standards for APIs?

A: There is no Government preferred list of API standards.

20. Q: When will an IAS AATS system interface requirements document be released?

A: Known interfaces will be shared upon starting integration activities.

21. Q: Will there be a single demonstration for Factor G or separate demonstration for each subfactor?

A: Single demonstration (same day).

22. Q: What is the timeline for Factor G demonstrations?

A: Instructions will be provided with the invitation.

23. Q: What is the environment technical stack?

A: Vendor provided hardware will be used for the demonstration. Please refer to solicitation attachment 6 which identifies the hardware specifications for IAS. Instructions will be provided with the invitation.

24. Q: Will you consider ontologies other than OWL 2 RDF/XML?

A: Please refer to PWS section 3.

25. Q: Cyber security requirements: how much of the RMF will be required prior to the demonstration?

A: None

26. Q: Will the demonstration be done in both connected and disconnected modes?

A: Instructions will be provided with the invitation. Refer to sections L and M of the solicitation, Subfactor G2.

27. Q: Concerning the ontology 3.2.5.1, recommend to user and saved vs. standing queries. Can you provide additional explanation of this requirement? Maybe talk over a specific use case.

A: Need more specifics. Please clarify and resubmit this question through the proper channels.

28. Q: If demonstration can provide capability beyond subfactors, will that be considered?

A: Please refer to Section L, Factor G

29. Q: Can Government provide AATS ontology as part of RFP?

30. Q: Has Government defined key performance parameters for system? Ontology based systems are notoriously slower than relational based systems. Example, x number of queries performed by y number of analyst in 1 hour.

A: The Government does not have specific KPPs associated to AATS. The Government has focused on technical performance requirements for the AATS solution on the IAS FoS.

31. Q: CI/NDI intent: estimated timeline for projected effort milestones.

A: Projected award for contract is April 2018

32. Q: To what degree of current implementation should this NDI have?

A: Refer to section L, Subfactor A5 of the draft RFP.

33. Q: Is there an interest in any specific tool or capability?

34. Q: Will the Navy be releasing CONOPs that the software tools are intended to support?

A: Please refer to Section C of the draft RFP which lists references.

35. Q: Will the Navy be developing the workflow tools or does one exist?

A: There is not a current tool that does this, but there are processes identified in the resources referenced in the draft RFP.

36. Q: Is there any interest in capability from classified programs above secret?

A: Not with this solicitation

37. Q: Can you tell us the companies that work currently on the AATS baseline?

A: There is no existing AATS baseline within the IAS FoS.

38. Q: Will the Government provide a demonstration environment for offerors in phase 2 which we will install into? (this could “level the playing field and ensure solutions are demonstrated in similar constraints and consistent with your infrastructure).

A: Refer to section L, Factor G. Instructions will be provided with the invitation.

39. Q: How long will the phase 2 demonstration be? Will the offerors need to demonstration all or as many as possible of the PWS capabilities?

A: See section L, Factor G of the draft RFP. Additional instructions will be provided with the invitation.

40. Q: What, if any, legacy applications will carry forward as part of this deployment?

A: Please reference the software specification attachment of the PWS. There are no legacy AATS applications on IAS FoS.

41. Q: Can the Government bring back up the chart on section L&M evaluation factors for phase 1 and 2?

A: The slides will be made available.

42. Q: Location(s) to support the AATS platform solution environment and secure cloud environment possible for primary data platform.

A: Please clarify and resubmit this “question” through the proper channels.

43. Q: IAS software baseline, the products today in use to be available for demonstration or to incorporate into solution set analysis?

A: The Government will not be providing the IAS baseline for integration prior to award. Reference the software and hardware specifications contained in RFP attachment 6.

44. Q: Can we get example data and RDF/OWL V2 examples?

A: Information will be provided with the invitation to Phase 2. Nothing will be released in Phase 1.

45. Q: Ontology: how often is this expected to change? It is clear it will change but how dynamic?

A: Ontology will be updated by the Marine Corps as needed.

46. Q: To what extent does this need to be a modular deployable system, pre-installed on h/w that can be deployed worldwide at a moment’s notice?

A: The IAS FoS is a modular deployable system that will have the AATS on the system.

47. Q: What is the estimated number of concurrent users this system will need to support?

A: 135 total servers; approx. 2500 clients (maximum based on AAO)

48. Q: Can you be more specific on the required capabilities regarding the automation of unstructured text importation?

A: Refer to PWS Section 3. Please clarify and resubmit this question through the proper channels.

49. Q: Will this system need to have mapping (geographic) software as part of the offering or does it merely need to be able to export data to various geographical programs?

A: Refer to PWS Section 3.

50. Q: Will the Government consider cost as part of Phase I, Phase II, or both?

A: Cost will be considered in the trade off analysis during both phases.

51. Q: Why is Factor A considered/weighted again in Phase II? Does this effectively “double count” written claims over fully functional demonstrated software – which should be the Phase II purpose?

A: A tradeoff analysis will be conducted at the completion of each phase and will consider the overall technical rating of all factors evaluated and cost at each phase of the evaluation. The tradeoff analysis must consider all factors evaluated as the basis for award for the final award decision.

52. Q: Will the solicitation be released as a small business set-aside?

A: The solicitation will be an unrestricted competitive procurement.

53. Q: Does Phase II Demonstration imply a second demonstration? In addition to pre-proposal demonstrations?

A: There is one demonstration required in the source selection for this solicitation, and this will occur during Phase II.

54. Q: Please provide a breakdown of the Total Acquisition Value (TAV).

A: TAV is the Total Proposed Cost. The TAV must equal Section B total.

55. Q: What is the value of the initial task orders (CLIN 0001 and CLIN 0004)?

A: The Government does not intend to provide the estimated value of the initial delivery or task orders. Offerors are expected to submit the proposed value as a part of their proposal.

56. Q: Will industry be evaluated higher if their small business plan is higher than 5%?

A: The subcontracting plan, which is only required from large businesses, is a separate requirement than the small business participation evaluation Factor and is in addition to the information required to evaluate the small business participation Factor. Small business subcontracting plans must meet the established DoD goals of total subcontracting dollars (not TAV) which can be found at http://www.acq.osd.mil/osbp/statistics/sbProgramGoals.shtml. The minimum acceptable small business participation average goal is established as 5% of the TAV for this procurement.

57. Q: Are you sure 5% participation for the small business is going to bring innovation needed?

A: The established goal is based on market research. The purpose of the small business participation Factor is to foster small business participation.

58. Q: Consider splitting the 5% across both the FFP and the CPFF or ensure it is represented on all CLINs?

A: The 5% is applied to TAV which includes CPFF and FFP.

59. Q: Will slides from presentation and list of attendees be available? If so, where (link)?

A: Presentation material and a list of attendees will be made available at https://e-commerce.sscno.nmci.navy.mil/

60. Q: Will the Government allow contractors to revise their cost proposal after demonstration?

A: Proposal revisions will not be allowed unless discussions are held.

61. Q: When does the Government expect to announce and notify companies that were down-selected/not down-selected?

A: Offerors will be notified after the completion of the evaluation of Phase I and a tradeoff analysis has been completed.

62. Q: How will the Government evaluate the sustainability of a non-developmental item (NDI) versus a true commercial off-the-shelf (COTS) item when NDI typically requires services to upgrade and the COTS is maintained under license?

A: The Government will evaluate each cost/price proposal in accordance with solicitation provision M-307 (Evaluation and Criteria and Basis of Award (Best Value - Variation). With regard to pricing for sustainability of NDI versus COTS items, the solicitation will allow each offeror to submit a cost/price proposal for the initial delivery of AATS software under contract line item (CLIN) 0001 and for AATS annual software sustainment (including AATS annual license renewal, software updates, and security updates) under CLINs 0005, 0006, 0007, and 0008.

63. Q: What risk reduction steps is the government currently taking in terms of data management and strategy?

A: Data management strategy is not part of this solicitation.

64. Q: Do you view analytic models as products or services?

A: Analytic models are part of the product delivery (CLIN 0001 – Delivery of AATS Software).

65. Q: How much data is expected to be ingested daily? What is the current size of data being held?

A: The amount of data to be ingested daily will vary based upon the echelon level and employment of the AATS capability.

66. Q: Are there data sizing estimates expected to be managed within each of the 3 Tiers? Along the same lines are there estimates of the synchronization workload.

A: The amount of data to be managed will vary based on the echelon level and employment of the AATS capability.

67. Q: Can you talk about total and concurrent user numbers at the different deployment levels?

A: The number of total and concurrent users will vary based on the echelon level and employment of the AATS capability.

68. Q: How will the Government evaluate software tools that we could bring from other government agencies? E.g., we would not sell the tool, but instead offer for integration?

A: The Government will evaluate each proposal in accordance with the solicitation evaluation factors and solicitation provision M-307 (Evaluation and Criteria and Basis of Award (Best Value) (Variation)).

69. Q: It appears that services are not required in years 2 and 4? Is this the case? Who will mitigate vulnerability and troubleshoot integration issues at this time? What about data integration and ontology updates at this time?

A: Contract line item (CLIN) 0004 will provide Original Equipment Manufacturer (OEM)/ Subject Matter Expert (SME) Support Services for the entire contract performance period (contract years 1 through 5). CLINs 0005, 0006, 0007, and 0008 will provide AATS annual license renewal, software updates, and security updates.

70. Q: Given the timeframe and nature of the procurement, why is CMMI referenced in the PWS in lieu of other development methodologies such as agile or SAFE agile?

A: Draft solicitation, Section C, paragraph 6.2.1 indicates the contractor shall have processes in place that coincide with the Government’s quality management processes, and the contractor shall use best industry practices including, when applicable, ISO/IEC 15288 for System life cycle processes and ISO/IEC 12207 for Software life cycle processes.

Additionally, draft solicitation, Section L, Subfactor D3 (Model Based Maturity Assessment) states that where the implemented process execution of the software development model areas do not align to CMMI Level 3, or when they are executed under a different process model, the offeror shall describe their model approach in sufficient detail to encompass all developmental phases and associated major activities of the SDLC as described in IEEE/EIA Std 12207:2008.

71. Q: Will this system need to have mapping (geographic) software as part of the offering or does it merely need to be able to export data to various geographical programs?

A: Mapping requirements are identified in draft solicitation, Section C, paragraph 3.2.5.3.

72. Q: Is the Government choosing viable primes from the companies that have responded to previous sources sought/RFIs? If yes – are you still accepting responses?

A: As indicated in the AATS Industry Day/Pre-Solicitation Conference briefing presented on 5 December 2016, the estimated solicitation issue date is second quarter of fiscal year 2017. All potential offerors may submit proposals and should monitor the SPAWAR E-Commerce website for further updates on this procurement.

73. Q: Please confirm this will be a Full and Open competition.

A: As indicated in the pre-solicitation notice of 16 September 2016, this procurement will be conducted using full and open competitive procedures.

74. Q: Will this bid be competed under Seaport E – or F&O on FBO from SPAWARSYSCEN?

A: When it is released, the solicitation will be posted to the SPAWAR E-Commerce website.

75. Q: Would the Government please clarify what is expected 90 days after award? For example, does the Government expect to begin integration at the 90-day milestone, or is the expectation to have the solution fully integrated within 90 days? The Government accreditation process to be fully integrated into the required networks (i.e. SIPR, JWICS) can take well over 90 days.

A: CLIN 0001 is for Delivery of Advanced Analytics Technical Solution (AATS) Software within 90 days after date of contract award. CLIN 0004 is for Original Equipment Manufacturer (OEM)/Subject Matter Expert (SME) Support Services to assist the lead system integrator to integrate the AATS into the IAS FoS baseline after delivery of the software in 90 days. It is not expected that AATS will be integrated into the IAS baseline prior to the 90 days delivery of the software.

76. Q: Would the Government please revise the timeframe for the Phase 2 Demonstration from a 10-day notice to a 30-day notice to all invited offerors? A 30 calendar day period is consistent with similar Federal programs and would provide enough time for all invited offerors to review Government-provided source data, prepare their demonstration environments, and ship and set up hardware and software at the prescribed SPAWARSYSCEN Atlantic facility. Without the proper amount of time to support the Phase 2 Demonstration, highly rated offerors identified in Phase 1 may be forced to 'no-bid' this procurement, thus reducing competition.

A: The timeframe for the Phase II Demonstration is currently under review. It is anticipated the revised timeline will be extended to a 20 calendar day notice prior to the date of the demonstration.

77. Q: Would the Government please provide an estimated date for the Phase 2 evaluation schedule? The Government's intended timeline will provide offerors valuable information in preparation for Phase 2.

A: The government cannot provide a date for Phase II evaluations as the timeline for evaluations and corresponding phases cannot be predicted in any source selection due to the significant number of unknowns (i.e. complexity, qty of proposals, etc. ). Below are the projected / estimated solicitation and major milestone dates for planning purposes:

· estimated solicitation issue date – 2nd quarter, fiscal year 2017

· estimated contract award date – April 2018

NOTE: The anticipated preparation timeline for Phase II evaluations is detailed under the government response to Question 76.

78. Q: Would the Government please provide the detailed methodology to be used in the evaluation of Subfactors A1 through A5 in Section M? For example, will adjectival ratings/colors be assigned to each Subfactor, or will a quantitative scoring methodology be employed, or another methodology altogether? Please provide specific details on how each Subfactor will be scored as a whole and how each will be scored relative to the individual elements that will be considered within each Subfactor.

A: As stated in Federal Acquisition Regulation (FAR) 15.204-5(c) and FAR 15.304(d), all factors and significant subfactors that will affect contract award and their relative importance shall be stated clearly in the solicitation. The rating method need not be disclosed in the solicitation.

File details come from the government source that posted it.