CI ConOps V01 - Ite
A Project Document of the Connected Intersections (CI) CommitteeDRAFTCI ConOpsv01.02Concept of Operations (ConOps) for theConnected Intersections (CI)Implementation GuideDraft v01.02 – October 30, 2020This is a project document, which is distributed for review and comment purposes only. You mayreproduce and distribute this document within your organization, but only for the purposes of and only tothe extent necessary to facilitate review, comment and voting to the Connected Intersections (CI)Committee at standards@ite.org. Please ensure that all copies include this notice. This documentcontains preliminary information that is subject to change.
CI Implementation Guide - ConOps v01.02Page iiForewordThis document was developed by engaging with stakeholders representing the industry at large includingbut not limited to Car manufacturers, State DOTs, local municipalities, and was supported by the USDOTITS Joint Program Office (JPO). Several associations - such as the American Association of StateHighway Transportation Officials (AASHTO), Institute of Transportation Engineers (ITE), the NationalElectrical Manufacturers Associations (NEMA), Institute of Electrical and Electronics Engineers (IEEE),and SAE International - were involved in ensuring balanced and effective stakeholder representation andadherence to standards development process as Standards Development Organizations (SDOs).
CI Implementation Guide - ConOps v01.02Page iRecent Minor Version Revision HistoryFilenameCI ConOpsDraft1.02CI ConOpsDraft1.01aDate10/30/2009/15/20CI CI ConOpsDraft1.00g-pxcD1.docxCI ConOpsDraft1.00g.docxCI ConOpsDraft1.00f.docxCI ConOpsDraft1.00e.docxCI 8/12/2008/07/20CI gnaresChanCI ConOpsDraft1.00b.docxCI ConOpsDraft1.00a.docxCI anLahiriNotesIncorporate comments from review period.Update context diagrams. QAIncorporatefeedbackfromConOpsWalkthroughIncludes edits from comments and Day 1 of theConOps walkthroughDistributed to CI Committee for comments.Additional text and input from all other TFs.Additional text and input from Positioning TFAdditional input through 8/7 from TF co-chairson context diagram, SPaT/MAP TFAdditional changes and updates. Includescomments from co-chairs and SMEs thru 7/24.Initial Draft. Submitted to CI Co-Chairs.FormattingInitial layout of ConOps
CI Implementation Guide - ConOps v01.02Page iiTABLE OF CONTENTSPageSection 1 General Information [Informative] . 11.1Scope . 11.2References . 11.2.1 Normative References . 11.2.2 Other References. 21.2.3 Contact Information. 21.2.3.1 Architecture Reference for Cooperative and Intelligent Transportation (ARCIT) . 21.2.3.2 FHWA Documents . 21.2.3.3 IEEE Standards . 31.2.3.4 NTCIP Standards . 31.2.3.5 SAE International Documents . 31.3Terms . 31.4Abbreviations . 4Section 2 Concept of Operations [Normative] . 72.1Tutorial [Informative] . 72.2Current Situation and Problem Statement [Informative] . 82.3Reference Physical Architecture [Informative] . 112.4Needs . 122.4.1 Architectural Needs. 122.4.2 Messages . 132.4.2.1 Message Performance Needs. 13Uniform. 13Message Accuracy . 13Robustness . 13Concise Messages . 13Advanced Notification . 14Timeliness . 14Quality Assurance . 142.4.2.2 Generic Message Data Needs . 14Time Source . 14Message Revision . 14Timestamp . 142.4.2.3 Signal Timing Data Needs . 14Intersection Identification . 14Intersection Status . 15Current Movement State . 15Next Movement State . 15Time Change Details . 15Confidence Factor . 15Next Green . 15Enabled Lanes . 16Signal Timing and Roadway Indications Synchronization . 162.4.2.4 Roadway Geometry Data Needs . 16Intersection Geometry . 16Lane Attributes . 16Allowed Maneuvers . 16Connections Between Lanes . 16
CI Implementation Guide - ConOps v01.02Page iii2.52.62.72.8Approach Speed Limit Information . 17Revocable Lanes . 17Signal Timing and Roadway Geometry Synchronization . 172.4.2.5 Positioning Data Needs . 17Positioning Corrections . 17Real-Time Kinematic . 172.4.3 Security . 172.4.3.1 Correct Operations . 17Data Trustworthiness . 18Data Processing . 18Input Validation . 18Cyber Attacks . 18Cyber Attacks Recovery . 18Resilience. 18Secure Administration . 18Authenticated Secure Update . 182.4.3.2 Data Flow: Communications and Interface Security . 19Data Trustworthiness . 19Data Integrity . 192.4.3.3 Network Monitoring . 19Misbehavior Reporting by Network Administrators . 192.4.3.4 Credential Management . 19Credential Provisioning . 19Management of Untrustworthy Devices . 19Credentialing System Access . 19Operational Policies and Constraints . 20Operational Scenarios . 202.6.1 Red-Light Violation Warning (RLVW) Application . 202.6.2 Signal Timing Scenarios . 212.6.2.1 Rest in Green . 212.6.2.2 Two or More Signals or Intersections with One Controller . 212.6.2.3 Texas Diamond Intersections . 232.6.2.4 Florida T Intersection . 242.6.2.5 User Logic - Outside the "knowledge" of the Controller . 262.6.2.6 High-Intensity Activated Crosswalk Beacon (HAWK) . 272.6.2.7 Dynamic Lane Use . 29Relationship to the ITS National Architecture [Informative] . 30Testing and Conformity Verification Management . 312.8.1 Testing and Conformance . 312.8.1.1 Conformance Statement . 312.8.1.2 Conformance Definitions . 31Conformance . 31Conformance Testing. 31Interface . 32Interoperability . 32Interchangeability . 322.8.1.3 Testing and Conformance Scope Overview [Informative] . 32Testing and Conformance Scope Diagram . 32Testing and Conformance Scope Matrix . 33Clarifying Assumptions . 33Testing and Conformance Objectives: Operational Verificationand Conformance . 342.8.1.4 Infrastructure Testing . 34Validate Message Data Needs . 34Reference Integrity Message Data Needs . 34
CI Implementation Guide - ConOps v01.02Page iv2.8.2Test Methodology . 342.8.2.1 Test Methodology Concepts . 342.8.2.2 Test Environment . 352.8.3 Message Level Testing . 362.8.3.1 Positive Testing . 362.8.3.2 Negative Testing . 372.8.3.3 Boundary Testing . 372.8.3.4 Packet Capture Analysis-based Testing . 372.8.3.5 Field Environment Analysis . 372.8.3.6 Load and Stress Testing . 372.8.4 Test Documentation . 372.8.5 Requirements Verification Methods . 382.8.6 Test Cases . 382.8.7 Test Coverage . 382.8.8 Test Procedures. 392.8.9 Identify Existing Test Documentation . 392.8.10 Identify Existing Test Tools . 392.8.11 Configuration and Change Management Needs . 39Annex A - User Requests . 40A.1Needs . 40A.1.1 Mobility Applications . 40A.1.2 Queue Information at an Intersection . 40A.1.3 Indication of Pedestrians or Bicyclists in a Crosswalk . 40A.1.4 Signal Priority and Preemption . 40A.1.5 Advisory Speeds . 40A.1.6 Misbehavior Reporting by OBUs . 40A.1.7 Misbehavior Reporting by IOO Field Devices . 41A.1.8 Levels of Testing . 41
CI Implementation Guide - ConOps v01.02Page vTABLE OF FIGURESPageFigure 1. How Standards are used in a Connected Intersection . 10Figure 2. Connected Intersection . 11Figure 3. ARC-IT Physical View . 30Figure 4. Testing and Conformity Scope Context Diagram . 32Figure 5. Test Methodology Concepts . 35Figure 6. Example Test Environment for SPaT Testing . 36Figure 7. Test Documentation Relationships . 38LIST OF TABLESPage
CI Implementation Guide - ConOps v01.02Page vi This page intentionally left blank.
CI Implementation Guide - ConOps v01.02Page 1Section 1General Information [Informative]1.1ScopeThis document, the Connected Intersection (CI) Implementation Guide, defines the key capabilities andinterfaces a connected signalized intersection must support to ensure interoperability with productionvehicles for state and local infrastructure owner/operators (IOO). A connected intersection is defined asan infrastructure system that broadcasts signal, phase, and timing (SPaT), mapping information (MAP),and position correction data to vehicles.This CI Implementation Guide addresses the ambiguities and gaps identified by early deployers andprovides guidance to generate messages and develop applications for signalized intersections that areinteroperable across the United States, especially for automated transportation systems. This documentfocuses on harmonizing the existing SPaT messages deployed, using the United States Department ofTransportation (USDOT) sponsored Cooperative Automated Transportation Clarifications for ConsistentImplementations (CCIs) To Ensure National Interoperability Connected Signalized Intersections as astarting point.This document was developed with the combined effort of stakeholders representing the industry at largeincluding IOOs, Automotive Original Equipment Manufacturers (OEMs), Fleet and Truck operators, safetyadvocacy groups, multimodal partners and end users of data and services. Several associations - SAEInternational (SAE), American Association of State Highway Transportation Officials (AASHTO), NationalElectrical Manufacturers Associations (NEMA), Institute of Electrical and Electronics Engineers (IEEE)and Institute of Transportation Engineers (ITE) - are involved in ensuring balanced and effectivestakeholder representation and adherence to consensus-based Development ProcessThe Implementation Guide follows a Systems Engineering Process (SEP), so the contents of thisdocument include Concept of Operations (ConOps), a System Requirements (Functional Requirements),and System Design Details sections.The CI Implementation Guide defines procurement and implementation guidance and the expectationsleading to minimum performance requirements for a connected intersection. It is intended to be used byIOOs to provide guidance on how to implement an interoperable connected intersection. For OEMs andother application developers, this document provides an explanation on what data and connected vehiclemessages are being provided from an interoperable connected intersection so safety applications can bedeveloped for production vehicles, with an initial focus on the Red-Light Violation Warning application.The NRTM in Section 3.x provides the guidance to IOOs for the procurement of a connected intersection.1.21.2.1ReferencesNormative ReferencesNormative references contain provisions that, through reference in this text, constitute provisions of thisCI Implementation Guide. Other references in this document might provide a complete understanding orprovide additional information. At the time of publication, the editions indicated were valid. All standardsare subject to revision, and parties to agreements based on this CI Implementation Guide are encouragedto investigate the possibility of applying the most recent editions of the standards listed.IdentifierSAE J2735 202007TitleV2X Communications Message Set Dictionary, SAE International, published2020.
CI Implementation Guide - ConOps v01.02Page 21.2.2Other ReferencesThe following documents and standards may provide the reader with a more complete understanding ofconnected intersections; however, these documents do not contain direct provisions that are required bythe CI Implementation Guide. At the time of publication, the editions indicated were valid. All standardsare subject to revision, and parties to agreements based on the CI Implementation Guide are encouragedto investigate the possibility of applying the most recent editions of the standard listed.IdentifierU.S.ArchitectureReference for CooperativeandIntelligentTransportation (ARC-IT)CCIIEEE 610-1990IEEE 829-2008IEEE 1012-2016IEEE 1362-1998MUTCDThe NTCIP Guide (NTCIP9001, v04)RSU Standardization1.2.31.2.3.1TitleArchitecture Reference for Cooperative and Intelligent Transportation(ARC-IT), USDOT, http://local.iteris.com/arc-it/Cooperative Automated Transportation Clarifications for ConsistentImplementations (CCIs) To Ensure National Interoperability ConnectedSignalized Intersections, Version 1.9.5, June 2020IEEE Standard Glossary of Software Engineering Terminology, IEEE,1990IEEE Std 829 IEEE Standard for Software and System TestDocumentation, IEEE, 2008IEEE Standard for System, Software, and Hardware Verification andValidation, IEEE, 2016.IEEE Guide for Information Technology System Definition - Concept ofOperations (ConOps) Document, IEEE, 1998Enabling Connected Intersections Concept Paper – Working Draft toSupport Discussions of the IOO/OEM Forum SPaT/RLVW GroupManual on Uniform Traffic Control Devices for Streets and Highways,2009 Edition including Revision 1 and 2 dated May 2012, FederalHighway Administration, United States Department of TransportationThe NTCIP 9001, The NTCIP Guide, v04, AASHTO / ITE / NEMA,published July 2009Concept of Operations (ConOps) for the Roadside Unit (RSU) Standard,v01.06, July 12, 2020Contact InformationArchitecture Reference for Cooperative and Intelligent Transportation (ARC-IT)The Architecture Reference for Cooperative and Intelligent Transportation (ARC-IT) may be viewed onlineat:http://local.iteris.com/arc-it/ARC-IT is the US ITS reference architecture and includes all content from the (now deprecated) NationalITS Architecture v7.1 and the Connected Vehicle Reference Implementation Architecture (CVRIA) v2.2.1.2.3.2FHWA DocumentsU.S. Department of Transportation Federal Highway Administration (FHWA) documents (withdesignations FHWA-JPO- ) are available at the U.S. Department of Transportation NationalTransportation Library, Repository & Open Science Access Portal (ROSA P):https://rosap.ntl.bts.gov/
CI Implementation Guide - ConOps v01.02Page 31.2.3.3IEEE StandardsIEEE standards can be purchased on-line in electronic format or printed copy from:Techstreet6300 Interfirst Dr.Ann Arbor, MI 48108(800) 699-9277www.techstreet.com/ieee1.2.3.4NTCIP StandardsCopies of NTCIP standards may be obtained from:NTCIP CoordinatorNational Electrical Manufacturers Association1300 N.17th Street, Suite 900Rosslyn, Virginia 22209-3801www.ntcip.orge-mail: ntcip@nema.orgDraft amendments, which are under discussion by the relevant NTCIP Working Group, and amendmentsrecommended by the NTCIP Joint Committee are available.1.2.3.5SAE International DocumentsCopies of SAE International documents may be obtained from:SAE International400 Commonwealth DriveWarrendale, PA 15096www.sae.org1.3TermsThe following terms, definitions, acronyms, and abbreviations are used in this document.TermDefinitionConnected Intersections (CI)An infrastructure system that broadcasts signal, phase and timing(SPaT), mapping information and position correction data to OnBoard Units and Mobile Units.InterchangeabilityThe capability to exchange devices of the same type on the samecommunications channel and have those devices interact with othersdevices of the same type using standards-based functions.Source: The NTCIP GuideInterfaceA shared boundary across which information is passed.Source: IEEE Std 610, IEEE Standard Glossary of SoftwareEngineering Terminology, 1990.
CI Implementation Guide - ConOps v01.02Page 4TermDefinitionInteroperabilityThe ability of two or more systems or components to exchangeinformation and to use the information that has been exchanged.Source: IEEE Std 610, IEEE Standard Glossary of SoftwareEngineering Terminology, 1990.Mobile Unit (MU)A device used to wirelessly communicate with other devices forsafety and mobility purposes carried by a pedestrian, bicyclist, workzone worker, or other traveler.Source: Concept of Operations (ConOps) for the Roadside Unit(RSU) Standard, v01.06, July 12, 2020.On-Board Units (OBU)A device used to wirelessly communicate with other devices forsafety and mobility purposes installed in a vehicle as originalequipment or as aftermarket equipment (sometimes referred to asan “aftermarket safety device (ASD)”.Source: Concept of Operations (ConOps) for the Roadside Unit(RSU) Standard, v01.06, July 12, 2020.Roadside Unit (RSU)A transportation infrastructure communications device located on theroadside that provides V2X connectivity between OBUs/MUs andother parts of the transportation infrastructure including traffic controldevices, traffic management systems, and back-office systems.Note: Devices that are not part of the transportation infrastructure,such as cellular base stations or satellites, are not RSUs.Source: Concept of Operations (ConOps) for the Roadside Unit(RSU) Standard, v01.06, July 12, 2020.RobustnessDegree to which a system or component can function correctly in thepresence of invalid inputs or stressful environmental conditions.Source: sandsoftwareTransportation Field DevicesDevices and electronic systems that monitor and control trafficoperations on a roadway. Examples include a traffic signal controllerand a roadside unit.Vulnerable Road User (VRU)A term applied to those most at risk in traffic, i.e. those unprotectedby an outside shield. VRUs are pedestrians (especially children,seniors and people with disabilities), bicyclists, and motor cyclists.Source: Concept of Operations (ConOps) for the Roadside Unit(RSU) Standard, v01.06, July 12, 2020.1.4AbbreviationsThe abbreviations and acronyms used in this document are defined below.AASHTOAmerican Association of State Highway Transportation Officials
CI Implementation Guide - ConOps v01.02Page 5ARC-ITArchitecture Reference for Cooperative and Intelligent TransportationCATCooperative Automated Transportation CoalitionCCIClarifications for Consistent Implementations (CCIs) To Ensure NationalInteroperability - Connected Signalized Intersections (document)CIConnected IntersectionConOpsConcept of OperationsCVConnected VehicleDSRCDedicated Short Range CommunicationFHWAFederal HighWay AdministrationFOFunctional ObjectGNSSGlobal Navigation Satellite SystemIEEEInstitute of Electrical and Electronics EngineersIMUInertial Measurement UnitIOOInfrastructure Owner/OperatorITEInstitute of Transportation EngineersMPHmiles per hourMUMobile UnitsMUTCDManual of Uniform Traffic Control DevicesNEMANational Electrical Manufacturers AssociationsNRTMNeeds to Requirements Traceability MatrixOBUOn-Board UnitsOEMAutomotive Original Equipment ManufacturersRLVWRed-Light Violation WarningRTKReal-Time KinematicRTMRequirements Traceability MatrixSAESAE InternationalSCMSSecurity Credentials Management SystemSDOStandards Development OrganizationsSEPSystems Engineering ProcessSPaTSignal Phase and TimingUSDOTUnited States Department of rable Road User
CI Implementation Guide - ConOps v01.02Page 6
CI Implementation Guide - ConOps v01.02Page 7Section 2Concept of Operations [Normative]Section 2 defines the user needs that subsequent sections this CI Implementation Guide addresses.Accepted system engineering processes detail that requirements should only be developed to fulfill welldefined user needs. The first stage in this process is to identify the ways in which the system is intendedto be used. In the case of the CI Implementation Guide, this first stage entails identifying the various waysin which the IOOs may provide and Automotive OEMs may use SPaT, MAP and positioning data at aconnected intersection in a consistent, interoperable manner.This concept of operations provides the reader with:a)b)c)d)a detailed description of the scope of the CI Implementation Guide document;identifies the key capabilities and interfaces for a connected intersection;an understanding of the perspective of the developers of this document; anda testing framework to verify conformance to the CI Implementation Guide.Secti
IEEE 610-1990 IEEE Standard Glossary of Software Engineering Terminology, IEEE, 1990 IEEE 829-2008 IEEE Std 829 IEEE Standard for Software and System Test Documentation, IEEE, 2008 IEEE 1012-2016 IEEE Standard for System, Software, and Hardware
Extreme Cruzer Contour 8 GB – snsa Clip a 4 GB – MTP Player snsa Clip a 8 GB V01.01.05F Nicht unterstützt snsa e280a 8 GB V01.02.18F UsB Modus : MsC snsa Fuzea 2 GB V01.01.11F snsa Fuze a 8 GB V01.30.01 F Nicht unterstützt snsa Viewa 8 GB V01.02.09F MTP Player
Pearson Edexcel Level 3 GCE Turn over . 2 *P49875A0228* T ITE I THIS AEA T ITE I THIS AEA T ITE I THIS AEA T ITE I THIS AEA T ITE I THIS AEA T ITE I THIS AEA SECTION A Answer ALL questions. All multiple choice questions must be answered with a cross in the box for the correct answer from A
Edexcel Physics A Level 2017 P2 *P48102RRA01932* 19 Turn over T ITE I THI AEA T ITE I THI AEA T ITE I THI AEA T ITE I THI AEA T ITE I THI AEA T ITE I THI AEA (b) Light from a point object forms a focused image on the retina. The cornea and lens may be treated as a single lens of focal length 1.6 cm that is
ISO/EEC/IEEE 29148 referenced below are used consistently by ANSI/AIAA, ISO/DEC/IEEE, and the Department of Defense (as cited in Walden, 2015). ConOps description according to the INCOSE Systems Engineering Handbook Version 4 (as cited in Walden, 2015): "The ConOps, at the organization level, addresses the leadership's intended way of
CONCEPT OF OPERATIONS (CONOPS) . 5.3.1 Transition timeline . 35 5.4 MISSION OPERATIONS SUPPORT TEAM . 36. Effective Date: June 16, 2020 410-R-CONOPS-0008 Expiration Date: Five years from date of last change Version 3.0 Responsible Organization: GOES-R Program/Code 410 Check .
SanDisk — — — — Cruzer Cruzer 16 GB 32 GB — V01.01.05F — — — — — — Not supported — — — Not supported MTP Player Cruzer Blade Sansa Clip Cruzer Slice Cruzer Micro Skin Extreme Cruzer Contour Cruzer Pattern Sansa Clip 8 GB 8 GB 32 GB 8 GB 8 GB 8 GB 4 GB V01.02.18F V01.01.11F USB Mode : MSC — Sansa e280 Sansa Fuze 8 .
SanDisk — — — — Cruzer Cruzer 16 GB 32 GB — V01.01.05F — — — — — — MTP Player — — — Password protection software MTP Player Cruzer Blade Sansa Clip Cruzer Slice Cruzer Micro Skin Extreme Cruzer Contour Cruzer Pattern Sansa Clip 8 GB 8 GB 32 GB 8 GB 8 GB 8 GB 4 GB V01.02.18F V01.01.11F MTP Player Not supported Sansa .
SanDisk. SEAT LEON IBIZA ALTEA FAMILY MULTIMEDIA. Cruzer Slice 32 GB Extreme . Cruzer Contour 8 GB. Sansa Clip 4 GB. Sansa Clip . 8 GB V01.01.05F. MTP Player Sansa e280. 8 GB V01.02.18F. MTP Player Sansa Fuze. 2 GB V01.01.11F. Not compatible Sansa View.
