GOST appeared in Russia, defining the format of the exchange of electronic documents
The main stumbling block for the widespread introduction of electronic document management in Russia so far has been the lack of uniform rules for the formation of documents for transfer from one EDS to another. Thus, there was no guarantee that an electronic document of one organization would be able to read correctly and even less use it in another. Now the situation has changed: the GOST with the long title “Electronic Document Management Systems. The interaction of document management systems. Requirements for electronic communication.
About why this GOST is so necessary and what it can change - under the cut.
Problems associated with the “inconsistency” of the SED affect us, as private users, and business, and government departments. For example, if various organizations (including government agencies) with which the company deals have installed various EDS, the company will not be able to automatically exchange electronic documents with these organizations.
Another example. We all want to use electronic public services in order not to waste time and energy on standing in lines. But if several departments should be involved in the provision of services, then the fulfillment of a citizen's desire becomes almost impossible - departments will not be able to exchange electronic documents, because each has its own EDS.
')
The scale of the problem is such that the document of one department in another could not only be processed, but often even read. So, the problem of compatibility of various EDMS has been very acute and long ago: they have seriously dealt with this problem since 2004, when a group of development companies under the auspices of the Documentation Managers Guild developed the first such standard - “Interoperability of document management automation systems. The composition, content and description of the zones of electronic communication. " It became the basis for the recently adopted GOST R 53898-2010 “Electronic Document Management Systems. The interaction of document management systems. Requirements for electronic communication.
What is done in GOST? First, the document areas are highlighted and their detailed descriptions are given. Secondly, the rules for the design of these zones and the composition of the elements in each of them are created. Also prescribed procedure for transferring document files. In general, it was possible to agree on the structure and format of requisites containing information about the document.
Sample code in the framework of GOST:
Now a few words about what the adoption of GOST will lead to. The most important thing is to facilitate the interaction of companies and departments: automatic registration and routing of documents sent to other departments, automatic notification of the status of work with previously sent documents, and so on will become available. Information losses will be reduced, and the developers of the SED, which we are just, this will greatly facilitate life, because you will not have to solve the problem of interaction with other systems every time - the cost of developing interfaces and connections between document management systems will decrease.
In general, there was a real opportunity to get rid of the "manual" processing of documents - automation will allow to reduce the time for passing documents, and save finances. In addition, those same electronic public services that have received so much attention lately will become more accessible and more diverse - this is what foreign experience shows.
Details of the GOST can be found at the link: www.pk6.eos.ru/upload/pk6/Pr_GOSTR_OR.pdf
About why this GOST is so necessary and what it can change - under the cut.
Problems associated with the “inconsistency” of the SED affect us, as private users, and business, and government departments. For example, if various organizations (including government agencies) with which the company deals have installed various EDS, the company will not be able to automatically exchange electronic documents with these organizations.
Another example. We all want to use electronic public services in order not to waste time and energy on standing in lines. But if several departments should be involved in the provision of services, then the fulfillment of a citizen's desire becomes almost impossible - departments will not be able to exchange electronic documents, because each has its own EDS.
')
The scale of the problem is such that the document of one department in another could not only be processed, but often even read. So, the problem of compatibility of various EDMS has been very acute and long ago: they have seriously dealt with this problem since 2004, when a group of development companies under the auspices of the Documentation Managers Guild developed the first such standard - “Interoperability of document management automation systems. The composition, content and description of the zones of electronic communication. " It became the basis for the recently adopted GOST R 53898-2010 “Electronic Document Management Systems. The interaction of document management systems. Requirements for electronic communication.
What is done in GOST? First, the document areas are highlighted and their detailed descriptions are given. Secondly, the rules for the design of these zones and the composition of the elements in each of them are created. Also prescribed procedure for transferring document files. In general, it was possible to agree on the structure and format of requisites containing information about the document.
Sample code in the framework of GOST:
<!--*********************************************************************** --> <!-- ******************************* «» ************************ --> <!--*********************************************************************** --> <xs:complexType name="DocumentType"> <xs:sequence> <xs:element ref="RegNumber"/> <xs:element ref="Confident"/> <xs:element ref="Referred" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="DocNumber" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="Addressee" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="DocTransfer" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="RegHistory" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="Author" maxOccurs="unbounded"/> <xs:element ref="Validator" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="Writer" minOccurs="0"/> </xs:sequence> <xs:attribute name="idnumber" type="xs:string" use="required"/> <xs:attribute name="type" type="DocumentEnumType" use="required"/> <xs:attribute name="kind" type="xs:string" use="optional"/> <xs:attribute name="pages" type="xs:unsignedLong" use="optional"/> <xs:attribute name="title" type="xs:string" use="optional"/> <xs:attribute name="annotation" type="xs:string" use="optional"/> <xs:attribute name="collection" type="CollectionEnumType" use="optional"/> </xs:complexType> Now a few words about what the adoption of GOST will lead to. The most important thing is to facilitate the interaction of companies and departments: automatic registration and routing of documents sent to other departments, automatic notification of the status of work with previously sent documents, and so on will become available. Information losses will be reduced, and the developers of the SED, which we are just, this will greatly facilitate life, because you will not have to solve the problem of interaction with other systems every time - the cost of developing interfaces and connections between document management systems will decrease.
In general, there was a real opportunity to get rid of the "manual" processing of documents - automation will allow to reduce the time for passing documents, and save finances. In addition, those same electronic public services that have received so much attention lately will become more accessible and more diverse - this is what foreign experience shows.
Details of the GOST can be found at the link: www.pk6.eos.ru/upload/pk6/Pr_GOSTR_OR.pdf
Source: https://habr.com/ru/post/109299/
All Articles