Enterprise Architecture in the Rail Domain
Total Page:16
File Type:pdf, Size:1020Kb
EA, IA, O Enterprise Architecture in the Rail Domain [email protected] [1] Wikipedia "Old MacDonald Had a Farm" is a children's song about a farmer named MacDonald (or McDonald) and the various animals he keeps on his farm. Each verse of the song changes the name of the animal and its respective noise. In many versions, the song is cumulative, with the noises from all the earlier verses added to each subsequent verse. It has a Roud Folk Song Index number of 745. Renowned computer scientist Donald Knuth jokingly shows the song to have a complexity of in "The Complexity of Songs," attributing its source to "a Scottish farmer O. McDonald." [2] [3] Systems Engineering (SE) Systems of Systems (SoS) Enterprise Architecture (EA) Information Architecture (IA) Ontology (O) [4] Systems Engineering The Art and Science of creating effective systems, using whole system, whole life principles" OR "The Art and Science of creating optimal solution systems to complex issues and problems"[8] — Derek Hitchins, Prof. of Systems Engineering, former president of INCOSE (UK), 2007. [5] A logical sequence of activities and decisions that transforms an operational need into a description of system performance parameters and a preferred system configuration. (MIL-STD-499A, Engineering Management, 1 May 1974. Now cancelled.) An interdisciplinary approach that encompasses the entire technical effort, and evolves into and verifies an integrated and life cycle balanced set of system people, products, and process solutions that satisfy customer needs. (EIA Standard IS-632, Systems Engineering, December 1994.) An interdisciplinary, collaborative approach that derives, evolves, and verifies a life-cycle balanced system solution which satisfies customer expectations and meets public acceptability. (IEEE P1220, Standard for Application and Management of the Systems Engineering Process, [Final Draft], 26 September 1994.) [6] SE guide to SoS, DoD, 2008 [7] • Virtual. Virtual SoS lack a central management authority and a centrally agreed upon purpose for the system-of-systems. Large-scale behavior emerges—and may be desirable—but this type of SoS must rely upon relatively invisible mechanisms to maintain it. • Collaborative. In collaborative SoS the component systems interact more or less voluntarily to fulfill agreed upon central purposes. Control Local • Acknowledged. Acknowledged SoS have recognized objectives, a designated manager, and resources for the SoS; however, the constituent systems retain their independent ownership, objectives, funding, and development and sustainment approaches. Changes in the systems are based on collaboration between the SoS and the system. Control • Directed. Directed SoS are those in which the integrated system-of- Central systems is built and managed to fulfill specific purposes. It is centrally managed during long-term operation to continue to fulfill those purposes as well as any new ones the system owners might wish to address. The component systems maintain an ability to operate independently, but their normal operational mode is subordinated to the central managed purpose. SE guide to SoS, DoD, 2008 [8] Dr J Kaplan, 2006 [9] Common SoS Characteristics: System of Systems: •operational independence of individual systems •managerial independence of the systems •geographical distribution •emergent behavior •evolutionary development Many SoS definitions & characterizations look like a result of whiteboard brainstorming of lots of ideas of what systems of systems often look like. D.Cocks, INCOSE, 2006 [10] Dr W Reckmeyer, 2005 [11] Five Attributes of Systems of Systems • Operational Independence of the Elements • Managerial Independence of the Elements • Evolutionary Development • Emergent Behaviour • Geographic Distribution S.E.Sheard, Incose, 2008 [12] Stakeholders in the UK’s Liberalised Railway • Association of Train Operating Companies • Department for Transport • HM Railway Inspectorate • Network Rail • Office of Rail Regulation • Passenger Transport Executives • Rail Passenger Councils • Rolling Stock Leasing Companies • Train Operating Companies C.Roberts UoB [13] Whats in SoS World CxS Differences SoS Systems Non-Complex CxS Systems S.E.Sheard, Incose, 2008 [14] Dr B Write, 2005 [15] [16] C Siel, CE(Navy), 2005 Enterprise Architecture I see the ―Railway Service‖ expressed as an Enterprise Model, defined by a discrete number of architectural layers … Performance Architecture Business Architecture Solutions Architecture Information Architecture Technical Architecture Support Architecture … here the content in each layer is related (e.g. information will have business processes to collect it and use it) S Thurlow [17] The Value of an Architecture The lost opportunities of siloed evolution We see the ―Railway Service‖ expressed as an Enterprise Model, defined by a discrete number of architectural layers … Performance Architecture Performance issues Business constraints Business Architecture Unique Training Solutions Architecture Duplicate/inconsistent Information Point2Point Interfaces Information Architecture Little reuse Technical Architecture Heterogeneous Single Supply Support Architecture Unique Support Application An EA approach defines a consistent ArchitectureApplication in each layer that applies A B across the whole enterpriseStack Stack But the Legacy estate often evolves from piecemeal procurement for point solutions as a vertical stack fragmenting the ability to combine opportunities S Thurlow [18] The Federal Enterprise Architecture (FEA) The FEA is build with a collection of reference models, that develop a common taxonomy and ontology for describing IT resources. These include the, see image: Performance Reference Model, the Business Reference Model, the Service Component Reference Model, the Data Reference Model and the Technical Reference Model. It is designed to ease sharing of information and resources across federal agencies, reduce costs, and improve citizen services. It is an initiative of the US Office of Management and Budget that aims to comply with the Clinger-Cohen Act. Wikipedia [19] Enterprise architecture has become a key component of the information technology governance process in many organizations. These companies have implemented a formal enterprise architecture process as part of their IT management strategy. While this may imply that enterprise architecture is closely tied to IT, it should be viewed in the broader context of business optimization in that it addresses business architecture, performance management and process architecture as well as more technical subjects. Depending on the organization, enterprise architecture teams may also be responsible for some aspects of performance engineering, IT portfolio management and metadata management. The following image from the 2006 FEA Practice Guidance of US OMB sheds light on the relationship between enterprise architecture and segment(BPR) or Solution architectures. (From this figure and a bit of thinking one can see that software architecture is truly a solution architecture discipline, for example.) Activities such as software architecture, network architecture, database architecture may be seen as partial contributions to a solution architecture. Wikipedia [20] Enterprise Architecture A formal definition of the structure of an enterprise comes from the MIT Centre for Information Systems Research: Enterprise Architecture is the organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the firm’s operating model. It is often said that the architecture of an enterprise exists, whether it is described explicitly or not. This makes sense if you regard the architecture as existing in the system itself, rather than in a description of it. Certainly, the business practice of enterprise architecture has emerged to make the system structures explicit in abstract architecture descriptions. Practitioners are called "enterprise architects." Wikipedia [21] Many enterprise architecture frameworks break down the practice of developing artifacts into four practice areas. This allows the enterprise to be described from four important viewpoints. By taking this approach, enterprise architects can assure their business stakeholders that they have provided sufficient information for effective decision making. These practice areas are Business: Strategy maps, goals, corporate policies, Operating Model Functional decompositions (e.g. IDEF0, SADT), capabilities and organizational models Business processes Organization cycles, periods and timing Suppliers of hardware, software, and services Information: Metadata - data that describes your enterprise data elements Data models: conceptual, logical, and physical Applications: Application software inventories and diagrams Interfaces between applications - that is: events, messages and data flows Intranet, Extranet, Internet, eCommerce, EDI links within and outside of the organization Technology: Hardware, platforms, and hosting: servers, and where they are kept Local and wide area networks, Internet connectivity diagrams, Operating System Infrastructure software: Application servers, DBMS Programming Languages, etc.. Wikipedia [22] An Extended Enterprise is a loosely coupled, self-organizing network of firms that combine their economic output to provide products and services offerings to the market. Firms in the extended enterprise may operate independently, for example, through market mechanisms, or cooperatively through