Project Management Birutė Markevičiūtė Joint Technical Secretariat Lead Partner Seminar 13 October 2008, Riga.

Slides:



Advertisements
Similar presentations
Legal Basis for Management and Control Systems in INTERREG III programmes BSR INTERREG III B Joint Secretariat Matthias Heinicke Seminar on Financial Management.
Advertisements

PRESAGE CTE FINANCIAL MANAGEMENT AND REPORTING PROCESURES
Launch of the ESPON 2013 Programme Procedures for Call for Proposals under Priorities 1-3.
Subsidy Contract Lead Partner seminar October 2008, Riga Arina Andreičika Managing Authority
Support and Inclusion of students with disabilities at higher education institutions in Montenegro – Procedure for collecting valid documentations.
Sustainable Energy Systems Overview of contractual obligations, procedures and practical matters KICK-OFF MEETING.
Partners and cross-border cooperation. Why a partnership? Address common challenges jointly (e.g. cross-border pollution) Jointly develop opportunities.
Financial Management and Auditing Monitoring by the JTS 3 rd round operations Rostock, Elise Oukka.
Info Day on New Calls and Partner Café Brussels, 8 September 2010 How to apply – Budget and Reporting.
Large Scale Projects Aleksejs Šaforostovs LSP Project Manager Joint Technical Secretariat.
ESPON 2013 Programme 3 rd Financial Managers Seminar Brussels 19 May 2010.
GRIP- IT Governance of Regionally Integrated Projects using Innovative Tools. (Structural Funds implementation in an integrated approach ) RFO – INTERREGIIIC.
Latvia–Lithuania Cross Border Cooperation Programme 2007–2013 WORKSHOP “How to prepare good application?” Joint Technical Secretariat 3rd.
TEMPUS IV- THIRD CALL FOR PROPOSALS Recommendation on how to make a good proposal TEMPUS INFORMATION DAYS Podgorica, MONTENEGRO 18 th December 2009.
Name, Surname, Position Event, Date, Place Managing a LIFE project.
Project Implementation Monika Balode Joint Technical Secretariat Lead Partner Seminar 16 October 2009, Šiauliai.
Part-financed by the European Union European Regional Development Fund and European Neighbourhood and Partnership Instrument Activity reporting Baltic.
CENTRAL EUROPE PROGRAMME SUCCESS FACTORS FOR PROJECT DEVELOPMENT: focus on finances Partner Search Forum Poznań, Poland 16 – 17 December 2008.
INTERREG IIIB PROGRAMME “ALPINE SPACE“ FORALPS kick-off meeting March 10th & 11th, 2005 Trento (I)
INTERREG IVA 2 Mers Seas Zeeën Crossborder Cooperation Programme Part-financed by the European Regional Development Fund (ERDF) Second level.
S L H C – P P Management Tools Kick-off Meeting April 8 th, 2008 Mar CAPEANS CERN This project has received funding from the European.
Green Partnerships Local Partnerships for Greener Cities and Regions 1st Reporting /Presage Other administrative issues Portugal, 8-10 July 2013.
Financial reporting Elise Oukka, Head of Finance, FMO Riga.
Project Closure Guidelines Riga, Legal framework 2 EC Regulation 1828/2006 § 8, 9: Explanatory plaque, billboard, emblem of the EU, reference to.
INTERREG IVA 2 Mers Seas Zeeën Crossborder Cooperation Programme Part-financed by the European Regional Development Fund (ERDF) Project monitoring.
Project implementation, changes, reporting Edmunds Sniķeris Joint Technical Secretariat 16 April 2012, Kuldīga.
APPLICATION FORM OF ROBINWOOD SUBPROJECT SECOND STEP 1. The short listed Local Beneficiaries work together to create international partnerships and prepare.
INTERREG IVA 2 Mers Seas Zeeën Crossborder Cooperation Programme Part-financed by the European Regional Development Fund (ERDF) Legal framework:
Part-financed by the European Union Project implementation and monitoring: What is good to know when applying? Joint Technical Secretariat Lead Applicant.
South East Europe Transnational Cooperation Programme Bologna, 15° June 2009 Kick-off meeting of project SARMa SEE Joint Technical Secretariat.
1 NOT LEGALLY BINDING Energy Info day FP7-ENERGY-2008-RUSSIA 13th December 2007 International Co-operation FP7 Energy Theme Energy EU-Russia Call European.
SARMa project development WP1 Project management and coordination SARMa internal handbook Alianta d.o.o., Ljubljana Split, 4-5 February 2010.
Fulfillment of conditions and contracting Līga Kalvāne Joint Technical Secretariat Lead Partner Seminar 15 October 2009, Siauliai.
Audit Authority and Auditors Group of “European Territorial Cooperation” Programmes for Lessons to be learnt from the INTERREG IIIB NWE Auditors.
Part-financed by the European Union What makes final financial reporting different from regular reporting? Rostislav Zatloukal Financial Manager, BSR INTERREG.
Green Partnerships Local Partnerships for Greener Cities and Regions Study visit and 3 rd Steering Committee meeting Freiburg, 14 – 18 October 2013.
Narrative reporting: good practices. Joint Technical Secretariat Seminar for Beneficiaries February 2012 Narva, Estonia.
HiLumi LHC is co-funded by the EU FP7 Capacities Programme, Grant Agreement Svet Stavrev (EU Projects Office, CERN) Administrative Manager 17.
Financial reporting Linda Wormö, MA Per Dahlström, MA 1st October,2015 Kuopio, Finland.
Part-financed by the European Union Partnership Joint Technical Secretariat Lead Applicant Seminar for 1st application round Hamburg, April 2008.
Project preparation workshop “Bringing a transnational project to life” Project idea “Challenges and chances from Climate Change for regional and local.
MED PROGRAMME – – 2nd call MED PROGRAMME – Lead Partner Seminar – 2nd call Marseille – 26 th May 2010 Gianluca Ferreri, Project Evaluation and Monitoring.
Start and break slide Kick-Off-Meeting April 1 st – 3 rd 2009 Large Conference Hall of Hotel Riga Riga/ Latvia host: Baltic Sea Region Programme
Northern Periphery Programme Advice to Lead partners for final reports Lead Partner Seminar 18th September 2013 Scandic Hotel, Skellefteå, Sweden.
Application procedure From theory to practice Dieter H. Henzler, Steinbeis-Transfercenter Cultural Resources Management, Berlin.
Grant contract and annexes Training for Auditors Estonia/Latvia/Russia ENPI CBC Programme Riga, Tartu, April 2012.
INTERREG IIIB PROGRAMME “ALPINE SPACE“ ALPTER Reporting obligations and Financial control.
Grant Application Form (Annex A) Grant Application Form (Annex A) 2nd Call for Proposals.
The Lead partner responsibilities Stefan Nyström, MA Per Dahlström, MA Lead Partner Seminar.
Technical Assistance Office 1 Contract, Reports and errors to avoid! GRANT AGREEMENT 2005 Comenius coordinators’ meeting, 17/10/2005 Maryline Fiaschi,
Technical Assistance Office TCP Projects 2005 Contractual and Financial Management Administrative and Financial Handbook Prepared by IA, 14/12/2001 SOCRATES.
DG Justice and Consumers Project Management Some points of attention JUST/2014/JCOO/AG/CRIM and JUST/2014/JCOO/AG/CIVI Kick-off meeting 26 January2016.
Information & Communication Irma Astrauskaitė Joint Technical Secretariat Lead Partner Seminar 13 October 2008, Riga.
S&E and BMW Regional Operational Programmes 14 – 20 Training for Local Authorities involved in DUCGS projects, 21st April 2016 REPORTING, DATA COLLECTION.
CENTRAL EUROPE PROGRAMME PROJECT DEVELOPMENT FINANCIAL ISSUES Project development seminar Prague, 1 st February 2010 Luca FERRARESE JTS CENTRAL.
INTERREG III B CADSES Neighbourhood Programme Administrative and Financial Aspects of Hydrocare Project Dr. Janka Strakova Project contact.
1 SOUTH BALTIC CROSS-BORDER CO-OPERATION PROGRAMME The Lead Beneficiary Principle by Małgorzat Skolmowska, Project Manager, JTS Lead Beneficiary.
Welcome. Contents: 1.Organization’s Policies & Procedure 2.Internal Controls 3.Manager’s Financial Role 4.Procurement Process 5.Monthly Financial Report.
Management of the Grant Agreement By Philippe Ruffio & Nathalie Hoste-Luxen Tempus project representatives’ meeting Brussels December 2011.
WP8 Project management Milan Gocić University of Niš
Establishing good working relations
Transnational training seminar for potential Lead Partners and Partners to INTEREGG IIIB-CADSES procedures for 3° call for proposal CADSES implementation.
REPORTING THROUGH THE EMS
GREECE-ALBANIA IPA CROSS BORDER COOPERATION PROGRAMME
Financial management of DBBT project
Kick-off meeting of the project UMBRELLA
Reporting 25 April 2018.
REPORTING OF ACTIVITIES
Helene Skikos DG Education and Culture
COGAIN Kick-Off 5-6 September, 2004 FINANCIAL GUIDELINES
Presentation transcript:

