Attachment 3 - Mock TO3 PWS - NICE.pdf

National Initiative for Cybersecurity Education (NICE) Support Services CAPSS Sample TO 3 Performance Work Statement

1.0 Background

The National Initiative for Cybersecurity Education (NICE) is an initiative that enhances the overall cybersecurity posture of the United States by accelerating the availability of educational and training resources designed to improve the cybersecurity skills and knowledge of our nation’s learners and workforce. The National Institute of Standards and Technology (NIST) is leading the NICE initiative working from the strengths and energy of more than 20 federal departments and agencies and leveraging each of their relationships with academia and industry sectors to ensure coordination, cooperation, focus, public engagement, technology transfer, and sustainability.

NIST will highlight these activities, engage with various stakeholder groups, and create forums for sharing information and leveraging best practices.

2.0 Objectives

NICE is seeking to increase its visibility and impact through a variety of initiatives designed to improve communication and engagement with academia, industry, and government. In addition to professional staff, NICE will require the support of a contractor who can assist in fulfilling various tasks that are designed to help carry out strategic directions. The services outline in this task order are designed to identify priority needs for programmatic and technical services.

3.0 Scope

The Contractor shall provide support to the NICE Community Coordinating Council and subgroups, coordinate and publish the NICE eNewsletter, create NICE branding and promotional materials, facilitate updates to the NICE website, and support administrative functions of NICE webinars. The Contractor shall also support a virtual Workshop with an option for in-person support. Contractor personnel shall also attend periodic meetings virtually with NIST staff.

This is a Hybrid, Firm-Fixed Price (FFP)/Labor Hour type task order.

4.0 Base Tasks

4.1 CLIN 0001: Support NICE Community Coordinating Council Support Services (FFP)

To support the engagements between government, industry, and academia, NICE has established a Community Coordinating Council that includes working groups, communities of interest, and project teams to help facilitate collaboration and coordinate actions related to its strategic directions. The contractor shall provide the following services to facilitate and support the effective operation of the NICE Community:

• Take meeting minutes during monthly community meetings

• Track monthly membership metrics

• Maintain Community collaboration sites by updating and adding necessary documents and materials on the collaboration sites. The collaboration sites include two google group shared drives and the four groups mailing listservs. The contractors shall upload meeting minutes to the respective folders of these google groups. There will be 5 working group meetings and 1 monthly community meeting, a total of 6 meeting minutes uploads per month. For the group mailing listservs, the contractors shall moderate e-mails for spam and malicious content. The contractor shall reach out to the NICE program office if any issues raise or to suggest new steps and/or processes that may improve business operations

4.2 CLIN 0002: Publish the NICE eNewsletter (FFP)

One of the operational goals for NICE is to increase the visibility of the program across the Nation. One of the strategies to increase visibility and enhance awareness of cybersecurity education and workforce development activities is the dissemination of an eNewsletter created and distributed quarterly.

• The Contractor shall facilitate the collection and formatting of input into a provided eNewsletter template

• The Contractor shall establish timelines for on-time delivery of eNewsletters

• The Contractor shall support an online delivery mechanism for four (4) quarterly electronic newsletters

• The Contractor shall add eNewsletter content on the NICE website

• The Contractor shall develop and collect metrics regarding eNewsletter impact on a quarterly basis

4.3 CLIN 0003: Creation of NICE Branding & Promotional Materials (FFP)

NICE seeks to re-brand its program to increase its visibility in its variety of target stakeholder groups. The design and creation of materials that promote its brand and the affiliated programs or funded projects will assist NICE in the transition to re-brand. Materials developed shall include print and web based.

For this task:

• The contractor shall develop at least 10 graphics and infographics

• The contractor shall provide three options for graphical templates for one-pagers in Adobe format (PDF, InDesign)

The contractor shall develop a PowerPoint presentation template that can be used on a revolving basis by NICE staff.

4.4 CLIN 0004: Content Support for NICE Website (Labor Hour)

The NICE website provides timely announcements on news and events and other information relevant to cybersecurity education, training, and workforce development. The content needs to be maintained with current news and events, supported to include new resources, and evaluated to determine its effectiveness as a communication tool.

• Contractor shall update News and Events to website as needed and at minimum bi-weekly

• Contractor shall add new Resources to website as they become available and at minimum once per month

• Contractor shall develop metrics regarding the impact of the online presence

4.5 CLIN 0005: Administrative Support for NICE Webinars (FFP)

