GUIDANCE HOW TO IMPLEMENT THE PROJECT VIA THE ELECTRONIC MONITORING SYSTEM (PART I)

Transcription

1 Approved by the Head of the Managing Authority Sandis Cakuls on GUIDANCE HOW TO IMPLEMENT THE PROJECT VIA THE ELECTRONIC MONITORING SYSTEM (PART I) INTERREG V A LATVIA LITHUANIA PROGRAMME Version 2.0

2 Contents Abbreviations Introduction Registration in ems Decision on projects Fulfilling conditions Handing over the project to the Lead partner Contracting Supplementary information Handling project changes ems Mailbox

3 Abbreviations Electronic Monitoring System European Regional Development Fund Financial Control Interreg V-A Latvia Lithuania Programme Joint Secretariat Lead Partner Managing Authority Monitoring Committee Value Added Tax ems ERDF FC Programme JS LP MA MC VAT 3

4 1. Introduction Part I of the guidance presents practical information for implementation of the projects in the ems including fulfilling of project conditions, contracting and implementing project changes. When using this guidance, please refer to relevant sections in the Programme Manual to find out more about Programme requirements and procedures. The ems is a monitoring system developed by INTERACT which is used by the Programme for submission, approval, management and administration of projects. It is a web application, which can be accessed with recent versions of the most common browsers (e.g. Internet Explorer, Firefox, Chrome). The functionality of the ems follows the common standards of web applications for entering and submitting data. To gain access in ems every individual user has to register in the system through a link (please read section 2). LP has a wider set of functionalities than partner user rights. Project partners have access to their own reporting section as well as to the application form. The LP in turn has access to partner reporting, project reporting, change requests, supplementary information and the application form. In the ems each project has two main views: 1) Project i.e. the application form itself and project modification functionalities and 2) Reporting where reports can be created and accessed. Please remember that all project implementation stages contracting, reporting, submission of requests for project changes, as well as any other communication regarding project and Programme implementation shall be done via the ems. There are some crucial recommendations to remember when working in ems: Save the information by clicking Save button regularly or after any significant change (particularly before switching between sections in the application form or report), otherwise data will be lost or changes will not be saved. ems does not provide any warning or request of confirmation before leaving a section of the application form or before logging out. To ensure that data and information is not lost when entering it to the ems, it is recommended first to prepare text and only then to copy information into ems. Respect the length of input fields for entering data since they are limited (for each input field maximal number of symbols is indicated). Read carefully Programme Manual about requirements for processes described in this guidance. Use the latest version of the application form for project implementation (old versions are available in section History on the left side menu). Constant assistance of the JS employees is available in addition to this written guidance in case any questions about the ems or project implementation arise. 2. Registration in ems The ems can be accessed at the following link or on Programme webpage (banner on the main page). To get an access to the ems, user must register under the above mentioned link by filling in the registration form (Fig.1). 4

