Module 15 - A313b

A313b: Specifying Requirements for ESS Systems Based on NTCIP 1204 v04 Standard

HTML of the Student Supplement

(Note: This document has been converted from the Student Supplement to 508-compliant HTML. The formatting has been adjusted for 508 compliance, but all the original text content is included, plus additional text descriptions for the images, photos and/or diagrams have been provided below.)

 

A313b: Specifying Requirements for ESS Systems Based on NTCIP 1204 Standard v04

 

Table of Contents

Module Description - 2

Introduction/Purpose - 2

Case Study - 3

Samples/Examples - 4

References to Standards - 6

Glossary - 6

References - 7

Study Questions - 8

Icon Guide - 9

 

1. Module Description

This module is based on the recently released NTCIP 1204 v04 (May 2016) standard that covers Environmental Sensor Stations (ESS) and Road Weather Information System (RWIS).

The purpose of this updated module (the previous module was based on v03 of the standard) is to incorporate necessary changes such as new ESS user needs/requirements and ESS test procedures provided in recently completed work on NTCIP 1204 Standard v04 and reorganized documentation from the previous v03. The module provides participants with information on how to identify the appropriate use of the latest NTCIP 1204 Standard v04 and acquire an ESS system based on what the user is seeking to accomplish; it also provides participants with information on how to specify requirements.

ESS-Related Training Modules and Prerequisites

Agencies preparing a project specification for Environmental Sensor Stations (ESS) based on NTCIP 1204 v04 will need to consult the following three updated sequential modules:

  1. A313a: Understanding User Needs for ESS Systems Based on NTCIP 1204 Standard v04
  2. A313b: Specifying Requirements for ESS Systems Based on NTCIP 1204 Standard v04
  3. T313: Applying Your Test Plan to the Environmental Sensor Stations Based on NTCIP 1204 Standard v04

This module will be placed in the context of the systems engineering process as well in the acquisition curriculum path, with I101, A101, A102, and A201 being the prerequisites. This completes the acquisition lifecycle leading to the user being able to write specifications with a focus on ESS user needs in the previous module, followed by ESS requirements in this module. The logical next step for the participant is to consider modules in the testing lifecycle, which begins with modules T101, T201, and T202, and T203 and T204, which lead up to the T313 module: Applying Your Test Plan to the Environmental Sensor Stations Based on NTCIP 1204 Standard v04.

 

2. Introduction to ESS and NTCIP 1204 ESS Standard

Environmental Sensor Stations (ESS) are ground -based or pole-mounted sensors that collect base-level raw weather data from roadways sections or regions and transmit data to a central or field location, where they are used as part of a Road Weather Information System (RWIS). The module provides a brief background on RWIS/ESS and shows how agencies use weather information to make decisions and issue advisories to motorists and stakeholders.

NTCIP 1204 v04, an NTCIP standards publication, identifies and defines how a management station interfaces with a field device to control and monitor pavement sensors, weather stations, air quality sensors, and other equipment related to the monitoring of and response to environmental conditions in an NTCIP-conformant fashion. NTCIP 1204 v04 uses only metric units. NTCIP 1204 v04 provides definitions of data elements for environmental sensor data, including weather data, pavement condition data, water level data, and air quality data. NTCIP 1204 v04 defines

requirements that are applicable to all NTCIP environments and it also contains optional and conditional sections that are applicable to specific environments for which they are intended.

Types of ESS Requirements

As shown below, the ESS standard supports three types of ESS requirements to fulfill user needs.

Section 3 Functional Requirements [Normative] - 23

3.1 Tutorial [Informative] - 23

3.2 Scope of the Interface [Informative] - 23

3.3 Protocol Requirements List (PRL) - 24

3.3.1 Notation [Informative] - 24

3.3.2 Instructions for Completing the PRL [Informative] - 26

3.3.3 Protocol Requirements List (PRL) Table - 27

3.4 Architectural Requirements - 46

3.5 Data Exchange and Operational Environment Requirements - 46

3.5.1 ESS Manager Requirements - 46

3.5.2 Sensor Manager Requirements - 48

3.5.3 PTS Manager Requirements - 69

3.5.4 Backward Compatibility Requirements - 72

3.6 Supplemental Non-Communications Requirements - 75

3.6.1 Required Number of Atmospheric Pressure Sensors - 75

3.6.2 Required Number of Wind Sensors - 75

3.6.3 Required Number of Temperature Sensors - 76

3.6.4 Required Number of Humidity Sensors - 76

 

3. Case Study: Understanding How to Use the Protocol Requirements List (PRL) and Requirements Traceability Matrix (RTM)

Both PRL and RTM are required for a project specification and later for testing ESS systems.

PRL is a first step toward achieving a successful ESS system that is conformant to the ESS standard and ensuring an interoperable system that works as desired. Every ESS procurement specification must incorporate a PRL that meets project user needs and associated requirements. Readers are directed to familiarize themselves with the structure of the ESS PRL and learn how to prepare a project-level PRL.

