Difference between revisions of "Main"

From EnterprisePLUS [E+]
 
(92 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
A '''business process''' or '''business method'''  is a collection of related, structured activities or [[Task (project management)|tasks]] that produce a specific service or product (serve a particular goal) for a particular customer or customers. It may often be visualized as a [[flowchart]] of a sequence of activities with interleaving decision points or as a Process Matrix of a sequence of activities with relevance rules based on data in the process.
+
<h1 style="color: #087dc1; margin-top: 0px;">Welcome to '''EnterprisePLUS'''</h1>
  
−
== Overview ==
+
<hr style="margin-top: -5px; height: 10px; border: 0; box-shadow: 0 10px 10px -10px #fcaf17 inset;">
−
There are three types of business processes{{citation needed|date=March 2015}}:
+
−
# [[Management process]]es, the processes that govern the operation of a system. Typical management processes include "[[corporate governance]]" and "[[strategic management]]".
+
−
# Operational processes, processes that constitute the [[core business]] and create the primary value stream.  For example, taking orders from customers, and opening an account in a bank branch.
+
−
# Supporting processes, which support the core processes. Examples include Health & Safety, [[accounting]], [[recruitment]], [[call center]], [[technical support]].
+
  
−
A business process begins with a mission objective and ends with achievement of the business objective. Process-oriented organizations break down the barriers of structural departments and try to avoid [[functional silo]]s.
+
<div style="margin: 20px 40px 20px 0; width: 65%; float: left;">
  
−
A complex business process may be decomposed into several sub-processes,<ref>Information Resources Management Association USA, Enterprise Information Systems: Concepts, Methodologies, Tools and Applications, p. 1065</ref> which have their own attributes, but also contribute to achieving the goal of the super-process. The analysis of business processes typically includes the mapping of processes and sub-processes down to activity/task level.<ref name="DeselPernici2004">{{cite book|author1=Jörg Desel|author2=Barbara Pernici|author3=Mathias Weske|title=Business Process Management: Second International Conference, BPM 2004, Potsdam, Germany, June 17-18, 2004, Proceedings|url=http://books.google.com/books?id=F75MqHCmkXsC&pg=PA202|date=14 June 2004|publisher=Springer Science & Business Media|isbn=978-3-540-22235-4|pages=202–}}</ref><ref name="ceiton">{{cite web|url=http://ceiton.com/CMS/EN/workflow/introduction.html#Task_Management|title=Task management in a workflow|publisher=ceiton.com|accessdate=2015-03-20}}</ref>
+
The EnterprisePLUS software tools (Enterprise+ or E+) is a new breed of integrated modelling and architecture tool. It is offered as a Software as a Service (SaaS) solution, and consists of 2 major application components:
 +
#A Modelling Software component where the expert can create and work with many different types of modelling and architecture components; and
 +
#A Knowledge Management system where the models, views and standards can be posted for anybody within the enterprise. This provides a whole new experience to publishing, referencing, commenting and continuous improvements in a collaborative and user-friendly environment.
  
−
Business processes are designed<ref>William Bentley, Peter T. Davis, Lean Six Sigma Secrets for the CIO, p. 19</ref> to add value for the customer and should not include unnecessary activities. The outcome of a well designed business process is increased effectiveness (value for the customer) and increased efficiency (less costs for the company).
 
  
−
Business Processes can be modeled through a large number of methods and techniques. For instance, the [[Business Process Modeling Notation]] is a [[Business Process Modeling]] technique that can be used for drawing business processes in a [[workflow]].
+
== The '''Modelling Software''' Component ==
  
−
==History==
+
Various enterprise modelling and enterprise architecture concepts and disciplines have become a normal part of daily work. It doesn’t matter if it's about documenting the existing As-Is state or designing the future To-Be state, the need for modelling and architecting aspects of the enterprise is always relevant.
−
=== Adam Smith ===<!-- This section is linked from [[Division of labour]] -->
+
−
An important early (1776) description of processes was that of economist [[Adam Smith]] in his famous example of a [[pin (device)|pin]] factory. Inspired by an article in [[Diderot|Diderot's]] [[Encyclopédie]], Smith described the production of a pin in the following way:
+
−
<blockquote>
+
−
”One man draws out the wire, another straights it, a third cuts it, a fourth points it, a fifth grinds it at the top for receiving the head: to make the head requires two or three distinct operations: to put it on is a particular business, to whiten the pins is another ... and the important business of making a pin is, in this manner, divided into about eighteen distinct operations, which in some manufactories are all performed by distinct hands, though in others the same man will sometime perform two or three of them.”
+
−
</blockquote>
+
−
Smith also first recognized how the output could be increased through the use of [[Division of labour|labor division]]. Previously, in a society where production was dominated by [[artisan|handcrafted goods]], one man would perform all the activities required during the production process, while Smith described how the work was divided into a set of simple tasks, which would be performed by specialized workers. The result of labor division in Smith’s example resulted in productivity increasing by 24,000 percent (sic), i.e. that the same number of workers made 240 times as many pins as they had been producing before the introduction of labor division.
+
  
−
It is worth noting that Smith did not advocate labor division at any price and ''[[wikt:per se|per se]]''. The appropriate level of task division was defined through experimental design of the production process. In contrast to Smith's view which was limited to the same functional domain and comprised activities that are in direct sequence in the manufacturing process, today's process concept includes cross-functionality as an important characteristic. Following his ideas the division of labor was adopted widely, while the integration of tasks into a functional, or cross-functional, process was not considered as an alternative option until much later.
+
E+ has as the first tool incorporated standards from ISO, OMG, LEADing Practice and IEEE to support the following standards:
  
−
=== Frederick Winslow Taylor ===
+
'''Enterprise Modelling Standards:'''
−
American engineer, [[Frederick Winslow Taylor]] greatly influenced and improved the quality of [[industrial processes]] in the early twentieth century. His [[Principles of Scientific Management]] focused on standardization of processes, systematic training and clearly defining the roles of management and employees. His methods were widely adopted in the United States, Russia and parts of Europe and led to further developments such as “time and motion study” and visual task optimization techniques, such as [[Gantt charts]].
+
*Value Modelling Notations (VMN)
 +
*Strategy Modelling Notations (StMN)
 +
*Planning Modelling Notations (PLMN)
 +
*Policy Modelling Notations (PoMN)
 +
*Reporting Modelling Notations (RPMN)
 +
*Risk Modelling Notations (RiMN)
 +
*Rule Modelling Notations (RuMN)
 +
*Quality Modelling Notations (QMN)
 +
*Requirement Modelling Notations (ReMN)
 +
*Capability Modelling Notations (CMN)
 +
*Blockchain Modelling Notations (BcMN)
 +
*Service Modelling Notations (SMN)
 +
*Business Process Modelling Notations (BPMN)
 +
*Robotic Automation Modelling Notations (RAMN)
 +
*Application Modelling Notations (AMN)
 +
*Data Modelling Notations (DMN)
 +
*Platform Modelling Notations (PMN)
 +
*Infrastructure Modelling Notations (IMN)
 +
*Industry 4.0 Modelling Notations (I4MN)
  
−
=== Peter Drucker ===
+
'''Enterprise Architecture Standards:'''
−
In the latter part of the twentieth century, management guru [[Peter Drucker]] focused much of his work on simplification and decentralization of processes, which led to the concept of [[outsourcing]].
+
*Business Architecture Notations (BAN)
 +
*Information Architecture Notations (IAN)
 +
*Technology Architecture Notations (TAN)
 +
*Enterprise Architecture Notations (EAN)
  
−
=== Other definitions ===
+
The E+ software tools thereby uniquely satisfies the most common enterprise modelling and architecture needs.
−
In the early 1990s, US corporations, and subsequently companies all over the world, started to adopt the concept of [[business process reengineering]] (BPR) in an attempt to re-achieve the competitiveness that they had lost during the previous decade.
+
  
−
Davenport (1993)<ref>Thomas Davenport (1993). ''Process Innovation: Reengineering work through information technology''. Harvard Business School Press, Boston</ref> defines a (business) process as:
 
−
<blockquote>
 
−
”a structured, measured set of activities designed to produce a specific output for a particular customer or market. It implies a strong emphasis on how work is done within an organization, in contrast to a product focus’s emphasis on what. A process is thus a specific ordering of work activities across time and space, with a beginning and an end, and clearly defined inputs and outputs: a structure for action. ... Taking a process approach implies adopting the customer’s point of view. Processes are the structure by which an organization does what is necessary to produce value for its customers.”
 
−
</blockquote>
 
−
This definition contains certain characteristics a process must possess. These characteristics are achieved by a focus on the business logic of the process (how work is done), instead of taking a product perspective (what is done). Following Davenport's definition of a process we can conclude that a process must have clearly defined boundaries, input and output, that it consists of smaller parts, activities, which are ordered in time and space, that there must be a receiver of the process outcome- a customer - and that the transformation taking place within the process must add customer value.
 
  
−
Hammer & Champy’s (1993)<ref>Michael Hammer and James Champy (1993). ''Reengineering the Corporation: A Manifesto for Business Revolution'', Harper Business</ref> definition can be considered as a subset of Davenport’s. They define a process as:
+
== The '''Knowledge Management''' system ==
−
<blockquote>
+
−
”a collection of activities that takes one or more kinds of input and creates an output that is of value to the customer.”
+
−
</blockquote>
+
−
As we can note, Hammer & Champy have a more transformation oriented perception, and put less emphasis on the structural component – process boundaries and the order of activities in time and space.
+
  
−
Rummler & Brache (1995)<ref>Rummler & Brache (1995). ''Improving Performance: How to manage the white space on the organizational chart''. Jossey-Bass, San Francisco</ref> use a definition that clearly encompasses a focus on the organization’s external customers, when stating that
+
The combination of the E+ modelling and Knowledge Management System is what differentiates E+, from any other enterprise modelling, engineering and architecture tool. It is the combination of where the enterprise modeller, engineer and/or architect can share the views/models created with others who don’t need to have the software access. This can include uploading training content, quality parameters, own developed standards as well as time aspects, measures, reports, policies, procedures etc  to a specific function, process or service.
−
<blockquote>
+
−
”a business process is a series of steps designed to produce a product or service. Most processes (...) are cross-functional, spanning the ‘white space’ between the boxes on the organization chart. Some processes result in a product or service that is received by an organization's external customer. We call these primary processes. Other processes produce products that are invisible to the external customer but essential to the effective management of the business. We call these support processes.”
+
−
</blockquote>
+
  
−
The above definition distinguishes two types of processes, primary and support processes, depending on whether a process is directly involved in the creation of customer value, or concerned with the organization’s internal activities. In this sense, Rummler and Brache's definition follows Porter's [[value chain]] model, which also builds on a division of primary and secondary activities. According to Rummler and Brache, a typical characteristic of a successful process-based organization is the absence of secondary activities in the primary value flow that is created in the customer oriented primary processes. The characteristic of processes as spanning the white space on the organization chart indicates that processes are embedded in some form of organizational structure. Also, a process can be cross-functional, i.e. it ranges over several business functions.
+
The E+ knowledge management thereby creates and addresses the real knowledge issues inside the organization. KM Users can comment, provide feedback/suggestions to the uploaded content/views. As the E+ KMS content related back to the E+ objects and view (models), can the content be continuously be improved. While traditional content management databases contain only text and documents which computers can neither understand nor evaluate, the E+ KMS adds semantic annotations that allow any content to function as a collaborative database that recognizes cross relations. Making sure that there is a semantic relationship between the relevant subjects. The reason the E+ KMS users are cheaper than the E+ modelling user licenses, is based on that the E+ KMS users are viewing and using the system. There is no need for costly users, when all the need to do is to view, follow instructions, provide input, document changes and also offer feedback.
  
−
Johansson et al. (1993).<ref>Henry J. Johansson et al. (1993). ''Business Process Reengineering: BreakPoint Strategies for Market Dominance''. John Wiley & Sons</ref> define a process as:
 
−
<blockquote>
 
−
”a set of linked activities that take an input and transform it to create an output. Ideally, the transformation that occurs in the process should add value to the input and create an output that is more useful and effective to the recipient either upstream or downstream.”
 
−
</blockquote>
 
−
This definition also emphasizes the constitution of links between activities and the transformation that takes place within the process. Johansson et al. also include the upstream part of the value chain as a possible recipient of the process output. Summarizing the four definitions above, we can compile the following list of characteristics for a business process:
 
  
−
# ''Definability'' : It must have clearly defined boundaries, input and output.
+
== The '''E+ Demo Case''' ==
−
# ''Order'' : It must consist of activities that are ordered according to their position in time and space (a sequence).
+
−
# ''Customer'' : There must be a recipient of the process' outcome, a customer.
+
−
# ''Value-adding'' :  The transformation taking place within the process must add value to the recipient, either upstream or downstream.
+
−
# ''Embeddedness'' : A process cannot exist in itself, it must be embedded in an organizational structure.
+
−
# ''Cross-functionality'' : A process regularly can, but not necessarily must, span several functions.
+
  
−
Frequently, a [[process owner]], i.e. a person being responsible for the performance and continuous improvement of the process, is also considered as a prerequisite.
+
We have a lot of different self-study tutorials that help you work with E+. Here you can find a basic description tutorial of how to get started.
  
−
==Related Concepts==
+
'''Tutorial Document''': [[Media:E+ GBI Production & GBS Retailer Case.pdf|Download the E+ GBI Production & GBS Retailer Case Model.]]
  
−
===Workflow===
+
</div>
  
−
[[Workflow]] is the movement of information or material from one activity or worksite to another. Workflow includes the procedures, people and tools involved in each step of a business process. A single workflow may either be sequential, with each step contingent upon completion of the previous one, or parallel, with multiple steps occurring simultaneously.  Multiple combinations of single workflows may be connected to achieve a resulting overall process.
+
<div style="padding: 20px; margin: 20px 0 20px 0; width: 30%; background-color: #f5f5f5; border: 2px solid #d2d3d5; float: left;">
  
−
===Business Process Re-engineering===
+
'''UPDATES & TUTORIALS'''
 +
<hr style="margin-top: -5px; height: 10px; border: 0; box-shadow: 0 10px 10px -10px #fcaf17 inset;">
  
−
[[Business Process Re-engineering]] (BPR) was originally conceptualized by Hammer and Davenport as a means to improve organizational effectiveness and productivity. It consisted of starting from a blank slate and completely recreating major business processes as well as the use of information technology for significant performance improvement. The term unfortunately, became associated with corporate “downsizing” in the mid-1990s.
+
Here you can find a list of quick links that takes you directly to the tutorial page of each subject. Please find the list of tutorial subjects below:
 +
*[[Media:LEADing_Practice_-_Best Practice_&_Tips_&_Tricks_.pdf|Best Practice & Tips & Tricks]]
 +
*[[Media:Working_with_Objects_in_E+.pdf|Working with Objects in E+]]
 +
*[[LEAD_Reference_Content:Working_with_the_EnterprisePLUS_Modelling_Tool|Working with the EnterprisePLUS Modelling Tool]]
 +
*[[LEAD_Reference_Content:E%2B_GBI_Production_%26_GBS_Retailer_Case|E+ GBI Production & GBS Retailer Case]]
 +
*[[LEAD_Reference_Content:Creating_Maps_%26_Matrices|Creating Maps & Matrices]]
 +
*[[Media:E+_Bug_Reporting_Template.docx|Bug Reporting Template]]
 +
*[[LEAD_Reference_Content:Working_with_KM_%26_Templates|Working with KM & Templates]]
  
−
===Business Process Management (BPM)===
+
</div>
  
−
[[Business Process Management]] also termed as BPM covers how we study, identify, change and monitor business processes to ensure they run smoothly and can be improved over time.  It is a continuous evaluation of existing processes and identification of ways to improve upon it, resulting in a cycle of overall organizational improvement.<ref>Aiim-Glossary: [http://www.aiim.org/What-is-BPM-Business-Process-Management What is Business Process management?]</ref>
+
<div style="clear: both;"></div>
  
−
===Knowledge Management===
 
  
−
[[Knowledge Management]] is the definition of the knowledge that employees and systems use to perform their functions and maintaining it in a format that can be accessed by others. The Gartner Group definition states that "Knowledge management is a discipline that promotes an integrated approach to identifying, capturing, evaluating, retrieving, and sharing all of an enterprise's information assets. These assets may include databases, documents, policies, procedures, and previously un-captured expertise and experience in individual workers."
+
__NOTOC__
−
 
+
−
===Total Quality Management===
+
−
 
+
−
[[Total Quality Management]] (TQM) emerged in the early 1980s as organizations sought to improve the quality of their products and services. It was followed by the [[Six Sigma|Six Sigma methodology]] in the mid-1980s, first introduced by Motorola. Six Sigma consists of statistical methods to improve business processes and thus reduce defects in outputs. The "lean approach" to quality management was introduced by the Toyota Motor Company in the 1990s and focused on customer needs and reduction of wastage.
+
−
 
+
−
===Information Technology as an Enabler for Business Process Management===
+
−
 
+
−
Advances in information technology over the years, have changed business processes within and between business enterprises. In the 1960s, operating systems had limited functionality and any workflow management systems that were in use, were tailor made for the specific organization.
+
−
 
+
−
The 1970s-1980s saw the development of data-driven approaches, as data storage and retrieval technologies improved. Data modeling rather than process modeling was the starting point for building an information system. Business processes had to adapt to information technology because process modeling was neglected.
+
−
 
+
−
The shift towards process oriented management occurred in the 1990s. Enterprise resource planning software with workflow management components such as SAP, Baan, PeopleSoft, Oracle and JD Edwards emerged.
+
−
 
+
−
The world of e-business created a need to automate business processes across organizations, which in turn raised the need for standardized protocols and web services composition languages that can be understood across the industry. The [[Business Process Modeling Notation]] (BPMN) and [[Business Motivation Model]] (BMM) are widely used standards for business modeling. The Business Modeling and Integration Domain Task Force (BMI DTF) is a consortium of vendors and user companies that continues to work together to develop standards and specifications to promote collaboration and integration of people, systems, processes and information within and across enterprises.
+
−
 
+
−
The most recent trends in BPM are influenced by emergence of cloud technology, the prevalence of social media, mobile technology and development of analytical techniques. Cloud based technologies allow companies to purchase resources quickly and as required independent of their location. Social media, websites and smart phones are the newest channels through which organizations reach and support their customers. The abundance of customer data collected through these channels as well as through call center interactions, emails, voice calls, and customer surveys has led to a huge growth in data analytics which in turn is utilized for performance management and improving the ways in which the company services its customers.
+
−
 
+
−
==Importance of the process chain==
+
−
 
+
−
Business processes comprise a set of sequential sub-processes or tasks with alternative paths, depending on certain conditions as applicable, performed to achieve a given objective or produce given outputs. Each process has one or more needed inputs. The inputs and outputs may be received from, or sent to other business processes, other [[organizational unit]]s, or internal or external stakeholders.
+
−
 
+
−
Business processes are designed to be operated by one or more business functional units, and emphasize the importance of the “[[process chain]]” rather than the individual units.
+
−
 
+
−
In general, the various tasks of a business process can be performed in one of two ways
+
−
# manually and
+
−
# by means of business [[data processing]] systems such as [[ERP system]]s.
+
−
 
+
−
Typically, some process tasks will be manual, while some will be computer-based, and these tasks may be sequenced in many ways. In other words, the data and information that are being handled through the process may pass through manual or computer tasks in any given order.
+
−
 
+
−
==Policies, processes and procedures==
+
−
 
+
−
The above improvement areas are equally applicable to policies, processes and detailed procedures (sub-processes/tasks).  There is a cascading effect of improvements made at a higher level on those made at a lower level.
+
−
 
+
−
For instance, if a recommendation to replace a given policy with a better one is made with proper justification and accepted in principle by business process owners, then corresponding changes in the consequent processes and procedures will follow naturally in order to enable implementation of the policies
+
−
 
+
−
==Manual / administrative vs. computer system-based internal controls==
+
−
 
+
−
Internal controls can be built into manual / administrative process steps and / or computer system procedures.
+
−
 
+
−
It is advisable to build in as many system controls as possible, since these [[controls]], being automatic, will always be exercised since they are built into the design of the business system software. For instance, an error message preventing an entry of a received raw material quantity exceeding the purchase order quantity by greater than the permissible tolerance percentage will always be displayed and will prevent the system user from entering such a quantity.
+
−
 
+
−
However, for various reasons such as practicality, the need to be “flexible” (whatever that may signify), lack of business domain knowledge and experience, difficulties in designing/writing software, cost of software development/modification, the incapability of a computerised system to provide controls, etc., all internal controls otherwise considered to be necessary are often not built into business systems and software.
+
−
 
+
−
In such a scenario, the manual, administrative process controls outside the computer system should be clearly documented, enforced and regularly exercised.  For instance, while entering data to create a new record in a material system database’s item master table, the only internal control that the system can provide over the item description field is not to allow the user to leave the description blank – in other words, configure item description as a mandatory field.  The system obviously cannot alert the user that the description is wrongly spelled, inappropriate, nonsensical, etc.
+
−
 
+
−
In the absence of such a system-based internal control, the item creation process must include a suitable administrative control through the detailed checking, by a responsible officer, of all fields entered for the new item, by comparing a print-out taken from the system with the item data entry sheet, and ensuring that any corrections in the item description (and other similar fields where no system control is possible) are promptly carried out.
+
−
 
+
−
Last but not least, the introduction of effective manual, administrative controls usually requires an overriding periodic check by a higher authority to ensure that such controls are exercised in the first place.
+
−
 
+
−
==Information reports as an essential base for executing business processes==
+
−
 
+
−
Business processes must include up-to-date and accurate [[business reporting|reports]] to ensure effective action.  An example of this is the availability of [[purchase order]] status reports for supplier delivery follow-up as described in the section on effectiveness above. There are numerous examples of this in every possible business process.
+
−
 
+
−
Another example from production is the process of analysis of line [[wikt:reject|reject]]ions occurring on the shop floor. This process should include systematic periodical analysis of rejections by reason, and present the results in a suitable information report that pinpoints the major reasons, and trends in these reasons, for management to take [[corrective action]]s to control rejections and keep them within acceptable limits. Such a process of analysis and summarisation of line rejection events is clearly superior to a process which merely inquires into each individual rejection as it occurs.
+
−
 
+
−
Business [[process owner]]s and operatives should realise that process improvement often occurs with introduction of appropriate transaction, operational, highlight, exception or [[Management information system|M.I.S.]] reports, provided these are consciously used for day-to-day or periodical decision-making. With this understanding would hopefully come the willingness to invest time and other resources in business process improvement by introduction of useful and relevant reporting systems.
+
−
 
+
−
== Supporting theories and concepts ==
+
−
 
+
−
=== Span of control ===
+
−
The [[span of control]] is the number of subordinates a supervisor manages within a structural [[organization]]. Introducing a business process concept has a considerable impact on the structural elements of the organization and thus also on the span of control.
+
−
 
+
−
Large organizations that are not organized as markets need to be organized in smaller units - [[departmentalization|departments]] - which can be defined according to different principles.
+
−
 
+
−
=== Information management concepts ===
+
−
[[Information Management]] and the organization design strategies being related to it, are a theoretical cornerstone of the business process concept.
+
−
 
+
−
==See also==
+
−
* [[Business analysis]]
+
−
* [[Business Process Automation]]
+
−
* [[Business Process Definition Metamodel]]
+
−
* [[Business process improvement]]
+
−
* [[Business process management]]
+
−
* [[Business process mapping]]
+
−
* [[Business process outsourcing]]
+
−
* [[Information management]]
+
−
 
+
−
==References==
+
−
{{reflist}}
+
−
 
+
−
== Further reading ==
+
−
* Paul's Harmon, (2007). ''Business Process Change: 2nd Ed, A Guide for Business Managers and BPM and [[Six Sigma]] Professionals''. Morgan Kaufmann
+
−
* E. Obeng and S. Crainer S (1993). ''Making [[Business process reengineering|Re-engineering]] Happen''. Financial Times Prentice Hall
+
−
* Howard Smith and Peter Fingar (2003). ''Business Process Management''. The Third Wave, MK Press
+
−
* Slack et al., edited by: David Barnes (2000) The Open University, Understanding Business: Processes
+
−
* Malakooti, B. (2013). Operations and Production Systems with Multiple Objectives. John Wiley & Sons.
+
−
* McKeehan, A. (2015). ''[http://www.paradigmrpa.com/what-is-business-process-management-2/ What is Business Process Management?]''. Paradigm Robotics
+
−
 
+
−
{{Commons category|Business process management}}
+
−
 
+
−
{{DEFAULTSORT:Business Process}}
+
−
[[Category:Enterprise modelling]]
+
−
[[Category:Process management]]
+
−
[[Category:Business process]]
+

Latest revision as of 09:36, 12 April 2021

Welcome to EnterprisePLUS

The EnterprisePLUS software tools (Enterprise+ or E+) is a new breed of integrated modelling and architecture tool. It is offered as a Software as a Service (SaaS) solution, and consists of 2 major application components:

  1. A Modelling Software component where the expert can create and work with many different types of modelling and architecture components; and
  2. A Knowledge Management system where the models, views and standards can be posted for anybody within the enterprise. This provides a whole new experience to publishing, referencing, commenting and continuous improvements in a collaborative and user-friendly environment.


The Modelling Software Component

Various enterprise modelling and enterprise architecture concepts and disciplines have become a normal part of daily work. It doesn’t matter if it's about documenting the existing As-Is state or designing the future To-Be state, the need for modelling and architecting aspects of the enterprise is always relevant.

E+ has as the first tool incorporated standards from ISO, OMG, LEADing Practice and IEEE to support the following standards:

Enterprise Modelling Standards:

  • Value Modelling Notations (VMN)
  • Strategy Modelling Notations (StMN)
  • Planning Modelling Notations (PLMN)
  • Policy Modelling Notations (PoMN)
  • Reporting Modelling Notations (RPMN)
  • Risk Modelling Notations (RiMN)
  • Rule Modelling Notations (RuMN)
  • Quality Modelling Notations (QMN)
  • Requirement Modelling Notations (ReMN)
  • Capability Modelling Notations (CMN)
  • Blockchain Modelling Notations (BcMN)
  • Service Modelling Notations (SMN)
  • Business Process Modelling Notations (BPMN)
  • Robotic Automation Modelling Notations (RAMN)
  • Application Modelling Notations (AMN)
  • Data Modelling Notations (DMN)
  • Platform Modelling Notations (PMN)
  • Infrastructure Modelling Notations (IMN)
  • Industry 4.0 Modelling Notations (I4MN)

Enterprise Architecture Standards:

  • Business Architecture Notations (BAN)
  • Information Architecture Notations (IAN)
  • Technology Architecture Notations (TAN)
  • Enterprise Architecture Notations (EAN)

The E+ software tools thereby uniquely satisfies the most common enterprise modelling and architecture needs.


The Knowledge Management system

The combination of the E+ modelling and Knowledge Management System is what differentiates E+, from any other enterprise modelling, engineering and architecture tool. It is the combination of where the enterprise modeller, engineer and/or architect can share the views/models created with others who don’t need to have the software access. This can include uploading training content, quality parameters, own developed standards as well as time aspects, measures, reports, policies, procedures etc to a specific function, process or service.

The E+ knowledge management thereby creates and addresses the real knowledge issues inside the organization. KM Users can comment, provide feedback/suggestions to the uploaded content/views. As the E+ KMS content related back to the E+ objects and view (models), can the content be continuously be improved. While traditional content management databases contain only text and documents which computers can neither understand nor evaluate, the E+ KMS adds semantic annotations that allow any content to function as a collaborative database that recognizes cross relations. Making sure that there is a semantic relationship between the relevant subjects. The reason the E+ KMS users are cheaper than the E+ modelling user licenses, is based on that the E+ KMS users are viewing and using the system. There is no need for costly users, when all the need to do is to view, follow instructions, provide input, document changes and also offer feedback.


The E+ Demo Case

We have a lot of different self-study tutorials that help you work with E+. Here you can find a basic description tutorial of how to get started.

Tutorial Document: Download the E+ GBI Production & GBS Retailer Case Model.

UPDATES & TUTORIALS

Here you can find a list of quick links that takes you directly to the tutorial page of each subject. Please find the list of tutorial subjects below: