Attachment _1 PWS 89233124FNA400XXX FY24 Rebid.docx

Performance Work Statement for U.S Department of Energy, National Nuclear Security Administration (DOE/NNSA) Database Development and Support Services to the Office of Nuclear Incident Response (NA-84) and Office of Nuclear Forensics (NA-83)

1.0 Introduction

The Department of Energy (DOE), National Nuclear Security Administration’s (NNSA), Office of Counterterrorism and Counterproliferation (NA-80) administers and directs DOE/NNSA nuclear incident response capability to ensure availability and viability to respond to nuclear incidents at DOE and NNSA facilities and field sites, and to nuclear and radiological emergencies within the United States and abroad. To support this capability, NA-80: conducts operational planning and training to counter both domestic and international terrorism; develops and implements assessment, education, and protection strategies to mitigate potential nuclear terrorism threats; and serves as the primary point of contact for nuclear incident response activities.

2.0 Scope

The Office of Nuclear Incident Response (NA-84) and Office of Nuclear Forensics , in the form of the Nuclear Emergency Support Team (NEST) to which they provide all constituent parts, are responsible for preparing for and responding to nuclear and radiological incidents and attributing the origin of an incident on behalf of the U.S. Government and have an information management system, the Asset Readiness Management System (ARMS), to support these requirements. ARMS tracks operational and exercise planning and execution and provides readiness reporting of equipment maintenance and personnel training. The office has also integrated data management capabilities with the RadResponder network, a platform sponsored by the Federal Emergency Management Agency (FEMA) as a Whole Community solution for the management of radiological data. This requirement provides continuous technical development of and support to these key systems, to include training, documentation, and general user support. General software design and support may also be requested. Specific support required is detailed below:

Task 3.1: ARMS Design/Development and Support

The contractor shall provide, at client direction, software development and associated services in support of NEST’s Asset Readiness Management System (ARMS) and any comparable system that evolves from the existing ARMS during development projects.

ARMS is a browser-based management system hosted within and accessed through NA-84’s cloud hosting service. Physically, the system consists of an ASP.NET web site hosted within MS IIS on top of a SQL Server database. Additional components include web services, reports (SQL Server Reporting Services and Crystal Reports), mapping utilities, email notifications, and mobile tools (Windows CE based devices with onboard barcode scanners). ARMS is used throughout NEST, both by NA-84 and NA-83 employees as well as by contractors. Users are physically located at DOE headquarters in Washington D.C. And throughout the DOE and NNSA site and laboratory complex.

ARMS is used to both manage a wide variety of data as well as to perform numerous functions including:

· Central repository of all NA-84 and NA-83 emergency response personnel and equipment requirements and records

· Personnel training records

· Personnel medical qualification records

· Equipment maintenance records

· Master list of program and team readiness requirements

· Budgetary information (proposed and actuals)

· Deployment scheduling and watch lists

· Event planning information

· Lessons learned

· Electronic position taskbook (in development)

· Functions and features

· Real time readiness calculations

· Predictive readiness alerts; e.g. training and maintenance notifications

· Daily, reportable historical readiness history

· Deployment management utilities, including a deployment notification system

· Provides a wide variety of reports and automatic notifications and alerts in support of exercise planning, readiness, and deployment management.

As ARMS is a large system, specific requirements will be developed in concert with and under the supervision of the designated NA-84 technical point of contact. This POC will be an NA-84 employee. Technical requirements may be developed and coordinated by a contractor. All requirements will be authorized by the technical POC prior to development. All technical tasks and resulting deliverables will be individually defined and scheduled. Consequently, as individual requirements are defined in response to specific needs it is not possible to fully delineate particular deliverables in the context of this statement of work. However, please see Appendix 2 – Proposed ARMS Technical Deliverables for a list of potential projects. Given that there is a great deal of overlap between specific tasks within the major projects described throughout this document (i.e. ARMS, RadResponder, etc.), please see Appendix 1 – Common Development for detailed descriptions of what the following tasks entail:

· Task 3.1.1 ARMS Project Management

· Task 3.1.2 ARMS Software Design

· Task 3.1.3 ARMS Software Development

· Task 3.1.4 ARMS Software Training Material Production

· Task 3.1.5. ARMS Software Training

· Task 3.1.6 ARMS Operational Support/Help Desk

· Task 3.1.7 ARMS Software Documentation

Task 3.2: RadResponder Design/Development and Support The contractor shall provide, at client direction, software development and associated services in support of NEST’s requirements for radiological data acquisition using RadResponder

