24315 METR |
Submit Comment Traceability Tables: |
ID | Description | Discussion | Links |
---|---|---|---|
RSR-5 |
1 ScopeThe management of electronic transport r…
|
||
RSR-4 |
2 Normative referencesThe following documents are referred to …
|
||
RSR-335 |
ISO/TS 14812, Intelligent transport syst…
|
||
RSR-336 |
ISO/TS 24315-1, Intelligent transport sy…
|
||
RSR-337 |
ISO/IEC/IEEE 24765, Systems and software…
|
||
RSR-2 |
3 Terms and definitionsFor the purposes of this document, the t…
|
||
RSR-193 |
3.1 collected informationinformation collected from RSE and Vehic…
|
||
RSR-194 |
3.2 entered informationinformation entered by the operator
|
||
RSR-195 |
3.3 obtained informationinformation obtained from other center-b…
|
||
RSR-208 |
3.4 discrepancy fingerprintset of characteristics of a discrepancy …
|
||
RSR-3 |
4 Symbols and abbreviated terms |
||
RSR-338 |
4.1 ADSAutomated Driving System
|
||
RSR-339 |
4.2 ARC-ITArchitecture Reference for Cooperative a…
|
||
RSR-340 |
4.3 HTMLhypertext markup language
|
||
RSR-341 |
4.4 IECInternational Electrotechnical Commissio…
|
||
RSR-342 |
4.5 IEEEInstitute of Electrical and Electronics …
|
||
RSR-343 |
4.6 ISOOrganization for International Standardi…
|
||
RSR-344 |
4.7 ITSintelligent transport systems
|
||
RSR-345 |
4.8 METRmanagement of electronic traffic regulat…
|
||
RSR-346 |
4.9 RSEroadside equipment
|
||
RSR-351 |
4.10 SoSsystem of systems
|
||
RSR-347 |
4.11 SoSRSystem of systems requirements
|
||
RSR-348 |
4.12 TCDtraffic control device
|
||
RSR-349 |
4.13 TStechnical specification
|
||
RSR-350 |
4.14 VRUvulnerable road user
|
||
RSR-182 |
5 Overview |
||
RSR-353 |
5.1 METR purposeThe Management of Electronic Transport R…
|
||
RSR-354 |
5.2 METR scopeThe METR network is designed to provide …
|
||
RSR-540 |
5.3 Regulation system overview |
||
RSR-352 |
5.3.1 GeneralFigure 1 identifies the incoming and out…
|
2023-08-15: Kenneth Vaughn
Add Graphic |
|
RSR-263 |
5.3.1.1 Centre-based regulation system for pre-announced rulesCentre-based regulation systems for pre-…
|
2023-08-15: Kenneth Vaughn
Add graphic |
|
RSR-264 |
5.3.1.2 Centre-based regulation system for emergent rulesCentre-based regulation systems for emer…
|
2023-08-15: Kenneth Vaughn
Add graphic |
|
RSR-265 |
5.3.1.3 Localized regulation systemLocalized regulation systems are primari…
|
2023-08-15: Kenneth Vaughn
Add graphic |
|
RSR-274 | EXAMPLE: Jurisdiction A only allows activation of… | ||
RSR-275 | EXAMPLE: Jurisdiction B only allows certain types… | ||
RSR-541 |
5.3.2 MRS information flowsThe MRS-related information transfers (i…
|
||
RSR-363 |
|
||
RSR-539 |
|
||
RSR-385 |
|
||
RSR-381 |
|
||
RSR-382 |
|
||
RSR-538 |
|
||
RSR-379 |
|
||
RSR-377 |
|
||
RSR-362 |
|
||
RSR-387 |
|
||
RSR-378 |
|
||
RSR-380 |
|
||
RSR-383 |
|
||
RSR-369 |
|
||
RSR-360 |
|
||
RSR-361 |
|
||
RSR-370 |
|
||
RSR-364 |
|
||
RSR-386 |
|
||
RSR-543 |
|
||
RSR-535 |
|
||
RSR-372 |
|
||
RSR-536 |
|
||
RSR-365 |
|
||
RSR-384 |
|
||
RSR-534 |
|
||
RSR-373 |
|
||
RSR-537 |
|
||
RSR-359 |
Details about each flow shown in the fig…
|
||
RSR-542 |
5.3.3 Contextual information flowsIn addition to the MRS-related informati…
|
||
RSR-355 |
5.3.4 User characteristics |
||
RSR-390 |
5.3.4.1 Rule makerRule makers are responsible for approvin…
|
||
RSR-545 |
5.3.4.2 Rule signing agent |
||
RSR-388 |
5.3.4.3 Rule translation agentRule translation agents are responsible …
|
||
RSR-546 |
5.3.4.4 Rule verification agent |
||
RSR-356 |
5.3.5 Assumptions and dependencies |
||
RSR-391 |
5.3.5.1 Assumptions |
||
RSR-392 |
5.3.5.1.1 Internet-based communicationsThe MRS will likely use the Internet and…
|
||
RSR-394 |
5.3.5.1.2 Information deliveryThe MRS should be designed and operated …
|
||
RSR-395 | EXAMPLE: A jurisdiction uses a wide-area informat… | ||
RSR-396 | NOTE: The probability that a user system can a… | ||
RSR-397 |
5.3.5.1.3 Geo-positioning rulesThe MRS will geo-position rules using re…
|
||
RSR-398 |
5.3.5.1.4 Leverage existing standardsMETR is one ITS service among many exist…
|
||
RSR-357 |
5.3.6 Traceability conventionsWithin the systems engineering process, …
|
||
RSR-267 |
5.3.7 Internal interfacesThis document does not place requirement…
|
2023-08-15: Kenneth Vaughn
I don't think that there are any such interfaces for the MRS (although the text probably needs to be refined to be more clear what we are talking about). The prime example of the interface being discussed here is the interface between the consumer system and the interpreter (i.e., an internal interface that exists within the Vehicle OBE Physical Object). We do not intend to define an interoperable interface for this or even to attempt to define all requireents - but we do need to at least state what our expectations are. This should keep TC 22 reasonably happy. 2023-08-18: Kenneth Vaughn
Needs further review in reflection of clause 8 content |
|
RSR-7 |
6 Regulation system requirements |
||
RSR-358 |
6.1 GeneralThe MRS requirements are presented based…
|
||
RSR-422 |
|
||
RSR-423 |
|
||
RSR-424 |
|
||
RSR-425 |
|
||
RSR-426 |
|
||
RSR-427 |
|
||
RSR-105 |
6.2 Inputs to MRS |
||
RSR-196 |
6.2.1 Information flow: consolidated discrepancy report |
derived from:
DHSR-83 Information flow: Consolidated discrepan…
|
|
RSR-428 |
6.2.1.1 DefinitionThe consolidated discrepancy report flow…
|
2023-08-18: Kenneth Vaughn
Do we define the content and flow each time or do we simply reference the text in the architecture (SoSR) |
realizes:
SoSR-1048 consolidated discrepancy report
|
RSR-430 |
6.2.1.2 SourceThe MRS receives the consolidated discre…
|
||
RSR-431 |
6.2.1.3 CausalityThe consolidated discrepancy report flow…
|
||
RSR-442 | NOTE: Local policies can establish rules defin… | ||
RSR-432 |
6.2.1.4 ConstraintsNo constraints are defined for this inpu…
|
2023-08-18: Kenneth Vaughn
Consider moving to the architecture portion of the SoSR |
|
RSR-433 |
6.2.1.5 Resulting actionUpon receipt of the consolidated discrep…
|
supported by:
RSR-213 Resolve discrepancy
|
|
RSR-212 |
6.2.2 Information flow: discrepancy report details |
derived from:
DHSR-100 Information flow: Discrepancy report det…
generated by:
RSR-205 Coordinate with others
|
|
RSR-435 |
6.2.2.1 DefinitionThe discrepancy report details flow shal…
|
realizes:
SoSR-1049 discrepancy report details
|
|
RSR-437 |
6.2.2.2 SourceThe MRS receives the discrepancy report …
|
||
RSR-439 |
6.2.2.3 CausalityAs directed by a rule translator agent, …
|
||
RSR-440 |
6.2.2.4 ConstraintsThe request shall indicate the consolida…
|
2023-08-21: Kenneth Vaughn
I am thinking this is where we would identify additional filters: e.g., reports containing images, sequential report number, what else? |
|
RSR-438 |
6.2.2.5 Resulting actionThe MRS shall provide the discrepancy re…
|
2023-08-21: Kenneth Vaughn
Do we need flows for these interactions with the rule translator agent? |
|
RSR-401 |
6.2.3 Information flow: METR application status |
||
RSR-455 |
6.2.3.1 DefinitionThe METR application status flow shall b…
|
realizes:
SoSR-1054 METR application status
|
|
RSR-456 |
6.2.3.2 SourceThe MRS receives the discrepancy report …
|
||
RSR-457 |
6.2.3.3 CausalityThe MRS shall request the METR applicati…
|
||
RSR-458 |
6.2.3.4 ConstraintsNo constraints are defined for this inpu…
|
||
RSR-178 |
6.2.3.5 Resulting actionThe METR regulation system shall monitor…
|
2023-08-22: Kenneth Vaughn
I wonder if this is really the MRS or whether it might be the TMC and the MRS just tells the TMC what the rules are. |
derived from:
DSR-224 rule management application status
|
RSR-286 | NOTE: The status information can include the p… | ||
RSR-214 |
6.2.4 Information flow: METR coordination |
derived from:
RSR-128 Information flow: METR coordination
realizes:
SoSR-491 Information flow: METR coordination
|
|
RSR-450 |
6.2.4.1 DefinitionThe METR coordination flow shall be as d…
|
realizes:
SoSR-1055 METR coordination
|
|
RSR-451 |
6.2.4.2 SourceThe METR coordination flow can be initia…
|
||
RSR-452 |
6.2.4.3 CausalityAs needed to investigate and resolve dis…
|
||
RSR-453 |
6.2.4.4 ConstraintsNo constraints are defined for this inpu…
|
||
RSR-454 |
6.2.4.5 Resulting actionUpon the receipt of a METR coordination …
|
supported by:
RSR-213 Resolve discrepancy
|
|
RSR-118 |
6.2.5 Information flow: METR information |
derives:
RSR-110 Information flow: METR information
realizes:
SoSR-74 METR information availability
tailored by:
SoSR-394 translationUpdateInterval
|
|
RSR-460 |
6.2.5.1 DefinitionThe METR information flow shall be as de…
|
realizes:
SoSR-1059 METR information
|
|
RSR-461 |
6.2.5.2 SourceThe METR information flow is received fr…
|
||
RSR-153 |
6.2.5.3 CausalityFor each relevant regulation system from…
|
||
RSR-462 | NOTE: A national regulation system can collect… | ||
RSR-157 | NOTE: A regulation system for a city can colle… | ||
RSR-177 |
6.2.5.4 ConstraintsWhen making a request for METR informati…
|
||
RSR-282 | EXAMPLE: A city regulation system can request all… | ||
RSR-174 |
6.2.5.5 Resulting actionThe METR distribution system shall perfo…
|
supported by:
RSR-167 Verification process
|
|
RSR-114 |
6.2.6 Information flow: METR input |
realizes:
SoSR-487 Information flow: legal rules
SoSR-472 proximity from a point location;
SoSR-473 proximity along a route; and
SoSR-474 user-defined area.
SoSR-74 METR information availability
SoSR-339 Emerging rule availability
SoSR-162 Remote emergent rules
SoSR-60 Jurisdictional vocabulary
SoSR-221 the geographical boundaries of the defin…
SoSR-337 the jurisdictional entity with authority…
SoSR-65 Rule catalogue
|
|
RSR-402 |
6.2.6.1 DefinitionThe METR input flow shall be as defined …
|
realizes:
SoSR-1061 METR input
|
|
RSR-319 |
6.2.6.2 SourceThe “METR input” flow is provided by one…
|
||
RSR-163 | NOTE: It is the responsibility of translator a… | ||
RSR-324 |
6.2.6.3 CausalityThe METR input flow is initiated by a ru…
|
||
RSR-405 |
6.2.6.4 Constraints |
||
RSR-325 |
6.2.6.4.1 Location constraintThe MRS shall require each rule to ident…
|
realizes:
SoSR-471 Location constraint
|
|
RSR-326 |
6.2.6.4.2 Constraints based on characteristicsThe MRS shall require each rule to clear…
|
2023-08-21: Kenneth Vaughn
The details should probably be moved to the SoSR or MDR |
realizes:
SoSR-475 Content constraint
|
RSR-327 |
|
||
RSR-328 |
|
||
RSR-329 |
|
||
RSR-330 |
(others as deemed appropriate in req’ts …
|
||
RSR-407 |
6.2.6.4.3 Data format constraintThe entered data shall conform to METR s…
|
||
RSR-50 |
6.2.6.5 Resulting actionThe METR regulation system shall perform…
|
supported by:
RSR-333 Information verification
RSR-167 Verification process
|
|
RSR-400 |
6.2.7 Information flow: signed METR information |
||
RSR-463 |
6.2.7.1 DefinitionThe signed METR information flow shall b…
|
realizes:
SoSR-1060 signed METR information
|
|
RSR-464 |
6.2.7.2 SourceThe METR information approval flow is ob…
|
||
RSR-465 |
6.2.7.3 CausalityThe MRS shall prompt the relevant rule-m…
|
||
RSR-466 |
6.2.7.4 ConstraintsTHE MRS shall have established policies …
|
||
RSR-257 |
6.2.7.5 Resulting actionOnce the rule has been signed by a rule …
|
2023-08-21: Kenneth Vaughn
Do we want to be as specific as an electronic signature or is there another way to say this in a more functional context |
realizes:
SoSR-161 Transport rule signing organization
|
RSR-211 |
6.2.8 Information flow: system-generated discrepancy report |
supported by:
RSR-213 Resolve discrepancy
derived from:
DHSR-88 Information flow: System-generated discr…
DSR-137 Information flow: System-generated discr…
RSR-210 Information flow: system-generated discr…
realizes:
SoSR-1065 system-generated discrepancy report
|
|
RSR-468 |
6.2.8.1 DefinitionThe system-generated discrepancy report …
|
||
RSR-469 |
6.2.8.2 SourceThe “system-generated discrepancy report…
|
||
RSR-470 |
6.2.8.3 CausalityThe system-generated discrepancy report …
|
||
RSR-471 |
6.2.8.4 ConstraintsNo constraints are defined for this inpu…
|
||
RSR-472 |
6.2.8.5 Resulting actionUpon receipt of the system-generated dis…
|
summarized by:
RSR-213 Resolve discrepancy
|
|
RSR-399 |
6.2.9 Information flow: TCD discrepancy status |
||
RSR-473 |
6.2.9.1 DefinitionThe system-generated discrepancy report …
|
realizes:
SoSR-1066 TCD discrepancy status
|
|
RSR-474 |
6.2.9.2 SourceThe TCD discrepancy status flow can be i…
|
||
RSR-475 |
6.2.9.3 Causality |
2023-10-17: Kenneth Vaughn
Is it appropriate for this document to place requirements on external systems? |
|
RSR-528 |
6.2.9.3.1 NotificationThe M&CMC shall notify the MRS whenever …
|
||
RSR-529 |
6.2.9.3.2 QueryAt any time, the MRS may request the sta…
|
||
RSR-476 |
6.2.9.4 ConstraintsA request for TCD discrepancy status may…
|
||
RSR-477 |
6.2.9.5 Resulting actionThe MRS shall allow the translator agent…
|
||
RSR-56 |
6.2.10 Information flow: TCD installation status |
||
RSR-478 |
6.2.10.1 DefinitionThe TCD installation status flow shall b…
|
realizes:
SoSR-1067 TCD implementation status
|
|
RSR-480 |
6.2.10.2 SourceThe TCD discrepancy status flow can be i…
|
||
RSR-481 |
6.2.10.3 Causality |
||
RSR-530 |
6.2.10.3.1 NotificationThe M&CMC shall notify the MRS whenever …
|
||
RSR-531 |
6.2.10.3.2 QueryAt any time, the MRS may request the sta…
|
||
RSR-482 |
6.2.10.4 ConstraintsA request for TCD installation status ma…
|
||
RSR-479 |
6.2.10.5 Resulting actionUpon notice of the installation of a tra…
|
||
RSR-57 |
|
realizes:
SoSR-205 Transport rule status
|
|
RSR-58 |
|
realizes:
SoSR-205 Transport rule status
|
|
RSR-59 | NOTE: The appropriate rule can be an existing … | ||
RSR-55 |
6.2.11 Information flow: verified METR information |
||
RSR-483 |
6.2.11.1 DefinitionThe verified METR information flow shall…
|
2023-08-21: Kenneth Vaughn
Need to add to SoSR |
realizes:
SoSR-1246 verified METR information
|
RSR-484 |
6.2.11.2 SourceThe verified METR information flow is in…
|
||
RSR-485 |
6.2.11.3 CausalityThe METR verification system shall initi…
|
||
RSR-487 | NOTE: An unverified METR information flow can … | ||
RSR-486 |
6.2.11.4 ConstraintsNo constraints are defined for this inpu…
|
||
RSR-201 |
6.2.11.5 Resulting actionThe MRS shall update the meta-data for t…
|
||
RSR-198 | NOTE: NOTE: Local regulations can require the … | ||
RSR-106 |
6.3 Outgoing flow requirements |
||
RSR-24 |
6.3.1 Component statusThe METR regulation system shall make it…
|
2023-08-16: Kenneth Vaughn
Should this be moved to the ITS-SUR? |
derived from:
DSR-168 Information flow: Component status
|
RSR-284 | EXAMPLE: A distribution system can include a serv… | ||
RSR-414 |
6.3.2 Information flow: discrepancy suppression information |
||
RSR-488 |
6.3.2.1 DefinitionThe discrepancy suppression information …
|
realizes:
SoSR-1050 discrepancy suppression info
|
|
RSR-489 |
6.3.2.2 DestinationThe discrepancy suppression information …
|
||
RSR-491 |
6.3.2.3 CausalityAs necessary, the MRS may request the st…
|
||
RSR-492 |
6.3.2.4 ConstraintsThe request shall identify the type of d…
|
||
RSR-493 |
6.3.2.5 Resulting actionThe MRS shall maintain a log of discrepa…
|
||
RSR-494 |
The MRS can use this log to release supp…
|
||
RSR-415 |
6.3.3 Information flow: METR application information |
||
RSR-495 |
6.3.3.1 DefinitionThe METR application information flow sh…
|
realizes:
SoSR-1053 METR application information
|
|
RSR-496 |
6.3.3.2 DestinationThe discrepancy suppression information …
|
||
RSR-497 |
6.3.3.3 CausalityThe METR application information flow is…
|
||
RSR-498 |
6.3.3.4 ConstraintsNo constraints are defined for this outp…
|
||
RSR-127 |
6.3.3.5 Rule management application infoWithin the provisionLatency time after t…
|
derived from:
DSR-169 Rule management application info
|
|
RSR-287 | NOTE: This flow can also include additional in… | ||
RSR-128 |
6.3.4 Information flow: METR coordination |
derives:
RSR-214 Information flow: METR coordination
supported by:
RSR-167 Verification process
generated by:
RSR-167 Verification process
RSR-205 Coordinate with others
|
|
RSR-505 |
6.3.4.1 DefinitionThe METR coordination flow shall be as d…
|
realizes:
SoSR-1055 METR coordination
|
|
RSR-506 |
6.3.4.2 SourceThe METR coordination flow can be initia…
|
||
RSR-507 |
6.3.4.3 CausalityAs needed to investigate and resolve dis…
|
||
RSR-508 |
6.3.4.4 ConstraintsNo constraints are defined for this outp…
|
||
RSR-509 |
6.3.4.5 Resulting actionSending a METR coordination flow can be …
|
||
RSR-129 |
6.3.4.6 Submit rulesUpon direction from the translator agent…
|
||
RSR-130 |
6.3.4.7 Identify issuesThe METR regulation system shall accept …
|
||
RSR-131 |
6.3.4.8 Revise rulesThe METR regulation system shall submit …
|
||
RSR-132 |
6.3.4.9 Explain issuesThe METR regulation system shall provide…
|
||
RSR-416 |
6.3.5 Information flow: METR device status |
||
RSR-500 |
6.3.5.1 DefinitionThe METR device status flow shall be as …
|
realizes:
SoSR-1056 METR device status
|
|
RSR-501 |
6.3.5.2 DestinationThe METR device status flow is sent to t…
|
||
RSR-502 |
6.3.5.3 CausalityThe MRS shall notify the MDS of the stat…
|
||
RSR-503 |
6.3.5.4 ConstraintsNo constraints are defined for this outp…
|
||
RSR-504 |
6.3.5.5 Resulting action |
||
RSR-113 |
6.3.6 Information flow: METR feedback |
generated by:
RSR-167 Verification process
|
|
RSR-408 |
6.3.6.1 DefinitionThe METR feedback flow shall be as defin…
|
realizes:
SoSR-1058 METR feedback
|
|
RSR-410 |
6.3.6.2 Destination |
||
RSR-411 |
6.3.6.3 Causality |
2023-08-16: Kenneth Vaughn
Or in response to successful METR input? |
|
RSR-532 |
6.3.6.3.1 Feedback in Response to InputThe MRS shall send the METR feedback flo…
|
||
RSR-533 |
6.3.6.3.2 Feedback in response to discrepanciesThe MRS shall send the METR feedback flo…
|
||
RSR-412 |
6.3.6.4 ConstraintsThe METR regulation system shall provide…
|
||
RSR-413 |
6.3.6.5 Resulting actionIt is the responsibility of the translat…
|
2023-08-16: Kenneth Vaughn
and/or to submit for approval? |
supported by:
RSR-213 Resolve discrepancy
|
RSR-110 |
6.3.7 Information flow: METR information |
derived from:
DHSR-51 Information flow: METR information
DSR-80 Information flow: METR information
RSR-118 Information flow: METR information
|
|
RSR-510 |
6.3.7.1 DefinitionThe METR information flow shall be as de…
|
realizes:
SoSR-1059 METR information
|
|
RSR-310 |
6.3.7.2 DestinationThe METR regulation system shall provide…
|
||
RSR-311 |
6.3.7.3 CausalityThe METR regulation system shall provide…
|
||
RSR-511 |
6.3.7.4 Constraints |
||
RSR-312 |
6.3.7.4.1 Location constraintsThe METR regulation system shall filter …
|
realizes:
SoSR-471 Location constraint
|
|
RSR-313 |
6.3.7.4.2 Characteristic constraintsThe METR regulation system shall filter …
|
realizes:
SoSR-475 Content constraint
|
|
RSR-314 |
|
||
RSR-315 |
|
||
RSR-316 |
|
||
RSR-317 |
(others as deemed appropriate in req’ts …
|
||
RSR-261 |
6.3.7.4.3 Provisioning latencyWithin the provisioningLatency time afte…
|
realizes:
SoSR-480 Response time
tailored by:
SoSR-391 provisionLatency
|
|
RSR-285 | NOTE: Authorized external systems include dist… | ||
RSR-126 |
6.3.7.4.4 Provide expiration timeThe regulation system shall indicate the…
|
realizes:
SoSR-80 Freshness period
|
|
RSR-241 |
6.3.7.5 Resulting actionNo actions are necessary after sending M…
|
||
RSR-417 |
6.3.8 Information flow: METR information signature request |
||
RSR-420 |
6.3.8.1 DefinitionThe METR information approval request fl…
|
||
RSR-421 |
6.3.8.2 DestinationThe METR information approval request is…
|
||
RSR-512 |
6.3.8.3 CausalityThe METR information approval request is…
|
||
RSR-513 |
6.3.8.4 ConstraintsThere are no constraints defined for thi…
|
||
RSR-514 |
6.3.8.5 Resulting actionThere are no actions required after send…
|
||
RSR-418 |
6.3.9 Information flow: METR management information |
||
RSR-515 |
6.3.9.1 DefinitionThe METR management information flow sha…
|
realizes:
SoSR-1062 METR management information
|
|
RSR-516 |
6.3.9.2 DestinationThe METR management information is sent …
|
||
RSR-517 |
6.3.9.3 CausalityThe METR management information flow is …
|
||
RSR-518 |
6.3.9.4 ConstraintsThere are no constraints for this output
|
||
RSR-175 |
6.3.9.5 FunctionalityWithin the provisionLatency time after t…
|
derived from:
DSR-191 Ad-hoc rule management info
tailored by:
SoSR-391 provisionLatency
|
|
RSR-210 |
6.3.10 Information flow: system-generated discrepancy report |
derives:
RSR-211 Information flow: system-generated discr…
supported by:
RSR-167 Verification process
generated by:
RSR-167 Verification process
realizes:
SoSR-356 electronic discrepancies; and
|
|
RSR-239 |
6.3.10.1 DefinitionThe METR information approval request fl…
|
realizes:
SoSR-1065 system-generated discrepancy report
|
|
RSR-520 |
6.3.10.2 DestinationThe MRS can send the system-generated di…
|
||
RSR-521 |
6.3.10.3 CausalityWhen the MRS detects an issue with incom…
|
||
RSR-522 |
6.3.10.4 ConstraintsThere are no constraints for this output…
|
||
RSR-523 |
6.3.10.5 Resulting actionThe MRS should flag the associated METR …
|
||
RSR-419 |
6.3.11 Information flow: unverified METR information |
||
RSR-525 |
6.3.11.1 DefinitionThe METR information approval request fl…
|
realizes:
SoSR-1245 unverified METR information
|
|
RSR-524 |
6.3.11.2 DestinationThe unverified METR information flow is …
|
||
RSR-197 |
6.3.11.3 CausalityUpon direction from the translator agent…
|
||
RSR-526 |
6.3.11.4 ConstraintsThere are no constraints for this output…
|
||
RSR-527 |
6.3.11.5 Resulting actionThe MRS should maintain a list of METR i…
|
||
RSR-104 |
6.4 Additional requirements |
||
RSR-135 |
6.4.1 Rule provenanceThe METR regulation system shall record …
|
realizes:
SoSR-67 Provenance of information
|
|
RSR-333 |
6.4.2 Information verification |
supports:
RSR-50 Resulting action
|
|
RSR-167 |
6.4.2.1 Verification processThe METR distribution system shall perfo…
|
generates:
RSR-128 Information flow: METR coordination
RSR-113 Information flow: METR feedback
RSR-210 Information flow: system-generated discr…
realizes:
SoSR-62 Verify rule consistency
supports:
RSR-174 Resulting action
RSR-50 Resulting action
RSR-128 Information flow: METR coordination
RSR-210 Information flow: system-generated discr…
RSR-203 Inspect electronic discrepancy
RSR-206 Update information based on confirmed di…
|
|
RSR-168 |
|
||
RSR-169 |
|
||
RSR-170 |
|
realizes:
SoSR-167 Verify locations associated with rules
|
|
RSR-171 |
|
||
RSR-172 |
|
||
RSR-173 |
|
||
RSR-224 | |||
RSR-334 |
6.4.2.2 Performance requirementThe METR regulation system shall make al…
|
realizes:
SoSR-480 Response time
|
|
RSR-213 |
6.4.3 Resolve discrepancy |
summarizes:
RSR-472 Resulting action
supports:
RSR-433 Resulting action
RSR-454 Resulting action
RSR-211 Information flow: system-generated discr…
RSR-413 Resulting action
|
|
RSR-202 |
6.4.3.1 Flag discrepancyUpon receipt of a discrepancy report, th…
|
||
RSR-443 | NOTE: This flag is used to prevent consumer sy… | ||
RSR-203 |
6.4.3.2 Inspect electronic discrepancyFor reported discrepancies between elect…
|
supported by:
RSR-167 Verification process
|
|
RSR-434 |
6.4.3.3 Alert translation agentThe MRS shall alert one or more rule tra…
|
||
RSR-101 |
6.4.3.4 Operator discrepancy interfaceThe METR regulation system shall provide…
|
realizes:
SoSR-356 electronic discrepancies; and
SoSR-355 physical discrepancies;
|
|
RSR-444 | NOTE: This allows translation agents to perfor… | ||
RSR-205 |
6.4.3.5 Coordinate with othersThe MRS shall allow the rule translator …
|
generates:
RSR-212 Information flow: discrepancy report det…
RSR-128 Information flow: METR coordination
|
|
RSR-445 | NOTE: Additional coordination can allow the ru… | ||
RSR-206 |
6.4.3.6 Update information based on confirmed discrepancyThe MRS shall allow the translator agent…
|
supported by:
RSR-167 Verification process
RSR-447 Rule approval
|
|
RSR-446 | NOTE: This requirement is relevant when a repo… | ||
RSR-207 |
6.4.3.7 Update meta-data for a rejected discrepancy reportThe MRS shall allow the rule translator …
|
||
RSR-448 | NOTE: This requirement is relevant when a disc… | ||
RSR-209 |
6.4.3.8 Notify discrepancy logic contacts for rejected reportThe MRS shall allow the rule translator …
|
||
RSR-449 | NOTE: This allows the discrepancy reporter con… | ||
RSR-447 |
6.4.4 Rule approval |
supports:
RSR-206 Update information based on confirmed di…
|
|
RSR-259 |
6.4.5 Ensure structured rulesThe MRS shall require rules to be define…
|
realizes:
SoSR-79 General
|
|
RSR-288 |
6.4.6 Language NeutralityThe MRS shall require all rules to be de…
|
realizes:
SoSR-101 Language neutral
|
|
RSR-268 |
6.4.7 Scope of rules verified against |
||
RSR-269 |
6.4.7.1 Verify against all applicable rulesWithin the rule categories and geographi…
|
||
RSR-270 |
6.4.7.2 Verify against internally-stored rulesThe regulation system shall perform cons…
|
||
RSR-271 |
6.4.7.3 Restrict rule implementation based on local policiesThe MRS shall prohibit the implementatio…
|
||
RSR-181 |
7 Collection requirements |
||
RSR-184 |
7.1 Incoming flow requirements |
||
RSR-185 |
7.2 Outgoing flow requirements |
||
RSR-183 |
7.3 Additional requirementsThere are no additional requirements for…
|
||
RSR-108 |
8 Internal flow descriptions (informative) |
||
RSR-133 |
8.1 Rule entryIt is the responsibility of the translat…
|
realizes:
SoSR-472 proximity from a point location;
SoSR-473 proximity along a route; and
SoSR-474 user-defined area.
SoSR-476 manually reported characteristics (i.e.,…
SoSR-74 METR information availability
SoSR-97 Emergent rule availability
SoSR-64 Maintain rules
|
|
RSR-136 |
8.2 Vocabulary entryIt is the responsibility of the translat…
|
realizes:
SoSR-60 Jurisdictional vocabulary
|
|
RSR-137 |
8.3 Defined area entryIt is the responsibility of the translat…
|
realizes:
SoSR-221 the geographical boundaries of the defin…
SoSR-169 the jurisdictional entity with authority…
SoSR-65 Rule catalogue
|
|
RSR-220 |
8.4 Facility entryIt is the responsibility of the translat…
|
realizes:
SoSR-169 the jurisdictional entity with authority…
|
|
RSR-217 |
8.5 Location entryIt is the responsibility of the translat…
|
realizes:
SoSR-234 Define location accurately
|
|
RSR-218 |
8.6 Discrepancy managementIt is the responsibility of the translat…
|
||
RSR-273 |
8.7 Awareness of rule-makersIt is the responsibility of the translat…
|
Last paragraph needs work