Atch_A__02_00703_DRAFT_PWS_OIO_Coding.pdf

Atch A: NIST PSCR OIO as of 01/04/2018

PERFORMANCE WORK STATEMENT

OPEN INNOVATION OPPORTUNITY: CODING EVENT CHALLENGE

UPDATED AS OF 01/04/2018

I. BACKGROUND

The National Institute of Standards and Technology (NIST) Public Safety Communications Research (PSCR) program has established the Innovation Accelerator (IA) to spearhead Research and Development (R&D) that supports the development and deployment of the Nationwide Public Safety Broadband Network (NPSBN). PSCR’s Open Innovation Program engages public safety, government, academia, and industry to identify innovation opportunities and foster technology advancements for public safety communications through Open Innovation Opportunities (OIO).

The most recent OIO is a public private partnership focusing the coding and software expertise of students, novices, and professionals on the data and software specific challenges facing first responders and public safety professionals with the goal of improving public safety in local communities and across the nation.

II. OBJECTIVES

In general, the Contractor shall assist PSCR in the design, management, and implementation of the competition named “Public Safety Code: <X>” which consists of a series of coding and innovation events as part of a national competition. Events are technology development marathons that draw on the talents and initiative of bright minded volunteers – developers, engineers, technologists, designers, and anyone with a passion and desire to have an immediate impact on the world. They are open to anyone who has a passion for making a difference and are focused on developing real solutions to public safety related events. Each event is part of a larger year-long effort, intensively working to prototype solutions, and subsequently refining and implementing the most promising prototypes.

The specific objectives of this work are as follows:

1. Host ten (10) innovation & coding events across the U.S. between May 2018-May 2019.

2. Each event requires a partnership with local Universities, Coding Academies, and Public

Safety Organizations with the expertise, local network of participants, and connections to the program mission to support the success of each event.

3. Each event will have ten (10) coding contests for software or computational outputs depending on the specifics of each contest.

4. Contests will be discrete, refined, focused topic based coding activities created in collaboration with PSCR and the Contractor.

5. Support a unified event website, coordinate across all ten events, support registration, post event statements, link data sets, and support collection of official entries.

6. Support the evaluation and assessment of challenge contestant’s work product, Subject Matter Expert review of work products, and final judging of prizes to be awarded to participants by NIST or other partners.

7. Assist with ranking outputs from all events to select the highest qualified participants to present their work at a national event in June 2019.

III. SCOPE

The Contractor shall provide the following open innovation services and support:

1. The Contractor shall perform all management functions including technical and business management necessary to plan, implement, track, report and deliver the required services described herein.

2. Platform design and use for prize and event competitions and community engagement;

3. Planning, implementation, and facilitation of digital and in-person events. (e.g., Hack-a-thons, data jams, idea jams, and code events);

4. Support services for OIOs. (e.g., review, judging, metrics/analysis, industry research, technology searches);

5. Consulting services for OIOs. (e.g., community development, outreach, problem definition, prize strategy, impact and process evaluation);

6. Provide access to unique research on innovation best practices;

7. Promote NIST and the PSCR Innovation Accelerator Program to help build a network of partners.

IV. TASKS

The Contractor shall assist with or be responsible for the completion of the following tasks:

1. Concept creation, vetting, and development

a. The Contactor will be required to coordinate with PSCR staff supporting the internal and external process concerning concept review and selection of concepts for continued development in the NIST OIO review and approval process (which is generally outlined in these series of tasks). The concepts created by this task will be the core elements for creating the ten contests offered at each of the ten events hosted.

2. Research to support the Contests

a. Research the created concepts and industry trends to develop technology baselines to ensure that the concept is focused on a clear problem definition. Example research tasks include:

1) Technology search.

2) Intellectual property mapping and patent searches.

3) Sourcing and business capabilities research.

4) Product capability assessment in the communications, IT, software, hardware fields.

