Content Comparison

Table of Contents

style	none

...

Info

Relationship of Domain, Attributes, Elements and Sub-Elements

To understand the Relationship of Domain, Attributes, Elements and Sub-Elements, see: https://orthogramic.atlassian.net/wiki/spaces/OM/pages/245137488/Domain+Attributes+Elements?atlOrigin=eyJpIjoiNWYyMjRjYzk3MzNjNDQxNWE4NjJlZjU1NmI1ZDg5NTEiLCJwIjoiYyJ9

Information attributes

Domain	Attribute	Description	Example
information	Title	The name or title of the information management element	Railroad Safety Data Analysis System
information	Description	A detailed explanation of what the information management element entails	Centralized system for collecting and analyzing railroad safety data nationwide
information	Purpose	The intended purpose or function of the information management element within the Organization	Enable data-driven safety decisions through comprehensive accident and inspection analysis
information	Owner	The individual or team responsible for the information management element	Chief Safety Data Officer
information	orgUnitTitle	The Organization unit(s) to which the information management element is linked	Safety Analysis Division
information	Inputs	The resources information or materials required for the information management element	Accident reports, inspection data, hazmat incidents, PTC implementation status
information	Outputs	The deliverables or results produced by the information management element	Monthly safety reports, risk predictions, trend analysis, regulatory recommendations
information	Processes	The set of processes that define how the information management element operates	Data collection, validation, analysis, reporting, predictive modeling
information	Performance Indicators	Metrics used to measure the effectiveness and efficiency of the information management element	Data accuracy: 99.8%, Report timeliness: 97%, Analysis completion rate: 95%
information	Dependencies	Other elements processes or systems that the information management element depends on	Railroad reporting systems, inspection databases, accident investigation reports
information	Related Information Elements	Information elements that are related or linked to this element	Track quality database, grade crossing inventory, bridge management system
information	Maturity Level	The current maturity level of the information management element	Level 4 - Predictive Analytics Capability
information	Tools and Technologies	Tools and technologies used to support or enable the information management element	Machine learning algorithms, SQL databases, visualization tools, statistical software
information	Compliance and Standards	Regulatory requirements and standards the information management element must adhere to	49 CFR Part 225 - Railroad Accidents/Incidents, FRA Data Quality Standards
information	Cost	The financial cost associated with implementing and maintaining the information management element	Annual operating cost: $8.4M, Development budget: $2.1M
information	Risks	Potential risks associated with the information management element and its operations	Data quality issues, system downtime, reporting delays, cybersecurity threats
information	Improvement Opportunities	Areas where the information management element can be enhanced or improved	Implement AI-driven analysis, enhance mobile reporting, automate validation
information	Strategic Alignment	How the information management element aligns with the Organizations strategic goals and objectives	Provides critical data support for accident reduction and safety improvement goals
information	Information Component	A piece of data or information used within the Organization to support various processes and decision-making	Accident investigation reports, track inspection records, hazmat movement data

Information Element

Elements	Sub-Element	Description	Example
informationComponent	Title	The name or title of the information component	Railroad Accident/Incident Reporting System
informationComponent	Description	A detailed explanation of the information component	Centralized database for tracking and analyzing all railroad accidents incidents and casualties
informationComponent	Purpose	The intended use or function of the information component	Enable comprehensive analysis of railroad safety trends and accident causes
informationComponent	Owner	The individual or team responsible for managing the information	Director of Railroad Safety Analysis
informationComponent	orgUnitTitle	The Organization unit(s) using the information component	Safety Analysis and Statistical Services Division
informationComponent	Data Sources	The sources from which the information is collected	Form FRA F 6180.54 (Rail Equipment), Form FRA F 6180.57 (Highway-Rail Grade Crossing), Form FRA F 6180.55A (Railroad Injury and Illness Summary)
informationComponent	Data Quality	The quality measures and standards for the information component	Accuracy: 99.9%, Completeness: 98.5%, Timeliness: 97% within 30 days
informationComponent	Security	The security measures applied to protect the information	Role-based access control, 256-bit encryption, Multi-factor authentication

Information JSON schema

Code Block

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "Information Domain Schema",
  "description": "Schema for the Information domain in the Orthogramic Metamodel",
  "type": "object",
  "properties": {
    "title": {
      "type": "string",
      "description": "The name or title of the information management element"
    },
    "description": {
      "type": "string",
      "description": "A detailed explanation of what the information management element entails"
    },
    "purpose": {
      "type": "string",
      "description": "The intended purpose or function of the information management element within the Organization"
    },
    "owner": {
      "type": "string",
      "description": "The individual or team responsible for the information management element"
    },
    "orgUnitTitle": {
      "type": "string",
      "description": "The Organization unit(s) to which the information management element is linked"
    },
    "inputs": {
      "type": "string",
      "description": "The resources information or materials required for the information management element"
    },
    "outputs": {
      "type": "string",
      "description": "The deliverables or results produced by the information management element"
    },
    "processes": {
      "type": "string",
      "description": "The set of processes that define how the information management element operates"
    },
    "performanceIndicators": {
      "type": "string",
      "description": "Metrics used to measure the effectiveness and efficiency of the information management element"
    },
    "dependencies": {
      "type": "string",
      "description": "Other elements processes or systems that the information management element depends on"
    },
    "relatedInformationElements": {
      "type": "string",
      "description": "Information elements that are related or linked to this element"
    },
    "maturityLevel": {
      "type": "string",
      "description": "The current maturity level of the information management element"
    },
    "toolsAndTechnologies": {
      "type": "string",
      "description": "Tools and technologies used to support or enable the information management element"
    },
    "complianceAndStandards": {
      "type": "string",
      "description": "Regulatory requirements and standards the information management element must adhere to"
    },
    "cost": {
      "type": "string",
      "description": "The financial cost associated with implementing and maintaining the information management element"
    },
    "risks": {
      "type": "string",
      "description": "Potential risks associated with the information management element and its operations"
    },
    "improvementOpportunities": {
      "type": "string",
      "description": "Areas where the information management element can be enhanced or improved"
    },
    "strategicAlignment": {
      "type": "string",
      "description": "How the information management element aligns with the Organizations strategic goals and objectives"
    },
    "informationComponent": {
      "type": "array",
      "description": "Components or pieces of information",
      "items": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string",
            "description": "The name or title of the information component"
          },
          "description": {
            "type": "string",
            "description": "A detailed explanation of the information component"
          },
          "purpose": {
            "type": "string",
            "description": "The intended use or function of the information component"
          },
          "owner": {
            "type": "string",
            "description": "The individual or team responsible for managing the information"
          },
          "orgUnitTitle": {
            "type": "string",
            "description": "The Organization unit(s) using the information component"
          },
          "dataSources": {
            "type": "string",
            "description": "The sources from which the information is collected"
          },
          "dataQuality": {
            "type": "string",
            "description": "The quality measures and standards for the information component"
          },
          "security": {
            "type": "string",
            "description": "The security measures applied to protect the information"
          }
        }
      }
    }
  }
}

Version	Old Version 7	New Version 8
Changes made by	damian.hickey	damian.hickey
Saved on	Apr 14, 2025	Apr 14, 2025

Versions Compared

Key

Relationship of Domain, Attributes, Elements and Sub-Elements

Information attributes

Information Element

Information JSON schema