The plugin was found but not activated by eaist 2.0. What is the EAIST supplier portal?

1. Work on the topic “Procurement planning in EAIST 2.0” in the subsystems “Purchase Plan” and “Plan Schedule”

1.1. Theoretical part

1.1.1. Study of the regulatory framework for planning, in accordance with Article 16-23 of Law No. 44-FZ of 04/06/2013.

1.1.2. Detailed analysis and analysis of RF Government resolutions No. 1043 of November 21, 2013 on the form of the procurement plan and No. 554 of June 5, 2015 on the form of the schedule plan.

1.1.3. Review and analysis of Resolution No. 555 of 06/05/2015 on the justification for the choice of procurement object, procurement method and NMC.

1.2. Practical part

1.2.1. Formation of procurement objects.

1.2.2. Creation and publication of the Procurement Plan.

1.2.3. Amendments to the Procurement Plan.

1.2.4. Detailing of procurement objects.

1.2.5. Entering and adjusting the calculation of the NMC.

1.2.6. Formation of Lots.

1.2.7. Formation of Lots for joint procurement.

1.2.8. Formation of an Aggregating Lot.

1.2.9. Planning and placing purchases from a single supplier.

1.2.10. Creation and publication of the Schedule.

1.2.11. Making changes to the schedule.

2. Work on the topic "Organization of procedures in EAIST 2.0" in the "Tendering" subsystem

2.1. Theoretical part

2.1.1. Features of competitive procedures and timing of placement of each stage

2.1.2. Features of an electronic auction and terms for posting protocols

2.1.3. Features of the request for quotations and timing of the protocol placement

2.1.4. Features of the request for proposals, variations and timing of posting an extract from the protocol and the final protocol

2.2. Practical part

2.2.1. Attaching documentation to Lots.

2.2.2. Editing auction attributes.

2.2.3. Preparing the Procedure for publication.

2.2.4. Agreement on the Procedure before publication.

2.2.5. Formation of an electronic register of applications.

2.2.6. Formation of procurement protocols (Open tender, request for quotations, request for proposals).

2.2.8. Viewing procurement protocols (Electronic auction).

2.2.9. Formation and processing of requests for clarification.

3. Work on the topic "Contract" in the subsystems "Contracts" and "Electronic store"

3.1. Theoretical part

3.1.1. Studying the basics of the formation and execution of contracts in accordance with the requirements of Articles 34 and 94 of Law No. 44-FZ.

3.2.2. A detailed analysis of the features of changing and terminating contracts based on the requirements of Article 95 of Law No. 44-FZ.

3.1.3. Features of small volume purchases in accordance with the requirements of paragraphs 4 and 5 of Article 93 of Law No. 44-FZ.

3.2. Practical part

3.2.1. Preparation for contract registration.

3.2.2. Entering information about the execution of the contract.

3.2.3. Entering information about contract termination.

3.2.4. Making changes to a registered contract.

3.2.5. Work in the electronic store EAIST 2.0.

Schedule

Hours 20 20 20
Form of study full-time full-time full-time
date 13.02.2020 02.03.2020 16.04.2020
Time 09:30-12:30 12:30-18:30 09:30-15:30
Days Intensive Intensive Intensive

The supplier portal is a subsystem of the Unified Automated Information System of Moscow Bidding (EAIST), on which suppliers can post their proposals for government customers. In the article we will analyze what opportunities this system provides to the supplier, and we will consider step by step how registration with EAIST takes place.

What is the EAIST supplier portal

The supplier portal of the EAIST system (the abbreviation stands for Unified Automated Bidding Information System) on the website www.zakupki.mos.ru was created by the Moscow Government to automate the procurement procedure for small volumes of Moscow government customers and to attract small and medium-sized businesses to such procurements. This service is also called the EAIST electronic store.