The PRL provided under Section 3.3.3 maps the user needs defined in Section 2 to the requirements defined in Section 3. The following examples illustrate how a project-level PRL can be developed that includes user needs/requirements as a tailored version of what the standard provides, and how an RTM provides dialogs and objects necessary to fulfil a requirement.

This figure contains the following text and table. Please see the Extended Text Description below.

(Extended Text Description: This figure contains the following text and table:

Find Associated Requirements given by PRL has an arrow pointing to row 2.5.1.2 in the table below, which is highlighted, along with the text How it is to be done:

Protocol Requirements List (PRL)
User Need ID User Need FR ID Functional Requirement Conformance Support Additional Specifications
2.4 Architectural Meeds M Yes  
2.4.1 Generic Architectural Needs M Yes  
2.5 Fe atures   Yes  
2.5.1 ESS Manaqer Fealures M Yes  
2.5.1.1 Generic Features M Yes  
2.5.1.2 Monitor Door Status O Yes / No  
    3.5.1.2.1 Retrieve ESS Door Slatus M Yes / NA  
2.5.1.3 Monitor Power O Yes / No  
    3.5.1.2.2 Retrieve Battery Stains 0.1 (1..*) Yes / No / NA  
    3.5.1.2.3 Retrieve Line Volts 0.1 (1..*) Yes / No / NA  
2.5.1.4 Monitor Mobile Station Data Mobile :M Yes / NA  
    3.5.1.3.1 Retrieve Mobile ESS Movement M Yes / NA NTCIP 1204 v04 does not impose any accuracy requirements. Any accuracy requirements should be inserted here.
2.5.1.5 Deteimine ESS Type M Yes  
2.5.1.5.a
2.5.1.5.b
2.5.1 S.c (Mobile)
Permanent
Transportable
Mobile
0.2 (1)
0.2 (1)
0.2 (1)
Yes / No
Yes / No
Yes / No
 
  13.5.1.1.1 Retrieve ESS Characteristics M Yes  
2.5.1.6 Monitor the Status of the ESS 0 Yes / No  
    3.5.1.2.4 Retrieve ESS Stalus M Yes / NA  
2.5.2 Sensor Manager Fealures 0.3 (1...*) Yes / No  

)

Using Requirements Traceability Matrix (RTM) to Specify Dialogs and Objects

This figure contains the following text and table. Please see the Extended Text Description below.

(Extended Text Description: This figure contains the following text and table:

Requirements Traceability Matrix (RTM)

Requirement with ID points to the first two columns of the table. Standardized design that fulfills the requirement points to the content starting at G.1 and including rows 5.2.1 through 5.5.1. Design includes a Dialog, and Objects. The table is shown below:

Requirements Traceability Matrix (RTM)
FR ID Functional Requirement Dialog ID Object ID |Object Name Additional Specifications
3.4 Architectural Requirements
3.5 Data Exchange and Operational Environment Requirements
3.5.1 ESS Manager Requirements
3.5.1.1 ESS Configuration Requirements
3.5.1.1.1 Retrieve ESS Characteristics G.1      
      5.2.1 essNtcipCategory  
      5.2.2 essNtcipSiteDescription  
      5.3.1 essTypeofStation  
      5.4.1 essLatitude  
      5.4.2 essLongitude  
      5.5.1 essReferenceHeight  

)

 

4. Example of RTM Use

Requirement: 3.5.2.1.9 Configure Snapshot Camera

Upon request, the ESS shall store a textual description of the location and direction to which the camera points and the filename to be used when storing new snapshots.

a. Retrieve Snapshot

Upon request, the ESS shall return a copy of the specified snapshot image.

4.1.1. The following RTM entry shows how this requirement is managed with dialog and additional notes, if needed.

Using RTM to Specify Design for Retrieving Snapshot

Requirements Traceability Matrix (RTM)
FR ID Functional Requirement Dialog ID Object ID Object Name Additional Specifications
3.5.2.3.8 Retrieve Snapshot 4.2.2       Upon ESS delivery the FTP usemame shall be ___________
Upon ESS delivery, the FTP password be __________
Note: For agencies that restrict the use of FTP see Annex E 3 for additional information.
      5.17.1     <not an SNMP Object> Snapshotfilename.text
      5.17.2     <not an SNMP Object> Snapshotimage.frame

5.17.1 Filename

Definition> The name of the file in which the snapshot image is stored.
<Descriptive Name> Snapshot.filename:text
<Data Concept Type> Data Element

4.2. Image
<Definition> The graphic snapshot image. The storage format is not defined by this standard.
<DescriptiveName>Snapshot.image:frame
<Data Concept Type> Data Element

Summary of Key Steps to Achieve Conformance to Standard

  1. Secure user need support with selecting YES in PRL, making those requirements Mandatory
  2. RTM-identified dialogs, in proper sequence-order
  3. RTM-identified objects as allocated by standard
  4. Both PRL and RTM are required for Conformance to the standard

Implementations seeking to achieve interoperability must have selected same user needs-requirements-dialogs-objects.

 

