1. PIE migration: new interface with the same functionalities
Derek Mathieson
Jozef Dransfield
Pavel Razumovskiy
Piotr Sowinski
Wim Van Leersum
IT-AIS-EB :
IT-AIS-F :

2. Agenda Introduction Reasons for migration Looking for solutions
Implementation
Demo
Q&A
JOZEF SPEAKS

3. Introduction PIE purpose
A single coherent set of high quality data for Experiments, Collaborations and People Participating in these activities.
Intuitive
Reduced Oracle HR complexity
JOZEF SPEAKS
as most of you already know PIE stands for People , Institutes and Experiments...
Tapplication provides a single coherent set of high quality data concerning Experiments, Collaboration, Institutes and People participating in these activities, to both Collaborations and the CERN central services

4. Introduction PIE and procedures
Communication improved between services
Responsibilities and task defined across services
AIS applications evaluated and updated
JOZEF SPEAKS
When pie was created no procedures where defined, the procedures grew from the PIE development and the pie users and are now securily established.
Communication improved between services
Each experiment was working seperately with its own data. PIE moved to common way share etc
Responsibilities and task defined across services
When a primary parctipation is defined what does it mean what does it imply (standard ised semantics)
AIS applications evaluated and updated
The applications Greybook Pie and HRT where changed to meet all the user requirements.

5. Reasons for Migration Very sensitive to your machine’s configuration
Does not work on Mac...
Very sensitive to OUR Oracle*HR configuration
Data placed in Oracle*HR via home made interface
Support problem: depending on one person
Overnight extraction to FOUNDATION database
Data propagation delays
Synchronization issues
Incoherence (example: data concerning institutes is initially entered in PIE and after transfer from hr is completed in Foundation)
JOZEF SPEAKS

6. Looking for solutions Avoid dependencies on user machines
No local machine installation
Works on Mac / PC / Linux
Works on most browsers
Data placed in Oracle*HR via standard interface
Minimize synchronization process
Easier to maintain, database application upgrade proof
JOZEF SPEAKS

7. Looking for solutions Keep PIE functionalities
“Lego building blocks” + a little bit of additional development
JOZEF SPEAKS

8. Solutions: Persons’ screens
Done via EDH screens
Read only
HRT
Read only
Read only
JOZEF
Overview is not used any more in PIE
Address we do not implemented it.
Access rights is in HRT
View access rights is the same that access rights
We have asked PER to include origin institute and costing (access read-only) in HRT-PIE
Done via Foundation screen

9. Fundamental changes Persons’ screens Access Rights Auditing
By Screen (Not Experiment based)
Controlled through EDH Access Rights
Auditing
Shows ALL changes by Every User
Important: Do not share your password
New Look and Feel
JOZEF
If you have access you can edit anyone in any division, unlike previously.
Access can be turned on or off by screen, DAO’s and GAOS are given access by default to the screens they need and other people can be given access through the ACCEdit screen.
Now all changes are stored, and viewable by people with the access right.
Standard Oracle APIs
Future oracle releases will be safe, because the API will be maintained by Oracle.

10. Closer look
Demo

11. Solutions: Institutes & Experiments screens
Foundation
Done via Foundation screens
Piotr SPEAKS
Done via Foundation screens

12. Fundamental changes – cont
Institutes and Experiments
Access to application given via foundation menu
When modifying data verification against assigned roles – standard mechanism used in Foundation EXAMPLE
Done at the table level
Gives possibility of granting read-only access
Audit tool
who, when, what , old and new values
Simple lookup
History of changes
users of the tool to be defined
Piotr SPEAKS

13. Closer look
Demo
Piotr SPEAKS

14. What are the next steps? Tests by users (we’ll send you URL)
Collect key users feedback (following 2 weeks)
Modifications if neccesary
PIE users presentation / training (End of August)
Production (End of August)
Running in parallel with original PIE for a short period
Piotr SPEAKS

15. Q & A
USERS speak