b. Identify networks or potential participants to engage by creating outreach and communications strategies for the contests.

c. Determine how to measure the outputs and outcomes of each contest and how to collect and assess progress toward those outputs and outcomes.

3. Design and build the Events and Contests

a. Determine the structure of the contests

1) Identify intellectual property issues, conflicts or other specialized terms and conditions for participation in the event/contest.

2) Create rules for the event/contest that comply with all NIST legal and regulatory requirements.

3) Create terms of participation that comply with all NIST legal and regulatory requirements.

4) Create participant agreement that complies with all NIST legal and regulatory requirements.

5) Complete an insurance determination for participation in the event/contest.

6) Obtain forms and agreements needed for judges (Non-Disclosure Agreement

(NDA), etc.).

b. Develop incentives for participants and stakeholders.

c. Outline potential partnerships to increase the impact of the event/contest.

d. Draft the Challenge.gov Notice.

e. Judging:

1) Determine qualifications for Judges.

2) Develop judging criteria.

3) Create scoring sheets and process.

4) Distribute to, and collect from, all judges the completed legal agreement and forms (NDA, etc.), complying with all NIST legal and regulatory requirements.

f. Payments to participants

1) Collect and ensure the accuracy of data needed to provide payment to participants and coordinate with NIST PSCR to ensure that payments are completed properly and on schedule.

4. Launch the Events and Contests

a. Capture launch metrics.

1) Track web visits (Event.gov, vendor platform, nist.gov/pscr page, etc.).

2) Track email campaigns (how many, where in country, audience).

b. Outreach, media, and marketing efforts for community engagement.

1) Assess strategies pre-launch to determine current trends, complete a marketing strategy in coordination with NIST PSCR staff, and be prepared to implement the strategy as part of the events/contests launch.

2) Information webinars to reach potential participants.

3) Develop and implement marketing/outreach strategies.

(a) Research methods of reaching diverse communities, and engaging stakeholder communities in the events/contests.

(b) Create digital, video, print content for engaging participants and stakeholder communities.

(c) Place content through ad buys, op-eds, blogs, coordination with media or outreach partners to engage participant and stakeholder communities.

(d) Assess the value of different marketing channels through reporting and analytics and coordinating with NIST PSCR staff to optimize the impact of outreach efforts.

c. Internal Communications

1) Create content for NIST PSCR communications team to distribute and place via internal communication channels (e.g., PSCR website).

d. External Communications

1) Coordinate with NIST PSCR staff to develop and implement a brand awareness and placement to increase connectivity to stakeholder and participant communities (e.g.,).

(a) Email lists of potential participants.

(b) Blogs.

(c) Social media.

(d) Event.gov.

5. Run the Events and Contests

a. Community engagement to ensure that participants are active and accomplishing the goals of the events/contests, such as:

1) Monitor chat-boards, forums, and emails.

2) Monitor social media.

3) Run webinars to explain OIO goals and answer contestants, reviewers, and or judge’s questions.

b. Develop and implement strategies to engage current and encourage potential participants.

c. Provide updates throughout the events/contests via social media or other methods.

d. Metrics collection.

1) Capture metrics from the launch phase into the run phase of the events/contests and adjust methods accordingly.

2) At the end of the run phase (after judging) collect:

(a) # of participants.

(b) # reach.

(c) # of submissions.

(d) # of viable solutions.

(e) + all web metrics and social media.

(f) + industry check-in.

e. Assess the significance of and coordinate with NIST PSCR staff to address changes in industry in the time between the events/contests launch to its conclusion.

f. Organize virtual storage capabilities (e.g., cloud computing products) for participants to store, retrieve, and access data securely outside and independently of the NIST PSCR network.

g. Organize collaboration tools and/or platforms for participant and stakeholder communities.

h. Detailed Events/Contests Logistics.

