Module 34 - A317b
A317b: Understanding Requirements for CCTV Systems Based on NTCIP 1205 Standard
HTML of the PowerPoint Presentation
(Note: This document has been converted from a PowerPoint presentation 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.)
Slide 1:
(Extended Text Description: Slide 1: Welcome - Graphic image of introductory slide. A large dark blue rectangle with a wide, light grid pattern at the top half and bands of dark and lighter blue bands below. There is a white square ITS logo box with words “Standards ITS Training” in green and blue on the middle left side. The word “Welcome” in white is to the right of the logo. Under the logo box are the words “RITA Intelligent Transportation Systems Joint Program Office.”)
Slide 2:
Welcome
Ken Leonard, Director
ITS Joint Program Office
(Extended Text Description: Intro Slide: Screen capture snapshot of RITA website - for illustration only. Below this image is a link to the current website: https://www.its.dot.gov/pcb - this screen capture snapshot shows an example from the RITA website from April 2013. At the top of the page it shows the RITA logo with the text U.S. Department of Transportation Research and Innovative Technology Administration - Intelligent Transportation Systems Joint Program Office - ITS Professional Capacity Building Program/Advanced ITS Education. Below the main site banner, it shows the main navigation menu with the following items: About, ITS Training, Knowledge Exchange, Technology Transfer, ITS in Academics, and Media Library. Below the main navigation menu, the page shows various content of the website, including a graphic image of professionals seated in a room during a training program. A text overlay has the text Welcome to ITS Professional Capacity Building. Additional content on the page includes a box entitled What's New and sections entitled Available E-Training (free), Free ITS Training and T3 Webinars. Again, this image serves for illustration only. The current website link is: https://www.its.dot.gov/pcb)
(Note: There is additional text attached to this slide that includes the following introductory information from Ken Leonard):
"ITS Standards can make your life easier. Your procurements will go more smoothly and you’ll encourage competition, but only if you know how to write them into your specifications and test them. This module is one in a series that covers practical applications for acquiring and testing standards-based ITS systems.
I am Ken Leonard, director of the ITS Joint Program Office for USDOT and I want to welcome you to our newly redesigned ITS standards training program of which this module is a part. We are pleased to be working with our partner, the Institute of Transportation Engineers, to deliver this new approach to training that combines web based modules with instructor interaction to bring the latest in ITS learning to busy professionals like yourself.
This combined approach allows interested professionals to schedule training at your convenience, without the need to travel. After you complete this training, we hope that you will tell colleagues and customers about the latest ITS standards and encourage them to take advantage of the archived version of the webinars.
ITS Standards training is one of the first offerings of our updated Professional Capacity Training Program. Through the PCB program we prepare professionals to adopt proven and emerging ITS technologies that will make surface transportation safer, smarter and greener which improves livability for us all. You can find information on additional modules and training programs on our web site ITS PCB Home
Please help us make even more improvements to our training modules through the evaluation process. We look forward to hearing your comments. Thank you again for participating and we hope you find this module helpful."
Slide 3:
Slide 4:
A317b:
Understanding Requirements for CCTV Systems Based on NTCIP 1205 Standard
Slide 5:
Instructor
Raman K. Patel, Ph.D., P.E.
President
RK Patel Associates, Inc.
New York City, NY, USA
Slide 6:
Target Audience
- Engineering staff
- Traffic Management Center (TMC)/Operations staff
- System developers
- Private and public sector users, including manufacturers
- Traveler and other information service providers
Slide 7:
Recommended Prerequisite(s)
I101 Using ITS Standards: An Overview
A101 Introduction to Acquiring Standards-based ITS Systems
A102 Introduction to User Needs Identification
A103 Introduction to ITS Standards Requirements Development
A201 Details On Acquiring Standards-based ITS Systems
A202 Identifying and Writing User Needs When ITS Standards Do Not Have SEP Content
A203 Writing Requirements When ITS Standards Do Not Have SEP Content
Slide 8:
Recommended Prerequisite(s) (cont.)
C101 Introduction to the Communications Protocols and Their Uses in ITS Applications
A317a Understanding User Needs for CCTV Systems Based on NTCIP 1205 Standard
Slide 9:
Curriculum Path (Non-SEP)
(Extended Text Description: A graphical illustration indicating the sequence of training modules for the standards that include Systems Engineering Process content. 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 "A202 Understanding and Writing User Needs when ITS Standards Do Not Have SEP Content and an arrow connects to the box labeled as "C101 Introduction to Communications Protocols and their Uses in ITS Applications. An arrow from this box connects to "A317a: Understanding User Needs for CCTV Systems Based on NTCIP 1205 Standard", followed by "A317b: Understanding requirements for CCTV Systems Based on NTCIP 1205 Standard"-highlighted. From this box an arrow connects to the last box labeled as: "Applying Your Test Plan for NTCIP 1205 standard")
Slide 10:
Learning Objectives
- Learn how to develop requirements using the NTCIP 1205 CCTV standard
- Achieve interoperability and vendor-independence
- Understand traceability
- Incorporate requirements not supported by standardized objects
- Develop the CCTV system specification
Slide 11:
Learning Objective #1— Develop Requirements Using the NTCIP 1205
CCTV Standard
- Review the structure of the NTCIP 1205 standard
-
Identify requirements from various sources
- User needs developed in Module A317a
- Configuration-Control and Monitoring perspectives
- Content from the SEP-based standards
- Review criteria for well-formed requirements
- Develop sample requirements
Slide 12:
Learning Objective #1
Review of the NTCIP 1205 v1.08 Structure
(Extended Text Description: Review of the NTCIP 1205 v1.08 Structure: Three top boxes are labeled as Section 1 CCTV Review, Section 2 General and Appendix-Extended Glossary. Below that a blue colored box contains Section 3 details which include CCTV MIB in a cylindrical shape on the left and three bubbles on right each as Object 1, Object 2 and Object 70. CCTV MIB on left and three Objects on right are connected with one way arrows from the CCTV MIB. On the right side of the slide another box appears as Section 4 Conformance Groups and contains Configuration, Motion Control, Extended Functions and On-Screen Menu. There are four dashed arrows from Section 3 to Section 4 provided to show that conformance groups are groupings of objects.)
Slide 13:
Learning Objective #1
CCTV System Terminology
(Extended Text Description: Author's relevant descriptive notes: CCTV System Terminology: A photo image of a CCTV system interface is provided with terminology. In the top left corner a Control Pad as keyboard appears. On top right corner PTZ mechanism is shown. On the left side of the photo Focus and Iris with arrows point to the image are shown. On the right Presets and Labeling with arrows pointing to the image are shown. Each term is explained by the instructor.)
Source: NYCDOT: TMC CCTV Interface
Slide 14:
Learning Objective #1
Typical Desired Camera Control Functions
(Extended Text Description: Author's relevant descriptive notes: Typical Desired Camera Control Functions: real-world camera control functions are shown in a graphical way with listing of terminology on left side and view of a CCTV image on right. The graphic explains how each control functions support user interface.)
Source: NYSDOT
Slide 15:
Learning Objective #1
CCTV Information Required for Specification
(Extended Text Description: CCTV Information Required for Specification: Three boxes are shown on the slide with content. The first box lists 1. User Needs and 2. Requirements and an arrow leads to NOT Available. Second box contains 3. Objects and 4. Dialogs with arrow point to Available. The last box lists 5. Protocols Requirements List (PRL) and 6. Requirements Traceability Matric (RTM) with an arrow point to Not Available.)
Slide 16:
Learning Objective #1
Requirements are a Translation of User Needs
A translation of needs into a set of individual quantified or descriptive specifications for the characteristics of an entity in order to enable its realization on examination.
-ISO/IEC Guide 25: 1990
Example
(Extended Text Description: The text reads "The CCTV device shall allow the management station to remotely turn on or off the camera operation." And underneath, a red box surrounds the text "The burden of design is placed on the device". An elliptical shape covers the text "CCTV device shall allow," with a solid line to the text box of "The burden of designs is placed on the device")
Slide 17:
Learning Objective #1
User Needs' Relationship to Requirements
(Extended Text Description: There are three text boxes. The first contains "One User Need" with an arrow to "Requirement 1". The second contains "One User Need" with two arrows pointing to "Requirement 1" and "Requirement n". The third contains "Many User Needs" with an arrow to "Requirement 1".)
Slide 18:
Learning Objective #1
Approach to CCTV Requirements
(Extended Text Description: Author's relevant descriptive notes: Approach to CCTV Requirements: There are two inputs shown on left side: first Utilize user Needs from Module A317a and second (below) is Configuration, Monitoring and Control Perspectives. There is a box on right side of the slide with text; Develop CCTV Requirements and PRL and RTM. In the middle two small green squares and an arrow points to the outputs, the right side box.)
Slide 19:
Learning Objective #1
Review of a Well-Formed Requirement
Step-1 Provide Structure of a Requirement
(Extended Text Description: This slide contains the following text: 1. Actor identifies who does the action. 2. Action identifies what is to happen. 3. Target identifies who or what received the action. 4. Constraint identifies how to measure success or failure of the requirement. 5. Localization identifies the circumstances under which the requirement applies. There is a bracket next to items 4 and 5 with the text: Not all requirements will have both.)
Slide 20:
Learning Objective #1
Review of a Well-Formed Requirement
Step-2 Include Characteristics of a Requirement
- Necessary: Must be useful and traceable to needs.
- Concise: Minimal, understandable, and expressed as a shall statement.
- Attainable: Realistic to achieve within available resources and time.
- Standalone: Stated completely in one place.
- Consistent: Does not contradict itself, nor any other stated requirement.
- Unambiguous: Susceptible to only one interpretation.
- Verifiable: Requirement can be verified through inspection, analysis, demonstration, or test.
Slide 21:
Learning Objective #1
Developing Well-Formed CCTV Requirements
(Extended Text Description: Developing Well-Formed CCTV Requirements: Two boxes on left side are connected with two arrows to a box on right. The graphic represents two-step process to develop CCTV requirements. The boxes on the left contain the text Provide a Structure and Incorporate Characteristics, which both point to the box on the right which contains the text Types of CCTV Requirements.)
Slide 22:
Learning Objective #1
Types of CCTV Requirements
NTCIP Aim is to Achieve Remote Management
(Extended Text Description: Types of CCTV Requirements: Three text boxes on left are highlighted with colors and example of each is again highlighted in boxes on the right side. The three boxes on the left contain the text, from top to bottom, Architectural Requirements, Data Exchange Requirements, and Supplemental Requirements. In the center of the slide, there is text adjacent to the three boxes, which read, from top to bottom, Supports general communications capabilities, Supports Device feature-function, and Not covered above Special project need. To the right of the slide are three boxes which contain the text, from top to bottom, SNMP Interface, Pan-Tilt-Zoom, and Local.)
Slide 23:
Learning Objective #1
Organization of Requirements
SAMPLE CCTV REQUIREMENTS
3.1 Background Information
3.2 Architectural Requirements
3.2.1 Provide Live Data
3.2.2 Provide Off-Line Logged Data
3.3 Data Exchange Requirements
3.3.1 Managing Configuration
3.3.2 Camera Control
3.3.3 Monitoring Status
3.4 Supplemental Requirements
See Student Supplement for Details
Slide 24:
Learning Objective #1
Architectural Requirements
(Extended Text Description: This slide contains the following text and graphics elements: A bullet point with the text that reads: Requirements related to communications between a central Management Station and the CCTV Device. Under that text is a box with the following items: 1. Retrieve data from a device. 2. Deliver data to a device. 3. Explore data in a device. 4. Manage access levels to the device. A graphic at the bottom of the slide shows Management Station in a box connected with a solid line to another box on the right that is labeled CCTV Device. An arrow from the text in first line ("communications between") leads to the solid line between two boxes.)
Slide 25:
Learning Objective #1
Architectural Requirements Supported by NTCIP 1205 Standard
(Extended Text Description: Author's relevant descriptive notes: Architectural Requirements Supported by NTCIP 1205 Standard: The slide has the following text at the top: Provide Live Data: Monitor-Control CCTV System when Connected. Under that text, the graphic has two rows: The first row shows Management station box linked to CCTV Device with a solid line. In the second row Management station is linked to CCTV device with a broken path. First row thus depicts how data communications take place when both ends are connected, and second row indicate no connect or off-line condition. At the bottom, the text reads, Probide Off-line Log Data: Retrieve Log Data when NOT-Connected (Example: Dial-Up Links).)
Slide 26:
Learning Objective #1
Where do Architectural Requirements Come from?
Example: Operational User Need: Provide Live Data
3.2.1 Provide Live Data [Requirement]
3.2.1.1 Retrieve Data
The CCTV device shall allow the management station to retrieve data from the camera control receiver.
3.2.1.2 Deliver Data
The CCTV device shall allow the management station to deliver data (e.g. configuration data, commands etc.)
Slide 27:
Learning Objective #1
Where do Architectural Requirements Come from? (cont.)
Operational User Need: Provide Off-Line Data
3.2.2 Provide Off-Line Logged Data [Requirement]
3.2.2.3 Retrieve Logged Data
The CCTV device shall allow the management station to retrieve one or more available logged data from the event log.
3.2.2.4 Clear Log
The CCTV device shall allow the management station to clear any or all log entries of a given event class.
Slide 28:
Learning Objective #1
Data Exchange Requirements
-
Requirements to:
- Manage the CCTV Device Configuration
- Control the CCTV Device
- Monitor the Status of the CCTV Device
(Extended Text Description: Data Exchange Requirements: The slide has two part graphic. On the bottom left side an operator is shown at the work station and at right side a CCTV device with a traffic signal are shown on a pole. Both ends are connected with a two-way arrow showing Center to Field Communications. A box outlined in red at the bottom contains the text Example of Multiple Devices Sharing a Channel, with arrows pointing to the traffic light and CCTV in the photo to the right.)
Source: NYCDOT
Slide 29:
Learning Objective #1
Where do Data Exchange Requirements Come from?
CCTV User Needs Dictate Requirement(s)
- We have discussed well-written user needs in Module A317a [Please refer to Module A317a supplement]
-
Examples of titles of CCTV User Needs:
Configure a CCTV Device
Move and Control Camera in the Field
Set-Up a Camera Tour
Set-Up Zones
Share Video Images
Slide 30:
Learning Objective #1
Providing the Structure to a Requirement
(Extended Text Description: This slide contains the text: Title of a User Need "Configure a CCTV Device". An arrow points from Title of a User Need directly below to Requirement: Remotely Configure a CCTV Device. Below that, the text The CCTV device shall allow the management station to remotely configure the camera preset positions for a maximum number or 255. An elliptical shape is placed on the CCTV device to show it as a Target, another one is placed on remotely configure to indicate it as an Action and one on Management Station to indicate as an Actor.)
Slide 31:
Learning Objective #1
Assessing Characteristics of a Requirement
(Extended Text Description: There are four text boxes shown on the top of the slide: Necessary?, Concise?, Attainable? and Standalone? Three boxes are shown at the bottom of the slide; Consistent?, Unambiguous?, and Verifiable? Both Unambiguous and Verifiable boxes are placed in an elliptical shape and linked with an arrow to range of 1-xx in the middle of requirement text. The requirement text in the middle of the slide reads: 3.3.1.1 Configure Range Maximum Presets - The CCTV device shall allow the management station to select a preset from the preconfigured range of 1-xx to enable quick monitoring operation for a user defined timeframe.)
Slide 32:
Learning Objective #1
3.3.2.4 Pan Control
Ensures Structure + Characteristics
(Extended Text Description: The slide contains the follow text: The CCTV device shall allow the management sstation to remotely control a camera position horizontally (Pan - 0° to 360°). This requirement applies to both the primary management station and a backup TMC facility. Below this text are two boxes, Unambiguous? and Verifiable? These two boxes are circled and point to the text (Pan - 0° to 360°). In the main body of the text, the words "The CCTV device" are circled and labeled as TARGET, "management station" is labeled as ACTOR and "to remotely control" is labeled as ACTION.)
Slide 33:
Learning Objective #1
3.3.2.5 Tilt Control
Ensures Structure + Characteristics
(Extended Text Description: The slide contains the follow text: The CCTV device shall allow the management sstation to remotely control a camera position vertically (Tilt-is +/- 90°). This requirement applies to both the primary management station and a backup TMC facility. Below this text are two boxes, Unambiguous? and Verifiable? These two boxes are circled and point to the text (Tilt-is +/- 90°). In the main body of the text, the words "The CCTV device" are circled and labeled as TARGET, "management station" is labeled as ACTOR and "to remotely control" is labeled as ACTION.)
Slide 34:
Learning Objective #1
3.3.2.6 Zoom Operation
(Extended Text Description: The text at the top of the slide reads, "The CCTV device shall provide motorized camera-lens equipped with zoom capability to allow management station to remotely adjust lens for a wide and telephoto views. The words "The CCTV device" is labeled as TARGET, "management station" is labeled as ACTOR and "to remotely adjust" is labeled as ACTION. Two photos are shown at the bottom of the slide. Photo on the left shows an incident on a highway with fire spreading, with some details. This signifies Close Up view of CCTV images. Photo on the right shows large number of people walking on the Brooklynn Bridge. This vies gives long distance or far view of the roadway details under zoom operation.)
Source: NYCDOT
Slide 35:
Learning Objective #1
3.3.1.15
Timeout Limit of a Zoom Operation
(Extended Text Description: The single bullet text on this slide reads: The CCTV device shall allow the management station to adjust timeout of a zoom motion of the lens to continue for up to 655535 milliseconds without a reissue of a zoom command. Below that text reads, Ensures Structure + Characteristics. At the bottom of the slide is a red box with the text "Zero means timeout feature is not supported" which points to "timeout of a zoom motion" in the body of the text above it.)
Slide 36:
Slide 37:
Learning Objective #1
Which of the following is a well-formed requirement?
- The CCTV device shall allow the management station to retrieve current status of the device features from the camera control receiver.
- The camera position must be controllable by the TMC.
- Operator needs to monitor current temperature condition inside the camera enclosure.
- TMC staff shares camera controls with the maintenance personnel located at another building.
Slide 38:
Learning Objective #1
Review of Answers
a) The CCTV device shall allow the management station to retrieve current status of the device features from the camera control receiver.
Correct, because this requirement ensures structure and characteristics.
| Necessary | Standalone | |
| Concise | Consistent | |
| Attainable | Unambiguous | Verifiable |
Slide 39:
Learning Objective #1
Review of Answers
b) The camera position must be controllable by the TMC operator.
Incorrect, because this represents a user need.
c) Operator needs to monitor current temperature condition inside the camera enclosure.
Incorrect, because this is a user need statement.
d) TMC staff shares camera controls with the maintenance personnel located at another building.
Incorrect, because this is a user need statement.
Slide 40:
Summary of Learning Objective #1
Develop requirements using the NTCIP 1205
CCTV standard
- Reviewed the structure of the standard
- Learned how to identify types of CCTV requirements from various sources
- Discussed criteria for writing well-formed requirements and developed examples
- Additional examples of requirements are provided in the supplement
Slide 41:
Learning Objective #2 — Achieve Interoperability and Vendor-Independence
- Understand SNMP interface and dialogs
- Understand NTCIP objects
- Develop sample dialogs
Slide 42:
Learning Objective #2
Understanding Interoperability and Vendor-Independence
(Extended Text Description: Understanding Interoperability and Vendor-Independence: The slide presents a graphic that has six photo images. The top most photo shows a management station that is connected with one way three separate arrows. The first arrow on the left is marked as compatibility and points to a Dynamic Message Sign with a traffic controller. The second arrow labeled as Interoperability links to a combination of a signal and CCTV device mounted on the pole. The third arrow on the right is labeled as Interchangeability and shows an old tube camera being replaced with a newer dome CCTV camera.)
Slide 43:
Learning Objective #2
SNMP Interface
- SNMP Interface consists of the SNMP, dialogs, and messages
(Extended Text Description: There are two boxes at the bottom of the slide: First box contains the text "SNMP Manager - Management Station" and second box contains "SNMP Agent - CCTV Device" on the right. Both are linked with a two-way arrow in the middle.)
Slide 44:
Learning Objective #2
SNMP Messages
- Get message to read data (retrieve)
- GetNext message to retrieve more data
- Set message to write data (control)
Each message is a Command and Contains a Protocol Data Unit (PDU)
[Details Provided in Module C101 and NTCIP Guide]
Slide 45:
Learning Objective #2
Source of PDU Data: Object
- Structure of an Object is Based on
Abstract Syntax Notation 1 Language (ASN.1)
(Extended Text Description: This slide contains the following text explaining the Source of PDU Data: Object. The structure, located on the right, is labeled on the left with an explanation, which reads as follows: 1. Objects name - rangeMaximumPresets OBJECT-TYPE; 2. Data type value range - SYNTAXINTEGER (0..255); 3. Aces limitations - ACESS read-only; 4. Conformance requirement - STATUS mandatory; 5. Human readable description, states purpose - DESCRIPTION "A preset is the pre-specified position where a camera is pointed to a fixed point in space....."; 6. Object Identifier (OID) - ::={cctvRange1}. Items 2 and 6 above are highlighted with a red box.)
Slide 46:
Learning Objective #2
Formation of PDU Data: varBind
Example
(Extended Text Description: Example of PDU on left (rangeMaximumPresets) has two arrows that identify SYNTAX INTEGER (0..255) and ::={CCTVRange1} -- both are shown as pair under varBind on right side in a two sided bracket: { OID, 32 }.)
Slide 47:
Learning Objective #2
Formation of an SNMP Message
VarBindList Encapsulated in the Message
(Extended Text Description: Author's relevant descriptive notes: At the top of the slide five small boxes are shown as parts of an encapsulated PDU: PDU Type, Request ID, Error Status, Error Index, and VarBindList. This is also labeled {OID, 32},.... This PDU is linked to a stack of protocols for transmission. The stack has four layers of commonly used protocols such as SNMP, UDP, IP and DLC layers. Under the stack of layers is the text DLC-Data Link Control Layer.)
See NTCIP Guide for Details
Slide 48:
Learning Objective #2
Generic SNMP Dialogs for Messages
D.1 SNMP Get Interface Used to Retrieve Data from the Device
D.2 SNMP Get-Next interface Used to Retrieve More Data
D.3 SNMP Set Interface Used to Send Data to the Device
(Extended Text Description: At the bottom of the slide a box on the left labeled as Management Station is linked to the box on right labeled as CCTV device. Two separate messages are shown in the middle with one way arrows; one from the management station to the CCTV device and another from the CCTV device to the management station.)
Slide 49:
Learning Objective #2
D.1 Generic SNMP Get Interface Dialog
(Extended Text Description: Author's relevant descriptive notes: Generic SNMP Get Interface Dialog: The slide shows an UML diagram with SNMP Get Interface dialog. There is a figure on this slide showing a Unified Modeling Language (UML) sequence diagram. It shows the sequence of events to perform a GET operation, with a stick figure representing the Management Station on the left that issues the GET command. A box to the right represents the controller or a camera control receiver, which receives the command, processes it, assembles the response package, and sends it back to the requesting management station.)
Slide 50:
Learning Objective #2
D.2 Generic SNMP Get-Next Interface Dialog
(Extended Text Description: Author's relevant descriptive notes: Generic SNMP Get-Next Interface Dialog: The slide shows an UML diagram with SNMP Get-Next Interface dialog. There is a figure on this slide showing a Unified Modeling Language (UML) sequence diagram. It shows the sequence of events to perform a GET-Next operation, with a stick figure representing the Management Station on the left that issues the GET command. A box to the right represents the controller or a camera control receiver, which receives the command, processes it, assembles the response package, and sends it back to the requesting management station.)
Slide 51:
Learning Objective #2
D.3 Generic SNMP Set Interface Dialog
(Extended Text Description: Author's relevant descriptive notes: Generic SNMP Set Interface Dialog: The slide shows an UML diagram with SNMP Set Interface dialog. There is a figure on this slide showing a Unified Modeling Language (UML) sequence diagram. It shows the sequence of events to perform a Set operation, with a stick figure representing the Management Station on the left that issues the Set command. A box to the right represents the controller or a camera control receiver, which receives the command, processes it, assembles the response package, and sends it back to the requesting management station.)
Slide 52:
Slide 53:
Learning Objective #2
Which Generic SNMP Interfaces will allow the operator to monitor the current temperature within the camera enclosure?
Answer Choices
- SNMP SET Interface
- SNMP Get Interface
- SNMP GetNext Interface
- Any one of the above
Slide 54:
Learning Objective #2
Review of answers
a) SNMP SET Interface
Incorrect, because SET operation alters (WRITE) the device behavior, not used for monitoring.
b) SNMP Get Interface
Correct, because Get operation retrieves (READ) current data about the current temperature value.
c) SNMP GetNext Interface
Incorrect-Perhaps; because for single reading, Get is the appropriate operation, however, GetNext is typically used to read multiple objects in a table.
d) Any one of the above
Incorrect, because each interface performs a specific operation. Monitoring requires a Get operation.
Slide 55:
Learning Objective #2
Ensuring Interoperability
Specification must select the same Objects-Messages-PDUs and Dialogs
(Extended Text Description: To the left of the slide three vertical boxes appear; first box is MIB-Objects, second box lists messages GetRequest, GetNextRequest, SetRequest and GetResponse. Third box is PDU varBindList. An arrow from these boxes leads to a middle box that lists Dialogs D.1 D.2 and D.3. An arrow from this goes to Camera Control Receiver box at bottom right.)
Slide 56:
Learning Objective #2
Example: Requirement for the SET Operation
(Extended Text Description: The text reads D.3.1 Support of SET Operation - The CCTV device shall allow the management station to perform the SET operation on any supported object indicated in in the CCTV specification RTM. An elliptical shape is placed on "The CCTV device" to show it as a Target, another one is placed on "SET operation" to indicate it as an Action and one on "management station" to indicate as an Actor. "CCTV specification RTM" is linked with an arrow to Unambiguous-Necessary.)
Slide 57:
Learning Objective #2
Example: Requirement for Presets [Slide 30]
"The CCTV device shall allow the management station to select a preset from the preconfigured range of 1-xx to enable quick monitoring operation for a user defined timeframe."
![Example: Requirement for Presets [Slide 30]. Please see the Extended Text Description below.](m34ppt41.jpg)
(Extended Text Description: Author's relevant descriptive notes: The slide discusses example of slide 30 and shows an UML diagram with SNMP Set Interface dialog. Management station on left that issues commands is shown to explain a Unified Modeling Language (UML) sequence diagram. It shows the sequence of events to perform a Set operation, between the Management Station and a box to the right represents a camera control receiver, which receives the command, processes it, assembles the response package, and sends it back to the requesting management station.)
Slide 58:
Summary of Learning Objective #2
Achieve Interoperability and Vendor-Independence
- Discussed SNMP interface and dialogs for communications
- Discussed interoperability and interchangeability
- Reviewed a sample dialog with a message content
Slide 59:
Learning Objective #3 — Understand Traceability
- User needs to requirements traceability
- Requirements to design traceability
- Benefits of documenting a traceability
Slide 60:
Learning Objective #3
What is traceability?
-
Traceability is the ability to follow or study the logical progression among the need, requirements, and design details in a step-by-step fashion".
—SEP Based-NTCIP 1204 ESS standard, page 7- Traceability of requirements to user needs is achieved with a Protocol Requirements List (PRL)
- Traceability of design concepts to requirements is achieved with a Requirements Traceability Matrix (RTM)
Slide 61:
Learning Objective #3
Traceability Matrix — PRL
- SEP-based NTCIP Standards provides a format to trace requirements to user needs
(Extended Text Description: There is a table with the following data:
| UN ID | User Need | RQ. ID | Requirement | Additional Specs. |
|---|---|---|---|---|
| Each requirement is traced to | ||||
| at least one user need | ||||
The text "Each requirement is traced to at least one user need" is circled with an arrow pointing to the left to the column "User Need")
- CCTV standard does not provide a PRL
Slide 62:
Learning Objective #3
Preparing a Project Level PRL
(Extended Text Description: There is a table with the following content:
| User Need | RQ. ID | Requirement | Additional Specs. | |
|---|---|---|---|---|
| 1.0 | Configure CCTV Device | 3.3.1 | Data Exchange Requirements for Managing Configuration | |
| 3.3.1.1 | Configure Range Maximum presets | 32 for Dome | ||
| 3.3.1.2 | Configure Range-Pan Left Limit | |||
| 3.3.1.3 | Configure Range-Pan Right Limit | |||
| 3.3.1.4 | Configure Range Pan Home Position | |||
| 3.3.1.5 | Configure True North Offset | |||
| 3.3.1.6 | Configure Range Iris Limit | |||
| 3.3.1.13 | Configure Timeout Pan | |||
| 3.3.1.16 | Configure Timeout Focus | |||
| 3.3.1.19 | Configure Label Table |
There is a red box surrounding the columns and content of RQ. ID and Requirement. There is a blue box surrounding the text from the first and second columns: "1.0 Configure CCTV".)
Slide 63:
Learning Objective #3
Additional PRL Entries: Camera Control
| UN ID | User Need | RQ. ID | Additional Specs. | |
|---|---|---|---|---|
| 2.0 | Remote Camera Control | 3.3.2 | Camera Control | |
| 3.3.2.1 | Preset Go to Position | |||
| 3.3.2.2 | Move Camera to a Stored Position | |||
| 3.3.2.6 | Zoom Operation | |||
| 3.3.2.4 | Camera Position Horizontally (Pan) | 0° to 360° |
Additional requirements on camera movements is stated in the last column. More User needs and Requirements can be added as per table format.
Slide 64:
Learning Objective #3
Additional PRL Entries: Monitoring a CCTV
Device
| UN ID | User Need | RQ. ID. | Requirement | Additional Specs. |
|---|---|---|---|---|
| Remote Monitoring | 3.3.3 | Status condition within the device | ||
| 3.3.3.1 | Temperature | |||
| 3.3.3.2 | Pressure | |||
| 3.3.3.2 | Washer fluid | |||
| 3.3.3.3 | ID Generator |
Additional requirements on camera movements are stated in the last column. More User needs and Requirements can be added as per table format.
Slide 65:
Learning Objective #3
Benefits of the Project PRL
- PRL shows relationship of user needs (features) to requirements
- As a primary tool for specifying the NTCIP 1205 interface, developers, vendors and users are "connected" to the project's objectives
- Completed project PRL in the specification becomes a checklist in a validation process: "Did the CCTV system meet my user needs?"
- Eliminates "guess-work"
Slide 66:
Learning Objective #3
Preparing a Project Level RTM
(Extended Text Description: There is a table with the following content:
| RQ. ID | Requirement | Dialog | Object Reference and Title NTCIP 1205 Section 3 |
|---|---|---|---|
| 3.3.1 | Data Exchange Requirements for Managing Configuration | D.3 Generic SNMP SET Interface | |
| 3.3.1.1 | Configure Range Maximum presets | 3.2.1 rangeMaximumPreset | |
| 3.3.1.2 | Configure Range-Pan Left Limit | 3.2.2 rangePanLeftLimit | |
| 3.3.1.3 | Configure Range-Pan Right Limit | 3.2.3 rangePanrightLimit | |
| 3.3.1.4 | Configure Range Pan Home Position | 3.2.4 rangePanHomePosition | |
| 3.3.1.5 | Configure True North Offset | 3.2.5 rangeTrueNorthOffset | |
| 3.3.1.6 | Configure Range Iris Limit | 3.2.10 rangIirisLimit | |
| 3.3.1.13 | Configure Timeout Pan | 3.3.1 timeOurPan | |
| 3.3.1.16 | Configure Timeout Focus | 3.3.4 timeOutFocus | |
| 3.3.1.19 | Configure Label Table | 3.11.2 labelTable | |
The table also shows the following region highlighted with a red box: rows 3.3.1.1 through 3.3.1.19 in the columns Dialog and Object Reference and Title NTCIP 1205 Section 3.)
Slide 67:
Learning Objective #3
Additional RTM Entries: Camera Control
| Rq. ID | Requirement | Dialog | Object Reference and Title NTCIP 1205 |
|---|---|---|---|
| 3.3.2 | Camera Control | D.3 Generic SNMP SET Interface | |
| 3.3.2.1 | Preset Go to Position | 3.4.1 presetGotoPosition | |
| 3.3.2.2 | Go to a Stored Position | 3.4.2.presetStorePosition | |
| 3.3.2.6 | Zoom Operation |
3.2.8 rangeZoomLimit 3.3.3 timeoutZoom 3.3.3 positionZoomLens |
|
| 3.3.2.4 | Camera Position Horizontally (Pan) |
3.2.2 rangePanLeftLimit 3.2.4 rangePanHomePosition 3.2.11 rangeMinimumPanStepAngle 3.3.1 timeoutPan 3.5.1 positionPan 3.2.3 rangePanRightLimit 3.2.4 rangePanHomePosition 3.2.11 rangeMinimumPanStepAngle 3.3.1 timeoutPan |
|
Slide 68:
Learning Objective #3
Additional RTM Entries: Monitoring
| Rq. ID | Requirement | Dialog | Object Reference and Title NTCIP 1205 Section 3 |
|---|---|---|---|
| 3.3.3 | Status condition within the device | D.1 Generic SNMP GET Interface | |
| 3.3.3.2 | Temperature | 3.7.5 alarmTemperatureCurrentValue | |
| 3.3.3.2 | Pressure |
3.7.6 alarmPressureHighLowThreshold 3.2.7 alramPressureCurrentValue |
|
| 3.3.3.2 | Washer fluid |
3.7.8 alarmWasherFluidHighLowThreshold 3.2.9 alarmWasherCurrentValue |
|
| 3.3.3.3 | ID Generator | 3.11 cctv label Objects | |
Additional requirements can be added and related objects are collected from the 4 CGs and then go to MIB objects in Section 3 to read each object title
Slide 69:
Learning Objective #3
Benefits of the Project RTM
- RTM shows relationship of requirements to the specific design items of the interface (dialogs and data objects)
- Useful for identifying data objects within standard that may be sub-ranged within the specification
-
Helps in system acceptance:
"Did they build the CCTV system right?"
"Does my interface deliver?"
Slide 70:
Slide 71:
Learning Objective #3
Which will ensure the precise objects necessary to fulfill a requirement?
Answer Choices
- The PRL table
- The RTM table
- SNMP Get Interface
- Major Desired Capability (MDC)
Slide 72:
Learning Objective #3
Review of answers
a) The PRL table
Incorrect, because PRL traces user needs to requirements, not objects.
b) The RTM table
Correct, because RTM it is the only matrix where the precise objects necessary to fulfill a requirement are identified.
c) SNMP Get Interface
Incorrect, because SNMP Get interface is generic and does not contain objects.
d) Major Desired Capability (MDC)
Incorrect, because MDC is part of a user need.
Slide 73:
Summary of Learning Objective #3
Understand Traceability
- We have discussed how to develop a project PRL to trace User Needs to CCTV requirements
- We have discussed how to develop a project RTM to trace CCTV requirements to dialogs and objects (design)
- We reviewed the benefits of preparing a project level PRL and RTM
Slide 74:
Learning Objective #4 — Incorporate Requirements not Supported by Standardized Objects
- Conditions and context for extending the standard
- Example of extending the standard
Slide 75:
Learning Objective #4
Conditions and Context for Extending the CCTV Standard
- 70 objects based on ASN.1 format are available
- User-developed requirements must trace to NTCIP 1205 data objects and SNMP dialogs to gain interoperability and interchangeability
- Adding new objects to CCTV MIB is possible if it is documented and made available to anyone
Slide 76:
Learning Objective #4
Conditions and Context for Extending the CCTV Standard (cont.)
-
Extending or adding objects to the CCTV Standard can make sense to provide for:
- Control features and requirements that are specific to certain camera systems
- Objects for IP network cameras are not covered in the standard
Slide 77:
Learning Objective #4
Examples of Objects
Proposed Amendment to NTCIP 1205 v01 Standard
- Objects for Query-position-pan-tilt-Iris-focus-Zoom and preset-position.
-
Extensions Conditions:
- ASN.1 based Objects must support READ operation for retrieval and WRITE operation for control functions without restrictions
- Syntax must be a non-negative Integer/Bytes
- Object must have an OID with MIB node
- Only SNMP interface will be allowed (as per NTCIP 1103 rules)
Slide 78:
Learning Objective #4
Extensions - Drawbacks
-
Interoperability may be compromised
- Other management stations that do not support the new objects will be unable to exercise the new capabilities
- If the agency is not consistent on defining how the requirement is fulfilled, interoperability cannot be achieved without custom integration for each deployment
Example: "Provide remotely selectable shutter speed"
Slide 79:
Slide 80:
Learning Objective #4
Which of the following is NOT applicable to the following extended CCTV requirement?
"The CCTV device shall allow the management station to remotely control selectable shutter speed of the field camera."
Answer Choices
- All extended requirements are non-conformant to the standard, and depend on proprietary vendor-specific objects.
- The requirement is well-developed and meets criteria.
- This requirement will break the interoperability.
- The project RTM will ensure interoperability.
Slide 81:
Learning Objective #4
Review of answers
a) All extended requirements are non-conformant to the standard and depend on proprietary vendor-specific objects.
Incorrect, because the statement is true.
b) The requirement is well-developed and meets criteria.
Incorrect, because the statement is true.
c) This requirement will break the interoperability
Incorrect, because the statement is true.
d) The project RTM will ensure interoperability
Correct, because the statement is false; project RTM does not reference a private Object.
Slide 82:
Summary of Learning Objective #4
Incorporate requirements not supported by standardized objects
- Reviewed conditions and context for extending the CCTV standard
- Discussed some example of extending the standard
- Extensions break interoperability and should be avoided
Slide 83:
Learning Objective #5 — Develop a CCTV System Specification
- How the CCTV specification fits in the specification package
- Checklist of key elements that must be present
Slide 84:
Learning Objective #5
(Extended Text Description: This slide contains the following text: at the top in a box, it reads, Plans-Specifications and Estimates (PS&E). Below that reads, Contractual requirements during system development, testing, deployment, integration, and operations/maintenance. Below this are three boxes: On the left, box 1 - Hardware specifications, Functional requirements, Performance requirements, Electrical-Mechanical requirements, Environmental requirement. On the right, box 2 - Software specification, Functional requirements, Performance requirements. On the bottom, box 3 - Communication Interface Specifications, Architectural Requirements, Data Exchange Requirements.)
Slide 85:
Learning Objective #5
Checklist of Specification Elements
(Extended Text Description: Part 3 - Communication Interface Specifications - of PS&E (slide 84) as a check list is shown with four text bullets: Address Interoperability Issues, Integrate Project PRL and RTM in the Specification, Coordination Requirements, Video formats-standards.)
Slide 86:
Learning Objective #5
Addressing Interoperability Issues
-
To achieve interoperability agencies must:
- Select the same user needs and design solutions
- Use common protocols
(Extended Text Description: A graphical box on left of slide shows Management Station with MIB and another box at right shows CCTV device with MIB. An arrow from the management station to the device shows request message and a separate arrow from the device to the management station shows a response message.)
- The management station and cameras must have the same CCTV MIB and use the same dialogs to support the same features.
Slide 87:
Learning Objective #5
Interoperability Issues
(Extended Text Description: The slide shows a graphic that a photo of a TMC operator with four screens in front of him. From his left the First screen is labeled as Video System-1, second TIM, third Video System-2 and fourth screen is Video System-3. A text box at bottom points to TIM, which is labeled TIM-Traffic Incident Management. At top of the slide, a circle is placed over the text Implications and it connects to three Video systems on the photo.)
Source: JTMC-NYC Patel
Slide 88:
Learning Objective #5
Integrating PRL in the Project Specification
- A project PRL defines data exchange requirements for the communications interface
- Underlying communications standards need to be specified too (protocols at various levels)
- Reference to interface standards must be specific to the version and publication date
- Include the completed PRL with object value ranges for all the objects to clarify parameters
Slide 89:
Learning Objective #5
Coordination of Requirements
- The requirements for the communications interface must be consistent with the CCTV system specification
- Include statement to use standardized design solutions, as specified in the project RTM
- Include a completed copy of the PRL plus the RTM as a source for the design of the system and the test plan
Slide 90:
Learning Objective #5
CCTV System Video Formats
- Video format standards are outside the scope of the NTCIP 1205
-
Video standards support compression, storage, and transmission:
- H.264 [See supplement]
- IP Cameras [Open network Video Interface Forum-ONVF]
- Certain legacy-based implementation may present video format issues and may need a new requirement. (See student supplement for more information)
Slide 91:
Slide 92:
Learning Objective #5
Which of the following statements is false?
Answer Choices
- A CCTV system vendor may support features not selected in the project PRL.
- The Project RTM specifies the objects and dialogs.
- Analog cameras can be controlled with a common digital camera control interface.
- The interface specification must specify SNMP.
Slide 93:
Learning Objective #5
Review of answers
a) A CCTV system vendor may support features not selected in the project PRL.
Incorrect, because the statement is true.
b) Project RTM specifies the objects and dialogs.
Incorrect, because the statement is true.
c) Analog cameras can be controlled with a common digital cameras control interface.
Correct, because the statement is false; an analog camera signal must be first converted to a digital signal using an encoder for a common digital camera control interface.
d) The interface specification must specify SNMP.
Incorrect, because the statement is true.
Slide 94:
Summary of Learning Objective #5
Develop a CCTV System specification
- Discussed a checklist of key elements, including interoperability issues
- Discussed a CCTV system specification fits in the overall project specification package
Slide 95:
What We Have Learned
- CCTV Standard does not provide requirements and user must develop and write them for project specification.
- A requirement is a translation of a user need, and has a structure and certain characteristics.
- Requirements are linked to interoperability and vendor-independence.
Slide 96:
What We Have Learned (cont.)
Specifically at the project level;
- Each requirement is traced to at least one user need in the project PRL.
- Requirements should be traced to Objects and Dialogs in the project RTM.
Slide 97:
What We Have Learned (cont.)
- To retrieve data (reading operation) from the CCTV device, SNMP GET interface is used.
- To control a CCTV device (writing operation), SNMP SET interface is used.
- To support the same features, the Management station and a CCTV device must have the same MIB and must use the same Dialogs.
Slide 98:
Resources
- Student Supplement
-
NTCIP Documentation available at www.ntcip.org:
- NTCIP 1201 v03 Global Object Definitions
- NTCIP 1205 v01.08 CCTV Camera Control
- NTCIP 9001: Guide v04
-
PCB Training Modules Available at stds training.aspx
- Module A103: Introduction to ITS Standards Requirements Development (to review "well-formed" requirements)
- Module A203: Writing Requirements When ITS Standards Do Not Have SE Content
Slide 99:
Slide 100:
Next Course Module
T317: Applying Your Test Plan to the NTCIP 1205 Standard
- Explains how to write a CCTV system Test Plan
- How to test CCTV system requirements