{"rows":20,"os":"0","page":"1","total":"16","procnotices":[{"id":"OP00454957","notice_type":"Request for Expression of Interest","noticedate":"22-Jul-2026","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2026-08-07T00:00:00Z","submission_deadline_time":"04:30","project_ctry_name":"Caribbean","project_id":"P179210","project_name":"OECS- Skills and Innovation Project","bid_reference_no":"LC-OECS COMMISSION-558060-CS-QCBS","bid_description":"Consultancy Services: Independent Technical Assurance (ITA)","procurement_group":"CS","procurement_method_code":"QCBS","procurement_method_name":"Quality And Cost-Based Selection","contact_address":"P.O. Box 179 \nMorne Fortune \nCastries \nSaint Lucia","contact_ctry_name":"St. Lucia","contact_email":"francillia.solomon@oecs.int","contact_name":"Francilia Solomon","contact_organization":"Organization of Eastern Caribbean States Commission","contact_phone_no":"758-455-6300","submission_date":"2026-07-22T00:00:00Z","notice_text":"

ORGANISATION OF EASTERN CARIBBEAN STATES

REQUEST FOR EXPRESSIONS OF INTEREST

NAME OF PROJECT - OECS SKILLS AND INNOVATION PROJECT (SKIP)

GRANT NO.: E286

Assignment Title: Consultancy Services for an Independent Technical Assurance (ITA)

Reference No. LC-OECS COMMISSION-558060-CS-QCBS

 

The Organisation of Eastern Caribbean States (OECS) has received financing from the World Bank toward the cost of the OECS Skills and Innovation Project (SKIP) and intends to apply part of the proceeds to Consultancy Services for an Independent Technical Assurance (ITA).

The objectives of the consulting services (“the Services) are to provide independent, evidencebased technical validation of the existing builds (KTIP and Virtual Campus) and of the sourced EMIS DPG and its adaptation, and to provide feedback to the SDT on how to bring each platform to a regionallydeployable standard through an iterative cycle of review, recommendations, remediation, and signoff.

 

The OECS 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. The minimum required qualifications and experience are listed in section 8.0 of the TOR below.  The Qualifications and Experience of Key Experts shall not be included in the shortlisting criteria. Key Experts will not be evaluated at the shortlisting stage.

 

The attention of interested Consultants is drawn to Section III, paragraphs 3.14, 3.16, and 3.17 of the World Bank’s “Procurement Regulations for IPF Borrowers” September 2023 and (‘Procurement Regulations’), setting forth the World Bank’s policy on conflict of interest. 

To obtain the maximum degree of comparison among Expressions of Interest (EOIs) and facilitate the evaluation process, the EOI should be a maximum of 20 pages (including annexes) with the following information included below.  Any pages exceeding this limit will not be considered for evaluation or shortlisting.

 

 

Consultants may associate with other firms to enhance their qualifications, but should clearly indicate whether the association is a joint venture and/or a sub-consultancy. In the case of a joint venture, all partners shall be jointly and severally liable for the entire contract, if selected.

    

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 08:30 a.m. – 4:30 p.m. (0830 to 1630 hours).

Organisation of Eastern Caribbean States

OECS Skills and Innovation Projects

P.O. Box 179
Morne Fortune
Castries
Saint Lucia
TEL: +1 758-455-6349/68

E-mail: procurement@oecs.int

An electronic copy of the Expressions of Interest must be sent by August 7, 2026, at 4:30 p.m. to:

Yasmine Anatole, Procurement Officer

At the following email address:

procurementbids@oecs.int

copied to: skip@oecs.int       

The email submissions should include the Firm's name and address and shall be clearly marked in the subject line as “Expression of Interest – Consultancy Services for an Independent Technical Assurance (ITA).”

The Terms of Reference for the Submission of Expressions of Interest for this consultancy are provided below.

 

 
  

 

 

 

 

 

TERMS OF REFERENCE

CONSULTANCY SERVICES FOR AN INDEPENDENT TECHNICAL ASSURANCE (ITA) FOR THE OECS SKILLS AND INNOVATION PROJECT (SKIP)

    

Terms of Reference

Independent Technical Assurance (ITA)

Consultancy

Technical Assurance and Iterative Validation of the KTIP, OECS Virtual Campus, and Regionally-Interoperable Post-Secondary EMIS Architecture under the OECS Skills and Innovation Project (SKIP)

Revised draft v 6— 22 June 2026

1. Background and Project Context

The OECS Skills and Innovation Project (SKIP) is a World Bank–financed regional operation implemented by the Organisation of Eastern Caribbean States (OECS) Commission and the participating OECS Member States of Grenada and Saint Lucia. The Project’s Development Objective (PDO) is to enhance youth transversal and advanced technical skills, strengthen regional collaboration in post-secondary education, and foster collaborative innovation across the OECS Member States.

The OECS SKIP is structured around four components:

Component 1 is designed to generate regional platforms, standards, and systems that benefit all nine OECS Member States and create economies of scale that individual countries cannot efficiently achieve on their own. Key activities under Component 1 include: (i) development of a regional strategic framework for postsecondary education; (ii) common learning standards and assessment tools for priority skills; (iii) harmonised standards for postsecondary faculty and institutional leadership; (iv) the OECS Virtual Campus; (v) the Knowledge, Technology and Innovation Platform (KTIP); and (vi) a regionally interoperable postsecondary Education Management Information System (EMIS) architecture.

1.1 Current state of the three Component 1 platforms

The three platforms that fall within the scope of this assignment are at materially different stages and follow materially different delivery models. The Independent Technical Assurance (ITA) Consultancy’s engagement is calibrated to those differences.

 

 

Across all three platforms, a prior technical assessment confirmed the viability of the chosen delivery approach but identified material risks related to scalability and performance at the regional level; integration across heterogeneous systems; production readiness; data governance and crosscountry compliance; and capacity constraints and longterm sustainability.

To mitigate these risks, the OECS Commission will engage a suitably qualified firm to serve as an Independent Technical Assurance Consultancy (ITA), providing independent technical assurance and certification across the lifecycle stages relevant to each platform, operating under the iterative reviewandvalidation model set out in Section 4.

Independence is a foundational requirement. The credibility of the ITA’s findings depends on a firm distinction between the ITA’s assurance role and the SDT’s development role. The ITA reviews and validates; the SDT implements. The ITA’s recommendations should specify what must be remediated and to what standard, with the implementation approach reserved for the SDT. This distinction, set out in detail in Section 4.1, Section 7, and Section 10, is foundational to the assignment and is nonnegotiable.

2. Objective and Role of the ITA

The objective of this assignment is to provide independent, evidencebased technical validation of the existing builds (KTIP and Virtual Campus) and of the sourced EMIS DPG and its adaptation, and to provide feedback to the SDT on how to bring each platform to a regionallydeployable standard through an iterative cycle of review, recommendations, remediation, and signoff.

2.1 Consolidated role description

The ITA shall act as a technical assurance and function across the full lifecycle of the three Component 1 platforms. The role comprises six discrete functions, all of which are exercised iteratively across the validation gates set out in Section 4.2:

This role description is the single, limited-scope document detailing the ITA’s functions. Subsequent sections elaborate the operational mechanics (Section 4), the phased activities (Section 5), and the institutional arrangements that support the role (Section 7).

 

3. Scope of Work

3.1 Platforms covered

The ITA shall provide technical assurance across the three SKIP Component 1 platforms and their integrations:

3.2 Differentiated assurance pathway by platform

Given the different starting positions of the three platforms, the ITA shall apply a differentiated assurance pathway, agreed in the Inception Report (D1). The pathways are articulated below; while KTIP and the Virtual Campus follow the same gate sequence, the substantive content of the review at each gate differs due to their distinct architectures and codebases.

Platform

Starting Position

ITA Pathway

KTIP

Existing SDT build, ~80% complete.

Baseline audit of existing KTIP build → Recommendations → SDT remediation → ITA revalidation & signoff → Predeployment certification → GoLive → Postdeployment review.

Virtual Campus (LearnBoard)

Existing SDT build, ~80% complete.

Baseline audit of existing Virtual Campus build against the approved Mobile Specification and target architecture → Recommendations → SDT remediation → ITA revalidation & signoff → Predeployment certification → GoLive → Postdeployment review.

Regional EMIS

To be sourced as a Digital Public Good (DPG); adaptation by SDT and partners.

DPG suitability & compliance validation → Recommendations on adaptation scope → SDT adaptation → ITA revalidation & signoff → Predeployment certification → GoLive → Postdeployment review.

 

The ITA’s role is to validate existing or sourced builds and to certify that successive remediation cycles have brought the three platforms to the required standard.

3.3 Integration scope- to ensure proper scope integration across the platforms, the ITA will seek to:

3.4 Assessment Dimensions: The ITA will undertake relevant assessments as follows:

A. Platform-Level

B. Documentation

The ITA shall assess the completeness, accuracy, and usability of technical and operational documentation associated with each platform, including:

Documentation completeness is assessed at the G2 Build Completion gate (Section 4.2), not at predeployment, so that any gaps identified can be remediated alongside other build issues.

C. DPG-Specific (EMIS only)

For the regional interoperable EMIS, the ITA shall review and assess:

D. Ecosystem-Level (System-of-Systems)

4. Technical Assurance Framework

4.1 Iterative ReviewandValidation Cycle

The ITA shall operate under an iterative reviewandvalidation cycle, applied on a per-platform basis. Each cycle consists of four steps and is the unit on which RBF approval for expenditures for the next tranche of activities proposed by the RPIU is structured:

Step 1 — Review. The ITA reviews the existing build (KTIP, Virtual Campus) or the sourced DPG and its adaptation (EMIS) against the agreed criteria for the cycle.

Step 2 — Recommendations. The ITA issues written recommendations to the SDT. Recommendations shall be scoped at the level of what must be remediated and to what standard, with clear acceptance criteria.

Step 3 — SDT implementation and testing. The SDT implements the recommendations and conducts its own internal testing. The SDT shall submit to the ITA a remediation evidence pack documenting the changes made, the testing performed, and the results obtained.

Step 4 — Revalidation and signoff. The ITA revalidates the platform against the acceptance criteria stated in its recommendations. Where the criteria are met, the ITA issues a written signoff for the build phase, thereby triggering approval of expenditures for the corresponding RBF tranche of RPIU activities. Where criteria are not met, the cycle returns to Step 2 with revised or supplementary recommendations.

Cycles are platformspecific. KTIP, the Virtual Campus, and the EMIS may proceed through their cycles in parallel or in different sequences, as agreed in the Inception Report.

Decoupling ITA fees from SDT performance. The ITA’s entitlement to its own contractual fees is determined by the delivery of each ITA deliverable (Section 6), not by whether the SDT achieves a positive signoff in any given cycle. A Remediation Required determination represents a completed and payable piece of ITA work as much as a Validated determination does. This separation is critical to the integrity of the assignment: the ITA’s fees must not depend on the speed or quality of the SDT’s remediation, since such dependence would create a structural incentive to issue premature positive signoffs. RBF approval of expenditures for the tranche of activities is to the RPIU, on the strength of ITA signoff; the ITA itself is paid on the OECS Commission’s acceptance of its determinations and reports per Section 6.

4.2 Validation Gates

Each platform progresses through a sequence of validation gates. The gates are eventbased: a gate is triggered when the SDT submits the corresponding deliverable package, not on a fixed calendar date. A mapping of the milestones and key dates will be presented during the inception meeting. The gates and their applicability per platform are as follows:

 

 

Gate

Trigger

Deliverable from SDT

ITA Role

Outcome on Sign-off

G1 — Baseline / DPG Validation

 

 

SDT presents the current build status pack (KTIP, VC) or DPG suitability assessment and adaptation plan (EMIS) at the point of ITA engagement.

Build status pack documenting work completed to date (KTIP, VC); DPG suitability assessment and adaptation plan (EMIS).

Review and acknowledge the baseline; confirm that the scope, architecture, and DPG positioning are consistent with the SKIP requirements, as documented in the project documents; record any observations to inform subsequent gates.

Baseline of record established. Expenditures for Tranche 1 of activities proposed by the RPIU are approved.

G2 — Architecture Lock-in & Pilot Validation

SDT submits an integrated build with pilot deployment in selected institutions across lead Member States, supported by load-testing evidence and pilot monitoring data.

Integrated build with technical and operational documentation; architecture specification proposed for lock-in; security, performance and load-testing results against agreed thresholds; pilot deployment in selected institutions with monitoring data over an agreed observation window; user acceptance testing outcomes from pilot sites.

Review, recommend, re-validate. Confirm architecture is fit for regional deployment and may be locked in; verify load and performance behaviour under realistic institutional conditions; certify pilot outcomes against acceptance criteria.

Architecture locked in. Expenditures for  Tranche 2 of activities proposed by the RPIU are approved.

G3 — Regional Go-Live & Post-Deployment

SDT submits the regional innovations deployment plan and proceeds with rollout across Member States.

Regional deployment evidence across the nine Member States; post-deployment monitoring data; operational handover documentation; sustainability and support arrangements.

Validate regional innovation deployment, conduct a final audit, and issue sustainability recommendations.

Regional go-live certified. Expenditures for the final tranche of activities proposed by the RPIU are approved.

 

Within each gate, the fourstep iterative cycle (Section 4.1) may be repeated as many times as is necessary for the platform to meet the acceptance criteria. The ITA shall not artificially compress the cycle, but recommendations and revalidations shall be issued within the timeliness windows set out in Section 4.3.

ITA mobilisation timing. Given that KTIP and the Virtual Campus are at approximately 80% completion, ITA mobilisation must take place as soon as practicable following procurement, and shall not be deferred to align with the EMIS DPG sourcing timeline. The OECS Commission RPIU shall ensure that the procurement schedule supports mobilisation in time for the first G1 baseline audit of KTIP and the Virtual Campus. Where ITA mobilisation cannot be completed in time for an applicable gate, the OECS Commission RPIU shall document the gap and either (a) defer the affected gate or (b) authorise SDT continuation under a documented risk acceptance, with ITA retrospective review at the next gate.

 

4.3 Decision Authority and Timeliness

At each validation point within a gate, the ITA shall issue one of the following determinations:

Review turnaround. The ITA shall issue its determination within 10 working days of receipt of the complete deliverable package or remediation evidence pack from the SDT. Where the ITA requires further information, the 10workingday clock pauses upon issuance of a written information request and resumes upon receipt. The SDT shall respond to ITA information requests within 5 working days. The OECS Commission recognises that the SDT operates as a volunteer regional network, and prolonged review periods materially affect the SDT’s ability to maintain delivery momentum.

Recommendations specificity. Each recommendation issued by the ITA shall include: (i) a clear statement of the issue identified; (ii) the standard or criterion that is not met; (iii) the acceptance criteria that the SDT’s remediation must satisfy; and (iv) the evidence required from the SDT to support revalidation. The ITA shall not issue findings that are nonspecific, that prescribe a particular implementation approach, or that require openended further review.

Dispute resolution. Where the OECS Commission RPIU or the SDT documents a goodfaith technical disagreement with a Remediation Required or Critical Issues determination, the RPIU may, with World Bank concurrence, refer the matter to an independent technical panel for a binding second opinion. The panel shall comprise three subjectmatter experts who have not previously been engaged on the Project, jointly nominated by the OECS Commission and the World Bank. The cost of the panel shall be borne by the Project. This mechanism does not extend to findings issued under the Escalation Protocol (Sec. 7.5).

5. Phased Activities

5.1 Inception, Baseline Audits, and DPG Validation

On mobilisation, and applied per platform, the ITA shall:

5.2 Iterative Review and Remediation Oversight

During the buildcompletion and integration stages, the ITA shall, per platform:

5.3 Testing, Validation, and Quality Assurance

Minimum benchmarks (to be refined at inception):

5.4 Data Governance and DPI Readiness

5.5 PreDeployment Certification and GoLive

No deployment shall proceed without ITA certification.

5.6 PostDeployment and Scale Readiness

6. Deliverables and Payment Structure

Each substantive deliverable is delivered per platform: KTIP, OECS Virtual Campus, and Regional Post-Secondary EMIS. The payment share for D2 through D6 is split across the three platforms, so that the ITA’s entitlement under any deliverable is contingent on completion of that deliverable for each platform to which it applies. D1 (Inception) and D5 (Final Audit) are single combined deliverables across all three platforms.

The ITA is paid for delivering its own determinations and reports. The ITA is not paid contingent on the SDT achieving a Validated outcome: a properlyissued Remediation Required or Critical Issues determination is a delivered piece of ITA work and is payable on the same basis as a Validated (or Validated with Recommendations) determination. Conversely, approval of expenditures for the RBF tranche of activities proposed by the RPIU is contingent on the ITA’s Validated or Validated with Recommendations signoff for the corresponding gate.

 

Ref

Deliverable

Description

Per Platform Share

Total Share

D1

Inception Report and Workplan

Single combined report covering KTIP, Virtual Campus, and EMIS: audit framework, scope confirmation, per-platform pathway, pilot scope and load-testing thresholds for G2, risk register, review schedule.

—

10%

D2a

G1 Baseline Validation Report — KTIP

Baseline audit of the existing KTIP build with determination per Sec. 4.3 and recommendations register.

5%

—

D2b

G1 Baseline Validation Report — Virtual Campus

Baseline audit of the existing Virtual Campus build with determination per Sec. 4.3 and recommendations register.

5%

—

D2c

G1 DPG & Adaptation Validation Report — EMIS

Validation of the DPG suitability assessment and the proposed adaptation scope with determination and recommendations register.

5%

D2 sub-total: 15%

D3a

G2 Architecture Lock-in & Pilot Validation Report — KTIP

Per-cycle audit reports across the G2 review-and-validation cycle: architecture review, load and performance testing review, security and UAT outcomes, pilot deployment validation across selected institutions, recommendations register, SDT remediation responses, re-validation outcome, sign-off determination, and architecture lock-in certification. This triggers the approval of SDT KTIP expenditures for tranche 2 activities.

13.33%

—

D3b

G2 Architecture Lock-in & Pilot Validation Report — Virtual Campus

Per-cycle audit reports across the G2 review-and-validation cycle: architecture review, load and performance testing review, security and UAT outcomes, pilot deployment validation across selected institutions, recommendations register, SDT remediation responses, re-validation outcome, sign-off determination, and architecture lock-in certification. This triggers the approval of SDT Virtual Campus expenditures for tranche 2 activities.

 

13.33%

—

D3c

G2 Architecture Lock-in & Pilot Validation Report — EMIS

Per-cycle audit reports across the G2 review-and-validation cycle: architecture review, load and performance testing review, security and UAT outcomes, pilot deployment validation across selected institutions, recommendations register, SDT remediation responses, re-validation outcome, sign-off determination, and architecture lock-in certification. This triggers the approval of SDT EMIS expenditures for tranche 2 activities.

13.34%

D3 sub-total: 40%

D4a

G3 Regional Go-Live & Post-Deployment Report — KTIP

Go / Conditional Go / No-Go certification for regional rollout; post-deployment stability and adoption findings; sustainability recommendations for KTIP. This triggers the approval of SDT KTIP expenditures for the final tranche.

 

8.33%

—

D4b

G3 Regional Go-Live & Post-Deployment Report — Virtual Campus

Go / Conditional Go / No-Go certification for regional rollout; post-deployment stability and adoption findings; sustainability recommendations for Virtual Campus. This triggers the approval of SDT Virtual Campus expenditure for the final tranche.

 

8.33%

—

D4c

G3 Regional Go-Live & Post-Deployment Report — EMIS

Go / Conditional Go / No-Go certification for regional rollout; post-deployment stability and adoption findings; sustainability recommendations for EMIS. This triggers the approval of SDT EMIS expenditures for the final tranche.

 

8.34%

D4 sub-total: 25%

D5

Final Audit Report

Single combined report across KTIP, Virtual Campus, and EMIS: scale readiness and sustainability recommendations across the regional deployment.

—

10%

Total contract value: 100%, comprising D1 (10%) + D2 (15%) + D3 (40%) + D4 (25%) + D5 (10%). The per-platform structure ensures that the ITA's payments are tied to completion of work on each named platform, rather than to a single global completion event that could be dominated by the slowest platform.

All deliverables shall be submitted in English using both Word and PDF formats.

 

7. Reporting and Institutional Arrangements

7.1 Reporting Line: The ITA shall report to the OECS Commission through the reporting line confirmed by the OECS Commission prior to contract effectiveness. The reporting arrangement shall preserve the ITA’s independence from the SDT and from any other unit of the OECS Commission whose work is subject to audit. For daytoday coordination, the ITA shall liaise with the RPIU Project Manager and/or the relevant Technical Specialists. The ITA reports to the Director General or his designee, who shall be confirmed in writing by the OECS Commission prior to the issuance of the request for proposals.

7.2 Independence and NonInterference: The ITA operates as an independent function. OECS Commission leadership commits to ensuring the ITA’s independence is protected and that no impediment is placed on the ITA’s access or on the integrity of its findings.

7.3 Constructive Engagement with the SDT: The iterative reviewandvalidation model requires the ITA to engage constructively with the SDT throughout each cycle. The ITA shall: (i) issue recommendations that are clear, specific, and actionable; (ii) make itself available for technical clarification discussions on the meaning and scope of its recommendations, without prescribing implementation; (iii) share draft determinations with the SDT before finalising, to allow opportunity to respond to or clarify factual matters; and (iv) maintain a working relationship oriented toward bringing each platform to the required standard. This constructive engagement does not affect independence; final conclusions, recommendations, and signoff determinations remain the ITA’s sole determination.

7.4 World Bank Interface: The ITA’s deliverables shall be submitted simultaneously to the OECS Commission and to the World Bank task team. The ITA may be requested to participate in project implementation support missions, midterm reviews, or technical briefings organised by the World Bank. Coordination on such requests shall be managed through the RPIU.

7.5 Escalation Protocol: If the ITA identifies a finding that poses a significant risk to the Project, including serious technical failure, system instability, security breaches or vulnerability, material deviation from approved design, data integrity breaches or risks, or misuse of project resources, the ITA shall notify the senior officer to whom it reports (Sec. 7.1) in writing within 5 working days. The OECS Commission shall acknowledge and advise on next steps within 5 working days. The SDT lead shall be notified at the same time as the senior officer to enable a timely operational response. The World Bank shall be informed within the same 5workingday window, accompanied by a brief contextual note from the OECS Commission RPIU where the RPIU determines such context is necessary for accurate interpretation of the finding. The provision of an RPIU contextual note shall not delay World Bank notification beyond 5 working days.

7.6 Access and Cooperation: OECS Commission staff and consultants, including members of the inhouse development team (i.e. SDT), are required to cooperate fully with the ITA and to provide timely access to all documentation, source code, test environments, development records, and personnel reasonably requested. As far as practicable, the OECS Commission shall invite the ITA to relevant technical meetings specific to design reviews, sprint reviews, testing sessions, and demonstrations. The ITA shall be granted readonly access to the inhouse team’s source code repositories, architecture documentation, test environments and logs, deployment pipelines, project management tools, and documentation repositories. The Project Manager in the RPIU shall respond to ITA information requests within 5 working days.

 

8. Qualifications and Staffing

The assignment shall be delivered by a firm. Individual consultancy arrangements are not permitted, in line with World Bank requirements for the assignment. The firm shall mobilise the key expert team set out in Section 8.2 and shall meet the firmlevel experience requirements set out in Section 8.1.

 

8.1 Firm-level qualifications and experience

The firm or consortium shall demonstrate the following at the proposal stage:

8.2 Key experts required

The firm shall propose the following five key expert positions. Each position must be filled by a separate qualified individual. The Team Leader shall be clearly identified throughout the proposal as the firm’s single named accountable individual for the assignment.

Team Leader / Senior Technical Auditor

The Team Leader is the firm’s single named accountable individual for the assignment, the primary author of the Inception Report (D1), the Final Audit Report (D7), and all gate signoff determinations, and the principal interlocutor with the OECS Commission and the World Bank.

Systems Architect / Integration Specialist

Cybersecurity and Data Protection Specialist

Testing and Quality Assurance Specialist

 

Digital Public Goods and EMIS Specialist

9. Duration and Level of Effort

The assignment is expected to commence in Q3 2026, subject to confirmation of the procurement schedule prior to the issuance of the request for proposals. Given that KTIP and the Virtual Campus are at approximately 80% completion, the procurement and mobilisation schedule shall be designed to support ITA mobilisation in time for the first G1 baseline audit, and a target mobilisation date shall be confirmed by the OECS Commission RPIU when issuing the request for proposals.

Total assignment duration is estimated at approximately 18 months from contract effectiveness, covering the iterative cycles, predeployment certification, and postdeployment stabilisation across all three platforms. Engagement on KTIP and the Virtual Campus shall conclude as each completes its postdeployment stabilisation gate; engagement on EMIS shall continue through its DPG adaptation, pilot, and stabilisation gates.

Total estimated level of effort (LOE) is approximately 110 to 130 working days. “Level of effort” refers to the total number of professional working days, aggregated across the firm’s key experts, that the firm is expected to expend in delivering the assignment. The LOE is not continuous: engagement is concentrated around platformspecific gates, iterative review cycles, testing phases, and reporting dates. The indicative LOE distribution is as follows:

Component

Indicative LOE (days)

Basis

Inception, baseline audits (KTIP, VC), DPG validation (EMIS)

20–25

Three platforms: two baseline audits of existing builds and one DPG suitability validation

Iterative reviewandvalidation cycles

35–40

Multiple cycles per platform; expected 2 cycles per platform between G1 and G3

Testing, validation, and security clearance

20–25

All three platforms

Predeployment certification and golive

15–20

Perplatform Go / NoGo decisions

Postdeployment monitoring and final audit

20–20

Stabilisation review and scaling recommendations

 

A detailed work plan, with the Level of Effort broken down by platform, by gate, and by expected number of cycles, shall be finalised in the Inception Report (D1) within 10 working days of contract effectiveness.

10. Ethical Standards, Independence, and Confidentiality

The ITA shall at all times:

Conflict of Interest Declaration. All members of the ITA team must submit a signed conflictofinterest declaration before the contract takes effect. Any new conflict arising during the assignment must be disclosed within five (5) working days.

11. Intellectual Property

All reports, audit plans, assessment notes, tools, checklists, and other materials produced under this assignment shall be the exclusive property of the OECS Commission. The ITA shall deliver copies of all working documentation upon request and upon contract completion. The ITA shall not retain, publish, or use these materials without prior written consent from the OECS Commission.

 

 

"},{"id":"OP00437275","notice_type":"Request for Expression of Interest","noticedate":"08-Apr-2026","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2026-04-28T00:00:00Z","submission_deadline_time":"17:00","project_ctry_name":"Lebanon","project_id":"P181954","project_name":"GFPP for Lebanon Digital Acceleration Project","bid_reference_no":"LB-OMSAR-537752-CS-CQS","bid_description":"e-services, Business Process Reengineering Foundational Work as part of Re-inventing Government (6 priority services)","procurement_group":"CS","procurement_method_code":"CQS","procurement_method_name":"Consultant Qualification Selection","contact_address":"STARCO Building, Block A, 5th Floor, Omar Daouk Street, Mina Al Hosn City: Beirut, Lebanon","contact_ctry_name":"Lebanon","contact_email":"mhammoud@omsar.gov.lb","contact_name":"Mirvat Hammoud","contact_organization":"Office of the Minister of State for Administrative Reform","contact_phone_no":"+961 (1) 371 505","submission_date":"2026-04-08T00:00:00Z","notice_text":"

REQUEST FOR EXPRESSIONS OF INTEREST (REOI)

\n\n

CONSULTANT’S QUALIFICATIONS BASED SELECTION (CQS)

\n\n

E-Services, Business Process Reengineering Foundational Work as part of Re-Inventing Government

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Name of Project

\n\t\t\t		\n\t\t\t

GFPP for Lebanon Digital Acceleration Project (LDAP)

\n\t\t\t
\n\t\t\t

Loan No/Credit No/ Grand Number

\n\t\t\t		\n\t\t\t

TF0C8895

\n\t\t\t
\n\t\t\t

Assignment Title

\n\t\t\t		\n\t\t\t

E-Services, Business Process Reengineering Foundational Work as part of Re-Inventing Government

\n\t\t\t
\n\t\t\t

Procurement Plan Ref Number

\n\t\t\t		\n\t\t\t

LB-OMSAR-537752-CS-CQS

\n\t\t\t
\n\t\t\t

Country of Delivery

\n\t\t\t		\n\t\t\t

Lebanon

\n\t\t\t
\n\n

The Office of the Minister of State for Administrative Reform (OMSAR) has received financing from the World Bank toward the cost of the Preparation Grant for the Lebanon Digital Acceleration Project (LDAP) and intends to apply part of the proceeds for the following consulting services.

\n\n

The consulting services (“the Services”) include the end-to-end improvement and digital transformation of six (6) priority public services within selected sectors/clusters. The assignment utilizes an agile methodology (MVP, alpha, and beta stages) to diagnose "As-Is" processes, redesign "To-Be" workflows, classify data according to the National Data Classification Policy, and integrate electronic signature use cases. The Consultant will configure these services on Lebanon’s National Portal, a low-code automation platform, and provide capacity building for civil servants. The estimated implementation period is five (5) months from the contract commencement date.

\n\n

The detailed Terms of Reference (TOR) for the assignment is attached to this REOI.

\n\n

OMSAR 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.

\n\n

The attention of interested Consultants is drawn to paragraph 3.14, 3.16 and 3.17 of the World Bank’s Procurement Regulations for IPF Borrowers dated September 2025 (“the Regulations”), setting forth the World Bank’s policy on conflict of interest.

\n\n

The best qualified firm to carry out the services will be selected in accordance with the Consultant’s Qualifications Based Selection (CQS) method set out in the Regulations and based on the following criteria:

\n\n

Mandatory Minimum Requirements:

\n\n\n\n

Desirable Requirements (Technical and Managerial Capability):

\n\n\n\n

(Note: The qualifications and experience of Key Experts shall not be evaluated at this shortlisting stage).

\n\n

To ensure a complete submission, the Expression of Interest (EOI) must include the following minimum documentation:

\n\n\n\n

Further information can be obtained at the address below during office hours (09:00 AM to 04:00 PM Beirut Time).

\n\n

Expressions of interest must be delivered in a written form to the address below (in person, or by mail, or by e-mail) by COB 28 April, 2026.

\n\n

 

\n\n

Office of the Minister of State for Administrative Reform (OMSAR)

\n\n

Technical Unit – Preparation Grant for Lebanon Digital Acceleration Project

\n\n

Attn: Ms. Mirvat Hammoud – Procurement Specialist

\n\n

Address: STARCO Building, Bloc A, 5th Floor, Room 505a

\n\n

Omar Daouk Street, Mina El Hosn Sector

\n\n

Beirut, Lebanon

\n\n

Tel: +961 (1) 371 505; ext. 160

\n\n

E-mail: mhammoud@omsar.gov.lb

\n\n

 

\n\n

Attachment: Terms of Reference (TOR)

\n\n

 

\n\n

TERMS OF REFERENCE

\n\n

PREPARATION GRANT FOR LEBANON DIGITAL ACCELERATION PROJECT (P181954)

\n\n

E-Services, Business Process Reengineering Foundational Work as part of Re-Inventing Government

\n\n
    \n\t
  1. Background
    2. \n
\n\n

Lebanon’s public administration has remained largely unchanged for decades, operating with outdated structures, fragmented mandates, widespread vacancies, and weak digital and human capital systems. Combined with paper-based processes, siloed information systems, and manual approval workflows, these constraints have resulted in inefficient service delivery, duplication of roles, limited transparency, and a growing gap between government capabilities and citizen expectations.

\n\n

 

\n\n

In response, the Government of Lebanon, with support from the World Bank, as part of the Lebanon Digital Acceleration Project (LDAP), is undertaking a strategic investment aimed at modernizing public administration and strengthening the core digital enablers required for trusted digital service delivery. To support project readiness, the World Bank’s Grant Facility for Project Preparation (GFPP) has been extended to the Office of the Minister of State for Administrative Reform (OMSAR). The GFPP grant is implemented by a Technical Unit (TU) housed within OMSAR.

\n\n

 

\n\n

In parallel, OMSAR, under direct government sponsorship, has launched “Reinventing Government 2030” a whole of government reform effort that aims to restructure the public sector into a coherent, citizen centric, mission driven public administration.

\n\n

 

\n\n

The reform is structured in phases progressively building toward implementation. It began with the Stakeholders’ Aspirations phase, which defined a forward-looking vision for Lebanon’s public administration and establishing guiding design principles. This phase has been completed. It is followed by the development of a Blueprint for Public Sector Reform, encompassing baseline assessments and benchmarking of current institutions and services, and the piloting of the proposed model across selected ministries. The final phase focus is on implementation, including the re-engineering and digitization of priority public services, supported by the necessary legal and regulatory changes.

\n\n

 

\n\n

To support service transformation under this agenda, OMSAR is advancing key digital foundations as part of the LDAP. These efforts will be undertaken by OMSAR and OMSTAI within their mandates and technical expertise and in coordination with relevant stakeholders, ensuring consistency with national digital transformation, national digital trust, data governance, and interoperability frameworks. This includes the development of a National Data Classification Policy, as well as targeted support to the electronic signature framework under the existing legal system. In particular, OMSAR will work closely with the Lebanese Accreditation Council (COLIBAC) to support the definition of practical requirements and baseline criteria for electronic signature accreditation and use.

\n\n

 

\n\n

The activities are intended to be implemented in parallel and informed by practical application in real service contexts. Within this framework, e-services constitute the operational layer through which institutional reform and key digital enablers are translated into tangible improvements in service delivery.

\n\n

 

\n\n

As part of the preparatory work, an initial service prioritization exercise across several ministries has been carried out to identify potential candidate services for the assignment. Indicative examples of such services, and which are non-exhaustive and non-binding, and are subject to further validation, include digital diploma attestation, trader registration and clearance services, tourism licensing digitization, payment of fees for investment and right-of-way services, and selected municipal and sectoral permits.

\n\n

 

\n\n

The redesign and digitization of selected priority public services will enable the practical piloting of data classification and the integration of one or more electronic signature use cases within end-to-end government workflows.

\n\n

 

\n\n

This initiative will create a controlled environment to apply data classification rules and electronic signature mechanisms in practice, generate actionable lessons, and support future scale-up under the full LDAP through a phased and realistic expansion of digital public services in Lebanon.

\n\n
    \n\t
  1. Assignment and Objective
    2. \n
\n\n

The objective of this assignment is to establish an evidence-based, end-to-end improvement of priority public services within selected sector(s)/cluster(s). This will be achieved through an agile approach, utilizing MVP (Minimum Viable Product), alpha, and beta stages. This requires various iterations in diagnosing current service processes and organizational arrangements, redesigning workflows to remove pain points and operational bottlenecks, digitizing service-delivery practices, applying data classification requirements and operationalizing one or more electronic signature use cases within real government workflows to ensure consistent execution.

\n\n

 

\n\n

The assignment will demonstrate a full transformation cycle, that will inform future scaling, covering process re-engineering, technology enablement and civil servants’ operational readiness, and will generate validated lessons to inform future scaling across other services and sectors. Ultimately, the project aims to provide concrete execution that will strengthen public trust and citizen experience, streamline government operations, enhance transparency, and promote more efficient and accountable use of public resources.

\n\n

This will be achieved by:

\n\n
    \n\t
  1. Diagnosing and mapping current service processes, including assessing regulatory, policy and organizational arrangements across the involved entities, reviewing existing systems and platforms, and identifying main pain points for the citizen and the civil servants;
    2. \n\t
  2. Collecting and analyzing service-related data and applying the National Data Classification Policy to classify data used within the selected services;
    3. \n\t
  3. Redesigning workflows and ministry service points to eliminate pain points, inefficiencies, and bottlenecks identified during the diagnostic phase; and
    4. \n\t
  4. Digitizing and enabling service-delivery processes on the National Portal to ensure consistent, scalable, and user-centric execution, and integrating one or more electronic signature use cases, in line with the existing legal, institutional, and policy frameworks.
    5. \n
\n\n

Note: Integration shall rely on existing systems and available APIs. The Consultant will be responsible for integrating services with the National Portal using existing APIs and interfaces where available. The development of new APIs is not required under this assignment.

\n\n

The National Portal is a low-code platform that supports workflow automation. It allows the creation of reusable libraries and modular service components that can be configured and reconfigured across different services, supporting integration and the transition from paper-based procedures to structured and traceable digital processes.

\n\n
    \n\t
  1. Scope of Work
    2. \n
\n\n

The Consultant will implement the redesign and digitally transform 6 priority services. These services will be selected through a collaborative process where the Consultant proposes a list of 10-12 proposed services, which are then shortlisted and approved to arrive at the final 6. As part of the assignment, data associated with the selected services will be collected, analyzed, and classified in line with the proposed National Data Classification Policy, and one or more electronic signature use cases will be operationalized within selected service workflows, in accordance with the applicable legal and institutional framework. For each service, the scope of work includes:

\n\n

 

\n\n
    \n\t
  1. Confirming the service scope, stakeholders, boundaries and interministerial dependencies to clarify objectives and ensure alignment with cross government digital enablers;
    2. \n\t
  2. Conducting an as is diagnostic to map current service workflows, roles, handoffs, pain points and bottlenecks (from citizen and civil servant perspectives) and to analyze all relevant or potential regulatory, policy and cross government dependencies such as e-signature application, data governance and classification rules, and future digital identity/trust requirements;
    3. \n\t
  3. Designing a streamlined, digitization ready “to be” service workflow that removes bottlenecks, simplifies approvals, and reasonably aligns with the existing legal and trust framework;
    4. \n\t
  4. Proposing functional and non‑functional elements (including security, privacy, interoperability and performance), acceptance criteria and operating roles for the redesigned service, in line with existing applicable frameworks;
    5. \n\t
  5. Developing, configuring, testing, validating, and operationally rolling out the digitized services in accordance with the approved “to-be” design, including the integration of cross-government digital enablers (e.g., data classification controls, electronic signature use cases, interoperability components, and trust services; and
    6. \n\t
  6. Civil servants enablement and capacity building for service operations, ensuring that personnel across participating entities are equipped to operate, manage, and sustain the transformed services.
    7. \n
\n\n

The complexity layer defined in the table below assesses the level of effort, coordination, legal change, and technical integration required to redesign and digitize the initial pool of 10–12 proposed services, from which the final list of six services will be selected.

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Complexity layer

\n\t\t\t		\n\t\t\t

Definition (how to interpret complexity)

\n\t\t\t		\n\t\t\t

Minimum distribution across 10-12 services

\n\t\t\t
\n\t\t\t

High

\n\t\t\t		\n\t\t\t

Requires significant cross-entity coordination and/or end-to-end workflow redesign; multiple approval points; complex integrations (e.g., interoperability/API dependencies), high institutional and legislative change load, and/or heightened data/sensitivity considerations.

\n\t\t\t		\n\t\t\t

At most 2

\n\t\t\t
\n\t\t\t

Medium

\n\t\t\t		\n\t\t\t

Moderate redesign and coordination requirements; limited number of entities; some integration needs; manageable procedural/legal constraints; moderate change load for staff and operations.

\n\t\t\t		\n\t\t\t

At least 4

\n\t\t\t
\n\t\t\t

Low

\n\t\t\t		\n\t\t\t

Contained workflow and limited stakeholders; minimal integration; simpler procedural/legal footprint; low change load; can be digitized with relatively standard patterns.

\n\t\t\t		\n\t\t\t

At least 4

\n\t\t\t
\n\n

 

\n\n

The prioritization and selection of services will be guided by a set of criteria aligned with the LDAP design and objectives. These include: (i) expected number of users or beneficiaries and the potential to improve citizen experience at scale; (ii) magnitude of the anticipated developmental impact, including improvements in transparency, efficiency, and service delivery outcomes; (iii) potential to benefit vulnerable groups, including low-income, conflict-affected, and climate-vulnerable populations, as well as women and girls; (iv) readiness for digitization, taking into account existing technological, institutional, and legal conditions; (v) sustainability and the potential for scaling beyond the pilot phase; (vi) feasibility of achieving end-to-end digitalization; and (vii) the ability to leverage existing / future national digital foundations and enablers, such as digital identity, data sharing frameworks, and data governance systems.

\n\n
    \n\t
  1. Key Activities
    2. \n
\n\n

This assignment will operationalize the transformation agenda by translating previously developed frameworks into practical, service-level improvements. It will provide the evidence, design solutions, and implementation of insights required to validate the Target Operating Model and demonstrate how re-engineered, digitally enabled services supported by data classification and electronic signature use cases can be delivered in practice and scaled across government.

\n\n

Building on the frameworks, interaction models, and sector analyses developed under earlier deliverables, the selected firm will lead the end-to-end implementation of priority services within the selected sector(s)/cluster(s). The assignment follows a structured, outcome-oriented approach covering service assessment, workflow redesign, data classification, digitization, and the operationalization of electronic signature use cases, as detailed below.

\n\n

Deliverable D1: Inception Report and Agile Roadmap.

\n\n

Prepare and submit an inception report as a deliverable, that shall include:

\n\n
    \n\t
  1. A validated understanding of the assignment context, objectives, scope including confirmation of stakeholders, boundaries, and dependencies;
    2. \n\t
  2. A detailed workplan and timeline aligned with the agreed deliverables, including validation milestones and decision gates;
    3. \n\t
  3. A methodology and engagement approach, including developing data / information gathering templates from the various service providers and ministries, and describing data collection, analysis techniques, and stakeholder engagement;
    4. \n\t
  4. A description of the agile approach (delivery stages - MVP, alpha and beta, sprint structure, sequencing approach and governance arrangements for iterative delivery and approvals); and
    5. \n\t
  5. An initial risk assessment and mitigation strategy.
    6. \n
\n\n

Deliverable D2: Initial Data Collection and Preliminary Consultations to Inform the Subsequent Phases, Including the Shortlisting of Services.

\n\n

Present a summary on the initial data collection exercise and consultations:

\n\n
    \n\t
  1. Minimum data collection exercise leveraging previous work conducted and related to the service data collection efforts, catalogs, and existing documentation
    2. \n\t
  2. Rapid consultations with relevant service owners and stakeholders to validate service scope, relevance, and key dependencies; and
    3. \n\t
  3. Confirm the initial list of 10-12 candidate services out of which the final set of services to be digitalized will be selected.
    4. \n
\n\n

 

\n\n

Deliverables D3-D5(three sprint waves): Agile End-to-End Service Transformation, Deployment, Monitoring and Capacity Building.

\n\n

The Consultant shall implement the assignment using a structured agile, sprint-based approach, progressing services iteratively from discovery to working Minimum Viable Product (MVP) delivery and validation. Services shall be advanced in pairs (two services per sprint wave) and be configured and deployed through the National Portal. Each sprint wave shall follow a defined cycle of discovery, co-design, build, test, user validation, and retrospective review.

\n\n

Progression to subsequent sprint waves shall be contingent upon formal validation of the MVPs of the preceding wave and completion of sprint retrospectives capturing lessons learned, reusable components, and required adjustments.

\n\n

 As stated above, the digitalization of services under will be implemented through the National low-code platform that enables workflow automation and service configuration with minimal need for custom software development. Under this approach, the Consultant will design and configure service workflows, data structures, business rules, and integration points within the platform, with minimal development of custom code. These configurations are executed by the platform to deliver fully functional digital services. The Consultant will therefore focus on preparing structured workflows, functional specifications, and integration logic that can be deployed on the platform, ensuring that services are delivered in a standardized, secure, and user-accessible format. The platform supports the use of reusable components, libraries, and modular building blocks, which can be configured and adapted across multiple services to improve efficiency and scalability.

\n\n

The Consultant will hence be able to leverage the platform’s flexibilities, continuously improving across waves through by reusing configurable libraries, workflow blocks, and integration components developed on the National Portal.

\n\n

Activities under this deliverable shall include:

\n\n
    \n\t
  1. Progressive selection and preliminary assessment of candidate services from an initial pool of 10-12 services, including evaluation of impact, complexity, feasibility (legal and technical), and institutional readiness;
    2. \n\t
  2. Validation meetings with the relevant ministries/entities for each candidate service to confirm service scope and boundaries, responsible and participating entities (service owner and process owner), decision/approval authority, inter-ministerial dependencies, current workflow realities, implementation readiness, and assessment existing digital systems;
    3. \n\t
  3. The Consultant must obtain formal written endorsement from the Technical Committee (TC) in coordination with the concerned ministries prior to initiating detailed mapping and redesign activities. The endorsement shall confirm approval of the agile implementation approach, agreement on the selected service(s), and the nomination of a dedicated focal point to ensure ongoing coordination and decision-making;
    4. \n\t
  4. Service-level baseline (“As-Is”) mapping for each service entering the sprint cycle, including current workflows, roles, hand-offs, approvals, bottlenecks, data flows, governance procedures, and legal, procedural, and technical constraints, together with documentation of baseline requirements and operational readiness prerequisites to inform redesign and digitization. The Consultant shall submit a detailed Business Requirements Document (BRD) reflecting the findings from the mapping and stakeholder engagement;
    5. \n\t
  5. Iterative redesign of current services to make them streamlined, digitization-ready “To-Be” workflows. Classify the data elements related to the services in accordance with the National Data Classification Framework and proposed Policy. Where the redesigned service includes approvals, signatures, and authentication steps, assess and implement the appropriate electronic signature use cases in alignment with the existing legal and institutional framework;
    6. \n\t
  6. Definition of functional and non-functional requirements for the redesigned and digitized service (not the legacy workflow), including security, privacy, interoperability, performance, user stories, acceptance criteria, operating roles, and system integration requirements, ensuring that redesigned workflows are compatible with and can be deployed through the National Portal. The consultant must submit a functional specification document (FSD) on the redesigned service that will go into the low-code platform;
    7. \n\t
  7. Identification of enabling legislative, regulatory, or policy adjustments required to operationalize the redesigned digital service and ensure alignment with cross-government digital enablers;
    8. \n\t
  8. Iterative configuration, development, testing, deployment, and stakeholder validation (including demos and UAT where applicable), resulting in working MVP/alpha versions for the services that successfully progress through the sprint cycle;
    9. \n\t
  9. Development and progressive enhancement of a service performance monitoring dashboard, including:
    10. \n
\n\n\n\n
    \n\t
  1. Delivery of hands-on training and capacity-building sessions as part of each sprint wave, covering:
    2. \n
\n\n\n\n

Throughout D3–D5, the Consultant shall apply core agile principles, including time-boxed sprints, continuous stakeholder engagement, rapid feedback loops, and formal sprint retrospectives to ensure adaptive delivery, risk reduction, and scalable reuse across services. To initiate the release of payments associated with these deliverables, the Consultant must provide documented evidence of satisfactory delivery. This shall include a Certificate of Delivery of Services issued by the Consultant, and submitted to the Grant Coordinator, and subsequently validated and approved by the TC.

\n\n

Deliverable D6: Lessons Learned and Scale-Up Recommendations (Final Report).

\n\n

Capture and document lessons learned from the implementation and recommendations to inform the scale-up of service redesign and digitization to additional clusters/sectors. This deliverable will include:

\n\n
    \n\t
  1. Analysis of what worked well and what challenges emerged across service redesign, data classification, and e-signature implementation;
    2. \n\t
  2. Identification of enablers and constraints related to institutional arrangements, inter-entity coordination, and operational readiness;
    3. \n\t
  3. Recommendations for improving processes, governance, and technical approaches in future phases;
    4. \n\t
  4. Guidance on future implementation sequencing, capacity building and policy reforms required to support sustainable digital service delivery; and
    5. \n\t
  5. Identification of potential risks and mitigation strategies for scaling and future implementation.
    6. \n
\n\n
    \n\t
  1. Project Oversight and Management Structure
    2. \n
\n\n

A Technical Committee (TC) will be established to provide strategic direction, oversight, and effective management of this engagement. Chaired by the Grant Coordinator and composed of members from OMSAR, OMSTAI, and the involved ministries as applicable, the TC    serve as the primary governing body responsible for reviewing the firm’s progress and ensuring alignment with beneficiary requirements and national digital transformation goals.

\n\n

For the purpose of this assignment, the TC is the sole authority empowered to formally accept and approve project deliverables. Approval of each milestone deliverable by TC is a mandatory prerequisite for the release of corresponding payments. The Consulting firm shall provide regular updates and shall submit required Deliverables and reports through the Grant Coordinator to the TC, in addition to official invoice for payment upon the TC formal written acceptance of each deliverable.

\n\n
    \n\t
  1. Deliverables Table
    2. \n
\n\n

The assignment will be completed over a total period of 5 months from the contract commencement date. The contract commencement date is defined as the date of formal written notification issued by OMSAR to the Consultant to start the work, following the successful completion of the Project Kickoff meeting.

\n\n

 

\n\n

The consultant must submit all deliverables in English and in Arabic in a format to be agreed upon with TC. The provisional timetable is as follows:

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Deliverables

\n\t\t\t		\n\t\t\t

Description & Key Components

\n\t\t\t		\n\t\t\t

Timeline (Cumulative)

\n\t\t\t		\n\t\t\t

Approvals Required

\n\t\t\t		\n\t\t\t

Payment Terms (% of Contract Total Value)

\n\t\t\t
\n\t\t\t

D1 Inception Report and Agile Roadmap

\n\t\t\t		\n\t\t\t

Validated scope for services, detailed workplan, and agile sprint structure

\n\t\t\t		\n\t\t\t

Week 2

\n\t\t\t		\n\t\t\t

TC

\n\t\t\t		\n\t\t\t

10%

\n\t\t\t
\n\t\t\t

D2 Summary Report on the initial data collection exercise and consultations

\n\t\t\t		\n\t\t\t

Initial data collection exercise, consultations, and confirmation of the initial list of 10-12 candidate services.

\n\t\t\t		\n\t\t\t

Week 4

\n\t\t\t		\n\t\t\t

TC

\n\t\t\t		\n\t\t\t

15%

\n\t\t\t
\n\t\t\t

D3 First sprint of 2 services

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Agile Service Discovery, Redesign, and Initial Digital Deployment
    • \n\t\t\t\t
  • Performance Monitoring Dashboard
    • \n\t\t\t\t
  • Training Materials and Capacity Building for Service Operations
    • \n\t\t\t
\n\t\t\t		\n\t\t\t

Week 9

\n\t\t\t		\n\t\t\t

TC & Entities

\n\t\t\t		\n\t\t\t

20%

\n\t\t\t
\n\t\t\t

D4 Second sprint of 2 services

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Agile Service Discovery, Redesign, and Initial Digital Deployment
    • \n\t\t\t\t
  • Performance Monitoring Dashboard
    • \n\t\t\t\t
  • Training Materials and Capacity Building for Service Operations
    • \n\t\t\t
\n\t\t\t		\n\t\t\t

 

\n\n\t\t\t

Week 14

\n\t\t\t		\n\t\t\t

TC & Entities

\n\t\t\t		\n\t\t\t

20%

\n\t\t\t
\n\t\t\t

D5 Third sprint of 2 services

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Agile Service Discovery, Redesign, and Initial Digital Deployment
    • \n\t\t\t\t
  • Performance Monitoring Dashboard
    • \n\t\t\t\t
  • Training Materials and Capacity Building for Service Operations
    • \n\t\t\t
\n\t\t\t		\n\t\t\t

Week 19

\n\t\t\t		\n\t\t\t

TC & Entities

\n\t\t\t		\n\t\t\t

20%

\n\t\t\t
\n\t\t\t

D6 Final Report & Lessons Learned and Scale-Up Recommendations

\n\t\t\t		\n\t\t\t

Analysis of results, lessons learned, and future scale-up recommendations

\n\t\t\t		\n\t\t\t

Week 21

\n\t\t\t		\n\t\t\t

TC

\n\t\t\t		\n\t\t\t

15%

\n\t\t\t
\n\n
    \n\t
  1.  Payment Terms and Administrative Requirements
    2. \n
\n\n

7.1 General Payment Conditions

\n\n\n\n

7.2 The TC Approval Gate

\n\n

The Technical Committee (TC) serves as the sole authority for the acceptance of services. The following administrative process applies to every milestone:

\n\n\n\n

7.3 Invoicing Requirements

\n\n

To initiate a payment, the Consultant must submit to the Grant Coordinator an administrative package containing:

\n\n
    \n\t
  1. Official Invoice: Referencing the contract number and specific deliverable code (D1–D6).
    2. \n\t
  2. Certificate of Delivery of Services: A formal certificate signed by the Consultant, accompanied by the Deliverable itself and a Concise Summary Report documenting the completion of specific contractual milestones.
    3. \n\t
  3. Progress Evidence: For technical stages, evidence of configuration/deployment on the National Portal must be demonstrated.
    4. \n
\n\n

Attendance Sheets: Signed logs of training participants must be attached as proof of capacity building.

\n\n

7.4 Delays and Escalations

\n\n\n\n

Payments will be processed within the timeframe specified in the contract conditions following the formal receipt of a "complete" invoice package.

\n\n
    \n\t
  1. Duration of the assignment and estimated key staff-months input
    2. \n
\n\n

The total duration of the assignment is 5 months from the date of contract signature.

\n\n

The distribution of Level of Effort for all proposed Key Experts should be detailed in the bidder’s technical and financial proposals.

\n\n
    \n\t
  1. Firm Qualifications\n\t
      \n\t\t
    1. General Corporate Experience
      2. \n\t
    \n\t
    2. \n
\n\n\n\n

The Firm must demonstrate a proven track record by submitting reference details for at least two (2) similar contracts successfully completed within the last seven (7) years. A "similar contract" is defined as follows:

\n\n\n\n

The Firm must demonstrate in its profile that it possesses in-house expertise or established partnerships in:

\n\n\n\n
    \n\t
  1. Expected Key Experts
    2. \n
\n\n

The consultant's team shall be composed of qualified experts with proven experience. The bidder must propose, at a minimum, the following Key Expert positions:

\n\n

Key Expert 1: Team Leader / Project Manager

\n\n

Key Expert 2: Business Analyst Expert

\n\n

Key Expert 3: Developer/Digital Transformation Architect

\n\n

Bidders may propose additional non-key experts as they see fit to successfully deliver the scope of work.

\n\n

Required Qualifications

\n\n

All experts must be fluent in English and Arabic (written and spoken). The minimum required qualifications for the Key Experts are as follows:

\n\n

Key Expert 1: Team Leader / Project Manager

\n\n\n\n

Key Expert 2: Senior Business Process Re-engineering (BPR) Expert

\n\n\n\n

 

\n\n

Key Expert 3: Senior Digital Solution Architect

\n\n\n\n\n\n
    \n\t
  1. Reporting Requirements
    2. \n
\n\n

The Consultant’s reporting obligations are divided into two distinct categories: Contractual Deliverables and Administrative Progress Reports.

\n\n

11.1 Contractual Deliverables (Payment Milestones)

\n\n

These outputs are directly linked to the payment schedule defined in the Deliverables Table (Section 6). Payments will only be released upon formal written acceptance of these specific documents by the TC.

\n\n\n\n

11.2 Administrative Progress Reporting (Monitoring Only)

\n\n

These reports are for performance monitoring and coordination purposes.

\n\n\n\n

11.3 Enforcement of Reporting Compliance

\n\n

Timely submission of Administrative Progress Reports (as defined in Section 11.2) is a material obligation of the Consultant and considered an integral part of the deliverables and related acceptance.

\n\n
    \n\t
  1. OMSAR and OMSTAI Inputs
    2. \n
\n\n

To facilitate the successful execution of the assignment, OMSAR and OMSTAI shall provide the following:

\n\n\n\n
    \n\t
  1. Environmental and Social Considerations
    2. \n
\n\n

The Firm shall integrate environmental and social principles consistent with the World Bank Environmental and Social Framework (ESF) throughout the redesign and development of e-services. All work must ensure:

\n\n\n\n

These considerations should be reflected in service workflows, user experience recommendations, prototypes, and final technical outputs.

\n\n

REQUEST FOR EXPRESSIONS OF INTEREST (REOI)

\n\n

CONSULTANT’S QUALIFICATIONS BASED SELECTION (CQS)

\n\n

E-Services, Business Process Reengineering Foundational Work as part of Re-Inventing Government

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Name of Project

\n\t\t\t		\n\t\t\t

GFPP for Lebanon Digital Acceleration Project (LDAP)

\n\t\t\t
\n\t\t\t

Loan No/Credit No/ Grand Number

\n\t\t\t		\n\t\t\t

TF0C8895

\n\t\t\t
\n\t\t\t

Assignment Title

\n\t\t\t		\n\t\t\t

E-Services, Business Process Reengineering Foundational Work as part of Re-Inventing Government

\n\t\t\t
\n\t\t\t

Procurement Plan Ref Number

\n\t\t\t		\n\t\t\t

LB-OMSAR-537752-CS-CQS

\n\t\t\t
\n\t\t\t

Country of Delivery

\n\t\t\t		\n\t\t\t

Lebanon

\n\t\t\t
\n\n

The Office of the Minister of State for Administrative Reform (OMSAR) has received financing from the World Bank toward the cost of the Preparation Grant for the Lebanon Digital Acceleration Project (LDAP) and intends to apply part of the proceeds for the following consulting services.

\n\n

The consulting services (“the Services”) include the end-to-end improvement and digital transformation of six (6) priority public services within selected sectors/clusters. The assignment utilizes an agile methodology (MVP, alpha, and beta stages) to diagnose "As-Is" processes, redesign "To-Be" workflows, classify data according to the National Data Classification Policy, and integrate electronic signature use cases. The Consultant will configure these services on Lebanon’s National Portal, a low-code automation platform, and provide capacity building for civil servants. The estimated implementation period is five (5) months from the contract commencement date.

\n\n

The detailed Terms of Reference (TOR) for the assignment is attached to this REOI.

\n\n

OMSAR 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.

\n\n

The attention of interested Consultants is drawn to paragraph 3.14, 3.16 and 3.17 of the World Bank’s Procurement Regulations for IPF Borrowers dated September 2025 (“the Regulations”), setting forth the World Bank’s policy on conflict of interest.

\n\n

The best qualified firm to carry out the services will be selected in accordance with the Consultant’s Qualifications Based Selection (CQS) method set out in the Regulations and based on the following criteria:

\n\n

Mandatory Minimum Requirements:

\n\n\n\n

Desirable Requirements (Technical and Managerial Capability):

\n\n\n\n

(Note: The qualifications and experience of Key Experts shall not be evaluated at this shortlisting stage).

\n\n

To ensure a complete submission, the Expression of Interest (EOI) must include the following minimum documentation:

\n\n\n\n

Further information can be obtained at the address below during office hours (09:00 AM to 04:00 PM Beirut Time).

\n\n

Expressions of interest must be delivered in a written form to the address below (in person, or by mail, or by e-mail) by COB 28 April, 2026.

\n\n

 

\n\n

Office of the Minister of State for Administrative Reform (OMSAR)

\n\n

Technical Unit – Preparation Grant for Lebanon Digital Acceleration Project

\n\n

Attn: Ms. Mirvat Hammoud – Procurement Specialist

\n\n

Address: STARCO Building, Bloc A, 5th Floor, Room 505a

\n\n

Omar Daouk Street, Mina El Hosn Sector

\n\n

Beirut, Lebanon

\n\n

Tel: +961 (1) 371 505; ext. 160

\n\n

E-mail: mhammoud@omsar.gov.lb

\n\n

 

\n\n

Attachment: Terms of Reference (TOR)

\n\n

 

\n\n

TERMS OF REFERENCE

\n\n

PREPARATION GRANT FOR LEBANON DIGITAL ACCELERATION PROJECT (P181954)

\n\n

E-Services, Business Process Reengineering Foundational Work as part of Re-Inventing Government

\n\n
    \n\t
  1. Background
    2. \n
\n\n

Lebanon’s public administration has remained largely unchanged for decades, operating with outdated structures, fragmented mandates, widespread vacancies, and weak digital and human capital systems. Combined with paper-based processes, siloed information systems, and manual approval workflows, these constraints have resulted in inefficient service delivery, duplication of roles, limited transparency, and a growing gap between government capabilities and citizen expectations.

\n\n

 

\n\n

In response, the Government of Lebanon, with support from the World Bank, as part of the Lebanon Digital Acceleration Project (LDAP), is undertaking a strategic investment aimed at modernizing public administration and strengthening the core digital enablers required for trusted digital service delivery. To support project readiness, the World Bank’s Grant Facility for Project Preparation (GFPP) has been extended to the Office of the Minister of State for Administrative Reform (OMSAR). The GFPP grant is implemented by a Technical Unit (TU) housed within OMSAR.

\n\n

 

\n\n

In parallel, OMSAR, under direct government sponsorship, has launched “Reinventing Government 2030” a whole of government reform effort that aims to restructure the public sector into a coherent, citizen centric, mission driven public administration.

\n\n

 

\n\n

The reform is structured in phases progressively building toward implementation. It began with the Stakeholders’ Aspirations phase, which defined a forward-looking vision for Lebanon’s public administration and establishing guiding design principles. This phase has been completed. It is followed by the development of a Blueprint for Public Sector Reform, encompassing baseline assessments and benchmarking of current institutions and services, and the piloting of the proposed model across selected ministries. The final phase focus is on implementation, including the re-engineering and digitization of priority public services, supported by the necessary legal and regulatory changes.

\n\n

 

\n\n

To support service transformation under this agenda, OMSAR is advancing key digital foundations as part of the LDAP. These efforts will be undertaken by OMSAR and OMSTAI within their mandates and technical expertise and in coordination with relevant stakeholders, ensuring consistency with national digital transformation, national digital trust, data governance, and interoperability frameworks. This includes the development of a National Data Classification Policy, as well as targeted support to the electronic signature framework under the existing legal system. In particular, OMSAR will work closely with the Lebanese Accreditation Council (COLIBAC) to support the definition of practical requirements and baseline criteria for electronic signature accreditation and use.

\n\n

 

\n\n

The activities are intended to be implemented in parallel and informed by practical application in real service contexts. Within this framework, e-services constitute the operational layer through which institutional reform and key digital enablers are translated into tangible improvements in service delivery.

\n\n

 

\n\n

As part of the preparatory work, an initial service prioritization exercise across several ministries has been carried out to identify potential candidate services for the assignment. Indicative examples of such services, and which are non-exhaustive and non-binding, and are subject to further validation, include digital diploma attestation, trader registration and clearance services, tourism licensing digitization, payment of fees for investment and right-of-way services, and selected municipal and sectoral permits.

\n\n

 

\n\n

The redesign and digitization of selected priority public services will enable the practical piloting of data classification and the integration of one or more electronic signature use cases within end-to-end government workflows.

\n\n

 

\n\n

This initiative will create a controlled environment to apply data classification rules and electronic signature mechanisms in practice, generate actionable lessons, and support future scale-up under the full LDAP through a phased and realistic expansion of digital public services in Lebanon.

\n\n
    \n\t
  1. Assignment and Objective
    2. \n
\n\n

The objective of this assignment is to establish an evidence-based, end-to-end improvement of priority public services within selected sector(s)/cluster(s). This will be achieved through an agile approach, utilizing MVP (Minimum Viable Product), alpha, and beta stages. This requires various iterations in diagnosing current service processes and organizational arrangements, redesigning workflows to remove pain points and operational bottlenecks, digitizing service-delivery practices, applying data classification requirements and operationalizing one or more electronic signature use cases within real government workflows to ensure consistent execution.

\n\n

 

\n\n

The assignment will demonstrate a full transformation cycle, that will inform future scaling, covering process re-engineering, technology enablement and civil servants’ operational readiness, and will generate validated lessons to inform future scaling across other services and sectors. Ultimately, the project aims to provide concrete execution that will strengthen public trust and citizen experience, streamline government operations, enhance transparency, and promote more efficient and accountable use of public resources.

\n\n

This will be achieved by:

\n\n
    \n\t
  1. Diagnosing and mapping current service processes, including assessing regulatory, policy and organizational arrangements across the involved entities, reviewing existing systems and platforms, and identifying main pain points for the citizen and the civil servants;
    2. \n\t
  2. Collecting and analyzing service-related data and applying the National Data Classification Policy to classify data used within the selected services;
    3. \n\t
  3. Redesigning workflows and ministry service points to eliminate pain points, inefficiencies, and bottlenecks identified during the diagnostic phase; and
    4. \n\t
  4. Digitizing and enabling service-delivery processes on the National Portal to ensure consistent, scalable, and user-centric execution, and integrating one or more electronic signature use cases, in line with the existing legal, institutional, and policy frameworks.
    5. \n
\n\n

Note: Integration shall rely on existing systems and available APIs. The Consultant will be responsible for integrating services with the National Portal using existing APIs and interfaces where available. The development of new APIs is not required under this assignment.

\n\n

The National Portal is a low-code platform that supports workflow automation. It allows the creation of reusable libraries and modular service components that can be configured and reconfigured across different services, supporting integration and the transition from paper-based procedures to structured and traceable digital processes.

\n\n
    \n\t
  1. Scope of Work
    2. \n
\n\n

The Consultant will implement the redesign and digitally transform 6 priority services. These services will be selected through a collaborative process where the Consultant proposes a list of 10-12 proposed services, which are then shortlisted and approved to arrive at the final 6. As part of the assignment, data associated with the selected services will be collected, analyzed, and classified in line with the proposed National Data Classification Policy, and one or more electronic signature use cases will be operationalized within selected service workflows, in accordance with the applicable legal and institutional framework. For each service, the scope of work includes:

\n\n

 

\n\n
    \n\t
  1. Confirming the service scope, stakeholders, boundaries and interministerial dependencies to clarify objectives and ensure alignment with cross government digital enablers;
    2. \n\t
  2. Conducting an as is diagnostic to map current service workflows, roles, handoffs, pain points and bottlenecks (from citizen and civil servant perspectives) and to analyze all relevant or potential regulatory, policy and cross government dependencies such as e-signature application, data governance and classification rules, and future digital identity/trust requirements;
    3. \n\t
  3. Designing a streamlined, digitization ready “to be” service workflow that removes bottlenecks, simplifies approvals, and reasonably aligns with the existing legal and trust framework;
    4. \n\t
  4. Proposing functional and non‑functional elements (including security, privacy, interoperability and performance), acceptance criteria and operating roles for the redesigned service, in line with existing applicable frameworks;
    5. \n\t
  5. Developing, configuring, testing, validating, and operationally rolling out the digitized services in accordance with the approved “to-be” design, including the integration of cross-government digital enablers (e.g., data classification controls, electronic signature use cases, interoperability components, and trust services; and
    6. \n\t
  6. Civil servants enablement and capacity building for service operations, ensuring that personnel across participating entities are equipped to operate, manage, and sustain the transformed services.
    7. \n
\n\n

The complexity layer defined in the table below assesses the level of effort, coordination, legal change, and technical integration required to redesign and digitize the initial pool of 10–12 proposed services, from which the final list of six services will be selected.

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Complexity layer

\n\t\t\t		\n\t\t\t

Definition (how to interpret complexity)

\n\t\t\t		\n\t\t\t

Minimum distribution across 10-12 services

\n\t\t\t
\n\t\t\t

High

\n\t\t\t		\n\t\t\t

Requires significant cross-entity coordination and/or end-to-end workflow redesign; multiple approval points; complex integrations (e.g., interoperability/API dependencies), high institutional and legislative change load, and/or heightened data/sensitivity considerations.

\n\t\t\t		\n\t\t\t

At most 2

\n\t\t\t
\n\t\t\t

Medium

\n\t\t\t		\n\t\t\t

Moderate redesign and coordination requirements; limited number of entities; some integration needs; manageable procedural/legal constraints; moderate change load for staff and operations.

\n\t\t\t		\n\t\t\t

At least 4

\n\t\t\t
\n\t\t\t

Low

\n\t\t\t		\n\t\t\t

Contained workflow and limited stakeholders; minimal integration; simpler procedural/legal footprint; low change load; can be digitized with relatively standard patterns.

\n\t\t\t		\n\t\t\t

At least 4

\n\t\t\t
\n\n

 

\n\n

The prioritization and selection of services will be guided by a set of criteria aligned with the LDAP design and objectives. These include: (i) expected number of users or beneficiaries and the potential to improve citizen experience at scale; (ii) magnitude of the anticipated developmental impact, including improvements in transparency, efficiency, and service delivery outcomes; (iii) potential to benefit vulnerable groups, including low-income, conflict-affected, and climate-vulnerable populations, as well as women and girls; (iv) readiness for digitization, taking into account existing technological, institutional, and legal conditions; (v) sustainability and the potential for scaling beyond the pilot phase; (vi) feasibility of achieving end-to-end digitalization; and (vii) the ability to leverage existing / future national digital foundations and enablers, such as digital identity, data sharing frameworks, and data governance systems.

\n\n
    \n\t
  1. Key Activities
    2. \n
\n\n

This assignment will operationalize the transformation agenda by translating previously developed frameworks into practical, service-level improvements. It will provide the evidence, design solutions, and implementation of insights required to validate the Target Operating Model and demonstrate how re-engineered, digitally enabled services supported by data classification and electronic signature use cases can be delivered in practice and scaled across government.

\n\n

Building on the frameworks, interaction models, and sector analyses developed under earlier deliverables, the selected firm will lead the end-to-end implementation of priority services within the selected sector(s)/cluster(s). The assignment follows a structured, outcome-oriented approach covering service assessment, workflow redesign, data classification, digitization, and the operationalization of electronic signature use cases, as detailed below.

\n\n

Deliverable D1: Inception Report and Agile Roadmap.

\n\n

Prepare and submit an inception report as a deliverable, that shall include:

\n\n
    \n\t
  1. A validated understanding of the assignment context, objectives, scope including confirmation of stakeholders, boundaries, and dependencies;
    2. \n\t
  2. A detailed workplan and timeline aligned with the agreed deliverables, including validation milestones and decision gates;
    3. \n\t
  3. A methodology and engagement approach, including developing data / information gathering templates from the various service providers and ministries, and describing data collection, analysis techniques, and stakeholder engagement;
    4. \n\t
  4. A description of the agile approach (delivery stages - MVP, alpha and beta, sprint structure, sequencing approach and governance arrangements for iterative delivery and approvals); and
    5. \n\t
  5. An initial risk assessment and mitigation strategy.
    6. \n
\n\n

Deliverable D2: Initial Data Collection and Preliminary Consultations to Inform the Subsequent Phases, Including the Shortlisting of Services.

\n\n

Present a summary on the initial data collection exercise and consultations:

\n\n
    \n\t
  1. Minimum data collection exercise leveraging previous work conducted and related to the service data collection efforts, catalogs, and existing documentation
    2. \n\t
  2. Rapid consultations with relevant service owners and stakeholders to validate service scope, relevance, and key dependencies; and
    3. \n\t
  3. Confirm the initial list of 10-12 candidate services out of which the final set of services to be digitalized will be selected.
    4. \n
\n\n

 

\n\n

Deliverables D3-D5(three sprint waves): Agile End-to-End Service Transformation, Deployment, Monitoring and Capacity Building.

\n\n

The Consultant shall implement the assignment using a structured agile, sprint-based approach, progressing services iteratively from discovery to working Minimum Viable Product (MVP) delivery and validation. Services shall be advanced in pairs (two services per sprint wave) and be configured and deployed through the National Portal. Each sprint wave shall follow a defined cycle of discovery, co-design, build, test, user validation, and retrospective review.

\n\n

Progression to subsequent sprint waves shall be contingent upon formal validation of the MVPs of the preceding wave and completion of sprint retrospectives capturing lessons learned, reusable components, and required adjustments.

\n\n

 As stated above, the digitalization of services under will be implemented through the National low-code platform that enables workflow automation and service configuration with minimal need for custom software development. Under this approach, the Consultant will design and configure service workflows, data structures, business rules, and integration points within the platform, with minimal development of custom code. These configurations are executed by the platform to deliver fully functional digital services. The Consultant will therefore focus on preparing structured workflows, functional specifications, and integration logic that can be deployed on the platform, ensuring that services are delivered in a standardized, secure, and user-accessible format. The platform supports the use of reusable components, libraries, and modular building blocks, which can be configured and adapted across multiple services to improve efficiency and scalability.

\n\n

The Consultant will hence be able to leverage the platform’s flexibilities, continuously improving across waves through by reusing configurable libraries, workflow blocks, and integration components developed on the National Portal.

\n\n

Activities under this deliverable shall include:

\n\n
    \n\t
  1. Progressive selection and preliminary assessment of candidate services from an initial pool of 10-12 services, including evaluation of impact, complexity, feasibility (legal and technical), and institutional readiness;
    2. \n\t
  2. Validation meetings with the relevant ministries/entities for each candidate service to confirm service scope and boundaries, responsible and participating entities (service owner and process owner), decision/approval authority, inter-ministerial dependencies, current workflow realities, implementation readiness, and assessment existing digital systems;
    3. \n\t
  3. The Consultant must obtain formal written endorsement from the Technical Committee (TC) in coordination with the concerned ministries prior to initiating detailed mapping and redesign activities. The endorsement shall confirm approval of the agile implementation approach, agreement on the selected service(s), and the nomination of a dedicated focal point to ensure ongoing coordination and decision-making;
    4. \n\t
  4. Service-level baseline (“As-Is”) mapping for each service entering the sprint cycle, including current workflows, roles, hand-offs, approvals, bottlenecks, data flows, governance procedures, and legal, procedural, and technical constraints, together with documentation of baseline requirements and operational readiness prerequisites to inform redesign and digitization. The Consultant shall submit a detailed Business Requirements Document (BRD) reflecting the findings from the mapping and stakeholder engagement;
    5. \n\t
  5. Iterative redesign of current services to make them streamlined, digitization-ready “To-Be” workflows. Classify the data elements related to the services in accordance with the National Data Classification Framework and proposed Policy. Where the redesigned service includes approvals, signatures, and authentication steps, assess and implement the appropriate electronic signature use cases in alignment with the existing legal and institutional framework;
    6. \n\t
  6. Definition of functional and non-functional requirements for the redesigned and digitized service (not the legacy workflow), including security, privacy, interoperability, performance, user stories, acceptance criteria, operating roles, and system integration requirements, ensuring that redesigned workflows are compatible with and can be deployed through the National Portal. The consultant must submit a functional specification document (FSD) on the redesigned service that will go into the low-code platform;
    7. \n\t
  7. Identification of enabling legislative, regulatory, or policy adjustments required to operationalize the redesigned digital service and ensure alignment with cross-government digital enablers;
    8. \n\t
  8. Iterative configuration, development, testing, deployment, and stakeholder validation (including demos and UAT where applicable), resulting in working MVP/alpha versions for the services that successfully progress through the sprint cycle;
    9. \n\t
  9. Development and progressive enhancement of a service performance monitoring dashboard, including:
    10. \n
\n\n\n\n
    \n\t
  1. Delivery of hands-on training and capacity-building sessions as part of each sprint wave, covering:
    2. \n
\n\n\n\n

Throughout D3–D5, the Consultant shall apply core agile principles, including time-boxed sprints, continuous stakeholder engagement, rapid feedback loops, and formal sprint retrospectives to ensure adaptive delivery, risk reduction, and scalable reuse across services. To initiate the release of payments associated with these deliverables, the Consultant must provide documented evidence of satisfactory delivery. This shall include a Certificate of Delivery of Services issued by the Consultant, and submitted to the Grant Coordinator, and subsequently validated and approved by the TC.

\n\n

Deliverable D6: Lessons Learned and Scale-Up Recommendations (Final Report).

\n\n

Capture and document lessons learned from the implementation and recommendations to inform the scale-up of service redesign and digitization to additional clusters/sectors. This deliverable will include:

\n\n
    \n\t
  1. Analysis of what worked well and what challenges emerged across service redesign, data classification, and e-signature implementation;
    2. \n\t
  2. Identification of enablers and constraints related to institutional arrangements, inter-entity coordination, and operational readiness;
    3. \n\t
  3. Recommendations for improving processes, governance, and technical approaches in future phases;
    4. \n\t
  4. Guidance on future implementation sequencing, capacity building and policy reforms required to support sustainable digital service delivery; and
    5. \n\t
  5. Identification of potential risks and mitigation strategies for scaling and future implementation.
    6. \n
\n\n
    \n\t
  1. Project Oversight and Management Structure
    2. \n
\n\n

A Technical Committee (TC) will be established to provide strategic direction, oversight, and effective management of this engagement. Chaired by the Grant Coordinator and composed of members from OMSAR, OMSTAI, and the involved ministries as applicable, the TC    serve as the primary governing body responsible for reviewing the firm’s progress and ensuring alignment with beneficiary requirements and national digital transformation goals.

\n\n

For the purpose of this assignment, the TC is the sole authority empowered to formally accept and approve project deliverables. Approval of each milestone deliverable by TC is a mandatory prerequisite for the release of corresponding payments. The Consulting firm shall provide regular updates and shall submit required Deliverables and reports through the Grant Coordinator to the TC, in addition to official invoice for payment upon the TC formal written acceptance of each deliverable.

\n\n
    \n\t
  1. Deliverables Table
    2. \n
\n\n

The assignment will be completed over a total period of 5 months from the contract commencement date. The contract commencement date is defined as the date of formal written notification issued by OMSAR to the Consultant to start the work, following the successful completion of the Project Kickoff meeting.

\n\n

 

\n\n

The consultant must submit all deliverables in English and in Arabic in a format to be agreed upon with TC. The provisional timetable is as follows:

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Deliverables

\n\t\t\t		\n\t\t\t

Description & Key Components

\n\t\t\t		\n\t\t\t

Timeline (Cumulative)

\n\t\t\t		\n\t\t\t

Approvals Required

\n\t\t\t		\n\t\t\t

Payment Terms (% of Contract Total Value)

\n\t\t\t
\n\t\t\t

D1 Inception Report and Agile Roadmap

\n\t\t\t		\n\t\t\t

Validated scope for services, detailed workplan, and agile sprint structure

\n\t\t\t		\n\t\t\t

Week 2

\n\t\t\t		\n\t\t\t

TC

\n\t\t\t		\n\t\t\t

10%

\n\t\t\t
\n\t\t\t

D2 Summary Report on the initial data collection exercise and consultations

\n\t\t\t		\n\t\t\t

Initial data collection exercise, consultations, and confirmation of the initial list of 10-12 candidate services.

\n\t\t\t		\n\t\t\t

Week 4

\n\t\t\t		\n\t\t\t

TC

\n\t\t\t		\n\t\t\t

15%

\n\t\t\t
\n\t\t\t

D3 First sprint of 2 services

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Agile Service Discovery, Redesign, and Initial Digital Deployment
    • \n\t\t\t\t
  • Performance Monitoring Dashboard
    • \n\t\t\t\t
  • Training Materials and Capacity Building for Service Operations
    • \n\t\t\t
\n\t\t\t		\n\t\t\t

Week 9

\n\t\t\t		\n\t\t\t

TC & Entities

\n\t\t\t		\n\t\t\t

20%

\n\t\t\t
\n\t\t\t

D4 Second sprint of 2 services

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Agile Service Discovery, Redesign, and Initial Digital Deployment
    • \n\t\t\t\t
  • Performance Monitoring Dashboard
    • \n\t\t\t\t
  • Training Materials and Capacity Building for Service Operations
    • \n\t\t\t
\n\t\t\t		\n\t\t\t

 

\n\n\t\t\t

Week 14

\n\t\t\t		\n\t\t\t

TC & Entities

\n\t\t\t		\n\t\t\t

20%

\n\t\t\t
\n\t\t\t

D5 Third sprint of 2 services

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Agile Service Discovery, Redesign, and Initial Digital Deployment
    • \n\t\t\t\t
  • Performance Monitoring Dashboard
    • \n\t\t\t\t
  • Training Materials and Capacity Building for Service Operations
    • \n\t\t\t
\n\t\t\t		\n\t\t\t

Week 19

\n\t\t\t		\n\t\t\t

TC & Entities

\n\t\t\t		\n\t\t\t

20%

\n\t\t\t
\n\t\t\t

D6 Final Report & Lessons Learned and Scale-Up Recommendations

\n\t\t\t		\n\t\t\t

Analysis of results, lessons learned, and future scale-up recommendations

\n\t\t\t		\n\t\t\t

Week 21

\n\t\t\t		\n\t\t\t

TC

\n\t\t\t		\n\t\t\t

15%

\n\t\t\t
\n\n
    \n\t
  1.  Payment Terms and Administrative Requirements
    2. \n
\n\n

7.1 General Payment Conditions

\n\n\n\n

7.2 The TC Approval Gate

\n\n

The Technical Committee (TC) serves as the sole authority for the acceptance of services. The following administrative process applies to every milestone:

\n\n\n\n

7.3 Invoicing Requirements

\n\n

To initiate a payment, the Consultant must submit to the Grant Coordinator an administrative package containing:

\n\n
    \n\t
  1. Official Invoice: Referencing the contract number and specific deliverable code (D1–D6).
    2. \n\t
  2. Certificate of Delivery of Services: A formal certificate signed by the Consultant, accompanied by the Deliverable itself and a Concise Summary Report documenting the completion of specific contractual milestones.
    3. \n\t
  3. Progress Evidence: For technical stages, evidence of configuration/deployment on the National Portal must be demonstrated.
    4. \n
\n\n

Attendance Sheets: Signed logs of training participants must be attached as proof of capacity building.

\n\n

7.4 Delays and Escalations

\n\n\n\n

Payments will be processed within the timeframe specified in the contract conditions following the formal receipt of a "complete" invoice package.

\n\n
    \n\t
  1. Duration of the assignment and estimated key staff-months input
    2. \n
\n\n

The total duration of the assignment is 5 months from the date of contract signature.

\n\n

The distribution of Level of Effort for all proposed Key Experts should be detailed in the bidder’s technical and financial proposals.

\n\n
    \n\t
  1. Firm Qualifications\n\t
      \n\t\t
    1. General Corporate Experience
      2. \n\t
    \n\t
    2. \n
\n\n\n\n

The Firm must demonstrate a proven track record by submitting reference details for at least two (2) similar contracts successfully completed within the last seven (7) years. A "similar contract" is defined as follows:

\n\n\n\n

The Firm must demonstrate in its profile that it possesses in-house expertise or established partnerships in:

\n\n\n\n
    \n\t
  1. Expected Key Experts
    2. \n
\n\n

The consultant's team shall be composed of qualified experts with proven experience. The bidder must propose, at a minimum, the following Key Expert positions:

\n\n

Key Expert 1: Team Leader / Project Manager

\n\n

Key Expert 2: Business Analyst Expert

\n\n

Key Expert 3: Developer/Digital Transformation Architect

\n\n

Bidders may propose additional non-key experts as they see fit to successfully deliver the scope of work.

\n\n

Required Qualifications

\n\n

All experts must be fluent in English and Arabic (written and spoken). The minimum required qualifications for the Key Experts are as follows:

\n\n

Key Expert 1: Team Leader / Project Manager

\n\n\n\n

Key Expert 2: Senior Business Process Re-engineering (BPR) Expert

\n\n\n\n

 

\n\n

Key Expert 3: Senior Digital Solution Architect

\n\n\n\n\n\n
    \n\t
  1. Reporting Requirements
    2. \n
\n\n

The Consultant’s reporting obligations are divided into two distinct categories: Contractual Deliverables and Administrative Progress Reports.

\n\n

11.1 Contractual Deliverables (Payment Milestones)

\n\n

These outputs are directly linked to the payment schedule defined in the Deliverables Table (Section 6). Payments will only be released upon formal written acceptance of these specific documents by the TC.

\n\n\n\n

11.2 Administrative Progress Reporting (Monitoring Only)

\n\n

These reports are for performance monitoring and coordination purposes.

\n\n\n\n

11.3 Enforcement of Reporting Compliance

\n\n

Timely submission of Administrative Progress Reports (as defined in Section 11.2) is a material obligation of the Consultant and considered an integral part of the deliverables and related acceptance.

\n\n
    \n\t
  1. OMSAR and OMSTAI Inputs
    2. \n
\n\n

To facilitate the successful execution of the assignment, OMSAR and OMSTAI shall provide the following:

\n\n\n\n
    \n\t
  1. Environmental and Social Considerations
    2. \n
\n\n

The Firm shall integrate environmental and social principles consistent with the World Bank Environmental and Social Framework (ESF) throughout the redesign and development of e-services. All work must ensure:

\n\n\n\n

These considerations should be reflected in service workflows, user experience recommendations, prototypes, and final technical outputs.

"},{"id":"OP00376045","notice_type":"Request for Expression of Interest","noticedate":"29-Aug-2025","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2025-09-29T00:00:00Z","submission_deadline_time":"18:00","project_ctry_name":"Brazil","project_id":"P168634","project_name":"Parana Public Sector Modernization and Innovation for Service Delivery Operation","bid_reference_no":"BR-SPPE-340218-CS-QCBS","bid_description":"Plano de Dimensionamento da Força de Trabalho - Contratação de consultoria para elaboração de dimensionamento da força de trabalho da administração direta e autárquica do estado do Paraná.","procurement_group":"CS","procurement_method_code":"QCBS","procurement_method_name":"Quality And Cost-Based Selection","contact_address":"Rua Jacy Loureiro de Campos - Centro Cívico, Curitiba - PR, 82590-300","contact_ctry_name":"Brazil","contact_email":"licita.bird@seap.pr.gov.br","contact_name":"Wellington Dias de Paula","contact_organization":"Secretaria de Estado da Administração e da Previdência / State Secretariat for Administration and Social Security (SEAP)","contact_phone_no":"(41) 3313-6362","contact_web_url":"www.administracao.pr.gov.br","submission_date":"2025-08-29T00:00:00Z","notice_text":"

NOTICE OF REQUEST FOR EXPRESSION OF INTEREST IN SELECTION

\n\n

BASED ON QUALITY AND COST – SMI 003/2025

\n\n

 

\n\n

SELECTION OF CONSULTANCY IN PROJECT FINANCED BY THE IBRD TO PREPARE A WORKFORCE SIZING PLAN FOR THE DIRECT ADMINISTRATION AND AUTONOMOUS AGENCIES OF THE STATE OF PARANÁ

\n\n

 

\n\n

Brazil

\n\n

Innovation and Modernization Project for Public Management in Paraná - EFFICIENT PARANÁ PROJECT

\n\n

Loan Agreement: N°. 9378-BR[1] - BIRD

\n\n

Contract Object: Preparation and implementation of a Sizing methodology, based on pre-existing models and/or models developed for this purpose, and a Workforce Adequacy Plan (replacement, expansion and optimization) for agencies and entities of the Direct Administration and Autonomous Agencies of the State of Paraná, aiming at providing subsidies for the entry policy for the short, medium and long term, based on the identification of a sufficient and adequate number of employees so that the agencies can deliver the public services they are responsible quickly and efficiently, and also an information technology system that includes the means for their continuous management and monitoring.

\n\n

 

\n\n

Reference N°.: BR-SPPE-340218-CS-QCBS

\n\n

 

\n\n

1.    The State of Paraná received a loan from the International Bank for Reconstruction and Development (IBRD) under the Paraná Public Management Innovation and Modernization Program – Efficient Paraná for the Development of Paraná. The program was structured to respond the challenges faced by the State of Paraná in providing health and other priority public services, in addition to supporting the implementation of the economic recovery plan in response to the short, medium, and long term impacts of the COVID-19 pandemic. The project's main overall objective is to mitigate the impacts of COVID-19 on health and improve the efficiency and effectiveness of health service delivery, environmental management, and public administration through management reforms and the use of information technology.

\n\n

2.    This request for Expression of Interest is in accordance with the General Procurement Notice for this Project, published on Development Business online (UNDB online), on: 19/02/2024.

\n\n

3.    Thus, the State of Paraná, through the State Secretariat for Planning - SEPL and the Department of Human Resources and Social Security - DRH of the State Secretariat for Administration and Social Security - SEAP, inform that they will prepare a Short List of institutions for selection of Consulting in the Preparation of the Workforce Sizing Plan, in accordance with the Acquisition Regulation for Borrowers of Investment Project Financing Operations in the acquisition operations of Goods, Works, Technical Services and Consulting Services, resulting from an Agreement in the form of Investment Project Financing - IPF for AT, Fourth Edition, November 2020.
\nThe State Secretariat of Administration and Social Security invites eligible consulting institutions to express their interest in providing the Services. Interested consulting firms must provide information demonstrating their required qualifications and relevant experience to perform the Services. The Short List criteria are as follows: core business, number of years in the business, and relevant experiences. Lead Specialists will not be evaluated at the Short list stage.

\n\n

4.    The consulting services covered by the Terms of Reference (TDR) cover the diagnosis, sizing, and planning of the State of Paraná's workforce within 11 (eleven) agencies and entities, including the collection of information and standards, interviews, diagnostics, and flows and tools available within the agencies involved. The services include the development of an Information System for managing workforce planning.

\n\n

5.    The consulting services to be contracted aim to develop and implement a methodology for sizing and adequacy plan of the workforce (replacement, expansion and optimization) of the Direct Administration and Autonomous Agencies of the State of Paraná, indicating the priority sectors and their respective costs, as well as suggestions for improving management that allow for more efficient use of resources related to personnel expenses in accordance with the structures contained in Annexes I and II of the Terms of Reference, which provide subsidies for the recruitment policy for the short, medium and long term, based on the identification of a sufficient and adequate number of employees so that the agencies can deliver their respective public services quickly and efficiently, and also the formulation and implementation of an information technology system that includes the means for continuous management and monitoring through system development and integration of software tools. 

\n\n

6.    The full implementation of this project is expected to last 21 (twenty-one) months.

\n\n

7.    The details of the Terms of Reference (TDR) for these Services are attached to this Notice of Request for Expression of Interest and available on the website: https://www.administracao.pr.gov.br/Compras.

\n\n

8.    Eligible institutions interested in providing these services must express their interest by submitting information demonstrating the experience and expertise required to perform the requested services. To this end, they must submit:
\na.    Characterization of the company/institution containing all data according to model “A”.
\nb.    List of completed and completed work similar to the subject matter of the TDR, with proof of services provided. Submit a completed table according to model "B."
\nc.    Declaration of intent to form a consortium, if appropriate. In this case, identify the institution with which you intend to establish the consortium relationship, according to model "C." The required information must include the identification of each potential consortium member, as well as their respective legal representatives. Formalization of the consortium is required only upon signing the contract, whereby the members will be equally responsible.
\nd.    Documentation grouped and numbered in a unique, continuous and sequential way.
\ne.    The pages corresponding to the documentation supporting the information included in the tables (models A, B and C) must be numbered in sequence.
\nf.    Other information or documents that the company/institution considers relevant to demonstrate its experience in services related to the subject of the TDR;
\ng.    Documentation that is not presented in accordance with models “A”, “B” and “C” and as follows will be disregarded:
\n•    Tables must be submitted in PDF format and in editable format (Excel);
\n•    If necessary, add rows to the table;
\n•    Documents not indicated in the table will not be considered.

\n\n

9.    This Request for Expression of Interest, as well as the expression itself, does not imply any commitment to hiring.

\n\n

10.    Institutions will be selected according to the evaluation criteria for the composition of the “Short List”, according to their proven experience.

\n\n

11.    World Bank standards require consultants to provide professional, objective, and impartial advice, always prioritizing the client's interests without considering the possibility of future work. When offering consultancy, they must avoid conflicts with other services or their own corporate interests. Consultants may not be hired to perform any task that conflicts with their current or previously undertaken obligations to other clients, nor may it place them in a position that prevents them from performing the service in a manner that best serves the borrower's interests.

\n\n

12.    The selection and hiring of the consultancy will follow the provisions of the Acquisition Regulation for Borrowers of Investment Project Financing Operations in the acquisition of Goods, Works, Technical Services and Consulting Services, resulting from an Agreement in the form of Investment Project Financing - IPF for AT, Fourth Edition, November 2020.

\n\n

Available at:
\nPortuguese -
\nhttps://www.planejamento.pr.gov.br/sites/default/arquivos_restritos/files/documento/2022-12/Regulamento_de_Aquisi%C3%A7%C3%B5es_2020_PORT_reduced.pdf

\n\n

English -
\nhttps://thedocs.worldbank.org/en/doc/1783315330658711950290022020/original/ProcurementRegulations.pdf

\n\n

13.    Consulting firms may associate with other institutions to enhance their qualifications; however, they must clearly indicate whether the association will be a joint venture (consortium) or subcontracting. In the case of a joint venture (consortium), all members must be jointly and severally liable for the entire contract if the joint venture (consortium) is selected.

\n\n

14.    Without limiting the general nature of the above, consultants will not be hired in the situations described in the clauses dealing with conflicts of interest in the Procurement Regulation.
\nIt is the Bank's policy to require all borrowers, contractors and their agents, as well as all employees linked to them, to maintain the highest ethical standards during the selection and execution of contracts financed by the Bank under item 3.33 of the Procurement Regulations for Borrowers of Investment Project Financing Operations in the acquisition of Goods, Works, Technical Services and Consulting Services, arising from an Agreement in the form of Investment Project Financing - IPF for AT, Fourth Edition, November 2020.

\n\n

15.    Further information can be obtained by calling: (41) 3313-6221 and email: licita.bird@seap.pr.gov.br.

\n\n

16.    Expressions of interest will be received necessarily electronically, from August 29, 2025 to September 29, 2025 at the address: licita.bird@seap.pr.gov.br, Access links to virtual servers and digital format, in .pdf format, and must be accompanied by tables and supporting documents, as per Models A, B and C.

\n\n

16.1. The tables relating to Models A, B and C will be received necessarily electronically, at the address: licita.bird@seap.pr.gov.br, Access links to virtual servers and digital format, in PDF and 1 (one) editable copy in Excel.

\n\n

17. Expressions of interest will be received until 5:00 p.m. (five o'clock in the afternoon) on the last day of the deadline established as per the official publication of the bidding process.

\n\n


\nCuritiba, 29 of august of 2025.

\n\n

 

\n\n

[1]       Source: https://www.planejamento.pr.gov.br/Pagina/Parana-Eficiente-Banco-Mundial

\n\n

 

\n\n

MODEL “A” - Characterization of the company/institution

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Company/Institution Data

\n\t\t\t		\n\t\t\t

Description

\n\t\t\t		\n\t\t\t

Page N°.

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Interested Institution

\n\t\t\t		\n\t\t\t

Company name

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

CNPJ

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Segment

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Date of incorporation

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Legal nature

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

6

\n\t\t\t		\n\t\t\t

Size (Number of employees)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

7

\n\t\t\t		\n\t\t\t

Legal representative

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

8

\n\t\t\t		\n\t\t\t

Full address

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

9

\n\t\t\t		\n\t\t\t

Country

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

10

\n\t\t\t		\n\t\t\t

Telephone

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

11

\n\t\t\t		\n\t\t\t

e-mail

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

12

\n\t\t\t		\n\t\t\t

Website address

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

13

\n\t\t\t		\n\t\t\t

Your company's main area of activity

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

14

\n\t\t\t		\n\t\t\t

Consulting areas of activity: Public Management, People Management, others (specify)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

15

\n\t\t\t		\n\t\t\t

What services do you offer (Recruitment and Selection, HR Consulting, Training and Development etc.)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

16

\n\t\t\t		\n\t\t\t

How long has the company been operating in Human Resources Management Consulting?

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

17

\n\t\t\t		\n\t\t\t

Approximate number of contracts signed in the last 12 months:

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

18

\n\t\t\t		\n\t\t\t

Other information (list/include lines)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\n

Complete the information as above, attaching supporting documents and indicating the corresponding page. If submitting other relevant data/documents in addition to those indicated in the table, add additional lines.
\nDocuments not indicated in the table will not be considered.
\nAll documentation relating to the full versions of Models A, B and C must have unique, sequential and continuous numbering.
\nThe table must be submitted in PDF format and in editable format (Excel).

\n\n

 

\n\n

 

\n\n

MODEL “B” - Main projects similar to the subject of the TDR executed and under completion in the last 36 months

\n\n

Project 1: Name (fill in the table for each project).

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Data

\n\t\t\t		\n\t\t\t

Description

\n\t\t\t		\n\t\t\t

Page No.

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Contractor

\n\t\t\t		\n\t\t\t

Company name

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

CNPJ

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Segment

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Size (Number of employees)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Full address

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

6

\n\t\t\t		\n\t\t\t

Municipality

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

7

\n\t\t\t		\n\t\t\t

State

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

8

\n\t\t\t		\n\t\t\t

Country

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

9

\n\t\t\t		\n\t\t\t

Telephone

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

10

\n\t\t\t		\n\t\t\t

e-mail

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

11

\n\t\t\t		\n\t\t\t

Website address

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

12

\n\t\t\t		\n\t\t\t

Sphere (Private, Municipal, State, Federal)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

13

\n\t\t\t		\n\t\t\t

Legal regime (Statutory or Employment Law)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

14

\n\t\t\t		\n\t\t\t

Other information (list/include lines)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

15

\n\t\t\t		\n\t\t\t

Contract/supporting document

\n\t\t\t		\n\t\t\t

Object

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

16

\n\t\t\t		\n\t\t\t

Project Area

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

17

\n\t\t\t		\n\t\t\t

Workforce sizing (yes/no)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

18

\n\t\t\t		\n\t\t\t

Other area (specify)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

19

\n\t\t\t		\n\t\t\t

Number of servers/employees covered by the contract/project

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

20

\n\t\t\t		\n\t\t\t

Products delivered

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

21

\n\t\t\t		\n\t\t\t

System development (yes/no)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

22

\n\t\t\t		\n\t\t\t

Contract signature date

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

23

\n\t\t\t		\n\t\t\t

Start date of execution

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

24

\n\t\t\t		\n\t\t\t

End date of execution

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

25

\n\t\t\t		\n\t\t\t

Duration in months

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

26

\n\t\t\t		\n\t\t\t

Total contract value

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

27

\n\t\t\t		\n\t\t\t

Other information (list/include lines)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\n

Complete the information as above, attaching supporting documents and indicating the corresponding page. If submitting other relevant data/documents in addition to those indicated in the table, add additional lines.
\nDocuments not indicated in the table will not be considered.
\nPresent the data from the table above for each project.
\nAll documentation relating to the full versions of Models A, B and C must have unique, sequential and continuous numbering.
\nThe table must be submitted in PDF format and in editable format (Excel).

\n\n

 

\n\n

 

\n\n

 

\n\n

MODEL “C” – Companies/institutions intending to form the consortium

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Consortium Company/Institution Data

\n\t\t\t		\n\t\t\t

Description

\n\t\t\t		\n\t\t\t

Page No.

\n\t\t\t
\n\t\t\t

1

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

MAIN/LEADER CONSORTIUM MEMBER

\n\t\t\t
\n\t\t\t

Company name

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

CNPJ

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Country

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Declaration of intention to form a consortium

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

2

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

CONSORTIUM MEMBER 1

\n\t\t\t
\n\t\t\t

Company name

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

CNPJ

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Country

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Declaration of intention to form a consortium

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

3

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

CONSORTIUM 2

\n\t\t\t
\n\t\t\t

Company name

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

CNPJ

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Country

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Declaration of intention to form a consortium

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

4

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

CONSORTIUM 3

\n\t\t\t
\n\t\t\t

Company name

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

CNPJ

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Country

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Declaration of intention to form a consortium

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\n

Present the information/data from models “A” and “B” for each company/institution intending to form the consortium.
\nInsert lines if necessary
\nDocuments not indicated in the table will not be considered.
\nThe table must be submitted in PDF format and in editable format (Excel).

\n\n

 

\n\n

 

\n\n

TERMS OF REFERENCE

\n\n

 

\n\n

 

\n\n

HIRING OF CONSULTANCY FOR ELABORATION THE SIZING OF THE WORKFORCE OF THE DIRECT ADMINISTRATION AND AUTONOMOUS AGENCIES OF THE STATE OF PARANÁ

\n\n

 

\n\n

 

\n\n

SUMMARY
\n1.     CONTEXT    4
\n2.     JUSTIFICATION    4
\n3.     OBJECTIVES    7
\n3.1.     GENERAL OBJECTIVE    7
\n3.2.    SPECIFIC OBJECTIVES    7
\n4. GENERAL GUIDELINES AND SCOPE    8
\n4.1. WORKFORCE    9
\n4.2. METHODOLOGICAL PROPOSAL TO BE DETAILED IN THE WORK PLAN SHOULD CONSIDER THE FOLLOWING ASPECTS:    9
\n5. PRODUCTS INCLUDED IN THIS TERM    10
\n5.1. PHASE 1: WORK PLAN    10
\n5.2. PHASE 2: SURVEY OF THE CURRENT SITUATION AND SIZING OF THE WORKFORCE    12
\n5.2.1.     Survey of the Current Situation    12
\n5.2.2. Workforce Sizing    14
\n5.3. PHASE 3: WORKFORCE ADEQUACY PLAN (REPLACEMENT, EXPANSION AND OPTIMIZATION) FOR THE SHORT, MEDIUM AND LONG TERM AND WORKFORCE PLANNING INSTITUTIONALIZATION PLAN    17
\n5.3.1. The Adequacy and Implementation Plan for Replacement, Expansion and Optimization    17
\n5.3.1.2. Main Activities for Execution:    18
\n5.3.2. The Workforce Planning Institutionalization Plan    18
\n5.4. PHASE 4: COMMUNICATION AND TRAINING PLAN FOR MANAGERS WORKING IN THE TECHNICAL AREA AND PEOPLE MANAGEMENT.    19
\n5.5. PHASE 5: FORMULATION AND IMPLEMENTATION INFORMATION OF TECHNOLOGY SYSTEMATICS APPLIED TO WORKFORCE SIZING – DEVELOPMENT OF INFORMATION SYSTEMS.    20
\n5.5.1. Information Technology Systematics Applied to Workforce Sizing – Development of Information Systems.    21
\n5.5.1.1. System Project Plan    22
\n5.5.1.2. Business Process Modeling    22
\n5.5.1.3. Data Load Module    22
\n5.5.1.4. Sizing Module    23
\n5.5.1.5. Global Integration (final delivery)    23
\n6.     PHYSICAL-FINANCIAL EXECUTION SCHEDULE OF PRODUCTS    24
\n7.    FORM OF PRESENTATION AND DELIVERY OF PRODUCTS (TABLE 2)    25
\n8.    AVAILABLE INPUTS    25
\n9.    EXECUTIVE GROUP RESPONSIBLE FOR MONITORING AND APPROVAL OF PRODUCTS        26
\n10. KEY TEAM    26
\n11. SUPPORT TEAM    27
\nANNEX I - LIST OF AGENCIES/ENTITIES OF DIRECT ADMINISTRATION AND AUTONOMOUS AGENCIES OF THE STATE OF PARANÁ    28
\nANNEX II - NUMBER OF POSITIONS/FUNCTIONS PER CAREER CADRE    29
\nANNEX III - GUIDELINES AND REQUIREMENTS SPECIFICATION FOR SOFTWARE DEVELOPMENT    30
\n(PHASE 5 –5.5)    30
\n1.    SCOPE AND LIMITS OF THE PRODUCT    30
\n1.1.    GENERAL DEFINITIONS ABOUT SYSTEM PROJECT    30
\n1.2.    PHYSICAL VIEW OF THE SYSTEM    31
\n1.2.1     SEAP SYSTEMS TO BE INTEGRATED    32
\n2.    ACTIVITIES TO BE DEVELOPED    33
\n2.1. SYSTEM PROJECT PLAN    33
\n2.2. DESIGN AND DEVELOPMENT    34
\n2.2.1. BUSINESS PROCESS MODELING    34
\n2.2.2. SYSTEMS ANALYSIS AND DESIGN    34
\n2.2.3. SOFTWARE ANALYSIS AND DESIGN    35
\n2.3. INTEGRATION AND QUALIFICATION    35
\n2.3.1. PREPARATION OF THE SYSTEM TEST PLAN    36
\n2.3.2. TESTING PROCEDURES    36
\n2.3.3. ACCEPTANCE TESTS – APPROVAL ENVIRONMENT    36
\n2.3.4. ACCEPTANCE TESTING – PRODUCTION ENVIRONMENT    36
\n2.4.     TRANSITION    37
\n2.4.1.     ASSISTED OPERATION    37
\n2.4.2. DATA INTEGRATION    38
\n2.5.    SOURCE CODE    38
\n2.6.    DOCUMENTATION    39
\n2.7.    TRANSFER OF TECHNOLOGY    39
\n2.8.    APPROVAL OF THE INTEGRATED ENVIRONMENT    40
\n2.9.    MAINTENANCE AND TECHNICAL SUPPORT    40
\n2.10.    SYSTEM OPERATION INFRASTRUCTURE SPECIFICATION    42
\n2.11.    PREPARATION OF DEVELOPMENT, APPROVAL AND PRODUCTION ENVIRONMENTS    43
\n3.    PRODUCTS, EXPECTED RESULTS, FORM OF PRESENTATION AND ACCEPTANCE OF SERVICES    43
\n3.1.    PRODUCTS AND BY-PRODUCTS TO BE SUPPLIED    43
\n3.2.    FORM OF PRESENTATION AND ACCEPTANCE OF PRODUCTS    45
\n3.3.    PLACE OF SERVICE PERFORMANCE    46
\n4.    TECHNOLOGICAL PARTNER    46
\n5.    CELEPAR PRODUCTION ENVIRONMENT    47
\nANNEX IV        49

\n\n

 

\n\n

TERMS OF REFERENCE

\n\n


\nHIRING OF CONSULTANCY FOR ELABORATION THE SIZING OF THE WORKFORCE OF THE DIRECT ADMINISTRATION AND AUTONOMOUS AGENCIES OF THE STATE OF PARANÁ

\n\n

1.     CONTEXT

\n\n

The Direct Administration and Autonomous Agencies of the Executive Branch of the State of Paraná is structured into forty-seven agencies and, to meet its responsibilities, relies on a workforce that totals, considering all types of service provision, 125,043[1]  positions/functions. This structure serves the 399 municipalities of the State in a centralized or decentralized manner and includes statutory employees (civil and military), employees under the CLT, temporary hires, positions in commission without a bond and interns.

\n\n

The State Secretariat for Administration and Social Security (SEAP) is responsible for managing the state's human resources through the Human Resources and Social Security Department (DRH/SEAP), a unit responsible for formulating, standardizing and monitoring public policies in this sector. Specifically, with regard to planning and supplying human resources, the Human Resources Recruitment and Selection Division (DSRH) is responsible for analyzing applications for admission of civil servants (civil and military) and temporary contracts through special regime contracts (CRES). These modalities correspond to 94.8% of the total available workforce.

\n\n

2.     JUSTIFICATION

\n\n

The current economic and social situation in Brazil requires that the public administra-tion rethink its role and seek to optimize the application of the resources at its disposal, emphasizing results and improving the services provided to the population. However, the effective execution of services depends largely on the workforce, whether for the implementation of public policies or for developing and articulating solutions to the de-mands of the State.
\nOn the other hand, managers shall ensure the maintenance of services and the achieve-ment of results while at the same time reconciling their actions with the available finan-cial, budgetary, human and material resources and complying with the expenditure limits set by the Fiscal Responsibility Law.
\nAdded to this context was the scenario outlined by the outbreak of the Coronavirus pandemic, which had a strong impact on the economy and the demand for certain ser-vices, leading to an imbalance in public finances. This combination of factors requires that the State's strategic actions converge to address it, as well as to implement immedi-ate interventions in the areas of Health and sectors with the potential to leverage the resumption of economic growth. In this line of understanding, Workforce Sizing emerg-es as a tool to drive this direction, as it will support the formulation of guidelines for people management to face these challenges.
\nGiven this scenario, it is essential and urgent to adopt a methodology to obtain subsidies with technical grounds for establishing a policy for hiring civil servants in the short, me-dium and long term, based on the identification of a sufficient and adequate number of professionals in order to enable agencies to deliver public services quickly and efficient-ly. It is also necessary to indicate the academic and professional profile aligned with each of the segments of state activity.
\nThe absence of such methodology sometimes results in the cost being prioritized over the benefit of a given recruitment of personnel, however without being able to assess the resulting loss due to the failure to achieve results in government projects and programs affected by the lack of these professionals.
\nCurrently, a well-founded methodology based on pre-established sizing parameters is not adopted. When analyzing requests for authorization to enter through a public selec-tion process, formal aspects are predominantly considered, such as: (i) the existence of vacant positions in the careers to which the personnel is intended; (ii) compatibility of the positions/functions with the indicated duties and with the corresponding position structure; (iii) the justification presented; (iv) the number of civil servants in the posi-tions/functions that are the subject of the demand. It should be noted that, in relation to this last point, the ideal is to consider, in addition to the quantity, the situation of these civil servants in terms of productivity, time until retirement, among others.
\nThe same applies to requests for temporary hires, but with some aggravating factors, since these are intended to replace an employee who is temporarily away, considering that the number of employees may be oversized, the need for replacement in some cases is questionable and may be unnecessary. It should also be considered that not every dismissal or temporary absence necessarily has to give rise to a replacement.
\nIn addition to all these factors, it is essential to recognize that the area of human re-sources management in state administration faces a dilemma between providing the de-partments with qualified employees, with compatible and attractive remuneration, and in sufficient numbers to meet the demands for public services, and the imperative need to adjust to the spending limits imposed by the Fiscal Responsibility Law.
\nIncidentally, personnel expenses have frequently reached worrying levels, which reaf-firms the need for in-depth reflection on the rational allocation of financial and human resources and their effectiveness. It is worth noting that the diversity of career cadre and the remuneration structure based on differentiated treatment for certain units limits the administration's ability to reallocate personnel between the various departments.
\nWhile the recruitment of employees, whether to maintain the provision of services or to implement new demands, requires better planning and greater agility, the loss of em-ployees is continuous and affects all departments. To better demonstrate the magnitude of the numerical reduction over the last 9.6 years, the figures recorded in September 2015 can be used again, when the total workforce was 195,529 positions/functions and the average monthly number of dismissals was 412.67.
\nThe layoffs, whose current monthly average is around 336[2]  positions, the fact that 45.2%[3]  of the effective employees are in the age group of 50 years or more, with service time approaching retirement, demand a planning of restructuring of the career cadre that allows the necessary transfer of technical knowledge and experience acquired over the years.
\nIn order to mitigate the losses resulting from the lack of replacement of dismissed civil servants, a decree was issued that establishes Replacement Rates[4]  for most positions provided for in the careers of Direct Administration and Autonomous Agencies. How-ever, its implementation requires constant monitoring through a structured methodology, which shall be integrated into the dimensioning of the workforce, complementing the planning tools for adequacy (replacement, expansion and optimization) of servers.
\nThat said, it is essential that the Administration has the elements to establish the bases of its personnel structure and identify where, in which activities, each type of contractual relationship applies: statutory, temporary, intern, outsourced services, among others. Furthermore, based on a consistent diagnosis, it is possible to detect, in addition to the lack of employees, the need for training, modernization of work processes and invest-ment in information technology, in its broadest sense.
\nIt is important to highlight the relevance of diagnosis and planning of human resources in Public Administration, as other public policies in the various sectors of activity, budg-etary and actuarial projections, among other aspects, depend on these.
\nHowever, the development of Sizing by the technical team of the Human Resources Recruitment and Selection Division, of the Human Resources Department of SEAP, is unfeasible, considering the insufficient number of existing technicians to carry out the work, the diversity of the activities developed, as well as the high specialization, fun-damental for such assignment.
\nIn view of the above, it is necessary to hire a human resources consulting company to develop and implement a Workforce Sizing methodology, based on pre-existing models and/or models developed specifically for agencies and entities of the Direct Administra-tion and Autonomous Agencies, structured in an information technology system that allows its management and continuous monitoring.

\n\n

3.     OBJECTIVES
\n3.1.     GENERAL OBJECTIVE
\nContract the elaboration and implementation of a Sizing methodology, based on pre-existing models and/or models developed for this purpose, and a Workforce Adequacy Plan (replacement, expansion and optimization) for the agencies and entities of the Direct Administration and Autonomous Agencies of the State of Paraná, in accordance with the structures contained in the ANNEX I and ANNEX II of this Term, which provide subsidies for the admission policy for the short, medium and long term, based on the identification of a sufficient and adequate number of civil servants so that the agencies can deliver the public services that are their responsibility quickly and efficiently, and also an information technology system that includes the means for their continuous management and monitoring.

\n\n

3.2.     SPECIFIC OBJECTIVES
\n3.2.1.    Survey of the current situation of the existing workforce in the agencies, from a qualitative, quantitative and cost perspective, by type of employment relationship, position/function, with emphasis on the activities performed, as well as the respective institutional data, such as characterization, objectives and organizational structure. Factors with potential impact on the dimensioning of the workforce should also be surveyed, such as information regarding turnover, absenteeism, absences, seasonal demand, pent-up demand, overestimated demand, deviations from function and their effects on performance and productivity.

\n\n

3.2.2.    Qualitative and quantitative dimensioning of the necessary human resources, by type of link, position/function, to the agencies and entities of the Direct Administration and Autonomous Agencies  of the Executive Branch indicated in Annex I of this Term, developing methodologies, based on the prospecting of existing models in Brazil and abroad, adopted in public and/or private administration, types of activities, implemented on a similar or larger scale, legislation applied to the sector and/or definition of specific parameters, taking into account the current and future scenario of the State of Paraná.

\n\n

3.2.3. Plans for:
\n3.2.3.1. Adequacy (replacement, expansion and optimization) of the workforce, based on the need indicated in the dimensioning versus the quantity indicated in the survey of the current situation, for the short term: zero to two years, medium term: 3 to 5 years and long term: 6 to 10 years, which includes suggestions for adjustments and measures to be adopted and considers replacement rates, cost projections, the State's budgetary capacity and the potential to meet demand through the expansion of vacancies in current public examinations; and
\n3.2.3.2. Institutionalization of workforce planning within the scope of the Direct Administration and Autonomous Agencies  of the Executive Branch that establishes the organization and functioning of the processes that constitute it, as well as the governance and management mechanisms for the continuous implementation and improvement of the program.
\n3.2.4. Project Communication Plan, as detailed in subitem 5.4.1, for each target audien-ce and for each product generated throughout the project, and Training of those invol-ved in the project, as described in subitem 5.4.2, with the purpose of ensuring its execu-tion from start to finish, its subsequent replication and continuous use, covering human resources technicians and managers, strategic managers, IT professionals designated by the Information and Communication Technology Company of Paraná – Celepar, and the Project Executive Group, for the assimilation of the developed methodology and the monitoring of its application.
\n3.2.5. Formulation and implementation of a system using information technology, appli-ed to Workforce Sizing – Development of information systems compatible with the sys-tems used in the State of Paraná, which will enable permanent support for the execution, processing, and diagnosis of workforce sizing, with an estimate of the respective costs.

\n\n

The details of each specific objective are presented in item “ 5. PRODUCTS INCLUDED IN THIS TERM”.

\n\n


\n4. GENERAL GUIDELINES AND SCOPE 

\n\n

This Workforce Sizing project shall include the Agencies/Entities of the Direct Administration and Autonomous Agencies (Annex I), headquartered in the capital and/or in the interior of the state, according to their location and respective regionalized structure.

\n\n

Likewise, the products to be developed within the scope of the project, as per Table 2, shall cover all the Agencies/Entities covered (Annex I), careers/career cadres with respective positions/functions, which have not been declared extinct upon becoming vacant (Annex II). It should be noted that possible changes in the organizational structure and/or careers/career cadres due to new state management guidelines implemented after the publication of this Term shall be considered and incorporated. Consider the updated version of Annexes I and II at the time of the contract.

\n\n

4.1. WORKFORCE 

\n\n

Table 1 - Total workforce size

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Description

\n\t\t\t		\n\t\t\t

Qty.

\n\t\t\t
\n\t\t\t

Effective civil servants (civil and military)

\n\t\t\t		\n\t\t\t

113,600

\n\t\t\t
\n\t\t\t

Unlinked commissioned positions

\n\t\t\t		\n\t\t\t

3.239

\n\t\t\t
\n\t\t\t

Special Regime Contracts (temporary)*

\n\t\t\t		\n\t\t\t

4,940

\n\t\t\t
\n\t\t\t

Interns (Middle and Higher Levels)

\n\t\t\t		\n\t\t\t

2.606

\n\t\t\t
\n\t\t\t

Others (CLT)

\n\t\t\t		\n\t\t\t

658

\n\t\t\t
\n\t\t\t

TOTAL

\n\t\t\t		\n\t\t\t

125,043

\n\t\t\t
\n\n

Source: RHPARANA META4 – January/2025 base

\n\n

* The number of temporary contracts for January is atypical, as it is a school break period and does not include teachers in Basic Education. The average for the school term is around 25,000.

\n\n

 

\n\n

4.2. METHODOLOGICAL PROPOSAL TO BE DETAILED IN THE WORK PLAN SHOULD CONSIDER THE FOLLOWING ASPECTS:
\n4.2.1. The execution of the work may adopt different methodologies in relation to the surveys and analyses provided for in the other products: (i) activities whose dynamics and typology allow the establishment of productivity and performance parameters, in final activities of service provision, regional or sectoral administration, such as Regional Health, Hospitals, Socio-Education Centers, Regional Education Offices, Instrumental Units, among others; (ii) activities related to management, advisory, formulation of pu-blic policies, and regulation, in which the nature of the activities presents complexity in establishing parameters for the comparison of productivity and performance, in view of the diversity of processes.
\n4.2.2. Parameters may be established for the workforce necessary to meet the current and future demands of the State, in accordance with the methodological proposal and products to be developed under this Term.
\n4.2.3. Due to the scope of the universe of analysis, the methodology and execution of the work shall adopt the following Strategic Lines of Action of the State: a) Health; b) Justice, Rights; c) Urban and Economic Development; d) General Government Adminis-tration; e) Education. It is emphasized that, in the development of the products, priority shall be given to the Health area. Regarding the Strategic Lines of Action of the State, their delimitation will be confirmed prior to the preparation and execution of the Work Plan. Within the scope of the Universities, only University Hospitals – UHs will be con-sidered, which will be included in the Strategic Line of Health.
\n4.2.4. The Methodological Proposal, including in the data collection and definition of parameters, may, subject to the Client’s approval, be developed through the establish-ment of stratified and representative samples in each area, agency, or career cadre, pro-vided that there is a high degree of standardization of processes.
\nBoth the Workforce Sizing of the Ideal career cadre (Phase 2) and the Planning for the Adequacy of the Workforce (Phase 3) shall show the number of positions/functions cur-rently provided for in the careers, for which, according to the diagnosis carried out (Phase 2), the lack of necessity is found, or recommendations are made in terms of care-er or employment relationship. The products presented shall consider the possibility of optimizing the existing career cadre and career structures. If necessary, new functions shall be proposed considering the profile and qualifications required to meet unmet de-mands, as well as indicating the possibilities and/or need for the relocation and retrai-ning of existing professionals.

\n\n

 

\n\n

5. PRODUCTS INCLUDED IN THIS TERM

\n\n

Table 2 - Products included in this Terms of Reference

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

PHASE

\n\t\t\t		\n\t\t\t

PRODUCT

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

WORK PLAN

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

SURVEY OF THE CURRENT SITUATION AND SIZING OF THE WORKFORCE

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

ADEQUACY PLAN (REPLACEMENT, EXPANSION AND OPTIMIZATION) FOR THE SHORT, MEDIUM AND LONG TERM AND WORKFORCE PLANNING INSTITUTIONALIZATION PLAN

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

COMMUNICATION AND TRAINING PLAN FOR MANAGERS OPERATING IN THE TECHNICAL AND HUMAN RESOURCES MANAGEMENT AREAS

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

FORMULATION AND IMPLEMENTATION OF INFORMATION TECHNOLOGY SYSTEMATICS APPLIED TO WORKFORCE SIZING – DEVELOPMENT OF INFORMATION SYSTEMS.

\n\t\t\t
\n\n

 

\n\n

5.1. PHASE 1: WORK PLAN

\n\n

Prior to the development of the work, a document describing the Work Plan for executing the purpose of this terms shall be submitted for approval by the Executive Group responsible for monitoring the services.

\n\n

In order to prepare the Work Plan, with the aim of supporting the contractor, a technical meeting will be held with the Executive Group to pass on available information summarized as to the organizational structure, current data, current panorama of human resources management, number of employees, reports that are part of the database of the State's human resources management systems, relevant legislation, career cadre , professional profiles, interlocutors involved and expectations regarding the work. Additional information may be made available to the consulting firm, upon express request, at least 15 (fifteen) business days in advance. If the information provided is considered insufficient by the contractor, the contractor shall provide other information that it deems relevant from other sources by its own means.

\n\n

The Work Plan shall present:
\n-    Report containing a detailed description of the methodological proposal to be adopted, specifying the model parameters, variables required for data analysis, indicators, among other elements necessary for a better understanding and approval of the methodology to be applied.
\n-    Tool, made available by the contractor, which will be used for project governance during its execution.
\n-    Physical and financial schedule with all activities to be developed and their respective costs and durations, compatible with the deadlines established by the Client, in a sequence that considers the precedence and dependency relationships between activities. The physical and financial schedule shall present the project milestones and define the dates and costs of the deliveries of intermediate and final products for each project activity. Any changes shall be approved by the Client.
\n-    Quality and Risk Management Plan containing a detailed description, by project activities, of the quality assurance process and compliance of the project products based on the Technical Specifications of this Term of Reference. The quality and Risk Management plan shall include the Risk Matrix, including planned, corrective and predictive actions.
\n-    Project Communication Plan indicating the different approaches between the management, coordination, technical and target audience levels of the surveys in each agency/entity as set out in Annex I, as well as between those responsible for the product in the Contractor and the Client; the communication strategies adopted for each product and interested parties at the internal and external levels. It shall include the plan for monthly and extraordinary project monitoring meetings, methods of recording the product (minutes, emails and other documents), constituting an integral part of the official product documentation and to be followed.
\n-    Documents and forms to be used in data collection and interview scripts, both those planned with directors and intermediate-level managers, as well as, if applicable, an indication of the applications and/or platforms used.
\n-    Schedule with estimated dates for technical visits and/or online meetings through an application or service with the possibility of sharing presentations and files via the web with the Agencies, located in the Capital and in the interior of the State, for data collection and application of interviews, which can be carried out remotely or through digital forms.
\n-    Technical team allocated and the organizational chart defined for the project, containing the Responsibility Matrix and the functions to be performed by each technical manager, identifying the management and coordination levels of each project activity.

\n\n

The Contractor shall describe in the project plan the approach envisaged for the development of the project, and its representation in the schedule details, considering the possibility of using multiple project deliveries, including a possible agile approach, compatible with the maturity stages of the methodology and its application throughout the contractual period. In these delivery stages, all types of products shall be considered, including artifacts provided for in the Information System.

\n\n

It is important to emphasize that, with regard to Phase 4 (Training), in addition to the items provided above, this Work Plan shall include: (i) the content to be covered in each training session; (ii) the objectives and details of the program; (iii) the methodologies and didactic-pedagogical strategies to be used; and (iv) workload.
\nThe Work Plan and project management shall be aligned with the project management method principles of the Project Management Body of Knowledge (PMBOK) / Project Management Institute (PMI), covering the following knowledge areas: project integration management; project scope management; project time management; project quality management; project human resource management; project communication management; project risk management.

\n\n

In relation to Phase 5 – Formulation and Implementation of an Information Technology System Applied to Workforce Sizing – Development of Information Systems, the actions/activities to be described in this Work Plan shall cover the major stages of system development, since the preparation of the System Project Plan (Annex III) is foreseen.

\n\n

Once the Work Plan is approved, the consultancy will begin the development of the products specified below, with the preparation and submission of monthly reports on the monitoring/execution of actions/activities to the Project Executive Group being mandatory.

\n\n

 

\n\n

5.2. PHASE 2: SURVEY OF THE CURRENT SITUATION AND SIZING OF THE WORKFORCE

\n\n


\n5.2.1.     Survey of the Current Situation

\n\n

Currently, the State workforce is made up of statutory employees (civil and military), employees with CLT contracts, commissioned positions without a contract, temporary contracts under a special regime, interns and outsourced service provision contracts.

\n\n

In parallel with the workforce survey, in order to understand the current and future scenarios and challenges of the different segments, it is necessary to approach the strategic management level of each agency, through structured interviews that can be conducted in person or remotely. The interviews should enable the mapping of seasonal demands[5]  and pent-up demands due to the lack of employees, the need for better qualification of professionals, or increased investment in information technology, in order to ensure the achievement of the results established in the government goals and programs quickly and efficiently.

\n\n

It is necessary to carry out a survey of the current situation of the workforce of the agencies, the structure of careers, attributions and other pertinent information, pointing out the distortions, deficiencies and problems identified, through the presentation of a consolidated diagnosis by agency and area of activity.
\nThe activities listed below constitute a reference model, which may be adapted, as well as supplemented with others by the Contractor, depending on the methodology adopt-ed, provided they are approved by the Client.
\n5.2.1.1.The survey of the current situation from a qualitative and quantitative point of view of the current situation of the workforce by career cadre/career and by agency of the Direct Administration and Autonomous Agencies should present, whenever possible, based on the data made available by the state and collected throughout the project, an estimate of current costs and should cover:
\n5.2.1.1.1. Survey and analysis of the current workforce in agencies/entities: quantity by type of employment relationship, career cadre, position/function and unit, with emphasis on the activities performed;
\n5.2.1.1.2. Survey, identification and analysis of the organizational structure of all Agencies/Entities that make up the Direct Administration and Autonomous Agencies according to the level of activity of the organizational structure, covering regional structures;

\n\n

5.2.1.1.3. Survey of legally established competencies, competencies intrinsic to the execution of the public service, and organizational goals of the Agencies/Entities subject to the dimensioning to be carried out according to the levels of action of their organizational structure, covering regional structures;

\n\n

5.2.1.1.4. Survey and analysis of available productivity data, individually and comparatively, in the case of units that have a similar service profile, providing, when possible, indicators for the subsequent preparation of action plans to improve productivity (for example, a plan for training employees, standardization of processes, automation of activities, need to improve technological conditions, including the use of information systems and application of artificial intelligence, etc.);

\n\n

5.2.1.1.5. Survey of information regarding turnover, absenteeism, absences, seasonal demand, pent-up demand, overestimated demand, deviations from function and their impacts on performance and productivity, as well as on the state public budget;

\n\n

5.2.1.1.6. Mapping of existing jobs in agencies/entities, by type: in-person, hybrid and teleworking, with a breakdown of the levels of operational units in their organizational structure;

\n\n

5.2.1.1.7. Conducting interviews with directors, managers, deans or key employees of the agencies/entities to learn about their vision and current and future challenges. The objective of these interviews is to identify the strategic role played by the State area and its vision for the future, taking into account social and economic changes, changes in labor and social security systems, technological and work processes innovations, and their respective impacts on the demand for the workforce, both qualitatively and quantitatively;

\n\n

5.2.1.1.8. Structured interviews with managers, those responsible, deans or reference employees of the agencies to identify and analyze priority demands, repressed demands, difficulties, distortions, critical issues, good management practices that resulted in increased productivity, among others. This activity should occur after the training described in subitem 5.4.2.1.;

\n\n

5.2.1.1.9. Obtaining information considered relevant to the execution of the survey and dimensioning, from the respective agencies and managers, using specific forms and structured questionnaires. This activity shall occur after the training described in subitem 5.4.2.2;

\n\n

5.2.1.1.10. Obtaining, from SEAP/DRH, macrodata relating to costs corresponding to the career cadre/careers, considering all financial advantages (bonuses, benefits, assistance, dangerousness, unhealthy conditions, among others) related to the position/function evaluated;

\n\n

5.2.1.1.11. Obtaining professional profiles for each position/function, such as education, duties, work regime, working hours, among others;

\n\n

5.2.1.1.12. Obtaining data from the HR management system and obtained through (interviews and forms), the percentage of absenteeism by function, disaggregated by career cadre, agency/entity, considering and discriminating the different causes of absence (foreseen and unforeseen);

\n\n

5.2.1.1.13. Identification of seasonal demand, pent-up demand, overestimated demand, function deviations and their impacts on performance and productivity, as well as on the state public budget, through interviews and forms by agency/entity, function.

\n\n

5.2.2. Workforce Sizing

\n\n

It is extremely important to identify, in terms of qualitative and quantitative profiles, the ideal career cadre for the functioning of the administrative units that make up the areas of State activity in the current context and over a horizon of up to 10 years.

\n\n

The sizing should be based on the identification of existing methodologies already implemented in other governments, similar studies, applied legislation and/or the development of a specific methodology for each area. The implementation of Workforce Sizing in private spheres that carry out activities that are not exclusive to the State may also be considered.

\n\n

It is important to emphasize that, as a general focus of the project, it should be considered that certain functions performed by the State are by nature exclusive to the public sector, such as the custody of inmates in socio-educational units. Others, such as those related to health and education, are carried out in both the private and public sectors, subject to the established constitutional competencies. However, for the proposals related to the Sizing of the Ideal career cadre, even in activities where the corresponding parameters are found in the private sector, it is necessary to assess whether the same parameters for sizing the workforce can be adopted, taking into account aspects of the legislation on public servants that impose some restrictions compared to other workers.

\n\n

Different strategies may be adopted for the various sectors according to the reality identified. For example, in areas and units with the same service profile, such as hospitals and schools, the sizing work can be replicated by adopting sizes. In units of the same profile and size or of equivalent size, the same dimensioning may be applied, but it shall always be aligned with the trend indicated by the demographic behavior of the state/municipalities.
\nAll changes to business requirements (activities, agencies, etc.) shall be parameterizable by Governance and Information Systems, when necessary, and may include:

\n\n

•    the creation and maintenance of the organizational structure, the definition of Organizational Units, their functions and hierarchical relationships for each institution;
\n•    workstation  and its specific characteristics (workstation profile).

\n\n

5.2.2.1. Sizing of the ideal career cadre qualitatively (position and function) and quantitatively of the workforce of the State's Direct Administration and Autonomous Agencies, detailed by Career Cadre and by Agency/Entity consolidated in a report to be delivered to the Client, covering:

\n\n

5.2.2.1.1. Consolidation of the methodological proposal for sizing the workforce, by area of activity, based on the collection of qualitative, quantitative and cost data, analysis of indicators and application of the adopted parameters;
\n5.2.2.1.2. Presentation of detailed and structured documentation/Dossier by area of activity, career cadre, position and function of the methodology developed for preparing the Workforce Sizing, indicating the parameters used, indicators and other information pertinent to the data modeling used;
\n5.2.2.1.3. Identification of which Agencies/Entities, based on a comparison of the proposed ideal sizing and the existing staff, are oversized, undersized, or have the correct sizing, but with an imbalance between the levels of activity of their organizational structure, covering the regions;

\n\n

5.2.2.1.4. Proposal of strategies aimed at optimizing human, material, financial and budgetary resources that include, among others:
\na) adjustments to the composition of the workforce, in terms of profile, hiring method, modernization and restructuring of career cadre, including recommendations for the elimination, creation or reformulation of positions and/or functions;
\nb) modernization of management through review of processes, investment in information technology, including the use of information systems and application of artificial intelligence, change in the way services are offered (digital and others);
\nc) adoption of the Teleworking regime[6];
\nd) indication of distortions, deficiencies and problems found and recommendation of the necessary interventions to solve them;
\ne) guidelines for developing a staff training plan;
\nf) Possibility of alternative service provision models that consider, among other possibilities, partnerships with the third sector, public-private partnerships and outsourcing.

\n\n

5.2.2.2. Main Activities for Execution:
\nThe activities listed below are a reference model and may be adapted or others added by the Contractor, depending on the methodology adopted, provided that they are ap-proved by the Client.
\n5.2.2.2.1. Identification of existing workforce sizing parameters, methodologies and studies.
\n5.2.2.2.2. Identification and definition of indicators and parameters to be adopted by the proposed methodology.
\n5.2.2.2.3. Proposals for measures to meet seasonal demands with quality, by level of activity of the organizational structure of the Agencies/Entities.
\n5.2.2.2.4. Analysis of the demographic behavior of the State and Municipalities and corresponding impact on the demand for services, with scenarios for the short, medium and long term, as covered in Phase 3.
\n5.2.2.2.5. Consolidation of the survey of workforce sizing methodologies, by area of activity, based on the survey of qualitative, quantitative and cost data, analysis of indicators and application of the adopted parameters;
\n5.2.2.2.6. The results obtained in the two sub-products, Survey and Sizing, shall be included in reports containing the reality found and the proposals related to Sizing in each of the Agencies/Entities, as well as, when possible, the disaggregation by their levels of action[7]. A summary report shall also be prepared, establishing a scenario of the State, where the predominant situations verified and their respective proposals will be listed.

\n\n

5.3. PHASE 3: WORKFORCE ADEQUACY PLAN (REPLACEMENT, EXPANSION AND OPTIMIZATION) FOR THE SHORT, MEDIUM AND LONG TERM AND WORKFORCE PLANNING INSTITUTIONALIZATION PLAN
\nOnce the Survey of the Current Situation and the Sizing of the Ideal Career Cadre have been completed, the deficit and surplus areas should be identified, indicating the necessary interventions, which may include, in addition to replacing or increasing the number of employees, the restructuring of work processes, requalification, reassignments or reformulation of the service contracting method.

\n\n

Next, a workforce adequacy plan (replacement, expansion and optimization) shall be drawn up, establishing the need to recruit employees and the respective cost forecast for the short, medium and long term, considering the expected recruitment resulting from replacement rates and projection of State revenues and expenses, by agency/entity, in accordance with the Career Cadres, Positions and Functions, taking into account the potential for using a reserve list in current public competitions and the limits established in Complementary Law No. 101, Fiscal Responsibility Law.
\nShort term - zero to 2 years;
\nMedium term - 3 to 5 years;
\nLong term - 6 to 10 years.
\n5.3.1. The Adequacy and Implementation Plan for Replacement, Expansion and Optimization
\n5.3.1.1. The Plan to be delivered to the Administration shall:
\n5.3.1.1.1. Demonstrate the losses to the full execution of public services and the resulting risks, in the event that the replacement indicated as necessary is not carried out;

\n\n

5.3.1.1.2. Identify services compromised due to lack/shortage of human resources;

\n\n

5.3.1.1.3. Present a comparison of personnel expenses, in different workforce replacement scenarios, and the agency's budget availability for personnel expenses;

\n\n

5.3.1.1.4. Present a report assessing the projection of demand for services provided, detailed by Career Cadre, Agency/Entity of the State's Direct Administration and Autonomous Agencies, for the next 2, 5 and 10 years, considering the expectation of layoffs and implementation of the replacement rate in the same periods and the prospect of advances in management performance resulting from the implementation of the measures indicated in the survey carried out and in the proposed dimensioning;

\n\n

5.3.1.1.5. Propose the adoption of strategies that consider the potential use of the reserve list of current public selection processes as well as the proposals highlighted in item 5.2. 2, aiming at the optimization of human, material, financial and budgetary resources; and

\n\n

5.3.1.1.6. Foresee the possible impact on the number of career cadre when proposing to adopt new hiring processes provided for in item 5.2.2.
\nThe analyses and results obtained from the above items shall be included in specific reports for each of the agencies/entities, as well as the breakdown by their levels of activity. A summary report on the State shall also be presented, consolidating the overall analysis.
\n5.3.1.2. Main Activities for Execution:
\nThe activities listed below constitute a reference model, which may be adapted, as well as supplemented with others by the Contractor, depending on the methodology adopted, provided they are approved by the Client.
\n5.3.1.2.1. Analysis of the demographic behavior of the State and Municipalities and corresponding impact on the demand for services, with scenarios for the short, medium and long term.
\n5.3.1.2.2. Projection of demand by agency/entity broken down by career cadre, Positions and Functions and consolidated by strategic line of State action (e.g.: health, education, management, among others), for 2, 5 and 10 years.
\n5.3.1.2.3. Projection of layoffs by position/function in the period, considering the different areas of activity under analysis.
\n5.3.1.2.4. Forecast of income resulting from the application of replacement rates.
\n5.3.1.2.5. Survey of current public selection processes  with the potential to meet demand.
\n5.3.1.2.6. Obtaining and analyzing historical budget data from the state administration.
\n5.3.1.2.7. Projection of server entry and maintenance costs.
\n5.3.1.2.8. Analysis of the impact of the proposed measures as set out in subitem 5.2.2.1.4. of subitem 5.2.2.

\n\n

5.3.2. The Workforce Planning Institutionalization Plan
\n5.3.2.1. The Plan to be delivered to the Administration shall:
\n5.3.2.1.1. Propose the management instance and the structure necessary for the implementation of workforce planning, which includes processing the sizing, comparison with the existing workforce, adoption of strategies and schedule for workforce adequacy, monitoring of the results obtained and other routines for periodic updating.
\n5.3.2.1.2. Establish the processes that make up workforce planning and the respective flows.

\n\n


\n5.4. PHASE 4: COMMUNICATION AND TRAINING PLAN FOR MANAGERS WORKING IN THE TECHNICAL AREA AND PEOPLE MANAGEMENT.
\n5.4.1. Project Communication Plan and Execution
\nThe Communication Plan will be developed prior to the start of the project and implemented throughout the entire life cycle. This plan aims to promote fluidity, coherence and effectiveness of communication among all stakeholders, respecting the different levels of responsibility and interest - managerial, coordination, technical and other stakeholders. It should also indicate specific approaches for each target audience in the agencies/entities, as set out in Annex I, and for each product generated throughout the project. It should include the plan for monthly and extraordinary meetings to monitor the project. between those responsible for the product at the Contractor and the Client, communication material and presentations, product recording methods (minutes, emails and other documents), constituting an integral part of the official product documentation to be followed at each stage of the project until completion. It shall also act in external communication by preparing materials for unions, the press, digital media and other dissemination channels relevant to the scope of the project.
\n5.4.2 Training
\nThe training will consist of events to be conducted at different times, as detailed below.
\n5.4.2.1. Carrying out at least 07 (seven) workshops with a minimum workload of 08 (eight) hours.
\nThe workshops, with a maximum of 40 (forty) participants each, aim to promote preliminary awareness in order to train and equip managers and technicians working in the area of human resources management, regarding the assumptions and foundations of the Management Model for Results in line with the object addressed in this Term. This training should address: (i) contextualization of the current economic scenario and its long-term projection; (ii) reflection on the role of the State and the trends for human resources management in the public sphere; (iii) presentation of the work schedule to be used in the project (in accordance with Phase 1 – Action Plan); (iv) description of the actions/activities involving the areas of human resources management.
\nThe Contractor is responsible for providing consultant(s) with compatible training, knowledge of the economic situation of international and national public administration and the socioeconomic reality of the State of Paraná, as well as skills in leading participants to reflect on the importance of each segment in meeting the set of demands of society.
\n5.4.2.2. Carrying out training, in each agency, for the employees who will work directly in the Survey stage (5.2), with the aim of ensuring that the information is passed on in an objective and appropriate manner, with a workload of around 8 (eight) hours.
\n5.4.2.3. Holding of 01 (one) Seminar, with a minimum workload of 04 (four) hours, and 02 (two) Workshops, with a minimum workload of 16 (sixteen) hours.
\nHolding a Seminar, with a minimum workload of 4 hours, for the Government's Strategic Center and the Project's Executive around 50 participants in each workshop system developed for application of the sizing methodology; (v) presentation of the proposal for training on the operationalization of the system and its functionalities, based on a guidance manual and tutorials; (vi) presentation of suggestions and proposals that provide for the maintenance of the system and the longevity of the methodology developed.
\nThe Contractor is responsible for providing a consultant to carry out the events included in this Product, who shall be an integral member of the key team, in addition to having communication and leadership skills and ability to conduct meetings with intermediate and strategic management levels.
\n5.4.2.4. Carrying out at least 01 (one) training course on the operation, administration and architecture of the Computerized System with a minimum workload of 24 (twenty-four) hours.
\nThis training shall be planned and conducted by the Contractor and aimed at addressing the system administration functions, with the objective of training the technicians working at SEAP (approximately 20 staff members) to operate and maintain the solution. At the end of the training, users should be able to use the system functions, also understanding its overall operation, to become agents for multiplying this knowledge within the agencies, and to recognize all modules and functions; define user types, granting different access levels; implement and parameterize the system, including the maintenance of indicators and calculation formulas, change tables, include new users, among other knowledge necessary to maintain the system's operability.
\nAt a specific moment of the aforementioned training, technicians from Celepar or another institution responsible for the State of Paraná system will be present so that the contractor can provide the knowledge that enables a structural view of the system, its components (programs, database and other tools), as well as mastery of the development environment, without prejudice to the specific training indicated in Annex III, in order to enable technology transfer.
\n 
\n5.5. PHASE 5: FORMULATION AND IMPLEMENTATION INFORMATION OF TECHNOLOGY SYSTEMATICS APPLIED TO WORKFORCE SIZING – DEVELOPMENT OF INFORMATION SYSTEMS.
\nThe importance or need for the application of information technology in Workforce Sizing programs lies precisely in the possibility of having a system that allows for permanent support for Human Resources management – in a timely manner and with reliable information – within parameters that allow for the provision of stability diagnostics between the demand for human resources and the availability of personnel, respecting their requirements, characteristics and skills. Systematically monitoring the impacts caused by permanent situations such as employee layoffs, especially retirements, and greater demand from society for improvements or expansion of certain services (e.g. health, education, etc.). Once the sizing parameters have been defined, the system will indicate the possible need for adjustments to the career cadre. Likewise, these diagnostics are influenced by temporary situations such as vacations, leaves and other types of absences of public servants.

\n\n

To achieve the main objective of the project, it is essential to ensure the continued application of the methodology, in order to direct efforts towards maintaining a human resources structure that meets the strategic objectives of the State, which are dynamic. At the same time, it is essential that the public administration takes ownership of the methodology and algorithms, as well as the data captured and the results of the project, generating continuous changes in work processes that will enable the optimization of human resources and public administration costs.

\n\n

Thus, the development of an information system, in the context of the project, is justified by the need for appropriation and continued application of the methodology/algorithms and dimensioning data, since the parameters and indicators defined by area of activity (e.g. service provision in the health and socio-educational areas), as well as other data related to the workforce of the agencies and entities (e.g. total number of positions by employment relationship, education, admissions, dismissals, absences, absenteeism), budgetary capacity, among other information, shall be updated systematically and routinely.

\n\n

However, it is important to emphasize that the perfect adherence of the system to be developed, to the RH- Paraná/Meta4 System, used by the State for payroll and functional registration management, is a sine qua non, consisting of a mandatory requirement. In other words, the system to be contracted shall be independent and capable of interacting with the RH-Paraná/Meta4 System and, if necessary, others used by the State. 

\n\n

In this context, the computational routines to be developed through an Information System shall be capable of storing and systematizing the collected data, representing the defined methodology through algorithms and providing the necessary results through queries, reports and panels, through a human interface with usability appropriate to the users of the Information System. The fundamental requirements, which may be complemented based on the definition of the proposed Methodology, are listed in ANNEX IV - List of Requirements for the DIMFT Information System.
\n5.5.1. Information Technology Systematics Applied to Workforce Sizing – Development of Information Systems.
\nThe definition of the products to be developed meets the guidelines and technological compatibility of the State of Paraná, having been established in conjunction with the Companhia de Tecnologia da Informação e Comunicação do Paraná - Celepar, as detailed in ANNEX III, which includes, among others, the specification of the technological environment for the operation of the System and the definition of the criteria to be used for the full implementation of the products that make up this Phase.

\n\n

5.5.1.1. System Project Plan
\nThe general Work Plan of the project shall be complemented and detailed with the spe-cific activities for the elaboration and implementation of the Information System.
\nThe approach to be used in the Information System project shall be compatible with the overall project approach, including the possibility of multiple iterations and an agile ap-proach. The activities listed in ANNEX III primarily aim to define a set of typical Soft-ware Engineering artifacts, without being limited to specific development models to be adopted. The approach strategy to be adopted for the project as a whole, and conse-quently for the software, shall define the development model to be used in the project, while taking into account the delivery of the products scheduled in the timeline de-scribed in item 6 – PHYSICAL-FINANCIAL EXECUTION SCHEDULE OF THE PRODUCTS:
\n•    System Project Plan
\n•    Business Process Modeling
\n•    Data Load Module
\n•    Sizing Module
\n•    Global Integration (final delivery)
\nThe System Project Plan shall be the first product of this phase to be delivered by the Contractor and shall be approved by the Project Executive Group and Celepar. The oth-er products define a perspective of executable product deliveries that support the activi-ties of Workforce Survey, Workforce Sizing, Workforce Adequacy, and Institutionaliza-tion of Workforce Planning.
\nThe detailed activities planned for the execution of the above products are provided in ANNEX III.

\n\n

5.5.1.2. Business Process Modeling
\nFor the execution of this product, the necessary activities and tasks for the system de-sign shall be considered, including the mapping and modeling of processes inherent to the sizing methodology, which will later serve as the basis for the entire design and specification of the Information System.Activities related to the execution of the fol-lowing sub-products shall be developed:(i) Process Mapping Document relating to the methodology defined for Workforce Sizing;(ii) Consolidation Document of the Process-es of the Workforce Sizing System (DIMFT), which will be part of the software solution scope.The technical reference for executing the activities for product delivery can be obtained in ANNEX III, essentially in its item 2.2. Business Process Modeling.
\n5.5.1.3. Data Load Module
\nThis product will be characterized by the operational delivery of the Information System functionalities that support the Workforce Survey activities, within their processes de-fined as part of the software solution scope, and which will also constitute the databases later used in the other activities provided in the methodology.The technical reference for executing the activities for product delivery can be obtained in ANNEX III, essentially in its items 2.2. CONCEPTION AND ELABORATION and 2.3. INTEGRATION AND QUALIFICATION.
\n5.5.1.4. Sizing Module
\nThis product will be characterized by the operational delivery of the Information System functionalities that support the Workforce Sizing activities, within their processes de-fined as part of the software solution scope.The technical reference for executing the activities for product delivery can be obtained in ANNEX III, essentially in its items 2.2. CONCEPTION AND ELABORATION and 2.3. INTEGRATION AND QUALIFICATION.
\n5.5.1.5. Global Integration (final delivery)
\nThis product will be characterized by the operational delivery of the Information System functionalities that support the activities for the implementation of the Workforce Ad-justment Plan and the Institutionalization of Workforce Planning, according to the pro-cesses defined as part of the software solution scope. In addition to this specific deliv-ery, all other activities and deliveries scheduled for the completion of the Information System, as well as the services planned during the Assisted Operation and Technical Maintenance and Support periods, shall be included in this product delivery.The tech-nical reference for executing the activities for product delivery can be obtained in AN-NEX III, essentially in its items: 2.2. CONCEPTION AND DEVELOPMENT, 2.3. INTEGRATION AND QUALIFICATION, 2.4. TRANSITION, 2.5. SOURCE CODE, 2.6. DOCUMENTATION, 2.7. TECHNOLOGY TRANSFER, 2.8. IN-TEGRATED ENVIRONMENT ACCEPTANCE, 2.9. MAINTENANCE AND TECHNICAL SUPPORT, 2.10. SYSTEM OPERATION INFRASTRUCTURE SPECIFICATION, and 2.11. PREPARATION OF DEVELOPMENT, AC-CEPTANCE, AND PRODUCTION ENVIRONMENTS.

\n\n

 
\n6.     PHYSICAL-FINANCIAL EXECUTION SCHEDULE OF PRODUCTS
\nThe following schedule may be adapted depending on the details of the Work Plan, respecting the maximum time foreseen, from the signing of the contract, for the completion of the work.

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

MONTHS

\n\t\t\t
\n\t\t\t

PHASE/PRODUCT EXECUTION SCHEDULE

\n\t\t\t		\n\t\t\t

1 

\n\t\t\t		\n\t\t\t

2 

\n\t\t\t		\n\t\t\t

3 

\n\t\t\t		\n\t\t\t

4 

\n\t\t\t		\n\t\t\t

5 

\n\t\t\t		\n\t\t\t

6 

\n\t\t\t		\n\t\t\t

7 

\n\t\t\t		\n\t\t\t

8 

\n\t\t\t		\n\t\t\t

9 

\n\t\t\t		\n\t\t\t

10 

\n\t\t\t		\n\t\t\t

11 

\n\t\t\t		\n\t\t\t

12 

\n\t\t\t		\n\t\t\t

13 

\n\t\t\t		\n\t\t\t

14 

\n\t\t\t		\n\t\t\t

15 

\n\t\t\t		\n\t\t\t

16 

\n\t\t\t		\n\t\t\t

17 

\n\t\t\t		\n\t\t\t

18 

\n\t\t\t		\n\t\t\t

19 

\n\t\t\t		\n\t\t\t

20 

\n\t\t\t		\n\t\t\t

21 

\n\t\t\t		\n\t\t\t

TOTAL  

\n\t\t\t
\n\t\t\t

PHASE 1 

\n\t\t\t		\n\t\t\t

5.1

\n\t\t\t		\n\t\t\t

PRODUCT 1 – WORK PLAN

\n\t\t\t		\n\t\t\t

 -

\n\t\t\t		\n\t\t\t

10%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		 \n\t\t\t

10%

\n\t\t\t
\n\t\t\t

PHASE 2 

\n\t\t\t		\n\t\t\t

5.2

\n\t\t\t		\n\t\t\t

PRODUCT 2 – CURRENT WORKFORCE SURVEY AND WORKFORCE SIZING

\n\t\t\t
\n\t\t\t

5.2.1

\n\t\t\t		\n\t\t\t

Current Workforce Survey.

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

5.2.1.1

\n\t\t\t		Survey stage 1 - 50% of the Agencies - Annex I Report of Agencies/entities
\n\t\t\tof Direct Administration and Autonomous Agencies.		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

10%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

10%

\n\t\t\t
\n\t\t\t

5.2.1.2

\n\t\t\t		\n\t\t\t

Survey stage 2 - 50% of the Agencies - Annex I Report of Agencies/entities
\n\t\t\tof Direct Administration and Autonomous Agencies.

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

10%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

10%

\n\t\t\t
\n\t\t\t

5.2.2

\n\t\t\t		\n\t\t\t

Workforce Sizing

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

12%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

12%

\n\t\t\t
\n\t\t\t

PHASE 3 

\n\t\t\t		\n\t\t\t

5.3

\n\t\t\t		\n\t\t\t

PRODUCT 3 – WORKFORCE ADEQUACY AND WORKFORCE PLANNING INSTITUTIONALIZATION PLAN

\n\t\t\t
\n\t\t\t

5.3.1

\n\t\t\t		\n\t\t\t

Workforce Adequacy Plan (Replacement, Expansion and Optimization)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

5%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

10%

\n\t\t\t
\n\t\t\t

5.3.2

\n\t\t\t		\n\t\t\t

Workforce Planning Institutionalization Plan

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

5%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		 
\n\t\t\t

PHASE 4 

\n\t\t\t		\n\t\t\t

5.4

\n\t\t\t		\n\t\t\t

PRODUCT 4 - COMMUNICATION AND TRAINING PLAN FOR MANAGERS WORKING IN THE TECHNICAL AREA AND PEOPLE MANAGEMENT.

\n\t\t\t
\n\t\t\t

5.4.1

\n\t\t\t		\n\t\t\t

Project Communication Plan

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

5%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

5%

\n\t\t\t
\n\t\t\t

5.4.1.1

\n\t\t\t		\n\t\t\t

Execution of the Project Communication Plan

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

7%

\n\t\t\t
\n\t\t\t

5.4.2

\n\t\t\t		\n\t\t\t

Training

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

5.4.2.1

\n\t\t\t		Carrying out at least 07 (seven) workshops with a minimum workload 
\n\t\t\tof 08 (eight) hours.		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

5.4. 2.2

\n\t\t\t		\n\t\t\t

Carrying out training in each agency for the Survey stage (5.2.1).

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 -

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

5.4.2.3

\n\t\t\t		Holding of 01 (one) Seminar with a minimum workload of 04 (four)
\n\t\t\thours and 02 (two) Workshops, with a minimum workload of 16 (sixteen) hours.		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		--\n\t\t\t

 

\n\t\t\t
\n\t\t\t

5.4.2.4

\n\t\t\t		\n\t\t\t

Completion of 01 (one) training session on the operation, administration and 
\n\t\t\tarchitecture of the Computerized System with a minimum workload of 24 
\n\t\t\t(twenty-four) hours.

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		-
\n\t\t\t

PHASE 5 

\n\t\t\t		\n\t\t\t

5.5

\n\t\t\t		\n\t\t\t

PRODUCT 5 – FORMULATION AND IMPLEMENTATION OF INFORMATION TECHNOLOGY SYSTEMS APPLIED TO WORKFORCE SIZING – DEVELOPMENT OF INFORMATION SYSTEMS.

\n\t\t\t
 \n\t\t\t

5.5.1

\n\t\t\t		\n\t\t\t

Information Technology Systematics Applied to Workforce Sizing – Development of Information Systems.

\n\t\t\t
 \n\t\t\t

5.5.1.1

\n\t\t\t		\n\t\t\t

System Project Plan

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

4%

\n\t\t\t
\n\t\t\t

5.5.1.2

\n\t\t\t		\n\t\t\t

Business Process Modeling

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

4%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

5.5.1.3

\n\t\t\t		\n\t\t\t

Data Loading Module

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

6%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

6%

\n\t\t\t
\n\t\t\t

5.5.1.4

\n\t\t\t		\n\t\t\t

Sizing Module

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

8%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

8%

\n\t\t\t
\n\t\t\t

5.5.1.5

\n\t\t\t		\n\t\t\t

Global Integration (final delivery)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

-

\n\t\t\t		\n\t\t\t

18%

\n\t\t\t		\n\t\t\t

18%

\n\t\t\t
\n\t\t\t

PAYMENT (%)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

15%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

4%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

6%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

10%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

18%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

22%

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

25%

\n\t\t\t		\n\t\t\t

100%

\n\t\t\t
\n\n

 

\n\n

7.    FORM OF PRESENTATION AND DELIVERY OF PRODUCTS (Table 2)

\n\n

The Contractor  shall present in the Work Plan the standard and model for structuring, referencing and organizing the project documents, which shall be analyzed and approved by the Client. This will be the standard to be followed when delivering related products (Project Documents and Project Reports).
\nAll documents generated (manuals, results reports, presentations of work meetings, meeting minutes, teaching and learning materials for training, etc.) shall be submitted in two printed copies (when applicable), in Brazilian Portuguese, and on a magnetic medium (HD or similar) appropriate to the volume of the submission. The digital format shall be 1 (one) copy in .pdf and 1 (one) copy in open format of the software used (Word, for example).
\nPrinted copies shall be bound and organized into volumes corresponding to each of the by-products and/or products described in this Term.
\nThe preliminary version of the documents shall be forwarded to the Executive Group 5 (five) business days in advance of the presentation, which will take place through a face-to-face meeting between the Contractor and the Client, with a minimum workload of 8 (eight) hours, for discussion and validation, with the Contractor being responsible for implementing the adjustments defined after assessment by the Client.

\n\n

The Contractor shall deliver the final version of the deliverables (e.g. documents, files) within a maximum of 5 (five) business days after the face-to-face meeting.

\n\n

The form of presentation and acceptance of the products that make up Phase 5 shall comply with the description contained in subitem 3.2 of Annex III of this Term.

\n\n


\n8.    AVAILABLE INPUTS

\n\n

The Human Resources and Social Security Department of the Administration and Social Security Secretariat – DRH/SEAP, will provide a place for meetings, technical discussions and product presentations, as well as facilitating, within the scope of the State Administration, consultants' access to information relevant to their area of activity, scheduling meetings with interlocutors from the agencies involved and, when convenient, participating in them.
\nThe processes, documents, data and information available for the execution of the activities to be developed, such as: reports containing the number of employees per agencyt, career cadre, position and function, organizational charts, professional profiles, rules and regulations, human resources legislation and other normative acts, indicators extracted from the State database and other data to support demand projections, will also be made available to the consulting firm upon express request, at least 15 (fifteen) business days in advance. These inputs will be made available by the DRH/SEAP or by the human resources heads of the departments involved.
\nThose responsible for monitoring services will be available to align actions, methods and work techniques, adapting your demands to the products to be presented by the company.

\n\n

9.    EXECUTIVE GROUP RESPONSIBLE FOR MONITORING AND APPROVAL OF PRODUCTS

\n\n

The Executive Group will be formed by professionals from the Human Resources and Social Security Department of the State Secretariat for Administration and Social Security - DRH/SEAP, predominantly from the Human Resources Recruitment and Selection Division - DSRH, which is the unit responsible for centrally executing human resources management activities related to recruitment, selection, admission, assignment, and movement, as well as coordinating, guiding, and monitoring the sizing of the workforce. Employees from the advisory department and other DRH/SEAP units who have knowledge in the area of careers and remuneration may also join the Executive Group. Employees with experience in these activities will be designated to directly and continuously monitor the consultancy's work.
\nSpecifically, to execute Phase 5 (System/Solution Development), technicians to be appointed by the Paraná Information and Communication Technology Company – Celepar will be integrated into the Executive Group.

\n\n

10. KEY TEAM
\nThe key team of the Consultancy, responsible for the overall management of the project, which shall ensure the integration and compliance of the products while actively partici-pating in all stages, from the Work Plan, product development, training, and presenta-tion of results and proposals to the Client, to the system implementation, shall be com-posed of the following professionals, with minimum education and experience require-ments as follows:
\n(01) Specialist Consultant, who will act as Coordinator, with experience in Process Im-provement, having at least ten (10) years of proven practical experience in project man-agement, strategic planning project development, human resources management, and workforce sizing for public institutions (Autarchies and State Secretariats, Foundations). Degree and/or postgraduate studies in areas of knowledge related to the theme and products of the consultancy.
\n(03) Senior Consultants, with experience in Human Resources Administration or Peo-ple Management, having at least five (5) years of experience in Public Administra-tion/Management (Autarchies, State Secretariats, Foundations), complemented by expe-rience in Planning, Workforce Sizing and Management for public institutions (Autar-chies and State Secretariats, Foundations). Degree and/or postgraduate studies in areas of knowledge related to the theme and products of the consultancy.
\n(01) Specialist Consultant with experience in Information Technology, Systems Analy-sis, or related areas, having at least five (5) years of experience in systems analysis and software development for Public Administration/Management (Autarchies, State Secre-tariats, Foundations). Participation in at least three projects involving the processing and analysis of large datasets, with desirable experience in projects related to public sector human resources management. Proficiency in data visualization and analysis platforms (e.g., Power BI, Tableau, Qlik Sense, or similar). Proven experience in creating analytical models and preparing technical reports to support strategic decision-making.
\nDegree and/or postgraduate studies in Information Technology, Systems Analysis, Computer Science, or related areas. In addition to the specified technical knowledge, this consultant shall have communication skills and experience in technically leading multidisciplinary teams, considering that they will be one of the professionals responsi-ble for delivering the product specified in item 5.4.2.4.

\n\n

11. SUPPORT TEAM
\nAt the Contractor’s discretion, a support team may be constituted, composed of:
\na) Consultants with professional education and experience in Administration, People Management, or Public Management (Autarchies, State Secretariats, Foundations) to work on activities related to data collection, formulation of indicators and parameters, and support in product development;
\nb) Information Technology Consultants (Systems Analysis and Development), acting as Developers with experience in Information Technology, Systems Analysis, Computer Science, or related areas, related to software development with the characteristics of the intended software;
\nc) Senior Consultant acting as Project Manager, with experience in Strategic Planning, having at least five (5) years of experience in Public Administration/Management (Au-tarchies, State Secretariats, Foundations). Degree and/or postgraduate studies in areas of knowledge related to the theme and products of the consultancy. This consultant will perform project management functions, with experience in areas such as Project Man-agement, IT Management, or Innovation and Technology, leadership skills, administra-tion focused on team and process management, experience working on technology pro-jects, technical knowledge of tools and technologies used in projects (e.g., development platforms, servers, database systems, IT security), management of technology teams, knowledge of Development Methodologies in project management such as PMI and PMBOK, stakeholder management, and project management tools.

\n\n

 

\n\n

[1] Reference month January 2025.
\n[2] Average monthly number of layoffs from Feb/2024 to Jan/2025: retirements, dismissals, deaths and dismissals, excluding those occurring at universities.
\n[3] Calculation basis 113,600 effective servers – Ref. Jan/2025.
\n[4] Decree No. 10,313/2022.
\n[5] Operation summer.
\n[6] Law No. 19,776/2018; Decree No. 9879/2021.
\n[7] The following are considered as the Level of Action of the Organizational Structure (Law No. 21,352/2023) of the Agencies/Entities: Senior Management, Advisory, Management, Instrumental, Programmatic Execution, Regional.

\n\n

 

\n\n

ANNEX I - LIST OF AGENCIES/ENTITIES OF DIRECT ADMINISTRATION AND AUTONOMOUS AGENCIES OF THE STATE OF PARANÁ

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
NAME OF THE AGENCY/ENTITYACRONYM
AGÊNCIA DE ASSUNTOS METROPOLITANOS DO PARANÁAMEP
COLÉGIO ESTADUAL DO PARANÁCEP
CONTROLADORIA GERAL DO ESTADOCGE
INSTITUTO PARANAENSE DE DESENVOLVIMENTO ECONÔMICO E SOCIALIPARDES
INSTITUTO PARANAENSE DE DESENVOLVIMENTO EDUCACIONALFUNDEPAR
SECRETARIA DE ESTADO DA ADMINISTRAÇÃO E DA PREVIDÊNCIASEAP
SECRETARIA DE ESTADO DA EDUCAÇÃOSEED
SECRETARIA DE ESTADO DA JUSTIÇA E CIDADANIASEJU
SECRETARIA DE ESTADO DA SAÚDESESA
SECRETARIA DE ESTADO DO PLANEJAMENTOSEPL
SECRETARIA DE ESTADO DO TURISMOSETU
\n\n

Detailed information about the administrative structure of the State of Paraná can be accessed at: https://www.legislacao.pr.gov.br/legislacao/pesquisarAto.do?action=exibir&codAto=278128&indice=1&totalRegistros=1&dt=14.5.2023.18.6.24.361

\n\n

 

\n\n

 

\n\n

ANNEX II - NUMBER OF POSITIONS/FUNCTIONS PER CAREER CADRE

\n\n

TOTAL NUMBER OF POSITIONS AND FUNCTIONS, PROVIDED FOR IN LEGISLATION, BY CAREER/EMPLOYEE STRUCTURE – 2025 SUBJECT TO SIZING (EXCEPT THOSE EXTINCT OR EXTINCT WHEN BECOMING VACANCY)

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
CAREER CADRE/CAREERPOSITIONSFUNCTIONS
Executive Branch's Own Career Cadre – QPPE344
The State Health Department's own Career Cadre - QPSS237
Higher Education Institutions' Own Career Cadre - IEES214
Teaching Own Career Cadre - QPM12*
\n\n

Note: the number of positions and functions indicated refers to those provided for in legislation and with the possibility of entry. * The position of QPM Teacher does not include functions, however there are different responsibilities for teachers of the Matrix Curricular Components and for Pedagogues.

\n\n

IEES - Higher Education Institutions' Own Career Cadres - University Hospitals will be included in the Hospitals' sizing, therefore the University Technical career shall be considered, only for functions compatible with the hospital area.

\n\n

Detailed information about careers, functional career cadres, list of positions and functions by career/career cadres, salary tables and professional profile shall be accessed at: https://www.administracao.pr.gov.br/Recursos-Humanos

\n\n

 

\n\n

 

\n\n

ANNEX III - GUIDELINES AND REQUIREMENTS SPECIFICATION FOR SOFTWARE DEVELOPMENT
\n(PHASE 5 –5.5)

\n\n

In addition to the information described above and in order to clarify the main expectations and needs in relation to the aforementioned contracting, the following is a detailed breakdown of the specifications for Phase 5 - FORMULATION AND IMPLEMENTATION OF INFORMATION TECHNOLOGY SYSTEMATICS APPLIED TO WORKFORCE SIZING - DEVELOPMENT OF INFORMATION SYSTEM.
\nIt should be noted that the coordination of the product is under the responsibility of the State Secretariat for Administration and Social Security - SEAP, but with regard to technological aspects, the Companhia da Informação e Comunicação do Paraná - Celepar will also be responsible for accepting the product.
\nThe requirements set out in this document are not restrictive in nature, having only been carried out a preliminary survey of the needs and, for the effective implementation of the DIMFT System, the Contractor shall complement the survey and its modeling, mapping, descriptions and other pertinent documents and artifacts, in order to implement, through the Information System, the methodology established for the DIMFT.
\nThe Contractor shall implement a solution that fully meets the needs that gave rise to this acquisition, and any changes to be proposed shall be approved by SEAP and Celepar.
\n 
\n1.    SCOPE AND LIMITS OF THE PRODUCT
\n1.1.    GENERAL DEFINITIONS ABOUT SYSTEM PROJECT

\n\n

The scope of services of this Term of Reference for the elaboration of the Workforce Sizing System - DIMFT will involve, in general terms:
\n•    The definition of the Information System design based on the proposed methodology and its planned activities;
\n•    The Information System Project based on the established Conception, with the production of the artifacts defined in this document;
\n•    The implementation of the Information System, in line with the approach established for the project as a whole;
\n•    The transfer of the necessary knowledge for understanding and operating the system, as well as for the system’s transition to another institution, if required; The assisted operation of the System; and
\n•    Maintenance and technical support.

\n\n

The Project Plan for the development of the DIMFT System, as part of the overall Work Plan of the project, shall consider all the activities necessary for the planning, development, implementation and delivery of the DIMFT System in operation in the production environment of the Client and shall be presented by the Contractor with, at least, the following steps:
\n-    Systems Analysis, considering business modeling and related products that shall be validated by the SEAP business team and Celepar;
\n-    Software design, considering its architecture, interface and database;
\n-    System coding and testing, with the presentation of preliminary software versions for validation by SEAP and Celepar, to mitigate any risk resulting from the development process being misaligned with the project objectives;
\n-    Approval, with installation and configuration, by the Contractor of the system's operating environment accompanied by Celepar;
\n-    Approval, by SEAP and Celepar, of the integrated operation of the system modules and with external systems;
\n-    Loading of data required to start system operation;
\n-    Assisted operation of the system in production, with monitoring by the Contractor together with SEAP and Celepar;
\n-    Training to ensure technical capability and technology transfer of the new system; and
\n-    Maintenance and technical support.

\n\n

1.2.     PHYSICAL VIEW OF THE SYSTEM
\nThe physical view of the DIMFT System architecture shall enable integration with existing systems and service infrastructure, with adequate use of the infrastructure in the environment to be indicated by SEAP.
\nThe physical architecture of the DIMFT System will be developed and presented in the System Project Plan, after defining the technology to be used, respecting the established software definitions.
\nTo implement the physical architecture, the Contractor shall carry out, together with SEAP and Celepar, an analysis of the existing infrastructure with the aim of:
\n-    Obtain a detailed understanding of the software development architecture standards already existing at SEAP/Celepar regarding development standards, platform restrictions, and characteristics of the services to be integrated (components, webservices, database);
\n-    Obtain a detailed understanding of SEAP/Celepar database architecture standards, considering the current database and legacy databases, in favor of the development of new DIMFT System databases.
\n-    Use the physical infrastructure of Information and Communication Technology, which will be made available for the product, in order to develop the DIMFT System compatible with the SEAP/Celepar guidelines;
\n-    Support mechanisms for load balancing and failure control through the use of server clusters;
\n-    Have mechanisms to automatically detect and identify shutdowns or disconnections of integrated systems, generate logs, trigger alerts and send messages about the occurrence;
\n-    Provide system access security and data integrity mechanisms that are compatible and integrated with the technological security infrastructure provided by SEAP;
\n-    Provide data backup and recovery mechanisms compatible with the needs and characteristics of the system and integrated with the technological infrastructure provided by SEAP.
\n1.2.1     SEAP systems to be integrated
\nThe integrations indicated here may undergo changes and shall be reassessed and validated by the Client when developing the contracted solution.
\nThe main system used by SEAP and which will provide data and information to DIMFT is the Meta4 RH-Paraná System, which is a unified and proprietary Human Resources Management and Payroll system. SEAP manages this information, serving: Own Regime (rules defined by the State): effective employees of the Executive Branch, commissioned positions and Special Regime Contracts (CRES).
\nThrough Meta4, it is possible to manage human resources (through features) such as hiring, dismissal, promotions, in addition to maintaining the registration of organizations, bank accounts, positions, dependents, various historical data, reference value tables, import processes, etc. From the data resulting from HR management, it is possible to calculate the payroll according to the rules defined by SEAP.
\nIntegration with the Meta4 System or with other systems under the responsibility of SEAP and Public Administration agenciesof the government of the State of Paraná will be done through the use of APIs, with SEAP being responsible for developing the API for accessing the source data and the Contractor being responsible for developing the APIs necessary for data consumption by the DIMFT system.
\nAnother system in which there may be a need for integration, depending on the characteristics of the methodology to be applied, is SIAFIC - Integrated System for Planning, Execution and Fiscal Management, which operates financial, accounting and budgetary data from the Public Administration of the Government of the State of Paraná, and operates in the Celepar Data Center and was contracted with the company Logus Sistemas de Gestão Pública.

\n\n

2.    ACTIVITIES TO BE DEVELOPED

\n\n

Macro activities to be developed within the scope of the project will be presented below, as well as the subproducts to be delivered.

\n\n

2.1. SYSTEM PROJECT PLAN
\nThe System Project Plan shall describe in detail all service planning, methodology, stages and activities to be performed and respective responsibilities with their respective values, when relevant, meeting the objectives and technical specifications of this Term of Reference.
\nThe Contractor shall prepare the planning of the activities to be carried out in the development of this product, as a complementary part of the general Work Plan of the project, covering: (i) definition of the use of management tools; (ii) detailed schedule of the activities that will involve this product with their respective values; (iii) preparation of the responsibility matrix; (iv) definition of the structure of the documents to be prepared.

\n\n

The System Project Plan shall contain, at a minimum, the following items, in a manner consistent with what was defined in the project's general Work Plan:
\n•    Methodology for Executing Activities: technical description of the methodology to be applied in each process and production activities and the respective expected results;
\n•    List and Description of Activities: Project Breakdown Structure (WBS);
\n•    Physical and Financial Schedule for the Execution of Services: details of the physical and financial schedule with all activities to be developed and their respective costs and durations, compatible with the deadlines established by the Client, in a sequence that considers the precedence and dependency relationships between activities. The physical and financial schedule shall present the project milestones and define the dates and costs of the deliveries of intermediate and final products for each project activity;
\n•    Technical Team and Organization Chart: the Contractor shall present the allocated technical team and the organization chart defined for the project, containing the Responsibility Matrix and the functions to be performed by each technical lead identifying the management and coordination levels of each project activity;
\n•    Communication Plan: The Contractor, without prejudice to the provisions set forth in subitem 5.4.1, shall submit the Product Communication Plan containing descriptions of the types of relationships between the management, coordination and technical levels, and between those responsible for the product at the Contractor and the Client. It shall include the plan for monthly and extraordinary project monitoring meetings, and methods of recording the product (minutes, emails and other documents), constituting an integral part of the official product documentation and to be followed;
\n•    Quality and Risk Plan: The Contractor shall submit the Quality and Risk Management Plan containing a detailed description, by project activities, of the quality assurance and compliance process to be applied to the project products based on the Technical Specifications of this Terms of Reference. The Quality and Risk Management Plan shall include the Risk Matrix, including planned, corrective and predictive actions.

\n\n


\n2.2. DESIGN AND DEVELOPMENT 
\nThe Design and Development activity of the solution shall consider the phases, activities and tasks necessary for the design, development and implementation of the Information System, in accordance with the best practices of Information Technology - IT, including considering agile methodologies for software and systems development that will be presented in the System Project Plan and in the detailed schedule.
\nThe Design and Development activity shall consider the entire system specified in this Terms of Reference and shall cover activities such as: Business Process Modeling within the scope of the specified system; Systems Analysis and Design within the scope of the DIMFT System; Software Analysis and Design within the scope of the DIMFT System and the respective developments and implementation. The integration, qualification and transition procedures for the implementation of the contracted system are described in the following items.
\nAs previously described, the operating mode and methodology for executing the project, involving the Design and Development of the system, as well as the tasks that will comprise this activity shall be detailed in the System Project Plan to be delivered by the Contractor.
\n2.2.1. Business Process Modeling
\nAt this stage, the following activities shall be carried out: (i) Planning and Strategy for modeling the Information System based on the design of the DIMFT Methodology to be adopted; (ii) Mapping and Modeling of Processes resulting from the Personnel Sizing Methodology.
\nThe by-products to be generated in this stage are: (i) Personnel Sizing Process Mapping Document; (ii) DIMFT System Process Consolidation Document that will be part of the scope of the software solution.
\n2.2.2. Systems Analysis and Design 
\nIn this stage, the following activities should be carried out: (i) Description of the system's operating concepts; (ii) Specification of the system requirements, involving the identification and analysis of business processes proposed in the methodology; detailing of the logical and physical flows; (iii) Identification and description of the System's External Interfaces; (iv) System Design/Architecture involving the preparation of the system architecture project.
\nThe by-products to be generated in this stage are: (i) Description of Operating Concepts; (ii) Specification of System Requirements; (iii) Description of External System Interfaces; (iv) System Design/Architecture Document.
\n2.2.3. Software Analysis and Design
\nAt this stage of the product, at least the following activities shall be performed: (i) Specification of software requirements; (ii) Modeling and design of the database; (iii) WEB design of the interfaces, involving the specifications of the requirements of the software WEB interfaces; (iv) Software design, involving the preparation of the Software Design and the Specifications of the Internal Interfaces and integration with other systems; (v) Development of the DIMFT System Version. In a multiple iteration approach, it is expected that several cycles of versions of the DIMFT System and corresponding resulting processes will be generated.
\nThe by-products to be generated in this stage are: (i) Software Requirements Specification; (ii) System Software Design; (iii) Software Version Delivery.

\n\n

2.3. INTEGRATION AND QUALIFICATION
\nIntegration and Qualification activities involve the execution, by the Contractor, of the services necessary to integrate the DIMFT System with other SEAP systems and include the definition, preparation and execution of procedures and tests.
\nThis activity will be supported by SEAP in order to guarantee the exchange of information with user agencies or information providers to the DIMFT System, to avoid delays in the development of the project due to the failure to provide the necessary data and information.
\nAfter the software development is completed, software verification and validation tests will be carried out, with the aim of ensuring that the integrated software meets the previously defined system requirements and the needs of SEAP.
\nThe testing procedures defined in the System Test Plan shall be executed, using the Contractor's approval environment (Development Environment) and, subsequently, final acceptance tests of the software shall be carried out in the approval environment and final implementation in the production environment defined by SEAP.
\nThe following activities shall be carried out (for all modules that make up the System): (i) Preparation and provision of test plans for each module, involving unit, information security, usability, performance and integration tests; (ii) Preparation of test procedures; (iii) Execution of test procedures; (iv) Execution of the following tests: information security, contingency and backup and restore of the environment.

\n\n

2.3.1. Preparation of the System Test Plan
\nSystem testing aims to verify the correct functioning of the system in relation to its functional and non-functional requirements. Before executing the tests, a Test Plan shall be prepared to guide the execution of the tests, meeting all the functionalities of the developed software and its integrations.
\nThe Test Plan shall include descriptions of the tests to be performed, the traceability of the test cases with the system requirements, with the software requirements and respective use cases.
\nThe Test Plan shall describe and establish the test environments, that is, preparation for carrying out the tests considering hardware, software, database, initial data load and information from the Contractor's development environments, as well as SEAP approval and production environments.
\nThe by-product to be generated at this stage for each of the modules that make up the DIMFT System is the document: (i) System Test Plan.

\n\n

2.3.2. Testing Procedures
\nThis product activity refers to the preparation of the set of test procedures for each module of the DIMFT System. The inspection script and test procedures to be performed on the developed modules shall be presented.
\nThe by-product to be generated at this stage for each of the modules that make up the System is the document: (i) System Testing Procedure.

\n\n

2.3.3. Acceptance Tests – Approval Environment
\nAcceptance tests shall be carried out in the approval environment of all modules of the DIMFT System, which will aim to evaluate the results of the modules developed and the way in which the tests are conducted.
\nThe by-product to be generated in this stage for each of the modules that make up the System is the document: (i) Report on the Results of Acceptance Tests in the System approval Environment.

\n\n

2.3.4. Acceptance Testing – Production Environment
\nAcceptance tests shall be carried out in the SEAP production environment, after completion of the approval tests.
\nPreparation for production deployment should cover: (i) Specific requirements related to and the desired infrastructure during the deployment process, considering gradual deployment; (ii) Provision of configuration files necessary for the correct functioning of the systems; (iii) Technical documentation of the necessary environment, considering the configurations planned for gradual deployment of the system; (iv) Ways of monitoring performance of the production environment.
\nThe by-product to be generated in this stage for each of the modules that make up the DIMFT System is the document: Report on the Results of Acceptance Tests in the System's Production Environment, which shall be delivered with the Information System Software Version.

\n\n

2.4.     TRANSITION
\nThe Product Transition activity refers to the set of services to be performed for the DIMFT System modules, relating to Assisted Operation and Technical Support, Training and Data Migration, as well as the preparation of system Documentation.
\nIt is emphasized that the definitions and detailed description of the activities related to the Training are provided in Phase 4 – Capacity Building.

\n\n

2.4.1.     Assisted Operation
\nThe Contractor shall perform the Assisted Operation for users of the DIMFT System, which shall last 60 (sixty) business days after the approval and implementation of the Information System. This stage shall be carried out at the end of the development of each module and may occur in different periods for each module.
\nAssisted operation refers to the support services to be performed in the DIMFT System by the Contractor, during the period specified above, to technically support users on the use of the system and correct any failures in the functionalities of the modules implemented in order to guarantee the system and include: (i) Clarifying user doubts related to the use of the system functionalities; (ii) Detecting and recording actual or potential nonconformities in the technological solution; (iii) Performing analyses on the need for system maintenance; (iv) Detecting and guiding the correction of programs, products and functionalities of the system or of the methodology implemented by the system; (v) Performing periodic monitoring of users with the objective of detecting any inappropriate use of the system, helping to prevent future problems and identifying other needs, such as corrections and new training for users; (vi) Performing other related activities to support users.
\nThe objective of these services is to provide greater productivity to users regarding the use of the solution's resources, as well as to maintain effective control of the problems presented, aiming at the perfect functioning, use, security and integrity of the solution.
\nServices shall be performed during business hours (from 9:00 a.m. to 6:00 p.m., Monday to Friday) using teleconferencing tools, when applicable. When in person, at the SEAP headquarters, or at the agencies that are part of the work.
\nTo carry out this activity, SEAP will provide professionals from its staff to monitor, record occurrences and accept the services and technical solutions proposed, as well as the infrastructure necessary for the development of this activity, including telephone, furniture and Internet access.
\nThe by-products to be generated in this stage are: (i) Assisted Operation Plan; (ii) Report on results of the assisted operation.
\n2.4.2. Data Integration
\nSEAP has systems, databases and spreadsheets with registered information. In this sense, the Contractor shall analyze the data and information to prepare the Integration Plan of the existing data for the system platform, according to the data structure and the data model applied in the DIMFT System. All data existing in the various institutions shall be considered, and the Contractor is responsible for collecting the data for analysis in the various locations, and SEAP and other State Public Administration agencies are responsible for providing the data.
\nIntegrations with other Information Systems, within the scope of State Public Administration institutions and which are of a continuous nature, should be carried out, preferably, through the use of APIs, with SEAP being responsible for authorizing the use of APIs to access the systems to be integrated and the Contractor being responsible for developing the APIs that are part of the DIMFT system.
\nSingle or sporadic data uploads may be made by generating files, under the responsibility of SEAP, when the data are part of the institutions of the State Public Administration, and under the guidance of the Contractor. If the methodology to be applied depends on access to data available in public databases external to the Public Administration of the State of Paraná, it will be the responsibility of the Contractor to identify and capture the data in their respective sources.
\nIn situations that require data cleansing to make the data from their sources compatible with the information system, the Contractor will be responsible for carrying out this work, with support from SEAP to clarify the contents of the source data.
\nThe Contractor will be responsible for operationalizing the Integration Plan and will present a by-product to be generated at this stage: (i) Integration Plan.

\n\n


\n2.5.    SOURCE CODE
\nThe Contractor  shall provide the source codes developed to support the solution, the data model, the development component packages together with their APIs (Application Program Interface) and third-party tools required to structure the solution's development and operation environment. These artifacts shall be delivered every month, according to the execution schedule and, at the end of the contract term, in the updated version. The tools to be proposed should preferably be those in use at Celepar 's Data Center. If a tool is proposed that does not fit this situation, its use shall be previously approved by the Client The Contractor shall provide the software components complementary to the developed software (e.g., Artificial Intelligence, data analysis or Business Intelligence tools). For dimensioning purposes, up to 32 nominated users who may use these tools shall be considered. Any software licenses complementary to the developed products shall be valid and updated at least until the termination of the contract.

\n\n


\n2.6.    DOCUMENTATION
\nThe Contractor shall document all meetings held on the product through meeting minutes, containing the information exchanged and the decisions taken and the actions to be carried out by the parties, in accordance with the Communication Plan contained in the Work Plan. Any meetings held by teleconference shall, whenever requested, be recorded and kept in the documentation collection.
\nIn addition to the record of meetings and management actions of the product, the Contractor shall provide the Project Documentation, in all its phases, stages and the System Documentation, in accordance with best practices and standards, including the Data Dictionary with all due descriptions, System Operation Manual, User Operation Manual and System Installation Manual.
\nThe manuals shall be prepared incorporating all the system's functionalities, adopting clear and objective writing, at the same time simple and easy to understand, avoiding, whenever possible, especially in the User Operation manual, complex technical terms.
\nThe Contractor shall define and document the technical characteristics of the environment, covering the description of all the infrastructure necessary for the operation of the DIMFT System, comprising the server environment and the user workstations, including: (i) Technical characteristics of the environment - description of all the infrastructure necessary for the operation of the process, comprising the server environment and the user workstations; (ii) Storage, backup and recovery policies; and (iii) Description of the operational environment - hardware and software that make the operation of the system possible.
\nThe by-products to be generated in this stage for each of the modules that make up the DIMFT System are: (i) Data Dictionary;(ii) System Operation Manual;(iii) User Operation Manual;(iv) System Installation Manual.

\n\n


\n2.7.    TRANSFER OF TECHNOLOGY
\nThe technology transfer aims to promote the transfer of knowledge acquired and developed during the project and includes the results of the services and developments carried out in the preparation of the system during the period of its execution, to the technical team indicated by the Client, which will include Celepar technicians.
\nThe Contractor shall, during the execution of the project, provide the Client with: (i) Supply of all technical documentation of the systems with all their components, as well as additional information produced for use by the Client in the interest of the product; (ii) Support of the implementation of the DIMFT System product, by process managers and technicians indicated by the Client; (iii) Monitoring and support in the installation and maintenance of the products with the Client's technology team; (iv) Delivery of all documentation of the artifacts generated for the DIMFT System; (v) Inclusion of practical development activities (workshop and simulation) in the scheduled courses, to internalize the theoretical knowledge obtained.

\n\n

2.8.    APPROVAL OF THE INTEGRATED ENVIRONMENT
\nAs established as a system requirement, there is a need to integrate the DIMFT System with systems and data from various institutions within the state.
\nIntegration with the RH-Parana/Meta4 System is one of the main ones and, in addition to sharing data on public servants, positions and salaries, involves the integration of the workflow of processes.
\nAfter implementing all modules of the DIMFT System, the Contractor  shall have all planned integration functionalities approved, proving the integration between the developed modules and those existing systems for which integration is planned.
\nTo do this, the Conctractor team, shall be coordinated and work together with the team defined by the Client and and by Celepar to identify and correct possible failures in order to ensure that all integrations work as planned in the DIMFT System production environment.
\nA technician from the Client will monitor the approval process for the integrated environment.

\n\n


\n2.9.    MAINTENANCE AND TECHNICAL SUPPORT
\nThe Contractor shall prepare a Maintenance and Technical Support Plan with the procedures to be adopted for the continuity of the DIMFT in the production environment. This Maintenance and Technical Support Plan shall be executed in the event of failures or defects in the DIMFT software, upon request by the Client.
\nDuring the maintenance period, the Contractor  shall respond to calls received from the Client to resolve potential problems related to maintaining the correct functioning of the DIMFT System. The specific Maintenance and Technical Support service shall focus on corrective maintenance. On the other hand, if evolutionary maintenance that is relevant to DIMFT is identified, this will be handled through requirements and change management.
\nThe requested technical support service may be provided locally or remotely. Remote service may be provided by email or through the 0800-call center provided by the Contractor. Cases that require local service and that require time for the technician to be mobilized to the Contractor's facilities shall be handled and agreed upon between the Client and the Contractor.
\nThis communication channel shall allow, at a minimum, the recording of the following information:
\na)    Opening hours;
\nb)    Degree of severity and description of the occurrence;
\nc)    Time of first return by the Contractor;
\nd)    Start time of the contractor's work for the technical solution;
\ne)    Communication, by the Contractor, of the completion of work to resolve the situation;
\nf)    Client’s assessment of the completion of the technical solution;
\ng)    For the purposes of controlling service deadlines, the technical call will be considered resolved/completed at the time the Contractor communicates the completion of the work, provided that the Client's assessment is positive, even if it occurs later.
\nThe degree of severity will determine the priority of service according to the impact resulting from the incident as recorded in the following table which represents the established Service Level Agreement (SLA).
\nThe verification of indicators and the assessment of compliance with established goals will be carried out through the receipt of monthly reports, generated through a computerized system connected to the service platform made available by the Contractor.

\n\n

 

\n\n

Incident Handling Table

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Severity

\n\t\t\t		\n\t\t\t

Impact

\n\t\t\t		\n\t\t\t

TR - Response Time

\n\t\t\t		\n\t\t\t

TS - Solution Time

\n\t\t\t		\n\t\t\t

Treatment Regimen

\n\t\t\t
\n\t\t\t

High

\n\t\t\t		\n\t\t\t

Total Unavailability: operational incident that causes the total interruption of the service for users

\n\t\t\t		\n\t\t\t

4 hours

\n\t\t\t		\n\t\t\t

8 hours

\n\t\t\t		\n\t\t\t

Commercial

\n\t\t\t
\n\t\t\t

Average

\n\t\t\t		\n\t\t\t

Partial Unavailability: operational incident that causes the interruption of one or more functionalities for service users

\n\t\t\t		\n\t\t\t

6 hours

\n\t\t\t		\n\t\t\t

12 hours

\n\t\t\t		\n\t\t\t

Commercial

\n\t\t\t
\n\t\t\t

Low

\n\t\t\t		\n\t\t\t

Slowness, reduced performance or operational incident that impacts a functionality of the solution

\n\t\t\t		\n\t\t\t

8 hours

\n\t\t\t		\n\t\t\t

40 hours

\n\t\t\t		\n\t\t\t

Commercial

\n\t\t\t
\n\n

Upon justification and provided that it is accepted by SEAP, the established deadlines may be extended or temporary workaround solutions may be adopted.
\nThe Contractor's actions in the event of incidents and requests recorded by the Client will comply with service levels in accordance with the impact resulting from the severity of the incidents and in accordance with the established service provision schedules.
\nThe service deadline for incidents and requests will start from the registration of the request, within the Treatment Regime hours, or from the first hour of the next service cycle to be initiated.
\nFor the purpose of initiating technical action activities on the incident, the record in the incident management tool will be considered, which will also be used to note the resumption of normal services or additional actions that may be necessary to resolve any problem that caused the incident.
\nIf the incident originates from software and hardware components that depend on third-party interventions, this information shall be recorded, as well as the steps being taken and the prospect of normalization.
\nWhile the incident call or request is under the responsibility of the Client, the counting of the time of action will be paused, resuming when it is under the responsibility of the Contractor.
\nThe incident will be considered closed, for ANS accounting purposes, when service availability is reestablished under the terms defined for Severity Levels and ANS, regardless of the recording of the action and closing of the respective call.
\nWhen opening multiple incidents related to the same source, they will be referenced by the first one.

\n\n


\n2.10.    SYSTEM OPERATION INFRASTRUCTURE SPECIFICATION
\nThe DIMFT System shall be a system entirely built to be accessed via a WEB platform, and may be accessed from the Internet, via the State's corporate network or externally. The provision of a suitable network link for access to the system and for the system to be used via an Internet browser shall be the responsibility of the Client.
\nThe Client will be responsible for the fundamental items for the system to function in a WEB environment, namely: Internet link on the corporate network; Secure environment; Corporate network infrastructure; Hosting of processing units (physical and logical), managed by operating systems, as well as the installation of a set of other applications, routines or systems (software) that will perform specific activities, installed and configured in a personalized manner and other infrastructure items necessary for the operation of the development, approval and production environments, according to standards defined for the system hosting environment in the Celepar Data Center.
\nAll hardware, software and network infrastructure described above as fundamental items for the implementation of the DIMFT System will be the responsibility of the Client, and the Contractor may only support its dimensioning. The Contractor undertakes to provide additional software licenses to the environment defined in the Celepar Data Center and which are necessary for structuring the development and operation environment  the DIMFT system.
\nAs previously mentioned, the systems will be installed in Celepar's Data Center, in the environment that serves SEAP. The available infrastructure consists of high-performance servers with large storage capacity, which are hosted in Celepar's Data Center that serves the Government of the State of Paraná.
\nCelepar's current production environment is described in Item 5 of ANNEX III of this document.

\n\n

2.11.    PREPARATION OF DEVELOPMENT, APPROVAL AND PRODUCTION ENVIRONMENTS
\nThe Contractor will be responsible for the installation, documentation and configuration of the DIMFT System in the development environments and in the approval and production environments to be made available by the Client, in order to allow its perfect functioning and compliance with the specified technical requirements.
\nThe DIMFT System will be developed in the Contractor's development environment, which shall provide, at its own expense, all hardware and software infrastructure, as well as the physical resources necessary to provide the contracted services.
\nThe Contractor  shall install and configure the approval and production environments indicated by the Client.
\nThe infrastructure of the approval environment shall be adequate to meet the needs of the approval process, and may adopt hardware with a lower capacity than that provided for the production environment, but including the same configurations as the production environment.
\nRequirements for deployment into production shall include a final code audit to verify the use of good programming practices and system security verification tests, including intrusion tests.
\nThe services described above shall be performed by the Contractor's technicians, accompanied by technicians appointed by the Client, and at the end of this process, the systems shall be implemented and in operation, configured, stable and operational, duly approved by Celepar.
\nThe Contractor shall observe the security standards, norms and rules in use in the Client´s technological environments.
\nAny need for adjustments or changes arising from specific characteristics and requirements shall be discussed in advance with the Client's technicians.
\nThe Contractor shall submit the complete technological solution to be approved by the Client with support from Celepar.

\n\n

3.    PRODUCTS, EXPECTED RESULTS, FORM OF PRESENTATION AND ACCEPTANCE OF SERVICES
\n3.1.    PRODUCTS AND BY-PRODUCTS TO BE SUPPLIED
\nThe products and by-products to be provided under this Term of Reference are the software engineering artifacts required for system operation and future transition, resulting from the project's macro activities, as well as monitoring reports on project management activities, assisted operation and technical support.
\nThe products related to the activities that make up each macroactivity, intermediate products to the deliveries defined in the table below, shall be detailed in the System Project Plan, as well as the distribution of these deliveries in the months of the project, in accordance with the Physical and Financial Schedule of Activities presented in the System Project Plan.
\nThe following table shows the deliveries expected throughout the project, defining the products/by-products. For the disbursement to be made, all subproducts related to the delivery shall be approved by the Client through the acceptance term.

\n\n

Products, subproducts/activities distributed throughout the information system project

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\n
PRODUCT NAME BY-PRODUCT/ACTIVITIES
System Project  Plan
Personnel Sizing Process Mapping Document;
DIMFT System Process Consolidation Document that will be part of the scope of the software solution
Description of System Operation Concepts
System Requirements Specification
Description of the System's External Interfaces
System Design/Architecture Document
Software Requirements Specification
System Software Design
Software Version Delivery
System Test Plan
System Testing Procedure
Report on the Results of Acceptance Tests in the System Approval Environment 
Report on the Results of Acceptance Tests in the System Production Environment that shall be delivered with the Information System Software Version
Assisted Operation Plan
Assisted Operation Results Report
Integration Plan
Source code, data model, APIs and third-party tools
Data dictionary
System Operation Manual
User Operation Manual
System Installation Manual
Provision of all technical documentation of the systems with all their components, as well as additional information produced for use by the Client in the interest of the product
Monitoring of the implementation of the DIMFT System product, by process managers and technicians indicated by the Client.
Monitoring and support in the installation and maintenance of products together with the Client's technology team
Delivery of all documentation of the artifacts generated for the DIMFT System
Inclusion of practical development activities (workshop and simulation) in the scheduled courses, to internalize the theoretical knowledge obtained
Integration functions tested and working
Technical support services, in accordance with the established service level
System Operation Infrastructure Specified in accordance with the standards adopted in the Data Center defined by the Client
Ready-to-use Development, Homologation and Production Environments
\n\n

The schedule presented, as well as the description of the by-products/activities, is a forecast for analysis by the Contractor, who may present changes in its proposal for evaluation by SEAP and Celepar.

\n\n


\n3.2.    FORM OF PRESENTATION AND ACCEPTANCE OF PRODUCTS
\nAll products resulting from activities that are part of the scope of Phase 5 of this Term of Reference shall be presented in digital format and, in specific cases, in accordance with the following compliance:
\n•    01 (one) digital copy of the DIMFT System software, in version 1.0 approved by the Client. For each new version produced, the Contractor shall deliver a new copy after approval, until the final version of the implemented software is delivered;
\n•    Operation Manual in digital media;
\n•    System Manual and System Installation Manual in digital format;
\n•    Project reports, in digital format, generated monthly, with the appropriate document identification and numbering, according to the standard proposed by the Contractor;
\n•    Final product report, in digital format, including all product documents, in an orderly, referenced and organized manner, according to the standard proposed by the Contractor.

\n\n

The Contractor shall present, in the System Project Plan, the standard and model for structuring, referencing and organizing the product documents, which shall be analyzed and approved by the Client. This will be the standard to be followed when delivering related products (Product Documents and Product Reports).
\nAll generated artifacts, reports and documents cited shall be delivered in digital format, with the digital format being 1 (one) copy in .pdf and 1 (one) copy in editable format (word, for example).
\nSEAP will issue a Provisional Receipt Term for each stage delivered by the Contractor.
\nSEAP together with Celepar will have a maximum period of 15 (fifteen) business days, respecting the minimum period of 5 (five) business days, to assess whether the products delivered are in accordance with the specifications of this Term of Reference, with the aim of APPROVING (ACCEPT) or REJECTING the products delivered. This period shall be considered in the Project Plan. Failure by SEAP to respond within these periods will imply tacit acceptance of the delivered artifacts.
\nIf the products of a delivery are REJECTED, the Contractor shall, after notification from SEAP, make the necessary and requested adjustments, based on the technical specifications of the products, contained in this Term of Reference, within 10 days, counted from the date of receipt of the formalization of the rejection issued by the Client.
\nThe Final Receipt and Approval of Products Term, through the product acceptance term, relating to each delivery will be issued after compliance assessment and confirmation that the artifacts comply with the technical specifications established in this Term of Reference and in the System Project Plan.
\nThe Rejection Term will be issued when there are technical errors or improprieties or failure to meet technical specifications that are characterized as impediments to receiving the artifacts, quality defects or failure to observe the standards and best practices for project development.
\nAPPROVAL or ACCEPTANCE of products by SEAP and Celepar, where applicable, does not exempt the CONTRACTOR from responsibility for correcting errors identified within the warranty period defined for the project.

\n\n


\n3.3.    PLACE OF SERVICE PERFORMANCE
\nThe services shall be performed at the Contractor's facilities, which shall provide, at its own expense, all hardware and software infrastructure as well as the physical resources necessary to perform the contracted services.
\nInteractions with SEAP professionals, necessary for the execution of services, will take place in Curitiba - PR, and the Contractor will be responsible for the displacement of professionals involved in the provision of services when necessary. Meetings may be held remotely, via teleconference, when possible and authorized by the Client.
\nThe Contractor shall necessarily connect to the Celepar network, duly authorized by SEAP, to use the Celepar technological infrastructure environment, mainly for configuration and technical support activities related to the approval and operation services of the Information System in the Celepar Data Center environment. To this end, all security and access standards for systems and environments defined by Celepar shall be followed.
\nThe technological infrastructure required to provide the contracted service, including: hardware, software and physical and logical connections of the CONTRACTOR's development environment, shall be in operation within a maximum period of 60 (sixty) days from the signing of the contract, at which time it may be subject to inspection by Celepar/SEAP.

\n\n

4.    TECHNOLOGICAL PARTNER
\nCelepar is the company responsible for maintaining the Information and Communication Technology (ICT) infrastructure in the State of Paraná and providing related services. It is responsible for defining the software platforms adopted by the State of Paraná, as well as maintaining the physical network, providing corporate systems and network security.
\nSEAP does not have a physical structure or ICT technical team to maintain systems and data centers, and hosts its systems on servers at Celepar, through contracts with the company.
\nThe DIMFT System will be installed in a production environment at Celepar's data center and shall follow platform definitions and restrictions, in addition to security protocols.
\nAfter the end of the development and technical support contract, SEAP will define the institution that will be responsible for the development of the systems. To this end, one or more technicians will be designated to monitor all phases of the project, including training and technology transfer.
\nFurthermore, a large part of the State's legacy systems and corporate systems, which shall be considered in the integration with the new systems, are also under the responsibility of Celepar or in operation in the company's Data Center.
\nTherefore, all information contained in this Term of Reference related to the Client with regard to technological aspects will include its partner Celepar – Companhia de Tecnologia da Informação e Comunicação do Paraná, located at Rua Mateus Leme, 1561 – Centro Cívico – CEP 80.530-010 – Curitiba/PR.

\n\n

5.    CELEPAR PRODUCTION ENVIRONMENT 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Database

\n\t\t\t
\n\t\t\t

Software

\n\t\t\t		\n\t\t\t

Version

\n\t\t\t
\n\t\t\t

PostgreSQL

\n\t\t\t		\n\t\t\t

10.1

\n\t\t\t
\n\t\t\t

Oracle

\n\t\t\t		\n\t\t\t

11G R2 and 12C (check license availability)

\n\t\t\t
\n\t\t\t

Platforms for Development

\n\t\t\t
\n\t\t\t

Software

\n\t\t\t		\n\t\t\t

Version

\n\t\t\t
\n\t\t\t

Java Web

\n\t\t\t		\n\t\t\t

1.7 or higher

\n\t\t\t
\n\t\t\t

Light PHP

\n\t\t\t		\n\t\t\t

5.5.11 or higher

\n\t\t\t
\n\t\t\t

Application Servers

\n\t\t\t
\n\t\t\t

Software

\n\t\t\t		\n\t\t\t

Version

\n\t\t\t
\n\t\t\t

JBoss

\n\t\t\t		\n\t\t\t

WildFly 10.x (for new applications)

\n\t\t\t
\n\t\t\t

Apache

\n\t\t\t		\n\t\t\t

No version restriction - latest available on the operating system

\n\t\t\t
\n\t\t\t

Version Control Systems

\n\t\t\t
\n\t\t\t

Software

\n\t\t\t		\n\t\t\t

Version

\n\t\t\t
\n\t\t\t

CVS or SVN

\n\t\t\t		\n\t\t\t

Use the version available in the Celepar corporate environment

\n\t\t\t
\n\t\t\t

Application Publishing Systems

\n\t\t\t
\n\t\t\t

Software

\n\t\t\t		\n\t\t\t

Version

\n\t\t\t
\n\t\t\t

Shipyard

\n\t\t\t		\n\t\t\t

Use the version available in the Celepar corporate environment

\n\t\t\t
\n\t\t\t

Jenkins

\n\t\t\t		\n\t\t\t

Use the version available in the Celepar corporate environment

\n\t\t\t
\n\t\t\t

Systems for Library Managers

\n\t\t\t
\n\t\t\t

Software

\n\t\t\t		\n\t\t\t

Version

\n\t\t\t
\n\t\t\t

Composer

\n\t\t\t		\n\t\t\t

Use the version available in the Celepar corporate environment

\n\t\t\t
\n\t\t\t

Maven

\n\t\t\t		\n\t\t\t

Use the version available in the Celepar corporate environment

\n\t\t\t
\n\t\t\t

Security Systems

\n\t\t\t
\n\t\t\t

Software

\n\t\t\t		\n\t\t\t

Version

\n\t\t\t
\n\t\t\t

IDDigital

\n\t\t\t		\n\t\t\t

Use the version available in the Celepar corporate environment

\n\t\t\t
\n\t\t\t

Security Center

\n\t\t\t		\n\t\t\t

Use the version available in the Celepar corporate environment

\n\t\t\t
\n\t\t\t

Server Operating Systems

\n\t\t\t
\n\t\t\t

Software

\n\t\t\t		\n\t\t\t

Version

\n\t\t\t
\n\t\t\t

Linux

\n\t\t\t		\n\t\t\t

SLES 12 sp1 or sp3 (constantly evolving)

\n\n\t\t\t

CentOS and Debian distributions

\n\t\t\t
\n\t\t\t

Windows

\n\t\t\t		\n\t\t\t

2012 R2 (we have already developed the 2016 template, and this should be adopted in the next servers)

\n\n\t\t\t

Legacy - numerous versions (2000, 2003, 2008, 2008R2, etc...)

\n\t\t\t
\n\t\t\t

Systems for Virtualization

\n\t\t\t
\n\t\t\t

Software

\n\t\t\t		\n\t\t\t

Version

\n\t\t\t
\n\t\t\t

VMware

\n\t\t\t		\n\t\t\t

vSphere 6

\n\t\t\t
\n\t\t\t

Authoritative Bases

\n\t\t\t
\n\t\t\t

Software

\n\t\t\t		\n\t\t\t

Version

\n\t\t\t
\n\t\t\t

OpenLDAP (Expresso)

\n\t\t\t		\n\t\t\t

Use the version available in the Celepar corporate environment

\n\t\t\t
\n\t\t\t

AD – Active Directory

\n\t\t\t		\n\t\t\t

Use the version available in the Celepar corporate environment

\n\t\t\t
\n\t\t\t

IDDigital

\n\t\t\t		\n\t\t\t

Use the version available in the Celepar corporate environment

\n\t\t\t
\n\n

 

\n\n

ANNEX IV
\nList of Requirements for the DIMFT Information System 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
ITEM\n\t\t\t

DESCRIPTION

\n\t\t\t
1.\n\t\t\t

NON-FUNCTIONAL REQUIREMENTS

\n\t\t\t
\n\t\t\t

1.1.

\n\t\t\t		\n\t\t\t

The authentication of system users shall be done in an integrated manner with the Security Center used in the corporate environment of the State of Paraná.

\n\t\t\t
1.2.\n\t\t\t

The system's parameterization in its various modalities, such as report formatting, use of parameters for indicators (for example, open or closed regime, function), restrictions, establishment of calculation formulas or other situations that require adaptations for use of the proposed methodology shall be designed for creation and updating by system users, without the need for changes to the program code.

\n\t\t\t
1.3.\n\t\t\t

The system shall allow the creation of access profiles to its functionalities, with administration directly by its users.

\n\t\t\t
1.4.\n\t\t\t

Considering the diversity of users of the system, with different functions, its usability shall include accessibility aspects and the interface shall be compatible with the operations to be performed, according to the user profiles, being totally intuitive for operational activities and with information and guidance provided directly by the system for more complex functions that require user expertise, such as system parameterization, sizing calculations and information analysis.

\n\t\t\t
1.5.\n\t\t\t

Access to the DIMFT System functionalities will be provided, at least, through the following WEB browsers: Microsoft Edge, Firefox, Safari and Chrome, in their most recent versions, in an infrastructure and operating software that will be provided by SEAP, as stated in item 2.10 (System Operating Infrastructure Specification).

\n\t\t\t
1.6.\n\t\t\t

Integrations with other Information Systems, within the scope of State Public Administration institutions and which are of a continuous nature, should be carried out, preferably, through the use of APIs, with SEAP being responsible for authorizing the use of APIs to access the systems to be integrated and the Contractor being responsible for developing the APIs that are part of the DIMFT system.

\n\t\t\t
1.7.\n\t\t\t

The DIMFT System shall include the creation of APIs that allow the exposure of data generated by the system to be accessed by other systems of interest to the State Public Administration. In specific situations, the system data may also be exported in file exchange formats.

\n\t\t\t
1.8.\n\t\t\t

The DIMFT System shall be developed within the scope of this Term of Reference using a development platform in accordance with environments approved for the Celepar Data Center, as stated in item 2.10 (System Operation Infrastructure Specification).

\n\t\t\t
1.9.\n\t\t\t

The Database Management System to be used in the system shall be PostgreSQL, unless another proposal is approved by the Client, provided that the state's interest is proven.

\n\t\t\t
1.10.\n\t\t\t

The System should consider the adoption of specialized tools that can be integrated with the core to be developed, in order to enable data analysis, scenario generation, report and dashboard generation, application of Artificial Intelligence and other facilities compatible with the functional requirements employed. The tools to be proposed should preferably be those in use at Celepar's Data Center. If a tool is proposed that does not fit this situation, its use shall be previously approved by the Client. In the case of proposing these specialized tools, the established licensing rules shall be complied with.

\n\t\t\t
2.\n\t\t\t

GENERAL REQUIREMENTS

\n\t\t\t
2.1.\n\t\t\t

The products to be developed within the scope of the project shall cover all the Agencies/Entities covered (Annex I), careers/career cadres with respective positions/functions, which have not been declared extinct upon becoming vacant (Annex II). It should be noted that possible changes in the organizational structure and/or careers/career cadres due to new state management guidelines implemented after the publication of this Term shall be considered and incorporated. Consider the updated version of Annexes I and II at the time of the contract. (Item 4)

\n\t\t\t
2.2.\n\t\t\t

The System shall be capable of including a methodological proposal, including data collection and parameter definition, which includes the establishment of stratified and statistically representative samples in each area, agency or career cadre, provided that there is a high degree of standardization of processes. (Item 4.2.4)

\n\t\t\t
2.3.\n\t\t\t

The system shall be capable of maintaining versions produced in the functional dimensions performed, including the data used for dimensioning, enabling comparison of the results obtained in each of the versions.

\n\t\t\t
3.\n\t\t\t

CURRENT SITUATION SURVEY (5.2.1)

\n\n\t\t\t

The System shall provide functionalities for data capture through integration with other systems, manual input, and asynchronous data loading to store the information resulting from the current situation survey, in accordance with Annexes I and II. It shall  also be capable of including other institutions and career paths, and shall address the following aspects — or others, should there be changes in the proposed reference model:

\n\t\t\t
3.1.\n\t\t\t

Survey and analysis of the current workforce in agencies/entities: quantity by type of employment relationship, carreer cadre, position/function and unit, with emphasis on the activities performed. (Item 5.2.1.1.1.)

\n\t\t\t
3.2.\n\t\t\t

Survey, identification and analysis of the organizational structure of all Agencies/Entities that make up the Direct Administration and Autonomous Agencies, according to the level of activity of the organizational structure, covering regional structures. (Item 5.2.1.1.2.)

\n\t\t\t
3.3.\n\t\t\t

Survey of legally established competencies, competencies intrinsic to the execution of the public service, and organizational goals of the Agencies/Entities subject to the dimensioning to be carried out according to the levels of action of their organizational structure, covering regional structures. (Item 5.2.1.1.3.)

\n\t\t\t
3.4.\n\t\t\t

Survey and analysis of available productivity data, individually and comparatively, in the case of units that have a similar service profile, providing, when possible, indicators for the subsequent preparation of action plans to improve productivity (for example, employee training plan, process standardization, automation of activities, need to improve technological conditions etc.). (Item 5.2.1.1.4.)

\n\t\t\t
3.5.\n\t\t\t

Collection of information regarding turnover, absenteeism, absences, seasonal demand, pent-up demand, overestimated demand, deviations from function and their impacts on performance and productivity, as well as on the state public budget. (Item 5.2.1.1.5)

\n\t\t\t
3.6.\n\t\t\t

Mapping of existing jobs in agencies/entities, by type: in-person, hybrid and teleworking, with a breakdown of the levels of operational units in their organizational structure. (Item 5.2.1.1.6)

\n\t\t\t
3.7.\n\t\t\t

Identification of the strategic role played by the areas of the State and vision of the future, taking into account social and economic changes, in work and social security regimes, technological and work processes innovations, and respective impacts on the demand for the workforce, qualitatively and quantitatively. (Item 5.2.1.1.7)

\n\t\t\t
3.8.\n\t\t\t

Identification and analysis of priority demands, repressed demands, difficulties, distortions, critical issues, good management practices that resulted in increased productivity, among others. (Item 5.2.1.1.8)

\n\t\t\t
3.9.\n\t\t\t

Information considered relevant to the execution of the survey and dimensioning, obtained from the respective agencies and managers, using specific forms and structured questionnaires. (Item 5.2.1.1.9)

\n\t\t\t
3.10.\n\t\t\t

Macro data relating to costs corresponding to the carreer cadre, considering all financial advantages (bonuses, benefits, assistance, dangerousness, unhealthy conditions, among others) related to the position/function evaluated. (Item 5.2.1.1.10)

\n\t\t\t
3.11.\n\t\t\t

Professional profiles of each position/function, such as education, duties, work regime, working hours, among others. (Item 5.2.1.1.11)

\n\t\t\t
3.12.\n\t\t\t

Percentage of absenteeism by function, broken down by the career cadre, agency/entity, considering and discriminating the different causes of absence (foreseen and unforeseen). (Item 5.2.1.1.12)

\n\t\t\t
3.13.\n\t\t\t

Seasonal demand, pent-up demand, overestimated demand, function deviations and their impacts on performance and productivity, as well as on the state public budget. (Item 5.2.1.1.13)

\n\t\t\t
4.\n\t\t\t

WORKFORCE SIZING (5.2.2)

\n\t\t\t
4.1.\n\t\t\t

The System shall be able to identify, in terms of qualitative and quantitative profiles, the ideal carreer cadre for the functioning of the administrative units that make up the areas of State activity in the current context and over a horizon of up to 10 years.

\n\t\t\t
4.2.\n\t\t\t

The System shall be able to implement differentiated strategies for the various sectors according to the reality identified. For example, in areas and units that present the same service profile as hospitals, the dimensioning work can be replicated by adopting sizes. In units of the same profile and size or of equivalent size, the same dimensioning can be applied, but it shall always be aligned with the trend indicated by the demographic behavior of the state/municipalities.

\n\t\t\t
4.3.\n\t\t\t

The System shall provide functionalities to dimension the workforce, according to the proposed methodology, through the implementation of parameterizable algorithms and indicators, user interaction interfaces, data analysis mechanisms, production of queries, reports and panels representing the results and generation of data to eventually be consumed by other systems (for example, in csv format), covering, at least, the following aspects, or others if there is a change in the proposed reference model.

\n\t\t\t
4.4.\n\t\t\t

The system shall consolidate the methodological proposal for sizing the workforce, by area of activity, based on a survey of qualitative, quantitative and cost data, analysis of indicators and application of the parameters adopted. (Item 5.2.2.1.1)..

\n\t\t\t
4.5.\n\t\t\t

The system shall present a detailed and structured documentation/dossier by area of activity, carreer cadre, position and function, of the methodology developed for preparing the Workforce Sizing, indicating the parameters used, indicators and other information pertinent to the data modeling used. (Item 5.2.2.1.2.)

\n\t\t\t
4.6.\n\t\t\t

The system shall identify of which Agencies/Entities, based on a comparison of the proposed ideal sizing and the existing staff, are oversized, undersized, or have the correct sizing, but with an imbalance between the levels of activity of their organizational structure, covering the regions. (Item 5.2.2.1.3.)

\n\t\t\t
4.7.\n\t\t\t

The system shall provide information that allows the preparation of strategy proposals aimed at optimizing human, material, financial and budgetary resources that include, among others: (Item 5.2.2.1.4.)

\n\n\t\t\t

a) adjustments to the composition of the workforce, in terms of profile, hiring method, modernization and restructuring of career cadres, including recommendations for the elimination, creation or reformulation of positions and/or functions;

\n\n\t\t\t

b) modernization of management through review of processes, investment in information technology, including the use of information systems and application of artificial intelligence, change in the way services are offered (digital and others);

\n\n\t\t\t

c) adoption of the Teleworking regime;

\n\n\t\t\t

d) indication of distortions, deficiencies and problems found and recommendation of the necessary interventions to solve them;

\n\n\t\t\t

e) guidelines for developing a career cadres training plan;

\n\n\t\t\t

f) Possibility of alternative service provision models that consider, among other possibilities, partnerships with the third sector, public-private partnerships and outsourcing.

\n\t\t\t
4.8.\n\t\t\t

The system shall provide functionalities that support workforce sizing activities, as described in subitem 5.2.2.2 of the Term of Reference.

\n\t\t\t
5.\n\t\t\t

WORKFORCE ADEQUACY PLAN AND WORKFORCE PLANNING INSTITUTIONALIZATION PLAN (5.3)

\n\t\t\t
5.1.\n\t\t\t

The System shall provide functionalities for carrying out comparative analyses between the current situation and the sizing, allowing the identification of deficit and surplus areas, indicating the necessary interventions, which may include, in addition to the replacement or expansion of the number of employees, the restructuring of work processes, requalification, reassignments or reformulation of the service contracting method, according to the proposed methodology.

\n\t\t\t
5.2.\n\t\t\t

The System shall provide functionalities to support the preparation of the workforce adequacy plan (replacement, expansion and optimization), as detailed in 5.3.1, establishing the need for hiring employees and the respective cost forecast, for the short term (zero to 2 years), medium term (3 to 5 years) and longterm (6 to 10 years), considering the hiring forecast resulting from the replacement rates and projection of revenues and expenses of the State, by agency/entity, in accordance with the Carreer cadres, Positions and Functions, taking into account the potential for using a reserve register in current public examinations and the limits established in Complementary Law No. 101, Fiscal Responsibility Law.

\n\t\t\t
\n\n

 

\n\n

 

"},{"id":"OP00370973","notice_type":"Request for Expression of Interest","noticedate":"19-Aug-2025","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2025-08-25T00:00:00Z","submission_deadline_time":"18:00","project_ctry_name":"Uzbekistan","project_id":"P168180","project_name":"Institutional Capacity Building Project","bid_reference_no":"MEF-DEVOPS-IC","bid_description":"Engagement of a DevOps Engineer IT Specialist to Support the Development and Maintenance of AI-based Digital Infrastructure at the Ministry of Economy and Finance of the Republic of Uzbekistan","procurement_group":"CS","procurement_method_code":"INDV","procurement_method_name":"Individual Consultant Selection","contact_address":"29., Istiklol street, 100017 Tashkent","contact_ctry_name":"Uzbekistan","contact_email":"piu_mof@mail.ru","contact_name":"Sirojiddin Imanov","contact_organization":"Ministry of Economy and Finance of the Republic of Uzbekistan","contact_phone_no":"+998903311662","contact_web_url":"info@imv.uz","submission_date":"2025-08-19T00:00:00Z","notice_text":"

REQUEST FOR EXPRESSIONS OF INTEREST

\n\n

(CONSULTING SERVICES – INDIVIDUAL CONSULTANT SELECTION)

\n\n

 

\n\n

Uzbekistan

\n\n

Institutional Capacity Building Project

\n\n

Credit No.: IDA 6431-UZ

\n\n

 

\n\n

Assignment Title: Engagement of a DevOps Engineer IT Specialist to Support the Development and Maintenance of AI-based Digital Infrastructure at the Ministry of Economy and Finance of the Republic of Uzbekistan.

\n\n

Reference No.: MEF-DEVOPS-IC

\n\n

 

\n\n

The Ministry of Economy and 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 for the Ministry of Economy and finance of the Republic of Uzbekistan.

\n\n

The Ministry of Economy and finance of the Republic of Uzbekistan plans to engage a team of experienced local IT specialists. The primary mandate of these local experts is to enhance the Ministry’s “Online Advisor” service on its official website by leveraging AI technologies to automatically respond to inquiries from individuals and legal entities concerning the Ministry’s core functions—such as state budget preparation and execution, treasury operations, public–private partnerships, subsidy allocation, and other government services.

\n\n

The Ministry of Economy and finance of the Republic of Uzbekistan now invites eligible Individual Consultants (“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 (reference to similar services, experience in similar assignments, availability, etc.) submitting directly to the piu_mof@mail.ru.

\n\n

 

\n\n

Qualification requirements for the Consultant:

\n\n

 

\n\n

– Bachelor’s degree in IT/Software Engineering;

\n\n

– 5+ years of DevOps experience;

\n\n

– Hands-on with Docker, YAML, Bash/Python scripting;

\n\n

– Familiar with GitLab, Jenkins, Prometheus, Grafana;

\n\n

– Implement CI/CD pipelines and containerized deployment (Docker);

\n\n

– Configure orchestration tools (Kubernetes preferred);

\n\n

– Maintain server monitoring using tools like Zabbix, Grafana, Prometheus;

\n\n

– Automate environment provisioning and rollback scenarios.

\n\n

 

\n\n

Candidates possessing the following certifications will be given priority consideration:

\n\n

- Docker Certified Associate (DCA) or Certified Kubernetes Administrator (CKA);

\n\n

- GitLab CI/CD Certification (preferred).

\n\n

 

\n\n

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, 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 Economy and finance of the Republic of Uzbekistan.

\n\n

 

\n\n

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

\n\n

 

\n\n

Expressions of interest must be delivered in a written form in English or Russian languages to the address below (in person, or by mail, or by e-mail) by August 25, 2025.

\n\n

 

\n\n

Project Implementation Unit under the
\nMinistry of Economy and finance of the Republic of Uzbekistan

\n\n

Attn: Sirojiddin Imanov, Manager of the Project

\n\n

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

\n\n

Tel: +998903311662

\n\n

E-mail: piu_mof@mail.ru

\n\n

 

\n\n

 

\n\n

Terms of Reference (ToR) for the Engagement of a DevOps Engineer IT Specialist to Support the Development and Maintenance of AI-based Digital Infrastructure at the Ministry of Economy and Finance of the Republic of Uzbekistan

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1. Project Background and Objectives

\n\n\t\t\t

On May 24, 2019, the World Bank and Ministry of Economy and Finance of the Republic of Uzbekistan (MEF) agreed on a World Bank loan program called “Institutional Capacity Building Project” (ICBP) for Uzbekistan.

\n\n\t\t\t

The development objectives of ICBP are to strengthen public financial management (PFM) and enable the market operation of the corporate sector. This project has four components. 1) The first component, Improving PFM, aims to support improvements in areas fundamental to a functional PFM system that promotes the achievement of public policy objectives, improved performance, and institutionalized accountability. 2) The second component, Improving Conditions for Market Operation of the Corporate Sector, aims to support the restructuring and rightsizing of the State-Owned Enterprise (SOE) sector in Uzbekistan. 3) The third component, Improving Support Mechanisms for Reforms, aims to provide support to the newly established Economic Council, key regulatory agencies, and other public sector agencies expected to be identified as critical for implementing market reforms during project implementation. 4) The fourth component, Project Management, aims to provide support to the overall implementation arrangements for the project.

\n\n\t\t\t

 

\n\n\t\t\t

As part of this initiative, the Ministry plans to engage a team of experienced local IT specialists.

\n\n\t\t\t

 

\n\n\t\t\t

Pursuant to Instruction No. 25/3‑285 dated 17 June 2025 issued by the Ministry of Economy and Finance, an AI Technologies Working Group—comprising Ministry staff and external experts—will be established to systematically coordinate and strategically advance all AI‑related initiatives. This Working Group will include four local experts: a Network Administrator, a System Administrator, a DevOps Engineer, and a Software Developer.

\n\n\t\t\t

 

\n\n\t\t\t

The primary mandate of these local experts is to enhance the Ministry’s “Online Advisor” service on its official website by leveraging AI technologies to automatically respond to inquiries from individuals and legal entities concerning the Ministry’s core functions—such as state budget preparation and execution, treasury operations, public–private partnerships, subsidy allocation, and other government services.

\n\n\t\t\t

 

\n\n\t\t\t

The Ministry cannot successfully deliver on these objectives without the engagement of qualified and reputable IT professionals with demonstrated experience in these roles: Network Administrator, System Administrator, DevOps Engineer, and Software Developer.

\n\t\t\t
\n\t\t\t

2. Goals and objectives set for the Ministry:

\n\n\t\t\t

Identify the Ministry’s core service areas (state budget drafting and execution, treasury operations, public–private partnership programs, subsidy allocation, tax and customs regimes, etc.) and compile a comprehensive FAQ corpus reflecting the most frequent inquiries from individuals and legal entities.

\n\n\t\t\t

Develop and continually update this FAQ corpus using semantic intent recognition and NLP models (e.g., GPT‑series) to ensure relevance and accuracy.

\n\n\t\t\t

Design and integrate a chatbot module into the Ministry’s official website “Online Advisor” interface, capable of interpreting natural‑language queries, routing users to the appropriate department or document, or providing an automated response.

\n\n\t\t\t

Enable multilingual support (Uzbek, Russian, English) and implement a continuous feedback‑loop mechanism to improve understanding and response quality over time.

\n\n\t\t\t

Establish key performance indicators (average response time, successful automated response rate, user satisfaction score) and integrate real‑time monitoring dashboards to track and optimize the “Online Advisor” service.

\n\n\t\t\t

Improve accessibility and adoption by optimizing UI/UX for both web and mobile platforms, creating user guides, and conducting targeted outreach to stakeholders.

\n\n\t\t\t

Conduct regular service audits—reviewing chatbot responses, assessing inquiry complexity, and recommending process optimizations—and pilot proposed improvements to validate their effectiveness.

\n\t\t\t
\n\t\t\t

3. Scope of Services:

\n\n\t\t\t

The DevOps Engineer will:

\n\n\t\t\t

1. CI/CD Pipeline Design & Implementation

\n\n\t\t\t

– Architect, build, and maintain end‑to‑end CI/CD pipelines using GitLab CI, Jenkins, or comparable platforms;

\n\n\t\t\t

– Automate code build, test, containerization, and deployment workflows for the AI chatbot and supporting microservices.

\n\n\t\t\t

2. Container Orchestration & Infrastructure Provisioning

\n\n\t\t\t

– Design and manage Kubernetes clusters (EKS, GKE, AKS, or on‑prem) for scalable deployment of containers;

\n\n\t\t\t

– Implement Infrastructure as Code (IaC) using Terraform or CloudFormation to provision servers, networks, and storage.

\n\n\t\t\t

3. Configuration Management & Automation

\n\n\t\t\t

– Use Ansible, Puppet, or Chef to automate configuration drift prevention, patch management, and environment standardization;

\n\n\t\t\t

– Create reusable playbooks, roles, and modules for rapid environment replication.

\n\n\t\t\t

4. Monitoring, Logging & Alerting

\n\n\t\t\t

– Integrate Prometheus, Grafana, ELK Stack, or Loki/Tempo for real‑time observability of application performance, system health, and cost metrics;

\n\n\t\t\t

– Define SLOs/SLIs, configure alerts, and establish escalation processes to meet agreed SLAs.

\n\n\t\t\t

5. Security & Compliance Automation

\n\n\t\t\t

– Embed security checks into the pipeline: container image scanning (Trivy/Clair), IaC linting (TFLint), and dependency vulnerability scanning;

\n\n\t\t\t

– Implement automated secrets management with Vault, AWS Secrets Manager, or equivalent tools.

\n\n\t\t\t

6. Performance Optimization & Scalability

\n\n\t\t\t

– Design horizontal and vertical autoscaling policies for Kubernetes pods and VMs based on CPU, memory, and custom metrics;

\n\n\t\t\t

– Profile and tune application start‑up times, resource limits, and load‑balancer configurations for minimal latency.

\n\n\t\t\t

7. Disaster Recovery & Business Continuity

\n\n\t\t\t

– Develop and test backup, restore, and failover procedures for critical services and data stores;

\n\n\t\t\t

– Maintain runbooks for emergency response, disaster recovery drills, and post‑mortem analyses.

\n\t\t\t
\n\t\t\t

4. Qualification requirements

\n\n\t\t\t

DevOps Engineer to support AI-based digital infrastructure at the Ministry of Economy and Finance.

\n\n\t\t\t

Requirements for work experience and qualifications:

\n\n\t\t\t

– Bachelor’s degree in IT/Software Engineering;

\n\n\t\t\t

– 5+ years of DevOps experience;

\n\n\t\t\t

– Hands-on with Docker, YAML, Bash/Python scripting;

\n\n\t\t\t

– Familiar with GitLab, Jenkins, Prometheus, Grafana;

\n\n\t\t\t

– Implement CI/CD pipelines and containerized deployment (Docker);

\n\n\t\t\t

– Configure orchestration tools (Kubernetes preferred);

\n\n\t\t\t

– Maintain server monitoring using tools like Zabbix, Grafana, Prometheus;

\n\n\t\t\t

– Automate environment provisioning and rollback scenarios.

\n\n\t\t\t

Candidates possessing the following certifications will be given priority consideration:

\n\n\t\t\t

Docker Certified Associate (DCA) or Certified Kubernetes Administrator (CKA);

\n\n\t\t\t

GitLab CI/CD Certification (preferred).

\n\t\t\t
\n\t\t\t

5. Responsibility and Performance Assessment

\n\n\t\t\t

Coordination:

\n\n\t\t\t

– Reports to the Ministry’s Chief IT Architect and liaises with the Project Implementation Unit (PIU);

\n\n\t\t\t

– Works on‑site in Tashkent under a jointly‑approved work plan.

\n\n\t\t\t

Deliverables & Reporting:

\n\n\t\t\t

– Monthly progress reports detailing network builds, tests, incidents and mitigations;

\n\n\t\t\t

– Final “as‑built” network diagrams, configuration files and transition documentation.

\n\t\t\t
\n\t\t\t

6. Duration and mode of operation

\n\n\t\t\t

The duration of the expert's work is expected to be 5 months.

\n\n\t\t\t

At the same time, the organization of the work of specialists is carried out based on the work plan between The Client and The Expert: the expert works directly in Tashkent. The remuneration for the activities described in these TORs will be in a monthly salary basis.

\n\t\t\t
\n\t\t\t

7. Results

\n\n\t\t\t

1. Result 1: High-performance GPU servers are procured, configured, and deployed to support AI model training and inference. The AI computing environment is made fully operational for chatbot model execution.

\n\n\t\t\t

2. Result 2: AI models (e.g., GPT-based) are fine-tuned using ministry-specific content such as legal documents, regulations, and FAQs. The chatbot is trained to support multilingual interaction, including Uzbek.

\n\n\t\t\t

3. Result 3: The chatbot is connected to core systems such as UzASBO, budget management platforms, and electronic document circulation via secure APIs. Enables real-time responses to data-driven queries (e.g., budget status, payment records, document tracking).

\n\n\t\t\t

4. Result 4: A responsive web-based interface for the chatbot is developed for ministry staff and the public. Mobile applications for Android/iOS platforms are deployed and user-tested.

\n\n\t\t\t

5. Result 5: Chatbot queries are protected with authentication, role-based response control, and logging mechanisms. IDS/IPS systems are used to secure AI server network communications.

\n\n\t\t\t

6. Result 6: Chatbot usage is monitored, and accuracy and user satisfaction levels are measured. Based on feedback and performance reports, the model is retrained, and the response base is regularly updated.

\n\t\t\t
\n\t\t\t

8. Organizational issues

\n\n\t\t\t

The Client is the Ministry of Economy and Finance. The Ministry is responsible for receiving the work performed by expert within the framework of this assignment, as well as signing the act of acceptance of the work.

\n\n\t\t\t

The PIU under the Ministry of Economy and Finance is responsible for making payments based on the act of acceptance of work/Timesheet/Service signed by the Ministry (based on the Protocol approving the relevant deliverable(s)) and the preliminary act of expert.

\n\n\t\t\t

All costs, including taxes, are covered by expert.

\n\t\t\t
\n\n

 

\n\n

 

\n\n

 

"},{"id":"OP00370974","notice_type":"Request for Expression of Interest","noticedate":"19-Aug-2025","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2025-08-25T00:00:00Z","submission_deadline_time":"18:00","project_ctry_name":"Uzbekistan","project_id":"P168180","project_name":"Institutional Capacity Building Project","bid_reference_no":"MEF-SYSTEM-IC","bid_description":"Engagement of a System Administrator IT Specialist to Support the Development and Maintenance of AI-based Digital Infrastructure at the Ministry of Economy and Finance of the Republic of Uzbekistan","procurement_group":"CS","procurement_method_code":"INDV","procurement_method_name":"Individual Consultant Selection","contact_address":"29., Istiklol street, 100017 Tashkent","contact_ctry_name":"Uzbekistan","contact_email":"piu_mof@mail.ru","contact_name":"Sirojiddin Imanov","contact_organization":"Ministry of Economy and Finance of the Republic of Uzbekistan","contact_phone_no":"903311662","contact_web_url":"info@imv.uz","submission_date":"2025-08-19T00:00:00Z","notice_text":"

REQUEST FOR EXPRESSIONS OF INTEREST

\n\n

(CONSULTING SERVICES – INDIVIDUAL CONSULTANT SELECTION)

\n\n

 

\n\n

Uzbekistan

\n\n

Institutional Capacity Building Project

\n\n

Credit No.: IDA 6431-UZ

\n\n

 

\n\n

Assignment Title: Engagement of a System Administrator IT Specialist to Support the Development and Maintenance of AI-based Digital Infrastructure at the Ministry of Economy and Finance of the Republic of Uzbekistan.

\n\n

Reference No.: MEF-SYSTEM-IC

\n\n

 

\n\n

The Ministry of Economy and 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 for the Ministry of Economy and finance of the Republic of Uzbekistan.

\n\n

The Ministry of Economy and finance of the Republic of Uzbekistan plans to engage a team of experienced local IT specialists. The primary mandate of these local experts is to enhance the Ministry’s “Online Advisor” service on its official website by leveraging AI technologies to automatically respond to inquiries from individuals and legal entities concerning the Ministry’s core functions—such as state budget preparation and execution, treasury operations, public–private partnerships, subsidy allocation, and other government services.

\n\n

The Ministry of Economy and finance of the Republic of Uzbekistan now invites eligible Individual Consultants (“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 (reference to similar services, experience in similar assignments, availability, etc.) submitting directly to the piu_mof@mail.ru.

\n\n

 

\n\n

Qualification requirements for the Consultant:

\n\n

 

\n\n

– Bachelor’s degree in Computer Science or related fields;

\n\n

– Proficiency in Linux (RHEL/Ubuntu) and Windows Server systems;

\n\n

– Experience with virtualization tools like KVM, Hyper-V, Vmware;

\n\n

– Familiarity with enterprise-level GPU servers and RAID-based storage systems;

\n\n

– Administer Linux/Windows servers and cloud infrastructure;

\n\n

– Ensure optimal performance of AI-related backend systems;

\n\n

– Manage OS-level security, updates, and patch management;

\n\n

– Support database and storage services used in AI systems.

\n\n

 

\n\n

Candidates possessing the following certifications will be given priority consideration:

\n\n

- LPIC or RHCSA/RHCE (Linux);

\n\n

- VMware VCP or Microsoft MCSA/MCSE (preferred).

\n\n

 

\n\n

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, 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 Economy and finance of the Republic of Uzbekistan.

\n\n

 

\n\n

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

\n\n

 

\n\n

Expressions of interest must be delivered in a written form in English or Russian languages to the address below (in person, or by mail, or by e-mail) by August 25, 2025.

\n\n

 

\n\n

Project Implementation Unit under the
\nMinistry of Economy and finance of the Republic of Uzbekistan

\n\n

Attn: Sirojiddin Imanov, Manager of the Project

\n\n

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

\n\n

Tel: +998903311662

\n\n

E-mail: piu_mof@mail.ru

\n\n

 

\n\n

 

\n\n

Terms of Reference (ToR) for the Engagement of a System Administrator IT Specialist to Support the Development and Maintenance of AI-based Digital Infrastructure at the Ministry of Economy and Finance of the Republic of Uzbekistan
\n 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1. Project Background and Objectives

\n\n\t\t\t

On May 24, 2019, the World Bank and Ministry of Economy and Finance of the Republic of Uzbekistan (MEF) agreed on a World Bank loan program called “Institutional Capacity Building Project” (ICBP) for Uzbekistan.

\n\n\t\t\t

The development objectives of ICBP are to strengthen public financial management (PFM) and enable the market operation of the corporate sector. This project has four components. 1) The first component, Improving PFM, aims to support improvements in areas fundamental to a functional PFM system that promotes the achievement of public policy objectives, improved performance, and institutionalized accountability. 2) The second component, Improving Conditions for Market Operation of the Corporate Sector, aims to support the restructuring and rightsizing of the State-Owned Enterprise (SOE) sector in Uzbekistan. 3) The third component, Improving Support Mechanisms for Reforms, aims to provide support to the newly established Economic Council, key regulatory agencies, and other public sector agencies expected to be identified as critical for implementing market reforms during project implementation. 4) The fourth component, Project Management, aims to provide support to the overall implementation arrangements for the project.

\n\n\t\t\t

 

\n\n\t\t\t

As part of this initiative, the Ministry plans to engage a team of experienced local IT specialists.

\n\n\t\t\t

 

\n\n\t\t\t

Pursuant to Instruction No. 25/3‑285 dated 17 June 2025 issued by the Ministry of Economy and Finance, an AI Technologies Working Group—comprising Ministry staff and external experts—will be established to systematically coordinate and strategically advance all AI‑related initiatives. This Working Group will include four local experts: a Network Administrator, a System Administrator, a DevOps Engineer, and a Software Developer.

\n\n\t\t\t

 

\n\n\t\t\t

The primary mandate of these local experts is to enhance the Ministry’s “Online Advisor” service on its official website by leveraging AI technologies to automatically respond to inquiries from individuals and legal entities concerning the Ministry’s core functions—such as state budget preparation and execution, treasury operations, public–private partnerships, subsidy allocation, and other government services.

\n\n\t\t\t

 

\n\n\t\t\t

The Ministry cannot successfully deliver on these objectives without the engagement of qualified and reputable IT professionals with demonstrated experience in these roles: Network Administrator, System Administrator, DevOps Engineer, and Software Developer.

\n\t\t\t
\n\t\t\t

2. Goals and objectives set for the Ministry:

\n\n\t\t\t

Identify the Ministry’s core service areas (state budget drafting and execution, treasury operations, public–private partnership programs, subsidy allocation, tax and customs regimes, etc.) and compile a comprehensive FAQ corpus reflecting the most frequent inquiries from individuals and legal entities.

\n\n\t\t\t

Develop and continually update this FAQ corpus using semantic intent recognition and NLP models (e.g., GPT‑series) to ensure relevance and accuracy.

\n\n\t\t\t

Design and integrate a chatbot module into the Ministry’s official website “Online Advisor” interface, capable of interpreting natural‑language queries, routing users to the appropriate department or document, or providing an automated response.

\n\n\t\t\t

Enable multilingual support (Uzbek, Russian, English) and implement a continuous feedback‑loop mechanism to improve understanding and response quality over time.

\n\n\t\t\t

Establish key performance indicators (average response time, successful automated response rate, user satisfaction score) and integrate real‑time monitoring dashboards to track and optimize the “Online Advisor” service.

\n\n\t\t\t

Improve accessibility and adoption by optimizing UI/UX for both web and mobile platforms, creating user guides, and conducting targeted outreach to stakeholders.

\n\n\t\t\t

Conduct regular service audits—reviewing chatbot responses, assessing inquiry complexity, and recommending process optimizations—and pilot proposed improvements to validate their effectiveness.

\n\t\t\t
\n\t\t\t

3. Scope of Services:

\n\n\t\t\t

The System Administrator will:

\n\n\t\t\t

1. AI Infrastructure Deployment & Management

\n\n\t\t\t

– Install, configure, and maintain GPU‑accelerated servers (e.g., NVIDIA H100), storage arrays, and virtualization hosts (KVM, VMware, or Hyper‑V);

\n\n\t\t\t

– Provision and optimize DDR5 ECC RAM, NVMe SSD RAID arrays, and network file systems for high‑IOPS workloads.

\n\n\t\t\t

2. Operating System & Virtualization Administration

\n\n\t\t\t

– Deploy and harden Linux distributions (Ubuntu Server, RHEL) and Windows Server environments according to security best practices;

\n\n\t\t\t

– Manage container and VM platforms (Docker, Kubernetes, KVM), including image repositories, networking, and resource quotas.

\n\n\t\t\t

3. Backup, Recovery & High Availability

\n\n\t\t\t

– Design and implement automated backup strategies (file‑ and image‑level) for critical data stores using enterprise tools (e.g., Bacula, Veeam);

\n\n\t\t\t

– Configure high‑availability clusters and failover mechanisms for essential services (database, authentication, storage).

\n\n\t\t\t

4. Monitoring, Logging & Alerting

\n\n\t\t\t

– Integrate and maintain monitoring solutions (Prometheus, Zabbix) and log aggregation platforms (ELK Stack, Graylog) to track system health, resource utilization, and error conditions;

\n\n\t\t\t

– Define thresholds, alerts, and escalation procedures; produce weekly and ad‑hoc performance and capacity reports.

\n\n\t\t\t

5. Security & Compliance

\n\n\t\t\t

– Apply OS‑level security controls: patch management, SELinux/AppArmor, file integrity monitoring, and vulnerability scanning (OpenVAS, Nessus);

\n\n\t\t\t

– Enforce role‑based access control (RBAC), multi‑factor authentication (MFA), and encryption at rest/in transit for sensitive data.

\n\n\t\t\t

6. Configuration Management & Automation

\n\n\t\t\t

– Develop and maintain Infrastructure as Code (IaC) playbooks and templates using Ansible, Terraform, or equivalent;

\n\n\t\t\t

– Automate routine tasks (provisioning, patching, scaling) to ensure consistency and reduce manual intervention.

\n\t\t\t
\n\t\t\t

4. Qualification requirements

\n\n\t\t\t

System Administrator to support AI-based digital infrastructure at the Ministry of Economy and Finance.

\n\n\t\t\t

Requirements for work experience and qualifications:

\n\n\t\t\t

– Bachelor’s degree in Computer Science or related fields;

\n\n\t\t\t

– Proficiency in Linux (RHEL/Ubuntu) and Windows Server systems;

\n\n\t\t\t

– Experience with virtualization tools like KVM, Hyper-V, Vmware;

\n\n\t\t\t

– Familiarity with enterprise-level GPU servers and RAID-based storage systems;

\n\n\t\t\t

– Administer Linux/Windows servers and cloud infrastructure;

\n\n\t\t\t

– Ensure optimal performance of AI-related backend systems;

\n\n\t\t\t

– Manage OS-level security, updates, and patch management;

\n\n\t\t\t

– Support database and storage services used in AI systems.

\n\n\t\t\t

Candidates possessing the following certifications will be given priority consideration:

\n\n\t\t\t

LPIC or RHCSA/RHCE (Linux);

\n\n\t\t\t

VMware VCP or Microsoft MCSA/MCSE (preferred).

\n\t\t\t
\n\t\t\t

5. Responsibility and Performance Assessment

\n\n\t\t\t

Coordination:

\n\n\t\t\t

– Reports to the Ministry’s Chief IT Architect and liaises with the Project Implementation Unit (PIU);

\n\n\t\t\t

– Works on‑site in Tashkent under a jointly‑approved work plan.

\n\n\t\t\t

Deliverables & Reporting:

\n\n\t\t\t

– Monthly progress reports detailing network builds, tests, incidents and mitigations;

\n\n\t\t\t

– Final “as‑built” network diagrams, configuration files and transition documentation.

\n\t\t\t
\n\t\t\t

6. Duration and mode of operation

\n\n\t\t\t

The duration of the expert's work is expected to be 5 months.

\n\n\t\t\t

At the same time, the organization of the work of specialists is carried out based on the work plan between The Client and The Expert: the expert works directly in Tashkent. The remuneration for the activities described in these TORs will be in a monthly salary basis.

\n\t\t\t
\n\t\t\t

7. Results

\n\n\t\t\t

1. Result 1: High-performance GPU servers are procured, configured, and deployed to support AI model training and inference. The AI computing environment is made fully operational for chatbot model execution.

\n\n\t\t\t

2. Result 2: AI models (e.g., GPT-based) are fine-tuned using ministry-specific content such as legal documents, regulations, and FAQs. The chatbot is trained to support multilingual interaction, including Uzbek.

\n\n\t\t\t

3. Result 3: The chatbot is connected to core systems such as UzASBO, budget management platforms, and electronic document circulation via secure APIs. Enables real-time responses to data-driven queries (e.g., budget status, payment records, document tracking).

\n\n\t\t\t

4. Result 4: A responsive web-based interface for the chatbot is developed for ministry staff and the public. Mobile applications for Android/iOS platforms are deployed and user-tested.

\n\n\t\t\t

5. Result 5: Chatbot queries are protected with authentication, role-based response control, and logging mechanisms. IDS/IPS systems are used to secure AI server network communications.

\n\n\t\t\t

6. Result 6: Chatbot usage is monitored, and accuracy and user satisfaction levels are measured. Based on feedback and performance reports, the model is retrained, and the response base is regularly updated.

\n\t\t\t
\n\t\t\t

8. Organizational issues

\n\n\t\t\t

The Client is the Ministry of Economy and Finance. The Ministry is responsible for receiving the work performed by expert within the framework of this assignment, as well as signing the act of acceptance of the work.

\n\n\t\t\t

The PIU under the Ministry of Economy and Finance is responsible for making payments based on the act of acceptance of work/Timesheet/Service signed by the Ministry (based on the Protocol approving the relevant deliverable(s)) and the preliminary act of expert.

\n\n\t\t\t

All costs, including taxes, are covered by expert.

\n\t\t\t
\n\n

 

\n\n

 

"},{"id":"OP00339275","notice_type":"Invitation for Bids","noticedate":"13-Feb-2025","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2025-04-18T00:00:00Z","submission_deadline_time":"14:00","project_ctry_name":"Ethiopia","project_id":"P176731","project_name":"Power Sector Reform, Investment and Modernization in Ethiopia (PRIME-1)","bid_reference_no":"ET-EEP-455042-CW-RFB","bid_description":"Plant Design, Supply, Installation, Test and, Commissioning of New Shashemane II 230/132/33/15kV, Bale Robe 132/33/15kV, Bensa Daye 132/33kV, Durame 132/15kV Substations and addition of one 132/15kV, 31.5MVA transformer at Hallaba substation","procurement_group":"CW","procurement_method_code":"RFB","procurement_method_name":"Request for Bids","contact_address":"P.O.BOX 1233Degaule SquareAddis Ababa","contact_ctry_name":"Ethiopia","contact_email":"kmergiya@yahoo.com","contact_name":"Kefyalew Mergiya","contact_organization":"Ethiopian Electric Power","contact_phone_no":"251-911895433","contact_web_url":"www.eep.com.et","submission_date":"2025-02-13T00:00:00Z","notice_text":"

Specific Procurement Notice

\n\n

Request for Bids

\n\n

Plant

\n\n

Design, Supply and Installation

\n\n

(Two-envelope Bidding Process, Without Prequalification)

\n\n

Employer: Ethiopian Electric Power (EEP)

\n\n

Project: Power Sector Reform Investment and Modernization -1 in Ethiopia (Prime-1)

\n\n

Contract title:  Plant Design, Manufacture, Supply, Installation, Test and Commissioning of New Shashemane II 230/132/33/15kV, Bale Robe 132/33/15kV, Bensa Daye 132/33kV, Durame 132/15kV Substations and addition of one 132/15kV, 31.5MVA transformer at Hallaba substation

\n\n

Country: Ethiopia

\n\n

Loan No. /Credit / loan No.: IDA-75200

\n\n

RFB No: ET-EEP-455042-CW-RFB

\n\n

1.      The Government of Federal Democratic Republic of Ethiopia has received financing from the World Bank toward the cost of the Power Sector Reform, Investment and Modernization in Ethiopia, and intends to apply part of the proceeds toward payments under the Contract for Plant Design, Supply, Installation, Test and Commissioning of New Shashemane II 230/132/33/15kV, Bale Robe 132/33/15kV, Bensa Daye 132/33kV, Durame 132/15kV Substations and addition of one 132/15kV, 31.5MVA transformer at Hallaba substation. For this contract, the Borrower shall process the payments using the Direct Payment disbursement method, as defined in the World Bank’s Disbursement Guidelines for Investment Project Financing, except for those payments, which the contract provides to be made through letter of credit.”

\n\n

2.      The Ethiopian Electric Power (EEP) now invites sealed Bids from eligible Bidders for Plant Design, Manufacture, Supply, Installation, Test and Commissioning of New Shashemane II 230/132/33/15kV, Bale Robe 132/33/15kV, Bensa Daye 132/33kV, Durame 132/15kV Substations and addition of one 132/15kV, 31.5MVA transformer at Hallaba substation.

\n\n

            The Scope of work entails Plant Design, Supply, Installation, Test and Commissioning of:

\n\n

a. New 132/15kV, Durame substation;

\n\n

b) New 132/15kV, Bensa Daye substation

\n\n

c) One (1) 132/15kV, 31.5MVA transformer at Hallaba substation

\n\n

d) New 230/132/33/15kV, Shashemane II substation

\n\n

e) New 132/33/15kV, Bale Robe substation

\n\n

f) Protection, communication, and RTU system modification works at Wolayita II and Hallaba substations following existing 132kV line LILO at Durame.

\n\n

g) Protection, communication, and RTU system modification works at Shakisso and Yirgalem I substations following existing 132kV line LILO at Bensa Daye.

\n\n

h) Protection, communication, and RTU system modification works at Yirgalem II, Hawassa II, Shashemane I, Hallaba, and Genda Arba substations following existing 230kV & 132kV lines LILO at Shashemane II substation.

\n\n

i) Protection, communication, and RTU system modification works at Melka Wakena Yugo and Yadot substations following existing 132kV line LILO at Bale Robe.

\n\n

No margin of domestic preference shall apply, and bidders are required to meet the following criteria:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Item/ No.

\n\t\t\t		\n\t\t\t

Qualification Criteria

\n\t\t\t		\n\t\t\t

Minimum Requirement

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Average Annual Turnover for the Last Five Years

\n\t\t\t		\n\t\t\t

USD 34 Million

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Cash flow Requirement

\n\t\t\t		\n\t\t\t

USD 5.7 Million

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

General Experience

\n\t\t\t		\n\t\t\t

Experience in the Power Sector under contracts in the role of contractor, subcontractor, or management contractor for at least the last Ten (10) years starting 1st January 2015.

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Specific Project Experience

\n\t\t\t		\n\t\t\t

Participation as contractor, management contractor, or subcontractor, in at least, Two (2) substations contracts of 230kV voltage level or above within the last five (5) years, each with a value of at least 27 Million USD; that have been successfully completed and that are similar to the proposed Plant and Installation Services. The similarity shall be based on the physical size, complexity, methods/technology or other characteristics

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Specific Experience in managing ES aspects

\n\t\t\t		\n\t\t\t

For the contract above and/or any other contracts completed  as a prime contractor, Joint Venture or sub-contractor, between 1st January 2020 and bid submission deadline, experience in managing ES risk and impacts in the following aspects:

\n\n\t\t\t

i) Preparation and implementation of the Construction Environmental and Social Management Plan C ESMP and other related management plans

\n\n\t\t\t

ii) Preparation of ES reports

\n\t\t\t
\n\t\t\t

6

\n\t\t\t		\n\t\t\t

Others

\n\t\t\t		\n\t\t\t

Bids must be accompanied by a Sexual Exploitation and Abuse (SEA) and/or Sexual Harassment (SH) Declaration.

\n\t\t\t
\n\n

The Employer’s evaluation of responsive bids will take into account the following technical factors, in addition to cost factors.

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No

\n\t\t\t		\n\t\t\t

Technical Factor

\n\t\t\t		\n\t\t\t

Weight in percentage 

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Methodology and Work Plan

\n\t\t\t		\n\t\t\t

35%

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

To what extent the Proposal adds value in terms of performance, functionality, Capacity and/or operating and maintenance (O&M) costs for the major item

\n\t\t\t		\n\t\t\t

20%

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Environmental and Social Management Strategies and Implementation Plans (ES-MSIP)

\n\t\t\t		\n\t\t\t

20%

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Quality management systems

\n\t\t\t		\n\t\t\t

10%

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Contractor’ Representative and Key Personnel

\n\t\t\t		\n\t\t\t

15%

\n\t\t\t
\n\t\t\t

Total Point

\n\t\t\t		\n\t\t\t

100%

\n\t\t\t
\n\n

The weight to be assigned for the technical factors is 40% and cost is 60%.

\n\n

3.      Bidding will be conducted through international competitive procurement using a Request for Bids (RFB) as specified in the World Bank’s “Procurement Regulations for IPF Borrowers”, dated July 2016 and revised in September 2023 (“Procurement Regulations”) and is open to all eligible Bidders as defined in the Procurement Regulations.

\n\n

4.      Interested eligible Bidders may obtain further information from Ethiopian Electric Power /EEP/ and inspect the bidding document during office hours 8:00 hour to 17:00 hours Ethiopian Time at the address given below.

\n\n

5.      The Bidding document in English language may be purchased by interested eligible Bidders upon the submission of a written application to the address below and upon payment of a nonrefundable fee of Ethiopian Birr Twenty Thousand (ETB 20,000.00) or US$ One Hundred fifty (US$ 150.00) or its equivalent in any freely convertible currency from the Ethiopian Electric Power, Procurement office. The method of payment shall be in cash or cashier’s check or through telegraphic transfer to EEP Transmission Construction A/C No.: 1000252665203, Commercial Bank of Ethiopia (CBE), Arada Giorgis Branch, Swift Code: CBETETAA; and EEP BUMBUNA HPP A/C No.0101181300051, National Bank of Ethiopia (NBE), Swift Code: NBETETAA, for ETB and Foreign Currency Account respectively starting from February 17, 2025. The document will be collected by local representatives from the address given below or will be couriered to the bidder through courier service pre-arranged and paid by the bidder.

\n\n

A single-stage, where two envelope RFB process will be used, and the Proposal will consist of (i) the Technical Part, without any reference to prices; and (ii) the Financial Part, as detailed in the RFB Document. The Technical and Financial Parts of the Proposals shall be submitted simultaneously in two separate sealed envelopes.

\n\n

6.      Bids must be delivered to the address below on or before April 18, 2025 at 14:00 hour Ethiopian Time. Electronic bidding will not be permitted. Late Bids will be rejected. The outer Bid envelopes marked “ORIGINAL BID”, and the inner envelopes marked “TECHNICAL PART” will be publicly opened in the presence of the Bidders’ designated representatives and anyone who chooses to attend, at the address below on April 18, 2025 at 14:00 hour Ethiopian Time. All envelopes marked “FINANCIAL PART” shall remain unopened and will be held in safe custody of the Employer until the second public Bid opening.

\n\n

7.      All Bids must be accompanied by a bid Security in US$ 500,000.00 (US$ Five hundred thousand only) or ETB 64.0 million (ETB Sixty-four million only) or its equivalent in any freely convertible currency.

\n\n

8.      Attention is drawn to the Procurement Regulations requiring the Borrower to disclose information on the successful bidder’s beneficial ownership, as part of the Contract Award Notice, using the Beneficial Ownership Disclosure Form as included in the bidding document.

\n\n

9.      The address (es) referred to above is (are):

\n\n

Ethiopian Electric Power/EEP/

\n\n

Attn: Mr. Kefyalew Mergiya

\n\n

Director, EEP Procurement

\n\n

Yeka Sub City, Worda 09, In front of Kotebe Metal Tools Factory, Ethiopian Electric Power Compound, Block Number 09, First Floor, Office Number 203

\n\n

P.O Box 15881

\n\n

E-mail:   kmergiya@yahoo.com,

\n\n

Copy:    Hussen Adem,

\n\n

Manager, Project Procurement

\n\n

Yeka Sub City, Worda 09, In front of Kotebe Metal Tools Factory, Ethiopian Electric Power Compound , Block Number 09, First Floor, Office Number 205

\n\n

E-mail:  Hussen.Adem@eep.com.et, hussenadem377@gmail.com

\n\n

 

"},{"id":"OP00339282","notice_type":"Invitation for Bids","noticedate":"13-Feb-2025","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2025-04-18T00:00:00Z","submission_deadline_time":"14:00","project_ctry_name":"Ethiopia","project_id":"P176731","project_name":"Power Sector Reform, Investment and Modernization in Ethiopia (PRIME-1)","bid_reference_no":"ET-EEP-455044-CW-RFB","bid_description":"Plant Design, Supply, Installation, Test and, Commissioning of New Haromaya II 132/33/15 kV, Chellenko II 132/33/15kV, Woliso 230/33/15kV, Limu Genet Limu Genet 132/33kV and , Arsirobe 132/33kV Substations","procurement_group":"CW","procurement_method_code":"RFB","procurement_method_name":"Request for Bids","contact_address":"P.O.BOX 1233Degaule SquareAddis Ababa","contact_ctry_name":"Ethiopia","contact_email":"kmergiya@yahoo.com","contact_name":"Kefyalew Mergiya","contact_organization":"Ethiopian Electric Power","contact_phone_no":"251-911895433","contact_web_url":"www.eep.com.et","submission_date":"2025-02-13T00:00:00Z","notice_text":"

Specific Procurement Notice

\n\n

Request for Bids

\n\n

Plant
\nDesign, Supply and Installation

\n\n

(Two-envelope Bidding Process, Without Prequalification)

\n\n

Employer: Ethiopian Electric Power (EEP)

\n\n

Project: Power Sector Reform Investment and Modernization -1 in Ethiopia (Prime-1)

\n\n

Contract title: Plant Design, Manufacture, Supply, Installation, Test and, Commissioning of New Haromaya II 132/33/15 kV, Chellenko II 132/33/15kV,  Woliso 230/33/15kV, Limu Genet 132/33kV  and , Arsirobe 132/33kV Substations

\n\n

Country: Ethiopia

\n\n

Loan No. /Credit No. / Grant No.:  IDA-75200   

\n\n

RFB No: ET-EEP-455044-CW-RFB

\n\n

1.        The Government of Federal Democratic Republic of Ethiopia has received financing from the World Bank toward the cost of the Power Sector Reform, Investment and Modernization in Ethiopia, and intends to apply part of the proceeds toward payments under the Contract for Plant Design, Supply, Installation, Test and Commissioning of Haramaya, Chelenko, Woliso, Limu Genet and Arsirobe Substations. “For this contract, the Borrower shall process the payments using the Direct Payment disbursement method, as defined in the World Bank’s Disbursement Guidelines for Investment Project Financing, except for those payments, which the contract provides to be made through letter of credit.”

\n\n

2.        The Ethiopian Electric Power /EEP/ now invites sealed Bids from eligible Bidders for Plant Design, Supply, Installation, Test and Commissioning of Haramaya, Chelenko, Woliso, Limu Genet and Arsirobe Substations.

\n\n

            The Scope of work entails Plant Design, Supply, Installation, Test and Commissioning of:

\n\n

a)  132/33/15kV, Haromaya II substation;

\n\n

b)  132/33/15kV, Chellenko II substation

\n\n

c)   230/33/15kV, Woliso substation

\n\n

d)  132/33kV, Arsi Robe substation

\n\n

e)  one (1) 132kV line bay and 132kV bus bar shunt capacitor bank at Assela Wind substation

\n\n

f)  132/33kV Limu Genet substation

\n\n

g)  one (1) 132kV line bay extension at the existing Jimma II substation

\n\n

h)  Protection, communication, and RTU system setting/modification works at Harar III and Dire Dawa II substations following existing 132kV line LILO at Haromaya II.

\n\n

i) Protection, communication, and RTU system setting/modification works at Wolkite and Woda Metal substations following existing 132kV line LILO at Woliso.

\n\n

No margin of domestic preference shall apply, and bidders are required to meet the following criteria:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Item/ No.

\n\t\t\t		\n\t\t\t

Qualification Criteria

\n\t\t\t		\n\t\t\t

Minimum Requirement

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Average Annual Turnover for the Last Five Years

\n\t\t\t		\n\t\t\t

USD 37.5 Million

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Cash flow Requirement

\n\t\t\t		\n\t\t\t

USD 6 Million

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

General Experience

\n\t\t\t		\n\t\t\t

Experience in the Power Sector under contracts in the role of contractor, subcontractor, or management contractor for at least the last Ten (10) years starting 1st January 2015.

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Specific Project Experience

\n\t\t\t		\n\t\t\t

Participation as contractor, management contractor, or subcontractor, in at least, Two (2) substations contracts of 230kV voltage level or above within the last five (5) years, each with a value of at least 30 Million USD; that have been successfully completed and that are similar to the proposed Plant and Installation Services. The similarity shall be based on the physical size, complexity, methods/technology or other characteristics

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Specific Experience in managing ES aspects

\n\t\t\t		\n\t\t\t

For the contract above and/or any other contracts completed  as a prime contractor, Joint Venture or sub-contractor, between 1st January 2020 and bid submission deadline, experience in managing ES risk and impacts in the following aspects:

\n\n\t\t\t

Preparation and implementation of the Construction Environmental and Social Management Plan C ESMP and other related management plans

\n\n\t\t\t

Preparation of ES reports

\n\t\t\t
\n\t\t\t

6

\n\t\t\t		\n\t\t\t

Others

\n\t\t\t		\n\t\t\t

Bids must be accompanied by a Sexual Exploitation and Abuse (SEA) and/or Sexual Harassment (SH) Declaration.

\n\t\t\t
\n\n

 

\n\n

The Employer’s evaluation of responsive Proposals will take into account the following technical factors, in addition to cost factors.

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No

\n\t\t\t		\n\t\t\t

Technical Factor

\n\t\t\t		\n\t\t\t

Weight in percentage 

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Methodology and Work Plan

\n\t\t\t		\n\t\t\t

35%

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

To what extent the Proposal adds value in terms of performance, functionality, Capacity and/or operating and maintenance (O&M) costs for the major item

\n\t\t\t		\n\t\t\t

20%

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Environmental and Social Management Strategies and Implementation Plans (ES-MSIP)

\n\t\t\t		\n\t\t\t

20%

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Quality management systems

\n\t\t\t		\n\t\t\t

10%

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Contractor’ Representative and Key Personnel

\n\t\t\t		\n\t\t\t

15%

\n\t\t\t
\n\t\t\t

Total Point

\n\t\t\t		\n\t\t\t

100%

\n\t\t\t
\n\n

 

\n\n

The weight to be assigned for the technical factors is 40% and cost is 60%.

\n\n

3.        Bidding will be conducted through international competitive procurement using a Request for Bids (RFB) as specified in the World Bank’s “Procurement Regulations for IPF Borrowers”, dated July 2016 and revised in September 2023  (“Procurement Regulations”) and is open to all eligible Bidders as defined in the Procurement Regulations.

\n\n

4.        Interested eligible Bidders may obtain further information from Ethiopian Electric Power /EEP/ and inspect the bidding document during office hours 8:00 hour to 17:00 hours Ethiopian Time at the address given below.

\n\n

5.        The Bidding document in English language may be purchased by interested eligible Bidders upon the submission of a written application to the address below and upon payment of a nonrefundable fee of Ethiopian Birr Twenty Thousand (ETB 20,000) or United States Dollar One Hundred fifty (USD 150) or its equivalent in any freely convertible currency from the Ethiopian Electric Power, Procurement office. The method of payment shall be in cash or cashier’s check or through telegraphic transfer to EEP Transmission Construction A/C No.: 1000252665203, Commercial Bank of Ethiopia (CBE), Arada Giorgis Branch, Swift Code: CBETETAA; and EEP BUMBUNA HPP A/C No.0101181300051, National Bank of Ethiopia (NBE), Swift Code: NBETETAA, for ETB and Foreign Currency Account respectively starting from   February 17, 2025. The document will be collected by local representatives from the address given below or will be couriered to the bidder through courier service pre-arranged and paid by the bidder.

\n\n

6.        Bids must be delivered to the address below on or before April 18, 2025, at 14:00 hour Ethiopian Time. Electronic bidding will not be permitted. Late Bids will be rejected. The outer Bid envelopes marked “ORIGINAL BID”, and the inner envelopes marked “TECHNICAL PART” will be publicly opened in the presence of the Bidders’ designated representatives and anyone who chooses to attend, at the address below on April 18, 2025. All envelopes marked “FINANCIAL PART” shall remain unopened and will be held in safe custody of the Employer until the second public Bid opening.

\n\n

7.        All Bids must be accompanied by a bid Security in USD 560, 000.00 (US$ five hundred sixty thousand only) or ETB 71.6 million (ETB Seventy-one million Six hundred thousand only) or its equivalent in any freely convertible currency.

\n\n

8.        Attention is drawn to the Procurement Regulations requiring the Borrower to disclose information on the successful bidder’s beneficial ownership, as part of the Contract Award Notice, using the Beneficial Ownership Disclosure Form as included in the bidding document.

\n\n

9.        The address (es) referred to above is (are):

\n\n

Ethiopian Electric Power/EEP/

\n\n

Attn: Mr. Kefyalew Mergiya

\n\n

Director, EEP Procurement

\n\n

Yeka Sub City, Worda 09, In front of Kotebe Metal Tools Factory, Ethiopian Electric Power Compound , Block Number 09, First Floor, Office Number 203

\n\n

P.O Box 15881

\n\n

E-mail:   kmergiya@yahoo.com,

\n\n

 

\n\n

Copy:    Hussen Adem,

\n\n

Manager, Project Procurement

\n\n

Yeka Sub City, Worda 09, In front of Kotebe Metal Tools Factory, Ethiopian Electric Power Compound , Block Number 09, First Floor, Office Number 205

\n\n

E-mail:  Hussen.Adem@eep.com.et, hussenadem377@gmail.com

"},{"id":"OP00299120","notice_type":"Request for Expression of Interest","noticedate":"08-Jul-2024","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2024-07-26T00:00:00Z","submission_deadline_time":"18:00","project_ctry_name":"Uzbekistan","project_id":"P168180","project_name":"Institutional Capacity Building Project","bid_reference_no":"MEF-SAMA-QCBS-SYSTEM-2","bid_description":"Development and Implementation of an Automated System of Accounting and Monitoring for the Activities of State-owned enterprises (SOEs)","procurement_group":"CS","procurement_method_code":"QCBS","procurement_method_name":"Quality And Cost-Based Selection","contact_address":"29., Istiklol street, 100017 Tashkent","contact_ctry_name":"Uzbekistan","contact_email":"jasur.karshibayev@imv.uz","contact_name":"Jasur Karshibaev","contact_organization":"Ministry of Economy and Finance of the Republic of Uzbekistan","contact_phone_no":"+998903311662","contact_web_url":"info@imv.uz","submission_date":"2024-07-08T00:00:00Z","notice_text":"

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

\n\n

 

\n\n

Uzbekistan

\n\n

Institutional Capacity Building Project

\n\n

Credit No.: IDA 6431-UZ

\n\n

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

\n\n

 

\n\n

Reference No.: MEF-SAMA-QCBS-SYSTEM-2

\n\n

 

\n\n

The Ministry of Economy and 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).

\n\n

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”)

\n\n

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.

\n\n

The Ministry of Economy and 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.

\n\n

The qualification requirements for the Consultants are:

\n\n\n\n

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.

\n\n

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

\n\n

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.

\n\n

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

\n\n

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

\n\n

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 July 26 2024.

\n\n

 

\n\n

Project Implementation Unit under the
\nMinistry of Economy and finance of the Republic of Uzbekistan

\n\n

Attn: Sirojiddin Imanov, Manager of the Project

\n\n

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

\n\n

Tel: +998901741711

\n\n

E-mail: piu_mof@mail.ru

\n\n

 

\n\n

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

\n\n\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Date:

\n\t\t\t		\n\t\t\t

Country of Incorporation:

\n\t\t\t
\n\t\t\t

Consultant Name:

\n\t\t\t		\n\t\t\t

Acronym:

\n\t\t\t
\n\t\t\t

EOI Submission Authorized by:

\n\t\t\t		\n\t\t\t

Position

\n\t\t\t
\n\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Consultant

\n\t\t\t		\n\t\t\t

Acronym

\n\t\t\t		\n\t\t\t

Country of Incorporation

\n\t\t\t		\n\t\t\t

Joint Venture (JV) or Sub-consultant

\n\t\t\t		\n\t\t\t

EOI Submission Authorized By

\n\t\t\t		\n\t\t\t

Position

\n\t\t\t
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
      
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\n

 

\n\n

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.

\n\n\n\n

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

\n\n\n\n

Project References, present experiences in similar geographic areas.

\n\n\n\n\n\n\n\n

 

\n\n

 

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

N

\n\t\t\t		\n\t\t\t

Project

\n\t\t\t		\n\t\t\t

Project start date (year, month, mandatory)

\n\t\t\t		\n\t\t\t

Project end date (year, month, mandatory)

\n\t\t\t		\n\t\t\t

Client

\n\t\t\t		\n\t\t\t

Country

\n\t\t\t		\n\t\t\t

Firm

\n\t\t\t		\n\t\t\t

Participated lawyers in the project among the recommended personnel (full name)

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		 \n\t\t\t

 

\n\t\t\t		   \n\t\t\t

 

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		 \n\t\t\t

 

\n\t\t\t		   \n\t\t\t

 

\n\t\t\t
\n\t\t\t

…

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

…

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

…

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

10

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\n

 

\n\n\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Project Title

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Country / Region

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Start Date

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Completion Date

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Continuous / Intermittent

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Client

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Participated lawyers in the project among the recommended personnel (full name)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Funding Source

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Project description

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

The role of the consulting firm

\n\t\t\t		\n\t\t\t

(indicate your role and contribution in terms of men-months)

\n\t\t\t
\n\n\n\n

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

\n\n\n\n\n\n\n\n\n\n

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.

\n\n

Terms of Reference (TOR) for development and implementation of an automated system of accounting and monitoring for the activities of SOEs

\n\n

 

\n\n
    \n\t
  1. GENERAL INFORMATION\n\n\t
      \n\t\t
    1. Full name of the project and its symbol
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

 

\n\n

Purchasers Ministry of Economy and Finance of the Republic of Uzbekistan- - manages administrative and financial issues.

\n\n

The final beneficiary of the project is the State Assets Management Agency of the Republic of Uzbekistan (hereinafter referred to as the " Agency").

\n\n

Requisites:

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Supplier
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

Basic requirements for the Supplier:

\n\n\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

The role of the specialist

\n\t\t\t		\n\t\t\t

Requirements

\n\t\t\t
\n\t\t\t

BI Project Manager

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Experience with BI for at least 5 years;
    • \n\t\t\t\t
  • Experience in managing at least two BI projects;
    • \n\t\t\t\t
  • Possession of a full range of knowledge and skills of project management;
    • \n\t\t\t\t
  • Experience in managing a project team of 15 people.
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

BI project architector

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Experience with BI for at least 5 years;
    • \n\t\t\t\t
  • Experience of participation in at least two projects for the development and implementation of BI class systems;
    • \n\t\t\t\t
  • Knowledge of programming languages on the database server;
    • \n\t\t\t\t
  • Experience in the design of class BI systems.
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

BI Functional Consultant

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Experience with BI class systems for at least 3 years;
    • \n\t\t\t\t
  • Experience in participating in projects for the development and implementation of class BI systems;
    • \n\t\t\t\t
  • Knowledge of programming languages on the database server;
    • \n\t\t\t\t
  • Experience in preparing technical documentation.
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

Financial consultant BI

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Experience with BI class systems for at least 3 years;
    • \n\t\t\t\t
  • Experience in participating in projects for the development and implementation of class BI systems;
    • \n\t\t\t\t
  • Experience in financial analysis projects in various sectors of the economy - at least 3x;
    • \n\t\t\t\t
  • Knowledge of IFRS reporting.
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

BI Technical Consultant

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Experience in working with data warehouses and BI class systems for at least 3 years;
    • \n\t\t\t\t
  • Experience in participating in projects for the development of data warehouses and implementation of BI class systems;
    • \n\t\t\t\t
  • Knowledge of programming languages on the database server;
    • \n\t\t\t\t
  • Experience in the preparation of technical documentation for the developed solutions.
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

DBMS administrator

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Experience with BI for at least 3 years;
    • \n\t\t\t\t
  • Experience participating in at least 3 similar projects as a DB / BI administrator;
    • \n\t\t\t\t
  • Experience in administering BI environments.
    • \n\t\t\t
\n\t\t\t
\n\n

 

\n\n\n\n

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:

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Basis for development
      2. \n\t
    \n\t
    2. \n
\n\n

The basis for the development of the System project is:

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Planned start and finish dates
      2. \n\t
    \n\t
    2. \n
\n\n

Planned project implementation timeline:

\n\n

Start: October, 2024 

\n\n

Completion: October 2025

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Sources of financing
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. The procedure for registration and presentation of the results of work
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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

\n\n

To the Acceptance Commission, the Supplier submits documentation, the list
\nand requirements for registration of which are determined in accordance with State standards (GOST/ГОСТ) and other standards, and governing documents in force in the territory of the Republic of Uzbekistan, as well as by mutual agreement of the Agencyand the Supplier.

\n\n

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

\n\n

 

\n\n
    \n\t
  1. PURPOSE OF THE SYSTEM AND OBJECTIVES OF PROJECT IMPLEMENTATION
    2. \n
\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Purpose of the system
      2. \n\t
    \n\t
    2. \n
\n\n

The main purpose of the information system for accounting and monitoring the activities of SOEs 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 Agencyand enterprises with a state share, regardless of the source of such information. This information can come from the following data sources:

\n\n\n\n

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

\n\n\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Project implementation goals
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

The purpose of introducing a business analysis system is to improve the efficiency of management of the operation and development of the Agency'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.

\n\n

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.

\n\n

The purpose of the system is:

\n\n\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Expected deliverables
      2. \n\t
    \n\t
    2. \n
\n\n

 

\n\n\n\n
    \n\t
  1. CHARACTERISTICS OF THE INFORMATION OBJECT
    2. \n
\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. General information
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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

\n\n\n\n

 

\n\n

Also, the main participants in the project are:

\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n

Republican Stock Exchange - supplier of information on securities;

\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Architecture and composition of the current solution.
      2. \n\t
    \n\t
    2. \n
\n\n

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:

\n\n\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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

\n\n

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.

\n\n

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

\n\n

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.

\n\n

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

\n\n

 

\n\n


\np. 3.2.1 Architecture of the current solution.

\n\n

 

\n\n

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

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

System name

\n\t\t\t		\n\t\t\t

System Description

\n\t\t\t		\n\t\t\t

Data retrieval method

\n\t\t\t
\n\t\t\t

Internal systems of the Agency

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

IS "State Property"

\n\t\t\t		\n\t\t\t

Existing IS of business analysis

\n\t\t\t		\n\t\t\t

The existing IS "State Property" receives data from the Agency's database

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Agency DB

\n\t\t\t		\n\t\t\t

Existing DB

\n\t\t\t		\n\t\t\t

Formed database. The accumulation of the database comes from all of the following sources. The depth of historical data is 4 years.

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

www.property.davaktiv.uz

\n\t\t\t		\n\t\t\t

Register of state property of registration and submission of reports for legal entities in the form of state unitary enterprises and state enterprises.

\n\t\t\t		\n\t\t\t

Filling out forms posted on the web platform is carried out by enterprises in manual mode.

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

www.kpi.davaktiv.uz

\n\t\t\t		\n\t\t\t

Information portal for submitting reports by joint-stock companies and other business entities in the form of JSCs, LLCs, enterprises with a state share.

\n\t\t\t		\n\t\t\t

Filling out forms posted on the web platform is carried out by enterprises in manual mode.

\n\t\t\t
\n\t\t\t

External systems

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

STC DB

\n\t\t\t		\n\t\t\t

State Tax Committee database

\n\t\t\t		\n\t\t\t

Data collection from the STC DB collected on an automatic basis.

\n\t\t\t
\n\n

Tab. 3.2.1 Composition of internal and external systems.

\n\n

 

\n\n

The composition of the reporting forms (Table 3.2.2)

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Accepted reporting forms

\n\t\t\t
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Organizational and legal form

\n\t\t\t		\n\t\t\t

Reporting forms

\n\t\t\t		\n\t\t\t

Periodicity

\n\t\t\t		\n\t\t\t

Fill / receive method

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

•      Joint Stock Company (JSC);

\n\n\t\t\t

•      Limited Liability Company (LLC);

\n\n\t\t\t

•       Unitary enterprises (GUP)

\n\t\t\t		\n\t\t\t

Reporting forms according to national accounting standards (NAS)

\n\n\t\t\t

•      Form No. 1 (small and medium enterprises)

\n\n\t\t\t

•      Form No. 2 (small and medium enterprises)

\n\n\t\t\t

•      Form No. 4 (Large enterprises)

\n\n\t\t\t

•      Form No. 5 (Large enterprises)

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Accepted by the Agency in automatic mode from the database of the STC

\n\t\t\t
\n\t\t\t

Key performance indicators (KPI) reporting form

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Filled in by enterprises manually on the web platform www.kpi.davaktiv.uz

\n\t\t\t
\n\t\t\t

Key performance indicators (KPI) reporting form for the financial and banking sector

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Filled in by enterprises manually on the web platform www.kpi.davaktiv.uz

\n\t\t\t
\n\t\t\t

Key performance indicators (KPI) reporting form for insurance companies

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Filled in by enterprises manually on the web platform www.kpi.davaktiv.uz

\n\t\t\t
\n\t\t\t

Reporting form - business plan

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Filled in by enterprises manually on the web platform www.kpi.davaktiv.uz

\n\t\t\t
\n\t\t\t

Reporting form according to international financial reporting standards (IFRS) for enterprises

\n\n\t\t\t

•      Statement of financial position

\n\n\t\t\t

•      Statement of comprehensive income

\n\n\t\t\t

•      Cash flow statement

\n\n\t\t\t

•      Statement of changes in equity

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Tax Committee Database

\n\t\t\t
\n\t\t\t

Reporting form according to international financial reporting standards (IFRS) for the financial and banking sector

\n\n\t\t\t

•      Statement of financial position

\n\n\t\t\t

•      Profit or loss statement

\n\n\t\t\t

•      Statement of comprehensive income

\n\n\t\t\t

•      Cash flow statement

\n\n\t\t\t

•      Statement of changes in equity

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Tax Committee Database

\n\t\t\t
\n\t\t\t

Management reporting

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Management reporting forms

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Formed in the IS "State Property"

\n\t\t\t
\n\n

Tab. 3.2.2 Composition of reporting forms

\n\n

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

\n\n

 

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

TAS-IX Network

\n\t\t\t
\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

МСПД (interstate data transmission system)

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Firewall all

\n\t\t\t
\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Local computing

\n\n\t\t\t

network

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Applications server

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Database server

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Backup Applications

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Backup databases

\n\t\t\t
\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

p. 3.2.2. logical diagram of the existing technical complex

\n\n

 

\n\n

 

\n\n

 

\n\n

Key technical specifications for Application Server and Database Server:

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Applications server

\n\t\t\t
\n\t\t\t

Fujitsu Database Server Primary rx2530 m4

\n\t\t\t		\n\t\t\t

CPU Intel Xeon Silver 4110 8c 2.10 GHz 2x

\n\n\t\t\t

DDR4 32GB

\n\n\t\t\t

HDD SATA 6G 1TBx4 SSD 256Gbx2

\n\n\t\t\t

 OS / Oracle Linux Unbreakable

\n\n\t\t\t

PSU 800W 2x

\n\n\t\t\t

LANs

\n\n\t\t\t

I350-AM2 (Onboard on D3383-A1x, on D3383-C1x

\n\n\t\t\t

Intel® C620 Chipset (1Gb / 10Gb Ethernet) (Onboard on D3383-C1x, on D3383-A1x)

\n\t\t\t
\n\t\t\t

Database server

\n\t\t\t
\n\t\t\t

Fujitsu Database Server Primary rx2530 m4

\n\t\t\t		\n\t\t\t

CPU Intel Xeon Silver 4110 8c 2.10 GHz 2x

\n\n\t\t\t

DDR4 32GB

\n\n\t\t\t

HDD SATA 6G 1TBx4 SSD 256Gbx2

\n\n\t\t\t

 OS / Oracle Linux Unbreakable

\n\n\t\t\t

PSU 800W 2x

\n\n\t\t\t

LANs

\n\n\t\t\t

I350-AM2 (Onboard on D3383-A1x, on D3383-C1x

\n\n\t\t\t

Intel® C620 Chipset (1Gb / 10Gb Ethernet) (Onboard on D3383-C1x, on D3383-A1x)

\n\t\t\t
\n\n

 Main challenges in working with the current information system:

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Organizational scope of the project
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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

\n\n

 

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

State Assets Management Agency

\n\n\t\t\t

of the Republic of Uzbekistan

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Rep. of Karakalpakstan

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Andijan region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Jizzakh region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Navoi region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Samarkand region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Syrdarya region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Khorezm region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Tashkent city

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Bukhara region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Kashkadarya region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Namangan region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Surkhandarya region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Ferghana region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Tashkent region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Total departments: 14

\n\n\t\t\t

Central department: 1

\n\t\t\t
\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Process volume\n\n\t\t
        \n\t\t\t
      1. Optimization and automation of business processes
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

 

\n\n
    \n\t
  1. SYSTEM REQUIREMENTS\n\n\t
      \n\t\t
    1. System requirements as a whole
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

The system should include the following subsystems:

\n\n\n\n

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

\n\n\n\n

 The system should be organized as follows:

\n\n\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the structure and functioning of the system
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

The system should provide high interactivity of work
\nwith 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).

\n\n

General system requirements.

\n\n

The system should be able to:

\n\n\n\n

 

\n\n

The system should contain the following subsystems:

\n\n\n\n

 

\n\n

The reporting forms issued by the System must include:

\n\n\n\n

p 4.1. General software architecture

\n\n

 

\n\n

Basic functional principles of the system

\n\n

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

\n\n\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the component composition and architecture of the solution
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

For the functioning of the System, the data will be loaded
\nfrom the existing DBMS of the Agency.

\n\n

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.

\n\n

The main components of the platform:

\n\n\n\n\n\n

The system under development should include the following technological components:

\n\n\n\n

 

\n\n

 

\n\n

Рис. 4.1.1.2.1. Hi-level architecture of the system of accounting and monitoring of the activities of SOEs

\n\n

More detailed requirements are indicated in clauses 4.1.9 and 4.2.

\n\n

 

\n\n

Requirements for modes of operation

\n\n

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:

\n\n

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

\n\n

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

\n\n\n\n

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.).

\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. List and description of scenarios for using information systems
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

The use of the System implies the following scenario:

\n\n

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

\n\n

The model includes two main scenarios:

\n\n\n\n\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

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

\n\t\t\t
\n\n


\n General model of using IS scripts:

\n\n

 

\n\n

p. 4.1.4.1 “General Scenario Model”

\n\n

 

\n\n

 

\n\n

p. 4.1.4.2 “Script Action Diagram”

\n\n

 

\n\n

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

\n\n

This scenario implies the receipt by the User of the Agency's management of data from SOEs, 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.

\n\n

Process steps:

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

 

\n\n\n\n

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.

\n\n

Process steps:

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

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. System Diagnostic Requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the possibility of modernization and development of the system
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for interaction with third-party information systems
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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:

\n\n\n\n

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

\n\n

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

\n\n

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

\n\n

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.

\n\n

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

\n\n\n\n

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.

\n\n

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.

\n\n

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the number and qualifications of system personnel and their mode of work
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. \n\t\t\t
          \n\t\t\t\t
        1. Requirements for the number of personnel (users) of IS
          2. \n\t\t\t
        \n\t\t\t
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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 Supplier at the stage of the Terms of Reference and is agreed upon by the protocol with the Agency. 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.

\n\n

 

\n\n

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

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Department / Management

\n\t\t\t		\n\t\t\t

Position

\n\t\t\t		\n\t\t\t

Number of users, people

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Internal departments of UzSAMA

\n\t\t\t		\n\t\t\t

Director, head, deputy

\n\t\t\t		\n\t\t\t

30

\n\t\t\t
\n\t\t\t

Specialist, employee

\n\t\t\t		\n\t\t\t

70

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Territorial administrations

\n\t\t\t		\n\t\t\t

Director, head, deputy

\n\t\t\t		\n\t\t\t

20

\n\t\t\t
\n\t\t\t

Specialist, employee

\n\t\t\t		\n\t\t\t

40

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Other users of Ministries and departments

\n\t\t\t		\n\t\t\t

Director, head, deputy

\n\t\t\t		\n\t\t\t

10

\n\t\t\t
\n\t\t\t

Specialist, employee

\n\t\t\t		\n\t\t\t

20

\n\t\t\t
\n\t\t\t

Observer

\n\t\t\t		\n\t\t\t

10

\n\t\t\t
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Total

\n\t\t\t		\n\t\t\t

Director, head, deputy

\n\t\t\t		\n\t\t\t

60

\n\t\t\t
\n\t\t\t

Specialist, employee

\n\t\t\t		\n\t\t\t

130

\n\t\t\t
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Observer

\n\t\t\t		\n\t\t\t

10

\n\t\t\t
\n\n

Table 4.1.7.1. Planned number of users of the System

\n\n

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.

\n\n

 

\n\n

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

\n\n

Observer role: viewing reports;

\n\n\n\n

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

\n\n

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

\n\n

• 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).

\n\n

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

\n\n

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.

\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. \n\t\t\t
          \n\t\t\t\t
        1. \n\t\t\t\t
            \n\t\t\t\t\t
          1. Required mode of operation of IS personnel
            2. \n\t\t\t\t
          \n\t\t\t\t
          2. \n\t\t\t
        \n\t\t\t
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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

\n\n

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:

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Indicators of appointment
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n\n\n

System performance: 

\n\n\n\n

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

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

The name of the purpose indicators

\n\t\t\t		\n\t\t\t

Explanation

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Reliability indicators

\n\t\t\t		\n\t\t\t

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

\n\t\t\t
\n\t\t\t

1.1

\n\t\t\t		\n\t\t\t

Validity

\n\t\t\t		\n\t\t\t

The system must meet the stated goals and functional requirements of the technical specifications

\n\t\t\t
\n\t\t\t

1.2

\n\t\t\t		\n\t\t\t

Security

\n\t\t\t		\n\t\t\t

The system must be able to prevent unauthorized access to data

\n\t\t\t
\n\t\t\t

1.3

\n\t\t\t		\n\t\t\t

Operability

\n\t\t\t		\n\t\t\t

The system should function in the specified modes in the absence of destabilizing influences

\n\t\t\t
\n\t\t\t

1.4

\n\t\t\t		\n\t\t\t

Consistency

\n\t\t\t		\n\t\t\t

The system and documentation must have unambiguous, consistent descriptions for the same objects, functions, terms, definitions, etc.

\n\t\t\t
\n\t\t\t

1.5

\n\t\t\t		\n\t\t\t

Sustainability

\n\t\t\t		\n\t\t\t

The system must have the ability to ensure continued operation of the System after the occurrence of deviations caused by destabilizing influences

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Performance indicators

\n\t\t\t		\n\t\t\t

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 

\n\t\t\t
\n\t\t\t

2.1

\n\t\t\t		\n\t\t\t

Performance

\n\t\t\t		\n\t\t\t

The system must be able to perform actions in the time interval that meets the specified requirements

\n\t\t\t
\n\t\t\t

2.2

\n\t\t\t		\n\t\t\t

Profitability

\n\t\t\t		\n\t\t\t

The system must be able to operate on the minimum resources of the System

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Manufacturability indicators

\n\t\t\t		\n\t\t\t

They characterize the technological aspects that make it easy to eliminate errors in the System

\n\t\t\t
\n\t\t\t

3.1

\n\t\t\t		\n\t\t\t

Modifiability

\n\t\t\t		\n\t\t\t

The system should be capable of providing ease of making the necessary changes and improvements to the System during operation.

\n\t\t\t
\n\t\t\t

3.2

\n\t\t\t		\n\t\t\t

Repeatability

\n\t\t\t		\n\t\t\t

The System should use typical design solutions or components

\n\t\t\t
\n\t\t\t

3.3

\n\t\t\t		\n\t\t\t

Structurality

\n\t\t\t		\n\t\t\t

The system should consist of complexes that perform interrelated functions

\n\t\t\t
\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Reliability requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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.

\n\n

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

\n\n

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

\n\n

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

\n\n\n\n

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

\n\n\n\n

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

\n\n\n\n

The reliability of the system being created is ensured by:

\n\n\n\n

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

\n\n\n\n

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

\n\n

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

\n\n

  

\n\n

Values of reliability indicators

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Index

\n\t\t\t		\n\t\t\t

Meaning

\n\t\t\t
\n\t\t\t

The whole system

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Time to identify and neutralize current threats to information security

\n\t\t\t		\n\t\t\t

no more than 5 hours (provided that the data is saved in the System)

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Recovery time of parameters of normal functioning after the implementation of a computer attack

\n\t\t\t		\n\t\t\t

no more than 10 hours (provided that the data is saved in the System)

\n\t\t\t
\n\t\t\t

Data visualization subsystem

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Reliability

\n\t\t\t		\n\t\t\t

10,000 hours

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Availability ratio

\n\t\t\t		\n\t\t\t

0.9995

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Availability

\n\t\t\t		\n\t\t\t

99.95%

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Data loss tolerance

\n\t\t\t		\n\t\t\t

1 hour in (provided that the data is saved in the System)

\n\t\t\t
\n\t\t\t

Subsystem of distribution of roles and differentiation of access rights

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Reliability

\n\t\t\t		\n\t\t\t

6000 hours

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Availability ratio

\n\t\t\t		\n\t\t\t

0.99

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Availability

\n\t\t\t		\n\t\t\t

99.9%

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Data loss tolerance

\n\t\t\t		\n\t\t\t

12 hours

\n\t\t\t
\n\n

Tab. 4.1.8.1 Values of reliability indicators

\n\n

 

\n\n

Composition of reliability indicators for the System

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Index

\n\t\t\t		\n\t\t\t

Description

\n\t\t\t
\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Availability

\n\t\t\t		\n\t\t\t

Ability Systems perform coordinated function to within a specified time ((time operation systems - while idle) / time operation Systems * 100). Measured as a percentage

\n\t\t\t
\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Availability ratio

\n\t\t\t		\n\t\t\t

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

\n\t\t\t
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Data loss tolerance

\n\t\t\t		\n\t\t\t

Allowable period of time for which System data may be lost . Measured in hours

\n\t\t\t
\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Time to recovery

\n\t\t\t		\n\t\t\t

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  

\n\t\t\t
\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Reliability

\n\t\t\t		\n\t\t\t

The property of the System to continuously maintain an operational state for some time, or

\n\n\t\t\t

developments. Measured in hours

\n\t\t\t
\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Time identifying and neutralization of actual threats to information security

\n\t\t\t		\n\t\t\t

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 .

\n\n\t\t\t

Measured in hours

\n\t\t\t
\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Restoration time of parameters of normal operation      after

\n\n\t\t\t

implementation of a computer attack

\n\t\t\t		\n\t\t\t

The duration of the restoration of the System 's operational state after the implementation of a computer attack.

\n\n\t\t\t

Measured in hours

\n\t\t\t
\n\n

Tab. 4.1.8.2 Composition of reliability indicators for the System

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Safety requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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

\n\n

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

\n\n

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. \n\t\t\t
          \n\t\t\t\t
        1. Requirements for protecting information from unauthorized access
          2. \n\t\t\t
        \n\t\t\t
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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 SOEs.

\n\n

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

\n\n

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

\n\n\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. \n\t\t\t
          \n\t\t\t\t
        1. Requirements for the differentiation of access rights
          2. \n\t\t\t
        \n\t\t\t
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. \n\t\t\t
          \n\t\t\t\t
        1. Requirements for the safety of information in case of accidents
          2. \n\t\t\t
        \n\t\t\t
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

The system of accounting and monitoring of the activities of SOEs should provide for the means of backing up, archiving and restoring data.

\n\n

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.

\n\n

Emergency situations for which the safety of information in the System for recording and monitoring the activities of SOEs should be ensured:

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Characteristics of the emergency

\n\t\t\t		\n\t\t\t

Measures to ensure the safety of information in the System

\n\t\t\t		\n\t\t\t

Emergency elimination time

\n\t\t\t
\n\t\t\t

Power outage

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Application of uninterruptible power supply devices;
    • \n\t\t\t\t
  • Application of stand-alone alternators.
    • \n\t\t\t
\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Equipment support for at least 20 minutes;
    • \n\t\t\t\t
  • Automatic start within no more than 15-30 seconds
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

Failure (failure) of hard disk drives (disk array) of the server

\n\t\t\t		\n\t\t\t

Backing up data to external media

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Organization of disk arrays using the technology of RAID levels 0, 1, 5 or 10;
    • \n\t\t\t\t
  • Storage and automatic redistribution of information to spare disks for at least 20 minutes
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

Failure (failure) of the server (processor, power supply, RAM, etc.)

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Carrying out diagnostics of the state of technical means using the tools supplied as part of the technical means;
    • \n\t\t\t\t
  • Duplication of critical server elements
    • \n\t\t\t
\n\t\t\t		\n\t\t\t

Automatic transition of all functioning systems to a backup platform

\n\t\t\t
\n\t\t\t

Failure (failure) of the system software

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Diagnostics of the state of the system software using the tools supplied as part of the system software;
    • \n\t\t\t\t
  • Backing up data to external media
    • \n\t\t\t
\n\t\t\t		\n\t\t\t

Restore a saved backup within 15 minutes

\n\t\t\t
\n\n

 

\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. \n\t\t\t
          \n\t\t\t\t
        1. Requirements for protection against the influence of external influences
          2. \n\t\t\t
        \n\t\t\t
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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

\n\n

 

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Ergonomic and technical aesthetics requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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.

\n\n

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".

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the operation, maintenance, repair and storage of system components
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

The system must be designed for operation as part of the Agency'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
\nand organizational means of the Agency.

\n\n

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

\n\n

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

\n\n

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

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

  

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for patent and license purity
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n

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.

\n\n

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

\n\n

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

\n\n

The System must use licensed software.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for standardization and unification
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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.

\n\n

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

\n\n

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.

\n\n

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

\n\n

Communication should include:

\n\n\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the degree of adaptability of the system to changes
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n\n\n

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

\n\n\n\n

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Software technical support requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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

\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Requirements for the functions (tasks) performed by the Information System
      2. \n\t
    \n\t
    2. \n
\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the functions (tasks) performed by the System for recording and monitoring the activities of SOEs.
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

The information system for accounting and monitoring the activities of SOEs will be designated from the following subsystems:

\n\n\n\n

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:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Function

\n\t\t\t		\n\t\t\t

Task

\n\t\t\t
\n\t\t\t

The form

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Grouping data in different sections defined by the data hierarchy down to the lowest level of detail;
    • \n\t\t\t\t
  • Grouping data from different levels of the hierarchy;
    • \n\t\t\t\t
  • Creation and saving of fixed groupings of data available in subsequent sessions of work with the system after the completion of the current one;
    • \n\t\t\t\t
  • Creation of templates defining the sequential steps of the analysis with the support of the interactive mode;
    • \n\t\t\t\t
  • Ranking, sorting and filtering by various categories and indicators;
    • \n\t\t\t\t
  • Creation of multi-section reports with different levels of data grouping;
    • \n\t\t\t\t
  • Creation of a set of standard report templates that make it easier for the user to build standard reports;
    • \n\t\t\t\t
  • Setting the parameters of reports in the interactive mode;
    • \n\t\t\t
\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Analysis

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Flexible data manipulation;
    • \n\t\t\t\t
  • Data scaling (drill-down);
    • \n\t\t\t\t
  • Possibilities of data aggregation by arbitrary indicators;
    • \n\t\t\t\t
  • Support for the ability to display monetary amounts in more than one currency with the ability to quickly recalculate;
    • \n\t\t\t\t
  • Ranking values ​​of measurement categories by values ​​of indicators;
    • \n\t\t\t\t
  • Analysis of trends over time;
    • \n\t\t\t
\n\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Performance

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Pie charts;
    • \n\t\t\t\t
  • Column charts are two-dimensional;
    • \n\t\t\t\t
  • Column charts are three-dimensional;
    • \n\t\t\t\t
  • Line charts;
    • \n\t\t\t\t
  • Scatter plots;
    • \n\t\t\t\t
  • Simultaneous output of data in tabular and graphical form;
    • \n\t\t\t\t
  • Formation of balanced and unbalanced nested pivot tables;
    • \n\t\t\t\t
  • Calculations over the values ​​of indicators for arbitrary groups of measurement categories;
    • \n\t\t\t\t
  • Conditional formatting of indicators depending on their values;
    • \n\t\t\t\t
  • Displaying indicators in the form of absolute values ​​and shares of total values;
    • \n\t\t\t\t
  • Export of slices of multidimensional cubes in various formats.
    • \n\t\t\t
\n\t\t\t
\n\n

 

\n\n

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

\n\n\n\n

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

\n\n

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.

\n\n

 

\n\n

List of reporting forms:

\n\n

Table 4.2.1 - Forms of reporting in accordance with NAS

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Form No. 1 - balance sheet

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Long-term assets

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Current assets

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Sources of own funds

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Commitments

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Certificate of availability of valuables recorded on off-balance sheet accounts

\n\t\t\t
\n\t\t\t

6

\n\t\t\t		\n\t\t\t

Deciphering overdue receivables and payables - overdue receivables

\n\t\t\t
\n\t\t\t

7

\n\t\t\t		\n\t\t\t

Overdue payables

\n\t\t\t
\n\t\t\t

Form No. 2 - Statement of financial results

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Form -2

\n\t\t\t
\n\t\t\t

Form No. 4 - statement of cash flows

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Operating activities

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Investment activities

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Financial activities

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Taxation

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Statement of cash flow in foreign currency

\n\t\t\t
\n\t\t\t

Form No. 5 - statement of equity capital

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Form No. 5

\n\t\t\t
\n\n

Table 4.2.2 - Forms of reporting on key performance indicators.

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Key Performance Indicators - Industrial

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

List of key KPIs

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

List of additional key performance indicators

\n\t\t\t
\n\t\t\t

Key performance indicators - banking sector

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Indicators of assets and liabilities

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Compliance with normative indicators in the bank

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Financial performance

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Trust Fund Tax and Payments

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Distribution of net profit

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

External credit lines / Eurobonds

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Sponsorship

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Amount of workers

\n\t\t\t
\n\t\t\t

Key performance indicators - insurance companies

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Indicators of assets and liabilities

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Compliance with normative indicators

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Financial performance

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Trust Fund Tax and Payments

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Distribution of net profit

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

External debt

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Sponsorship

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Amount of workers

\n\t\t\t
\n\n

 

\n\n

Table 4.2.3- Reporting forms - business plan

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Business plan

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Production facilities (works and services)

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Production volume (Works and services)

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Financial performance

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Taxes and payments to trust funds

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Distribution of net profit

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Debentures

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

External debt

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Foreign trade and foreign economic activity of the enterprise.

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Important performance indicators

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Production of products included in the localization program

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Investment projects.

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Sponsorship

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

The number of employees

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Management and control bodies of SOEs

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Changes in the composition of the supervisory board, the executive body of the audit commission.

\n\t\t\t
\n\n

 

\n\n

 

\n\n

Table 4.2.4 - Management reporting forms

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Management reporting

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Information on the production indicators of enterprises

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Production indicators

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Financial performance

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

About business plans of SOEs

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

On the state of the analysis of the activities of SOEs

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Payment of dividends by SOEs

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

According to the results of 9 months of the reporting year, state enterprises operating in the territory of the republic.

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Financial recovery of SOEs

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Information about the labor resources of enterprises

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Production of products included in the localization program

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Investment projects.

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Sponsorship

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

The number of employees

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Management and control bodies of SOEs

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Changes in the composition of the supervisory board, the executive body of the audit commission.

\n\t\t\t
\n\n

 

\n\n

Table 4.2.5 - Preliminary reporting forms in accordance with IFRS

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Preliminary IFRS reporting forms - enterprises

\n\t\t\t
\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Statement of financial position

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Statement of comprehensive income

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Statement of changes in equity

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Cash flow statement (direct method)

\n\t\t\t
\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 

\n\n\t\t\t

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

\n\t\t\t
\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Statement of financial position

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Statement of comprehensive income

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Profit or loss statement

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Statement of changes in equity

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Cash flow statement

\n\t\t\t
\n\n

 

\n\n

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.).

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

p. 4.2.1 – Example of visualization of predictive analysis

\n\n

 

\n\n

 

\n\n

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

\n\n

 

\n\n

 

\n\n

 

\n\n

p. 4.2.1 – An example of KPI visualization

\n\n

Time schedule for the implementation of each function, tasks:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Interim regulation requirements

\n\t\t\t		\n\t\t\t

Task

\n\t\t\t
\n\t\t\t

The entire period of operation of the system upon user initiation

\n\t\t\t		\n\t\t\t

Grouping data in different sections defined by the data hierarchy down to the lowest level of detail;

\n\t\t\t
\n\t\t\t

Grouping data from different levels of the hierarchy;

\n\t\t\t
\n\t\t\t

Creation and saving of fixed groupings of data available in subsequent sessions of work with the system after the completion of the current one;

\n\t\t\t
\n\t\t\t

Creation of templates defining the sequential steps of the analysis with the support of the interactive mode;

\n\t\t\t
\n\t\t\t

Ranking, sorting and filtering by various categories and indicators;

\n\t\t\t
\n\t\t\t

Creation of multi-section reports with different levels of data grouping;

\n\t\t\t
\n\t\t\t

Ranking values ​​of measurement categories by values ​​of indicators;

\n\t\t\t
\n\t\t\t

Analysis of trends over time;

\n\t\t\t
\n\t\t\t

Pie charts;

\n\t\t\t
\n\t\t\t

Column charts are two-dimensional;

\n\t\t\t
\n\t\t\t

Column charts are three-dimensional;

\n\t\t\t
\n\t\t\t

Line charts;

\n\t\t\t
\n\t\t\t

Scatter plots;

\n\t\t\t
\n\t\t\t

Simultaneous output of data in tabular and graphical form;

\n\t\t\t
\n\t\t\t

Formation of balanced and unbalanced nested pivot tables;

\n\t\t\t
\n\t\t\t

Calculations over the values ​​of indicators for arbitrary groups of measurement categories;

\n\t\t\t
\n\t\t\t

Conditional formatting of indicators depending on their values;

\n\t\t\t
\n\t\t\t

Displaying indicators in the form of absolute values ​​and shares of total values;

\n\t\t\t
\n\t\t\t

Export of slices of multidimensional cubes in various formats.

\n\t\t\t
\n\t\t\t

The entire period of operation of the system

\n\t\t\t		\n\t\t\t

Creation of a set of standard report templates that make it easier for the user to build standard reports;

\n\t\t\t
\n\t\t\t

Setting the parameters of reports in the interactive mode;

\n\t\t\t
\n\t\t\t

Flexible data manipulation;

\n\t\t\t
\n\t\t\t

Data scaling (drill-down);

\n\t\t\t
\n\t\t\t

Possibilities of data aggregation by arbitrary indicators;

\n\t\t\t
\n\n

Requirements for the quality of implementation of functions, tasks.

\n\n

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

\n\n

 

\n\n

 

\n\n

List of failure criteria for each function:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Function

\n\t\t\t		\n\t\t\t

Refusal criteria

\n\t\t\t		\n\t\t\t

Recovery time

\n\t\t\t		\n\t\t\t

Availability ratio

\n\t\t\t
\n\t\t\t

The form

\n\t\t\t		\n\t\t\t

One of the tasks of the function is not being performed.

\n\t\t\t		\n\t\t\t

8 ocloc'k

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

0.85

\n\t\t\t
\n\t\t\t

Analysis

\n\t\t\t		\n\t\t\t

One of the tasks of the function is not being performed.

\n\t\t\t		\n\t\t\t

12 hours

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

0.75

\n\t\t\t
\n\t\t\t

Performance

\n\t\t\t		\n\t\t\t

One of the tasks of the function is not being performed.

\n\t\t\t		\n\t\t\t

12 hours

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

0.75

\n\t\t\t
\n\n

 

\n\n

 

\n\n

 

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

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

\n\n

The subsystem should perform the following functions:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Function

\n\t\t\t		\n\t\t\t

Task

\n\t\t\t
\n\t\t\t

User management and monitoring

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • User management;
    • \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • Provision of routine maintenance provided for by the operational documentation for the software product;
    • \n\t\t\t\t
  • Resolution of problems arising during the operation of the software product;
    • \n\t\t\t\t
  • Elimination of emergency situations (incidents) arising during the operation of the software product;
    • \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • Monitoring the work of users of the software product and means for interacting with them;
    • \n\t\t\t\t
  • Monitoring of the parameters of the functioning of the software product;
    • \n\t\t\t\t
  • Procedures for managing the operation of a software product;
    • \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • The possibility of deleting information about users registered in the software product, including blocked ones, must be excluded;
    • \n\t\t\t\t
  • The possibility of changing (modifying) demo data (last name, first name, patronymic) of the established users must be excluded;
    • \n\t\t\t\t
  • The implementation of the administration mechanism should not reveal the logic of building the database of the software product;
    • \n\t\t\t\t
  • Users who do not have business roles (Administrator, Operator, etc.) should not be able to change the business data of the software product.
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

Access rights management

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • The mechanism for differentiating access rights should ensure that the employee can launch only the functions allowed to him.
    • \n\t\t\t
\n\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Identification and authentication mechanisms

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • 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);
    • \n\t\t\t\t
  • 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.  
    • \n\t\t\t
\n\t\t\t
\n\n

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

\n\n

Requirements for the quality of implementation of functions, tasks.

\n\n

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

\n\n

List of failure criteria for each function:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Function

\n\t\t\t		\n\t\t\t

Refusal criteria

\n\t\t\t		\n\t\t\t

Recovery time

\n\t\t\t		\n\t\t\t

Availability ratio

\n\t\t\t
\n\t\t\t

User management and monitoring

\n\t\t\t		\n\t\t\t

One of the tasks of the function is not being performed.

\n\t\t\t		\n\t\t\t

12 hours

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

0.75

\n\t\t\t
\n\t\t\t

Access rights management

\n\t\t\t		\n\t\t\t

One of the tasks of the function is not being performed.

\n\t\t\t		\n\t\t\t

12 hours

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

0.75

\n\t\t\t
\n\t\t\t

Identification and authentication mechanisms

\n\t\t\t		\n\t\t\t

One of the tasks of the function is not being performed.

\n\t\t\t		\n\t\t\t

8 ocloc'k

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

0.85

\n\t\t\t
\n\n

 

\n\n

 

\n\n\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Requirements to types of support\n\n\t\t
        \n\t\t\t
      1. Requirements for software
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

The software of the System should include:

\n\n

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

\n\n\n\n

Software algorithms must meet the following requirements:

\n\n\n\n

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. 

\n\n

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.

\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Information support requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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.

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for information exchange between system components
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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.

\n\n

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

\n\n

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:

\n\n\n\n

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.

\n\n

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Linguistic requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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:

\n\n\n\n

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.

\n\n

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

\n\n

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

\n\n

 

\n\n

 

\n\n\n\n

The System software must have the following characteristics:

\n\n\n\n

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 Agency.

\n\n

All software must be guaranteed for at least 1 year.

\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for metrological support
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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”.

\n\n

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

\n\n

There are no additional requirements for metrological support.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for technical support
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

There are no requirements for the existing technical support.

\n\n

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.

\n\n

The hardware, standard software, and network equipment for the implementation of the project are provided by the Agency

\n\n

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. 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for methodological support
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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 Supplier based on the results of a preliminary survey of the Agency's IT structure and are agreed with the Agency.

\n\n

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

\n\n

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

\n\n

The methodological support includes:

\n\n\n\n

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

\n\n

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

\n\n\n\n

The Supplier 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 Agency (the date of the signing by the Agencyof the Certificate of Acceptance of Works).

\n\n

The Supplier is responsible for defects and deficiencies found during the warranty period. In case of revealing defects and deficiencies during the warranty period, the Supplier 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 Agencyand the Supplier, but should not exceed one month.

\n\n
    \n\t
  1. SCOPE AND CONTENT OF THE SYSTEM IMPLEMENTATION WORKS
    2. \n
\n\n

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.

\n\n

Preliminary stages of work (table 5.1):

\n\n

 

\n\n

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

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Stage number

\n\t\t\t		\n\t\t\t

Name of works and their content

\n\t\t\t		\n\t\t\t

Deadline

\n\t\t\t		\n\t\t\t

Supplier (organization)

\n\t\t\t		\n\t\t\t

How the stage ends

\n\t\t\t
\n\t\t\t

Start

\n\t\t\t		\n\t\t\t

The ending

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Formation of requirements for the System:

\n\n\t\t\t
    \n\t\t\t\t
  1. Initial survey of the facility and justification of the need for the System;
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

October 2024

\n\t\t\t		\n\t\t\t

November

\n\n\t\t\t

2024

\n\t\t\t		\n\t\t\t

Executor

\n\t\t\t		\n\t\t\t

Site survey report;

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

System concept development:

\n\n\t\t\t
    \n\t\t\t\t
  1. Development of the project charter;
    2. \n\t\t\t\t
  2. Pre-design survey;
    3. \n\t\t\t\t
  3. Formation of business requirements for the system.
    4. \n\t\t\t\t
  4. Formation of a report on the results of work.
    5. \n\t\t\t
\n\t\t\t		\n\t\t\t

November

\n\n\t\t\t

2024

\n\t\t\t		\n\t\t\t

December 2024

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  1. Project charter;
    2. \n\t\t\t\t
  2. Project schedule;
    3. \n\t\t\t\t
  3. Report on the results of the work.
    4. \n\t\t\t
\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Technical task:

\n\n\t\t\t

Drawing up the Terms of Reference for the creation of the system and its form

\n\t\t\t		\n\t\t\t

December2024

\n\t\t\t		\n\t\t\t

January2025

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Terms of reference for data marts in terms of the received reporting on:

\n\n\t\t\t
    \n\t\t\t\t
  1. National accounting standards (NAS);
    2. \n\t\t\t\t
  2. KPI;
    3. \n\t\t\t\t
  3. Implementation of the business plan, production indicators, personnel report;
    4. \n\t\t\t\t
  4. Management reporting;
    5. \n\t\t\t\t
  5. IFRS
    6. \n\t\t\t
\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Design:

\n\n\t\t\t

1. Development of design solutions for the system and its parts. Testing;

\n\n\t\t\t

2. Development of documentation for the System and its parts;

\n\t\t\t		\n\t\t\t

February2025

\n\t\t\t		\n\t\t\t

August2025

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Development specifications, data mappings in terms of the received reporting on:

\n\n\t\t\t
    \n\t\t\t\t
  1. NAS;
    2. \n\t\t\t\t
  2. KPI;
    3. \n\t\t\t\t
  3. Implementation of the business plan, production indicators, personnel report;
    4. \n\t\t\t\t
  4. Management reporting;
    5. \n\t\t\t\t
  5. IFRS
    6. \n\t\t\t
\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Working documentation:

\n\n\t\t\t
    \n\t\t\t\t
  1. Development of working documentation for the system and its parts.
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

August2025

\n\t\t\t		\n\t\t\t

September 2025

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Working documentation for the development of reporting

\n\t\t\t
\n\t\t\t

6

\n\t\t\t		\n\t\t\t

Commissioning:

\n\n\t\t\t
    \n\t\t\t\t
  1. Preparation of the automation object for putting the System into operation;
    2. \n\t\t\t\t
  2. Personnel training;
    3. \n\t\t\t\t
  3. Commissioning works:
    4. \n\t\t\t\t
  4. Setting up integration with systems in accordance with the TOR;
    5. \n\t\t\t\t
  5. Preliminary tests;
    6. \n\t\t\t\t
  6. Coordination of improvements and settings, correction of defects;
    7. \n\t\t\t\t
  7. Acceptance tests.  
    8. \n\t\t\t\t
  8. Pilot industrial operation
    9. \n\t\t\t\t
  9. Industrial exploitation
    10. \n\t\t\t
\n\t\t\t		\n\t\t\t

September 2025

\n\t\t\t		\n\t\t\t

October 2025

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Reporting on:

\n\n\t\t\t
    \n\t\t\t\t
  1. NAS
    2. \n\t\t\t\t
  2. KPI
    3. \n\t\t\t\t
  3. Implementation of the business plan, performance indicators, personnel;
    4. \n\t\t\t\t
  4. Management reporting
    5. \n\t\t\t\t
  5. IFRS
    6. \n\t\t\t
\n\n\t\t\t

Guides :

\n\n\t\t\t
    \n\t\t\t\t
  1. Business Analysis System User Guide
    2. \n\t\t\t\t
  2. Business Analysis System Administrator Guide
    3. \n\t\t\t\t
  3. Acceptance test procedure
    4. \n\t\t\t\t
  4. Acceptance test report
    5. \n\t\t\t
\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

7

\n\t\t\t		\n\t\t\t

System Maintenance:

\n\n\t\t\t
    \n\t\t\t\t
  1. Performance of work in accordance with warranty obligations;
    2. \n\t\t\t\t
  2. Post-warranty service.
    3. \n\t\t\t
\n\t\t\t		\n\t\t\t

November 2025

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\n

Tab. 5.1 Preliminary stages of work.

\n\n

 

\n\n

Preliminary work schedule (table 5.2):

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Year

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

№

\n\t\t\t		\n\t\t\t

Stage

\n\t\t\t		\n\t\t\t

10.24

\n\t\t\t		\n\t\t\t

11.24

\n\t\t\t		\n\t\t\t

12.24

\n\t\t\t		\n\t\t\t

01.25

\n\t\t\t		\n\t\t\t

02.25

\n\t\t\t		\n\t\t\t

03.25

\n\t\t\t		\n\t\t\t

04.25

\n\t\t\t		\n\t\t\t

05.25

\n\t\t\t		\n\t\t\t

06.25

\n\t\t\t		\n\t\t\t

07.25

\n\t\t\t		\n\t\t\t

08.25

\n\t\t\t		\n\t\t\t

09.25

\n\t\t\t		\n\t\t\t

10.25

\n\t\t\t		\n\t\t\t

11.25

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

11.26

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Formation of requirements for the System

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

System concept development

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Technical task

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Design

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Working documentation

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

6

\n\t\t\t		\n\t\t\t

Commissioning

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

7

\n\t\t\t		\n\t\t\t

System Maintenance

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Within 12 months

\n\t\t\t
                     
\n\n

 

\n\n

 

\n\n

Tab. 5.2 Preliminary work schedule.

\n\n

 

\n\n

 

\n\n
    \n\t
  1. SYSTEM CONTROL AND ACCEPTANCE PROCEDURE
    2. \n
\n\n

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.

\n\n

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

\n\n

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

\n\n\n\n

Conducting test tests must be carried out on a test environment. Pilot and operational work - on a productive environment.

\n\n

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
\nand timing of tests to ensure the specified reliability of the results obtained. The test program and methodology can be developed
\nfor the System as a whole and (or) its parts. Tests (test cases) can be included as an attachment.

\n\n

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

\n\n\n\n

System tests are carried out at the Agency's site. By agreement between the Agencyand 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.

\n\n

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

\n\n

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.

\n\n

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

\n\n

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.

\n\n

Additional requirements of the Agencyarising 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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Types, scope and test methods
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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.

\n\n

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

\n\n

Preliminary tests

\n\n

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.

\n\n

Preliminary tests are carried out at a specially equipped stand.

\n\n

Pilot industrial operation

\n\n

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.

\n\n

Operations management works include:

\n\n\n\n

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.

\n\n

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.

\n\n

Acceptance tests

\n\n

Acceptance tests are carried out in accordance with the program and methodology of acceptance tests, which indicate:

\n\n

list and completeness of acceptance test objects;

\n\n

• list of requirements that the System and its parts must comply with (with reference to the clauses of the TT for the System);

\n\n

• scope, conditions, procedure and methods of testing and criteria for evaluating results;

\n\n

• list and sequence of checks to which the System must be subjected in accordance with the requirements of the TT for the System;

\n\n

• methods of performing checks for compliance of the indicators of the System as a whole and its components with the requirements of the TT for the System;

\n\n

• logistics and metrological support for testing;

\n\n

• acceptance criteria for the System and its parts;

\n\n

• details of the persons responsible for carrying out the tests;

\n\n

• the procedure, methods and conditions for checking the functioning and interaction of parts of the System, the functioning of the System as a whole in accordance with the requirements of the TT for the System;

\n\n

• ensuring safety during testing;

\n\n

• list and types of reporting documentation.

\n\n

The program and methodology for acceptance testing are approved by the Agency.

\n\n

Acceptance tests of the System or its corresponding phase put into permanent operation are carried out by a commission appointed by the Agency at the operating site in accordance with the program and test methodology approved by it.

\n\n

The timing of acceptance tests and the composition of the commission are determined by the Agency. The commission includes representatives of the developer.

\n\n

To carry out acceptance tests the following must be presented:

\n\n

• notification of the readiness of the System or its corresponding queue for acceptance testing;

\n\n

• TT for the System and TT for parts of the System (if available);

\n\n

• The system or its corresponding queue being tested;

\n\n

• documentation for the System;

\n\n

• program and methodology for acceptance testing;

\n\n

• agreed tests (test cases);

\n\n

• software and equipment necessary for testing, and the corresponding operational documentation;

\n\n

• acceptance certificate for trial operation;

\n\n

• certificate of completion of trial operation

\n\n

Acceptance tests should primarily include checking:

\n\n

 

\n\n

• completeness and quality of implementation of functions at standard, limiting, critical values ​​of parameters of the automation object and in other operating conditions of the System specified in the TT for the System;

\n\n

• convenience of work for users and staff;

\n\n

• means and methods for restoring the functionality of the System after failures;

\n\n

• completeness and quality of operational documentation.

\n\n

It is recommended to check the completeness and quality of the System functions in two stages. At the first stage, individual functions (tasks, sets of tasks) are tested. At the same time, compliance with the requirements of the System Specifications for functions (tasks, sets of tasks) is checked. At the second stage, the interaction of tasks in the System is checked and the requirements of the TT for the System are met.

\n\n

The ease of use of users and staff is checked taking into account the completeness and quality of performance of the functions of the System as a whole.

\n\n

The following are subject to verification:

\n\n

• completeness of messages and requests available to the user and their sufficiency for operating the system;

\n\n

• the ability for users and personnel to work without special training;

\n\n

• reaction of the System and its parts to user errors, functionality of service tools.

\n\n

 

\n\n

Checking the means of restoring the functionality of the System after failures of technical means should include:

\n\n

• checking the presence in the operational documentation of recommendations for restoring operability and the completeness of their description;

\n\n

• practical feasibility of recommended procedures;

\n\n

The test results of objects provided for by the test program and methodology are recorded in protocols containing the following sections:

\n\n

• the purpose of the tests and the number of the section of the requirements of the TT for the System, according to which the test is carried out;

\n\n

• composition of hardware and software used during testing;

\n\n

• indication of the checks in accordance with which the tests were carried out, processing and evaluation of the results;

\n\n

• test conditions and characteristics of the initial data;

\n\n

• testing tools used;

\n\n

• generalized test results;

\n\n

• conclusions about test results and compliance of the created System or its parts with a certain section of the requirements of the TT for the System.

\n\n

Test protocols for objects are summarized in a single protocol, on the basis of which a conclusion is made about the system’s compliance with the requirements of the TT for the System.

\n\n

Industrial exploitation

\n\n

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. General requirements for acceptance of works by stages
      2. \n\t
    \n\t
    2. \n
\n\n

Below are the main stages and stages performed by the Supplier 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:

\n\n

 

\n\n\n\n

 

\n\n

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

\n\n

RASCI matrix (distribution of responsibilities between project participants)

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

R

\n\t\t\t		\n\t\t\t

Responsible
\n\t\t\t(Ответственный)

\n\t\t\t		\n\t\t\t

The Project Participant performing the Work to achieve the Project Result. Responsible for the achievement of the Result

\n\t\t\t
\n\t\t\t

A

\n\t\t\t		\n\t\t\t

Approver
\n\t\t\t(Утверждающий)

\n\t\t\t		\n\t\t\t

A project participant who approves the correctness and completeness of the work. Accepts the Results of the Works.

\n\t\t\t
\n\t\t\t

S

\n\t\t\t		\n\t\t\t

Support
\n\t\t\t(Соисполнитель)

\n\t\t\t		\n\t\t\t

A project participant who provides support within his competence for the Responsible.

\n\t\t\t
\n\t\t\t

C

\n\t\t\t		\n\t\t\t

Consulted
\n\t\t\t(Консультирующий)

\n\t\t\t		\n\t\t\t

A project participant whose opinion (resources) is taken into account to create the Project Results. Subject matter experts.

\n\t\t\t
\n\t\t\t

I

\n\t\t\t		\n\t\t\t

Informed
\n\t\t\t(Информируемый)

\n\t\t\t		\n\t\t\t

A project participant who is informed about the progress of the Work on the creation of the Project Results.

\n\t\t\t
\n\n

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

\n\n

 

\n\n

Responsibility matrix for project results

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Stage

\n\t\t\t		\n\t\t\t

Responsible

\n\t\t\t		\n\t\t\t

results

\n\t\t\t
\n\t\t\t

Suppliers

\n\t\t\t		\n\t\t\t

Agency

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

1.

\n\t\t\t		\n\t\t\t

Formation of requirements for the System

\n\t\t\t		\n\t\t\t

R

\n\t\t\t		\n\t\t\t

A, C, S

\n\t\t\t		\n\t\t\t

1. Terms of reference for a business analysis system;

\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

2.

\n\t\t\t		\n\t\t\t

System concept development

\n\t\t\t		\n\t\t\t

R

\n\t\t\t		\n\t\t\t

A, C, S

\n\t\t\t		\n\t\t\t

1. Project charter;

\n\n\t\t\t

2. Schedule of the project;

\n\n\t\t\t

3. Report on the results of the work.

\n\t\t\t
\n\t\t\t

3.

\n\t\t\t		\n\t\t\t

Technical task

\n\t\t\t		\n\t\t\t

R, A, C

\n\t\t\t		\n\t\t\t

A, C, S

\n\t\t\t		\n\t\t\t

Terms of reference for data marts in terms of the received reporting on:

\n\n\t\t\t

1. NAS;

\n\n\t\t\t

2. KPI;

\n\n\t\t\t

3. Fulfillment of the business plan, production indicators, personnel report;

\n\n\t\t\t

4. Management reporting;

\n\n\t\t\t

5. IFRS

\n\t\t\t
\n\t\t\t

4.

\n\t\t\t		\n\t\t\t

Design

\n\t\t\t		\n\t\t\t

R, A, C

\n\t\t\t		\n\t\t\t

A, C, S

\n\t\t\t		\n\t\t\t

Development specifications, data mappings in terms of the received reporting on:

\n\n\t\t\t

1. NAS;

\n\n\t\t\t

2. KPI;

\n\n\t\t\t

3. Fulfillment of the business plan, production indicators, personnel report;

\n\n\t\t\t

4. Management reporting;

\n\n\t\t\t

5. IFRS

\n\t\t\t
\n\t\t\t

5.

\n\t\t\t		\n\t\t\t

Working documentation

\n\t\t\t		\n\t\t\t

R

\n\t\t\t		\n\t\t\t

A, C, S

\n\t\t\t		\n\t\t\t

1. Working documentation for the development of reporting

\n\t\t\t
\n\t\t\t

6.

\n\t\t\t		\n\t\t\t

Commissioning

\n\t\t\t		\n\t\t\t

R

\n\t\t\t		\n\t\t\t

R, A, C

\n\t\t\t		\n\t\t\t

Reporting on:

\n\n\t\t\t

1. NAS

\n\n\t\t\t

2. KPI

\n\n\t\t\t

3. Implementation of the business plan, performance indicators, personnel;

\n\n\t\t\t

4. Management reporting

\n\n\t\t\t

5. IFRS

\n\n\t\t\t

Guides:

\n\n\t\t\t

1. Business Analysis System User Guide

\n\n\t\t\t

2. Business Analysis System Administrator's Guide

\n\n\t\t\t

3. Acceptance test procedure

\n\n\t\t\t

4. Acceptance test report

\n\t\t\t
\n\t\t\t

7

\n\t\t\t		\n\t\t\t

System Maintenance

\n\t\t\t		\n\t\t\t

R

\n\t\t\t		\n\t\t\t

A, C, S

\n\t\t\t		\n\t\t\t

Warranty technical support

\n\t\t\t
\n\n

Tab. 6.2.2 Responsibility matrix for project results

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Requirements for managing organizational change
      2. \n\t
    \n\t
    2. \n
\n\n

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:

\n\n

Communication

\n\n

Key tasks:

\n\n

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

\n\n\n\n

Organizational Design

\n\n

Key tasks:

\n\n\n\n

Education

\n\n

Key tasks:

\n\n

Training of the system implementation project team:

\n\n\n\n

Preliminary estimate of the number of employees for training:

\n\n

• Professional training - business users: 50 people

\n\n

• Professional training - technical specialists: 20 people.

\n\n

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

\n\n

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

\n\n

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

\n\n

 

\n\n

Methodological support for Organizational Change Management

\n\n

Key tasks:

\n\n\n\n

Assess the impact of change and readiness for change

\n\n\n\n

 

\n\n

 

\n\n
    \n\t
  1. REQUIREMENTS FOR THE COMPOSITION AND CONTENT OF WORKS ON PREPARING THE SYSTEM FOR COMMISSIONING
    2. \n
\n\n

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

\n\n

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.

\n\n

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

\n\n\n\n

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

\n\n\n\n
    \n\t
  1. DOCUMENTATION REQUIREMENTS\n\n\t
      \n\t\t
    1. Project documentation
      2. \n\t
    \n\t
    2. \n
\n\n\n\n

 

\n\n
    \n\t
  1. SOURCES OF DEVELOPMENT
    2. \n
\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. PROJECT ASSUMPTIONS AND RESTRICTIONS\n\n\t
      \n\t\t
    1. Organizational Assumptions and Constraints
      2. \n\t
    \n\t
    2. \n
\n\n\n\n

 

\n\n\n\n

 

\n\n\n\n

 

\n\n\n\n

 

\n\n\n\n
    \n\t
  1. Terms of the Project execution
    2. \n
\n\n

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

\n\n"},{"id":"OP00280697","notice_type":"Request for Expression of Interest","noticedate":"21-Mar-2024","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2024-04-19T00:00:00Z","submission_deadline_time":"10:00","project_ctry_name":"Eastern and Southern Africa","project_id":"P171967","project_name":"Regional Infrastructure Finance Facility (RIFF) Project","bid_reference_no":"ZM-COMESA -394070-CS-LCS","bid_description":"Human Resource Management System","procurement_group":"CS","procurement_method_code":"LCS","procurement_method_name":"Least Cost Selection","contact_address":"Ben Bella Road, P. O. Box 30051, Lusaka","contact_ctry_name":"Zambia","contact_email":"jmutale@comesa.int","contact_name":"Mohamed Kheir Elginaid","contact_organization":"COMESA","contact_phone_no":"+260979413591","submission_date":"2024-03-21T00:00:00Z","notice_text":"

COMMON MARKET FOR EASTERN AND

\n\n

SOUTHERN AFRICA

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

السوق المشتركة للشرق والجنوب الأفريقى

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

MARCHE COMMUN

\n\t\t\t
\n\n

REQUEST FOR EXPRESSION OF INTEREST

\n\n

               (FIRM SELECTION)

\n\n

 

\n\n

NAME OF PROJECT: REGIONAL INFRASTRUCTURE FINANCE FACILITY       (RIFF) PROJECT

\n\n

GRANT NO: D6780-3A

\n\n

ASSIGNMENT TITLE: PROCUREMENT OF A  HUMAN RESOURCE MANAGEMENT SYSTEM  .   REFERENCE No. ZM-COMESA - 394070-CS-LCS

\n\n

ISSUED ON : 21  MARCH 2024

\n\n
    \n\t
  1. Background
    2. \n
\n\n

The Common Market for Eastern and Southern Africa (COMESA) received a grant from the World Bank towards the implementation of the Regional Infrastructure Finance Facility project and intends to apply a portion of the proceeds of this grant to eligible payments under the contract for the procurement of a Human Resource Management System.

\n\n

The Common Market for Eastern and Southern Africa (COMESA) is a regional grouping of 21 African States which have agreed to promote regional integration through trade development and transport facilitation. COMESA's objectives include sustainable economic development through economic and social progress in all Member States through increased cooperation and integration in all fields of development particularly in Trade, Customs and Monetary Affairs, Transport, Communication and Information Technology, Industry and Agriculture, Energy, Environment and Natural Resources including Gender and Social Development. The Secretariat is based in Lusaka, Zambia.

\n\n

The COMESA Secretariat wishes to procure a Human Resource Management System that will be a digital platform to be used to support the COMESA Secretariat’s Human Resource processes. The System will among others help to streamline recruitment management, benefits administration, payroll management, employee data, employee performance, compensation management, timesheets and other Human Resource Management functions. It will also leverage technology to increase efficiency and effectiveness in the management of the Human Resource functions and ensure reliability and integrity of the data.

\n\n
    \n\t
  1. objectives of the system
    2. \n
\n\n

The main objectives of the Human Resources Management system is to help COMESA enhance its systems, improve productivity, availability, reliability, and flexibility, and minimize response time in a cost-effective way.  Furthermore, it is expected that a new HRMS will help COMESA to:

\n\n
    \n\t
  1. Work Smarter by increasing efficiency and reducing back-office interventions thus increasing COMESA’s performance and reducing costs;
    2. \n\t
  2. Work Remotely since the system would be accessible from anytime and anywhere.  In addition, employees should be able to access their personal information, submit leave requests, update contact details, view pay slips, and participate in performance appraisals via an employee self-service portal; and 
    3. \n\t
  3. Work Securely by protecting and controlling employee’s data and information confidentially every time.
    4. \n
\n\n
    \n\t
  1. Current Problems to resolve
    2. \n
\n\n

The following problems need to be resolved:

\n\n
    \n\t
  1. Technology: Manual processes should be automated, and the system should be developed on the latest technologies. 
    2. \n\t
  2. Mobility: Staff should be able to access the system and its e-services at any time, from anywhere, and on different types of devices (tablets, mobiles, laptops, etc.).
    3. \n\t
  3. Collaboration: The HR processes should be able to fully integrate with current and future application systems.
    4. \n\t
  4. Security:  The system should meet the security requirements as per industry standards, best practices and IT audit requirements of COMESA.
    5. \n\t
  5. Scalability: All applications/systems at COMESA should be able to accommodate new features/modules to meet the changing organizational needs.
    6. \n\t
  6. Integration: The system should be able to fully integrate with current and future relevant application systems.
    7. \n\t
  7. Reports: The system should be able to generate Reports that are accurate and promotes integrity of the data.
    8. \n
\n\n

The detailed Terms of Reference (TOR) for the assignment are attached to this request for Expressions of Interest (EOI).

\n\n

The Common Market for Eastern and Southern Africa now invites eligible consultants to indicate their interest in providing these services. Interested consultants must provide information indicating that they are qualified to perform the services (brochures, description of similar assignments, core business and not less than 10 years’ experience in similar assignments, relevant experience, technical and managerial capability of the firm, etc). Consultants may constitute joint ventures to enhance their chances of qualification but should indicate clearly whether the association is in the form of a joint venture. In the case of a joint venture, all the partners in the joint venture shall be jointly and severally liable for the entire contract, if selected.

\n\n

The attention of interested Consultants is drawn to Section III, paragraphs, 3.14, 3.16, and 3.17 of the World Bank’s “Procurement Regulations for IPF Borrowers”  November  2020 setting forth the World Bank’s policy on conflict of interest.

\n\n
    \n\t
  1. SUBMISSION
    2. \n
\n\n

Expressions of interest must be submitted  in written  to the following email address;

\n\n

Tenders@comesa.int with a copy to procurement@comesa.int

\n\n

ASSIGNMENT TITLE:PROCUREMENT OF A HUMAN RESOURCE MANAGEMENT SYSTEM.    REFERENCE No. ZM-COMESA -394070-CS-LCS

\n\n

ATT: THE HEAD OF PROCUREMENT, COMESA SECRETARIAT, BEN BELLA ROAD, LUSAKA, ZAMBIA

\n\n

   CLOSING DATE FOR SUBMISSION

\n\n

The Closing date for receipt of Expression of Interest is 19th April 2024 at 10:00 hours Central  Africa Time (CAT)

\n\n

Further information can be obtained at the address below during office hours,  09:00 - 17: 00 hours Central Africa Time (CAT) to the following address.

\n\n

COMESA Secretariat, Ben Bella Road, Lusaka, Zambia

\n\n

Email address:  procurement@comesa.int

\n\n

 

\n\n

NB: Physical submission of EOIs shall  not be accepted.

\n\n

ANNEX 1: TERMS OF REFERENCE 

\n\n

COMMON MARKET FOR EASTERN AND

\n\n

SOUTHERN AFRICA

\n\n

 

\n\n

 \n

    \n\t
  1. Background
    2. \n
\n

\n\n

The Common Market for Eastern and Southern Africa (COMESA) is a regional grouping of 21 African States which have agreed to promote regional integration through trade development and transport facilitation. COMESA's objectives include sustainable economic development through economic and social progress in all Member States through increased co-operation and integration in all fields of development particularly in Trade, Customs and Monetary Affairs, Transport, Communication and Information Technology, Industry and Agriculture, Energy, Environment and Natural Resources including Gender and Social Development. The Secretariat is based in Lusaka, Zambia.

\n\n

The COMESA Secretariat wishes to procure a Human Resource Management System that will be a digital platform to be used to support the COMESA Secretariat’s Human Resource processes. The System will among others help to streamline recruitment management, benefits administration, payroll management, employee data, employee performance, compensation management, and timesheets. It will also leverage technology to increase efficiency and effectiveness in the management of the Human Resource functions and ensure reliability and integrity of the data.

\n\n
    \n\t
  1. Purpose of this document
    2. \n
\n\n

This document identifies the User requirements, Functional and Non-functional specifications for a Human Resource Management System (HRMS) for COMESA Secretariat. Furthermore, it specifies the scope of work, methodology and deliverables for the HRMS project.

\n\n
    \n\t
  1. Main Objectives of a modern HMRS
    2. \n
\n\n

The main objectives of the project are to help COMESA to enhance its systems to improve productivity, availability, reliability, and flexibility, and minimize response time in a cost-effective way.  Furthermore, it is expected that a new HRMS will help COMESA to:

\n\n
    \n\t
  1. Work Smarter: Increase efficiency and reduce back-office interventions thus increasing COMESA’s performance and reducing costs.
    2. \n\t
  2. Work Remotely: The system should be accessible from anytime and anywhere.  In addition, employees should be able to access their personal information, submit leave requests, update contact details, view pay slips, and participate in performance appraisals via an employee self-service portal. 
    3. \n\t
  3. Work Securely: Protecting and controlling employee’s data and information confidentially every time.
    4. \n
\n\n
    \n\t
  1. Current Problems to resolve
    2. \n
\n\n

The following problems need to be resolved:

\n\n
    \n\t
  1. Technology: Manual processes should be automated, and the system should be developed on the latest technologies.  
    2. \n\t
  2. Mobility: Staff should be able to access the system and its e-services at any time, from anywhere, and on different types of devices (tablets, mobiles, laptops, etc.).
    3. \n\t
  3. Collaboration: The HR processes should be able to fully integrate with current and future application systems.
    4. \n\t
  4. Security:  The system should meet the security requirements as per industry standards, best practices and IT audit requirements of COMESA.
    5. \n\t
  5. Scalability: All applications/systems at COMESA should be able to accommodate new features/modules.
    6. \n
\n\n
    \n\t
  1. Scope of Work
    2. \n
\n\n

The scope of work of the project is as follows:

\n\n
    \n\t
  1. Implementation and Customization of an Off the Shelf HRMS System.
    2. \n
\n\n

The supplier is expected to implement a comprehensive user friendly HRMS solution and to customize the HRMS package as per COMESA user requirements.

\n\n

The HRMS solution shall be developed using a modular approach to enhance flexibility, scalability, and maintainability. The solution shall consist of distinct modules, with each module catering to specific HRMS functionalities such as employee management, recruitment, onboarding, benefits administration, payroll, etc.

\n\n

The core HRMS functions and the Payroll functions will be treated as independent systems and be implemented as a separate, dedicated module. Integration between core HRMS and Payroll modules shall be seamless, enabled through a Service Oriented Architecture (SOA) approach or any other integrating approach that follows industry best practices.

\n\n
    \n\t
  1. Integration
    2. \n
\n\n

The application should be fully integrated with the Sun Accounting System, COMESA Portal, Document Management System, active directory and with a workflow management system.

\n\n
    \n\t
  1. Migration of Data
    2. \n
\n\n

The bidder should provide an effective and efficient data migration approach of all existing data from the current system (Smart HR) to the configured environment. The successful bidder will be expected to provide full support to the COMESA during the data migration phases, including the identification and resolution of data quality issues.

\n\n
    \n\t
  1. Training and Knowledge Transfer
    2. \n
\n\n

The bidder shall provide a detailed training plan to ensure proper knowledge transfer to the business users as well as the IT Administrators. The bidder shall provide specific training programme for:

\n\n
    \n\t
  1. Business users to continue operational responsibility for the delivered solution.
    2. \n\t
  2. IT staff to enable first line support to users and for the proper administration of the delivered solution.
    3. \n\t
  3. Business users and IT staff create and eventually customize reports/dashboards using the proposed reporting tools.
    4. \n\t
  4. Business users and IT staff perform basic administration tasks like create users, assign roles to users and de-activate users.
    5. \n
\n\n
    \n\t
  1. Documentation
    2. \n
\n\n

The successful bidder will be required to provide a comprehensive set of documentations regarding the application system including the solution blueprint, system manual, installation manual and user manual.

\n\n
    \n\t
  1. Post implementation support
    2. \n
\n\n

The Bidder should provide a minimum of two (3) months on-site post implementation support.

\n\n
    \n\t
  1. Warranty
    2. \n
\n\n

The warranty period should be for a period of 12 months, effective immediately after the expiry of the on-site post implementation support period. The warranty shall cover all configurations and functions as stated in the scope of the work for corrective maintenance.

\n\n
    \n\t
  1. Support and Maintenance after warranty period
    2. \n
\n\n

Bidders shall submit their support and maintenance costs related to support over the next two (2) years after the warranty period, based on an agreed Service Level Agreement (SLA) (8x5). The support shall cover among other troubleshooting/bug fixing, patch management, fine tuning and health checks. Bidder should also provide the response time to blocking/non-blocking issues as well as their rates on an hourly basis for any intervention that is not covered under SLA. COMESA reserves the right to proceed with award and renewal of the Maintenance agreement.

\n\n

 

\n\n
    \n\t
  1. Human Resource Management System Specification
    2. \n
\n\n

The specifications of the Human Resource Management System include features which have been divided into Functional Solution Requirements and non-functional solutions Requirements as follows:

\n\n

6.1     Functional Systems Requirements

\n\n

Functional requirements define what a system must do, and the features it must have to fulfil user Requirements. This enables a system to meet the specific user requirements and describe the system behavior under specific conditions.

\n\n

The specific features and functions of Human Resource Management System to serve the requirement of the COMESA Secretariat will require to have the following modules with the descriptions indicated below:

\n\n
    \n\t
  1. Core Human Resource Module
    2. \n
\n\n

The core HR module should be able to store all the required information about employees and will be the main repository for functionality that is applicable to the whole Human Resource management system. This would be Employee Master Data that will have employees’ information in one centralized database. The employee information will include the following: employee details (name, date of birth, age, address, emergency contacts, next of kin, salary, job title, grade, Division/Unit, incremental dates, dependent information, effective date of contract, contract expiry date, etc.), employment history, employee qualifications, benefits and compensation, performance history, etc.

\n\n
    \n\t
  1. Recruitment Module
    2. \n
\n\n

Recruitment module would enable the Secretariat to manage all recruitment activities using a single, intuitive self-service interface. The recruitment module shall provide facilities for job posting, candidate sourcing, application management, screening, and assessment of candidates. The automation of the recruitment function would assist in the shortlisting process as applicants would submit their applications online and the shortlisting would be seamlessly done sieving the applications based on a set criterion in line with the job requirements. The automation of the recruitment would reduce purported biases in the shortlisting process thereby promoting objectivity and fairness of the entire process.  The system shall be used to schedule and manage interviews, maintain a candidate database for future reference and talent acquisition.

\n\n
    \n\t
  1. On Boarding Module
    2. \n
\n\n

The onboarding module should help the Secretariat to effectively onboard and integrate new employees into the company. The onboarding module aims to create a positive and engaging experience for new hires, fostering their connection to the organization and setting them up for success. By automating and centralizing onboarding processes, it saves time, reduces paperwork, and ensures consistent and standardized onboarding practices across the organization. Some of the tools and functionalities to streamline the process of welcoming, orienting, and training new hires, ensuring a smooth transition and facilitating their productivity from day one. Some of the features include pre-boarding, new hire paperwork & documentation, orientations, etc.

\n\n
    \n\t
  1. Benefits
    2. \n
\n\n

This module should help manage the administration of benefits that aligns with the Secretariats applicable benefits and policies, and the approved budget. It should enable users to factor in benefits such as Medical, Education Allowance, Dependency and Spouse Allowances, Overtime, Advances, Acting Allowance (where applicable) and any other applicable benefits. Employees should be able to have easy access to applicable benefits and how they have been utilized through self-service. Features of the module should among others include:

\n\n
    \n\t
  1. Eligibility rules to determine which employees are entitled to certain benefits.
    2. \n\t
  2. Budgets that can restrict managers from overspending.
    3. \n\t
  3. Inbuilt Workflows and approval processes.
    4. \n\t
  4. Inclusion of data security and control to protect sensitive data; and
    5. \n\t
  5. Synchronizing data to payroll to avoid rekeying data.
    6. \n
\n\n
    \n\t
  1. Employee self-services
    2. \n
\n\n

Self-Service Human Resources will enable staff in the Secretariat to be able to manage information through interfaces personalized to their roles, on-line experience, work content, language, and information needs. Staff would be given user rights to access the Employee Self-Service Module that would allow them to do the following:

\n\n
    \n\t
  1. Change personal information.
    2. \n\t
  2. Apply for Leave.
    3. \n\t
  3. View Pay slips Online (including historical payroll).
    4. \n\t
  4. Apply for advances.
    5. \n\t
  5. Prepare Individual Training Plan.
    6. \n\t
  6. Perform self-assessments.
    7. \n\t
  7. Update their Curriculum Vitae; and
    8. \n\t
  8. Query personal information.
    9. \n
\n\n
    \n\t
  1. Performance Management
    2. \n
\n\n

Performance Management is a key module that would enable the Secretariat to continuously measure the performance of its employees effectively. It should have five components that include planning, monitoring, performance feedback, developing, rating, and rewarding. These components should work together and support each other to ensure effective performance management.

\n\n

The performance management module should be customized to suit the current Performance Management system being used by the Secretariat, which is the Balance Scorecard. It should also have features to be aligned to other Performance Management Systems.

\n\n

It should enable users to look back through data and offer future performance guides according to desired KPIs and goals.  It must also offer tailored and customizable analytics and reports from system’s data with real-time information and reporting that facilitates timely decisions that enhance performance against KPIs.

\n\n
    \n\t
  1. Training and Development
    2. \n
\n\n

The HRMS should have a Training and Development module that offers a full range of learning options manageable from one interface. This includes mapping activities against competency frameworks for personal performance management and connecting learning outcomes to desirable skill-building.

\n\n

This module should ensure that training interventions are made in a systematic manner to avoid haphazard requests for training. Training should be needs based and the module should make it simple track training and make informed development decisions. It should enable users to access personal training records, future training needs/requirements and personal development archives. 

\n\n
    \n\t
  1. Time and Attendance
    2. \n
\n\n

As a process of tracking employee working hours, the time and attendance model is very critical as it would assist COMESA Secretariat to unlock functions like absence management, employee scheduling, clocking in and out, compliance, cost estimates, and payroll integration. It would provide features to track and manage the absence of employees and capture working hours on a timesheet. It is very necessary that the module should be aligned to the Secretariats policies and practices. The key features of the module should among others include:

\n\n
    \n\t
  1. Creation of attendance modules, manage schedules, and set notifications and alerts that enable users to check things like attendance or overtime.
    2. \n\t
  2. Keeping a record of their hours.
    3. \n\t
  3. Provision of options such as PINs, biometric scanners, magnetic card readers, and fingerprint and facial recognition tools.
    4. \n\t
  4. Check and use data for reporting and compliance purposes.
    5. \n\t
  5. Provide automatic alerts and notifications when there is noncompliance with policies and practices.
    6. \n\t
  6. provide the ability to configure all the absence types used by the Secretariat and define which absence types apply to which employee populations.
    7. \n\t
  7. produce schedules and timesheets that display, and capture required information.
    8. \n\t
  8. provide exception reporting to highlight missed shifts, missed clock-outs and overtime.
    9. \n\t
  9. specify statutory holidays by country and region and configure eligibility requirements; and
    10. \n\t
  10. Provide approval workflows and reminders for absence requests and completed timesheets.
    11. \n
\n\n
    \n\t
  1. Leave Management
    2. \n
\n\n

Leave Management Software facilitates the effective and smooth management of personnel leave. It will enable the Human Resources Unit to always be up to date with the leave management. Its main objective is to handle employees' leave requests impartially while ensuring that the employees' absence from work does not adversely affect the business.   The system facilitates the total leave process, from completing leave applications by employees, leave application approval by HR and the final approving Officer. The salient features required for this module should among others include: 

\n\n
    \n\t
  1. On-line application for leave without the need for paperwork.
    2. \n\t
  2. Email notifications to approving officer and applicants.
    3. \n\t
  3. Applicant and Approving Officer should be able to check complete leave records and approval history respectively.
    4. \n\t
  4. Leave records to be updated automatically once applications are approved.
    5. \n\t
  5. Leave records to be printed out or generated into reports.
    6. \n\t
  6. Leave records to be exported to any back-end system.
    7. \n\t
  7. Advanced features such as block leave, document tracking and leave adjustment; and
    8. \n\t
  8. All leave policies and requirements such as leave entitlements, forfeiture of leave days should be configurable in the system.
    9. \n
\n\n

 

\n\n
    \n\t
  1. Payroll Administration Module
    2. \n
\n\n

The Payroll Administration Module shall be treated as independent system. However, the system shall allow seamless integration between the HRMS and Payroll modules. As an extension of the Core HR module, it would be used to maintain payroll data and manage the payroll process. It is critical in reducing set-up costs, administrative time, and processing errors. The key features of the module should among others include:

\n\n
    \n\t
  1. To calculate employee salaries and benefit and support multiple currencies.
    2. \n\t
  2. Enough payroll codes to meet current and future needs.
    3. \n\t
  3. Employee access to pay statements and other tax-related forms.
    4. \n\t
  4. Integration with the time and attendance module and benefits module.
    5. \n\t
  5. Simple data validation tools to ensure data is correct before being submitted.
    6. \n\t
  6. Payroll comparison to highlight significant changes from one pay cycle to the next.
    7. \n\t
  7. User driven process of rules definition with the ability to link user defined formulas to calculate any type of payroll element (payment, deduction, tax, benefit).
    8. \n\t
  8. Process many payrolls quickly and easily in a single day.
    9. \n\t
  9. Create innovative compensation plans – from salary, overtime, and union deductions to company cars, health insurance, and company pension contributions.
    10. \n\t
  10. Make retroactive adjustments to employee past earnings or deductions based on changes to pay rates, contribution table values, or other information.
    11. \n\t
  11. Examine employee payment history at any time.
    12. \n\t
  12. Perform all the necessary post processing to generate payment for employees once satisfied that payroll run results are correct; and
    13. \n\t
  13. Advanced feature that allows you to undo and correct payment mistakes.
    14. \n\t
  14. Tight integration with core HR to avoid rekeying data and maintain reliability of the data.
    15. \n\t
  15. Integrability with the existing Sun System or any other accounting systems to facilitate timely, accurate and seamless payments of salaries and benefits.
    16. \n
\n\n

 

\n\n
    \n\t
  1. Analytics and Reporting
    2. \n
\n\n

The system should provide a flexible management reporting tool with data extraction in various formats such as PDF or Excel and includes drilling capabilities. It should include interactive dashboards and highly formatted reporting. Users should be able to design their own reports and generate them in a wide range of formats including listing, charts, and pivot tables.  Users should be able to access data at different levels of granularity in a single report itself.

\n\n

The objective is to facilitate decision-making with regards to HR Management.

\n\n

 

\n\n

6.2     Non-Functional Requirements

\n\n

Non-functional requirements or features are not related to the system functionality but define how the system should perform. Some examples are the technical specifications, which are components of an HR system including security, scalability, user friendliness speed, Usability, Maintainability, Support, Regulatory, Compatibility and integrability among others are detailed below.

\n\n

 

\n\n

These features are usually expressed as constraints or criteria that define a level of freedom for developers or users. Although non-functional requirements may seem a bit subtler, they are still as important as functional features. The description of the features that will be required in the Human Resource System are as follows:

\n\n
    \n\t
  1. External interface requirements\n\n\t\n\t
    2. \n
\n\n

The user interface is key to application usability. The System should include content presentation, application navigation, and user assistance.

\n\n

Role-based User Groups: The system must provide users with screens focusing on their roles (minimizing clutter).

\n\n

Dynamic content presentation: Users should be provided with in data presentation. The system should allow users to select appropriate settings and property values on display options that fits their preferences, e.g., choice of whether data appears in a grid, a chart, or a grid/chart combination.

\n\n

User assistance: the system should provide online help that includes comprehensive instructions on using each feature. The users should be provided with default mechanisms for accessing help pages e.g., by clicking the question mark icon across all the screens or a distinct menu Help > Help... menu option in the menu bar. A link to a comprehensive help resource should be provided in various formats e.g., Wiki, PDF etc.

\n\n

User navigation: the system should provide a simple traceable navigation of the entire system with options clearly showing the users where they are and how they can navigate away from the current screens and consequences of doing so.

\n\n

Saving users’ work: The system should provide users performing data manipulation tasks to save their work at a certain point or make a particular view of the data available to other users.

\n\n

Branding guide: the system interface design will adhere to the COMESA branding guide which shall be provided.

\n\n\n\n

All server-side components must execute on server-class computers. All client-side components must execute on workstation-class and personal-class computers.

\n\n\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. The system shall communicate with the COMESA active directory system to provide role-based authentication as shall be provided during detailed requirements gathering stage.
      2. \n\t\t
    2. The system shall have an interface with the COMESA public facing website to publish vacancies and various recruitment drives.
      3. \n\t\t
    3. The system shall interface with the COMESA Financial Management System to interface staff costs and relevant expense accounts and salary payments directly to staff bank accounts.
      4. \n\t\t
    4. The system should be able to integrate with a Document Management System and a workflow management system.
      5. \n\t
    \n\t
    2. \n
\n\n\n\n

Web browser: The system must provide an option to be accessed via the internet using the latest browsers e.g., Chrome, Edge, Mozilla, Safari with backward compatibility support to 2 versions.

\n\n

Note: in a scenario where the system uses third party plugins to run, this must be stated in advance for information security tests and clearance.

\n\n

Communication standards and Network server communications protocols: All communications between the server components and user interactions must be encrypted to safeguard user and data privacy. Only secure protocols shall be permitted e.g., HTTPS, FTPS with appropriate authentication and authorization mechanisms.

\n\n

Electronic forms: the system must provide interfaces using electronic forms either on the browser or client application. The forms must be secured.

\n\n

Data transfer rates: The system must provide appropriate data transfer rates that shall be agreed upon meeting performance requirements.

\n\n

E-mail: the system must provide communication mechanisms with various stakeholders or user groups within the system. This can be achieved via forms that create support tickets or defined emails on the COMESA (comesa.int) domain.

\n\n

Communication security or encryption: end to end encryption must be provided in all the interactions in the system e.g., chat facilities, web browsers, mobile apps etc.

\n\n
    \n\t
  1. Performance
    2. \n
\n\n

The system should be responsive and perform efficiently, even with many concurrent users and data. It should have acceptable response times for tasks such as employee data retrieval, report generation, and system updates. System performance is the most important quality in non-functional requirements and affects almost all the other preceding ones. A stress test is to be performed by the vendor once the system is commissioned.

\n\n

The reliability, availability, and maintainability (RAM) features fall exclusively under these requirements.

\n\n
    \n\t
  1. Reliability
    2. \n
\n\n

Reliability is the probability and percentage of the software performing without failure for a specific number of uses or amount of time.

\n\n
    \n\t
  1. Availability
    2. \n
\n\n

The system should be designed to minimize downtime through robust error handling, fault tolerance, and backup and recovery mechanisms. It should also have appropriate monitoring and alerting capabilities to identify and address potential issues proactively.

\n\n
    \n\t
  1. Maintainability
    2. \n
\n\n

This feature indicates the average time, ease, and rapidity with which a system can be restored after a failure.

\n\n
    \n\t
  1. Recoverability
    2. \n
\n\n

Recoverability is the ability to recover from a crash or a failure in the system and return to full operations.

\n\n
    \n\t
  1. Capacity
    2. \n
\n\n

This feature indicates the system’s storage capacity, which is dependent on its type and characteristics. The system should have enough storage capacity and backup to store all the employee data.

\n\n
    \n\t
  1. Serviceability
    2. \n
\n\n

This feature indicates how easy it is to perform service when necessary.

\n\n
    \n\t
  1. Security
    2. \n
\n\n

Security measures ensure the software’s safety against espionage or sabotage. These features are necessary even for stand-alone systems and it is necessary to ensure that access to sensitive data is restricted or limited. Some security features may include encryption of data on database and web services, implementation using HTTPS, only authorized users are able to access the system via an authentication mechanism and Role based access.

\n\n

The HRMS shall implement secure user authentication mechanisms, including username/password, multi-factor authentication (MFA), or Single Sign-On (SSO). User access to HRMS functionalities and data shall be role-based, with strict control over user permissions. The system shall enforce strong password policies, requiring password complexity, regular expiration, and lockout after multiple failed login attempts. Additionally, employee data, such as personal information, financial records, and performance evaluations, shall be encrypted both at rest and during transmission to safeguard data privacy. The HRMS shall comply with data privacy regulations and ensure data subject rights, including data access, rectification, and erasure (right to be forgotten).

\n\n

A detailed audit trail of user activities, including login attempts, password changes, and data access, shall be maintained, along with continuous monitoring for potential security threats. Access control measures shall be implemented within the HRMS, enforcing role-based restrictions on specific modules and data based on user roles and responsibilities. Administrators will have the necessary authority to grant, revoke, or modify user access rights as required.

\n\n

Employee data should be securely stored in a centralized database, protected against unauthorized access or tampering. The system shall incorporate mechanisms to prevent common security risks or OWASP top ten vulnerabilities, such as SQL injection attacks. All communications between the user's browser and the HRMS shall be encrypted using HTTPS to prevent eavesdropping and man-in-the-middle attacks. Additionally, the HRMS should implement secure session management to prevent session hijacking and enforce session timeouts after a period of inactivity. The system should allow to perform regular data backups to ensure data integrity and facilitate data recovery in case of system failures or data loss.

\n\n
    \n\t
  1. Environmental
    2. \n
\n\n

These factors concern the software’s environment in terms of how long it should be operational and what external factors might affect it.

\n\n
    \n\t
  1. Data integrity
    2. \n
\n\n

Data integrity refers to maintaining and assuring data accuracy and consistency over its entire lifecycle. If this factor is corrupted, data is lost due to a database error.

\n\n
    \n\t
  1. Interoperability
    2. \n
\n\n

All system components must follow a common and standard set of exchange formats to exchange data. It is essential to follow standards in order to ensure interoperability.

\n\n
    \n\t
  1. Usability 
    2. \n
\n\n

This feature concerns the users as it indicates how effectively they can learn and use a system. It defines how difficult it will be for a user to learn and operate the system. Usability can be assessed from different points of view such as the level of user friendliness and ease of use of the system or how simple it is to understand the interface, buttons and headings.

\n\n

 

\n\n
    \n\t
  1. Scalability
    2. \n
\n\n

The robustness or the elasticity of a system is a major quality to be considered.

\n\n

Failing to meet non-functional requirements will cause users dissatisfaction and will ultimately lead the system to fail in the market.

\n\n\n\n

This is a very critical feature in any system as it facilitates the integration of multiple IT components to work seamlessly together. Since COMESA Secretariat uses the sun system to process payment, the integration of the two systems is a must. The HRMS should also be able to integrate with other systems such as time and attendance, document management systems, workflow and Business Intelligence. It should provide standardized interfaces (APIs) or support industry-standard integration protocols to facilitate data exchange and interoperability.

\n\n
    \n\t
  1. Compliance
    2. \n
\n\n

The HRMS should adhere to relevant legal and regulatory requirements, such as data protection and privacy regulations (e.g., GDPR) and employment law. It should support features and controls to ensure compliance, such as data retention policies, audit trails, and consent management.

\n\n
    \n\t
  1. Mobile Compatibility
    2. \n
\n\n

HRMS should be accessible and functional on mobile devices, allowing users to perform essential tasks on smartphones or tablets. The user interface should be responsive and optimized for mobile screens, enabling employees and managers to access HR information on the go.

\n\n
    \n\t
  1. Project Deliverables
    2. \n
\n\n

The following mandatory deliverables should be provided:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

SN

\n\t\t\t		\n\t\t\t

Deliverable

\n\t\t\t		\n\t\t\t

Details

\n\t\t\t
\n\t\t\t

1.

\n\t\t\t		\n\t\t\t

Project Management Plan and Project Documents

\n\t\t\t		\n\t\t\t

The project management plan shall cover the following aspects:

\n\n\t\t\t
    \n\t\t\t\t
  1. Project approach and organization
    2. \n\t\t\t\t
  2. Requirement Management
    3. \n\t\t\t\t
  3. Scope Management
    4. \n\t\t\t\t
  4. Schedule Management
    5. \n\t\t\t\t
  5. Deliverable Plan
    6. \n\t\t\t\t
  6. Configuration management
    7. \n\t\t\t\t
  7. Quality Management
    8. \n\t\t\t\t
  8. Risk Management
    9. \n\t\t\t\t
  9. Change management, communication, and training plan
    10. \n\t\t\t\t
  10. Go-Live Plan
    11. \n\t\t\t\t
  11. Warranty service plan
    12. \n\t\t\t
\n\n\t\t\t

 

\n\n\t\t\t

The supplier shall update the project plan at the end of each project phases. Furthermore, the supplier is expected to provide regular weekly progress reports or as specified by COMESA project steering committee.

\n\t\t\t
\n\t\t\t

2.

\n\t\t\t		\n\t\t\t

Solution Blueprint

\n\t\t\t		\n\t\t\t

The solution blueprint shall cover all the functional, technical, migration and security requirements as well as the system architecture of the proposed solution.

\n\t\t\t
\n\t\t\t

3.

\n\t\t\t		\n\t\t\t

Training

\n\t\t\t		\n\t\t\t

Training for business users as well as Administration training for IT department and IT Auditor. A comprehensive user manuals and Administrator manual for each module configured shall be delivered.

\n\t\t\t
\n\t\t\t

4.

\n\t\t\t		\n\t\t\t

User Acceptance Test Document

\n\t\t\t		\n\t\t\t

Bidder should submit the UAT test scripts and ensure that all the UAT scenarios are catered for the requirements expressed by the users. The UAT exercise should consist of different rounds of testing. The bidder should ensure that a full-fledged testing has been carried out prior to UAT.

\n\t\t\t
\n\t\t\t

5.

\n\t\t\t		\n\t\t\t

A fully operational and bug free efficient system as per requirement

\n\t\t\t		\n\t\t\t

The supplier shall provide a fully operational and bug free system prior to Go-Live. The following will have to be addressed to the satisfaction of the users prior to Go-Live of the system:

\n\n\t\t\t
    \n\t\t\t\t
  1. All requirements of the users (including IT Security requirements) have been catered for in the Application Software.
    2. \n\t\t\t\t
  2. All identified scenarios are fully and comprehensively tested during each round of UAT.
    3. \n\t\t\t\t
  3. All bugs identified during UAT have been dealt with.
    4. \n\t\t\t\t
  4. Trainings on System Administration and Application Software have been delivered.
    5. \n\t\t\t\t
  5. All documentations are provided
    6. \n\t\t\t
\n\t\t\t
\n\t\t\t

6.

\n\t\t\t		\n\t\t\t

Commissioning report

\n\t\t\t		\n\t\t\t

The commissioning report shall include among others:

\n\n\t\t\t
    \n\t\t\t\t
  1. The level of customization for each module configured
    2. \n\t\t\t\t
  2. System setup document
    3. \n\t\t\t\t
  3. Security Policies
    4. \n\t\t\t
\n\n\t\t\t

The sign-off shall be done at the end of the operational acceptance.

\n\t\t\t
\n\t\t\t

6.

\n\t\t\t		\n\t\t\t

Warranty Plan

\n\t\t\t		\n\t\t\t

The bidder shall provide all the terms and condition of the warranty.

\n\t\t\t
\n\t\t\t

7.

\n\t\t\t		\n\t\t\t

Support Agreement

\n\t\t\t		\n\t\t\t

The bidder shall provide all the terms and condition of the support. Furthermore, the bidder should provide a monthly progress report on maintenance & support activities and a periodic SLA performance report.

\n\t\t\t
\n\n

 

\n\n

 

\n\n
    \n\t
  1. Other Requirements
    2. \n
\n\n
    \n\t
  1. The vendor is required to sign a Non-Disclosure Agreement (NDA).
    2. \n\t
  2. The system should support multilingual.
    3. \n\t
  3. The HRMS shall be developed using the latest and most up-to-date technologies and frameworks.
    4. \n\t
  4. The security features of the system shall meet industry standards and best practices.
    5. \n
\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Payment Terms
      2. \n\t
    \n\t
    2. \n
\n\n

The structure of payment shall be as follows:

\n\n
    \n\t
  1. Implementation Services
    2. \n
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

S.N

\n\t\t\t		\n\t\t\t

Deliverable

\n\t\t\t		\n\t\t\t

Payment

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Inception Report with agreed project implementation plan

\n\t\t\t		\n\t\t\t

20%

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Detailed Software Requirements Specifications

\n\t\t\t		\n\t\t\t

30%

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Solution Prototype based on the Solution Blueprint

\n\t\t\t		\n\t\t\t

30%

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Go-live

\n\t\t\t		\n\t\t\t

20%

\n\t\t\t
\n\n
    \n\t
  1. Support Services
    2. \n
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

S.N

\n\t\t\t		\n\t\t\t

Deliverable

\n\t\t\t		\n\t\t\t

Payment

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

12 Months post go-live Warranty

\n\t\t\t		\n\t\t\t

0%

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Annual Maintenance Contract

\n\t\t\t		\n\t\t\t

25% per quarter

\n\t\t\t
\n\n

 

\n\n

Bidders shall give a breakdown of the prices as per below Bill of Quantity:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Items

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Qty

\n\t\t\t		\n\t\t\t

Unit

\n\t\t\t		\n\t\t\t

Amount (USD)

\n\t\t\t
\n\t\t\t

Implementation of HCM Modules (Recruitment and Selection, Onboarding, Human Resource, Training & Development, Leave Management, Performance Management, Time & Attendance, Employee Self-service) & Interfaces including 1 year full warranty.

\n\t\t\t		\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Lot

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Implementation of Payroll module, Self-Services & Interfaces including 1 year full warranty.

\n\t\t\t		\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Lot

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Reports and Analytics Module

\n\t\t\t		\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Lot

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Training on HCM Modules

\n\t\t\t		\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Lot

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Training on Payroll module

\n\t\t\t		\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Lot

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

1 Year Full Maintenance – HCM Modules

\n\t\t\t		\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Lot

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

1 Year Full Maintenance – Payroll Modules

\n\t\t\t		\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Lot

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\n

 

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Project Approach, Methodology & Governance
      2. \n\t
    \n\t
    2. \n
\n\n

The bidder is expected to describe how the firm intends to manage all aspects of the work to be performed, including schedules for completion of tasks/subtasks, procedures for scheduling and cost control.

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Testing, Quality Assurance & Change Management
      2. \n\t
    \n\t
    2. \n\t
  2. Testing and UAT
    3. \n
\n\n

The supplier should commit to submit Unit Test Plans, System Test Plans, Integration Test Plans, Load and Stress Test Plan. The Test Results should be submitted to COMESA as evidence of full-fledged testing carried out prior to UAT.

\n\n

The supplier should submit UAT test scripts to ensure that the UAT scenarios cater for all the requirements expressed by the users. A comprehensive user manual should be made available before the training.

\n\n

 

\n\n

The UAT exercise should consist of different rounds of testing as follows:

\n\n
    \n\t
  1. Round 1 should consist of executing all the test scenarios business flow wise and identify list of issues if any by the users
    2. \n\t
  2. Bidder should commit to ensure that issues identified in Round 1 are fully addressed to the satisfaction of the users prior to starting the next round (Round 2)
    3. \n\t
  3. Bidder should also commit to producing evidence that that non-regression testing has been performed prior to starting next round,
    4. \n\t
  4. Subsequent rounds are conducted until no further issues are identified.
    5. \n
\n\n
    \n\t
  1. Quality Assurance Plan
    2. \n
\n\n

The bidder shall provide a proper Quality Assurance plan to ensure the success of project.  The bidder should ensure that all work products are evaluated and that evidence is provided to the fact that:

\n\n
    \n\t
  1. It conforms to specified requirements.
    2. \n\t
  2. It has been produced according to the project standards and processes.
    3. \n
\n\n
    \n\t
  1. Change Management
    2. \n
\n\n

As the implementation and adoption of business process changes will be vital to the success of the project, the consultant should be able to explain and communicate business process changes and their associated requirements to individuals throughout the COMESA including to executive managers, division heads, subject matter experts, and end-users. The consultant shall provide guidance and mentor the project core team to successfully implement the overall business transformation and system changes for the COMESA.

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Project Timeline
      2. \n\t
    \n\t
    2. \n
\n\n

Based upon the proposed project approach and work plan, provide a Project Gantt chart detailing the project schedule, phase, task and subtask duration, proposed phasing for roll-out of proposed system and highlight key milestone dates that illustrates the duration of tasks listed in the scope of work and identifies results and deliverable milestones.

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Company Profile and Profile of Consultants
      2. \n\t
    \n\t
    2. \n
\n\n

A company profile of the Bidder as well as a list of staff that would be involved in the project and their respective qualifications and experience should be provided.

\n\n

In this respect, Bidders are required to submit information on reference sites and staff profiles as per format at Annex II

\n\n

COMESA shall be notified in writing of any change or replacement of staff being assigned on the project as per their response of the bidding document. Respective qualifications and experience of any new staff joining the implementation team should be provided. COMESA reserves the right to approve any such change.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Customer References
      2. \n\t
    \n\t
    2. \n
\n\n

To be eligible for this exercise, bidders should have at least three (3) reference sites where they have successfully implemented a similar project.

\n\n
    \n\t
  1. Annexes
    2. \n
\n\n

Annex 1: Team Composition Template

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Table 1: Work Assignment and Manpower Input in Man Months

\n\t\t\t
\n\t\t\t

SN

\n\t\t\t		\n\t\t\t

Name of Expert

\n\t\t\t		\n\t\t\t

Designation

\n\t\t\t		\n\t\t\t

Manpower Input in Months

\n\t\t\t
\n\t\t\t

Remote

\n\t\t\t		\n\t\t\t

On-Site

\n\t\t\t		\n\t\t\t

Total

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

John Doe

\n\t\t\t		\n\t\t\t

Project Manager

\n\t\t\t		\n\t\t\t

2

\n\t\t\t		\n\t\t\t

4

\n\t\t\t		\n\t\t\t

6

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Jane Doe

\n\t\t\t		\n\t\t\t

Solution Architect

\n\t\t\t		\n\t\t\t

0

\n\t\t\t		\n\t\t\t

6

\n\t\t\t		\n\t\t\t

6

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Expert III

\n\t\t\t		\n\t\t\t

Designation III

\n\t\t\t		\n\t\t\t

2

\n\t\t\t		\n\t\t\t

4

\n\t\t\t		\n\t\t\t

6

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Expert IV

\n\t\t\t		\n\t\t\t

Designation IV

\n\t\t\t		\n\t\t\t

3

\n\t\t\t		\n\t\t\t

3

\n\t\t\t		\n\t\t\t

6

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Expert V

\n\t\t\t		\n\t\t\t

Designation V

\n\t\t\t		\n\t\t\t

5

\n\t\t\t		\n\t\t\t

1

\n\t\t\t		\n\t\t\t

6

\n\t\t\t
\n\t\t\t

6

\n\t\t\t		\n\t\t\t

Expert VI

\n\t\t\t		\n\t\t\t

Designation VI

\n\t\t\t		\n\t\t\t

2

\n\t\t\t		\n\t\t\t

4

\n\t\t\t		\n\t\t\t

6

\n\t\t\t
\n\t\t\t

7

\n\t\t\t		\n\t\t\t

Expert VII

\n\t\t\t		\n\t\t\t

Designation VII

\n\t\t\t		\n\t\t\t

2

\n\t\t\t		\n\t\t\t

4

\n\t\t\t		\n\t\t\t

6

\n\t\t\t
\n\t\t\t

8

\n\t\t\t		\n\t\t\t

Expert VIII

\n\t\t\t		\n\t\t\t

Designation VIII

\n\t\t\t		\n\t\t\t

1

\n\t\t\t		\n\t\t\t

5

\n\t\t\t		\n\t\t\t

6

\n\t\t\t
\n\n

 

\n\n

Annex 2: Individual Team Profiles       

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Curriculum Vitae: Expert 1

\n\t\t\t
\n\t\t\t

Role in the Project

\n\t\t\t		\n\t\t\t

Role X

\n\t\t\t
\n\t\t\t

Name of Expert

\n\t\t\t		\n\t\t\t

Expert 1

\n\t\t\t
\n\t\t\t

Date of Birth

\n\t\t\t		\n\t\t\t

Dd/mm/yyyy

\n\t\t\t
\n\t\t\t

Nationality

\n\t\t\t		\n\t\t\t

XXXX

\n\t\t\t
\n\t\t\t

Education

\n\t\t\t
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Degree

\n\t\t\t		\n\t\t\t

College

\n\t\t\t		\n\t\t\t

Year

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Bacheleor of Science XXX

\n\t\t\t		\n\t\t\t

College Name

\n\t\t\t		\n\t\t\t

2002

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Master of Science XXX

\n\t\t\t		\n\t\t\t

College Name

\n\t\t\t		\n\t\t\t

2010

\n\t\t\t
\n\t\t\t

Professional Certifications

\n\t\t\t
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Certification

\n\t\t\t		\n\t\t\t

Body and Number

\n\t\t\t		\n\t\t\t

Status

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Certified XXX

\n\t\t\t		\n\t\t\t

Body X Certificate #

\n\t\t\t		\n\t\t\t

Active

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Certified XXX

\n\t\t\t		\n\t\t\t

Body X Certificate #

\n\t\t\t		\n\t\t\t

Expired

\n\t\t\t
\n\t\t\t

Expert Profile Summary

\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Work Experience

\n\t\t\t
\n\t\t\t

No

\n\t\t\t		\n\t\t\t

Employer

\n\t\t\t		\n\t\t\t

From

\n\t\t\t		\n\t\t\t

To

\n\t\t\t		\n\t\t\t

Designation

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Employer X

\n\t\t\t		\n\t\t\t

00/00/0000

\n\t\t\t		\n\t\t\t

00/00/0000

\n\t\t\t		\n\t\t\t

Designation x

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Employer X

\n\t\t\t		\n\t\t\t

00/00/0000

\n\t\t\t		\n\t\t\t

00/00/0000

\n\t\t\t		\n\t\t\t

Designation x

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Employer X

\n\t\t\t		\n\t\t\t

00/00/0000

\n\t\t\t		\n\t\t\t

00/00/0000

\n\t\t\t		\n\t\t\t

Designation x

\n\t\t\t
\n\t\t\t

Project Experience Related to Current Assignment

\n\t\t\t
\n\t\t\t

Project Client

\n\t\t\t		\n\t\t\t

Client Name

\n\t\t\t
\n\t\t\t

Project Summary

\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Responsibilities in the project

\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Technologies Used

\n\t\t\t		\n\t\t\t

Technology 1, Technology 2, Technology N

\n\t\t\t
\n\t\t\t

Sign

\n\t\t\t		\n\t\t\t

Expert Signature

\n\t\t\t		\n\t\t\t

Date

\n\t\t\t		\n\t\t\t

00/00/00

\n\t\t\t
       
\n\n

 

"},{"id":"OP00237823","notice_type":"Request for Expression of Interest","noticedate":"18-Oct-2023","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2023-11-10T00:00:00Z","submission_deadline_time":"15:30","project_ctry_name":"Mozambique","project_id":"P173178","project_name":"Managing Public Resources for Service Delivery","bid_reference_no":"MZ-MEF - GEPRES-345292-CS-INDV","bid_description":"Quality Assurance Consultant for Tax Portal","procurement_group":"CS","procurement_method_code":"INDV","procurement_method_name":"Individual Consultant Selection","contact_address":"PRACA DA MARINHA \nP.O.BOX 272 MAPUTO","contact_ctry_name":"Mozambique","contact_email":"mefaquisicoes@gmail.com","contact_name":"Claudina Cassamo de Sá","contact_organization":"Ministry of Economy and Finance - GEPRES","contact_phone_no":"+258 82 307 0652","submission_date":"2023-10-18T00:00:00Z","notice_text":"

MINISTRY OF ECONOMY AND FINANCE

Managing Public Resources for Service Delivery Project

(GEPRES)

 

REQUEST FOR EXPRESSION OF INTEREST

(Individual Consultant)

 

Assignment title: Quality Assurance for the Taxpayers Portal

Reference nr: MZ-MEF-GEPRES -345292/345319

Loan/Grant Number: G 947-MZ

  1. The Government of Mozambique through the Ministry of Economy and Finance has received a Grant from the World Bank toward the cost of the Managing Public Resources for Service Delivery Project (GEPRES), and intends to apply part of the proceeds for the recruitment of two individual consultants specialized to provide services as Quality Assurance for the Taxpayers Portal.
  2. The consulting services (“the services”) include the following activities without prejudice to others not listed or included in Terms of References:

           a) Assess the current architecture of development/production, systems dependency, technologies used, process analysis and data structure;

           b) Ensure the implementation of a continuous integration (CI) and continuous delivery (CD) environment based on Jenkins, including Plug-ins: Maven,                     Junit, Ant, pipeline, antifactory;

           c) Ensure development of a TDD (Test Driven Development) culture with a minimum 80% coverage;

           d) Undertake trainings and workshops of automated testing of the tools to be applied;

           e) Apply advanced test automation;

           f) Ensure standardization of frameworks development, artefacts and process support architecture;  

           g) Tests results monitoring;

           h) Identify the root causes of failures;

           i) Ensure the monitoring of the application within production environment (Troubleshooting); 

           j) Apply automated tests throughout the portal development process:

 

     3. The consulting services will be carried out within a period of 18 months.

     4. The detailed Terms of Reference (TOR) for the assignment can be obtained through email mefaquisicoes@gmail.com or at the address given below.

     5. The attention of interested consultants is drawn to section III, paragraphs 2.14, 3.16, and 3.17 of the World Bank’s Procurement Regulations for IPF                          Borrowers, November 2020 (“Procurement Regulations”), setting forth the World Bank’s policy on conflict of interest.

      6. The Ministry of Economy and Finance through the Managing Public Resources for Service Delivery Project (GEPRES), now invites eligible Individual                   consultants (“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 in the form of a curriculum vitae (CV). A consultant will be selected in                   accordance with the individual consultant selection (IC) method set out in the World Bank’ Project Consultancy guideline edition of November 2020 that               can be accessed via the World Bank website at www.world bank.org/ procurement.

       7. The attention of interested Consultants is drawn to the minimum qualification criteria for the Consultancy are:

            Mandatory Requirements:

             Desirable requirements:

      8. Further information can be obtained at the address stated below during the office hours from 7:30 a.m. to 3:30 p.m(local time).

      9. Expressions of interest in the form of submission letter accompanied by a curriculum vitae (CV) must be delivered in a written form to the address below                directly by person or by mail, or by email by November 10th, 2023, at 3:30 p.m. (local time).

       10. Address:

             Ministry of Economy and Finance,

             Managing Public Resources for Service Delivery Project (GEPRES),

             449/469, Julius Nyerere Avenue, Bloc A, 13rd floor (Reception Room of the Procurement Department)

             Tel: +258 21 481 600/1 or +258 82 307 0652

             Email: mefaquisicoes@gmail.com

             Maputo – Mozambique

"},{"id":"OP00253147","notice_type":"Request for Expression of Interest","noticedate":"18-Oct-2023","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2023-11-10T00:00:00Z","submission_deadline_time":"15:30","project_ctry_name":"Mozambique","project_id":"P173178","project_name":"Managing Public Resources for Service Delivery","bid_reference_no":"MZ-MEF - GEPRES-345319-CS-INDV","bid_description":"Quality Assurance Consultant for Tax Portal 2","procurement_group":"CS","procurement_method_code":"INDV","procurement_method_name":"Individual Consultant Selection","contact_address":"PRACA DA MARINHA \nP.O.BOX 272 MAPUTO","contact_ctry_name":"Mozambique","contact_email":"mefaquisicoes@gmail.com","contact_name":"Claudina Cassamo de Sá","contact_organization":"Ministry of Economy and Finance - GEPRES","contact_phone_no":"+258 82 307 0652","submission_date":"2023-10-18T00:00:00Z","notice_text":"

MINISTRY OF ECONOMY AND FINANCE

Managing Public Resources for Service Delivery Project

(GEPRES)

 

REQUEST FOR EXPRESSION OF INTEREST

(Individual Consultant)

 

Assignment title: Quality Assurance for the Taxpayers Portal

Reference nr: MZ-MEF-GEPRES -345292/345319

Loan/Grant Number: G 947-MZ

  1. The Government of Mozambique through the Ministry of Economy and Finance has received a Grant from the World Bank toward the cost of the Managing Public Resources for Service Delivery Project (GEPRES), and intends to apply part of the proceeds for the recruitment of two individual consultants specialized to provide services as Quality Assurance for the Taxpayers Portal.
  2. The consulting services (“the services”) include the following activities without prejudice to others not listed or included in Terms of References:

           a) Assess the current architecture of development/production, systems dependency, technologies used, process analysis and data structure;

           b) Ensure the implementation of a continuous integration (CI) and continuous delivery (CD) environment based on Jenkins, including Plug-ins: Maven,                     Junit, Ant, pipeline, antifactory;

           c) Ensure development of a TDD (Test Driven Development) culture with a minimum 80% coverage;

           d) Undertake trainings and workshops of automated testing of the tools to be applied;

           e) Apply advanced test automation;

           f) Ensure standardization of frameworks development, artefacts and process support architecture;  

           g) Tests results monitoring;

           h) Identify the root causes of failures;

           i) Ensure the monitoring of the application within production environment (Troubleshooting); 

           j) Apply automated tests throughout the portal development process:

 

     3. The consulting services will be carried out within a period of 18 months.

     4. The detailed Terms of Reference (TOR) for the assignment can be obtained through email mefaquisicoes@gmail.com or at the address given below.

     5. The attention of interested consultants is drawn to section III, paragraphs 2.14, 3.16, and 3.17 of the World Bank’s Procurement Regulations for IPF                          Borrowers, November 2020 (“Procurement Regulations”), setting forth the World Bank’s policy on conflict of interest.

      6. The Ministry of Economy and Finance through the Managing Public Resources for Service Delivery Project (GEPRES), now invites eligible Individual                   consultants (“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 in the form of a curriculum vitae (CV). A consultant will be selected in                   accordance with the individual consultant selection (IC) method set out in the World Bank’ Project Consultancy guideline edition of November 2020 that               can be accessed via the World Bank website at www.world bank.org/ procurement.

       7. The attention of interested Consultants is drawn to the minimum qualification criteria for the Consultancy are:

            Mandatory Requirements:

             Desirable requirements:

      8. Further information can be obtained at the address stated below during the office hours from 7:30 a.m. to 3:30 p.m(local time).

      9. Expressions of interest in the form of submission letter accompanied by a curriculum vitae (CV) must be delivered in a written form to the address below                directly by person or by mail, or by email by November 10th, 2023, at 3:30 p.m. (local time).

       10. Address:

             Ministry of Economy and Finance,

             Managing Public Resources for Service Delivery Project (GEPRES),

             449/469, Julius Nyerere Avenue, Bloc A, 13rd floor (Reception Room of the Procurement Department)

             Tel: +258 21 481 600/1 or +258 82 307 0652

             Email: mefaquisicoes@gmail.com

             Maputo – Mozambique

"},{"id":"OP00218284","notice_type":"Request for Expression of Interest","noticedate":"13-Mar-2023","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2023-03-19T00:00:00Z","submission_deadline_time":"14:00","project_ctry_name":"Bangladesh","project_id":"P174085","project_name":"Recovery and Advancement of Informal Sector Employment","bid_reference_no":"PKSF/RAISE/S-04.2","bid_description":"Selection of a Consulting Firm for the development of Integrated Management Information System","procurement_group":"CS","procurement_method_code":"QCBS","procurement_method_name":"Quality And Cost-Based Selection","contact_address":"PKSF Bhaban,\nPlot: E-4/B, Agargaon Administrative Area,\nSher-e-Bangla Nagar\nDhaka-1207","contact_ctry_name":"Bangladesh","contact_email":"raise.procurement@gmail.com","contact_name":"AQM Golam Mawl","contact_organization":"Palli Karma-Sahayak Foundation","contact_phone_no":"880-2-8181658-61","contact_web_url":"http://pksf.org.bd","submission_date":"2023-03-13T00:00:00Z","notice_text":"

PALLI KARMA-SAHAYAK FOUNDATION (PKSF)

PKSF Bhaban, E-4/B, Agargaon Administrative Area, Sher-e-Bangla Nagar Dhaka-1207, Bangladesh

Tel: 880-2-8181658-61, 8181664-9, 8181169; Fax: 880-2-8181671, 8181678 Website: www.pksf.org.bd

Memo No. 53.23.0000.041.20.001.22.793                                                                                 Date: 01.03.2023

REQUEST FOR EXPRESSION OF INTEREST (REoI)

(IT CONSULTING SERVICES - FIRMS SELECTION)

Country: Bangladesh

Name of Project: Recovery and Advancement of Informal Sector Employment (RAISE)

Credit No: 6841-BD

Assignment Title: Selection of a Consulting Firm for the development of Integrated Management Information System.

Reference No: PKSF/RAISE/S-4.2

The Government of Bangladesh has received finance from the World Bank and implementing an economic inclusion program through the Palli Karma-Sahayak Foundation (PKSF) for low-income, less-educated urban youth, for low-income microentrepreneurs and self-employed in urban areas whose livelihoods have been impacted by COVID-19. PKSF intends to apply a portion of the financing to procure services of a consultant for the design, development, and service integration of the RAISE Management Information System (MIS).

  1. The main objective of this assignment is to hire a qualified MIS/IT firm (Consultant hereafter) for the design, development, customization, commissioning and implementation of the MIS to make it a scalable and integrated MIS Platform that facilitates end-to-end automation of the core PKSF business functions through a unified IT Platform. In this regard, the following objectives needs to achieve as the part of this project execution.
  2. The consulting service (“the Services”) include but not limited to

The assignment will be estimated 51 professional staff-months and also non-key expert as required mentioned in the TOR, implementation period will approximately 6 months, expected start date of assignment may be from May, 2023 for ensuring full consistency with the TOR.

  1. The Government of Bangladesh, through the Palli Karma-Sahayak Foundation (PKSF), now invites eligible consulting firms (“Consultants”) to show 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.

The shortlisting criteria are:

  1. General Experience of the Firm’s;
  2. Experience in similar assignments of compatible size, complexity and technical specialty in required area;
  3. Financial Soundness, staffing and logistics of the firm;
  4. Experience of working with development partner funded project or development agencies regarding software development;

Consultants are requested to submit the following supporting documents in support of the above-mentioned criteria:

  1. Up to Date Relevant Legal Papers of the Firm’s including TIN,VAT, BASIS membership, CMMI-DEV-3, and ISO certification;
  2. JV Agreement/Letter of Intent (if applicable) along with the proposed JV agreement;
  3. Firm’s brochure including staffing and logistics;
  4. Strong financial capability will be required (Need to submit cash flow statement and balance sheet ONLY of last 3 years’ audit report);
  5. List of IT service experience records of last 15 (Fifteen) years (including employer, duration, location of service, nature, total cost of contract, etc.); (Tentatively within 60 pages)
  6. All other items necessary to substantiate satisfaction of the shortlisting criteria listed above and/or included in the TOR; However, Key experts will not be evaluated at the shortlisting stage.   
  1. The attention of interested IT/Consulting firms is drawn to Section III, paragraphs-3.14, 3.16 and 3.17 of the World Bank’s “Procurement Regulations for IPF Borrowers” November 2020 (“Procurement Regulations”), setting forth with the World Bank’s policy on conflict of interest.
  2. Consultants may associate with other firms to enhance their qualifications, but should indicate clearly whether the association is in the form of a Joint Venture and/or a Sub-consultancy. In the case of a joint venture, all the partners in the joint venture shall be jointly and severally liable for the entire contract, if selected. In the case of an Association, all members of such “Association” should have real and well-defined inputs to the assignment and in such “Association” it is preferable to limit the total number of firms including the Associates to a maximum of two (2).
  3. A Consultant will be selected in accordance with the Quality and Cost Based Selection (QCBS) method set out in the procurement regulations.
  4. Further information can be obtained at the address below during office hours, 0900 to 1600 hours. The detailed Term of Reference (TOR) for the assignment can be downloaded from www.pksf.org.bd website or can be obtained upon request from the address below or either by e-mail or in person during the office hours (Local Time: 09:00 to 16:00 hours).
  5. Expression of Interest (EOI) must be delivered in a written form to the address below (in-person, or by mail) by 19 March, 2023 on or before 14:00 hours (UTC+6 hours).
  6. The Procuring Entity (PE) reserves the right to accept or reject any or all EOI’s without assigning any reason whatsoever.
"},{"id":"OP00156550","notice_type":"Request for Expression of Interest","noticedate":"30-Nov-2021","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2021-12-17T00:00:00Z","submission_deadline_time":"18:00","project_ctry_name":"Uzbekistan","project_id":"P168180","project_name":"Institutional Capacity Building Project","bid_reference_no":"UZ-MOF-SAMA-QCBS-SYSTEM","bid_description":"Development and Implementation of an Automated System of Accounting and Monitoring for the Activities of Enterprises with State Participation","procurement_group":"CS","procurement_method_code":"QCBS","procurement_method_name":"Quality And Cost-Based Selection","contact_address":"29, Istiklol str. Tashkent","contact_ctry_name":"Uzbekistan","contact_email":"axaydarov@mf.uz","contact_name":"Ahadbek Khaydarov","contact_organization":"Ministry of Finance of the Republic of Uzbekistan","contact_phone_no":"+ 998 71 2394646","contact_web_url":"www.mf.uz","submission_date":"2021-11-30T00:00:00Z","notice_text":"

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

\n\n

 

\n\n

Uzbekistan

\n\n

Institutional Capacity Building Project

\n\n

Credit No.: IDA 6431-UZ

\n\n

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

\n\n

 

\n\n

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

\n\n

 

\n\n

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).

\n\n

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”)

\n\n

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.

\n\n

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.

\n\n

The qualification requirements for the Consultants are:

\n\n\n\n

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.

\n\n

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

\n\n

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.

\n\n

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

\n\n

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

\n\n

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.

\n\n

Project Implementation Unit under the
\nMinistry of Finance of the Republic of Uzbekistan

\n\n

Attn: Foziljon Kalandarov, Manager of the Project

\n\n

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

\n\n

Tel: +998907380050

\n\n

E-mail: piu_mof@mail.ru

\n\n

 

\n\n

 

\n\n

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

\n\n\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Date:

\n\t\t\t		\n\t\t\t

Country of Incorporation:

\n\t\t\t
\n\t\t\t

Consultant Name:

\n\t\t\t		\n\t\t\t

Acronym:

\n\t\t\t
\n\t\t\t

EOI Submission Authorized by:

\n\t\t\t		\n\t\t\t

Position

\n\t\t\t
\n\n

 

\n\n\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Consultant

\n\t\t\t		\n\t\t\t

Acronym

\n\t\t\t		\n\t\t\t

Country of Incorporation

\n\t\t\t		\n\t\t\t

Joint Venture (JV) or Sub-consultant

\n\t\t\t		\n\t\t\t

EOI Submission Authorized By

\n\t\t\t		\n\t\t\t

Position

\n\t\t\t
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
      
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\n

 

\n\n

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.

\n\n

 

\n\n\n\n

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

\n\n

 

\n\n\n\n

 

\n\n

Project References, present experiences in similar geographic areas.

\n\n

 

\n\n\n\n\n\n\n\n

 

\n\n

 

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

N

\n\t\t\t		\n\t\t\t

Project

\n\t\t\t		\n\t\t\t

Project start date (year, month, mandatory)

\n\t\t\t		\n\t\t\t

Project end date (year, month, mandatory)

\n\t\t\t		\n\t\t\t

Client

\n\t\t\t		\n\t\t\t

Country

\n\t\t\t		\n\t\t\t

Firm

\n\t\t\t		\n\t\t\t

Participated experts in the project among the recommended personnel (full name)

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		 \n\t\t\t

 

\n\t\t\t		   \n\t\t\t

 

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		 \n\t\t\t

 

\n\t\t\t		   \n\t\t\t

 

\n\t\t\t
\n\t\t\t

…

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

…

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

…

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

10

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\n

 

\n\n\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Project Title

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Country / Region

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Start Date

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Completion Date

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Continuous / Intermittent

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Client

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Participated experts in the project among the recommended personnel (full name)

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Funding Source

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Project description

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

The role of the consulting firm

\n\t\t\t		\n\t\t\t

(indicate your role and contribution in terms of men-months)

\n\t\t\t
\n\n

 

\n\n\n\n

 

\n\n

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

\n\n

 

\n\n\n\n

 

\n\n\n\n

 

\n\n\n\n

 

\n\n\n\n

 

\n\n\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 

\n\t\t\t
\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

TERMS OF REFERENCE

\n\n

For the project

\n\n

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

\n\n

 

\n\n

 

\n\n

on 68 sheets

\n\n

 

\n\n

 

\n\n

valid from "___" ____________ 2021

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

Tashkent 2021

\n\n

 

\n\n

 

\n\n

1.      GENERAL INFORMATION.. 7

\n\n

1.1.      Full name of the project and its symbol 7

\n\n

1.2.      Customer 7

\n\n

1.3.      Executor 7

\n\n

1.4.      Basis for development 8

\n\n

1.5.      Planned start and finish dates. 9

\n\n

1.6.      Sources of financing. 9

\n\n

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

\n\n

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

\n\n

2.1.      Purpose of the system.. 10

\n\n

2.2.      Project implementation goals. 11

\n\n

2.3.      Expected deliverables. 12

\n\n

3.      CHARACTERISTICS OF THE INFORMATION OBJECT. 13

\n\n

3.1.      General information. 13

\n\n

3.2.      Architecture and composition of the current solution. 14

\n\n

3.2.1.       Organizational scope of the project 19

\n\n

3.3.      Process volume. 20

\n\n

3.3.1.       Optimization and automation of business processes. 20

\n\n

4.      SYSTEM REQUIREMENTS. 20

\n\n

4.1.      System requirements as a whole. 20

\n\n

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

\n\n

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

\n\n

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

\n\n

4.1.4.       System Diagnostic Requirements. 28

\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n

4.1.7.2.1.        Required mode of operation of IS personnel 31

\n\n

4.1.8.       Indicators of appointment 32

\n\n

4.1.9.       Reliability requirements. 33

\n\n

4.1.10.         Safety requirements. 36

\n\n

4.1.10.1.     Requirements for protecting information from unauthorized access. 37

\n\n

4.1.10.2.     Requirements for the differentiation of access rights. 37

\n\n

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

\n\n

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

\n\n

4.1.11.         Ergonomic and technical aesthetics requirements. 39

\n\n

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

\n\n

4.1.13.         Requirements for patent and license purity. 40

\n\n

4.1.14.         Requirements for standardization and unification. 41

\n\n

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

\n\n

4.1.16.         Software technical support requirements. 42

\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n

4.2.2.       Connecting of source systems. 49

\n\n

4.3.      Requirements to types of support 50

\n\n

4.3.1.       Requirements for software. 50

\n\n

4.3.2.       Information support requirements. 51

\n\n

4.3.3.       Requirements for information exchange between system components. 52

\n\n

4.3.4.       Linguistic requirements. 52

\n\n

4.3.5.       Software Requirements. 53

\n\n

4.3.6.       Requirements for metrological support 54

\n\n

4.3.7.       Requirements for technical support 54

\n\n

4.3.8.       Requirements for methodological support 54

\n\n

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

\n\n

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

\n\n

6.      SYSTEM CONTROL AND ACCEPTANCE PROCEDURE. 59

\n\n

6.1.      Types, scope and test methods. 60

\n\n

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

\n\n

6.3.      Requirements for managing organizational change. 62

\n\n

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

\n\n

8.      DOCUMENTATION REQUIREMENTS. 67

\n\n

8.1.      Project documentation. 67

\n\n

9.      SOURCES OF DEVELOPMENT. 67

\n\n

10.        PROJECT ASSUMPTIONS AND RESTRICTIONS. 68

\n\n

10.1.        Organizational Assumptions and Constraints. 68

\n\n

10.2.        Restrictions on the scope of work. 69

\n\n

10.3.        Limitations on the scope of work. 69

\n\n

10.4.        Limitations on implemented functionality. 69

\n\n

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

\n\n

10.6.        Terms of the Project execution. 70

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

LIST OF SYMBOLS, ABBREVIATIONS AND TERMS

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

DWH (QCD)

\n\t\t\t		\n\t\t\t

Data Warehouse

\n\t\t\t
\n\t\t\t

HD

\n\t\t\t		\n\t\t\t

Data store

\n\t\t\t
\n\t\t\t

BI

\n\t\t\t		\n\t\t\t

Business Intelligence - reporting and analysis system

\n\t\t\t
\n\t\t\t

RH

\n\t\t\t		\n\t\t\t

Guidance document

\n\t\t\t
\n\t\t\t

O'z DSt

\n\t\t\t		\n\t\t\t

State standard of the Republic of Uzbekistan

\n\t\t\t
\n\t\t\t

AWP

\n\t\t\t		\n\t\t\t

Automated workplace

\n\t\t\t
\n\t\t\t

DB

\n\t\t\t		\n\t\t\t

Database

\n\t\t\t
\n\t\t\t

GOST

\n\t\t\t		\n\t\t\t

State standard

\n\t\t\t
\n\t\t\t

ICT

\n\t\t\t		\n\t\t\t

Information and communication technologies

\n\t\t\t
\n\t\t\t

ISO / IEC (ISO / IEC)

\n\t\t\t		\n\t\t\t

International standard

\n\t\t\t
\n\t\t\t

LAN

\n\t\t\t		\n\t\t\t

Local area network

\n\t\t\t
\n\t\t\t

OS

\n\t\t\t		\n\t\t\t

Operating system

\n\t\t\t
\n\t\t\t

PC

\n\t\t\t		\n\t\t\t

Personal Computer

\n\t\t\t
\n\t\t\t

IB

\n\t\t\t		\n\t\t\t

Information Security

\n\t\t\t
\n\t\t\t

IT

\n\t\t\t		\n\t\t\t

Information Technology

\n\t\t\t
\n\t\t\t

IS

\n\t\t\t		\n\t\t\t

Information system

\n\t\t\t
\n\t\t\t

KS

\n\t\t\t		\n\t\t\t

Corporate network

\n\t\t\t
\n\t\t\t

ON

\n\t\t\t		\n\t\t\t

Software

\n\t\t\t
\n\t\t\t

IUI

\n\t\t\t		\n\t\t\t

Test program and methodology

\n\t\t\t
\n\t\t\t

SPD

\n\t\t\t		\n\t\t\t

Data transmission system

\n\t\t\t
\n\t\t\t

TT

\n\t\t\t		\n\t\t\t

Technical task

\n\t\t\t
\n\t\t\t

TC

\n\t\t\t		\n\t\t\t

Technical conditions

\n\t\t\t
\n\t\t\t

TR

\n\t\t\t		\n\t\t\t

Technical requirements

\n\t\t\t
\n\t\t\t

Dynamic reporting

\n\t\t\t		\n\t\t\t

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.

\n\t\t\t
\n\t\t\t

Static report

\n\t\t\t		\n\t\t\t

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.

\n\t\t\t
\n\t\t\t

STC

\n\t\t\t		\n\t\t\t

State Tax Committee

\n\t\t\t
\n\t\t\t

NAS

\n\t\t\t		\n\t\t\t

National accounting standards

\n\t\t\t
\n\t\t\t

IFRS

\n\t\t\t		\n\t\t\t

International Financial Reporting Standards

\n\t\t\t
\n\t\t\t

CRM

\n\t\t\t		\n\t\t\t

Customer Relationship Management

\n\t\t\t
\n\t\t\t

HR

\n\t\t\t		\n\t\t\t

Human Resource Management

\n\t\t\t
\n\t\t\t

KPI

\n\t\t\t		\n\t\t\t

Key Performance Indicator is a quantifiable indicator of actual results achieved.

\n\t\t\t
\n\n

 

\n\n

 

\n\n
    \n\t
  1. GENERAL INFORMATION\n\n\t
      \n\t\t
    1. Full name of the project and its symbol
      2. \n\t
    \n\t
    2. \n
\n\n

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").

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Customer
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

Requisites:

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Executor
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

Basic requirements for the contractor:

\n\n\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

The role of the specialist

\n\t\t\t		\n\t\t\t

Requirements

\n\t\t\t
\n\t\t\t

BI Project Manager

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Experience with BI for at least 5 years;
    • \n\t\t\t\t
  • Experience in managing at least two BI projects;
    • \n\t\t\t\t
  • Possession of a full range of knowledge and skills of project management;
    • \n\t\t\t\t
  • Experience in managing a project team of 15 people.
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

BI project architector

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Experience with BI for at least 5 years;
    • \n\t\t\t\t
  • Experience of participation in at least two projects for the development and implementation of BI class systems;
    • \n\t\t\t\t
  • Knowledge of programming languages ​​on the database server;
    • \n\t\t\t\t
  • Experience in the design of class BI systems.
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

BI Functional Consultant

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Experience with BI class systems for at least 3 years;
    • \n\t\t\t\t
  • Experience in participating in projects for the development and implementation of class BI systems;
    • \n\t\t\t\t
  • Knowledge of programming languages ​​on the database server;
    • \n\t\t\t\t
  • Experience in preparing technical documentation.
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

Financial consultant BI

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Experience with BI class systems for at least 3 years;
    • \n\t\t\t\t
  • Experience in participating in projects for the development and implementation of class BI systems;
    • \n\t\t\t\t
  • Experience in financial analysis projects in various sectors of the economy - at least 3x;
    • \n\t\t\t\t
  • Knowledge of IFRS reporting.
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

BI Technical Consultant

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Experience in working with data warehouses and BI class systems for at least 3 years;
    • \n\t\t\t\t
  • Experience in participating in projects for the development of data warehouses and implementation of BI class systems;
    • \n\t\t\t\t
  • Knowledge of programming languages ​​on the database server;
    • \n\t\t\t\t
  • Experience in the preparation of technical documentation for the developed solutions.
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

DBMS administrator

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Experience with BI for at least 3 years;
    • \n\t\t\t\t
  • Experience participating in at least 3 similar projects as a DB / BI administrator;
    • \n\t\t\t\t
  • Experience in administering BI environments.
    • \n\t\t\t
\n\t\t\t
\n\n

 

\n\n\n\n

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:

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Basis for development
      2. \n\t
    \n\t
    2. \n
\n\n

The basis for the development of the System project is:

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Planned start and finish dates
      2. \n\t
    \n\t
    2. \n
\n\n

Planned project implementation timeline:

\n\n

Start: September, 2021 

\n\n

Completion: February 2023

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Sources of financing
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. The procedure for registration and presentation of the results of work
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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

\n\n

To the Acceptance Commission, the Contractor submits documentation, the list
\nand requirements for registration of which are determined in accordance with GOSTs
\nand 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.

\n\n

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

\n\n

 

\n\n

 

\n\n

 

\n\n
    \n\t
  1. PURPOSE OF THE SYSTEM AND OBJECTIVES OF PROJECT IMPLEMENTATION
    2. \n
\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Purpose of the system
      2. \n\t
    \n\t
    2. \n
\n\n

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:

\n\n\n\n

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:

\n\n\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Project implementation goals
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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,
\ntaking 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.

\n\n

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.

\n\n

 

\n\n

The purpose of the system is:

\n\n\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Expected deliverables
      2. \n\t
    \n\t
    2. \n
\n\n

 

\n\n\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n
    \n\t
  1. CHARACTERISTICS OF THE INFORMATION OBJECT
    2. \n
\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. General information
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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

\n\n\n\n

 

\n\n

Also, the main participants in the project are:

\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n

Republican Stock Exchange - supplier of information on securities;

\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Architecture and composition of the current solution.
      2. \n\t
    \n\t
    2. \n
\n\n

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:

\n\n\n\n

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.
\n 

\n\n

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.

\n\n

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.

\n\n

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

\n\n

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.

\n\n

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

\n\n

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.

\n\n

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

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n


\np. 3.2.1 Architecture of the current solution.

\n\n

 

\n\n

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

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

System name

\n\t\t\t		\n\t\t\t

System Description

\n\t\t\t		\n\t\t\t

Data retrieval method

\n\t\t\t
\n\t\t\t

Internal systems of the Agency

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

IS "State Property"

\n\t\t\t		\n\t\t\t

Existing IS of business analysis

\n\t\t\t		\n\t\t\t

The existing IS "State Property" receives data from the Agency's database

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Agency DB

\n\t\t\t		\n\t\t\t

Existing DB

\n\t\t\t		\n\t\t\t

Formed database. The accumulation of the database comes from all of the following sources. The depth of historical data is 2 years.

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

www.property.davaktiv.uz

\n\t\t\t		\n\t\t\t

Register of state property of registration and submission of reports for legal entities in the form of state unitary enterprises and state enterprises.

\n\t\t\t		\n\t\t\t

Filling out forms posted on the web platform is carried out by enterprises in manual mode.

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

www.kpi.davaktiv.uz

\n\t\t\t		\n\t\t\t

Information portal for submitting reports by joint-stock companies and other business entities in the form of JSCs, LLCs, enterprises with a state share.

\n\t\t\t		\n\t\t\t

Filling out forms posted on the web platform is carried out by enterprises in manual mode.

\n\t\t\t
\n\t\t\t

External systems

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

STC DB

\n\t\t\t		\n\t\t\t

State Tax Committee database

\n\t\t\t		\n\t\t\t

Data collection from the STC DB collected on an automatic basis.

\n\t\t\t
\n\n

Tab. 3.2.1 Composition of internal and external systems.

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

The composition of the reporting forms (Table 3.2.2)

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Accepted reporting forms

\n\t\t\t
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Organizational and legal form

\n\t\t\t		\n\t\t\t

Reporting forms

\n\t\t\t		\n\t\t\t

Periodicity

\n\t\t\t		\n\t\t\t

Fill / receive method

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

•      Joint Stock Company (JSC);

\n\n\t\t\t

•      Limited Liability Company (LLC);

\n\n\t\t\t

•      State-owned enterprises

\n\t\t\t		\n\t\t\t

Reporting forms according to national accounting standards (NAS)

\n\n\t\t\t

•      Form No. 1 (small and medium enterprises)

\n\n\t\t\t

•      Form No. 2 (small and medium enterprises)

\n\n\t\t\t

•      Form No. 4 (Large enterprises)

\n\n\t\t\t

•      Form No. 5 (Large enterprises)

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Accepted by the Agency in automatic mode from the database of the STC

\n\t\t\t
\n\t\t\t

Key performance indicators (KPI) reporting form

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Filled in by enterprises manually on the web platform www.kpi.davaktiv.uz

\n\t\t\t
\n\t\t\t

Key performance indicators (KPI) reporting form for the financial and banking sector

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Filled in by enterprises manually on the web platform www.kpi.davaktiv.uz

\n\t\t\t
\n\t\t\t

Key performance indicators (KPI) reporting form for insurance companies

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Filled in by enterprises manually on the web platform www.kpi.davaktiv.uz

\n\t\t\t
\n\t\t\t

Reporting form - business plan

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Filled in by enterprises manually on the web platform www.kpi.davaktiv.uz

\n\t\t\t
\n\t\t\t

Reporting form according to international financial reporting standards (IFRS) for enterprises

\n\n\t\t\t

•      Statement of financial position

\n\n\t\t\t

•      Statement of comprehensive income

\n\n\t\t\t

•      Cash flow statement

\n\n\t\t\t

•      Statement of changes in equity

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Beginning of the reporting period - January 2022

\n\t\t\t
\n\t\t\t

Reporting form according to international financial reporting standards (IFRS) for the financial and banking sector

\n\n\t\t\t

•      Statement of financial position

\n\n\t\t\t

•      Profit or loss statement

\n\n\t\t\t

•      Statement of comprehensive income

\n\n\t\t\t

•      Cash flow statement

\n\n\t\t\t

•      Statement of changes in equity

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Beginning of the reporting period - January 2022

\n\t\t\t
\n\t\t\t

Management reporting

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Management reporting forms

\n\t\t\t		\n\t\t\t

Quarterly

\n\t\t\t		\n\t\t\t

Formed in the IS "State Property"

\n\t\t\t
\n\n

Tab. 3.2.2 Composition of reporting forms

\n\n

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

\n\n

 

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

TAS-IX Network

\n\t\t\t
\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

МСПД (interstate data transmission system)

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Firewall all

\n\t\t\t
\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Local computing

\n\n\t\t\t

network

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Applications server

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Database server

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Backup Applications

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Backup databases

\n\t\t\t
\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

p. 3.2.2. logical diagram of the existing technical complex

\n\n

 

\n\n

 

\n\n

 

\n\n

Key technical specifications for Application Server and Database Server:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Applications server

\n\t\t\t
\n\t\t\t

Fujitsu Database Server Primary rx2530 m4

\n\t\t\t		\n\t\t\t

CPU Intel Xeon Silver 4110 8c 2.10 GHz 2x

\n\n\t\t\t

DDR4 32GB

\n\n\t\t\t

HDD SATA 6G 1TBx4 SSD 256Gbx2

\n\n\t\t\t

 OS / Oracle Linux Unbreakable

\n\n\t\t\t

PSU 800W 2x

\n\n\t\t\t

LANs

\n\n\t\t\t

I350-AM2 (Onboard on D3383-A1x, on D3383-C1x

\n\n\t\t\t

Intel® C620 Chipset (1Gb / 10Gb Ethernet) (Onboard on D3383-C1x, on D3383-A1x)

\n\t\t\t
\n\t\t\t

Database server

\n\t\t\t
\n\t\t\t

Fujitsu Database Server Primary rx2530 m4

\n\t\t\t		\n\t\t\t

CPU Intel Xeon Silver 4110 8c 2.10 GHz 2x

\n\n\t\t\t

DDR4 32GB

\n\n\t\t\t

HDD SATA 6G 1TBx4 SSD 256Gbx2

\n\n\t\t\t

 OS / Oracle Linux Unbreakable

\n\n\t\t\t

PSU 800W 2x

\n\n\t\t\t

LANs

\n\n\t\t\t

I350-AM2 (Onboard on D3383-A1x, on D3383-C1x

\n\n\t\t\t

Intel® C620 Chipset (1Gb / 10Gb Ethernet) (Onboard on D3383-C1x, on D3383-A1x)

\n\t\t\t
\n\n

 

\n\n

Main challenges in working with the current information system:

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Organizational scope of the project
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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

\n\n

 

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

State Assets Management Agency

\n\n\t\t\t

of the Republic of Uzbekistan

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Rep. of Karakalpakstan

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Andijan region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Jizzakh region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Navoi region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Samarkand region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Syrdarya region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Khorezm region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Tashkent city

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Bukhara region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Kashkadarya region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Namangan region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Surkhandarya region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Ferghana region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 Tashkent region

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

1

\n\n\t\t\t

department

\n\t\t\t
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Total departments: 14

\n\n\t\t\t

Central department: 1

\n\t\t\t
\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Process volume\n\n\t\t
        \n\t\t\t
      1. Optimization and automation of business processes
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

 

\n\n
    \n\t
  1. SYSTEM REQUIREMENTS\n\n\t
      \n\t\t
    1. System requirements as a whole
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

The system should include the following subsystems:

\n\n\n\n

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

\n\n\n\n

 The system should be organized as follows:

\n\n\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the structure and functioning of the system
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

The system should provide high interactivity of work
\nwith 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).

\n\n

General system requirements.

\n\n

The system should be able to:

\n\n\n\n

 

\n\n

The system should contain the following subsystems:

\n\n\n\n

 

\n\n

The reporting forms issued by the System must include:

\n\n\n\n

p 4.1. General software architecture

\n\n

 

\n\n

Basic functional principles of the system

\n\n

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

\n\n\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the component composition and architecture of the solution
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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

\n\n

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.

\n\n

The main components of the platform:

\n\n\n\n\n\n

The system under development should include the following technological components:

\n\n\n\n

 

\n\n

 

\n\n

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

\n\n

More detailed requirements are indicated in clauses 4.1.9 and 4.2.

\n\n

 

\n\n

Requirements for modes of operation

\n\n

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:

\n\n

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

\n\n

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

\n\n\n\n

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.).

\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. List and description of scenarios for using information systems
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

The use of the System implies the following scenario:

\n\n

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

\n\n

The model includes two main scenarios:

\n\n\n\n\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

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

\n\t\t\t
\n\n


\n General model of using IS scripts:

\n\n

 

\n\n

p. 4.1.4.1 “General Scenario Model”

\n\n

 

\n\n

 

\n\n

p. 4.1.4.2 “Script Action Diagram”

\n\n

 

\n\n

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

\n\n

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.

\n\n

Process steps:

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

 

\n\n\n\n

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.

\n\n

Process steps:

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

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. System Diagnostic Requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the possibility of modernization and development of the system
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for interaction with third-party information systems
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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:

\n\n\n\n

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

\n\n

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

\n\n

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

\n\n

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.

\n\n

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

\n\n\n\n

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.

\n\n

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.

\n\n

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the number and qualifications of system personnel and their mode of work
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. \n\t\t\t
          \n\t\t\t\t
        1. Requirements for the number of personnel (users) of IS
          2. \n\t\t\t
        \n\t\t\t
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

 

\n\n

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

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Department / Management

\n\t\t\t		\n\t\t\t

Position

\n\t\t\t		\n\t\t\t

Number of users, people

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Internal departments of AUGA

\n\t\t\t		\n\t\t\t

Director, head, deputy

\n\t\t\t		\n\t\t\t

30

\n\t\t\t
\n\t\t\t

Specialist, employee

\n\t\t\t		\n\t\t\t

70

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Territorial administrations

\n\t\t\t		\n\t\t\t

Director, head, deputy

\n\t\t\t		\n\t\t\t

20

\n\t\t\t
\n\t\t\t

Specialist, employee

\n\t\t\t		\n\t\t\t

40

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Other users of Ministries and departments

\n\t\t\t		\n\t\t\t

Director, head, deputy

\n\t\t\t		\n\t\t\t

10

\n\t\t\t
\n\t\t\t

Specialist, employee

\n\t\t\t		\n\t\t\t

20

\n\t\t\t
\n\t\t\t

Observer

\n\t\t\t		\n\t\t\t

10

\n\t\t\t
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Total

\n\t\t\t		\n\t\t\t

Director, head, deputy

\n\t\t\t		\n\t\t\t

60

\n\t\t\t
\n\t\t\t

Specialist, employee

\n\t\t\t		\n\t\t\t

130

\n\t\t\t
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Observer

\n\t\t\t		\n\t\t\t

10

\n\t\t\t
\n\n

Table 4.1.7.1. Planned number of users of the System

\n\n

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.

\n\n

 

\n\n

 

\n\n

 

\n\n

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

\n\n

Observer role: viewing reports;

\n\n\n\n

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

\n\n

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

\n\n

• 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).

\n\n

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

\n\n

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.

\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. \n\t\t\t
          \n\t\t\t\t
        1. \n\t\t\t\t
            \n\t\t\t\t\t
          1. Required mode of operation of IS personnel
            2. \n\t\t\t\t
          \n\t\t\t\t
          2. \n\t\t\t
        \n\t\t\t
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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

\n\n

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:

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Indicators of appointment
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n\n\n

System performance: 

\n\n\n\n

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

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

The name of the purpose indicators

\n\t\t\t		\n\t\t\t

Explanation

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Reliability indicators

\n\t\t\t		\n\t\t\t

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

\n\t\t\t
\n\t\t\t

1.1

\n\t\t\t		\n\t\t\t

Validity

\n\t\t\t		\n\t\t\t

The system must meet the stated goals and functional requirements of the technical specifications

\n\t\t\t
\n\t\t\t

1.2

\n\t\t\t		\n\t\t\t

Security

\n\t\t\t		\n\t\t\t

The system must be able to prevent unauthorized access to data

\n\t\t\t
\n\t\t\t

1.3

\n\t\t\t		\n\t\t\t

Operability

\n\t\t\t		\n\t\t\t

The system should function in the specified modes in the absence of destabilizing influences

\n\t\t\t
\n\t\t\t

1.4

\n\t\t\t		\n\t\t\t

Consistency

\n\t\t\t		\n\t\t\t

The system and documentation must have unambiguous, consistent descriptions for the same objects, functions, terms, definitions, etc.

\n\t\t\t
\n\t\t\t

1.5

\n\t\t\t		\n\t\t\t

Sustainability

\n\t\t\t		\n\t\t\t

The system must have the ability to ensure continued operation of the System after the occurrence of deviations caused by destabilizing influences

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Performance indicators

\n\t\t\t		\n\t\t\t

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 

\n\t\t\t
\n\t\t\t

2.1

\n\t\t\t		\n\t\t\t

Performance

\n\t\t\t		\n\t\t\t

The system must be able to perform actions in the time interval that meets the specified requirements

\n\t\t\t
\n\t\t\t

2.2

\n\t\t\t		\n\t\t\t

Profitability

\n\t\t\t		\n\t\t\t

The system must be able to operate on the minimum resources of the System

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Manufacturability indicators

\n\t\t\t		\n\t\t\t

They characterize the technological aspects that make it easy to eliminate errors in the System

\n\t\t\t
\n\t\t\t

3.1

\n\t\t\t		\n\t\t\t

Modifiability

\n\t\t\t		\n\t\t\t

The system should be capable of providing ease of making the necessary changes and improvements to the System during operation.

\n\t\t\t
\n\t\t\t

3.2

\n\t\t\t		\n\t\t\t

Repeatability

\n\t\t\t		\n\t\t\t

The System should use typical design solutions or components

\n\t\t\t
\n\t\t\t

3.3

\n\t\t\t		\n\t\t\t

Structurality

\n\t\t\t		\n\t\t\t

The system should consist of complexes that perform interrelated functions

\n\t\t\t
\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Reliability requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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.

\n\n

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

\n\n

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

\n\n

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

\n\n\n\n

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

\n\n\n\n

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

\n\n\n\n

The reliability of the system being created is ensured by:

\n\n\n\n

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

\n\n\n\n

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

\n\n

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

\n\n

  

\n\n

Values ​​of reliability indicators

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Index

\n\t\t\t		\n\t\t\t

Meaning

\n\t\t\t
\n\t\t\t

The whole system

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Time to identify and neutralize current threats to information security

\n\t\t\t		\n\t\t\t

no more than 5 hours (provided that the data is saved in the System)

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Recovery time of parameters of normal functioning after the implementation of a computer attack

\n\t\t\t		\n\t\t\t

no more than 10 hours (provided that the data is saved in the System)

\n\t\t\t
\n\t\t\t

Data visualization subsystem

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Reliability

\n\t\t\t		\n\t\t\t

10,000 hours

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Availability ratio

\n\t\t\t		\n\t\t\t

0.9995

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Availability

\n\t\t\t		\n\t\t\t

99.95%

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Data loss tolerance

\n\t\t\t		\n\t\t\t

1 hour in (provided that the data is saved in the System)

\n\t\t\t
\n\t\t\t

Subsystem of distribution of roles and differentiation of access rights

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Reliability

\n\t\t\t		\n\t\t\t

6000 hours

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Availability ratio

\n\t\t\t		\n\t\t\t

0.99

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Availability

\n\t\t\t		\n\t\t\t

99.9%

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Data loss tolerance

\n\t\t\t		\n\t\t\t

12 hours

\n\t\t\t
\n\n

Tab. 4.1.8.1 Values ​​of reliability indicators

\n\n

 

\n\n

Composition of reliability indicators for the System

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Index

\n\t\t\t		\n\t\t\t

Description

\n\t\t\t
\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Availability

\n\t\t\t		\n\t\t\t

Ability Systems perform coordinated function to within a specified time ((time operation systems - while idle) / time operation Systems * 100). Measured as a percentage

\n\t\t\t
\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Availability ratio

\n\t\t\t		\n\t\t\t

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

\n\t\t\t
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Data loss tolerance

\n\t\t\t		\n\t\t\t

Allowable period of time for which System data may be lost . Measured in hours

\n\t\t\t
\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Time to recovery

\n\t\t\t		\n\t\t\t

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  

\n\t\t\t
\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Reliability

\n\t\t\t		\n\t\t\t

The property of the System to continuously maintain an operational state for some time, or

\n\n\t\t\t

developments. Measured in hours

\n\t\t\t
\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Time identifying and neutralization of actual threats to information security

\n\t\t\t		\n\t\t\t

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 .

\n\n\t\t\t

Measured in hours

\n\t\t\t
\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Restoration time of parameters of normal operation      after

\n\n\t\t\t

implementation of a computer attack

\n\t\t\t		\n\t\t\t

The duration of the restoration of the System 's operational state after the implementation of a computer attack.

\n\n\t\t\t

Measured in hours

\n\t\t\t
\n\n

Tab. 4.1.8.2 Composition of reliability indicators for the System

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Safety requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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

\n\n

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

\n\n

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. \n\t\t\t
          \n\t\t\t\t
        1. Requirements for protecting information
          \n\t\t\t\tfrom unauthorized access
          2. \n\t\t\t
        \n\t\t\t
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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.

\n\n

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

\n\n\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. \n\t\t\t
          \n\t\t\t\t
        1. Requirements for the differentiation of access rights
          2. \n\t\t\t
        \n\t\t\t
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. \n\t\t\t
          \n\t\t\t\t
        1. Requirements for the safety of information in case of accidents
          2. \n\t\t\t
        \n\t\t\t
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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.

\n\n

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:

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Characteristics of the emergency

\n\t\t\t		\n\t\t\t

Measures to ensure the safety of information in the System

\n\t\t\t		\n\t\t\t

Emergency elimination time

\n\t\t\t
\n\t\t\t

Power outage

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Application of uninterruptible power supply devices;
    • \n\t\t\t\t
  • Application of stand-alone alternators.
    • \n\t\t\t
\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Equipment support for at least 20 minutes;
    • \n\t\t\t\t
  • Automatic start within no more than 15-30 seconds
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

Failure (failure) of hard disk drives (disk array) of the server

\n\t\t\t		\n\t\t\t

Backing up data to external media

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Organization of disk arrays using the technology of RAID levels 0, 1, 5 or 10;
    • \n\t\t\t\t
  • Storage and automatic redistribution of information to spare disks for at least 20 minutes
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

Failure (failure) of the server (processor, power supply, RAM, etc.)

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Carrying out diagnostics of the state of technical means using the tools supplied as part of the technical means;
    • \n\t\t\t\t
  • Duplication of critical server elements
    • \n\t\t\t
\n\t\t\t		\n\t\t\t

Automatic transition of all functioning systems to a backup platform

\n\t\t\t
\n\t\t\t

Failure (failure) of the system software

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Diagnostics of the state of the system software using the tools supplied as part of the system software;
    • \n\t\t\t\t
  • Backing up data to external media
    • \n\t\t\t
\n\t\t\t		\n\t\t\t

Restore a saved backup within 15 minutes

\n\t\t\t
\n\n

 

\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. \n\t\t\t
          \n\t\t\t\t
        1. Requirements for protection against the influence of external influences
          2. \n\t\t\t
        \n\t\t\t
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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

\n\n

 

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Ergonomic and technical aesthetics requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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.

\n\n

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".

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the operation, maintenance, repair and storage of system components
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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
\nand organizational means of the Customer.

\n\n

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

\n\n

It must be possible to operate the Complex
\naround the clock.

\n\n

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

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

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.

\n\n

  

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for patent and license purity
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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

\n\n

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

\n\n

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

\n\n

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.

\n\n

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

\n\n

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

\n\n

The System must use licensed software.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for standardization and unification
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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.

\n\n

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

\n\n

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.

\n\n

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

\n\n

Communication should include:

\n\n\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for the degree of adaptability of the system to changes
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n\n\n

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

\n\n\n\n

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Software technical support requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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

\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Requirements for the functions (tasks) performed by the Information System
      2. \n\t
    \n\t
    2. \n
\n\n

 

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

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

\n\n\n\n

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:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Function

\n\t\t\t		\n\t\t\t

Task

\n\t\t\t
\n\t\t\t

The form

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Grouping data in different sections defined by the data hierarchy down to the lowest level of detail;
    • \n\t\t\t\t
  • Grouping data from different levels of the hierarchy;
    • \n\t\t\t\t
  • Creation and saving of fixed groupings of data available in subsequent sessions of work with the system after the completion of the current one;
    • \n\t\t\t\t
  • Creation of templates defining the sequential steps of the analysis with the support of the interactive mode;
    • \n\t\t\t\t
  • Ranking, sorting and filtering by various categories and indicators;
    • \n\t\t\t\t
  • Creation of multi-section reports with different levels of data grouping;
    • \n\t\t\t\t
  • Creation of a set of standard report templates that make it easier for the user to build standard reports;
    • \n\t\t\t\t
  • Setting the parameters of reports in the interactive mode;
    • \n\t\t\t
\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Analysis

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Flexible data manipulation;
    • \n\t\t\t\t
  • Data scaling (drill-down);
    • \n\t\t\t\t
  • Possibilities of data aggregation by arbitrary indicators;
    • \n\t\t\t\t
  • Support for the ability to display monetary amounts in more than one currency with the ability to quickly recalculate;
    • \n\t\t\t\t
  • Ranking values ​​of measurement categories by values ​​of indicators;
    • \n\t\t\t\t
  • Analysis of trends over time;
    • \n\t\t\t
\n\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Performance

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • Pie charts;
    • \n\t\t\t\t
  • Column charts are two-dimensional;
    • \n\t\t\t\t
  • Column charts are three-dimensional;
    • \n\t\t\t\t
  • Line charts;
    • \n\t\t\t\t
  • Scatter plots;
    • \n\t\t\t\t
  • Simultaneous output of data in tabular and graphical form;
    • \n\t\t\t\t
  • Formation of balanced and unbalanced nested pivot tables;
    • \n\t\t\t\t
  • Calculations over the values ​​of indicators for arbitrary groups of measurement categories;
    • \n\t\t\t\t
  • Conditional formatting of indicators depending on their values;
    • \n\t\t\t\t
  • Displaying indicators in the form of absolute values ​​and shares of total values;
    • \n\t\t\t\t
  • Export of slices of multidimensional cubes in various formats.
    • \n\t\t\t
\n\t\t\t
\n\n

 

\n\n

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

\n\n\n\n

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.

\n\n

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.

\n\n

 

\n\n

List of reporting forms:

\n\n

Table 4.2.1 - Forms of reporting in accordance with NAS

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Form No. 1 - balance sheet

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Long-term assets

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Current assets

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Sources of own funds

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Commitments

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Certificate of availability of valuables recorded on off-balance sheet accounts

\n\t\t\t
\n\t\t\t

6

\n\t\t\t		\n\t\t\t

Deciphering overdue receivables and payables - overdue receivables

\n\t\t\t
\n\t\t\t

7

\n\t\t\t		\n\t\t\t

Overdue payables

\n\t\t\t
\n\t\t\t

Form No. 2 - Statement of financial results

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Form -2

\n\t\t\t
\n\t\t\t

Form No. 4 - statement of cash flows

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Operating activities

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Investment activities

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Financial activities

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Taxation

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Statement of cash flow in foreign currency

\n\t\t\t
\n\t\t\t

Form No. 5 - statement of equity capital

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Form No. 5

\n\t\t\t
\n\n

Table 4.2.2 - Forms of reporting on key performance indicators.

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Key Performance Indicators - Industrial

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

List of key KPIs

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

List of additional key performance indicators

\n\t\t\t
\n\t\t\t

Key performance indicators - banking sector

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Indicators of assets and liabilities

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Compliance with normative indicators in the bank

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Financial performance

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Trust Fund Tax and Payments

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Distribution of net profit

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

External credit lines / Eurobonds

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Sponsorship

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Amount of workers

\n\t\t\t
\n\t\t\t

Key performance indicators - insurance companies

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Indicators of assets and liabilities

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Compliance with normative indicators

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Financial performance

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Trust Fund Tax and Payments

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Distribution of net profit

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

External debt

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Sponsorship

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Amount of workers

\n\t\t\t
\n\n

 

\n\n

Table 4.2.3- Reporting forms - business plan

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Business plan

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Production facilities (works and services)

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Production volume (Works and services)

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Financial performance

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Taxes and payments to trust funds

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Distribution of net profit

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Debentures

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

External debt

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Foreign trade and foreign economic activity of the enterprise.

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Important performance indicators

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Production of products included in the localization program

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Investment projects.

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Sponsorship

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

The number of employees

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Management and control bodies of state-owned enterprises

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Changes in the composition of the supervisory board, the executive body of the audit commission.

\n\t\t\t
\n\n

 

\n\n

 

\n\n

Table 4.2.4 - Management reporting forms

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Management reporting

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Information on the production indicators of enterprises

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Production indicators

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Financial performance

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

About business plans of state-owned enterprises

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

On the state of the analysis of the activities of enterprises with state participation

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Payment of dividends by state-owned enterprises

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

According to the results of 9 months of the reporting year, state enterprises operating in the territory of the republic.

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Financial recovery of state-owned enterprises

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Information about the labor resources of enterprises

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Production of products included in the localization program

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Investment projects.

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Sponsorship

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

The number of employees

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Management and control bodies of state-owned enterprises

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.                     
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Changes in the composition of the supervisory board, the executive body of the audit commission.

\n\t\t\t
\n\n

 

\n\n

Table 4.2.5 - Preliminary reporting forms in accordance with IFRS

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Preliminary IFRS reporting forms - enterprises

\n\t\t\t
\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Statement of financial position

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Statement of comprehensive income

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Statement of changes in equity

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Cash flow statement (direct method)

\n\t\t\t
\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 

\n\n\t\t\t

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

\n\t\t\t
\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Statement of financial position

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Statement of comprehensive income

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Profit or loss statement

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Statement of changes in equity

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Cash flow statement

\n\t\t\t
\n\n

 

\n\n

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.).

\n\n

 

\n\n

 

\n\n

 

\n\n

 

\n\n

p. 4.2.1 – Example of visualization of predictive analysis

\n\n

 

\n\n

 

\n\n

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

\n\n

 

\n\n

 

\n\n

 

\n\n

p. 4.2.1 – An example of KPI visualization

\n\n

Time schedule for the implementation of each function, tasks:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Interim regulation requirements

\n\t\t\t		\n\t\t\t

Task

\n\t\t\t
\n\t\t\t

The entire period of operation of the system upon user initiation

\n\t\t\t		\n\t\t\t

Grouping data in different sections defined by the data hierarchy down to the lowest level of detail;

\n\t\t\t
\n\t\t\t

Grouping data from different levels of the hierarchy;

\n\t\t\t
\n\t\t\t

Creation and saving of fixed groupings of data available in subsequent sessions of work with the system after the completion of the current one;

\n\t\t\t
\n\t\t\t

Creation of templates defining the sequential steps of the analysis with the support of the interactive mode;

\n\t\t\t
\n\t\t\t

Ranking, sorting and filtering by various categories and indicators;

\n\t\t\t
\n\t\t\t

Creation of multi-section reports with different levels of data grouping;

\n\t\t\t
\n\t\t\t

Ranking values ​​of measurement categories by values ​​of indicators;

\n\t\t\t
\n\t\t\t

Analysis of trends over time;

\n\t\t\t
\n\t\t\t

Pie charts;

\n\t\t\t
\n\t\t\t

Column charts are two-dimensional;

\n\t\t\t
\n\t\t\t

Column charts are three-dimensional;

\n\t\t\t
\n\t\t\t

Line charts;

\n\t\t\t
\n\t\t\t

Scatter plots;

\n\t\t\t
\n\t\t\t

Simultaneous output of data in tabular and graphical form;

\n\t\t\t
\n\t\t\t

Formation of balanced and unbalanced nested pivot tables;

\n\t\t\t
\n\t\t\t

Calculations over the values ​​of indicators for arbitrary groups of measurement categories;

\n\t\t\t
\n\t\t\t

Conditional formatting of indicators depending on their values;

\n\t\t\t
\n\t\t\t

Displaying indicators in the form of absolute values ​​and shares of total values;

\n\t\t\t
\n\t\t\t

Export of slices of multidimensional cubes in various formats.

\n\t\t\t
\n\t\t\t

The entire period of operation of the system

\n\t\t\t		\n\t\t\t

Creation of a set of standard report templates that make it easier for the user to build standard reports;

\n\t\t\t
\n\t\t\t

Setting the parameters of reports in the interactive mode;

\n\t\t\t
\n\t\t\t

Flexible data manipulation;

\n\t\t\t
\n\t\t\t

Data scaling (drill-down);

\n\t\t\t
\n\t\t\t

Possibilities of data aggregation by arbitrary indicators;

\n\t\t\t
\n\n

Requirements for the quality of implementation of functions, tasks.

\n\n

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

\n\n

 

\n\n

List of failure criteria for each function:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Function

\n\t\t\t		\n\t\t\t

Refusal criteria

\n\t\t\t		\n\t\t\t

Recovery time

\n\t\t\t		\n\t\t\t

Availability ratio

\n\t\t\t
\n\t\t\t

The form

\n\t\t\t		\n\t\t\t

One of the tasks of the function is not being performed.

\n\t\t\t		\n\t\t\t

8 ocloc'k

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

0.85

\n\t\t\t
\n\t\t\t

Analysis

\n\t\t\t		\n\t\t\t

One of the tasks of the function is not being performed.

\n\t\t\t		\n\t\t\t

12 hours

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

0.75

\n\t\t\t
\n\t\t\t

Performance

\n\t\t\t		\n\t\t\t

One of the tasks of the function is not being performed.

\n\t\t\t		\n\t\t\t

12 hours

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

0.75

\n\t\t\t
\n\n

 

\n\n

 

\n\n

 

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

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

\n\n

The subsystem should perform the following functions:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Function

\n\t\t\t		\n\t\t\t

Task

\n\t\t\t
\n\t\t\t

User management and monitoring

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • User management;
    • \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • Provision of routine maintenance provided for by the operational documentation for the software product;
    • \n\t\t\t\t
  • Resolution of problems arising during the operation of the software product;
    • \n\t\t\t\t
  • Elimination of emergency situations (incidents) arising during the operation of the software product;
    • \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • Monitoring the work of users of the software product and means for interacting with them;
    • \n\t\t\t\t
  • Monitoring of the parameters of the functioning of the software product;
    • \n\t\t\t\t
  • Procedures for managing the operation of a software product;
    • \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • The possibility of deleting information about users registered in the software product, including blocked ones, must be excluded;
    • \n\t\t\t\t
  • The possibility of changing (modifying) demo data (last name, first name, patronymic) of the established users must be excluded;
    • \n\t\t\t\t
  • The implementation of the administration mechanism should not reveal the logic of building the database of the software product;
    • \n\t\t\t\t
  • Users who do not have business roles (Administrator, Operator, etc.) should not be able to change the business data of the software product.
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

Access rights management

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • 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;
    • \n\t\t\t\t
  • The mechanism for differentiating access rights should ensure that the employee can launch only the functions allowed to him.
    • \n\t\t\t
\n\n\t\t\t

 

\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Identification and authentication mechanisms

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  • 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);
    • \n\t\t\t\t
  • 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.  
    • \n\t\t\t
\n\t\t\t
\n\n

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

\n\n

Requirements for the quality of implementation of functions, tasks.

\n\n

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

\n\n

List of failure criteria for each function:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Function

\n\t\t\t		\n\t\t\t

Refusal criteria

\n\t\t\t		\n\t\t\t

Recovery time

\n\t\t\t		\n\t\t\t

Availability ratio

\n\t\t\t
\n\t\t\t

User management and monitoring

\n\t\t\t		\n\t\t\t

One of the tasks of the function is not being performed.

\n\t\t\t		\n\t\t\t

12 hours

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

0.75

\n\t\t\t
\n\t\t\t

Access rights management

\n\t\t\t		\n\t\t\t

One of the tasks of the function is not being performed.

\n\t\t\t		\n\t\t\t

12 hours

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

0.75

\n\t\t\t
\n\t\t\t

Identification and authentication mechanisms

\n\t\t\t		\n\t\t\t

One of the tasks of the function is not being performed.

\n\t\t\t		\n\t\t\t

8 ocloc'k

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

0.85

\n\t\t\t
\n\n

 

\n\n

 

\n\n\n\n

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

\n\n\n\n

 

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Requirements to types of support\n\n\t\t
        \n\t\t\t
      1. Requirements for software
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

The software of the System should include:

\n\n

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

\n\n\n\n

Software algorithms must meet the following requirements:

\n\n\n\n

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. 

\n\n

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.

\n\n

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

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Information support requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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.

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for information exchange between system components
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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.

\n\n

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

\n\n

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:

\n\n\n\n

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.

\n\n

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Linguistic requirements
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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:

\n\n\n\n

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.

\n\n

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

\n\n

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

\n\n

 

\n\n

 

\n\n\n\n

The System software must have the following characteristics:

\n\n\n\n

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.

\n\n

All software must be guaranteed for at least 1 year.

\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for metrological support
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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”.

\n\n

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

\n\n

There are no additional requirements for metrological support.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for technical support
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

There are no requirements for the existing technical support.

\n\n

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.

\n\n

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. 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. \n\t\t
        \n\t\t\t
      1. Requirements for methodological support
        2. \n\t\t
      \n\t\t
      2. \n\t
    \n\t
    2. \n
\n\n

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.

\n\n

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

\n\n

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

\n\n

The methodological support includes:

\n\n\n\n

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

\n\n

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

\n\n\n\n

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).

\n\n

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.

\n\n
    \n\t
  1. SCOPE AND CONTENT OF THE SYSTEM IMPLEMENTATION WORKS
    2. \n
\n\n

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.

\n\n

Preliminary stages of work (table 5.1):

\n\n

 

\n\n

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

\n\n

 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Stage number

\n\t\t\t		\n\t\t\t

Name of works and their content

\n\t\t\t		\n\t\t\t

Deadline

\n\t\t\t		\n\t\t\t

Contractor (organization)

\n\t\t\t		\n\t\t\t

How the stage ends

\n\t\t\t
\n\t\t\t

Start

\n\t\t\t		\n\t\t\t

The ending

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Formation of requirements for the System:

\n\n\t\t\t
    \n\t\t\t\t
  1. Initial survey of the facility and justification of the need for the System;
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

September 2021

\n\t\t\t		\n\t\t\t

October

\n\n\t\t\t

2021

\n\t\t\t		\n\t\t\t

Executor

\n\t\t\t		\n\t\t\t

Site survey report;

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

System concept development:

\n\n\t\t\t
    \n\t\t\t\t
  1. Development of the project charter;
    2. \n\t\t\t\t
  2. Pre-design survey;
    3. \n\t\t\t\t
  3. Formation of business requirements for the system.
    4. \n\t\t\t\t
  4. Formation of a report on the results of work.
    5. \n\t\t\t
\n\t\t\t		\n\t\t\t

October 2021

\n\t\t\t		\n\t\t\t

November

\n\n\t\t\t

2021

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t
    \n\t\t\t\t
  1. Project charter;
    2. \n\t\t\t\t
  2. Project schedule;
    3. \n\t\t\t\t
  3. Report on the results of the work.
    4. \n\t\t\t
\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Technical task:

\n\n\t\t\t

Drawing up the Terms of Reference for the creation of the system and its form

\n\t\t\t		\n\t\t\t

November

\n\n\t\t\t

2021

\n\t\t\t		\n\t\t\t

February

\n\n\t\t\t

2022

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Terms of reference for data marts in terms of the received reporting on:

\n\n\t\t\t
    \n\t\t\t\t
  1. NSBU;
    2. \n\t\t\t\t
  2. KPI;
    3. \n\t\t\t\t
  3. Implementation of the business plan, production indicators, personnel report;
    4. \n\t\t\t\t
  4. Management reporting;
    5. \n\t\t\t\t
  5. IFRS
    6. \n\t\t\t
\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Design:

\n\n\t\t\t

1. Development of design solutions for the system and its parts. Testing;

\n\n\t\t\t

2. Development of documentation for the System and its parts;

\n\t\t\t		\n\t\t\t

February

\n\n\t\t\t

2022

\n\t\t\t		\n\t\t\t

May

\n\n\t\t\t

2022

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Development specifications, data mappings in terms of the received reporting on:

\n\n\t\t\t
    \n\t\t\t\t
  1. NSBU;
    2. \n\t\t\t\t
  2. KPI;
    3. \n\t\t\t\t
  3. Implementation of the business plan, production indicators, personnel report;
    4. \n\t\t\t\t
  4. Management reporting;
    5. \n\t\t\t\t
  5. IFRS
    6. \n\t\t\t
\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Working documentation:

\n\n\t\t\t
    \n\t\t\t\t
  1. Development of working documentation for the system and its parts.
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

May

\n\n\t\t\t

2022

\n\t\t\t		\n\t\t\t

June

\n\n\t\t\t

2022

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Working documentation for the development of reporting

\n\t\t\t
\n\t\t\t

6

\n\t\t\t		\n\t\t\t

Commissioning:

\n\n\t\t\t
    \n\t\t\t\t
  1. Preparation of the automation object for putting the System into operation;
    2. \n\t\t\t\t
  2. Personnel training;
    3. \n\t\t\t\t
  3. Commissioning works:
    4. \n\t\t\t\t
  4. Setting up integration with systems in accordance with the TOR;
    5. \n\t\t\t\t
  5. Preliminary tests;
    6. \n\t\t\t\t
  6. Coordination of improvements and settings, correction of defects;
    7. \n\t\t\t\t
  7. Acceptance tests.  
    8. \n\t\t\t\t
  8. Pilot industrial operation
    9. \n\t\t\t\t
  9. Industrial exploitation
    10. \n\t\t\t
\n\t\t\t		\n\t\t\t

June

\n\n\t\t\t

2022

\n\t\t\t		\n\t\t\t

February 2023

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Reporting on:

\n\n\t\t\t
    \n\t\t\t\t
  1. NAS
    2. \n\t\t\t\t
  2. KPI
    3. \n\t\t\t\t
  3. Implementation of the business plan, performance indicators, personnel;
    4. \n\t\t\t\t
  4. Management reporting
    5. \n\t\t\t\t
  5. IFRS
    6. \n\t\t\t
\n\n\t\t\t

Guides :

\n\n\t\t\t
    \n\t\t\t\t
  1. Business Analysis System User Guide
    2. \n\t\t\t\t
  2. Business Analysis System Administrator Guide
    3. \n\t\t\t\t
  3. Acceptance test procedure
    4. \n\t\t\t\t
  4. Acceptance test report
    5. \n\t\t\t
\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

7

\n\t\t\t		\n\t\t\t

System Maintenance:

\n\n\t\t\t
    \n\t\t\t\t
  1. Performance of work in accordance with warranty obligations;
    2. \n\t\t\t\t
  2. Post-warranty service.
    3. \n\t\t\t
\n\t\t\t		\n\t\t\t

February 2023

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\n

Tab. 5.1 Preliminary stages of work.

\n\n

 

\n\n

 

\n\n

Preliminary work schedule (table 5.2):

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Год

\n\t\t\t		\n\t\t\t

2021

\n\t\t\t		\n\t\t\t

2022

\n\t\t\t
\n\t\t\t

№

\n\t\t\t		\n\t\t\t

Этап

\n\t\t\t		\n\t\t\t

09.21

\n\t\t\t		\n\t\t\t

10.21

\n\t\t\t		\n\t\t\t

11.21

\n\t\t\t		\n\t\t\t

12.21

\n\t\t\t		\n\t\t\t

01.22

\n\t\t\t		\n\t\t\t

02.22

\n\t\t\t		\n\t\t\t

03.22

\n\t\t\t		\n\t\t\t

04.22

\n\t\t\t		\n\t\t\t

05.22

\n\t\t\t		\n\t\t\t

06.22

\n\t\t\t		\n\t\t\t

07.22

\n\t\t\t		\n\t\t\t

08.22

\n\t\t\t		\n\t\t\t

09.22

\n\t\t\t		\n\t\t\t

10.22

\n\t\t\t		\n\t\t\t

11.22

\n\t\t\t		\n\t\t\t

12.22

\n\t\t\t		\n\t\t\t

01.23

\n\t\t\t		\n\t\t\t

02.23

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Formation of requirements for the System

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

System concept development

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Technical task

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Design

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Working documentation

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

6

\n\t\t\t		\n\t\t\t

Commissioning

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

7

\n\t\t\t		\n\t\t\t

System Maintenance

\n\t\t\t		\n\t\t\t

Within 12 months

\n\t\t\t
                     
\n\n

Tab. 5.2 Preliminary work schedule.

\n\n

 

\n\n

 

\n\n
    \n\t
  1. SYSTEM CONTROL AND ACCEPTANCE PROCEDURE
    2. \n
\n\n

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.

\n\n

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

\n\n

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

\n\n\n\n

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
\nand timing of tests to ensure the specified reliability of the results obtained. The test program and methodology can be developed
\nfor the System as a whole and (or) its parts. Tests (test cases) can be included as an attachment.

\n\n

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

\n\n\n\n

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.

\n\n

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

\n\n

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.

\n\n

Tests of the System are performed after debugging
\nand testing of the supplied software and hardware of the System
\nand 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.

\n\n

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.

\n\n

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Types, scope and test methods
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n

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.

\n\n

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

\n\n

Preliminary tests

\n\n

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.

\n\n

Preliminary tests are carried out at a specially equipped stand.

\n\n

On a larger scale, preliminary tests include 3 stages.

\n\n

Pilot industrial operation

\n\n

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.

\n\n

Operations management works include:

\n\n\n\n

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.

\n\n

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.

\n\n

Industrial exploitation

\n\n

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.

\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. General requirements for acceptance of works by stages
      2. \n\t
    \n\t
    2. \n
\n\n

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:

\n\n\n\n

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

\n\n

RASCI matrix (distribution of responsibilities between project participants)

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

R

\n\t\t\t		\n\t\t\t

Responsible
\n\t\t\t(Ответственный)

\n\t\t\t		\n\t\t\t

The Project Participant performing the Work to achieve the Project Result. Responsible for the achievement of the Result

\n\t\t\t
\n\t\t\t

A

\n\t\t\t		\n\t\t\t

Approver
\n\t\t\t(Утверждающий)

\n\t\t\t		\n\t\t\t

A project participant who approves the correctness and completeness of the work. Accepts the Results of the Works.

\n\t\t\t
\n\t\t\t

S

\n\t\t\t		\n\t\t\t

Support
\n\t\t\t(Соисполнитель)

\n\t\t\t		\n\t\t\t

A project participant who provides support within his competence for the Responsible.

\n\t\t\t
\n\t\t\t

C

\n\t\t\t		\n\t\t\t

Consulted
\n\t\t\t(Консультирующий)

\n\t\t\t		\n\t\t\t

A project participant whose opinion (resources) is taken into account to create the Project Results. Subject matter experts.

\n\t\t\t
\n\t\t\t

I

\n\t\t\t		\n\t\t\t

Informed
\n\t\t\t(Информируемый)

\n\t\t\t		\n\t\t\t

A project participant who is informed about the progress of the Work on the creation of the Project Results.

\n\t\t\t
\n\n

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

\n\n

 

\n\n

Responsibility matrix for project results

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

No.

\n\t\t\t		\n\t\t\t

Stage

\n\t\t\t		\n\t\t\t

Responsible

\n\t\t\t		\n\t\t\t

results

\n\t\t\t
\n\t\t\t

Executor

\n\t\t\t		\n\t\t\t

Customer

\n\t\t\t		\n\t\t\t

 

\n\t\t\t
\n\t\t\t

1.

\n\t\t\t		\n\t\t\t

Formation of requirements for the System

\n\t\t\t		\n\t\t\t

R

\n\t\t\t		\n\t\t\t

A, C, S

\n\t\t\t		\n\t\t\t

1. Terms of reference for a business analysis system;

\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

2.

\n\t\t\t		\n\t\t\t

System concept development

\n\t\t\t		\n\t\t\t

R

\n\t\t\t		\n\t\t\t

A, C, S

\n\t\t\t		\n\t\t\t

1. Project charter;

\n\n\t\t\t

2. Schedule of the project;

\n\n\t\t\t

3. Report on the results of the work.

\n\t\t\t
\n\t\t\t

3.

\n\t\t\t		\n\t\t\t

Technical task

\n\t\t\t		\n\t\t\t

R, A, C

\n\t\t\t		\n\t\t\t

A, C, S

\n\t\t\t		\n\t\t\t

Terms of reference for data marts in terms of the received reporting on:

\n\n\t\t\t

1. NSBU;

\n\n\t\t\t

2. KPI;

\n\n\t\t\t

3. Fulfillment of the business plan, production indicators, personnel report;

\n\n\t\t\t

4. Management reporting;

\n\n\t\t\t

5. IFRS

\n\t\t\t
\n\t\t\t

4.

\n\t\t\t		\n\t\t\t

Design

\n\t\t\t		\n\t\t\t

R, A, C

\n\t\t\t		\n\t\t\t

A, C, S

\n\t\t\t		\n\t\t\t

Development specifications, data mappings in terms of the received reporting on:

\n\n\t\t\t

1. NSBU;

\n\n\t\t\t

2. KPI;

\n\n\t\t\t

3. Fulfillment of the business plan, production indicators, personnel report;

\n\n\t\t\t

4. Management reporting;

\n\n\t\t\t

5. IFRS

\n\t\t\t
\n\t\t\t

5.

\n\t\t\t		\n\t\t\t

Working documentation

\n\t\t\t		\n\t\t\t

R

\n\t\t\t		\n\t\t\t

A, C, S

\n\t\t\t		\n\t\t\t

1. Working documentation for the development of reporting

\n\t\t\t
\n\t\t\t

6.

\n\t\t\t		\n\t\t\t

Commissioning

\n\t\t\t		\n\t\t\t

R

\n\t\t\t		\n\t\t\t

R, A, C

\n\t\t\t		\n\t\t\t

Reporting on:

\n\n\t\t\t

1. NAS

\n\n\t\t\t

2. KPI

\n\n\t\t\t

3. Implementation of the business plan, performance indicators, personnel;

\n\n\t\t\t

4. Management reporting

\n\n\t\t\t

5. IFRS

\n\n\t\t\t

Guides:

\n\n\t\t\t

1. Business Analysis System User Guide

\n\n\t\t\t

2. Business Analysis System Administrator's Guide

\n\n\t\t\t

3. Acceptance test procedure

\n\n\t\t\t

4. Acceptance test report

\n\t\t\t
\n\n

Tab. 6.2.2 Responsibility matrix for project results

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Requirements for managing organizational change
      2. \n\t
    \n\t
    2. \n
\n\n

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:

\n\n

Communication

\n\n

Key tasks:

\n\n

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

\n\n\n\n

Organizational Design

\n\n

Key tasks:

\n\n\n\n

Education

\n\n

Key tasks:

\n\n

Training of the system implementation project team:

\n\n\n\n

Preliminary estimate of the number of employees for training:

\n\n

• Professional training - business users: 50 people

\n\n

• Professional training - technical specialists: 20 people.

\n\n

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

\n\n

• 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).

\n\n

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

\n\n

 

\n\n

Methodological support for Organizational Change Management

\n\n

Key tasks:

\n\n\n\n

Assess the impact of change and readiness for change

\n\n\n\n

 

\n\n

 

\n\n
    \n\t
  1. REQUIREMENTS FOR THE COMPOSITION AND CONTENT OF WORKS ON PREPARING THE SYSTEM FOR COMMISSIONING
    2. \n
\n\n

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.

\n\n

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.

\n\n

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

\n\n\n\n

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

\n\n\n\n

 

\n\n

 

\n\n
    \n\t
  1. DOCUMENTATION REQUIREMENTS\n\n\t
      \n\t\t
    1. Project documentation
      2. \n\t
    \n\t
    2. \n
\n\n\n\n

 

\n\n
    \n\t
  1. SOURCES OF DEVELOPMENT
    2. \n
\n\n

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

\n\n\n\n

 

\n\n
    \n\t
  1. PROJECT ASSUMPTIONS AND RESTRICTIONS\n\n\t
      \n\t\t
    1. Organizational Assumptions and Constraints
      2. \n\t
    \n\t
    2. \n
\n\n\n\n

 

\n\n\n\n

 

\n\n\n\n

 

\n\n\n\n

 

\n\n\n\n

 

\n\n
    \n\t
  1. \n\t
      \n\t\t
    1. Terms of the Project execution
      2. \n\t
    \n\t
    2. \n
\n\n

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

\n\n\n\n

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.

\n\n

 

"},{"id":"OP00154301","notice_type":"Request for Expression of Interest","noticedate":"16-Nov-2021","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2022-09-22T00:00:00Z","submission_deadline_time":"14:00","project_ctry_name":"Bangladesh","project_id":"P160819","project_name":"Cash Transfer Modernization Project","bid_reference_no":"SD 07","bid_description":"Selection of Consultant Firm for Upgradation of MIS","procurement_group":"CS","procurement_method_code":"QCBS","procurement_method_name":"Quality And Cost-Based Selection","contact_address":"E-8/B-1, Somaj Sheba Bhaban (9th Floor), Agargaon, Sher-e Bangla Nagar, Dhaka, Bangladesh.","contact_ctry_name":"Bangladesh","contact_email":"pd.ctm@dss.gov.bd","contact_name":"Khurshid Alam Chowdhury","contact_organization":"Department of Social Services","contact_phone_no":"01552379422","contact_web_url":"www.dss.gov.bd","submission_date":"2021-11-16T00:00:00Z","notice_text":"

REQUEST FOR EXPRESSIONS OF INTEREST (REOI)

\n\n

(CONSULTING SERVICES – FIRMS SELECTION)

\n\n

 

\n\n

Selection of IT Firm for ‘Design, Development and Implementation support services of an Integrated Social Protection Management Information System’

\n\n

Country: Bangladesh

\n\n

Name of Project: Cash Transfer Modernization Project

\n\n

Credit No: IDA-61630

\n\n

Assignment Title: Selection of IT Firm for ‘Design, Development and Implementation support services of an Integrated Social Protection Management Information System’.

\n\n

Reference No.: SD-07

\n\n

The Government of the People’s Republic of Bangladesh has received financing from the World Bank toward the cost of the “Cash Transfer Modernization (CTM) Project” under the Department of Social Services (DSS), Ministry of Social Welfare (MoSW), and intends to apply part of the proceeds for consulting services of ‘Design, Development and Implementation support services of an Integrated Social Protection Management Information System’.

\n\n
    \n\t
  1. The main objective of this assignment is to hire a qualified MIS/IT firm (Consultant hereafter) for the design, development, commissioning and implementation of the MIS to make it a scalable and integrated MIS Platform that facilitates end-to-end automation of the core DSS business functions through unified IT Platform. In this regard, objectives are to achieve the following milestones as a part of this project execution.
    2. \n\t
  2. The consulting services (“the Services”) include but not limited to:  
    3. \n
\n\n\n\n

The assignment will be estimated 180 professional staff-months and also non-key expert as required mentioned in the TOR, implementation period will approximately 24 months, expected start date of assignment may be 15 May, 2022 to ensuring full consistency with the TOR.

\n\n

3. Department of Social Services under Ministry of Social Welfare represented by  the Project Director, The Cash Transfer Modernization (CTM) Project, 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.

\n\n

The shortlisting criteria are:

\n\n\n\n

Consultants are requested to submit the following supporting documents in support of the above-mentioned criteria:

\n\n\n\n

4. The attention of interested Consultant firm is drawn to Section III, paragraphs, 3.14, 3.16, and 3.17 of the World Bank’s “Procurement Regulations for IPF Borrowers” July 2016 (“Procurement Regulations”), setting forth the World Bank’s policy on conflict of interest.

\n\n

5. Consultants may associate with other firms to enhance their qualifications, but should indicate clearly whether the association is in the form of a joint venture and/or a sub-consultancy. In the case of a joint venture, all the partners in the joint venture shall be jointly and severally liable for the entire contract, if selected. In the case of an association, all members of such “association” should have real and well-defined inputs to the assignment and in such "association" it is preferable to limit the total number of firms including the associates to a maximum of 03 (Three).

\n\n

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

\n\n

7. Further information can be obtained at the address below during office hours, i.e. 0900 to 1700 hours. The detailed Terms of Reference (TOR) for the assignment can be downloaded from www.dss.gov.bd website or can be obtained upon request from the address below either by e-mail or in person during the office hours (Local Time: 09:00 to 17:00 hours).

\n\n

8. Expressions of interest must be delivered in a written form to the address below (in person, or by mail, or by e-mail) by14 December, 2021 on or before 1400 hours (UTC+ 6 hours).

\n\n

9. The Procuring Entity (PE) reserves the right to accept or reject any or all EOIs without assigning any reason whatsoever.

\n\n

 

\n\n

(Khurshid Alam Chowdhury)

\n\n

Project Director (Additional Secretary)

\n\n

Cash Transfer Modernization (CTM) Project

\n\n

E-8/B-1, Somaj Sheba Bhaban (9th Floor),

\n\n

Agargaon, Sher-e Bangla Nagar, Dhaka-1207, Bangladesh.

\n\n

Email: pd.ctm@dss.gov.bd

\n\n

Phone: +880 2 55006575

"},{"id":"OP00121855","notice_type":"Request for Expression of Interest","noticedate":"22-Mar-2021","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2021-04-07T00:00:00Z","submission_deadline_time":"12:00","project_ctry_name":"West Bank and Gaza","project_id":"P168739","project_name":"Water Security Development - Gaza Central Desalination Program – Associated Works Phase I Project","bid_reference_no":"PWA/GCDP/CS11/CQS","bid_description":"Water Sector Application","procurement_group":"CS","procurement_method_code":"CQS","procurement_method_name":"Consultant Qualification Selection","contact_address":"Ramallah","contact_ctry_name":"West Bank and Gaza","contact_email":"risseed@pwa.ps","contact_name":"Rawan Isseed","contact_organization":"Palestinian Water Authority","contact_phone_no":"+ 970 598914044","contact_web_url":"www.pwa.ps","submission_date":"2021-03-22T00:00:00Z","notice_text":"

STATE OF PALESTINE

\n\n

PALESTINIAN WATER AUTHORITY

\n\n

 

\n\n

REQUEST FOR EXPRESSIONS OF INTEREST

\n\n

(CONSULTING SERVICES – FIRMS SELECTION)

\n\n

 

\n\n

 

\n\n

Country:                    State of Palestine

\n\n

Name of Project:       Water Security Development- Gaza Central Desalination Program:

\n\n

                                         Associated Works Project Phase I (AWP-Phase 1)

\n\n

Project ID No.:          P168739

\n\n

Assignment Title:      Water Sector Application

\n\n

Reference No.:           PWA/GCDP/CS11/CQS

\n\n

 

\n\n

The Palestinian Liberation Organization (PLO) for the benefit of the Palestinian Authority has received financing from the World Bank toward the cost of the Water Security Development - Gaza Central Desalination Program: Associated Works Project Phase I (AWP-Phase 1), and intends to apply part of the proceeds for consulting services.

\n\n

 

\n\n

The consulting services (“the Services”) include:

\n\n\n\n

 

\n\n

The estimate level of effort for the key staff is 66 days per entire assignment. The assignment is expected to commence in May 2021, and the implementation period is around three months.

\n\n

 

\n\n

The detailed Terms of Reference (TOR) for the assignment can be found at the following website: www.pwa.ps , http://www.pwa.ps/page.aspx?id=d3fEhna1248699936ad3fEhn.

\n\n

 

\n\n

The Palestinian Water Authority (PWA) 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. The selection criteria are:

\n\n
    \n\t
  1. General experience: Have been in business for at least the past 3 years in development of IT using a complex database schema (20%);
    2. \n\t
  2.  Specific experience: Evidence of firm capability and relevant experience in the execution of Consultancy Assignment of a similar nature, including the nature and value of the relevant contracts, as well as works in hand and contractually committed. The evidence shall include successful experience in the execution of at least one (1) Consultancy Services of a similar nature and size and complexity during the last three (3) years (80%);
    3. \n
\n\n

 

\n\n

The attention of interested Consultants is drawn to Section III, paragraphs,3.14, 3.16, and 3.17 of the World Bank’s “Procurement Regulations for IPF Borrowers” July 2016 Revised November 2017 and August 2018 (“Procurement Regulations”), setting forth the World Bank’s policy on conflict of interest. 

\n\n

 

\n\n

Consultants may associate with other firms to enhance their qualifications, but should indicate clearly whether the association is in the form of a joint venture and/or a sub-consultancy. In the case of a joint venture, all the partners in the joint venture shall be jointly and severally liable for the entire contract, if selected.

\n\n

 

\n\n

A Consultant will be selected in accordance with the Consultant's Qualification-based Selection (CQS) method set out in the Procurement Regulations.

\n\n

 

\n\n

Further information can be obtained at the address (1) below during office hours from 8:00 am to 15:00 pm. 

\n\n

 

\n\n

Expressions of interest must be delivered in a written form to the address (2) below in person, or by e-mail on or before Wednesday 07/04/2021 no later than 12:00 noon local time.

\n\n

 

\n\n

The addresses are:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Address 1:  For Information

\n\n\t\t\t

Palestinian Water Authority

\n\n\t\t\t

Kamal Nasir Street, Al Masayef, Ramallah, West Bank, State of Palestine

\n\n\t\t\t

Attn: Eng. Rawan Isseed

\n\n\t\t\t

Institutional Specialist

\n\n\t\t\t

Project Management &Support Unit (PMSU)

\n\n\t\t\t

Tel:  +972 2 2987665

\n\n\t\t\t

Fax: +972 2 2987336

\n\n\t\t\t

Mobile: + 970 598914044

\n\n\t\t\t

Email: risseed@pwa.ps, rawan_isseed@hotmail.com

\n\t\t\t		\n\t\t\t

Address 2: For  Submission

\n\n\t\t\t

The Palestinian Water Authority

\n\n\t\t\t

Procurement Unit

\n\n\t\t\t

Kamal Nasir Street,

\n\n\t\t\t

Al Masayef, West Bank, Palestine

\n\n\t\t\t

Attn: Raed Sawaftah

\n\n\t\t\t

Head of Procurement Unit

\n\n\t\t\t

Tel:  + 970 2987665

\n\n\t\t\t

Fax: + 970 2 2987336

\n\n\t\t\t

Mobile: + 970 599814065

\n\n\t\t\t

E-mail: rsawaftah@pwa.ps, raed_sf@yahoo.com

\n\t\t\t
\n\n

 

\n\n

Palestinian Water Authority

\n\n

 

\n\n

Terms of Reference

\n\n

Water Security Development Program (WSDP)

\n\n

Gaza Central Desalination Program: Associated Works Phase I Project

\n\n

Consultancy Service to develop Water Sector Application

\n\n

 

\n\n

Introduction

\n\n

Since the declaration of the state of emergency to confront the Corona virus in Palestine and the instructions issued by the Prime Minister and in line with the prevailing national situation, the Palestine Water Authority (PWA) has taken a number of measures to ensure the sustainability of water and wastewater services efficiently and effectively. The PWA implement a precautionary emergency plan at the level of bulk water systems and the level of water and sanitation service providers in all governorates, in response to the government's strategic plan and goals to control the disease and limit its transmission, and provide basic needs for citizens.

\n\n

The Palestinian Water Authority is intensifying its current efforts in the context of the existing challenges facing the water sector, which has doubled with the spread of the COVID-19. Water sector in normal situation suffers from a decrease in the available water quantities especially in summer season.  As for wastewater services, more than 68% of the West Bank population and more than 28% of the Gaza Strip are still without adequate and safe sanitation services. The population still relies on cesspits to get rid of wastewater to this day. In addition, the majority challenges facing the service providers result from weak institutional capacity, inadequate infrastructure and high water losses.

\n\n

Issues that the PWA has been working relentlessly on includes:

\n\n\n\n

Considering the challenges facing the water sector , and due to the rapid spread of COVID-19 across Palestine, innovative new approaches are required to be developed to ensure appropriate communication between the Palestinian Water Authority, Service Providers and customers concerning water issues through a  unified platform, to ensure that WASH topics are being handled in a timely manner with high efficiency.

\n\n

 

\n\n

 

\n\n

The consultancy

\n\n

A. Objective:

\n\n

The firm is to support PWA in developing a native mobile application for water service providers and water customers- responding to emergency situation and facilitating quick and direct access to important information for customers and service providers.

\n\n

The Mobil application will support quick and effective responses to needs of different stakeholders, mainly service providers and water customer, and support disseminating coherent information and awareness messages to citizens across Palestine.

\n\n

 

\n\n

B. Application Component :

\n\n

The firm shall provide the following modules:

\n\n\n\n\n\n

The communication includes complains[1], clarifications, information, notification. The firm shall develop a separate page to send the request, or clarification, notification to the service providers or PWA with the ability to check the status (Received, in progress, complete) in the system and have it archived in an acceptable format for PWA.

\n\n\n\n

 

\n\n

C. Scope of work

\n\n
    \n\t
  1. Inception phase:  The Experts shall meet all relevant parties in PWA to understand existing software and hardware equipment’s at PWA related to the assignment in order to collect all needed data to fulfil the activities of the assignment. The firm is expected to prepare an inception report that includes comprehensive technical proposal. The inception report shall include (but not limited to) detailed working plan with milestones, deliverables, and anticipated risks related to the successful assignment completion and proposed mitigation measures…
    2. \n\t
  2. Development of a functional Mobile App design and architecture : The Consultant shall prepare a functional diagram design based on the inception report. It shall reflect the design of the data base related to the application, interfaces, links with other available applications in PWA, communication protocols and procedures, and its architecture function. The Consultant shall develop the application theme (interface theme) such as colours, fonts, visual design, wires frames, etc. The functional Mobile App design and architecture shall be approved by PWA.
    3. \n\t
  3. Application Development (CODE) : The firm shall develop the CODE in both Android & IOS. The CODE shall be developed in a professional form, be simple to understand and follow-up, and free of bugs. The mobile application will be managed by PWA . PWA and the firm will make test and quality assurance to the application and its function. The firm shall provide full source code with all assets to PWA.
    4. \n\t
  4. Application Release : The firm shall release the App in Google Play and Apple App. Store with a valid accounts related to PWA. The deployment fees for the first time should be covered by Firm and then handed over to PWA. The App release should be considered to have a development version and production version, and the firm should fully responsible for releasing both version.
    5. \n\t
  5. Capacity building: shall provide on job training to PWA team ( 2 employees ) . The training topics shall include the design of the App architectural, the App development, deployment, solving bugs, and administrate PWA employee on managing the App after contract completion
    6. \n\t
  6. User Management page: The firm shall develop a User management page were PWA can manage the App and provide support to other clients ( eg. add, delete users , manage pages and models , Audit, …). The firm shall develop user registration process in the App.
    7. \n\t
  7. Mobile App tutorials: The firm shall develop territorial material including manual, and application structure to support the use of the App, including frequently asked questions.
    8. \n\t
  8. Support and maintenance: The firm shall provide the needed support and maintenance for one year after the completion of the final App release. The firm is responsible for providing a free update of the App within the framework of this ToR, bug fixing and technical support for the application for one year after its launch.
    9. \n\t
  9. Final Reporting: The firm shall produce final reports for mobile application performance with recommendations for improvements and updates.
    10. \n
\n\n

 

\n\n

D. Application Description

\n\n\n\n

 

\n\n

E. Reporting and Outputs to be achieved:

\n\n

The firm will prepare, produce and submit the following outputs:

\n\n\n\n

 

\n\n

F. Services, and Facilities to be made available to the Expert

\n\n

Services, and facilities to be made available to the expert by PWA :

\n\n\n\n

 

\n\n

G. Management arrangements

\n\n

The firm will be technically, contractually and administratively responsible for the preparation and implementation of the assignment to the PWA. PWA will appoint a Focal Coordinator for this assignment.

\n\n

 

\n\n

H. Contracts Type and Payments Schedule

\n\n

The contract is Lump Sum. The payments schedule (Reference to Item E “Reporting and Outputs to be Achieved” of the ToR) is one payment 100% of contract value upon the submission of functional Mobile App design and releasing Application Development (CODE), conducing capacity building activities , developing Mobile App tutorials, and manual , and handing over the Final Report  (Output #1,2,3, 4,5,6) acceptable to PWA. The payment will be done upon Firm submission of written liability letter for one year to support the App according to the terms and conditions highlighted in this ToR.

\n\n

 

\n\n

Duration of The Contrat and milestines

\n\n\n\n

 

\n\n

Qualifications:

\n\n

The firm should have the following recent proven minimum experiences:

\n\n
    \n\t
  1. Well-established firm with 3 years of experience in development of IT using a complex database schema.
    2. \n\t
  2. Developed and implemented at least one similar assignment during the last 3 years
    3. \n\t
  3. Experience in the water sector is an added advantage
    4. \n
\n\n

The firm shall provide key Expert and supporting staff to fulfil the assignment. The key Expert shall hold the following qualifications:

\n\n
    \n\t
  1. strong experience in Mobile Application Development in Web, Hybrid, and Native and Application lifecycle management:
    2. \n\t
  2. Bachelor or master’s degree in information technology management or any other relevant filed
    3. \n\t
  3. Minimum of three years of experience in Mobile Application Development and Management
    4. \n\t
  4. Working experience within multicultural teams and international organizations
    5. \n\t
  5. App design, coding, backend web service knowledge
    6. \n\t
  6. Knowledge in UI & UX, Code reviews and automation
    7. \n\t
  7. Strong knowledge in iOS and Android SDK
    8. \n\t
  8. Excellent communication skills, oral, written, and presentation.
    9. \n\t
  9. Cross-browser compatibility, web user interface design (UI).
    10. \n\t
  10. Prototype Software experience for Mobile Developments.
    11. \n
\n\n

 

\n\n

[1] The firm shall consider existing Complain System for PWA ( exist at PWA Web ), Communication concerning complain between Service Provider and Customer to be developed in a simple manner

\n\n

 

\n\n

 

"},{"id":"OP00085136","notice_type":"Request for Expression of Interest","noticedate":"27-Feb-2020","notice_lang_name":"English","notice_status":"Published","submission_deadline_date":"2020-03-13T00:00:00Z","submission_deadline_time":"17:00","project_ctry_name":"Moldova","project_id":"P127734","project_name":"Tax Administration Modernization Project","bid_reference_no":"TAMP/2/CQS-6","bid_description":"Technical assistance for new State Tax Service web site","procurement_group":"CS","procurement_method_code":"CQS","procurement_method_name":"Consultant Qualification Selection","contact_address":"9 Constantin Tanase Street, 2nd Floor, MD-2005, Chisinau, Republic of Moldova","contact_ctry_name":"Moldova","contact_email":"tamp@sfs.md","contact_name":"Anastasia Movilă","contact_organization":"State Tax Service","contact_phone_no":"+373 22 82 33 75","contact_web_url":"http://www.sfs.md/","submission_date":"2020-02-27T00:00:00Z","notice_text":"

REQUEST FOR EXPRESSIONS OF INTEREST

\n\n

(CONSULTING SERVICES – FIRMS SELECTION)

\n\n

 

\n\n

Republic of Moldova

\n\n

Tax Administration Modernization Project

\n\n

Project ID Number: P127734

\n\n

Loan No./Credit No./ Grant No.: IDA Credit No. 5829-MD, IBRD Loan No. 8625-MD

\n\n

Reference No.: TAMP/2/CQS-5

\n\n

 

\n\n

Title of Assignment: Technical assistance for the development of the new State Tax Service website

\n\n

 

\n\n

The State Tax Service has received financing from the World Bank toward the cost of the Tax Administration Modernization Project and intends to apply part of the proceeds for technical assistance for the development of the new State Tax Service website.

\n\n

The technical assistance consists of developing the new STS website www.sfs.md, where taxpayers will be able to find useful information on tax administration and will be able to access all the electronic services provided by the authority.

\n\n

Detailed information is provided in Terms of References (Appendix 1).

\n\n

The State Tax Service now invites eligible consulting firms to indicate their interest in providing the Services. Interested Consultants should provide information demonstrating that they have the required qualifications and relevant experience mentioned in the attached Terms of Reference to perform the Services. The shortlisting criteria are:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

№

\n\t\t\t		\n\t\t\t

Criteria

\n\t\t\t		\n\t\t\t

Points

\n\t\t\t
\n\t\t\t
    \n\t\t\t\t
  1.  
    2. \n\t\t\t
\n\t\t\t		\n\t\t\t

Company’s experience as a web designer and developer using open source technologies proven by at least three (3) contracts with the development phase finalized in the last five (5) years (experience for public institution will be an asset), including inter alia company’s proven experience in:

\n\n\t\t\t

- required technology stack;

\n\n\t\t\t

- web UI design and development using responsive frameworks, progressive web apps;

\n\n\t\t\t

- unit testing, continuous integration, DevOps;

\n\n\t\t\t

- database design, development and optimization;

\n\n\t\t\t

- systems’ integration, API design and development using SOAP/REST;

\n\n\t\t\t

- IT and information security audit (GDPR, ISO / IEC 27002 etc.);

\n\n\t\t\t

- conducting training sessions for end-users and IT specialists and in on-line training development using e-learning system;

\n\n\t\t\t

- writing technical and end-user documentation.

\n\t\t\t		\n\t\t\t

70

\n\t\t\t
\n\t\t\t

       2.

\n\t\t\t		\n\t\t\t

Experience in software development using agile software development principles.

\n\t\t\t		\n\t\t\t

30

\n\t\t\t
\n\n

The attention of interested Consultants is drawn to paragraph 1.9 of the World Bank’s Guidelines: Selection and Employment of Consultants (under IBRD Loans and IDA Credits & Grants) by World Bank Borrowers, dated January 2011, revised July 2014, setting forth the World Bank’s policy on conflict of interest. 

\n\n

Consultants may associate with other firms in the form of a joint venture or a subconsultancy to enhance their qualifications.

\n\n

It is expected, that the services will be provided starting from May 2020 and continuing through December 2020, including 4 months for development and 3 months of warranty period.

\n\n

The Consultant will be selected in accordance with the Consultants’ Qualifications selection method set out in the Consultant Guidelines.

\n\n

Further information can be obtained at the address below during office hours 08:00 to 17:00 hours (Chisinau time).

\n\n

Expressions of interest must be delivered in a written form to the address below (in person, or by mail, or by e-mail) by March 13, 2020.

\n\n

State Tax Service

\n\n

Attn: Anastasia Movilă, Head of Organizational Management Department

\n\n

9 Constantin Tanase, Street, 2nd Floor, 246 office, MD-2005,

\n\n

Chisinau, Republic of Moldova

\n\n

Phone: +373 (22) 82-33-75

\n\n

Email: tamp@sfs.md.

\n\n

 

\n\n

 

\n\n

Terms of reference

\n\n

Technical assistance for the development of the new State Tax Service website

\n\n

Reference No: TAMP/2/CQS-5

\n\n

 

\n\n

1. GENERAL INFORMATION

\n\n

Background

\n\n

The Government of the Republic of Moldova is implementing a comprehensive Tax Administration Modernization Project (TAMP), aimed at reforming the State Tax Service (STS), funded by the International Development Association and the International Bank for Reconstruction and Development. 

\n\n

The long-term vision supported by the project is a tax administration with simplified business processes, supported by risk-based compliance management, efficient use of electronic communication with taxpayers, qualified and professional staff, contributing to inefficient taxpayer-oriented tax administration. The modernized tax administration will improve the business environment and improve the country's competitiveness.

\n\n

Electronic communication with taxpayers is done through the STS web page and the electronic services accessible through it. At the moment, the web page is simultaneously a useful information space for taxpayers and a window of electronic services offered by STS, based on two separate solutions and two separate domains. The gradual transition to the expanded digital interaction with the taxpayers requires the combination of these spaces and elaboration of a single counter with a set of useful components for individuals, legal entities, authorities and public institutions and, at the same time, with a set of tools for integration with the future system information of the STS.

\n\n

Mission objective

\n\n

The project development objective is to improve revenue collection, tax compliance and taxpayer services.

\n\n

The objective will be partially achieved by designing and launching a new STS website. In order to accomplish the proposed task, SFS is seeking an ICT consulting company to develop the new STS website www.sfs.md, where taxpayers will be able to find useful information on tax administration (for example, tax law, list of documents the contact addresses of the institution) and will be able to access all the electronic services provided by the authority.

\n\n

STS is seeking a consultancy company with experience in designing and implementing projects of similar complexity to provide continuous maintenance and technical support services.

\n\n

Parties involved

\n\n

The Company that will develop the new STS website (Consultant) will be responsible for execution of this assignment in the process of interacting with the following stakeholders (through STS) in order to achieve the objectives set forth in this document, including:

\n\n\n\n

Warranty

\n\n

The Consultant shall provide 3 months of warranty for the developed solution. The warranty period starts after final release. During the warranty period the Consultant shall fix any identified defects.

\n\n

Duration of the assignment

\n\n

It is expected, that the technical assistance for the development of the new STS website will be provided within three months from the contract signing date (7 months: 4 months for development and 3 months of warranty period), estimated period is May 2020 - December 2020.  

\n\n

2. SCOPE OF ASSIGNMENT

\n\n

The scope of this assignment is to design, develop, configure and deploy the web site as a fully functional product with all functionalities in place, according to the specifications defined by the STS (the set of requirements are listed in Annex 1 and Annex 2) and following the development approach described below.

\n\n

The portal will have a multi-dimensional structure and allows searching the services by a number of criteria, e.g taxpayers (individual and legal entities, individuals- residents, patent holders, residents and non-residents of the Republic of Moldova, etc.)  category, tax code, fiscal practice database, legislative acts, international treaties, electronic tax service, news, chat bot etc.

\n\n

The portal will serve as a one-stop space for accessing public information and electronic services provided by STS, accurate, and accessible information to visitors about public electronic tax services.

\n\n

The development of the solution will be based on following software development principles and must be in compliance with the legal and regulatory documents listed in Annex 3.

\n\n

Iterative development

\n\n

The solution shall be developed in iterations named sprints, implementation of different functionalities will take place in phases with some modules being in production while others still being in development. The priorities of functionalities which are included in a sprint will be determined by the STS. Sprint duration will be determined by the STS together with the Consultant.

\n\n

Agile development

\n\n

The development shall follow agile principles by allowing change and flexibility in implementation. STS will maintain the master list of generic requirements for the solution– product backlog, which consists of ordered business and technical requirements as seen by the STS. Items in product backlog are ordered by the STS by their priorities. STS is free to manage the product backlog by adding new items to it, removing items and reordering them as it is desired. At the beginning of each sprint, the topmost number (N) of items that fit into a sprint are taken, and a sprint backlog is built out of them. Items in sprint backlog are further detailed and distributed to developers. Sprint backlog is not changed during the sprint.

\n\n

Working product in each iteration

\n\n

Each sprint ends up in a working product which is presented to the STS for acceptance in the last day(s) of sprint then uploaded, released and then it will move on to the next sprint. The working product shall meet the agreed criteria – Definition of Done (e.g. it must be fully functional, fully tested, accompanied with relevant unit tests, accompanied with relevant documentation where necessary, complete commented source code supplied etc. as well as uploaded / launched on the new page).

\n\n

Technology stack

\n\n

To preserve STS, the solution shall be developed using the latest versions of the following technology stack:

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

№

\n\t\t\t		\n\t\t\t

Category

\n\t\t\t		\n\t\t\t

Technology

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

OS

\n\t\t\t		\n\t\t\t

Linux

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Web server

\n\t\t\t		\n\t\t\t

Apache / NGINX

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Language

\n\t\t\t		\n\t\t\t

PHP / JAVA / Python/ Ruby

\n\t\t\t
\n\t\t\t

4

\n\t\t\t		\n\t\t\t

Data Base

\n\t\t\t		\n\t\t\t

MySQL / MongoDB/ PostgreSQL

\n\t\t\t
\n\t\t\t

5

\n\t\t\t		\n\t\t\t

Framework

\n\t\t\t		\n\t\t\t

Drupal / Symphony / Laravel / Ruby on rails/ Struts, etc

\n\t\t\t
\n\n

During the development process, the Consultant or the STS may propose use of additional components required for the development and proper functionality of the solution in production.

\n\n

3. Deliverables

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

ID

\n\t\t\t		\n\t\t\t

Deliverable

\n\t\t\t		\n\t\t\t

Description

\n\t\t\t		\n\t\t\t

Delivery term

\n\t\t\t
\n\t\t\t

The following reports will be provided during the assignment by the Consultant for each sprint:

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

"Next Sprint Backlog"

\n\t\t\t		\n\t\t\t

Includes the breakdown and estimated duration of the proposed tasks, the resources that STS will provide to the Consultant and / or actions to be undertaken by STS, to be implemented in the first sprint. The document will be delivered electronically and on paper in Romanian.

\n\t\t\t		\n\t\t\t

within 5 days of signing the contract

\n\n\t\t\t

and

\n\n\t\t\t

 on the day of submission and reporting of the works performed from the previous sprint

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Sprint Report

\n\t\t\t		\n\t\t\t

Includes release notes, sprint acceptance minutes, breakdown and duration of tasks implemented during the sprint, velocity, issues and outstanding problems, proposed actions to be taken. The document will be delivered electronically and on paper in Romanian.

\n\t\t\t		\n\t\t\t

within 5 days from the reporting and actual presentation of the works of the sprint

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

The Program / Plan of training sessions

\n\t\t\t		\n\t\t\t

Includes training sessions for target groups, such as web site administrators, service providers, portal managers. Documents will be delivered electronically and on paper in Romanian.

\n\t\t\t		\n\t\t\t

within 5 days from the date of the last sprint presentation

\n\t\t\t
\n\t\t\t

The consultant will provide the following final deliverables for the execution of the contract:

\n\t\t\t
\n\t\t\t

1

\n\t\t\t		\n\t\t\t

Information system

\n\t\t\t		\n\t\t\t

A fully functional information system with all functionalities developed and deployed according to the requirements defined by the STS during the assignment. The Consultant will deliver compliable and documented source code (including third-party tools and libraries, licenses, where applicable and automation scripts). Information and functionalities of the system will be delivered in Romanian, Russian and English.

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

within 3 months from the signing of the contract

\n\t\t\t
\n\t\t\t

2

\n\t\t\t		\n\t\t\t

Technical and End-user documentation

\n\t\t\t		\n\t\t\t

Documentation developed according to the STS’s documentation requirements defined in Annex 2. It will be delivered electronically (Word, PDF etc.) and in two copies on paper in Romanian, Russian and English.

\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

3

\n\t\t\t		\n\t\t\t

Training reports

\n\t\t\t		\n\t\t\t

Reports developed in accordance with the training requirements of the STS mentioned in Annex 2), like:

\n\n\t\t\t
    \n\t\t\t\t
  • Materials related to training;
    • \n\t\t\t\t
  • Minutes of the training, the lists of participants, test results.
    • \n\t\t\t
\n\n\t\t\t

Documents will be delivered electronically and on paper in Romanian.

\n\t\t\t
\n\n

4. Qualification Requirements

\n\n

Consultant qualifications requirements

\n\n

The Consultant shall furnish documentary evidence (including information about the completed contracts and contact information of clients from whom the references could be taken or whom the STS may, when necessary, visit to familiarize themselves with the systems put into operation by the Consultant) to demonstrate that it meets the following experience requirements:

\n\n
    \n\t
  1. Experience as a web designer and developer using open source technologies proven by at least three (3) contracts with the development phase finalized in the last five (5) years.
    2. \n\t
  2. Experience as a web designer and developer using open source technologies for public institution will be an asset.
    3. \n\t
  3. Experience in software development using agile software development principles. This qualification shall be demonstrated by presenting the project methodology describing the role of the company.
    4. \n\t
  4. Certifications in any technology from the required technology stack;
    5. \n\t
  5. Demonstrated experience using required technology stack;
    6. \n\t
  6. Experience in web UI design and development using responsive frameworks, progressive web apps;
    7. \n\t
  7. Experience with unit testing, continuous integration, DevOps;
    8. \n\t
  8. Proven experience in database design, development and optimization;
    9. \n\t
  9. Proven experience in systems’ integration, API design and development using SOAP/REST;
    10. \n\t
  10. Experience of IT and information security audit (GDPR, ISO / IEC 27002 etc.);
    11. \n\t
  11. Proven experience in conducting training sessions for end-users and IT specialists and in on-line training development using e-learning system;
    12. \n\t
  12. Proven experience in writing technical and end-user documentation;
    13. \n
\n\n

Staff qualifications requirements

\n\n

The Consultant shall provide a team of the following key experts:

\n\n\n\n

5. Client’s input

\n\n

The STS will provide support for the meeting space, meeting agenda and logistics. In order to enable the Consultant to achieve the objective of the consultancy, the STS will provide the Consultant with the:

\n\n\n\n

- over 2,000,000 symbols

\n\n

- 5000 grid tables

\n\n

- 2000 news

\n\n

- 5000 pdf files - tax reports, instructions, laws, orders etc.

\n\n

- 1000 text files - Word, Notepad

\n\n

- 1000 table files - Excel

\n\n

- 500 presentation files - Powerpoint

\n\n

- 5000 photo files - jpg, png, gif, tiff, bmp, etc.

\n\n

- 500 video and audio files - mpeg, avi, mkv, mp3, flac etc.

\n\n

During the definition of the sprinting and reporting requirements, amount of information and files can be adjusted, according to the needs found during the implementation.

\n\n

6. Working arrangements

\n\n

The Consultant shall be responsible for all logistics and accommodations that will be required to perform the assignment, as well as interpretation and translation services, if needed.

\n\n

The Consultant will ensure visits to the STS site to provide training to end users.

\n\n

The language of communication during the assignment is Romanian.

\n\n

The Consultant shall demonstrate a high-level professional behavior in its working relationships with all relevant stakeholders in performing this assignment.

\n\n

To ensure that Consultant is in position to deliver on time working products, a STS team will interact with Consultant for answering eventual questions and coordinate all issues related to the technical elements of the assignment.

\n\n

The documents will be delivered to the State Tax Service, indicating the name of the head of the institution, which will further ensure the dissemination of the information to the parties involved in the process.

\n\n

The Consultant will report directly to the person designated by the STS, supervising the project implementation work.

\n\n

Consultant will deliver the Technical and End-user Documentation for acceptance. STS will review the Documentation internally and prepare the list of comments or accept the document.

\n\n

STS will deliver to Consultant the consolidated list of comments within 10 days after receipt of the Consultant’s Technical and End-user documentation.

\n\n

Consultant will review the list of comments and modify/complete the report within 5 days after receipt.

\n\n

Annexes

\n\n

Annex 1. Business Requirements

\n\n

This Annex describes the Functional Requirements of web site. Functional requirements identify what the system does, they define a specific function that sets what the system is supposed to accomplish.

\n\n

The Functional Requirements are defined using User Stories. Each user story is described as a need of an identified user.

\n\n

Public User

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

ID

\n\t\t\t		\n\t\t\t

Description

\n\t\t\t
\n\t\t\t

US-PU-1.001

\n\t\t\t		\n\t\t\t

Public User should be able to search for services through a list of pre-defined filters so that I can identify the needed service without entering any search criteria.

\n\t\t\t
\n\t\t\t

US-PU-1.002

\n\t\t\t		\n\t\t\t

Public User should be able to apply filters in any of the available languages (at least Romanian and Russian) so that I can understand all the results.

\n\t\t\t
\n\t\t\t

US-PU-1.003

\n\t\t\t		\n\t\t\t

Public User should be able to view and read the results of the query so that I can assess if they correspond to what I needed.

\n\t\t\t
\n\t\t\t

US-PU-1.004

\n\t\t\t		\n\t\t\t

Public User should be able to return to previous levels of the filters hierarchy so that I can re-submit the search query if the results are not satisfactory.

\n\t\t\t
\n\t\t\t

US-PU-1.005

\n\t\t\t		\n\t\t\t

Public User should be able to access the links included in the results obtained so that I can retrieve the information I need.

\n\t\t\t
\n\t\t\t

US-PU-1.006

\n\t\t\t		\n\t\t\t

Public User should receive an ‘’Error 404: Not found’’ in case the result of my search query is a broken link so that I can be aware of that fact.

\n\t\t\t
\n\t\t\t

US-PU-1.007

\n\t\t\t		\n\t\t\t

Public User should be able to provide his feedback anonymously so that he can protect his personal information.

\n\t\t\t
\n\t\t\t

US-PU-1.008

\n\t\t\t		\n\t\t\t

Public User should be able to provide my feedback in any of the available languages (at least RO, RU, EN) so that he can use the language he feel more comfortable with.

\n\t\t\t
\n\t\t\t

US-PU-1.009

\n\t\t\t		\n\t\t\t

Public User should input a search query expressed by providing relevant keywords so that he can get relevant results.

\n\t\t\t
\n\t\t\t

US-PU-1.010

\n\t\t\t		\n\t\t\t

Public User should be able to use a list of autocomplete/suggestion keywords so that he can express my query easily.

\n\t\t\t
\n\t\t\t

US-PU-1.011

\n\t\t\t		\n\t\t\t

Public User should be able to use any of the available languages (at least RO and RU) so that I can express my query.

\n\t\t\t
\n\t\t\t

US-PU-1.012

\n\t\t\t		\n\t\t\t

The results of Public User queries to be structured so that he get it in the shape of a result list that shows the metadata and links to the relevant web resource on a Service Provider website, ordered by relevancy.

\n\t\t\t
\n\t\t\t

US-PU-1.013

\n\t\t\t		\n\t\t\t

Public User should be able to use custom filters, so he can query in a more specific way.

\n\t\t\t
\n\t\t\t

US-PU-1.014

\n\t\t\t		\n\t\t\t

The results of Public User queries to contain a link to corresponding services so that he can access the corresponding services information.

\n\t\t\t
\n\t\t\t

US-PU-1.015

\n\t\t\t		\n\t\t\t

The results of Public User queries to be ordered by relevancy so that he can perform a helpful search.

\n\t\t\t
\n\t\t\t

US-PU-1.016

\n\t\t\t		\n\t\t\t

Public User should be able to filter his query by any of the web site registered classification (ex. Service, Service Type, STS Service Provider, last update date, type of document, most rated) so that he just retrieve the filtered information.

\n\t\t\t
\n\t\t\t

US-PU-1.017

\n\t\t\t		\n\t\t\t

Public User should be able to save locally or print any of the search result so that he can use the information offline.

\n\t\t\t
\n\t\t\t

US-PU-1.018

\n\t\t\t		\n\t\t\t

Public User should be able to authenticate to web site, so that he can acces the Authenticated user functionalities.

\n\t\t\t
\n\t\t\t

US-PU-1.019

\n\t\t\t		\n\t\t\t

Public User should be able to search for life event through a list of pre-defined life events so that he can identify the needed services.

\n\t\t\t
\n\t\t\t

US-PU-1.020

\n\t\t\t		\n\t\t\t

Public User should be able to search for business event through a list of pre-defined business events so that I can identify the needed services.

\n\t\t\t
\n\t\t\t

US-PU-1.021

\n\t\t\t		\n\t\t\t

Public User should be able to interact with a chatbot tool using natural language so that I can find general information about services, life events and business events based on provided information such as age, social status, marital status etc.

\n\t\t\t
\n\t\t\t

US-PU-1.022

\n\t\t\t		\n\t\t\t

Public User should be able to give access to my location, so that he can get personalize information about Service Providers working hours and locations near me.

\n\t\t\t
\n\n

Authenticated User

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

ID

\n\t\t\t		\n\t\t\t

Description

\n\t\t\t
\n\t\t\t

US-AU-2.001

\n\t\t\t		\n\t\t\t

Authenticated User should to be able to provide my feedback on quality and availability of the services provided through the web site and of the common user interface, so that my feedback can be considered for future improvements.

\n\t\t\t
\n\t\t\t

US-AU-2.002

\n\t\t\t		\n\t\t\t

Authenticated User should  be able to interact with a chatbot tool using natural language so that he can find information about services, life events and business events related to my status (age, social status, marital status etc.)

\n\t\t\t
\n\t\t\t

US-AU-2.003

\n\t\t\t		\n\t\t\t

Authenticated User should  be able to configure my own workspace in portal so that he can setup and configure some preferences using web site (ex. notifications, favorites).

\n\t\t\t
\n\n

 

\n\n

Service Provider

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

ID

\n\t\t\t		\n\t\t\t

Description

\n\t\t\t
\n\t\t\t

US-SP-3.001

\n\t\t\t		\n\t\t\t

STS Service Provider should be able to login into the web site, so that he can have access to all functionalities associated to my role.

\n\t\t\t
\n\t\t\t

US-SP-3.002

\n\t\t\t		\n\t\t\t

STS Service Provider should be able to manage services he is responsible in any of the available languages so that others can understand them.

\n\t\t\t
\n\t\t\t

US-SP-3.003

\n\t\t\t		\n\t\t\t

STS Service Provider should be able to upload items to a service so that others can access or download them.

\n\t\t\t
\n\t\t\t

US-SP-3.004

\n\t\t\t		\n\t\t\t

STS Service Provider should be able to view uploaded service items so that he can consult them.

\n\t\t\t
\n\t\t\t

US-SP-3.005

\n\t\t\t		\n\t\t\t

STS Service Provider should be able to communicate with other Service Providers through a communication system so that he can exchange information.

\n\t\t\t
\n\t\t\t

US-SP-3.006

\n\t\t\t		\n\t\t\t

STS Service Provider should be able to request and have access to a report on feedbacks on quality of services managed by me so that he can have information to support my decisions.

\n\t\t\t
\n\t\t\t

US-SP-3.007

\n\t\t\t		\n\t\t\t

STS Service Provider should be able to print the reports and download the data so that he can work offline.

\n\t\t\t
\n\t\t\t

US-SP-3.08

\n\t\t\t		\n\t\t\t

STS Service Provider should be able to manage the service links (legal, corresponding services etc.) so that the links can be crawled.

\n\t\t\t
\n\t\t\t

US-SP-3.009

\n\t\t\t		\n\t\t\t

STS Service Provider should receive a notification of approved changes of services managed by me so that he can get information that my changes were approved.

\n\t\t\t
\n\t\t\t

US-SP-3.010

\n\t\t\t		\n\t\t\t

STS Service Provider should receive a notification of rejected changes of services managed by me so that he can revise and change them.

\n\t\t\t
\n\t\t\t

US-SP-3.011

\n\t\t\t		\n\t\t\t

STS Service Provider should be able to deliver to the web site the user feedback data collected at Institution level, so that it can be taken into account to improve quality and availability of the services.

\n\t\t\t
\n\t\t\t

US-SP-3.012

\n\t\t\t		\n\t\t\t

STS Service Provider should be able to indicate georeferenced locations, so that the Users are displayed information about the locations closest to them (working hours, Address, etc.)

\n\t\t\t
\n\t\t\t

US-SP-3.013

\n\t\t\t		\n\t\t\t

STS Service Provider should be able to manage life and business events by adding or removing life event related services and relations between them so that they will be available to users.

\n\t\t\t
\n\n

Portal administrator

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

ID

\n\t\t\t		\n\t\t\t

Description

\n\t\t\t
\n\t\t\t

US-PA-4.001

\n\t\t\t		\n\t\t\t

Portal Administrator should be able to login into the web site System so that I can have access to all functionalities associated to my role.

\n\t\t\t
\n\t\t\t

US-PA-4.002

\n\t\t\t		\n\t\t\t

Portal Administrator should be able to view, create, delete or update role assignments for users so that the user's interaction with the system is controlled.

\n\t\t\t
\n\t\t\t

US-PA-4.003

\n\t\t\t		\n\t\t\t

Portal Administrator should be able to create, view update or delete languages so that the languages can be available and used for localization by the system.

\n\t\t\t
\n\t\t\t

US-PA-4.004

\n\t\t\t		\n\t\t\t

Portal Administrator should be able to create, view, update or delete classifications so that the classifications are available to be used by the system.

\n\t\t\t
\n\t\t\t

US-PA-4.005

\n\t\t\t		\n\t\t\t

Portal Administrator should be able to create, view, update or delete links to a web resource on a Service Providers website so that the classifications are available to be used by the system.

\n\t\t\t
\n\t\t\t

US-PA-4.006

\n\t\t\t		\n\t\t\t

Portal Administrator should be able to create, view, update or delete classification of feedback on quality so that the classifications are available to be used by the system.

\n\t\t\t
\n\t\t\t

US-PA-4.007

\n\t\t\t		\n\t\t\t

Portal Administrator should be able to CRUD (Create, Read, Update, and Delete) classifications of statistics so that the statistics can be analyzed more easily

\n\t\t\t
\n\t\t\t

US-PA-4.008

\n\t\t\t		\n\t\t\t

Portal Administrator should be able to communicate with other users through a communication platform so that he can exchange information.

\n\t\t\t
\n\t\t\t

US-PA-4.009

\n\t\t\t		\n\t\t\t

Portal Administrator should be able to request and have access to a report on statistics of defined indicators so that he can have information to support my decisions.

\n\t\t\t
\n\t\t\t

US-PA-4.010

\n\t\t\t		\n\t\t\t

Portal Administrator should be able to request and have access to a report on feedbacks on quality of published services so that he can have information to support my decisions.

\n\t\t\t
\n\t\t\t

US-PA-4.011

\n\t\t\t		\n\t\t\t

Portal Administrator should be able to print the reports and download the data so that he can work offline.

\n\t\t\t
\n\t\t\t

US-PA-4.012

\n\t\t\t		\n\t\t\t

Portal Administrator should be able to manage feedbacks so that the feedbacks can be analyzed more easily.

\n\t\t\t
\n\n

Portal Manager

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

ID

\n\t\t\t		\n\t\t\t

Description

\n\t\t\t
\n\t\t\t

US-PM-5.001

\n\t\t\t		\n\t\t\t

Portal Manager should be able to login into the web site, so that he can have access to all functionalities associated to my role.

\n\t\t\t
\n\t\t\t

US-PM-5.002

\n\t\t\t		\n\t\t\t

Portal Manager should be able to view, create and delete role assignments for Service Providers so that the user's interaction with the system is controlled.

\n\t\t\t
\n\t\t\t

US-PM-5.003

\n\t\t\t		\n\t\t\t

Portal Manager should be able to view the complete or filtered users’ lists so that he can have necessary information about users.

\n\t\t\t
\n\t\t\t

US-PM-5.004

\n\t\t\t		\n\t\t\t

Portal Manager should be able to approve Service Providers’ requests for submitting service passport changes so that the updated information can be available in ITMS System.

\n\t\t\t
\n\t\t\t

US-PM-5.005

\n\t\t\t		\n\t\t\t

Portal Manager should be able to reject Service Providers’ requests for submitting service passport changes indicating the reason so that Service Provider will be able to correct the errors.

\n\t\t\t
\n\t\t\t

US-PM-5.006

\n\t\t\t		\n\t\t\t

Portal Manager should be able to communicate with other users through a communication system so that he can exchange information.

\n\t\t\t
\n\t\t\t

US-PM-5.007

\n\t\t\t		\n\t\t\t

Portal Manager should be able to track each Service Providers' progress towards publishing and updating the provided services passports so that he can have complete information about the progress.

\n\t\t\t
\n\t\t\t

US-PM-5.008

\n\t\t\t		\n\t\t\t

Portal Manager should be able to generate a report on feedbacks on quality of the published services so that he can have information to support my decisions.

\n\t\t\t
\n\t\t\t

US-PM-5.009

\n\t\t\t		\n\t\t\t

Portal Manager should be able to print the reports and download the data in an open format (ex. *.csv) so that he can work offline.

\n\t\t\t
\n\t\t\t

US-PM-5.010

\n\t\t\t		\n\t\t\t

Portal Manager should be able to forward the feedbacks on obstacles accessed to a Service Providers so that they can analyze them.

\n\t\t\t
\n\t\t\t

US-PM-5.011

\n\t\t\t		\n\t\t\t

Portal Manager should be able to consult an online overview on the obstacles identified through the End users’ feedbacks, so that he can verify that the information is provided correctly to the End users.

\n\t\t\t
\n\t\t\t

US-PM-5.012

\n\t\t\t		\n\t\t\t

Portal Manager should he want to be able to export the reports in a PDF format, so that he can save it for myself and share it.

\n\t\t\t
\n\t\t\t

US-PM-5.013

\n\t\t\t		\n\t\t\t

Portal Manager should register new Service Providers, so they will be able to manage their services.

\n\t\t\t
\n\t\t\t

US-PM-5.014

\n\t\t\t		\n\t\t\t

Portal Manager should be able to assign new users to web site, so they can be assigned to one role.

\n\t\t\t
\n\t\t\t

US-PM-5.015

\n\t\t\t		\n\t\t\t

Portal Manager should be able to visualize and export the complete user list, users’ lists filtered by Service Providers, by Services and by role so that he can search easily a user.

\n\t\t\t
\n\t\t\t

US-PM-5.016

\n\t\t\t		\n\t\t\t

Portal Manager should be able to manage service categories so that Service Providers will be able to add their services to available categories. 

\n\t\t\t
\n\t\t\t

US-PM-5.017

\n\t\t\t		\n\t\t\t

Portal Manager should be able to manage life and business events by adding or removing life event related services and relations between them so that they will be available to users.

\n\t\t\t
\n\n

Annex 2. Technical Requirements

\n\n

Documentation requirements 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

User Documentation 

\n\t\t\t		\n\t\t\t

The Consultant will prepare and deliver the following documentation for end-users: 

\n\n\t\t\t
    \n\t\t\t\t
  • \n\t\t\t\t
      \n\t\t\t\t\t
    • Interactive guidance included in user interface of web site adjusted to user role (Public user, Authenticated User, Service provider, Web site Administrator, Web site Manager) 
      • \n\t\t\t\t\t
    • Downloadable user manuals in PDF format for Service Provider, Portal Administrator, etc. 
      • \n\t\t\t\t
    \n\t\t\t\t
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

How-To video tutorials 

\n\t\t\t		\n\t\t\t

The Consultant will prepare How-To video tutorials for ITMS main functions. 

\n\t\t\t
\n\t\t\t

Technical documentation 

\n\t\t\t		\n\t\t\t

The Consultant will prepare and deliver the following technical documentation: 

\n\n\t\t\t
    \n\t\t\t\t
  • \n\t\t\t\t
      \n\t\t\t\t\t
    • System architecture documentation (including description of models in UML language, which will include a sufficient level of details of the system architecture) 
      • \n\t\t\t\t\t
    • Test strategy document
      • \n\t\t\t\t\t
    • Compilable and documented source code for applications, components and unit tests developed within the project  
      • \n\t\t\t\t\t
    • System installation and configuration manual (including code compilation, container image build scripts, system installation, hardware and software requirements, platform description and configuration, backup and disaster recovery procedures) 
      • \n\t\t\t\t
    \n\t\t\t\t
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

API documentation 

\n\t\t\t		\n\t\t\t

The Consultant will prepare and deliver: 

\n\n\t\t\t
    \n\t\t\t\t
  • \n\t\t\t\t
      \n\t\t\t\t\t
    • API integration guide  
      • \n\t\t\t\t\t
    • Integration samples in PHP and JavaScript  
      • \n\t\t\t\t\t
    • Human and machine-readable description in a standard description language (e.g. WSDL or Swagger). 
      • \n\t\t\t\t
    \n\t\t\t\t
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

Sprint documentation

\n\t\t\t		\n\t\t\t

The consultant will prepare and provide the following sprint documentation:
\n\t\t\t"Next Sprint Backlog", which includes the breakdown and estimated duration of the proposed tasks, the resources that STS will provide to the Consultant and / or actions to be undertaken by STS.

\n\n\t\t\t


\n\t\t\tSprint report, including release notes, sprint acceptance minutes, breakdowns and duration of tasks implemented during the sprint, outstanding issues, proposed actions to be implemented

\n\t\t\t
\n\n

 

\n\n

Training requirements 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Training sessions 

\n\t\t\t		\n\t\t\t

The Consultant will provide training sessions for target groups such as web site Administrators, Service Providers, Portal Managers. 

\n\t\t\t
\n\t\t\t

Training reports

\n\t\t\t		\n\t\t\t

Training programs– minutes of training, lists of participants, (manuals, video tutorials, quizzes, PowerPoint etc.) for administrators, services providers, portal managers and end-users (individuals and businesses). 

\n\n\t\t\t

All training content/materials will be provided in Romanian. 

\n\t\t\t
\n\n

Rights requirements 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Perpetual software license 

\n\t\t\t		\n\t\t\t

The Consultant grants to the STS the rights to run and use entire solution with all included software components with no constraints on time, location and offered functionality.  

\n\t\t\t
\n\t\t\t

Redistribution rights 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The Consultant shall grant to the STS the right to re-distribute the solution.  

\n\n\t\t\t

While the STS does not intend to re-distribute at a massive scale it still envisions the need to transfer the software solution to another state agency due for example to potential reorganization. Also, the STS might get the opportunity to re-deploy the entire e-Government platform elsewhere. 

\n\t\t\t
\n\t\t\t

Full data rights 

\n\t\t\t		\n\t\t\t

The STS keeps full rights on data created by the means of this solution. 

\n\t\t\t
\n\t\t\t

Open data format 

\n\t\t\t		\n\t\t\t

The solution preserves the data in an open format or includes mechanisms to extract data from the system in an open format thus enabling the capability to transfer/migrate the data into another system. 

\n\t\t\t
\n\n
    \n\t
  1. Architecture requirements 
    2. \n
\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Open standards 

\n\t\t\t		\n\t\t\t

The solution architecture shall be based on relevant open standards. The solution architecture shall not use proprietary standards. 

\n\t\t\t
\n\t\t\t

Service Oriented Architecture 

\n\t\t\t		\n\t\t\t

The solution shall be based on a Service Oriented Architecture. 

\n\t\t\t
\n\t\t\t

Hosting environment 

\n\t\t\t		\n\t\t\t

The solution shall not include any hardware components and upon finalization will be deployed on governmental cloud environment (MCloud). 

\n\t\t\t
\n\t\t\t

Running environment 

\n\t\t\t		\n\t\t\t

System shall run on Docker container engine and shall not depend on specific host OS instance. Building container images shall be automated. (refer to the following link for details: https://docs.docker.com/develop) 

\n\n\t\t\t

Running in a container-based environment, the application must be elastic, including when adding/removing application container instances (above minimum required instances for HA), changing of configurations and system parameters has no impact on any work in progress, such as any active sessions, requests, etc. 

\n\t\t\t
\n\t\t\t

Multiple sites 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The solution architecture shall ensure high availability (functional availability will be provided by CTIF, therefore, the availability is on average 96%, and their accessibility is 24/24, 7 days a week, 365 days a year.) including during new versions deployment and the possibility to run simultaneously on multiple sites 

\n\t\t\t
\n\t\t\t

Browser compatibility requirements 

\n\t\t\t		\n\t\t\t

The system shall be compatible with latest two major versions (to be considered at the time of system acceptance) of following web browsers: Chrome, Safari, FireFox and Edge. 

\n\t\t\t
\n\t\t\t

Detailed data model 

\n\t\t\t		\n\t\t\t

System's detailed data model shall be described fully in a machine-readable data scheme for example using a DDL language for relational databases.  

\n\n\t\t\t

The Consultant shall coordinate the detailed data model schema format with the STS in advance. 

\n\t\t\t
\n\n

System Integration requirements 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Governmental platform services integration 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

MPass shall be used to authenticate users;

\n\n\t\t\t

MLog shall be used to journal business critical events. The events that are business critical will be defined at analysis and design stages and must be configurable;

\n\n\t\t\t

MNotify shall be used for notifications.

\n\t\t\t
\n\t\t\t

Open data integration 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Web site shall publish agreed sets of data in a machine-readable format to Open Data portal located at date.gov.md using its API. 

\n\n\t\t\t

Web site shall provide integration between Fiscal practice database and Telegram chatbot.

\n\n\t\t\t

 

\n\t\t\t
\n\t\t\t

Integration with electronic services

\n\t\t\t		\n\t\t\t

The site will be the gateway to the electronic tax services provided by STS to taxpayers.

\n\n\t\t\t

Access to the electronic tax services will be performed from the compartment intended for them, from the personal tax office of the taxpayer, depending on the status, role, etc.

\n\n\t\t\t

The system will be integrated with each existing electronic service in the current STS system, available on the portal.  www.servicii.fisc.md. The integration of the portal with the current services will be realigned by the Consultant, including IP Center for Information Technologies in Finance.

\n\t\t\t
\n\t\t\t

Integration with social media platforms

\n\t\t\t		\n\t\t\t

Ability to incorporate all the network’s social media platforms (Facebook, Twitter, YouTube, etc.) with live update options.

\n\n\t\t\t

Incorporate Google analytics

\n\t\t\t
\n\n

   System Performance requirements 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Asynchronous processing 

\n\t\t\t		\n\t\t\t

System shall use asynchronous processing whenever possible to perform any input-output.  

\n\t\t\t
\n\t\t\t

Concurrent users 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The system standard load and performance shall be guaranteed for 100 concurrent human users. 

\n\t\t\t
\n\t\t\t

Response time 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Response time for system functions shall be under 3 (three) second. The Consultant shall list the exceptions, if any, and discuss/agree them with the STS at analysis and design stages. 

\n\t\t\t
\n\t\t\t

Key performance Indicators 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The system shall meter and expose its key performance indicators. The Consultant shall propose the list of indicators and discuss/agree them with the STS. 

\n\t\t\t
\n\n

 User Interface requirements 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Multilanguage User Interface 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The system shall support multilanguage user interface. This support includes data type specific formats (such as date, time, time spans, currencies, etc.). The system front-end interface will be delivered with at least Romanian, Russian and English interfaces. The system back-end shall be delivered at least in Romanian. The default language for User interface shall be the Romanian.  

\n\t\t\t
\n\t\t\t

User Interface accessibility  

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

User interface shall conform at least to Level A of Web Content Accessibility Guidelines 2.0. 

\n\n\t\t\t

https://www.w3.org/TR/WCAG20/ 

\n\n\t\t\t

The accessibility of the website will be ensured for different categories of users with deficiencies (visual impairments, hearing impairments, etc.).

\n\t\t\t
\n\t\t\t

Responsive/Adaptive design 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The system user interface shall automatically adapt to various display resolutions. Minimal display width is 480px. 

\n\n\t\t\t

The system’s UI shall be implemented using progressive web application (PWA) technologies and shall be functional on mobile devices.  

\n\t\t\t
\n\t\t\t

Contextual help 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

User Interface elements shall include Tips and Hints for user interface elements.  

\n\t\t\t
\n\t\t\t

STS support 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

All pages shall include STS support contacts. 

\n\t\t\t
\n\t\t\t

Bookmarks 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

All major web site pages shall be bookmarkable and the User shall be able to access bookmarked pages later. 

\n\n\t\t\t

The bookmarkable pages will be defined at analyzing stage. 

\n\t\t\t
\n\t\t\t

Friendly URLs 

\n\t\t\t		\n\t\t\t

Web site shall use friendly URLs for accessing its pages. 

\n\t\t\t
\n\n

System maintenance requirements 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

System logs 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The system shall log its various actions and events in a structured manner. Logging shall be configurable and based on extensible logging framework (such as log4net, nlog, etc.). Logging framework shall minimally support JSON format and the following targets: console, rolling files, UDP and HTTP POST. 

\n\t\t\t
\n\t\t\t

Log levels and event log records 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The system shall differentiate events and actions it logs into at least following levels: Critical, Error, Warning, Info, Debug 

\n\n\t\t\t

Critical and Error level events shall be logged only for non-recoverable error that require human intervention. 

\n\n\t\t\t

Event log records will include at least: 

\n\n\t\t\t
    \n\t\t\t\t
  • \n\t\t\t\t
      \n\t\t\t\t\t
    • the type of the event 
      • \n\t\t\t\t\t
    • timestamp when the event took place 
      • \n\t\t\t\t\t
    • event level 
      • \n\t\t\t\t\t
    • system component that produced the event 
      • \n\t\t\t\t\t
    • user/user agent, IP that triggered the event 
      • \n\t\t\t\t\t
    • information object identifier affected 
      • \n\t\t\t\t\t
    • textual details about the produced event 
      • \n\t\t\t\t
    \n\t\t\t\t
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

Graceful shutdown 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The system shall implement graceful shutdown, i.e. shutting down an application container instance at any time shall not impact any work in progress, such as any active sessions, requests, event logs, etc.  

\n\t\t\t
\n\t\t\t

Source code 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The Consultant shall supply all the source code for system components that are not available as COTS from third parties. 

\n\n\t\t\t

The source code shall use package managers for dependencies to 3rd party libraries. All prerequisite software must be part of container image definition and based on public container repository. 

\n\t\t\t
\n\t\t\t

System deployment 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The Consultant shall supply the deployment procedure and supporting tools for this. Deployment procedure shall cover all the prerequisites before proceeding to system installation. The deployment shall be automated and include database structure initialization and seeding. 

\n\t\t\t
\n\t\t\t

System upgrades 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

System upgrades shall be automated, including database upgrade/downgrade scripts or code. To enable rolling upgrades in production environment, the recommended practice is to perform database breaking changes in incremental changes. 

\n\t\t\t
\n\n

Security requirements 

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Secure architecture

\n\t\t\t		\n\t\t\t

The system shall be secure by design and comply with the relevant requirements specified in GD 201 from 28.03.2017 (http://lex.justice.md/md/369772/).  

\n\n\t\t\t

The Consultant shall supply documentation describing this design and supporting evidences that such a design is secure.  

\n\n\t\t\t

the Consultant will coordinate with the STS the format of the documentation, supporting evidence and list of requirements to comply with. 

\n\t\t\t
\n\t\t\t

Least privilege principle enforcement

\n\t\t\t		\n\t\t\t

The system's components shall rely on the least privilege principle and run under such a limited privilege account under the OS rights model. 

\n\n\t\t\t

The documentation shall highlight each of the system's components required privilege level and considerations that force use of that level or access. 

\n\t\t\t
\n\t\t\t

Secrets and addresses

\n\t\t\t		\n\t\t\t

Secrets (passwords, private keys and certificates, connection strings) and addresses of external services shall be clearly delineated in configuration documentation and easily modifiable via automated scripts. 

\n\t\t\t
\n\t\t\t

Secure communication channels

\n\t\t\t		\n\t\t\t

All system's communication with external systems or users takes place over encrypted communication channels.  

\n\t\t\t
\n\t\t\t

No Username/Password authentication

\n\t\t\t		\n\t\t\t

The system shall rely on authentication via MPass for tax digital services. and other forms of user authentication for public acces information.  

\n\t\t\t
\n\t\t\t

Minimize personal information storage

\n\t\t\t		\n\t\t\t

The system shall minimize the amount of personally identifiable information stored. For example, there is no need to store a user's First and Second names since this will be provided after authentication by MPass. 

\n\n\t\t\t

The system shall comply with the relevant requirements related to personal data processing specified in GD 1123 from 14.12.2010 (http://lex.justice.md/md/337094/) 

\n\n\t\t\t

the Consultant shall coordinate with the STS the list of requirements to comply with. 

\n\t\t\t
\n\t\t\t

Secure against OWASP Top 10 vulnerabilities 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The system shall include security controls for all its components for at least OWASP Top 10 vulnerabilities. Refer https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project 

\n\t\t\t
\n\t\t\t

Health-check API  

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The system shall expose readiness and health-check API via a HTTP GET requests. The health-check shall check the health of as many system components as possible. In case of health check error, a human-readable error message shall be returned. 

\n\t\t\t
\n\t\t\t

Users’ roles management 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The users and their roles will be managed in MPass. The system shall retrieve the users’ roles from MPass.  

\n\t\t\t
\n\t\t\t

Session expiration 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The system shall include a session expiration mechanism when after a specific period of inactivity, the user is required to authenticate again. The period of inactivity shall be configurable and by default it is 15 mins. 

\n\t\t\t
\n\t\t\t

Input validation 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

All input data shall be validated on STS server side.  

\n\t\t\t
\n\t\t\t

User content 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

User content can be captured in text format only. The system shall forbid entry of special characters used for formatting and markup of special Web content. 

\n\n\t\t\t

Otherwise all UNICODE characters shall be possible to enter/view by system's components. 

\n\t\t\t
\n\t\t\t

Unauthorized access attempts 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

Unauthorized access attempts 

\n\n\t\t\t

When the system registers unauthorized access attempts it shall: 

\n\n\t\t\t
    \n\t\t\t\t
  • \n\t\t\t\t
      \n\t\t\t\t\t
    • log such attempts with at least ERROR level 
      • \n\t\t\t\t\t
    • provide users with a warning message that access is not authorized and that abuse will be investigated 
      • \n\t\t\t\t
    \n\t\t\t\t
    • \n\t\t\t
\n\t\t\t
\n\t\t\t

Data integrity 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

The Consultant will ensure data integrity by providing appropriate solution for prevention of unauthorized internal activities (for ex. deletion of authorizations records directly from database). 

\n\t\t\t
\n\n

Support and Warranty requirements  

\n\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\n\t\n
\n\t\t\t

Support 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

  During the warranty period the Consultant shall provide necessary technical assistance to the STS; 

\n\t\t\t
\n\t\t\t

Warranty 

\n\n\t\t\t

 

\n\t\t\t		\n\t\t\t

  During the warranty period the Consultant shall: 

\n\n\t\t\t
    \n\t\t\t\t
  • \n\t\t\t\t
      \n\t\t\t\t\t
    • fix all defects reported by the STS; 
      • \n\t\t\t\t\t
    • solve all incidents reported by the STS according to the agreed SLAs; 
      • \n\t\t\t\t
    \n\t\t\t\t
    • \n\t\t\t
\n\n\t\t\t

Note: The response and resolution time shall not exceed 60 minutes for non-critical errors and 15 minutes in case of critical errors. 

\n\n\t\t\t

The incidents shall be solved within 2 working days for non-critical errors and within 4 working hours for critical errors starting from escalation time. Hourly progress report will be provided for critical errors. 

\n\t\t\t
\n\n

 

\n\n

Annex 3.

\n\n

Relevant legal codes and regulations. 

\n\n
    \n\t
  1. Tax Code No. 1163-XIII of 24.04.1997
    2. \n
\n\n

https://www.fisc.md/Upload/LinkedPDF/Tax%20Code2.pdf

\n\n
    \n\t
  1. Law nr.71/2007 on registries - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=325732. 
    2. \n\t
  2. Law nr.1069/2000 on informatics - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=312902. 
    3. \n\t
  3. Law nr.467/2003 on informatics and state informational resources - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=313189. 
    4. \n\t
  4. Law nr.982/2000 on access to information - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=311759. 
    5. \n\t
  5. Law nr.133/2011 on personal data protection - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=340495. 
    6. \n\t
  6. Law nr.142/2018 on data exchange and interoperability - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=376762. 
    7. \n\t
  7. Government Decision nr.710/2011 on approving strategic Programme of technological modernization of government (e-Transformation) - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=340301; 
    8. \n\t
  8. Government Decision nr.1140/2017 on approving the Regulation  of the activity of the certification service providers in the field  application of the electronic signature - http://lex.justice.md/md/373494/. 
    9. \n\t
  9. Government Decision nr.1141/2017 on approving the Regulation on modality of application of the electronic signature on electronic documents by functionaries of legal persons governed by public law in the electronic document circulation - http://lex.justice.md/md/373495/.  
    10. \n\t
  10. Government Decision nr.1123/2010 on approving requirements regarding security of personal data during its processing by systems designed to work with personal data - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=337094. 
    11. \n\t
  11. Government Decision nr.128/2014 on Government single technological platform (MCloud) - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=351760. 
    12. \n\t
  12. Government Decision nr.1090/2013 on the governmental electronic service of authentication and access control (MPass) - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=351035. 
    13. \n\t
  13. Government Decision nr.405/2014 on the governmental electronic integrated service for digital signature (MSign) - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=353239. 
    14. \n\t
  14. Government Decision nr.708/2014 on the governmental electronic journaling service (MLog) - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=354589. 
    15. \n\t
  15. Government Decision nr.916/2007 on the concept of a Government Portal - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=324962. 
    16. \n\t
  16. Government Decision nr.330/28.05.2012 on development and administration of a single public services portal - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=343406. 
    17. \n\t
  17. Government Decision nr.701/2014 approving the Methodology of government open data publication - http://lex.justice.md/index.php?action=view&view=doc&lang=1&id=354534. 
    18. \n
"}]}