What is nsi in accounting. How not to go crazy when developing reference information management systems. From the history of our projects. Centralized management of regulatory and reference information with DATAREON

UDC 004.37.01

OH. Zhilyaev ,
Institute of Informatics and
problems of regional management
KBSC RAS, researcher, Nalchik.

Introduction

Creation of a unified information space is a necessary condition effective management various objects, be it an enterprise, department, region or state. The formation of a unified environment presupposes integration management processes, accompanied by the normalization of information flows. Often, the movement of information at different levels and parts of the control object is supported by various information and accounting systems. Accordingly, there is a need to integrate these systems. The growing processes of globalization of the world economy are, in essence, integration processes. Such integration tasks are especially relevant for Russia in connection with its upcoming entry into the World War II Trade Organization(WTO).

The task of integrating information and accounting systems consists of two interrelated parts: data integration and subsequent application integration. When performing data integration, it is necessary to unify and standardize regulatory reference information(NSI). .

Master data is a conditionally permanent part of all information in an information system (IS), in contrast to current information generated directly in the process of working in the IS. The master data includes: directories, dictionaries, linear and hierarchical lists, classifiers, registers, codifiers, data from which is used in the generation of current documents.

To denote such reference information in the English-language literature, the term Master Data (master data, master data) is used, and the tasks of managing it are called Master Data Management (MDM). However, in Russian the concept of normative reference information (RNI) is now more often used ), which has emerged in management disciplines national economy, back in pre-computer times. In this case, the definition of “normative” reflects the fact that the problem of creating directories must be solved taking into account industry, state and international standards.

If today such terms as, for example, ACS (Automated Control Systems) or IS (Information Systems) have become familiar, then the abbreviation “SU NSI” (Regulatory Reference Information Management System) often causes confusion. Even the meaning that lies behind its decoding is often understood only by specialists. NSI is not just a database, but a complexly organized system with many cross-references between individual directories and classifiers. The mechanism for maintaining the relevance of reference information is especially important. The requirements for the completeness, accuracy and relevance of information in the reference data system are much stricter than in a conventional database, since during the operation of any information system, including automated control systems, the information content of applied tasks depends on the reference data data. Master data is the “foundation” of the entire information system and management of this system should be centralized. In Figure 1, reference data is shown as the lower level, the “information foundation” of the entire IS structure.

Rice. 1 Information system levels

It is the centralized management of the reference data system, subject to unified regulations and provided by a unified technological environment, that allows maintaining the unification of data, completeness, integrity and relevance of all reference books and classifiers included in its composition. Therefore, to have an effectively working IS that solves real problems.

Development of a complete software for the management of reference data began only a few years ago. Leading software manufacturers have recently been paying more and more attention to master data management tools (in the English version MDM, Master Data Management - master data management).

It is difficult to imagine solving integration problems without centralized management of reference data. The problem of master data management arises even in such automated and information-supported structures as banks or Insurance companies. Master data management systems allow not only to accumulate data from several integrated banking systems, for example, to generate reports for several accounting systems; but also to solve the problems of operational management of reference data.

In Russia there is no single center for the formation of reference data similar to GOSTs. And, although new laws related to the development and circulation of electronic technical documents have recently come into force, they have not yet had a noticeable impact on the situation.

The role of NSI in the informatization of the region

An important role in the implementation of the sector’s development strategy information technologies in our country belongs to regional informatization. Recently in the regions Russian Federation Work has intensified on the use of information technologies in all spheres of life in the regions. This was facilitated by federal authorities state authorities of a number of events and adoption regulatory documents in the field of use of information technologies at the federal, departmental, regional and municipal levels. One of such documents, designed to help solve problems of comprehensive informatization of the region, is the Decree of the Government of the Russian Federation “On the procedure for the formation and use of basic classifiers, reference books and registers in the provision of government and municipal services V electronic form" dated 08/31/2010

A special role for reference data is also assigned to informatization programs for industries and departments. For example, in published on March 31, 2010. The draft Concept of Informatization of Healthcare especially emphasizes that information systems in healthcare should be designed taking into account standards and regulations and be based on a single master data. (The composition of the reference data used in the healthcare sector includes social development And labor relations The Russian Federation includes a total of 163 different classifiers and reference books)..

At the regional level, the goal of implementing the reference data infrastructure in automated management systems is the creation of a unified system of reference books and classifiers used in state (municipal) information systems ah of the subject of the Russian Federation, as well as the formation of basic accounting registers that ensure the collection and storage of provided information on the main objects of regional management. The master data management system, being a centralized repository and sole supplier a common reference data for all infrastructure and departmental information systems of the region should ensure information compatibility of local information systems and “electronic government” applications of the subject.

Obviously, the next step in the development of information technology in the Russian Federation should be the subsequent integration of departmental, regional and municipal information systems at the federal level. This task of integrating government information systems is so complex that in addition to standardizing documents (for example, based on XML) and integration infrastructure in the form of software, routing XML documents, government efforts are also needed in the field of standardizing data descriptions.

