FInest Future Internet enabled optimisation of transport and logistics networks
|
|
- Patricia Shepherd
- 8 years ago
- Views:
Transcription
1 FInest Future Internet enabled optimisation of transport and logistics networks D11.1 Project Management Plan Project Acronym Project Title FInest Project Number Workpackage Lead Beneficiary Future Internet enabled optimisation of transport and logistics networks #WP11 Project Management Kuehne + Nagel Management AG Editor(s) Dr. J. Rod Franklin KN Contributors(s) Dr. Michael Stollberg SAP Dr. Andreas Metzger UDE Reviewer Dr. Fabiana Fournier IBM Reviewer <name> <organisation> Dissemination Level Public Contractual Delivery Date 30 June 2011 Actual Delivery Date Version 1.0 The research leading to these results has received funding from the European Community's Seventh Framework Programme [FP7/ ] under grant agreement no
2 THIS PAGE INTENTIONALLY LEFT BLANK The research leading to these results has received funding from the European Community's Seventh Framework Programme [FP7/ ] under grant agreement no
3 Abstract This document provides an overview of the methodologies and tools that the FInest team is employing to manage the project. The document is being submitted as specified in the FInest Description of Work (DoW) as part of deliverable D11.1, Project Management Plan. The focus of this document is to describe the approaches being taken in the project to manage the various work packages, share and store documents, communicate amongst consortium members, control the quality of project deliverables and mitigate risks associated with the project deliverables. Examples, screen shots and other aids are included to assist the reader in better understanding the approaches being used by the project team to ensure that it complies with the work documented in its DoW and that it delivers the project outcomes described in that document. D11.1 Project Management Plan V1.0 Page 3 of 26
4 Document History Version Date Comments V First draft V Second draft after first comment V Third draft after comments V Fourth draft after comments V1.0 dd-mm-yyyy Final version D11.1 Project Management Plan V1.0 Page 4 of 26
5 Table of Contents Abstract... 3 Document History... 4 Table of Contents... 5 List of Figures... 7 List of Tables... 7 Acronyms Introduction Project Management Plan Project organization Project Coordinator (PC) Technical Coordinator (TC) FI PPP Alignment Coordinator (AC) Logistics Stakeholder Coordinator (LSC) Work Package Leaders (WPL) Deliverable Leader (DL) Project collaboration tool Project reporting processes Project communications Project website Project newsletters Project templates Project quality control Project risk management D11.1 Project Management Plan V1.0 Page 5 of 26
6 8. Summary D11.1 Project Management Plan V1.0 Page 6 of 26
7 List of Figures Figure 1 High level overview of FInest project Figure 2 - FInest project management structure Figure 3 - FInest eroom dashboard Figure 4 FInest contact list Figure 5 FInest project calendar Figure 6 Example work package team calendar Figure 7 Example work package team contact list Figure 8 Example work package project task plan Figure 9 Project deliverable reporting template Figure 10 Project effort reporting template Figure 11 Mock-up of project website Figure 13 Risk Management Process List of Tables Table 1 FInest coordination call/meeting list Table 2 Project risk register D11.1 Project Management Plan V1.0 Page 7 of 26
8 Acronyms Acronym AC AFKL ARC DoW DL FI PPP IBM KN LSC MRTK PC PMB SAP TC UDE WPL Explanation FI PPP Alignment Coordinator Koninkluke Luchtvaart Maatschappijnv Arcelik AS Description of Work Deliverable Lead Future Internet Public Private Partnership IBM Israel Science and Technology Ltd Kuehne + Nagel Management AG Logistics Stakeholder Coordinator Norsk Marinteknisk Forskningsinstitutt AS Project Coordinator Project Management Board SAP AG Technical Coordinator Universität Duisburg-Essen Work Package Leader D11.1 Project Management Plan V1.0 Page 8 of 26
9 1. Introduction Deliverable D11.1, Project Management Plan, focuses on providing the European Commission with an initial overview of how the FInest team proposes to manage and control the execution of the FInest project. Included in this deliverable are overviews of: The initial project management plan, Tools employed to manage the project, Procedures utilized to manage the project, Communications processes for the consortium, Quality control process for the project, and Risk management process. The FInest team is employing a standard project management approach based on documented timelines, regular communications, active follow up, and formal quality control and risk mitigation processes. To support its project management approach, the FInest team has elected to use EMC s eroom, hosted by SINTEF/MARINTEK. This collaboration platform provides the team with facilities for sharing and managing of documents, managing work package tasks, tracking progress against task deliverables, scheduling meetings and discussions, managing lists and generally ensuring that the distributed project team can pro-actively collaborate to meet project requirements as stated in the FInest DoW. This collaboration environment is private to FInest team. Procedures and templates have been created by the team to ensure that regular progress reports are made by deliverable leads, that actual resource consumption is tracked against plan and that any deviations from plan are quickly surfaced and appropriate risk mitigation actions taken. To facilitate on-going reporting activities and project team work, lists have been created and conference calling facilities established. In addition, a project website is being developed to provide not only internal communications capabilities for the FInest team, but to support the team s dissemination and exploitation activities. Finally, formal quality control and risk management processes have been established so that project deliverables meet the operational criteria established for them and so that any deviations from plan are properly addressed. The FInest team believes that by employing project management approach summarized above and discussed in more detail in the following sections, it will be able to successfully deliver to the European Commission those deliverables described in its DoW. 2. Project Management Plan The FInest project has been developed and planned as a set of integrated work packages coordinated to deliver progressive results in four six month cycles. The first six month cycle focuses on the delivery of initial domain requirements for the project s collaboration services. The second six month cycle refines these requirements and uses D11.1 Project Management Plan V1.0 Page 9 of 26
10 them to create initial solution designs. The third six month cycle refines the solution designs and delivers initial technical specifications for the realization of these designs. The final six month cycle ends in the delivery of detailed technical specifications and Phase II project plans for the realization of these technical specifications. All project management activities for the FInest project are built around these six month cycles. A high level overview of the iterative nature of the project is shown in Figure 1 below. Figure 1 High level overview of FInest project 2.1. Project organization The FInest project is managed based on the principle that decision making should be made as close as possible to actual development activities. This means that the FInest project management organization is flat with a focus on rapid decision making. This organization, shown in Figure 2 below, allows the FInest team to react quickly to issues and ensures that problems are quickly resolved. The roles of each of the primary internal project stakeholders are described following Figure 2. D11.1 Project Management Plan V1.0 Page 10 of 26
11 FI PPP Boards and Working Groups FP ICT-FI Finest European Commission Project Coordinator Communications with European Commission General Assembly Decisions to be Executed Proposals for Decision Making Project Management Board FI PPP Alignment Coordinator Finest Technical Coordinator Logistics Stakeholder Coordinator Work Package Leaders Deliverable Lead Deliverable Lead Deliverable Lead Deliverable Lead Figure 2 - FInest project management structure Project Coordinator (PC) The Project Coordinator is a senior representative of the coordinating partner of the project. He acts as the intermediary between the project consortium and the European Commission, serving as the interaction point between the project consortium and the Project Officer / Commission. Within the project, the PC has the main responsibility in terms of project execution including, but not limited to, administrative and financial management. The PC thus conducts, in cooperation with the other coordinators and work package leaders, the daily management of the project and handles operational procedures and controls. The PC reports to and is accountable to the General Assembly. The Project Coordinator of the FInest project is Dr. J. Rod Franklin (Kuehne + Nagel) Technical Coordinator (TC) The Technical Coordinator is a senior researcher with a strong scientific-technical background and project management experience. The TC is responsible for coordinating the progress and consistency of the project s technical work, and for the quality control of all deliverables. The TC will monitor the technical progress on a day-to-day basis, supervising and closely collaborating with the leaders of the technical work packages. For the FInest project, the Technical Coordinator is Dr. Andreas Metzger (UDE) FI PPP Alignment Coordinator (AC) The FI PPP Alignment Coordinator is a senior representative of a consortium partner that is deeply involved with the Future Internet PPP. The AC is responsible for the D11.1 Project Management Plan V1.0 Page 11 of 26
12 coordination of the project within the Future Internet PPP, i.e. the alignment with the core platform project as well as the other use case projects and support actions. He, along with other senior project members, represents the project within the relevant FI PPP committees and events. For the FInest project, the Alignment Coordinator is Dr. Michael Stollberg (SAP) Logistics Stakeholder Coordinator (LSC) The Logistics Stakeholder Coordinator is a senior project member with a very strong background in industry and with well-established business networks in the transport and logistics and commercial shipper domains. The LSC is responsible for all activities related to the preparation for broad industrial adoption and user community building, including the investigation of business opportunities, the definition and implementation of a strategy for propagation to external stakeholders, and standardization activities. The scope of this role is not restricted to the consortium, but is explicitly concerned with the awareness generation and propagation of the project results to external stakeholders (commercial companies [within the transport and logistics domain and outside this domain] as well as public authorities and industry-relevant bodies) in order to ensure a broad adoption. The Logistics Stakeholder Coordinator for the project is Mr. Jan Vreeburg (AFKL) Work Package Leaders (WPL) The Work Package Leaders are responsible for the timely and effective execution of the work packages in accordance to the Description of Work. On a case-by-case basis, such responsibilities can be delegated to parties responsible for a given task. The WPLs are accountable for the day-to-day management of the work packages. They report to the Technical Coordinator, and closely interact with the FI PPP Alignment Coordinator and the Logistics Stakeholder Coordinator. The Work Package Leaders for the FInest project are: Work package 1 Michael Zahlmann (KN) Work package 2 Dr. Lone Sletbakk Ramstad (MRTK) Work package 3 Dr. Michael Stollberg (SAP) Work package 4 Dr. Fabiana Fournier (IBM) Work package 5 Dr. Michael Stollberg (SAP) Work package 6 Dr. Yagil Engel (IBM) Work package 7 Dr. Lone Sletbakk Ramstad (MRTK) Work package 8 Clarissa Marquezan (UDE) Work package 9 Dr. Michael Stollberg (SAP) Work package 10 H. Haluk Gökman (ARC) Work package 11 Dr. J. Rod Franklin (KN) D11.1 Project Management Plan V1.0 Page 12 of 26
13 2.1.6 Deliverable Leader (DL) The responsibilities of the Deliverable Leader include: (1) The technical and operational coordination and supervision of the work related to producing the deliverable; (2) Consolidating the contributions and assessing the quality of the deliverable. DLs directly report to the WPLs and are appointed by their organizations based on technical capabilities to carry out the work related to the deliverable. 3. Project collaboration tool The FInest team has elected to use EMC s eroom collaboration application as its internal knowledge management and collaboration tool. The eroom is hosted by SINTEF/MARINTEK, one of the FInest consortium partners, and provides services for storing project documents, document versioning, communicating among team members, managing project tasks, and scheduling project events. The eroom is organized around project dashboards that allow project managers to create virtual workspaces that facilitate project team collaboration and management. The top level project dashboard for the FInest project appears below. Figure 3 - FInest eroom dashboard The eroom dashboard provides both a file folder (center) and hierarchical relationship map (left side) structure for navigation. In the file folder section one can quickly access information concerning project members from the Contact List (see Figure 4) D11.1 Project Management Plan V1.0 Page 13 of 26
14 Figure 4 FInest contact list or information critical project related events from the FInest Calendar, as can be seen in Figure 5 below. Figure 5 FInest project calendar Work package leaders manage their work packages by setting up separate calendars and contact lists for their work packages, creating task lists and assigning responsibilities or creating detailed project plans with responsibilities and expected delivery dates through the services of the eroom. Examples of each of these management tools appear below. D11.1 Project Management Plan V1.0 Page 14 of 26
15 Figure 6 Example work package team calendar Figure 7 Example work package team contact list D11.1 Project Management Plan V1.0 Page 15 of 26
16 Figure 8 Example work package project task plan In addition to its management tools, the eroom provides the team with facilities for controlled document storage, tracking versions of documents and managing document checkout and controlling access. Facilities for various notifications are also included in the eroom so that document owners can be notified if a document has been changed, automated s sent out to notify individuals or groups that an action is required, etc. 4. Project reporting processes To facilitate communicating progress on each deliverable, a process has been established whereby each work package leader reports progress on their deliverables at regular intervals. This process requires each work package leader to comment on progress and issues during bi-weekly project management conference calls and formally document progress on a quarterly basis. The template that is filled out by each work package lead for the quarterly progress report is shown below. D11.1 Project Management Plan V1.0 Page 16 of 26
17 Figure 9 Project deliverable reporting template The responsibility for reporting person month effort against deliverables has been assigned to each of the partners in the FInest project. Each partner must report all of their personnel efforts against the various deliverables worked on by each person on a quarterly basis. These reports are collected by the Project Manager and consolidated for redistribution back to the work package leads for comparison of planned versus actual effort against deliverable. In addition, these reports are used as the basis for all reporting back to the European Commission on effort expended on project tasks. A copy of the reporting template for each of the partners is included below. D11.1 Project Management Plan V1.0 Page 17 of 26
18 Figure 10 Project effort reporting template 5. Project communications The FInest project uses several mechanisms for ensuring open and frequent communications amongst its members. Besides the eroom, which is the primary collaboration vehicle for the project, the FInest team uses conference and web presentation facilities from SAP and IBM, conference call facilities from Kuehne + Nagel, lists and a soon to be deployed web site. Regularly scheduled conference calls are the primary means of detailed communication between the work package leads, work package members and deliverable teams. Overall project management leadership calls are held on a bi-weekly basis to ensure that all work package leads are informed of any upcoming events, issues that may have arisen since the last call or new factors that may have a bearing on the project. Work package leaders are responsible for coordinating their work package teams and hold conference calls and meetings based on schedules that they establish. Formal discussions between work package leaders are held on a regular basis to ensure that each work package is being developed in a manner that ensures that it will support the other work packages. Technical work package leaders use these formal calls to ensure that the work being performed on in their work package will integrate into the overall collaboration service architecture. Project plenary meetings are scheduled to be held on a semi-annual basis so that the entire project team can meet to share ideas and exchange experiences based on their work on the project. The first project meeting was held at the University of Duisburg- Essen in April to both kick-off the project and to introduce individuals to one another in a face-to-face manner. The second plenary meeting is scheduled to be held the first week in September in Instanbul, Turkey. Additional plenary sessions will be planned during the meeting in Instanbul. D11.1 Project Management Plan V1.0 Page 18 of 26
19 The table that follows summarizes the various calls and meetings currently being utilized by the FInest team to communicate and manage the project. Call/Meeting Type PMB Conference Call WPL Conference Call Plenary Sessions Work Package Calls Deliverable Calls FI PPP Board Calls/Meetings Schedule Bi-weekly 1.5 hour call Bi-weekly 1.5 hour call Every six months As required by WPLs As required by DLs Monthly Purpose Project updates from PC, TC, AC, LSC and WPLs Inter-work package coordination call to ensure technical designs fit collaboration architecture and address domain requirements Face-to-face FInest team meeting to present progress to date and discuss next six months activities Intra-work package coordination calls to ensure technical designs are being developed per plan and domain requirements Focused deliverable calls to ensure that progress is being made on deliverable development Discuss issues related to the overall FI PPP program (Steering Board, Architecture Board, Working Groups) Table 1 FInest coordination call/meeting list 5.1. Project website The FInest team has begun designing and implementing a project website ( This website will serve as a dissemination vehicle for the project providing interested parties with an overview of project activities and access to all the public documents generated during project execution. It is planned that the website will be made operational and accessible to the public during the first half of July External users of the website will find information on the project, the FI PPP program, downloadable public documents from the project, notices on conferences either hosted by the FInest team or where the team will be presenting information on the project, academic papers generated by project team members concerning the project, information on other projects within the FI PPP program and/or addressing issues associated with the Future Internet, and other documents that provide valuable insights on what the project is all about to external parties. A mock-up of how the website might look is shown below. For more information on the FInest website see project deliverable D10.1. D11.1 Project Management Plan V1.0 Page 19 of 26
20 Figure 11 Mock-up of project website 5.2. Project newsletters In addition to the communications processes described in previous sections, the FInest team has begun developing a project newsletter to distribute to interested individuals. The newsletter will contain important information about the current activities of the FInest team and articles of interest to the readers of the newsletter. A draft newsletter was developed for the FIA conference in Budapest and based on the feedback received at the conference a final form of the newsletter is under development. The newsletter will be updated periodically based on important advances in the FInest project and posted to the FInest website to ensure that it has broad distribution Project templates To ensure consistency in the FInest project when communicating with external stakeholders or interested parties, the FInest team has developed a set of standard templates for various communications activities that are maintained in the eroom. These templates include a standard deliverable template, a standard presentation template, a standard review template, standard internal project reporting templates and standard logos for the project. 6. Project quality control A formal quality control process has been developed by the FInest team to ensure that the quality of deliverables generated by the team meets the requirements of the D11.1 Project Management Plan V1.0 Page 20 of 26
21 European Commission and that any potential risks affecting the project are properly managed. The deliverable quality assurance process that has been developed by the FInest team is graphically depicted in Figure 12 below. Figure 12 - Quality assurance process for deliverables The quality control process for deliverables requires that the deliverable owners and reviewers ensure that the deliverables adhere to the following quality aspects: The contribution of the deliverable to the WP and the overall goals of FInest should be clearly stated The objectives of the deliverable should be clearly expressed in the introduction to the document (and in the abstract / management summary). Specifically, the deliverable should feature a short 1-2 paragraphs introduction that clearly states the role and duty of said document, in the scope of FInest (and possibly the whole PPP programme). The deliverable should be clearly related to previous and future deliverables in the WP and if applicable to deliverables from other WPs The relation / additions / differences to previous deliverables in the same work package (i.e. in the case the deliverable is an improved version of a previous one) should be clearly stated The deliverable should be a self-contained document, which can be understood without knowledge of the DoW (or previous deliverables) The deliverable contents should be consistent with its description in the DoW; if not, the deviation should be explained The deliverable should be cohesive and concise (typically not more than pages) D11.1 Project Management Plan V1.0 Page 21 of 26
22 The deliverable should not contain any claims that are not proven or supported by references The terminology in the deliverable should as far as possible be aligned with the definitions from D1.2 Transport and logistics domain dictionary, as well as the FI-WARE definitions (that should be published as part of their deliverable D.2.2 FI-WARE High-level Description ) Concerning the use of notations (modelling languages and the like): A deliverable should clearly state if the standard semantics of the notation is used, or not. Deviations from the standard semantics need to be explained in the text 7. Project risk management Risk management for the project is based on the risk management and cross-partner risk awareness process shown in the figure that follows. Below this figure the phases and management approaches employed by the FInest team to control project risk are explained in more detail. Figure 13 Risk Management Process 1. Risk Planning is concerned with identifying risk management procedures and responsibilities. Risk Management Planning occurs as part of the proposal and negotiation phase and continues throughout the lifecycle of the project to ensure that any changes in project scope or focus are carefully analysed as to their potential impacts on project risk. 2. Risk Identification is the proactive process of uncovering risks before they turn into problems. Like risk planning, risk identification is an iterative process. The first phase of risk identification occurred during the proposal phase; the risks identified during the proposal phase of the project have been re-examined and updated based on the current state of the project. This process of ongoing updating will continue throughout the lifecycle of the project. Participants in risk identification include subject-matter experts, WPLs, project management and team members. Identified risks are documented in a risk statement that describes the conditions that are causing concern, followed by a brief description of the potential consequences of these risks. 3. Risk Analysis is the most detailed phase of the entire risk management process. It involves evaluating the risk attributes and prioritizing the risks. Evaluating the attributes of a risk involves establishing values for probability (the likelihood the risk will occur) and the impact (in terms of significance for the project). The D11.1 Project Management Plan V1.0 Page 22 of 26
23 following five level scoring approach is currently being used for the analysis of the risks in the project. Probability Qualitative Impact 1 20% = Remote Insignificant 21 40% = Unlikely Minor 41 60% = Likely Moderate 61 80% = Highly Likely Major 81 99% = Near Certainty Catastrophic 4. Risk Response is the process of deciding what should be done with a risk, if anything at all. Risk Response answers two key questions: (1) who owns the risk (responsibility) and (2) what can / should be done (scope and actions). The range of response actions for the project is as follows: Delegate: Risk is internal to project. Research: Means investigating the risk until enough is known to be able to decide what to do. Research ranges from making phone calls to conducting a detailed review of the risk drivers. Transfer: Risk is external to the project. Resources and knowledge outside of the project are better able to manage the risk. Transfer implies the ultimate accountability, responsibility and authority to expend resources, it requires acceptance of the risk by the receiving party. Accept: Do nothing, but handle the risk as an issue if it occurs. However, no further resources are expended in managing the risk. These are usually risks of lower significance. Mitigate: Eliminate or reduce the risk by reducing the impact, reducing the probability, or shifting the timeframe when action must be taken. Watch: Monitor the risks and their attributes for early warning of critical changes in impact, probability, timeframe or other aspects. 5. Risk Monitoring is the process of keeping track of the risks and evaluating the effectiveness of the response actions. Monitoring may also provide a basis for developing additional response actions and identifying new risks and is done in a continuous manner. In order to manage the project s risks in accordance to the process and assessment instruments as defined above, a risk register has been created and populated with initial risk estimates. This register will be updated quarterly based on input from the WPLs and the project TC. The current risk register, with impact assessments for identified risks, appears in the table following. Risk Description Probability Impact Prevention and Mitigation Technical Risks D11.1 Project Management Plan V1.0 Page 23 of 26
24 1 Insufficient domain relevance by missing real world requirements 15% Moderate The consortium includes several leading service providers with vast expertise in various fields of the Transport & Logistics industry and involves them strongly in domain and use case definition as well as technical development 2 Conceptual Design not well aligned with business requirements and domain knowledge 15% Moderate The work plan is structured in two iterative cycles with a synchronization every 6 months to ensure alignment with requirements; the first iteration ends in M12 and provides refined requirements and an initial design for the second iteration, that ends in M24 3 Conceptual failure within the software design 20% Major The overall design is defined by experienced software engineers from several partners, broad expertise can be accessed since some partners have decades of experiences in software engineering 4 Poor alignment with FI PPP Core Platform (Generic Enablers, domain-specific capabilities) 15% Major Work package 9 is dedicated for all FI PPP alignment activities and coordinates the answers for Core Platform Calls and provides all requirements from technical work packages 5 Time for domain analysis, design and specification is underestimated 25% Moderate Project milestones every 6 months will monitor project progress and will detect problems early to take corrective actions; additional resources will be invested to ensure project timeline; adequate replanning of actions in collaboration between Executive Management Board and involved WP leads to ensure project results in the worst case 6 Specification of use cases does not meet real word requirements 30% Moderate The application partners within the consortium have a vast expertise in the Transport & Logistics domain. Real world applicability of envisioned use cases will be proofed in D11.1 Project Management Plan V1.0 Page 24 of 26
25 dedicated experimentation environments, including both software and hardware aspects. Management / Financial Risks 1 The coordination and/or management of FInest fails 2 Personnel leaves before project completion 5% Major 80% Moderate The project coordinator KN as well as all of the consortium members have extensive experience in managing and running EU research projects, and professional project management will plan and proactively avoid deviations and failures Introduction of common responsibility and backup developers (at least two people are familiar with critical aspects within the project) 3 Key person leaves consortium 50% Major If the partner cannot provide a replacement, a re-allocation of responsibilities between partners will be implemented 4 Partner leaves consortium 10% Major The Project Coordinator will find a capable new partner. The delay of the project will be kept to a minimum by contributing additional resources to remaining partners. 5 Dissemination of the project results is not sufficient to create impact 25% Moderate The consortium is highly motivated to create sustaining impact, and the partners have substantial experience in the international R&D business; the dedicated work package for dissemination, exploitation and standardization will ensure proper dissemination of results. 6 Standardization committee rejects or declines standard proposals; severe changes in standards conflict with FInest results 35% Moderate The consortium will discuss and monitor standardization activities, participate in applicable standards setting bodies and maintain a proactive stance with respect to any changes proposed for standards that impact the project. D11.1 Project Management Plan V1.0 Page 25 of 26
26 7 Lack of communication or consensus within consortium 50% Moderate Management procedures have been defined for enabling effective decision making. The project coordinator and the members of the Project Management Board have the necessary skills to resolve such conflicts by adequate negotiation. Additionally, it is planned to keep close contact within the consortium by regular telephone conferences and virtual meetings. 8 Partner does not report financial or effort consumption in time to realize the management report 40% Moderate Project management processes have been established to enforce timely and correct reporting. In the worst case, the missing data for reports and cost statements will be handed in later. Table 2 Project risk register 8. Summary This document presents the approach taken by the FInest team to manage the project. In addition, the tools used by the team to manage the project, communicate internally and externally about the project and to control the quality and risks associated with the project have been presented. The project management plan and the various instruments used to control the project will be continuously updated and refined as the project moves forward. These updates will become part of the FInest project s review at the end of each review cycle. D11.1 Project Management Plan V1.0 Page 26 of 26
ACESS A Comprehensive Enterprise Social Services System
State of Louisiana Department of Social Services ACESS A Comprehensive Enterprise Social Services System Project Control Standards and Procedures Deliverable AC09 SEPTEMBER 1, 2004 VERSION 1.1 State of
More informationProject Governance Plan Next Generation 9-1-1 Project Oregon Military Department, Office of Emergency Management, 9-1-1 Program (The OEM 9-1-1)
Oregon Military Department, Office of Emergency Management, 9-1-1 Program (The OEM 9-1-1) Date: October 1, 2014 Version: 3.1 DOCUMENT REVISION HISTORY Version Date Changes Updated By 0.1 02/13/014 Initial
More informationProject Execution Guidelines for SESAR 2020 Exploratory Research
Project Execution Guidelines for SESAR 2020 Exploratory Research 04 June 2015 Edition 01.01.00 This document aims at providing guidance to consortia members on the way they are expected to fulfil the project
More informationFInest Future Internet enabled optimisation of transport and logistics networks
FInest Future Internet enabled optimisation of transport and logistics networks Deliverable D3.4 Technical Specification of the Domain-Specific Future Internet (FI) Platform for Transport and Logistics
More informationPublic Transportation - Accessibility for All
Deliverable 1.1 Project Management Plan & Schedule (incl. project management strategies, risk management plan, dissemination plan and a detailed project schedule) Grant agreement no.: 233701 Project acronym:
More informationGuidance notes and templates for Project Technical Review involving Independent Expert(s)
Guidance notes and templates for Project Technical Review involving Independent Expert(s) FP7 Collaborative Projects, Networks of Excellence, Coordination and Support Actions Version 18/12/2007 Disclaimer
More informationMicrosoft Solutions for Security. Delivering the Windows Server 2003 Security Guide
Microsoft Solutions for Security Delivering the Windows Server 2003 Security Guide Information in this document, including URL and other Internet Web site references, is subject to change without notice.
More informationPROJECT WEBSITE PROJECT WEBSITE
PROJECT WEBSITE published by the research team of the Horizon 2020 Project DiDIY Digital Do It Yourself in the context of WorkPackage 8 Dissemination, future roadmap and sustainability (WP Lead Partner:
More informationGuillem Bernat (RAPITA) Communication, Deliverable, Dissemination, Publication, Reporting
D5.2 Project Handbook Document Information Contract Number 249100 Project Website Contractual Deadline Dissemination Level Nature Author Contributors Reviewer Keywords www.proartis-project.eu PM04 Public
More informationDeliverable D6.2: Quality Plan FP7-ICT-2011-8
Deliverable D6.2: Quality Plan Date of Delivery: M2 Authors: Eleni Toli (UoA) Dissemination level: PU WP: Work package number Version: 1.0 Keywords: Quality assurance, internal procedures, templates, key
More informationGuidance notes and templates for Project Technical Review involving Independent Expert(s)
Guidance notes and templates for Project Technical Review involving Independent Expert(s) FP7 Collaborative Projects (CP), Networks of Excellence, Coordination and Support Actions (CSA), CP-CSA, ERA-NET,
More informationLEXEVS OPERATIONS AND MAINTENCE SUPPORT PROJECT MANAGEMENT PLAN
LEXEVS OPERATIONS AND MAINTENCE SUPPORT PROJECT MANAGEMENT PLAN Version Number: 1.0 Version Date: October 1, 2014 VERSION HISTORY Version Number Implemented By Revision Date Approved By Approval Date 1.0
More informationDeliverable 9.1 Management Plan
Deliverable 9.1 Management Plan Author: Maurizio Omologo Affiliation: Fondazione Bruno Kessler Document Type: R Date: May 15 th, 2012 Status/Version: 1.0 Dissemination semination Level: PU Project Reference
More informationUNITED STATES DEPARTMENT OF EDUCATION OFFICE OF INSPECTOR GENERAL
UNITED STATES DEPARTMENT OF EDUCATION OFFICE OF INSPECTOR GENERAL AUDIT SERVICES August 24, 2015 Control Number ED-OIG/A04N0004 James W. Runcie Chief Operating Officer U.S. Department of Education Federal
More informationVoice Over IP Network Solution Design, Testing, Integration and Implementation Program Overview
Voice Over IP Network Solution Design, Testing, Integration and Implementation Program Overview 1/1 Table of Contents 1. Introduction...3 2. Executive Summary...4 3. Program Definition...5 3.1. Program
More informationRSA ARCHER OPERATIONAL RISK MANAGEMENT
RSA ARCHER OPERATIONAL RISK MANAGEMENT 87% of organizations surveyed have seen the volume and complexity of risks increase over the past five years. Another 20% of these organizations have seen the volume
More informationNegotiations feedback for successful project preparation. ERANIS workshop, 27.11.2007, Minsk
Negotiations feedback for successful project preparation Negotiations procedure Feedback from the Commission on the project plan issues that need to be explained in more detail Request to formulate Annex
More informationStrategic Risk Management for School Board Trustees
Strategic Management for School Board Trustees A Management Process Framework May, 2012 Table of Contents Introduction Page I. Purpose....................................... 3 II. Applicability and Scope............................
More informationHow To Improve Transport And Logistics
Cloud Based Collaboration Platform for Transport & Logistics Business Networks Prof. Dr. Rod Franklin, Managing Director, Executive Education and Adjunct Professor of Logistics, The Kuehne Logistics University,
More informationPHASE 3: PLANNING PHASE
PHASE 3: PLANNING PHASE The ning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
More informationUniversity of Wisconsin Platteville IT Governance Model Final Report Executive Summary
University of Wisconsin Platteville IT Governance Model Final Report Executive Summary February 2013 Project Objectives & Approach Objectives: Build on the efforts of the Technology Oversight Planning
More informationPHASE 3: PLANNING PHASE
PHASE 3: PLANNING PHASE The Planning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
More informationHabEat - FP7-245012. HabEat
HabEat Determining factors and critical periods in food habit formation and breaking in early childhood: a multidisciplinary approach Grant agreement number: FP7-245012 Medium-scale Collaborative Project
More informationFive best practices for deploying a successful service-oriented architecture
IBM Global Services April 2008 Five best practices for deploying a successful service-oriented architecture Leveraging lessons learned from the IBM Academy of Technology Executive Summary Today s innovative
More informationProcess Assessment and Improvement Approach
Process Assessment and Improvement Approach June 2008 The information contained in this document represents the current view of Virtify on the issues discussed as of the date of publication. Virtify cannot
More informationDeliverable D1.1. Building data bridges between biological and medical infrastructures in Europe. Grant agreement no.: 284209
Deliverable D1.1 Project Title: Building data bridges between biological and medical infrastructures in Europe Project Acronym: BioMedBridges Grant agreement no.: 284209 Research Infrastructures, FP7 Capacities
More informationVisual Enterprise Architecture
Business Process Management & Enterprise Architecture Services and Solutions October 2012 VEA: Click About to edit Us Master title style Global Presence Service and Solution Delivery in 22 Countries and
More informationAdministrative + Management Aspects. EU - Framework Programme 7. Grant Agreement: Acronym FMT-XCT Project Kick-off Meeting, 14.05.
Administrative + Management Aspects EU - Framework Programme 7 Grant Agreement: Acronym FMT-XCT Project Kick-off Meeting, 14.05.2008 Dr. Jürgen Ertel Department Program Planing and Management Head of Project
More informationDeliverable 1.1 Description of Quality Management and Risk Processing Responsible partner:
Deliverable 1.1 Description of Quality Management and Risk Processing Responsible partner: BOKU - University of Natural Resources and Life Sciences, Vienna Institute for Transport Studies List of abbreviations
More informationEuro-BioImaging European Research Infrastructure for Imaging Technologies in Biological and Biomedical Sciences
Euro-BioImaging European Research Infrastructure for Imaging Technologies in Biological and Biomedical Sciences WP1 Project Management Task 1.3 Delivery of milestones; reporting duties Deliverable 1.1
More informationInternational Collaboration on Research Data Infrastructure
Project Acronym Project Title icordi International Collaboration on Research Data Infrastructure Project Number 312424 Deliverable Title Quality plan and Risk register Deliverable No. D1.1 Delivery Date
More informationHEADS Website and Collaboration Platform
Deliverable reference: Date: Responsible partner: D6.1 27 November 2013 ATC Project co-funded by the European Commission within the Seventh Framework Programme (FP7-ICT-2013-10)) ICT-2013.1.2: Software
More informationD01.1 Project Management Plan
D01.1 Project Management Plan Document identification Related SP / WP SP0 / WP01 Reference SCR-WP01-D-THA-008 Related Deliverable D01.2 Dissemination Level CO Lead Participant THALES Lead Author Bruno
More informationAudit of the Test of Design of Entity-Level Controls
Audit of the Test of Design of Entity-Level Controls Canadian Grain Commission Audit & Evaluation Services Final Report March 2012 Canadian Grain Commission 0 Entity Level Controls 2011 Table of Contents
More informationGuidelines for reporting. for Accompanying Measures. implemented as. Specific Support Action
SIXTH FRAMEWORK PROGRAMME Research Infrastructures Action Guidelines for reporting for Accompanying Measures implemented as Specific Support Action This document can be found on the INTERNET at the following
More informationSECTION I PROJECT SUMMARY (TRW)
SECTION I PROJECT SUMMARY (TRW) Table I Summary Agency/Department Information TRW Information Executive Sponsor: Cynthia Lorenzo Received Date: Managers: Ron McCranie/Andy Loveland Status Meeting Date:
More informationCHEST FP7-611333. Collective enhanced Environment for Social Tasks. Deliverable D4.1. CHEST Communication web site and dissemination material PNO
D4.1 - CHEST Communication web site and dissemination material Version: v1.0 CHEST FP7-611333 Collective enhanced Environment for Social Tasks Deliverable D4.1 CHEST Communication web site and dissemination
More informationAppendix V Risk Management Plan Template
Appendix V Risk Management Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms Definitions
More informationAUDIT CERTIFICATE GUIDANCE NOTES 6 TH FRAMEWORK PROGRAMME
AUDIT CERTIFICATE GUIDANCE NOTES 6 TH FRAMEWORK PROGRAMME GUIDANCE NOTES FOR CONTRACTORS AND CERTIFYING ENTITIES MATERIALS PREPARED BY INTERDEPARTMENTAL AUDIT CERTIFICATE WORKING GROUP VERSION 1 APPROVED
More informationInternal Communications Channels
Learning Analytics Community Exchange Internal Communications Channels Public Deliverable D9.1 By: Hendrik Drachsler, Maren Scheffel Published: 30 April 2014 Keywords: management, internal communications,
More informationAdrian Cristal (BSC), Osman Unsal (BSC) Reviewer
Document Information Contract Number 318693 Project Website D1.1 Project Management Tools www.paradime-project.eu Contractual Deadline Month 6 (30 March 2013) Dissemination Level Public Nature Report Author
More informationTREASURY INSPECTOR GENERAL FOR TAX ADMINISTRATION
TREASURY INSPECTOR GENERAL FOR TAX ADMINISTRATION The Customer Account Data Engine 2 Systems Development Guidelines; However, Process Improvements Are Needed to Address Inconsistencies September 30, Year
More informationMicrosoft Active Directory Project
Microsoft Active Directory Project Simcoe County District School Board Project Kick-off Meeting Rami Wehbe (Solution Architect) January 18, 2012 Agenda Introductions Project objectives and drivers Approach
More informationQualification of innovative floating substructures for 10MW wind turbines and water depths greater than 50m
Qualification of innovative floating substructures for 10MW wind turbines and water depths greater than 50m Project acronym LIFES50+ Grant agreement 640741 Collaborative project Start date 2015-06-01 Duration
More informationMaturity Model. March 2006. Version 1.0. P2MM Version 1.0 The OGC logo is a Registered Trade Mark of the Office of Government Commerce
Maturity Model March 2006 Version 1.0 P2MM Version 1.0 The OGC logo is a Registered Trade Mark of the Office of Government Commerce This is a Value Added product which is outside the scope of the HMSO
More informationFinding the Right People for Your Program Evaluation Team: Evaluator and Planning Team Job Descriptions
: Evaluator and Planning Team Job Descriptions I. Overview II. Sample Evaluator Job Description III. Evaluator Competencies IV. Recruiting members of your strategic evaluation planning team V. Recruiting
More informationProject reporting in FP6
Guidance notes for Integrated Projects, Networks of Excellence, Specific Targeted Research or Innovation Projects, Coordination Actions, Specific Support Actions, Co-operative Research Projects and Collective
More informationPROJECT MANAGEMENT PLAN <PROJECT NAME>
PROJECT MANAGEMENT PLAN TEMPLATE This Project Management Plan Template is free for you to copy and use on your project and within your organization. We hope that you find this template useful and welcome
More informationPROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE:
PROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE: Project Name Project Management Plan Document Information Document Title Version Author Owner Project Management Plan Amendment History
More informationEnterprise Portfolio Management
Enterprise Portfolio Management Managing large volumes of structured data Through its powerful capabilities as a structural modeling tool, ABACUS Summary provides of whitepaper a ready-to-go Summary solution
More informationBiometrics Enterprise Architecture Project Management Plan (BMEA PMP)
Biometrics Enterprise Architecture Project Management Plan (BMEA PMP) Version 1.0 Prepared by: Date: November 24, 2008 Revision History Purpose Revision Date Level 11/17/2009 First Draft 1.0 Responsible
More informationDevelopment, Acquisition, Implementation, and Maintenance of Application Systems
Development, Acquisition, Implementation, and Maintenance of Application Systems Part of a series of notes to help Centers review their own Center internal management processes from the point of view of
More informationPOSITION DETAILS. Centre for Higher Education Development (CHED)
JOB DESCRIPTION NOTES Forms must be downloaded from the UCT website: http://www.uct.ac.za/depts/sapweb/forms/forms.htm This form serves as a template for the writing of job descriptions. A copy of this
More informationIntroduction to the ITS Project Management Methodology
Introduction to the ITS Project Management Methodology In September 1999 the Joint Legislative Committee on Performance Evaluation and Expenditure Review (PEER) produced a report entitled Major Computer
More informationCyber Security Consultancy Standard. Version 0.2 Crown Copyright 2015 All Rights Reserved. Page 1 of 13
Cyber Security Consultancy Standard Version 0.2 Crown Copyright 2015 All Rights Reserved Page 1 of 13 Contents 1. Overview... 3 2. Assessment approach... 4 3. Requirements... 5 3.1 Service description...
More informationHow To Develop Software
Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which
More informationMNLARS Project Audit Checklist
Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?
More informationEXECUTIVE SUMMARY...5
Table of Contents EXECUTIVE SUMMARY...5 CONTEXT...5 AUDIT OBJECTIVE...5 AUDIT SCOPE...5 AUDIT CONCLUSION...6 KEY OBSERVATIONS AND RECOMMENDATIONS...6 1. INTRODUCTION...9 1.1 BACKGROUND...9 1.2 OBJECTIVES...9
More informationAustralia/New Zealand General Insurance Program Activity and Implementation Report
Australia/New Zealand General Insurance Program Activity and Implementation Report (PAIR Report) March 2015 ACORD is a non-profit membership standards development organization (SDO) which develops and
More informationITRM Guideline CPM 110-01 Date: January 23, 2006 SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE
PROJECT MANAGEMENT GUIDELINE SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE Table of Contents Introduction... 3 Project Execution and Control Phase Overview... 3 Activities and Documents in the Execution
More informationUnderstand why, when and how-to to formally close a project
Project Closure Purpose: Understand why, when and how-to to formally close a project Audience: Project managers, project sponsors, team members and other key stakeholders Learning Objectives: Describe
More informationCRM Business Plan Template Introduction: How to Use This Template
CRM Business Plan Template Introduction: How to Use This Template This template will help build a living CRM business plan for the enterprise as well as document business justifications for specific near-term
More informationproject portfolio management Effectively plan, manage, and control projects and resources Planview Enterprise Planview Project Portfolio Management
project portfolio management Effectively plan, manage, and control projects and resources Planview Project Portfolio Management gives you the tools you need to effectively manage projects and resources
More informationHow To Be An Architect
February 9, 2015 February 9, 2015 Page i Table of Contents General Characteristics... 1 Career Path... 3 Typical Common Responsibilities for the ure Role... 4 Typical Responsibilities for Enterprise ure...
More informationNASCIO EA Development Tool-Kit Solution Architecture. Version 3.0
NASCIO EA Development Tool-Kit Solution Architecture Version 3.0 October 2004 TABLE OF CONTENTS SOLUTION ARCHITECTURE...1 Introduction...1 Benefits...3 Link to Implementation Planning...4 Definitions...5
More informationProcess Guide. Release Management. Service Improvement Program (SIP)
Process Guide Release Service Improvement Program (SIP) i Table of Contents Process Guide Release Document Information... 3 Approval... 4 Section 1: Process Vision... 6 Overview... 6 Process Mission and
More informationKPMG Advisory. Microsoft Dynamics CRM. Advisory, Design & Delivery Services. A KPMG Service for G-Cloud V. April 2014
KPMG Advisory Microsoft Dynamics CRM Advisory, Design & Delivery Services A KPMG Service for G-Cloud V April 2014 Table of Contents Service Definition Summary (What s the challenge?)... 3 Service Definition
More informationIT Services Management Service Brief
IT Services Management Service Brief Capacity Management Prepared by: Rick Leopoldi May 25, 2002 Copyright 2002. All rights reserved. Duplication of this document or extraction of content is strictly forbidden.
More informationWhite Paper. PPP Governance
PPP Governance The Governance of Projects, Programs and Portfolios (PPP) (sometimes called project governance for convenience) is the sub-set of corporate and organisational governance 1 focused on assisting
More informationIT Services Management Service Brief
IT Services Management Service Brief Service Continuity (Disaster Recovery Planning) Prepared by: Rick Leopoldi May 25, 2002 Copyright 2002. All rights reserved. Duplication of this document or extraction
More informationDepartment of Administration Portfolio Management System 1.3 June 30, 2010
E 06/ 30/ 2010 EX AM PL 1. 3 06/ 28/ 2010 06/ 24/ 2010 06/ 23/ 2010 06/ 15/ 2010 06/ 18/ 2010 Portfolio System 1.3 June 30, 2010 Contents Section 1. Project Overview... 1 1.1 Project Description... 1 1.2
More informationProject Management through
Project Management through Unified Project and Portfolio Fluent User Interface Management Built on SharePoint Server 2010 Time Reporting Enhancements Project Initiation & Business Case Exchange Server
More informationFinal. North Carolina Procurement Transformation. Governance Model March 11, 2011
North Carolina Procurement Transformation Governance Model March 11, 2011 Executive Summary Design Approach Process Governance Model Overview Recommended Governance Structure Recommended Governance Processes
More informationFInest Future Internet enabled optimisation of transport and logistics networks
FInest Future Internet enabled optimisation of transport and logistics networks D1.3 Business Requirements for future transport and logistics ICT solutions The research leading to these results has received
More informationUDC Software Development Life Cycle
Office of Information Technology UDC Software Development Life Cycle Document Number: Effective Date: 3/3/2011 Revision Date: Author(s): Leslie Pinyan Contributors: Approved By: Dale Matthews, Hakeem Fahm
More informationWHY DO I NEED A PROGRAM MANAGEMENT OFFICE (AND HOW DO I GET ONE)?
WHY DO I NEED A PROGRAM MANAGEMENT OFFICE (AND HOW DO I GET ONE)? Due to the often complex and risky nature of projects, many organizations experience pressure for consistency in strategy, communication,
More informationSecond Clinical Safety Review of the Personally Controlled Electronic Health Record (PCEHR) June 2013
Second Clinical Safety Review of the Personally Controlled Electronic Health Record (PCEHR) June 2013 Undertaken by KPMG on behalf of Australian Commission on Safety and Quality in Health Care Contents
More informationUoD IT Job Description
UoD IT Job Description Role: Projects Portfolio Manager HERA Grade: 8 Responsible to: Director of IT Accountable for: Day to day leadership of team members and assigned workload Key Relationships: Management
More informationState of California Department of Transportation. Transportation System Data Business Plan
DRAFT Page i State of California Department of Transportation Transportation System Data Business Plan RFO# TSI DPA-0003 September 29, 2011 DRAFT Page ii Table of Contents Executive Summary... 4 Chapter
More informationPurpose of Report To present a revised corporate risk register as at May 2013
Report to Standards and Audit Committee Agenda Item 8 Report SAC 06/13 Date 25 June 2013 By Title of Report Director of Corporate Services Corporate Risk Register Purpose of Report To present a revised
More informationProposal template (technical annex) Health, demographic change and wellbeing Two-stage Research and Innovation actions Innovation actions
Proposal template (technical annex) Health, demographic change and wellbeing Two-stage Research and Innovation actions Innovation actions Note: This is for information only. The definitive templates to
More informationPosition Description. Enterprise Agreement: Budget Responsibility: Nil
Position Description Position Details Position Scope Title: Division: Project Manager Finance & Corporate Services Enterprise Agreement: Budget Responsibility: Department: Payroll Authority Level: Ambulance
More informationSensing, monitoring and actuating on the UNderwater world through a federated Research InfraStructure Extending the Future Internet SUNRISE
Sensing, monitoring and actuating on the UNderwater world through a federated Research InfraStructure Extending the Future Internet SUNRISE Grant Agreement number 611449 Announcement of the Second Competitive
More informationGUIDE FOR APPLICANTS
European Commission THE SEVENTH FRAMEWORK PROGRAMME The Seventh Framework Programme focuses on Community activities in the field of research, technological development and demonstration (RTD) for the period
More informationDriving Excellence in Implementation and Beyond The Underlying Quality Principles
SAP Thought Leadership Paper SAP Active Quality Management Driving Excellence in Implementation and Beyond The Underlying Quality Principles 2014 SAP AG or an SAP affiliate company. All rights reserved.
More informationBiSL Glossary. 5 February 2014
Acceptance test Annual Business Information Management plan Annual information provisioning plan Application Application management ASL (Application Services Library) ASP (Application Service Providing)
More informationIn accordance with risk management best practices, below describes the standard process for enterprise risk management (ERM), including:
Enterprise Risk Management Process and Procedures Scope In accordance with risk management best practices, below describes the standard process for enterprise risk management (ERM), including: Risk identification
More informationCloud Computing Security Considerations
Cloud Computing Security Considerations Roger Halbheer, Chief Security Advisor, Public Sector, EMEA Doug Cavit, Principal Security Strategist Lead, Trustworthy Computing, USA January 2010 1 Introduction
More informationPROJECT MANAGEMENT GUIDELINES NATIONAL TRANSPORT AUTHORITY
PROJECT MANAGEMENT GUIDELINES FOR PROJECTS FUNDED BY THE NATIONAL TRANSPORT AUTHORITY (UP TO 20 MILLION IN VALUE) december 2011 Table of Contents Section A 1. Introduction 4 1.1 Purpose 4 1.2 Applicability
More informationRelease Management: Effective practices for IT delivery
Release Management: Effective practices for IT delivery Introduction Today s health plans face a unique combination of technology challenges due to their complex IT environments. These environments serve
More informationProject Knowledge Areas
From Houston S: The Project Manager s Guide to Health Information Technology Implementation. Chicago: HIMSS; 2011; pp 27 39. This book is available on the HIMSS online bookstore at www. himss.org/store.
More informationThe Project Management Life Cycle By Jason Westland (A book review by R. Max Wideman)
The Project Management Life Cycle By Jason Westland (A book review by R. Max Wideman) 11/17/07 Introduction Editor's Note: We liked so much of this book that we asked for the author's permission to quote
More informationPROPOSAL ACRONYM - ETN / EID / EJD (delete as appropriate and include as header on each page) START PAGE MARIE SKŁODOWSKA-CURIE ACTIONS
START PAGE MARIE SKŁODOWSKA-CURIE ACTIONS Innovative Training Networks (ITN) Call: H2020-MSCA-ITN-2015 PART B PROPOSAL ACRONYM This proposal is to be evaluated as: [ETN] [EID] [EJD] [delete as appropriate]
More informationIT1T Integrated Recruitment Systems 2015
UCD IT Services IT1T Integrated Recruitment Systems 2015 Project Initiation Document Version 1.0 2 December 2014 Version History Version Date Summary of Changes Changed by 1.0 02/12/2014 Initial Draft
More informationOffice of the Auditor General AUDIT OF IT GOVERNANCE. Tabled at Audit Committee March 12, 2015
Office of the Auditor General AUDIT OF IT GOVERNANCE Tabled at Audit Committee March 12, 2015 This page has intentionally been left blank Table of Contents Executive Summary... 1 Introduction... 1 Background...
More informationFuture Internet Public-Private Partnership Call 3 (Objectives 1.8-1.9) European Commission Communications Networks, Content and Technology DG
Future Internet Public-Private Partnership Call 3 (Objectives 1.8-1.9) European Commission Communications Networks, Content and Technology DG FI-PPP Leadership beyond R&D ICT applications research Application
More informationStandard Monitoring Procedures
Standard Monitoring Procedures GEO Certified Club and Course Management Golf Environment Organization 2 Quality Street North Berwick Scotland EH39 4HW T: +44 (0) 1620 895100 W: golfenvironment.org Reference:
More informationARTEMIS-ED-21-09. Guidance notes and templates for Project Technical Review involving independent expert(s)
Guidance notes and templates for Project Technical Review involving independent expert(s) 1 CONTENTS 1 INTRODUCTION... 3 2 THE PROJECT REVIEW PROCESS... 3 3 MANDATE OF THE INDEPENDENT EXPERT(S)... 5 3.1
More informationEMPIR Reporting Guidelines Part 0 Guide to the parts
Part 0 Guide to the parts EMPIR Reporting Guidelines Part 0 Guide to the parts EURAMET MSU, Hampton Road, Teddington, Middlesex, TW11 0LW, UK Phone: +44 20 8943 6666 Email: msu@npl.co.uk msu.euramet.org
More informationCompliance Management of Company Law Compliances Approach and Technology Perspective
Compliance Management of Company Law Compliances Approach and Technology Perspective Shujath Bin Ali*, Manager (Corporate Affairs, Legal & Tax), Deloitte Consulting India Private Limited, Hyderabad. Compliance
More information