1) Kicking off with a Coding & Data Bootcamp - The purpose of a Bootcamp is to broaden the base knowledge of hackathon participants with the goal of expanding the diversity of skills and perspectives to address events/contests. Coding & Data Bootcamps include a series of talks and hands-on workshops to allow participants new to the activity to get their feet wet using skills and resources that would help them engage productively at the upcoming Event. Workshop topics could include:

(a) Getting started with Arduino.

(b) A brief intro to UX design.

(c) Telling the story: the art of the project pitch.

(d) Finding the data needed.

i. Participant Registration.

1) All events/contests registration will be accomplished online.

2) All events/contests must use a unified official registration system.

3) Encourage participants to register prior to events/contests.

4) All events/contests require a check in at the events/contests entrance desk.

5) The events/contests desk will be staffed throughout the events/contests to:

(a) Register anyone who attends the day of the events/contests but has not pre-registered.

(b) Direct participants to check in on events/contests days.

(c) Direct participants to fill out and wear name tag stickers.

(d) Direct the participants to the events/contests floor where they can sit, store the personal items, etc.

(e) Answer any questions participants may have.

(f) Provide a computer with Internet so participants who haven’t registered may do so.

j. Venue Selection Criteria.

1) Consider community centers, conference centers, and university campuses.

2) Available 24 hours per day for events/contests duration.

3) Capacity for holding all participants in one large room for briefings, presentations, and awards ceremonies.

4) Have smaller breakout rooms or areas where groups can work together.

5) Convenient access via public transportation.

6) Reasonable access to building (no high security buildings).

7) Reasonable access to local restaurants.

8) Allow participants to bring in food.

9) Have tables and chairs for small group gathering and brainstorming.

10) Have bathrooms available.

11) Convenient refuse disposal.

k. Connectivity Guidelines.

1) Internet connectivity is required.

2) Access to electricity/plugs for all the participants.

3) Bandwidth sufficient for all participants to actively use the Internet simultaneously.

4) Plenty of IP addresses available for the participants (each participant is allowed up to 3 devices).

5) Ensure Wi-Fi availability and access.

6) Capacity for video/web streaming.

7) Capacity for live online connection with other sites.

l. Supplies.

1) Notify participants laptops will not be provided.

2) Consider having the following spare supplies available:

(a) Power strips.

(b) Extension cords.

(c) Projector/Screen (or blank wall).

(d) Microphone/Podium.

(e) USB drives.

(f) Tables/chairs (if not provided at venue).

(g) Name tag stickers.

(h) Laptop/printer (for registration and other general purposes).

(i) Office supplies: Pens, pencils, highlighters, stapler, paper.

(j) Whiteboard/Blackboard/Large Paper.

(k) Dry erase pens/chalk/markers.

m. Pre-Event/Contest Coordination – seek community groups to partner with, such as:

1) Universities – generally make good hosts.

2) Coding academies – generally have skilled potential participants.

3) Public safety organizations – to provide context, mentorship, and mission engagement.

4) For-profit organizations – able to participate as well as to support the Event and encourage participation.

5) In general, software and technology companies, telecommunications companies, NGOs, civil society organizations, government offices, universities, etc., are all potential partners.

n. Outreach to Participants.

1) Coders and developers.

2) Anyone passionate about the public safety mission.

3) Attend tech and non-tech meetups. Go meet with people.

4) Post on mailing lists with a technical audience at least 4 weeks before the Event.

5) Post on local university mailing lists.

6) Blog about it on your own and other technical blogs.

7) Post on Event planning sites.

8) Tweet about it on Twitter.

9) Personally, invite your friends that you think will have a great time.

10) Help people market the Event to their friends.

11) Encourage people to "own" the Event.

12) Make the time and place very clear.

o. Outreach to Volunteers for Staffing.

1) Registration support.

2) People to help manage logistics like food and trash.

3) Clean-up after the Event.

4) People available to answer questions.

p. Outreach to Media.

