Module 15 - A313b

A313b: Specifying Requirements for ESS Systems Based on NTCIP 1204 v03 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 v03 Standard. See extended text description below.

(Extended Text Description: Large graphic cover page with dark blue background with the title in white letters “A313b - Specifying Requirements for ESS Systems Based on NTCIP 1204 v03 Standard.” At the middle left is the “Standards ITS Training” logo with a white box and letters in blue and green. The words “Student Supplement” and “RITA Intelligent Transportation Systems Joint Program Office” in white lettering are directly underneath the logo. Three light blue lines move diagonally across the middle of the blue background.)

 

A313b Specifying Requirements for ESS Systems Based on NTCIP 1204 v03 Standard

 

Table of Contents

Purpose - 2
NTCIP 1204 History- 3
NTCIP 1203 v02-Table of Contents - 3
Curriculum Path-Showing Prerequisites to A313b (Requirements) - 4
NTCIP 1204 v03 – Table of Contents (Requirements section only) - 5
NTCIP 1204 v03-Protocol Requirements List (PRL) - 7
NTCIP 1204 v03-Protocol Requirements List (PRL) – Supplemental Table -13
Glossary - 14
References - 16

 

Purpose

This participant supplement provides additional information for the Professional Capacity Building (PCB) Module A313b – Specifying Requirements for ESS Systems Based on NTICP 1204 v03 Standard.

The focus of this module is to assist technical staff in specifying clear requirements from the list of requirements that exist in NTCIP 1204 v03 ESS and in meeting identified user needs. This module will continue to provide participants with information on how to identify the appropriate use of the NTCIP 1204 standard and acquire an ESS system based on what the user is seeking to accomplish as identified by tracing the user needs to the requirements with support from tools and resources such as a Requirements Traceability Matrix (RTM) and Protocol Requirements List (PRL) in following a systems engineering process (SEP). The module will review the pros and cons of selecting requirements not covered by the standard and the need to avoid an orphaned user need or requirement for their system.

This module also helps the user understand the scope of the ESS standard and its versions in continuation with the previous module, A313a. This module is to be placed in the context of the SE process as well as in the acquisition curriculum path with I101, A101, A102, A201, and A313a being the prerequisites. This completes the acquisition life cycle leading to the user being able to write specifications. The logical next step for the participant is to consider modules in the testing life cycle, which are T101, T201, and T202, which lead up to the module T313: Applying Your Test Plan to the NTCIP 1204 v03 ESS Standard and other testing modules still to be developed. 


NTCIP 1204 History

 

NTCIP 1204 v03 – Table of Contents

Section 1 General
Section 2 Concept of Operations
Section 3 Functional Requirements
Section 4 Dialogs
Section 5 Object Definitions (Management Information Base)
Annex A Requirements Traceability Matrix (RTM)
Annex B Object Tree
Annex C Test Procedures
Annex D Documentation of Revisions
Annex E User Requests
Annex F Generic Clauses
Annex G Encoding of Sample Block Objects
Annex H Controller Configuration Objects

 

Curriculum Path – Showing Prerequisites to A313b (Requirements)

Curriculum Path - Showing Prerequisites to A313b

(Extended Text Description: A graphical illustration indicating the sequence of training modules for the standards related to specifying environmental sensor stations (ESS). Each module is represented by a box with the name of the module in it and an arrow showing the logical flow of the modules and the current module highlighted. The first box is labeled “I101 Using ITS Standards: An Overview.” An arrow from this box connects it to a highlighted box labeled “A101 Introduction to Acquiring Standards-based ITS Systems,” representing this module. An arrow from this box connects it to a box labeled “A102 Introduction to User Needs Identification.” An arrow from this box connects it to a box located at the start of the next line labeled “A201 Details on Acquiring Standards-based ITS Systems.” An arrow from this box connects it to a box labeled “A313a Understanding User Needs for ESS Systems Based on NTCIP 1204 v03 Standard.” Finally, an arrow from this box connects it to a box labeled “A313b Specifying Requirements for NTCIP 1204 v03.”)


