Institutional Capacity Building Project

REQUEST FOR EXPRESSIONS OF INTEREST
(CONSULTING SERVICES – FIRMS SELECTION)

 

Uzbekistan

Institutional Capacity Building Project

Credit No.: IDA 6431-UZ

Assignment Title: Development and Implementation of an Automated System of Accounting and Monitoring for the Activities of Enterprises with State Participation

 

Reference No.: UZ-MOF-SAMA-QCBS-SYSTEM

 

The Ministry of Finance of the Republic of Uzbekistan has received financing from the World Bank toward the cost of the Institutional Capacity Building Project and intends to apply part of the proceeds for consulting services on behalf of the State Assets Management Agency (UzSAMA).

The Consulting services (“the Services”) include Development and Implementation of an Automated System of Accounting and Monitoring for the Activities of Enterprises with State Participation (“Information system”)

The main purpose of the information system for accounting and monitoring the activities of enterprises with state participation is an organized data array of the UzSAMA, processed in a single hardware and software complex, which provides quick access to operational and historical information, multidimensional data analysis (KPIs for various dimensions), obtaining forecasts and statistics in terms of both the activities of the Customer and enterprises with a state share, regardless of the source of such information.

The Ministry of Finance of the Republic of Uzbekistan now invites eligible consulting firms (“Consultants”) to indicate their interest in providing the Services. Interested Consultants should provide information demonstrating that they have the required qualifications and relevant experience to perform the Services submitting directly to the piu_mof@mail.ru.

The qualification requirements for the Consultants are:

• General experience in implementing the consultancy contracts in the field of information systems implementation not less 7 years;
• Experience in implementing successfully completed projects for building business analysis systems (Business Intelligence) at least 3 projects in the last 7 years;
• Have authorization from the software manufacturer or its regional structural unit (if the tender participant is not the manufacturer of the offered product);
• Experience in CIS countries will be considered as additional asset

The proposed team will have both the skills and experience necessary to undertake the range of tasks set out in these Terms of Reference. The Key experts will be not evaluation during review the EOI.

    The components of the System must have patent purity on the territory of the Republic of Uzbekistan.

The attention of interested Consultants is drawn to Section III of the World Bank’s “Procurement Regulations for IPF Borrowers” dated July 2016, revised in November 2017 and August 2018 (“Procurement Regulations”), setting forth the World Bank’s policy on conflict of interest.  In addition, please refer to the following specific information on conflict of interest related to this assignment: Consultants shall not be hired for any assignment that would be in conflict with their prior or current obligations to other clients, or that may place them in a position of being unable to carry out the assignment in the best interests of the Ministry of Finance of the Republic of Uzbekistan.

A Consultant will be selected in accordance with the Quality and Cost Based Selection (QCBS) method set out in the Procurement Regulations.

Further information can be obtained at the address below during office hours from 9:00 a.m. to 18:00 p.m. Tashkent time.

Expressions of interest must be delivered in a written form in English, Russian or Uzbek languages to the address below (in person, or by mail, or by e-mail) by December 17, 2021.

Project Implementation Unit under the
Ministry of Finance of the Republic of Uzbekistan

Attn: Foziljon Kalandarov, Manager of the Project

Uzbekistan, 100017, Tashkent city, 29, Istiklol St.

Tel: +998907380050

E-mail: piu_mof@mail.ru

 

 

As part of the EOI, the consultant should include the following information:

• Consulting Firm Information

 

Date:	Country of Incorporation:
Consultant Name:	Acronym:
EOI Submission Authorized by:	Position

 

• Associations (Joint Venture or Sub-consultancy)

 

Consultant	Acronym	Country of Incorporation	Joint Venture (JV) or Sub-consultant	EOI Submission Authorized By	Position

 

Present the rationale for and benefits of working in association (JV or Sub-consultant) with others rather than undertaking the assignment independently (as appropriate). Describe the proposed management and coordination approach of the association and the role of each firm.

 

• Technical competence

Project References - highlight the technical qualifications of your entity/consortium in undertaking similar assignments. Provide details of past experiences working with similar project authorities

 

• Geographical experience

 

Project References, present experiences in similar geographic areas.

 

• Management Competence

• Describe standard policies, procedures, and practices that your entity has to assure quality interaction with clients and outputs. Please state if your company is ISO certified.
• How your firm/consortium handles complaints concerning the performance of experts or quality of the reports submitted for previous and future assignments? What internal controls are in place to address and resolve complaints.
• How you ensure the quality of your firm’s/consortium’s performance over the life of assignments.

• Projects references

 

 

 

N	Project	Project start date (year, month, mandatory)	Project end date (year, month, mandatory)	Client	Country	Firm	Participated experts in the project among the recommended personnel (full name)
1
2
…
…
…
10

 

• Summary for the Projects listed above

 

Project Title
Country / Region
Start Date
Completion Date
Continuous / Intermittent
Client
Participated experts in the project among the recommended personnel (full name)
Funding Source
Project description
The role of the consulting firm	(indicate your role and contribution in terms of men-months)

 

• Eligibility

 

We, the undersigned, certify to the best of our knowledge and belief:

 

• We have read the advertisement, including the terms of reference (TOR), for this assignment (YES/NO)

 

• Neither the consulting firm nor its JV member or sub-consultant or any of its experts prepared the TOR for this activity (YES/NO)

 

• We confirm that the project references submitted as part of this EOI accurately reflect the experience of the specified firm/consortium. (YES/NO)

 

• Ensuing assignment resulting from our work product under this assignment, our firm, JV member or sub-consultant, and the expert(s) will be disqualified from short-listing and participation in the assignment.

 

• The lead entity and JV member or sub-consultant are NOT currently sanctioned by or other MDBs. Neither the consulting firm nor the JV member or sub-consultant has ever been convicted of an integrity-related offense or crime related to theft, corruption, fraud, collusion or coercion.

 

 

 

 

 

 

 

 

 

 

 

TERMS OF REFERENCE

For the project

" DEVELOPMENT AND IMPLEMENTATION OF AN AUTOMATED SYSTEM OF ACCOUNTING AND MONITORING FOR THE ACTIVITIES OF ENTERPRISES WITH STATE PARTICIPATION "

 

 

on 68 sheets

 

 

valid from "___" ____________ 2021

 

 

 

 

 

 

Tashkent 2021

 

 

1.      GENERAL INFORMATION.. 7

1.1.      Full name of the project and its symbol 7

1.2.      Customer 7

1.3.      Executor 7

1.4.      Basis for development 8

1.5.      Planned start and finish dates. 9

1.6.      Sources of financing. 9

1.7.      The procedure for registration and presentation of the results of work. 9

2.      PURPOSE OF THE SYSTEM AND OBJECTIVES OF PROJECT IMPLEMENTATION.. 10

2.1.      Purpose of the system.. 10

2.2.      Project implementation goals. 11

2.3.      Expected deliverables. 12

3.      CHARACTERISTICS OF THE INFORMATION OBJECT. 13

3.1.      General information. 13

3.2.      Architecture and composition of the current solution. 14

3.2.1.       Organizational scope of the project 19

3.3.      Process volume. 20

3.3.1.       Optimization and automation of business processes. 20

4.      SYSTEM REQUIREMENTS. 20

4.1.      System requirements as a whole. 20

4.1.1.       Requirements for the structure and functioning of the system.. 21

4.1.2.       Requirements for the component composition and architecture of the solution  24

4.1.3.       List and description of scenarios for using information systems. 26

4.1.4.       System Diagnostic Requirements. 28

4.1.5.       Requirements for the possibility of modernization and development of the system   28

4.1.6.       Requirements for interaction with third-party information systems. 29

4.1.7.       Requirements for the number and qualifications of system personnel and their mode of work. 30

4.1.7.1.        Requirements for the number of personnel (users) of IS. 30

4.1.7.2.        Requirements for the qualifications of personnel, the procedure for their training and control of knowledge and skills. 31

4.1.7.2.1.        Required mode of operation of IS personnel 31

4.1.8.       Indicators of appointment 32

4.1.9.       Reliability requirements. 33

4.1.10.         Safety requirements. 36

4.1.10.1.     Requirements for protecting information from unauthorized access. 37

4.1.10.2.     Requirements for the differentiation of access rights. 37

4.1.10.3.     Requirements for the safety of information in case of accidents. 38

4.1.10.4.     Requirements for protection against the influence of external influences. 39

4.1.11.         Ergonomic and technical aesthetics requirements. 39

4.1.12.         Requirements for the operation, maintenance, repair and storage of system components. 40

4.1.13.         Requirements for patent and license purity. 40

4.1.14.         Requirements for standardization and unification. 41

4.1.15.         Requirements for the degree of adaptability of the system to changes. 41

4.1.16.         Software technical support requirements. 42

4.2.      Requirements for the functions (tasks) performed by the Information System.. 42

4.2.1.       Requirements for the functions (tasks) performed by the System for recording and monitoring the activities of enterprises with state participation. 42

4.2.1.1.        Requirements for the functions (tasks) performed by the data visualization subsystem   42

4.2.1.2.        Requirements for the functions (tasks) performed by the subsystem for allocating roles and access rights. 48

4.2.2.       Connecting of source systems. 49

4.3.      Requirements to types of support 50

4.3.1.       Requirements for software. 50

4.3.2.       Information support requirements. 51

4.3.3.       Requirements for information exchange between system components. 52

4.3.4.       Linguistic requirements. 52

4.3.5.       Software Requirements. 53

4.3.6.       Requirements for metrological support 54

4.3.7.       Requirements for technical support 54

4.3.8.       Requirements for methodological support 54

4.3.9.       Requirements for the scope and / or duration of guarantees. 55

5.      SCOPE AND CONTENT OF THE SYSTEM IMPLEMENTATION WORKS. 56

6.      SYSTEM CONTROL AND ACCEPTANCE PROCEDURE. 59

6.1.      Types, scope and test methods. 60

6.2.      General requirements for acceptance of works by stages. 61

6.3.      Requirements for managing organizational change. 62

7.      REQUIREMENTS FOR THE COMPOSITION AND CONTENT OF WORKS ON PREPARING THE SYSTEM FOR COMMISSIONING.. 65

8.      DOCUMENTATION REQUIREMENTS. 67

8.1.      Project documentation. 67

9.      SOURCES OF DEVELOPMENT. 67

10.        PROJECT ASSUMPTIONS AND RESTRICTIONS. 68

10.1.        Organizational Assumptions and Constraints. 68

10.2.        Restrictions on the scope of work. 69

10.3.        Limitations on the scope of work. 69

10.4.        Limitations on implemented functionality. 69

10.5.        Restrictions on the composition and form of results. 69

10.6.        Terms of the Project execution. 70

 

 

 

 

 

 

 

LIST OF SYMBOLS, ABBREVIATIONS AND TERMS

DWH (QCD)	Data Warehouse
HD	Data store
BI	Business Intelligence - reporting and analysis system
RH	Guidance document
O'z DSt	State standard of the Republic of Uzbekistan
AWP	Automated workplace
DB	Database
GOST	State standard
ICT	Information and communication technologies
ISO / IEC (ISO / IEC)	International standard
LAN	Local area network
OS	Operating system
PC	Personal Computer
IB	Information Security
IT	Information Technology
IS	Information system
KS	Corporate network
ON	Software
IUI	Test program and methodology
SPD	Data transmission system
TT	Technical task
TC	Technical conditions
TR	Technical requirements
Dynamic reporting	Analytical reporting implemented by the System in the form of interactive analytical panels (dashboards), providing the user with the ability to interact with the analyzed data: filtering, full-text search, sorting, detailing and aggregation, changing the list of displayed indicators, changing the analytical sections used, etc.
Static report	A report generated by the System in the format of an Excel, Word, PDF or PowerPoint file, containing information that is relevant at the time of creation and does not provide for interactive work with the report data.
STC	State Tax Committee
NAS	National accounting standards
IFRS	International Financial Reporting Standards
CRM	Customer Relationship Management
HR	Human Resource Management
KPI	Key Performance Indicator is a quantifiable indicator of actual results achieved.

 

 

1. GENERAL INFORMATION
   1. Full name of the project and its symbol

Full name of the project: "Development and implementation of an automated system of accounting and monitoring for the activities of enterprises with state participation " (hereinafter referred to as the "System").

 

1. 1. Customer

Agency for State Assets Management of the Republic of Uzbekistan (hereinafter referred to as the "Customer").

Requisites:

• Address: 100000, Republic of Uzbekistan, Tashkent city, Amir Temur avenue
  , 6
• Phone: (+998 71) 259-20-54.
• E-mail: info@davaktiv.uz

 

1. 1. Executor

The contractor for this project will be determined based on the results of the tender selection.

Basic requirements for the contractor:

• The performer should not be in the Unified Register of Unscrupulous Performers;
• Not to have improperly fulfilled obligations under previously concluded contracts;
• Have experience in implementing projects similar in scope and specifics to the subject of the tender over the past 7 years;
• Experience in the implementation of successfully completed projects on the construction of business analysis systems – at least 3 projects.
• Have authorization from the software manufacturer or its regional structural unit (if the bidder is not the manufacturer of the proposed product);
• Have certificates confirming the presence of certified specialists (at least 3) who are not involved in other projects on the platform proposed for implementation;
• The following requirements are imposed on the contractor's specialists, which must be confirmed by the resumes provided: 