Another mechanism for increasing NICE's visibility and maintaining professional connections with the community throughout the task order period of performance is through the NICE Webinar Series that provides program highlights and spotlights new initiatives. The NICE staff will provide content expertise but will require logistical support.

• Contractor shall coordinate with speakers to schedule rehearsal meetings

• Contractor shall coordinate with speakers to obtain photos, biographies, and presentation slides and shall compile slides into a single presentation

• Contractor shall upload and test webinar presentations and links to the webinar platform

• Contractor shall support online delivery mechanism for bi-monthly webinar announcements

4.6 CLIN 0006: Workshop Support (FFP)

Each of these tasks consists of informal writing (e.g., emails) and discussions, as well as deliverables and support as described in each subtask. Each subtask describes the anticipated level of effort and deliverables.

4.6.1 Workshop Planning

This task includes all phases of pre-workshop planning and coordination for one (1) virtual workshop including support for planning, agenda development, opening remarks development, Plenary or Keynote coordination and development, coordination with speakers, facilitators, scribes and pre-workshop planning and support. It is envisioned that this workshop will be structured as a 2- to 3-day workshop with five (5) breakout sessions.

4.6.2 Workshop Preparation and Facilitation

The workshop shall have five breakout sessions which will require facilitation. To accomplish this:

• The Contractor shall supply five expert facilitators to facilitate the breakout sessions at each workshop;

• The Contractor shall schedule a 90-minute preparation session before the workshop to include the workshop coordinator, facilitators, scribes and NIST representatives;

• The Contractor shall draft instructions and prep materials for facilitators in the form of a PowerPoint deck (not to exceed 20 slides). The PowerPoint deck shall include at least 50% content from other resources and support a preparation session;

• The Contractor shall prepare a reference content PowerPoint deck for facilitators to use during the breakout sessions (not to exceed 20 slides). The PowerPoint deck shall include up to 80% content from other resources;

• The Contractor shall hold a post-workshop debriefing session (Hotwash) at the end of each workshop day with the coordinator, facilitators, and scribes in order to collect key observations (not to exceed 1 hour per day);

4.6.3 Workshop Support

The contractor shall provide services to support the breakout sessions at this workshop. The contractor shall provide five scribes to support each of the breakout session). The contractor shall attend the preparation session, the post-workshop debriefing session, take notes, and to edit their notes after the workshop. One of these five scribes shall also take notes during any non-breakout sessions (e.g., introductory/closing remarks, plenaries/keynotes, etc.) and edit these after the workshop. In addition, the Contractor shall supply support for coordination of all of the day’s activities.

4.7 CLIN 0007: Program Management & Reporting (Firm-Fixed Price)

4.7.1 Integrated Project Work Plan

All work to be accomplished under this task order shall be managed through an Integrated Project Work Plan (IPWP). The IPWP is due to NIST for review at least 2 days before the Kick-off meeting. NIST will approve the IPWP or provide comments for revision within three (3) business days of delivery.

The IPWP must be reported on monthly and sent to the project stakeholders, to include the Government Contracting Officer’s Representative (COR), Technical Lead and Project Sponsor (optional), as well as the contractor’s Task Order Manager and Key Personnel (optional) at least 3 days prior to the monthly status meeting. The IPWP shall contain Government dependencies highlighted in yellow. Updates to the plan that do not impact the critical path can be resolved at the monthly status meeting as a function of the project plan. Changes that extend the period of performance or impact product delivery (i.e., removing PWS defined deliverables or adding new deliverables) will be addressed only through mutually agreed upon contract modification action executed by the Contracting Officer.

4.7.2 Kick-off Meeting

The contractor shall attend one kick-off meeting on-site at NIST Gaithersburg, or virtually while restrictions are in place, no later than 10 business days after award of the task order. The kick-off meeting shall be utilized to introduce all members of the contractor’s team, review all task order requirements and deliverables, review the initial IPWP provided by the contractor, evaluate the contractor critical path analysis, and discuss the contractor’s proposed approach. The contractor’s key personnel shall be present at the kick-off meeting.

4.7.3 Monthly status and reporting

The Contractor shall attend monthly program status meetings (tentatively to be held on the 3rd Wednesday of each month) on-site at NIST Gaithersburg, or virtually while restrictions are in place, and provide a detailed status of the IPWP to include task percent complete metrics, burn rate (both current and projected), Cost Performance Index (CPI), and critical path analysis. The burn rate analysis and CPI shall only be determined for the labor hour task. The Contractor shall provide written impact statements for any event or circumstance that could impact the cost, schedule of project, or quality of the project work. Impact statements are due no later than 1 week after the determination of the impact. If during the program status meeting the Government determines it is necessary to conduct a status meeting with a large contingent of stakeholders (i.e., project sponsors, technical leads, etc.), the government will schedule it with at least 5 business days’ notice, and the Contractor shall present the status of the project and recommendations from the written impact statement(s).