As RadResponder is a large system and shall interface with databases maintained by NA-84 and NA-83 through the Read/Write API, specific requirements will be developed in concert with and under the supervision of the designated NA-84 technical point of contact. This POC will be an NA-84 employee. Technical requirements may be developed and coordinated by a contractor. All requirements will be authorized by the technical POC prior to development. All technical tasks and resulting deliverables will be individually defined and scheduled. Consequently, as individual requirements are defined in response to specific needs it is not possible to fully delineate particular deliverables in the context of this statement of work.

Given that there is a great deal of overlap between specific activities within the major projects described throughout this document (i.e. ARMS, RadResponder), please see Appendix 1 – Common Development for detailed descriptions of the following activities:

· Task 3.2.1 RadResponder Integration Project Management

· Task 3.2.2 RadResponder Integration Software Design

· Task 3.2.3 RadResponder Integration Software Development

· Task 3.2.4 RadResponder Integration Software Training Material Production

· Task 3.2.5 RadResponder Integration Software Training

· Task 3.2.6 RadResponder Integration Operational Support/Help Desk

· Task 3.2.7 RadResponder Integration Software Documentation

Task 3.3: General Software Design/Development and Support

The contractor shall provide, at client direction, software development and associated services in support of any other projects requested by the client. Historically, these may be specialized modules or extensions created for existing projects (e.g. ARMS or RadResponder), integration efforts (e.g. VSP, TurboFRMAC, NARAC, DFM tablets etc.), technical and design consulting (e.g. ICLN, CRCPD, etc.), or standalone systems or utilities (e.g. NNSA Response Data portal, etc.). Projects of this nature often are managed through the NA-84 Capability Assurance Program’s technology development process, but may be initiated for any reason.

As systems of this nature tend to be ad hoc and/or developed quickly in response to immediate needs, specific requirements will be developed in concert with and under the supervision of the designated NA-84 technical point of contact. This POC may be an NA-84 employee or a contractor. All requirements will be documented and authorized by the technical POC prior to development. All technical tasks and resulting deliverables will be individually defined and scheduled.

Given that there is a great deal of overlap between specific activities within the major projects described throughout this document (i.e. ARMS and RadResponder), please see Appendix 1 – Common Development for detailed descriptions of the activities.

89233124FNA400XXX Attachment #1

3.0 Tasks

The contractor shall perform the tasks listed in the table below.

Task 3.1: ARMS Design/Development and Support

Task 3.1.1 Project Management

Or within 1 week after request

Monthly, or as requested Face to Face, Telephone, Webinar

Or within 1 week after request

Quarterly, or as requested Electronic Document

Or within 1 week after request

Quarterly, or as requested Electronic Document

Deployments

Task 3.1.2 Software Design

Task 3.1.3 Software Development:

· Creation of database components (tables, views, procedures, functions, etc.).

· Creation of browser based user interfaces and controls.

· Creation of mobile based[endnoteRef:1] user interfaces and controls. [1: Mobile user interfaces may include iOS, Android, and Windows based code and devices, and any other equivalent devices that become commercially available.]

· Creation of reports and other business intelligence components.

· Creation of notifications components such as: emails; faxes; pager messages; social network notifications; and SMS (text) notifications.

· Integration with companion tools, technologies, systems, and peripheral devices and hardware as required.

