enterprise modelling
veryard projects > sebpc > modelling > enterprise modelling
|
enterprise modellingveryard projects > sebpc > modelling > enterprise modelling |
|
| enterprise modelling | material | links |
| An enterprise model is a structured representation
of a business organization, of its internal structure and its relationships
with its environment.
Enterprise models may be static or dynamic. A static model is a snapshot of the enterprise or organization at a particular time, which may include its structure, boundaries with the environment, processes, strategic objectives, Porter's competitive forces, values, external influences, SWOT (strengths, weaknesses, opportunities & threats), and so on. A dynamic model is one that represents the way these things change over time. Organizational learning models, maturity models and technology assimilation models fall into this category. Warning: people sometimes misleadingly use the term to refer to an enterprise-wide model - in other words, a model (such as an information model) whose scope is the whole enterprise. |
> motivation
> styles > demands > archived papers > modelling > methodology |
|
 |
Motivation for Enterprise Modellingveryard projects > sebpc > modelling > enterprise modelling > motivation |
| Business Strategy | Identifying and implementing business strategies appropriate for the enterprise in a given context (with internal strengths and weaknesses, and with external opportunities and threats) |
| Organization Design
& Process Design |
Identifying and implementing radical or incremental operational or management improvements |
| IT / IS Planning | Cost justification, procurement and implementation of all aspects of IT, including communications infrastructures, and tools and environments for application development and operation. Cost justification, procurement and implementation of application systems, within a framework defined by the IT Plan. Also includes the organizational structures to support IT, and policies to support Development Coordination. |
| Requirements Engineering
& System Development |
Defining the requirements for particular applications or application portfolios, developing systems, and planning the transition and/or bridging from legacy systems to newly developed systems |
|
Styles of Enterprise Modellingveryard projects > sebpc > modelling > enterprise modelling > styles |
Enterprise models may be static or dynamic. A static model is a snapshot of the enterprise or organization at a particular time, which may include its structure, boundaries with the environment, processes, strategic objectives, Porter's competitive forces, values, external influences, SWOT (strengths, weaknesses, opportunities & threats), and so on. A dynamic model is one that represents the way these things change over time. Organizational learning models, maturity models and technology assimilation models fall into this category.
Enterprise models typically include such concepts as organization (unit), agent, responsibility/role, business process, value chain, contract and policy.
Various enterprise modelling styles have been identified. These
include:
| style | description | examples |
| Business Strategy Modelling | A hierarchical model including such concepts as objective, goal, critical success factor, inhibitor, performance measure, benefit, cost, strategy, tactic and plan | |
| Organization Hierarchy and Geography Modelling | A hierarchical model of the organization mapped to locations | |
| Responsibility Modelling | A model of responsibilities, obligations and activities. | ORDIT
RAEW analysis |
| Business Process Modelling | A model of value chains, measuring the costs and delays of each process. | BPR |
| Maturity Modelling | Systematic ways of assessing the strengths and weaknesses of an enterprise as a whole, of a particular process (such as software development) or of the usage of particular technology. Software process maturity models are often influenced by Crosby's work in quality management. | Nolan
SEI CMM Bootstrap SPICE |
| Business Cohesion Modelling | A model of the coordination mechanisms that hold hierarchical or network structures together. | VSM |
| Communication Modelling | A model of conversations and contracts between agents, often based on the speech act theory of Austin & Searle. | |
| Business Relationship Modelling | Defines the topology of a distributed system, in which many autonomous agents interact commercially and technically to perform one or many decentralized business processes, or to deliver one or many business services. | SCIPIO |
|
Demands on Enterprise Modellingveryard projects > sebpc > modelling > enterprise modelling > demands |
| Complexity | Ability to reason "holistically" about the (emergent) identity, intentions and behaviour of an enterprise as a complex whole. |
| Open systems | Ability to reason about systems in dynamic interaction with the environment, with permeable and flexible boundaries. |
| Distribution | Ability to reason about different organizational forms, including virtual enterprises, federated and distributed structures. |
| Politics | Ability to reason about conflicting intentions and behaviour. |
|
Archived Papersveryard projects > sebpc > modelling > enterprise modelling > papers |
| 1993 | Enterprise Computing: ODP as an
Instrument of Hegemony
(pdf, 360k) |
David Iggulden
John Dobson Richard Veryard |
This position paper makes use of ODP enterprise language concepts in understanding the relationship between an information systems architecture and the politics of ownership for the system. The focus is conflict resolution - between views occurring in the enterprise that are fundamentally opposed but which need to co-exist and to interact. Resolution of conflict is not strictly the province of ODP. However, the nature of the support provided by an ODP infrastructure must allow the system to respond to any changes made in the organisational structure and policy. The application of basic ODP concepts is illustrated by part of an example of tertiary medical care provided by the ORDIT project. This brief example raises a number of issues of how ODP concepts could be applied to a model of system development. |
| 1994 | EMM/ODP A methodology for federated
and distributed systems
(pdf, 122k) |
Richard. Veryard
Ian Macdonald with
|
EMM/ODP is a methodology for defining and cost-justifying the organizational and business requirements for federated and distributed information systems, especially those following the emerging standards for Open Distributed Processing (ODP). Federated/ distributed information systems have the potential for increasing coordination between heterogeneous organizational units, but this almost always requires significant organizational changes as well as the development and installation of appropriate computer systems. The EMM/ODP methodology is therefore based around an enterprise modelling language EML/ODP, which allows both the organizational and technological issues to be properly explored and resolved. |
|
