24315 METR |
Submit Comment Traceability Tables: |
ID | Description | Discussion | Links |
---|---|---|---|
SoSR-35 |
1 ScopeThe management of electronic transport r…
|
||
SoSR-36 |
2 Normative referencesThe following documents are referred to …
|
||
SoSR-174 |
ISO/TS 14812:2022, Intelligent transport…
|
||
SoSR-175 |
ISO/TS 24315-1:2024 , Intelligent transp…
|
||
SoSR-906 |
ISO/IEC/IEEE 24765:2017, Systems and sof…
|
||
SoSR-9 |
3 Terms and definitionsFor the purposes of this document, the t…
|
||
SoSR-1819 |
3.1 distribution system rule set signerentity associated with the distribution …
|
||
SoSR-1824 | NOTE: The distribution system rule set signer … | ||
SoSR-1825 | NOTE: The distribution system rule set signer … | ||
SoSR-1820 |
3.2 regulation system rule set signerentity associated with the regulation sy…
|
||
SoSR-1821 | NOTE: Metadata includes useful information (e.… | ||
SoSR-10 |
4 Symbols and abbreviated terms |
||
SoSR-987 |
4.1 ADSAutomated Driving System
|
||
SoSR-988 |
4.2 ARC-ITArchitecture Reference for Cooperative a…
|
||
SoSR-989 |
4.3 CCMScooperative ITS credentials management s…
|
||
SoSR-990 |
4.4 CVconnected vehicle
|
||
SoSR-991 |
4.5 FMfrequency modulation
|
||
SoSR-992 |
4.6 GNSSglobal navigation satellite system
|
||
SoSR-993 |
4.7 HTMLhypertext markup language
|
||
SoSR-994 |
4.8 IECInternational Electrotechnical Commissio…
|
||
SoSR-995 |
4.9 IEEEInstitute of Electrical and Electronics …
|
||
SoSR-996 |
4.10 ISOOrganization for International Standardi…
|
||
SoSR-997 |
4.11 ITSintelligent transport systems
|
||
SoSR-998 |
4.12 MCMCmaintenance and construction management …
|
||
SoSR-999 |
4.13 METRmanagement of electronic traffic regulat…
|
||
SoSR-1000 |
4.14 OBEon-board equipment
|
||
SoSR-1001 |
4.15 OEMoriginal equipment manufacturer
|
||
SoSR-1002 |
4.16 PIDpersonal information device
|
||
SoSR-1003 |
4.17 PMRpublic mobile robot
|
||
SoSR-1004 |
4.18 RSEroadside equipment
|
||
SoSR-1012 |
4.19 SoSsystem of systems
|
||
SoSR-1005 |
4.20 SoSRsystem of systems requirements
|
||
SoSR-1006 |
4.21 SRADSservice registration and discovery servi…
|
||
SoSR-1007 |
4.22 TCDtraffic control device
|
||
SoSR-1008 |
4.23 TStechnical specification
|
||
SoSR-1009 |
4.24 UNuser need
|
||
SoSR-1010 |
4.25 VRUvulnerable road user
|
||
SoSR-1011 |
4.26 WAIDSwide-area information disseminator syste…
|
||
SoSR-1 |
5 Overview |
||
SoSR-2 |
5.1 METR purposeThe ISO 24315 series intends to provide …
|
||
SoSR-3 |
5.2 METR scopeThe METR SoS is designed to provide elec…
|
||
SoSR-4 |
5.3 METR overview |
||
SoSR-176 |
5.3.1 Functional viewFigure 1 summarizes the functional view …
|
||
SoSR-1444 |
5.3.2 Physical view |
||
SoSR-177 |
5.3.2.1 OverviewFigure 2 provides a corresponding physic…
|
||
SoSR-1445 |
5.3.2.2 Information flows with the METR SoSThe physical view includes the following…
|
||
SoSR-812 |
|
architecture for:
SoSR-556 Source
SoSR-557 Causality
SoSR-670 Destination
SoSR-671 Causality
|
|
SoSR-814 |
|
architecture for:
SoSR-575 Source
SoSR-576 Causality
|
|
SoSR-818 |
|
architecture for:
SoSR-606 Source
SoSR-608 Causality
|
|
SoSR-1013 |
|
architecture for:
SoSR-1381 Destination
SoSR-1382 Causality
|
|
SoSR-1446 |
|
architecture for:
SoSR-1464 Destination
SoSR-1465 Causality
|
|
SoSR-816 |
|
architecture for:
SoSR-466 Destination
SoSR-470 Causality
|
|
SoSR-1407 |
|
architecture for:
SoSR-1381 Destination
SoSR-1382 Causality
|
|
SoSR-817 |
|
architecture for:
SoSR-522 Source
SoSR-524 Causality
|
|
SoSR-1447 |
5.3.2.3 Other relevant information flowsIn addition to the information flows ide…
|
||
SoSR-1449 |
|
||
SoSR-1448 |
|
||
SoSR-1450 |
|
||
SoSR-1451 |
5.3.2.4 Physical objectsThe top-level physical view includes the…
|
||
SoSR-1452 |
Physical object Description Assigned pro…
|
||
SoSR-1453 |
5.3.2.5 Component systems within the METR SoSClause 8 further analyses the internals …
|
||
SoSR-8 |
5.4 Assumptions and dependencies |
||
SoSR-183 |
5.4.1 Assumptions |
||
SoSR-188 |
5.4.1.1 Internet-based communicationsIt is assumed that the METR SoS will lik…
|
fulfils:
ConOps-231 Communications — Stationary components —…
ConOps-232 Communications — Mobile users — Mobile w…
|
|
SoSR-899 |
5.4.1.2 Leverage existing standardsMETR is one ITS service among many exist…
|
fulfils:
ConOps-246 Existing standards
|
|
SoSR-952 |
5.4.1.3 Supporting dataIt is assumed that supporting data provi…
|
fulfils:
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
SoSR-953 | NOTE: Being able to provide evidence that accu… | ||
SoSR-903 |
5.4.1.4 Avoiding vehicle inoperabilityIt is assumed that vehicles will not bec…
|
fulfils:
ConOps-476 User — Rule — Obsolescence
|
|
SoSR-904 | NOTE: This can be achieved by allowing the veh… | ||
SoSR-184 |
5.4.2 Dependencies |
||
SoSR-189 |
The requirements defined in this documen…
|
||
SoSR-919 |
|
fulfils:
ConOps-231 Communications — Stationary components —…
ConOps-232 Communications — Mobile users — Mobile w…
ConOps-233 Communications — Mobile users — Instabil…
ConOps-234 Communications — Mobile users — Areas wi…
|
|
SoSR-920 |
|
fulfils:
ConOps-247 Communications — Delivery — Supporting d…
|
|
SoSR-1247 |
|
fulfils:
ConOps-463 User — Awareness — Mapping
|
|
SoSR-1248 |
|
fulfils:
ConOps-463 User — Awareness — Mapping
|
|
SoSR-378 |
5.5 Traceability conventionsWithin the systems engineering process, …
|
||
SoSR-1455 |
From the perspective of the developers o…
|
||
SoSR-951 |
Table 1 indicates the rules for each tra…
|
||
SoSR-921 |
Source Type Destination Each functional …
|
||
SoSR-1454 |
[1] High-level requirements are used whe…
|
||
SoSR-11 |
6 System of systems requirements |
||
SoSR-922 |
6.1 GeneralThe SoS requirements are presented in th…
|
||
SoSR-923 |
|
||
SoSR-924 |
|
||
SoSR-925 |
|
||
SoSR-926 |
|
||
SoSR-927 |
|
||
SoSR-928 |
|
||
SoSR-462 |
6.2 Input Requirements |
||
SoSR-487 |
6.2.1 Information flow: legal rules |
realized by:
RSR-114 Information flow: METR input
|
|
SoSR-830 |
6.2.1.1 FunctionThe METR SoS accepts legal rules [SOURCE…
|
supports:
SoSR-1373 Function
SoSR-855 Function
|
|
SoSR-509 |
6.2.1.2 ContentThe METR input shall include:
|
||
SoSR-510 |
|
uses:
SoSR-512 METR information
|
|
SoSR-518 |
|
uses:
SoSR-85 METR information content
|
|
SoSR-519 |
|
uses:
SoSR-86 METR information meta-data
|
|
SoSR-520 |
|
uses:
SoSR-87 Observable transport rule attributes
|
|
SoSR-822 |
|
uses:
SoSR-821 Additional transport rule attributes
|
|
SoSR-522 |
6.2.1.3 SourceThe METR SoS shall obtain the legal rule…
|
from architecture:
SoSR-817 Rule maker —> METR SoS: legal rules (as …
|
|
SoSR-523 | NOTE: The legal rules are preferably obtained … | ||
SoSR-524 |
6.2.1.4 CausalityIdeally, the legal rule flow is initiate…
|
from architecture:
SoSR-817 Rule maker —> METR SoS: legal rules (as …
|
|
SoSR-525 |
6.2.1.5 ConstraintsNo constraints are defined for this info…
|
||
SoSR-526 |
6.2.1.6 Resulting actionUpon receipt of the legal rule flow, the…
|
supported by:
SoSR-503 Verification of METR rules
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
SoSR-491 |
6.2.2 Information flow: METR coordination |
realized by:
RSR-214 Information flow: METR coordination
|
|
SoSR-831 |
6.2.2.1 FunctionThe METR SoS shall enable METR operation…
|
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-446 Trustworthiness — Reliability — Complete…
|
|
SoSR-555 |
6.2.2.2 ContentThe METR coordination flow can include:
|
||
SoSR-832 |
|
uses:
SoSR-512 METR information
|
|
SoSR-833 |
|
uses:
SoSR-85 METR information content
|
|
SoSR-834 |
|
uses:
SoSR-86 METR information meta-data
|
|
SoSR-835 |
|
uses:
SoSR-87 Observable transport rule attributes
|
|
SoSR-836 |
|
uses:
SoSR-821 Additional transport rule attributes
|
|
SoSR-565 |
|
||
SoSR-556 |
6.2.2.3 SourceThe METR SoS shall obtain the METR coord…
|
from architecture:
SoSR-812 Discrepancy Contact Centre <—> METR SoS:…
|
|
SoSR-557 |
6.2.2.4 CausalityThe METR coordination flow is initiated …
|
from architecture:
SoSR-812 Discrepancy Contact Centre <—> METR SoS:…
|
|
SoSR-558 |
6.2.2.5 ConstraintsNo constraints are defined for this inpu…
|
||
SoSR-559 |
6.2.2.6 Resulting actionUpon initiation of the METR coordination…
|
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
|
|
SoSR-496 |
6.2.3 Information flow: METR discrepancy information |
||
SoSR-867 |
6.2.3.1 FunctionThe METR SoS shall accept all METR discr…
|
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-438 Trustworthiness — Reliability — Quality …
ConOps-487 Rule maker — Discrepancies — Secondary
ConOps-488 Rule maker — Rule discovery service
supports:
SoSR-858 Function
|
|
SoSR-607 |
6.2.3.2 ContentThe METR discrepancy information flow sh…
|
||
SoSR-629 |
|
uses:
SoSR-69 METR information identifier
|
|
SoSR-632 |
|
fulfils:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
SoSR-868 |
|
fulfils:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
SoSR-630 |
|
fulfils:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
SoSR-356 |
|
realized by:
CSR-127 Information flow: METR discrepancy repor…
DHSR-83 Information flow: Consolidated discrepan…
DHSR-100 Information flow: Discrepancy report det…
DHSR-88 Information flow: System-generated discr…
DSR-137 Information flow: System-generated discr…
RSR-210 Information flow: system-generated discr…
RSR-101 Operator discrepancy interface
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
|
|
SoSR-355 |
|
realized by:
CSR-127 Information flow: METR discrepancy repor…
CSR-142 Discrepancy notification
DHSR-83 Information flow: Consolidated discrepan…
DHSR-100 Information flow: Discrepancy report det…
RSR-101 Operator discrepancy interface
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-490 Rule maker — Independent verification
|
|
SoSR-635 |
|
fulfils:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
SoSR-631 |
|
fulfils:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
SoSR-633 |
|
fulfils:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
SoSR-634 |
|
fulfils:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
SoSR-606 |
6.2.3.3 SourceThe METR SoS shall obtain the METR discr…
|
from architecture:
SoSR-818 METR adapter system —> METR SoS: METR di…
|
|
SoSR-608 |
6.2.3.4 CausalityThe METR discrepancy information flow is…
|
from architecture:
SoSR-818 METR adapter system —> METR SoS: METR di…
|
|
SoSR-609 |
6.2.3.5 ConstraintsNo constraints are defined for this inpu…
|
||
SoSR-610 |
6.2.3.6 Resulting actionAfter receipt of sufficient METR discrep…
|
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
|
|
SoSR-493 |
6.2.4 Information flow: TCD status |
||
SoSR-843 |
6.2.4.1 FunctionThe METR SoS shall maintain its awarenes…
|
fulfils:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-465 User — Conflicts — Detected
supports:
SoSR-339 Emerging rule availability
SoSR-977 indicate the confirmed discrepancy;
SoSR-978 indicate whether continued discrepancy r…
SoSR-976 provide guidance as to how the discrepan…
|
|
SoSR-574 |
6.2.4.2 ContentThe TCD status information flow shall in…
|
||
SoSR-579 |
|
||
SoSR-580 |
|
uses:
SoSR-85 METR information content
|
|
SoSR-581 |
|
uses:
SoSR-87 Observable transport rule attributes
|
|
SoSR-595 |
|
||
SoSR-583 |
|
||
SoSR-575 |
6.2.4.3 SourceThe METR SoS shall obtain the TCD status…
|
from architecture:
SoSR-814 MCMC —> METR SoS: TCD status (as defined…
|
|
SoSR-576 |
6.2.4.4 CausalityThe TCD status information flow is typic…
|
from architecture:
SoSR-814 MCMC —> METR SoS: TCD status (as defined…
|
|
SoSR-585 | NOTE: It is the responsibility of the MCMC to … | ||
SoSR-577 |
6.2.4.5 Constraints |
||
SoSR-885 |
6.2.4.5.1 Change notificationsThe MCMC is responsible for providing th…
|
||
SoSR-592 |
6.2.4.5.2 QueryA request for the TCD status flow shall …
|
||
SoSR-598 |
|
||
SoSR-597 |
|
||
SoSR-849 |
|
summarizes:
SoSR-69 METR information identifier
|
|
SoSR-850 |
|
||
SoSR-886 |
6.2.4.5.3 Query responseThe MCMC is responsible for providing th…
|
||
SoSR-578 |
6.2.4.6 Resulting actionUpon receipt of the TCD status informati…
|
fulfils:
ConOps-490 Rule maker — Independent verification
|
|
SoSR-586 | EXAMPLE: In the case of implementing a stop sign,… | ||
SoSR-981 | EXAMPLE: In the case of a resolved discrepancy [S… | ||
SoSR-587 | NOTE: The resulting action can be different ba… | ||
SoSR-463 |
6.3 Output requirements |
||
SoSR-1443 |
6.3.1 Information flow: METR audit information |
||
SoSR-1456 |
6.3.1.1 FunctionThe METR SoS shall enable METR auditors …
|
fulfils:
ConOps-966 Third party — Auditing
|
|
SoSR-1457 | NOTE: Audits are especially useful to establis… | ||
SoSR-1458 |
6.3.1.2 ContentThe METR audit information can include:
|
||
SoSR-1459 |
|
||
SoSR-1460 |
|
||
SoSR-1461 |
|
||
SoSR-1462 |
|
||
SoSR-1463 |
|
||
SoSR-1464 |
6.3.1.3 DestinationThe METR SoS shall provide the METR audi…
|
from architecture:
SoSR-1446 METR SoS —> METR auditor: METR audit inf…
|
|
SoSR-1465 |
6.3.1.4 CausalityThe METR audit information flow is initi…
|
from architecture:
SoSR-1446 METR SoS —> METR auditor: METR audit inf…
|
|
SoSR-1466 |
6.3.1.5 ConstraintsThe METR auditor can specify filtering c…
|
||
SoSR-1467 |
6.3.1.6 Resulting actionIt is the responsibility of the auditor …
|
||
SoSR-499 |
6.3.2 Information flow: METR coordination |
||
SoSR-858 |
6.3.2.1 FunctionThe METR SoS shall enable METR operation…
|
supported by:
SoSR-867 Function
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-446 Trustworthiness — Reliability — Complete…
|
|
SoSR-663 |
6.3.2.2 ContentThe METR coordination flow can include:
|
||
SoSR-860 |
|
uses:
SoSR-512 METR information
|
|
SoSR-861 |
|
uses:
SoSR-85 METR information content
|
|
SoSR-862 |
|
uses:
SoSR-86 METR information meta-data
|
|
SoSR-863 |
|
uses:
SoSR-87 Observable transport rule attributes
|
|
SoSR-864 |
|
uses:
SoSR-821 Additional transport rule attributes
|
|
SoSR-859 |
|
||
SoSR-670 |
6.3.2.3 DestinationThe METR SoS shall provide the METR coor…
|
from architecture:
SoSR-812 Discrepancy Contact Centre <—> METR SoS:…
|
|
SoSR-671 |
6.3.2.4 CausalityThe METR SoS shall enable METR operation…
|
from architecture:
SoSR-812 Discrepancy Contact Centre <—> METR SoS:…
|
|
SoSR-674 |
6.3.2.5 ConstraintsNo constraints are defined for this outp…
|
||
SoSR-675 |
6.3.2.6 Resulting actionIt is the responsibility of the operatio…
|
||
SoSR-1372 |
6.3.3 Information flow: METR information |
||
SoSR-1373 |
6.3.3.1 FunctionThe METR SoS shall provide authorized re…
|
supported by:
SoSR-830 Function
fulfils:
ConOps-442 Trustworthiness — Reliability — Resilien…
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
SoSR-1374 |
6.3.3.2 ContentThe METR information flow shall include …
|
||
SoSR-1375 |
|
uses:
SoSR-102 Feature catalogue
|
|
SoSR-1376 |
|
uses:
SoSR-512 METR information
|
|
SoSR-1377 |
|
uses:
SoSR-85 METR information content
|
|
SoSR-1378 |
|
uses:
SoSR-86 METR information meta-data
|
|
SoSR-1379 |
|
uses:
SoSR-87 Observable transport rule attributes
|
|
SoSR-1380 |
|
uses:
SoSR-821 Additional transport rule attributes
|
|
SoSR-1381 |
6.3.3.3 DestinationThe METR SoS shall provide METR informat…
|
from architecture:
SoSR-1013 METR SoS —> MCMC: METR information (as d…
SoSR-1407 METR SoS —> Non-METR Distribution System…
|
|
SoSR-1382 |
6.3.3.4 CausalityThe METR SoS shall provide METR informat…
|
from architecture:
SoSR-1013 METR SoS —> MCMC: METR information (as d…
SoSR-1407 METR SoS —> Non-METR Distribution System…
|
|
SoSR-1384 |
6.3.3.5 Constraints |
||
SoSR-1385 |
6.3.3.5.1 Location constraintThe METR SoS may allow subscribed system…
|
fulfils:
ConOps-473 User — Rule — Distribution — Efficiency
|
|
SoSR-1386 |
|
||
SoSR-1387 |
|
fulfils:
ConOps-475 User — Rule — Journey planning
|
|
SoSR-1388 |
|
||
SoSR-1389 | NOTE: The mobile user can vary its location co… | ||
SoSR-1390 |
6.3.3.5.2 Content constraintThe METR SoS may allow subscribed system…
|
fulfils:
ConOps-473 User — Rule — Distribution — Efficiency
|
|
SoSR-1398 |
6.3.3.5.3 Response timeThe METR SoS shall begin providing the M…
|
fulfils:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
SoSR-1399 |
6.3.3.5.4 Data qualityThe METR SoS shall only distribute METR …
|
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-441 Trustworthiness — Reliability — Quality …
ConOps-490 Rule maker — Independent verification
|
|
SoSR-1403 |
6.3.3.5.5 Emerging rule availabilityThe METR SoS shall provide authorized sy…
|
fulfils:
ConOps-446 Trustworthiness — Reliability — Complete…
|
|
SoSR-1405 |
6.3.3.6 Resulting actionThe requesting system is responsible for…
|
||
SoSR-464 |
6.3.4 Information flow: METR information for adaptation |
||
SoSR-855 |
6.3.4.1 FunctionThe METR SoS shall provide METR adapter …
|
supported by:
SoSR-830 Function
fulfils:
ConOps-468 User — Rule — Awareness
|
|
SoSR-465 |
6.3.4.2 ContentMETR information for adaptation flow sha…
|
realized by:
CSR-211 Information content
DSR-282 Information content
DSR-264 Information content
|
|
SoSR-467 |
|
uses:
SoSR-102 Feature catalogue
|
|
SoSR-468 |
|
uses:
SoSR-512 METR information
|
|
SoSR-469 |
|
uses:
SoSR-85 METR information content
|
|
SoSR-655 |
|
uses:
SoSR-86 METR information meta-data
|
|
SoSR-656 |
|
uses:
SoSR-87 Observable transport rule attributes
|
|
SoSR-657 |
|
uses:
SoSR-821 Additional transport rule attributes
|
|
SoSR-466 |
6.3.4.3 DestinationThe METR SoS shall provide METR informat…
|
from architecture:
SoSR-816 METR SoS —> METR adapter system: METR in…
|
|
SoSR-470 |
6.3.4.4 CausalityThe METR SoS shall provide the METR info…
|
from architecture:
SoSR-816 METR SoS —> METR adapter system: METR in…
|
|
SoSR-676 | NOTE: Within the context of this document, the… | ||
SoSR-856 |
6.3.4.5 Constraints |
||
SoSR-471 |
6.3.4.5.1 Location constraintThe METR SoS shall provide METR informat…
|
realized by:
CSR-218 Location constraint
DSR-287 Location constraint
DSR-269 Location constraints
RSR-325 Location constraint
RSR-312 Location constraints
|
|
SoSR-472 |
|
realized by:
CSR-70 Information flow: METR information for c…
CSR-86 Request relevant METR information
DSR-188 General
RSR-114 Information flow: METR input
RSR-133 Rule entry
fulfils:
ConOps-468 User — Rule — Awareness
|
|
SoSR-473 |
|
realized by:
CSR-70 Information flow: METR information for c…
CSR-86 Request relevant METR information
DSR-188 General
RSR-114 Information flow: METR input
RSR-133 Rule entry
fulfils:
ConOps-468 User — Rule — Awareness
ConOps-475 User — Rule — Journey planning
|
|
SoSR-474 |
|
realized by:
CSR-70 Information flow: METR information for c…
CSR-86 Request relevant METR information
DSR-188 General
RSR-114 Information flow: METR input
RSR-133 Rule entry
fulfils:
ConOps-468 User — Rule — Awareness
ConOps-475 User — Rule — Journey planning
|
|
SoSR-661 | NOTE: The mobile user can vary its location co… | ||
SoSR-475 |
6.3.4.5.2 Content constraintThe METR SoS shall provide the METR info…
|
realized by:
CSR-219 Constraints based on characteristics
DSR-288 Constraints based on characteristics
DSR-273 Constraints based on characteristics
RSR-326 Constraints based on characteristics
RSR-313 Characteristic constraints
|
|
SoSR-476 |
|
Implies:
SoSR-507 Identify necessary rule criteria
realized by:
CSR-156 METR information criteria
CSR-150 changes to the vehicle configuration (e.…
CSR-59 Maintain awareness of user characteristi…
DSR-194 the relevant rules;
RSR-133 Rule entry
fulfils:
ConOps-462 User — Awareness — Self-awareness
ConOps-468 User — Rule — Awareness
ConOps-474 User — Rule — Applicability — Permits
ConOps-477 User — Status — Manual inputs
|
|
SoSR-1818 |
|
fulfils:
ConOps-474 User — Rule — Applicability — Permits
|
|
SoSR-477 |
|
Implies:
SoSR-507 Identify necessary rule criteria
realized by:
CSR-150 changes to the vehicle configuration (e.…
fulfils:
ConOps-462 User — Awareness — Self-awareness
ConOps-468 User — Rule — Awareness
|
|
SoSR-478 |
|
Implies:
SoSR-507 Identify necessary rule criteria
realized by:
CSR-151 Default configuration
fulfils:
ConOps-462 User — Awareness — Self-awareness
ConOps-468 User — Rule — Awareness
|
|
SoSR-662 |
|
Implies:
SoSR-507 Identify necessary rule criteria
fulfils:
ConOps-462 User — Awareness — Self-awareness
ConOps-468 User — Rule — Awareness
|
|
SoSR-865 | NOTE: This division of characteristics is inte… | ||
SoSR-220 |
6.3.4.5.3 Provide rules in priority orderThe METR SoS shall deliver METR informat…
|
realized by:
DSR-220 Priority delivery
fulfils:
ConOps-472 User — Rule — Distribution — Prioritizat…
|
|
SoSR-409 | NOTE: This requirement can assist in fulfillin… | ||
SoSR-480 |
6.3.4.5.4 Response timeThe METR SoS shall begin providing the M…
|
realized by:
CSR-227 Obtain METR information as directed
CSR-229 Latency
CSR-233 Performance requirement
DSR-278 Performance requirement for requests
DSR-295 Performance requirement
RSR-261 Provisioning latency
RSR-334 Performance requirement
fulfils:
ConOps-443 Trustworthiness — Reliability — Timeline…
tailored by:
SoSR-857 metrResponseTime
|
|
SoSR-979 |
6.3.4.5.5 Verified informationThe METR distributor shall only distribu…
|
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
|
|
SoSR-207 |
6.3.4.5.6 Information deliveryThe METR SoS shall ensure that each METR…
|
||
SoSR-410 | EXAMPLE: A jurisdiction uses a wide-area informat… | ||
SoSR-411 | NOTE: The probability that a user system can a… | ||
SoSR-74 |
6.3.4.5.7 METR information availabilityThe METR SoS shall ensure the continued …
|
realized by:
CSR-70 Information flow: METR information for c…
DHSR-51 Information flow: METR information
DSR-188 General
RSR-118 Information flow: METR information
RSR-114 Information flow: METR input
RSR-133 Rule entry
fulfils:
ConOps-433 Trustworthiness — Reliability — Availabi…
tailored by:
SoSR-866 metrUpdateCycle
|
|
SoSR-408 | NOTE: Mobile users are responsible for determi… | ||
SoSR-680 | EXAMPLE: Users can refresh rules often enough to … | ||
SoSR-1411 | EXAMPLE: Use a guaranteed delivery, subscription-… | ||
SoSR-1412 | EXAMPLE: Local beacons that notify approaching ve… | ||
SoSR-1413 | EXAMPLE: Local signs that notify approaching vehi… | ||
SoSR-1414 | EXAMPLE: Obtain access to low frequency spectrum … | ||
SoSR-339 |
6.3.4.5.8 Emerging rule availabilityThe METR SoS shall provide users with re…
|
realized by:
CSR-72 Information flow: local METR information…
CSR-199 availability of electronic rules for eac…
CSR-200 communication parameters used to obtain …
DSR-188 General
DSR-169 Rule management application info
DSR-191 Ad-hoc rule management info
RSR-114 Information flow: METR input
supported by:
SoSR-843 Function
fulfils:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-468 User — Rule — Awareness
|
|
SoSR-162 |
6.3.4.5.9 Remote emergent rulesUpon direction from a rule maker, the ME…
|
realized by:
CSR-72 Information flow: local METR information…
DSR-169 Rule management application info
DSR-191 Ad-hoc rule management info
RSR-114 Information flow: METR input
fulfils:
ConOps-468 User — Rule — Awareness
ConOps-484 Rule maker — Publicize — Rules at a dist…
|
|
SoSR-483 |
6.3.4.6 Resulting actionThe requesting user is responsible for d…
|
||
SoSR-500 |
6.4 Functional requirements |
||
SoSR-503 |
6.4.1 Verification of METR rules |
supports:
SoSR-526 Resulting action
|
|
SoSR-167 |
6.4.1.1 Verify locations associated with rulesThe METR SoS shall verify that the locat…
|
realized by:
RSR-170 verifying that the boundaries of defined…
constrained by:
ConOps-410 The applicable location for each rule ca…
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
|
|
SoSR-159 |
6.4.1.2 Maintain awareness of rule makersThe METR SoS shall be cognizant of the a…
|
fulfils:
ConOps-482 Rule maker — Rule signer
|
|
SoSR-62 |
6.4.1.3 Verify rule consistencyThe METR SoS shall identify inconsistenc…
|
realized by:
CSR-118 Verification process
DHSR-76 Information flow: Information verificati…
DSR-108 Verification process
RSR-167 Verification process
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-486 Rule maker — Discrepancies — Primary
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
SoSR-677 |
6.4.1.4 Ensure data qualityAll information shall be verified and si…
|
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-482 Rule maker — Rule signer
|
|
SoSR-1468 | NOTE: The extent of verification can be establ… | ||
SoSR-1813 |
6.4.1.5 Ensure data resiliencyThe METR SoS shall provide a local data …
|
fulfils:
ConOps-456 Trustworthiness — Reliability — Availabi…
ConOps-442 Trustworthiness — Reliability — Resilien…
|
|
SoSR-501 |
6.4.2 METR information storage requirements |
||
SoSR-678 |
6.4.2.1 AvailabilityThe METR SoS shall maintain the availabi…
|
fulfils:
ConOps-433 Trustworthiness — Reliability — Availabi…
ConOps-434 Trustworthiness — Reliability — Availabi…
ConOps-435 Trustworthiness — Reliability — Availabi…
ConOps-437 Trustworthiness — Reliability — Availabi…
ConOps-442 Trustworthiness — Reliability — Resilien…
|
|
SoSR-679 |
6.4.2.2 IntegrityThe METR SoS shall maintain the integrit…
|
fulfils:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-450 Trustworthiness — Security — Authority —…
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
SoSR-105 |
6.4.2.3 Access control for dataThe METR SoS shall only grant access to …
|
realized by:
ITS-SUR-10 Access controls
fulfils:
ConOps-450 Trustworthiness — Security — Authority —…
|
|
SoSR-103 |
6.4.2.4 Ensure confidentiality of stored informationThe METR SoS shall maintain the confiden…
|
realized by:
ITS-SUR-8 minimizing the amount of PII that it sto…
ITS-SUR-10 Access controls
fulfils:
ConOps-449 Trustworthiness — Security — Confidentia…
|
|
SoSR-965 |
6.4.2.5 Limited data storageThe METR SoS shall only store data that …
|
fulfils:
ConOps-455 Trustworthiness — Security — Authority —…
|
|
SoSR-107 |
6.4.2.6 Ensure data privacyThe METR SoS shall only use data for pur…
|
2022-05-03: Kenneth Vaughn
Any suggestions on how to be more specific and yet still appropriate? |
realized by:
ITS-SUR-40 Maintain privacy
fulfils:
ConOps-455 Trustworthiness — Security — Authority —…
|
SoSR-964 | NOTE: Some jurisdictions have legal requiremen… | ||
SoSR-344 |
6.5 Applicable ITS station unit requirements |
||
SoSR-851 |
6.5.1 Support services |
||
SoSR-852 |
6.5.1.1 Service registration and discovery |
||
SoSR-876 |
6.5.1.1.1 Service registrationThe METR SoS shall register the followin…
|
||
SoSR-878 |
|
realized by:
DHSR-11 Information flow: Object registration
DSR-214 Information flow: Object registration
fulfils:
ConOps-434 Trustworthiness — Reliability — Availabi…
ConOps-458 User — Distributor — Discovery
|
|
SoSR-879 |
|
realized by:
DHSR-11 Information flow: Object registration
DSR-214 Information flow: Object registration
fulfils:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
SoSR-877 |
6.5.1.1.2 Service discoveryThe METR SoS shall use the service regis…
|
||
SoSR-880 |
|
realized by:
CSR-55 Information flow: Object discovery
fulfils:
ConOps-434 Trustworthiness — Reliability — Availabi…
ConOps-458 User — Distributor — Discovery
|
|
SoSR-881 |
|
realized by:
CSR-55 Information flow: Object discovery
fulfils:
ConOps-487 Rule maker — Discrepancies — Secondary
|
|
SoSR-218 |
6.5.1.2 ITS system management |
||
SoSR-217 |
6.5.1.2.1 Use preferred communicationsThe METR SoS shall use the communication…
|
realized by:
CSR-54 Use preferred communications
CSR-58 Maintain awareness of communication pref…
fulfils:
ConOps-460 User — Connectivity — Preferences
ConOps-248 Limitations of short-range wireless comm…
|
|
SoSR-900 | NOTE: Communication technologies with limited … | ||
SoSR-210 |
6.5.1.2.2 METR updates and patchesThe METR SoS shall manage the installati…
|
realized by:
ITS-SUR-51 Updates and patches
fulfils:
ConOps-479 User — System — Upgrade
|
|
SoSR-228 |
6.5.1.2.3 METR device managementThe METR SoS shall manage each METR infr…
|
realized by:
ITS-SUR-52 Application management
fulfils:
ConOps-446 Trustworthiness — Reliability — Complete…
|
|
SoSR-55 |
6.5.1.2.4 Manage servicesThe METR SoS shall manage the services r…
|
realized by:
DSR-168 Information flow: Component status
fulfils:
ConOps-437 Trustworthiness — Reliability — Availabi…
|
|
SoSR-209 |
6.5.1.2.5 Resource managementThe METR SoS shall manage the resources …
|
realized by:
ITS-SUR-3 Resource management
fulfils:
ConOps-442 Trustworthiness — Reliability — Resilien…
|
|
SoSR-56 |
6.5.1.2.6 Radio frequency regulationsThe METR SoS shall comply with local reg…
|
realized by:
CSR-30 Radio frequency regulations
DSR-43 Radio frequency regulations
fulfils:
ConOps-428 Radio frequency regulations
|
|
SoSR-967 |
6.5.1.2.7 System resiliencyThe METR SoS shall recover from any serv…
|
fulfils:
ConOps-456 Trustworthiness — Reliability — Availabi…
ConOps-442 Trustworthiness — Reliability — Resilien…
tailored by:
SoSR-970 metrRecoveryTime
|
|
SoSR-968 |
6.5.1.2.8 System availabilityThe METR SoS shall be available to provi…
|
fulfils:
ConOps-442 Trustworthiness — Reliability — Resilien…
tailored by:
SoSR-969 metrUpTimePercent
|
|
SoSR-1814 |
6.5.1.2.9 Connectivity awarenessThe METR SoS shall allow the METR user t…
|
fulfils:
ConOps-437 Trustworthiness — Reliability — Availabi…
|
|
SoSR-47 |
6.5.1.3 ITS security support |
||
SoSR-48 |
6.5.1.3.1 Obtain policiesThe METR SoS shall obtain relevant polic…
|
realized by:
ITS-SUR-16 Security policy and networking informati…
fulfils:
ConOps-453 Trustworthiness — Security — Integrity —…
|
|
SoSR-50 |
6.5.1.3.2 Implement enrolment policiesThe METR SoS shall implement the relevan…
|
realized by:
ITS-SUR-11 Comply with policies
ITS-SUR-19 Device enrolment information
fulfils:
ConOps-453 Trustworthiness — Security — Integrity —…
|
|
SoSR-45 |
6.5.1.3.3 Implement authorization policiesThe METR SoS shall implement the relevan…
|
realized by:
ITS-SUR-11 Comply with policies
constrained by:
ConOps-409 Only appointed rule makers [SOURCE: ISO …
fulfils:
ConOps-453 Trustworthiness — Security — Integrity —…
|
|
SoSR-52 |
6.5.1.3.4 Implement misbehaviour reporting policiesThe METR SoS shall implement relevant mi…
|
realized by:
ITS-SUR-11 Comply with policies
ITS-SUR-27 Misbehaviour report
fulfils:
ConOps-453 Trustworthiness — Security — Integrity —…
|
|
SoSR-51 |
6.5.1.3.5 Implement revocation policiesThe METR SoS shall implement relevant re…
|
2022-04-27: Kenneth Vaughn
This sounds like the METR system is revoking certificates; is there a better way to phrase this to clarify that METR is honouring the revocation lists? |
realized by:
ITS-SUR-11 Comply with policies
ITS-SUR-28 Security credential revocations
fulfils:
ConOps-453 Trustworthiness — Security — Integrity —…
|
SoSR-49 |
6.5.1.3.6 Ensure authenticated communicationsThe METR SoS shall ensure that all commu…
|
realized by:
ITS-SUR-29 Ensure authenticated communications
fulfils:
ConOps-453 Trustworthiness — Security — Integrity —…
|
|
SoSR-104 |
6.5.1.3.7 Confidential communicationsThe METR SoS shall encrypt any data that…
|
realized by:
ITS-SUR-7 encrypting any data exchanged across a p…
fulfils:
ConOps-449 Trustworthiness — Security — Confidentia…
|
|
SoSR-887 |
6.5.1.3.8 Access control for operationsThe METR SoS shall only grant access to …
|
fulfils:
ConOps-450 Trustworthiness — Security — Authority —…
ConOps-482 Rule maker — Rule signer
ConOps-483 Rule maker — Translation agent
|
|
SoSR-106 |
6.5.1.3.9 Maintain change logWithin the required data privacy limits,…
|
realized by:
ITS-SUR-12 Maintain configuration log
ITS-SUR-26 Maintain activity log
fulfils:
ConOps-451 Trustworthiness — Security — Integrity —…
|
|
SoSR-108 |
6.5.1.3.10 Terms of serviceThe METR SoS shall provide the terms of …
|
realized by:
CSR-48 Provide terms of service
DHSR-118 terms of service
DSR-219 terms of service
fulfils:
ConOps-459 User — Distributor — Terms of service
|
|
SoSR-345 |
6.5.1.3.11 Disclose use of informationWhen requested, the METR SoS shall discl…
|
realized by:
ITS-SUR-9 openly publishing what it uses PII for.
fulfils:
ConOps-445 Trustworthiness — Reliability — Transpar…
|
|
SoSR-150 |
6.5.1.3.12 Maintain security certificatesThe METR SoS shall maintain its security…
|
realized by:
ITS-SUR-30 Security credentials
fulfils:
ConOps-453 Trustworthiness — Security — Integrity —…
|
|
SoSR-869 |
6.5.2 Timeliness |
||
SoSR-1811 |
6.5.2.1 Pre-announced rule completenessThe METR SoS shall allow the METR user t…
|
constrained by:
ConOps-416 Jurisdictions are responsible for making…
fulfils:
ConOps-433 Trustworthiness — Reliability — Availabi…
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-468 User — Rule — Awareness
|
|
SoSR-870 |
6.5.2.2 Time to refreshThe METR SoS shall provide an efficient …
|
fulfils:
ConOps-473 User — Rule — Distribution — Efficiency
ConOps-244 Communications — Delivery — Efficiency
|
|
SoSR-97 |
6.5.2.3 Emergent rule availabilityThe METR SoS shall distribute any active…
|
realized by:
CSR-74 METR information criteria updates
CSR-76 Deliver rules
DSR-188 General
ITS-SUR-13 Response requirement
RSR-133 Rule entry
constrained by:
ConOps-416 Jurisdictions are responsible for making…
fulfils:
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
SoSR-1812 |
Within this context, a relevant rule set…
|
||
SoSR-872 | NOTE: When immediately enacting a new, long-te… | ||
SoSR-149 |
6.5.3 Efficient exchangeThe METR SoS shall deliver METR informat…
|
realized by:
DSR-158 General
DSR-222 Efficient data exchange
fulfils:
ConOps-473 User — Rule — Distribution — Efficiency
|
|
SoSR-929 |
6.5.4 FilteringThe METR SoS shall deliver METR informat…
|
fulfils:
ConOps-473 User — Rule — Distribution — Efficiency
|
|
SoSR-100 |
6.5.5 Open specificationFor all interfaces between physical obje…
|
realized by:
ITS-SUR-5 Open specification
fulfils:
ConOps-445 Trustworthiness — Reliability — Transpar…
|
|
SoSR-898 |
6.5.6 Backwards compatibilityThe METR SoS shall support interoperabil…
|
fulfils:
ConOps-245 Forwards and backwards compatibility
|
|
SoSR-901 |
6.5.7 Forward compatibilityThe METR SoS shall provide interfaces th…
|
fulfils:
ConOps-245 Forwards and backwards compatibility
ConOps-249 Aerial drones
|
|
SoSR-902 | EXAMPLE: Support for rules related to low-altitud… | ||
SoSR-101 |
6.5.8 Language neutralThe METR SoS shall provide all rules and…
|
realized by:
RSR-288 Language Neutrality
constrained by:
ConOps-413 Rules are to support multi-lingual envir…
fulfils:
ConOps-447 Trustworthiness — Reliability — Usabilit…
|
|
SoSR-360 |
6.6 METR information requirements |
||
SoSR-79 |
6.6.1 GeneralThe METR SoS shall require rules to be d…
|
realized by:
RSR-259 Ensure structured rules
fulfils:
ConOps-438 Trustworthiness — Reliability — Quality …
ConOps-469 User — Rule — Characteristics
|
|
SoSR-102 |
6.6.2 Feature catalogueThe METR SoS shall provide a catalogue o…
|
used by:
SoSR-1375 feature catalogue, as defined in 6.6.2;
SoSR-467 feature catalogue, as defined in 6.6.2;
fulfils:
ConOps-448 Trustworthiness — Reliability — Usabilit…
|
|
SoSR-512 |
6.6.3 METR information |
used by:
SoSR-510 METR information, as defined in 6.6.3;
SoSR-832 METR information, as defined in 6.6.3;
SoSR-860 METR information, as defined in 6.6.3;
SoSR-1376 METR information, as defined in 6.6.3;
SoSR-468 METR information, as defined in 6.6.3;
summarizes:
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-221 the geographical boundaries of the defin…
SoSR-337 the jurisdictional entity with authority…
SoSR-354 whether the defined area is believed to …
SoSR-803 the location of the transport facility […
SoSR-169 the jurisdictional entity with authority…
SoSR-65 Rule catalogue
SoSR-75 availability of each data provider [SOUR…
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-796 Transport rules
|
|
SoSR-60 |
6.6.3.1 Jurisdictional vocabularyThe METR SoS shall be aware of relevant …
|
realized by:
DHSR-51 Information flow: METR information
DSR-160 jurisdiction-specific meanings of releva…
RSR-114 Information flow: METR input
RSR-136 Vocabulary entry
refines:
MDR-15 Jurisdictional term
|
|
SoSR-129 |
|
realized by:
CSR-202 vehicle terms;
DHSR-156 vehicle terms;
DSR-257 vehicle terms;
refined by:
MDR-155 Vehicle category
summarized by:
SoSR-512 METR information
fulfils:
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-461 User — Awareness — Jurisdictional classi…
ConOps-470 User — Rule — Definition
|
|
SoSR-128 |
|
realized by:
CSR-203 facility terms;
DHSR-157 facility terms;
DSR-258 facility terms;
refined by:
MDR-156 Facility category
summarized by:
SoSR-512 METR information
fulfils:
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-461 User — Awareness — Jurisdictional classi…
ConOps-470 User — Rule — Definition
|
|
SoSR-168 |
|
2022-05-09: Kenneth Vaughn
Should we treat environmental (and other) conditions this way? In other words, if a lower speed limit applies when it is raining, how does a vehicle know when it is precipitating: a. The rule does not provide any guidance b. The rule defines an explicit rate of precipitation c. The rule refers to a environmental classification of "precipitation" that defines a specific rate |
realized by:
CSR-204 environmental state terms;
DHSR-158 environmental state terms;
DSR-259 environmental state terms;
refined by:
MDR-219 Road weather state
summarized by:
SoSR-512 METR information
constrained by:
ConOps-412 Rules are to clearly identify the times …
fulfils:
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-461 User — Awareness — Jurisdictional classi…
ConOps-470 User — Rule — Definition
|
SoSR-954 |
|
refined by:
MDR-381 Air quality state
summarized by:
SoSR-512 METR information
constrained by:
ConOps-412 Rules are to clearly identify the times …
fulfils:
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-461 User — Awareness — Jurisdictional classi…
ConOps-470 User — Rule — Definition
|
|
SoSR-147 |
|
realized by:
CSR-205 restriction terms;
DHSR-159 restriction terms;
DSR-260 restriction terms;
refined by:
MDR-220 Restriction
summarized by:
SoSR-512 METR information
fulfils:
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-461 User — Awareness — Jurisdictional classi…
ConOps-470 User — Rule — Definition
|
|
SoSR-404 |
|
realized by:
CSR-206 user terms; and
DHSR-160 user terms; and
DSR-261 user terms; and
refined by:
MDR-157 User category
summarized by:
SoSR-512 METR information
fulfils:
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-461 User — Awareness — Jurisdictional classi…
ConOps-470 User — Rule — Definition
|
|
SoSR-405 |
|
realized by:
CSR-207 usage terms.
DHSR-161 usage terms.
DSR-262 usage terms.
refined by:
MDR-158 Usage category
summarized by:
SoSR-512 METR information
fulfils:
ConOps-446 Trustworthiness — Reliability — Complete…
ConOps-461 User — Awareness — Jurisdictional classi…
ConOps-470 User — Rule — Definition
|
|
SoSR-807 |
6.6.3.2 Defined area catalogueThe METR SoS shall maintain a catalogue …
|
||
SoSR-221 |
|
realized by:
CSR-70 Information flow: METR information for c…
CSR-135 the boundaries of each relevant sub-area…
DHSR-73 the boundaries of each relevant sub-area…
DSR-159 the boundaries of each relevant sub-area…
RSR-114 Information flow: METR input
RSR-137 Defined area entry
refined by:
MDR-44 Defined area
summarized by:
SoSR-512 METR information
fulfils:
ConOps-434 Trustworthiness — Reliability — Availabi…
ConOps-466 User — Facility — Defined area
ConOps-467 User — Jurisdiction — Sub-areas
|
|
SoSR-337 |
|
realized by:
CSR-70 Information flow: METR information for c…
RSR-114 Information flow: METR input
refined by:
MDR-38 Jurisdiction
summarized by:
SoSR-512 METR information
fulfils:
ConOps-467 User — Jurisdiction — Sub-areas
ConOps-481 Rule maker — Jurisdictions — Identificat…
|
|
SoSR-354 |
|
summarized by:
SoSR-512 METR information
fulfils:
ConOps-485 Rule maker — Rules — Non-electronic
|
|
SoSR-1239 | NOTE: Boundaries for defined areas can be defi… | ||
SoSR-1240 | NOTE: A translation agent can also define seco… | ||
SoSR-1241 | EXAMPLE: A translation agent for a nation can est… | ||
SoSR-808 |
6.6.3.3 Facility catalogueThe METR SoS shall maintain a catalogue …
|
refined by:
MDR-145 Facility
|
|
SoSR-803 |
|
summarized by:
SoSR-512 METR information
fulfils:
ConOps-466 User — Facility — Defined area
|
|
SoSR-169 |
|
realized by:
CSR-70 Information flow: METR information for c…
RSR-137 Defined area entry
RSR-220 Facility entry
summarized by:
SoSR-512 METR information
fulfils:
ConOps-466 User — Facility — Defined area
|
|
SoSR-65 |
6.6.3.4 Rule catalogueThe METR SoS shall indicate rule categor…
|
realized by:
CSR-101 availability of electronic rules for eac…
CSR-70 Information flow: METR information for c…
DHSR-60 availability of electronic rules for eac…
DSR-163 availability of electronic rules for eac…
DSR-194 the relevant rules;
RSR-114 Information flow: METR input
RSR-137 Defined area entry
refined by:
MDR-197 Class: METR catalogue
MDR-38 Jurisdiction
summarized by:
SoSR-512 METR information
fulfils:
ConOps-435 Trustworthiness — Reliability — Availabi…
ConOps-467 User — Jurisdiction — Sub-areas
|
|
SoSR-1238 | NOTE: In order to claim that all rules are sup… | ||
SoSR-802 |
6.6.3.5 Supporting data provider catalogueThe METR SoS shall maintain a catalogue …
|
||
SoSR-75 |
|
realized by:
CSR-102 availability of supplemental data provid…
DHSR-61 availability of supplemental data provid…
DSR-164 availability of each supplemental data c…
summarized by:
SoSR-512 METR information
fulfils:
ConOps-436 Trustworthiness — Reliability — Availabi…
ConOps-444 Trustworthiness — Reliability — Timeline…
|
|
SoSR-92 |
|
realized by:
CSR-102 availability of supplemental data provid…
CSR-201 communication parameters used to obtain …
CSR-209 length of time time that each type of su…
DHSR-61 availability of supplemental data provid…
DSR-164 availability of each supplemental data c…
summarized by:
SoSR-512 METR information
constrained by:
ConOps-412 Rules are to clearly identify the times …
fulfils:
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-454 Trustworthiness — Security — Authority —…
ConOps-469 User — Rule — Characteristics
|
|
SoSR-962 |
|
summarized by:
SoSR-512 METR information
fulfils:
ConOps-454 Trustworthiness — Security — Authority —…
|
|
SoSR-963 |
|
summarized by:
SoSR-512 METR information
fulfils:
ConOps-454 Trustworthiness — Security — Authority —…
|
|
SoSR-796 |
6.6.3.6 Transport rulesThe METR SoS shall be aware of all trans…
|
refined by:
MDR-147 METR information item
MDR-19 Transport rule
summarized by:
SoSR-512 METR information
fulfils:
ConOps-435 Trustworthiness — Reliability — Availabi…
|
|
SoSR-85 |
6.6.4 METR information content |
used by:
SoSR-518 METR information content, as defined in …
SoSR-833 METR information content, as defined in …
SoSR-580 associated METR information content, if …
SoSR-861 METR information content, as defined in …
SoSR-1377 METR information content, as defined in …
SoSR-469 METR information content, as defined in …
summarizes:
SoSR-957 General
SoSR-69 METR information identifier
SoSR-70 METR information type
SoSR-1816 Verification level
|
|
SoSR-957 |
6.6.4.1 GeneralAll METR information content shall be pr…
|
summarized by:
SoSR-85 METR information content
fulfils:
ConOps-453 Trustworthiness — Security — Integrity —…
|
|
SoSR-69 |
6.6.4.2 METR information identifierFor each item of METR information, the M…
|
summarized by:
SoSR-849 the METR information identification for …
SoSR-85 METR information content
used by:
SoSR-629 METR information identifier, if known, a…
fulfils:
ConOps-469 User — Rule — Characteristics
|
|
SoSR-70 |
6.6.4.3 METR information typeFor each item of METR information, the M…
|
summarized by:
SoSR-85 METR information content
fulfils:
ConOps-469 User — Rule — Characteristics
|
|
SoSR-1816 |
6.6.4.4 Verification levelFor each item of METR information, the M…
|
summarized by:
SoSR-85 METR information content
fulfils:
ConOps-441 Trustworthiness — Reliability — Quality …
|
|
SoSR-86 |
6.6.5 METR information meta-data |
summarized by:
SoSR-958 General
SoSR-67 Provenance of information
SoSR-80 Freshness period
SoSR-961 Confidence Metrics
SoSR-977 indicate the confirmed discrepancy;
SoSR-978 indicate whether continued discrepancy r…
SoSR-976 provide guidance as to how the discrepan…
used by:
SoSR-519 METR information meta-data, as defined i…
SoSR-834 METR information meta-data, as defined i…
SoSR-862 METR information meta-data, as defined i…
SoSR-1378 METR information meta-data, as defined i…
SoSR-655 METR information meta-data, as defined i…
|
|
SoSR-958 |
6.6.5.1 GeneralWhile all data shall be exchanged in a s…
|
summarizes:
SoSR-86 METR information meta-data
|
|
SoSR-67 |
6.6.5.2 Provenance of informationFor each item of METR information, the M…
|
realized by:
RSR-135 Rule provenance
fulfils:
ConOps-441 Trustworthiness — Reliability — Quality …
ConOps-445 Trustworthiness — Reliability — Transpar…
ConOps-451 Trustworthiness — Security — Integrity —…
ConOps-469 User — Rule — Characteristics
ConOps-483 Rule maker — Translation agent
summarizes:
SoSR-86 METR information meta-data
|
|
SoSR-798 | NOTE: The provenance can indicate the entity t… | ||
SoSR-80 |
6.6.5.3 Freshness periodFor each item of METR information, the M…
|
realized by:
RSR-126 Provide expiration time
fulfils:
ConOps-439 Trustworthiness — Reliability — Quality …
ConOps-469 User — Rule — Characteristics
summarizes:
SoSR-86 METR information meta-data
|
|
SoSR-403 | NOTE: Rules, even emergent rules, can be overr… | ||
SoSR-1815 | NOTE: For efficiency, a default freshness peri… | ||
SoSR-961 |
6.6.5.4 Confidence MetricsFor each category of METR information an…
|
fulfils:
ConOps-441 Trustworthiness — Reliability — Quality …
summarizes:
SoSR-86 METR information meta-data
|
|
SoSR-975 |
6.6.5.5 Known conflictsFor each item of METR information with a…
|
||
SoSR-977 |
|
supported by:
SoSR-843 Function
fulfils:
ConOps-441 Trustworthiness — Reliability — Quality …
ConOps-465 User — Conflicts — Detected
summarizes:
SoSR-86 METR information meta-data
|
|
SoSR-978 |
|
supported by:
SoSR-843 Function
fulfils:
ConOps-465 User — Conflicts — Detected
summarizes:
SoSR-86 METR information meta-data
|
|
SoSR-976 |
|
supported by:
SoSR-843 Function
fulfils:
ConOps-465 User — Conflicts — Detected
summarizes:
SoSR-86 METR information meta-data
|
|
SoSR-87 |
6.6.6 Observable transport rule attributes |
used by:
SoSR-520 observable transport rule attributes, as…
SoSR-835 observable transport rule attributes, as…
SoSR-581 observable transport rule attributes, as…
SoSR-863 observable transport rule attributes, as…
SoSR-1379 observable transport rule attributes, as…
SoSR-656 observable transport rule attributes, as…
summarizes:
SoSR-959 General
SoSR-797 Transport rule type
SoSR-114 Transport rule location
SoSR-123 Transport rule temporal characteristics
SoSR-122 Transport rule applicability characteris…
SoSR-205 Transport rule status
SoSR-844 Transport rule expected implementation d…
|
|
SoSR-959 |
6.6.6.1 GeneralObservable transport rule attributes sha…
|
summarized by:
SoSR-87 Observable transport rule attributes
fulfils:
ConOps-453 Trustworthiness — Security — Integrity —…
|
|
SoSR-797 |
6.6.6.2 Transport rule typeFor each transport rule, the METR SoS sh…
|
summarized by:
SoSR-87 Observable transport rule attributes
fulfils:
ConOps-470 User — Rule — Definition
|
|
SoSR-114 |
6.6.6.3 Transport rule locationFor each transport rule, the METR SoS sh…
|
summarized by:
SoSR-87 Observable transport rule attributes
fulfils:
ConOps-463 User — Awareness — Mapping
ConOps-469 User — Rule — Characteristics
|
|
SoSR-123 |
6.6.6.4 Transport rule temporal characteristicsFor each transport rule, the METR SoS sh…
|
summarized by:
SoSR-87 Observable transport rule attributes
constrained by:
ConOps-412 Rules are to clearly identify the times …
ConOps-415 Approved rules [SOURCE: ISO 24315-1:2024…
fulfils:
ConOps-469 User — Rule — Characteristics
|
|
SoSR-122 |
6.6.6.5 Transport rule applicability characteristicsFor each transport rule, the METR SoS sh…
|
summarized by:
SoSR-87 Observable transport rule attributes
fulfils:
ConOps-469 User — Rule — Characteristics
|
|
SoSR-205 |
6.6.6.6 Transport rule statusFor each transport rule, the METR SoS sh…
|
realized by:
RSR-57 associate the traffic control device wit…
RSR-58 update the status of the associated elec…
summarized by:
SoSR-87 Observable transport rule attributes
fulfils:
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-469 User — Rule — Characteristics
|
|
SoSR-844 |
6.6.6.7 Transport rule expected implementation dateIf the status of the transport rule is n…
|
summarized by:
SoSR-87 Observable transport rule attributes
fulfils:
ConOps-443 Trustworthiness — Reliability — Timeline…
|
|
SoSR-821 |
6.6.7 Additional transport rule attributes |
used by:
SoSR-822 additional transport rule attributes, as…
SoSR-836 additional transport rule attributes, as…
SoSR-864 additional transport rule attributes, as…
SoSR-1380 additional transport rule attributes, as…
SoSR-657 additional transport rule attributes, as…
summarizes:
SoSR-960 General
SoSR-121 Transport rule enforceability
SoSR-148 Transport rule precedence
SoSR-90 Transport rule priority
SoSR-161 Transport rule signing organization
SoSR-94 the supporting data to be provided; and
SoSR-420 each supporting data provider authorized…
|
|
SoSR-960 |
6.6.7.1 GeneralAdditional rule attributes shall not be …
|
summarized by:
SoSR-821 Additional transport rule attributes
|
|
SoSR-121 |
6.6.7.2 Transport rule enforceabilityFor each transport rule, the METR SoS sh…
|
realized by:
CSR-137 the relevant rules and meta-data, includ…
summarized by:
SoSR-821 Additional transport rule attributes
fulfils:
ConOps-440 Trustworthiness — Reliability — Quality …
ConOps-469 User — Rule — Characteristics
|
|
SoSR-148 |
6.6.7.3 Transport rule precedenceFor each transport rule, the METR SoS sh…
|
summarized by:
SoSR-821 Additional transport rule attributes
constrained by:
ConOps-411 Rules issued by rule makers of overlappi…
fulfils:
ConOps-469 User — Rule — Characteristics
ConOps-471 User — Rule — Precedence
|
|
SoSR-90 |
6.6.7.4 Transport rule priorityFor each transport rule, the METR SoS sh…
|
summarized by:
SoSR-821 Additional transport rule attributes
fulfils:
ConOps-469 User — Rule — Characteristics
ConOps-472 User — Rule — Distribution — Prioritizat…
|
|
SoSR-161 |
6.6.7.5 Transport rule signing organizationFor each transport rule, the METR SoS sh…
|
2023-08-21: Kenneth Vaughn
Should be rule-maker rather than translator |
realized by:
RSR-257 Resulting action
summarized by:
SoSR-821 Additional transport rule attributes
fulfils:
ConOps-482 Rule maker — Rule signer
|
SoSR-91 |
6.6.7.6 Associated supporting dataFor each piece of supporting data requir…
|
||
SoSR-94 |
|
realized by:
CSR-102 availability of supplemental data provid…
DHSR-61 availability of supplemental data provid…
DSR-164 availability of each supplemental data c…
summarized by:
SoSR-821 Additional transport rule attributes
constrained by:
ConOps-412 Rules are to clearly identify the times …
fulfils:
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-454 Trustworthiness — Security — Authority —…
ConOps-469 User — Rule — Characteristics
|
|
SoSR-420 |
|
realized by:
CSR-102 availability of supplemental data provid…
CSR-210 the legal standing of each type of suppl…
DHSR-61 availability of supplemental data provid…
DSR-164 availability of each supplemental data c…
summarized by:
SoSR-821 Additional transport rule attributes
constrained by:
ConOps-412 Rules are to clearly identify the times …
fulfils:
ConOps-444 Trustworthiness — Reliability — Timeline…
ConOps-454 Trustworthiness — Security — Authority —…
ConOps-469 User — Rule — Characteristics
|
|
SoSR-1469 |
6.6.8 Auditing attributes |
||
SoSR-1470 |
6.6.8.1 Transport rule translation agentFor each transport rule, the METR SoS sh…
|
fulfils:
ConOps-966 Third party — Auditing
|
|
SoSR-1471 |
6.6.8.2 Transport rule verification agentFor each transport rule, the METR SoS sh…
|
fulfils:
ConOps-966 Third party — Auditing
|
|
SoSR-1472 |
6.6.8.3 Transport rule signing agentFor each transport rule, the METR SoS sh…
|
fulfils:
ConOps-483 Rule maker — Translation agent
ConOps-966 Third party — Auditing
|
|
SoSR-506 |
7 Actor responsibilities |
||
SoSR-932 |
7.1 Rule maker responsibilities |
||
SoSR-64 |
7.1.1 Maintain rulesThe rule maker is responsible for creati…
|
realized by:
CSR-71 Update METR information prior to expirat…
DSR-194 the relevant rules;
DSR-153 Ad-hoc rule information for users
RSR-133 Rule entry
fulfils:
ConOps-446 Trustworthiness — Reliability — Complete…
|
|
SoSR-234 |
7.1.2 Define location accuratelyIt is the responsibility of the METR rul…
|
realized by:
RSR-217 Location entry
fulfils:
ConOps-463 User — Awareness — Mapping
|
|
SoSR-412 | EXAMPLE: A parking rule is likely to require grea… | ||
SoSR-930 |
7.2 METR user responsibilities |
||
SoSR-873 |
7.2.1 Acquire rules before travellingA METR user is responsible for being awa…
|
||
SoSR-874 | NOTE: A user can obtain transport rules throug… | ||
SoSR-507 |
7.2.2 Identify necessary rule criteriaThe METR user is responsible for notifyi…
|
realized by:
CSR-59 Maintain awareness of user characteristi…
CSR-89 Determine relevant permissions
Implied 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…
|
|
SoSR-1817 |
7.2.3 Obtain necessary supporting dataThe METR user is responsible for obtaini…
|
fulfils:
ConOps-444 Trustworthiness — Reliability — Timeline…
|
|
SoSR-508 |
7.2.4 Process rulesThe METR user is responsible for combini…
|
fulfils:
ConOps-444 Trustworthiness — Reliability — Timeline…
|
|
SoSR-934 |
7.2.5 Identify discrepanciesAny inconsistencies detected among METR …
|
||
SoSR-353 |
7.2.6 MappingIt is the responsibility of users of MET…
|
realized by:
CSR-155 Mapping of METR information
fulfils:
ConOps-463 User — Awareness — Mapping
|
|
SoSR-171 |
7.2.7 Determine user's locationIt is the responsibility of the METR use…
|
realized by:
CSR-86 Request relevant METR information
CSR-155 Mapping of METR information
fulfils:
ConOps-464 User — Awareness — Geopositioning
|
|
SoSR-173 |
7.2.8 Determine environmental conditionsIt is the responsibility of METR users t…
|
realized by:
CSR-90 Determine environmental conditions
fulfils:
ConOps-478 User — Status — Environmental awareness
|
|
SoSR-1415 |
7.3 Implementer responsibilitiesThe implementer is responsible for ensur…
|
||
SoSR-1473 |
7.4 Auditor responsibilitiesThe auditor is responsible for investiga…
|
||
SoSR-325 |
8 System-level reference architecture |
||
SoSR-376 |
8.1 Overview |
2022-12-02: Kenneth Vaughn
This text should be reviewed by Tom, especially the way we reference ARC-IT (i.e., is this a part of ARC-IT, derived from ARC-IT, etc.) |
|
SoSR-1014 |
This system reference architecture for M…
|
||
SoSR-1249 |
This document defines architectural elem…
|
||
SoSR-1474 |
8.2 Physical view |
||
SoSR-1475 |
8.2.1 Mapping to functional viewFigure 4 depicts the assignment of the p…
|
||
SoSR-1476 |
The primary responsibilities of these sy…
|
||
SoSR-1477 |
|
||
SoSR-1478 |
|
||
SoSR-1479 |
|
||
SoSR-1480 |
|
||
SoSR-1481 |
|
||
SoSR-1482 | NOTE: For brevity, the (1) security and creden… | ||
SoSR-1483 | NOTE: Support flows that are defined in ARC-IT… | ||
SoSR-1484 |
8.2.2 Centralized METR information distribution service package |
||
SoSR-1485 |
8.2.2.1 OverviewThe physical view for the centralized ME…
|
||
SoSR-1486 |
8.2.2.2 Physical objectsThe centralized METR information distrib…
|
||
SoSR-1487 |
|
||
SoSR-1488 |
|
||
SoSR-1489 |
|
||
SoSR-1490 |
|
||
SoSR-1491 |
|
||
SoSR-1492 |
|
||
SoSR-1493 |
|
||
SoSR-1494 |
|
||
SoSR-1495 |
|
||
SoSR-1496 |
|
||
SoSR-1497 |
|
||
SoSR-1498 |
|
||
SoSR-1499 |
|
||
SoSR-1500 |
|
||
SoSR-1501 |
|
||
SoSR-1502 |
8.2.2.3 Information flowsThe centralized METR information distrib…
|
||
SoSR-1503 |
|
||
SoSR-1504 |
|
||
SoSR-1505 |
|
||
SoSR-1506 |
|
||
SoSR-1507 |
|
||
SoSR-1508 |
|
||
SoSR-1509 |
|
||
SoSR-1510 |
|
||
SoSR-1511 |
|
||
SoSR-1512 |
|
||
SoSR-1513 |
|
||
SoSR-1514 |
|
||
SoSR-1515 |
|
||
SoSR-1516 |
|
||
SoSR-1517 |
8.2.2.4 Description |
||
SoSR-1518 |
8.2.2.4.1 Information inputThe rule translation agent enters releva…
|
||
SoSR-1519 |
8.2.2.4.2 Information verificationLocal policies may encourage or require …
|
||
SoSR-1520 |
8.2.2.4.3 Information signingOnce a legal rule has been translated in…
|
||
SoSR-1521 |
8.2.2.4.4 Physical and METR rule synchronicityWhen new legal rules are approved, the p…
|
||
SoSR-1522 | NOTE: The implementation of the TCD and the cr… | ||
SoSR-1523 | NOTE: A METR rule can be associated with multi… | ||
SoSR-1524 |
8.2.2.4.5 Internal information distributionMETR information that is signed can be s…
|
||
SoSR-1525 |
METR information is also forwarded to ot…
|
||
SoSR-1526 |
If supported, METR information can be fo…
|
||
SoSR-1527 |
8.2.2.4.6 Information distribution to usersAs the METR distribution system receives…
|
||
SoSR-1528 |
|
||
SoSR-1529 |
|
||
SoSR-1530 |
|
||
SoSR-1531 |
|
||
SoSR-1532 |
|
||
SoSR-1533 |
|
||
SoSR-1534 |
As a result of these challenges, it is e…
|
||
SoSR-1535 |
8.2.3 Localized METR information distribution |
||
SoSR-1536 |
8.2.3.1 OverviewThe physical view for the localized METR…
|
||
SoSR-1537 |
8.2.3.2 Physical objectsThe localized METR information distribut…
|
||
SoSR-1538 |
|
||
SoSR-1539 |
|
||
SoSR-1540 |
|
||
SoSR-1541 |
|
||
SoSR-1542 |
|
||
SoSR-1543 |
|
||
SoSR-1544 |
|
||
SoSR-1545 |
|
||
SoSR-1546 |
|
||
SoSR-1547 |
|
||
SoSR-1548 |
|
||
SoSR-1549 |
|
||
SoSR-1550 |
|
||
SoSR-1551 |
|
||
SoSR-1552 |
|
||
SoSR-1553 |
|
||
SoSR-1554 |
8.2.3.3 Information flowsThe localized METR information distribut…
|
||
SoSR-1555 |
|
||
SoSR-1556 |
|
||
SoSR-1557 |
|
||
SoSR-1558 |
|
||
SoSR-1559 |
|
||
SoSR-1560 |
|
||
SoSR-1561 |
|
||
SoSR-1562 |
|
||
SoSR-1563 |
|
||
SoSR-1564 |
|
||
SoSR-1565 |
|
||
SoSR-1566 |
|
||
SoSR-1567 |
|
||
SoSR-1568 |
|
||
SoSR-1569 |
8.2.3.4 Description |
||
SoSR-1570 |
8.2.3.4.1 Information inputThe service package logically starts wit…
|
||
SoSR-1571 |
8.2.3.4.2 Information internal distributionMETR information can also be sent to oth…
|
||
SoSR-1572 |
If supported, METR information can be fo…
|
||
SoSR-1573 |
8.2.3.4.3 Establishing localized distributionLocalized rules can be disseminated thro…
|
||
SoSR-1574 |
8.2.3.4.4 Monitoring and managing localized distributionThe METR input device should inform its …
|
||
SoSR-1575 |
8.2.3.4.5 Information distribution to usersLocalized rules can be locally distribut…
|
||
SoSR-1576 |
8.2.4 Discrepancy management |
||
SoSR-1577 |
8.2.4.1 OverviewThe physical view for the discrepancy ma…
|
||
SoSR-1578 |
8.2.4.2 Physical objectsThe discrepancy management service packa…
|
||
SoSR-1579 |
|
||
SoSR-1580 |
|
||
SoSR-1581 |
|
||
SoSR-1582 |
|
||
SoSR-1583 |
|
||
SoSR-1584 |
|
||
SoSR-1585 |
|
||
SoSR-1586 |
|
||
SoSR-1587 |
|
||
SoSR-1588 |
|
||
SoSR-1589 |
|
||
SoSR-1590 |
|
||
SoSR-1591 |
|
||
SoSR-1592 |
|
||
SoSR-1593 |
|
||
SoSR-1594 |
|
||
SoSR-1595 |
8.2.4.3 Information flowsThe discrepancy management service packa…
|
||
SoSR-1596 |
|
||
SoSR-1597 |
|
||
SoSR-1598 |
|
||
SoSR-1599 |
|
||
SoSR-1600 |
|
||
SoSR-1601 |
|
||
SoSR-1602 |
|
||
SoSR-1603 |
|
||
SoSR-1604 |
|
||
SoSR-1605 |
|
||
SoSR-1606 |
|
||
SoSR-1607 |
|
||
SoSR-1608 |
|
||
SoSR-1609 |
|
||
SoSR-1610 |
|
||
SoSR-1611 |
|
||
SoSR-1612 |
8.2.4.4 Description |
||
SoSR-1613 |
8.2.4.4.1 User reports of discrepanciesWhen the METR information adaption funct…
|
||
SoSR-1614 |
8.2.4.4.2 Discrepancy report consolidationThe METR discrepancy handling system wil…
|
||
SoSR-1615 |
METR regulation systems can also learn o…
|
||
SoSR-1616 |
8.2.4.4.3 Discrepancy dispositionWhen the METR regulation system becomes …
|
||
SoSR-1617 |
Fully resolving a discrepancy might requ…
|
||
SoSR-1618 |
8.2.4.4.4 Supression of confirmed discrepanciesOnce a METR regulation system has been a…
|
||
SoSR-1619 |
Alternatively, the regulation system can…
|
||
SoSR-1620 |
Furthermore, the regulation system may w…
|
||
SoSR-1622 |
8.2.5 METR auditing service package |
||
SoSR-1623 |
8.2.5.1 OverviewThe physical view for the METR auditing …
|
||
SoSR-1624 |
8.2.5.2 Physical objectsThe auditing service package uses the fo…
|
||
SoSR-1627 |
|
||
SoSR-1632 |
|
||
SoSR-1629 |
|
||
SoSR-1630 |
|
||
SoSR-1628 |
|
||
SoSR-1631 |
|
||
SoSR-1633 |
|
||
SoSR-1634 |
|
||
SoSR-1625 |
8.2.5.3 Information flowsThe discrepancy management service packa…
|
||
SoSR-1626 |
8.2.5.4 DescriptionThe METR auditor queries METR component …
|
||
SoSR-1621 |
8.2.6 Service registration and discoveryMETR relies upon the service registratio…
|
||
SoSR-1635 |
|
||
SoSR-1636 |
|
||
SoSR-1637 | NOTE: ISO 23708 is expected to standardize the… | ||
SoSR-386 |
8.2.7 Security enrolment and credentials managementMETR relies upon the "device certificati…
|
||
SoSR-786 |
|
||
SoSR-787 |
|
||
SoSR-789 |
|
||
SoSR-784 |
|
||
SoSR-785 |
|
||
SoSR-788 |
|
||
SoSR-1639 | NOTE: ISO 23708 is expected to standardize the… | ||
SoSR-388 |
8.2.8 Core authorizationMETR relies upon the core authorization …
|
||
SoSR-793 |
|
||
SoSR-792 |
|
||
SoSR-790 |
|
||
SoSR-791 |
|
||
SoSR-1640 | NOTE: ISO 23708 is expected to standardize the… | ||
SoSR-795 |
8.2.9 System monitoringMETR relies upon the core authorization …
|
2023-01-11: Kenneth Vaughn
Do we need to show this or is this already covered within the emergent rule SP? |
|
SoSR-892 |
|
||
SoSR-896 |
|
||
SoSR-889 |
|
||
SoSR-890 |
|
||
SoSR-888 |
|
||
SoSR-891 |
|
||
SoSR-893 |
|
||
SoSR-894 |
|
||
SoSR-895 |
|
||
SoSR-1641 | NOTE: ISO 23708 is expected to standardize the… | ||
SoSR-1028 |
8.2.10 Physical objects |
||
SoSR-1655 |
8.2.10.1 OverviewThe physical objects used in the system-…
|
||
SoSR-1029 |
8.2.10.2 Connected vehicle (CV) roadside equipment (RSE)The CV RSE represents the roadside devic…
|
||
SoSR-1045 | NOTE: CV RSEs typically use wireless technolog… | ||
SoSR-1207 |
8.2.10.3 ITS roadway equipment (IRE)The IRE represents roadside devices that…
|
||
SoSR-1035 |
8.2.10.4 METR consumer systemThe METR consumer system receives guidan…
|
||
SoSR-1032 |
8.2.10.5 METR discrepancy handling centreA "METR discrepancy handling centre" is …
|
||
SoSR-1648 |
8.2.10.6 METR discrepancy handling systemA METR discrepancy handling system accep…
|
||
SoSR-1250 | NOTE: The discrepancy handling system can inco… | ||
SoSR-1033 |
8.2.10.7 METR distribution centreA "METR distribution centre" is a centre…
|
||
SoSR-1649 |
8.2.10.8 METR distribution systemA METR distribution system collects METR…
|
||
SoSR-1038 |
8.2.10.9 METR distribution vehicleThe METR distribution vehicle is typical…
|
||
SoSR-1034 |
8.2.10.10 METR input deviceThe METR input device represents any dev…
|
||
SoSR-1650 |
8.2.10.11 METR regulation centreA "METR regulation centre" is a centre-b…
|
||
SoSR-1036 |
8.2.10.12 METR regulation systemA METR regulation system enables the cre…
|
||
SoSR-1652 |
8.2.10.13 METR user deviceA "METR user device" represents any devi…
|
||
SoSR-1046 |
8.2.10.14 Other METR discrepancy handling centreDepending on deployments scenarios, a di…
|
||
SoSR-1653 |
8.2.10.15 Other METR distribution centreA METR distribution centre can exchange …
|
||
SoSR-1044 |
8.2.10.16 Other METR regulation centreA METR regulation centre can exchange ME…
|
||
SoSR-1654 |
8.2.10.17 Rule implementation agentThe rule implementation agent represents…
|
||
SoSR-1656 |
8.2.10.18 Rule signing agentThe rule signing agent represents the pe…
|
||
SoSR-1658 |
8.2.10.19 Rule translation agentThe rule translation agent represents th…
|
||
SoSR-1657 |
8.2.10.20 Rule verification agentThe rule verification agent represents t…
|
||
SoSR-1047 |
8.2.11 Information flows |
||
SoSR-1048 |
8.2.11.1 consolidated discrepancy reportThe "consolidated discrepancy report" fl…
|
realized by:
RSR-428 Definition
|
|
SoSR-1068 |
|
||
SoSR-1069 |
|
||
SoSR-1049 |
8.2.11.2 discrepancy report detailsWhile investigating a consolidated discr…
|
realized by:
RSR-435 Definition
|
|
SoSR-1070 |
|
||
SoSR-1071 |
|
||
SoSR-1050 |
8.2.11.3 discrepancy suppression infoOnce a METR regulation system has been a…
|
realized by:
RSR-488 Definition
|
|
SoSR-1072 |
|
||
SoSR-1073 |
|
||
SoSR-1051 |
8.2.11.4 field equipment statusThe ‘field equipment status” information…
|
||
SoSR-1074 |
|
||
SoSR-1097 |
8.2.11.5 local METR information for consumersThe “local METR information for consumer…
|
||
SoSR-1094 |
|
||
SoSR-1095 |
|
||
SoSR-1053 |
8.2.11.6 METR application informationThe “METR application information flow” …
|
realized by:
RSR-495 Definition
|
|
SoSR-1076 |
|
||
SoSR-1054 |
8.2.11.7 METR application statusThe “METR application status” informatio…
|
realized by:
RSR-455 Definition
|
|
SoSR-1077 |
|
||
SoSR-1642 |
8.2.11.8 METR audit informationThe “METR audit information” information…
|
||
SoSR-1716 |
|
||
SoSR-1717 |
|
||
SoSR-1718 |
|
||
SoSR-1719 |
|
||
SoSR-1055 |
8.2.11.9 METR coordinationThe “METR coordination” information flow…
|
realized by:
RSR-450 Definition
RSR-505 Definition
|
|
SoSR-1078 |
|
||
SoSR-1079 |
|
||
SoSR-1080 |
|
||
SoSR-1081 |
|
||
SoSR-1082 |
|
||
SoSR-1056 |
8.2.11.10 METR device statusThe “METR device status” information flo…
|
realized by:
RSR-500 Definition
|
|
SoSR-1083 |
|
||
SoSR-1057 |
8.2.11.11 METR discrepancy reportThe “METR discrepancy report” informatio…
|
||
SoSR-1084 |
|
||
SoSR-1099 |
|
||
SoSR-1643 |
8.2.11.12 METR emergent rule inputThe "METR emergent rule input" informati…
|
||
SoSR-1720 |
|
||
SoSR-1058 |
8.2.11.13 METR feedbackThe “METR feedback” information flow sup…
|
realized by:
RSR-408 Definition
|
|
SoSR-1085 |
|
||
SoSR-1059 |
8.2.11.14 METR informationThe “METR information” information flow …
|
realized by:
RSR-460 Definition
RSR-510 Definition
|
|
SoSR-1087 |
|
||
SoSR-1088 |
|
||
SoSR-1089 |
|
||
SoSR-1090 |
|
||
SoSR-1091 |
|
||
SoSR-1086 |
8.2.11.15 METR information for consumersThe “METR information for consumers” inf…
|
||
SoSR-1093 |
|
||
SoSR-1242 |
8.2.11.16 METR information signature requestThe "METR information signature request"…
|
||
SoSR-1243 |
This information flow occurs between:
|
||
SoSR-1244 |
|
||
SoSR-1061 |
8.2.11.17 METR inputThe “METR input” information flow suppor…
|
realized by:
RSR-402 Definition
|
|
SoSR-1096 |
|
||
SoSR-1062 |
8.2.11.18 METR management informationIf the rule is to be distributed through…
|
realized by:
RSR-515 Definition
|
|
SoSR-1098 |
|
||
SoSR-1060 |
8.2.11.19 signed METR informationThe “signed METR information” informatio…
|
realized by:
RSR-463 Definition
|
|
SoSR-1092 |
|
||
SoSR-1064 |
8.2.11.20 supporting dataThe "supporting data" information flow i…
|
||
SoSR-1101 |
|
||
SoSR-1102 |
|
||
SoSR-1103 |
|
||
SoSR-1105 |
|
||
SoSR-1104 |
|
||
SoSR-1100 | NOTE: Vehicle-sourced supporting data does not… | ||
SoSR-1065 |
8.2.11.21 system-generated discrepancy reportMETR regulation systems can learn of dis…
|
realized by:
RSR-211 Information flow: system-generated discr…
RSR-239 Definition
|
|
SoSR-1106 |
|
||
SoSR-1107 |
|
||
SoSR-1108 |
|
||
SoSR-1066 |
8.2.11.22 TCD discrepancy statusThe "TCD discrepancy status" information…
|
realized by:
RSR-473 Definition
|
|
SoSR-1109 |
|
||
SoSR-1067 |
8.2.11.23 TCD implementation statusThe “TCD implementation status” informat…
|
realized by:
RSR-478 Definition
|
|
SoSR-1646 |
|
||
SoSR-1644 |
8.2.11.24 TCD statusThe “TCD status” information flow suppor…
|
||
SoSR-1645 |
|
||
SoSR-1245 |
8.2.11.25 unverified METR informationThe “unverified METR information” inform…
|
realized by:
RSR-525 Definition
|
|
SoSR-1369 |
|
||
SoSR-1210 |
8.2.11.26 user updatesThe "user updates" information flow prov…
|
||
SoSR-1211 |
|
||
SoSR-1246 |
8.2.11.27 verified METR informationThe “verified METR information” flow sup…
|
realized by:
RSR-483 Definition
|
|
SoSR-1370 |
|
||
SoSR-1826 |
8.2.12 Cybersecurity overviewMETR includes multiple features to promo…
|
||
SoSR-1827 |
Rules are established by rule makers. Ho…
|
||
SoSR-1828 |
|
||
SoSR-1829 |
|
||
SoSR-1830 |
In either case, the information is trans…
|
||
SoSR-1659 |
8.3 Enterprise view |
||
SoSR-1660 |
8.3.1 OverviewWhile the physical view reflects how the…
|
||
SoSR-1661 |
Figure 15 focuses on how each of the ent…
|
||
SoSR-1662 |
Key 4 - METR regulation system 5 - METR …
|
||
SoSR-1663 |
8.3.2 Enterprise objects |
||
SoSR-1749 |
8.3.2.1 Adapter system developer |
derived from:
SP-45 The preferred implementation is that a u…
SP-76 The ConOps should describe why we are di…
reflects:
ConOps-452 Trustworthiness — Reliability — Accuracy
|
|
SoSR-1750 |
The developer of the adapter is responsi…
|
||
SoSR-1751 |
|
||
SoSR-1752 |
|
||
SoSR-1753 |
|
||
SoSR-1754 |
|
||
SoSR-1755 |
|
||
SoSR-1756 |
The adapter considers all these data sou…
|
||
SoSR-1757 | NOTE: The algorithm is likely to consider othe… | ||
SoSR-1758 |
The adapter makes the current active rul…
|
||
SoSR-1664 |
8.3.2.2 AuditorThe auditor is responsible for determini…
|
||
SoSR-1747 |
8.3.2.3 Consumer system developer |
derived from:
SP-8 Users have a need to indicate their pref…
SP-28 It should be the responsibility of the u…
SP-73 The user is responsible for requesting a…
SP-85 Clarify text of responsibilities (as sho…
|
|
SoSR-1748 |
The consumer system developer [SOURCE: I…
|
||
SoSR-1666 |
8.3.2.4 Device manufacturerThe manufacturer is responsible for deve…
|
||
SoSR-1677 |
8.3.2.5 Device ownerThe device owner is responsible for purc…
|
||
SoSR-1667 |
8.3.2.6 Discrepancy contactThe discrepancy contact typically repres…
|
||
SoSR-1668 |
8.3.2.7 Discrepancy handler |
||
SoSR-1795 |
The primary responsibilities of the disc…
|
||
SoSR-1796 | NOTE: Jurisdictions will likely need to establ… | ||
SoSR-1669 |
8.3.2.8 DistributorThe distributor is responsible for colle…
|
derived from:
SP-43 The ConOps needs to assign the responsib…
SP-49 A mobile refresh provider should be char…
SP-61 The disseminator is responsible for ensu…
SP-72 The disseminator is responsible for publ…
SP-74 All roles are responsible for 1) identif…
reflects:
ConOps-452 Trustworthiness — Reliability — Accuracy
ConOps-435 Trustworthiness — Reliability — Availabi…
ConOps-443 Trustworthiness — Reliability — Timeline…
ConOps-448 Trustworthiness — Reliability — Usabilit…
|
|
SoSR-1738 |
For each defined area that it covers, a …
|
||
SoSR-1740 |
|
||
SoSR-1741 |
|
||
SoSR-1742 |
METR receivers need this information to …
|
||
SoSR-1739 |
An emergent rule distributor [SOURCE: IS…
|
||
SoSR-1743 |
All distributors package rules into one …
|
||
SoSR-1671 |
8.3.2.9 METR user |
||
SoSR-1773 |
8.3.2.9.1 OverviewWithin the existing system, transport us…
|
||
SoSR-1774 |
8.3.2.9.2 Transport-related userA transport-related user is a METR user …
|
||
SoSR-1775 |
|
||
SoSR-1776 |
|
||
SoSR-1777 |
|
||
SoSR-1778 |
|
||
SoSR-1779 |
|
||
SoSR-1780 |
|
||
SoSR-1781 |
|
||
SoSR-1782 |
|
||
SoSR-1783 |
A transport-related user does not have a…
|
||
SoSR-1784 |
8.3.2.9.3 Ancillary userAn ancillary user is a METR user that is…
|
||
SoSR-1785 |
|
||
SoSR-1786 |
|
||
SoSR-1787 |
|
||
SoSR-1788 |
|
||
SoSR-1789 |
|
||
SoSR-1790 |
|
||
SoSR-1791 |
|
||
SoSR-1792 |
|
||
SoSR-1793 |
An ancillary user does not have any addi…
|
||
SoSR-1794 | NOTE: Some ancillary users can be authorized t… | ||
SoSR-1672 |
8.3.2.10 METR adapter system developerThe METR adaptor system developer is res…
|
||
SoSR-1744 |
8.3.2.11 Non-METR distributor |
||
SoSR-1745 |
A non-METR distributor [SOURCE: ISO 2431…
|
||
SoSR-1746 | NOTE: A non-METR distributor strips the rule-s… | ||
SoSR-1670 |
8.3.2.12 Rule implementer |
||
SoSR-1721 |
8.3.2.12.1 GeneralThe rule implementer [SOURCE: ISO 24315-…
|
||
SoSR-1722 |
8.3.2.12.2 Announcing the implementationDistributing updates of pre-announced ru…
|
||
SoSR-1723 |
|
||
SoSR-1724 |
|
||
SoSR-1725 |
8.3.2.12.3 Avoiding rule duplicationIn either case, the information would ne…
|
||
SoSR-1726 |
|
||
SoSR-1727 |
|
||
SoSR-1728 |
|
||
SoSR-1729 |
During Step 2, some METR user systems wi…
|
||
SoSR-1730 |
8.3.2.12.4 Updating the pre-announced ruleOnce the TCD is implemented and the rele…
|
||
SoSR-1731 |
|
||
SoSR-1732 |
|
||
SoSR-1733 |
|
||
SoSR-1673 |
8.3.2.13 Rule makerThe rule maker is responsible for making…
|
||
SoSR-1678 |
8.3.2.14 Rule signerThe rule signer is responsible for signi…
|
||
SoSR-1674 |
8.3.2.15 Rule verifierThe rule verifier is responsible for ver…
|
||
SoSR-1675 |
8.3.2.16 Supporting data provider |
||
SoSR-1759 |
8.3.2.16.1 GeneralAlthough supporting data providers are a…
|
||
SoSR-1760 |
8.3.2.16.2 External data providersExternal data providers are supporting d…
|
||
SoSR-1761 |
|
||
SoSR-1762 |
|
||
SoSR-1763 |
8.3.2.16.3 Vehicle-sourced data providersA vehicle-sourced data provider is a sto…
|
||
SoSR-1764 |
|
||
SoSR-1765 |
|
||
SoSR-1766 |
|
||
SoSR-1767 |
8.3.2.16.4 User-sourced data providersA user-sourced data provider is a stored…
|
||
SoSR-1768 |
|
||
SoSR-1769 |
|
||
SoSR-1770 |
|
||
SoSR-1772 |
Due to the varied degree of trustworthin…
|
||
SoSR-1771 |
8.3.2.16.5 Other classification schemesData can also be classified as either cr…
|
||
SoSR-1676 |
8.3.2.17 TranslatorThe translator is responsible for conver…
|
||
SoSR-1734 |
A translator can use an entirely manuall…
|
||
SoSR-1735 |
|
||
SoSR-1736 |
|
||
SoSR-1737 |
Regardless of the process used, the tran…
|
||
SoSR-1679 |
8.3.3 Agreements and expectation definitions |
||
SoSR-1700 |
8.3.3.1 GeneralIt is expected that agreements that requ…
|
||
SoSR-1701 |
|
||
SoSR-1702 |
|
||
SoSR-1703 |
Ideally all conflicts and inconsistencie…
|
||
SoSR-1680 |
8.3.3.2 Current rule or provisioning agreementAn agreement that the provider (e.g., co…
|
||
SoSR-1681 |
8.3.3.3 Discrepancy reporting agreementAn agreement that the provider (e.g., di…
|
||
SoSR-1682 |
8.3.3.4 Expectation of audit informationAn expectation that the provider (i.e., …
|
||
SoSR-1683 |
8.3.3.5 Expectation of coordinationAn expectation that the provider and cli…
|
||
SoSR-1684 |
8.3.3.6 Expectation of discrepancy issueAn expectation that the provider (i.e., …
|
||
SoSR-1685 |
8.3.3.7 Expectation of discrepancy reportsAn expectation that the provider (e.g., …
|
||
SoSR-1686 |
8.3.3.8 Expectation of relevant rulesAn expectation that the provider (e.g., …
|
||
SoSR-1687 |
8.3.3.9 Expectation of rulesAn expectation that the provider will ma…
|
||
SoSR-1688 |
8.3.3.10 Expectation of supporting dataAn expectation that the provider (e.g., …
|
||
SoSR-1689 |
8.3.3.11 Expectation of TCD maintenanceAn expectation that the provider (i.e., …
|
||
SoSR-1690 |
8.3.3.12 Relevant rule provisioning agreementAn agreement that the provider (e.g., ad…
|
||
SoSR-1691 |
8.3.3.13 Rule distribution agreementAn agreement stating that the provider (…
|
||
SoSR-1692 |
8.3.3.14 Rule provisioning agreementAn agreement that the provider (i.e., tr…
|
||
SoSR-1693 |
8.3.3.15 Rule publication agreementAn agreement that the provider (i.e., ru…
|
||
SoSR-1694 |
8.3.3.16 Rule sharing agreementAn agreement that the provider (e.g., di…
|
||
SoSR-1695 |
8.3.3.17 Rule signing agreementAn agreement that the provider (e.g., ru…
|
||
SoSR-1696 |
8.3.3.18 Rule verification agreementAn agreement stating that the provider (…
|
||
SoSR-1697 |
8.3.3.19 System provisioning agreementAn agreement that the provider (i.e., ma…
|
||
SoSR-1698 |
8.3.3.20 TCD status provisioning agreementAn agreement that the provider (i.e., im…
|
||
SoSR-1699 |
8.3.3.21 Vehicle usage agreementAn agreement that the provider (e.g., ve…
|
||
SoSR-1704 |
8.3.4 Role definitionsThe role types referenced in this docume…
|
||
SoSR-1705 |
Role Description Monitors The enterprise…
|
||
SoSR-1797 |
8.3.5 Resources |
||
SoSR-1809 |
8.3.5.1 GeneralThis clause describes the resources cont…
|
||
SoSR-1801 |
8.3.5.2 EnvironmentNo changes are envisioned for the enviro…
|
||
SoSR-1800 |
8.3.5.3 Public recordNo changes are envisioned for the public…
|
||
SoSR-1798 |
8.3.5.4 RulesThe rules discussed in ISO 24315-2:2024,…
|
||
SoSR-1799 |
8.3.5.5 Traffic control devicesThe TCDs discussed in ISO 24315-2:2024, …
|
||
SoSR-1806 |
8.3.5.6 Wide area information dissemination systemA wide area information dissemination sy…
|
||
SoSR-389 |
9 Variables |
||
SoSR-390 |
9.1 GeneralVariables allow customization of perform…
|
||
SoSR-396 |
9.2 catalogueUpdateIntervalThe catalogueUpdateInterval is the allow…
|
tailors:
DHSR-59 Information flow: METR catalogue
DSR-162 Information flow: METR catalogue
|
|
SoSR-397 |
9.3 criteriaLatencyTimeThe criteriaLatencyTime is the allowable…
|
tailors:
CSR-74 METR information criteria updates
|
|
SoSR-393 |
9.4 distributionResponseTimeThe distributionResponseTime is the maxi…
|
tailors:
DSR-156 One-time request performance requirement
|
|
SoSR-972 |
9.5 informationRefreshDurationThe informationRefreshDuration is the mi…
|
||
SoSR-970 |
9.6 metrRecoveryTimeThe metrRecoveryTime is the maximum allo…
|
tailors:
SoSR-967 System resiliency
|
|
SoSR-857 |
9.7 metrResponseTimeThe metrResponseTime is the maximum allo…
|
tailors:
SoSR-480 Response time
|
|
SoSR-660 | NOTE: The metrResponseTime does not consider t… | ||
SoSR-866 |
9.8 metrUpdateCycleThe amount of time that retrieved METR i…
|
tailors:
SoSR-74 METR information availability
|
|
SoSR-969 |
9.9 metrUpTimePercentThe metrUpTimePercent is the minimum per…
|
tailors:
SoSR-968 System availability
|
|
SoSR-391 |
9.10 provisionLatencyThe provisionLatency is the allowable ti…
|
tailors:
RSR-261 Provisioning latency
RSR-175 Functionality
|
|
SoSR-392 |
9.11 subscriptionRefreshTimeThe subscriptionRefreshTime is the allow…
|
tailors:
DSR-157 Subscription performance requirement
|
|
SoSR-394 |
9.12 translationUpdateIntervalThe translationUpdateInterval is the all…
|
tailors:
DHSR-51 Information flow: METR information
DSR-188 General
RSR-118 Information flow: METR information
|
|
SoSR-982 |
10 Conformance |
||
SoSR-985 |
10.1 GeneralThis annex provides a concise conformanc…
|
||
SoSR-909 |
10.2 Symbols indicating requirement statusTable 1 defines the codes used to specif…
|
||
SoSR-910 |
Abbreviated term Description M Mandatory…
|
||
SoSR-911 |
The O.# (range) notation is used to show…
|
||
SoSR-912 |
10.3 Conditional status notationThe predicate notations in Table 2 may b…
|
||
SoSR-913 |
Notation Description
|
||
SoSR-914 |
The
|
||
SoSR-915 |
The predicates used in the concise confo…
|
||
SoSR-916 |
Predicate Subclause serviceDiscovery Con…
|
||
SoSR-984 |
10.4 Concise conformance tableTable 4 provides the concise conformance…
|
||
SoSR-983 |
Clause Title Conformance 6.2.2 Informati…
|
||
SoSR-986 | NOTE: For example, item 6.5.1.1.2.b in the las… | ||
SoSR-905 |
11 Traceability |
||
SoSR-908 |
11.1 GeneralEach requirement in this document traces…
|
||
SoSR-955 |
11.2 Column ExplanationEach user need, constraint, and requirem…
|
||
SoSR-1416 |
12 Diagram conventions |
||
SoSR-1706 |
12.1 Physical view conventionsThe physical viewpoint represents physic…
|
||
SoSR-1707 |
Each physical view diagram includes phys…
|
||
SoSR-1708 | |||
SoSR-1709 |
Major categories of physical objects inc…
|
||
SoSR-1710 |
|
||
SoSR-1711 |
|
||
SoSR-1712 |
|
||
SoSR-1713 |
|
||
SoSR-1714 |
|
||
SoSR-1417 |
12.2 Enterprise view conventions |
||
SoSR-1715 |
12.2.1 OverviewThe data expectation diagrams contained …
|
||
SoSR-1418 |
12.2.2 Enterprise objectsEach box with a heavy border in the figu…
|
||
SoSR-1419 |
12.2.3 ResourcesEach box with a lightly dashed border re…
|
||
SoSR-1420 |
12.2.4 Relationships |
||
SoSR-1421 |
12.2.4.1 AgreementsWhile agreements are often established w…
|
||
SoSR-1422 |
|
||
SoSR-1423 |
|
||
SoSR-1424 |
|
||
SoSR-1425 |
|
||
SoSR-1426 |
|
||
SoSR-1427 |
If formal agreements cannot be establish…
|
||
SoSR-1428 |
12.2.4.2 ExpectationsAll expectations include expectations th…
|
||
SoSR-1429 |
|
||
SoSR-1430 |
|
||
SoSR-1431 |
|
||
SoSR-1432 |
Any expectation can be formalized into a…
|
||
SoSR-1433 |
12.2.4.3 RolesRelationships between enterprise objects…
|
||
SoSR-1434 |
12.2.5 Naming conventionsEnterprise view relationships use initia…
|
||
SoSR-1435 |
12.2.6 Relationship statusThe status of relationships are depicted…
|
||
SoSR-1436 |
12.2.7 Colour coding of elementsEnterprise objects and resources are col…
|
||
SoSR-1437 |
12.3 Diagrams provide limited contextReference architectures are typically ve…
|
||
SoSR-1251 |
13 Possible deployments of role-based architecture |
derived from:
SP-18 Should provide sample diagrams showing i…
SP-20 The ConOps should provide practical use …
|
|
SoSR-1252 |
13.1 OverviewThe METR SoS is a complex system of syst…
|
||
SoSR-1253 |
13.2 Physical grouping of functionality |
||
SoSR-1254 |
Regardless of the amount of area covered…
|
||
SoSR-1311 | NOTE: Many of the physical objects identified … | ||
SoSR-1255 |
|
||
SoSR-1313 |
|
||
SoSR-1256 |
|
||
SoSR-1371 | NOTE: Campuses include any private grounds. | ||
SoSR-1314 |
|
||
SoSR-1315 |
|
||
SoSR-1257 |
|
||
SoSR-1316 |
|
||
SoSR-1258 |
|
||
SoSR-1317 |
|
||
SoSR-1318 |
|
||
SoSR-1319 |
The ISO 24315 series documents assume th…
|
||
SoSR-1260 |
13.3 Regulation system inputs |
||
SoSR-1261 |
13.3.1 OverviewThe complexity of a METR regulation syst…
|
||
SoSR-1262 |
13.3.2 Isolated regulation systemIf the jurisdictional environment for a …
|
||
SoSR-1263 |
13.3.3 Hierarchical regulation systemsIn most cases, it is envisioned that reg…
|
||
SoSR-1264 |
13.3.4 Composite regulation systemsWhile eventually most regulation systems…
|
||
SoSR-1326 |
13.3.5 Regulation system evolutionSystems evolve over time and early syste…
|
||
SoSR-1265 |
13.3.6 Importance of coordinationPrior to deploying a METR regulation sys…
|
||
SoSR-1266 |
13.4 Populating METR information |
||
SoSR-1267 |
13.4.1 OverviewOne of the challenges of deploying the M…
|
||
SoSR-1268 |
13.4.2 Select rule categories to populateOne useful way to organize the entry of …
|
||
SoSR-1331 |
13.4.3 Pre-announced information |
||
SoSR-1328 |
13.4.3.1 Define sub-jurisdictionsIt is envisioned that most regulation sy…
|
||
SoSR-1269 |
13.4.3.2 Define jurisdictional sub-areasLarge jurisdictional entities (e.g., a l…
|
||
SoSR-1329 |
13.4.3.3 Define key termsJurisdictional entities need to ensure t…
|
||
SoSR-1270 |
13.4.3.4 Coordinate entry of pre-announced rulesIdeally, pre-announced rules should be e…
|
||
SoSR-1330 |
13.4.4 Plan for emergent rulesWhen developing a regulation system, it …
|
||
SoSR-1334 |
13.4.5 Identify supporting data providersSome rules will require supporting data …
|
||
SoSR-1335 |
13.4.6 Commercial involvement |
||
SoSR-1336 |
13.4.6.1 Commercial off-the-shelf softwareThe standardization of interfaces is exp…
|
||
SoSR-1337 |
13.4.6.2 Commercial data entryIn addition to developing commercial off…
|
||
SoSR-1272 |
13.4.6.3 Commercial regulation systemA private company can also enter rules. …
|
||
SoSR-1339 |
13.5 Pre-announced METR information distribution |
||
SoSR-1344 |
13.5.1 OverviewDue to the volume of information coupled…
|
||
SoSR-1325 |
13.5.2 Distribution of rulesThe primary purpose of the pre-announced…
|
||
SoSR-1347 |
13.5.3 Scope of distribution system |
||
SoSR-1348 |
13.5.3.1 Geographic coverage of rulesIt is expected that most distribution sy…
|
||
SoSR-1349 |
13.5.3.2 Rule category coverageLikewise, distribution systems can have …
|
||
SoSR-1350 |
13.5.3.3 Communications reachIt is expected that most pre-announced d…
|
||
SoSR-1340 |
13.5.4 Number of distribution systems |
||
SoSR-1342 |
13.5.4.1 Single distribution systemThe design of the regulation system need…
|
||
SoSR-1343 |
13.5.4.2 Multiple distribution systemsIf the regulation system is expected to …
|
||
SoSR-1345 |
13.5.5 Number of regulation systems |
||
SoSR-1346 |
13.5.5.1 Single regulation systemIf there is a one-to-one relationship be…
|
||
SoSR-1323 |
13.5.5.2 Multiple regulation systemsIt is envisioned that, in most deploymen…
|
||
SoSR-1324 |
13.5.6 Maintenance of rulesDistribution systems need to be aware of…
|
||
SoSR-1355 |
13.5.7 Boundary considerationsAnother factor to consider when deployin…
|
||
SoSR-1273 |
13.6 Emergent rule distribution |
||
SoSR-1351 |
13.6.1 OverviewThe distribution of emergent rules is mu…
|
||
SoSR-1357 |
13.6.2 Scope of distribution systemIt is envisioned that emergent rule dist…
|
||
SoSR-1353 |
13.6.3 Distribution mechanismsEmergent rules can be distributed throug…
|
||
SoSR-1356 |
13.6.4 Migrating emergent rules to pre-announced rulesDeployments also need to consider how em…
|
||
SoSR-1358 |
13.7 Consumer system deploymentsIt is expected that consumer systems wil…
|
||
SoSR-1359 |
13.8 Discrepancy handling system deployments |
||
SoSR-1360 |
13.8.1 Policies for pre-processing reports |
||
SoSR-1362 |
13.8.1.1 OverviewDiscrepancy handling systems are respons…
|
||
SoSR-1363 |
13.8.1.2 Public reportsIt is expected that most reports will be…
|
||
SoSR-1364 |
13.8.1.3 Certified reportsIn addition to crowd-sourced data [SOURC…
|
||
SoSR-1361 |
13.8.2 Scope of discrepancy handling system |
||
SoSR-1365 |
13.8.2.1 Geographic coverage areaDeployers of discrepancy handling system…
|
||
SoSR-1366 |
13.8.2.2 Sources of discrepancy reportsDiscrepancy reports originate from consu…
|
||
SoSR-1367 |
13.8.2.3 Destination of reportsThe discrepancy handling systems also ne…
|
Needed so that users can identify areas that support rule categories without asking for all rules (e.g., for routing I first want to exclude areas that do not support types of data)