The role of the specialist	Requirements
BI Project Manager	Experience with BI for at least 5 years; Experience in managing at least two BI projects; Possession of a full range of knowledge and skills of project management; Experience in managing a project team of 15 people.
BI project architector	Experience with BI for at least 5 years; Experience of participation in at least two projects for the development and implementation of BI class systems; Knowledge of programming languages ​​on the database server; Experience in the design of class BI systems.
BI Functional Consultant	Experience with BI class systems for at least 3 years; Experience in participating in projects for the development and implementation of class BI systems; Knowledge of programming languages ​​on the database server; Experience in preparing technical documentation.
Financial consultant BI	Experience with BI class systems for at least 3 years; Experience in participating in projects for the development and implementation of class BI systems; Experience in financial analysis projects in various sectors of the economy - at least 3x; Knowledge of IFRS reporting.
BI Technical Consultant	Experience in working with data warehouses and BI class systems for at least 3 years; Experience in participating in projects for the development of data warehouses and implementation of BI class systems; Knowledge of programming languages ​​on the database server; Experience in the preparation of technical documentation for the developed solutions.
DBMS administrator	Experience with BI for at least 3 years; Experience participating in at least 3 similar projects as a DB / BI administrator; Experience in administering BI environments.

 

• Not be at the stage of reorganization, liquidation or bankruptcy;
• Not be in a state of litigation or arbitration with the "Customer";
• Not to have improperly fulfilled obligations under previously concluded contracts;

In addition, in accordance with the legislation of the Republic of Uzbekistan, it is not allowed to participate in tenders of companies upon detection of:

• conflicts of interest;
• preliminary collusion of participants with the aim of distorting prices or results of selection of participants;
• manifestations of fraud, falsification and corruption.

 

1. 1. Basis for development

The basis for the development of the System project is:

• Decree of the President of the Republic of Uzbekistan No.UP-5630 dated September 14, 2019 "On measures to radically improve the system of state assets management, antimonopoly regulation and the capital market";
• Resolution of the President of the Republic of Uzbekistan No. PP-1730
  dated March 21, 2012 "On measures for the further introduction and development of modern information and communication technologies";
• Minutes No. 5 of the meeting of the Republican Commission for Coordination of the Implementation of the Comprehensive Program for the Development of the National Information and Communication System of the Republic of Uzbekistan
  for 2013-2020 No. 01-08 / 1-417 dated 31.12.2014;
• Resolution of the President of the Republic of Uzbekistan dated April 28, 2020
  No. PP-4699 "On measures for the widespread introduction of the digital economy
  and electronic government";
• Decree of the President of the Republic of Uzbekistan on October 5, 2020 No. UP-6079 "On approval of the" digital Uzbekistan-2030 "strategy and measures
  for its effective implementation."
• Resolution of the Cabinet of Ministers of the Republic of Uzbekistan
  No. PKM - 273 dated 05/08/2020 "On measures to improve the procedure for accounting for state property";

 

1. 1. Planned start and finish dates

Planned project implementation timeline:

Start: September, 2021 

Completion: February 2023

 

1. 1. Sources of financing

A financing source for works under the project shall be the funds of the International Financial Institutions (IFIs)

 

1. 1. The procedure for registration and presentation of the results of work

Upon completion of individual stages and work as a whole, the Contractor submits an acceptance certificate.

The results of the work are evaluated by the acceptance committee. The acceptance committee is formed by the Customer in the prescribed manner.

To the Acceptance Commission, the Contractor submits documentation, the list
and requirements for registration of which are determined in accordance with GOSTs
and other standards, and governing documents in force in the territory of the Republic of Uzbekistan, as well as by mutual agreement of the Customer and the Contractor.

The date of delivery - acceptance of work is the date of signing the act by the acceptance commission.

 

 

 

1. PURPOSE OF THE SYSTEM AND OBJECTIVES OF PROJECT IMPLEMENTATION

 

1. 1. Purpose of the system

The main purpose of the information system for accounting and monitoring the activities of enterprises with state participation is an organized data array of the Agency, processed in a single hardware and software complex, which provides quick access to operational and historical information, multidimensional data analysis (KPIs for various dimensions), obtaining forecasts and statistics in terms of both the activities of the Customer and enterprises with a state share, regardless of the source of such information. This information can come from the following data sources:

• The Agency's own database;
• The personal account of the enterprise, posted on the information portal for submitting reports by joint-stock companies and other economic entities with a state share www.kpi.davaktiv.uz
• State property register www.property.davaktiv.uz
• Enterprise information systems;
• Information systems of state bodies (State Tax Committee, Customs Committee, Statistics Committee, Stock Exchange, Commodity Exchange)

During the implementation of the project of an information system for accounting and monitoring the activities of enterprises with state participation, the following tasks should be solved:

• Increasing the efficiency of information, analytical and management activities by automating functional areas and business processes related to the issues of making management decisions and creating a unified logical presentation of data;

• Implementation of management based on uniform information;
• Improving the quality of information provided for management decision-making;
• Separation of access rights to information;
• Providing a unified system of procedures for the formation of management reports;
• Bringing data from various sources into a single, easily understood format;
• Standardization and reduction of labor intensity of the reporting process.
• Increasing the use of analytical tools in the operational work of departments and the trust of end users.
• Reduced time to adapt business user requirements and implement changes.
• Reducing the total cost of maintaining reporting systems.
• Improving the performance of information systems and the efficiency of obtaining analytical data.
• Ensuring transparency of the Agency's activities;
• Formation of reports online;
• Reliable and secure data storage.

 

1. 1. Project implementation goals

Business intelligence systems are a type of information systems that allow you to turn accumulated factual data into useful knowledge
in order to make effective business decisions. Such knowledge can be used to solve any problems in analysis, management, forecasting, etc.

The purpose of introducing a business analysis system is to improve the efficiency of management of the operation and development of the Customer's Company, which is ensured by providing stakeholders,
taking into account their powers, prompt access to consolidated from various sources, relevant and reliable information, fully characterizing the current state of the business and the dynamics of its development.

The System will present data in a unified manner that will allow Users to form management, analytical and regulatory reporting. The business analysis system is created to perform complex and diverse functions, including the processing of analytical information, the formation of regulatory reporting and support for arbitrary requests.

 

The purpose of the system is:

• Improving the efficiency of the reporting process;
• Improving the efficiency of the Agency's Assets management;
• Increasing the availability of the Agency's operational reporting in terms of key performance indicators and project management, including from mobile devices;
• Creation of a unified system of reporting on performance indicators;
• Organization of data collection on the results of interaction with Assets for making decisions to improve the efficiency of work with them;
• Reduction of labor costs for reporting preparation;
• Providing business users with the ability to independently build analytical reporting;
• Improving the quality and reducing the time required for the preparation and submission of analytical reports;
• Creation of a control system for key performance indicators in order to increase the speed of adoption and the quality of management decisions;

To achieve the set goals within the framework of building the Agency's system, the following tasks must be solved:

• Creating a single tool for the formation of operational, consistent and reliable information on key performance indicators and work with Assets, necessary for making management decisions at the corporate management level;
• Creation of an interactive tool that allows filtering data, detailing data and uploading it to reporting forms, necessary to reduce the time for processing operational requests from the Agency's management;
• Creation of a role model and differentiation of access rights in the system;
• Performing the necessary system settings based on the requirements, design solutions, data model, dashboard layouts approved as part of the project work;
• Implementation of information exchange of the system with data sources;
• Training users to work in the system.

 

1. 1. Expected deliverables

 

• An internal portal must be implemented;
• With the help of the System, monitoring, analysis and control of the main indicators determined by the Customer should be carried out, as well as the formation of basic reports / dashboards according to these indicators with the possibility of their detailed decoding should be provided.
• The System should implement flexible analytical tools that allow considering indicators in different sections, providing filtering by various parameters, ensuring the delineation of the roles of access to data that meet the requirements for the composition of indicators and analysts;
• All project documentation has been completed in accordance with the documentation requirements;
• The System shall operate in a sustainable way, there shall be no complaints about quality of its operations (no freezes, logic operation errors, critical software failures, etc.).

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1. CHARACTERISTICS OF THE INFORMATION OBJECT

 

1. 1. General information

The Agency for State Assets Management of the Republic of Uzbekistan (hereinafter referred to as the Agency) was established by the Decree of the President of the Republic of Uzbekistan dated January 14, 2019 N UP-5630 “On measures to radically improve the system of state assets management, antimonopoly regulation and the capital market.

The Agency for State Assets Management of the Republic of Uzbekistan is a public administration body, the main activities of which are:

• Maintaining a unified state policy for the efficient management of state assets;
• Exercise of the right of a shareholder (founder and participant) on the state blocks of shares (shares) transferred to him in the authorized capital of enterprises with state participation;
• Implementation of modern methods and forms of corporate governance
  in enterprises with state participation on the basis of best international practice, a radical increase in the role of shareholders and supervisory boards in their management;
• Assistance, including on the basis of recommendations of international financial institutions, of the gradual transformation of enterprises
  with state participation into efficient enterprises that can compete in the domestic and foreign markets;
• Coordination of the development and approval of strategies for the development of enterprises
  with state participation, aimed at ensuring the efficiency and transparency of their activities, optimizing the management structure, high profitability and capitalization growth, withdrawing non-core
  and unused assets;
• Implementation of investment activities ensuring the interests of the state, including by transferring state shares (stakes)
  to trust;
• Organization of a set of measures to attract investments, including foreign direct, as well as portfolio investments through the issuance and sale of bonds and shares of enterprises with state participation, including the placement of an IPO / SPO issue on domestic and foreign stock exchanges;
• Ensuring an open and transparent mechanism for the sale (privatization) and lease of state assets, monitoring the implementation of investment
  and social obligations by investors , as well as participation in the development of proposals
  for public-private partnerships;
• Identification based on the analysis of idle, low-profit
  and unprofitable enterprises with state participation, development and participation in the implementation of programs for their financial recovery and increasing the efficiency of their activities;
• Implementation of state policy on bankruptcy cases;
• Conducting, together with the Ministry of Finance of the Republic of Uzbekistan, an effective dividend policy in enterprises with state participation;
• Provision of state regulation of appraisal activities, approval of property appraisal standards, as well as certification of realtors.

 

Also, the main participants in the project are:

State-owned enterprises. As of January 1,
2020, the number of enterprises with state participation is
2,965 (257 JSCs, 990 LLCs, 1,718 SUEs), enterprises in which there is a share of enterprises with state participation of about 2 thousand.

State Tax Committee of the Republic of Uzbekistan - provision of data on NAS (tax and other mandatory payments, tax arrears, tax benefits, etc.);

State Customs Committee of the Republic of Uzbekistan - information on the volumes of import and export of goods and services;

State Committee of the Republic of Uzbekistan on Statistics - supplier of data on industry indicators;

Republican Stock Exchange - supplier of information on securities;

The Uzbek Republican Commodity and Raw Materials Exchange is a supplier of information
on the cost of products.

 

1. 1. Architecture and composition of the current solution.

The Agency is currently collecting and analyzing data as part of the management of state assets. At the same time, the main sources of data received by the Agency are:

• Own Agency Database;
• Information portal for submitting reports by joint-stock companies
  and other economic entities with a state share www.kpi.davaktiv.uz;
• State Property Register www.property.davaktiv.uz;
• Database of the State Tax Committee of the Republic of Uzbekistan.

Information portal of putting public companies report and other economic entities with state share (JSC, LLC, companies with state shares.) Kpi.davaktiv.uz - information resource, using the accounting records of the collection of key performance indicators (hereinafter "KPI") and business plans from business entities with a state share (hereinafter the “Subject”). Each business entity with a state share has a personal account on the kpi.davaktiv.uz website. Access to your personal account is carried out using an electronic digital signature (hereinafter “EDS”) of a legal entity. In the personal account of the Subject there are electronic forms that are filled in by the Subject manually. The list of forms and the frequency of submission of reports is indicated in table. 3.2.2. Control over the correctness of filling out the report is carried out by the Agency's specialists manually. When analyzing the submitted report, the Agency's specialist has the opportunity to both accept this report and return it for revision, indicating in the comments the reason for the discrepancy.
 

The register of state property property.davaktiv.uz is an information resource for registration and submission of reports for legal entities in the form of state unitary enterprises and state enterprises. The principle of access to a personal account, as well as monitoring of received reports, is similar to the information portal kpi.davaktiv.uz. The list of forms and the frequency of submission of reports is indicated in table. 3.2.2.

Database of the State Tax Committee of the Republic of Uzbekistan - The database on objects of taxation and objects related to taxation is generated in electronic form in the territorial bodies of the state tax service at the location of the object on the basis of internal and external sources of information. Internal sources contain information on quarterly, annual financial reports, calculations of taxes and other obligatory payments, revised tax reports, explanatory notes, information and certificates provided by taxpayers to the state tax authorities.