1) Press Releases – sample press releases will be circulated to local lead teams at least four weeks before the Event.

2) Social Media – materials for outreach to local, national, and international tech blogs that you read and ask them to post about the Event.

3) Local pitch contacts for regional outreach groups and media.

4) Other outreach materials as necessary, for example support for follow up interviews and questions.

5) All engagement with media will be coordinated with NIST PSCR.

q. Post Events/Contests Reporting & Media Summary.

1) Collect all events/contests social media channels so the events/contests can be followed on Twitter, Tumblr, Facebook, Instagram and any other relevant platforms.

2) Blogging and other publications – collect all related publications initiated by NIST, the events/contests, or independently.

3) Summary of how the events/contests went – the results, the winners, lessons learned, number of participants, copy of the agenda, pictures, etc.

r. Event Agenda (example only).

1) Day 1.

(a) 9:00 a.m. Registration.

(b) 10:00 a.m. Schedule and logistics announcements.

(c) 10:30 a.m. Subject Matter Expert briefing.

(d) 11:00 a.m. Begin developing.

(e) 12:30 p.m. Lunch break.

(f) 1:30 p.m. Developing continued.

(g) 4:30 p.m. Optional progress briefing, more developing.

(h) 6:30 p.m. Dinner break.

(i) 8:00 p.m. More developing.

2) Day 2.

(a) 10:00 a.m. Logistics briefing & updates.

(b) 10:15 a.m. Begin developing.

(c) 12:00 p.m. Submission Deadline.

(d) 12:00 p.m. Lunch break.

(e) 1:30 p.m. Presentations.

(f) 3:00 p.m. Judges Voting.

(g) 3:30 p.m. Awards.

(h) 4:00 p.m. Post Event social.

s. Event Management Timeline (example only).

1) Five to Eight Weeks in advance of the Event:

(a) Ensure location page is completely up to date with all relevant information for participants.

(b) Confirm venue’s capacity and bandwidth are adequate.

(c) Begin outreach to developers to encourage registration and attendance.

(d) Reach out to local tech bloggers and ask them to post about the Event.

(e) Reach out to local subject matter experts about potentially attending the Event and to advise on any of the posted Events.

(f) Think about any security requirements at your host location (e.g., need for ID to get in).

2) Four Weeks in advance of the Event:

(a) Begin mainstream PR in coordination with NIST—send press releases to local media.

(b) Secure a local organizing team member, developer or subject matter expert to act as the emcee for the Event.

(c) Consider hosting a pre-Event meetup for participants to form teams and brainstorm about Events.

3) Two Weeks in advance of the Event:

(a) Confirm necessary A/V support.

(b) Confirm any VIP speakers or mentors that you plan to have attending, as well as any local scientists or experts who might be present to speak about the Events.

4) One Week in advance of the Event:

(a) Send out a confirmation email to all those registered for your location with start and end time of Event, location address, any security information and reception details.

(b) Confirm bandwidth availability (sufficient IP addresses, passwords, access points, etc.).

(c) Purchase any additional items needed (markers, paper, power strips, name tags, etc.).

5) Day before the Event:

(a) Download registration spreadsheet to use at check in.

(b) Confirm that space and A/V equipment have been properly set-up.

(c) Put up signage in appropriate locations.

6. Reviewing & Judging the Events/Contests

a. Provide the platform for NIST PSCR approved reviewers and judges to assess and evaluate the performance of events/contests participants.

b. Collect and organize information from NIST PSCR approved reviewers and judges, consolidating and preparing it for PSCR internal processing and action.

c. Ensuring that all reviewers and judges are compliant with NIST PSCR guidelines and rule, regarding NDAs, COIs, etc.

7. Processing awards for the Events/Contests

a. Provide the platform for NIST PSCR approved awardees to provide the appropriate information for processing awards for participation or performance as part of the events/contests.

