Alee Software: KBNTI Corporate system of normative and technical information

Corporate system of normative and technical information

Characteristic of the used documents:

1. Variety (foreign and international standards, recommendations, managements, reference books; national standards of other countries, including Russian; industry standards; standards of the enterprise; specifications (external and internal); the additional or accompanying literature; the documents which are closely connected with standards, such as licenses, certificates, permissions and so forth documents; etc.)
2. Frequency of changes
3. Interrelation of documents
4. Sources of obtaining information
5. Importance of the document
6. Complexity of understanding and application

Architecture of KBNTI:

What questions are closed:

1. Creation of the uniform tool on work with all types of ND and the related documents
2. Transfer of non-key processes on support of base of external ND on outsourcing
3. the Organization of the tool for joint work as with external ND, and internal
4. Completeness and relevance of the used data
5. the Possibility of carrying out accounting of the available documents and the analysis of use of documents on the enterprises
6. Observance license politician of SDO
7. Providing new tools on work with documents (end-to-end full-text search, cuts and selections by different criteria, dynamically created structures and so forth)

Use of a system and examples of use:

A system is intended for large enterprises or concerns with a big variety of the applied regulating documents.

The relevance of a system consists in optimization of work and cost reduction (temporary and financial) on formation and service of base of regulating documents, exceptions of risks.

1. Pipe Metallurgic Company: works with a system since 2007, supports base of all of ND (including foreign and international) used at the plants of holding and also contains the documents connected with ND, such as certificates, permissions, licenses and so forth.
2. Existence of a system allowed Pipe Metallurgic Company to undergo certification in foreign certification authorities.
3. Kola MMC Company: works with a system since 2005, supports ND base of foreign and Russian ND and standards of the enterprise, it is integrated with support system of design documentation.
4. Arsenal Plant: works with a system since 2006, supports base of the Russian ND and standards of the enterprise.

Features:

1. the Possibility of support of any number of the documents entered as independently, and in the automatic mode by NORMDOKS company
2. Updating of descriptive (bibliographic) data on regulating documents as in the manual, and automatic modes
3. Updating of complete texts of regulating documents, as in the manual, and automatic modes
4. the Organization of a system of notifications of users for new receipts, changes of the status of the standard, emergence of changes and additions to the text of the standard, expiration and other important changes with regulating documents
5. Tracking of observance of licensing terms on each developer and even according to separate standards
6. Accounting of the printed copies of documents
7. the Organization of the different access levels to documents and functions of a system
8. Possibility of end-to-end difficult search (attributive and full text)
9. Support and tracking of a ssylochnost between documents
10. Creation of tasks with a possibility of tracking of discipline of execution

And other opportunities, such as adding of any functionality necessary for you and integration with already available systems, for example SAP, 1C, Documentum.

Advantages:

For end users

1. Simplification of formation of base of regulating documents and its support in current status;
2. Quick search of the necessary regulating documentation and creation of selections by different criteria;
3. Access to relevant documents from a workplace (via the browser or via the special interface);
4. Knowledge on all changes in regulating documents;
5. Simple work with a system and fast system learning at the expense of simple and usual interfaces.

For the organization

1. Reducing costs for support of several programs and databases on ND;
2. Simplification of maintaining classical paper archives of internal and external regulating documents;
3. Cutting of costs for search of necessary information;
4. Performance improvement of work and improvement of quality of work;
5. Consolidation of documents: the ordered centralized storage of all documents, including documents of branches and representations;
6. Storage of all documentation in the protected repository (storage) and a possibility of fast reservation of information;
7. Tracking of licenses according to documents for observance of license policy of external developers of standards.

For administrators

1. Fast deployment of software and its updates;
2. Simplicity of administration of a system which allows to release IT resources and to provide administration functions to heads of departments or divisions;
3. Reduction of load of IT personnel due to work of the browser system interface;
4. Simplicity of monitoring of system operation.

Specifications

1. Architecture
2. the Supported DBMS
3. Scaling
4. Migration
5. Technologies
6. Integration
7. Requirements to hardware and program parts

Architecture

The KBNTI system has three-unit architecture.

