24315 METR |
Submit Comment Traceability Tables: |
ID | Description | Discussion | Links |
---|---|---|---|
ConOps-2 |
1 ScopeThe management of electronic transport r…
|
||
ConOps-51 |
2 Normative referencesThe following documents are referred to …
|
||
ConOps-636 |
ISO/TS 14812:2022, Intelligent transport…
|
||
ConOps-637 |
ISO/TS 24315-1: - , Intelligent transpor…
|
||
ConOps-638 |
ISO/IEC/IEEE 24765:2017, Systems and sof…
|
||
ConOps-52 |
3 Terms and definitionsFor the purposes of this document, the t…
|
||
ConOps-402 |
4 Symbols and abbreviated terms |
||
ConOps-969 |
4.1 3Gthird-generation technology standard for…
|
||
ConOps-970 |
4.2 3GPP3rd Generation Partnership Project
|
||
ConOps-971 |
4.3 4Gfourth-generation technology standard fo…
|
||
ConOps-972 |
4.4 5Gfifth-generation technology standard for…
|
||
ConOps-973 |
4.5 ADSAutomated Driving System
|
||
ConOps-974 |
4.6 ARC-ITArchitecture Reference for Cooperative a…
|
||
ConOps-975 |
4.7 C-ITScooperative intelligent transport system…
|
||
ConOps-976 |
4.8 CCMScooperative ITS credentials management s…
|
||
ConOps-977 |
4.9 DDTdynamic driving task
|
||
ConOps-978 |
4.10 DSRCdedicated short-range communications
|
||
ConOps-979 |
4.11 FMfrequency modulation
|
||
ConOps-980 |
4.12 GNSSglobal navigation satellite system
|
||
ConOps-981 |
4.13 HMIhuman-machine interface
|
||
ConOps-982 |
4.14 IECInternational Electrotechnical Commissio…
|
||
ConOps-983 |
4.15 IEEEInstitute of Electrical and Electronic E…
|
||
ConOps-984 |
4.16 ISOInternational Organization for Standardi…
|
||
ConOps-985 |
4.17 ITSintelligent transport systems
|
||
ConOps-986 |
4.18 LTE-V2Xlong-term evolution vehicle-to-everythin…
|
||
ConOps-987 |
4.19 METRmanagement of electronic traffic regulat…
|
||
ConOps-988 |
4.20 MUTCDManual on Uniform Traffic Control Device…
|
||
ConOps-1061 |
4.21 OBEon-board equipment
|
||
ConOps-989 |
4.22 OCRoptical character recognition
|
||
ConOps-990 |
4.23 ODDoperational design domain
|
||
ConOps-991 |
4.24 OEMoriginal equipment manufacturer
|
||
ConOps-992 |
4.25 PMRpublic-area mobile robot
|
||
ConOps-993 |
4.26 QRquick response
|
||
ConOps-994 |
4.27 RSUroadside unit
|
||
ConOps-995 |
4.28 TCtechnical committee
|
||
ConOps-996 |
4.29 TMDDTraffic Management Data Dictionary
|
||
ConOps-997 |
4.30 TN-ITStransport network - intelligent transpor…
|
||
ConOps-998 |
4.31 TPEGtransport protocol experts group
|
||
ConOps-999 |
4.32 UKUnited Kingdom
|
||
ConOps-1000 |
4.33 UNECEUnited Nations Economic Commission for E…
|
||
ConOps-1001 |
4.34 USUnited States of America
|
||
ConOps-1002 |
4.35 USDOTUnited States Department of Transportati…
|
||
ConOps-1003 |
4.36 UTCuniversal coordinated time
|
||
ConOps-1004 |
4.37 Wi-Fiwireless network protocols
|
||
ConOps-1005 |
4.38 WPworking party
|
||
ConOps-6 |
5 Current system or situation |
||
ConOps-7 |
5.1 GeneralThis clause describes the current situat…
|
||
ConOps-763 |
|
||
ConOps-764 |
|
||
ConOps-765 |
|
||
ConOps-766 |
The description of the current system is…
|
||
ConOps-8 |
5.2 Background, objectives and scope |
||
ConOps-163 |
5.2.1 BackgroundEven before Karl Friedrich Benz produced…
|
||
ConOps-164 | |||
ConOps-168 |
The sign reads: NOTICE TO OWNERS AND DRI…
|
||
ConOps-165 |
In fact, the world's first traffic signa…
|
||
ConOps-166 |
5.2.2 ObjectivesRules for the use of road transport are …
|
||
ConOps-683 |
|
||
ConOps-684 |
|
||
ConOps-685 |
|
||
ConOps-686 |
|
||
ConOps-687 |
|
||
ConOps-688 |
The objective of METR is to provide trav…
|
||
ConOps-167 |
5.2.3 Scope of applicationWithin the current situation, most estab…
|
||
ConOps-689 |
|
||
ConOps-690 |
|
||
ConOps-1068 |
|
||
ConOps-691 |
|
||
ConOps-692 |
|
||
ConOps-693 |
|
||
ConOps-694 |
The scope of rules considered in the des…
|
||
ConOps-695 |
The METR design may also be applicable f…
|
||
ConOps-933 | NOTE: The intent is that this document can sup… | ||
ConOps-9 |
5.3 Operational policies and constraints |
||
ConOps-169 |
5.3.1 PoliciesThe typical current system is assumed to…
|
||
ConOps-421 |
|
||
ConOps-422 |
|
||
ConOps-423 |
|
||
ConOps-425 |
|
||
ConOps-424 |
|
||
ConOps-1065 | NOTE: While the term "campus" is often used to… | ||
ConOps-426 |
|
||
ConOps-427 |
|
||
ConOps-414 |
|
||
ConOps-417 |
|
||
ConOps-418 |
|
||
ConOps-640 |
|
||
ConOps-641 |
|
||
ConOps-642 |
|
||
ConOps-170 |
5.3.2 ConstraintsThe typical system is assumed to have th…
|
||
ConOps-409 |
|
constrained:
SoSR-45 Implement authorization policies
|
|
ConOps-410 |
|
constrained:
SoSR-167 Verify locations associated with rules
|
|
ConOps-411 |
|
constrained:
SoSR-148 Transport rule precedence
|
|
ConOps-412 |
|
constrained:
SoSR-168 weather terms (e.g., if a different spee…
SoSR-954 air quality and emission terms (e.g., wh…
SoSR-92 cyber location [SOURCE: ISO 24315-1:2024…
SoSR-123 Transport rule temporal characteristics
SoSR-94 the supporting data to be provided; and
SoSR-420 each supporting data provider authorized…
|
|
ConOps-413 |
|
constrained:
SoSR-101 Language neutral
|
|
ConOps-415 |
|
constrained:
SoSR-123 Transport rule temporal characteristics
|
|
ConOps-416 |
|
constrained:
SoSR-1811 Pre-announced rule completeness
SoSR-97 Emergent rule availability
|
|
ConOps-10 |
5.4 Description of the current situation |
||
ConOps-403 |
5.4.1 GeneralSubclause 5.4 provides an overview of ho…
|
||
ConOps-1070 |
5.4.2 ProcessesTable 1 provides a description of each p…
|
||
ConOps-1071 |
Process Description Responsible Stakehol…
|
||
ConOps-1072 |
5.4.3 Data flowsTable 2 describes the content of each da…
|
||
ConOps-1073 |
Output from Data flow Input to Descripti…
|
||
ConOps-1140 |
5.4.4 Responsible stakeholders |
||
ConOps-182 |
5.4.4.1 Rule makerA rule maker represents an entity with t…
|
||
ConOps-189 |
Most locations fall within a jurisdictio…
|
||
ConOps-696 | EXAMPLE: Legislative bodies often establish unpos… | ||
ConOps-697 | EXAMPLE: Regional government transportation agenc… | ||
ConOps-698 | EXAMPLE: Local government transportation agencies… | ||
ConOps-699 | EXAMPLE: Separate government entities sometimes e… | ||
ConOps-700 | EXAMPLE: Maintenance agencies often establish tem… | ||
ConOps-701 | EXAMPLE: Emergency response agencies can establis… | ||
ConOps-702 | EXAMPLE: Private entities can establish rules for… | ||
ConOps-706 | NOTE: Rules established by any rule maker can … | ||
ConOps-703 |
Rule makers are responsible for establis…
|
||
ConOps-704 |
Rule makers are ultimately responsible f…
|
||
ConOps-705 |
Rule makers also need to work with other…
|
||
ConOps-939 |
5.4.4.2 Implementer |
||
ConOps-196 |
5.4.4.2.1 Publicizing rulesAn implementer is responsible for perfor…
|
||
ConOps-707 |
|
||
ConOps-708 |
|
||
ConOps-709 |
|
||
ConOps-710 |
|
||
ConOps-711 |
|
||
ConOps-712 |
|
||
ConOps-713 |
|
||
ConOps-714 |
|
||
ConOps-1076 |
Properly performing these actions can re…
|
||
ConOps-715 |
5.4.4.2.2 ChallengesThese methods of publicizing rules are n…
|
||
ConOps-716 |
|
||
ConOps-717 |
|
||
ConOps-718 |
|
||
ConOps-719 |
|
||
ConOps-720 |
In recent years, these problems have bec…
|
||
ConOps-721 |
5.4.4.2.3 Rule implementationIn most cases, an unposted rule will typ…
|
||
ConOps-722 |
By comparison, a posted rule is typicall…
|
||
ConOps-173 |
5.4.4.3 Supporting data providerAt times, the transport user may have to…
|
||
ConOps-783 | EXAMPLE: A transport user can use in-vehicle cloc… | ||
ConOps-784 | EXAMPLE: A transport user can watch a traffic sig… | ||
ConOps-785 | EXAMPLE: A transport user can use a navigation sy… | ||
ConOps-786 | EXAMPLE: A transport user can use a navigation sy… | ||
ConOps-787 |
Within the existing system, information …
|
||
ConOps-174 |
5.4.4.4 Transport user |
||
ConOps-175 |
5.4.4.4.1 GeneralEach transport user has the primary resp…
|
||
ConOps-176 |
|
||
ConOps-177 |
|
||
ConOps-178 |
|
||
ConOps-934 |
|
||
ConOps-179 |
|
||
ConOps-180 |
5.4.4.4.2 AwarenessRegardless of the complexities of the ju…
|
||
ConOps-723 |
|
||
ConOps-724 |
|
||
ConOps-725 |
|
||
ConOps-726 |
5.4.4.4.3 Location accuracyWithin the existing system, a transport …
|
||
ConOps-727 |
5.4.4.4.4 ContextDetermining the precise location of a ju…
|
||
ConOps-181 |
Unposted rules can also change by jurisd…
|
||
ConOps-728 |
|
||
ConOps-729 |
|
||
ConOps-730 |
|
||
ConOps-731 |
|
||
ConOps-936 |
5.4.4.4.5 Proper judgementTransport users are also expected to exe…
|
||
ConOps-1077 |
5.4.5 Data Details |
||
ConOps-404 |
5.4.5.1 Rules |
||
ConOps-429 |
The rules established by a rule maker ne…
|
||
ConOps-215 |
5.4.5.1.1 Rule lifecycleRules change over time at varying rates.…
|
||
ConOps-405 |
Figure 3 indicates how rules can transit…
|
||
ConOps-430 |
A proposed rule [SOURCE: ISO 24315-1:202…
|
||
ConOps-771 |
|
||
ConOps-772 |
|
||
ConOps-773 |
|
||
ConOps-774 |
A rule can transition between states mul…
|
||
ConOps-775 | NOTE: When rules are defined with an expected … | ||
ConOps-407 |
5.4.5.1.2 Rule characteristicsWhile the standards for TCDs cover typic…
|
||
ConOps-632 | EXAMPLE: A lower speed limit applies at night on … | ||
ConOps-633 | EXAMPLE: A lower speed limit applies 1) at night,… | ||
ConOps-634 | EXAMPLE: A lower speed limit applies 1) at night … | ||
ConOps-631 |
Including multiple conditions on a rule,…
|
||
ConOps-408 |
5.4.5.1.3 Rule precedenceRules need to be unambiguous in their pr…
|
||
ConOps-197 |
5.4.5.1.4 Jurisdictional boundariesRules are limited by geographic boundari…
|
||
ConOps-198 |
5.4.5.1.5 ConclusionRules that apply to the transport enviro…
|
||
ConOps-1080 |
5.4.5.2 Traffic control devices |
||
ConOps-406 |
5.4.5.2.1 GeneralTCDs are one way by which implementers c…
|
||
ConOps-776 |
|
||
ConOps-777 |
|
||
ConOps-778 |
|
||
ConOps-779 |
|
||
ConOps-780 |
While these documents are informative an…
|
||
ConOps-781 |
As an example, within the United States,…
|
||
ConOps-1079 |
5.4.5.2.2 Maintenance |
||
ConOps-1078 |
In addition, the infrastructure used to …
|
||
ConOps-767 |
|
||
ConOps-768 |
|
||
ConOps-769 |
|
||
ConOps-1081 | |||
ConOps-770 |
Legal requirements to maintain TCDs vary…
|
||
ConOps-1082 |
5.4.5.2.3 Public recordIn addition to TCDs, the implementer can…
|
||
ConOps-1083 |
5.4.5.2.4 EnvironmentMost jurisdictions have rules requiring …
|
||
ConOps-1084 |
5.4.5.2.5 Vehicle or deviceWithin the context of the ISO 24315 seri…
|
||
ConOps-202 |
5.5 Modes of operation for the current situationThe current situation can be described b…
|
||
ConOps-732 |
|
||
ConOps-733 |
|
||
ConOps-734 |
|
||
ConOps-735 |
|
||
ConOps-736 |
|
||
ConOps-737 |
|
||
ConOps-738 |
|
||
ConOps-739 |
|
||
ConOps-11 |
5.6 User classes and other involved personnel |
||
ConOps-203 |
5.6.1 GeneralSubclause 5.6 describes the major user c…
|
||
ConOps-204 |
5.6.2 Users subject to rulesUsers that are subject to rules distribu…
|
||
ConOps-740 |
|
||
ConOps-741 |
|
||
ConOps-742 |
|
||
ConOps-743 |
|
||
ConOps-744 |
|
||
ConOps-745 |
|
||
ConOps-746 |
|
||
ConOps-747 |
|
||
ConOps-748 |
|
||
ConOps-749 |
|
||
ConOps-750 |
|
||
ConOps-751 |
|
||
ConOps-752 |
|
||
ConOps-753 |
|
||
ConOps-754 |
|
||
ConOps-755 |
|
||
ConOps-756 |
|
||
ConOps-757 |
|
||
ConOps-758 |
|
||
ConOps-815 |
|
||
ConOps-759 |
|
||
ConOps-760 |
|
||
ConOps-761 |
|
||
ConOps-762 |
|
||
ConOps-205 |
5.6.3 Entities that establish rulesEntities that establish rules, which inc…
|
||
ConOps-788 |
|
||
ConOps-789 |
|
||
ConOps-790 |
|
||
ConOps-791 |
|
||
ConOps-792 |
|
||
ConOps-793 |
|
||
ConOps-794 |
|
||
ConOps-795 |
|
||
ConOps-796 |
|
||
ConOps-797 |
|
||
ConOps-798 |
|
||
ConOps-799 |
|
||
ConOps-800 |
|
||
ConOps-801 |
|
||
ConOps-802 |
|
||
ConOps-803 |
|
||
ConOps-816 |
|
||
ConOps-804 |
Infrastructure operators and field perso…
|
||
ConOps-206 |
5.6.4 Third party entitiesThird parties include:
|
||
ConOps-805 |
|
||
ConOps-806 |
|
||
ConOps-807 |
|
||
ConOps-808 |
|
||
ConOps-809 |
|
||
ConOps-817 |
|
||
ConOps-810 |
|
||
ConOps-811 |
|
||
ConOps-812 |
|
||
ConOps-813 |
|
||
ConOps-814 |
|
||
ConOps-1062 |
|
||
ConOps-207 |
5.7 Support environment |
||
ConOps-208 |
5.7.1 GeneralSubclause 5.7 describes the support conc…
|
||
ConOps-209 |
5.7.2 Sources of support |
||
ConOps-210 |
5.7.2.1 Travellers |
||
ConOps-942 |
5.7.2.1.1 GeneralTravellers are supported in discovering …
|
||
ConOps-818 |
|
||
ConOps-819 |
|
||
ConOps-824 |
|
||
ConOps-1063 |
|
||
ConOps-820 |
5.7.2.1.2 Vehicle maintenanceWithin the current environment, travelle…
|
||
ConOps-821 |
If a vehicle is disabled, it can be towe…
|
||
ConOps-822 |
5.7.2.1.3 Technology updatesTechnology devices (e.g., smartphones, V…
|
||
ConOps-826 |
|
||
ConOps-827 |
|
||
ConOps-828 |
|
||
ConOps-211 |
5.7.2.2 Delivery service usersDelivery service users are supported in …
|
||
ConOps-829 |
|
||
ConOps-212 |
5.7.2.3 Driving automation systemsDriving automation systems are supported…
|
||
ConOps-830 |
|
||
ConOps-831 |
|
||
ConOps-1064 |
|
||
ConOps-832 |
|
||
ConOps-213 |
5.7.2.4 Vehicle/device ownersVehicle/device owners are supported in d…
|
||
ConOps-833 |
|
||
ConOps-834 |
|
||
ConOps-835 |
|
||
ConOps-214 |
5.7.2.5 Transport service providersTransport service providers are supporte…
|
||
ConOps-836 |
|
||
ConOps-837 |
|
||
ConOps-838 |
|
||
ConOps-17 |
6 Justification for and nature of changes |
||
ConOps-216 |
6.1 GeneralThis clause describes the shortcomings o…
|
||
ConOps-217 |
6.2 Justification of changes |
||
ConOps-682 |
6.2.1 GeneralThis document specifies the operational …
|
||
ConOps-647 |
6.2.2 Evolving transport environmentWe live in a transformative time with re…
|
||
ConOps-646 |
6.2.3 Discrepancy ReportsPart of the plan to ensure trustworthy i…
|
||
ConOps-649 |
A user can detect a discrepancy [SOURCE:…
|
||
ConOps-19 |
6.3 User need statements |
||
ConOps-432 |
6.3.1 Trustworthiness Needs |
||
ConOps-452 |
6.3.1.1 Trustworthiness — Reliability — AccuracyA METR user [SOURCE: ISO 24315-1:2024, 3…
|
fulfilled by:
SoSR-526 Resulting action
SoSR-831 Function
SoSR-559 Resulting action
SoSR-867 Function
SoSR-356 electronic discrepancies; and
SoSR-355 physical discrepancies;
SoSR-610 Resulting action
SoSR-858 Function
SoSR-1399 Data quality
SoSR-979 Verified information
SoSR-167 Verify locations associated with rules
SoSR-62 Verify rule consistency
SoSR-677 Ensure data quality
SoSR-679 Integrity
reflected by:
ConOps-1095 Process Description Responsible Stakehol…
SoSR-1749 Adapter system developer
SoSR-1669 Distributor
derived from:
SP-46 Peer roles need the ability to coordinat…
SP-48 Disseminators need to be able to share c…
SP-51 The feedback loop needs to include the r…
SP-109 The METR ConOps will be written so that …
SP-114 Rules provided by METR should be complet…
SP-131 The ConOps should indicate the importanc…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-278 Rule discrepancy
|
|
ConOps-433 |
6.3.1.2 Trustworthiness — Reliability — Availability — ConnectivityA METR user needs to be able to download…
|
fulfilled by:
SoSR-74 METR information availability
SoSR-678 Availability
SoSR-1811 Pre-announced rule completeness
derived from:
SP-165 In some cases, authorities might disable…
SP-187 Users should be able to discover when th…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-271 ADS fallback based on METR information
ConOps-290 Download rules
ConOps-286 Reporting inconsistent data
|
|
ConOps-434 |
6.3.1.3 Trustworthiness — Reliability — Availability — Geographic boundariesA METR user needs to be aware of the jur…
|
fulfilled by:
SoSR-678 Availability
SoSR-878 distribution service; and
SoSR-880 distribution service; and
SoSR-221 the geographical boundaries of the defin…
derived from:
SP-24 State of rule availability should be cap…
SP-56 There needs to be a fifth catalogue stat…
SP-183 User systems need to be able to determin…
SP-190 METR data must be reliable and provided …
SP-192 Transport user systems need to know what…
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-270 Pit stop
ConOps-290 Download rules
|
|
ConOps-435 |
6.3.1.4 Trustworthiness — Reliability — Availability — Rule coverageA METR user needs to be aware of the ava…
|
fulfilled by:
SoSR-678 Availability
SoSR-65 Rule catalogue
SoSR-796 Transport rules
reflected by:
SoSR-1669 Distributor
derived from:
SP-24 State of rule availability should be cap…
SP-56 There needs to be a fifth catalogue stat…
SP-125 METR needs to be able to indicate how co…
SP-182 The rule categories should be standardiz…
SP-183 User systems need to be able to determin…
SP-190 METR data must be reliable and provided …
SP-192 Transport user systems need to know what…
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-290 Download rules
|
|
ConOps-436 |
6.3.1.5 Trustworthiness — Reliability — Availability — Supporting data coverageA METR user needs to be aware of the ava…
|
fulfilled by:
SoSR-75 availability of each data provider [SOUR…
|
|
ConOps-456 |
6.3.1.6 Trustworthiness — Reliability — Availability — InterruptionsA METR user needs to be able to rely upo…
|
fulfilled by:
SoSR-1813 Ensure data resiliency
SoSR-967 System resiliency
|
|
ConOps-437 |
6.3.1.7 Trustworthiness — Reliability — Availability — DegradationA METR user needs to be aware of degrade…
|
fulfilled by:
SoSR-678 Availability
SoSR-55 Manage services
SoSR-1814 Connectivity awareness
derived from:
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-287 Encountering a disabled traffic signal
|
|
ConOps-446 |
6.3.1.8 Trustworthiness — Reliability — CompletenessA METR user needs all relevant data for …
|
fulfilled by:
SoSR-831 Function
SoSR-867 Function
SoSR-858 Function
SoSR-1403 Emerging rule availability
SoSR-228 METR device management
SoSR-1811 Pre-announced rule completeness
SoSR-97 Emergent rule availability
SoSR-129 vehicle terms (e.g., what vehicles quali…
SoSR-128 facility terms (e.g., if there is a defa…
SoSR-168 weather terms (e.g., if a different spee…
SoSR-954 air quality and emission terms (e.g., wh…
SoSR-147 restriction terms (e.g., what qualifies …
SoSR-404 user terms (e.g., class of driver licens…
SoSR-405 usage terms (e.g., delivery for hire).
SoSR-64 Maintain rules
derived from:
SP-23 State of rules in force on the transport…
SP-32 User systems need high confidence that t…
SP-51 The feedback loop needs to include the r…
SP-114 Rules provided by METR should be complet…
SP-119 In order to be trustworthy and relied up…
SP-120 In order to claim support for any rule d…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-258 Refresh rule set
ConOps-290 Download rules
ConOps-298 On-board management of rules
ConOps-276 Rental car
|
|
ConOps-438 |
6.3.1.9 Trustworthiness — Reliability — Quality — ClarityA METR user needs rules to be unambiguou…
|
fulfilled by:
SoSR-867 Function
SoSR-79 General
reflected by:
ConOps-1095 Process Description Responsible Stakehol…
derived from:
SP-46 Peer roles need the ability to coordinat…
SP-48 Disseminators need to be able to share c…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-260 Start of snowfall
ConOps-292 Encountering rain
|
|
ConOps-439 |
6.3.1.10 Trustworthiness — Reliability — Quality — ExpirationA METR user needs to be aware when previ…
|
fulfilled by:
SoSR-80 Freshness period
incorporates to:
ConOps-258 Refresh rule set
ConOps-272 Starting outside of METR coverage
|
|
ConOps-440 |
6.3.1.11 Trustworthiness — Reliability — Quality — Legal statusA METR user needs to be aware of the enf…
|
fulfilled by:
SoSR-121 Transport rule enforceability
derived from:
SP-190 METR data must be reliable and provided …
SP-193 Transport user systems need to know how …
SP-196 The information provided by METR is safe…
SP-201 Facilities that support METR need to ind…
incorporates to:
ConOps-269 Snow chain requirements
|
|
ConOps-441 |
6.3.1.12 Trustworthiness — Reliability — Quality — Confidence metricsA METR user needs to be aware of how muc…
|
fulfilled by:
SoSR-1399 Data quality
SoSR-1816 Verification level
SoSR-67 Provenance of information
SoSR-961 Confidence Metrics
SoSR-977 indicate the confirmed discrepancy;
derived from:
SP-79 What is the legal standing of C-ITS data…
SP-136 Transport user systems need insights int…
SP-137 Need to support (and convey to users) th…
SP-163 For the foreseeable future, METR should …
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-278 Rule discrepancy
|
|
ConOps-442 |
6.3.1.13 Trustworthiness — Reliability — ResilienceA METR user needs the METR environment t…
|
fulfilled by:
SoSR-1373 Function
SoSR-1813 Ensure data resiliency
SoSR-678 Availability
SoSR-209 Resource management
SoSR-967 System resiliency
SoSR-968 System availability
derived from:
SP-128 METR cannot rely on just one path for da…
SP-162 METR needs to be resilient as possible i…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-286 Reporting inconsistent data
|
|
ConOps-443 |
6.3.1.14 Trustworthiness — Reliability — Timeliness — RulesA METR user needs to be aware of each ru…
|
fulfilled by:
SoSR-526 Resulting action
SoSR-843 Function
SoSR-1373 Function
SoSR-1398 Response time
SoSR-480 Response time
SoSR-339 Emerging rule availability
SoSR-1811 Pre-announced rule completeness
SoSR-97 Emergent rule availability
SoSR-205 Transport rule status
SoSR-844 Transport rule expected implementation d…
reflected by:
SoSR-1669 Distributor
derived from:
SP-30 Withdrawn/rescinded rules need to be pub…
SP-35 Push is probably needed for coordination…
SP-38 Centralized dynamic rules either need tr…
SP-45 The preferred implementation is that a u…
SP-49 A mobile refresh provider should be char…
SP-71 Evacuation plans should be distributed i…
SP-94 Each individual rule should have its own…
SP-110 METR needs to be able to advertise when …
SP-123 Responders and field crews often have ne…
SP-144 It might be worth including an optional …
SP-154 METR should include pavement markings, i…
SP-156 Locally implemented/activated rules need…
SP-170 Pedestrians, especially those with disab…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-258 Refresh rule set
ConOps-265 Download rule set for long journey
ConOps-266 Encountering road works
ConOps-267 Encountering a new traffic control devic…
ConOps-268 Encountering a variable speed limit
ConOps-269 Snow chain requirements
ConOps-290 Download rules
ConOps-293 Emergent rules due to emergency
ConOps-294 Downloading new rules en-route
ConOps-295 Transition to manual control
ConOps-296 Turn prohibited
ConOps-276 Rental car
ConOps-301 Navigation to meeting spot
ConOps-302 Kerbside pickup
ConOps-252 Parking the van
ConOps-253 Sidewalk closure
ConOps-283 Evacuation orders
ConOps-284 Manual traffic directions
|
|
ConOps-444 |
6.3.1.15 Trustworthiness — Reliability — Timeliness — Supporting dataA METR user needs to be aware of the cur…
|
fulfilled by:
SoSR-75 availability of each data provider [SOUR…
SoSR-92 cyber location [SOURCE: ISO 24315-1:2024…
SoSR-94 the supporting data to be provided; and
SoSR-420 each supporting data provider authorized…
SoSR-1817 Obtain necessary supporting data
SoSR-508 Process rules
derived from:
SP-29 Each METR rule (e.g., give way to emerge…
SP-45 The preferred implementation is that a u…
SP-55 To the extent that C-ITS data is exchang…
SP-86 Some conditions might require dynamic da…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-259 Snowy conditions
ConOps-267 Encountering a new traffic control devic…
ConOps-268 Encountering a variable speed limit
ConOps-269 Snow chain requirements
ConOps-292 Encountering rain
ConOps-287 Encountering a disabled traffic signal
|
|
ConOps-445 |
6.3.1.16 Trustworthiness — Reliability — TransparencyA METR user needs data that are transpar…
|
fulfilled by:
SoSR-345 Disclose use of information
SoSR-100 Open specification
SoSR-67 Provenance of information
derived from:
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-275 Configuring the car
ConOps-305 Defence
ConOps-306 Prosecution
ConOps-307 Rebuttal
|
|
ConOps-447 |
6.3.1.17 Trustworthiness — Reliability — Usability — Language neutralityA METR user needs rules to be exchanged …
|
fulfilled by:
SoSR-101 Language neutral
derived from:
SP-26 All rules should be defined in a languag…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-275 Configuring the car
|
|
ConOps-448 |
6.3.1.18 Trustworthiness — Reliability — Usability — FeaturesA METR user needs to be aware of the cap…
|
fulfilled by:
SoSR-102 Feature catalogue
reflected by:
SoSR-1669 Distributor
derived from:
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
|
|
ConOps-450 |
6.3.1.19 Trustworthiness — Security — Authority — Access controlA METR user needs to have confidence tha…
|
fulfilled by:
SoSR-679 Integrity
SoSR-105 Access control for data
SoSR-887 Access control for operations
derived from:
SP-42 ConOps should explain that all component…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-258 Refresh rule set
ConOps-305 Defence
|
|
ConOps-455 |
6.3.1.20 Trustworthiness — Security — Authority — Data privacyA METR user needs to have confidence tha…
|
fulfilled by:
SoSR-965 Limited data storage
SoSR-107 Ensure data privacy
derived from:
SP-58 User privacy needs to be protected, espe…
SP-68 User requests should be confidential and…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-265 Download rule set for long journey
|
|
ConOps-454 |
6.3.1.21 Trustworthiness — Security — Authority — LegitimacyA METR user needs to be aware of the aut…
|
fulfilled by:
SoSR-92 cyber location [SOURCE: ISO 24315-1:2024…
SoSR-962 information required to authenticate the…
SoSR-963 an indication of the data that the data …
SoSR-94 the supporting data to be provided; and
SoSR-420 each supporting data provider authorized…
derived from:
SP-79 What is the legal standing of C-ITS data…
SP-121 Users need to be aware of when they shou…
SP-181 Each METR component needs to be certifie…
SP-183 User systems need to be able to determin…
SP-190 METR data must be reliable and provided …
SP-192 Transport user systems need to know what…
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-276 Rental car
|
|
ConOps-449 |
6.3.1.22 Trustworthiness — Security — ConfidentialityA METR user needs to have confidence tha…
|
fulfilled by:
SoSR-103 Ensure confidentiality of stored informa…
SoSR-104 Confidential communications
derived from:
SP-68 User requests should be confidential and…
SP-96 Unless otherwise indicated, the ConOps s…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-258 Refresh rule set
ConOps-265 Download rule set for long journey
|
|
ConOps-451 |
6.3.1.23 Trustworthiness — Security — Integrity — AccountabilityWithin established data privacy [SOURCE:…
|
fulfilled by:
SoSR-952 Supporting data
SoSR-679 Integrity
SoSR-106 Maintain change log
SoSR-67 Provenance of information
derived from:
SP-13 Trustworthiness should include non-repud…
SP-21 The ConOps needs to identify accountabil…
SP-47 METR must provide accountability such th…
SP-84 We need to indicate that each system nee…
SP-112 All rules should be signed by the transl…
SP-151 METR should provide a way for an entity …
SP-184 Users need to be able to determine the s…
SP-188 Each METR component needs to support non…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
SP-197 METR data needs to be available to users…
incorporates to:
ConOps-305 Defence
ConOps-306 Prosecution
ConOps-307 Rebuttal
|
|
ConOps-453 |
6.3.1.24 Trustworthiness — Security — Integrity — AuthenticityA METR user needs to be able to authenti…
|
fulfilled by:
SoSR-48 Obtain policies
SoSR-50 Implement enrolment policies
SoSR-45 Implement authorization policies
SoSR-52 Implement misbehaviour reporting policie…
SoSR-51 Implement revocation policies
SoSR-49 Ensure authenticated communications
SoSR-150 Maintain security certificates
SoSR-957 General
SoSR-959 General
derived from:
SP-42 ConOps should explain that all component…
SP-137 Need to support (and convey to users) th…
SP-138 Users need all rules to be digitally sig…
SP-190 METR data must be reliable and provided …
SP-196 The information provided by METR is safe…
incorporates to:
ConOps-258 Refresh rule set
|
|
ConOps-457 |
6.3.2 User needs |
||
ConOps-458 |
6.3.2.1 User — Distributor — DiscoveryA METR user needs to discover the approp…
|
fulfilled by:
SoSR-878 distribution service; and
SoSR-880 distribution service; and
reflected by:
ConOps-624 Service registration and discovery servi…
derived from:
SP-62 Users need a way to discover disseminato…
SP-126 METR providers might need to be certifie…
SP-129 Identification of the disseminator is ou…
incorporates to:
ConOps-270 Pit stop
ConOps-290 Download rules
ConOps-276 Rental car
|
|
ConOps-459 |
6.3.2.2 User — Distributor — Terms of serviceA METR user needs to be able to discover…
|
fulfilled by:
SoSR-108 Terms of service
|
|
ConOps-460 |
6.3.2.3 User — Connectivity — PreferencesA METR user needs to be able to identify…
|
fulfilled by:
SoSR-217 Use preferred communications
derived from:
SP-8 Users have a need to indicate their pref…
incorporates to:
ConOps-265 Download rule set for long journey
|
|
ConOps-461 |
6.3.2.4 User — Awareness — Jurisdictional classification schemesA METR user needs to understand the clas…
|
fulfilled by:
SoSR-129 vehicle terms (e.g., what vehicles quali…
SoSR-128 facility terms (e.g., if there is a defa…
SoSR-168 weather terms (e.g., if a different spee…
SoSR-954 air quality and emission terms (e.g., wh…
SoSR-147 restriction terms (e.g., what qualifies …
SoSR-404 user terms (e.g., class of driver licens…
SoSR-405 usage terms (e.g., delivery for hire).
derived from:
SP-104 Road types regulated by a jurisdiction n…
SP-171 VRUs/VRVs need to be aware of the classe…
SP-192 Transport user systems need to know what…
incorporates to:
ConOps-291 Hazardous goods
ConOps-297 Crossing a major border
ConOps-280 Micromobility and VRUs
ConOps-253 Sidewalk closure
|
|
ConOps-462 |
6.3.2.5 User — Awareness — Self-awarenessA METR user needs to be sufficiently awa…
|
fulfilled by:
SoSR-476 manually reported characteristics (i.e.,…
SoSR-477 detectable characteristics;
SoSR-478 static characteristics; and
SoSR-662 METR information type (e.g., rule catalo…
derived from:
SP-64 METR filtering needs to accommodate the …
SP-102 Vehicle types regulated by a jurisdictio…
SP-192 Transport user systems need to know what…
incorporates to:
ConOps-291 Hazardous goods
ConOps-297 Crossing a major border
ConOps-280 Micromobility and VRUs
ConOps-301 Navigation to meeting spot
ConOps-252 Parking the van
ConOps-253 Sidewalk closure
|
|
ConOps-463 |
6.3.2.6 User — Awareness — MappingA METR user needs electronic map(s) for …
|
fulfilled by:
SoSR-1247 availability of both maps and map update…
SoSR-1248 being able to align the map quickly and …
SoSR-114 Transport rule location
SoSR-234 Define location accurately
SoSR-353 Mapping
derived from:
SP-172 Motor vehicle systems need to be aware o…
SP-194 Map information within METR has to be ab…
incorporates to:
ConOps-261 Operation of a traffic signal
ConOps-277 Campus rules
ConOps-252 Parking the van
ConOps-283 Evacuation orders
|
|
ConOps-464 |
6.3.2.7 User — Awareness — GeopositioningA METR user needs to be able to determin…
|
fulfilled by:
SoSR-171 Determine user's location
incorporates to:
ConOps-258 Refresh rule set
ConOps-261 Operation of a traffic signal
ConOps-277 Campus rules
ConOps-252 Parking the van
ConOps-253 Sidewalk closure
|
|
ConOps-465 |
6.3.2.8 User — Conflicts — DetectedA METR user needs to be aware of confirm…
|
fulfilled by:
SoSR-843 Function
SoSR-977 indicate the confirmed discrepancy;
SoSR-978 indicate whether continued discrepancy r…
SoSR-976 provide guidance as to how the discrepan…
derived from:
SP-88 The ConOps should allow flexibility for …
SP-89 The ConOps should allow any vehicle (tha…
SP-90 A vehicle reporting a conflict should ha…
SP-91 A disseminator should not publicize repo…
incorporates to:
ConOps-286 Reporting inconsistent data
|
|
ConOps-466 |
6.3.2.9 User — Facility — Defined areaA METR user needs to be aware of the rel…
|
fulfilled by:
SoSR-221 the geographical boundaries of the defin…
SoSR-803 the location of the transport facility […
SoSR-169 the jurisdictional entity with authority…
derived from:
SP-139 METR needs to be able to accommodate hig…
SP-140 METR needs to be able to accommodate roa…
incorporates to:
ConOps-297 Crossing a major border
ConOps-277 Campus rules
|
|
ConOps-467 |
6.3.2.10 User — Jurisdiction — Sub-areasA METR user needs to be aware of any def…
|
fulfilled by:
SoSR-221 the geographical boundaries of the defin…
SoSR-337 the jurisdictional entity with authority…
SoSR-65 Rule catalogue
derived from:
SP-141 METR needs to be able to accommodate jur…
SP-143 METR needs to be able to accommodate ind…
incorporates to:
ConOps-277 Campus rules
|
|
ConOps-468 |
6.3.2.11 User — Rule — AwarenessA METR user needs to be aware of all ava…
|
fulfilled by:
SoSR-855 Function
SoSR-472 proximity from a point location;
SoSR-473 proximity along a route; and
SoSR-474 user-defined area.
SoSR-476 manually reported characteristics (i.e.,…
SoSR-477 detectable characteristics;
SoSR-478 static characteristics; and
SoSR-662 METR information type (e.g., rule catalo…
SoSR-339 Emerging rule availability
SoSR-162 Remote emergent rules
SoSR-1811 Pre-announced rule completeness
derived from:
SP-86 Some conditions might require dynamic da…
SP-174 There should be the ability for regulato…
SP-177 METR should be able to convey informatio…
SP-179 METR needs to be able to support rules c…
SP-180 METR needs to support permitting micromo…
incorporates to:
ConOps-258 Refresh rule set
ConOps-271 ADS fallback based on METR information
ConOps-291 Hazardous goods
ConOps-280 Micromobility and VRUs
|
|
ConOps-469 |
6.3.2.12 User — Rule — CharacteristicsA METR user needs to be aware of the rel…
|
fulfilled by:
SoSR-79 General
SoSR-92 cyber location [SOURCE: ISO 24315-1:2024…
SoSR-69 METR information identifier
SoSR-70 METR information type
SoSR-67 Provenance of information
SoSR-80 Freshness period
SoSR-114 Transport rule location
SoSR-123 Transport rule temporal characteristics
SoSR-122 Transport rule applicability characteris…
SoSR-205 Transport rule status
SoSR-121 Transport rule enforceability
SoSR-148 Transport rule precedence
SoSR-90 Transport rule priority
SoSR-94 the supporting data to be provided; and
SoSR-420 each supporting data provider authorized…
derived from:
SP-29 Each METR rule (e.g., give way to emerge…
SP-40 There is a lack of consistent terminolog…
SP-69 See slide for examples of rule character…
SP-70 METR should allow rule characteristcis t…
SP-94 Each individual rule should have its own…
SP-103 The characteristics used by a jurisdicti…
SP-105 METR needs to convey the location for ev…
SP-106 METR needs to support rules that charact…
SP-111 Characteristics should include permits, …
SP-177 METR should be able to convey informatio…
incorporates to:
ConOps-259 Snowy conditions
ConOps-260 Start of snowfall
ConOps-261 Operation of a traffic signal
ConOps-252 Parking the van
ConOps-253 Sidewalk closure
|
|
ConOps-470 |
6.3.2.13 User — Rule — DefinitionA METR user needs to be able to become a…
|
fulfilled by:
SoSR-129 vehicle terms (e.g., what vehicles quali…
SoSR-128 facility terms (e.g., if there is a defa…
SoSR-168 weather terms (e.g., if a different spee…
SoSR-954 air quality and emission terms (e.g., wh…
SoSR-147 restriction terms (e.g., what qualifies …
SoSR-404 user terms (e.g., class of driver licens…
SoSR-405 usage terms (e.g., delivery for hire).
SoSR-797 Transport rule type
derived from:
SP-40 There is a lack of consistent terminolog…
incorporates to:
ConOps-297 Crossing a major border
|
|
ConOps-471 |
6.3.2.14 User — Rule — PrecedenceA METR user needs to be aware of the pre…
|
fulfilled by:
SoSR-148 Transport rule precedence
derived from:
SP-14 METR should indicate the level of legal …
SP-36 Hierarchy of rules should support the co…
SP-161 Overrides of normal traffic control is a…
incorporates to:
ConOps-279 Permitted parking
ConOps-284 Manual traffic directions
ConOps-285 Ignoring signs that are overridden
|
|
ConOps-472 |
6.3.2.15 User — Rule — Distribution — PrioritizationA METR user needs rules to be distribute…
|
fulfilled by:
SoSR-220 Provide rules in priority order
SoSR-90 Transport rule priority
incorporates to:
ConOps-296 Turn prohibited
ConOps-283 Evacuation orders
|
|
ConOps-473 |
6.3.2.16 User — Rule — Distribution — EfficiencyA METR user needs to obtain relevant rul…
|
fulfilled by:
SoSR-1385 Location constraint
SoSR-1390 Content constraint
SoSR-870 Time to refresh
SoSR-149 Efficient exchange
SoSR-929 Filtering
derived from:
SP-37 Pull process must support filtering
SP-38 Centralized dynamic rules either need tr…
SP-39 Filtering should include almost all para…
SP-50 Need to be able to filter rules based on…
SP-64 METR filtering needs to accommodate the …
SP-101 The ConOps should allow the definition o…
SP-107 METR users need to be able to identify w…
incorporates to:
ConOps-258 Refresh rule set
ConOps-280 Micromobility and VRUs
|
|
ConOps-474 |
6.3.2.17 User — Rule — Applicability — PermitsA METR user needs to be aware of the per…
|
2023-01-20: Kenneth Vaughn
Should this be removed from the UN or moved to a section that relates to roles outside of the defined METR boundary? (We previously decided that non-public rules are not in-scope.) DT=> Keep as a UN and trace to a Consumer System assumption. Also explain that there should be a standard interface for consumer systems to read in permits, but this is also outside of our scope. |
fulfilled by:
SoSR-476 manually reported characteristics (i.e.,…
SoSR-1818 authenticated permits (e.g., permissions…
derived from:
SP-12 Need to support rules related to specifi…
SP-149 METR needs to provide a way for the vehi…
SP-153 METR needs to support both permits that …
SP-180 METR needs to support permitting micromo…
incorporates to:
ConOps-262 Locating appropriate parking
ConOps-279 Permitted parking
ConOps-301 Navigation to meeting spot
ConOps-302 Kerbside pickup
|
ConOps-475 |
6.3.2.18 User — Rule — Journey planningA METR user needs to be able to obtain a…
|
fulfilled by:
SoSR-1387 proximity along a route; or
SoSR-473 proximity along a route; and
SoSR-474 user-defined area.
derived from:
SP-9 User systems might support the ability t…
incorporates to:
ConOps-258 Refresh rule set
ConOps-265 Download rule set for long journey
|
|
ConOps-476 |
6.3.2.19 User — Rule — ObsolescenceA METR user needs to be able to operate …
|
fulfilled by:
SoSR-903 Avoiding vehicle inoperability
derived from:
SP-99 The ConOps should indicate that for the …
SP-100 Any remote refresh would have to be prov…
incorporates to:
ConOps-272 Starting outside of METR coverage
|
|
ConOps-477 |
6.3.2.20 User — Status — Manual inputsA METR user needs to be aware of vehicle…
|
2023-01-20: Kenneth Vaughn
Trace to assumption in Consumer system |
fulfilled by:
SoSR-476 manually reported characteristics (i.e.,…
derived from:
SP-164 An ADS-equipped vehicle might need some …
incorporates to:
ConOps-269 Snow chain requirements
|
ConOps-478 |
6.3.2.21 User — Status — Environmental awarenessA METR user needs to be able to determin…
|
2023-01-20: Kenneth Vaughn
Trace to assumption in Consumer system |
fulfilled by:
SoSR-173 Determine environmental conditions
incorporates to:
ConOps-292 Encountering rain
|
ConOps-479 |
6.3.2.22 User — System — UpgradeA METR user needs the METR network to pa…
|
fulfilled by:
SoSR-210 METR updates and patches
derived from:
SP-198 Every version of METR needs to be backwa…
|
|
ConOps-480 |
6.3.3 Rule maker needs |
||
ConOps-481 |
6.3.3.1 Rule maker — Jurisdictions — IdentificationWithin a jurisdictional area, the rule m…
|
fulfilled by:
SoSR-337 the jurisdictional entity with authority…
derived from:
SP-173 A private company (e.g., vehicle share o…
incorporates to:
ConOps-279 Permitted parking
|
|
ConOps-482 |
6.3.3.2 Rule maker — Rule signerA rule maker needs to identify those ind…
|
fulfilled by:
SoSR-159 Maintain awareness of rule makers
SoSR-677 Ensure data quality
SoSR-887 Access control for operations
SoSR-161 Transport rule signing organization
incorporates to:
ConOps-276 Rental car
|
|
ConOps-483 |
6.3.3.3 Rule maker — Translation agentA rule maker needs to identify those ind…
|
fulfilled by:
SoSR-887 Access control for operations
SoSR-67 Provenance of information
SoSR-1472 Transport rule signing agent
incorporates to:
ConOps-276 Rental car
|
|
ConOps-484 |
6.3.3.4 Rule maker — Publicize — Rules at a distanceA rule maker might need to publicize eme…
|
fulfilled by:
SoSR-162 Remote emergent rules
derived from:
SP-155 Locally implemented/activated rules migh…
incorporates to:
ConOps-267 Encountering a new traffic control devic…
ConOps-268 Encountering a variable speed limit
ConOps-293 Emergent rules due to emergency
|
|
ConOps-485 |
6.3.3.5 Rule maker — Rules — Non-electronicThe rule maker needs to be able to infor…
|
fulfilled by:
SoSR-354 whether the defined area is believed to …
incorporates to:
ConOps-284 Manual traffic directions
|
|
ConOps-486 |
6.3.3.6 Rule maker — Discrepancies — PrimaryA rule maker needs to be informed when a…
|
fulfilled by:
SoSR-62 Verify rule consistency
derived from:
SP-195 The METR ConOps should identify the need…
|
|
ConOps-487 |
6.3.3.7 Rule maker — Discrepancies — SecondaryA rule maker needs to be informed when s…
|
fulfilled by:
SoSR-867 Function
SoSR-632 location of the discrepancy;
SoSR-868 time at which the discrepancy was detect…
SoSR-630 type of discrepancy identified, such as:
SoSR-635 meta-data about the METR adapter system …
SoSR-631 image of the site;
SoSR-633 associated sensor readings; and
SoSR-634 free form notes.
SoSR-62 Verify rule consistency
SoSR-879 discrepancy handling service.
SoSR-881 discrepancy handling service.
derived from:
SP-15 Users should have a way to report discre…
SP-88 The ConOps should allow flexibility for …
SP-89 The ConOps should allow any vehicle (tha…
SP-90 A vehicle reporting a conflict should ha…
SP-115 When any conflict is discovered, it shou…
SP-195 The METR ConOps should identify the need…
incorporates to:
ConOps-278 Rule discrepancy
ConOps-254 Reporting unexpected conditions
ConOps-255 Propagation of conditions
ConOps-287 Encountering a disabled traffic signal
|
|
ConOps-488 |
6.3.3.8 Rule maker — Rule discovery serviceA rule maker needs to discover and valid…
|
fulfilled by:
SoSR-867 Function
derived from:
SP-168 In order to automatically update systems…
SP-195 The METR ConOps should identify the need…
|
|
ConOps-490 |
6.3.3.9 Rule maker — Independent verificationA rule maker needs to be able independen…
|
fulfilled by:
SoSR-355 physical discrepancies;
SoSR-578 Resulting action
SoSR-1399 Data quality
derived from:
SP-51 The feedback loop needs to include the r…
SP-197 METR data needs to be available to users…
|
|
ConOps-965 |
6.3.4 Third party needs |
||
ConOps-966 |
6.3.4.1 Third party — AuditingAuditors need to be able to retrieve his…
|
fulfilled by:
SoSR-1456 Function
SoSR-1470 Transport rule translation agent
SoSR-1471 Transport rule verification agent
SoSR-1472 Transport rule signing agent
|
|
ConOps-20 |
6.4 PrioritiesISO/IEC/IEEE 29148 indicates that an ope…
|
||
ConOps-218 |
6.5 Deferred user needs |
||
ConOps-219 |
6.5.1 GeneralSubclause 6.5 identifies user needs cons…
|
||
ConOps-220 |
6.5.2 User needs deferred to a future release |
||
ConOps-221 |
6.5.2.1 Precise legal meaning of rulesThe initial version of METR does not att…
|
||
ConOps-943 |
|
||
ConOps-944 |
|
||
ConOps-945 |
|
||
ConOps-946 |
|
||
ConOps-947 |
Future efforts can address areas of know…
|
||
ConOps-222 |
6.5.2.2 Aerial dronesThe initial edition of METR does not att…
|
derived from:
SP-175 METR should be designed so that it can b…
|
|
ConOps-223 |
6.5.2.3 Indoor pedestrian environmentsIndoor pedestrian environments are poten…
|
||
ConOps-224 |
6.5.3 User needs considered but not included |
||
ConOps-225 |
While the general design of METR might a…
|
||
ConOps-22 |
6.6 Assumptions and constraints |
||
ConOps-226 |
6.6.1 Assumptions |
||
ConOps-227 |
6.6.1.1 Users — ModesThe scope of METR is intended to include…
|
derived from:
SP-11 METR should cover the full scope of surf…
|
|
ConOps-228 |
6.6.1.2 Users — VarietyMETR users include humans (e.g., drivers…
|
derived from:
SP-10 METR should support ordinary traffic (i.…
|
|
ConOps-229 |
6.6.1.3 Users — Mixed environmentVehicles that support METR need to be ab…
|
derived from:
SP-3 Some users might not be connected to MET…
|
|
ConOps-230 |
6.6.1.4 Users — Stationary usersSome METR receivers will not be mobile (…
|
derived from:
SP-7 METR should support user systems that mi…
|
|
ConOps-231 |
6.6.1.5 Communications — Stationary components — Sufficient bandwidthSufficient communication bandwidth will …
|
fulfilled by:
SoSR-188 Internet-based communications
SoSR-919 publicly available communication technol…
|
|
ConOps-232 |
6.6.1.6 Communications — Mobile users — Mobile wireless internetAll mobile METR receivers will support m…
|
fulfilled by:
SoSR-188 Internet-based communications
SoSR-919 publicly available communication technol…
derived from:
SP-4 All ~mobile~ METR-enabled transport user…
SP-45 The preferred implementation is that a u…
|
|
ConOps-233 |
6.6.1.7 Communications — Mobile users — Instability of internet accessMobile wireless internet connectivity ca…
|
fulfilled by:
SoSR-919 publicly available communication technol…
derived from:
SP-5 Mobile wireless internet is not guarante…
|
|
ConOps-234 |
6.6.1.8 Communications — Mobile users — Areas without internet coverageMobile wireless internet can be unavaila…
|
fulfilled by:
SoSR-919 publicly available communication technol…
derived from:
SP-6 Mobile wireless internet might not be av…
|
|
ConOps-235 |
6.6.1.9 Communications — Mobile users — Short-range wirelessAll motor vehicles that support METR wil…
|
derived from:
SP-2 Road vehicles should support short-range…
SP-45 The preferred implementation is that a u…
|
|
ConOps-236 |
6.6.1.10 Communications — Delivery — Pre-announced rulesPre-announced rules will be retrieved at…
|
derived from:
SP-27 METR should be based on a centralized pu…
|
|
ConOps-237 |
6.6.1.11 Communications — Delivery — Emergent rulesMETR receivers will be notified of relev…
|
derived from:
SP-27 METR should be based on a centralized pu…
|
|
ConOps-967 |
|
||
ConOps-968 |
|
||
ConOps-247 |
6.6.1.12 Communications — Delivery — Supporting dataMETR will rely upon existing data source…
|
fulfilled by:
SoSR-920 inputs from supporting data providers as…
derived from:
SP-23 State of rules in force on the transport…
|
|
ConOps-238 |
6.6.1.13 Communications — Delivery — Third partyThis document assumes that there may be …
|
||
ConOps-239 |
6.6.1.14 Geopositioning — AccuracyVehicle sensors will be able to correspo…
|
||
ConOps-240 |
6.6.1.15 Safety — Rule makersRule makers are responsible for ensuring…
|
||
ConOps-241 |
6.6.1.16 Safety — UsersThe DDT includes the responsibility to p…
|
derived from:
SP-163 For the foreseeable future, METR should …
SP-185 User systems are responsible for operati…
|
|
ConOps-242 |
6.6.1.17 Safety — RelianceFor the foreseeable future, METR will be…
|
derived from:
SP-163 For the foreseeable future, METR should …
|
|
ConOps-243 |
6.6.2 Constraints |
||
ConOps-244 |
6.6.2.1 Communications — Delivery — EfficiencyMETR needs to be designed to enable effi…
|
fulfilled by:
SoSR-870 Time to refresh
derived from:
SP-93 A rule refresh should only provide the c…
|
|
ConOps-245 |
6.6.2.2 Forwards and backwards compatibilityEvery version of METR needs to be backwa…
|
fulfilled by:
SoSR-898 Backwards compatibility
SoSR-901 Forward compatibility
derived from:
SP-198 Every version of METR needs to be backwa…
|
|
ConOps-246 |
6.6.2.3 Existing standardsThe design of METR needs to rely upon ex…
|
fulfilled by:
SoSR-899 Leverage existing standards
derived from:
SP-31 METR will rely upon existing standards w…
SP-198 Every version of METR needs to be backwa…
|
|
ConOps-248 |
6.6.2.4 Limitations of short-range wireless communicationsShort range wireless communication chann…
|
fulfilled by:
SoSR-217 Use preferred communications
derived from:
SP-34 Use of push should be minimized while st…
|
|
ConOps-431 | NOTE: This might require the use of short-rang… | ||
ConOps-249 |
6.6.2.5 Aerial dronesThe design of METR needs to be flexible …
|
fulfilled by:
SoSR-901 Forward compatibility
derived from:
SP-175 METR should be designed so that it can b…
|
|
ConOps-428 |
6.6.2.6 Radio frequency regulationsMETR needs to comply with local regulati…
|
fulfilled by:
SoSR-56 Radio frequency regulations
|
|
ConOps-23 |
7 Concepts for the proposed system |
||
ConOps-491 |
7.1 GeneralThis clause describes all the key concep…
|
||
ConOps-492 |
7.2 Background, objectives, and scopeTo address the issues raised in Subclaus…
|
||
ConOps-493 |
7.3 Operational policies and constraints |
||
ConOps-494 |
7.3.1 PoliciesAll the policies defined in Subclause 5.…
|
||
ConOps-496 |
7.3.2 ConstraintsAll the constraints defined in Subclause…
|
||
ConOps-497 |
7.4 Description of the proposed system |
||
ConOps-498 |
7.4.1 OverviewSubclause 7.4 provides a vision for the …
|
||
ConOps-499 |
derived from:
SP-16 We should emphasize that the types of re…
|
||
ConOps-1141 | NOTE: The information contained within this su… | ||
ConOps-1069 | NOTE: For simplicity, Figure 8 shows a single … | ||
ConOps-1094 |
7.4.2 ProcessesTable 3 provides a description of each p…
|
||
ConOps-1095 |
Process Description Responsible Stakehol…
|
derived from:
SP-43 The ConOps needs to assign the responsib…
SP-45 The preferred implementation is that a u…
SP-46 Peer roles need the ability to coordinat…
SP-48 Disseminators need to be able to share c…
SP-51 The feedback loop needs to include the r…
SP-74 All roles are responsible for 1) identif…
SP-1 In order to provide a more seamless expe…
reflects:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-438 Trustworthiness — Reliability — Quality …
|
|
ConOps-1142 |
In addition to the processes in Table 3,…
|
||
ConOps-1096 |
7.4.3 Data flowsTable 4 provides a complete list of data…
|
||
ConOps-1097 |
Output from Data flow Input to Data flow…
|
||
ConOps-615 |
7.5 Modes of operation |
||
ConOps-616 |
7.5.1 GeneralSubclause 7.5 describes the various mode…
|
||
ConOps-617 |
7.5.2 Normal modeIn the normal mode, a METR receiver can …
|
||
ConOps-618 |
7.5.3 Degraded modeIn the degraded mode, the METR environme…
|
||
ConOps-894 |
|
||
ConOps-896 |
|
||
ConOps-898 |
|
||
ConOps-899 |
The degraded mode is only entered if the…
|
||
ConOps-619 |
7.5.4 Fallback modeThe fallback mode represents a condition…
|
||
ConOps-900 |
|
||
ConOps-901 |
|
||
ConOps-621 |
7.6 User classes and other involved personnelThe proposed system does not change the …
|
||
ConOps-622 |
7.7 Support environment |
||
ConOps-623 |
7.7.1 GeneralThe support environment includes the fac…
|
||
ConOps-620 |
7.7.2 Rule discovery serviceThe rule discovery service [SOURCE: ISO …
|
||
ConOps-1066 | NOTE: Within the METR design documents, the ru… | ||
ConOps-624 |
7.7.3 Service registration and discovery serviceThe ITS service registration and discove…
|
derived from:
SP-62 Users need a way to discover disseminato…
reflects:
ConOps-458 User — Distributor — Discovery
|
|
ConOps-625 |
7.7.4 Security serviceThe Cooperative ITS Credential Managemen…
|
||
ConOps-626 |
7.7.5 Technology servicesTechnology services provide base informa…
|
||
ConOps-902 |
|
||
ConOps-903 |
|
||
ConOps-627 |
7.7.6 METR CertificationThe METR Certification Manager is respon…
|
derived from:
SP-181 Each METR component needs to be certifie…
|
|
ConOps-628 |
7.7.7 MaintenanceMaintenance facilities will be responsib…
|
||
ConOps-629 |
7.7.8 EnforcementAn enforcer encourages compliance with t…
|
||
ConOps-630 |
7.7.9 Academic research and advocacyAcademic institutions and advocacy group…
|
||
ConOps-904 |
|
||
ConOps-905 |
|
||
ConOps-906 |
|
||
ConOps-35 |
8 Summary of impacts |
||
ConOps-36 |
8.1 Operational impactsMETR is expected to have the following i…
|
||
ConOps-907 |
|
||
ConOps-908 |
|
||
ConOps-909 |
|
||
ConOps-910 |
|
||
ConOps-911 |
|
||
ConOps-912 |
|
||
ConOps-913 |
|
||
ConOps-914 |
|
||
ConOps-915 |
|
||
ConOps-37 |
8.2 Organizational impactsMETR is expected to have the following i…
|
||
ConOps-930 |
|
||
ConOps-931 |
|
||
ConOps-932 |
|
||
ConOps-38 |
8.3 Impacts during developmentMETR is expected to have the following i…
|
||
ConOps-916 |
|
||
ConOps-917 |
|
||
ConOps-918 |
|
||
ConOps-919 |
|
||
ConOps-39 |
9 Analysis of the proposed system |
||
ConOps-40 |
9.1 BenefitsMETR is expected to provide the followin…
|
||
ConOps-920 |
|
||
ConOps-921 |
|
||
ConOps-41 |
9.2 Disadvantages and limitationsMETR is expected to present the followin…
|
||
ConOps-922 |
|
||
ConOps-923 |
|
||
ConOps-924 |
|
||
ConOps-925 |
|
||
ConOps-42 |
9.3 Alternatives consideredThe null alternative (i.e., not providin…
|
||
ConOps-34 |
10 Operational scenarios |
||
ConOps-308 |
10.1 GeneralThis annex is intended to provide an ove…
|
||
ConOps-256 |
10.2 Sandy the busy mother |
||
ConOps-257 |
10.2.1 GeneralOur first operational scenario is Sandy,…
|
||
ConOps-258 |
10.2.2 Refresh rule setWhen Sandy starts her minivan, component…
|
incorporates from:
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-439 Trustworthiness — Reliability — Quality …
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-450 Trustworthiness — Security — Authority —…
ConOps-449 Trustworthiness — Security — Confidentia…
ConOps-453 Trustworthiness — Security — Integrity —…
ConOps-464 User — Awareness — Geopositioning
ConOps-468 User — Rule — Awareness
ConOps-473 User — Rule — Distribution — Efficiency
ConOps-475 User — Rule — Journey planning
|
|
ConOps-259 |
10.2.3 Snowy conditionsLocal ordinances in Sandy’s locale speci…
|
incorporates from:
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-469 User — Rule — Characteristics
MDR-375 Supporting data
derived from:
SP-20 The ConOps should provide practical use …
SP-95 The ConOps should provide an example of …
SP-130 The ConOps should structure at least one…
SP-132 The ConOps might include a scenario with…
|
|
ConOps-260 |
10.2.4 Start of snowfallWithin this jurisdiction, a lower speed …
|
incorporates from:
ConOps-438 Trustworthiness — Reliability — Quality …
ConOps-469 User — Rule — Characteristics
MDR-375 Supporting data
MDR-377 Environmental conditions
|
|
ConOps-261 |
10.2.5 Operation of a traffic signalThe "motor vehicle right-of-way" rule se…
|
incorporates from:
ConOps-463 User — Awareness — Mapping
ConOps-464 User — Awareness — Geopositioning
ConOps-469 User — Rule — Characteristics
MDR-351 Location
MDR-375 Supporting data
|
|
ConOps-262 |
10.2.6 Locating appropriate parkingAs Sandy reaches her destination to meet…
|
incorporates from:
ConOps-474 User — Rule — Applicability — Permits
MDR-353 Map alignment
derived from:
SP-146 METR rules need to define areas reserved…
SP-150 A METR operational scenario should indic…
|
|
ConOps-263 |
10.3 Trip to grandma's house |
||
ConOps-264 |
10.3.1 OverviewLittle Red Riding Hood has decided to ta…
|
||
ConOps-265 |
10.3.2 Download rule set for long journeyBased on the information contained on he…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-455 Trustworthiness — Security — Authority —…
ConOps-449 Trustworthiness — Security — Confidentia…
ConOps-460 User — Connectivity — Preferences
ConOps-475 User — Rule — Journey planning
|
|
ConOps-266 |
10.3.3 Encountering road worksAs the ADS leaves Ms. Hood's neighbourho…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
MDR-351 Location
MDR-353 Map alignment
|
|
ConOps-267 |
10.3.4 Encountering a new traffic control deviceAs the vehicle proceeds through the work…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-484 Rule maker — Publicize — Rules at a dist…
derived from:
SP-20 The ConOps should provide practical use …
SP-81 The ConOps should include a use case tha…
SP-152 Process to deploy known rules includes p…
SP-186 Within our scenarios, we should assume t…
|
|
ConOps-963 | NOTE: The same process can be followed for the… | ||
ConOps-268 |
10.3.5 Encountering a variable speed limitAs Ms. Hood's vehicle gets onto the moto…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-484 Rule maker — Publicize — Rules at a dist…
|
|
ConOps-269 |
10.3.6 Snow chain requirementsAs Ms. Hood begins to cross the mountain…
|
incorporates from:
ConOps-440 Trustworthiness — Reliability — Quality …
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-477 User — Status — Manual inputs
|
|
ConOps-270 |
10.3.7 Pit stopAs the trip continues, Ms. Hood realizes…
|
incorporates from:
ConOps-434 Trustworthiness — Reliability — Availabi…
ConOps-458 User — Distributor — Discovery
|
|
ConOps-271 |
10.3.8 ADS fallback based on METR informationAs Ms. Hood nears her destination, the A…
|
incorporates from:
ConOps-433 Trustworthiness — Reliability — Availabi…
ConOps-468 User — Rule — Awareness
derived from:
SP-20 The ConOps should provide practical use …
SP-97 The ConOps should indicate that we assum…
SP-124 Between METR and the map data, ADS-equip…
|
|
ConOps-272 |
10.3.9 Starting outside of METR coverageAfter an extended visit with her grandmo…
|
incorporates from:
ConOps-439 Trustworthiness — Reliability — Quality …
ConOps-476 User — Rule — Obsolescence
derived from:
SP-98 The ConOps should provide an example use…
SP-99 The ConOps should indicate that for the …
SP-100 Any remote refresh would have to be prov…
|
|
ConOps-949 |
|
||
ConOps-950 |
|
||
ConOps-951 |
Since Ms. Hood's vehicle supports manual…
|
||
ConOps-288 |
10.4 Klaus the truck operator |
||
ConOps-289 |
10.4.1 OverviewKlaus drives a container-carrying commer…
|
||
ConOps-290 |
10.4.2 Download rulesWhile Klaus's truck is being loaded with…
|
incorporates from:
ConOps-433 Trustworthiness — Reliability — Availabi…
ConOps-434 Trustworthiness — Reliability — Availabi…
ConOps-435 Trustworthiness — Reliability — Availabi…
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-458 User — Distributor — Discovery
|
|
ConOps-291 |
10.4.3 Hazardous goodsToday's trip includes the transport of h…
|
incorporates from:
ConOps-461 User — Awareness — Jurisdictional classi…
ConOps-462 User — Awareness — Self-awareness
ConOps-468 User — Rule — Awareness
|
|
ConOps-292 |
10.4.4 Encountering rainAs Klaus begins his journey, he notices …
|
incorporates from:
ConOps-438 Trustworthiness — Reliability — Quality …
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-478 User — Status — Environmental awareness
MDR-376 General
|
|
ConOps-293 |
10.4.5 Emergent rules due to emergencyAs Klaus leaves the city, the METR recei…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-484 Rule maker — Publicize — Rules at a dist…
derived from:
SP-20 The ConOps should provide practical use …
SP-82 The ConOps should also include a use cas…
SP-157 Ad Hoc rules might provide detour inform…
|
|
ConOps-294 |
10.4.6 Downloading new rules en-routeThe ADS decides that the publicized deto…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
ConOps-295 |
10.4.7 Transition to manual controlThe METR receiver notifies the ADS of th…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
ConOps-296 |
10.4.8 Turn prohibitedAs Klaus continues to follow the detour,…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-472 User — Rule — Distribution — Prioritizat…
|
|
ConOps-297 |
10.4.9 Crossing a major borderAs Klaus continues along his route, he c…
|
incorporates from:
ConOps-461 User — Awareness — Jurisdictional classi…
ConOps-462 User — Awareness — Self-awareness
ConOps-466 User — Facility — Defined area
ConOps-470 User — Rule — Definition
|
|
ConOps-952 |
|
||
ConOps-953 |
|
||
ConOps-954 |
|
||
ConOps-955 |
|
||
ConOps-956 |
|
||
ConOps-957 |
|
||
ConOps-958 |
From Klaus's perspective, when the ADS i…
|
||
ConOps-298 |
10.4.10 On-board management of rulesOver time, the on-board electronics accu…
|
incorporates from:
ConOps-446 Trustworthiness — Reliability — Complete…
|
|
ConOps-273 |
10.5 Bilo the jet-set professor |
||
ConOps-274 |
10.5.1 OverviewBilo is an international expert in his f…
|
||
ConOps-275 |
10.5.2 Configuring the carAs a part of Bilo's rental car account, …
|
incorporates from:
ConOps-445 Trustworthiness — Reliability — Transpar…
ConOps-447 Trustworthiness — Reliability — Usabilit…
|
|
ConOps-276 |
10.5.3 Rental carIn addition to the rules that all other …
|
incorporates from:
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-454 Trustworthiness — Security — Authority —…
ConOps-458 User — Distributor — Discovery
ConOps-482 Rule maker — Rule signer
ConOps-483 Rule maker — Translation agent
|
|
ConOps-277 |
10.5.4 Campus rulesThe first stop on Bilo's trip is the uni…
|
incorporates from:
ConOps-463 User — Awareness — Mapping
ConOps-464 User — Awareness — Geopositioning
ConOps-466 User — Facility — Defined area
ConOps-467 User — Jurisdiction — Sub-areas
|
|
ConOps-278 |
10.5.5 Rule discrepancyAt some time, Bilo's ADS detects an inco…
|
incorporates from:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-441 Trustworthiness — Reliability — Quality …
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
ConOps-279 |
10.5.6 Permitted parkingThe large university campus requires vis…
|
incorporates from:
ConOps-471 User — Rule — Precedence
ConOps-474 User — Rule — Applicability — Permits
ConOps-481 Rule maker — Jurisdictions — Identificat…
derived from:
SP-20 The ConOps should provide practical use …
SP-145 Within one of its scenarios, the METR Co…
SP-147 Within one of its scenarios, the METR Co…
SP-150 A METR operational scenario should indic…
|
|
ConOps-280 |
10.5.7 Micromobility and VRUsOnce parked, Bilo exits his vehicle and …
|
incorporates from:
ConOps-461 User — Awareness — Jurisdictional classi…
ConOps-462 User — Awareness — Self-awareness
ConOps-468 User — Rule — Awareness
ConOps-473 User — Rule — Distribution — Efficiency
|
|
ConOps-299 |
10.6 Partially blind Fiona |
||
ConOps-300 |
10.6.1 OverviewFiona just bought a new cup and saucer a…
|
||
ConOps-301 |
10.6.2 Navigation to meeting spotThe ride-sourced service notes that Fion…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-462 User — Awareness — Self-awareness
ConOps-474 User — Rule — Applicability — Permits
|
|
ConOps-302 |
10.6.3 Kerbside pickupAs the driver approaches the passenger l…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-474 User — Rule — Applicability — Permits
|
|
ConOps-250 |
10.7 Rosie the delivery robot |
||
ConOps-251 |
10.7.1 OverviewRosie, along with eleven other sibling p…
|
||
ConOps-252 |
10.7.2 Parking the vanRosie's parent van is a level 4 ADS-equi…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-462 User — Awareness — Self-awareness
ConOps-463 User — Awareness — Mapping
ConOps-464 User — Awareness — Geopositioning
ConOps-469 User — Rule — Characteristics
|
|
ConOps-253 |
10.7.3 Sidewalk closureOn the way to the parking spot, Rosie wa…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-461 User — Awareness — Jurisdictional classi…
ConOps-462 User — Awareness — Self-awareness
ConOps-464 User — Awareness — Geopositioning
ConOps-469 User — Rule — Characteristics
|
|
ConOps-254 |
10.7.4 Reporting unexpected conditionsAs Rosie traverses the alternate path, d…
|
incorporates from:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
ConOps-255 |
10.7.5 Propagation of conditionsIn the meantime, the report handler rece…
|
incorporates from:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
ConOps-281 |
10.8 Thibideaux on the Bayou |
||
ConOps-282 |
10.8.1 OverviewThibideaux is enjoying his delicious shr…
|
||
ConOps-283 |
10.8.2 Evacuation ordersThibideaux attempts to engage his ADS on…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-463 User — Awareness — Mapping
ConOps-472 User — Rule — Distribution — Prioritizat…
derived from:
SP-20 The ConOps should provide practical use …
SP-165 In some cases, authorities might disable…
SP-168 In order to automatically update systems…
|
|
ConOps-284 |
10.8.3 Manual traffic directionsAs Thibideaux creeps along in slow traff…
|
incorporates from:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-471 User — Rule — Precedence
ConOps-485 Rule maker — Rules — Non-electronic
|
|
ConOps-285 |
10.8.4 Ignoring signs that are overriddenAs Thibideaux enters the motorway, he ob…
|
incorporates from:
ConOps-471 User — Rule — Precedence
|
|
ConOps-286 |
10.8.5 Reporting inconsistent dataWhile Thibideaux likes his relatives, he…
|
incorporates from:
ConOps-433 Trustworthiness — Reliability — Availabi…
ConOps-442 Trustworthiness — Reliability — Resilien…
ConOps-465 User — Conflicts — Detected
derived from:
SP-20 The ConOps should provide practical use …
SP-91 A disseminator should not publicize repo…
SP-135 We need an example scenario that describ…
|
|
ConOps-959 |
|
||
ConOps-960 |
|
||
ConOps-961 |
|
||
ConOps-962 |
With this information adapters are bette…
|
||
ConOps-287 |
10.8.6 Encountering a disabled traffic signalThe METR receiver is aware of where traf…
|
incorporates from:
ConOps-437 Trustworthiness — Reliability — Availabi…
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
ConOps-303 |
10.9 Larry the lawyer |
||
ConOps-304 |
10.9.1 OverviewLarry is a lawyer who has been hired to …
|
||
ConOps-305 |
10.9.2 DefenceOne of the main pieces of evidence that …
|
incorporates from:
ConOps-445 Trustworthiness — Reliability — Transpar…
ConOps-450 Trustworthiness — Security — Authority —…
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
ConOps-306 |
10.9.3 ProsecutionThe prosecutor points out that the lower…
|
incorporates from:
ConOps-445 Trustworthiness — Reliability — Transpar…
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
ConOps-307 |
10.9.4 RebuttalLarry can demonstrate that several other…
|
incorporates from:
ConOps-445 Trustworthiness — Reliability — Transpar…
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
ConOps-650 |
10.10 Tracy the Traffic Engineer |
||
ConOps-651 |
10.10.1 OverviewTracy is the traffic engineer responsibl…
|
||
ConOps-652 |
10.10.2 InvestigationAfter receiving the request, Tracy has h…
|
||
ConOps-653 |
10.10.3 Rule approvalThe system notifies Tracy that her assis…
|
||
ConOps-655 |
|
||
ConOps-654 |
|
||
ConOps-656 |
|
||
ConOps-657 |
|
||
ConOps-658 |
|
||
ConOps-659 |
|
||
ConOps-661 |
|
||
ConOps-660 |
Tracy reviews the request and approves i…
|
||
ConOps-662 |
10.10.4 Work ordersOnce the rule changes are approved, the …
|
||
ConOps-663 |
10.10.5 METR pre-announced rulesAs soon as the modified rules are approv…
|
||
ConOps-664 |
10.10.6 METR emergent rules and supporting dataHowever, in this case, the TCDs were imp…
|
||
ConOps-1093 |
11 Data flow diagram conventions |
||
ConOps-1100 |
11.1 GeneralThe data expectation diagrams contained …
|
||
ConOps-500 |
|
||
ConOps-1102 |
|
||
ConOps-1116 |
11.2 Naming conventionsFunctional view processes and data flows…
|
||
ConOps-1119 |
11.3 Diagrams provide limited contextReference architectures are typically ve…
|
||
ConOps-44 |
12 Tentative categories for METR information |
||
ConOps-677 |
12.1 GeneralThis annex provides a tentative example …
|
||
ConOps-316 |
12.2 Vocabulary categoriesEach jurisdiction will need to maintain …
|
||
ConOps-317 |
|
||
ConOps-318 |
|
||
ConOps-319 |
|
||
ConOps-926 |
|
||
ConOps-320 |
|
||
ConOps-321 |
|
||
ConOps-322 |
|
||
ConOps-323 |
|
||
ConOps-324 |
12.3 Rule CategoriesIt is expected that during the early sta…
|
||
ConOps-325 |
|
derived from:
SP-159 Road closures (both long-term and short-…
SP-176 METR needs to support public transport r…
SP-180 METR needs to support permitting micromo…
|
|
ConOps-326 |
|
derived from:
SP-159 Road closures (both long-term and short-…
SP-160 Evacuations are in the scope of METR
SP-180 METR needs to support permitting micromo…
|
|
ConOps-327 |
|
||
ConOps-328 |
|
||
ConOps-329 |
|
||
ConOps-330 |
|
||
ConOps-331 |
|
||
ConOps-332 |
|
||
ConOps-333 |
|
||
ConOps-334 |
|
derived from:
SP-179 METR needs to be able to support rules c…
SP-180 METR needs to support permitting micromo…
|
|
ConOps-335 |
|
||
ConOps-336 |
|
derived from:
SP-176 METR needs to support public transport r…
SP-177 METR should be able to convey informatio…
SP-179 METR needs to be able to support rules c…
|
|
ConOps-337 |
|
||
ConOps-338 |
|
||
ConOps-339 |
|
||
ConOps-340 |
|
||
ConOps-341 |
|
||
ConOps-342 |
|
||
ConOps-343 |
|
||
ConOps-344 |
|
||
ConOps-345 |
|
||
ConOps-346 |
|
||
ConOps-347 |
|
||
ConOps-348 |
|
||
ConOps-349 |
|
||
ConOps-350 |
|
||
ConOps-351 |
|
||
ConOps-352 |
|
||
ConOps-353 |
|
||
ConOps-354 |
|
||
ConOps-355 |
|
||
ConOps-356 |
|
||
ConOps-357 |
|
||
ConOps-358 |
|
||
ConOps-359 |
|
||
ConOps-360 |
|
||
ConOps-361 |
|
||
ConOps-644 |
|
||
ConOps-420 |
13 Change request process |
||
ConOps-679 |
13.1 GeneralIt is expected that over time this docum…
|
||
ConOps-680 |
13.2 Requesting changesStakeholders who would like to propose a…
|
||
ConOps-681 |
13.3 Impacts to the standards seriesThe deletion, modification, or addition …
|
||
ConOps-45 |
14 Bibliography |
Trace to a general ITS-SU requirement assumption that the interpreter (or other external component) is still part of the trust environment. Also applies to time and all supporting data