Sample_Task_1_-SOW_Systems_Modeling.pdf

Sample/Mock Task Order Statement of Work: Systems-based Modeling of Communities

1. Background

NIST research in community resilience focuses on providing a science-based approach for assessment of the community’s current physical, social, and economic systems and development and evaluation of proposed alternatives to improve community performance and recovery from hazard events.

NIST conducts research in several areas of community resilience. This statement of work supports research into the modeling of the community resilience system. The systems modeling simulates the expected performance of physical infrastructure systems, including dependencies between physical systems and changes in system functionality which are based on the needs of the community and social institutions. An important part of this research, and the focus here, is the addition of decision support capabilities to the systems model. The goal of the decision support capabilities are computer-based tools that facilitate exploration of decision alternatives for community resilience.

This statement of work focuses on two aspects of systems modeling for decision support. The first task is to build the interface between resilience decisions and the NIST systems model. While this SOW focuses on floods, this same work will be required for other hazards (e.g., wind, WUI fire, seismic) and for more components of the resilience system.

The second task consists of software implementation of the decision support components of the systems model. A software prototype is in development at NIST to demonstrate the expected software architecture and functionality of the tool. This work involves building more robust implementations of the software components and interfaces.

2. Objective

To build the interface of the flood resilience decisions to the systems model, and to implement needed software components for a computer-based tool, the goal of which is to facilitate exploration of decision alternatives for community resilience.

3. Scope

The contractor shall provide support to the government in systems modeling for decision support. The contractor shall build the interface between resilience decisions and the NIST systems model. The contractor shall implement the software of the decision support components of the systems model. A software prototype is in development at NIST to demonstrate the expected software architecture and functionality of the tool. This work involves building more robust implementations of the software components and interfaces.

This is a firm-fixed price type task order.

4. Specific Tasks

The Contractor shall:

Task 1: Develop the interface between flood resilience decisions and the systems model

This task focuses on developing the systems model interface for resilience decision-making with flood as an example hazard, working in conjunction with NIST. A particular decision consists of setting the values of decision variables, those variables that are under our control and that influence the performance of the system. As an example of an engineering-related decision, the decision variables may consist of the selection (from many) of one configuration for a resilience option and the specification of the key sizing parameters for that configuration (e.g., height of a levee). (Other design parameters may be tied to the decision variable, e.g., with a minimum side slope for the levee).

As an example of the level of the complexity of the modeling required to link the resilience decision to the systems model, the reader is referred to the FEMA-102 report. In that report on the floodproofing of non-residential structures, basic configurations and design parameters were specified for each of several floodproofing options and linked via a set of equations to the level of flood protection they provide. In addition, the form of equations linking the configurations and design parameters to cost were supplied.

Similar equations are needed for each decision variable, for components across the resilience system. The scope of this task is limited, however, to resilience decisions for the following components:

• Water supply:

o Water intake structures o Water treatment plants: electrical controls

• Electrical power network:

o Electrical substations o Generators

• Portable water treatment trailers

• Portable pumps to remove water from behind a levee

• Roads

• Schools

• Preparedness (e.g., education, evacuation planning)

Task 1 will involve the following subtasks for each of the above items:

Task 1.1: Conduct a Literature review for available relevant information sources and tools

The contractor shall conduct a literature review for available relevant sources and tools, and for each describe their purpose, scope, and relevance

Task 1.2: Listing and description of resilience options, and for each resilience option, identification of the decision variables, including basic configurations and design parameters

The contractor shall provide a list and description of resilience options, and shall identify the decision variables for each option, including the basic configurations and design parameters. NIST will provide feedback to help in prioritization of resilience options if necessary.

Task 1.3: Formulation of equations that link decision variables to level of protection against flood stage/elevations

These formulations shall include the functional forms (e.g., linear, quadratic) of the equations, the independent variables (clearly described), default values for the coefficients, and characterization the uncertainty, as ranges or distributions, of the coefficients. The contractor shall provide a justification for these choices .

Task 1.4: Selection and justification of the functional forms for the cost functions

The contractor shall select and provide a justification for the functional forms for the cost functions. The contractor shall also provide details on the underlying regressions or bottom up approach .

Task 1.5: Coding of the equations in MS Excel spreadsheets

Coefficients shall be identified in separate cells. The uncertainty ranges (or distributional parameters) shall be specified (but no uncertainty propagation required).

Task 1.6: Documentation of equations/spreadsheets -- within code

The contractor shall provide the government with spreadsheets documenting the results of the related tasks above. The spreadsheet shall be well documented to point out any modeling or data choices that may not be obvious to the user.

The level of complexity (i.e., number of design parameters and configurations) of the modeling shall be determined in consultation with NIST. It is important that the complexity be commensurate with that of the NIST systems model and that it also reflect a community’s expected availability of data.

Task 2. Software implementation

This task involves implementation of certain components of a software system in development at NIST.

The software architecture is anticipated to include, among others, the following components

• Mathematical program (i.e., optimization model) (prototype: written in the mathematical programming language AMPL)

• Solver (prototype: FICO XPRESS)

• Solution manager (prototype: MS Excel)