An example of an initiative in this area is the e-GMS (UK GoverNmeNt Metadata StaNdard) standard adopted in the UK. . Many countries have taken as a basis the so-called “Dublin Core”, which includes 15 elements of information description:

  • title;
  • author or creator;
  • topic and keywords;
  • description;
  • publisher;
  • other contributors;
  • date of;
  • resource type;
  • format;
  • resource identifier;
  • source;
  • language;
  • communications;
  • area (coverage);
  • rights management.

In addition to the elements themselves, the “Dublin Core” has so-called clarifications of elements, for example: “Date of creation”, “Date of publication”, “Expiration date”, etc. Countries can not only use this core, but also add any additional elements they deem necessary. In addition, the first tool when searching for information is usually browsing categories. Therefore, government metadata standards initiatives are defining standards for a list of categories (a primary search tool without the use of keywords).

conclusions

When familiarizing yourself with legislation aimed at regulating the provision of state and municipal services in in electronic format, and the organization of interdepartmental information interaction at the state and municipal levels, can be seen:

  • actual absence in regulatory legal acts mandatory for compliance with the requirements for standardization of information technologies and software used in government information systems necessary to ensure interdepartmental exchange of information;
  • the absence in regulatory legal acts of uniform clear requirements for directories, classifiers and data schemes of information systems used in interdepartmental information exchange;
  • the absence in regulatory legal acts of uniform and mandatory mechanisms for providing information and providing assistance to all federal, regional and municipal authorities public services electronic. .

Today, both in the Russian Federation and abroad, the main difficulty in implementing projects in the field of providing electronic services at the state, regional and municipal levels, as well as similar interdepartmental projects, is in conditions where significant efforts are required to integrate data and applications, consists not in the use of certain specific technologies, but in organizing the process of adopting relevant standards and harmonizing the information technology architectures of various organizations and departments.

Projects in the field of provision of electronic services at the state, regional, municipal and departmental levels, which are carried out by governments of different countries, provide for the following main types of standards:

  • data standards;
  • standards for interdepartmental information exchange;
  • metadata (and information retrieval) standards;
  • safety standards.

A unified modern methodology for maintaining master data is needed, otherwise, as the amount of data increases, the system will become unmanageable.
The regulations and methodology for filling reference books and classifiers must be spelled out in detail, otherwise it will be extremely difficult to ensure high-quality and orderly work of experts in maintaining reference data. There is a need for a clear delineation of the areas of competence and responsibility of users of reference data and experts in its management.

Highly efficient modern technology and reference data management system, problem solving multi-user access to it with the possibility of physical separation of powers, implementing the interaction of users with experts and ensuring easy scaling of the system when increasing both the reference data base and the number of serving experts.

Literature:
1. “Strategy for the development of the information society in the Russian Federation” (approved by the President of the Russian Federation on February 7, 2008 No. Pr-212);
2. Draft resolution of the Government of the Russian Federation "On the procedure for the formation and use of basic classifiers, directories and registers in the provision of state and municipal services in electronic form" dated August 31, 2010.
3. “Review of NSI”, Publication of the Ministry of Economic Development, 2010
4. "The concept of creating an information system in healthcare for the period until 2020", 2010.
5. Polotnyuk I."Metadata as a basis for integration", PC Week/RE (492), 2005.
6. Ray Wang, Rob Karel."Trends 2008: Master Data Management" 2008.

In the context of the transition to a digital economy, companies have finally become convinced that data is an asset that is important to properly store, process, analyze, use for making decisions and making forecasts. The efficiency of these processes is ensured by a single repository into which verified quality data must be loaded. The task of consolidating them from different sources involves collating and synchronizing directories in various IT systems. This is why businesses need regulatory reference information (RNI) management systems.

According to TAdviser, the volume of the market for master data management systems is about 1.5 billion rubles at the end of 2017. The demand for these solutions is growing by 20-25% per year - in direct proportion to the growth of business digitalization. The acceleration of dynamics is facilitated by the growth of penetration cloud services in the domestic market (at a level of about 20% per year), as well as the launch of initiatives for informatization of the state and society as part of the implementation of the program.

The general path to digitalization dictates the need for a unified knowledge base about customers, products, etc. For digital initiatives to succeed, data must be effectively managed and must first be brought together to formulate a reliable and accurate “single version of the truth” for everyone. structural divisions. Accordingly, there is a growing demand for data collation and consolidation tools that enable rapid access to information regardless of its source, analysis of patterns and anomalies, and secure distribution of data.

In Focus

Business representatives are becoming more and more demanding of the quality of reference data and its management processes. Questions about the quality of reference data also arise locally, among specialists. The more sharply the volume of data accumulated by organizations increases, the higher the requirements for the performance of information systems. The volumes of reference books are constantly growing. Modern solutions in the field of reference data management are expected to be able to support work with more than 1 billion records.

If 10 years ago, at the end of the 2000s, the tasks of reference data were more often understood as the process of migrating directories as part of the implementation of accounting information systems, then in 2018, businesses approach the tasks of managing reference data more consciously and structurally, with the involvement of functional departments that directly use this information in business processes. Tasks related not only to equipment and materials, but also to contractors and other reference data are clarified.

