Decree No 57 / 1986 Coll.
Decree of the State Commission for Scientific, Technical and Investment Development on the Construction of Automated Management Systems
Valid
Effective from 01.11.1986
Zobrazeno prvních 200 z celkem 233 ustanovení tohoto předpisu.
Zobrazit celý předpis →
Pro stažení celého znění použijte tlačítko Stáhnout výše.
57
DECLARATION
State Commission for Scientific, Technical and Investment Development
of 18 August 1986
on the construction of automated steering systems
The State Commission on Scientific, Technical and Investment Development provides, pursuant to § 53 paragraph 1 (b) of Act No. 133 / 1970 Coll., on the jurisdiction of federal ministries, as amended by Act No. 115 / 1983 Coll.:
INTRODUCTORY AND GENERAL PROVISIONS
Subject matter and scope
(1) The Decree regulates the way in which automatic management systems are to be prepared, tackled, implemented and innovated1 (hereinafter referred to as "building") in all public administrations and socialist organisations (hereinafter referred to as "organisations"); determine the scope of their documentation and the procedure for its discussion, approval and amendment.
(2) The documentation of automated process control systems built within the framework of the construction shall be processed, discussed, evaluated and approved in accordance with this Decree, unless otherwise specified in the Specific Regulations (2).
(3) The Decree does not apply to automated control systems built for foreign users.
Terms
(1) The automated management system (ASR) is a management system in which selected activities and processes are automated using computer and other techniques and in which scientific management methods are applied simultaneously. ASR is divided into subsystems and their integrated parts capable of independent use. It is developed for individual stages of management and for individual special-purpose activities and proces.3)
(2) The ASR designer is an organization that solves ASR and produces its project documentation at least within the scope of the initial ASR project and performs the author's watch.4) If an agreement has been reached when discussing the preparatory documentation of ASR that the project documentation following the initial project of ASR is processed by the ASR user or supplier for ASR, the designer ASR ensures consistency between the different parts of this project documentation of ASR.
(3) An ASR supplier is an organisation which, in accordance with the specific regulations (5), supplies equipment or provides work and services related to the construction or use of ASR, its subsystems and their integrated parts.
(4) The user of ASR is an organisation that is responsible for the construction of ASR within its scope 6). It designates the organisational services which are obliged to participate in the building of ASR and to use ASR according to approved documentation. If the ASR user is also an ASR designer at the same time, the organizational services that perform the function of ASR designer in the organisation shall be determined.
Principles of ASR Building
(1) The building of ASR is managed by the central authorities under their responsibility in accordance with the medium and implementing economic plans for the development of the national economy. In the area of national committees and bodies managed by them and managed by them, automated management systems shall be built within the framework of the automated information system of national committees. The Ministry of the Interior, in order to ensure the governance and control role of the Government in relation to national committees, directs the organisation of the information system of national committees. 7) The central authorities shall entrust subordinate bodies and organisations with tasks in the management of ASR building. If required, use national, 8) sector9) or branch head of the ASR.
(2) ASR is built under conditions such as:
(a) one-level (for one degree of management, purpose or process); or
(b) as multi-level (for senior and subordinate stages of management, for continuous special-purpose activities and processes); in this case, the authority or organisation of the highest of the management stages concerned shall ensure the consistency of the ASR building at all subordinate stages.
(3) The stage of the procedure referred to in paragraph 2 shall be understood as: 8)
(a) central authorities;
(b) economic management bodies acting as central management bodies, 10)
(c) the organisation. 10)
(4) The ASR user may, as his advisory body, set up an ASR Building Commission on essential issues of ASR building and evaluation of the results achieved.
(5) Where the construction of ASR requires conditional measures consisting of:
(a) acquisition of a building or modification of a building, 11)
(b) acquisition or modification (modernisation, reconstruction) of machinery and equipment not included in the budgets of buildings, including construction and (or) assembly works, 12)
in addition to the ASR documentation (according to Part Two), the documentation for these measures shall be processed in accordance with a separate Regulation. 2) The investor of the conditional measures is usually the user of ASR.
(6) In the cases referred to in paragraph 5, the ASR designer shall be responsible for the substantive and temporal compliance of both documentation.
(7) The institutions and organisations involved in the construction of ASR are required to ensure the protection of classified information under specific regulations. 13)
Use of type solutions
(1) The user and designer of ASR are obliged to take care to reduce the workload of ASR building and improve the quality and unification of ASR, subsystems and their integrated parts, in particular by using type solutions.
(2) Type solutions are repeatedly usable project documentation ASR and software.
(3) The authorities which, pursuant to Article 3 (1), manage the construction of ASR shall provide:
(a) the object and scope of the type-solution, including the procedures for its approval and the range of users of the type-solution;
(b) an organisation that will be the designer of the type solution, or an organisation that will provide, maintain and update the type solution and provide downstream services.
(4) Type solutions available for use in each sector are registered with the relevant industry head of the ASR, 9) National type solutions for designated organisations. 14)
Efficiency of ASR
(1) Efficiency of ASR means the relationship of benefits to costs incurred for the construction and use of ASR.
(2) Benefits are derived from positive changes in indicators characterising the activity of ASR users. The selection of indicators and how they are assessed shall be determined by the central authorities (Section 3 (1)) according to the conditions in their departments.
(3) The calculation of the efficiency of ASR is one of the criteria by which:
(a) on the basis of the expected positive changes to the indicators, assess the need to build ASR when approving the preparatory documentation of ASR;
(b) on the basis of positive changes in indicators achieved by the introduction of ASR, the ASR shall demonstrate the effectiveness of the ASR when approving ASR.
DOCUMENTATION ASR
Breakdown of ASR documentation
(1) ASR documentation is divided into the preparatory and project documentation ASR.
(2) The preparatory documentation of the ASR is a project task; in the cases referred to in § 3 (5), the preparatory documentation shall also include the documentation referred to in the special regulation.2)
(3) The project documentation ASR contains an initial and implementation project or a one-stage project.
Project task
(1) Project task is provided by ASR user.
(2) The project task is initiated at the initiative of the ASR user or at the decision of his superior body.
(3) When an organization other than an ASR user is considered as an ASR designer, the ASR user is entitled under the conditions agreed in advance (15) to require from the ASR project designer considered data and documentation for processing certain parts of the project task (in particular for calculating the costs of the ASR solution, processing of project documentation and the design of the plan).
(4) The content of the project task is set out in the Annex.
Purpose of the project task
(1) The project task defines ASR and the range of management improvement problems solved within a specified time period, justifies the need for automation in ASR management or innovation and provides in particular:
(a) ASR objectives and requirements for its solutions, including the use of type solutions;
(b) the framework design and structure of the ASR, including links to the continuous stages of management, special-purpose activities and processes and surrounding systems, evaluation of possible options for solutions;
(c) requirements for technical, programme and other necessary equipment of ASR, design and evaluation of possible variants of technical and software equipment, including requirements for the working environment;
d) method of security of ASR solution and processing of ASR project documentation (§ 2 (2) and § 10 (1)), method of cooperation of ASR user or suppliers for ASR project documentation processing ASR,
(e) a proposal for an ASR-building procedure including, where appropriate, a proposal for conditional measures pursuant to Article 3 (5);
(f) calculation of ASR efficiency,
(g) method of ensuring the use of ASR.
(2) For multi-level ASR, one project task is to set the ASR objectives of each level of management and their interlinks.
(3) The project task serves as a basis:
(a) the decision to build the ASR;
(b) to ensure the building of ASR within the framework of the plans of the institutions and organisations building ASR, including the provision of the necessary resources;
(c) to safeguard the conditional measures referred to in Article 3 (5);
(d) to identify the ASR designer or, where appropriate, to conclude a contract for the delivery of the ASR project documentation or of the supporting measures (§ 3 (5)).
Project task discussion
(1) During the work on the project assignment, the ASR user is required to discuss the scope and form of their deliveries with the ASR suppliers and the ASR designer the method of cooperation on the ASR project documentation including the provision of documentation for this documentation.
(2) The documents with the conclusions of the discussion referred to in paragraph 1 shall be attached to the project task.
(3) If the project task is discussed in conflict, the discrepancy in the annex to the documentation submitted for approval shall be expressed.
(4) The authority responsible for approving the project task shall decide on the way in which the discrepancies arise to be removed (Section 15).
Project documentation ASR
(1) Project documentation ASŘ16) is created in accordance with the procedure of the ASŘR solution from whole to parts. An initial project is used to document the overall solution, and an implementation project is used to document the detailed solution. A single-stage project is a simplified project documentation replacing the initial and implementation projects. Depending on the conditions under which ASR is built, one of the following methods of processing ASR project documentation is chosen:
(a) the initial and implementation project or the one-stage ASR project as a whole;
(b) the initial ASR project as a whole and for sub-systems (their integrated parts) either the initial sub-system project and the implementation of the sub-system project (its integrated parts) or the one-stage sub-system project (its integrated parts).
(2) In particular, the following aspects are crucial for the selection of the method of processing the ASR project documentation: the scope and structure of ASR, the degree of innovation of ASR, the degree of use of type solutions, the need for a gradual monitoring of the ASR solution process and the approval of its documentation.
(3) The use of type solutions can only be marked in the ASR project documentation by reference to the type solution used and by describing how it is incorporated into ASR. The type-solution documentation becomes part of the ASR project documentation.
(4) A multi-level ASR is documented by one initial project or, where appropriate, separate initial projects for each stage of management.
(5) The work on the project documentation ASR is usually started after the project task is approved.
(6) The content of the ASR project documentation is set out in the Annex.
Purpose of project documentation ASR
(1) The ASR project documentation documents the ASR solution in the details necessary for the implementation of ASR. It defines:
(a) the function, scope and effects of ASR (its technical and economic parameters);
(b) the structure and links of ASR,
(c) the content and procedure of management activities under ASR conditions;
(d) the organisation and use of the ASR data base;
(e) technical and programming solutions of ASR;
(f) the manner and conditions of implementation, use and changes of ASR, including related organisational measures.
(2) The ASR project documentation serves as:
(a) the basis for the management of the ASR-building process and, where appropriate, for securing the conditional measures referred to in Article 3 (5);
(b) the basis for the conclusion of economic contracts with suppliers for ASR, unless they have been concluded on the basis of an approved project task or where appropriate for the adoption of the necessary measures.
Consultation of project documentation ASR
(1) The ASR designer is obliged to discuss during work on the ASR project documentation:
(a) a list of works and supplies to be provided by the ASR user when the ASR is implemented; If not for a one-stage project, also a list of works which the ASR user must carry out during the process of implementing projects, including, where appropriate, the provision of conditional measures (Section 3 (5)),
(b) with suppliers for ASR for the purposes of processing the ASR project documentation, a specification of the scope and form of supply envisaged (Section 9 (1)).
(2) The documents of discussion referred to in paragraph 1 are attached to the ASR project documentation.
(3) If the ASR project documentation is discussed in conflict, the discrepancy in the annex to the documentation submitted for approval shall be expressed.
(4) The authority responsible for approving the ASR project documentation shall decide on how to remove the discrepancies arising (Section 15).
PURPOSE AND STATEMENT OF INSTALLATION
Purpose and content of introduction of ASR
(1) The purpose of the introduction of ASR is to prepare and transmit to the use of ASR, its subsystems and their integrated parts capable of independent use.
(2) The introduction of ASR includes:
(a) preparation of the ASR user for the introduction of ASR into use, including the necessary cadre, organisational and technical measures;
(b) setting up the ASR data base;
(c) verification of the competence of ASR, subsystems and their integrated parts for use;
(d) definition of scope and provision of work and services related to the use of ASR provided by the supplier for ASR, 4)
(e) transfer to use.
Procedure for implementation of ASR
(1) ASR, subsystems and their integrated parts are implemented by ASR user in cooperation with the designer and with ASR suppliers.
(2) The ASR designer carries out copyright supervision during the implementation, in particular:
a) verifies the achievement of the specified technical and economic parameters of ASR and compliance with the organisation of management and implementation activities by the ASR user established by the ASR project documentation;
(b) express its views on the possible non-compliance with the technical and economic parameters and organisation of management and implementation activities and submit proposals to the authorising authority for the necessary measures;
c) assess proposals for changes to the ASR project documentation resulting from the implementation of ASR;
d) ensures consistency between the different parts of the project documentation ASR.
(3) During the implementation, the ASR user organises a gradual verification of the functionality of the subsystems, their integrated parts and ASR as a whole in operational conditions, including verification of the necessary extent of the data base. The user of ASR also organises operator training and carries out the necessary measures to achieve the planned technical and economic parameters.
(4) The results of the verification and take-over shall be written by the ASR user and the ASR designer, in which he shall evaluate the eligibility of the certified subsystems, their integrated parts and ASR as a whole for use (hereinafter referred to as the "verification registration '), in so far as the supply cases for ASR are not covered by the transfer and take-over of which the registration shall be drawn up in accordance with specific regulations. 5)
(5) The content of the verification note is set out in the Annex.
APPROVAL AND AMENDMENTS
Approval of ASR
(1) Approval means the decision on the need to build an ASR and, where appropriate, the accuracy of its solution and the decision on the ready-to-use ASR.
(2) Approval shall be subject to:
(a) project task;
(b) project documentation of ASR, unless otherwise specified below;
(c) registration of verification,
(d) change of ASR.
(3) The approval authority is:
(a) the ASR user, if it is a project task of ASR of the central authority, its changes and the verification of ASR of the central authority,
(b) the superior body of the ASR user, if other project tasks are involved, changes pursuant to Section 16 (3) and entries of the ASR verification,
(c) the ASR user, if it is the ASR project documentation and changes pursuant to Section 16 (4), or the entries for verification of subsystems and their integrated parts.
(4) The central authority or the competent authority of the ASR user may, for the cases referred to in paragraph 3 (a). (c) determine that approval shall be waived or designate another authorising authority.
(5) The document subject to approval in accordance with paragraph 3 (b) shall be submitted for approval by the ASR user.
(6) The authorising authority shall provide for a comprehensive assessment and evaluation of the documentation submitted, a verification note or a draft change; in the case referred to in paragraph 3 (a), request an opinion from the national head of the ASR and, in the case referred to in paragraph 3 (b), from the relevant sectoral or sectoral head of the ASR. It shall also establish the procedure, form and manner of the approval procedure, unless otherwise specified by the central authority.
(7) In the assessment and evaluation referred to in paragraph 6, the authorising authority shall, where appropriate, take into account:
(a) the current state of the management system and the effectiveness of the introduction or amendment of the ASR;
(b) performance of tasks arising from documents relating to management development (e.g. a comprehensive management development programme);
c) quality of the ASR solution and feasibility of the proposed solution, possibly to comply with technical and economic parameters from previous approved ASR documentation;
(d) the reality of the financial and material requirements;
(e) cadre security for the building and use of ASR;
(f) options and scope for the use of type solutions;
(g) the effectiveness of ASR.
Amendment of ASR
(1) If there is a need at any time after the project task has been approved to change the existing results of the ASR building, the amendment shall be made on the basis of the design of the change and its approval after the previous assessment (§ 15) and shall be reflected in the ASR documentation.
(2) The change of ASR may be proposed by the designer, user or supplier for ASR.
(3) Changes that alter the scope of ASR, the dates of transmission of systems and subsystems into use, the effectiveness of ASR, the computer system and the date of its entry into service are approved by the superior authority of the user, if not the ASR of the central authority. The draft amendment shall be submitted for approval by the ASR user.
(4) Other amendments are approved by the ASR user (Section 15 (4)).
(5) The procedure for the processing, assessment and approval of amendments shall be determined by the authority empowered to approve the amendment.
FINAL PROVISIONS
Transitional provision
The ASR documentation prepared on the effective date of this decree shall be completed in accordance with this decree, unless the State Commission for Scientific, Technical and Investment Development provides otherwise on a proposal from the central authority of the ASR user.
Repeal
They shall be deleted:
1. Methodological Guidelines of the Federal Ministry of Technical and Investment Development, the Ministry of Construction and Technology of the Czech Republic and the Ministry of Construction and Technology of the SSR for the Construction of Automated Sector Management Systems No. 7770 / 31 / 74, announced in the amount of 26 / 1975 Coll.
2. Methodological guidelines of the Federal Ministry of Technical and Investment Development, the Ministry of Construction and Technology of the Czech Republic and the Ministry of Construction and Technology of the SSR for the construction of automated corporate management systems no. 14243 / 31 / 73, notified in amount 30 / 1973 Coll.
3. Addendum to the guidelines of the Federal Ministry of Technical and Investment Development, the Ministry of Construction and Technology of the Czech Republic and the Ministry of Construction and Technology of the SSR for the construction of automated corporate management systems no. 1402 / 31 / 75, announced in the amount of 26 / 1975 Coll.
4. Methodological guidelines of the Federal Ministry of Technical and Investment Development, the Ministry of Construction and Technology of the Czech Republic and the Ministry of Construction and Technology of the SSR for the construction of automated technology process management systems no. 25567 / 31 / 75, announced in the amount of 7 / 1976 Coll.
Efficacy
This Decree shall take effect on 1 November 1986.
Deputy Prime Minister of CSSR and Chairman of the State Commission for Scientific, Technical and Investment Development:
Doc. PhDr. Obzina DrSc. v. r.
Annex to Decree No 57 / 1986 Coll.
SUMMARY OF DOCUMENTATION AND ASR
1. Project task
It defines and rationalises the ASR and the requirements for its construction in detail for the decisions on the construction of ASR and for the preparation of the initial (one-stage) project.
Sign in for notes, favorites and notifications
Regulation Information
| Citation | Decree of the State Commission for Scientific, Technical and Investment Development No. 57 / 1986 Coll., on the Construction of Automated Management Systems |
|---|---|
| Regulation Type | - |
| Author | - |
| Collection | Code of Laws |
| Date of Promulgation | 26.09.1986 |
|---|---|
| Effective from | 01.11.1986 |
| Effective until | - |
| Status | Valid |
The regulation text is for informational purposes only.
Comments 0