The client application (both are a complete client and the web client) does not contain data and logic of system operation. All logic of work with a system is on the application server. All these systems, except for files (electronic documents or their copies), are stored in DBMS. Electronic documents or their copies are located in the file structure having a certain structure.

Advantages of such architecture are obvious:

Security and security — the client application KBNTI has no direct access to data — only through functions of the application server.

Flexibility — and in terms of change of logic of system operation of KBNTI, and in terms of load distribution — links of a system can be placed on different hardware and thus load of a single element is reduced. For example, the application server and DBMS can be located on different servers, and the file structure to be placed on an independent RAID.

Low requirements to client computers due to accomplishment of resource-intensive transactions by the application server and solving now only problems of data visualization. Client applications of the KBNTI system represent the "thin" client who is not overloaded with data processing functions, and executes a role of information representation, arriving from the application server in a system. Client interfaces are implemented using standard means of Web technology — the browser and Java that reduces amount of data, transferred between the client and the application server and allows to connect client computers even on slow lines like express speaker circuits.

The supported DBMS

The KBNTI system works with different DBMS. At the moment we suggest the clients to select among the following list of bases: MySQL, MSSQL, Oracle and PostgreSQL. In the near future work with DB2 is planned.

Support of different DBMS is defined by use of Hibernate technology which allows a system to be independent in application of this or that DBMS and provides transparent support of safety of data.

It is impossible to tell that we recommend this or that DBMS in respect of the best work with the KBNTI system. Any of DBMS cannot be considered as the best or optimal variant. Selecting DBMS, we suggest you to select that from them which is given preference in your company or is defined by corporate policy, or the choice of which is defined by existence in the company of the specialist having experience with only from certain DBMS or, eventually, you subjectively incline to a certain base. In each choice there are pluses and the minuses and they decide by features of work of DBMS, but not system operation of KBNTI on this or that DBMS.

Scaling

The KBNTI system can work as on one server and, if necessary, to be scaled on several servers for load distribution from a large number of at the same time working users. A system supports both horizontal and vertical scaling that allows to increase to certain time high-speed performance of a system accumulation of computing powers and RAM of one server and at achievement of system restrictions to break a system into several independent servers. Any of KBNTI components – the DB server, the application server, a web the interface, image the server — can be carried on different physical servers.

Migration

The KBNTI system not only works at all main platforms and DBMS, but also allows to switch instantly between them. As data view does not depend on the operating system and the processor if you want to transfer, for example, the server with Windows to Unix a system, everything that it will be required to proinstallirovat software on the new platform. If you want to pass from one DBMS producer to another — rather simply to make the backup copy on an old DB and to recover it on new means of an archive system.

Technologies

KBNTI is the full-fledged enterprise-level system constructed based on JavaEE 5 technology. Thanks to the checked technologies, it with ease processes as 10 thousand and 10 million objects of a DB, at the same time servicing requests as 3 and 3000 users, without requiring at the same time the expensive specialized equipment.

Communications between components of a system happen on the bus of message exchange of the application server (Enterprise Service Bus), and work kliyenstky the application — by means of a web of services. Kliyenstky applications, including the complete client, work on almost any communication channels — for an ustnovleniye of connection with the server enough only the protocol resolved the HTTP server through a proxy and width of the channel of 512 kbps

And accomplishment of all logic the application server provides to technology of abstraction from a layer of data storage high portability and a broad spectrum of the supported DBMS

Web of service allow to make easy integration of third-party ICs and programs with an archive system and if necessary, to get direct access to data in a DB.

Integration

The KBNTI system is constructed by the principle of the three-unit IC and is full-function Enterprise the application working under management of the JEE application server that provides a wide range of possibilities on integration of third-party applications with a system:

1. Integration by regular unloading of information from KBNTI in external data files for their postprocessing in a third-party information system;
2. Direct access to tables of the KBNTI database;
3. Use a web of the services published by KBNTI;
4. WebSDK Use, for creation of own web applications working with data of KBNTI;
5. Use of Java connector KBNTI in own Java programs, a web and enterprise applications for gaining access to data of a system.

Requirements to hardware and program parts

Requirements to the hardware form proceeding from system configuration of KNTI (the selected modules and servers) and also proceeding from expected loads of a system in use and to the approximate volume of the stored data. The system software is selected from personal priobritet and the policy of the company.

