10-15 (ca) at CSC in Esboo
PM Mats Lindstedt 100% first year, 75% last year and >50% 2017
Travelling takes a lot of time, more time to support partners than planned. No major risk for underprioritizing the project due to other responsibilities.
Jonna is the main backup for the PM role. There is also a team at CSC that knows about the project and that has the necessary skills. The other WP leads are also very self propellant on their respective areas. The informal contacts around the project that Mats has been keeping up is what could fall in worst case.
There is quite a bit of documentation around WP1 that can be used for a hand-over in worst case.
Present main responsibility lies in the follow-up and encuragement of the WP’s work during the rest of the project.
Jonna Korhonen more involved in the WP4 participation. Has new responsibilities at work that takes full time.
For now there is little time needed, lack of time not a problem. Participation in WP4 at a low level.
Using existing networks as a ground for marketing of EMREX.
If problems arises it is possible to take in someone else into the project.
Other itemes, outside the project but that aims at making EMREX a success at Finish univeristies will take som time and effort.
QM Reijo Soréus
5-10%, other responsibilities takes priority often. The audit is focused in time. Normally not much QA activities outside the audit unless there are specific quality issues coming up.
External supplier is contracted to fix any bugs found in the system.
Financing only covers EMREX during the project period, no descision on the future yet. Ongoing preparations for a descision regarding a financial solution.
-
Quarterly reporting to the steering group.
Yearly and extra reports to EACEA, written as well as informal reporting.
All under Control.
Risk analysis, monitoring and reduction activities
Denmarks participation is no longer a project risk.
Student participation seems to reach our goals, especially compared to the theoreticals. Basic data has been difficult to get.
High dependencies on individuals for all partners, but especially so at CINECA. Needs to involve more individuals and spread the work. More and quicker response when needed.
Challenge how to ensure that the work on the final report will progress as needed.
EU – happy at the moment
Ministeries
Universities
Students
Other organisations
Internal stakeholders
Kati is WP3/FI when it comes to development (mantenance) and operations ordering. 10% dedicated which is slightly undersized.
Virta staff helps out with practicals.
Contingency is secured by other Virta staff who are fairly well initiated in Emrex. There is also staff at the outsourcing supplier who bulit the solution.
Participation in the ELMO 2 work is probably ok.
External supplier is contracted to fix any bugs found in the system.
Financing only covers EMREX during the project period, no descision on the future yet. Ongoing preparations for a descision regarding a financial solution.
The lack of unique identification of foreign students has impacted the premises of the use of EMREX. There is a need of procedual and legal changes in Finland in order to make a solution such as EMREX to work smoothly.
There is also a direct impact on the theoretical maximal number of users during the Field Trial. This is also a result of the project, a lesson learnt.
No deliverables planned but there is improvements to be done with the handling of imported pdf in the SMP. Development is ongoing and the solution is supposed to be in production in Q1 2017.
-
-
Small volumes of log data, no known problems with supplying what is available to WP5.
Risk analysis, monitoring and reduction activities
There are no major risks that would have an impact on the Field Trial. There is a modification planned that is supposed to replace the transformation to ELMO that could cause problems but that would not affect the Field Trial as such.
WP3 is a stakeholder as responsible for supplying the network
WP4 is a stakeholder due to the field trial
WP5 is a stakeholder for the surveys and usage statistics
The project internal stakeholders are followed up through the project groul meetings
Students and adminstrators are stakeholders as users of the system.
Direct contacts with the institutions through the IRO’s, feedback.
Also direct contacts with IT staff regarding xml retreival (technical).
Student identification is needed to be improved.
Process of student account recalling is also in need of a change, extension to ½-1 year after end of studies.