The operating procedure of the portal is regulated by the Regulations for maintaining the supplier portal, approved by Order of the Moscow Department of Competition Policy dated September 25, 2014 No. 70-01-149/14.

  1. 1. Unified Automated Information System of Trading 2.0 State budgetary institution of the city of Moscow “Service Center 44” REMINDER for the transition of state managers of budget funds and subordinate organizations to EAIST 2.0
  2. 2. EAIST 2.0 connection schedule News from June 24, 2015
  3. 3. Connection schedule PRINCIPLE OF CONSTRUCTION OF SCHEDULE 1886 DEPARTMENT OF HEALTH OF THE CITY OF MOSCOW 34445 Registration period in EAIST 2.0 Period of formation of Procurement Plans and Schedules Period of disconnection from EAIST 1.0 DATES OF TRANSITION TO EAIST version 2 Active users from 01.09.20 14 to 03/01/2015 Quantity lots for 2014  1 week – GRBS, which published less than 300 lots in 2014  2 weeks – GRBS, published from 300 to 1000 lots in 2014  3 weeks – GRBS, published from 1000 to 3000 lots in 2014  more than 4 weeks - GRBS, which published more than 3000 lots in 2014. GRBS CONNECTION SCHEDULE ON EAIST 2.0 PUBLISHED ON THE EAIST START PAGE OF THE CURRENT VERSION EAIST 2.0
  4. 4. EAIST 2.0 News dated June 24, 2015 Order to provide access
  5. 5. Instructions for registering EAIST 2.0 Forum address: http://erkt.tender.mos.ru/forum/Default.aspx?g=topics&f=111 Forum
  6. 6. Instructions for registering EAIST 2.0 Forum Forum address: http://erkt.tender.mos.ru/forum/Default.aspx?g=topics&f=111
  7. 7. Order to provide access to EAIST 2.0 Prepares and issues an order to provide access to information resources to EAIST 2.0 to authorized employees CHIEF MANAGER OF BUDGET FUNDS SUBSIDIARY INSTITUTIONS (if any) ORDER TEMPLATE FOR PROVIDING ACCESS TO EAIST 2.0 PUBLISHED ON THE START PAGE EAIST CURRENT VERSION
  8. 8. EAIST 2.0 ALL ACTIONS ARE CARRIED OUT IN EAIST 2.0 The procedure for submitting an application for registration in the EAIST 2.0 System is carried out independently by users and consists of three consecutive steps. The transition to the next step is carried out by clicking on the “Next” button, provided that all required fields of the form are filled out. Otherwise, if not all required fields are filled in, unfilled fields with hints are highlighted. User registration
  9. 9. Registration of an EAIST 2.0 user Open Google Chrome Go to eaist.mos.ru IN ACCORDANCE WITH THE SCHEDULE! 1 2 Click on the active link “Submit an application for registration” 3
  10. 10. User registration EAIST 2.0 Fill in the necessary user data. 4 ACCORDING TO SCHEDULE! It is necessary to indicate the following information about the user:  “Last name” (required)  “First name” (required)  “Patronymic” (if necessary)  “SNILS number” (required)  Check the “No middle name” (if necessary)  “ Place of work”, select from the directory (required)  “Division” (if necessary)  “Position” (if necessary)  “Telephone” (if necessary)  “Email” (required)  Check the “Manager” checkbox (if necessary)
  11. 11. User registration EAIST 2.0 Fill in the necessary user data. 5 ACCORDING TO SCHEDULE! The “Place of work” field is filled in by selecting from the appropriate directory; to do this, click on the “Not specified” link. The “Select Organization” window will open.
  12. 12. User registration EAIST 2.0 Filling out information about the organization 6 IN ACCORDANCE WITH THE SCHEDULE! In order to quickly find the required organization, you can use the inclusion search. To do this, you need to search by key. For example, by short name, indicating part of the name of the desired organization. You need to select the desired entry with the left mouse button and click
  13. 13. User registration EAIST 2.0 Completion of filling in general data 7 IN ACCORDANCE WITH THE SCHEDULE! After filling out all the fields, the transition to the next stage is carried out by clicking on the “Next” button, provided that all required fields of the form are completed. Otherwise, if not all required fields are filled in, they are highlighted along with the tooltips.
  14. 14. User registration EAIST 2.0 Definition of powers8 IN ACCORDANCE WITH THE SCHEDULE! The “Step 2. Determination of authority” form will open. At this step, by default, the first available organization is automatically set to the organization - place of work specified in step 1 without the possibility of deleting it. You must complete the following fields on the Permission Definition tab. In this case, the fields “Validity from”, “Validity to”, “Document date” are entered automatically and are available for editing. “Name” (if necessary) “Number” (if necessary) “Validity period from” (required) “Validity period until” (required) “Document date” (required)
  15. 15. User registration EAIST 2.0 Definition of powers9 IN ACCORDANCE WITH THE SCHEDULE! The “Step 2. Determination of authority” form will open. At this step, by default, the first available organization is automatically set to the organization - place of work specified in step 1 without the possibility of deleting it.
  16. 16. User registration EAIST 2.0 Definition of powers 10 IN ACCORDANCE WITH THE SCHEDULE! Next, it is necessary to indicate the powers that the future user will perform in the System. Indication and selection of powers occurs by pressing a button.
  17. 17. User registration EAIST 2.0 Definition of powers 11 IN ACCORDANCE WITH THE SCHEDULE! The “Selection of powers” ​​window opens, in which the user is offered a complete description of the powers available in the System. To change the number of visible records on a page, you must use the “Display by” tool located under the table.
  18. 18. User registration EAIST 2.0 Definition of powers 12 IN ACCORDANCE WITH THE SCHEDULE! You need to mark the required entries with the checkboxes and click on the button
  19. 19. User registration EAIST 2.0 Definition of powers 13 IN ACCORDANCE WITH THE SCHEDULE! After selecting the necessary powers, a table is generated where you need to check the degree of privileges: “I exercise these powers for my organization” and/or “I exercise these powers for subordinates”
  20. 20. User registration EAIST 2.0 Definition of powers 14 IN ACCORDANCE WITH THE SCHEDULE! If you need to delete any of the selected permissions, click the button next to the corresponding role
  21. 21. User registration EAIST 2.0 Definition of powers 15 IN ACCORDANCE WITH THE SCHEDULE! If you need to indicate other available organizations other than the organization-place of work, you should use the button At the added organization you should also specify information on the basis document, select the necessary powers that will be exercised within the organization, and set the degree of privileges next to each role .
  22. 22. User registration EAIST 2.0 Definition of powers 16 IN ACCORDANCE WITH THE SCHEDULE! If you need to delete any of the available organizations other than the organization where you work, you should click on the button next to the corresponding organization. When you delete an available organization, all permissions and base document data specified for it are deleted.
  23. 23. User registration EAIST 2.0 Definition of powers 17 IN ACCORDANCE WITH THE SCHEDULE! The transition to the next step is carried out by clicking on the “Next” button, provided that all required fields of the step 2 form are completed. Otherwise, empty fields with hints are highlighted.
  24. 24. User registration EAIST 2.0 Definition of powers 18 IN ACCORDANCE WITH THE SCHEDULE! The “Step 3. View and Confirm” form will open, which is a complete list of data filled out in the two previous forms of Step 1 and Step 2 without the ability to edit (view only). At this stage of registration itself, it is possible to return to step 2 and then to step 1 to edit the data (button). When you click on, the procedure for generating a registration application is completed.
  25. 25. User registration EAIST 2.0 Definition of powers 19 IN ACCORDANCE WITH THE SCHEDULE! The user registration application has been successfully created. You will be informed about this in a corresponding message.
  26. 26. User registration EAIST 2.0 Receive a letter to the E-mail specified during registration with a link to the credential confirmation form IN ACCORDANCE WITH THE SCHEDULE! 20
  27. 27. User registration EAIST 2.0 After successful user registration, you can log in using an electronic signature. There is no need to register a certificate - user information is verified using SNILS Follow the link to confirm credentials and register (generate) a password Enter your password twice or generate it using the registration system 21 22
  28. 31. Information kiosk EAIST Organizational support for users with the participation of the developer. By appointment by email [email protected] Address: Makarenko street, 4, building 1, room. 202, 206 Work schedule: - Monday to Friday from 9:00 to 21:00 - weekends - according to a separate schedule. Webinars on work in EAIST 2.0 Weekly on Fridays from 11:00 to 12:00 http://gbusc44.mos.ru/napravlenie/webinars/index.php Platform for communication on issues of work in EAIST 2.0 on the social network: http:// vk.com/eaist_official

