80JSC018NIICE__RFP_Amendment_2_Questions_and_Answers.pdf

Question 1: Does this Solicitation have a chance of being a SDVOSB set-aside?

Response 1: This solicitation is not anticipated to be considered for a SDVOSB set-aside.

Question 2: How firm is the requirement for FedRamp / GovCloud? I note that you ‘prefer’ this, but is not mandatory. What sort of weighting are you putting on this requirement? Is this a top/high priority for the program?

Response 2: FedRamp ATO is not required, and no additional weight is given for a system with FedRamp certification. The solicitation will be amended to reflect this change.

Question 3: Are there any other security regulations that you require? ITAR / DFARS?

Response 3: The security requirements for the system are listed in the Solicitation SOW (1.0.i.2). At this time, ITAR controlled information is not anticipated to reside on this system.

Question 4: I see that you have 508 compatibility as a requirement. Is compliance mandatory?

Response 4: Compliance is not required for proposal/quote submission. However, offerors must demonstrate their approach to minimum 508 compliance following contract award. NASA anticipates working with the successful offeror to determine the best approach for assessing 508 compliance during the contract phase-in period. Additional Information regarding 508 compliance can be found in SOW 6.0.

Question 5: Just to confirm, the responses are due Jan 17, 5:00pm CST.

Response 5: Responses to the solicitation are due Jan 17, 2018, 5:00 pm Central Time

Question 6: before responding to the RFQ it may be worth checking you are happy with cloud technology?

Response 6: Cloud Technology is considered acceptable. Please Reference SOW “1.0 Architectural Requirements” for additional compatability and security requirements.

Question 7: Can you provide/share some clarity on those documents and the process? I also wanted to confirm the RFQ due date.

Response 7: Per the NIICE Pre-proposal Bulletin slide 34, also attached as an amendment to this solicitation, the Proposal is anticipated to consist of 5 parts/volumes as listed below:

Volume I - Technical Factor

(Note: Per RFQ, Volume I - Safety and Health Approach and Labor Relations Approach are NOT required)

Volume II – Past Performance

Volume III – Cost/Price Proposal

Volume IV – Other Proposal Requirements

Volume V – Model Contract

NASA anticipates awarding to the technically acceptable, responsible offeror whose proposal represents the best value to the Government based on the Evaluation Criteria published in the RFQ (page 62).

Question 8: We would like to request that NASA open up competition to NAICS 541512 in the interests of allowing small businesses from a slightly higher size standard to participate in this solicitation. We believe this would benefit NASA and would result in lowering implementation risks while still including qualified small businesses.

Response 8: The Government is not currently anticipating changing the NAICS of this solicitation at this time.

Question 9: NASA indicates that the system should be compatible with all of NASA browsers and lists IE 11. For how long does the system need to support IE 11 for NASA?

Response 9: The system must be compatible with NASA standard browsers including Firefox, Chrome, and Safari. The matrix will be updated to remove IE.

Question 10: Do all users of the NIICE site need to be authenticated users? Are there any Public pages that do not require authentication?

Response 10: Yes, all NIICE users must be NASA authenticated users. No public pages are anticipated.

Question 11: Is Nasa Open to Self-registration of users or will they all need provisioning by administrator or data import?

Response 11: Yes, data import is required to import existing users. New user access will be managed through self-registration via NASA’s Authentication mechanism or by administrator provisioning.

Question 12: Can Challenge owners see/edit other challenge content?

Response 12: Challenge owners should only be able to see/edit challenge content for challenges they are assigned ownership to prior to challenge launch.

Question 13: Is each challenge solution going to be a separate page?

Response 13: There is no requirement for each solution to be a separate page.

Question 14: What would be the estimated avg size embedded images and particularly Videos on the Challenge pages?

Response 14: Estimated average sizes of Images are 1- 10 MB, Videos are 100 – 1000 MB.

Question 15: How large is the estimated data to be imported via CSV into the site? How many rows or categories of data?