NTCIP 1204 v03 – Table of Contents (Requirements section only)

The following is a copy of the table of contents for Sections 3 and 4 of NTCIP 1204 v3 provided as an overview, with particular emphasis on Sections 3.4, 3.5, and 3.6, which are shown with four-level heading contents.  Sections 3 and 4 are the sections for the functional requirements and the dialogs, with the emphasized subsections showing the headings for the architectural requirements, data exchange requirements, and the supplemental requirements supported by the standard.

SECTION 3 FUNCTIONAL REQUIREMENTS [NORMATIVE] - 18

3.1 Tutorial [Informative] -18
3.2 Scope of the Interface [Informative] - 19
3.3 3.3.1 User Needs Column - 19
3.3.2 Requirements Column - 19
3.3.3 Conformance Column - 19
3.3.4 Project Requirement Column - 20
3.3.5 Additional Project Requirements Column - 21
3.3.6 Instructions for Completing the PRL - 21
3.3.7 Protocol Requirements List (PRL) Table - 22
3.3.8 Protocol Requirements List—Supplemental Table - 33
Protocol Requirements List - 19
3.4 Architectural Requirements - 34
3.5 Data Exchange Requirements - 34
3.5.1 ESS Manager Requirements- 34
3.5.2 Sensor Manager Requirements - 35
3.5.3 PTS Manager Requirements - 40
3.5.4 Backward Compatibility Requirements - 41
Supplemental Requirements - 42
3.6.1 Required Number of Atmospheric Pressure Sensors- 43
3.6.2 Required Number of Wind Sensors - 43
3.6.3 Required Number of Temperature Sensors - 43
3.6.4 Required Number of Humidity Sensors - 43
3.6.5 Required Number of Precipitation Sensors - 43
3.6.6 Required Number of Solar Radiation Sensors - 43
3.6.7 Required Number of Visibility Sensors - 43
3.6.8 Required Number of Pavement Sensors - 43
3.6.9 Active Pavement Treatment Sensors - 43
3.6.10 Passive Pavement Treatment Sensors - 43
3.6.11 Required Number of Subsurface Sensors - 44
3.6.12 Required Number of Pavement Treatment Products- 44
3.6.13 Required Number of Carbon Monoxide Sensors - 44
3.6.14 Required Number of Carbon Dioxide Sensors - 44
3.6.15 Required Number of Nitrous Oxide Sensors - 44
3.6.16 Required Number of Nitrogen Dioxide Sensors - 44
3.6.17 Required Number of Sulfur Dioxide Sensors - 44
3.6.18 Required Number of Ozone Sensors - 44
3.6.19 Required Number of Small Particulate Matter Sensors - 45
3.6.20 Required Number of Snapshot Cameras - 45
3.6.21 Maximum Response Time for Requests - 45
3.6.22 Required Number of Water Level Sensors - 45
3.6.23 Support Camera Number in Filename - 45
3.6.24 Support Sequence Number in Filename - 45
3.6.25 Support Date in Filename - 45
3.6.26 Support Time in Filename - 45
3.6.27 Support Time in Filename - 45

SECTION 4 DIALOGS [NORMATIVE]- 46

