Performance_Work_Statement-_SB1341-15-RQ-0391.pdf
PDF 208 KB Posted
- Attached to
- Cyber Physical Systems Testbed Support, including Cloud and Smart Grid Federal contract opportunity
- Solicitation number
- SB1341-15-RQ-0391
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Solicitation-_SB1341-15-RQ-0391.pdf | ||
| APPLICABLE_PROVISIONS_AND_CLAUSES.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Performance Work Statement
SB1341-15-RQ-0391
1 | P a g e
Title: Cyber Physical Systems (CPS) Testbeds support, including Cloud and SmartGrid.
1.0 PURPOSE
The Software and Systems Division (SSD) of NIST is requesting that the Contractor furnish advanced research and development expertise to assist the SSD in providing leadership and technical expertise in the development of measurement methods for our Cyber Physical Systems (CPS) Testbeds, including the time synchronization testbed for the power industry to support the Smart Grid, and the
Cyber Physical Cloud Computing (CPCC) testbed. The mission of the SSD is to develop software testing tools and methods that improve quality, conformance to standards and correctness. The Division participates with industry in the development of forward-looking standards for the Smart Grid, Cloud and
Healthcare communities. The Division's programs respond to industry, consortia, and standards groups’ needs by concentrating on key research areas at the forefront of technology and assisting in the transfer of technology and expertise to industry via testbeds and tools.
2.0 BACKGROUND
The NIST SSD has been working on testbed activities in Smart Grid Precision Time
Synchronization. In collaboration with the Quantum Electrical Metrology Division (QEMD), Computer
Security Division (CSD), Time and Frequency Division (TFD), Energy and Environment Division (EED) and Intelligent Systems Division (ISD), the SSD Smart Grid Precision Time Synchronization project requires leadership and technical staff support in the area of standards and technology development and adoption, measurement, and development of software and hardware testing tools to improve the quality and correctness of distributed time synchronization standards adoption. The project focuses on NIST’s efforts to build an IEEE (Institute of Electronics and Electrical Engineering) 1588 (Precision Time
Protocol) time synchronization testbed. The IEEE 1588 standard has been approved for use in the Smart
Grid, however concerns of its reliability and vendor interoperability need to be verified before widespread industry adoption. The IEEE 1588 testbed is a collaborative effort among NIST, academia and industry to help ensure that test methods utilize state-of-the-art capabilities while ensuring the technologies developed can be readily transferred to industry.
The initial IEEE 1588 Testbed was developed to characterize the factors impacting time synchronization performance in the next-generation Smart Grid. The initial testbed has been instrumental in understanding the parameters that characterize the time synchronization performance.
The impact of synchronization intervals, syntonization, topology, and network traffic on the synchronization accuracy has been assessed. Conformance test methods have also been developed.
The plan is to begin research and development into practical issues such as interoperability, secure and resilient time as well as Smart Grid control scenarios to better support the reliability requirements and understand the impact of precision timing on various control applications in the Smart Grid.
A key goal of these efforts is to support the development of the NIST Smart Grid and CPS testbeds and enabling an infrastructure for conformance and interoperability testing as well as research and development on understanding the impact of precision time on measurement and control uncertainty as
2 | P a g e well as novel applications of precision time. To achieve this goal, NIST SSD will be working to expand the precision timing testbed as well as ramping up the NIST CPCC testbed by building software and hardware tools that will enable measurement and experimentation of precision timing networks and will promote consistent definitions and reuse of test methods for precision timing standards and power profiles.
3.0 REQUIRED RESEARCH AREAS AND TASKS
The demand for accurately distributed time synchronization is critical to improving our nation’s infrastructures such as the Smart Grid. In particular, wide area monitoring and situational awareness required to take corrective actions will need to rely on Phasor Measurement Units (PMUs), which are critically dependent upon accurately time-stamped data. PMUs and other substation IED measurements rely on synchronized time-stamps to accurately reconstruct the sequence of events in order to make intelligent control decisions. This research project seeks to contribute to the general state of the art for software and hardware time synchronization protocol standards testing, by advancing the development of time synchronization protocol standards that are complete and testable and by providing the necessary conformance tests, tests tools and techniques where appropriate. There is a real need for formal and informal coordination of these efforts to leverage the synergy of the various efforts, to enable interoperability, and to promote consistent testing across and within organizations.
NIST SSD is collaborating with other NIST divisions in the NIST Physical Measurement Laboratory
(PML) and Engineering Laboratory (EL), industry, standards organizations, and academia to perform research in expanding the use and reliability of precision time in the Smart Grid. The project will also build tools, simulations and prototypes to advance the adoption of distributed time synchronization in the
Smart Grid.
This task order seeks to contribute to the general state of the art for conformance software as well as contribute to the healthcare industry specifically, by advancing healthcare information standards that are complete and testable and by providing the necessary conformance tests, tests tools and techniques where appropriate.
The NIST SSD requires project leadership and technical staff support from the Contractor in the areas of standards and technology development and adoption, measurement, and development of software testing tools to improve the quality and correctness of software used in our nation’s critical infrastructures such as Healthcare, CPS, and Cloud Computing. The task order focuses on NIST’s efforts in two areas:
1. Testing for Meaningful Use of Healthcare technologies -- The Health IT Standards Testing is a collaborative effort to help ensure interoperability among all healthcare providers, hospitals, clinical laboratories, pharmacies, payers, and others via the meaningful use criteria. NIST has developed testing tools to support the meaningful use testing for ePrescribing and testing for
Simple Object Access protocol (SOAP) based Cross-Enterprise Document Reliable
Interchange (XDR) data exchange. NIST will require the contractor to assist in extending the functionality of these test tools to include the new requirements of meaningful Use 2015
3 | P a g e edition.
2. Cloud Computing – NIST is leading the development of reference architecture and standard service level agreements for government use of Cloud Computing resources. Specifically, NIST requires support from the contractor in the development of Business Use Cases for Cloud
Computing supporting this architecture.
The Cyber Infrastructure Group of the NIST SSD has a number of activities that require the development of software for CPS. “Cyber-physical systems are rapidly becoming critical to the business success of many companies and the mission success of many government agencies. In transportation, manufacturing, telecommunications, consumer electronics, and health and medical equipment, and intelligent buildings the value share of electronics, computing, communications, sensing, and actuation is expected to exceed 50% of the cost by the end of the decade. ”1 NIST is researching challenges for modern CPS also known as the Internet of Things (IoT). These modern
CPS are complex, distributed, flexible, and heterogeneous collections of interconnected components or services. One way to build these systems is using a service based approach where the resulting systems exhibit the cloud characteristics (or Cyber-Physical Cloud Computing). Cyber-Physical Cloud
Computing systems (CPCC) will combine social systems and cloud computing technologies with traditional CPS technologies using new infrastructures, technologies, services, and standards to allow collaborative operations combining many different components in a flexible module. To enable innovative and efficient combination of physical, cyber and human resources the CPCC environment will provide a framework so components (sensors, processor, data, and actuators) may be provided as cloud services and used for more than one system. Not only do these resources need to be provided as shared services, but they need a way of reporting their specific capabilities in a consistent and comparable manner with supporting measurement capabilities to ensure that the virtual system achieves the requisite performance. To create this infrastructure standards are needed in the following areas: description of service capabilities (including, timeliness, physical location, data uncertainty, and reliability), interoperability, portability, security and privacy. The goal is to create a CPCC testbed that implements the basic functionality of the CPCC infrastructure using existing standards and technology. The testbed can be used to test different aspects of the infrastructure including service interoperability, characterization, performance and security. This phase of the project will focus on the service characterization and performance; other aspects will be evaluated in the future.
4.0 SCOPE OF WORK
The NIST SSD requires technical staff support from the Contractor in the areas of standards and technology development and adoption, measurement, and development of software testing tools. As requested, the Contractor shall support NIST SSD in the collaboration with industry, NIST PML and EL, related standards organizations, and academia to build tools and prototypes to advance the adoption of
1 Strategic Vision and Business Drivers for 21st Century Cyber-Physical Systems Executive Roundtable Highlights -http://www.nist.gov/el/upload/Exec-Roundtable-SumReport-Final-1-30-13.pdf
4 | P a g e
IEEE 1588 within the Smart Grid. Specific objectives include:
Collaborating with the IEEE PSRC WG, Time-Aware Applications, Computers, Communications and Systems (TAACCS), NIST CSD, NIST Synchrophasor Testbed, and NIST CPS Testbeds in the development of research to advance the reliability and use of precision time in improving Smart Grid measurement and control for the NIST
Precision Timing and Smart Grid testbeds.
Providing technical leadership on the IEEE 1588 Smart Grid Time Synchronization
Testbed.
Providing technical leadership for research and development in secure time and Smart
Grid controls with respect to precise timing.
The Contractor shall support NIST SSD in the collaboration with industry, healthcare informatics-related standards organizations, consortia, and government agencies to build tools and prototypes to advance the adoption of ePrescribing protocols to support meaningful use testing. The contractor shall also develop test cases for additional message types based on input from NIST.
NIST will lead interested USG agencies and industry to define target USG Cloud Computing business use cases (set of candidate deployments to be used as examples) for Cloud Computing model options, to identify specific risks, concerns and constraints. For example, a candidate deployment might be employee email or migration of a specific application system to a specific cloud computing model option. NIST will lead and facilitate this effort via the Federal CIO Council sponsored Cloud Computing Standards
Working Group and working groups by NIST. The contractor shall participate and serve in a leadership role of the Business Use Case Definitions working group (subgroup of the Mail Cloud Committee at
NIST). The mission of the working group is to define USG Target Business (mission) Use Cases which include: definition of a candidate agency system or service for the Cloud Computing model option; list of perceived risks, concerns, questions, issues; and operational scenario (scope to be determined;
sufficient but not necessarily limited to focus security, interoperability, and portability requirements.)
The Target USG Cloud Computing Business Use Cases are a set of candidate deployments to be used as examples for various Cloud Computing model options, and identify realistic risks, concerns and constraints (i.e. a candidate deployment might be employee email and office automation or migration of a specific application system to a specific cloud computing model option.)
5.0 SPECIFIC TASKS
Task 1: Testbed Support for SmartGrid Time Synchronization for the Power Industry
The contractor is responsible for performing the following specific tasks, which are further categorized into Tasks 1A, 1B and 1C as described below:
1. Complete the installation, testing and validation of IEEE 1588 PTP equipment for the Smart
Grid and Precision Timing testbeds.
2. Complete implementation of a real-time simulation of a Smart Grid control scenario using precision time accuracies based on the timing testbed.
5 | P a g e
3. Continue research, development and validation in secure and resilient time. Assess and validate results based on a set of timing quality metrics established with NIST.
4. Continue research and development as well as validation on the use of precise time for anomaly detection in CPS networks.
5. Support cybersecurity and control systems research as related to precision timing and/or CPS.
6. Continue research on how timing errors impact distributed measurement uncertainty. Research potential uses cases and develop or implement an existing control algorithm requiring distributed measurements to understand how timing performance affects control algorithm performance in the context of grid resiliency and optimization with Distributed Energy
Resources (DERs).
7. Begin exploratory research and prototyping of hardware measurement tools for the NIST
Precision Timing Testbed.
8. Begin exploratory research on low-cost wireless time synchronization.
9. Support the design and implementation of NIST CPS testbeds.
Status Reports: The contractor shall keep the Contracting Officer’s Representative (COR) apprised of developments and issues on a weekly basis at minimum.
Based on the reports in various tasks, deliverables, and due dates may be modified upon approval by the COR, and modification to the contract.
Specified data formats. The contractor shall provide results in Microsoft Excel and CSV formats, presentations in Power Point or Keynote and reports in Microsoft Word format.
Standards for Acceptance of Deliverables: The NIST COR will provide comments on each deliverable within 10 business days from receipt of a given deliverable. The contractor shall make any needed changes to the deliverables within 10 business days from receipt of electronic or written comments from the COR.
Task 1A: Complete the installation, testing and validation of IEEE 1588 PTP equipment for the Smart
Grid and Precision Timing testbeds. Complete implementation of a real-time simulation of a Smart
Grid control scenario using precision time accuracies based on the timing testbed. Begin exploratory research and prototyping of hardware remote measurement tools for the NIST Precision Timing
Testbed. Begin exploratory research on low-cost wireless time synchronization. Continue research on how timing errors impact distributed measurement and control uncertainty. Research potential uses cases and develop or implement an existing control algorithm requiring distributed measurements to understand how timing performance affects control algorithm performance in the context of grid resiliency and optimization with DERs. This task encompasses Tasks 1, 2, 6, 7 and 8 listed above.
Deliverables:
Test results of the IEEE 1588 PTP network based on agreed metrics including, but not limited to synchronization accuracy.
Documentation on the tests as well as the validation process.
A hardware remote measurement tool capability striving for at least 100 ns accuracy.
6 | P a g e
A paper that describes the research, development and validation of how timing errors impact distributed measurement and control uncertainty.
Presentation, demo and version controlled source code of real-time RT-Lab Simulation.
Due 12 months after contract award.
Task 1B: Continue research, development and validation in secure and resilient time. Assess and validate results based on a set of timing quality metrics established with NIST. Support cybersecurity and control systems research as related to precision timing and/or CPS. Continue research and development as well as validation on the use of precise time for anomaly detection in CPS networks.
This task encompasses Tasks 3, 4, 5, and 9 listed above.
Deliverable
An embedded board with ensemble of synchronizable clocks and associated documentation / training for operating the board.
A presentation and paper that describes the design, implementation and validation of a novel research concept in secure and resilient time.
A paper on end-to-end authentication of PMU measurements assessing impact of timing on security.
A paper on state-based loop recovery for industrial control system.
Demo and source code of anomaly detection software.
Task 1C: Support exploratory research in CPS decision support systems and use knowledge gathered to support the design and implementation of NIST CPS testbeds. This task encompasses 9 listed above.
Deliverable:
Paper documenting the exploratory research in CPS decision support systems.
Presentation on the design justifications and research goals for the NIST CPS testbeds.
Task 2: Cloud Computing and Meaningful Use Tool Development
The NIST SSD requires project leadership and technical staff support from the Contractor in the areas of standards and technology development and adoption, measurement, and development of software testing tools to improve the quality and correctness of software used in our nation’s critical infrastructures such as Healthcare and Cloud Computing. This task focuses on NIST’s efforts in two areas:
7 | P a g e
1. Testing for Meaningful Use of Healthcare technologies -- The Health IT Standards Testing is a collaborative effort to help ensure interoperability among all healthcare providers, hospitals, clinical laboratories, pharmacies, payers, and others via the meaningful use criteria. NIST has developed testing tools to support the meaningful use testing for ePrescribing. NIST will require the contractor’s support in extending the ePrescribing tool to include the new requirements of meaningful Use.
2. Cloud Computing – NIST is leading the development of reference architecture and standard service level agreements for Government Use of Cloud Computing Resources. Specifically, NIST requires support from the contractor in the development of Business Use Cases for cloud computing supporting this architecture.
Task 2A: Support the NIST Cloud Computing Program (NCCP)
Specific Tasks:
The NCCP has been leading the effort to advance the adoption of cloud computing by the federal government. In that endeavor the NCCP has lead several public working groups to address requirements like standardization, security, service agreements or metrics. The
Contractor shall work with the NIST NCCP team on the efforts of the working groups.
More specifically, the Contractor shall focus on the metrics ecosystem definition by leading the NIST Cloud Service Metrics Public Working Group. The Contractor shall work with members of the working group and members of the NCCP team to define models, examples or documents of the cloud service metric ecosystem that build upon the
CSM model (Cloud Service Metric). Possible extensions of that model are the Context model, the Measurement Model or the Scenario Model. In addition the Contractor shall assist in interactions with outside Standards Development Organizations (SDOs) to find common goals and complementary activities that can be used to advance the goals of the
NCCP. Interactions with the outside will require the contractor to develop and maintain a website with the NCCP documents and other information available.
Status Reports: The contractor shall keep the COR apprised of developments and issues on a weekly basis at minimum.
Based on the reports in various tasks, deliverables, and due dates may be modified upon approval by the COR, and modification to the contract.
8 | P a g e
A paper, based on the work on cloud service metric ecosystem, selected by NCCP staff to be published.
A report on the common goals and complementary activities with other SDOs. The report shall include a justification for the selection of those common goals and complementary activities, the projected outcomes, and a timeline for completion for each item and document the progress towards each. Report shall be prepared in MS-Word format.
An internal website to support NCCP staff host cloud computing workshops and assistance on workshop organization and implementation as required.
Deliverables due no later than 12 months from task award order.
Task 2B: Support Cloud Research
Specific Tasks:
The NIST Advanced Networking Division (ANTD) has been developing expertise in cloud and CPS research to address challenges like mobile clouds, edge clouds or heterogeneous virtualized connected things. To that effect ANTD is looking to gain a better understanding on how a cloud infrastructure is built and architected. The objective is to understand what core components are critical for the cloud infrastructure to work and to know how to use these components independently from one another and coupled to each other. This will allow the research group to better determine what components are critical for mobile and edge cloud computing and how to develop or integrate them. The
Contractor shall work with the NIST team to establish to research parameters and planning to deconstruct and rebuild a reference cloud implementation based on
OpenStack. OpenStack is the candidate implementation for this exercise because as of today it is the most popular open source project for IaaS with a very vibrant community.
The Contractor shall also work with the NIST team to identify areas of work in the cloud
CPS testbed that are complementary with other efforts at NIST and how this work should be integrated.
Deliverables:
Feasibility and planning document for the OpenStack reboot
Iterated releases of code base Living document for lessons learned.
Contractor provides quarterly report on lab alignment activity of CPS and ANTD Cloud
Research Group. (Format MS-Word)
9 | P a g e
Task 2C: Support the Meaningful Use Tool for ePrescibing ePrescribing (e-Rx) - a prescriber's ability to electronically send an accurate, error-free and understandable prescription directly to a pharmacy from the point-of-care is an important element in improving the quality of patient care. NIST supports the testing of Meaningful Use of EHRs to implement ePrescribing standards. NIST has developed a tool to test an EHR's ability to perform several required messages. The Contractor shall assist NIST staff in supporting this tool.
The Contractor shall assist NIST staff to:
Receive and respond to requests from the public inquiries on the tool via the Google Group set up by NIST (https://groups.google.com/d/forum/erx-testing-tool)
Help NIST staff with Java programming support of the tool.
Provide bug fixes to the tool based on industry input.
Provide any needed modifications to the tool based on industry input.
Modify Validation reports based on industry input and to provide new functionality.
The Contractor shall deliver a working version of the conformance tool and source code.
Task 3: Composition and Interoperability of Components in Cyber-Physical Cloud
Computing Systems
In this task, NIST is looking at several challenges related to system orchestration that are critical to creating flexible, complex systems of connected components with cloud characteristics:
● Intelligent and accurate component and service representation - The ability to represent component and systems capabilities and attributes at different levels of granularity based on the context of use.
● Disparate/heterogeneous component connection/interaction - The ability to combine components from disparate sources into systems so the resulting system meets the design requirements.
● Intelligent system optimization - The ability to have intelligent provisioning of system resources.
● Dynamic intelligent system optimization - The ability to have intelligent system optimization during runtime.
It is critical to understand these concepts in CPCC systems. For instance, how does one know what
10 | P a g e the characteristics of each service are, how to decide what components to combine, how to compose it or how to optimize the composition based on user requirements? Furthermore, how does one choose to conduct the system or for the system to learn how to best provision and de-provision resources?
Task 3A: Establish research parameters and plans
In this task, the Contractor shall work with NIST staff to determine how sciences and technologies like category theory, rule engines, machine learning, semantic science, reactive programming can address the challenges of system orchestration -composition and conduction. The Contractor shall then work with NIST to establish concrete scenarios that show proofs of concept of a composition framework and a conduction framework.
Status Reports: The contractor shall keep the COR apprised of developments and issues on a weekly basis at minimum.
Based on the reports in various tasks, deliverables, and due dates may be modified upon approval by the COR, and modification to the contract.
Deliverables
● A short report (less than 10 pages) that indicates the challenges intended to be researched, and the proposed technologies to be implemented
● A detailed plan for the development of scenarios for an orchestration framework for CPCC focused around composition and conducting
Deliverables due no later than 2 months from task award order.
The content and deliverables of task 3B might be affected by the outcome of task 3A, i.e., Task 3B will start when task 3A ends.
Task 3B: Develop proof of concept for a composition framework for CPCC
In this task, the Contractor shall work with NIST staff to design and develop a composition framework proof of concept for time-aware and elastic connected things. The Contractor shall lead the effort and base the design and development of the solution on the planned scenario laid out in
Task 3A.
11 | P a g e
● An implemented proof of concept of the composition framework for creating CPCC. This framework shall integrate with the CPCC Testbed Phase 2
● A document summarizing the design concepts, implementation, and results note
Deliverables due no later than 8 months from task award order.
The content and deliverables of task 3B might be affected by the outcome of task 3A, i.e., Task 3B will start when task 3A ends.
Task 3C: Develop proof of concept for an optimization framework for CPCC
In this task, the Contractor shall work with NIST staff to design and develop an optimization framework proof of concept for time-aware and elastic connected things. The Contractor shall lead the effort and base the design and development of the solution on the planned scenario laid out in
Task 3A.
● An implemented proof of concept of the optimization framework for CPCC. This framework shall integrate with the CPCC Testbed Phase 2
● A document summarizing the design concepts, implementation, and results
Deliverables due no later than 10 months from task award order.
Task 3D: Support the Meaningful Use Tool for XDR Protocol Testing - NIST Edge Testing
Tool (edge.nist.gov)
NIST SSD is collaborating with industry, standards organizations, consortia, and government agencies to build tools and prototypes to advance the adoption of IT within healthcare systems.
The Contractor shall support NIST SSD in the collaboration with industry, healthcare informatics-related standards organizations, consortia, and government agencies to build tools and prototypes to advance Meaningful Use testing of healthcare systems related to transport standards. Specific objectives include:
● Collaborating with NwHIN members to help ensure SOAP/XDRL messaging of an
Electronic Health Record (EHR) systems' conformance can be defined and measured at an appropriate level.
● Providing technical leadership on Office of the National Coordinator (ONC) projects, in particular the Edge Testing Tool (ETT).
12 | P a g e
On March 20, 2015, the Department of Health and Human Services (HHS) issued the 2015 Edition
Certification and Stage 3 NPRM. This interim final rule specifies the 2015 criteria (meaningful use objectives and measures) that eligible professionals (EPs), eligible hospitals (EHs), and critical access hospitals (CAHs) must meet in order to qualify for Medicare and/or Medicaid electronic health record (EHR) incentive payments. For Meaningful Use Stage 2, the Transition of Care (ToC) objectives and measures, for EPs and for EHs/CAHs, require electronic exchange. Specifically, EPs and EHs/CAHs can electronically exchange a summary of care record using the XDR protocol, tested by the edge testing tool (ETT) edge.nist.gov. The Contractor shall assist NIST staff in supporting the tool.
The Contractor shall assist NIST staff to:
Receive and respond to requests from the public inquiries on the tool – Via Google Group -
(https://groups.google.com/forum/#!forum/ edge-test-tool)
Help NIST staff with Java programming support of the tool.
Provide bug fixes to the tool based on industry input.
Provide any needed modifications to the tool based on industry input.
The Contractor shall deliver a working version of the conformance tool and all source code.
Deliverable due no later than 12 months from task award order.
6.0 MAN HOURS/LABOR CATAGORIES
NIST estimates the contractor will require a total minimum level of effort (LOE) as identified in the following table to complete these tasks:
Task Key Personnel Estimated Hours by Labor Category
Task 1 Key Personnel 1920
Task 2 Key Personnel 1920
Task 3 Key Personnel 1920
Total 5760
7.0 PERIOD OF PERFORMANCE
Period of Performance is from June 15, 2015 through September 30, 2016.
8.0 CONTRACTOR QUALIFICATIONS
The following contractor key personnel are required for successful performance of the work detailed in
13 | P a g e this document. The titles of the labor categories used below are not required; they are only used to demonstrate the nature of the key personnel position.
Task 1: Research Scientist
The Contractor must have formal training and/or demonstrated experience in the following areas
• IEEE 1588-2008 expert (Precision Time Protocol)
• Proficient in the IEEE C37-238 Power profile
• Expertise with the Smart Grid, Microgrids, PMUs (Phasor Measurement Units) and the power distribution time-synchronization requirements
• PhD in Control Systems
• Proficient in using an oscilloscope
• Design and solder printed circuit boards (PCBs)
• Experience with working in a control research environment, published in high impact journal
• Experience with deploying and testing fiber optic networks
• Experience with acquiring GPS and other radio sources (WWVB) of time
• Familiar with IEC 61850
• Composable testbed design and implementation experience
• Proficient in Matlab/Simulink/SimPowerSystems
• Proficient with RT-LAB and OPAL-RT simulation systems
• Expertise in Cybersecurity
Task 2: Research Scientist
The Contractor must have formal training and/or demonstrated experience in the following areas:
NIST Cloud Computing Roadmap – 4 years
Cloud Computing - 4 years
UML Modeling – 8 years
Business Use Case Development – 4 years
Use Case Editors - 4 years
NCPCP Script Standard for ePrescribing version 10.6 (XML & EDI) – 4 years
EDIFACT – 4 years
XML – 8 years
Java Programming – 8 years
Experience with the NIST ePrescribing Tool – 4 years
Experience with the NIST Randomizer Tool – 3 year
Task 3: Research Scientist
The staff proposed for this task must have formal training in the following areas or demonstrated
14 | P a g e experience in the areas within the last Ten (10) years:
Senior Java Developer (6+ years).
Web Development: Spring, JSF, JQuery, Tomcat (5+ Years)
Development Process: JUnit, Maven, Hudson, Redmine, Design Pattern.
XML: XML Schema, XML Beans, XPath, XSLT.(5+ Years) and SOAP. (5+ Years)
Proficient in HL7 v2 and v3 message validation and generation. (5+ Years)
Proficient in IHE PIX/PDQ domain. (5+ Years)
Proficient in test case development (5+ Years)
Experience with the NIST Core Message Validation Engine (3+ Years)
3 years’ experience as a Developer
3 years’ experience implementing SAML
3 years’ experience with Connect
3 years’ experience with SOAP RTM specification
3 years’ experience with the Direct specification and implementation experience
3 years’ experience SOAP.
3 years’ experience with message validation and generation
3 years’ experience with XDS and XDR messaging
2 years’ experience with Cyber Physical Systems and the NIST testbed
9.0 DELIVERABLES
Task
Number
Description Format Quantity Due Date
Task 1A Presentation
Report
Demo
Power Point
PDF or MS Word
Java Source Code
RTLAB Source
Code/MATLAB/S
IMULINK
12 months from award
Task 1B Hardware Board
Report
Presentation
Demo
PDF or MS Word
Power Point
Source Code
12 months from award
Task 1C Report
Presentation
PDF or MS Word
Power Point
Task 2A Report
Paper
Wiki
PDF or MS Word
PDF or MS Word
Wiki
12 months from award
15 | P a g e
Description Format Quantity Due Date
Task 2B Java Source Code
Paper
Report
Wiki
Java Source Code
PDF or MS Word
PDF or MS Word
Wiki
12 months from award
Task 2C Java Source Code
Working Web-Based
Tool
Java Source Code
URL
Task 3A A short report that indicate the challenges intended to be researched, and the proposed technologies to be implemented
A detailed plan for the development of scenarios for an orchestration framework for CPCC focused around composition and conducting
Word Document
Word Document
2 months from award
2 months from award
Task 3B An implemented proof of concept of the composition framework for creating CPCC. This framework should integrate with the
CPCC Testbed Phase
A document summarizing the design concepts, implementation, and
Source Code
Word document
8 months from award
8 months from award
16 | P a g e
Description Format Quantity Due Date results
Task 3C An implemented proof of concept of the optimization framework for
CPCC. This framework should integrate with the
CPCC Testbed Phase
A document summarizing the design concepts, implementation, and results
Source code
Word document
10 months from award
10 months from award
Task 3D Java Source Code
Working Web-Based
Tool
Java Source Code
URL
10.0 PLACE OF PERFORMANCE
The majority of the distributed development team is located at NIST, Gaithersburg, MD, and the
Contractor staff shall be physically located at NIST.
11.0 INSPECTION AND ACCEPTANCE CRITERIA
As duties and responsibilities are completed, the Contractor shall request review and inspection by the
NIST COR. Tasks completed in an unacceptable manner may require corrective action by the
Contractor. Within 10 business days of receipt of deliverables, the NIST COTR shall provide the
Contractor of any required revisions or deliverable acceptance.
12.0 GOVERNMENT FURNISHED PROPERTY AND RESPONSIBILITIES
The Government will provide to the Contractor key personnel through the NIST COR:
17 | P a g e
1. Office space to include desk and chair
2. All computing hardware, software and networking resources.
3. Access to NIST campus during working hours; non-working hour access may be granted on a need basis.
13.0 EXHIBITS AND ATTACHMENTS
None.
14.0 TRAVEL
Travel will be required to attend workshops or conferences as required to present NIST work.
Currently Task 1 will require two CONUS trips to attend conferences and present papers. Task 2 will require two CONUS trips to attend conferences and present papers.
16.0 QUALITY ASSURANCE SURVEILLANCE PLAN
The purpose of this plan is to provide a quality assurance surveillance plan for the work to be conducted under this contract. The plan provides a basis for the NIST COR to evaluate the quality of the Contractor's performance. The oversight outlined in this plan will help to ensure that the topics and assessment are maintained at the required levels through the Period of Performance. Further, this plan provides the NIST COR with a proactive way to avoid unacceptable or deficient performance.
Performance Standards:
1. Quality Level: By monitoring the Contractor, the NIST COR will determine whether the
Performance Standards set forth in the contract have been attained. Performance Standards for all tasks are specified in the Performance Requirements Summary of the Performance Work Statement.
2. Frequency: During the performance of this contract, the NIST COR takes periodic measurements
(i.e., conduct surveillance), as specified, and will analyze whether the frequency of measurement is appropriate for the work being performed. Adjustments may only be made by a modification to the
Contract.
3. Management Responsiveness: The NIST COR will determine whether the Contractor has managed the Contract effectively and efficiently with successful completion of the topics and assessment as specified in the Performance Standards set forth in the Performance Requirements Summary.
17.0 PERFORMANCE REQUIREMENTS SUMMARY
Task 1: Testbed Support for SmartGrid Time Synchronization for the Power Industry
18 | P a g e
Desired Output: An Excel spreadsheet of test results with graphical summary on timing errors including but not limited to phase error. A Word document detailing the tests and test procedures for validating the network. Input provided to Project Leader through meetings, email and other discussion opportunities.
Meetings attended as required. Phone and email discussions held as needed. Presentation (in Power Point or Keynote) describing the Smart Grid scenario. An Excel Spreadsheet with log of timing errors acquired from various scenarios in the timing testbed used for the simulation. Version controlled source code and executable of RT-Lab. Demo of the simulation. Word document details the automation protocol performance and a presentation and demo of the protocol.
Monitoring Method: Reviewed by COR.
Performance Standard: Excel spreadsheet of test results with graphical summaries detailing the timing uncertainties of the PTP testbed in normal operation. The Contractor responds promptly to phone calls and emails and is in attendance at meetings. Any written communication is in grammatically correct
English and delivered on time. Present and demonstrate to the Smart Grid team. The source code should execute successfully.
Task 2: Cloud Computing and Meaningful Use Tool Development
Desired Output: Update the Redmine application with status of tasks assigned by the COR. Redmine application will be provided by NIST and tasks assigned by the COR. Input provided to COR through meetings, email and other discussion opportunities. Meetings attended as required. Phone and email discussions held as needed. Reports provided on time and technically correct. Software management is provided to all developers and projects. The software tools provide the capability in accordance with the specified implementation guides (provided by COR).
Performance Standard: Redmine status details all the status, test methods, scenarios and services necessary as required in Task 2. The Contractor responds promptly to phone calls and emails and is in attendance at meetings. Any written communication is in grammatically correct English and delivered on time in correct format. The software tool is functionally correct, well-documented and easy to use. The software tool system is in-line with industry-acceptable practices and techniques.
Source code and software release will be made publicly available. The software is functionally correct, well-documented and easy to use. The software tool follows NIST practices which will be explained by the Project Lead at start of contract.
Task 3: Composition and Interoperability of Components in Cyber-Physical Cloud Computing
Systems
Desired Output: Update the Redmine application with status of tasks assigned by the COR. Redmine application will be provided by NIST and tasks assigned by the COR. Input provided to COR through meetings, email and other discussion opportunities. Meetings attended as required. Phone and email discussions held as needed. Reports provided on time and technically correct. Software management
19 | P a g e is provided to all developers and projects. The software tools provide the capability in accordance with the specified implementation guides (provided by COR).
Performance Standard: Redmine status details all the status, test methods, scenarios and services necessary as required in Task 3. The Contractor responds promptly to phone calls and emails and is in attendance at meetings. Any written communication is in grammatically correct English and delivered on time in correct format. The software management is functionally correct, well-documented and easy to use. The software management system is in-line with industry-acceptable practices and techniques. Source code and software release will be made publicly available. The software is functionally correct, well-documented and easy to use. The software system follows
NIST practices which will be explained by the Project Lead at start of contract.
File details come from the government source that posted it. Updated .