-- :APPLICATION--EXECUTION--ENVIRONMENT_lexForm_3
++ :SYSTEM--UNDER--CONSIDERATION_lexForm_4
++ :ADVANCED--SAFE--TRAIN--POSITIONING_lexConcept_2
-- :APPLICATION--EXECUTION--ENVIRONMENT_lexConcept_2
++ :CENTRAL--PROCESSING--UNIT_lexConcept_2
++ :LAYOUT--ELEMENT--CONTROLLER_lexConcept_3
++ :LAYOUT--ELEMENT--CONTROLLER_lexConcept_4
++ :LAYOUT--ELEMENT--CONTROLLER_lexConcept_5
++ :LAYOUT--ELEMENT--CONTROLLER_lexConcept_6
-- :MANAGEMENT--BY--TRACEABILITY--KANBAN--BASED_lexConcept_3
-- <https://dbpedia.org/page/Arcadia_(engineering)>
-- <https://en.wikipedia.org/wiki/Arcadia_(engineering)>
-- :OPERATIONAL--ENTITY_ACTOR_lexConcept_2
-- :SYSTEM--PILLAR--STEERING--GROUP_lexConcept_2
++ :SYSTEM--UNDER--CONSIDERATION_lexConcept_4
-- <https://dbpedia.org/property/workItem>
-- <https://en.wikipedia.org/wiki/Work_breakdown_structure>
-- <https://polarion.plm.automation.siemens.com/>
-- :THE--SET--OF--ALL--TRACES--TOGETHER--IS--CALLED--A--_MODEL_lexConcept_2
++ :TRAIN--DISPLAY--SYSTEM--CONTROLLER_lexConcept_3
++ :TRAIN--DISPLAY--SYSTEM--CONTROLLER_lexConcept_4
++ :TRAIN--DISPLAY--SYSTEM--CONTROLLER_lexConcept_5
++ "It is a one-dimensional reference frame attached to the vehicle where the ASTP is installed. On the plan of the carriage floor, it is defined by the origin represented by the ASTP reference point (refer to definition D21.1 2.1.1.1.1) and a x axis following the track centreline and oriented toward one end of the vehicle. The end of the vehicle used as the reference for the orientation of the x axis is defined by static configuration (e.g., side A or side B of the vehicle). This reference frame is fixed, it doesn’t change with either the train configuration, or the train movement. This reference frame is defined by static parameters represented by the ASTP reference point location and the orientation of the x axis in the vehicle. This 1D reference frame is used by the ASTP to express along the track centre line, the position, the speed, and the acceleration of the carriage where the ASTP is installed."
-- "1 D reference frame is a one-dimensional reference frame where the bogie position, speed and acceleration along the track centreline axis are expressed. It is defined by the bogie frame. On the plan defined by the carriage floor, the x axis is the tangent of the track centreline oriented toward the train front end, the bogie pin close to the train front end is the tangency point. The bogie pin is located on the longitudinal axis of the carriage."
++ "It is a three-dimensional reference frame attached to the vehicle where the ASTP is installed. It is defined by the carriage frame by a right trihedron. The origin is the ASTP reference point (refer to definition D21.1 2.1.1.1.1). On the plan defined by the carriage floor, the x axis is the carriage longitudinal axis oriented toward one end of the vehicle (same direction as the x axis 1D reference frame), y axis is the orthogonal to the carriage longitudinal axis oriented to the left, z axis the orthogonal to the carriage floor oriented up. This reference frame is fixed, it doesn’t change with either the train configuration, or train movement. The 3D reference frame is used by the ASTP to express the velocity and acceleration of the vehicle where the ASTP is installed."
-- "It is a three-dimensional reference frame where the train speed and acceleration are expressed on the 3 axis component values. It is defined by the carriage frame by a right trihedron. On the plan defined by the carriage floor, the x axis is the carriage longitudinal axis oriented toward the train front end, y axis is the orthogonal to the carriage longitudinal axis oriented to the left, z axis the orthogonal to the carriage floor oriented up, the origin point is the bogie pin close to the train front end."
++ "The Application configuration refers to use case-specific data for the Consuming Systems for a specific application. These can be detailed as SPT2TS-127776 - Infrastructure data i.e., Track edges, Track geometry, Track properties, Segment Profiles, etc. and SPT2TS-127777 - Vehicle data i.e., Braking and Traction efforts, Rolling coefficients, etc."
-- "The Application configuration refers to use case-specific data for the Consuming Systems for a specific application. These can be detailed as SPT2TS-127776 - Infrastructure data i.e., Track edges, Track geometry, Track properties, Segment Profiles, etc. and SPT2TS-127777 - Vehicle data i.e., Max acceleration, Traction efforts, Rolling coefficients, etc."
++ "Arc{comment:3}hitecture Analysis & Design Integrated Approach (ARCADIA) is a system and software architecture engineering method based on architecture-centric and model-driven engineering activities. A short description of the method can be found here. Main resources about ARCADIA can be found on the official website: https://www.eclipse.org/capella/arcadia-reference.html ARCADIA uses four layers to develop and model a system: * Operational Analysis - what the users of the system need to accomplish * System Need Analysis{comment:4} - what the system has to accomplish for the user * Logical Architecture - How the system will work to fulfil expectations * Physical Architecture - How the system will be developed and built (image: 3-1-screenshot-20230107-163323.png) Figure {caption:Figure} Figure Four perspectives of Arcadia [Arcadia web : https://www.eclipse.org/capella/arcadia.html ]"
-- "Arc{comment:3}hitecture Analysis & Design Integrated Approach (ARCADIA) is a system and software architecture engineering method based on architecture-centric and model-driven engineering activities. A short description of the method can be found here. Main resources about ARCADIA can be found on the official website: https://www.eclipse.org/capella/arcadia-reference.html ARCADIA uses four layers to develop and model a system: * Operational Analysis - what the users of the system need to accomplish * System Analysis{comment:4} - what the system has to accomplish for the user * Logical Architecture - How the system will work to fulfil expectations * Physical Architecture - How the system will be developed and built (image: 3-1-screenshot-20230107-163323.png) Figure {caption:Figure} Figure Four perspectives of Arcadia [Arcadia web : https://www.eclipse.org/capella/arcadia.html ]"
++ "The Area Controller manages areas for the View."
-- "Area Controller The Area Controller manages areas for the View."
++ "ATO | Automatic Train Operation AoC | Area of Control | CCS | Control Command and Signaling CI/CD | Continuous Integration / Continuous Deployment CMS | Capacity Management system CPU | Central Processing Unit CTC | Centralized traffic control CVSS | Common Vulnerability Scoring System | DBMS | Database Management System DDOS | Distributed Denial of Service DEV | Development DLP | Data loss prevention DNS | Domain Name System DR | Disaster Recovery-Plan | EDA | Event-driven architecture ELK | Elasticsearch, Logstash, Kibana | FAM | Fixed asset mgmt | HMI | Human Machine Interface HTTP | Hypertext Transfer Protocol | IRM | Information Rights Management | OS | Operating system OR | Operational Requirements | NTMS | Neighborhood TMS | MD5 | Message Digest Method 5 MITM | Man-in-the-middle attack MS | Microservices MVCC | Multi-version concurrency control | PES | Plan Execution System PIS | Passenger Information System POS | Path Order System PROD | Production | QA | Quality Assurance{comment:128} | RAID | Redundant Array of Independent Disks RAM | Random Access Memory RBAS | Role Based Access Control REST | Representational State Transfer RIM | Rail Infrastructure Manager ROC | Rail Operating Company RT | Real Time RU | Rail Undertakings | SAD | System Architecture Description SCI-OP | Standard Communications Interface – Operational Plan SEMP | System Engineering Management Plan SOAP | Simple Object Access Protocol SoC | Separation of Concerns SSL | Secure Sockets Layer | TAF | Telematics Applications for Freight TAP | Telematics Applications for Passenger Services TCR | Temporary Capacity Restrictions TLS | Transport Layer Security TMSTPS | Traffic Management SystemTrain Protection System TSI | Technical Specification for Interoperability | UML | Unified Modeling Language | WAF | Web Application Firewall WSDL | Web Services Description Language | XFN | Cross functional"
-- "ATO | Automatic Train Operation AoC | Area of Control | CCS | Control Command and Signaling CI/CD | Continuous Integration / Continuous Deployment CMS | Capacity Management system CPU | Central Processing Unit CTC | Centralized traffic control CVSS | Common Vulnerability Scoring System | DBMS | Database Management System DDOS | Distributed Denial of Service DEV | Development DLP | Data loss prevention DNS | Domain Name System DR | Disaster Recovery-Plan | EDA | Event-driven architecture ELK | Elasticsearch, Logstash, Kibana | FAM | Fixed asset mgmt | HMI | Human Machine Interface HTTP | Hypertext Transfer Protocol | IRM | Information Rights Management | OS | Operating system OR | Operational Requirements | NTMS | Neighborhood TMS | MD5 | Message Digest Method 5 MITM | Man-in-the-middle attack MS | Microservices MVCC | Multi-version concurrency control | PE | Plan Execution PIS | Passenger Information System POS | Path Order System PROD | Production | QA | Quality Assurance{comment:128} | RAID | Redundant Array of Independent Disks RAM | Random Access Memory RBAS | Role Based Access Control REST | Representational State Transfer RIM | Rail Infrastructure Manager ROC | Rail Operating Company RT | Real Time RU | Rail Undertakings | SAD | System Architecture Description SCI-OP | Standard Communications Interface – Operational Plan SEMP | System Engineering Management Plan SOAP | Simple Object Access Protocol SoC | Separation of Concerns SSL | Secure Sockets Layer | TAF | Telematics Applications for Freight TAP | Telematics Applications for Passenger Services TCR | Temporary Capacity Restrictions TLS | Transport Layer Security TMS | Traffic Management System TSI | Technical Specification for Interoperability | UML | Unified Modeling Language | WAF | Web Application Firewall WSDL | Web Services Description Language | XFN | Cross functional"
++ "The process to verify the identity of communicating peers."
-- "The process to verify the identity of communicating peers. (source: SPPRAMSS-1705 - [UNISIG Subset-146] )"
++ "Availability: property of being accessible and usable on demand by an authorized entity (source: ISO 27000-2018 )"
-- "Availability: property of being accessible and usable on demand by an authorized entity (source: ISO 27000-2018 )"
++ "Sets of specifications or work products at specific points in time that have been formally reviewed and agreed on. Notes: - Pay attention that, in the context of System Pillar (and use of Polarion), several kinds of baselines exist: Polarion Document Baseline, Polarion Project Baseline, Polarion Collection Baseline and System Pillar Release (treated in the Configuration Management Plan ){comment:218} - This definition is a general definition. Another definition exists in glossary imported from the Subset-23. : SPLI-772 - BASELINE {comment:348}"
-- "Baseline{comment:46} Sets of specifications or work products at specific points in time that have been formally reviewed and agreed on. Notes: - Pay attention that, in the context of System Pillar (and use of Polarion), several kinds of baselines exist: Polarion Document Baseline, Polarion Project Baseline, Polarion Collection Baseline and System Pillar Baseline (treated in the Configuration Management Plan ){comment:218} - This definition is a general definition. Another definition exists in glossary imported from the Subset-23. : SPLI-772 - BASELINE"
++ "Device that reads the identity of a person by comparing some attributes of their physiological being or behavioral traits against a sample database. This reader permits the authentication of the actor."
-- "Device that reads the identity of a person by comparing some attribute of their physiological being or behavioral traits against a sample database. This reader permits the authentication of the actor."
-- "Biometric Reader Device that reads the identity of a person by comparing some attribute of their physiological being or behavioral traits against a sample database. This reader permits the authentication of the actor."
++ "A Hard Key allocated to a dedicated system on a cab. It's designed with a dedicated SIL. It allows a selection from two states and keeps one state as long as it is pressed."
-- "A Hard Key allocated to a dedicated system on a cab. It's designed with a dedicated SIL level. It allows a selection from two states and keeps one state as long as it is pressed."
-- "Button A Hard Key allocated to a dedicated system on a cab. It's designed with a dedicated SIL level. It allows a selection from two states and keeps one state as long as it is pressed."
++ "Electrical device that makes a buzzing noise and is used to provide an audible warning."
-- "Buzzer Electrical device that makes a buzzing noise and is used to provide an audible warning."
++ "The Capella2Polarion bridge is used to synchronise Capella model elements with Polarion work items. These work items have the prefix C2P in the name to indicate the specific purpose. More information can be found in here https://github.com/DSD-DBS/capella-polarion."
-- "The Capella2Polarion bridge is used to synchronise Capella model elements with Polarion work items. These work items have the prefix C2P in the name to indicate the specific purpose. More information can be found in here: SPPR-7501 - Capella to Polarion synchronization: list of cloned elements and links."
++ "implicit-from-entry-label: Central Processing Unit"
++ "PROPOSAL what to change where. Shall normally be linked to an Isse."
-- "PROPOSAL what to change where. Shall normally be linked to an Isse. See SPPR-2210 - Manage change request links"
++ "A Compartment{comment:4} is a consistent, integrated entity comprising exactly one Runtime Environment Instance, Safety Environment Task Replicas of at most one Safety Environment, and Functional Application Task Replicas of its respective Functional Applications. It can be deployed on either a Physical or a Virtual Computing Element."
-- "A Compartment is a consistent, integrated entity comprising exactly one Runtime Environment Instance, Safety Environment Task Replicas of at most one Safety Environment, and Functional Application Task Replicas of its respective Functional Applications. It can be deployed on either a Physical or a Virtual Computing Element."
++ "A connection between two components that allows them to convey functional exchange and their exchange items. In the System Pillar component exchange is used as SPPR-2601 - Interface."
-- "A connection between two components that allows them to convey functional exchange and their exchange items."
++ "A{comment:122} content for sketching concepts regarding analysis purposes which is linked to requirements."
-- "A content for sketching concepts regarding analysis purposes which is linked to requirements."
++ "Property that information is not made available or disclosed to unauthorized individuals, entities, or processes (source: ISO 27000-2018 )"
-- "Property that information is not made available or disclosed to unauthorized individuals, entities, or processes (source: ISO 27000-2018 )"
++ "The Controller Unit is a hardware component which embeds logical controller(s). There may be only one Hardware or distributed to several HMI elements."
-- "Controller Unit The Controller Unit is a hardware component which embeds logical controller(s). There may be only one Hardware or distributed to several HMI elements."
++ "Definition: * The Pass Movement Event Constraint define a point in time that must be reached to trigger the DPSGroupState-Request. * The Pass Movement Event Constraint is only calculated, if there is Movement Event of type PASS (Operational Plan Movement) planned between the calculated Pass Position Constraint and the specific DPSGroup. * The Pass Movement Event Constraint replaces the Pass Position Constraint for a specific DPSGroupState-Request."
++ "Desk Area is a location attribute (left, center...) associated to HMI Element for TDS Controller to allocate elements to a View."
-- "Desk Area Desk Area is a location attribute (left, center...) associated to HMI Element for TDS Controller to allocate elements to a View."
++ "The Desk Display Area identifies the desk controlled by TDS (in case of multiple cabins controlled only by one TDS such as locomotive or centralised integration)."
-- "A Zone displaying a piece of visual information of particular system and defined by a size (in cells) and an absolute position (x ,y, z axes). It is more commonly named Area in this specification."
-- "Desk Display Area A Zone displaying a piece of visual information of particular system and defined by a size (in cells) and an absolute position (x ,y, z axes). It is more commonly named Area in this specification."
++ "Inside a cab, the set of operating controls*, which is dedicated to preferred movements in a given direction (i.e. forward movements, in which visibility from the cab is provided to the driver). Exception: some single cab locomotives are fitted with one single desk, allowing normal movements in both directions. *(set of operating controls: screens, buttons, traction/brake lever, direction controller, radio control, switches, …)"
-- "Inside a cab, the set of operating controls*, which is dedicated to preferred movements in a given direction (i.e. forward movements, in which visibility from the cab is provided to the driver). Exception: some single cab locomotives are fitted with one single desk, allowing normal movements in both directions. *set of operating controls: screens, buttons, traction/brake lever, direction controller, radio control, switches, …Desk"
-- "Desk Inside a cab, the set of operating controls*, which is dedicated to preferred movements in a given direction (i.e. forward movements, in which visibility from the cab is provided to the driver). Exception: some single cab locomotives are fitted with one single desk, allowing normal movements in both directions. *set of operating controls: screens, buttons, traction/brake lever, direction controller, radio control, switches, …Desk"
++ "Diagnostics is the assessment{comment:1} of health and performance of an asset or a group of assets. Furthermore, the diagnostic system also provides all information of single components in the field like: software version, parametrisation file version, firmware version, hardware version, manufacturer part number, manufacturer serial number,{comment:35} ID in the field (e.g. NID_ENGINE), cumulated hours in operation, IP address, etc. All this data is being used for analysis purposes."
-- "Diagnostics{comment:95} : Diagnostics is the assessment{comment:1} of health and performance of an asset or a group of assets. Furthermore, the diagnostic system also provides all information of single components in the field like: software version, parametrisation file version, firmware version, hardware version, manufacturer part number, manufacturer serial number,{comment:35} ID in the field (e.g. NID_ENGINE), cumulated hours in operation, IP address, etc. All this data is being used for analysis purposes."
++ "Glass (LCD) showing pixels without controller."
-- "Display Panel Glass (LCD) showing pixels without controller."
++ "The Engineering Data (aka Configuration Input Data) is created based on the SPT2TS-125758 - Engineering Input Data but generic (IM-unspecific). Typically, the data are not adapted to cope with specific views demanded by different Consuming Systems. The Engineering Data contains all the base data (i.e., track topology and topography) for deriving the Configuration Data during the compilation process. Besides providing base data for the Configuration Data generation, the Engineering Data shall also cover the needs for the configuration of Consuming Systems (e.g., Parameter Data). The Engineering Data must fulfil engineering rules that are influenced by the requirements of the Configuration Data for the Consuming Systems. The Engineering Data contains only the updated resulting data (i.e., not several variants/versions of the same track) that is needed for the next compiling and provisioning of Configuration Data and operation at a certain point in time in the Consuming Systems."
-- "The Engineering Data aka Configuration Input Data is created based on the SPT2TS-125758 - Engineering Input Data but generic (IM-unspecific). Typically, the data are not adapted to cope with specific views demanded by different Consuming Systems. The Engineering Data contains all the base data (i.e., track topology and topography) for deriving the Configuration Data during the compile process. Besides providing base data for the Configuration Data generation, the Engineering Data shall also cover the needs for the configuration of Consuming Systems (e.g., Parameter Data). The Engineering Data must fulfill engineering rules that are influenced by requirements of the Configuration Data for the Consuming Systems. The Engineering Data contains only the updated resulting data (i.e., not several variants/versions of the same track) that is needed for the next compiling and provisioning of Configuration Data and operation at a certain point in time in the Consuming Systems."
++ "The Engineering Data as part of the SPT2TS-2040 - CCS/TMS Extended ERA Ontology (CCS/TMS Data Model) contains all the base data (i.e.,{comment:19} track topology, track geometry, track asset configuration) for compiling the next version(s) of use case-specific Domain Data. The standardized Engineering Data comprehensively covers the data needs for the SERA in the scope of the System Pillar (i.e. radio-based ETCS only). Specific data needed for migration is out of the scope of SPT2TS-2040 - CCS/TMS Extended ERA Ontology (CCS/TMS Data Model)."
-- "The Engineering Data as part of the SPT2TS-2040 - CCS/TMS Data Model contains all the base data (i.e.,{comment:19} track topology, track geometry, track asset configuration) for compiling the next version(s) of use case-specific Domain Data. The standardized Engineering Data comprehensively covers the data needs for the SERA in the scope of the System Pillar (i.e. radio-based ETCS only). Specific data needed for migration is out of the scope of SPT2TS-2040 - CCS/TMS Data Model."
++ "Refers to data from Infrastructure Manager (IM) specific digital sources required for engineering, such as: * Track layout (nominal geometry of the respective construction phase * Track Assets (points, signals, train detection elements, etc.) * Properties (speeds, gradients, etc.) * Structures (platform, tunnel, etc.) * Logical data such as trackside train detection sections (if still available) * Acquisition Data * Configuration Data for track objects * Others (placeholder to include other possible data from IM)"
-- "Refers to data from Infrastructure Manager (IM) specific digital sources required for engineering, such as: * Track layout (nominal geometry of the respective construction phase * Track Assets (points, signals, train detection elements, etc.) * Properties (speeds, gradients, etc.) * Structures (platform, tunnel, etc.) * Logical data such as trackside train detection sections (if still available) * Acquisition Data * Configuration Data for track objects * Others (placeholder to include other possible data from IM)"
++ "A collection of enterprise security interface (ESI) implementations of central security and IT communication functions in a back-office environment. Examples are Security Incident and Event Management System (SIEM), Intrusion Detection System, PKI Certificate Authority, Corporate Directory, Asset Management, DNS. These services are typically accessible for the automation network via controlled communication paths (e.g. DMZ). The interfaces of the Shared Cybersecurity Services to the Enterprise Services are identified by ESI-<Service name>. Note: Enterprise Shared Services are typically 3rd-party components not dedicated to the rail environment. Therefore the realization of the Enterprise Shared Services may use other security requirements than the Secure Component Specification. Recommended security specification are ISO 27033, ISO 27034, NIST 800-53, and/or IEC 62443-4-2. Note: Enterprise Shared Services and Shared Cybersecurity Services are separated by the IT/OT border (e.g. by a DMZ)."
-- "A collection of enterprise security interface (ESI) implementations of central security and IT communication functions in a back-office environment. Examples are Security Incident and Event Management System (SIEM), Intrusion Detection System, PKI Certificate Authority, Corporate Directory, Asset Management, DNS. These services are typically accessible for the automation network via controlled communication paths (e.g. DMZ). The interfaces of the Shared Cybersecurity Services to the Enterprise Services are identified by ESI-<Service name>. Note: Enterprise Shared Services are typically 3rd-party components not dedicated to the rail environment. Therefore the realization of the Enterprise Shared Services may use other security requirements than the Secure Component Specification. Recommended security specification are ISO 27033, ISO 27034, NIST 800-53, and/or IEC 62443-4-2. Note: Enterprise Shared Services and Shared Cybersecurity Services are separated by the IT/OT border (e.g. by a DMZ)."
-- "function or capability that is required to maintain health, safety, the environment and availability for the equipment under control Note 1 to the entry: Essential functions include, but are not limited to, the safety instrumented function (SIF), the control function and the ability of the operator to view and manipulate the equipment under control. The loss of essential functions is commonly termed loss of protection, loss of control and loss of view respectively. In some industries additional functions such as history may be considered essential. IEC 63452 definition: all functions needed to operate the railway system, such as per example traffic control, speed control, traction/breake control,..."
++ "function or capability that is required to maintain health, safety, the environment and availability for the equipment under control Note 1 to the entry: Essential functions include, but are not limited to, the safety instrumented function (SIF), the control function and the ability of the operator to view and manipulate the equipment under control. The loss of essential functions is commonly termed loss of protection, loss of control and loss of view respectively. In some industries additional functions such as history may be considered essential. IEC 63452 definition: all functions needed to operate the railway system, such as per example traffic control, speed control, traction/breake control,..."
-- "function or capability that is required to maintain health, safety, the environment and availability for the equipment under control Note 1 to the entry: Essential functions include, but are not limited to, the safety instrumented function (SIF), the control function and the ability of the operator to view and manipulate the equipment under control. The loss of essential functions is commonly termed loss of protection, loss of control and loss of view respectively. In some industries additional functions such as history may be considered essential."
++ "View displayed on more than one Display Panel."
-- "Extended View View displayed on more than one Display Panel."
++ "A button which is not directly managed by TDS."
-- "External Button A button which is not directly managed by TDS."
++ "A Fixed Virtual Block is a Fixed Block where the limits are virtual and do not necessarily correspond to train detection boundaries."
-- "A Fixed Virtual Block is a Fixed Block where the extremities are virtual and do not necessarily correspond to train detection boundaries."
++ "Functional apportionment is the clear assignment of functions to subsystems. It is an architectural choice supporting the ability to replace a subsystem of supplier A by a subsystem of supplier B both compliant with a given FIS."
-- "Functional apportionment is the clear assignment of functions to sub-systems. It is an architectural choice supporting the ability to replace a sub-system of supplier A by a subsystem of supplier B both compliant with a given FIS."
++ "Is an ordered set of references to functions and the SPPR-2047 - Functional Exchange that link them, describing one possible path among all the paths forming the data-flow. Functional chains are used to describe the system behaviour in a particular usage context, to contribute to one or more SPPR-2583 - System Capability.{comment:95} Each reference to a function or exchange inside the chain can be qualified by an expectation in the context of the chain (the value that an exchange item or a function attribute should take, for example). Furthermore: A functional chain also specifies constraints or expectations of precedence or anteriority via oriented sequence links. A set of functions and sequence links is a sequence. Control nodes can be defined between the sequence links, to express the parallelism or alternative between several sequences of functions, or, also the iteration or condition of a sequence to be realised. ARCADIA talks only about a functional chain from system level onwards, in operational analysis, it is still called operational process, the methodology is the same for both, therefore no further distinction is made."
-- "Is an ordered set of references to functions and the functional exchanges that link them, describing one possible path among all the paths forming the data-flow. Functional chains are used to describe the system behaviour in a particular usage context, to contribute to one or more capabilities. Each reference to a function or exchange inside the chain can be qualified by an expectation in the context of the chain (the value that an exchange item or a function attribute should take, for example). Furthermore: A functional chain also specifies constraints or expectations of precedence or anteriority via oriented sequence links. A set of functions and sequence links is a sequence. Control nodes can be defined between the sequence links, to express the parallelism or alternative between several sequences of functions, or, also the iteration or condition of a sequence to be realised. ARCADIA talks only about a functional chain from system level onwards, in operational analysis, it is still called operational process, the methodology is the same for both, therefore no further distinction is made."
++ "A SPPR-3791 - System Requirement which specifies a function that a system has to do."
-- "A requirement which specifies a function that a system has to do."
++ "Physical key not part of view. This key can also have a text label or symbol."
-- "Hard Key Physical key not part of view. This key can also have a text label or symbol."
++ "An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key..."
-- "HMI Element An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key..."
++ "Infrastructure Data is a detailed digital representation of the railway network that contains all infrastructure related information necessary for planning and performing railway operations, such as infrastructure characteristics, location and details of Field Elements, etc. The Infrastructure Data is static and remains unchanged until intended infrastructure updates occur."
-- "Infrastructure Data is a detailed digital representation of the railway network that contains all infrastructure related {comment:3}information necessary for planning and performing railway operations, such as infrastructure characteristics, location and details of Field Elements, etc. The Infrastructure Data is static and remains unchanged until relevant infrastructure updates occur."
++ "Infrastructure Manager{comment:161}"
++ "Integrity: property of accuracy and completeness (source: ISO 27000-2018 )"
-- "Integrity: property of accuracy and completeness (source: ISO 27000-2018 )"
-- "Interlocking is a set of signaling devices which physically materializes, in the area of action of a switch post (junction, crossing of tracks, etc.) throught mechanical, and / or electrical solutions . It allows train movement if the safety conditions have been met regarding train maneuver and signal control devices. (double. needs to be deleted)"
++ "Interlocking is a set of signaling devices which physically materializes, in the area of action of a switch post (junction, crossing of tracks, etc.) throught mechanical, and / or electrical solutions . It allows train movement if the safety conditions have been met regarding train maneuver and signal control devices. (double. needs to be deleted)"
-- "Interlocking is a set of signaling devices which physically materializes, in the area of action of a switch post (junction, crossing of tracks, etc.) throught mechanical, and / or electrical solutions . It allows train movement if the safety conditions have been met regarding train maneuver and signal control devices."
++ "The Internal Button is a button which is managed directly by TDS."
-- "Internal Button The Internal Button is a button which is managed directly by TDS."
++ "Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches."
-- "Key Controller Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches."
++ "Hard Key located close to a Display Area allowing soft key technology."
-- "Lateral Key Hard Key located close to a Display Area allowing soft key technology."
++ "The Layout Controller manages the Layout for an Area."
-- "Layout Controller The Layout Controller manages the Layout for an Area."
++ "The Layout Element Controller manages Layout Elements of a Layout. It knows how to present itself and how to react on events."
-- "Layout Element Controller The Layout Element Controller managesLayout Elements of a Layout. It knows how to present itself and how to react on events."
++ "The Layout Engine is an application and supplier specific piece of software, able to generate any View based on application specific needs."
-- "The Layout Engine is a generic piece of software able to generate any View based on Areas, Layouts and Layout Elements as defined in a configuration."
-- "Layout Engine The Layout Engine is a generic piece of software able to generate any View based on Areas, Layouts and Layout Elements as defined in a configuration."
**++ "Layout is a list of Layout Elements which is displayed in an area."
**-- "Layout is a list of layout elements which is displayed in an area."
++ "Layout is a list of Layout Elements which is displayed in an area."
-- "Layout Layout is a list of layout elements which is displayed in an area."
++ "Device that converts an electrical audio signal into a corresponding sound."
-- "Loudspeaker Device that converts an electrical audio signal into a corresponding sound."
++ "The Microphone Controller manages states and signals of Microphone."
-- "Microphone Controller The Microphone Controller manages states and signals of Microphone."
++ "Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker."
-- "Microphone Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker."
++ "Movement Permissions (MPs) are stored within the trackside safety system. A Movement Permission is an extent of track reserved within the trackside safety system for a particular Train Object to move. A Movement Permission includes all conditions under which the movement of the Train Object can be performed safely. A Movement Permission always refers to exactly one Train Object. A Movement Permission is distinct from a Movement Authority, which is sent from the trackside safety system to the ETCS On-Board."
-- "A Movement Permission (MP) is an authorisation for a particular Train Object to move. A Movement Permission includes all conditions under which the movement of the Train Object can be performed safely. A Movement Permission always refers to exactly one Train Object."
++ "Moving block is a concept where Movement Authorities can end at any location on the track. The Safe Train Extent of each train moves with that train based on its reported position and train integrity status and is not constrained to fixed block locations."
-- "Moving block is a concept where Movement Authorities can end at any location on the track. The Safe Train Extent of each train moves with that train based on its reported position and confirmed train integrity status and is not constrained to fixed block locations. Moving Block can be based on Absolute Braking Distance or Relative Braking Distance."
++ "Non-Repudiation: ability to prove the occurrence of a claimed event or action and its originating entities (source: ISO 27000-2018 )"
-- "Non-Repudiation: ability to prove the occurrence of a claimed event or action and its originating entities (source: ISO 27000-2018 )"
++ "On operational activity is one step in an operational process, that has inputs and outputs. The activity describes what and how the operational entity the operational activity is allocated to is doing."
-- "On operational activity is one step in an operational process, that has one or more inputs, and one or more outputs. The activity describes what and how the operational entity the operational activity is allocated to is doing."
-- "A problematic situation that can occure with a process design."
++ "The Operational Plan is the result of the planning process performed by TMS. An Operational Plan will be issued by the TMS for any operationally relevant activity. This comprises all movements of Physical Train Units{comment:86} incl. shunting operations (Operational Movement), restrictions due to e.g., infrastructure maintenance and construction works, and warning measures during restrictions."
-- "The Operational Plan is the result of the planning process performed by TMS. An Operational Plan will be issued by the TMS for any operationally relevant activity. This comprises all movements of Physical Train Units incl. shunting operations (Operational Movement), restrictions due to e.g., infrastructure maintenance and construction works, and warning measures during restrictions."
++ "Is defined by SPPR-2066 - Exchange scenario."
++ "Parameter Data define the system configuration data required for national and supplier-specific operative environments. A notable example of such data are ETCS national values. ETCS national values may be required for migration purposes and shall be replaced by SERA standardised values in the target system.{comment:34}"
-- "Parameter Data define the system configuration data required for national and supplier-specific operative environments. A notable example for such data are ETCS national values."
++ "Means of communication/transport relating to the hosting of physical components, used as a medium by exchanges between behavioural components."
-- "means of communication/transport relating to the hosting of physical components, used as a medium by exchanges between behavioural components"
**++ "Railway requirements are epics, visions, needs or user stories coming from stakeholders as their concrete vision (who, what, why). It can be formulated in a few sentences and has not a strict form criteria. These can be translated to precise operational requirements during analysis processes in case they describe operational epics for the business target picture of an operational area (like CCS or energy). The can be freely formulated but should follow the writing patterns of epics and user stories. They should be specific enough to be assigned to exactly one System Pillar task."
**-- "Railway requirements are epics, visions, needs or user stories coming from stakeholders as their concrete vision (who, what, why). It can be formulated in a few sentences and has not a strict form criteria. These can be translated to precise operational requirements during analysis processes in case they describe operational epics for the business target picture of an operational area (like CCS or Energy). The can be freely formulated but should follow the writing patterns of epics and user stories. They should be specific enough to be assigned to exactly one System Pillar task."
++ "The Reader Controller manages states and failures of the Biometric Reader and/or the RFID Reader."
-- "The Reader Controller manages states and failures of the Biometric Readerand/or the RFID Reader."
-- "Reader Controller The Reader Controller manages states and failures of the Biometric Readerand/or the RFID Reader."
++ "Radio Frequency Identification (RFID) refers to a wireless system comprised of two components: tags and readers. The reader is a device that has one or more antennas that emit radio waves and receive signals back from the RFID tag. This reader permits the authentication of the actor."
-- "RFID Reader Radio Frequency Identification (RFID) refers to a wireless system comprised of two components: tags and readers. The reader is a device that has one or more antennas that emit radio waves and receive signals back from the RFID tag. This reader permits the authentication of the actor."
-- "An implementation, as part of an industrial automation control system, which comprises system components, such as host devices, embedded devices, network devices or software applications on a host device, that implement security capabilities and consisting of a physical encasing, computing capabilities and network communication, and interfacing to the Shared Cybersecurity Services. Examples of CCS secure components are object controller, trackside cabinet, IXL rack, ATO-OB, OBU, ATO-TS, IXL/RBC combination, shared cybersecurity services, security proxy for legacy devices, …) Examples of components which are not meeting the definition of a Secure Component are components with no network communication, e.g. directly connected sensors or displays."
++ "A Segment Profile is a one-dimensional object that describes a single and consecutive section of track and corresponds to the Track Centreline of that section of track. A Segment Profile has a Start Point and an End Point, which correspond to the boundary points of the section of Track Centreline of that Segment Profile. A Segment Profile defines a set of static infrastructure data required by different on-board applications like ATO, Perception, Localisation, APM. The Segment Profile is part of Application Configuration Data. These data are derived from Infrastructure Data according to the interface data structure requirements of the consumers."
-- "A Segment Profile is a one-dimensional object that describes a single and consecutive section of track and corresponds to the Track Centreline of that section of track. A Segment Profile has a Start Point and an End Point, which correspond to the boundary points of the section of Track Centreline of that Segment Profile. A Segment Profile defines a set of static infrastructure data required by different on-board applications like ATO, Perception, Localisation, APM. {comment:2} The Segment Profile is part of Application Configuration Data. These data are derived from Infrastructure Data according to the interface data structure requirements of the consumers."
++ "Shared Security Service {comment:7}"
++ "Context-dependent key which consists of a Hard Key with an associated label on the Display Area. When using a soft key technology, the driver action is done via the Hard Key adjacent to the label."
-- "Soft Key Context-dependent key which consists of a Hard Key with an associated label on the Display Area. When using a soft key technology, the driver action is done via the Hard Key adjacent to the label."
++ "The Software Configuration data refers to executable binary files from suppliers which are usually required to install software on the systems. Software Configuration Data is provided via configuration interface to the CCS/TMS Systems.{comment:73}"
-- "The Software Configuration data refers to executable binary files from supplies which are usually required to install software on the systems."
++ "Stakeholder requirements are precise requirements of stakeholders for the system of interest. They are derived from railway requirements and the operational analysis."
-- "Stakeholder{comment:42} requirements are precise requirements that are derived from railway requirements and the operational analysis.{comment:23}"
++ "TODO: Add definition for standard interfaces"
-- "Add definition for standard interfaces"
**++ "Collection of states connected by transitions."
**-- "collection of states connected by transitions"
++ "A change of state toward itself or toward another state. A transition is characterised by a trigger which can be an event or a boolean condition."
-- "A change of state toward itself or toward another state. A transition is characterised by a trigger which can be a boolean condition applied on certain model elements, such as functional exchanges."
++ "Subsystems are along systems with standard interfaces on System Level 5. Not to be confused with subsystems in the TSI / interoperability directive. A subsystem is a part of a system, which is not refined any further during the specification task(The term subsystem is used in this document following the referenced architecting standards, it does not correspond to the subsystem definition as in the Interoperability Directive.). It represents a leaf element in the hierarchy of systems-of-systems. A subsystem is defined by the following characteristics: * For each subsystem exists a set of specification documents, that allows a supplier to build that subsystem, ideally without the need for further documentation. * The level of strictness of the specification can be variable: * Interoperable specification: Strict standardisation of all interface aspects that are needed for to systems to fulfil a defined set of operational capabilities together on runtime. * Interchangeable specification: Standardisation of all interface aspects that are needed to exchange one of the systems with the lowest reasonable integration effort. * Core standardisation specification: An interoperable standardisation that defines a guaranteed minimum of interoperability, but allows and gives room for specific and perhaps incompatible extensions that are only used, when all involved systems have them. * Guideline: A recommended specification that can be used as a whole, or can be used partly or changed. * A subsystem can be implemented as software only, as hardware only, as a mixture of both depending on the strictness of the specification (the specification can leave that aspect open). * Each subsystem can be individually tendered to a supplier * Each subsystem can be built individually by a supplier * Each subsystem must be integrated into a system, which includes all necessary test, verification, certification and validation activities."
-- "Subsystems are along ARCADIA systems with standard interfaces on System Level 5. Not to be confused with subsystems in the TSI / interoperability directive. A subsystem is a part of a system, which is not refined any further during the specification task(The term subsystem is used in this document following the referenced architecting standards, it does not correspond to the subsystem definition as in the Interoperability Directive.). It represents a leaf element in the hierarchy of systems-of-systems. A subsystem is defined by the following characteristics: * For each subsystem exists a set of specification documents, that allows a supplier to build that subsystem, ideally without the need for further documentation. * The level of strictness of the specification can be variable: * Interoperable specification: Strict standardisation of all interface aspects that are needed for to systems to fulfil a defined set of operational capabilities together on runtime. * Interchangeable specification: Standardisation of all interface aspects that are needed to exchange one of the systems with the lowest reasonable integration effort. * Core standardisation specification: An interoperable standardisation that defines a guaranteed minimum of interoperability, but allows and gives room for specific and perhaps incompatible extensions that are only used, when all involved systems have them. * Guideline: A recommended specification that can be used as a whole, or can be used partly or changed. * A subsystem can be implemented as software only, as hardware only, as a mixture of both depending on the strictness of the specification (the specification can leave that aspect open). * Each subsystem can be individually tendered to a supplier * Each subsystem can be built individually by a supplier * Each subsystem must be integrated into a system, which includes all necessary test, verification, certification and validation activities. Some non-functional requirements (e.g. weight constraints or physical dimension constraints) will be allocated to subsystems."
-- "The company or organization providing a component, product or system."
**++ "IACSs are typically composed of products and services integrated and tested to work together. Each of these products and services is provided to the asset owner by an organization (which may include the asset owner) that is generally referred to as a supplier. Each supplier often has suppliers of its own, and each of these second level suppliers may have suppliers of its own. This cascading of suppliers is referred to as the supply chain. (from IEC 62443-2-1, Org 1.6)."
**-- "IACSs are typically composed of products and services integrated and tested to work together. Each of these products and services is provided to the asset owner by an organization (which may include the asset owner) that is generally referred to as a supplier. Each supplier often has suppliers of its own, and each of these second level suppliers may have suppliers of its own. This cascading of suppliers is referred to as the supply chain. (from IEC 62443-2-1, Org 1.6)"
++ "Physical component which allows a selection of 2 to N states and keeps the state until its position is changed."
-- "Switch Physical component which allows a selection of 2 to N states and keeps the state until its position is changed."
-- "Electrical switch. Closes or opens a circuit."
++ "Describes the high-level behaviour of a system and its interaction with other involved entities, resulting in a specific, observable outcome. This capability signifies the system's expected ability in delivering services that represents an operational objective. Essentially, a system capability defines a context for system usage, characterised by a set of exchanges scenarios that outline the conditions under which system functions contribute to achieving the objective. Traditional approaches like the ARCADIA method describe system capabilities from the system's perspective. However, we've opted to deviate from this method, focusing on an actor's perspective similar to use cases to suit our needs better. This deviation aims to create a stronger distinction between capability and function and ensure compatibility with SysML. The actor-oriented approach allows the capability to be documented from the perspective of those interacting with the system, enhancing clarity in defining system objectives and functionality. For example, rather than solely focusing on the system's technical aspects, we assess how the system's capabilities meet the needs and objectives of the users or external entities, ensuring comprehensive alignment with stakeholder goals."
-- "Description of a high-level behaviour of a system and its interaction with other involved entities, which yields an observable outcome. The system capability is the system’s expected ability to provide a high-level service allowing it to carry out an operational objective. A system capability represents a system usage context. It is characterised by a set of functional chains and scenarios that it references, and which more precisely describes the conditions for performing the system functions that contribute to it. A capability can also reference a function that contributes to it by itself. A capability can use one or more other capabilities that it will reference. Although the ARCADIA method describes system capabilities from the system perspective. We have decided that a deviation from the established method is preferred for our purposes. So the system capabilities shall be written from an actor's perspective, similar to use cases. In order to have a greater distinction between capability and function and to be compatible with SysML."
++ "The System Configuration data refers to the static data set required to configure systems with primary information before being put into operation. These data are elaborated as SPT2TS-127829 - Parameter Data"
-- "The System Configuration data refers to static data set required to configure systems with primary information before being put into operation. These data are elaborated as SPT2TS-127829 - Parameter Data"
++ "The main output documents of the System Pillar are described in Systems Engineering Management Plan - Annex L List of System Pillar Deliverables.{comment:68}"
-- "The main output documents of the System Pillar are described in List of System Pillar deliverables.{comment:68}"
-- "System Pillar Steering Group monitoring the progress of the System Pillar"
++ "System requirements are precise functional or non-functional requirements for the system of interest that are derived from system analysis or system architecture. They are recursively used on system level and subsystem level, where a subsystem is specified as system.{comment:108}"
-- "System requirements are precise functional or non-functional requirements that are derived from system analysis or system architecture. They are recursively used on system level and subsystem level, where a subsystem is specified as system."
-- "The defined scope of components and its interrelation the security analysis and security specifications are made for. The system under consideration is defined in Security Architecture. The red rectangle displays the scope. These are the components in the system under consideration (SuC)."
++ "The defined scope of components and its interrelation the security analysis and security specifications are made for. The system under consideration is defined in Security Architecture. The red rectangle displays the scope. These are the components in the system under consideration (SuC)."
-- "System under Consideration (from SPPRAMSS-334 - [EN 50129:2018/AC:2019-04])"
++ "System under Consideration (from SPPRAMSS-334 - [EN 50129:2018/AC:2019-04])"
-- "System under Consideration [SOURCE: SPPRAMSS-4697 - [EN IEC 62443-3-2:2020]]"
++ "Arrangement of system elements, that together exhibit a stated behaviour or meaning that the individual constituents do not. According to ISO 15288 a system is “a combination of interacting elements organised to achieve one or more stated purposes. “. In terms of this document, a system in black box view is furthermore defined by: * interfaces to actors outside the system, defining the system boundary * at least one function allocated to it A system in white box view can be further refined into (exclusive or): * into a more granular systems, hence making itself to a system of systems * into subsystems on the lowest level of system of systems refinement In both cases, a system is a conceptual entity that aggregates the properties of its constituents but is not the element that defines the properties itself. A system is hence subject to the emerging properties of its constituents. Usage context definitions of term „system“: * Constituent system: according to ISO 21839, a system that forms part of a system of systems * System of interest: according to ISO 21839, a system whose life cycle or properties are under consideration in a given context"
-- "Arrangement of system elements, that together exhibit a stated behaviour or meaning that the individual constituents do not. According to ISO 15288 a system is “a combination of interacting elements organised to achieve one or more stated purposes. “. In terms of this document, a system in black box view is furthermore defined by: * interfaces to actors outside the system, defining the system boundary * at least one function allocated to it * at least one capability that the system delivers as a service to the actors A system in white box view can be further refined into (exclusive or): * into a more granular systems, hence making itself to a system of systems * into subsystems on the lowest level of system of systems refinement In both cases, a system is a conceptual entity that aggregates the properties of its constituents but is not the element that defines the properties itself. A system is hence subject to the emerging properties of its constituents. Usage context definitions of term „system“: * Constituent system: according to ISO 21839, a system that forms part of a system of systems * System of interest: according to ISO 21839, a system whose life cycle or properties are under consideration in a given context"
++ "Set of test inputs, conditions, and expected results developed to verify compliance with a specific system requirement."
++ "Threat landscape is used in this document as synonym for threat environment. Threat environment (definition from CENELEC TS 50701, IEC PT 63452) environment summary of information about threats, such as threat sources, threat vectors and trends, that have the potential to adversely impact a defined target (for example a company, facility or SuC)"
-- "Threat landscape is used in this document as synonym for threat environment. Threat environment (definition from CENELEC TS 50701, IEC PT 63452) environment summary of information about threats, such as threat sources, threat vectors and trends, that have the potential to adversely impact a defined target (for example a company, facility or SuC)"
++ "Controller which manages the states and failures of a Touch Panel."
-- "Touch Controller Controller which manages the states and failures of a Touch Panel."
**++ "Trackside Assets are elements on or near the track which are used to monitor (using sensors) and/or control (using actuators) the movement of vehicles through the railway network to provide a safe route through the railway network. They can be switchable or non-switchable and are controlled by the actors Trackside Asset Control and Supervision."
**-- "Trackside Assets are elements on or near the track which are used to monitor (using sensors) and/or control (using actuators) the movement of vehicles through the railway network. to provide a safe route through the railway network. They can be switchable or non-switchable and are controlled by the actors Trackside Asset Control and Supervision."
++ "Trackside Train Detection is a system which determines the occupancy status of TTD sections. TTD section may be a Track Circuit or an Axle Counting system section. EULYNX synonym for TTD section: Track Vacancy Proving Section (TVPS)"
-- "The proof of the presence or absence of trains on a defined section of line"
++ "TDS Controller is the same as the Display Manager in the new architecture of MDS."
-- "The TDS Controller interacts with system (CCS, TCMS,CVR) and manages the Desk Display Area."
++ "The TDS Controller interacts with systems (CCS, TCMS,CVR...) and manages the Desk Display Area."
-- "Train Display System Controller The TDS Controller interacts with system (CCS, TCMS,CVR) and manages the Desk Display Area."
++ "The Train Display System is the train cab display system that comprises and manages one or more displays on the driver desk and a driver interface. It is composed of at least one display with the associated input devices, at least one loudspeaker and at least one Display Manager. It offers a standardised communication interface to systems that need driver interaction."
-- "The Train Display System is the train cab display system that comprises and manages one or more displays on the driver desk and a driver interface. It is composed of at least one display with the associated input devices, at least one loudspeaker and at least one Train Display System Controller. It offers a standardised communication interface to systems that need driver interaction."
++ "Train Object is the object needed by the ETPS to manage the Communication with an ETCS Equipped train.{comment:84}{comment:85}"
-- "Train Object is the object needed by the Traffic CS to manage the connected trains currently performing their mission. Note: This Train Object could nevertheless correspond to a train not (yet) localised by MBS. If a Train Object is referenced as a geometric extent, the extent is the Safe Train Extent."
++ "A number under which the train is operated."
-- "A number under which the train is operated. Reference: Glossary of Terms and Abbreviation. SUBSET-023. Issue 4.0.0"
++ "Train Splitting is an operational procedure that involves the process of separating a train into two or more consists,{comment:90} possible anywhere on the network and normally based on the operational plan{comment:21}{comment:37} as planned splitting. Specific procedures of the Railway Undertaking describe (vehicles specific, e.g., closing of flaps, protection covering against snow){comment:31} details to perform the splitting. Unplanned splitting needs the communication with the signaller.{comment:57}"
-- "Train Splitting is the physically separation of one train into two or more trains possible anywhere on the network{comment:51} and normally based on the timetable as planned splitting.{comment:5}{comment:52} Specific procedures of the Railway Undertaking describe (train specifc) details to perform the splitting. Unplanned splitting needs the communication with the signaller."
++ "Unresolved Trackbound Object is the object needed by ETPS to manage occupancies of track areas where track vacancy is not proven and that cannot be associated to a Train Object{comment:83}"
-- "Unresolved Trackbound Object is the object needed by the Traffic CS to manage a contiguous track area where track vacancy is not proven and cannot be linked to any connected train (Train Object). RCA source: uMOB X2R5 source: Unknown Track Status Area (partly)"
++ "Vehicle Data is a detailed definition of the static train/vehicle characteristics i.e., Braking and Traction efforts, rolling coefficients, of the train, wagons, locomotives used for railway operations.{comment:35}"
-- "Vehicle Data is a detailed definition of the train/vehicle {comment:4}characteristics i.e., max acceleration, Traction efforts, rolling coefficients, of the train, wagons, locomotives used for railway operations."
++ "The View Controller aggregates the View, the output devices and the controller of each input device."
-- "View Controller The View Controller aggregates the View, the output devices and the controller of each input device."
++ "Aggregation of Areas required for systems (CCS, TCMS, CVR...). A View can represent Areas of different systems at the same time."
-- "View Aggregation of Areas required for systems (CCS, TCMS, CVR...). A View can represent Areas of different systems at the same time."
-- "A view is a filter that restricts the set of data types to a subset that is of interest in the context of a use case. Filtering is by discipline and spatially."