· Creation of integration components including APIs[endnoteRef:2] and SDKs[endnoteRef:3]. [2: API: Application Programming Interface; procedures and methods used by other developers to integrate with a system. Typically expressed as WebServices, FTP based processes, stored procedures, or standard data exchange formats such as text files, excel, XML, or EDI.] [3: SDK: Software Development Kit; more robust components and tools which can be used by other developers when integrating with or extending another system or platform. Typically expressed as dll’s (dynamic link libraries) or class files (e.g. java or C#) that are directly incorporated into other code projects.]

Software Change

· Perform quality assurance and quality control (i.e. unit and regression testing)

Report

Task 3.1.4 Software Training Material Production:

Software Training Materials

· PowerPoint’s and other briefing materials

· Distributable job aids

· Flyers and posters

· Videos

· Recorded webinars

Task 3.1.5 Software Training

Software Training for ARMS users:

· Hosting of online webinars

· Leading in-person training classes

· Provide on-site just-in-time training during exercise and responses

Task 3.1.6 Operational Support/Help Desk

Diagnosis

· System will be available when needed

Task 3.1.7 Software Documentation

· Database schema documentation

· Non-Proprietary source code

· API and SDK documentation

· Change logs (i.e. deployment and configuration management documentation)

· System administrator documentation

· Server administration documentation Documentation Source Code Logs

Task 3.2: RadResponder Integration Design/Development and Support

Task 3.2.1 Project Management

Or within 1 week of request

Or within 1 week of request

Or within 1 week of request

Deployment

· Certify quality assurance and quality control prior to and after deployment

Task 3.2.2 Software Design

· Participate in discussions with NA-84 staff members, associated contract staff, and other interested parties (e.g. other government agencies).

· Assist in development of technical requirements.

Requirements Reports

· Assist in development of performance and “return on investment” metrics to support the post-deployment success.

· Conduct and report upon research into technologies, tools, and methods.

Task 3.2.3 Software Development

· Creation of database components (tables, views, procedures, functions, etc.).

· Creation of browser based user interfaces and controls.

· Creation of mobile based[endnoteRef:4] user interfaces and controls. [4: Mobile user interfaces may include iOS, Android, and Windows based code and devices, and any other equivalent devices that become commercially available.]

· Creation of reports and other business intelligence components.

· Creation of notifications components such as: emails; faxes; pager messages; social network notifications; and SMS (text) notifications.

· Integration with companion tools, technologies, systems, and peripheral devices and hardware as required.

· Creation of integration components including APIs[endnoteRef:5] and SDKs[endnoteRef:6]. [5: API: Application Programming Interface; procedures and methods used by other developers to integrate with a system. Typically expressed as WebServices, FTP based processes, stored procedures, or standard data exchange formats such as text files, excel, XML, or EDI.] [6: SDK: Software Development Kit; more robust components and tools which can be used by other developers when integrating with or extending another system or platform. Typically expressed as dll’s (dynamic link libraries) or class files (e.g. java or C#) that are directly incorporated into other code projects.]

Task 3.2.4 Software Training

Task 3.2.5 Operational Support/Help Desk

Diagnosis

Task 3.2.7 Software Documentation

· Database schema documentation

· Non-Proprietary source code

· API and SDK documentation

· Change logs (i.e. deployment and configuration management documentation)

· System administrator documentation

· Server administration documentation Documentation Source Code Logs

Task 3.3: General Software Design/ Development and Support

Task 3.3.1 Project Management

Or within 1 week after request Monthly, or As requested

Or within 1 week after request

Or within 1 week after request

Deployments

Task 3.3.2 Software Design

Reports

· Conduct and report upon research into technologies, tools, and methods.

Task 3.3.3 Software Development

· Creation of database components (tables, views, procedures, functions, etc.).

· Creation of browser based user interfaces and controls.

· Creation of mobile based[endnoteRef:7] user interfaces and controls. [7: Mobile user interfaces may include iOS, Android, and Windows based code and devices, and any other equivalent devices that become commercially available.]

· Creation of reports and other business intelligence components.

· Creation of notifications components such as: emails; faxes; pager messages; social network notifications; and SMS (text) notifications.

· Integration with companion tools, technologies, systems, and peripheral devices and hardware as required.

· Creation of integration components including APIs[endnoteRef:8] and SDKs[endnoteRef:9]. [8: API: Application Programming Interface; procedures and methods used by other developers to integrate with a system. Typically expressed as WebServices, FTP based processes, stored procedures, or standard data exchange formats such as text files, excel, XML, or EDI.] [9: SDK: Software Development Kit; more robust components and tools which can be used by other developers when integrating with or extending another system or platform. Typically expressed as dll’s (dynamic link libraries) or class files (e.g. java or C#) that are directly incorporated into other code projects.]

· Perform quality assurance and quality control (i.e. unit and regression testing)

Task 3.3.4 Software Training Material Production

Software Training Materials:

· PowerPoint’s and other briefing materials

· Distributable job aids

· Flyers and posters

· Videos

· Recorded webinars

Task 3.3.5 Software Training

Training to ARMS users:

· Hosting of online webinars

· Leading in person training classes

· Provide on-site just-in-time training during exercise and responses

Task 3.3.6 Operational Support/Help Desk

Diagnosis See Section 4.0

As directed

· System will be available when needed

As directed

Task 3.3.7 Software Documentation

· Database schema documentation

· Non-Proprietary source code

· API and SDK documentation

· Change logs (i.e. deployment and configuration management documentation)

· System administrator documentation

· Server administration documentation Documentation Source Code Logs

4.0 Performance Based Objectives, Measures and Expectations

Contractor performance shall be evaluated on the following performance criteria at the conclusion of the contract: performance schedule, management performance, technical performance, product quality, and cost control. The contractor will be evaluated on the following performance-based objectives, measures, and expectations that are directly associated with the work described in Section 3.0. Standards delineated in Section 3.0 take shall be used instead of these (when provided).

Responsive Contractor responds to requirements in a professional timely manner

Subjective measurement by COR and Client

Observation

Positive Performance Evaluation

Technical Documentation and Analysis:

Security

Observation and inspection

Positive Performance Evaluation

Budget/Project Schedules (Pert, Gantt) Timeliness Accuracy Deliverable due date 100% accuracy

Deliverable due date

Accuracy Deliverable due date 100% accuracy

Accuracy Deliverable due date 100% accuracy

5.0 Security Requirements

Contractor personnel working on this task will not require clearances. The required work will be performed at an unclassified level.

6.0 Period of Performance

The Period of Performance will be a one-year base period, plus two one-year option periods, and will be as follows:

7.0 Place of Performance

The place of performance will be the contractor’s facility.

8.0 Travel

The Contractor shall be prepared to travel to the following places: Washington, D.C.; Albuquerque, New Mexico; Las Vegas, Nevada; Amarillo, Texas; Livermore, California; Oak Ridge, Tennessee; Los Alamos, New Mexico; other DOE facilities, and other locations.

9.0 Government Furnished Resources

None.

Appendix 1 – Common Development Tasks

Given that there is a great deal of overlap between specific activities within ARMS and RadResponder, please refer to the following common list of activities and descriptions as these apply to all projects.

Task x.x.1 Project Management

The contractor shall perform the following project management tasks:

· Facilitate client communication

· Participate, As requested, in periodic status meetings with the technical POC.

· Manage and track technical progress and provide regular and on demand reporting

· Develop and communicate level of effort (LOE) estimates

· Develop and communicate work plans, As requested, at the project, month, or week level.

· Coordinate production scheduling and deployments

· Provide technical staff oversight and management

· Certify quality assurance and quality control

Task x.x.2 Software Design

The contractor shall perform software design tasks which may include some or all of the following:

· Participate in discussions with NA-84 and NA-83 staff members, associated contract staff, and other interested parties (e.g. other government agencies).

· Assist in development of technical requirements.

· Assist in development of performance and “return on investment” metrics to support the post-deployment success.

· Conduct and report upon research into technologies, tools, and methods.

Task x.x.3 Software Development

The contractor shall perform software development tasks which may include some or all of the following:

· Creation of database components (tables, views, procedures, functions, etc.).

· Creation of browser based user interfaces and controls.

· Creation of mobile based[endnoteRef:10] user interfaces and controls. [10: Mobile user interfaces may include iOS, Android, and Windows based code and devices, and any other equivalent devices that become commercially available.]

· Creation of reports and other business intelligence components.

· Creation of notifications components such as: emails; faxes; pager messages; social network notifications; and SMS (text) notifications.

· Integration with companion tools, technologies, systems, and peripheral devices and hardware as required.

· Creation of integration components including API’s[endnoteRef:11] and SDK’s[endnoteRef:12]. [11: API: Application Programming Interface; procedures and methods used by other developers to integrate with a system. Typically expressed as WebServices, FTP based processes, stored procedures, or standard data exchange formats such as text files, excel, XML, or EDI.] [12: SDK: Software Development Kit; more robust components and tools which can be used by other developers when integrating with or extending another system or platform. Typically expressed as dll’s (dynamic link libraries) or class files (e.g. java or C#) that are directly incorporated into other code projects.]

· Perform quality assurance and quality control (i.e. unit and regression testing)

Task x.x.4 Software Training Material Production

The contractor shall produce training materials which may include some or all of the following:

· PowerPoint’s and other briefing materials

· Distributable job aids

· Flyers and posters

· Videos

· Recorded webinars

Task x.x.5 Software Training

The contractor shall provide training to ARMS users, which may include some or all of the following:

· Hosting of online webinars

· Leading in person training classes

· Provide on-site just-in-time training during exercise and responses

· Presentations at conferences and meetings

Task x. x.6 Operational Support/Help Desk

The contractor shall provide help desk support during some or all of the following activities: routine operations; trainings; exercises; demonstrations; responses. Specific tasks may include:

· Account support (user accounts, passwords, privileges etc.)

· User support; e.g. data entry, validation, navigation, searching etc .

· Performance monitoring and diagnosis

· Troubleshooting and other general user information requests

Task x.x.7 Software Documentation

The contractor shall provide, at client direction, software documentation which may include some or all of the following:

· Database schema documentation

· Non-Proprietary source code

· API and SDK documentation

· Change logs (i.e. deployment and configuration management documentation)

· System administrator documentation

· Server administration documentation

Appendix 2 – Proposed ARMS Technical Deliverables Proposed deliverables for the ARMS system are listed below. Please note that this list is based upon current needs and usage, and is expected that these deliverables will be modified, re-prioritized, or replaced subject to the direction of NA-84 and NA-83.

ARMS ongoing technical support and maintenance ARMS vNext User Interface ARMS Security Enhancement ARMS Readiness Reporting Improvements ARMS Maintenance Overhaul ARMS Mobile Interfaces NA-84 and NA-83 Service Oriented Architecture NA-84 and NA-83 Central Authentication Service ARMS Evaluation Module Migration of ARMS to a Cloud Environment