Project Management Birutė Markevičiūtė Joint Technical Secretariat Lead Partner Seminar 13 October 2008, Riga

Project start and end date 2 Project start date:  when first costs incurred and/or  date indicated in the Subsidy Contract  earliest – day after JMSC decision (17 September 2008) Project end date:  project start date + project duration in Application Form;  set in Subsidy Contract.

Basic principles of cooperation 3  Joint development;  Joint implementation;  Joint staffing;  Joint financing.

Lead Partner Principle 4 LP solely bears the overall financial and legal responsibility for the Project (see full list in Subsidy Contract and PM, 7.1.1) In practice, it means LP is responsible for:  signing Subsidy Contract;  representing Project;  setting effective management and financial control system;  ensuring that EU, Programme and national rules are followed;  coordination of activities with Project Partners;  achievement of quality Project outputs and results;  observance of spending plan;  reporting of Project progress via Progress Reports;  requesting payments and distributing to Project Partners;  ensuring audit trail on each Project Partner level.

Project Partners 5 Project Partners are responsible to implement their part of Project, and in particular they shall:  Assume responsibility in the event of any irregularity;  Repay the LP any amounts unduly paid;  Responsible for information and communication measures;  Keep available all documents related to the Project.

Operational Project Management 6 LP should appoint:  Project Coordinator: overall project implementation, coordination of different activities within Work Packages;  Financial Manager: overall financial control of the project. Requirements:  good knowledge of English and previous experience;  ability to work as a “uniting force” for a partnership;  clear coordination system between LP and external manager. Project Partners:  Local coordinators at institution.