Data from the State Oil Company database are sent to the Agency in automatic mode and are indicated in table. 3.2.2.

All data from the above sources are fed into the local database of the Agency. The Agency's existing database has accumulated information with a depth of 2 years.

The analytical layer is the information system (hereinafter “IS”) “State property” developed in 2018.

IS “State Property” is an analytical tool of the Agency, with the help of which the analysis and processing of data takes place. The users of the Information System "State Property" are the specialists of the Agency. The system has a role-based data access model. Information in the system is presented in tabular and graphical form. Completion and modernization of the system is carried out exclusively by the IT management specialists of the Agency.

  The architecture of the current solution is shown below in p. 3.2.1

 

 

 

 

 

 

 

 

 

p. 3.2.1 Architecture of the current solution.

 

The composition of the internal and external systems of the Agency (Table 3.2.1):

No.	System name	System Description	Data retrieval method
Internal systems of the Agency
1	IS "State Property"	Existing IS of business analysis	The existing IS "State Property" receives data from the Agency's database
2	Agency DB	Existing DB	Formed database. The accumulation of the database comes from all of the following sources. The depth of historical data is 2 years.
3	www.property.davaktiv.uz	Register of state property of registration and submission of reports for legal entities in the form of state unitary enterprises and state enterprises.	Filling out forms posted on the web platform is carried out by enterprises in manual mode.
4	www.kpi.davaktiv.uz	Information portal for submitting reports by joint-stock companies and other business entities in the form of JSCs, LLCs, enterprises with a state share.	Filling out forms posted on the web platform is carried out by enterprises in manual mode.
External systems
1	STC DB	State Tax Committee database	Data collection from the STC DB collected on an automatic basis.

Tab. 3.2.1 Composition of internal and external systems.

 

 

 

 

The composition of the reporting forms (Table 3.2.2)

Accepted reporting forms
No.	Organizational and legal form	Reporting forms	Periodicity	Fill / receive method
1	•      Joint Stock Company (JSC); •      Limited Liability Company (LLC); •      State-owned enterprises	Reporting forms according to national accounting standards (NAS) •      Form No. 1 (small and medium enterprises) •      Form No. 2 (small and medium enterprises) •      Form No. 4 (Large enterprises) •      Form No. 5 (Large enterprises)	Quarterly	Accepted by the Agency in automatic mode from the database of the STC
		Key performance indicators (KPI) reporting form	Quarterly	Filled in by enterprises manually on the web platform www.kpi.davaktiv.uz
		Key performance indicators (KPI) reporting form for the financial and banking sector	Quarterly	Filled in by enterprises manually on the web platform www.kpi.davaktiv.uz
		Key performance indicators (KPI) reporting form for insurance companies	Quarterly	Filled in by enterprises manually on the web platform www.kpi.davaktiv.uz
		Reporting form - business plan	Quarterly	Filled in by enterprises manually on the web platform www.kpi.davaktiv.uz
		Reporting form according to international financial reporting standards (IFRS) for enterprises •      Statement of financial position •      Statement of comprehensive income •      Cash flow statement •      Statement of changes in equity	Quarterly	Beginning of the reporting period - January 2022
		Reporting form according to international financial reporting standards (IFRS) for the financial and banking sector •      Statement of financial position •      Profit or loss statement •      Statement of comprehensive income •      Cash flow statement •      Statement of changes in equity	Quarterly	Beginning of the reporting period - January 2022
Management reporting
1	Management reporting forms		Quarterly	Formed in the IS "State Property"

Tab. 3.2.2 Composition of reporting forms

The information computer network of the Agency is a system of two components: an application server and a database server.

 

 

TAS-IX Network

 

 

 

 

МСПД (interstate data transmission system)

Firewall all

 

 

 

 

Local computing network

Applications server

Database server

Backup Applications

Backup databases

 

 

 

 

 

 

 

 

 

 

 

p. 3.2.2. logical diagram of the existing technical complex

 

 

 

Key technical specifications for Application Server and Database Server:

