Iem

The IEM concept was first formulated ^{[1] [2] by the} partner of Ultima Consulting in 2017 as a systematic response to business requirements for transforming ERP from an information system to a managing one, implementing the principle of direct one-time automatic input and reuse of information in the system, implementing the principle of self-service, and also automatic execution of production and business processes without the direct involvement of personnel. A more formalized definition is given in the journals Modern Science ^[3] and Research in Social Sciences and Technology ^[4]

The IEM paradigm formulates requirements for both IEM systems themselves and the methodology for their implementation in a particular enterprise and its further operation.

Exceptional Uniqueness and Inclusiveness

Without exception, all value chains (business process blocks) of an automated enterprise are included in the IEM system circuit and are managed in exclusive mode.

IEM is the only enterprise system that encapsulates its business processes, manages them, and completely replaces the functionality of the currently used ERP, CRM , WMS , MES and other narrowly functional systems.

Compositional Dualism

The complexity and nonlinearity of the requirements for the implementation of the IEM system, stemming from the principle of uniqueness and inclusiveness, lead to the second, technological, imperative of IEM: internal duality.

Integrally unified and all-encompassing, from the point of view of the operator, the system from within is a superposition of two separated parts of the opposite nature and purpose: the IEM platform and the business logic space (BLS).

The platform (the core of the system) provides the background functioning of low-level mechanisms of the system.

BLS implements the electronic abstraction of the operating company: the electronic analogues of offices, warehouses, employees, goods, money and other really existing objects "live" there, from the interaction of which the work of any organization is formed.

System External Circuit Requirements

They flow from the requirement of exceptional uniqueness and inclusiveness of IEM.

• Orderliness

Orderliness requires the standardization of all business processes introduced into the system circuit, without exception.

• Symmetry

The abstraction of the IEM system implements a symmetric, one-to-one projection of a real enterprise, its virtual model, evolving in synchronism with the managed enterprise.

All significant parameters of the enterprise are recorded by the virtual model, and vice versa, changes in the parameters of the virtual model are reflected in the real enterprise in real time.

• Integrity

Integrity (monolithic or highly connected) guarantees the reliability of the data of the IEM infocontainer in the mathematical sense: either all system data are reliable, or they are all unreliable at once.

• Enclosure

All interpreted information on the progress of the company's business processes is recorded in the IEM system. The company operates inside a dense information shell that absorbs all information about significant events.

• Versatility

Universality of IEM functionality: for solving any formalized task within the framework of organizational process management, replacing all other private systems.

The logic of internal organization

• Closeness

The closed IEM platform isolates complex infrastructure functionality within itself.

• Invariance

The invariance of the IEM platform, the heaviest part of the IEM system that implements the most complex and potentially risky functionality, is designed to significantly facilitate both the actual support of the operating system and the application development for it.

• Openness

The business logic space is completely open to the application developer.

• Mutability

The Business Logic Space (BLS) is a fully open and arbitrarily modifiable and complemented area of ​​IEM.

The BLS configuration of each operational IEM system is unique and tailored to the needs of the particular operator.

Business Logic Space (BLS)

• Rich data model

Automated enterprise is described by high-level abstractions

• Commonly developed programming language

A modern, universal, open development language with broad community support.

IEM Platform

• Multifunctionality

The platform encapsulates the heavy functional of the invariant core of the IEM.

• Centralized data storage

The data are presented in a single copy for the entire information space of the enterprise. Data is entered once and reused. Direct data entry through automatic input from smart sensors, sensors, scanners and the Internet of things.

• Close integration of the platform with selected DBMS

Tight integration with optimal DBMS with maximum use of the most powerful and modern data processing tools of the latter. The level of integration is high enough to logically interpret the DBMS and the IEM platform as a whole.

• Single information field. All users of the system work online with equally current data.
• Real time transactions
• Automatically executable scripts for processing high-level business objects of unlimited complexity
• Continuous consistency and reliability of data, allowing you to use them for analysis by Big Data, BI, Data mining in real time without additional filtering and normalization procedures
• A wide market for low-cost developers due to the use of a modern, widespread programming language for application development
• Omni-channel in the environment of a single information field IEM with real-time transactions is implemented naturally without additional effort

IEM Community https://iemcommunity.ru