4.1 Tutorial [Informative] - 47
4.2 Specified Dialogs - 48
4.2.1 Capture Snapshot Image- 48
4.2.2 Retrieve Snapshot - 48
4.2.3 Delete Snapshot- 49
4.2.4 Copy Snapshot—Deprecated in v03- 49
4.2.5 Retrieve Stationary Pavement Treatment Configuration - 49
4.2.6 Retrieve Icing Conditions—Passive - 49
4.2.7 Configure Stationary Pavement Treatment System - 50
4.2.8 Configure Passive Ice Detection Logic- 50
4.2.9 Configure Mobile Pavement Treatment System - 50
4.2.10 Configure Snapshot Camera - 51
4.2.11 Retrieve Snapshot Camera Configuration - 51
4.2.12 Retrieve Precipitation Presence- 51
4.2.13 Retrieve Solar Radiation - 52
4.2.14 Retrieve Pavement Surface Condition - 52
4.2.15 Retrieve Icing Conditions—Active - 52
4.3 State Transition Diagrams - 52
4.3.1 Pavement Treatment System State Transition Diagram - 53
4.4 Class Diagrams- 54
4.4.1 ESS Characteristics - 55
4.4.2 Pressure Sensor - 56
4.4.3 Wind Data - 57
4.4.4 Temperature - 57
4.4.5 Precipitation - 58
4.4.6 Radiation - 60
4.4.7 Visibility - 61
4.4.8 Pavement Sensor Data - 61
4.4.9 Subsurface Data - 63
4.4.10 Air Quality Data - 64
4.4.11 Snapshot Data - 64
4.4.12 Pavement Treatment System- 66

 

TCIP 1204 v03 – Protocol Requirements List (PRL)

User Need ID

User Need

FR ID

Functional Requirement

Conformance

Project Requirement

Additional Project Requirements

2.4

Architectural Needs

M

Yes

 

2.4.1

Generic Architectural Needs

M

Yes

(See F.1.1)

2.5

Features

M

Yes

 

2.5.1

ESS Manager Features

M

Yes

 

2.5.1.1

Generic Features

M

Yes

(See F.1.2)

2.5.1.2

Monitor Door Status

O

Yes / No

 

 

 

3.5.1.2.1

Retrieve ESS Door Status

M

Yes / NA

 

2.5.1.3

Monitor Power

O

Yes / No

 

 

 

3.5.1.2.2

Retrieve Battery Status

O.6 (1..*)

Yes / No / NA

 

 

 

3.5.1.2.3

Retrieve Line Volts