• Solution display (prototype: MS Excel)

• Databases (prototype: MS Access) o Geospatial o Resilience options o Power, Water, Networks (links,nodes)

• Input manager (prototype: MS Excel)

• Interfaces between several of the above components

This task requires the contractor to implement at least two of the above components. The subtasks are as follows:

Task 2.1: Select the programming languages and (if needed) additional software components

Task 2.2: Develop high-quality code/solutions that implement the interfaces for the above components

Task 2.3: Develop a testing plan and execute

The Contractor shall practice requirements management, change control management and testing. NIST will provide requirements, interface definitions, and metadata standards, and preferred programming languages. NIST preference is for open source codes (e.g., python). Consultation with NIST is needed as in certain cases, (e.g., solver), the quality of open source components may not be sufficient. The contractor shall provide adequate commenting within the code.

Task 3: Project management Task 3.1: Provide a project work plan to be presented at a NIST kickoff meeting

Upon award, the contractor shall convene a video conference call to kick off the project at a mutually agreed upon date and time. This call shall include the NIST Contracting Officer’s Representative (COR) and the TPOC, along with key contract personnel.

Task 3.2: Attend/participate remotely in monthly project review meetings and present issues and work in progress

Monthly update video conference calls are required and shall include all major project reporting, as well as review of any issues that arise during the course of the work. However, if significant issues should arise between monthly updates, the contractor shall contact the COR and TPOC as soon as possible. Prior to the monthly call (at least 2 business days), an agenda shall be provided along with a brief summary of progress via email to the COR and TPOC. Following the meeting (within 5 business days), the contractor shall provide a brief report that shall include a summary of the meeting (key discussion points and decisions) and general updates for that month.

5. Deliverables

Deliverabl e for task…

Description Quantity/ Media

Date Completed (from award of contract)

3.1 Summary of kickoff meeting and project plan

Digital file in MS Word (docx) format

NLT 50 calendar days

1.1,1.2,1.3,

1.4 Document resilience option equations

MS Word (docx), MS Excel (xlsx) format

NLT 200 calendar days

1.5 Resilience option spreadsheet models MS Excel

(xlsx) format

NLT 300 calendar days

2 Code implementing software components Zipped file (.zip)

NLT 270 calendar days

3.2 Summaries of monthly updates and meeting, including presentation materials

Digital files:

MS Word (docx), Powerpoint (pptx) format

Every 30 calendar days

6. References

FEMA, “FLOODPROOFING NON-RESIDENTIAL STRUCTURES”, Report FEMA-102, 1986.

7. Key Personnel

The contractor shall assign at minimum key personnel for the positions identified below. Contractor Key Personnel shall meet the following minimum qualifications for each of the respective required key personnel positions.

Program Manager Minimum Education: Bachelor s degree from accredited college or university in Engineering, Science, Mathematics or other related field.

Minimum/General Experience: This position requires a minimum of 10 years general project management experience, of which at least 5 is managing similar work than that contemplated in this solicitation.

Civil Engineer Minimum Education: Bachelor's degree from accredited college or university in Engineering, Computer Science, Science, Mathematics or other related field.

Minimum Experience: 10 year

Computer Application Developer

Technical Level II Minimum Education: Bachelor's degree from accredited college or university in Engineering, Computer Science, Science, Mathematics or other related field.

Minimum Experience: 5 years, of which 2 years is specialized in a specific field.

Computer Database Manager Technical Level II Minimum Education: Bachelor's degree from accredited college or university in Engineering, Computer Science, Science, Mathematics or other related field.

Minimum Experience: 5 years, of which 2 years is specialized in a specific field.

8. Government Furnished Information

NIST will provide requirements, interface definitions, and metadata standards, and preferred programming languages/software components.

9. Security

There are no special security requirements. This contract has a low security risk. Disaster Resilience Fellows must be able to pass a public trust background check.

10. Travel

The Contractor shall be reimbursed in accordance with the GSA Federal Travel Regulations. The Contractor shall not exceed funding for travel as specified in this contract. The NIST Contracting Officer Representative (COR) must approve estimated travel costs 10 calendar days prior to travel.

Contractor travel expenses cannot exceed government rates for travel or per diem. Contractor shall follow the Federal Travel Regulation and NIST policies for all travel under this Task Order. The Contractor shall not be responsible for any travel expenses for Government employees who are associated with this project.

11. Place of Performance

Contractors shall work from their normal place of business.

12. Period of Performance

The period of performance shall be up to 12 months from the date of award.

13. Meeting Requirements

Project meetings for Task 3 will be held at NIST, Gaithersburg, MD campus or at an alternate location approved by NIST (Task 3). NIST reserves the right to invite other participants to project review meetings. Such participants will not travel at the expense of the Contractor.

14. General Information

1. Confidential or Proprietary Data: This work does involve confidential or proprietary data.

2. Media Inquiries: The Contractor employee shall not respond to any media inquiries. Any inquiries from the media shall be immediately relayed to the COR and/or the Contracting Officer. There shall be no media interviews, comments, or any other response without the knowledge and approval of the NIST Director.