The current situation requires more high level automation and formalization: everything that can be “hardwired” into a clear automated algorithm must be formalized, because Without strict rules, work with reference data turns into chaos. Also, the involvement of various business departments in NSI projects increases their duration. As a solution, modern means of automating data quality using mechanisms come to the fore,” comments Bair Danilov, head of the reference data department at IBS.

As of 2018, up to 75% of this market comes from consulting and about 25% is occupied by licenses. This situation is due to the fact that in addition to the direct creation of the directory, companies need its integration with other information systems, and for customer directories - with personal data protection systems, Krok notes.

New trends

Among the “hot” global technological trends changing the reference data market, IBS experts note the expansion of the scope of directory management, i.e. management not only of basic data - contractors and materials, but also of a unified chart of accounts, production assets and other necessary reference books for key business processes of the enterprise. Also in focus is the automation of the process of checking reference data, including using machine learning technologies, the development of uniform standards for maintaining counterparties and materials, as well as the creation of digital ecosystems in which manufacturers and buyers can freely exchange transparent information about goods and transactions.

Improvement remains the defining trend. Machine learning technologies allow for higher-quality deduplication in an automated manner. In general, the development noticeably changes previously established approaches to working with reference data - the efficiency of data recognition and correction increases, the ability to use multimedia information is added, make data more visual, etc.

Today, not only economic giants, but also medium-sized companies are showing interest in the quality of reference data. IBS notes an increase in the number of requests for scientific research projects from the pharmaceutical industry, Food Industry, mechanical engineering and Agriculture. This interest is also spurred by import substitution initiatives - it is the introduction of NSI that makes it possible to solve the problem of phased and rational import substitution of foreign solutions.

Top 8 players in the Russian market of reference data management systems

Krok IBS SDI Solution "NCIT "Intertech" TaskData Lanit EAE-Consult Navicon
Revenue from NSI projects 2016RUB 135 millionRUB 99.9 millionRUB 63.3 millionRUB 51.9 million44 million rub.28 million rub.RUB 11.2 million7.5 million rubles.
Revenue dynamics for NSI projects 2016/2015 13% 6% 32% 50% 90% 10% -10% Height
Number of NSI projects 2017 4 7 7 6 completed, 2 in progress 6 5 4
Number of NSI projects 2016 4 in progress, 1 completed 4 7 4 5 3 4
Solutions/platforms usedCroc NSI Suite, Talend Platform for MDM, MDM, Informatica MDM, a number of Oracle systems, as well as the domestic Unidata platformSAP, Ataccama, own development (20%), 1C MDMproprietary development of Semantic MDM. DBMS Microsoft SQL Server, Oracle, PostgreSQL* own development - software platform for managing reference data systems Ontologic (registered in the Register of Russian Software No. 4114 dated December 11, 2017);

2. Mining and metallurgical company - creation of an Automated system for managing regulatory and reference information, development of a materials and equipment classifier, normalization of the materials and equipment directory and the directory of contractors. More than 2000 users. Based on SAP MDM, SAP PI, SAP Portal, SAP BPM.

3. Federal executive authority - Consolidation and cleaning of received information, integration of the solution into the corporate IS. Based on Informatica MDM, Informatica Power Center, Informatica Data Quality, Oracle BPM.

1. United Engine Construction Corporation - “Creation and implementation of a Corporate system for managing normative and reference information on the platform of the Semantic Reference Information Management System”

2. Development of an automated system for managing regulatory and reference information of JSC Kalashnikov Concern on the platform of the Semantic reference data management system.

3. “Development of an automated system “Management of electronic directories of an enterprise” for the needs of PJSC RSC Energia.

1. Design, implementation and commissioning industrial operation corporate system management of research and development information of the Inter RAO Group;

2. Creation of a Unified System of Regulatory and Reference Information of the State Oil Company of the Azerbaijan Republic (SOCAR);

3. Creation of a unified system for managing regulatory and reference information in the Company CJSC “ABI Product”;

4. Implementation of the master data management system (extended reference books) of PJSC MMC Norilsk Nickel;

5. Normalization of the Unified Directory of Materials and Equipment and mapping in the records of the Unified Nomenclature Directory as part of the project to introduce a unified concept for managing corporate master data of PJSC Polyus;

6. Creation of a methodological and regulatory framework for regulatory and reference information regarding the directory of material and technical resources and normalization of the directory of materials and equipment of Irkutsk Oil Company LLC;

7. Creation of a Unified system for managing regulatory and reference information of basic data of the Power Machines group of companies.

1. Industry center for the development and implementation of information systems (OCRS). The functionality of the first stage of ASOUP-3, which includes an Automated complex for maintaining reference data, has been developed.

2. Federal agency forestry (Rosleskhoz). Creation of a regulatory and reference information management subsystem (RNSI).

3. United Instrument-Building Corporation (UPK). A project to build a model of a reference data management system as part of the implementation of the “Network Integrated Settlement and Information Management System” (SIRIUS) project - a centralized procurement management system for the defense industry.

