|
Republic of Latvia
Cabinet
Regulation No. 597
Adopted 31 August 2021
|
Procedures for Supervising
Development Projects for State Information Systems
Issued pursuant to
Section 4, Paragraph two of the Law
on State Information Systems
1. The Regulation prescribes the procedures for supervising
development projects for State information systems.
2. The requirements included in the Regulation shall apply to
the activities of development projects for information systems
(hereinafter - the development activity) that are financed from
the policy instruments of the European Union and other foreign
financial assistance as well as from the State budget or that are
to be implemented within the scope of the maintenance budget of
the State information systems (hereinafter - the information
system).
3. The development activity, within the meaning of this
Regulation, is an activity that is related to the development of
the information and communication technological resources and
services required for one information system and its
operation.
4. The Regulation shall apply to those development activities
that introduce new information systems or affect the existing
technical architecture of information systems or the
technological structure of information and communication
infrastructure services, and also information and communication
technological resources of other authorities or the data exchange
with them.
5. The State information system manager who is responsible for
the implementation of the development activity (hereinafter - the
responsible authority) shall submit the following documents to
the Ministry of Environmental Protection and Regional Development
(hereinafter - the Ministry) for agreement in accordance with the
laws and regulations in the field of the preparation, drawing up,
storage, and circulation of electronic documents:
5.1. an application for the development activity (Annex 1)
that plans the development of the projects for information
systems shall be submitted before requesting financing for the
implementation of the development activity;
5.2. a description of the development activity (Annex 2) that
explains and attests compliance of the development activity with
the laws and regulations regarding technological and security
requirements for information and communication of State
authorities shall be submitted before commencing the development
activity;
5.3. a change request for the development activity (Annex 3),
applying for changes in the development activity;
5.4. a notice on the conclusion of the development activity
(Annex 4) shall be submitted within 10 working days after
completing the implementation of the development activity.
6. The Ministry is entitled to request an additional
information from the responsible authority on the document
referred to in Sub-paragraphs 5.2, 5.3, and 5.4 of this
Regulation if the information submitted in any of them is
inaccurate or incomplete.
7. Before commencing the implementation of the development
activity, a favourable opinion on the documents referred to in
Sub-paragraphs 5.2 and 5.3 of this Regulation shall be
required:
7.1. from the Ministry on compliance of the development
activity with the laws and regulations in the field of the
development of the information and communication technological
resources and services required for the State information systems
and their operation;
7.2. from the Ministry of Defence on the planned security
measures of the State information system;
7.3. from the Central Statistical Bureau on compliance of the
development activity with the laws and regulations in the field
of official statistics;
7.4. from the Data State Inspectorate on compliance of the
development activity with the laws and regulations in the field
of circulation of personal data;
7.5. from the Ministry of Culture on compliance of the
development activity with the laws and regulations in the field
of records and archives management;
7.6. from the Latvian Association of Local and Regional
Governments on the interactive technological solution selected
within the scope of the development activity if such information
system is being developed which supports processes interacting
with the processes at the local governments;
7.7. from other involved authorities the activities and
competence of which may be affected by the implementation of the
development activity.
8. During the assessment of the document referred to in
Sub-paragraph 5.2 or 5.3 of this Regulation, the Ministry has the
right to require that, in addition to the authorities involved in
providing an opinion referred to in Sub-paragraphs 7.2, 7.3, 7.4,
7.5, 7.6, and 7.7 of this Regulation, also other authorities the
activities and competence of which may be affected by the
implementation of the development activity provide an opinion on
the development activity.
9. The authorities involved in providing the opinion referred
to in Sub-paragraphs 7.2, 7.3, 7.4, 7.5, 7.6, and 7.7 of this
Regulation, and also authorities that have been sent a request to
provide an opinion in accordance with Paragraph 8 of this
Regulation shall provide an opinion on the document referred to
in Sub-paragraph 5.2 or 5.3 of this Regulation within 10 working
days from the date of its receipt.
10. The responsible authority shall submit the document
referred to in Sub-paragraphs 5.2 and 5.3 of this Regulation
simultaneously for the agreement provided for in Paragraphs 5 and
7 of this Regulation. Upon receipt, the responsible authority
shall compile and submit to the Ministry the opinions referred to
in Sub-paragraphs 7.2, 7.3, 7.4, 7.5, 7.6, and 7.7 of this
Regulation and, if required, also in Paragraph 8 in one document
set.
11. The Ministry shall provide an opinion on the documents
referred to in Paragraph 5 of this Regulation within the
following time periods:
11.1. on the application for the development activity, within
10 working days from the date of its receipt;
11.2. on the description of the development activity, taking
into account the opinions received from the authorities referred
to in Sub-paragraphs 7.2, 7.3, 7.4, 7.5, 7.6, and 7.7 and
Paragraph 8 of this Regulation, within 10 working days from the
date of its receipt;
11.3. on a change request for the development activity, taking
into account the opinions received from the authorities referred
to in Sub-paragraphs 7.2, 7.3, 7.4, 7.5, 7.6, and 7.7 and in
Paragraph 8 of this Regulation, within 10 working days from the
date of its receipt;
11.4. on the notice on the conclusion of the development
activity, within 10 working days from the date of its receipt or
it shall inform the responsible authority of the check to be
organised and referred to in Paragraph 15 of this Regulation;
11.5. on the conclusion review of the development activity
which has had a check organised, within 10 working days after
completion of the check.
12. The responsible authority shall implement the development
activity according to the documents agreed upon by the Ministry
and referred to in Sub-paragraphs 5.2 and 5.3 of this
Regulation.
13. If the Ministry provides an opinion with objections on any
of the documents referred to in Sub-paragraph 5.2, 5.3, or 5.4 of
this Regulation, the responsible authority shall remedy the
deficiencies indicated in the opinion within 10 working days from
the date of receipt of the opinion and submit the document
referred to in Sub-paragraph 5.2, 5.3, or 5.4 of this Regulation
on which the opinion with objections has been received for
repeated agreeing thereupon.
14. If any of the authorities referred to in Sub-paragraphs
7.2, 7.3, 7.4, 7.5, 7.6, and 7.7 and Paragraph 8 of this
Regulation provides an opinion on the development activity with
objections and, in the course of agreeing thereupon, no agreement
is made between the responsible authority and the opinion
provider, the Ministry shall decide on the further direction of
the development activity.
15. During any implementation phase of the development
activity or after completion of the development activity, any
authority involved in providing opinions referred to in Paragraph
7 of this Regulation may propose a sample check of the
development activity in order to verify its compliance with the
description or the change request for the development activity
which has been agreed upon by the Ministry.
16. The Ministry shall take the decision on the usefulness of
the check referred to in Paragraph 15 of this Regulation,
determining the authority which will perform the check and the
invited authorities referred to in Paragraphs 7 and 8 of this
Regulation as well as determining the scope and content of the
check.
17. The authority performing the check shall provide an
opinion to the Ministry, the responsible authority, and the
authorities invited to the check within 10 working days after the
date of performing the check referred to in Paragraph 16 of this
Regulation.
18. Cabinet Regulation No. 71 of 24 January 2006, Procedures
for Supervising Development Projects for State Information
Systems (Latvijas Vēstnesis, 2006, No. 17; 2009, No. 85;
2013, No. 209), is repealed.
19. The requirements included in the Regulation in relation to
an information system already designed from the development
activities financed by the State budget shall be applied from 1
January 2023.
Prime Minister A. K. Kariņš
Minister for Environmental
Protection
and Regional Development A. T. Plešs
Annex 1
Cabinet
Regulation No. 597
31 August 2021
Application for the Development
Activity of the State Information System
| 1. |
Authority |
|
Sector |
| |
Authority - information system manager |
|
|
| 2. |
Title of the development activity and
VIRSIS1 identifier of the information system to be
developed |
|
VIRSIS No. |
| |
Title
representing the content of the activity |
|
|
| 3. |
Short description of the
content |
|
|
| 3.1. |
Problem to solve (up to 1000 characters) |
|
|
| 3.2. |
Main
activities (up to 2000 characters) |
|
|
| 3.3. |
Changes - result (up to 1000 characters) |
|
|
| 4. |
Impact on other information
systems |
|
VIRSIS No. |
| 4.1. |
Information systems to be replaced, if any. Other information
systems significantly affected also indicated |
|
|
| 4.2. |
Information on the front-end interfaces to be significantly
changed as well as on shared components and services giving
their availability, as an indication, if possible |
|
|
| 5. |
Technological characteristics |
| |
Characteristics, openness,
interoperability, and compliance with the requirements of the
modern ICT architecture of the technological
solution/platform (up to 1000 characters) |
|
|
| 6. |
ICT infrastructure |
|
|
| 6.1. |
A
short description of the planned ICT infrastructure (up to
500 characters) |
|
VIRSIS No. |
| 6.2. |
Information on the planned service provider for the ICT
infrastructure and the most essential services planned for
use, indicating also their VIRSIS1 object
registration numbers |
|
|
| 7. |
Relation with laws and
regulations |
|
|
| |
Title
and status of a law or regulation, a link to the
corresponding law or regulation in www.likumi.lv, if the law
or regulation in force is modified, modifications or the
nature of the legislative initiative |
|
|
| 8. |
Justification, prerequisites, and
risks |
|
|
| 8.1. |
Justification and prerequisites (urgency and other
circumstances) (up to 1000 characters) |
|
|
| 8.2. |
Risks
that may affect the implementation of the development
activity (up to 1000 characters) |
|
Date |
| |
The preferable
deadline for putting into operation the designing of the
development activity: |
|
|
| 9. |
Indicative financing source and amount
(rounded up to thousand EUR) |
|
EUR |
| |
Financing source and indicative amount, rounded up to
thousand EUR |
|
|
| 10. |
Person filling in the application of
the development activity |
Date |
| |
Given name, surname, e-mail, and
telephone |
|
|
| |
1 Cabinet Regulation No. 523 of 5
November 2019, Regulations Regarding the Information System
of State Information Resources, Systems, and
Interoperability |
|
|
Abbreviations used in the form:
Development activity - the development activity of the State
information system
ICT - information and communication technologies
Information system - State information system
Minister for Environmental
Protection
and Regional Development A. T. Plešs
Annex 2
Cabinet
Regulation No. 597
31 August 2021
Description of the Development
Activity of the State Information System
| 1. |
Authority |
|
Sector |
|
| |
Authority - information system manager |
|
|
|
| |
|
|
|
|
| 2. |
Title of the development
activity |
|
VIRSIS No. |
|
| |
Title and VIRSIS1 identifier of the
information system to be developed, if given |
|
|
|
| |
|
|
|
|
| 3. |
Short description of the
content |
|
|
|
| 3.1. |
Problem to solve (up to 2000 characters) |
|
|
|
| 3.2. |
Main activities (up to 2000 characters for each
activity, numbering them by sectioning in separate rows and
providing the indicative financing for each of the
activities) |
|
|
|
| 3.3. |
Result to be achieved (up to 2000
characters) |
|
|
|
| 4. |
Impact on other
information systems2 |
|
VIRSIS No. |
|
| 4.1. |
Information systems to be replaced, if any (also
indicating information systems significantly affected by
changes in interfaces). Each information system significantly
affected is given one row. To indicate VIRSIS1
identifier |
|
|
|
| 4.2. |
Data that will be received or transmitted to
other information systems. Data is grouped into rows of
information systems, indicating VIRSIS1
identifiers of the relevant information system |
|
|
|
| 4.3. |
Information on the shared components and services
to be developed (up to 500 characters for each by sectioning
in separate rows. To indicate VIRSIS1 identifier
for components, if given) |
|
|
|
| 4.a |
Institutions with which the development activity
needs to be agreed upon (Paragraph 7 of Cabinet Regulation
No. _________ of _____________________3) |
|
|
|
| |
|
|
|
|
| 5. |
Technological
characteristics |
|
Fulfilment of
requirements |
|
| 5.1. |
Cybersecurity. The person responsible for
security management of information technologies, description
of security provision and planned security checks, category
of security of the information system in accordance with
Cabinet Regulation No. 4424 (up to 2000
characters) |
|
|
|
| 5.1.c |
Attestation of compliance of the information system with the
requirements of Cabinet Regulation No. 4424 |
|
|
|
| 5.1.j |
Justification (not more than 500 characters) for deviations,
if any |
|
|
|
| |
|
|
|
|
| 5.2. |
Accessibility. Description of the
accessibility solution (up to 500 characters) |
|
|
|
| 5.2.c |
Attestation of compliance of the information system with the
requirements of Cabinet Regulation No. 4455 |
|
|
|
| 5.2.j. |
Justification (not more than 500 characters) for deviations,
if any |
|
|
|
| |
|
|
|
|
| 5.3. |
Opening of data. Description of the set of
data to be opened/published (up to 500 characters) |
|
|
|
| 5.3.c1 |
Compliance
with Sub-paragraph 1.1 of Annex to Cabinet Regulation No. 764
(publishing of generally accessible data)6 |
|
|
|
| 5.3.c2 |
Compliance
with Sub-paragraphs 1.2 and 1.3 of Annex to Cabinet
Regulation No. 764 (automation and
regularity)6 |
|
|
|
| 5.3.j |
Justification (not more than 500 characters) for deviations,
if any |
|
|
|
| |
|
|
|
|
| 5.4. |
Circulation of data. A short description
of the storing of data and essential front-end interfaces (up
to 1000 characters) |
|
|
|
| 5.4.c1 |
Compliance
with Sub-paragraph 2.2 of Annex to Cabinet Regulation No. 764
(the use of integrators)6 |
|
|
|
| 5.4.c2 |
Compliance
with Sub-paragraph 2.3 of Annex to Cabinet Regulation No. 764
(ensuring the data accessibility)6 |
|
|
|
| 5.4.c3 |
Compliance
with Sub-paragraph 2.4 of Annex to Cabinet Regulation No. 764
(API and their publishing)6 |
|
|
|
| 5.4.j |
Justification (not more than 500 characters) for deviations,
if any |
|
|
|
| |
|
|
|
|
| 5.5. |
Identification. Description of the
identification solution for information system users (up to
1000 characters) |
|
|
|
| 5.5.c1 |
Compliance
with Sub-paragraphs 3.1 and 3.2 of Annex to Cabinet
Regulation No. 764 (the use of a national and qualified
eID)6 |
|
|
|
| 5.5.c2 |
Compliance
with Sub-paragraph 3.3 of Annex to Cabinet Regulation No. 764
(the use of SRDA ULM)6 |
|
|
|
| 5.5.c3 |
Compliance
with Sub-paragraph 3.4 of Annex to Cabinet Regulation No. 764
(access to cross-border services)6 |
|
|
|
| 5.5.j |
Justification (not more than 500 characters) for deviations,
if any |
|
|
|
| |
|
|
|
|
| 5.6. |
Description of the technological
architecture (up to 2000 characters), including aspects
of sharing, specifically listing shared services and
components to be used |
|
|
|
| 5.6.c1 |
Compliance
with Sub-paragraphs 4.1 and 4.2 of Annex to Cabinet
Regulation No. 764 (the use of EU and LV
solutions)6 |
|
|
|
| 5.6.c2 |
Compliance
with Sub-paragraph 4.5 of Annex to Cabinet Regulation No. 764
(the open code)6 |
|
|
|
| 5.6.c3 |
Compliance
with Sub-paragraph 4.3 of Annex to Cabinet Regulation No. 764
(unlimited economic rights of an author)6 |
|
|
|
| 5.6.c4 |
Compliance
with Sub-paragraph 4.4 of Annex to Cabinet Regulation No. 764
(shared use of components and services)6 |
|
|
|
| 5.6.c5 |
Compliance
with Sub-paragraph 4.5 of Annex to Cabinet Regulation No. 764
(guidelines for the technological
architecture)6 |
|
|
|
| 5.6.j |
Justification (not more
than 500 characters) for not subjecting to requirements and
for deviations, if any |
|
|
|
| |
|
|
|
|
| 6. |
ICT infrastructure |
|
|
|
| 6.1. |
A short description of the planned ICT
infrastructure (up to 500 characters) |
|
VIRSIS No. |
|
| 6.2. |
Information on the planned service provider of
the ICT infrastructure and the most essential services
planned for use, also indicating VIRSIS1 object
registration numbers if they are already identifiable and
registered in VIRSIS1 (essential services divided
in separate rows) |
|
|
|
| |
|
|
Date |
|
| 6.3. |
Agreement of the ICT infrastructure on the
technological architecture by the service provider (in
accordance with Sub-paragraph 4.6 of Annex to Cabinet
Regulation No. 764)5 and the planned
infrastructure services |
|
|
|
| |
|
|
|
|
| 7. |
Justification,
prerequisites, risks, and planned deadlines |
|
|
|
| 7.1. |
Justification, including relation with the laws
and regulations already adopted or planned, indicating their
status and link to www.likumi.lv (up to 1000 characters) |
|
|
|
| 7.2. |
Prerequisites that determine initiating the
development activity and the risks that may affect its
initiation or successful implementation (up to 1000
characters) |
|
Date |
|
| 7.3. |
Commencement of the planned development activity |
|
|
|
| 7.4. |
Completion
of the planned development activity - putting the solution
into operation |
|
|
|
| 8. |
Financing source and
amount |
|
EUR |
|
| |
Financing source and the planned amount (rounded
up to thousand EUR) |
|
|
|
| |
|
|
|
|
| 9. |
Person drawing up the
description of the development activity |
|
Date |
|
| |
Given name, surname,
e-mail, and telephone |
|
|
|
| |
|
|
|
|
| |
1 Cabinet Regulation No. 523 of
5 November 2019, Regulations Regarding the Information System
of State Information Resources, Systems, and
Interoperability |
|
|
|
| |
2 Information systems of State
administration institutions (including local
governments) |
|
|
|
| |
3 Paragraph 7 of Cabinet
Regulation No. ________ of _________________ |
|
|
|
| |
4 Cabinet Regulation No. 442 of
28 July 2015, Procedures for the Ensuring Conformity of
Information and Communication Technologies Systems to Minimum
Security Requirements |
|
|
|
| |
5 Cabinet Regulation No. 445 of
14 July 2020, Procedures for the Institutions Posting
Information on the Internet |
|
|
|
| |
6 Cabinet Regulation No. 764 of
11 October 2005, General Technical Requirements of State
Information Systems |
|
|
|
| |
|
|
|
|
Abbreviations used in the form:
API - Application Programming Interface
Development activity - the development activity of the State
information system
eID - electronic identification
EU - European Union
ICT - information and communication technologies
Information system - State information system
LV - Latvia
ULM - Unified Login Module
SRDA - State Regional Development Agency
c - compliance
ch - change
j - justification
a - agreement
Minister for Environmental
Protection
and Regional Development A. T. Plešs
Annex 3
Cabinet
Regulation No. 597
31 August 2021
Change Request for the Development
Activity of the State Information Systems
| 1. |
Authority |
|
Sector |
|
| |
Authority - information system manager |
|
|
|
| |
|
|
|
|
| 2. |
Title of the development
activity |
|
VIRSIS No. |
|
| |
Title and VIRSIS1 identifier of the
information system to be developed, if given |
|
|
|
| |
|
|
|
|
| 3. |
Short description of the
content of the development activity |
|
|
|
| 3.1. |
Problem to solve (up to 2000 characters) |
|
|
|
| 3.2. |
Main activities (up to 2000 characters for each
activity, numbering them by sectioning in separate rows and
providing the indicative financing for each of the
activities) |
|
|
|
| 3.3. |
Result to be achieved (up to 2000
characters) |
|
|
|
| 3.ch |
Attestation "not changed" or a short description
and justification for changes (up to 500 characters) |
|
|
|
| 4. |
Impact on other
information systems2 |
|
VIRSIS No. |
|
| 4.1. |
Information systems to be replaced, if any (also
indicating information systems significantly affected by
changes in interfaces). Each information system significantly
affected is given one row. To indicate VIRSIS1
identifier |
|
|
|
| 4.2. |
Data that will be received or transmitted to
other information systems. Data is grouped into rows of
information systems indicating VIRSIS1 identifiers
of the relevant information system |
|
|
|
| 4.3. |
Information on the shared components and services
to be developed (up to 500 characters for each by sectioning
in separate rows. To indicate VIRSIS1 identifier
for components, if given) |
|
|
|
| 4.ch |
Attestation "not changed" or a short description
and justification for changes (up to 500 characters) |
|
|
|
| 4.a |
Institutions with which the changes need to be
agreed upon |
|
|
|
| |
|
|
|
|
| 5. |
Technological
characteristics |
|
Fulfilment of
requirements |
|
| 5.1. |
Cybersecurity. The person responsible for
security management of information technologies, description
of security provision and planned security checks, category
of security of the information system in accordance with
Cabinet Regulation No. 4424 (up to 2000
characters) |
|
|
|
| 5.1.c |
Attestation of compliance of the information system with the
requirements of Cabinet Regulation No. 4423 |
|
|
|
| 5.1.j |
Justification (not more than 500 characters) for deviations,
if any |
|
|
|
| |
|
|
|
|
| 5.2. |
Accessibility. Description of the
accessibility solution (up to 500 characters) |
|
|
|
| 5.2.c |
Attestation of compliance of the information system with the
requirements of Cabinet Regulation No. 4454 |
|
|
|
| 5.2.j. |
Justification (not more than 500 characters) for deviations,
if any |
|
|
|
| |
|
|
|
|
| 5.3. |
Opening of data. Description of the set of
data to be opened/published (up to 500 characters) |
|
|
|
| 5.3.c1 |
Compliance
with Sub-paragraph 1.1 of Annex to Cabinet Regulation No. 764
(publishing of generally accessible data)5 |
|
|
|
| 5.3.c2 |
Compliance
with Sub-paragraphs 1.2 and 1.3 of Annex to Cabinet
Regulation No. 764 (automation and
regularity)6 |
|
|
|
| 5.3.j |
Justification (not more
than 500 characters) for deviations, if any |
|
|
|
| |
|
|
|
|
| 5.4. |
Circulation of data. A short description
of the storing of data and essential front-end interfaces (up
to 1000 characters) |
|
|
|
| 5.4.c1 |
Compliance
with Sub-paragraph 2.2 of Annex to Cabinet Regulation No. 764
(the use of integrators)5 |
|
|
|
| 5.4.c2 |
Compliance
with Sub-paragraph 2.3 of Annex to Cabinet Regulation No. 764
(ensuring the data accessibility)5 |
|
|
|
| 5.4.c3 |
Compliance
with Sub-paragraph 2.4 of Annex to Cabinet Regulation No. 764
(API and their publishing)5 |
|
|
|
| 5.4.j |
Justification (not more 500 characters) for deviations, if
any |
|
|
|
| |
|
|
|
|
| 5.5. |
Identification. A description of the
identification solution for information system users (up to
1000 characters) |
|
|
|
| 5.5.c1 |
Compliance
with Sub-paragraphs 3.1 and 3.2 of Annex to Cabinet
Regulation No. 764 (the use of a national and qualified
eID)5 |
|
|
|
| 5.5.c2 |
Compliance
with Sub-paragraph 3.3 of Annex to Cabinet Regulation No. 764
(the use of SRDA ULM)5 |
|
|
|
| 5.5.c3 |
Compliance
with Sub-paragraph 3.4 of Annex to Cabinet Regulation No. 764
(an access to cross-border services)5 |
|
|
|
| 5.5.j |
Justification (not more than 500 characters) for deviations,
if any |
|
|
|
| |
|
|
|
|
| 5.6. |
Description of the technological
architecture (up to 2000 characters), including aspects
of sharing, specifically listing shared services and
components to be used |
|
|
|
| 5.6.c1 |
Compliance
with Sub-paragraphs 4.1 and 4.2 of Annex to Cabinet
Regulation No. 764 (the use of EU and LV
solutions)5 |
|
|
|
| 5.6.c2 |
Compliance
with Sub-paragraph 4.5 of Annex to Cabinet Regulation No. 764
(the open code)5 |
|
|
|
| 5.6.c3 |
Compliance
with Sub-paragraph 4.3 of Annex to Cabinet Regulation No. 764
(unlimited economic rights of an author)5 |
|
|
|
| 5.6.c4 |
Compliance
with Sub-paragraph 4.4 of Annex to Cabinet Regulation No. 764
(shared use of components and services)5 |
|
|
|
| 5.6.c5 |
Compliance
with Sub-paragraph 4.5 of Annex to Cabinet Regulation No. 764
(guidelines for the technological
architecture)5 |
|
|
|
| 5.6.j |
Justification (not more
than 500 characters) for not subjecting to requirements and
for deviations, if any |
|
|
|
| 5.ch |
Statement "not changed"
or a short description and justification for changes (up to
500 characters) |
|
|
|
| |
|
|
|
|
| 6. |
ICT infrastructure |
|
|
|
| 6.1. |
A short description of the planned ICT
infrastructure (up to 500 characters) |
|
VIRSIS No. |
|
| 6.2. |
Information on the planned service provider of
the ICT infrastructure and the most essential services
planned for use, also indicating VIRSIS1 object
registration numbers if they are already identifiable and
registered in VIRSIS1 (essential services divided
in separate rows) |
|
|
|
| |
|
|
Date |
|
| 6.3. |
Agreement of the ICT infrastructure on the
technological architecture by the service provider (in
accordance with Sub-paragraph 4.6 of Annex to Cabinet
Regulation No. 764)4 and the planned
infrastructure services |
|
|
|
| 6.ch |
Attestation "not
changed" or a short description and justification for changes
(up to 500 characters) |
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| 7. |
Justification,
prerequisites, risks, and planned deadlines |
|
|
|
| 7.1. |
Justification, including relation with laws and
regulations already adopted or planned, indicating their
status and link to www.likumi.lv (up to 1000 characters) |
|
|
|
| 7.2. |
Prerequisites that determine initiating the
development activity and the risks that may affect its
initiation or successful implementation (up to 1000
characters) |
|
Date |
|
| 7.3. |
Commencement of the planned development activity |
|
|
|
| 7.4. |
Completion
of the planned development activity - putting the solution
into operation |
|
|
|
| 7.ch |
Attestation "not
changed" or a short description and justification for changes
(up to 500 characters) |
|
|
|
| 8. |
Financing source and
amount |
|
EUR |
|
| |
Financing source and the planned amount (rounded
up to thousand EUR) |
|
|
|
| |
|
|
|
|
| 8.ch |
Statement "not changed"
or a short description and justification for changes (up to
500 characters) |
|
|
|
| 9. |
Person drawing up the
description of the development activity |
|
Date |
|
| |
Given name, surname,
e-mail, and telephone |
|
|
|
| |
|
|
|
|
| |
1 Cabinet Regulation No. 523 of
5 November 2019, Regulations Regarding the Information System
of State Information Resources, Systems, and
Interoperability |
|
|
|
| |
2 Information systems of State
administration institutions (including local
governments) |
|
|
|
| |
3 Cabinet Regulation No. 442 of
28 July 2015, Procedures for the Ensuring Conformity of
Information and Communication Technologies Systems to Minimum
Security Requirements |
|
|
|
| |
4 Cabinet Regulation No. 445 of
14 July 2020, Procedures for the Institutions Posting
Information on the Internet |
|
|
|
| |
5 Cabinet Regulation No. 764 of
11 October 2005, General Technical Requirements of State
Information Systems |
|
|
|
| |
|
|
|
|
Abbreviations used in the form:
API - Application Programming Interface
Development activity - the development activity of the State
information system
eID - electronic identification
EU - European Union
ICT - information and communication technologies
Information system - State information system
LV - Latvia
ULM - Unified Login Module
SRDA - State Regional Development Agency
c - compliance
ch - change
j - justification
a - agreement
Minister for Environmental
Protection
and Regional Development A. T. Plešs
Annex 4
Cabinet
Regulation No. 597
31 August 2021
Notice on the Closure of the
Development Activity of the State Information System
| 1. |
Authority |
|
Sector |
|
| |
Authority - information system manager |
|
|
|
| 2. |
Title of the development activity
and VIRSIS1 object registration numbers of the
information system to be developed |
|
VIRSIS No. |
|
| |
Objects developed within the development activity
(including information system and its components registered
in VIRSIS1) indicated in separate rows, also
indicating given VIRSIS1 object registration
numbers |
|
|
|
| 3. |
Reference to the
current version for the description of the development
activity |
|
Date |
|
| |
Development activity
implemented according to the description version submitted to
MoEPRD: |
|
|
|
| |
|
|
|
|
| 4. |
Person drawing up the
notice on the closure of the development activity
(given name, surname, e-mail, and telephone) |
Date |
|
| |
|
|
|
|
| |
1 Cabinet Regulation No. 523 of
5 November 2019, Regulations Regarding the Information System
of State Information Resources, Systems, and
Interoperability |
|
|
|
Abbreviations used in the form:
Development activity - the development activity of the State
information system
Information system - State information system
MoEPRD - the Ministry of Environmental Protection and Regional
Development
Minister for Environmental
Protection
and Regional Development A. T. Plešs
Translation © 2022 Valsts valodas centrs (State
Language Centre)