Response 15: Existing Challenge Database: Estimated database size is 100 MB, attachments are estimated at 2000 MB. Database CSV is approximately 200 rows by 50 columns/fields.

Question 16: How many users are in the current system and what is the mix of internal NASA vs external (public) users?

Response 16: The NIICE preproposal bulletin, “CoECI Overview” section, (slide 9) provides current system usage statistics including challenges per year, user statistics, etc. There are no external users.

Question 17: Is NASA open to 3rd party COTS add-ons to the solution to provide extended functionality or features?

Response 17: Offerors may propose any add-ons available provided the system and add-ons meet the requirements in the statement of work and T&Cs.

Question 18: “Given that FAR Part 11 Describing Agency Needs 11.002 – Policy (a) (1)(ii).

States that an agency will “Only include restrictive provisions or conditions to the extent necessary to satisfy the needs of the agency or as authorized by law”. The RFP states “Synchronization with NASA’s Enterprise Directory (NED)” as stated in Attachment 5-1, row 12, which only can be met by the current incumbent contractor.

Would the government consider changing the RFP to state “the technical requirement for Synchronization with NASA’s Enterprise Directory (NED) along with other technical requirements must be met by the end of the phase-in period?”

Response 18: The RFQ will be changed to “Ability to synchronize with…”. Offeror’s proposals are expected to demonstrate the offeror’s approach to meeting these requirements by contract start/end of phase-in and during the period of performance.

Question 19: We have the following questions regarding '8OJSC0180007_Preproposal_Bulletin.pdf' included as an attachment to the solicitation numbered 80JSC018NIICE: Will multiple vendors be onboarded to this IDIQ? Will the IDIQ include task orders for services like consulting and custom software development?

Response 19: This contract is anticipated to be a single award. Per RFQ Clause “RATES TABLE FOR DEVELOPING TASK ORDERS”, IDIQ is anticipated to include: Training – Administrators, Training – Users, Annual Reports.

Question 20: Is the NTE amount inclusive of all possible options?

Response 20: NIICE Preproposal Bulletin slide 30 “NTE Maximum Contract Total - $1,000,000” includes IDIQ only. The Base Firm-Fixed Price effort includes SOW 1.0 – 3.0 and 5.0 and is priced separately and is exclusive of the aforementioned “NTE Maximum Contract Total” (IDIQ Maximum). SOW 4.0 effort is ordered under IDIQ and included in the aforementioned “NTE Maximum Contract Total”. The Preproposal Bulletin will be updated to reflect this change.

Question 21: Must the offeror be on the GSA schedule to be considered?

Response 21: No, however offerors must be registered in the SAM.gov database to be considered. Registration is free and additional information may be found at www.sam.gov.

Question 22: What Platform data must be migrated? Is an API an option vs a .csv export?

Response 22: It is anticipated that the successful offeror will import historical challenge data, associated attachments and user data. An API option may be available, but a CSV export is anticipated which will consist of multiple tables, attachments and relationship maps.

Question 23: In addition to only NASA employees being able to participate/respond, must the challenges be visible to only NASA employees?

Response 23: Only NASA authenticated users are able to view and access the NIICE system.

Question 24: Saas Product Services -- how are the projects paid for? Do we offer them a fee for x # of projects? what's the expectation on # of projects to run annually? How do we get paid? What is the payment schedule?

Response 24: The NIICE preproposal bulletin, “CoECI Overview” section, (slide 9) provides current system usage statistics including challenges per year, user statistics, etc.

Offerors are required to include as part of Volume III – Cost/Price and Volume V – Model Contract, completed clauses “CONTRACT VALUE”, “RATES TABLES FOR DEVELOPING TASK ORDERS”, “OPTION TO EXTEND PERIOD OF PERFORMANCE” with the areas currently labeled as “$fill-in” completed with the offeror’s proposed price for the respective period of performance (phase-in/base) or Task Order price (IDIQ). The “IDIQ DELIVERY ORDERS” and “TOTAL VALUE” lines of the “CONTRACT VALUE” clause will be updated as options are exercised and task orders are issued.