1. Development of an automated system for maintaining reference data in one of the largest banks in Russia (on the Microsoft platform using the NORMA reference data management system, Oracle database).

2. Development of a master data management system for Gazprombank (on the Microsoft platform using the NORMA master data management system, Microsoft DBMS SQL Server).

KSSS turn 8 - translation of directories to the IBM MDM platform, interfaces to the SAP PI bus, quality control of reference data;

Integration of KSSS with 1C DO - integration of the Counterparties directory with 1C systems in DO;

KSSS-NSI RREM - translation and creation of RREM directories on the IBM MDM platform, interfaces to the SAP PI bus. Oracle DBMS is used for the lower storage layer and for the master data mart.

1. Food Union (consolidation of reporting from several branches and production facilities, the ability to accept management decisions based on a constantly updated data set, implementation in the Microsoft Azure cloud environment).

2. Gazprom Gazenergoset (automation of loading aggregated data from the accounting systems of subsidiaries and dependent companies (SDC) into the corporate data warehouse (CDW) in the central office).

3. Specialized depository “Infinitum Specialized Depository” (optimization business processes in terms of maintaining regulatory and reference information, optimizing the architecture by creating a centralized master data repository, eliminating duplicates and double data entry)

The largest projects by number of directories in 2015-2017 1. Project 1. The volume of reference books is more than 30.

2. Project 2. Volume of reference books: about 20.

3. Project 3. The volume of reference books is more than 200.

1. Project of JSC "UEC". The volume of reference books is more than 20.

Integration of KSSS with 1C for SIP - 31 organizations of the LUKOIL Group;

KSSS-NSI RREM - PJSC LUKOIL and 4 NGDO

1. Specialized depository "Infinitum" (about 40,000).

While working on large-scale automation projects and creating new information systems, we were each time faced with the need to implement a subsystem for maintaining directories, classifiers, registers and other similar objects that make up the customer’s reference information (RNI). Over the 15 years of working at LANIT with data management systems, life has given us clients with a wide variety of requirements. And, of course, different situations arose on these projects. I will tell you about several instructive stories that happened to us. In the article you will find examples that will be useful to many who are involved in software development. Well, for those who work directly with the NSI, it will be even more interesting - their own shirt is closer to the body.

Special thanks to the wonderful artist Vasya Lozhkin for the illustrations.

Case one. How to load a wagon and small cart

Creation of a unified counterparty management system for a large production company with many factories throughout the country and abroad.

Objective of the project– create a unified database of counterparties for all divisions. Counterparty management is carried out on the basis of requests, which are assigned priorities from low to urgent. An urgent application must be processed by NSI experts within 2 hours, regardless of the time difference between departments.