Applications server
Fujitsu Database Server Primary rx2530 m4	CPU Intel Xeon Silver 4110 8c 2.10 GHz 2x DDR4 32GB HDD SATA 6G 1TBx4 SSD 256Gbx2  OS / Oracle Linux Unbreakable PSU 800W 2x LANs I350-AM2 (Onboard on D3383-A1x, on D3383-C1x Intel® C620 Chipset (1Gb / 10Gb Ethernet) (Onboard on D3383-C1x, on D3383-A1x)
Database server
Fujitsu Database Server Primary rx2530 m4	CPU Intel Xeon Silver 4110 8c 2.10 GHz 2x DDR4 32GB HDD SATA 6G 1TBx4 SSD 256Gbx2  OS / Oracle Linux Unbreakable PSU 800W 2x LANs I350-AM2 (Onboard on D3383-A1x, on D3383-C1x Intel® C620 Chipset (1Gb / 10Gb Ethernet) (Onboard on D3383-C1x, on D3383-A1x)

 

Main challenges in working with the current information system:

• Analysis, summary and monitoring of the reports received is carried out in manual mode;
• Formation of a new form of puffiness or making changes to it implies significant both human and time costs on the part of IT management;
• Changing the visualization of reporting forms also requires the involvement of IT management;
• With an increase in the amount of information stored in the Agency's database, the time for processing historical data increases significantly.

 

1. 1. 1. Organizational scope of the project

Institutional scope of the project includes the State Assets Management Agency of the Republic of Uzbekistan with all regional offices.

As of 01.01.2021 the Agency has the following territorial distribution (figure 3.2.1.2):

 

 

State Assets Management Agency of the Republic of Uzbekistan

Rep. of Karakalpakstan

Andijan region

Jizzakh region

Navoi region

Samarkand region

Syrdarya region

Khorezm region

Tashkent city

Bukhara region

Kashkadarya region

Namangan region

Surkhandarya region

Ferghana region

Tashkent region

1 department

1 department

1 department

1 department

1 department

1 department

1 department

1 department

1 department

1 department

1 department

1 department

1 department

1 department

Total departments: 14 Central department: 1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1. 1. Process volume
      1. Optimization and automation of business processes

The scope of this Project includes the optimization and automation of business processes of reporting systems. Automation and carrying out on a regular basis the process of loading data from operational sources into an existing database, to consolidate information from various sources, to provide centralized quick access to data for business users.

 

1. SYSTEM REQUIREMENTS
   1. System requirements as a whole

The implementation of the System should be based on modern information technologies, as in the implementation of subject-oriented applied software systems that automate the execution of individual applied procedures and operations at all levels of the organizational hierarchy, a single information space based on a databank.

The system should include the following subsystems:

• Data visualization subsystem
• Subsystem for allocating roles and access rights (component of security and access control for various categories of users)

The system should provide opportunities for further development and modernization, including:

• Expansion of the number of enterprises and organizations;
• Expansion of the automated areas of activity of enterprises
  and organizations, with coverage, depending on the type of activity of the enterprise.

 The system should be organized as follows:

• The core, which has the functions of storing analysis, correlation and reporting, should provide high interactivity of working
  with consolidated data, flexible reporting in the form of the ability to perform unplanned (arbitrary) requests to data,
  as well as the user self-service function (self-configuration of new analytical reports);
• Web interface that provides users with access to the System;
• Have an intuitive user interface;
• Provide data protection and delimit data according to the level of user access;
• Authentication and authorization of users in the system should be performed on the basis of credentials for managing the rights and powers of users;
• Integrate with external systems;
• Be able to conduct basic predictive analysis;
• Have a reporting and analysis tool;
• Have pre-configured interactive dashboards
• The system should have a modular structure.

The system should provide for the ability to integrate with external information systems and databases using publicly available protocols such as:

• File exchange - directly or via FTP / SFTP protocols;
• SOAP - Simple Object Access Protocol, a structured messaging protocol in a distributed computing environment;
• ODBC - Open Database Connectivity, database access programming interface (API);
• RPC - Remote Procedure Call, a call to a remote procedure;
• RMI - Java Remote Method Invocation, a Java remote method invocation protocol for distributed object Java applications;
• COM, DCOM - Distributed Component Object Model, distributed component object model;
• Other.

 

1. 1. 1. Requirements for the structure and functioning of the system

The system should provide high interactivity of work
with consolidated data, flexible reporting in the form of the ability to perform unplanned (arbitrary) queries to data, as well as provide an opportunity for users to work independently (self-configuration of new analytical reports).

General system requirements.

The system should be able to:

• Extract data from various sources, build a unified information model;
• Be a simple and flexible analysis tool for the business user;
• Integrate with various information systems (information sources);
• Integrate with the most popular office applications (Microsoft Office);
• To support processing of large volumes of data (the minimum amount of data is specified in clause 3.2. Participants in the procurement procedure can also be provided with sample reporting forms to assess the amount of data);
• Maintain audit and development control mechanisms with the ability to track changes in code and scripts;
• The presence of a visual environment for the development of processes and rules for data transformation and control with a ready-made set of components;
• Have advanced visualization and customization tools for reports;
• Provide ready-made reporting forms to the user in print, PDF / PPT / EXL format, by e-mail or through the analytical portal in their own format;
• Have interactive navigation - hierarchy transitions, navigation between report sheets, etc.
• Support the construction of hierarchical reports, embedding graphs and charts in reports;
• Support the construction of non-standard analytical queries (ad-hoc query) by business users;
• Store the results of request processing in the form of an analytical document (report, graph, diagram) for further work with it or publication on the analytical portal;
• Use powerful mathematical tools for working
  with the received data, mechanisms for tracking changes, falling through hierarchies, setting up various kinds of notifications about deviations of values ​​from specified parameters;
• Support off-line work in the absence of communication
  with sources;
• Use familiar business terms when referring to data;
• Support the construction of control panels, which can contain a large set of graphic elements (speedometers, graphs, diagrams, interactive maps) intended for the visual presentation of information;
• Support mobile analytics.

 

The system should contain the following subsystems:

• Data visualization subsystem - designed to organize data presentation based on the data structure and develop the system user interface, including the development of data entry and display forms, reports and their printable forms, visualization tools for data samples in the form of diagrams and graphs.
• Subsystem for allocating roles and access rights - a module containing a set of functions for user authentication and authorization, including maintaining its own user database and using an external authentication system, maintaining a role model, assigning roles to users according to their job duties, differentiating access and configuring them for users workspace within the system.

 

The reporting forms issued by the System must include:

• Financial reporting (in accordance with NAS and IFRS);
• Publication of reports on the implementation of business plans and KPIs;
• Publication of management reports;

• Consumers of information

  WEB platforms of the Agency

  Agency staff

  Sources of information

  Agency assets

  WEB platforms of the Agency

  DB tax and customs committee

  The Agency's existing database

  Data visualization subsystem

  Administration module

  
  Other types of reporting.

p 4.1. General software architecture

 

Basic functional principles of the system

The main principles that the Contractor should be guided by when choosing / designing the System are as follows:

• The Agency's existing Database is a single source of consistent data and should provide users with consistent quality data from various information systems;

• The data should be available to employees in the amount necessary
  and sufficient to fulfill their functional duties;
• Employees must have a common understanding of the data, that is, a single semantic space must be established;
• It is necessary to eliminate conflicts in data encodings in source systems;
• Analytical computing should be separated from operational data processing;
• It is necessary to provide and maintain a tiered data organization;
• An evolutionary approach must be followed to ensure business continuity and preserve IT investments;
• The content of the existing Database and the commissioning of functional models are determined, first of all, by the requirements of business users;
• You need to ensure that your data is protected and stored securely. Information protection measures
  must be adequate to the value of the data.

 

1. 1. 1. Requirements for the component composition and architecture of the solution

The architecture of the System assumes the use of client-server technology with the ability to connect remote users through the WEB interface, as well as through a mobile application for mobile operating systems based on Android and iOS.

For the functioning of the System, the data will be loaded
from the existing DBMS of the Customer.

The composition of the software components of the Complex should correspond to the generally accepted structure of similar systems, and also represent an integral platform solution with a single metamodel, and not a set of disparate components.

The main components of the platform:

• BI application;
  • Visualization subsystem - Dashboards.
• Information security subsystems:

• Subsystem for allocating roles and access rights.

The system under development should include the following technological components:

• Application Server: a set of applications that provide standard approaches to organizing directory services, deploying analysis and reporting services;
• Administration tools, reporting development and additional applications;
• Client places of employees - AWPs (inside the LAN).

 

 

Рис. 4.1.1.2.1. Hi-level architecture of the system of accounting and monitoring of the activities of enterprises with state participation

More detailed requirements are indicated in clauses 4.1.9 and 4.2.

 

Requirements for modes of operation

The software tools of the complex of the systems being implemented must operate around the clock and provide the ability to work in the following modes:

Normal mode (continuous round-the-clock work);

Normal mode ensures the performance of system functions. This is the main mode of operation. In the normal operating mode of the system:

• Client software at users' workplaces provides the possibility of round-the-clock operation
  with regulated breaks for maintenance
  and software updates;
• The server software enables 24/7 operation with scheduled maintenance and software update intervals.

To ensure the normal operation of the system, it is necessary to comply with the requirements and maintain the operating conditions of the software specified in the relevant technical documents (technical documentation, operating instructions, etc.).

Service mode (for maintenance, reconfiguration
and replenishment of new components).

The service mode is intended for updating and preventive maintenance of software and hardware, changing the configuration of components.

The service mode of operation is used to perform operations of preparation and conduct of regulations, tests or significant restructuring of the system. 

This mode also carries out maintenance, reconfiguration, modernization and improvement of the system.

The mode allows diagnosing incidents or problems related to failures or accidents in the system.

The service mode is intended primarily for routine maintenance and system maintenance:

• Maintenance of the complex of technical means of the system;
• Installation of system-wide and special software updates;
• Monitoring the performance of system components;
• Performing a cold backup of the database.

 

1. 1. 1. List and description of scenarios for using information systems

The use of the System implies the following scenario:

A tool for operational business analysis - data will be presented in a unified manner, allowing Users to form management and analytical reporting.

The model includes two main scenarios:

• Analysis and reporting on data received from enterprises with state participation.

• Consolidation of data and formation of a consolidated report.

 

 

 

 

 

 

 

 

 

 

 

СИСТЕМа УЧЕТА И мониторинга

 General model of using IS scripts:

 

p. 4.1.4.1 “General Scenario Model”

 

 

p. 4.1.4.2 “Script Action Diagram”

 

Analysis and reporting on data received from the Assets of the Agency 001.

This scenario implies the receipt by the User of the Agency's management of data from enterprises with state participation, analysis of the enterprise and the formation of a report on the activities of the enterprise, taking into account the indication of the fulfillment of planned indicators.

Process steps:

1. User authorization in the system with the appropriate rights;
2. The user analyzes the data received from enterprises with state participation;
3. If the data is not correct, the user returns the data to the Asset for correction;
4.  If the data is correct, the User generates analytical reports, generates tabular and graphical reports;
5. At the end of the formation of analytical reports, the User sends the finished report to the Central Office of the Agency.

 

• Consolidation of data and formation of a consolidated report 002.

This scenario implies the receipt by the User of the Central Office of the Agency of data on the analytical report generated by the User of the Agency's management. The user of the Agency's Central Office consolidates data according to various criteria, generates a consolidated analytical report and publishes it in order to form an opinion on making certain decisions.

Process steps:

1. User authorization in the system with the appropriate rights;
2. The User analyzes the data received from the User of the regional administration;
3. The user consolidates the data;
4. The user generates analytical reports both in tabular and graphical form (dashboards);
5. The user publishes the generated data for the purpose of further decision-making.

Additional scenarios for the actions of each subsystem included in the delivery of the System will be reflected in the appropriate additions to this technical assignment at the design and development stage of the system.

 

1. 1. 1. System Diagnostic Requirements

Software diagnostics should be performed using standard system operating system modes, individual workstation operating systems, and by running a test case.

Software modules must have components according to the testing and testing methodology, which allow to control the possibility of functioning of the main modes of operation of the modules.

During the operation of the system, testing and diagnostics of software and hardware should be carried out by the system administrator in automatic mode when it starts.

As part of the development of the Program and Test Methodology, a test case must be formed to ensure that the nodes are operable and that interacting information systems are connected both during the initial installation and loading of the database, and in the course of daily work.

The test procedure will be carried out in accordance with the work plan indicated in Table 5.

 

1. 1. 1. Requirements for the possibility of modernization and development of the system

The system must be modernized and without a radical change in structure and composition, if it is necessary to use more modern high-performance technologies. Provide the ability to add new modules and additional systems (subsystem) to the existing software package or the ability to support a stepwise update - meaning that newer modules can be used in an existing system with previously installed ones. A software modularity approach should be provided.

In this case, the minimum allowable service life of the System must be at least 10 years.

1. 1. 1. Requirements for interaction with third-party information systems

Information interaction between the components of the System will be carried out on the basis of standard exchange formats. Methods and means of communication should provide:

• Using the TCP / IP protocol and various types of communication channels;
• Centralized management;
• Implementation of information protection functions, in accordance with the requirements for the protection of information transmitted through communication channels, set out in state and international standards.

Data exchange with other information systems should be carried out according to agreed formats and data transfer protocols.

The interaction of the System with third-party information systems is planned to be carried out using industrial integration tools.

The system must support the use of a WEB client. Provide the ability to use any device (smartphone, tablet or PC).

Information exchange between the ACS and external information systems should be carried out by calling the services provided by the components and using message queues.

The system should be able to interact with the following external information systems (if technically possible):

• Databases and data warehouses of enterprises with state. participation;
• Information systems of enterprises with state. participation;
• Database of the State Tax Committee;
• Database of the State Customs Committee.

The interaction of the System with third-party IS and scenarios of their use will be reflected in the corresponding technological instructions at the design stage. The technological instructions will indicate the protocols for receiving and transmitting data, the list and formats of the transmitted data and the lists of third-party databases used.

When interacting with third-party information systems included in the National Information System, the requirements of O'z DSt 2590 will be taken into account.

In order to ensure a further increase in the functionality of the system, it should be possible to add a list of external information systems and the composition of information transmitted and received in the course of information exchange between participants in information interaction within the framework of the creation, operation and modernization of the System.

 

1. 1. 1. Requirements for the number and qualifications of system personnel and their mode of work

 

1. 1. 1. 1. Requirements for the number of personnel (users) of IS

The preliminary number of users of the System is up to 200 internal users. The total number of personnel of users of the information system being implemented is determined by the Contractor at the stage of the Terms of Reference and is agreed upon by the protocol with the Customer. Detailed requirements for functional groups, composition, number, qualifications of personnel should be determined at the stage of development and Formation of requirements for the system in accordance with the organizational structure determined at the stage of inspection of the automation object.

 

Below is the estimated planned number of users of the System.

No.	Department / Management	Position	Number of users, people
1	Internal departments of AUGA	Director, head, deputy	30
		Specialist, employee	70
2	Territorial administrations	Director, head, deputy	20
		Specialist, employee	40
3	Other users of Ministries and departments	Director, head, deputy	10
		Specialist, employee	20
		Observer	10
	Total	Director, head, deputy	60
		Specialist, employee	130
		Observer	10

Table 4.1.7.1. Planned number of users of the System

In total, the approximate number of users of the System is 200 users involved in control, monitoring, analysis, and reporting, of which 60 are managers (directors, managers, deputies), 10 are observers. The system must assume at least 5 concurrent system administrators.

 

 

 

In this case, the main roles between users are as follows:

Observer role: viewing reports;

• The role of the employee: creation / modification of reporting;
• The role of the manager : creating / changing / deleting reports;
• The role of the System administrator : full access to the System, including the ability to conduct developments in the development environment, testing and transfer to a productive system.
  1. 1. 1. Requirements for the qualifications of personnel, the procedure for their training and control of knowledge and skills

Requirements for the procedure for training personnel of the System and control of knowledge and skills:

• The Contractor shall provide training separately for key users of the System;

• To control knowledge and skills in working with the System, questionnaires and a methodology for assessing the knowledge gained at the 5th stage should be developed (see Table 5.1).

Depending on the areas of activity, users study functional Systems and basic principles of administration.

It is possible to organize user training according to their roles in the System. During training, an emphasis is placed on the functionality of the System that is most in demand for the user's role.

Additional requirements are specified in clause 6.3 of this technical assignment.

 

1. 1. 1. 1. 1. Required mode of operation of IS personnel

The staffing table of the System is also determined by the Contractor at the stage of development and Formation of requirements for the system and is agreed upon by the protocol with the Customer. The mode of operation of users is determined by the job descriptions of the personnel providing the solution of functional tasks.

The operating mode of the service personnel should be determined based on the requirements for the time of the System operation. 

If it is necessary to ensure round-the-clock operation of the System, the organization of the on-call of the service personnel is required. Regardless of the operating mode of the System service personnel (normal or round-the-clock), the following must be ensured:

• All specialists should work with a normal work schedule no more than 8 hours a day; 
• The system is implemented on personal computers, therefore, the requirements
  for the organization of work and the mode of rest when working with it should be established based on the requirements for the organization of work and the mode of rest when working with this type of computer equipment;
• To ensure maximum efficiency and preserve the health of professional users, regulated breaks should be established during the work shift: 2 hours after the start of the work shift and 1.5 - 2.0 hours after the lunch break, each 15 minutes long or 10 minutes long every hour of work;
• The duration of continuous work of personnel with the developed system and personal computers without a regulated break should not exceed 2 hours.  

 

1. 1. 1. Indicators of appointment

The degree of adaptability of the system to changes in processes and management methods: 

• The menus of the software complex should be grouped
  in accordance with the subject of information, functional tasks
  and technology of work with the possibility of changing the composition; 
• The security administrator should be able to change user access rights to data and menus when the organizational structure, work technology or other factors affect the access rights to information; 

System performance: 

• The system must meet the scalability requirements, that is, the software included in its composition must ensure the simultaneous operation of the required number of users by increasing the computing resources of the corresponding data centers; 
• The inaccessibility of any information resource of the system should not affect the performance of the system as a whole;

Appointment indicators characterizing the degree of compliance of the System with the requirements for it for organizational and economic Informatization systems, in which the managerial decision and its implementation depend on the person, are difficult to Indicators of the degree of conformity of the System to the purpose

No.	The name of the purpose indicators	Explanation
1	Reliability indicators	They characterize the functional compliance of the System with the stated goals and the ability of the System to perform the specified functions in various conditions
1.1	Validity	The system must meet the stated goals and functional requirements of the technical specifications
1.2	Security	The system must be able to prevent unauthorized access to data
1.3	Operability	The system should function in the specified modes in the absence of destabilizing influences
1.4	Consistency	The system and documentation must have unambiguous, consistent descriptions for the same objects, functions, terms, definitions, etc.
1.5	Sustainability	The system must have the ability to ensure continued operation of the System after the occurrence of deviations caused by destabilizing influences
2	Performance indicators	They characterize the degree of satisfaction of the user's need for obtaining information, taking into account the economic, time and other resources of the System
2.1	Performance	The system must be able to perform actions in the time interval that meets the specified requirements
2.2	Profitability	The system must be able to operate on the minimum resources of the System
3	Manufacturability indicators	They characterize the technological aspects that make it easy to eliminate errors in the System
3.1	Modifiability	The system should be capable of providing ease of making the necessary changes and improvements to the System during operation.
3.2	Repeatability	The System should use typical design solutions or components
3.3	Structurality	The system should consist of complexes that perform interrelated functions

Tab. 4.1.7.1 Indicators of the degree of conformity of the System to the purpose

 

1. 1. 1. Reliability requirements

Reliability indicators for the system should be determined by the current requirements for the reliability of automated information systems for authorities and authorities and can be specified in the technical design. Also in the technical project, methods and means of performing work in the event of system failures must be determined.

System reliability indicators: - system availability factor 0.9997; - recovery time for the entire system is no more than 2 hours; - recovery time for individual subsystems is no more than 1 hour.

Availability is determined by the ratio of the time spent by the system in a healthy state to the total operating time.

Recovery time includes the time to identify an accident (failure) and eliminate its consequences. Including (if necessary) - restoring databases from archive copies.

The following requirements are imposed on the reliability of the equipment:

• As hardware platforms, tools with increased reliability should be used
  ;
• Application of technical means corresponding to the class of tasks to be solved;
• The software complex of the System must be able to recover in case of failures.

The following requirements are imposed on the reliability of power supply:

• In order to increase the fault tolerance of the system as a whole, it is necessary to equip the servers with an uninterruptible power supply with the possibility of autonomous operation of the system for at least 15 minutes;
• The system should be equipped with a subsystem for notifying Administrators about the transition to an autonomous mode of operation;
• The system must be equipped with agents to automatically shutdown the operating system in the event that a power failure exceeds 15 minutes;
• uninterruptible power supply of active network equipment must be provided.

The reliability of software should be ensured through the following organizational measures:

• Preliminary training for users and service personnel;
• Timely execution of administration processes;
• Compliance with the rules of operation and maintenance of software and hardware;
• Timely execution of data backup procedures.
• The reliability of the software of the subsystems should be ensured by:
• Reliability of the system-wide software and the Developer's software;
• Carrying out a set of measures for debugging, finding and eliminating errors.
• Keeping logs of system messages and errors by subsystems for subsequent analysis and configuration changes.

The reliability of the system being created is ensured by:

• High adaptability of the developed software and organizational support, which makes it possible to preserve the information circulating in the system in case of failures and other situations that violate or destroy the stability of the system's functioning;
• Using uninterruptible power supplies;
• Hot backup of the most important nodes of the System, which include database servers, application servers, storage network components, equipment that provides communication between subsystems, as well as communication between users of each subsystem with database servers;
• The choice of the topology of telecommunications and local computer networks, providing variability in the routing of information flows;
• Duplication of information carriers;
• High level of qualifications and organization of work of the service personnel;
• Organization of maintenance, using modern methods and diagnostic tools;
• Using only licensed software products;
• Debugging and testing modules of all subsystems;
• Availability of comprehensive sets of technical documentation that ensure reliable operation of all modules of subsystems;
• The operation of subsystem modules, which should not cause destruction, distortion and / or loss of information stored in the applied automated information systems of the subjects of interaction of the System. 

The reliability of the first stage of the System should be ensured by the possibility of recovery in the event of emergencies related to:

• With the occurrence of failures or failure of software, hardware and software and hardware of the System;
• With communication channel failures;
• With power outages;
• With the implementation of computer attacks.

Failures and malfunctions in the operation of software, hardware and (or) software and hardware of automated workstations of the System users should not lead to general destruction of the data stored in the System. The quantitative values ​​of the reliability indicators for the subsystems of the System, the achievement of which must be ensured, are presented in table 4.1.8.1

The composition and description of the reliability indicators of the System are indicated in table 4.1.8.2

  

Values ​​of reliability indicators

No.	Index	Meaning
The whole system
1	Time to identify and neutralize current threats to information security	no more than 5 hours (provided that the data is saved in the System)
2	Recovery time of parameters of normal functioning after the implementation of a computer attack	no more than 10 hours (provided that the data is saved in the System)
Data visualization subsystem
1	Reliability	10,000 hours
2	Availability ratio	0.9995
3	Availability	99.95%
4	Data loss tolerance	1 hour in (provided that the data is saved in the System)
Subsystem of distribution of roles and differentiation of access rights
1	Reliability	6000 hours
2	Availability ratio	0.99
3	Availability	99.9%
4	Data loss tolerance	12 hours

Tab. 4.1.8.1 Values ​​of reliability indicators

 

Composition of reliability indicators for the System

No.	Index	Description
	Availability	Ability Systems perform coordinated function to within a specified time ((time operation systems - while idle) / time operation Systems * 100). Measured as a percentage
	Availability ratio	The probability of that system will be in good working condition at an arbitrary moment of time, except for scheduled periods in during which the use of systems for other purposes not provided
	Data loss tolerance	Allowable period of time for which System data may be lost . Measured in hours
	Time to recovery	Time interval from the moment of failure (detection of failure) of the System until the moment of restoration of its operational state. Measured in hours
	Reliability	The property of the System to continuously maintain an operational state for some time, or developments. Measured in hours
	Time identifying and neutralization of actual threats to information security	The permissible period of time for which it is necessary to identify and neutralize the actual threats to the security of the System's information . Measured in hours
	Restoration time of parameters of normal operation      after implementation of a computer attack	The duration of the restoration of the System 's operational state after the implementation of a computer attack. Measured in hours

Tab. 4.1.8.2 Composition of reliability indicators for the System

 

1. 1. 1. Safety requirements

The required level of security must be ensured by the Customer through strict adherence to the rules of operation and maintenance of equipment recommended by the Contractors and developers of informatization tools.

Installation and commissioning of the system, as well as its subsequent maintenance should not be associated with exposure of personnel to dangerous values ​​of electric current, electromagnetic fields, acoustic noise, vibrations, etc.

The design of the technical means must ensure the protection of service personnel from electric shock in accordance with the requirements of GOST 12.2.003 and GOST 12.2.007.0.

The premises where the technical means of the system will be located must comply with the requirements of the guidance document RH 45-201: 2011.

All external elements of the Complex's technical means that are energized must be protected from accidental contact, and the technical means themselves must have grounding or protective grounding in accordance with GOST 12.1.030-81.

The power supply system must provide protective shutdown in case of overloads and short circuits in order to load, as well as emergency manual shutdown.

The design of technical means should provide free access to individual units and elements for their maintenance and repair, convenient connection of power cables.

All equipment included in the Complex must be serial and have appropriate certificates of conformity.

The security of the premises in which the technical means of the Complex will be located should be ensured by the appropriate working group at the enterprise, responsible for both the operation of the system as a whole and for the implementation of this Terms of Reference.

 

1. 1. 1. 1. Requirements for protecting information
            from unauthorized access

The System should provide for control and management tools that restrict the rights of users of the System for accounting and monitoring the activities of enterprises with state participation.

Access to the System for recording and monitoring the activities of enterprises with state participation should be provided only for registered users who have passed the identification and authentication procedure.

"Protection of information from unauthorized access" must be ensured by a set of technical (hardware and software) security means of the System, including:

• The system of security video surveillance of the perimeter and premises of the server part of the system.
• Authentication tools for users and elements of the System (workstations, engineering infrastructure management systems, etc.).
• Means of response to detected attempts of unauthorized access, both n premises and technical means.
• Means of protection against the penetration of computer viruses and the destructive impact of malware into the Systems affected by these vulnerabilities.

The information protection system of the system in terms of protecting local area networks and workstations must comply with the requirements of national standards:

• O'zDSt 2927: 2015 “Information technology. Information Security. Terms and Definitions";
• O'zDSt ISO / IEC 27001: 2016 Information technology. Methods for ensuring the security of the information security management system. Requirements;
• O'zDSt ISO / IEC 27002: 2016 Information technology. Security methods. Practical rules for information security management.

 

1. 1. 1. 1. Requirements for the differentiation of access rights

The system must meet the following requirements for managing data access rights within the system:

• The ability to restrict system users access only to the level of information and data that they need to perform their work functions, which are configured by the system administrator;
• Active Directory domain authentication;
• The ability to organize access to the application via HTTPS;
• The ability to customize the hierarchical structure of departments, offices and services of the Agency within the system, add users to various pre-configured groups, according to the organizational structure;
• The ability to assign users certain roles, and restrict access to data depending on the role;
• The ability to configure rights within a role separately for each object / system registry, in the context of the following privileges:
  • Creation;
  • Reading;
  • The change;
  • Removal;
  • Providing individual access;
• Prevent users from accessing data that they should not be able to access by assigned role or individually assigned access.
• The ability to provide access to analytics data according to the user's role level.
• The ability to customize the hierarchical organizational structure of employees within the system, and assign access to data depending on the position within this structure (for example, the 1st level manager has access to the data of his subordinates of the 2nd level, managers of the 2nd level have access to their subordinates 3rd level). The ability to customize the depth of access within the hierarchy (the number of levels down) for managers;
• Possibility of visual tree-like display of the configured user hierarchy and subordination structure in the organization;

The name of the roles, their rights and the description of access should be generated at the “Design” stage.

 

1. 1. 1. 1. Requirements for the safety of information in case of accidents

The system of accounting and monitoring of the activities of enterprises with state participation should provide for the means of backing up, archiving and restoring data.

The servers on which the information system operates must be provided with uninterruptible power supplies for at least 15 minutes to shut down the operating system and applications when the primary power supply is interrupted.

Emergency situations for which the safety of information in the System for recording and monitoring the activities of enterprises with state participation should be ensured:

 

Characteristics of the emergency	Measures to ensure the safety of information in the System	Emergency elimination time
Power outage	Application of uninterruptible power supply devices; Application of stand-alone alternators.	Equipment support for at least 20 minutes; Automatic start within no more than 15-30 seconds
Failure (failure) of hard disk drives (disk array) of the server	Backing up data to external media	Organization of disk arrays using the technology of RAID levels 0, 1, 5 or 10; Storage and automatic redistribution of information to spare disks for at least 20 minutes
Failure (failure) of the server (processor, power supply, RAM, etc.)	Carrying out diagnostics of the state of technical means using the tools supplied as part of the technical means; Duplication of critical server elements	Automatic transition of all functioning systems to a backup platform
Failure (failure) of the system software	Diagnostics of the state of the system software using the tools supplied as part of the system software; Backing up data to external media	Restore a saved backup within 15 minutes

 

A complete list of failures and their criteria will be clarified during the design and implementation of the project.

 

1. 1. 1. 1. Requirements for protection against the influence of external influences

In the premises with the located technical means, on which the System operates, climatic conditions must be ensured, determined by the requirements of the manufacturers of the used technical means.

Special requirements for protection against influence external influences are not presented.

 

 

1. 1. 1. Ergonomic and technical aesthetics requirements

While working with the system, the operating personnel of the system should not experience the inconvenience associated with improper organization of the workplace or human interaction with the elements of the system.

The equipment of the workplaces of the administrative personnel of the subsystem should ensure a continuous operation in the normal mode (without the need to leave the workplace to carry out production operations) a cycle of work in accordance with the operational and technological documentation.

AWS of users of the System must be equipped in accordance with SanPiN No. 0205-06 "Sanitary rules and hygienic requirements when working on personal computers, display terminals".

 

1. 1. 1. Requirements for the operation, maintenance, repair and storage of system components

The system must be designed for operation as part of the Customer's software and hardware complex. Technical and physical protection of the hardware components of the System, data carriers, uninterrupted power supply, resource reservation, routine maintenance is carried out by the technical
and organizational means of the Customer.

Periodic maintenance of the used technical means must be carried out in accordance with the requirements of the technical documentation of the Contractor

It must be possible to operate the Complex
around the clock.

Installation kits of the Complex should be kept
by system administrators in rooms with limited controlled access.

To store and restore data in the system, DBMS tools or internal software tools of the Complex must be used. The implementation of these requirements must be ensured by appropriate organizational measures - routine maintenance of the system.

Requirements for operation and maintenance procedures for technical means (equipment) of the system are determined by the relevant operational documents and instructions from the manufacturer of the relevant equipment.

Requirements for operation and maintenance procedures required for the functioning of the Complex, system software (operating system, database, etc.) are determined by the relevant operational documents and instructions from the software manufacturer.

Requirements for the permissible areas for accommodating the Service personnel of the Complex are determined in accordance with the requirements of labor protection and safety standards established in the Republic of Uzbekistan.

Requirements for the placement of technical means, the parameters of power supply networks and the operating conditions are developed on the basis of the corresponding technical conditions for the deployed hardware.

  

1. 1. 1. Requirements for patent and license purity

The contractor must provide evidence of the patent frequency of the solution used in the form of licensing agreements or a license purchase agreement.

The components of the System must be patent-free on the territory of the Republic of Uzbekistan.

The components of the System must meet the requirements for patent purity in accordance with the current legislation of the Republic of Uzbekistan.

Copyright and property rights to the software provided are determined in accordance with the legislation of the Republic of Uzbekistan.

When using programs (software systems or modules) developed by third parties, the conditions on which the right to use (execute) these programs is transferred should not impose restrictions that prevent the use of the system for its intended purpose.

The supplier is liable in case of violation of the rights of third parties to own the intellectual property and copyrights of third parties.

Non-exclusive rights to the software of the System are transferred to the extent that guarantees the absence of claims from third parties.

The System must use licensed software.

 

1. 1. 1. Requirements for standardization and unification

When implementing this project, the standards in force in the Republic of Uzbekistan should be accepted for guidance.

The equipment should use standard interfaces, technologies and data transfer protocols. The use of non-standard solutions is allowed in case of a significant increase in the efficiency of the system or the impossibility of using standard approaches.

Software and hardware that are subject to mandatory certification in accordance with the current legislation of the Republic of Uzbekistan must have appropriate certificates.

Unification at the stage of implementation of the System should be ensured by a uniform approach to solving the same type of control and management tasks (typing algorithmic modules) and the creation of unified components of information, linguistic, software and hardware.

The interaction of users with the application software included in the System should be carried out through a visual graphical interface (GUI).

Communication should include:

• use of unified data transfer formats and protocols.
• a unified system of classification and coding of information;
• use of standard accounting and reporting documents.

As part of the System software, uniform unified international classifiers and classifiers of the Republic of Uzbekistan should be used.

 

1. 1. 1. Requirements for the degree of adaptability of the system to changes

It is necessary to provide for changes in the automation object:

• Change in the number of system users;
• Changing the physical location of workplaces within working groups;
• Changing the composition and number of working groups of users;

To provide flexible control over the movement of workplaces
within any one object, provide ways to reconfigure the system:

• At the level of physical switching of patch cables,
• At the level of changing the configuration of active network devices.

The operation of the system should not depend on the type of computing devices used (computing platform), and allow the possibility of their replacement with equipment of a different type.

 

1. 1. 1. Software technical support requirements

The technical support of the processing solution software should provide a service hotline 24 hours a day * 7 days a week * 365 days a year for telephone consultations and, if necessary, remote access to the system for urgent problem solving.

The contractor must have a system for registering applications and monitoring them.

The contractor provides a guarantee for a period of 12 months. During the warranty period, software errors are corrected free of charge.

 

1. 1. Requirements for the functions (tasks) performed by the Information System

 

1. 1. 1. Requirements for the functions (tasks) performed by the System for recording and monitoring the activities of enterprises with state participation.

The information system for accounting and monitoring the activities of enterprises with state participation will be designated from the following subsystems:

• Data visualization subsystem
• Subsystem for allocating roles and access rights 
  1. 1. 1. Requirements for the functions (tasks) performed by the data visualization subsystem

Data visualization subsystem - designed to organize data presentation based on the data structure and develop the system user interface, including the development of data entry and display forms, reports and their printable forms, visualization tools for data samples in the form of diagrams and graphs. The subsystem should perform the following functions:

Function	Task
The form	Grouping data in different sections defined by the data hierarchy down to the lowest level of detail; Grouping data from different levels of the hierarchy; Creation and saving of fixed groupings of data available in subsequent sessions of work with the system after the completion of the current one; Creation of templates defining the sequential steps of the analysis with the support of the interactive mode; Ranking, sorting and filtering by various categories and indicators; Creation of multi-section reports with different levels of data grouping; Creation of a set of standard report templates that make it easier for the user to build standard reports; Setting the parameters of reports in the interactive mode;
Analysis	Flexible data manipulation; Data scaling (drill-down); Possibilities of data aggregation by arbitrary indicators; Support for the ability to display monetary amounts in more than one currency with the ability to quickly recalculate; Ranking values ​​of measurement categories by values ​​of indicators; Analysis of trends over time;
Performance	Pie charts; Column charts are two-dimensional; Column charts are three-dimensional; Line charts; Scatter plots; Simultaneous output of data in tabular and graphical form; Formation of balanced and unbalanced nested pivot tables; Calculations over the values ​​of indicators for arbitrary groups of measurement categories; Conditional formatting of indicators depending on their values; Displaying indicators in the form of absolute values ​​and shares of total values; Export of slices of multidimensional cubes in various formats.

 

The data visualization subsystem should be able to generate the following reporting groups:

• Reporting forms in accordance with NAS, which includes 4 reporting forms (the list is given in Table 4.2.1.);
• Reporting forms for key performance indicators (manufacturing enterprises, banking sector, insurance companies), which includes 18 reporting forms (the list is given in Table 4.2.2.);
• Reporting form for the implementation of the business plan, which includes 15 forms (the list is given in Table 4.2.3.);
• Management reporting form, which includes 15 forms (the list is given in Table 4.2.4.);
• Forms of reporting under IFRS for both industrial and financial and banking sectors, including 9 forms (a preliminary list is given in Table 4.2.5.);

The methodological component of the reporting forms, with the exception of the IFRS reporting form and its disclosure, is provided by the Customer at the Design stage.

Initially, the reporting forms in accordance with IFRS (enterprises and the financial and banking sector) will be filled out through the information portal kpi.davaktiv.uz by enterprises on the basis of their own calculations.

 

List of reporting forms:

Table 4.2.1 - Forms of reporting in accordance with NAS

Form No. 1 - balance sheet
1	Long-term assets
2	Current assets
3	Sources of own funds
4	Commitments
5	Certificate of availability of valuables recorded on off-balance sheet accounts
6	Deciphering overdue receivables and payables - overdue receivables
7	Overdue payables
Form No. 2 - Statement of financial results
1	Form -2
Form No. 4 - statement of cash flows
1	Operating activities
2	Investment activities
3	Financial activities
4	Taxation
5	Statement of cash flow in foreign currency
Form No. 5 - statement of equity capital
1	Form No. 5

Table 4.2.2 - Forms of reporting on key performance indicators.

Key Performance Indicators - Industrial
	List of key KPIs
	List of additional key performance indicators
Key performance indicators - banking sector
	Indicators of assets and liabilities
	Compliance with normative indicators in the bank
	Financial performance
	Trust Fund Tax and Payments
	Distribution of net profit
	External credit lines / Eurobonds
	Sponsorship
	Amount of workers
Key performance indicators - insurance companies
	Indicators of assets and liabilities
	Compliance with normative indicators
	Financial performance
	Trust Fund Tax and Payments
	Distribution of net profit
	External debt
	Sponsorship
	Amount of workers

 

Table 4.2.3- Reporting forms - business plan

Business plan
	Production facilities (works and services)
	Production volume (Works and services)
	Financial performance
	Taxes and payments to trust funds
	Distribution of net profit
	Debentures
	External debt
	Foreign trade and foreign economic activity of the enterprise.
	Important performance indicators
	Production of products included in the localization program
	Investment projects.
	Sponsorship
	The number of employees
	Management and control bodies of state-owned enterprises
	Changes in the composition of the supervisory board, the executive body of the audit commission.

 

 

Table 4.2.4 - Management reporting forms

Management reporting
	Information on the production indicators of enterprises
	Production indicators
	Financial performance
	About business plans of state-owned enterprises
	On the state of the analysis of the activities of enterprises with state participation
	Payment of dividends by state-owned enterprises
	According to the results of 9 months of the reporting year, state enterprises operating in the territory of the republic.
	Financial recovery of state-owned enterprises
	Information about the labor resources of enterprises
	Production of products included in the localization program
	Investment projects.
	Sponsorship
	The number of employees
	Management and control bodies of state-owned enterprises
	Changes in the composition of the supervisory board, the executive body of the audit commission.

 

Table 4.2.5 - Preliminary reporting forms in accordance with IFRS

Preliminary IFRS reporting forms - enterprises

 

	Statement of financial position
	Statement of comprehensive income
	Statement of changes in equity
	Cash flow statement (direct method)

 

Preliminary reporting forms under IFRS - (financial and banking sector)

 

	Statement of financial position
	Statement of comprehensive income
	Profit or loss statement
	Statement of changes in equity
	Cash flow statement

 

At the same time, the tools of the business analysis system should allow generating reports in a graphical form with various levels of complexity. Below is the graphic design of this kind of reporting (dashboards, graphs, diagrams, territorial dashboards, etc.).

 

 

 

 

p. 4.2.1 – Example of visualization of predictive analysis

 

 

p. 4.2.1 – An example of visualization of a territorial dashboard

 

 

 

p. 4.2.1 – An example of KPI visualization

Time schedule for the implementation of each function, tasks:

Interim regulation requirements	Task
The entire period of operation of the system upon user initiation	Grouping data in different sections defined by the data hierarchy down to the lowest level of detail;
	Grouping data from different levels of the hierarchy;
	Creation and saving of fixed groupings of data available in subsequent sessions of work with the system after the completion of the current one;
	Creation of templates defining the sequential steps of the analysis with the support of the interactive mode;
	Ranking, sorting and filtering by various categories and indicators;
	Creation of multi-section reports with different levels of data grouping;
	Ranking values ​​of measurement categories by values ​​of indicators;
	Analysis of trends over time;
	Pie charts;
	Column charts are two-dimensional;
	Column charts are three-dimensional;
	Line charts;
	Scatter plots;
	Simultaneous output of data in tabular and graphical form;
	Formation of balanced and unbalanced nested pivot tables;
	Calculations over the values ​​of indicators for arbitrary groups of measurement categories;
	Conditional formatting of indicators depending on their values;
	Displaying indicators in the form of absolute values ​​and shares of total values;
	Export of slices of multidimensional cubes in various formats.
The entire period of operation of the system	Creation of a set of standard report templates that make it easier for the user to build standard reports;
	Setting the parameters of reports in the interactive mode;
	Flexible data manipulation;
	Data scaling (drill-down);
	Possibilities of data aggregation by arbitrary indicators;

Requirements for the quality of implementation of functions, tasks.

All functions and tasks must have a characteristic of accuracy and execution time, determined by the operating regulations.

 

List of failure criteria for each function:

Function	Refusal criteria	Recovery time	Availability ratio
The form	One of the tasks of the function is not being performed.	8 ocloc'k	0.85
Analysis	One of the tasks of the function is not being performed.	12 hours	0.75
Performance	One of the tasks of the function is not being performed.	12 hours	0.75

 

 

 

1. 1. 1. 1. Requirements for the functions (tasks) performed by the subsystem for allocating roles and access rights.

The subsystem of distribution of roles and access rights is designed to provide the following functions:

The subsystem should perform the following functions:

Function	Task
User management and monitoring	User management; Provision of work on replacing versions of the client and server parts of the software product, setting the parameters of the client and server parts of the software product; Provision of routine maintenance provided for by the operational documentation for the software product; Resolution of problems arising during the operation of the software product; Elimination of emergency situations (incidents) arising during the operation of the software product; Elimination of the consequences of known (identified during operation, but not eliminated) errors of the software product associated with the operation of the software product; Monitoring the work of users of the software product and means for interacting with them; Monitoring of the parameters of the functioning of the software product; Procedures for managing the operation of a software product; Removal of users from the software product should be carried out by transferring them to the category of blocked users without the possibility of performing operations under their names and without the possibility of canceling this status; The possibility of deleting information about users registered in the software product, including blocked ones, must be excluded; The possibility of changing (modifying) demo data (last name, first name, patronymic) of the established users must be excluded; The implementation of the administration mechanism should not reveal the logic of building the database of the software product; Users who do not have business roles (Administrator, Operator, etc.) should not be able to change the business data of the software product.
Access rights management	The mechanism for distributing access rights to the functions of a software product should allow the provision of users with the minimum rights necessary to perform their functional duties; The architecture and construction of the database must be such that the rights of users in the database do not exceed the rights of users in the application part of the software product; The mechanism for distributing access rights should cover all user operations with objects of the software product. All objects of the software product and operations on them must be covered by the mechanism for distributing access rights; The mechanism for differentiating access rights should be implemented based on the creation of roles in a database or application part of a software product. Access to objects of the software product must be explicitly allowed or denied based on the user's security attributes; The mechanism for differentiating access rights should ensure that the employee can launch only the functions allowed to him.
Identification and authentication mechanisms	Access to information and functions of the software product should be provided to the user only after the presentation of a unique personalized identifier (name) of the user and an authentication procedure based on some information entered by the user (password, keys); It should be possible to determine the authorship of each operation in the software product and the absence of unauthorized operations based on the unique personalized identifiers of each user, the authentication procedure and logging of user actions in audit logs.

The time schedule for the implementation of each function, task is determined for the entire period of the system's operation.

Requirements for the quality of implementation of functions, tasks.

All functions and tasks must have a characteristic of accuracy and execution time, determined by the operating regulations.

List of failure criteria for each function:

Function	Refusal criteria	Recovery time	Availability ratio
User management and monitoring	One of the tasks of the function is not being performed.	12 hours	0.75
Access rights management	One of the tasks of the function is not being performed.	12 hours	0.75
Identification and authentication mechanisms	One of the tasks of the function is not being performed.	8 ocloc'k	0.85

 

 

• 1. 1. Connecting of source systems
• The customer undertakes to ensure interaction with related departments and projects, including interaction with source systems, to the extent necessary for the implementation of the project;
• The customer undertakes to provide access to all available up-to-date documentation on the source systems and to allocate competent specialists for consultations and approvals of the technical documentation of the project (TOR for uploading data, regulations for interaction with the source, etc.) in the amount necessary for the implementation of the project;
• The Customer undertakes to provide the Contractor with access to the productive and test environments of the source systems with up-to-date data and structures, organized on the basis of the Customer's equipment, corresponding in performance to the configuration of the database server environment at the appropriate stage of development;

The sources with which the integration is performed satisfy the following assumptions:

• All connected Sources have a data availability schedule for a specific date;
• Technological windows on the Sources and data transmission channels ensure the possibility of regular data uploading in accordance with the operating regulations of the reporting system;
• The Contractor develops a logical data model taking into account the business requirements of the Customer, defining the requirements for interfaces on the side of source systems (specification of interface objects);
• The granularity of the data and the set of attributes (Indicators, Dimensions) are determined by the business reporting requirements agreed at the stage of business analysis;
• The project does not envisage the implementation of special algorithms for uploading data via slow and unreliable communication channels; it is assumed that the System and the Sources are within the same high-speed local network with a guaranteed bandwidth of at least 100 Mbps (a network failure may lead to a download failure);
• It is assumed that sufficient hardware capacities will be used in accordance with the specifications calculated at the stage of forming the requirements for equipment;
• The quality of the data uploaded to the System corresponds to the quality of the data of the source systems;
• The Contractor implements control mechanisms, regulations for informing and reporting, allowing to track the compliance of data in the System and source systems.

 

 

1. 1. Requirements to types of support
      1. Requirements for software

The software of the System must ensure the implementation of the functions listed in this TT, as well as the performance of configuration, programming, database management and documentation operations. The system must ensure the implementation of the required algorithms for control, regulation and protection, information display, signaling and data archiving.

The software of the System should include:

Typical and developed methods and algorithms for collecting and processing information (including data entry into a PC, data reliability control, etc.);

• Data search and sorting algorithms;
• General requirements for software;
• Using the standard class library;
• Maximum use of standard methods and algorithms;
• The mathematical methods used must take into account the technical capabilities of hardware and software, have the minimum values ​​of the solution time and the occupied RAM;
• Documentation for software (problem statement and solution algorithms) should provide unambiguous interpretation and programming capability without additional clarifications;
• Any form of task description is allowed - formulaic, tabular, flowchart, UML diagram, verbal description, etc.

Software algorithms must meet the following requirements:

• Allow decomposition into relatively simple blocks;
• Make the most of the capabilities of programming languages ​​in your description;
• Provide functional interconnection of tasks.

Algorithms for searching and sorting data used in solving almost all functional problems of the System should be based on procedures in the system software and used in the System. These algorithms should ensure the search for information by the specified values ​​of the features, the formation of the specified information structures and the performance of the necessary operations on them. 

Algorithms for generating output documents should be as unified as possible, allow, if necessary, to quickly change the forms of documents and use standard procedures and software.

Algorithms for solving problems, if necessary, can include optimization methods and heuristic procedures for specific problems.

 

1. 1. 1. Information support requirements

Information support should be sufficient to perform all automated functions of the System.

The information support of the System should be a collection of data and data management tools, which are designed for integrated information processing and software solution of functional tasks.

• Compatibility with the information support of the Systems interacting with the systems being implemented must be ensured;
• Forms of documents must meet the requirements of the corporate standards of the Customer (or a unified documentation system);
• The structure of documents and screens should correspond to the characteristics of the terminals at the end-user workplaces;
• Formation schedules and content of information messages, as well as the abbreviations used must be generally accepted in this subject area and agreed with the Customer;
• Access to data should be provided only to authorized users, taking into account their official powers, as well as taking into account the category of the requested information;
• It is necessary to provide for the possibility of emergency disconnection of access to the systems being implemented in cases of emergency situations.

 

1. 1. 1. Requirements for information exchange between system components

The software and hardware of the components of the information system being implemented must comply with the data exchange standards using the TCP / IP protocol stack.

Information exchange between software components of subsystems should be carried out using standard protocols and technologies: web-services, JMS messaging, HTTP / HTTPS, EJB, file transfer (FTP, SFTP), LDAP, JDBC, etc.

Information exchange between the software components of the subsystems and the browser should be carried out using the HTTP / HTTPS protocols.

The software and hardware that ensure the interaction of the System with the users of the System must support the current versions of the following browsers supported by the manufacturer:

•                Mozilla Firefox - current version and current ESR version;
•                Google Chrome - current version;
•                Opera - current version;
•                Microsoft Internet Explorer - current version (Desktop);

At the time of the start of commercial operation of the System, consider the versions available for download on the download pages of the official websites of browser manufacturers as the current supported versions of browsers.

For browsers that support two ways of browsing the web, a touch-optimized Windows user interface, and a familiar touch-based interface, the latter should be supported.

 

1. 1. 1. Linguistic requirements

The linguistic support of the System, whenever possible, should provide for the use of a single logical and conceptual interface for users and designers. Including:

• Linguistic support should be sufficient for communication of various categories of users in a convenient form with automation tools and for carrying out transformation procedures and machine representation of information processed in the System;
• During the development and design of the System, tools should be used that include a complete set of tools for end-to-end design;
• The system must use high-level programming languages ​​(such as: C ++, C #, Delphi, Fortran, Java, JavaScript, Pascal, PHP, Ruby, Python, Perl), including for the data input / output process;
• A structured query language, such as SQL, must be used to manipulate data;
• The implementation of the System should be based on modern information technologies, as in the implementation of subject-oriented applied software systems that automate the execution of individual applied procedures and operations at all levels of the organizational hierarchy, a single information space based on a databank.

The information in the database must be stored in the language in which it was entered into it. The choice of the current data input language for the database depends on the current legislative acts of the Republic of Uzbekistan and must support input in Uzbek and Russian.

Application software development should be carried out in high-level languages. Users must interact with the system at the graphical user interface level.

All functions of the system, prior to their full implementation into industrial operation, must provide a Russian-language user interface.

 

 

• 1. 1. Software Requirements
• When implementing the system, advanced industry technologies from leading manufacturers should be used.
• Use as the main technology for placing data "in-memory".
• All tools supplied as part of the software (software) must have certificates, as well as license agreements (licenses) confirming the legality of their use.
• The software must be supplied with sets of licenses corresponding to the number of workstations on which it is supposed to be installed, and have the latest version of the manufacturer in terms of release time. 

The System software must have the following characteristics:

• Provide resilience to erroneous situations, including incorrect and inconsistent data; failures in the operation of programs, failures of part of the computing facilities, personnel errors should be diagnosed, accompanied by messages, and should not cause disturbances in the operation of the system;
• Provide a restart when the electric power is restored after it is turned off without generating false signals and control actions;
• Give correct results for all combinations of initial data that are admissible within the framework of the problem statement;
• Be able to quickly configure during the operation of the System.

If the software manufacturer does not have technical documentation in the state (Uzbek) language, the translation of the technical documentation into the state language is carried out by the Customer.

All software must be guaranteed for at least 1 year.

The systems should be able to interact with leading foreign IT systems:

• Database level: Oracle, DB / 2, MS SQL, PostgreSQL, SAP Hana, HP Vertica, etc.
• BI level: Oracle BI, SAS BI, SAP BO, QilckView, IBM Cognos, etc .;
• Business logic layer: Oracle OFSAA, SAS DDS, SAP FSDP, Sybase DDS, IBM BDW, etc .;
• Information on the compatibility of the versions of the proposed software should be provided.

 

1. 1. 1. Requirements for metrological support

The composition of information, control functions of the system, measured parameters of the control object, their exact characteristics, metrological characteristics will be determined and agreed upon during the implementation of the project stage “Formation of requirements for the system”.

Metrological compatibility of the technical means of the system is ensured through the choice of compatible technical means by the developer.

There are no additional requirements for metrological support.

 

1. 1. 1. Requirements for technical support

There are no requirements for the existing technical support.

The optimal requirements for technical support for the proposed software product should be indicated in the technical proposal by the participants in the procurement procedure.

In the process of developing and deploying an analytical reporting system, a test and production environment is required. These should be independent servers used for testing, training and deploying the system. 

1. 1. 1. Requirements for methodological support

The calculation methods used in solving system problems, as well as, if necessary, other specific requirements for the implementation of tasks, are detailed by the Contractor based on the results of a preliminary survey of the Customer's IT structure and are agreed with the Customer.

Systems should be implemented on the basis of current regulatory legal acts and organizational and administrative documents.

Methods and instructions for performing operations in the Systems by users must be developed and approved in the prescribed manner.

The methodological support includes:

• Regulatory legal documents;
• Job descriptions of personnel performing work using the System.

The composition of the methodological support can be specified in the process of technical and detailed design and is agreed with the customer.

Normative and technical documentation must comply with the requirements of regulatory legal acts and be developed in accordance with the following standards:

• O'z DSt 1986: 2018 State standard of Uzbekistan Information technology. Information Systems. Stages of creation;
• O'z DSt 1987: 2018 State standard of Uzbekistan “Information technology. Terms of Reference for the Creation of an Information System ";
• O'z DSt 1985: 2018 Types, completeness and designation of documents when creating an information system (IS);
• O'z DSt 3243: 2017 Information technology. Local and corporate
• T 45-194: 2007 Recommendations on the use of software and hardware to prevent acts of illegal entry into information systems.
  1. 1. Requirements for the scope and / or duration of guarantees

The contractor assumes obligations for quality assurance results obtained during the performance of work. The minimum period for providing a quality guarantee for work is 12 months plus 1 working day from the date of acceptance of the results of work by the Customer (the date of the signing by the Customer of the Certificate of Acceptance of Works).

The Contractor is responsible for defects and deficiencies found during the warranty period. In case of revealing defects and deficiencies during the warranty period, the Contractor performs work to eliminate them free of charge, including if during operation it is revealed that the System does not correspond to the purpose indicators declared in its Private Terms of Reference and / or Technical Design. The deadline for eliminating defects and deficiencies is established by agreement between the Customer and the Contractor, but should not exceed one month.

1. SCOPE AND CONTENT OF THE SYSTEM IMPLEMENTATION WORKS

The implementation of the requirements of this TT should be carried out in several stages. The composition and content of the work by stages is shown in the table below. The list of stages and stages of the work performed on the implementation of the automated system is indicated in accordance with O'zDSt 1986: 2018 Information technology. Information Systems. Stages of creation.

Preliminary stages of work (table 5.1):

 

List of stages and stages of work on the creation of the System

 

Stage number	Name of works and their content	Deadline		Contractor (organization)	How the stage ends
		Start	The ending
1	Formation of requirements for the System: Initial survey of the facility and justification of the need for the System;	September 2021	October 2021	Executor	Site survey report;
2	System concept development: Development of the project charter; Pre-design survey; Formation of business requirements for the system. Formation of a report on the results of work.	October 2021	November 2021		Project charter; Project schedule; Report on the results of the work.
3	Technical task: Drawing up the Terms of Reference for the creation of the system and its form	November 2021	February 2022		Terms of reference for data marts in terms of the received reporting on: NSBU; KPI; Implementation of the business plan, production indicators, personnel report; Management reporting; IFRS
4	Design: 1. Development of design solutions for the system and its parts. Testing; 2. Development of documentation for the System and its parts;	February 2022	May 2022		Development specifications, data mappings in terms of the received reporting on: NSBU; KPI; Implementation of the business plan, production indicators, personnel report; Management reporting; IFRS
5	Working documentation: Development of working documentation for the system and its parts.	May 2022	June 2022		Working documentation for the development of reporting
6	Commissioning: Preparation of the automation object for putting the System into operation; Personnel training; Commissioning works: Setting up integration with systems in accordance with the TOR; Preliminary tests; Coordination of improvements and settings, correction of defects; Acceptance tests.   Pilot industrial operation Industrial exploitation	June 2022	February 2023		Reporting on: NAS KPI Implementation of the business plan, performance indicators, personnel; Management reporting IFRS Guides : Business Analysis System User Guide Business Analysis System Administrator Guide Acceptance test procedure Acceptance test report
7	System Maintenance: Performance of work in accordance with warranty obligations; Post-warranty service.	February 2023

Tab. 5.1 Preliminary stages of work.

 

 

Preliminary work schedule (table 5.2):

	Год	2021						2022
№	Этап	09.21	10.21	11.21	12.21	01.22	02.22		03.22	04.22	05.22	06.22	07.22	08.22	09.22	10.22	11.22	12.22	01.23	02.23
1	Formation of requirements for the System
2	System concept development
3	Technical task
4	Design
5	Working documentation
6	Commissioning
7	System Maintenance	Within 12 months

Tab. 5.2 Preliminary work schedule.

 

 

1. SYSTEM CONTROL AND ACCEPTANCE PROCEDURE

Control and acceptance of the System must be carried out in accordance with the requirements of O'zDSt 1986: 2018 Information technology. Information Systems. Stages of creation.

Both the System as a whole and its individual stages (launch complexes), subsystems and individual tasks can be subject to control, testing and acceptance.

The following main types of tests are established for the System:

• Preliminary tests;
• Pilot industrial operation;
• Industrial exploitation

To plan the conduct of all types of tests, the documents "Program and Test Methodology" of the corresponding types of tests are being developed, which must establish the necessary and sufficient scope
and timing of tests to ensure the specified reliability of the results obtained. The test program and methodology can be developed
for the System as a whole and (or) its parts. Tests (test cases) can be included as an attachment.

When testing the System, compliance with the Terms of Reference (TOR) for the creation of the System should be checked and established as follows:

• The quality of performing automated functions by the complex of software and hardware in all modes of the System's operation;
• Completeness of the instructions to the personnel contained in the operational documentation on the performance of their functions in all modes of the System's operation;
• Quantitative and (or) qualitative characteristics of the performance of automatic and automated functions of the System;
• Other properties of the System, which it must comply with according to the requirements of the Terms of Reference.

System tests are carried out at the Customer's site. By agreement between the Customer and the Supplier, preliminary tests and acceptance of the System software may be carried out on the Supplier's technical means when conditions are created for obtaining reliable test results.

The status and composition of the acceptance committee is determined by the Customer.

Based on the test results, protocols are drawn up with a list of comments and acts of completion of tests, on the basis of which a decision is made on the possibility (or impossibility) of transition to the next type of test or acceptance of the System into permanent operation. The types of tests can be repeated until all comments to the System are eliminated and the operational documentation is corrected accordingly.

Tests of the System are performed after debugging
and testing of the supplied software and hardware of the System
and the submission by the Contractor of the relevant documents about their readiness for testing, as well as after familiarization of the Customer's technical specialists with the operational documentation of the System.

In the process of operation and testing, the readiness of individual parts, complexes and tasks of the System, as well as the presented documentation, is checked for operation in real conditions. Operation of the System and its parts begins from the moment of approval of the acceptance certificate for operation.

Additional requirements of the Customer arising in the process of preliminary tests and operation, which are not provided for in the terms of reference, are not grounds for a negative assessment of the results of operation and testing. They can be satisfied by an additional agreement within an agreed time frame.

 

1. 1. Types, scope and test methods

At the first stage, the check should be carried out in accordance with the program
and methodology for preliminary tests of the experimental segment, developed by the Contractor and approved by the Customer.

At the stage of trial operation of the experimental segment, an assessment of the completeness of the adopted design decisions should be made, and requirements for revision to a standard replicated solution can be formulated.

After completing the modifications, in accordance with the addendum to the TT, a program and methodology for acceptance tests should be developed.

Preliminary tests

Preliminary tests of the System are carried out to determine its operability and to resolve the issue of the possibility of transferring the System into operation.

Preliminary tests are carried out at a specially equipped stand.

On a larger scale, preliminary tests include 3 stages.

Pilot industrial operation

Pilot industrial operation of the System is carried out to determine the correctness of the design decisions and the constructed information model, to determine the degree of compliance of the System functionality with the users' requirements and the degree of convenience of working with the user graphical interface.

Operations management works include:

• Determination of the Customer's divisions in which the operation will be carried out;
• Determination of the responsible persons of the Customer for the operation;
• Determination of the Customer's employees involved in the operation;
• Determination of preliminary requirements for paper forms of accounting and reporting documentation and approval of temporary regulations for keeping records in organizations participating in the operation;
• Deployment of the System;
• Consultation of the Customer's employees on the rules of working with the System.

During the operation of the System, a work log is kept in which information is entered on the duration of operation, failures, failures, emergency situations, changes in the parameters of the modernization object, corrections of documentation and software, adjustment of technical means. The information is recorded in the journal with the date and the person in charge. The journal may contain staff comments on the convenience of the System operation.

Information entered into the System at the stage of test operation must be deleted from the data warehouse during the transition to the stage of operation and cannot be used to generate any official reporting forms.

Industrial exploitation

Operation of the System, put into operation in accordance with the established procedure, in accordance with the project and the safety of which is confirmed by tests at the stage of pilot operation.

 

1. 1. General requirements for acceptance of works by stages

Below are the main stages and stages performed by the Contractor for the implementation of IP, established in contracts and terms of reference based on O'zDSt 1986: 2018 Information technology. Information Systems. Stages of creation. The main stages of IS implementation are:

• Development of the concept of IS;
• Development of technical specifications;
• Technical project implementation;
• Development of operational documentation;
• Putting IS into industrial operation;
• Further support of IS in accordance with the terms of the contract between the Customer and the Contractor.

The project implementation methodology should be based on the Waterfall methodology.

RASCI matrix (distribution of responsibilities between project participants)

R	Responsible (Ответственный)	The Project Participant performing the Work to achieve the Project Result. Responsible for the achievement of the Result
A	Approver (Утверждающий)	A project participant who approves the correctness and completeness of the work. Accepts the Results of the Works.
S	Support (Соисполнитель)	A project participant who provides support within his competence for the Responsible.
C	Consulted (Консультирующий)	A project participant whose opinion (resources) is taken into account to create the Project Results. Subject matter experts.
I	Informed (Информируемый)	A project participant who is informed about the progress of the Work on the creation of the Project Results.

Tab. 6.2.1 RASCI Matrix (Distribution of Responsibilities among
Project Participants)

 

Responsibility matrix for project results

No.	Stage	Responsible		results
		Executor	Customer
1.	Formation of requirements for the System	R	A, C, S	1. Terms of reference for a business analysis system;
2.	System concept development	R	A, C, S	1. Project charter; 2. Schedule of the project; 3. Report on the results of the work.
3.	Technical task	R, A, C	A, C, S	Terms of reference for data marts in terms of the received reporting on: 1. NSBU; 2. KPI; 3. Fulfillment of the business plan, production indicators, personnel report; 4. Management reporting; 5. IFRS
4.	Design	R, A, C	A, C, S	Development specifications, data mappings in terms of the received reporting on: 1. NSBU; 2. KPI; 3. Fulfillment of the business plan, production indicators, personnel report; 4. Management reporting; 5. IFRS
5.	Working documentation	R	A, C, S	1. Working documentation for the development of reporting
6.	Commissioning	R	R, A, C	Reporting on: 1. NAS 2. KPI 3. Implementation of the business plan, performance indicators, personnel; 4. Management reporting 5. IFRS Guides: 1. Business Analysis System User Guide 2. Business Analysis System Administrator's Guide 3. Acceptance test procedure 4. Acceptance test report

Tab. 6.2.2 Responsibility matrix for project results

1. 1. Requirements for managing organizational change

In the Project, in order to effectively adapt employees to changes in processes, it is required to perform work on Organizational Change Management in the following areas:

Communication

Key tasks:

Ensure general awareness and understanding of all stakeholders about the objectives, scope, benefits and achievements of the Project:

• Create understanding, acceptance and full ownership of the System, organization
  and ways of working
• Help the implementation team make a successful transition to new processes and tools at all levels
• Inform the employees of the Customer about the project, goals and status in general
• Build an understanding of the impact of the change on all stakeholders of the implementation reach and manage expectations

Organizational Design

Key tasks:

• Implement the necessary changes in the organization at the level of roles, positions, organizational structure in accordance with changes
  in business processes:
• Identify changes in the organizational structure, distribution of roles and functions
• Form an understanding of changes in roles and positions for each individual, update job descriptions, communicate changes to employees and managers before starting the training process
• Plan and implement an organizational transition to a targeted organizational structure and distribution of roles and functions

Education

Key tasks:

Training of the system implementation project team:

• Ensure that the team members have the necessary knowledge on the implemented technological platform for the successful implementation of the Project
• Employee training:
• Prepare employees for new responsibilities
  and new ways of working
• Provide employees with the optimal form of training, at the right time and according to the established goals

Preliminary estimate of the number of employees for training:

• Professional training - business users: 50 people

• Professional training - technical specialists: 20 people.

• Training of employees should be conducted in the language agreed with the Customer.

• Training must be conducted in person on the territory of the Customer (by agreement with the Customer, the option of online training may be agreed upon).

• The skills acquired during the training must fully cover the functional skills of the Customer's specialists.

 

Methodological support for Organizational Change Management

Key tasks:

• Identify all stakeholders of the Project
• Transfer knowledge of approaches, methods, techniques, tools used for the effective implementation and management of organizational change management work
• Identify key organizational changes by detailed To Be and interviewing experts about the differences with the current process

Assess the impact of change and readiness for change

• Ensure participation in the formation of a roadmap for work on change management, participation in the formation of key tasks in all areas, in the adaptation of templates and the development of instructions for key tasks
• Quality control of the implementation of tasks for managing organizational changes, the formation of proposals for the required adjustments in the approaches, methods and tools used to implement them
• Support in the management of work, risks and issues of the implementation of tasks at all stages of the project.

 

 

1. REQUIREMENTS FOR THE COMPOSITION AND CONTENT OF WORKS ON PREPARING THE SYSTEM FOR COMMISSIONING

By the time the acceptance tests are carried out, all comments on the operation of engineering systems that ensure the functioning of the Customer's data center must be eliminated.

By the end of the period of trial operation, the maintenance personnel of the system must fully master the practical skills of working with the software and hardware complex.

To prepare the facility for commissioning the System, the Customer must perform the following work:

• Develop and implement, together with the executing organization, an action plan for preparing the modernization object for the implementation of the System (subsystems);
• Develop, together with the developer organization, and approve additions and changes in job descriptions that determine the work of personnel in the conditions of the System's functioning;
• If necessary, make changes to the organizational structure of the enterprise in order to ensure the required number of employees and technical personnel to ensure the operation of the System in accordance with the personnel requirements set out in section 4 of this document;
• Approve the regulatory documents developed as part of the project for the implementation of the System;
• Purchase, install and test technical means that ensure the functioning of the System (subsystems), taking appropriate measures to protect the technical means from external influences and unauthorized access;
• Prepare and execute the necessary organizational and administrative documentation;
• Ensure the solution of organizational issues for consultation
  and advanced training of employees who will work
  with the System;
• Organize the study of the user documentation of the System by all departments and divisions of the authorized body;
• Ensure that users study the operational documentation;
• Prepare reference and other information and enter
  it into the appropriate databases;
• Conduct control tests of the System (subsystems) together
  with the contractor at the workplace of the System administrator.

To prepare an object for commissioning the System, the executing company must:

• Develop and implement, together with the customer organization, an action plan for preparing the facility for the implementation of the System (subsystems);
• Develop and provide users with the necessary operational documentation to work with the applied software of the System;
• Conduct control tests of the System (subsystems, tasks) together with the Customer at the workplace of the System administrator;
• Consult the key users of the System.

 

 

1. DOCUMENTATION REQUIREMENTS
   1. Project documentation

• The list of sets and types of documents to be developed that meet the requirements of O'z DSt 1985: 2018 is agreed by the Contractor with the Customer on the basis of the protocols.
• The ISS documentation must comply with RH 34-381-1022: 2009. "Position. General requirements for the organization of comprehensive protection
  and information security ”.
• The documentation handed over to the Customer must be made
  in paper and electronic form on a carrier.
• The delivery of the System must be accompanied by the submission of a set of documentation of the following composition in Russian:
• User manuals (including operations of loading and manual data entry, work with reporting forms, other means of displaying data, etc. should be described);
• Administrator's Guide (including the procedure for installing and configuring the System - the client side and the DBMS, the procedure for differentiating access rights and managing user accounts, restoring the software in case of failures, auditing, etc.);
• The supplier must provide support and maintain documentation up
  to date for the entire duration of the contract;
• Technical description of the customization of system modules;
• A technical description of the configured integrations;
• Explanations how the Customer in the solution proposed by the Contractor is protected from the need for additional investments during the period of the project until it is put into commercial operation.
• Instructions for setting up business processes for the administrator
  and advanced business user.

 

1. SOURCES OF DEVELOPMENT

The sources for the development of this technical task are state industry standards of the Republic of Uzbekistan, guidelines and methodological materials:

• O'zDSt 1986: 2018 “Information technology. Information Systems. Stages of creation ";
• O'zDSt 1987: 2018 “Information technology. Terms of Reference for the Creation of an Information System ";
• O'zDSt ISO / IEC 2392-8: 2015 “Information technology. Information Security. Terms and Definitions";
• O'zDSt ISO / IEC 27001: 2016 “Information technology. Methods for ensuring the security of the information security management system. Requirements";
• O'zDSt ISO / IEC 27002: 2016 “Information technology. Security methods. Practical rules for information security management ";
• RH 45-170: 2004. Guidance document. "Basic technical requirements for the creation of local and corporate departmental computer networks";
• T 45-194: 2007 "Recommendations for the use of software and hardware to prevent acts of illegal entry into information systems."

 

1. PROJECT ASSUMPTIONS AND RESTRICTIONS
   1. Organizational Assumptions and Constraints

• All meetings on the Project are held on the territory of the Customer's divisions in Tashkent. All negotiations and correspondence, as well as the documentation of the Project are conducted in Russian;
• When implementing a project, the Customer ensures the involvement of employees in the project who have all the necessary information and authority to make decisions on the project;
• The environment for industrial operation of the System is prepared by the Contractor's specialists;
• Starting from the Design phase, the Customer includes 5 specialists in the design team;
• It is assumed that there are technical and organizational capabilities for the work of the Contractor's specialists on the development / testing environments of the Customer, including the possibility of remote work;
• The terms of implementation of the Solution depend on the clarified requirements and the timing of the implementation of improvements and the implementation of design work on the side of the Customer. The timing of the completion of each of the stages should be clarified based on the results of the analysis of the requirements and the preparation of a joint schedule;
• The area of ​​responsibility of the Consultant does not include control over the timing and results of related projects, the results of which may be related to the project for the implementation of the target system;
• The warranty technical support of the system is limited to the period of trial operation and is 1 (one) year. Warranty technical support includes only cases of elimination of defects, i.e. inconsistency of the result of the Services provided with the relevant technical requirements and / or other project documentation developed within the framework of the project, which arose through the fault of the Contractor;
• On the part of the Customer, a project manager is allocated for the entire duration of the project, who is the main entry point for communication with the Customer, and also coordinates the work of the Customer's divisions taking part in the project;
• On the Customer's side, the availability of key specialists (IT and business units) must be ensured for meetings, conferences, interviews to collect requirements in accordance with the requirements of the Consultant, which will be developed at the stage of project planning;
• The project evaluation does not include stress testing of the system. Such testing can be performed outside the scope of this assessment after the requirements for stress testing have been agreed.

 

• 1. Restrictions on the scope of work
• When distributing responsibility for specific work between the Contractor and the Customer, it is necessary to be guided by the matrix, the distribution of responsibilities by the project participants;
• If during data migration it is required to save the history of operations for the previous reporting periods, then the Contractor will arrange for the migration of this data on the registration cards of objects.

 

• 1. Limitations on the scope of work
• A detailed list of automated reporting is formed at the stage of the project "Detailed analysis of reporting requirements" in the form of a separate application;
• It is assumed that the main source of integration for building a system of accounting and monitoring the activities of enterprises
  with state participation is the existing database of the Agency, the database of the State Oil Company, the web-form (kpi.davaktiv.uz);
• It is assumed that the depth of migrated data from the systems of the Customer's sources does not exceed 2 years.

 

• 1. Limitations on implemented functionality
• The work on the completion of the adjacent systems of the project in the integration contour is carried out by the efforts of the Customer;
• The work on the deployment of the IT infrastructure necessary for the implementation of the project is carried out by the Contractor.

 

• 1. Restrictions on the composition and form of results
• Project documents are prepared on the basis of templates provided by the Agency and agreed at the stage of project preparation;
• The format of the results and the procedure for their acceptance for each phase of the project are determined jointly by the Contractor and the Customer at the beginning of each phase of the project.

 

1. 1. Terms of the Project execution

During the execution of the Project, the following conditions are expected to be met:

• The Project will be managed in accordance with the approved Charter.

Providing conditions for the successful work of the project team, the availability of the necessary infrastructure, including premises and equipment for the functioning of the System.