XidML OVERVIEW

1
XidML OVERVIEW

• Later, we will discuss in detail the various
  elements of XidML

2
THIS SESSION

• Earlier we introduced XML
• Now we will discuss
• A generic model for FTI
• Why use XML?
• What is XidML?
• Some of the key elements of XidML
• Using XidML for data interchange
• Next, we will introduce the nine key elements
• Later, we will look at each key element in detail

3
DATA MODEL FOR FTI
4
TYPICAL FTI PROJECT

• Multiple users and groups involved
• Different priorities
• Interested in different sorts of data
• Heterogeneous software
• Proprietary file formats
• Different operating systems
• Different programming languages
• Heterogeneous hardware
• Different protocols
• Different H/W interfaces
• High management overhead
• Inter-vendor coordination
• Data compatibility issues
• Costs time and money

5
USER CONCEPT
Parameter Rate Sensor...
Sampled
A 10k PXZ123
data
Magic!
B 10Hx JPY

• Transform a set of data acquisition requirements
  into usable data
• Everything else is noise

6
WHY XML?

• XML is the de facto standard for data exchange
• Maps well onto widely used relational databases
• Naturally supports structured data
• XML is a mature and stable standard
• XML is an open, non-proprietary standard
• A large number of XML tools and utilities exist
• A large body of XML knowledge already exists.
• Familiarity with FTI is not a prerequisite for
  using XML
• Low learning curves for those moving to XML
• XML allows us to define a standard for the FTI
  industry that is both rigorous and flexible

7
WHAT IS XidML?

• An open standard for an eXtensible
  Instrumentation Data exchange Mark-up Language
• An XML schema to address the needs of typical
  FTI projects
• XidML is truly vendor neutral
• Based on generic model of a data acquisition
  system
• Flexible and extensible
• Emphasis on reuse of information
• Designed to be future proof
• Published (www.xidml.org)

8
ON THE SHOULDERS OF GIANTS
9
XidML AS PIZZA

• XidML may restrict the choice of base and sauce
• 8 key ingredients (elements) from which any size
  or style can be made
• However it does come with a large choice of
  toppings
• Cheeses (Packages x 10)
• Savoury (DataLink)
• Gourmet (Algorithms x 14)
• Meats (Instruments x 30)
• It allows you take what you like and add your
  own toppings
• via Addendums or complete new sub-schema
• ..and once the recipe is in XidML you can order
  your pizza from any vendor you like

10
DATA, META DATA, AND
11
THE REQUIREMENTS
"I want to know with 16-bit precision the
vibration pattern up to 20kHz at four points on
this Panel A on the left wing. Strain gages with
a range of 900me should do ... but if any signal
exceeds this I want to know about it!"
We'll worry about the sample rate later when we
are building the PCM stream. We'll also leave the
alarm definition algorithm until later. For now
the signal list might be formalized into...
12
THE SIGNAL LIST

• Expressed in XidML
• Permits error/omission checking
• Will save time later for the FTI group

13
THE SIGNAL LIST
Parameter type is a useful way of storing defaults
This XidML file is incomplete from an
instrumentation point of view. Will add these
details later.
14
THE SAMPLED DATA
Ive got a million different frames and data
structures I have to handlesometimes
simultaneously. I need to maintain a library of
data structures or packages.
XidML can record this information, independent of
a specific program/configuration
15
A PCM PACKAGE
16
A PCM PACKAGE (CONTENT)
17
AN ETHERNET PACKAGE
18
THE SENSORS
Ill release these gages for use on the
project. I can export the conversion information
for the instrumentation guys and save a bunch of
paperwork and checking
XidML use Algorithms for data manipulation
information
19
AN ALGORITHM
20
THE INSTRUMENTATION
Im tasked with the physical setup of the data
acquisition system. Its up to the wiring folk to
decide what sensor connects where. Luckily, all I
have to do is add the instrumentation section to
the XidML file
21
INSTRUMENTATION
22
THE WIRING
I get a XidML file with parameters, hardware
and so on. My job is to fill it out so that it
matches the wiring diagrams I use
Sensor wiring is implicit in the source of a
parameter
23
DEFINING THE PARAMETER SOURCE
24
THE DATA MANAGEMENT
I need to document where a particular parameter
is in the PCM frame. This is easy, because my
frame is already defined. I just need to link a
parameter to a word
25
DEFINING THE PARAMETER DESTINATION
Only one source.but multiple destinations
allowed Destination can be a package, a
datastream, or an Algorithm
26
USING IT ALL AGAIN - AUXILIARY FILES
27
XidML SETUP PROCESS
28
ACQUIRING PCM DATA
29
CONFIGURING A GROUND STATION
Ground station
Software
30
THIS SESSION COVERED

• In this session we discussed
• A generic model for FTI
• Why use XML?
• What is XidML?
• Some of the key elements of XidML
• Using XidML for data interchange
• Next, we will look at the eight key elements
• Later, we will look at each key element in detail

31
END OF SESSION 2