5 Fig.1 ems registration form The registration form must be filled in English language. The potential user will receive a confirmation notice to the indicated in the registration form. Only after confirmation is received, the access to the ems is assigned. In section User Account the password, personal data and the mail signature can be modified. Each ems user is responsible for all activities done with the username and must keep safe the username and password. In case the password is forgotten, it can be restored by clicking Forgot Password (Fig.2). Fig.2 Restoring password After that please follow instructions how to proceed further for restoring the password in the received automatic . If the username is forgotten, please contact the JS to get help (contacts of JS employees are available on the Programme webpage 3. Decision on projects The MA based on the MC decision on selection of projects for funding prepares decision on awarding or rejecting the ERDF funding and sends it to the project LP within 10 working days after the MC decision on selection of projects for funding was taken. After the MA decision is received: If project is approved the project state in the ems will be Approved. Please go to section 5 Handing over the application to the LP of this guidance. If project is approved under conditions the project state in the ems will be Cr_in_process. Please go to section 4 Fulfilling conditions of this guidance. If project is rejected - the project state in the ems will be Rejected (if project was rejected based on quality assessment results) or Ineligible (if project did not pass administrative and eligibility check). 5

6 The whole process from selection of projects till contracting is as follows: Fig.3 Process from project selection till contracting MC selects project for funding Project approved (Project state in ems: Approved) Project approved under conditions (Project state in ems: Cr_in_process) Project rejected (Project state in ems: Ineligible or Rejected) LP hands over application to the LP (Project state in ems: Startup) Section 4 Subsidy Contract is signed between MA and LP (Project state in ems: Contracted) Section 6 LP fulfills conditions (Project state in ems Cr_done) Section 3 MA finally approves the project (Project state in ems: Approved) LP fills in Supplementary information Section 5 4. Fulfilling conditions If project is approved under conditions, all conditions must be fulfilled before final decision on project approval is made by the MA. The LP is responsible for the fulfilment of conditions and updating of application in the ems. The JS responsible Project manager will contact the LP and using the form for implementation of conditions (Attachment No 1) will agree with the LP on necessary modifications of the application form in the ems. Once the JS responsible Project manager accepts information provided in the form for implementation of conditions, he/she informs the LP that the application form can be modified in the ems. 6

7 In the ems the fulfilment of conditions is presented in a form of modification request and the application has a status Cr_in_process. To proceed with implementation of conditions and modification of the application form, the LP shall do the following: 1) Open the application and the modification request 1 will be displayed (Fig.4). In the line Decision message conditions are mentioned that have to be fulfilled by the project. The line Decision State - Accepted (Modification request open for modifications) means that the application form can be modified. Fig.4 Modification request for fulfilment of conditions 2) Update application form according to set conditions and modifications agreed with the JS responsible Project manager in form for implementation of conditions. If during modification of the application you need to see the Modification request with conditions, please press button Modification request on the left side menu.!!! When implementing changes in the project budget, please update partner contribution in section Partner budget/define contribution (Fig. 5). Fig.5 Define contribution Please remember to click Save button to save the data entered, otherwise data will be lost! 3) When all necessary updates are made, please press button Check modification under section Application and Contract (Fig.6). 7

8 Fig.6 Check modification The system will ask for confirmation Yes/No. If check is successful, then notification will be displayed Prepared to submit. 4) Press button Submit modification (Fig.7). After that updated application will be sent to the JS for revision. Fig.7 Submit modification When the modified application is submitted to the JS, project state will be changed to Cr_done. After JS revision of the modified application: If application form is updated correctly and all conditions are fulfilled, the application form will be approved. LP will get an automatic message to the ems Mailbox and state of the project is changed to Approved. For further actions please read section Handing over the application to the LP. If still additional clarifications and modifications are needed, JS will hand back the application for further update to the LP. In this case, LP will get automatic message to the ems Mailbox that conditions are not considered as fulfilled and additional modifications have to be made. In the section Modification request the LP will see reasons for handing back the 8

9 modified application form and the LP will be able to update application form again. To modify and submit updated application form, please repeat steps 1-4 specified above. If the conditions have not been fulfilled within the set deadline, the project will be rejected. LP will get automatic message to the ems Mailbox. MA will prepare final decision stating whether project is approved or rejected and within 10 days after it is taken will send it to the project LP.!!! Please note that old versions of the application form will be available in section Project history on the left side menu (Fig. 8). Fig.8 Project history 5. Handing over the project to the Lead partner After the MA has taken a final decision on awarding the ERDF funding, the Lead applicant, i.e. person responsible for the preparation and submission of the application via ems, needs to hand the project over to the LP. This step is obligatory for each approved project, even if the Lead applicant and the LP is the same. When entering the application form, there will be a system notification in the upper right corner of the page that the project has to be handed over to the LP (Fig.9). Fig.9 Notification about handing over the application to the LP 9

10 Lead applicant shall enter section Lead Partner on the left side menu (Fig.10), Fig.10 Section Lead partner write the username of the prospective LP (the user needs to be already registered in the ems) and press button Declare as Lead partner (Fig.11). Fig.11 Hand over project If the prospective LP is the same as the Lead applicant, then the username of the Lead applicant shall be entered. A yes/no confirmation message will be shown. Only one username can be proposed. The proposed LP will receive a message in the ems Mailbox that he/she has been nominated as a prospective LP in a project. The JS shall approve proposed LP. If proposed LP user is rejected, the Lead applicant is informed by the JS contact person to propose a new one. When the LP is accepted by the JS, the project state will be changed to Startup. After that the Lead applicant loses access to the most of functionalities of the project. He/she will have only read-only access to the version of the application form valid till the moment of handover, will not have access to the reporting dashboard, and will not see supplementary information and project history or modification requests. 6. Contracting After the MA has taken a final decision on awarding the ERDF funding to the project, the MA/JS prepares draft of Subsidy contract and sends for the LP for pre-check via . After harmonisation the MA/JS will post two signed paper originals for the LP for signing. The LP shall 10