Per the RFQ, “52.232-33, Payment by Electronic Funds Transfer— System for Award Management (JUL 2013) (31 U.S.C. 3332)”, payment will be made through EFT. Payments are anticipated to be made on a monthly basis. The RFQ will be amended to include instructions for submitting invoices through the NASA or Government invoicing system when they are available.

Question 25: We allow anyone to be able to run a challenge; does someone need to assign the project? or can anyone at NASA just start the challenge and they become part of the NASA internal community?

Response 25: It is anticipated that all challenges must be reviewed and approved by the NASA platform administrator/moderator prior to challenge launch. Any NASA user that can authenticate in NASA Enterprise Directory can register on the NIICE system. Any registered user may submit a challenge candidate.

Question 26: The system shall support NASA employee authentication leveraging NASA’sLaunchpad authentication mechanism -- does this mean that NASA is looking for single-sign on with NASA email accounts?

Response 26: NASA anticipates leveraging the Launchpad authentication system, via NED, to allow for single credential sign-on to the NIICE system. NASA’s Launchpad system uses NASA email addresses as the User ID.

Question 27: System shall support synchronization with NASA’s Enterprise Directory (NED) (leverages Lightweight Directory Access Protocol (LDAP)). -- what does this mean? and what are the requires to support synchronization?

Response 27: The NASA Enterprise Directory utilizes the industry standard LDAP authentication protocol for user login and authentication. NIICE system authenticated users must be synchronized to match appropriate users in NED. Synchronization is required to ensure users removed from NED are removed from the NIICE system.

Question 28: Once Company Name Redacted, anyone has the ability to create a challenge, to act as the administrator of that challenge, and then to add others to the challenge as readers, moderators, etc. What role does NASA need/want the administrators to play?

What read/right access should they have above others?

Response 28: See Section iii, SOW. User Roles.

Question 29: Can you identify, more specifically, what administrators need to be able to do from the "homepage?" What do they need to be able to do on the backend? And what modifications do they need to be able to make, without vendor product assist? Is this homepage only visible to challenge administrators? or to everyone?

Response 29: See Response 28

Question 30: Regarding the Present/Past Performance Questionnaire for Contract(s), the RFP instructs that we provide our customers a Present/Past Performance Questionnaire.

What is the deadline date for which questionnaires to customers be submitted?

Response 30: Past Performance Questionnaires are required to be submitted by the submission of the other volumes of the proposal. Per the RFQ “INSTRUCTIONS TO OFFERORS”, January 17, 2018 5:00 PM Central Standard Time.

Question 31: Our NASA Internal Innovation & Collaboration Environment (NIICE) solution is hosted in the Fedramp cloud. Is this acceptable?

Response 31: Offerors are required to meet the requirements in SOW 1.0.i.2. FedRamp Cloud meets the requirements in SOW 1.0.i.2.

Question 32: Please provide clarification on the definition of role-based communications as it pertains to this solution.

Response 32: Users should be able to communicate based on a given role. Example: Role based distribution lists. Challenge Owners can communicate with participants as a designated Challenge Owner on their challenges (not just a regular site user).

Question 33: In the solution, would we need to show platform roles to all users?

Response 33: In general, no. It may be useful to display roles within a challenge

Question 34: In the solution, will rewards be both monetary and/or badges? If so, to what percentage of both?

Response 34: Monetary rewards are not anticipated. However, NASA will be providing non-monetary awards (e.g. experiences/tours, certificates, etc.). See Preproposal Bulletin for additional information. If the offeror provides badges through the NIICE system, it will be in addition to NASA provided awards.

Question 35: Please provide clarification to the ability to manage user roles as it pertains to this solution.

Response 35: Admin should be able to assign roles and corresponding permissions to site users based on their specific role in a challenge. (Admin, Challenge Owner, Site User) See section iii, SOW.