8. Program Final Report: Upon completion of an event, the Contractor shall provide the Technical Point of Contact (TPOC) a report within 30 days that includes:

a. Description of the delivered solution.

b. Assessment of the lessons learned derived from the delivered solution.

c. Number of registered participants.

d. Number of unique competitors.

e. Number of submissions.

f. Number of award winners.

g. Value of awards.

h. Planned vs actual schedule duration.

i. Complete list of participant registration information.

j. America COMPETES Act reporting requirements summary.

V. DELIVERABLES

In this section, the deliverables required to be produced by the Contractor for each task are described. There will be opportunities to coordinate with PSCR staff, but the Contractor has the full responsibility to produce high quality and detailed deliverables which meet the requirements within the performance work statement.

1. Concept creation, vetting, and development

a. Concept briefing with PSCR Program Manager for review and approval.

b. Concept summary memo(s) (1.3)

2. Research to support the Contests

a. Research briefing with PSCR Program Manager for review and approval.

b. Contest summary memo(s)

3. Design and build the Contests

a. Complete contest rules which follow PSCR best practices and clear NIST legal review.

b. Insurance determination memo(s): This determination is designed to anticipate potential risks and ensure that participants are covered with the appropriate level of insurance to support any unforeseen costs caused by an accident or safety incident.

c. Paperwork Reduction Act Clearance / Review memo(s): Collecting information that pertains to people, places, or events as part of the prize or challenge, may require review under the provisions of the Paperwork Reduction Act.

d. Reviewer Selection memo(s): As part of the prize or challenge, it may be beneficial to include input from subject matter experts. Including this input requires that each individual be reviewed and approved by the Program Manager.

e. Judge Selection memo(s): All official judges are approved by the Director of NIST.

They are usually esteemed individuals with the academic and or professional qualifications necessary to make a determination on which contestants should be declared winners.

f. Communications & Engagement Plan: Plan that outlines the strategy required to engage potential participants and ensure the prize or challenge is full of qualified participants.

g. Appointment Letters to Judge(s): Once the official judges are approved, each will be notified via this letter.

4. Launch the Contest

a. Judges certificate/conflict of interest determination/Non-disclosure agreement.

1) This documentation ensures that, if they exist, conflicts of interest are discovered, and that there is time to work with the appropriate legal resources to mitigate or eliminate the conflict prior to the run stage of the prize of challenge.

b. Reviewer conflict of interest determination/Non-disclosure agreement.

1) This documentation ensures that, if they exist, conflicts of interest are discovered, and that there is time to work with the appropriate legal resources to mitigate or eliminate the conflict prior to the run stage of the prize of challenge.

c. Draft of NIST Challenge.gov Posting.

1) The Challenge.gov posting (CDGP) must be published either before the start date or on the same day as the start date of the prize competition or challenge; the notice cannot be published after the start date.

2) The CDGP must include:

(a) The subject of the competition;

(b) The rules for being eligible to participate in the competition;

(c) The process for participants to register for the competition;

(d) The amount of the prize; and

(e) The basis on which a winner will be selected.

d. Contest Fact Sheet.

5. Run the Events

a. Event Plan: The Contractor shall develop, present, and maintain throughout the period of performance a detailed Event Plan to include a work breakdown schedule, status meetings, briefings, and other management level information. In addition, the Contractor shall monitor the status of all tasks and deliverables, meet with the TPOC and/or designees at least monthly or as necessary to resolve problems, communicate status and present and discuss technical issues and approaches for the individual phases and stages of the Event.

1) The Contractor shall review and revise the Event Plan monthly with the TPOC.

2) The Contractor shall provide a schedule of strategy development sessions, in-progress reviews, develop reports, abstracts, posters and presentations of program results, as required to the TPOC.

3) The Contractor shall provide a list of conferences and recommendations for attendance to the TPOC.