11 sign both originals and return one original to the MA. When the Subsidy contract is signed by the MA, the project state will be displayed as Contracted in the ems. This is a responsibility for the LP to upload scanned copy of the contract to the section Attachments so that it is accessible for all partnership. 7. Supplementary information When the project is contracted, the LP shall fill in section Supplementary information concerning project management, bank information, Financial Control (FC), user assignment and documents (Fig. 12). Supplementary information must be kept updated by the LP during project implementation. The LP has continuous access to this section. Fig.12 Supplementary information Information on project management staff here information on project manager, financial manager and communication manager is filled in. Depending on the project, one person may be responsible for one or more of these tasks. Bank information here bank account information for the LP shall be filled in English. To confirm the bank account information, the LP must fill in Confirmation of financial information (Annex No 2) and upload it to the bank information section (Fig.13). The file should be filled in electronically rather than by hand. The file should be named Bank_account_project_acronym_yymmdd. Confirmation of financial information must be uploaded at the latest when the LP submits the first Project report. 11

12 Fig.13 Bank information!!! All payments are made to the bank account declared in section Bank information.!!! If the bank account changes, the information must be changed immediately, JS must be informed and updated Confirmation of financial information shall be attached. The LP is responsible for the correctness of the information; any risks or costs related to payments going to wrong accounts due to incorrect information provided by the LP are borne solely by the LP. Information about FC here information about FC for Lithuanian partners has to be provided. Latvian project partners do not need to fill in this section. In Latvia FC system is centralised and its functions are performed by the Ministry of Environmental Protection and Regional Development of the Republic of Latvia, therefore there is no need to specify individual controllers. However, in Lithuania FC system is decentralised, thus each Lithuanian project partner is responsible for finding its own FC. The FC must be certified by the Ministry of the Interior of the Republic of Lithuania, therefore the information on the FC can only be given after the certification. Please note that filling in information here does not replace the certification process but is purely for information. More information on FC can be found here: User assignment here the LP has to assign user rights for each project partner so that they would be able to access the project application and reporting. Assignments should be done for other users of the LP, too. Every person from the project partner personnel who needs user rights of ems must first register in ems. To assign user to the project please enter its username in the input field New User and press Add (Fig.14). Fig.14 User assignment Any user can be removed by selecting the user and pressing Remove. Note, that user rights for FC are given by the MA. Lithuanian project partners must in the beginning of the project have their FC certified by the Ministry of the Interior of the Republic of Lithuania. To avoid delays with Lithuanian FC user rights assignment Lithuanian partners should 12

13 procure their FC and get certification for it from the Ministry of the Interior of the Republic of Lithuania in the very beginning of the project implementation. Documents in this section the LP for each project partner shall provide information about location of the archives for project documents and responsible person for them. As this information may in some cases be used several years after the closing the project it is advised to indicate a position and/or a general address of the partner institutions rather than of a concrete person. In such a case, fill in the work title of the relevant person instead of first and last name. The information about archives must be filled in at the latest when the LP submits the first project Progress report. Partnership agreement here the LP must upload Partnership agreement signed by all project partners. Signed Partnership agreement shall be uploaded in the ems before LP submits the first Project Report. Procurements above the threshold this section can be filled in about planned procurements in the project, if necessary. 8. Handling project changes During project implementation it may become evident that the work plan or project budget needs to be revised. Before implementing project changes in ems please read section 7.2 Project changes in the Programme Manual. There are two types of changes in the project: minor project changes. Minor changes have a minor impact on the project implementation, project outputs and/or results. Changes stated in points 1, 2, 3.1., 4 and 5.1. of the Table No 7 Description of minor changes, sub-section of the Programme Manual do not require prior approval from JS; they must be reported via progress reports. Changes stated in points 3.2., 3.3., 5.2. of the Table No 7 Description of minor changes, sub-section of the Programme Manual require prior approval from JS. major project changes. Major changes have a significant impact on the project implementation, project outputs and/or results. In general, major changes require prior approval by the MA/JS or the MC before they are implemented by the project. MA/JS takes decision on the project changes related to modification of project activities, budget, partnership and duration (changes stated in Table No 8 Description of major changes, sub-section of the Programme Manual). MC takes decision on changes which affect achievement of the Programme output and result indicators or would be an exceptional case on the Programme manual rules.!!! If major changes are needed, LP must inform the JS as soon as possible during the project implementation, but not later than one month before the project end. To get approval on minor changes (stated in points 3.2., 3.3., 5.2. of the Table No 7 Description of minor changes, sub-section of the Programme Manual), and major changes (stated in Table No 8 Description of major changes, sub-section of the Programme Manual), the LP has to prepare request for changes on behalf of the project partnership and submit it via the ems to the JS. The LP must involve all partners in the discussions in due time so that the needs of the whole partnership are reflected in the request for changes. 13

