2. Agenda
Time Presentation Leader Notes
12:00 – 12:05 Welcome & overview INTRA -
of agenda
12:05 – 12:15 Work-Package 2 ATC
Presentations should focus on WP achievements and Tasks that need
12:15 – 12:25 Work-Package 3 IBM to be completed by the Review meeting. A maximum of 2-3 slides
should be used.
12:25 – 12:35 Work-Package 4 INTRA
12:35 – 13:45 Work-Package 5 ENG Presentation should provide insight on (a) the Pilot execution, and (b)
current evaluation results.
13:45 - 13:55 10 min. b r e a k
13:55 – 14:55 Work-Package 6 ATOS Presentation should address (a) how the PO’s request with respect to
approaching other PA institutions is satisfied, and what was the
impact of our actions, (b) the exploitation activities performed so far,
and intentions for presentation of corresponding material at review
meeting.
14:55 – 15:10 Work-Package 7 INTRA Issues that need to be addressed up to Review meeting.
15:10 – 15:15 Closure INTRA -
2 COCKPIT – 6th Plenary meeting, 12th January 2012
3. Work Package 2
Citizen’s Opinion Mining and Deliberation
ATC – Ilias Spais
3 COCKPIT – 6th Plenary meeting, 12th January 2012
4. Opinion Mining
o Optimization and enhancement of all Opinion Mining (OM) constituting
s/w tools and support of error handling activities
o Support on Cockpit’s pilot activities
o Adaptation of “Active learning” methodology during the training of the
module – monitoring of the process
o Research on how to enhance OM’s capabilities (provision of the 2nd
version)
‣ Deliberation Platform
o Bug fixes, implemented feature requests sent by users
o Re-arranged Home Page
o Added link to survey
o Greek pilot went live
4
4 COCKPIT – 6th Plenary meeting, 12th January 2012
5. January data are for the first 10 days. The Greek Pilot has an
average or 3 new users per day, since it went live.
5
5 COCKPIT – 6th Plenary meeting, 12th January 2012
6. OM – DP (2nd version)
Responsible partner Deadline Remarks
Focus on evaluating the
ATC, INTRASOFT Mid of January
training corpus
End users – Supporting Focus on OM’s performance
End of January
partners in total
Evaluate the results of OM’s
Can we utilize the uncertainty
realization in the 1st pilot execution
ATC, INTRASOFT 10th of February sampling technique to
evaluate the engine?
ENG - Evaluation report
The main focus should be the
polarity (positive, negative)
Development of an
ATC, INTRASOFT On going process classification of opinions
entity-based OM engine
based on entities like costs,
effort, time, etc.
Realization of document
Development of the algorithm that
classification algorithms to
will assure the relevancy of the ATC, INTRASOFT On going process
assure relevancy
opinions
The goal is to have a
prototype to demonstrate in
the 3rd review meeting
Premature version of the updated OM
environment released
ATC, INTRASOFT Review Meeting
Training corpus and ontology
may remain the same (those
included in the 1st version)
6
6 COCKPIT – 6th Plenary meeting, 12th January 2012
7. OM – DP (2nd version)
Responsible partner Deadline Remarks
Compare OM’s results of the 1stpilot
We should demonstrate that
execution and those resulted from the
ATC, INTRASOFT Review Meeting the adjustments will make
realization of the premature e2nd
OM more efficient
version
Update the instructions of creating
ATC, INTRASOFT End of March
the training corpus (2nd version)
Early creation of the
preparation material –
End users – Supporting
Preparation phase End of April necessary due to OM’s
partners
dependence on the language
specifications
Bugs will be fixed with a high
Bug fixes, address feature requests priority. All feature requests
sent by users
ATC On going process
will be replied, but not all of
them will be implemented.
An advanced usage statistics
module based on Google
Usage statistics ATC End of January
Analytics will be added to the
platform.
Platform presentation ATC Review Meeting
7
7 COCKPIT – 6th Plenary meeting, 12th January 2012
8. Thank you for your attention!
8 COCKPIT – 3rd Plenary meeting, 11th-12th of Nov. 2010
9. Work Package 3
Public Service Modelling and Costing
IBM – Nindhi Rajshree
9 COCKPIT – 6th Plenary meeting, 12th January 2012
10. ‣ Progress made (M18-M25)
o Conceptualization and documentation of a revised version of the
compliance view meta-model.
‣ Details:
o The model is composed of a set of compliance patterns.
o The patterns are used to write compliance expressions that formally
capture rules, norms, legislations, etc. a public service should comply to.
‣ Benefits:
o Integrated with the SE toolkit, this will allow the service designers to
import existing compliance rule specified by the policy makers and
validate if their BPMN process workflow is compliant or not.
‣ Action Plan until review meeting
o Finalizing the deliverable D3.1.2 writing up
o Incremental updates of the meta-model
10 COCKPIT – 6th Plenary meeting, 12th January 2012
11. ‣ Progress Made (Since Plenary V)
o Simulation
Transformation rules for supporting all BPMN entities
Improved output statistics
Improved user interface
o Other Functionality in SE Tool
Improved error handling
Implementation of new features in progress
o Support
Bug fixes raised during integration tests and pilots
Training sessions and demo creations
Released updates
‣ Action Plan until review meeting
o Functionality in SE Tool
Implementation of new features: Cheat Sheets, Search, Globalization etc. in progress
o Support
Release of updates
Bug fixes and enhancements
Generation of simulation applet to support the pilots
11 COCKPIT – 6th Plenary meeting, 12th January 2012
12. ‣ Progress made (M18-M25):
o Conceptualization and documentation of revised cost/valuation model
(reflected in D3.2.2)
o Incremental improvements and bug fixes for the cost/valuation
subsystem (reflected in D3.2.1.2)
o Evaluation design for Service Feature Model component
Questions to citizens on how the stating of preferences is perceived
Questions to service engineers on applicability and usefulness of the provided
modeling tools
o Support for the evaluation of the SFM designer and valuation server
‣ Action Plan until review meeting
o On-going support for evaluations
o Analysis and dissemination of evaluation results
o Incremental updates of the implementation
12 COCKPIT – 6th Plenary meeting, 12th January 2012
13. Thank you for your attention!
13 COCKPIT – 3rd Plenary meeting, 11th-12th of Nov. 2010
14. Work Package 4
Implementation of COCKPIT Toolkit
INTRASOFT– Charis Vassiliou
14 COCKPIT – 6th Plenary meeting, 12th January 2012
15. WP4: Progress performed so far…
‣ Successfully finished the implementation, integration and deployment of the Integrated
COCKPIT Toolkit (initial version):
‣ Complete portable installation prototype along with deployment and maintenance manual
distributed to all end-user partners.
‣ Training sessions conducted with end-users supported by technical partners.
‣ Update site set-up for consecutive updates and bug-fixes.
‣ The following deliverables have been successfully submitted to the EC according to the
project work plan:
‣ D4.1.1: Conceptual Architecture and Design Specifications of COCKPIT Toolkit, 1st version –
Resubmitted according to review report comments.
‣ D4.2.1: Test Cases and overall system evaluation results 1st version
‣ D4.3.1: Integrated COCKPIT Toolkit 1st version
‣ Currently performing bug-fixes and minor adjustments to the initial prototype to support
the parallel process of end-user trials (initial iteration)
‣ Several updates distributed to the end-users already.
‣ Presently focusing on final adjustments to the Simulation module (SV).
15 COCKPIT – 6th Plenary meeting, 12th January 2012
16. Planned work until M32 (August 2012)
‣ A second SVN has been deployed for the development, integration and
testing process of the second and final version of the Integrated COCKPIT
Toolkit.
‣ Prepare a detailed demonstration scenario (i.e. Public Service, Metadata,
etc.) to guide the Review Meeting prototype demo.
‣ A detailed development plan is under preparation featuring the functionality
envisioned for the final prototype, focusing mainly on the SE, OM and DP.
‣ The above mentioned plan will be enriched with the results and outcomes of the initial end-
user evaluation process.
‣ Issues marked with high importance derived from the end-users will be considered for
implementation towards the final prototype of the respective modules.
‣ Initiate the preparation of the respective WP4 deliverables to be submitted
by M32 (August 2012):
‣ D4.1.2: Conceptual Architecture and Design Specifications of COCKPIT Toolkit 2nd version.
‣ D4.2.2: Test Cases and overall system evaluation results 2nd version.
‣ D4.3.2: Integrated COCKPIT Toolkit 2nd version.
16 COCKPIT – 6th Plenary meeting, 12th January 2012
17. Thank you for your attention!
17 COCKPIT – 3rd Plenary meeting, 11th-12th of Nov. 2010
18. Work Package 5
COCKPIT Governance Model Pilots & Evaluation
ENG – Ivan Ficano
18 COCKPIT – 6th Plenary meeting, 12th January 2012
19. ‣ Insight on pilot execution
‣ Report of current evaluation results
19 COCKPIT – 6th Plenary meeting, 12th January 2012
20. 20 COCKPIT – 6th Plenary meeting, 12th January 2012
21. ‣ General considerations
‣ Former common action plan
‣ Adjustment of plan for the three local cases
‣ Current status of piloting progress
‣ Changes on Deliberation Platform
21 COCKPIT – 6th Plenary meeting, 12th January 2012
22. ‣ General considerations:
‣ The first piloting cycle is being revealed trickier than
expected, mostly due to
‣ acceptance of technology (Venice)
‣ involvement of stakeholders (CiTilburg)
‣ The first piloting cycle will be more focussed on the
technology rather than on the methodology
‣ The first piloting cycle will be definitely more based on
the SE modelling rather than on the DP deliberation
22 COCKPIT – 6th Plenary meeting, 12th January 2012
23. ‣ Former common action plan
‣ An early pilot schedule was circulated, aiming at leading the
activities of the three pilot partners.
‣ Original proposed deadlines for the 1st pilot execution:
‣ 11/11: Familiarization with Toolkit & DP
‣ 18/11: Training of OM
‣ 25/11: Initial modeling of public service, upload to the DP
& generation of Polls
‣ 25/11:Publication of Press release (in any case, after the
upload to the DP)
‣ 09/12: Remodeling, based on Poll feedback
‣ 14/12: Upload simulation to the DP
‣ 14/01: Remodeling, based on comments received from
simulation, forums etc. & upload to DP
‣ ...continuously: experience logging, DP monitoring,
generation of artifacts
‣ 30/01 Report of conclusions
23 COCKPIT – 6th Plenary meeting, 12th January 2012
24. ‣ Specific plans of three local cases
‣ Due to requirements specific for each partner, the three public
bodies adjusted the general plan according to their constraints
and directives, and circulated the new ones.
Original deadlines and Task CiTilburg YPES Venice
11/11: Familiarization with Toolkit & DP 15/12 11/11 15/12
18/11: Training of OM 15/12 18/11 15/12
25/11: Initial modeling of public service, upload to the DP
22/12 13/12 15/12
& generation of Polls
25/11:Publication of Press release -- 13/12 16/12
09/12: Remodeling based on Poll feedback 09/01 09/01 --
14/12:Upload simulation to the DP 15/01 11/01 --
14/01: Remodeling based on comments received from
20/01 30/01 --
simulation, forums etc. & upload to DP
30/01: Report of conclusions 30/01 10/02 10/02
24 COCKPIT – 6th Plenary meeting, 12th January 2012
25. ‣ Current status of piloting progress
Task CiTilburg YPES Venice
Only partially.
Only partially. The training tool is in
Training of OM Done.
It will be completed this week. “Pre-Analysis” state since
the 14 of december.
Initial 10 tryouts (modeling and DP
modeling of upload) with fake data.
Done.
public service Done. Problems with BPMN
& upload to the Real case “Werkgeversplein” in
modelling still to be fixed.
DP progress.
None.
Generation of None.
Done. Likely deadline: by the
Polls No planned deadline.
3rd week of January
No public press release is planned
by CiTilburg. Only professional
(government) bodies that are None.
Publication of responsable on innovation of Done Likely deadline: by the
Press release methodology and tools will be 3rd week of January
addressed.
No planned deadline.
25 COCKPIT – 6th Plenary meeting, 12th January 2012
26. ‣ Current status of piloting progress
Task CiTilburg YPES Venice
Remodeling None.
None. None.
based on poll No planned
feedback Planned by 20th of Janaury No planned deadline
deadline
Yes. Ongoing activity.
The number of active users is Through RSS feed
Monitoring the still low. However, almost all from Forum, though
None
DP posts are totally relevant and no real debate has
useful. There are no offensive, started yet.
insulting or advertising posts.
Sending of Done.
Done.
experiences log Not yet Up to 7th of
sheet Up to 23rd of November.
December.
26 COCKPIT – 6th Plenary meeting, 12th January 2012
27. Changes on the Deliberation Platform
‣ The DP has been customized by YPES and VENICE
according to their different languages and preferences.
‣ Some changes are still to be done for the VENICE case.
27 COCKPIT – 6th Plenary meeting, 12th January 2012
28. 28 COCKPIT – 6th Plenary meeting, 12th January 2012
29. ‣ Usage logs
‣ Self-assessment list
‣ Laboratory test
‣ Questionnaires
o On-line questionnaire
o User questionnaire
‣ General feedback
29 COCKPIT – 6th Plenary meeting, 12th January 2012
30. ‣ Usage logs
‣ YPES and Venice already sent a first version of the usage
log file, CiTilburg committed to send it as soon as possible
(maybe by the end of next week).
‣ Moreover, all mail exchanges and phone calls regarding the
pilot experiences have been noted down and will be
suitably used as material for the evaluation.
‣ Experiences reported so far refer to the early stages of the
piloting and are too immature to come to a consolidate
consideration. Moreover, some of them are sw bugs, some
other are suggestions for future improvements.
30 COCKPIT – 6th Plenary meeting, 12th January 2012
31. Self-assessment list
‣ Consortium partners (Intra, IBM, ATC, NTUA, KIT,
UniTilburg) have filled in a table with some questions
regarding intrinsic features of both the governance model
and the toolkit, according to their expertise on the issues.
‣ Results are very satisfactory. The technical partners have
unawarely showed a great allignment in the assessment,
except for
Accessibility:
Which level of accessibility the web part of the toolkit has?
•a. None
•b. Level “A” of Web Content Accessibility Guidelines
•c. Level “AA” of Web Content Accessibility Guidelines
•d.Level “AAA” of Web Content Accessibility Guidelines
Portability:
Is the toolkit installable and adaptable to different environments (i.e. operating systems, hardware configurations)
•a. Yes
•b. Yes, only partially
•c. Not
31 COCKPIT – 6th Plenary meeting, 12th January 2012
32. Laboratory test
‣ A first laboratory test has already been carried out in ENG
premises. The tester had only office automation SW skills.
Never used Eclipse or other IDE. Some significant results:
‣ good general acceptance (both explicitly and deduced through
facial expressions); high understandability; scarse attractiveness,
but that was perceived as reasonable considered the expected
target user, indeed sobriety was found as proper and suitable;
multi-tab layout naturally intuitive; scarse readability (too small
types); high perceived usefulness; in some cases limitative; etc.
‣ Other two tests are scheduled in January.
32 COCKPIT – 6th Plenary meeting, 12th January 2012
33. ‣ Questionnaires
o On-line questionnaire addressed to collect feedbacks on both the
new governance model and the interaction with the interface are
already available to citizens and have been linked from the DP
home pages (to the following URLs):
English (Citilburg): http://www.surveymonkey.com/s/LV2DTC2
Italian (Venice): http://www.surveymonkey.com/s/9PTY8GN
Greek (YPES): http://www.surveymonkey.com/s/966YRV7
o User questionnaire
By the end of the 1st piloting cycle, when all toolkit
functionalities are expected to be tested and assesseble by
the user partners, a survey will be provided to them in order
to evaluate aspects coming from the overall experience (not
related to single usages) on aspects such as satisfaction,
effectiveness and efficiency
33 COCKPIT – 6th Plenary meeting, 12th January 2012
34. Thank you for your attention!
34 COCKPIT – 3rd Plenary meeting, 11th-12th of Nov. 2010
36. ‣ Progress dissemination tools and activities
‣ Impact creation and assessment
‣ Progress exploitation activities
‣ Action Plan. Planning for review presentation
36
36 COCKPIT – 6th Plenary meeting, 12th January 2012
37. Dissemination tools
Press releases
Preparation of press releases
o General English version
o Version for each use case
Atos communication department:
preparing launch of press release in
relevant media
Ypes; NTUA; Intra - already
disseminated via diverse channels
Other partners circulate press
release
12 January 2012 37
37
38. Website updates
Uploading new
“Demonstration Prototype
Toolkit Presentation”
Including direct accesses to
the 3 pilot sites; visually by
countries’ flags
Uploading the “Demonstrator
of the Cockpit video toolkit to
homepage
Upload of 4th Cockpit
newsletter for download
12 January 2012 38
38
39. Cockpit Newsletter
Preparation and design of
Cockpit Newsletter 4th issue
sent to SIG Dec 2011
Currently 128 members in
the Cockpit Special Interest
Group (SIG) list
12 January 2012 39
39
40. Dissemination activities – publications and events (M13-M24)
Scientific publications
‣ 4 publications in books, journals, magazines
Publications in popular media
‣ Publications in Greek online journal and newspaper announcing the
pilot use case in Greece (Intra)
‣ Publications of Greek press release (Ypes, Ntua)
Paper submissions
‣ 2011: Total of 10 papers submitted to conferences/events
12 January 2012
40
40 COCKPIT – 6th Plenary meeting, 12th January 2012
41. Events (M13-M24)
‣ Participation of partners in a total of 17 events during 2nd year
‣ Upcoming events of interest:
14-15 June 2012 ECEG 2012 – 12th European Conference One of the most relevant
Barcelona on e-Government conferences in
eGovernment in Europe
July 3-5 2012 MeTTeG 2012 - 6th Intern. Conference Papers submission
Belgrade on Methodologies, Technologies and deadline: 31 Jan 2012
Tools enabling e-Government
3-6 Sept. 2012 4th IFIP International Conference on Papers submission
Kristiansand, eParticipation deadline: 15 Mar 2012
Norway
Please inform Atos about participations in project relevant events
or other dissemination activities
41
41 COCKPIT – 6th Plenary meeting, 12th January 2012
42. WP 6 – Deliverables
‣ D 6.6.1 Dissemination report 1st version Submitted M24
‣ D 6.8.2 Ethical issues report 2nd versions Submitted M24
42
42 COCKPIT – 6th Plenary meeting, 12th January 2012
43. Task of approaching Public Administrations
Cockpit dissemination activities particularly considered to raise
awareness and create impact among PAs:
Achievements so far:
Participation in events of special interest
1.) ePractice events
‣ Presentation of Cockpit in 2 ePractice events in Brussels
‣ Representatives of EC, Public Sector, Public Service Providers,
Researchers
o Collaborative production of eGovernment services (27/10/11)
o User centric eServices (20/12/2011)
43
43 COCKPIT – 6th Plenary meeting, 12th January 2012
44. 2.) Smart Cities events
‣ Smart Cities as the next stage in urbanisation with growing importance of
ICTs; currently area of great interest
‣ Six main axes: Cockpit = Smart governance axis
‣ Smart Cities Expo World Congress Barcelona (28 Nov-2Dec 2011):
o Presentation of Cockpit by Atos Research & Innovation Director
o Video show of Cockpit Methodology Video at the Atos exhibition booth;
distribution of Cockpit brochures
o Large event with considerably high impact; approx. 900 participants,
among them especially PAs
44
44 COCKPIT – 6th Plenary meeting, 12th January 2012
46. Cockpit as asset in Atos Smart
Cities campaign
Inclusion of Cockpit in the Atos
Smart Cities brochure as part
of the Smart governance axis
to be circulated massively
Cockpit presentation to be
included in future Smart Cities
events
Cockpit possibly forming part
of the Atos worldwide “IT for
cities campaign”
o Initiative of the Atos global Atos Brochure: “Empowering
marketing management
department for Public Sector
Smart Cities”
12 January 2012 46
46
47. ‣ In order to enlarge Cockpit impact to as many target groups
and regions as possible, Cockpit partners are encouraged to
contribute in the creation of impact
‣ The Atos initiatives can serve as examples for other partners
to carry out similar actions
o Within their organisations
o Among other initiatives they are involved
‣ Please report such activities to Atos
‣ If you need further information or support, Atos will assist you
when required
47
47 COCKPIT – 6th Plenary meeting, 12th January 2012
48. Cockpit seminar/workshop
‣ Celebrate workshop in Holland
o City of Tilburg, University of Tilburg, Atos Holland (provision of premises,
support organisation)
o Currently in process: critical success factor is involvement of some
important stakeholders:
- VNG/KING (Union of Dutch local governments)
- UWV
- Some larger cities
‣ Among all partners agree on the focus of this workshop:
o Settle the agenda: Demo of the tool, presentation of use
case (Tilburg?), tool assessment
o Seminar/workshop requires technical support
‣ Other (user) partners would also like to participate/contribute?
48
48 COCKPIT – 6th Plenary meeting, 12th January 2012
49. Impact assessment in three groups
1.) Dissemination activities impact assessment:
‣ Assessment carried out according to the success criteria table included in
the Dissemination report 1st version
2.) Workshop(s) impact assessment:
‣ Questionnaire circulation among workshop participants
o Questions include business evaluation, tools assessment and purchase interest
‣ Possible open table discussion with participants
3.) Pilots impact assessment:
‣ Our suggestion: including 2 or 3 questions to the existing evaluation
questionnaires (WP5) concerning user engagement and business
evaluation
o Questions on user engagement – to be included to online questionnaire on DP
o Questions business evaluation – to be included to Public Administration questionnaire
49
49 COCKPIT – 6th Plenary meeting, 12th January 2012
50. ‣ Table of content of D6.7.2: Business and Exploitation plan 2nd
version, (M35)
‣ 1. Competitive analysis. Benchmarking study
‣ 2. Exploitation Agreement
‣ 3. Individual Exploitation Plan
‣ 4. Potential client approach - Engage business development personnel from the partners’
organisations
‣ Questionnaire creation for business evaluation
‣ Individual exploitation plan template.
The business plan will establish guidelines to the market deployment of the product/service the
consortium and the individual partners want to exploit. In particular, the exploitation plan will
elaborate alternative exploitation/sustainability strategies for those outcomes that could not be
commercialised.
50
50 COCKPIT – 6th Plenary meeting, 12th January 2012
51. ‣ Potential client approach
Atos exploitation and impact efforts:
o Meeting with Atos Business Development Department
o Cockpit will possibly be included in Atos worldwide “IT for cities campaign”
o Cockpit to be included in future Smart Cities events; actual area of great interest ,
also among PAs.
‣ Engage business development personnel from the partners’ organisations - Each
partner find opportunity to transmit cockpit within its organisation, especially big
industry partners; business development
51
51 COCKPIT – 6th Plenary meeting, 12th January 2012
52. ‣ Update on dissemination tools and activities since the last review
o Please communicate all dissemination activities carried out to us (especially
publication of press releases about piloting, activities which create impact
‣ Cockpit workshop
o Short summary about the outcome; high level evaluation if timeframe permits
‣ Impact assessment method of user engagement & business
evaluation
o Questionnaire development
52
52 COCKPIT – 6th Plenary meeting, 12th January 2012
53. ‣ Cockpit products and services
‣ Benchmarking analysis draft
‣ Individual exploitation plans draft
‣ Exploitation Agreement draft
‣ Preliminary results of potential client approach
o (Engagement business development personnel from the partners’ organisations)
12 January 2012
53
53 COCKPIT – 6th Plenary meeting, 12th January 2012
54. Thank you for your attention!
54 COCKPIT – 3rd Plenary meeting, 11th-12th of Nov. 2010
55. Work Package 7
Project Management
INTRASOFT - Christos Georgousopoulos
55 COCKPIT – 6th Plenary meeting, 12th January 2012
56. Important dates
Input for Management Reports
‣ Effort consumption - Quarterly reports .xls files
12th of Jan. ( TODAY! )
‣ Work-Package updated descriptions
‣ Explanation notes on use of resources & Form C 20th of Jan. (coming Friday)
& upload of cost statements at NEF/ECAS
Deliverables:
‣ Provision of all deliverables for review to EC Reviewers & PO: 17th of Feb. 2012
(three weeks prior the review)
*D5.3.1: 2nd of Mar. 2012
(one week prior the review)
Meetings at Venice:
‣ Rehearsal meeting: 8th of Mar. 2012
Social event: night of rehearsal - PO will be present (and maybe the reviewers)
‣ Review meeting: 9th of Mar. 2012
56
COCKPIT – 6th Plenary meeting, 12th January 2012
57. Submission of pending Deliverables
‣ D7.3: Second Periodic Activity Report
Dec. 2011 (…early Feb.2012)
‣ D7.4: Second Management Report
‣ *D3.1.2: Public Service Formal Representation, 2nd version
‣ *D3.2.2: Public Service Cost Estimation and Valuation Model, 2nd version Jan. 2012
‣ *D3.2.2.1: Public Service Cost Estimation and Valuation system, 2nd version
‣ *D5.3.1: COCKPIT Governance Model and Toolkit Evaluation Report, 1st version Feb. 2012
*might receive feedback during review
57 COCKPIT – 6th Plenary meeting, 12th January 2012
58. Preparations for review
‣ Agenda:
‣ Live demonstration of COCKPIT usage PO’s focus
‣ Pilot evaluation results
‣ ENG will present in detail the overall results
‣ Users will present/highlight specific aspects of usage/experience
• Have a real decision maker/V.I.P. to talk about Cockpit (VENICE, YPES, CiTilburg)
‣ Exploitation and engagement of other PA institutions
‣ WP progress
‣ Feedback on Ethical issues for Greek case
‣ Management Reports & address of reviewers’ past comments
58 COCKPIT – 6th Plenary meeting, 12th January 2012
59. Thank you for your attention!
59 COCKPIT – 3rd Plenary meeting, 11th-12th of Nov. 2010
Notas do Editor
Substantially broadening the reach of our project to more EU Public Institutions, outside of our consortium, and assess the impact of our solution against a significant sample of EU Public Institutions. Suggested means for achieving this may include larger-scale communication events in Brussels or other places where stakeholders can be invited and appropriately presented the project, or utilizing electronic means for impact assessment such as on-line presentations and on-line questionnaires.