Attachment_1_SOW_update.pdf

i. Introduction

The NASA Center of Excellence for Collaborative Innovation (CoECI) requires a web application to serve as NASA’s internal challenge-based open innovation platform. CoECI’s internal open innovation initiative seeks to stimulate innovation across the Agency and connect employees to solve challenges by providing an online environment that facilitates an open community and provides a vehicle for NASA Employees to share knowledge and best practices.

NASA’s internal open innovation platform should promote these tenets through easy and intuitive access and participation in open competitions (challenges), incentives for participants, contributors, and solvers, and an integrated community management and communications system.

ii. Definitions, Acronyms, and Abbreviations

Center of Excellence for Collaborative Innovation (CoECI): CoECI collaborates with innovators across NASA to generate ideas and solve important problems by working with global communities using a challenge/competition-based, crowdsourcing approach. CoECI works with organizations to:

• Harness the power of the crowd for idea generation, problem solving or technology scouting

• Facilitate the planning and execution of challenges including scope development, cost and schedule management, marketing and awards

• Educate and share best practices

• Measure performance impacts

CoECI leverages both internal and external crowdsourcing mechanisms in support of NASA’s mission. One of CoECI’s endeavors includes an agency-wide initiative that seeks to increase innovation by fostering collaboration within the NASA community. The current internal open innovation platform supports this objective by enabling internally competed and incentivized challenges and allowing for open and interactive submissions and discussions.

Open Innovation Challenge: An open competition for all NASA contractors and civil servants to provide solutions or inputs to address a specific need. Challenges are limited in duration and usually result in a non-monetary award to a winning solver(s).

Crowdsourcing: The practice of obtaining needed services, ideas, or content by soliciting contributions from a large group of people and especially from the online community rather than from traditional employees or suppliers.

Requirements

1.0 ARCHITECTURAL REQUIREMENTS

i. Compatibility & Access

1. The system shall be compatible with NASA’s standard load web browsers

a. Microsoft Internet Explorer 11.0

b. Google Chrome

c. Mozilla Firefox

d. Microsoft Edge

e. Safari 10.1

2. The system shall comply with NASA IT security Guidelines.

a. NASA prefers that the SaaS Provider has FedRAMP ATO or reside on a certified system that has FedRAMP ATO, such as AWS commercial cloud or GovCloud, for more information visit https://www.fedramp.gov

b. The service provider portal shall communicate using Hypertext Transfer Protocol Secure (HTTPS) compliance per OMB M- 15-13 and NASA memo ITSD 16-53.

i. Approved versions of TLS shall be used.

ii. Approved signature algorithms shall be used.

iii. Authorized ciphers shall be used.

c. The contractor is authorized to do business in the US.

3. NASA@Work server and data storage

a. The NASA@Work platform shall be hosted on US based systems for both server and data storage

4. The system shall support NASA employee authentication leveraging NASA’s Launchpad authentication mechanism (SAML 2.0).

5. System shall support synchronization with NASA’s Enterprise Directory (NED) (leverages Lightweight Directory Access Protocol (LDAP)).

6. System shall have ability to support up to 60,000 users

7. System shall have ability support multiple Administrators

8. System shall have application availability in excess of 99.95%, and data availability in excess of 99.99%.

ii. Site Structure The system shall include the following pages and include Content Management Capabilities that permit the Administrator to add/edit sites pages and page content:

1. Home page that provides easy access to challenges and platform features

2. Browse Challenges capability that leverages a pre-existing information architecture to dynamically filter/sort challenge items

3. Individual pages for each challenge

4. A challenge/site dashboard with role-based views (administrator, challenge owner, etc.)

iii. User Roles and Role-based Capabilities

1. The system shall allow for content updates by individual users and groups based on defined roles.

2. The system shall include a role-based content management structure that supports various user roles and corresponding workflows.

3. System shall support ability to incorporate and customize Terms of Service pop-up /screen for first-time users.

User/System Role Minimum Capabilities

Administrators (up to 10 max) • Manage homepage content and layout

• View, create, edit, publish and delete challenges and related content

• Ability to provision/manage user roles

• Ability to award challenge winners

Challenge Owners (can assign multiple per challenge)

• Draft challenges and submit for publication

• Comment on challenge solutions/discussions as Challenge Owner

• Evaluate, score, and submit challenge winners for award

Site Members • Draft/submit solutions

• Comment on Challenges/challenge discussion

2.0 FUNCTIONAL REQUIREMENTS

i. Usability/Accessibility

UI must be 508 compliant. NASA will work with contractor to determine best approach for assessing 508 compliance. 508 requirements for web applications can be found in the Voluntary Product Accessibility Template® (VPAT®) http://www.itic.org/policy/accessibility/, criteria can be tailored as applicable for the given requirements.

ii. Platform Transition System shall support the ability to migrate (import/export) current system (user, challenge, etc.) data from .csv format.

iii. Scalability Server(s) shall have the capacity to accommodate loads associated with a large communications push or challenge launch (Note: NASA currently has a potential maximum of 60,000 community members).

iv. Homepage Homepage shall operate as a landing page that provides information and navigation capabilities for community members (i.e. challenges, events, notices, leaderboard, etc.)

Homepage shall support administrator management of page content.

v. Challenge Pages Each challenge shall have its own challenge page that includes, at a minimum, a challenge description and supporting videos/images, the deadline for submission, the challenge status (open/closed/etc.), and incentives.

vi. Challenge Solutions The system shall support the submission of challenge solutions and include capabilities such as challenge discussions, comments on submissions, saving submission drafts, attachments, embedding images/videos with thumbnails.

vii. Solutions Evaluation The system shall support the scoring and evaluation of challenge submissions, flagging/bookmarking and awarding solutions, commenting on submitted solutions (challenge owners), and enabling user voting on proposed solutions.

viii. Browsing Challenges The system shall support search/browse capability of current and historical challenges and include features such as the ability to filter by subject area, status (open/closed/draft), challenge owners, participants and winners, and challenge timeline.

ix. Administrator Dashboard System shall provide administrative dashboard and reporting capabilities with filterable/sortable view of all challenges, the ability to generate reports and filter/sort/compile data on system activity, challenge data, and user data/activity, and site analytics.

x. Notifications/Communications System shall provide the ability to communicate directly with community members and supports features such as the ability to flag or share challenges via email, send communications and surveys to community members, perform role-based communications.

Additionally the system shall support community notification features including subject-matter and challenge-specific subscription notifications.

3.0 SYSTEM SUPPORT

Contractor shall provide baseline training and support services which may include Subject Matter Expertise on challenge development and role-based system training & education.

Contractor shall provide administrator support for timely resolution of technical issues.

Contractor shall coordinate major platform updates and corresponding user outreach (as warranted).

4.0 IDIQ

Contractor shall provide User and Admin specific training as ordered per the Task Ordering Procedures.

Contractor shall submit Annual Reports as ordered per the Task Ordering Procedures.

5.0 DRD Reporting

Contractor shall submit all DRDs and DRD updates by the respective DRD due dates.

6.0 SUPPORTING INFORMATION

CoECI Website https://www.nasa.gov/offices/COECI/

NASA Technology References NASA Section 508 Overview https://www.nasa.gov/accessibility/section508/sec508_overview.html

NASA IT Security http://www.nasa.gov/offices/ocio/itsecurity/