Figure 1: Government Work Break Down Structure (WBS)

5.0 Deliverables, Due Dates, and Performance Requirements Summary (PRS)

All deliverables shall be posted to NIST’s shared drive or via another secure method (i.e., PGP files via email for proprietary information) as identified by the Technical Lead or the COR. Deliverables will be evaluated by the COR and the Technical Lead for completeness and the COR will either accept or reject the deliverables within 10 calendar days of contractor submission. All deliverables shall be provided to the COR.

Task Area #4 -

NICE

4.1 Support NICE Community Coordinating Council Support Services

4.2 Publish NICE eNewsletter

4.3 Creation of NICE Branding & Promotional Materials

4.4 Content Support for NICE Website

4.5 Admini-strative Support for NICE Webinars

4.6 Workshop Support

4.7 Program Management & Reporting

Deliverable & Task

Description Projected

Completion Date

Media / Quantity / Performance Standard

Monitoring Method

Base Tasks

D1 / 4.1 Meeting minutes during Community meetings

Monthly

• MS Word

• A logical, easy-to-read schedule that takes key personnel’s schedules into account

• Professional quality and free of typographical errors

• Minutes shall include all action items discussed

Tech Lead and COR review

D2 / 4.1 Meeting minutes during 5 working group meetings

Monthly

• MS Word

• A logical, easy-to-read schedule that takes key personnel’s schedules into account

• Professional quality and free of typographical errors

• Minutes shall include all action items discussed

D3 / 4.1

Monthly membership metrics

Monthly

• MS PowerPoint

• Logical, easy-to-read metrics that are complete and accurate

Tech Lead and COR review

D4 / 4.1

Maintained collaboration site for Community

Monthly

• Google Groups / Google Folders

• The collaboration site must be usable by government employees using government equipment. This potentially includes Department of Defense and NSA computers

Tech Lead and COR review

D5 / 4.2 Delivered eNewsletters Quarterly

• GovDelivery

• Professional quality, easy-to-read, complete, accurate, and free of typographical errors

Tech Lead and COR review

D6 / 4.2 Collected and formatted input in a provided eNewsletter template

As per IPWP

• MS Word / GovDelivery

• Expected length 5-8 pages

• Professional quality, easy-to-read, logical flow of content, and free of typographical errors

• Graphics and layout should be in industry standard file formats, but proofs should be compatible with MS Word/GovDelivery

Tech Lead and COR review

& Task

Description Projected

Completion Date

Media / Quantity / Performance Standard

Monitoring Method

D7 / 4.2 Final content for eNewsletter Quarterly

• MS Word / GovDelivery

• Expected length 5-8 pages

• Professional quality, easy-to-read, logical flow of content, and free of typographical errors

• Graphics and layout should be in industry standard file formats, but proofs should be compatible with MS Word/GovDelivery

Tech Lead and COR review

D8 / 4.2 Content added to NICE website

Quarterly

• Drupal

• Professional quality, easy-to-read, logical flow of content, and free of typographical errors

Tech Lead and COR review

D9 / 4.2 eNewsletter delivery timeline As per IPWP

• MS Word / MS Excel / MS PowerPoint

• Professional quality, easy-to-read, complete, accurate, and free of typographical errors

• Shall take NIST input into consideration

Tech Lead and COR review

D10 / 4.2 Developed and collected metrics regarding eNewsletter impact

Quarterly

• MS Work / MS PowerPoint

• Professional quality, easy-to-read, complete, and free of typographical errors

• Accuracy of metrics shall be defensible

• Shall take NIST input into consideration

Tech Lead and COR review

D11 / 4.3

Developed quality graphics in industry-standard file formats

As per IPWP • A copy of source files shall be delivered to the COR

• Final graphics shall also be provided in .eps, .png, or similar

• Professional quality graphics in industry-standard file formats

Tech Lead and COR review

D12 / 4.3

Developed one-pager templates in industry-standard file formats

As per IPWP • .PDF, Adobe InDesign, Illustrator, or similar

• Professional quality graphics in industry-standard file formats

Tech Lead and COR review

D13 / 4.3 Developed presentation templates in industry-standard file formats

As per IPWP • MS PowerPoint

• Professional quality graphics

Tech Lead

& Task

Description Projected

Completion Date

Media / Quantity / Performance Standard