4) The Contractor shall participate in periodic project status meetings at the request of the TPOC, or the Contracting Officer’s Representative (COR), or the Contracting Officer (CO), to discuss Event progress and issues.

5) The Contractor shall coordinate work through the Contracting Officers Representative (COR) when interacting with various Government agencies and the user community.

b. Event Progress Report: The Contractor shall provide weekly Event status updates to the TPOC to include data such as:

1) Current number of Community Participants.

2) Number of submissions.

3) Status of schedule milestones.

4) Geographic demographics.

5) Any significant activities or issues.

c. Quality Control Plan: The Contractor is responsible for using its own Quality Control Plan. The purpose of the Quality Control Plan during the contract performance is to ensure quality and consistency in all work performed and resulting deliverables. The plan shall address the approach and methods to assure all deliverables are accurate, in compliance with contract requirements, and must include actions to address and correct problems.

6. Reviewing & Judging the Event

a. Reviewer Instructions: Instructions to the reviewers to ensure they are appropriately supporting the contests.

b. Reviewer Comments: Complete summary of all reviewer comments collected in support of the contests.

c. Judge Instructions: Instructions to the judges to ensure they are appropriately considering selection criteria and adhering to the rules for the contests.

d. Judge Comments: Complete summary of all judge comments collected as part of the selection of contest winner(s).

e. Judge Determination Report.

1) The report is completed after the judge panel completes their independent evaluation and selection. It includes the following key information:

(a) Summary of how the judge panel and SME review process was implemented;

(b) The judge’s selection recommendations;

(c) If there is a dissenting opinion regarding a recommendation, at the request of a member of the judge panel, that dissenting opinion should be included in the DJR; and

(d) Supporting attachments.

7. Processing awards for the Event

a. Finalist Eligibility Verification.

1) Completed statement from each winning contestant, NIST will provide a form for this deliverable.

b. ACH Winner Payment.

1) Completed payment information from each winning contestant, NIST will provide a form for this deliverable.

8. Program Final Report: Upon completion of an Event, the Contractor shall provide the TPOC a report within 30 days that includes:

a. Description of the delivered solution.

b. Assessment of the lessons learned derived from the delivered solution.

c. Number of registered participants.

d. Number of unique competitors.

e. Number of submissions.

f. Number of award winners.

g. Value of awards.

h. Planned vs actual schedule duration.

i. Complete list of participant registration information.

j. America COMPETES Act reporting requirements summary

DELIVERABLES CHART

Task PWS

Refs.

Deliverable Format Due

1 IV.1

V.1

Concept briefing and summary memo

Electronic Completion of Task 1

2 IV.2

V.2

Concept briefing and summary memo

Electronic Completion of Task 2

3 IV.3

V.3

Memos, plans, and letters Electronic Completion of Task 3

4 IV.4

V.4

COIs, NDAs, CDGP Electronic Prior to state of Task 4

5 IV.5

V.5

Event Plan Event Event Progress Report Quality Control Report

Electronic Prior to state of Task 5 Weekly Prior to state of Task 5

6 IV.6

V.6

Instructions Comments Reports

Electronic Prior to state of Task 6 Prior to state of Task 6 Completion of Task 6

7 IV.7

V.7

NIST provided forms Electronic Completion of Task 7

8 IV.8

V.8

Final event report Electronic Within 30 days of event completion

VI. PERFORMANCE REQUIREMENT SUMMARY (PRS)

The TPOC will monitor, review, and determine the acceptability of the Contractor’s deliverables in accordance with the requirements included in the PRS and the information contained in the Quality Assurance Surveillance Plan (QASP), provided via separate attachment. The TPOC will determine acceptability of deliverables within three (3) days after receipt and provide notification to the Contractor of same within that period of time. Contractor deliverables determined unacceptable by the TPOC shall be corrected by the Contractor at no additional cost to the Government and within a timeframe to be determined by the TPOC. The TPOC will perform performance evaluations based on the requirements above and the Performance Standards set forth in the Performance Requirements Summary.

