METR
24315 METR |
Submit Comment Traceability Tables: |
| ID | Description | Discussion | Links |
|---|---|---|---|
| SP-2 |
Road vehicles should support short-range…
|
derives:
ConOps-235 Communications — Mobile users — Short-ra…
|
|
| SP-3 |
Some users might not be connected to MET…
|
derives:
ConOps-229 Users — Mixed environment
|
|
| SP-4 |
All ~mobile~ METR-enabled transport user…
|
derives:
ConOps-232 Communications — Mobile users — Mobile w…
|
|
| SP-5 |
Mobile wireless internet is not guarante…
|
derives:
ConOps-233 Communications — Mobile users — Instabil…
|
|
| SP-6 |
Mobile wireless internet might not be av…
|
derives:
ConOps-234 Communications — Mobile users — Areas wi…
|
|
| SP-7 |
METR should support user systems that mi…
|
derives:
ConOps-230 Users — Stationary users
|
|
| SP-8 |
Users have a need to indicate their pref…
|
derives:
ConOps-460 User — Connectivity — Preferences
SoSR-1747 Consumer system developer
|
|
| SP-9 |
User systems might support the ability t…
|
derives:
ConOps-475 User — Rule — Journey planning
|
|
| SP-10 |
METR should support ordinary traffic (i.…
|
derives:
ConOps-228 Users — Variety
|
|
| SP-11 |
METR should cover the full scope of surf…
|
derives:
ConOps-227 Users — Modes
|
|
| SP-12 |
Need to support rules related to specifi…
|
derives:
ConOps-474 User — Rule — Applicability — Permits
|
|
| SP-13 |
Trustworthiness should include non-repud…
|
derives:
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
| SP-14 |
METR should indicate the level of legal …
|
derives:
ConOps-471 User — Rule — Precedence
|
|
| SP-15 |
Users should have a way to report discre…
|
derives:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
| SP-16 |
We should emphasize that the types of re…
|
derives:
|
|
| SP-17 |
Some regions might wish to have a system…
|
derives:
N-3 Each system needs a system manager
|
|
| SP-18 |
Should provide sample diagrams showing i…
|
derives:
SoSR-1251 Possible deployments of role-based archi…
|
|
| SP-19 |
The role model should add a role between…
|
derives:
N-4 Explain that the regulator role includes…
|
|
| SP-20 |
The ConOps should provide practical use …
|
derives:
ConOps-259 Snowy conditions
ConOps-267 Encountering a new traffic control devic…
ConOps-271 ADS fallback based on METR information
ConOps-293 Emergent rules due to emergency
ConOps-279 Permitted parking
ConOps-283 Evacuation orders
ConOps-286 Reporting inconsistent data
SoSR-1251 Possible deployments of role-based archi…
|
|
| SP-21 |
The ConOps needs to identify accountabil…
|
derives:
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
| SP-22 |
The concept of modes does not seem to ap…
|
derives:
N-5 The concept of modes does not really app…
|
|
| SP-23 |
State of rules in force on the transport…
|
derives:
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-247 Communications — Delivery — Supporting d…
Vocab-7 completeness
|
|
| SP-24 |
State of rule availability should be cap…
|
derives:
ConOps-434 Trustworthiness — Reliability — Availabi…
ConOps-435 Trustworthiness — Reliability — Availabi…
|
|
| SP-25 |
The ConOps should reference ISO/IEC/IEEE…
|
derives:
N-6 The ConOps should reference ISO/IEC/IEEE…
|
|
| SP-26 |
All rules should be defined in a languag…
|
derives:
ConOps-447 Trustworthiness — Reliability — Usabilit…
|
|
| SP-27 |
METR should be based on a centralized pu…
|
derives:
ConOps-236 Communications — Delivery — Pre-announce…
ConOps-237 Communications — Delivery — Emergent rul…
|
|
| SP-28 |
It should be the responsibility of the u…
|
derives:
SoSR-1747 Consumer system developer
|
|
| SP-29 |
Each METR rule (e.g., give way to emerge…
|
derives:
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-469 User — Rule — Characteristics
|
|
| SP-30 |
Withdrawn/rescinded rules need to be pub…
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
| SP-31 |
METR will rely upon existing standards w…
|
derives:
ConOps-246 Existing standards
|
|
| SP-32 |
User systems need high confidence that t…
|
derives:
ConOps-446 Trustworthiness — Reliability — Complete…
Vocab-7 completeness
|
|
| SP-33 |
Development team needs to contact field …
|
||
| SP-34 |
Use of push should be minimized while st…
|
derives:
ConOps-248 Limitations of short-range wireless comm…
|
|
| SP-35 |
Push is probably needed for coordination…
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
| SP-36 |
Hierarchy of rules should support the co…
|
derives:
ConOps-471 User — Rule — Precedence
|
|
| SP-37 |
Pull process must support filtering
|
derives:
ConOps-473 User — Rule — Distribution — Efficiency
|
|
| SP-38 |
Centralized dynamic rules either need tr…
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-473 User — Rule — Distribution — Efficiency
|
|
| SP-39 |
Filtering should include almost all para…
|
derives:
ConOps-473 User — Rule — Distribution — Efficiency
MDR-344 Category
MDR-347 Permit information
MDR-351 Location
MDR-354 Temporal characteristics
MDR-356 Facility classification
MDR-359 Vehicle classification
MDR-360 Vehicle physical dimensions
MDR-370 Cargo classifications
MDR-373 User classification
|
|
| SP-40 |
There is a lack of consistent terminolog…
|
derives:
ConOps-469 User — Rule — Characteristics
ConOps-470 User — Rule — Definition
|
|
| SP-41 |
The definition of a "regulator" needs to…
|
derives:
Vocab-9 rule signer
|
|
| SP-42 |
ConOps should explain that all component…
|
derives:
ConOps-450 Trustworthiness — Security — Authority —…
ConOps-453 Trustworthiness — Security — Integrity —…
|
|
| SP-43 |
The ConOps needs to assign the responsib…
|
derives:
ConOps-1095 Process Description Responsible Stakehol…
SoSR-1669 Distributor
|
|
| SP-44 |
The preferred implementation is that the…
|
derives:
N-7 The preferred implementation is that the…
|
|
| SP-45 |
The preferred implementation is that a u…
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-232 Communications — Mobile users — Mobile w…
ConOps-235 Communications — Mobile users — Short-ra…
ConOps-1095 Process Description Responsible Stakehol…
N-8 The preferred implementation is that a u…
SoSR-1749 Adapter system developer
|
|
| SP-46 |
Peer roles need the ability to coordinat…
|
derives:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-438 Trustworthiness — Reliability — Quality …
ConOps-1095 Process Description Responsible Stakehol…
|
|
| SP-47 |
METR must provide accountability such th…
|
derives:
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
| SP-48 |
Disseminators need to be able to share c…
|
derives:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-438 Trustworthiness — Reliability — Quality …
ConOps-1095 Process Description Responsible Stakehol…
|
|
| SP-49 |
A mobile refresh provider should be char…
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
SoSR-1669 Distributor
|
|
| SP-50 |
Need to be able to filter rules based on…
|
derives:
ConOps-473 User — Rule — Distribution — Efficiency
|
|
| SP-51 |
The feedback loop needs to include the r…
|
derives:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-490 Rule maker — Independent verification
ConOps-1095 Process Description Responsible Stakehol…
|
|
| SP-52 |
The ConOps should be written to allow fo…
|
derives:
N-9 The use of mainstream data distribution …
|
|
| SP-53 |
The ConOps should mention that automated…
|
derives:
N-10 Automated discovery is a likely possibil…
|
|
| SP-54 |
METR should distinguish between "rules" …
|
derives:
Vocab-11 rule
Vocab-131 supporting data
Vocab-19 emergent rule
|
|
| SP-55 |
To the extent that C-ITS data is exchang…
|
derives:
ConOps-444 Trustworthiness — Reliability — Timeline…
N-11 The preferred implementation is that rea…
|
|
| SP-56 |
There needs to be a fifth catalogue stat…
|
derives:
ConOps-434 Trustworthiness — Reliability — Availabi…
ConOps-435 Trustworthiness — Reliability — Availabi…
|
|
| SP-57 |
Validity should apply to rules; we need …
|
derives:
Vocab-12 fresh METR information
Vocab-13 freshness period
|
|
| SP-58 |
User privacy needs to be protected, espe…
|
derives:
ConOps-455 Trustworthiness — Security — Authority —…
|
|
| SP-59 |
Australia will be issuing a report soon …
|
||
| SP-60 |
Need examples that can be presented to g…
|
||
| SP-61 |
The disseminator is responsible for ensu…
|
derives:
SoSR-1669 Distributor
|
|
| SP-62 |
Users need a way to discover disseminato…
|
derives:
ConOps-458 User — Distributor — Discovery
ConOps-624 Service registration and discovery servi…
|
|
| SP-63 |
When showing multiplicity in diagrams ot…
|
derives:
N-12 When showing multiplicity in diagrams ot…
|
|
| SP-64 |
METR filtering needs to accommodate the …
|
derives:
ConOps-462 User — Awareness — Self-awareness
ConOps-473 User — Rule — Distribution — Efficiency
|
|
| SP-65 |
Remove the rule types from the state mac…
|
derives:
N-13 Remove the rule types from the state mac…
|
|
| SP-66 |
When discussing rule types, we need to c…
|
derives:
Vocab-15 unposted rule
Vocab-19 emergent rule
Vocab-17 persistent rule
Vocab-18 temporary rule
|
|
| SP-67 |
When discussing planned rules, indicate …
|
derives:
N-14 When discussing planned rules, indicate …
|
|
| SP-68 |
User requests should be confidential and…
|
derives:
ConOps-455 Trustworthiness — Security — Authority —…
ConOps-449 Trustworthiness — Security — Confidentia…
|
|
| SP-69 |
See slide for examples of rule character…
|
derives:
ConOps-469 User — Rule — Characteristics
MDR-344 Category
MDR-347 Permit information
MDR-351 Location
MDR-354 Temporal characteristics
MDR-356 Facility classification
MDR-359 Vehicle classification
MDR-360 Vehicle physical dimensions
MDR-362 Vehicle permits/tags
MDR-364 Fuel type
MDR-365 Emission profile
MDR-367 Trailers and attachments
MDR-369 Vehicle usage classification
MDR-370 Cargo classifications
MDR-373 User classification
MDR-375 Supporting data
MDR-378 External conditions
|
|
| SP-70 |
METR should allow rule characteristcis t…
|
derives:
ConOps-469 User — Rule — Characteristics
|
|
| SP-71 |
Evacuation plans should be distributed i…
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
| SP-72 |
The disseminator is responsible for publ…
|
derives:
SoSR-1669 Distributor
|
|
| SP-73 |
The user is responsible for requesting a…
|
derives:
SoSR-1747 Consumer system developer
|
|
| SP-74 |
All roles are responsible for 1) identif…
|
derives:
ConOps-1095 Process Description Responsible Stakehol…
SoSR-1669 Distributor
|
|
| SP-75 |
The term "C-ITS data source" should perh…
|
derives:
N-9 The use of mainstream data distribution …
N-15 Change "C-ITS data source" to "dynamic d…
Vocab-131 supporting data
Vocab-21 supporting data provider
|
|
| SP-76 |
The ConOps should describe why we are di…
|
derives:
N-16 ConOps should explain that the dissemina…
SoSR-1749 Adapter system developer
|
|
| SP-77 |
The ConOps should provide a brief mentio…
|
derives:
N-17 The ConOps should explain that proposed …
|
|
| SP-78 |
The ConOps should explain that rules mig…
|
derives:
MDR-351 Location
MDR-373 User classification
|
|
| SP-79 |
What is the legal standing of C-ITS data…
|
derives:
ConOps-441 Trustworthiness — Reliability — Quality …
ConOps-454 Trustworthiness — Security — Authority —…
N-18 The ConOps should discuss the legal aspe…
|
|
| SP-80 |
The ConOps should explain that the rule …
|
derives:
N-19 The ConOps should explain that the rule …
|
|
| SP-81 |
The ConOps should include a use case tha…
|
derives:
ConOps-267 Encountering a new traffic control devic…
|
|
| SP-82 |
The ConOps should also include a use cas…
|
derives:
ConOps-293 Emergent rules due to emergency
|
|
| SP-83 |
The "when" responsibility should apply t…
|
||
| SP-84 |
We need to indicate that each system nee…
|
derives:
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
| SP-85 |
Clarify text of responsibilities (as sho…
|
derives:
SoSR-1747 Consumer system developer
|
|
| SP-86 |
Some conditions might require dynamic da…
|
derives:
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-468 User — Rule — Awareness
|
|
| SP-87 |
The ConOps should describe a process by …
|
derives:
N-20 The ConOps should describe a process by …
|
|
| SP-88 |
The ConOps should allow flexibility for …
|
derives:
ConOps-465 User — Conflicts — Detected
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
| SP-89 |
The ConOps should allow any vehicle (tha…
|
derives:
ConOps-465 User — Conflicts — Detected
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
| SP-90 |
A vehicle reporting a conflict should ha…
|
derives:
ConOps-465 User — Conflicts — Detected
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
| SP-91 |
A disseminator should not publicize repo…
|
derives:
ConOps-465 User — Conflicts — Detected
ConOps-286 Reporting inconsistent data
|
|
| SP-92 |
The ConOps should probably stay agnostic…
|
derives:
N-21 The ConOps should include a scenario tha…
|
|
| SP-93 |
A rule refresh should only provide the c…
|
derives:
ConOps-244 Communications — Delivery — Efficiency
|
|
| SP-94 |
Each individual rule should have its own…
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-469 User — Rule — Characteristics
Vocab-12 fresh METR information
Vocab-13 freshness period
|
|
| SP-95 |
The ConOps should provide an example of …
|
derives:
ConOps-259 Snowy conditions
|
|
| SP-96 |
Unless otherwise indicated, the ConOps s…
|
derives:
ConOps-449 Trustworthiness — Security — Confidentia…
|
|
| SP-97 |
The ConOps should indicate that we assum…
|
derives:
ConOps-271 ADS fallback based on METR information
|
|
| SP-98 |
The ConOps should provide an example use…
|
derives:
ConOps-272 Starting outside of METR coverage
|
|
| SP-99 |
The ConOps should indicate that for the …
|
derives:
ConOps-476 User — Rule — Obsolescence
ConOps-272 Starting outside of METR coverage
|
|
| SP-100 |
Any remote refresh would have to be prov…
|
derives:
ConOps-476 User — Rule — Obsolescence
ConOps-272 Starting outside of METR coverage
|
|
| SP-101 |
The ConOps should allow the definition o…
|
derives:
ConOps-473 User — Rule — Distribution — Efficiency
|
|
| SP-102 |
Vehicle types regulated by a jurisdictio…
|
derives:
ConOps-462 User — Awareness — Self-awareness
|
|
| SP-103 |
The characteristics used by a jurisdicti…
|
derives:
ConOps-469 User — Rule — Characteristics
MDR-365 Emission profile
MDR-369 Vehicle usage classification
|
|
| SP-104 |
Road types regulated by a jurisdiction n…
|
derives:
ConOps-461 User — Awareness — Jurisdictional classi…
|
|
| SP-105 |
METR needs to convey the location for ev…
|
derives:
ConOps-469 User — Rule — Characteristics
MDR-351 Location
|
|
| SP-106 |
METR needs to support rules that charact…
|
derives:
ConOps-469 User — Rule — Characteristics
MDR-369 Vehicle usage classification
MDR-370 Cargo classifications
|
|
| SP-107 |
METR users need to be able to identify w…
|
derives:
ConOps-473 User — Rule — Distribution — Efficiency
|
|
| SP-108 |
METR does not need to convey the graphic…
|
||
| SP-109 |
The METR ConOps will be written so that …
|
derives:
ConOps-452 Trustworthiness — Reliability — Accuracy
|
|
| SP-110 |
METR needs to be able to advertise when …
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
| SP-111 |
Characteristics should include permits, …
|
derives:
ConOps-469 User — Rule — Characteristics
MDR-347 Permit information
MDR-362 Vehicle permits/tags
MDR-373 User classification
MDR-380 On-board data
|
|
| SP-112 |
All rules should be signed by the transl…
|
derives:
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
| SP-113 |
Conform to the terminology of ISO 22736 …
|
derives:
Vocab-34 Terms and definitions
|
|
| SP-114 |
Rules provided by METR should be complet…
|
derives:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-446 Trustworthiness — Reliability — Complete…
|
|
| SP-115 |
When any conflict is discovered, it shou…
|
derives:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
| SP-116 |
We should use the terms "low latency" an…
|
||
| SP-117 |
Look at CEN ISO/TS 17426 Contextual spee…
|
derives:
Vocab-34 Terms and definitions
|
|
| SP-118 |
The operational scenarios should provide…
|
derives:
N-22 The operational scenarios should provide…
|
|
| SP-119 |
In order to be trustworthy and relied up…
|
derives:
ConOps-446 Trustworthiness — Reliability — Complete…
|
|
| SP-120 |
In order to claim support for any rule d…
|
derives:
ConOps-446 Trustworthiness — Reliability — Complete…
|
|
| SP-121 |
Users need to be aware of when they shou…
|
derives:
ConOps-454 Trustworthiness — Security — Authority —…
|
|
| SP-122 |
Regulators might establish rules that re…
|
derives:
MDR-363 Vehicle certifications
|
|
| SP-123 |
Responders and field crews often have ne…
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
| SP-124 |
Between METR and the map data, ADS-equip…
|
derives:
ConOps-271 ADS fallback based on METR information
|
|
| SP-125 |
METR needs to be able to indicate how co…
|
derives:
ConOps-435 Trustworthiness — Reliability — Availabi…
|
|
| SP-126 |
METR providers might need to be certifie…
|
derives:
ConOps-458 User — Distributor — Discovery
|
|
| SP-127 |
Identification and responding to dynamic…
|
derives:
N-23 Identification and responding to dynamic…
|
|
| SP-128 |
METR cannot rely on just one path for da…
|
derives:
ConOps-442 Trustworthiness — Reliability — Resilien…
|
|
| SP-129 |
Identification of the disseminator is ou…
|
derives:
ConOps-458 User — Distributor — Discovery
|
|
| SP-130 |
The ConOps should structure at least one…
|
derives:
ConOps-259 Snowy conditions
|
|
| SP-131 |
The ConOps should indicate the importanc…
|
derives:
ConOps-452 Trustworthiness — Reliability — Accuracy
|
|
| SP-132 |
The ConOps might include a scenario with…
|
derives:
ConOps-259 Snowy conditions
|
|
| SP-133 |
Define "static rule", "dynamic rule" and…
|
derives:
Vocab-131 supporting data
Vocab-26 vehicle-sourced data
Vocab-16 posted rule
Vocab-15 unposted rule
Vocab-19 emergent rule
Vocab-133 pre-announced rule
Vocab-17 persistent rule
Vocab-18 temporary rule
|
|
| SP-134 |
Distinguish between "governmental" and "…
|
||
| SP-135 |
We need an example scenario that describ…
|
derives:
ConOps-286 Reporting inconsistent data
|
|
| SP-136 |
Transport user systems need insights int…
|
derives:
ConOps-441 Trustworthiness — Reliability — Quality …
|
|
| SP-137 |
Need to support (and convey to users) th…
|
derives:
ConOps-441 Trustworthiness — Reliability — Quality …
ConOps-453 Trustworthiness — Security — Integrity —…
MDR-345 Source of information
|
|
| SP-138 |
Users need all rules to be digitally sig…
|
derives:
ConOps-453 Trustworthiness — Security — Integrity —…
|
|
| SP-139 |
METR needs to be able to accommodate hig…
|
derives:
ConOps-466 User — Facility — Defined area
|
|
| SP-140 |
METR needs to be able to accommodate roa…
|
derives:
ConOps-466 User — Facility — Defined area
|
|
| SP-141 |
METR needs to be able to accommodate jur…
|
derives:
ConOps-467 User — Jurisdiction — Sub-areas
|
|
| SP-142 |
METR needs to be able to accommodate enf…
|
derives:
MDR-348 Enforcement information
MDR-349 Penalty information
|
|
| SP-143 |
METR needs to be able to accommodate ind…
|
derives:
ConOps-467 User — Jurisdiction — Sub-areas
|
|
| SP-144 |
It might be worth including an optional …
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
| SP-145 |
Within one of its scenarios, the METR Co…
|
derives:
ConOps-279 Permitted parking
|
|
| SP-146 |
METR rules need to define areas reserved…
|
derives:
ConOps-262 Locating appropriate parking
|
|
| SP-147 |
Within one of its scenarios, the METR Co…
|
derives:
ConOps-279 Permitted parking
|
|
| SP-148 |
METR needs to provide a way to link rule…
|
derives:
MDR-347 Permit information
|
|
| SP-149 |
METR needs to provide a way for the vehi…
|
derives:
ConOps-474 User — Rule — Applicability — Permits
|
|
| SP-150 |
A METR operational scenario should indic…
|
derives:
ConOps-262 Locating appropriate parking
ConOps-279 Permitted parking
|
|
| SP-151 |
METR should provide a way for an entity …
|
derives:
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
| SP-152 |
Process to deploy known rules includes p…
|
derives:
ConOps-267 Encountering a new traffic control devic…
|
|
| SP-153 |
METR needs to support both permits that …
|
derives:
ConOps-474 User — Rule — Applicability — Permits
|
|
| SP-154 |
METR should include pavement markings, i…
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
| SP-155 |
Locally implemented/activated rules migh…
|
derives:
ConOps-484 Rule maker — Publicize — Rules at a dist…
|
|
| SP-156 |
Locally implemented/activated rules need…
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
| SP-157 |
Ad Hoc rules might provide detour inform…
|
derives:
ConOps-293 Emergent rules due to emergency
|
|
| SP-158 |
We need to define "regulator"
|
derives:
Vocab-9 rule signer
|
|
| SP-159 |
Road closures (both long-term and short-…
|
derives:
ConOps-325 right of way (i.e., 11.397-11.398, 11.42…
ConOps-326 general restrictions (i.e., 12.411-12.41…
|
|
| SP-160 |
Evacuations are in the scope of METR
|
derives:
ConOps-326 general restrictions (i.e., 12.411-12.41…
|
|
| SP-161 |
Overrides of normal traffic control is a…
|
derives:
ConOps-471 User — Rule — Precedence
|
|
| SP-162 |
METR needs to be resilient as possible i…
|
derives:
ConOps-442 Trustworthiness — Reliability — Resilien…
|
|
| SP-163 |
For the foreseeable future, METR should …
|
derives:
ConOps-441 Trustworthiness — Reliability — Quality …
ConOps-241 Safety — Users
ConOps-242 Safety — Reliance
N-1 METR will result in some operational cha…
|
|
| SP-164 |
An ADS-equipped vehicle might need some …
|
derives:
ConOps-477 User — Status — Manual inputs
|
|
| SP-165 |
In some cases, authorities might disable…
|
derives:
ConOps-433 Trustworthiness — Reliability — Availabi…
ConOps-283 Evacuation orders
|
|
| SP-1 |
In order to provide a more seamless expe…
|
derives:
ConOps-1095 Process Description Responsible Stakehol…
|
|
| SP-166 |
METR should be able to characterize each…
|
derives:
MDR-343 Identifier
MDR-344 Category
MDR-347 Permit information
MDR-351 Location
MDR-354 Temporal characteristics
MDR-356 Facility classification
MDR-359 Vehicle classification
MDR-360 Vehicle physical dimensions
MDR-362 Vehicle permits/tags
MDR-363 Vehicle certifications
MDR-364 Fuel type
MDR-365 Emission profile
MDR-367 Trailers and attachments
MDR-369 Vehicle usage classification
MDR-370 Cargo classifications
MDR-373 User classification
MDR-375 Supporting data
MDR-378 External conditions
MDR-380 On-board data
|
|
| SP-167 |
In order to implement some rules (e.g., …
|
derives:
MDR-353 Map alignment
|
|
| SP-168 |
In order to automatically update systems…
|
derives:
ConOps-488 Rule maker — Rule discovery service
ConOps-283 Evacuation orders
|
|
| SP-169 |
We should perhaps contact NACTO (https:/…
|
||
| SP-170 |
Pedestrians, especially those with disab…
|
derives:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
| SP-171 |
VRUs/VRVs need to be aware of the classe…
|
derives:
ConOps-461 User — Awareness — Jurisdictional classi…
MDR-353 Map alignment
|
|
| SP-172 |
Motor vehicle systems need to be aware o…
|
derives:
ConOps-463 User — Awareness — Mapping
MDR-351 Location
|
|
| SP-173 |
A private company (e.g., vehicle share o…
|
derives:
ConOps-481 Rule maker — Jurisdictions — Identificat…
|
|
| SP-174 |
There should be the ability for regulato…
|
derives:
ConOps-468 User — Rule — Awareness
|
|
| SP-175 |
METR should be designed so that it can b…
|
derives:
ConOps-222 Aerial drones
ConOps-249 Aerial drones
|
|
| SP-176 |
METR needs to support public transport r…
|
derives:
ConOps-325 right of way (i.e., 11.397-11.398, 11.42…
ConOps-336 pedestrian restrictions (i.e., 12.423, 1…
MDR-351 Location
MDR-359 Vehicle classification
MDR-373 User classification
|
|
| SP-177 |
METR should be able to convey informatio…
|
derives:
ConOps-468 User — Rule — Awareness
ConOps-469 User — Rule — Characteristics
ConOps-336 pedestrian restrictions (i.e., 12.423, 1…
MDR-354 Temporal characteristics
|
|
| SP-178 |
Should reach out to bicycle groups, espe…
|
||
| SP-179 |
METR needs to be able to support rules c…
|
derives:
ConOps-468 User — Rule — Awareness
ConOps-334 micromobility restrictions (i.e., 12.128…
ConOps-336 pedestrian restrictions (i.e., 12.423, 1…
|
|
| SP-180 |
METR needs to support permitting micromo…
|
derives:
ConOps-468 User — Rule — Awareness
ConOps-474 User — Rule — Applicability — Permits
ConOps-325 right of way (i.e., 11.397-11.398, 11.42…
ConOps-326 general restrictions (i.e., 12.411-12.41…
ConOps-334 micromobility restrictions (i.e., 12.128…
|
|
| SP-181 |
Each METR component needs to be certifie…
|
derives:
ConOps-454 Trustworthiness — Security — Authority —…
ConOps-627 METR Certification
|
|
| SP-182 |
The rule categories should be standardiz…
|
derives:
ConOps-435 Trustworthiness — Reliability — Availabi…
|
|
| SP-183 |
User systems need to be able to determin…
|
derives:
ConOps-434 Trustworthiness — Reliability — Availabi…
ConOps-435 Trustworthiness — Reliability — Availabi…
ConOps-454 Trustworthiness — Security — Authority —…
|
|
| SP-184 |
Users need to be able to determine the s…
|
derives:
ConOps-451 Trustworthiness — Security — Integrity —…
MDR-346 Issuing authority
|
|
| SP-185 |
User systems are responsible for operati…
|
derives:
ConOps-241 Safety — Users
|
|
| SP-186 |
Within our scenarios, we should assume t…
|
derives:
ConOps-267 Encountering a new traffic control devic…
|
|
| SP-187 |
Users should be able to discover when th…
|
derives:
ConOps-433 Trustworthiness — Reliability — Availabi…
|
|
| SP-188 |
Each METR component needs to support non…
|
derives:
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
| SP-189 |
Some jurisdictional entities might requi…
|
derives:
N-24 Jurisdictional entities might require su…
N-25 Jurisdictional entities might require tr…
|
|
| SP-190 |
METR data must be reliable and provided …
|
derives:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-433 Trustworthiness — Reliability — Availabi…
ConOps-434 Trustworthiness — Reliability — Availabi…
ConOps-435 Trustworthiness — Reliability — Availabi…
ConOps-437 Trustworthiness — Reliability — Availabi…
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-438 Trustworthiness — Reliability — Quality …
ConOps-440 Trustworthiness — Reliability — Quality …
ConOps-441 Trustworthiness — Reliability — Quality …
ConOps-442 Trustworthiness — Reliability — Resilien…
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-445 Trustworthiness — Reliability — Transpar…
ConOps-447 Trustworthiness — Reliability — Usabilit…
ConOps-448 Trustworthiness — Reliability — Usabilit…
ConOps-450 Trustworthiness — Security — Authority —…
ConOps-455 Trustworthiness — Security — Authority —…
ConOps-454 Trustworthiness — Security — Authority —…
ConOps-449 Trustworthiness — Security — Confidentia…
ConOps-451 Trustworthiness — Security — Integrity —…
ConOps-453 Trustworthiness — Security — Integrity —…
|
|
| SP-191 |
The METR ConOps will only define "what" …
|
derives:
N-26 A ConOps document only defines "what" is…
|
|
| SP-192 |
Transport user systems need to know what…
|
derives:
ConOps-434 Trustworthiness — Reliability — Availabi…
ConOps-435 Trustworthiness — Reliability — Availabi…
ConOps-454 Trustworthiness — Security — Authority —…
ConOps-461 User — Awareness — Jurisdictional classi…
ConOps-462 User — Awareness — Self-awareness
|
|
| SP-193 |
Transport user systems need to know how …
|
derives:
ConOps-440 Trustworthiness — Reliability — Quality …
|
|
| SP-194 |
Map information within METR has to be ab…
|
derives:
ConOps-463 User — Awareness — Mapping
|
|
| SP-195 |
The METR ConOps should identify the need…
|
derives:
ConOps-486 Rule maker — Discrepancies — Primary
ConOps-487 Rule maker — Discrepancies — Secondary
ConOps-488 Rule maker — Rule discovery service
|
|
| SP-196 |
The information provided by METR is safe…
|
derives:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-433 Trustworthiness — Reliability — Availabi…
ConOps-434 Trustworthiness — Reliability — Availabi…
ConOps-435 Trustworthiness — Reliability — Availabi…
ConOps-437 Trustworthiness — Reliability — Availabi…
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-438 Trustworthiness — Reliability — Quality …
ConOps-440 Trustworthiness — Reliability — Quality …
ConOps-441 Trustworthiness — Reliability — Quality …
ConOps-442 Trustworthiness — Reliability — Resilien…
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-445 Trustworthiness — Reliability — Transpar…
ConOps-447 Trustworthiness — Reliability — Usabilit…
ConOps-448 Trustworthiness — Reliability — Usabilit…
ConOps-450 Trustworthiness — Security — Authority —…
ConOps-455 Trustworthiness — Security — Authority —…
ConOps-454 Trustworthiness — Security — Authority —…
ConOps-449 Trustworthiness — Security — Confidentia…
ConOps-451 Trustworthiness — Security — Integrity —…
ConOps-453 Trustworthiness — Security — Integrity —…
N-27 The ConOps should mention the relevance …
|
|
| SP-197 |
METR data needs to be available to users…
|
derives:
ConOps-451 Trustworthiness — Security — Integrity —…
ConOps-490 Rule maker — Independent verification
|
|
| SP-198 |
Every version of METR needs to be backwa…
|
derives:
ConOps-479 User — System — Upgrade
ConOps-245 Forwards and backwards compatibility
ConOps-246 Existing standards
|
|
| SP-199 |
Some jurisdictions might adopt regulatio…
|
derives:
N-24 Jurisdictional entities might require su…
N-25 Jurisdictional entities might require tr…
|
|
| SP-200 |
The project should coordinate with EU: D…
|
||
| SP-201 |
Facilities that support METR need to ind…
|
derives:
ConOps-440 Trustworthiness — Reliability — Quality …
|
- Design: HTML5 UP
- Portions subject to ISO copyright. This website is not an ISO International Standard. It is provided to facilitate efforts to review and comment on the current draft. It is subject to change without notice and may not be referred to as an International Standard.
- Users of this website are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.