Monitoring Method

D14 / 4.4 News and Events updated to website

Ongoing

• Drupal

• Professional quality, easy-to-read, complete, accurate, and free of typographical errors and broken web links

Tech Lead and COR review

D15 / 4.4 Resources added to website Ongoing

• Drupal

• Professional quality, easy-to-read, complete, accurate, and free of typographical errors and broken web links

Tech Lead and COR review

D16 / 4.4 Report metrics on impact of NICE web and social media presence

As per IPWP

• MS Word / MS PowerPoint

• Professional quality, easy-to-read, complete, accurate, and free of typographical errors

• Accuracy of metrics should be defensible

• All graphics shall be easy to read and understand.

Tech Lead and COR review

D17 / 4.5 Evidence of coordination with speakers to schedule rehearsal meetings

Monthly

• MS Outlook

• A logical, easy-to-read schedule that takes key personnel’s schedules into account

Tech Lead and COR review

D18 / 4.5

Evidence of speaker materials obtained (photos, biographies, and presentation slides) and compiled slides in a single presentation

Monthly

• MS Word / MS PowerPoint

• Professional quality, easy-to-read, complete, accurate, and free of typographical errors and broken web links

Tech Lead and COR review

D19 / 4.5 Webinar presentations and links uploaded to webinar platform

Monthly

• Webinar platform must be usable by any government computer despite configurations

• Webinar platform must be free to end users

• Professional quality, easy-to-read, complete, accurate, and free of typographical errors

D20 / 4.5 Webinar presentations and links tested in webinar platform

Monthly

• Webinar platform must be usable by any government computer despite configurations

• Webinar platform must be free to end users

Tech Lead

& Task

Description Projected

Completion Date

Media / Quantity / Performance Standard

Monitoring Method

• Professional quality, easy-to-read, complete, accurate, and free of typographical errors

D21 / 4.5 Electronic announcements delivered

Bi-monthly

• GovDelivery

• Professional quality, easy-to-read, complete, accurate, and free of typographical errors and broken web links

Tech Lead and COR review

D22 / 4.6.1

Evidence of Workshop Planning (planning, agenda development, opening remarks development, Plenary / Keynote coordination & development, coordination with speakers, facilitators, scribes and pre-workshop planning and support for a 2–3-day workshop with an estimated 5 breakout sessions)

As per IPWP

• 10 pages once – MS Word

• 1 30-row worksheet once – MS Excel

• NTE 20 slides – MS PowerPoint

• MS Outlook

• Professional quality, easy-to-read, complete, accurate, and free of typographical errors

Tech Lead and COR review

D23 / 4.6.2 Evidence of Workshop Preparation & Facilitation final materials

No later than 1 week before the workshop begins

• 10 pages once – MS Word

• 1 30-row worksheet once – MS Excel

• NTE 20 slides – MS PowerPoint

• All materials are for public consumption and shall be of professional quality, easy-to-read, complete, accurate, and free of typographical errors

Tech Lead and COR review

D24 / 4.6.3 Evidence of Workshop Support

As per IPWP

• MS Outlook

• Emails from Contractor PM confirming identity of support personnel (confirmation of personnel assisting with overall coordination)

D25 / 4.6.3

Workshop session notes (plenary, keynote, all speakers, and all breakout sessions)

As per IPWP

• Expected length 50 pages – MS Word

• Professional quality, easy-to-read, complete, accurate, and free of typographical errors

Tech Lead and COR review

D26 / 4.7.1 Integrated Project Work Plan

(IPWP)

2 days prior to Kick-off meeting

• MS Project or similar

• The IPWP will be delivered no later than 2 business days before the Kick-off meeting

• IPWP shall include an identification of contractor resources, deliverables and

Tech Lead

& Task

Description Projected

Completion Date

Media / Quantity / Performance Standard

Monitoring Method completion dates, sequence of events, start dates, and duration for each activity

• IPWP will be available in electronic format

D27 / 4.7.2 Kick-off Meeting materials Within 10 business days of award

• MS Word / Project / PowerPoint

• The Kick-off meeting shall be no later than 10 business days after of the task order

• Electronic copy of the agenda should be delivered to the COR at least 2 business days before the meeting

• The kick-off meeting shall be utilized to introduce all members of the contractor’s team, review all task order requirements and deliverables, review the IPWP, evaluate the contractor critical path analysis, and discuss the contractor’s proposed approach

Tech Lead and COR review

D28 / 4.7.3 Monthly Updates Monthly

• MS Word / Project / PowerPoint