PRS TABLE

Task Performance

Indicators Performance

Standard Acceptable

Quality Level

(AQL)

Surveillance Method

Event Plan Initial plan presented IAW V.1. Update as necessary in conjunction with TPOC approval.

Provide plan NLT four (4) weeks after award. Attend monthly reviews. Keep current.

The plan must be current and written clearly, concisely, and cogently at all times.

The TPOC will review and approve the plan and all changes on an ongoing basis.

Event Progress Report

Provide timely, accurate data

IAW V.2.

Provide report at the first of every week.

Report data must be current, accurate, and complete upon presentation.

The TPOC will review and approve the report weekly.

Event Program Reviews

Support review

IAW V.3.

Provide relevant charts, tables, documents, and data necessary to discuss Event successes and probable course corrections.

Attendance is mandatory. All data to be presented will be 100% accurate.

The TPOC will review data accuracy and provide the Contractor a performance assessment to date.

Event Final Report

Present report

IAW V.4.

Provide report NLT thirty (30) days after Event completion.

The report shall be clear, accurate, and complete with substantively supported conclusions.

The TPOC will review and approve as well as provide the Contractor a final performance assessment.

VII. FUNCTIONAL TITLES/LABOR CATEGORY DESCRIPTIONS

The Contractor’s functional titles/labor categories shall crosswalk to the following:

Program Manager (Key Personnel): Full -Time Provide management and execution of all tasks in this requirement. The Program Manager must have full, autonomous authority to make and implement all decision critical to the success of the program. Experience with public safety and communications issues is preferred.

Program Support (Key Personnel): Full-Time Day-to-day execution of all tasks in this requirement. Experience with public safety and communications issues is preferred.

Junior Program Support: Full-Time Day-to-day execution support of all tasks in this requirement. Experience with public safety and communications issues is preferred.

VI. GOVERNMENT-FURNISHED PROPERTY, MATERIAL, EQUIPMENT, OR

INFORMATION (GFP, GFM, GFE, OR GFI): NIST PSCR will supply the Contractor with the necessary program information to complete assigned tasks.

VII. SECURITY

1. The solicitation and collection of personally or individually identifiable information shall be subject to the Contractor’s privacy and security policies. Personal identifiable information (PII) collected by the Contractor shall only be shared for competition winners and only with the NIST staff responsible for prize award processing.

2. Contractor web sites, platforms, and software shall operate independently of NIST and are, therefore, not subject to NIST IT Security requirements and review.

VIII. TRAVEL

1. Contractor personnel shall be required to travel. The Contractor shall be responsible for making its own arrangements for airline tickets, hotel and car rental reservations, arranging for passports and Visas if foreign travel is required, etc.

2. Travel performed shall be reimbursed in accordance with the Federal Travel Regulation.

3. All travel must be pre-authorized by the NIST Contracting Officer (CO) at least 30 days prior to a proposed trip for a given task order.

IX. OTHER UNIQUE REQUIREMENTS: The OIO launched under this agreement shall comply with legal requirements stipulated by NIST, such as eligibility and other guidelines included in 15 U.S.C. Section 3719 (Public Law Number 114-329).

X. PLACE OF PERFORMANCE: Work will be performed primarily offsite but implemented through the NIST PSCR Innovation Accelerator, Open Innovation Program located in Boulder, CO.

IX. PERIOD OF PERFORMANCE

Nineteen (19) months from date of award.

http://gsa.gov/portal/content/104790

X. PERSONNEL

Contracting Officer Representative (COR):

Name: Jim Harriman Phone: 303-497-5312 Email: james.harriman@nist.gov

Technical Point of Contact (TPOC):

Name: Craig Connelly Phone: 303-497-5968 Email: craig.connelly@nist.gov

XI. ATTACHMENTS

1. Quality Assurance Surveillance Plan