Mobility Project
This should be the workspace for the mobility project
Contents
1. Introduction
2. Participants
3. Work Teams
4. Project Plan
5. Technical Package
1. Introduction
1.1 Background
The proposal builds on the pilot prototype developed by 2 University Consortia - CINECA (Italy) and MUCI (Poland) - recently presented at both the RS3G Workshop and the annual EUNIS Conference held in Santiago de Compostela on June 22-26th 2009.
The presentation and paper are available here: http://www.rs3g.org/activities/future-events/20090622_eunis
1.2 Aim
Facilitate mobility - one of the main objectives of European Higher Education Area (as stated in the London Communiqué 2007, and emphasized in the Leuven Communiqué 2009)
1.3 Specific Objectives
- Interconnect European universities in a digital communication network
- Reduce administrative inefficiencies/problems in handling mobility data and procedures (intra-university)
- Streamline the communication flow among partner institutions (inter-universities )
- Digitize mobility documents (secure, authentic, transparent, tamper-proof)
- Produce reliable and accessible mobility statistics (EC interest)
1.4 Distinctive Traits
- The value of the project is directly proportional to the number of active participants - the "network effect".
- Economies of scale could be triggered faster by interconnecting the consortia and established implementers first - connect one, serve many - the "Hub-and-Spoke" approach.
- Adopting "Standards" specifications for an open, accessible and efficient implementation
- Leveraging established Federated Identity Management technologies.
2. Participants
2.1 Requirements and Profile
This is an OPEN project. Mobility is the "hallmark" of the European Higher Education Area, therefore any organization at stake willing to contribute is welcome to join in - the impact of the project is directly related to the number of active participants. However, due to the very nature of the project, the "preferred" profile is that of a partner with willingness and ability to execute and (some of) the following characteristics:
- installed universities (customer) base (software implementers - CINECA, MUCI...)
- means of promoting and disseminating the project (organizations - EUNIS, EAIE...)
- experience in European Funding Programs (LLP, TEMPUS, CIP...) and proven track record of successful project participation.
- lobbying channels into the European Commission (DG EAC)
- International mobility expertise (IROs)
- involvment in standardization activities (MLO, ELM, SCHAC..)
2.2 Participants list
Every participant should fill complete his profile (see OODI ) with :
- list of universities managed
- integrated mobility module or 3rd party
- any other info
University Consortia
- OODI - Finland - Finland
- SIGMA - Spain
- CINECA - Italy
- [Ladok] - Sweden
- FS - Norway
- MUCI - Poland
- [HIS] - Germany
- [SURF] - Netherlands
- AlmaLaurea - Italy
- [VHS] - Sweden
- OCU - Spain
Individual Universities
- [University of Stuttgart] - Germany
- [University of Malaga] - Spain
- University of Thessaloniki - Greece
- [University of Porto] - Portugal
- [University Fernando Pessoa] - Portugal
Companies
3. Work Teams
The distribution of the participants below is ONLY a proposal and not intended to be final. Please feel free to assign yourself to whichever team you could contribute most.
3.1 WSDL
- MUCI
- QS unisolution
- KION
- FS
- SIGMA
- AcademyOne
- Ladok
- Studielink
- OODI
- HIS
- FS
- Mark Stubbs (links to CEN / XML standards)
3.2 Identity and Access Management
- University of Malaga (SCHAC)
- SiGMA US
- Waterford IT
- HIS/DAASI...
3.3 Security and Lifecycle Management
- Digitary
- SIGMA US
- University of Malaga
3.4 Architecture
- FS
- AcademyOne
- MUCI
- OODI
- Surf ???
3.5 Business Processes
- QS unisolution
- University of Thessaloniki
- IBGroep
- all other universities
3.6 Funding
- KION (acting)
- Almalaurea
- UniStuttgart
- Waterford IT
3.6 Pilot
- MUCI
- KION
- University of Thessaloniki
Download the:
RS3G Mobility Project Work Teams.pdf

4. Project Plan
- Project (re)kick-off meeting (Nov. 16th @ RS3G workshop)
- Share prototype
- Factor in contributions
- Define Work Teams
- Set Goals and Deadlines
- schedule a joint workshop between RS3G and TF-EMC2 (Spring 2010)
- present the update on the project at EUNIS 2010 in Warsaw (June 2010) - running pilot with at least 5 institutions
- present the user scenarios at EAIE 2010 in Nantes (September 2010) - project presentation in a "user-oriented" way
4.1 History and Next Steps
- Starting week of Nov. 23 2010, each team leader will be responsible to contact his/hers members and collect the issues to be addressed by their team in the context of mobility project. These issues should be listed/documented on the wiki and will be discussed in the coordination call around mid-december.
- mid december 2010 we will have a coordination call among all the team leaders, to share a preliminary take at what are the issues to be addressed and set the specific (realistic) objectives to be reached by next workshop (joint RS3G-EMC2) in March 2010
- End of January (tbd) we will another coordination call to check on the stauts of things, and define the agenda (activities) for the March workshop - which
- RS3G Mobility Project Meeting (Bologna)18 March 2010 - Joint Workshop with EMC2, a very "hands-on" one . Ideally we will take 2 days of hand-on work where the different team should come together, and the 3rd day we will have the general assembly where the team leaders will report the progresses made. Particular focus will be put on IAM.
- June 2010 (Eunis conference) - presentation on the update of the project to the wider audience. By then our goal is to have a running pilot with at least 5 institutions. Paper on Mobility Project at EUNIS (Best Paper Award!)
- September 2010 (EAIE conference) - presentation of the project to a more "user-oriented" audience.
- 13-15 December 2010 - joint RS3G and TF-EMC2 workshop in Malaga. RS3G - ECAM joint meeting
- March 2011 (Mallorca) - Code Camp !