• Monthly updates shall be submitted to the COR before each monthly meeting

• Reports shall be legible and of a professional quality

• Any problems with the work, current or anticipated, should be clearly reported

Tech Lead

6.0 Government-Furnished Property, Material, Equipment, or Information (GFP, GFM, GFE, or GFI)

Government-furnished property (materials, equipment, and/or information) will be provided in conjunction with required performance under this task order. All work that is performed as a part of this effort will be conducted on government furnished equipment, except for workshop support by Facilitators. All GFE will be utilized and maintained in accordance with NIST IT Security Rules.

7.0 Key Personnel Minimum Qualifications

The Contractor shall provide program management and subject matter expertise on a key personnel basis. Contractor Key Personnel shall meet the minimum qualifications identified below. The quantity of key personnel required to address these minimum qualifications may be proposed by the Contractor for Government consideration. The titles of the labor categories given below are not mandatory, except for the Program Manager 2. That labor category is mandatory. The other labor categories are simply examples of titles suitable to the type of work to be performed by the respective key personnel positions. However, all minimum qualifications listed for each position below must be met by the contractor’s respective key personnel. Additionally, all proposed key personnel must meet the minimum qualifications detailed in the IDIQ contract for the labor category the candidate is proposed under.

Program Manager 2 – Task Order Level

Minimum/General Experience: This position requires a minimum of 6 years’ general project management experience and 3 years IT experience in computer security. Experience includes increasing responsibilities in information systems design and management.

Functional Responsibilities: Duties may include but are not limited to: Serves as project manager for a large, complex task order and shall assist the Program Manager in working with the ordering activity Contracting Officer (CO), the Federal Acquisitions Contract – Project/Program Manager (FAC-P/PM), the contract-level Contracting Officer’s Representative (COR), and the task order-level COR(s), ordering activity management personnel and customer agency representatives. The Project Manager is responsible for the overall management of the specific task order(s) and ensuring that the technical solutions and schedules in the task order are implemented in a timely manner. Performs enterprise wide horizontal integration planning and interfaces to other functional systems.

Minimum Education: Must either be certified as a.) Project Management Professional (PMP) by the Project Management Institute (PMI) or other such credentialing organization, or b.) Have been or currently are certified as a FAC- Program/Project Manager (P/PM) (Mid or Senior level). A Defense Systems Management College (DSMC) Program Management (PM) certification of Level 2 or 3 will be considered equivalent to a FAC-P/PM Mid or Senior Level. A Bachelor’s degree in computer science/engineering technology, software/programming, or mathematics can be substituted for 2 years’ general experience and 2 years IT experience. A PhD or Master’s Degree (in subjects described above) can be substituted for 3 years IT experience. A Master’s Degree in Project Management can be substituted for 3 years’ project management experience under this task order.

Communications Specialist 2

This Key Personnel shall work on the core work (D1-29), as well as be the Workshop Coordinator.

Minimum/General Experience: This position requires a minimum of 6 years of general communications experience of which at least 3 must be specialized experience that includes working in communications dealing with scientific and/or technical topics.

Functional Responsibilities: Duties to include, but not be limited to: With limited supervision, assists with the design and development of a wide variety of multimedia products using computers, production equipment, and software. Includes, but not limited to development of web pages, videos, models, graphics, etc. Writes, edits, creates layouts for publications, information displays, video scripts, internal/external websites, social media, and multimedia presentations. Promotes content standards and consistency across websites, social media, and/or content management systems. Works with technical staff to ensure content supports agency goals. Assists with preparing responses to public input on various topics.

Minimum Education: A Bachelor's degree in computer science/systems, information systems/technology, engineering/engineering technology, software engineering/ programming, management, natural sciences, social sciences, mathematics, or communications. A Master’s Degree (in subjects described above) may be substituted for 2 years' general experience. A PhD (in subjects described above) may be substituted for 5 years of general experience. OR no degree and 10 years of general experience of which at least 3 years must be specialized experience.

8.0 Risk Level

This Task Order is a low-risk Task Order with low IT risk.

9.0 Place of Performance

The primary place of performance shall be the Contractor’s site or remote work location. All work shall be performed virtually until COVID-19 restrictions have been lifted from NIST’s Gaithersburg campus.

When those restrictions are lifted, a percentage of the work will occur on campus. This percentage will be determined by the COR and Tech Lead based on the needs of the program at that time.

For estimation purposes, the Optional CLINs should be estimated as if the workshop will be held at Stanford University.

10.0 Period of Performance

This Task Order shall have a period of performance of 12 months from date of award.