1. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment ECCAIRS Technical Course Provided by the Joint Research Centre - Ispra (Italy) Repository

2. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 2 Repository Definition –A central location that manages occurrence data in a controlled manner for the connecting users Building blocks –Profiles Data Source Security Views Browser Dictionary Other to come –Roles Groups different profiles together as a unit Only one profile of each type, except for the Views –Users Assigned a role, or Assigned individual profiles

3. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 3 Repository Structure Collection of users, roles and profiles –Repeated for each repository –Unlimited amount of each entity –Either a role or a (series of) profiles for each user Repository Users Roles Profiles Profile 1 Profile n Role 1 Role n User 1 User n Profile 8 Role 5 Security Profile Dictionary Profile Views Profile Browser Profile Data Source Profile Profile 6 Profile 3

4. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 4 Users Task –Allow access to ECCAIRS occurrence data Affect –Access to repository thus to occurrence data Highlights –Identified by Name (ID) and password –Assigned to an organisation –Assigned a Role or Assigned a series of Profiles

5. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 5 Roles Task –Group different profiles Highlights –Contains all mandatory profiles –Contains a variable number of View profiles –“All-in-one package” for connecting users Using Roles instead of single Profiles –Quicker set up of many user accounts with same properties –Update to Role instantly affects all assigned users

6. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 6 Data Middleware DCOMMiddleware Applications Exercise 6 Objective –Creating a User Account so that ECCAIRS data can be accessed from a remote workstation Data Middleware Applications DCOM Data Middleware Applications

7. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 7 Exercise 6 Typical implementation –ECCAIRS Repository Server (right) Located in main office or in separate location Acts also as Database Server –ECCAIRS Client (left) Disseminated in various Investigators offices LAN

8. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 8 Exercise 6 Key Players –ECCAIRS Repository Server (right): Stores and Controls Configures DCOM Adds a USER to the REPOSITORY Communicates the –SERVER name and ‘E4ADMINISTRATOR’ password –REPOSITORY name –USER NAME and PASSWORD –ECCAIRS Client (left): Uses Needs to set up a REPOSITORY LINK –With the information above LAN

9. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 9 Exercise 6 Configuration (using Software Installation Manual) –Configure DCOM Configuration –Start the Repository Manager –Create a new user for the student at your left –Start the Browser –Create a new connection to the Repository at your right (obtain the connection data from that student) Use –Execute the count of the default “Select All” query –Ask the student at your right the correct amount of occurrences. Eventually execute the query.

10. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 10 Exercise 6 Result –Server system acts as data provider for client Data Middleware Data Middleware Applications DCOM Applications

11. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 11 Profiles Task –Manage specific functionality of ECCAIRS system Profile Types –Data Source Connects the Repository to a Database –Security Manages access policy –Browser Application Control of Browser’s user interface –Views Expose occurrence data in a structured manner –Dictionary Manages units (m, kg, lb, NM, etc.) –Tunnel Service A bridge between workstation and server for 3 rd party apps

12. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 12 Browser Application Profile Task –Control of Browser user interface Affects –Interaction with application Highlights –Mandatory (1) –Interface colours –Denied operations: what user is not allowed to do –“Start-up” occurrence –“Occurrences list” contents –“Search for duplicates” query during data-entry –De-identification –API configuration

13. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 13 Exercise 7 Objective –Creating a Browser Application profile so that the interface will depend on the connecting user

14. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 14 Exercise 7 Repository Manager –Start Repository Manager Configuration –Select the Repository used in Exercise 6 –Create a New Browser Application profile –Assign this profile to a New user –Start the Browser –Connect to the same Repository as in Exercise 6 Use –Alternatively modify the “Appearance”, the “Denied Operations” and the “Occurrence List” properties of this profile –Log off and log back on to see the result –Connect to the repository of the mentor 

15. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 15 Security Profile Task –Control access to the occurrence data Affects –Interaction between user and data Highlights –Mandatory (1) –Granular Drill down by organisation Drill down by attribute Combination of the above –Safe Proprietary format Encrypted Inherited profile cannot be modified Dedicated section follows here  

16. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 16 Exercise 8 Repository Manager –Start Repository Manager Configuration –Create a New Security profile –Assign this profile to the user created in Exercise 6 –Start the Browser –Connect to the same Repository as in Exercise 6 Use –Execute the default “Select All” query –Watch the result of the security settings on screen.

17. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 17 View Profile Task –Expose data elements in a structured manner Affects –Visualisation of occurrence data Highlights –Mandatory (1…n) –Based on ADREP Taxonomy –Made of Topics and Sections –At least one topic and one section –Complexity can follow function of user Few topics as Enquiry Form for initial investigation More topics during analysis Maximum for experts and administrators

18. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 18 Exercise 9 Objective –Creating a View profile so that the user can enter data for a preliminary investigation report

19. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 19 Exercise 9 Mandatory fields (required for saving) –State Reporting –State File Number –Reporting Organisation Other useful fields –When & Where –Type of occurrence (incident? accident?) –Aircraft data –Injuries –Narratives

20. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 20 Exercise 9 Repository Manager –Start Repository Manager Configuration –Select the Repository used in Exercise 6 –Create a New View profile –Build the view according personal taste –Assign this profile to an existing user –Start the Browser –Connect to the same Repository as in Exercise 6 Use –Execute the count of the default “Select All” query –Switch between groups and views –Edit a record with the newly created view

21. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 21 Data Source Profile Task –Establish connection between ECCAIRS and database Affects –Interaction between repository and RDBMS Highlights –Mandatory (1) only if connecting to RDBMS, not for E4F –One repository server, many Data Source profiles –Each repository can connect to different database server Each connection requires separate Data Source profile One user can use only one Data Source profile –Practical solution: one repository, one database Makes management straightforward No confusion when logging in

22. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 22 Exercise 10 Objective –Creating a Data Source profile so that ECCAIRS data residing on a third system can be accessed from a remote workstation OLEDB Data Middleware Applications Data Middleware Applications Middleware Applications DCOM

23. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 23 Exercise 10 Typical implementation –Database Server (right) Located in separate location –In-house server room –Out-house server farm –ECCAIRS Repository Server (middle) Located in office of ECCAIRS Administrator –ECCAIRS Client (left) Disseminated in various Investigators offices LAN

24. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 24 Exercise 10 Key Players –Database Server (right): Stores Communicates the –SERVER name –DATABASE name –USER NAME and PASSWORD –ECCAIRS Repository Server (middle): Controls Communicates the –SERVER name and ‘E4ADMINISTRATOR’ password –REPOSITORY, USER NAME and PASSWORD –ECCAIRS Client (left): Uses Needs to set up a REPOSITORY LINK LAN

25. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 25 Exercise 10 Repository Manager –Start Repository Manager Configuration –Create a New Data Source profile to the database at your right (obtain the connection data from that student) –Assign this profile to the user created in Exercise 6 –Start the Browser –Connect to the same Repository as in Exercise 6 Use –Execute the count of the default “Select All” query –Ask the second student at your right the correct amount of occurrences. Eventually execute the query.

26. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 26 Exercise 10 Result –Server system acts as bridge between client and data Data Middleware Applications Data Middleware Applications Data OLEDB Middleware DCOM Applications

27. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 27 Exercise 11 Objective –As Exercise 10, but using a New Repository Repository Manager –Start Repository Manager Configuration –Create a New Repository with the mandatory profiles –The Data Source profile must point to the database at your left (obtain the connection data from that student) –Start the Browser –Create a connection to the Repository at your right Use –Execute the count of the default “Select All” query –Ask the second student at your left the correct amount of occurrences. Eventually execute the query.

28. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 28 Dictionary Profile Task –Manage Dictionary decoded values Affects –Management of data Highlights –Not mandatory –Currently limited to measurement units (cm, km, etc) Setting up of metric, imperial, or other systems Company standards

29. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 29 Tunnel Service Profile Task –Create a bridge between client and server for 3 rd part apps Affects –Data transfer by 3 rd party apps Highlights –Not mandatory –Makes it possible to create client-server applications that interact with ECCAIRS –Currently used by TARGA

30. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 30 Repository Server Purpose –ECCAIRS Hub Gathering place for all users –Centralised management for Connecting users Security Database access Benefit –Easy configuration Centrally set and propagated Profiles for users, for data access, for security –Requires entry level hardware –If not running RDBMS Only Repository Server needs RDBMS client software Client workstations do not need RDBMS client software –Centralised control over whole environment

31. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 31 Repository Manager Location: Scenarios Stand-alone (1 user) –On single PC running or connecting to RDBMS –No extra configuration required Workgroup ( < 5 users) –On computer system with strongest hardware –On computer system running database (MSDE) –On computer system acting as proxy to RDBMS Company LAN ( > 2 users) –On computer system running database (RDBMS) –On computer system acting as proxy to RDBMS May reside in other Windows domain –Access through same ECCAIRS client –Only requirement: computer must be “visible”

32. Institute for the Protection and Security of the Citizen HAZAS – Hazard Assessment 32 Profile Distribution Purpose –Create a local copy of assigned profiles –Enforce system settings when working off-line Implementation –After connecting, profiles are copied locally –Upon each connection, copy is cross-checked with original –Updates are automatically applied locally Profile release number Modification date/time