O.6 (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

 

 

 

 

 

 

 

 

 

 

3.5.1.3.3

Retrieve Compressed Mobile Station Data

M

Yes / NA

 

2.5.2

Sensor Manager Features

O.1 (1..*)

Yes / No

 

2.5.2.1 (Weather)

Monitor Weather Conditions

O.2 (1..*)

Yes / No / NA

 

2.5.2.1.1 (Pressure)

Monitor Atmospheric Pressure

O.3 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.2.1

Retrieve Atmospheric Pressure

M

Yes / NA

 

 

 

3.6.1

Required Number of Atmospheric Pressure Sensors

M

Yes / NA

The ESS shall support at least ____ atmospheric pressure sensors.

2.5.2.1.2 (Wind)

Monitor Winds

O.3 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.2.2

Retrieve Wind Data

M

Yes / NA

 

 

 

3.6.2

Required Number of Wind Sensors

M

Yes / NA

The ESS shall support at least ____ wind sensors.

2.5.2.1.3 (Temperature)

Monitor Temperature

O.3 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.2.3

Retrieve Temperature

M

Yes / NA

 

 

 

3.5.2.3.2.4

Retrieve Daily Minimum and Maximum Temperature

M

Yes / NA

 

 

 

3.6.3

Required Number of Temperature Sensors

M

Yes / NA

The ESS shall support at least ____ temperature sensors (1..255).

2.5.2.1.4

Monitor Humidity

O.3 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.2.5

Retrieve Humidity

M

Yes / NA

 

 

 

3.6.4

Required Number of Humidity Sensors

M

Yes / NA

The ESS shall support at least ____ humidity sensors.

2.5.2.1.5

Monitor Precipitation

O.3 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.2.6.1

Retrieve Precipitation Presence

M

Yes / NA

 

 

 

3.5.2.3.2.6.2

Retrieve Precipitation Rates

O

Yes / No / NA

 

 

 

3.5.2.3.2.6.3

Retrieve Precipitation Totals

O

Yes / No / NA

 

 

 

3.5.2.3.5.2

Retrieve Precipitation Situation

M

Yes / NA

 

 

 

3.6.5

Required Number of Precipitation Sensors

M

Yes / NA

The ESS shall support at least ____ precipitation sensors.

2.5.2.1.6

Monitor Solar Radiation

O.3 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.2.7

Retrieve Solar Radiation

M

Yes / NA

 

 

 

3.6.6

Required Number of Solar Radiation Sensors

M

Yes / NA

The ESS shall support at least ____ solar radiation sensors.

2.5.2.1.7

Monitor Visibility

O.3 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.2.8

Retrieve Visibility

M

Yes / NA

 

 

 

3.6.7

Required Number of Visibility Sensors

M

Yes / NA

The ESS shall support at least ____ visibility sensors.

2.5.2.1.8

View Weather Image

O

Yes / No / NA

 

 

 

3.5.2.1.9

Configure Snapshot Camera

M

Yes / NA

 

 

 

3.5.2.3.8

Retrieve Snapshot

M

Yes / NA

Upon ESS delivery the FTP username shall be ____________. Upon ESS delivery, the FTP password shall be __________.

 

 

3.5.2.3.9

Retrieve Snapshot Camera Configuration

M

Yes / NA

 

 

 

3.5.2.4.1

Capture Snapshot Image

M

Yes / NA

 

 

 

3.5.2.4.2

Delete Snapshot

M

Yes / NA

 

 

 

3.5.2.4.3

Copy Snapshot

M

Yes / NA

 

 

 

3.6.20

Required Number of Snapshot Cameras

M

Yes / NA

The ESS shall support at least ____ snapshot cameras (1..255).

 

 

3.6.23

Support Camera Number in Filename

O

Yes / No / NA

 

 

 

3.6.24

Support Sequence Number in Filename

O

Yes / No / NA

 

 

 

3.6.25

Support Date in Filename

O

Yes / No / NA

 

 

 

3.6.26

Support Time in Filename

O

Yes / No / NA

 

 

 

3.6.27

Support Long Filenames

O

Yes / No / NA

 

2.5.2.2 (Pavement)

Monitor Pavement

O.2 (1..*)

Yes / No / NA

 

2.5.2.2.1

Monitor Pavement Surface Condition

M

Yes / NA

 

 

 

3.5.2.1.6

Configure Pavement Sensor

M

Yes / NA

 

 

 

3.5.2.3.3.1

Retrieve Pavement Surface Condition

M

Yes / NA

 

 

 

3.5.2.3.3.4

Retrieve Adjacent Snow Depth

O

Yes / No / NA

 

 

 

3.5.2.3.3.5

Retrieve Roadway Snow Depth

O

Yes / No / NA

 

 

 

3.5.2.3.3.6

Retrieve Roadway Ice Thickness

O

Yes / No / NA

 

 

 

3.6.8

Required Number of Pavement Sensors

M

Yes / NA

The ESS shall support at least ____ pavement sensors (1..255).

2.5.2.2.2 (Icing)

Monitor Icing Conditions

O

Yes / No / NA

 

 

 

3.5.2.1.8

Configure Passive Ice Detection Logic

Passive:M

Yes / NA

 

 

 

3.5.2.3.3.2

Retrieve Icing Conditions—Active

Active:M

Yes / NA

 

 

 

3.5.2.3.3.3

Retrieve Icing Conditions—Passive

Passive:M

Yes / NA

 

 

 

3.6.9 (Active)

Active Pavement Treatment Sensors

Icing:O.5 (1..2)

Yes / No / NA

 

 

 

3.6.10 (Passive)

Passive Pavement Treatment Sensors

Icing:O.5 (1..2)

Yes / No / NA

 

2.5.2.2.3

View Pavement Image

O

Yes / No / NA

 

 

 

3.5.2.1.9

Configure Snapshot Camera

M

Yes / NA

 

 

 

3.5.2.3.8

Retrieve Snapshot

M

Yes / NA

Upon ESS delivery the FTP username shall be ____________. Upon ESS delivery, the FTP password shall be __________.

 

 

3.5.2.3.9

Retrieve Snapshot Camera Configuration

M

Yes / NA

 

 

 

3.5.2.4.1

Capture Snapshot Image

M

Yes / NA

 

 

 

3.5.2.4.2

Delete Snapshot

M

Yes / NA

 

 

 

3.5.2.4.3

Copy Snapshot

M

Yes / NA

 

 

 

3.6.20

Required Number of Snapshot Cameras

M

Yes / NA

The ESS shall support at least ____ snapshot cameras (1..255).

 

 

3.6.23

Support Camera Number in Filename

O

Yes / No / NA

 

 

 

3.6.24

Support Sequence Number in Filename

O

Yes / No / NA

 

 

 

3.6.25

Support Date in Filename

O

Yes / No / NA

 

 

 

3.6.26

Support Time in Filename

O

Yes / No / NA

 

 

 

3.6.27

Support Long Filenames

O

Yes / No / NA

 

2.5.2.3 (Subsurface)

Monitor Subsurface Conditions

O.2 (1..*)

Yes / No / NA

 

 

 

3.5.2.1.7

Configure Subsurface Sensor

Subsurface:M

Yes / NA

 

 

 

3.5.2.3.4.1

Retrieve Basic Subsurface Conditions

M

Yes / NA

 

 

 

3.5.2.3.4.2

Retrieve Subsurface Moisture

O

Yes / No / NA

 

 

 

3.6.11

Required Number of Subsurface Sensors

M

Yes / NA

The ESS shall support at least ____ subsurface sensors (1..255).

2.5.2.4

Monitor Human Readings

O.2 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.5.1

Retrieve Wind Situation

M

Yes / NA

 

 

 

3.5.2.3.5.2

Retrieve Precipitation Situation

M

Yes / NA

 

 

 

3.5.2.3.5.3

Retrieve Cloud Situation

M

Yes / NA

 

 

 

3.5.2.3.5.4

Retrieve Visibility Situation

M

Yes / NA

 

 

 

3.5.2.3.5.5

Retrieve Ground State

O

Yes / No / NA

 

 

 

3.5.2.3.5.6

Retrieve Pavement State

O

Yes / No / NA

 

2.5.2.5

Monitor Water Level

O.2 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.7

Retrieve Water Level

M

Yes / NA

 

 

 

3.6.22

Required Number of Water Level Sensors

M

Yes / NA

The ESS shall support at least ____ water level sensors (1..255).

2.5.2.6 (Air)

Monitor Air Quality and Biohazards

O.2 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.6.1 (CO)

Retrieve Carbon Monoxide Reading

O.4 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.6.2 (CO2)

Retrieve Carbon Dioxide Reading

O.4 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.6.3 (N2O)

Retrieve Nitrous Oxide Reading

O.4 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.6.4 (NO2)

Retrieve Nitrogen Dioxide Reading

O.4 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.6.5 (SO2)

Retrieve Sulfur Dioxide Reading

O.4 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.6.6 (O3)

Retrieve Ozone Reading

O.4 (1..*)

Yes / No / NA

 

 

 

3.5.2.3.6.7 (PM10)

Retrieve Small Particulate Matter Reading

O.4 (1..*)

Yes / No / NA

 

 

 

3.6.13

Required Number of Carbon Monoxide Sensors

CO:M

Yes / NA

The ESS shall support at least ____ carbon monoxide sensors.

 

 

3.6.14

Required Number of Carbon Dioxide Sensors

CO2:M

Yes / NA

The ESS shall support at least ____ carbon dioxide sensors.

 

 

3.6.15

Required Number of Nitrous Oxide Sensors

N2O:M

Yes / NA

The ESS shall support at least ____ nitrous oxide sensors.

 

 

3.6.16

Required Number of Nitrogen Dioxide Sensors

NO2:M

Yes / NA

The ESS shall support at least ____ nitrogen dioxide sensors.

 

 

3.6.17

Required Number of Sulfur Dioxide Sensors

SO2:M

Yes / NA

The ESS shall support at least ____ sulfur dioxide sensors.

 

 

3.6.18

Required Number of Ozone Sensors

O3:M

Yes / NA

The ESS shall support at least ____ ozone sensors.

 

 

3.6.19

Required Number of Small Particulate Matter Sensors

PM10:M

Yes / NA

The ESS shall support at least ____ small particulate matter sensors.

2.5.2.7

Monitor Mobile Weather Profile

O

Yes / No / NA

 

 

 

3.5.2.3.1

Retrieve Weather Profile with Mobile Sources

M

Yes / NA

 

 

 

F.2.1.2.1

Retrieve Current Configuration of Logging Service

M

Yes / NA

 

 

 

F.2.1.2.2

Configure Logging Service

M

Yes / NA

 

 

 

F.2.1.2.3

Retrieve Logged Data

M

Yes / NA

 

 

 

F.2.1.2.4

Clear Log

M

Yes / NA

 

 

 

F.2.1.2.5

Retrieve Capabilities of Event Logging Service

M

Yes / NA

 

 

 

F.2.1.2.6

Retrieve Total Number of Logged Events

M

Yes / NA

 

2.5.3

Pavement Treatment System Manager Features

O.1 (1..*)

Yes / No / NA

 

2.5.3.1

Manage Stationary Spray System

Mobile:X; M

Yes / No / NA

 

 

 

3.5.3.1.1

Retrieve Stationary Pavement Treatment Configuration

M

Yes / NA

 

 

 

3.5.3.1.2

Configure Stationary Pavement Treatment System

M

Yes / NA

 

 

 

3.5.3.2.1

Retrieve Pavement Treatment Status

M

Yes / NA

 

 

 

3.5.3.4.1

Set PTS Operational Mode

M

Yes / NA

 

 

 

3.5.3.4.2

Manually Activate PTS Sprayer

M

Yes / NA

 

 

 

3.6.12

Required Number of Pavement Treatment Products

M

Yes / NA

The ESS shall support at least ____ pavement treatment products (1..255).

2.5.3.2

Manage Mobile Spray System

Mobile: M

Yes / No / NA

 

 

 

3.5.3.1.3

Retrieve Mobile Pavement Treatment Configuration

M

Yes / NA

 

 

 

3.5.3.1.4

Configure Mobile Pavement Treatment System

O

Yes / No / NA

 

2.6

Backwards Compatibility Needs

O

Yes / No

 

2.6.1

Backwards Compatibility with Version 1

O

Yes / No / NA

 

 

 

3.5.4.1

Version 1 Wind Sensor Meta Data

O

Yes / No / NA

 

 

 

3.5.4.2

Version 1 Average Wind Sensor Data

O

Yes / No / NA

 

 

 

3.5.4.3

Version 1 Spot Wind Sensor Data

O

Yes / No / NA

 

 

 

3.5.4.4

Version 1 Wind Gust Data

O

Yes / No / NA

 

 

 

3.5.4.5

Version 1 Wind Situation

O

Yes / No / NA

 

 

 

3.5.4.6

Version 1 Water Depth

O

Yes / No / NA

 

 

 

3.5.4.7

Version 1 Solar Radiation

O

Yes / No / NA

 

 

 

3.5.4.8

Version 1 Surface Water Depth

O

Yes / No / NA

 

 

 

3.5.4.9

Version 1 Surface Conductivity

O

Yes / No / NA

 

2.6.2

Backwards Compatibility with Version 2

O

Yes / No

 

 

 

3.5.4.10

Version 2 Station Meta Data Block

O

Yes / NA

 

 

 

3.5.4.11

Version 2 Weather Block

O

Yes / No / NA

 

 

 

3.5.4.12

Version 2 Pavement Block

O

Yes / No / NA

 

F.1.1

Generic Architectural Needs

M

Yes

 

F.1.1.1 (ESS)

Provide Live Data

M

Yes

 

 

 

F.2.1.1.1

Retrieve Data

M

Yes

 

 

 

F.2.1.1.2

Deliver Data

M

Yes

 

 

 

F.2.1.1.3

Explore Data

M

Yes

 

 

 

3.6.21

Maximum Response Time for Requests

M

Yes

The Maximum Response Time for all requests shall be ___ milliseconds.

F.1.1.2 (Compressed)

Provide Compressed Data

Mobile:M; O

Yes / No

 

 

 

3.5.1.1.2

Retrieve Compressed Station Metadata

M

Yes

 

 

 

3.5.2.3.2.9

Retrieve Compressed Weather Data

Weather:M

Yes / NA

 

 

 

3.5.2.3.3.7

Retrieve Compressed Pavement Condition Data

Pavement:M

Yes / NA

 

 

 

3.5.2.3.4.3

Retrieve Compressed Subsurface Condition Data

Subsurface:M

Yes / NA

 

 

 

3.5.2.3.6.8

Retrieve Compressed Air Quality Data

Air:M

Yes / NA

 

 

 

3.6.21

Maximum Response Time for Requests

M

Yes

The Maximum Response Time for all requests shall be ___ milliseconds.

F.1.1.3

Provide Off-line Log Data

Mobile:M ; O

Yes / No

 

 

 

F.2.1.2.1

Retrieve Current Configuration of Logging Service

M

Yes / NA

 

 

 

F.2.1.2.2

Configure Logging Service

M

Yes / NA

 

 

 

F.2.1.2.3

Retrieve Logged Data

M

Yes / NA

 

 

 

F.2.1.2.4

Clear Log

M

Yes / NA

 

 

 

F.2.1.2.5

Retrieve Capabilities of Event Logging Service

M

Yes / NA

 

 

 

F.2.1.2.6

Retrieve Total Number of Logged Events

M

Yes / NA

 

 

 

F.2.2.1.5.1

Set Time

M

Yes / NA

 

 

 

F.2.2.1.5.2

Retrieve Current Time

M

Yes / NA

 

 

 

3.6.21

Maximum Response Time for Requests

M

Yes

The Maximum Response Time for all requests shall be ___ milliseconds.

 

 

F.2.3.1†

Supplemental Requirements for Event Monitoring

M

Yes / NA

 

F.1.2

Generic Features

M

Yes

 

F.1.2.1

Retrieve the Device Identity

M

Yes

 

 

 

3.5.1.1.1

Retrieve ESS Characteristics

M

Yes

 

 

 

3.5.1.1.3

Configure ESS Manager

M

Yes

 

 

 

3.5.2.1.1

Retrieve Atmospheric Pressure Height

Pressure:M

Yes / NA

 

 

 

3.5.2.1.2

Retrieve Meta-Data for Each Wind Sensor

Wind:M

Yes / NA

 

 

 

3.5.2.1.3

Retrieve Temperature Sensor Meta-Data

Temperature:M

Yes / NA

 

 

 

3.5.2.1.4

Retrieve Pavement Sensor Meta-Data

Pavement:M

Yes / NA

 

 

 

3.5.2.1.5

Retrieve Subsurface Sensor Meta-Data

Subsurface:M

Yes / NA

 

 

 

F.2.2.1.1

Retrieve Device Component Information

M

Yes

 

 

 

F.2.2.1.2

Retrieve Device Configuration Identifier

M

Yes

 

 

 

F.2.2.1.3

Retrieve Supported Standards

M

Yes

 

 

 

F.2.2.1.4

Retrieve System Name

M

Yes

 

F.1.2.2

Control External Devices

O

Yes / No

 

 

 

F.2.2.1.6

Retrieve External Port Information

M

Yes / NA

 

 

 

F.2.2.1.7

Configure Port Information

M

Yes / NA

 

 

 

F.2.2.2.1

Monitor Status of External Device

M

Yes / NA

 

 

 

F.2.2.4.1

Control External Device

M

Yes / NA

 

 

 

F.2.3.2

Required Number of Auxiliary Ports

M

Yes / NA

The ESS shall support at least ____ binary analog output ports (1..255).

 

NTCIP 1204 v03 – Protocol Requirements List (PRL) – Supplemental Table

Supplemental Requirement ID

Supplemental Requirement

Conformance

Project Requirement

Additional Project Requirements

F.2.3

Generic Supplemental Requirements

 

 

 

F.2.3.1

Supplemental Requirements for Event Monitoring

M

Yes / NA

 

F.2.3.1.1

Record and Timestamp Events

M

Yes / NA

 

F.2.3.1.2

Support a Number of Event Classes

M

Yes / NA

The ESS shall support at least ____ event classes (1..255).

F.2.3.1.3

Support a Number of Event Types to Monitor

M

Yes / NA

The ESS shall support at least ____ event types (1..255).

F.2.3.1.4

Support Monitoring of Event Types

M

Yes / NA

 

F.2.3.1.4.1

Support On-Change Events

M

Yes / NA

 

F.2.3.1.4.2

Support Greater Than Events

M

Yes / NA

 

F.2.3.1.4.3

Support Less Than Events

M

Yes / NA

 

F.2.3.1.4.4

Support Hysteresis Events

M

Yes / NA

 

F.2.3.1.4.5

Support Periodic Events

M

Yes / NA

 

F.2.3.1.4.6

Support Bit-flag Events

M

Yes / NA

 

F.2.3.1.5

Support Event Monitoring on Any Data

M

Yes / NA

 

F.2.3.1.6

Support a Number of Events to Store in Log

M

Yes / NA

The ESS shall support storing at least ____ events in the log (1..65535).

 

Glossary

Term

Definition

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.

Binary Universal Form for the Representation of Meteorological Data (BUFR)

A definition for a binary data format maintained by the World Meteorological Organization (WMO). BUFR was designed to be portable, compact, and universal. Any kind of data can be represented, along with its specific spatial/temporal context and any other associated metadata. In the WMO terminology, BUFR belongs to the category of table-driven code forms, where the meaning of data elements is determined by referring to a set of tables that are kept and maintained separately from the message itself.

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 for 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.

Download

To download means to receive data to a local system from a remote system or to initiate such a data transfer. Examples of a remote system from which a download might be performed include a Web server, FTP server, e-mail server, or other similar systems. A download can mean either any file that is offered for downloading or that has been downloaded, or the process of receiving such a file.

Environmental Sensor Systems (ESS) – same as RWIS
NOTE—The abbr ESS may
also be used as a plural.

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).