Living history
The project was agreed upon with all interested parties (the customer's management convinced us of this) and developed within the given time frame in accordance with the approved requirements.

The presentation of the created counterparty management system went smoothly until one prominent woman stood up - the head of the Siberian branch - and very energetically, using Russian idiomatic expressions, brought to the attention of those gathered that when it comes to her Railway carriage for loading finished products, she will not wait 2 hours while someone there in Moscow considers the application to add a buyer.

She is not going to pay for the downtime of the car while the application is being approved, but will enter the buyer’s data into the system as is and ship the goods, and the Moscow comrades can then deal with the information about the buyer as much as they want.

This statement was supported by several more heads of the company's branches, which almost completely destroyed the centralized methodology of conducting single directory counterparties based on orders.

As a result, the project was modified in such a way that all branches had access to the counterparty database and could make changes to it directly, but at the same time automatic search similar records that were displayed to the branch employee, and he made a decision on the need to adjust the data, which was later checked by an expert group.

What we remembered: do not trust the words of managers and responsible persons on the customer’s side that all decisions have been agreed upon, everything is on topic and there are no objections. Identify all project stakeholders and try to find out system requirements and constraints directly from them.

Case two. We use it as we want

Creation of a centralized customer management system for an insurance company with a large number of branches and agents throughout the country.

Objective of the project– creation of a consolidated client base for use in analytical applications. The database was collected from all branches, the data was verified, supplemented, and duplicate objects were eliminated. The number of clients in one branch ranges from a thousand to several million. At the same time, there is practically no overlap in clients between branches.

Living history

Once a consolidated customer database was created, it had to be periodically compared with branch databases to identify differences, then process them and upload changes to the consolidated database. The growth of the client base between reconciliations amounted to several thousand records.

To perform the reconciliation, a special module was created, the architecture of which was designed based on the fact that it must quickly compare a large number of records and generate a relatively small XML file with changes for download. The XML format was chosen by the customer.

After implementing the system, we received a message from the customer that the reconciliation module works extremely slowly and generates a huge file for loading into the consolidated database, which they cannot open in any way.

What did it turn out to be? The customer carried out the initial loading of data from branches into the consolidated directory. The experts found this work tedious and time-consuming, and they simply took the reconciliation module and fed it with the complete data of the new branch, which had never been loaded into the consolidated directory.

The reconciliation module, which, in accordance with the technical specifications, was supposed to generate information about differences in the number of several thousand records, received two million records as input, and all of them were missing from the consolidated directory.

As a result, after several hours of superhuman effort, the reconciliation module nevertheless generated a file for downloading, which included all the branch data. And, yes, this file was huge.

The reconciliation module was not used by the customer for its intended purpose, but the customer liked the very fact that reconciliation allows for initial data loading, and he was going to continue working in this way, only he asked to significantly speed up the work of the module and do something with the created file so that it could be opened in a text editor.


In response to our objections that the reconciliation module is not intended for initial data loading, the customer happily showed the technical specifications and asked, where is it written here? We use it as we want!
As a result, we had to make changes to the architecture of the reconciliation module in order to process large amounts of data and generate an output file in CSV format, since the customer absolutely did not want to give up such a convenient tool.

What we remembered: Always include a description of the limitations in the specification - what your system should not do. Well, or create solutions that take into account all possible use cases, which is much more expensive.

Case three. Not a baby elephant, but an elephant, and it has to fly too

Creation of a centralized system for maintaining master data for a financial organization.

Objective of the project- creation of a centralized system for maintaining directories and classifiers with distribution of changes to interested systems and databases. Providing access to external systems to directories through the web services of our system.

Typically, customers have an average number of entries per directory from several hundred to several thousand. Our recent record holder is a directory that had 11 million entries. But this customer gave us a surprise. His directory contained over 100 million entries. We downloaded it for more than a day, because... During initial loading, many data checks were performed. It wouldn't be big problem, but the customer demanded that the directory download in a few minutes.

As a result, we had to greatly change the way the system works with this reference book. In fact, it is maintained outside the system, and we only provide an interface for its use. We are currently developing new ways for our system to work with very large directories. We hope the customer will like it.

What we remembered: In the modern world, there is more and more data, and its growth rate is constantly increasing. The system must be ready for high loads even where they were not initially expected. We are constantly developing our solution taking into account modern trends data growth and increased requirements for the speed of their processing.

Case four. Difficult trick with files

Creation of a centralized system for maintaining master data in a large bank.

Objective of the project– creation of a centralized system for maintaining directories and classifiers with distribution of changes to interested systems and databases. A special feature of the project is the very complex processes of propagating changes that affect many systems.

Since in the future I will have to mention our own solution to manage the NSI, I will allow myself a small lyrical digression.

Read more about the NORMA system.

The tasks of our customers are largely similar, and we decided to reduce software development costs and reduce project time by creating our own universal platform for maintaining master data and master data (Reference Data Management & Master Data Management). The system has existed for more than 10 years, and all these years we at LANIT have been actively developing it.

NORMA supports centralized and distributed reference data management. All data and meta-information are maintained taking into account the history of changes, and the system allows you to view and change the entire array of reference data for an arbitrary date in the past or future. Processes for coordination and approval of changes can be configured for directories. The system includes a dedicated change distribution server, which allows you to interact with external systems through various interfaces and create fairly complex integration business processes (a sort of mini BizTalk Server). We have data export/import packages that can upload/load directory data into databases and files of various formats. Maintaining conversion tables for external systems is supported.

NORMA includes a graphical query builder and report designer. In addition to working with its own directories, the system allows, through its interface, to view and change directories that are located in databases external to it, as well as use these directories in the query builder and export/import packages.

In response to the occurrence of various events in the system, for example, events of changes to the directory, plug-in software components written in C# can be launched, which can both check data and interact with external systems and, in fact, the NORMA system itself. Almost all system functions are available through web services.

The system can be scaled both vertically by increasing the power of the application server and database, and horizontally by using a multi-node application server, in which each node or group of nodes is responsible for performing a separate function. To store reference data, the system can use Microsoft SQL Server, Oracle or PostgreSQL.


Typically, when creating references and change propagation processes, the customer consults with our analysts about which tool or set of tools provided by the system is best to use for a particular task. This time the customer said that he would create directories and processes independently.

After some time, one of the customer’s specialists contacted us with a complaint that his data was not being loaded into the system. As confirmation, we were sent a data import package, a source file with the records being loaded, and an error message stating that the data being loaded was of the wrong type.

Let's start to figure it out. We twist the package this way and that, try it different variants presentation of the original data, but we cannot repeat the mistake. We contact the customer with questions: maybe the import package has connected software components, maybe some additional restrictions are imposed on the directory, maybe the data is not from this process? We get the answer to everything - there is nothing like that, everything should load easily and worked before.


It turns out that this import package was just the tip of the iceberg. Briefly and greatly simplified, the following happened. The import procedure loaded the correct data from source file to the directory. The original file was deleted. Our system then propagated the changes to multiple databases, one of which compared its own data with our changes and generated a discrepancy file that was returned to our system for download. Moreover, to download this file, the customer used the same import procedure as for the source file. And this particular file, generated by the external system, contained data of the wrong type. Obviously, when analyzing the original file, we could not find any errors, and we were not told anything about the second file and the sprawling process of distributing changes.

What we remembered: Always check the information you receive, even if they tell you that we have a little problem here, and it’s in this very place, I swear to my mother! Analyze the problem in context.

Case five. I'm getting used to the inconsistencies

Creation of a master data management system in a manufacturing company.

Objective of the project– creation of a system for maintaining reference data in management company with many branches, factories and design departments.

This time we did not progress beyond a few presentations. The techies really liked our NORMA system. She covered all their existing problems. Then it was the turn to show the system to management, and here the bummer of the decade happened. High leader looked, listened and said: “We all work here on Apple products, they have a certain style, but your system does not fit into this style. We won’t even consider it.”


What we remembered: Customers are different, and for some you are simply not suitable. The style is different.

Similar stories happen in various projects. What was interesting in your project life? What was an unexpected lesson for you? Share in the comments.

Tags: Add tags

In the 21st century, we have entered a period of development when it is absolutely impossible to imagine life without electronic computers and software for them, which help us in everyday life, increase the productivity of an individual specialist, and speed up the passage of time.

In our blessed and information age, a quick search for all questions that interest us is of great importance, from the method of opening a can without an opener to requesting a regulatory document at the federal level.

In our blessed and information age, a quick search for all questions that interest us is of great importance, from the method of opening a can without an opener to requesting a regulatory document at the federal level. Any legal action is accompanied by appropriate documentation. Therefore, there are even more such documents in the state document flow, because this area is quite large-scale.

Any reference and information base can be combined into one general name - regulatory and reference information. Of course, the system requires the presence of such employees who would work with it. Especially for this purpose, a department is created in the company, the work of which is entirely devoted to the fact that employees manage the reference data. Maintaining regulatory and reference information is a rather responsible matter that requires mandatory attention and high professionalism.

Regulatory and reference information is a complex of all information questions and answers to them that appear in various spheres of human life. Such a system consists of huge amount information that conveys all the necessary information from various areas of human life.

A good example for understanding reference data are special reference books information bases, representing a list of regulatory legal acts, decrees and laws. This type of work should be handled by a special department.

As a rule, such a reference book is needed by every specialist and institution that directly and on ordinary days are faced with the problematic issue of obtaining any legislative act. Everything legislative acts They are stored in reference books, there are quite a lot of them and it often happens that finding what you need is problematic. And the presence of reference data reference books (in addition to their classifiers) greatly simplifies the matter. Take, for example, the most common reference book of diseases, in which any person, based on specific symptoms, can approximately obtain the name of his disease, as well as methods and methods of treating it. NSI is also actively used to solve various problems that have a narrow specialization and are intended for specialists of a narrow profile. In other words, any organization must have a special reference data department, which, in turn, will deal with such matters as maintaining information, managing information, etc.

The master data usually includes the following information and analytical components:

  • reference books
  • classifiers, for example, such as OKDP, OKATU, etc.
  • various dictionaries

All this data as a whole represents a powerful tool capable of solving complex and multi-level problems.

Features and advantages of reference data

The set of normative and reference information is a fairly powerful tool for storing and high-quality systematization of information included in its components.

An important advantage of the master data system is the ability to create reports of any complexity, which helps to satisfy any, even the most complex user requirements.

In conclusion, we can add that master data systems are a powerful work tool that are simply necessary in any work processes of each enterprise, as well as in the work processes of federal and municipal self-government bodies.

H4 class="g-subhead">Definition of normative and reference information (RNI)

Regulatory and reference information enterprise is conditionally permanent information structured in a certain way, intended for the purpose of forming and describing business objects and business processes of the company.

Most often, regulatory and reference corporate information consists of reference books, regulatory documents, dictionaries, classifiers and other types of concepts designed to form a unified corporate information space.

The basis of the organization’s reference data consists of three main groups:

  • Information component. This includes classifiers, reference books and regulatory documents.
  • Software and hardware. This includes a set of software and hardware tools that are designed to collect, store and edit information. They are also designed to provide access to data.
  • Organizational support. This includes a system of regulations and organizational structure to maintain, control and support data analysis and transformation procedures.

Systems used to support reference information are currently in high demand among customers and project integrators. Russian large companies are trying not so much to acquire such systems as to take an active part in the development of their own software solutions this issue. Perhaps purchasing such a system will seem quite expensive to you, but believe me, it is worth it.

Reference data in organizations and firms

Companies that initially paid attention to the high importance of systems for supporting regulatory and reference information and invested in their development are already making good profits today.

There are several main reasons why managers of large companies try to use reference information systems in their organizations:

  • The need to integrate information systems, which, in turn, will significantly reduce the organization’s costs for a variety of processes for maintaining master data;
  • The ability to use a unified system of reference information codes - this will automate the generation of corporate reporting;
  • The ability to significantly increase the level of reliability and quality of regulatory and reference information by eliminating the possibility of data duplication;
  • Reducing the costs of obtaining and processing regulatory and reference information without losing the quality of this information.
1. Historical heritage

“The historical legacy of automation in large companies and holdings is in the vast majority of cases deplorable: individual systems and “systems” operate on different software platforms and use different local directories that are in no way connected with each other, which impedes information exchange and data consolidation. Many experts tend to use such metaphors as “patchwork automation” and “information zoo” in this situation. The key solution to the problem is the creation of a Unified System for Maintaining Regulatory and Reference Information, standardizing and unifying all information flows within the company.” (From the article by the President of NCIT “INTERTECH” D. E. Gulko “System of normative and reference information: typical errors and misconceptions”, published in the journal “ Gas industry"No. 6 in June 2004)

Experts from NCIT "INTERTECH" based on the results of the analysis of information systems used in large companies and government agencies Ah, we came to the following conclusions:

  • most of the application systems used are built on different software and hardware platforms;
  • application systems are not integrated with each other, they use non-standardized reference books that differ in structure and composition;
  • absent centralized system supporting user access to regulatory and reference information;
  • existing directories do not describe accounting objects fully enough, their names are not unified, and the coding system is not standardized;
  • When structuring large information arrays, classifiers are not used to facilitate the search for the required information.
2. Existing problems

Let us highlight some of the main problems of maintaining master data, which significantly increase the material and labor costs of many companies and government agencies to carry out important business processes:

  • consolidation of applications for centralized procurement and preparation of consolidated applications;
  • formation and execution of the budget in terms of logistics;
  • placing and monitoring the execution of orders, monitoring warehouse balances;
  • accounting and control of the movement of material flows throughout the supply chain;
  • formation and prompt provision of statistical and analytical information necessary for making effective management decisions.
3. Solutions

As a solution to these problems, INTERTECH proposes the creation of a Unified system for maintaining master data, linking all regulatory and reference information of the company's divisions, subsidiaries and partners into the general corporate information space.

To implement this solution you need:

Develop and adopt standards and regulations for maintaining reference data:

  • Company standard “Composition and structure of the Unified System for Maintaining Master Data, Classification and Coding Systems”.
  • Regulations for the use by divisions and subsidiaries of the Unified System for Maintaining Master Data, classification and coding systems.
  • Regulations for maintaining and maintaining the Unified System for maintaining reference data, classification and coding systems.
  • Regulations for ensuring access of company users to the resources of the Unified System for Maintaining Master Data and their technical support.

Use the ontological classification and coding methodology developed by INTERTECH specialists.

The methodology makes it possible to standardize the actions of expert specialists when they carry out operations to classify and encode groups (classes) of accounting objects, determine the properties (features) of classes and their values, and build navigation hierarchies.

The methodology includes a description of typical user requests, divided into groups according to the degree of uncertainty and inaccuracy of wording, and recommendations for the actions of support service specialists (experts).

Implement automated system, providing:

  • support for the accepted technology of classification and coding of information;
  • user access to the resources of the Unified System for Maintaining and Managing Reference Data – direct, through a web interface or through existing application systems;
  • work of support services for the Unified System for Maintaining and Managing Reference Data, classification and coding systems in accordance with the developed regulations.

4. Stages of work

Below are the main stages of work to create a Unified System for maintaining and managing reference data.

5. The essence of the approach

The proposed approach is based on the principles of evolution, adaptability, continuity, standardization and unification, accounting human factor.

Evolvability development of the system involves a step-by-step transition to modern principles of maintaining and maintaining corporate reference data. General scheme This approach looks like this: old -> old + new -> new, when at intermediate stages the parallel existence of the old and new systems is allowed.

Adaptability systems to the specifics and landscapes of existing application systems (including ERP-class systems), to the various classification and coding systems used, presupposes the ability of the system to integrate with external systems.

Continuity allows you to preserve all the best and valuable things that have been developed over years and decades. This concerns using the potential of reference data specialists, not disrupting the functioning of existing application systems, and the possibilities of migration and transformation of accumulated information arrays.

Standardization and unification regulations and methods for using and maintaining corporate master data, classification and coding systems, which allows us to ensure the constant relevance and availability of master data throughout the company.

Taking into account the human factor implies the ability to work in the system various categories users with different skills and “degree of advancement” in the field of information technology, ergonomic design and “friendliness” of system interfaces.

6. Software

Ontologic 4.6 is widely used by many major Russian companies as a platform for MDM solutions. On this platform, master data management systems (MDM) have been developed and implemented in companies such as TNK-BP, Tatneft, SIBUR, INTEGRA, Norilsk Nickel, Transmashholding, Transneft, GOZNAK, Polyus-Zoloto, NOVATEK, etc.

Taking into account the experience of such implementations, the INTERTECH company supplies ready standard solution for reference control system .

MAIN CHARACTERISTICS

6.1. Solution architecture

Composition of the solution components:

  • applications server;
  • database server;
  • integration module;
  • client applications (AWS).

Software used for the application server:

  • IIS 7.5 or higher;
  • .NET Framework 4.5

Software used for the database server:

  • Microsoft Windows Server 2008 R2 Standard or Microsoft Windows Server 2012 R2 Standard;
  • Microsoft SQL Server 2012 Standard or Microsoft SQL Server 2014 Standard;
  • .NET Framework 4.5.

Software used on workstations of users, experts, and administrators:

  • Operating system: Microsoft Windows 7/8/10, 32 or 64-bit;
  • .NET Framework 4.5;
  • Microsoft Excel 2007/2010/2013/2016;
  • Internet Explorer 11.

6.2. System functionality

Data search functions:

  • search by directory entry attributes (name, etc.);
  • search in text fields using word forms;
  • taxonomic search by properties/characteristics;
  • search through classifier hierarchies/navigator categories.

Functions for exporting and printing information about directory entries:

  • export data to external files in .xls, .txt, .mdb, .xml formats;
  • Printing of found directory items.

User functions for updating the directory:

  • generating/editing a request to add/change a directory item;
  • sending a request to add/change a position to the Reference Data Service;
  • monitoring the status of request processing.

Functions of an expert in maintaining reference data:

  • processing a request to add/change a position;
  • maintaining a class library (creating/adjusting hierarchies);
  • creating/changing positions in the directory;
  • adding documents to a directory position;
  • generating reports related to processing user requests and updating directories;

System administration functions:

  • settings of classifiers and reference books and connections between created tables;
  • editing the directory structure (adding/removing/changing the format of fields in a directory entry);
  • data export-import;
  • adding and editing functional user roles;
  • user registration, assignment of functional roles and user activation;
  • archiving data and restoring data from the archive;
  • audit of user actions;
  • setting up and monitoring the operation of system modules and components (including integration with application systems).

6.3. Information content

The solution comes with a pre-configured structure of directories and classifiers and loaded demo content. Includes:

MATERIALS (MTP):

  • Classifier with hierarchies and taxonomic sets of properties;
  • A directory with the following attributes: name of material, brand, specifications, links to the standard, to the Ontologic class, to a group of materials, etc.;
  • Auxiliary reference books (materials and equipment groups, units of measurement, etc.).

CONTRACTORS:

  • Directory of counterparties with the following attributes: names of the counterparty, INN, KPP, addresses, contact information, etc.;
  • Directory of banks.
  • Directory of settlement accounts of counterparties.
  • Auxiliary directories (organizational and legal forms, addresses, etc.).

CUSTOM DIRECTORIES AND CLASSIFIERS:

Using developed flexible configuration and administration tools, the Ontologic 4.6 platform allows you to create custom directories and classifiers of a given structure, including directories and classifiers of documents, accounting objects, etc. Flexible customization of existing directory and classifier structures is also possible.

6.4. Integration options

Solution integration tools on the ONTOLOGIC 4.6 platform allow you to configure various scenarios for replication of data updates from the EU reference data to customer application systems using integration buses (SAP PI/XI, IBM WebSphere, etc.) or file exchange.


7. Expected results from the implementation of the system
  • A centralized repository of regulatory and reference information, operating within the Company’s unified information space, and including the entire range of material and technical resources and other accounting objects at the Company’s disposal.
  • Centralization of functions for maintaining regulatory and reference information based on developed corporate classification and coding standards.
  • Unified regulations and technological environment for user access to reference data, maintenance and management of reference data by experts (classifier and directory) and technical support of the system by administrators.
  • Software built into the system that maintains the required level of data security and its constant updating, eliminating the storage of duplicate, erroneous or outdated information.
  • Integration of classifiers and directories of reference data into existing management, accounting and other systems, allowing to streamline and reduce costs for the processes of maintaining normative and reference information.
  • Promptly providing company management with the information necessary to make effective management decisions.
8. Why Intertech

INTERTECH is the developer and owner of a unique methodology and technology for constructing classifiers corporate level, OK software and complete databases, which allows comprehensively on a turnkey basis to solve all the problems described above.

INTERTECH is specialized company , the only one in Russia dealing with the problem of classification and unification of descriptions of industrial products, goods, works and services, at a high scientific and technical level, using modern effective technologies and methods of ontological classification. INTERTECH has state accreditation as a scientific organization.

INTERTECH has real implementations their decisions to build Unified systems maintaining reference data, classification and coding (ontological classifier).

INTERTECH leads full cycle design work – from consulting, including examination and analysis of existing information systems, flows and processes, development of recommendations for reengineering, development of a regulatory and methodological framework, to the development and implementation of turnkey systems.

INTERTECH introduced into its manufacturing process and uses quality management system in full compliance with the requirements of GOST R ISO 9001-2001.

INTERTECH actively interacts and coordinates work in the field of classification with the State Standard of the Russian Federation, the Ministry of Economic Development of the Russian Federation, the Ministry of Energy of the Russian Federation, the Ministry of Industry and Science of the Russian Federation, and the Chamber of Commerce and Industry of the Russian Federation.

INTERTECH has it all required licenses(FAPSI and the State Technical Commission under the President of the Russian Federation) for the right to work with information security systems on the territory of the Russian Federation.

The systems and solutions developed by INTERTECH have been examined and have positive reviews from a number of ministries and departments, including the State Standard of the Russian Federation, the Ministry of Industry and Science of the Russian Federation, High school Economics, Chamber of Commerce and Industry of the Russian Federation, RSPP, Russian Academy civil service(RAGS) under the President of the Russian Federation, etc.