PIE migration: new interface with the same functionalities

1
PIE migrationnew 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
• QA

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

4
Introduction

• PIE and procedures
• Communication improved between services
• Responsibilities and task defined across services
• AIS applications evaluated and updated

5
Reasons for Migration

• Very sensitive to your machines configuration
• Does not work on Mac...
• Very sensitive to OUR OracleHR configuration
• Data placed in OracleHR 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)

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 OracleHR via standard interface
• Minimize synchronization process
• Easier to maintain, database application upgrade
  proof

7
Looking for solutions

• Keep PIE functionalities
• Lego building blocks a little bit of
  additional development

8
SolutionsPersons screens
Done via EDH screens
Read only
Read only
Read only
9
Fundamental changes

• Persons screens
• Access Rights
• 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

10
Closer look

• Demo

11
SolutionsInstitutes Experiments screens
Done via Foundation screens
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

13
Closer look

• Demo

14
What are the next steps?

• Tests by users (well 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

15
Q A