Requirements to server hardware and to the software

1. Server components of an archive system (the application server, the Web server, DBMS, file storage) are established on a dedicated server with the recommended configuration and the following system software:
2. the Minimum clock rate of the processor — 2 GHz;
3. the Number of processors — 2-4;
4. the Minimum requirements to OZU — 16 GB (recommended — 32 GB);
5. Free disk space under a system — 1 GB, under data — settlement value;
6. Free disk space under data — settlement value;
7. the Operating system — Unix/Linux, Windows 2000, 2003, 2008 (64 bit) Server, MacOS X 10.5;
8. DBMS: MS SQL 2005/2008/2012, MySQL 5, Oracle 10, PostgreSQL 8 (in more detail about DBMS it is possible to read in the section "the Supported DBMS").

In case of an expected large number stored in an electronic data archive (from above 1tb) it is recommended to place file storage on an external RAID.

In case of high loads during the work with a system, such as attributive search, large number of the created cards and so forth) it is offered a) increase amount of RAM and b) carry the application server, DBMS on separate servers and (if is in delivery) such servers as OCR and Image of the server (the last — at a large number of recognizable documents). In more detail about scaling of a system it is possible to look at Scaling in the section.

Let's separately note that the KBNTI system does not impose strict requirements to use of servers or external storages of certain producers. It perfectly works as on the branded equipment, not at like that.

Requirements to a configuration local and Internet networks

Considering a network operation mode of a system requirements to lokalnyym are imposed on networks or the Internet, in case of remote work with a system:

1. Network protocols — TCP/IP;
2. Capacity of communication channels — 100 Mbps.
3. Requirements to client hardware and to the software
4. K is not imposed on workers by stations of readers any requirements.
5. Workstations of editors should meet the following conditions:
6. Display resolution not less than 1024х768 pixels (for the most comfortable work it is recommended to use permission in horizontal direction from 1280 points and large-format screens);
7. Not less 1Gb RAM;
8. Not less than 10 GB of an empty seat on the hard drive;.
9. the Operating system — any.

KBNTI in a cloud

What the base of the specifications and technical documentation of the company consists of

1. Various ND (foreign and international standards, recommendations, managements, reference books; national standards of other countries, including Russian; industry standards; standards of the enterprise; specifications (external and internal); the additional or accompanying literature)
2. the documents Interconnected with standards, such as licenses, certificates, permissions and so forth documents

These documents can be:

1. Acting, cancelled, replaced
2. More and less significant in a company performance
3. Capacious, difficult and simple in understanding and use
4. Often changing and without accurate modification time
5. Written in different languages

As we want to work with ND base

Accurately know what documents are used by the company or all companies in holding

1. the List of documents (by numbers, subjects, SDO, etc. to criteria) — accounting
2. the Status of the document — relevance
3. Interrelation between documents — influence
4. Notifications at changes in documents — awareness
5. Users of standards — use
6. an acquisition Source — legitimacy
7. the Rights to use (single-user or network) — "legal purity"
8. Maintenance of lifecycle of ND (creation, approval, change acceptance) — process

Evolution of work with the specifications and technical documentation

Local storage and use: we buy the single-user license, we make the paper copy, if necessary we report it (is copied) to other person.

Network storage: Are placed by the specifications and technical documentation in the shared or network folders, are available to almost instantly large number of users.

Use of the centralized information systems storing everything ND used in the company (holding) with necessary functions for work with regulating documents.

KBNTI in a cloud

Scheme KBNTI

The specifications and technical documentation from "KBNTI cloud"

Foreign standards in the Russian legal-reference systems (LRS)

ANY Russian legal-reference system has no right to sell network licenses and to place foreign standards in the information systems. If it occurs, require supporting documents (allowing letters and agreements with SDO).

Service cost

For an example we will consider the thematic collection from 200 standards of ASTM company.

The cost of an annual license subscription for this collection in the version of Plus (including the cancelled standards and the option RedLine), is specified in the table:

Who needs it?

1. to Active users foreign specifications and technical documentation
2. to All who need to provide access to standards more than to one employee

What is necessary for a start?

1. to Send the list of the interesting regulating documents
2. to Purchase the network license to use of these documents
3. to Sign the service contract KBNTI in "cloud"