Informative

Information that identifies a document, introduces its content, and explains its background, its development and its relationship with other documents; or information that provides additional information intended to assist the understanding or use of the document (see normative).

Interchangeability

A condition that exists when two or more items possess such functional and physical characteristics as to be equivalent in performance and durability and are capable of being exchanged one for the other without alteration of the items themselves, or adjoining items, except for adjustment, and without selection for fit and performance.

Interoperability

The ability of two or more systems or components to exchange information and use the information that has been exchanged.

Normative

Information that describes the scope of the document and that set out provisions (ISO).  Normative elements are considered to be a prescriptive part of the standard (see informative).

Protocol Requirements List (PRL)

A table mapping user needs with their associated requirements.  This table allows procurement personnel to specify the desired features of an ESS or it could be used by a manufacturer to document the features supported by their implementation.

Requirement

A condition or capability needed by a user to solve a problem or achieve an objective.

Remote Processor Unit (RPU)

A field processor that collects data from sensors and can communicate the collected data to other computers; the processor may also process the collected data and/or control equipment.

Requirements Traceability Matrix (RTM)

A table that links the requirements to the corresponding dialogs and objects.

Road/Weather Information System (RWIS) – same as ESS

The collection of RPUs and sensors connected to a central system for analysis and use by maintenance personnel and transportation system managers.

Sensor

A device that is capable of detecting a condition and reporting the result to an RPU.

Specification

A document that references a standard either to define the capabilities of a component (e.g., a specification sheet) or to define the required capabilities of a component being procured (e.g., a procurement specification).

Systems Engineering

An interdisciplinary approach and means to enable the realization of successful systems. (INCOSE)


 

References

Environmental Sensor Systems

 

Systems Engineering

 

Testing