1 Likfol1.doc Welcome speech VILAB - Project Meeting, Lingkoping, August 14, 1999 Welcome to the 3 rd VILAB Project meeting distinguished guests chairman of the Industrial Advisory Board (IAB Gunnar Carlsson Prof. G. Elst, Head of the Dresden Branch Lab of IIS/EAS representatives of Lingkoping University, Prof. Z. Peng basic goals to be met partners’ progress report included information about VILAB Sub projects how to involve the IAB in the VILAB project work administrative issues
Transcript
1
Likfol1.doc
Welcome speech VILAB - Project Meeting, Lingkoping, August 14, 1999
Welcome to the 3rd VILAB Project meeting
distinguished guests chairman of the Industrial Advisory Board (IABGunnar CarlssonProf. G. Elst, Head of the Dresden Branch Lab of IIS/EASrepresentatives of Lingkoping University, Prof. Z. Peng
basic goals to be met partners’ progress report included information about
VILAB Sub projects how to involve the IAB in the VILAB project work
administrative issues
2
Welcome speech VILAB - Project Meeting, Lingkoping, August 14, 1999
agreement today’s agenda• I suggest to make the change as small as possible
minutes of the meeting• I would like to ask Zebo to take over this task
other items to be discussed today
3
Final Agenda for the Lingkoping VILAB Project Meeting, August 13 - 14, 1999
09.00- 09.30 Welcome address and final agenda (Peng/Diener)
09.30 - 12.00 Partners’ report on results achieved (Diener)09.30 - 09.45 T TU (Ubar)09.45 - 10.00 EAS DD (Diener)10.00 - 10.15 TU DA (Hollstein)10.15 - 10.30 Lingk. Uni. (Peng)
10.30 - 10.45 Short Coffee Break
10.45 - 11.00 S TU (Fristacky)11.00 - 11.15 II SAS (Gramatova)11.15 - 11.30 IET (Kobus)11.30 - 11.45 W UT (Jaworski)11.45 - 12.00 TU B (Pataricza)
4
12.00 - 13.00 Free discussion (Peng)
13.00 - 14.00 Lunch Break
14.00 - 15.00 Discussion on the role of IAB (Carlsson)14.00 - 14.10 Introduction (Carlsson)14.10 - 14.20 Project Coordinator (Diener)14.20 - 14.30 Kuzmicz’s point of view (Jarworski)14.30 - 15.00 Free discussion (all)
15.00 - 16.00 Discussions in Working Groups (Coffee Breakincluded)
16.30 - 17.15 Administrative issues (Ubar)16.30 - 16.45 Annual Progress Report and CS (Diener)16.45 - 17.00 Discussion and decisions (all)17.00 - 17.15 Status report on Newsletter & Web (Ubar)17.00 - 17.05 Newsletters (Kobus)17.05 - 17.10 Web Site (Fristacky)17.10 - 17.15 Discussions and decisions (all)
17.15 - 17.30 Short Coffee Break
17.30 - 18.00 Conclusions (Diener)17.30 - 17.45 Summary of decisions for the minutes (Peng)17.45 - 17.55 Final free discussion (all)17.55 Words of thanks (Diener)
Basically VILAB have been focused on three measurableobjectives
• establishing the Virtual Laboratory (Workpackage I)• maintaining and exploiting the VL (Workpackage II)• making VL visible from the outside (Workpackage III).
1. EAS’ tasks to be tackled1.1 R&D activities Task 1: Creating a multimedia based environment
n Creation of the concept (Subtask 1.1)n Setting up the infrastructure for VL (Subtask 1.6)IIS/EAS is R&D partner within the VILAB subprojectn Improving the FPGA Design Flow by Introducing TestActivities led by T TU
IIS/EAS’ contributions are aimed atn pushing the Sub project forming process (weak point as mentioned above)n involving the IAB in the VILAB conception (will be discussed today)n making the Virtual Laboratory visible from the outside
(will be discussed today)ResumeVILAB project management suffers from an insufficient assistance by the partners (tobe discussed today)
11
Role of the VILAB Industrial Advisory Board (IAB) (1)
1. Role of IAB some remarks from the project coordinator’s point ofview
1.1 IAB should be made play a double rolen to help by focusing the main activities on the right
goals(passive - main activity has to come from the partners).n to provide the VILAB project partners with problems
expected to be tackled(active - IAB has to come up with problems born in SME)• the VILAB partners have to contact the national IAB• the active and the passive role - 2 sides of the same
coin• IAB is essential for bridging the gap between the VILAB
R&D results and their exploitation by SMEResume
12
That is the meaning of the statement that IAB has to be involved in improving theVILAB conception.
Role of the VILAB Industrial Advisory Board (IAB) (2)
2. Suggestions next steps• IAB should be provided with the relevant information
on the Sub projects (e.g. VILAB Newsletter or Web Site).• National IAB member’s list of technical problems born
in SME should be presented• IAB member’s list should be discussed with respect to
identifying proper technical problems which can betackled by VILAB Sub projects
• an exploitation plan of R&D results has to bedeveloped
13
• is there a real acceptance for joining IAB by a videoconference ?
Administrative issues
A. Administrative Hints and Remarks (1)
1. Reporting Periods (RP)• Commencement Date: September 01, 1998• No 1: September 01, 1998 to February 28, 1999• No 2: March 01, 1999 to August 31, 1999• No 3: September 01, 1999 to February 29, 2000• No 4: March 01, 2000 to August 31, 2000• No 5: September 01, 2000 to February 28, 2001• No 6: March 01, 2001 to August 31, 2001
14
15
Administrative issues
A. Administrative Hints and Remarks (2)
2. Cost Statements (CS) demands (to be refreshed)• CS have to be provided after each reporting period• CS forms are electronically available (please see my email dated March 02, 1999)• CS forms (original & 3 copies) must be ready for
submitting• CS with "0 cost“ are necessary• CS have to be submitted as a package by the co-
ordinator• CS have to be in Brussels not later than 1 month after R• 1 ECU should be taken as 1 EURO• CS must be provided with the signs as requested by the
EC
16
• Final date for submission: in Dresden by Friday September 10, 1999 at the latest
Administrative issues
A. Administrative Hints and Remarks (3)
3. Annual Progress Report (APR)3.1 General remarks
n each partner is responsible for PPR ready for submittingn sub task driven reports should be preferredn PPR should be drawn up in the context of the WPn results with deliverables should be presented
workpackage by workpackagen APR must be delivered within one month after each
project yearn partners’ draft should be sent electronically to
17
Gabor Peceli for finalizationn Final date for submission:
in Dresden by Friday, September 10 at the latest
Administrative issues
A. Administrative Hints and Remarks (4)
3. Annual Progress Report (APR)3.2 Report focus main report focus has to be given on
n obtaining an improved VILAB conceptn exploiting the virtual environment (first results)n involving the IAB in the VILAB conceptionimproved VILAB concept means forming Sub projectsn focused on the improvement of the VILAB concept,n main ideas of Sub projects should be presentedn a short summary on Sub projects goes into the annexes
18
Administrative issues
A. Administrative Hints and Remarks (5)
3. Annual Progress Report (APR)3.3 SMR and APR strategy to be pursued is to come up with
n Six Monthly Progress Reports (SMR) for EUn Annual Progress Reports (APR) to be submitted to EUn IPI in between SMR and APRAPR can be generated byn updating the SMR based on the IPIeach VILAB partner has the dutyn to enhance his part with the new results achievedn to improve his description (grammar, style, mistakes,
etc.)n to present the deliverables as indicated in the VILAB
WPResume
19
With small modifications the SMR will become the core part of the APR
Administrative issues
A. Administrative Hints and Remarks (6)
3. Annual Progress Report (APR)3.4 MPR organisation of the collaboration
n establishing VILAB Sub projects, involvement of IABn VILAB Newsletters (NL), Web Site, IPIMeetings and fringe meetingsn Opening meeting in Budapest (Sept. 04, 1998 , 1st Project meeting)n Fringe meeting in Bratislava (November 26 - 28, 1998)n Fringe meeting at Linkoping University (Dec. 11, 1998)
20
Administrative issues
A. Administrative Hints and Remarks (7)
3. Annual Progress Report (APR)3.4 MPR
n Fringe meeting at D.A.T.E’ 99 (March 08, 1999)n Project meeting in Warsaw (March 13, 1999, 2nd Project meeting)n fringe meeting at T TU (July 05, 1999)n Project meeting in Linkoping(August 14, 3rd Project meeting)User forum• organised by IET and W TU, Warsaw, March 12, 1999Problemsn what else should be mentioned ?
21
Administrative issues
B. Problems to be cancelled immediately (1)
1. Sub projects (SP) new quality of VILAB has to be demonstrated (SP)the VILAB WP defines three types of outputs or resultsn (a) new tools, interfaces, convertersn (b) co-operative R&D and teaching/qualification
activitiesn (c) co-operative joint designsSP should be based exclusively on the Work Programmesetting up SP cannot be orderedn highly self-organised R&D SP teams must be formedn each partner has to find her/his place in SP team(s)n the great VILAB project work must be balancedthe forming process has to be finished as soon as
possible
22
Administrative issues
B. Problems to be cancelled immediately (2)
2. IPI Intermediate VILAB Progress Information
IPI in between SMR and APR• today the IPI has not been provided completely• IPI should be put into the Newsletters (NL)
(pointers to the Web Site and vice verse)• Web site should offer static information• Newsletter should contain latest results and eventsI would like to decide as suggested above.IPI should be put into the NL byTuesday, August 31, 1999 at the latest
23
Administrative issues
B. Problems to be cancelled immediately (3)
3. General remarks on cooperation problems within VILAB
coordinators’ work needs assistance and supportExperience earned last time• Coordinators’ requests seem not be taken seriouslyExamples:n some IPI are missing up to nown short information on SP requested in Warsaw has never
been providedn at the moment Gabor cannot be contacted
(TU B has summer break now)• no chance to agree with him the decisions necessary
for today
24
Administrative issues
B. Problems to be cancelled immediately (4)
4. Conclusion
I am very sorry to bother you with such symptoms indicating that something in ourcooperation needs changing immediately
I would appreciate it if the VILAB partners would not only do their best for themselvesbut also assist the coordinators to do their job in the same good manner as it isexpected from each.
25
Administrative issues
C. Information & Planning (1)
1. VILAB Review Meeting a mid-term project review is planned for the early 20002.
The reviewer for the VILAB project is Mr Jean MERMETn I contacted him during the D.A.T.E’ 99n I will contact him again at the end of this yearn I will provide him with the technical annex, reports, etc.
as requested in timeWe need proposals / ideas forn Where and when to hold the Review Meeting ?n What should be presented (seen from our point of
view) ?Jean Mermet has the final decision on that
26
Administrative issues
C. Information & Planning (2)
2. VILAB Project Meeting before having the mid-term project review
My imaginationsn date: weeks before the project review takes place (nextyear)n venue: open, to be proposed, decision will be made by Jeann duration: one working day and one half day for fringe activitiesn focus:
final preparation of the Review Meeting and the SMR
27
Words of thanks VILAB Project Meeting, Lingkoping, August 14, 1999
We are very grateful to Zebo and his crew for bothn the extraordinary social event celebrated yesterdayn the organising of the 3rd project meeting in LinkopingWe have learned that success can be organised e.g. byn the commitment of the organisers and participantsI feel, we had success today, hopefully, all of us can
agree.Many thanks to Zebo and all who have been assisting
himThanks to all who made this meeting so impressive.
