BROADEN VO Requirements
Tom Jackson
BROADEN VO Requirements – NESC Nov 2006
Operational Scenario
Engine flight data
Engine flight data
London Airport
New York Airport
Airline office
GRID
Diagnostics
Centre
Maintenance
Centre
US data centre
European data centre
BROADEN VO Requirements – NESC Nov 2006
Complex Virtual Organisation
Engine
Manufacturer
(RR)
Airline / Maintenance Contractor
(at Airport)
Information / request for advice
Domain Expert (DE)
- engine expert
Dowload
Engine
Data
Investigate using tools
Provide
Diagnosis
/ Prognosis
/ Advice
Remote / Distributed
Tools and Services
Perform
Minor Repair
Local
Diagnosis
Upload
Engine
Data
Ground
Support
System
DAME
Diagnosis
Engine Data Center (EDC) - DS&S
Service Data Manager (SDM) - RR
Request advice
from MA
Maintenance
Engineer (ME)
Update Engine Records
Distributed Aircraft
Maintenance Environment (DAME)
- Miscellaneous Providers.
Investigate using
tools
Update Engine
Record
Remove engine and
dispatch for major overhaul
Request advice
from DE
Return overhauled
engine to service
Information / request
for advice
Provide
Diagnosis
/ Prognosis
/ Advice
Update Engine
Record
Update Engine
Records
Maintenance Analyst (MA)
- maintenance expert
Data Center
(DS&S)
Engine Maintenance
Repair and Overhaul
(MRO) Facility
(RR / Contractor)
BROADEN VO Requirements – NESC Nov 2006
Virtual Organisation
The DAME Virtual Organisation consists of:
– Diagnostics users (3 Roles)
– A diagnostics task
Airline
– Processing services, such as:
• Signal processing
• Pattern matching
• Case-based reasoning
– Distributed engine data
Other Airlines
Engine Lessee
1
Engine Data
employs
Other Airline Data
reads
reads
found in
<<organization unit>>
DAME Virtual Organisation
1..n
1
create
0..n
Processing Service
1
0..n
Maintenance Engineer
1..n
Problem
1
get diagnosis
– Compute Resources
1..n
1
1
0..n
detailed analysis
employs
0..n
1..n
executed by
invoke
resolve
0..n
1
owns
owns
Workflow Service
0..n
Compute Resource
diagnosis
employs
0..n
1..n
Fleet Maintenance Management
Maintenance Analyst
BROADEN VO Requirements – NESC Nov 2006
1
Engine Manufacturer
Domain Expert
Grid Portal for VO
The portal provides a single, secure, sign-on site for
the virtual diagnosis workbench
BROADEN VO Requirements – NESC Nov 2006
Escalation Process
Portal provides role based access to diagnostic data
and tools
Maintenance Engineer (ME)
BROADEN VO Requirements – NESC Nov 2006
Maintenance Analyst (MA)
Maintenance Analyst
• Work list of escalated engines
• Can work on multiple engines simultaneously
Work list
launches the
toolbench
BROADEN VO Requirements – NESC Nov 2006
Workflow and RB access
• Workflow Engine provides
management of manual and
automated workflows.
• Also handles certification
and role management
Browser
Portal
Role
Database
MyProxy
Server
Event
Generator
Engine
Data Store
SDM to
XTO
XTO
Broker
BROADEN VO Requirements – NESC Nov 2006
Workflow
Credential
Workflow
Manager
Aura-G
CBR
Engine
Model
Role Based Access Management
• Role-based access control in
the portal is used to limit
interface access.
• Whilst VOs are:
– specified in the Role
database, and
– instantiated in the Case
database.
Browser
Role
database
Portal
Case
database
Workflow
Manager
Engine
Data Store
Workflow
Advisor
Feature
Detection
Pattern
Matching
Broker
• The Workflow Manager
coordinates access to the grid
services.
BROADEN VO Requirements – NESC Nov 2006
White Rose Grid
Workflow
Credential
CBR
Engine
Model
Pattern Match Control
SRB
Stored Data
• The SDE interfaces
to the PMC middleware;
• PMC provides:
– Distributed search
– Interface to data archive
system (SRB or other)
– Scalability
– Robustness
Engine Data
Raw Engine Data
Engine Data
Storage Service
Raw Data
Tracked Orders
Signal Data
Explorer
Scope
Constraints
Store()
Extractor
Search()
GetResults()
Pattern Match Control (PMC)
‘master’ node
NodeSearch()
ReturnResults()
Store()
Search() ReturnResults()
Pattern Matching Service
BROADEN VO Requirements – NESC Nov 2006
Search
Constraints
Builder
Other PMC
nodes
PMC
PMC
PMC cont
• PMC architecture has been developed on business premise of
remote data.
• E.g. Airports act as data repositories for Engine health data
• Data stored where it arrives
DAME Airport Node - Gatwick
• SRB provides hugely scalable virtual
DAME Airport Node - Munich
catalogue & index system
Servic
es Node - JFK
DAME Airport
•Pattern
Servic
• Global data view is virtualised
Match
esNode
DAME Airport
- Heathrow
Servic
• Data is only processed locally
Control
es
Services
Catalogue
• But can be accessed globally
•Data
•Pattern Match
Extractor
Control
• SRB security protocols provide
•Data Extractor
SRB
•Pattern
partitioning and access control
•Pattern Match
Engines
Match
Engines
Tracked
Orders
BROADEN VO Requirements – NESC Nov 2006
MCAT
Signal
Data
Explorer
The node receiving the
request becomes the
‘master’ for a search.
The master PMC service
replicates the search
request to all other nodes.
Master Node
Search(…)
PMC
Slave Node
NodeSearch(…)
Search(…)
Signal Data Explorer
(Client Application)
In addition, the master PMC service
initiates a search by a Pattern
Matching Engine at that node.
PMC
Search(…
Slave PMC services
) initiate searches
also
by local PME.
Pattern Match
Engine
Pattern Match
Engine
Pattern Match Engines
request and stream data
from SRB.
SRB
SRB
Heathrow
Gatwick
BROADEN VO Requirements – NESC Nov 2006
Provenance and Audits
23456
Tools
SDE
CBR
QUICK
Model
Task List
23756
93496
83496
73496
Analysis history for engine:
Serial number: 23756
Type: X100.
Flight / Test: Ll573
QUICK Detector Sum
mary and Event List Received 11/09/2006
QUICK Detector
Summary
QUICK Event
List
Initial Assessment.
User 4563. Date 11/09/2006 Time: 09:26 GMT
Observations: LP1 anomalous signature- but within limits.
Action: further analysis necessary– not urgent.
Note.
User 4890. Date 11/09/2006 Time: 12:35 GMT
Will check to see if signature has occurred before.
SDE Analysis
Results
BROADEN VO Requirements – NESC Nov 2006
Use of provenance
• Workflow Advisor provides workflow process
support, based on workflow case histories and
provenance data
• E.g. in bird-strike fault scenario, suggests launch of
engine model, and investigate P30 performance
parameter
BROADEN VO Requirements – NESC Nov 2006
Summary
• Need for dynamic, flexible VO has been central to
DAME/BROADEN objectives.
• Key issues:
– Distributed data management and access control
– Role based access to services
– Provenance and audit trails
• Solution has required complex mix of engineered
services.
• Some aspects currently scalable (e.g. SRB), others
not.
BROADEN VO Requirements – NESC Nov 2006