5. References to Standards

 

6. Glossary

Term Definition
C2C Center to Center
C2F Center to Field
DMS Dynamic Message Signs
ESS Environmental Sensor Station
FMS Freeway Management System
MIB Management Information Base
NTCIP National Transportation Communications for ITS Protocols
PRL Protocol Requirements List
PTS Pavement Treatment Systems
RPU Remote Processor Unit
RTM Requirements Traceability Matrix
RWIS Road Weather Information System
SEP Systems Engineering Process
SNMP Simple Network Management Protocol
TMC Traffic Management Center
Agency Specification A document that has been prepared by an agency to define requirements for a subject item or process when procured by the agency.
Compliance A condition that exists when an item meets all of the requirements of an agency specification.
Concept of Operations A document that describes the purpose of a system project, including a description of the current and proposed system, as well as key user needs that the new system is required to address.
Conformance A condition that exists when an item meets all of the mandatory requirements as defined by a standard. It can be measured on the standard as a whole, which means that it meets all mandatory (and applicable conditional) requirements of the standard or on a feature level (i.e., it conforms to feature X as defined in section X.X.X), which means that it meets all mandatory (and applicable conditional) requirements of the feature.
Dialogs A sequence of information or message exchanges.
Environmental Sensor Station (ESS) A location that includes a remote processor unit (RPU) connected to one or more sensors for the collection of environmental or meteorological data. It may also include a pavement treatment system (PTS). Note: The acronym ESS may also be used as a plural.
Feature A service provided by/behavior of the device.
Protocol Requirements List (PRL) A table mapping user needs with their associated requirements. This table allows procurement personnel to specify the desired features of a DMS or can be used by a manufacturer to document the features supported by their implementation.
  Requirement is a condition or capability needed by a user to solve a problem or achieve an objective.
Specification The project-specific detailed requirements for a DMS to be purchased by an agency or a statement by a manufacturer defining the detailed features provided by the DMS. Within NTCIP 1203 v03, "specification" often refers to the text contained in the "Additional Project Requirements" column of the PRL.
Transportable In the context of an ESS, an ESS capable of being relocated, but its environmental sensors and pavement treatment devices do not operate while moving.
User Need The business or operational problem (opportunity) that must be fulfilled to justify purchase or use. While this is termed a "user need" within the NTCIP community, it reflects needs of all stakeholders.
Requirements Traceability Matrix (RTM) A table that links the requirements to the corresponding dialogs and objects.

 

7. References

 

8. Study Questions

1. Which of the following is a FALSE statement?

  1. ESS requirements are standardized by the standard
  2. RTM provides benefits to vendors only
  3. PRL provides standardized design
  4. NTCIP 1204 v04 is backward compatible to previous versions

2. Which of the following is a FALSE statement as applied to ESS?

  1. Remote Processing Unit (RPU) contains ESS Manager
  2. Sensor Manager collects data supplied by each sensor
  3. PRL allows users to select user needs and associated requirements
  4. Backward compatibility is not addressed by the PRL

3. Which of the following is NOT a correct statement as applied to communications interface specification?

  1. Project PRL lists standardized user needs
  2. Only PRL is necessary for conformance to standard
  3. PRL lists optional user needs
  4. RTM provides complete design

4. Which of the following is a CORRECT statement related to ESS extension?

  1. Extension will be conformant to the ESS standard
  2. Extension will break regional RWIS interoperability
  3. ESS implementation with extensions is manageable
  4. Extension may enable a remote operation of ESS field devices

5. Which is NOT a correct statement as applied to ESS Testing?

  1. Test procedures connect requirements to testing steps
  2. NTCIP 1204 v04 standard provides test procedures
  3. Test plan documentation includes test procedures
  4. Test planning is done at the testing stage

 

9. Icon Guide

The following icons are used throughout the module to visually indicate the corresponding learning concept listed below, and/or to highlight a specific point in the training material.

1) Background information: General knowledge that is available elsewhere and is outside the module being presented. This will be used primarily in the beginning of the slide set when reviewing information readers are expected to already know.

Background information icon indicates general knowledge that is available elsewhere and is outside the module being presented.

2) Tools/Applications: An industry-specific item a person would use to accomplish a specific task, and application of that tool to fit the need.

Tools/Applications icon. An industry-specific item a person would use to accomplish a specific task, and applying that tool to fit your need.

3) Remember: Used when referencing something already discussed in the module that is necessary to recount.

Remember icon. Used when referencing something already discussed in the module that is necessary to recount.

4) Refer to Student Supplement: Items or information that are further explained/detailed in the Student Supplement.

Supplement icon indicating items or information that are further explained/detailed in the Student Supplement.

5) Example: Can be real-world (case study), hypothetical, a sample of a table, etc.

Example icon. Can be real-world (case study), hypothetical, a sample of a table, etc.

6) Checklist: Used to indicate a process that is being laid out sequentially.

Checklist icon used to indicate a process that is being laid out sequentially.