14 !!! Please note that while changes in the project are open reporting functionality will not be active. Each Partner and Project report will be linked to the application form which is valid one for prepared report. That is why it is recommended to implement changes in the ems only when there are no reports with state Report in progress. Procedure for handling project changes is following: 1) The LP shall press button Request Modification on the left side menu (Fig.15) under section Application and Contract. Fig. 15 Request Modification 2) In the displayed form Change request LP shall specify categories of changes, provide description and justification of changes (Fig.16) and attach supporting documents in section Attachment, if necessary. LP shall divide minor and major changes in two groups when both kind of changes are requested in one request for changes.!!! Before submission of request for changes in ems, please prepare changes according to template of the request for changes that is available on our website and harmonise it with JS responsible manager. Fig. 16 Request for changes form 3) When request for changes is prepared in ems, press Submit and request will be sent to the JS. 4) The JS responsible Project manager will assess the request for changes. Clarifications and/or corrections of the request for changes can be requested from the LP. 14

15 5) When the decision on requested changes is taken, the LP will receive message in the ems with decision and in case of changes approval the application form will be opened for modification by the LP. 6) The LP shall update application form according to approved changes stated in the decision.!!! When updating project budget in the application form, please update partner contribution in section Partner budget/define contribution (Fig.17). Fig. 17 Define contribution Please remember to click Save button to save the data entered, otherwise data will be lost! 7) When all necessary updates are made, the LP shall check modification by pressing button Check modification under section Application and Contract (Fig.18). Fig.18 Check modification The system will ask for confirmation Yes/No. If check is successful, then notification will be displayed Prepared to submit and the updated application form can be submitted to the JS by pressing button Submit modification (Fig.19). 15

16 Fig.19 Submit modification When the modified application is submitted to the JS, project state will be changed to Cr_done. 8) JS responsible Project manager will check updated application form. If the modifications are done in acceptable and justified manner, according to what had been approved in the decision, the modified application form will be approved. If something needs to be corrected or clarified the JS responsible Project manager will hand back application form to LP for further modifications. 9) When the updated application form is approved, the project state will be Contracted. New version of the application form will be the valid one and the old version of the application form will be archived. The old and new version can be found and compared by clicking Project history at the left side menu (Fig. 20). Fig.20 Project history 10) If project changes relate to content of Subsidy contract, amendments for the Subsidy contract will be prepared by the MA/JS and sent to LP by for harmonisation and then by post for signing. One copy of the amendments to the Subsidy contract (with MA internal signatures) needs to be returned back. 16

17 9. ems Mailbox ems allows users to exchange messages within the system. It supports standard mailing functions such as sending, forwarding and replying the mails. ems enables sending messages to multiple recipients as well as sorting and filtering messages based on different criteria (Fig.21). Fig.21 My Mailbox In section My Mailbox users will receive automatic messages informing about created pdf files, submitted applications and other messages about application process and project implementation. 17

18 Attachment No 1 Project number Project title Project acronym Lead Partner (LP) Implementation of conditions Conditions: Information from the LP (proposed modification/amendment of the text in specified section(s) of the application form): JS opinion: 18

19 Attachment No 2 Project number Project title Project acronym Confirmation of financial information Hereby I certify that my bank account details are as follows: Title of the organisation in English Bank account No Bank Bank code I acknowledge that information presented in this document is correct and I am aware that any risks or costs related to payments going to wrong accounts due to incorrect information provided are borne solely by the LP. Official title of the organisation in English Name and position of the authorised representative Signature Date of signature 19