Dear colleagues! In order to simplify the registration of your contracts in the EAIST system, I am sending you the procedure (indicating the information to be entered) when working in the EAIST. 1. Log in to the subsystem "Register of Government Contracts 2.0". 2. Click the “create GC project” tab. 3. Next, fill out the “windows” in accordance with the attached table. All information is entered in accordance with paper media. 4. Click the "Check registration" tab. 5. If there are no errors, click the “Register” tab. 6. Check the information about the contract in the generated CONTRACT CARD. If the information is correct, click “sign”. In this case, the digital signature must be inserted into the computer. 7. After signing, the agreement should go to your personal account on the Official website zakupki.gov.ru (OOS). 8. To publish a contract on the OOS, you need to log into your personal account, the “contract register” tab. 9. Next to the corresponding agreement, click ▼ and select “submit for publication” from the drop-down list. 10. After publication, a contract registry number will be assigned. 11. After publication on the OOS, within 24 hours, the status of the agreement in EAIST should change to “registered”. If the status has not changed, you must contact the technical support service of EAIST or OOS to solve this problem. The procedure for filling out information about the contract when registering with EAIST. Tab name Name of the "window" Input information GENERAL INFORMATION Contract number Enter the contract number Registry number of the contract Not entered (assigned automatically after registration) Subject of the contract We look at the subject of the contract on paper Placement method Select from the drop-down tree Reason for placement Select from the drop-down tree in accordance with the information in the contract Civil Code type Select from the drop-down tree Registry number according to 807-PP Not filled in Date of conclusion Date that appears on the contract (or set it yourself) Validity period (execution + payment) In accordance with the contract Performance period In accordance with the contract Currency of the contract Ruble Target program Non-program part (other expenses) State customer Select your institution from the drop-down tree Payer under the contract Select from the drop-down tree (you can click “he is the payer” if you are also the payer). Compare the details, if they are correct - check the box, if incorrect - call EAIST, make a request for changes. Supplier/performer Select from the drop-down tree. (or enter the supplier’s tax identification number, it will be found automatically). Select the correct details in accordance with the contract and check the box. Payment form In accordance with the agreement Advance payment View the agreement (if there is no advance payment, “the checkbox must be removed”) Guarantee obligations under the government contract View the agreement. (if they are not required - "the checkbox must be removed" Click the "Save" button, after which more tabs will appear that need to be filled in WARRANTY OBLIGATIONS in accordance with the agreement SUBJECT OF THE CONTRACT specification Click the "add" tab KPGZ code Selected from the drop-down tree Name according to OKDPP Assigned automatically, in accordance with the selected KPGZ code. (Check its correctness. If it does not correspond, look for another KPGZ code) Name according to OKP (only for delivery) Filled in only in case of delivery of goods Type of units of measurement Select from the drop-down tree ("economic units", for example) Units of measurement Select ("service " for example) Quantity If the service is 1, If ​​the delivery is in accordance with the technical specifications Amount In accordance with the agreement (without VAT) VAT In accordance with the agreement Currency Ruble Amount with VAT In accordance with the agreement Delivery schedule Click the "add" tab Delivery date In accordance with the agreement Recipient Your institution Place of delivery Address and name of your institution Quantity If the service is 1, If ​​the delivery is in accordance with the terms of reference "save" Financing Click the "add" tab Source of financing Extra-budgetary funds (Funds from budgetary institutions for subsidies) Personal account number Your personal account number KBK Your KBKS Amount Amount of the contract without VAT VAT rate In accordance with the agreement Amount with VAT Amount of the contract Planned date payment The furthest date of validity of the contract "save" DOCUMENTS (the contract is attached) Click the "add" tab Document type "Contract" Document number Contract number Document name "Contract" or "Agreement" Document date Date of conclusion of the contract Document file A scanned contract with all attachments is attached (the date is set before scanning on paper) "save"

The government of Moscow
MOSCOW DEPARTMENT FOR COMPETITION POLICY

ORDER

On approval of the Procedure for providing access to information resources of the Unified Automated Information System of Bidding of the City of Moscow (EAIST) and on the invalidation of orders of the Moscow City Department for Competition Policy


Document with changes made:
.
____________________________________________________________________


In accordance with clause 1.3 of the Regulations on the procurement system of the city of Moscow, approved in order to regulate the procedure for interaction with executive authorities, institutions and organizations when performing procedures for providing and terminating access to information resources of the Unified Automated Information System of Bidding of the City of Moscow (EAIST) for authorized employees

I order:

1. Approve the Procedure for providing access to information resources of the Unified Automated Information System for Bidding of the City of Moscow (EAIST) in accordance with the appendix to this order.

2. To recognize as invalid:

2.1. Order of the Moscow City Department for Competition Policy dated April 17, 2013 N 70-01-62/13 “On approval of the Regulations for maintaining the Register of persons signing information on budgetary obligations in the EAIST”.

2.2. Order of the Moscow City Department for Competition Policy dated November 13, 2014 N 70-01-183/14 “On approval of the Procedure for providing access to information resources of the Unified Automated Information System of Bidding of the City of Moscow (EAIST).

2.3. Order of the Moscow City Department for Competition Policy dated August 17, 2015 N 70-01-90/15 "On amendments to the order of the Moscow City Department for Competition Policy dated November 13, 2014 N 70-01-183/14".

2.4. Order of the Moscow City Department for Competition Policy dated October 13, 2015 N 70-01-121/15 "On amendments to the order of the Moscow City Department for Competition Policy dated April 17, 2013 N 70-01-62/13".

2.5. Order of the Moscow City Department for Competition Policy dated September 12, 2016 N 70-01-112/16 "On amendments to the order of the Moscow City Department for Competition Policy dated November 13, 2014 N 70-01-183/14".

3. The state budgetary institution of the city of Moscow "Service Center 44" ensures the implementation of government work to provide access to EAIST information resources.

4. The second hyphen of clause 3.1, the fourth hyphen of clause 3.3 of the appendix to this order comes into force on January 1, 2018.

5. Entrust control over the implementation of this order to the Deputy Head of the Department for Competition Policy A.L. Danilov.

Acting Manager
Moscow City Department
on competition policy
V.N.Zhukov

Application. The procedure for providing access to information resources of the Unified Automated Information System for Bidding of the City of Moscow (EAIST)

Application
to the order of the Moscow City Department
on competition policy
dated July 13, 2017 N 70-01-88/17

1. General Provisions

1.1. The procedure for providing access to information resources of the Unified Automated Information System for Bidding of the City of Moscow (EAIST) (hereinafter referred to as the Procedure) determines the rules and procedure for performing procedures for providing and terminating access to information resources of EAIST for employees of Organizations.

1.2. The main objective of the Procedure is to ensure the functioning, types and forms of interaction of the Moscow City Department for Competition Policy with users of the Unified Automated Information System of Bidding of the City of Moscow.

2. Terms and definitions

2.1. Department - Moscow City Department for Competition Policy.

2.2. GBU "SC 44" - State budgetary institution of the city of Moscow, created and registered in the manner prescribed by law, in accordance with the order of the Government of Moscow dated June 13, 2013 N 296-RP "On the creation of the State budgetary institution of the city of Moscow "Service Center 44", performing work in accordance with the State assignment.

2.3. EAIST (System) - Unified automated information system for bidding in the city of Moscow in the field of procurement of goods, works, services to meet state and municipal needs.

2.4. Incident - a failure recorded in the operation of EAIST by the Technical Support Service.

2.5. NPSI is a section of the System intended for storing regulatory and reference information.

2.6. Organization - a legal entity interested in access to the EAIST.

2.7. User is an input or viewing operator registered in the System.

2.8. Order - the Customer’s administrative document on the appointment of an information entry operator, the generation of information and documents in EAIST, prepared in accordance with the form in accordance with Appendix 1 to this Procedure.

2.9. Authority (roles) - a set of access rights to EAIST accounting objects.

3. Providing access to work in the System

3.1. Registration of new users is carried out independently, by each user, by sending an application electronically using the functionality of the System according to the instructions posted in the “NPSI” block in the “Instructions” section.

Access is provided if:

- the current Order on the appointment of an information entry operator, prepared in accordance with Appendix 1 to this Procedure;

- a document confirming completion of certification for work at EAIST in the manner established by the Moscow City Department for Competition Policy.

Providing access to EAIST information resources for employees of supervisory, regulatory and other bodies who are not employees of contract services is carried out based on the results of consideration of an official application to the Department.

3.2. An application for registration in the EAIST is considered by an authorized employee of the State Budgetary Institution "SC 44" within 3 (three) working days from the date of submission of the application in electronic form. Based on the results of the review, a decision is made to provide access to EAIST information resources, or the application is rejected, indicating the appropriate comments to eliminate the comments.

3.3. An application for registration with the EAIST is rejected for the following reasons:

- there is no Order for the appointment of an information entry operator;

- the full name of the Organization is not indicated in the title of the order, date, number of the Order;

- the Order on the appointment of an information entry operator does not contain the seal of the Organization and the signature of the head of the Organization;

- there is no document confirming certification for work at EAIST;

- there are no documents or duly certified copies of documents specified in clause 3.1 of this Procedure.

3.4. The application is rejected with appropriate comments to eliminate the comments in the System through the functionality and the text of the refusal is automatically sent to the user’s email address.

3.5. Access is granted to a specific list of roles. The roles that fix the composition of information resources and the amount of information available to the User are determined on the basis of the Order, in accordance with the List and description of EAIST roles by organization category (Appendix 2 to this Procedure).

Access is granted to the following categories of Organizations:

Table 1.

Table 1

Reduction

Authorized body for organizing and implementing first-level procurement (Moscow City Department for Competition Policy)

Authorized body (institution) for organizing and implementing second-level procurement

Chief manager of budget funds/executive authority exercising management and control functions

Control departments of the city of Moscow (Main Control Department of the City of Moscow, Chamber of Control and Accounts of Moscow, Office of the Federal Antimonopoly Service for the City of Moscow, etc.), law enforcement agencies

Customers of the city of Moscow

3.6. The User's authority is granted for a period not exceeding 15 (fifteen) months. The organization must monitor the duration of powers.

3.7. Changing information about the User is carried out by sending an application through the System.

3.8. An application for changing personal data and for temporary transfer of authority is considered by the Department within 2 (two) working days.

3.9. To carry out legally significant actions and operations when working with EAIST information resources, the confirmation of which requires the presence of an electronic signature of the User authorized for these actions and operations, the Organization is obliged to provide Users with electronic signature keys.

At the same time, when carrying out other legally significant actions that do not require the use of an electronic signature, the User bears personal responsibility for failure to comply with the requirements of legislation in the field of procurement, goods, works, services, as well as for entering incomplete and/or false information.

3.10. Credentials (login, password) to access the System can only be used by those Users who were provided with the specified credentials during registration.

4. Termination of user access to EAIST

4.1. Termination of access to EAIST information resources is carried out in the following cases: upon dismissal, transfer to another place of work of an employee, expiration of the term of office, liquidation of the Organization, or by decision of the head of the Organization.

In such cases, the Organization sends a corresponding appeal to the State Budgetary Institution "SC 44" through the electronic document management system of the Moscow Government or in paper form through the "one window" service of the Department for Coordination of Work with Documents of the Department, as well as via e-mail to the following address: [email protected].

4.2. By decision of the Department, access to EAIST information resources may be terminated in the following cases:

4.2.1. Identification of gross and repeated violations of regulatory legal acts and (or) methodological requirements for the procurement procedure by customers in the city of Moscow.

4.2.2. Systematic violation of deadlines for posting information on procurement and (or) contracts in the EAIST (more than 50% of the volume of information to be posted per month).

4.2.3. Detection of violations of the rules for using accounts established by clauses 3.9 and 3.10 of this Procedure.

4.2.4. Receipts of requests from the Moscow executive authority for control in the field of procurement related to the facts of repeated refusals to approve changes under the same contract.

4.2.5. Carrying out actions in the Unified Information System in the field of procurement directly related to procurement and (or) contracts, without using the EAIST functionality.

4.2.6. Compromise or suspected compromise (loss, transfer or other dissemination of information) of credentials, as well as the User’s electronic signature key.

4.2.7. Exemption from filling a position in the state civil service, state civil servant of the city of Moscow or dismissal of an employee in accordance with the Labor legislation of the Russian Federation, who were granted access to the EAIST.

4.2.8. Expiration of the User account.

4.2.9. Lack of information about the use of the User's account for three months, except for cases of using an account with read access.

4.2.10. The User receives a negative result based on the results of certification at EAIST.

4.2.11. Identification of unlawful use of EAIST information resources.

4.2.12. Committing actions in EAIST (user errors) that led to the initiation of an incident.

4.2.13. Contacting the Technical Support Service with a question, the answer to which is included in the methodological material.

4.2.14. Sending requests to the Technical Support Service for questions of similar content.

4.2.16. Appeals from the User present at the meeting of the Mobile Mobile Group on questions the answers to which were provided at the meeting of the specified group.
(Clause 4.2 as amended, put into effect by order of the Tender Committee of the city of Moscow dated May 25, 2018 N 70-01-68/18.

5. User Responsibility

5.1. Users bear personal responsibility for entering incomplete and/or incorrect information into the EAIST, administrative liability for failure to comply with legal requirements in the field of procurement of goods, works, and services.

Appendix 1. Standard form of administrative document on the appointment of input operators

Annex 1
to Order

ORDER

"____"_____________ 20___

About the appointment of employees

(indicate the name of the Organization)

responsible for entering information, generating information and documents in the Unified Automated Information System for Bidding of the City of Moscow (EAIST)

In accordance with Federal Laws of April 5, 2013 N 44-FZ "On the contract system in the field of procurement of goods, works, services to meet state and municipal needs", dated April 6, 2011 N 63-FZ "On electronic signature" and dated July 18, 2011 N 223-FZ "On the procurement of goods, works, services by certain types of legal entities" by resolution of the Moscow Government dated February 24, 2012 N 67-PP "On the procurement system of the city of Moscow", in order to provide access to I order the information resources of the Unified Automated Information System of Bidding of the City of Moscow (EAIST):

1. Assign State Customer organizations responsible for entering information into the EAIST for the period from "___"___________ 20__ to "___"___________ 20__ with the following powers (roles):

Job title

List of roles

Privilege level

1.1. Assign responsibility for entering information into the EAIST for the period from "___"_________ 20__ to "___"___________ 20__ with the following powers (roles) of the organization of the Authorized Body of the second level for the subordinate network (specify GRBS organization):

________________

The clause requires inclusion in the Order in the event that employees of the 2nd level Authorized Body need access to the subordinate network of the GRBS, who is not an employee of the GRBS.

Job title

List of roles

Privilege level

2. Establish that:

2.1. The employees specified in paragraph 1 of this Order are responsible for the completeness and accuracy of the data entered into the EAIST, generated information and documents; for maintaining the confidentiality of ES private keys and other key information, compliance with the rules of operation of EAIST and ES tools.

________________

3. Please note that the employees specified in paragraph 1 of this Order:

3.1. Are employees

(indicate the name of the Organization)

3.2. Completed training in working with EAIST information resources: _____________________ (if available, document details are indicated).

3.3. They have the right to enter information into the EAIST with confirmation of data entry using an electronic signature, are provided with an electronic signature key certificate, and have been trained in the rules of working with electronic signatures.

________________

Except for employees who are only given a read role.

(indicate position, full name)

4.1. Establish control over the validity periods of electronic signature key certificates.

4.2. Ensure the continuity of entering information, generating information and documents in EAIST, including through the timely production of a qualified electronic signature key certificate in accordance with the identification data of the owner of the qualified certificate, taking into account the validity period of the key certificate.

________________

Except for employees who are only given a read role.

4.3. Ensure that changes are made to this order one month before the expiration of the employees’ term of office.

5. Control over the implementation of this order is entrusted to

(indicate the full name of the official)

Name
manager positions

according to staffing schedule

(signature)

________________
With the exception of cases where the order is issued on an official form for the executive authority of the city of Moscow.

Appendix 2. List and description of EAIST roles by organization category

Appendix 2
to Order

Table 1.

Table 1

Choice of powers for the Authorized body (institution) of the second level

List of roles

Role Description

Privilege level

Planning - reading

44-FZ /223-FZ

"for subordinates"

Placement - reading

I am a customer operator who has the authority to view information about the procurement publication process without making changes to them within the framework of 44-FZ / 223-FZ

"for subordinates"

Authorized person of the 2nd level

I am an operator of a second-level Authorized Body and/or GRBS, publishing second-level procurement within the framework of 44-FZ / 223-FZ

"for subordinates"

Table 2.

table 2

Choice of powers for the State Customer

List of roles

Role Description

Privilege level

Planning - View and Record

I am a customer operator who generates information about the planning process within the framework of 44-FZ / 223-FZ

"for my organization"

Planning - reading

I am a customer operator with authority to view information about the planning process within the framework of 44-FZ / 223-FZ

"for my organization"

Placement - viewing and recording 44-FZ / 223-FZ

"for my organization"

I am a user authorized to view and change information about contracts within the framework of 44-FZ / 223-FZ

"for my organization"

________________

*Numbering corresponds to the original. - Database manufacturer's note.

Register of contracts - reading

I am a user authorized to view information about contracts within the framework of 44-FZ / 223-FZ

"for my organization"

Head of Civil Protection

I am an official of the customer who has the right to sign documents within the framework of 44-FZ / 223-FZ

"for my organization"

Procurement Regulations

An employee responsible for the formation and registration of the Procurement Regulations within the framework of 223-FZ.

"for my organization"

I am a specialist who generates information about procurement protocols, including entering information about the voting of commission members before implementing the personal voting mechanism within the framework of 44-FZ

"for my organization"

Formation of commissions

I am a specialist responsible for the formation of orders and commissions within the framework of 44-FZ / 223-FZ

"for my organization"

Member of the commission

I am a member of the procurement evaluation committee; in the future - personally voting for his decisions in the process of forming protocols using an electronic signature within the framework of 44-FZ / 223-FZ

"for my organization"

Chairman of the Commission

I am the chairman of the procurement evaluation committee; in the future - approving protocols within the framework of 44-FZ / 223-FZ

"for my organization"

Table 3.

Table 3

Selecting powers for the GRBS

List of roles "for your organization" Placement - viewing and recording 44-FZ GRBS employee responsible for the RG GRBS 44-FZ

GRBS employee approving the PoZ

I am an employee of the GRBS, coordinating the Procurement Regulations for the subsequent placement of a subordinate network within the framework of 223-FZ

"for my organization"
And
"for subordinates"

Formation of commissions

"for my organization"

Member of the commission

I am a member of the procurement evaluation committee; in the future - personally voting for his decisions in the process of forming protocols using an electronic signature

"for my organization"
and/or
"for subordinates"

Chairman of the Commission

I am the chairman of the procurement evaluation committee; in the future - approving protocols

"for my organization"
and/or
"for subordinates"

Secretary of the commission (evaluation)

I am an official of the customer who has the right to sign documents

"for my organization"
and/or
"for subordinates"

Table 4.

Table 4

Typical set of roles for a government customer

Planning - View and Record

Contract register - viewing and recording

Placement - viewing and recording

Secretary of the commission (evaluation)

Contract register - viewing and recording

Formation of commissions

Secretary of the commission (evaluation)

Member of the commission

Formation of commissions

Member of the commission

Role PoZ Reading




Revision of the document taking into account
changes and additions prepared
JSC "Kodeks"



Have questions?

Report a typo

Text that will be sent to our editors: