Table of Contents | ||
---|---|---|
|
...
Info |
---|
Relationship of Domain, Attributes, Elements and Sub-ElementsTo understand the Relationship of Domain, Attributes, Elements and Sub-Elements, see: https://orthogramic.atlassian.net/wiki/spaces/OUG/pages/55246856/Business+Architecture+Domain+Attributes+Elements#The-relationships-between-Business-Architecture-Domains%2C-Attributes%2C-Elements-and-Sub-Elements |
Stakeholder attributes
Domain | Attribute | Description | Example |
stakeholders | Title | The name or title of the |
Customers
Stakeholder | Class I Railroad Operations | |
stakeholders | Type | The |
Stakeholders position in relation to the |
Internal, External, Ministerial
Organization | Primary Regulated Entity | |
stakeholders | Description | A detailed explanation of the |
Stakeholder group |
Individuals or entities that purchase and use the organization's products.
Major freight railroads operating on mainline tracks | ||
stakeholders | Role | Defined responsibilities and interests of the |
Provide feedback, influence product development
Stakeholders
Stakeholder | Maintain regulatory compliance, report safety data, implement safety programs | |
stakeholders | Organization Unit | The |
Organization unit(s) to which the |
Stakeholder is most closely linked |
Track and |
Rail Infrastructure Division |
stakeholders | Engagement Strategies | Plans to communicate and interact with this |
Regular surveys, customer support
Stakeholder | Monthly safety reviews, quarterly compliance audits | |
stakeholders | Interest Levels | Degree of influence and interest each |
Stakeholder has in |
Organization activities |
High influence |
- 80% of regulated track miles | ||
stakeholders | Inputs | Resources or information |
Stakeholders provide to the |
Feedback, purchase data
Organization | Monthly accident reports, track inspection data, employee injury statistics | |
stakeholders | Outputs | Benefits or outcomes |
Stakeholders receive from the |
Products, support services
Organization | Safety certificates, operation permits, technical guidance | |
stakeholders | Dependencies | Other |
Stakeholders processes |
or systems that the |
Stakeholder depends on |
Customer support team, product development
Equipment manufacturers, maintenance contractors | ||
stakeholders | Related Stakeholders | Stakeholders that are related or linked to this |
Suppliers, partners
Stakeholder | Short line railroads, rail unions, equipment suppliers | |
stakeholders | Performance Indicators | Metrics used to measure the effectiveness of |
Stakeholder engagement |
Customer satisfaction score, net promoter score
95% on-time reporting compliance, 2.1 reportable incidents per million train-miles | ||
stakeholders | Risks | Potential risks associated with |
Stakeholder engagement |
Negative feedback, customer churn
Incomplete data reporting, delayed safety implementations | ||
stakeholders | Improvement Opportunities | Areas where |
Stakeholder engagement can be enhanced or improved |
Improved communication channels, personalized support
Real-time data sharing, automated compliance reporting | ||
stakeholders | Strategic Alignment | How the |
Stakeholder aligns with the |
Organizations strategic goals and objectives |
Supports the strategic goal of increasing customer loyalty
Stakeholders
Stakeholder Requirement
A need or expectation from individuals or groups that have an interest in the organization's activities.
Critical to achieving system-wide safety goals |
Stakeholder requirements Element
Element | Sub-Element | Description | Example |
stakeholderRequirements | Title | The name or title of the |
Stakeholder requirement |
User Authentication
Track Inspection Compliance | ||
stakeholderRequirements | Description | A detailed explanation of the |
Stakeholder requirement |
Requirement for secure and reliable authentication mechanisms for users.
Maintain FRA class-specific track inspection frequencies and documentation | ||
stakeholderRequirements | Purpose | The intended purpose or benefit of the |
Stakeholder requirement |
To ensure security and protect user data.
Ensure track safety through regular inspections | ||
stakeholderRequirements | Owner | The individual or team responsible for fulfilling the requirement |
Security Team
Stakeholder Requirements
Chief Track Inspector | ||
stakeholderRequirements | Organization Unit | The |
Organization unit(s) impacted by the requirement |
IT, User Experience
Track Safety Division | ||
stakeholderRequirements | Acceptance Criteria | The criteria for accepting the |
Stakeholder requirement |
Successful login without security breaches, Multi-Factor Authentication enabled
100% inspection completion, <1% defect rate | ||
stakeholderRequirements | Dependencies | The dependencies related to the |
Stakeholder requirement |
Integration with existing security infrastructure, User Training
Track geometry car availability, inspector certification | ||
stakeholderRequirements | Regulatory Compliance | The regulatory requirements associated with the |
Stakeholder requirement |
49 CFR Part 213 - Track Safety Standards |