Decision Making 7 Project (LP) should establish procedures for decision-making and coordination. Structures:  Strategic level (e.g. Steering Group);  Working level (e.g. working group, advisory group). Mechanisms:  Regular communication;  Meetings;  Rules of Procedure;  Delegation of representatives from each PP;  Protocols. Note: clear, not complicated structures.

Monitoring and Evaluation 8 Monitoring and evaluation system should be established (LP): Application Form = Project results Quality of management and co-ordination:  efficiency of procedures and resources;  progress towards achievement of the Project goals;  time plan;  financial plan and costs effectiveness. Quality of project outputs and results:  Who sets quality criteria;  Who is responsible to monitor the quality;  What are constraints/ risk factors. Source: Evaluation sheets; indicators; Interviews; Procedures; Reports; External evaluation; Technical specifications (procurement).

Monitoring and Evaluation 9 Remember! Some hints:  to plan the monitoring and reporting tasks and costs in the AF and Partnership Agreement;  to set a proper monitoring system early enough;  to make it clear to every PP in terms of tasks, deadlines, etc;  to keep discipline among the PPs to report timely.

Partnership Agreement 10 Lead Partner Managing Authority Subsidy Contract Application Form Project Partner Partner Declarations Partnership Agreement

11 As a minimum requirement the issues stipulated (see full list in Subsidy Contract and PM,4.4.4) should include: 1  PPs tasks and responsibilities;  payment procedures;  decision making;  reporting obligations and deadlines;  communication between PPs;  solving of disputes;  project changes;  ownership of the project outputs and results;  arrangements for audit trail. 2 Annex: table indicating responsibility for project activities per PPs and budget breakdown per Work Packages/ Budget Lines for each PP. Model shall be available on the website

Information to the JTS 12 Project (LP) should inform JTS:  on major Project events not later than 2 weeks before event (add info to the web page);  on changes of the Project Coordinator, Financial Manager or LP contact person immediately (via ; Progress Reports). Recommended: to send copy of project information and publicity materials as soon as available to JTS!

Project Finalization 13 Results should be:  Freely accessible to general public;  Further disseminated;  Durable: no substantial changes within 5 years: The project must not undergo any substantial change: affecting its nature or its implementation conditions or giving to a firm or a public body an undue advantage; and resulting either from change in the nature of ownership of an item of infrastructure or the cessation of a productive activity. Not fulfilling these conditions can imply a recovery of the funds unduly paid. How, when and by whom outputs and results produced by the project will be used after the project has ended? How they will be maintained?

Project Finalization 14 Durability of contacts:  LP should indicate contact person at least for 6 months after Project end;  LP should inform on changes of contact person for 5 years after Project end.

Project Finalization 15 LP and PPs should retain Project documents at least until 31 December 2021 (see full list in Subsidy Contract and PM,10.7) such as, e.g.:  Application Form;  Subsidy Contract, Partnership Agreement;  Project correspondence (financial and contractual);  Progress Reports and Partner Reports;  list of declared expenditure and supporting documentation;  proof of payment for each invoice;  public procurement documents and contracts;  proofs for delivery of services and goods: studies, brochures, newsletters, minutes of meetings, signed participant lists, travel tickets, etc.;  record of assets, physical availability of equipment purchased in the context of the project.

Lessons Learned: 16 Start as fast as possible: projects usually delay; Ensure sufficient human resources; Good Project Manager and Financial Manager – part of project success; Efficient communication with PPs; Clear division of activities and budget between PPs; Realistic time planning (e.g. public procurement procedures); In line with what is written in the Application Form; Reporting takes more time than planned; Contact JTS for advise

More information 17 Other useful links:  National authorities    Project management tools:  ‘Projects’, ‘Management Toolkit’  INTERACT guidelines: