CTC-220 Sage

3 GE Aircraft Engines EFG
SAGE
Training Manual
February, 2002
GE/CFMI Proprietary Information CTC-220
Proprietary Information
Statement
The information contained in this document is GE Proprietary Information and is
disclosed in confidence. It is the property of GE and shall not be used, disclosed to
others or reproduced without the express written consent of GE. If consent is given
for reproduction in whole or in part, this notice and the notice set forth on each page
of this document shall appear in any such reproduction, in whole or in part. The
information contained in this document may also be controlled by U.S. export
control laws. Unauthorized export or re-export is prohibited.
Copyright  1998 by GE Aircraft Engines and CFM International
Technical Data General License TSU Applicable
All Rights Reserved
GE/CFMI Proprietary Information

3 GE Aircraft Engines
Table of Contents EFG
1 Overview 18 Interactive Reports

2 The SAGE System 19 Analyze Alerts
3 Hardware / Software 20 Stored Record Maintenance
4 Installation Considerations 21 On Wing Reprocessing
5 Database & ODBC 22 Fleet History
5.1 SAGE ODBC Functionality 23 Parameter Library
6 SAGE Installation 24 Maintain Smoothing
7 SAGE Input Data 25 Maintain Alerting
8 SAGE “Applications” 26 Maintain System Data
9 History File Conversion 27 Database Maintenance
10 Conversion Tools 28 SAGE Security
11 Error Files 29 Un-install Process
12 Interactive Features 30 SAGE Support
13 Fleet Management 31 Frequently used Terms
14 Enter Data 32 Aircraft / Engine Types
15 Browse Input 33 SAGE Input Database
16 Input Data Formats 34 Families & Types
17 On Wing Processing

Fundamentals of SAGE Operation
Class Objectives
✈ Goal -- A smooth transition to SAGE
✽ By helping you achieve a basic knowledge of SAGE
✽ By helping you gain familiarity & comfort with the operation of SAGE
✈ Plan -- Focus primarily on normal usage & getting started

✽ Demonstrate and perform normal SAGE operations
✽ Introduce other SAGE capabilities and maintenance activities
(Focus on how to use SAGE, not on how to monitor engines)
✈ Comments:
✽ SAGE may initially appear complex, with too much flexibility.
✽ But not all flexibility & capabilities are needed initially -- explore later.
✽ Default settings are basically the same as in ADEPT.
✽ Interpretation of output is similar to other monitoring programs.
✽ When familiar with SAGE, it should be easy to use.
Overview of SAGE
GEAE/CFMI ‘s
System for the Analysis of Gas turbine Engines
Overview
February 2002 GE/CFMI Proprietary Information Page 1
SAGE - System for the Analysis of Gas turbine Engines
Engine Condition Monitoring System :
✽ Interactive, “windows-like” monitoring system

✽ Used to monitor CF6, CFM56, and GE90 engines, CF34
Use routinely to monitor current “health” of engines:
✽ Assess and trend overall engine performance

✽ Judge suitability for operation / detect abnormal shifts in trends
✽ Provide longer-term trends to manage engine maintenance
SAGE
Overview
Sage typical window
Overview
Description of SAGE
Monitoring system in state-of-the-art environment
✽ Combines elements of old softwares (ADEPT & GEM)
✽ Takes advantage of today’s computing configurations

◆ “windows” look and feel (Windows 95 or NT)
◆ interactive system using “Graphical User Interfaces”
◆ true database (instead of limited access history file)
✽ Runs on a PC ….. either stand-alone or networked
New program -- more user-friendly
✽ Expanded flexibility to address user requests
✽ Use “as delivered” or as “customized” by the user

Overview
SAGE Monitoring System

Provides basic monitoring functionality
✽ Uses existing analytical routines to assess performance

✽ Enhances automatic trend “alerting” features
✽ Improves data handling (reprocessing, accessibility, etc.)
Enhances monitoring system
✽ Can be configured & customized to suit individual users

(e.g. how much data & what parameters to store)
✽ Database permits more control, capability, flexibility, …
✽ Designed for use in computer network (optional installation)
✽ Improved output capability -- easier to view / export data
Overview
SAGE Monitoring Functionality
Cruise Takeoff
✽ Cruise Trending ✽ Takeoff Performance
(OATL /EGT Margin)
✽ Oil Monitoring
✽ Takeoff Derate
✽ Vibration Monitoring
✽ Divergence
✽ Margins for MCT Operation
Not available in ADEPT
(ETOPS)
Climb (only CFM56-3 & GE90)
✽ VSV Monitoring
✽ OATL with Cruise Update (ETOPS)
✽ Divergence ✽ Climb Derate
✽ Divergence
Basic
Basiccruise
cruiseand
andtakeoff
takeofffunctionality
functionalityprovided
provided
for
forall
allproduction
productionCF6,
CF6,CFM56,
CFM56,&&GE90
GE90engine
enginemodels
models
Overview
SAGE is Not … a Single Program
SAGE is made up of
many programs
(or executables)
Each SAGE “program”

is run independently,
- either “interactively”
or
- in the “background”
Overview
Airline Feedback
Three regional meetings for Introduction:
✈ Singapore (Jan. 17, 1995)
✽ 15 airlines, 34 airline attendees
✈ Frankfurt (Jan. 19, 1995)
✈ Cincinnati (Jan. 19, 1995)
“User Reviewer” Volunteers: Review meeting for GEM Users:

✈ “Reviewer” Sites (Jan., 1995 - present) ✈ Cincinnati (June 22-23, 1997)
✽ 20 airlines ✽ 8 airlines, 16 airline attendees
Review meeting for “Beta” Functionality: SAGE Installation Seminar:

✈ Cincinnati (Dec. 9-13, 1996) ✈ Cincinnati (July 22-23, 1998)
✽ 15 airlines, 23 airline attendees ✽ 21 airlines, 34 airline attendees
Airlines
Airlineswere
wereinvolved
involved in
indevelopment
development
Overview
The SAGE System
SAGE System
SAGE System
SAGE is made up of
many programs
(or executables)
Each SAGE “program”

is run independently,
- either “interactively”
or
- automatically in the
“background”.
SAGE System
Categories of SAGE Programs

Fleet
Fleet Management Data Analysis
Interactive Reports
Fleet History
“Set-up” Programs Analyze Alerts
Installation Data Processing
Data Entry
Create Database OnWing Processing
Enter Data
Install SAGE AutoSAGE
Browse Input
UnInstall SAGE
Data Modification
Configuration Stored Record Maint.
Conversion
Maintain System Data OnWing Reprocessing
History File Convert
Maintain Alerting
GEM AIF to SAGE Input
Maintain Smoothing
Parameter Library
System Security
SAGE System
Normal SAGE Usage Flow-path
Other Frequently Used Programs
AutoSAGE
Data Source Enter Data
Fleet Management
Automatic Maintain Alerting

Data Entry
OnWing Re-Processing
Stored Record Maint.

OnWing Processing
Less Frequently Used

•Browse Input
•Fleet History
Analyze Alerts Interactive Reports •History File Converter
•Maintain System Data
- Performed by SAGE •Maintain Smoothing
•Parameter Library
- Performed by Airline •SAGE Help
•SAGE System Security
SAGE System
“Fleet” Program
Fleet Management
✽ Add, Modify, Delete Aircraft and
Engines
✽ Select Analytical Functions
✽ Install / Remove Engines
✽ Delete Installation Levels
✽ Set Incident Flag
SAGE System
Fleet program
➥ Fleet History
✽ Display Installation History for an Engine or an Aircraft
SAGE System
“Data Entry” Programs

Enter Data
Manual Data Entry of:
✽ Flight Data
✽ Engine Changes
(Removals & installations)
✽ Line Maintenance
✽ Times & Cycles
➥ Possibilities
➥ User control of entry sequence
➥ User control of required parameters
➥ User control of parameter names
➥ User control of range checking
✽ ( by using the “Parameter Library”)
ADEPT Capability
SAGE System
OnWing Processing
Automated
Data Entry
Auto Reports
Auto Reports
(Optional)
(Optional)
Input Files
OnWing Processing
Third Party Database :

-Access
-Oracle
-…..
Report Files
Error log
Analyse Alerts
Analyse Alerts
SAGE System
“Data Processing” Programs

AutoSAGE
Scheduler which controls when and under what conditions
OnWing Processing will automatically run:
◆ At fixed intervals or at specific times
◆ On user selected days of the week
The user can temporarily

disable the scheduler when
the automatic processing is
not desired.
SAGE System
“Data Analysis” Programs

Interactive Reports
✽ Generate and/or view ADEPT/GEM style trend/tabular reports
✽ Generate graphical & tabular reports for user selected parameters
✽ View parameter histogram (accumulator)
✽ Export data to spreadsheet
SAGE System
“Data Analysis” Programs

Analyze Alerts
✽ Engine Alert Summary
✽ Alert Details
✽ Fleet Alert Summary
✽ Watch List
✽ Alert Status
✽ Engine History
✽ Engine Notes
✽ Reports on Alert Output
Alert: A message generated by SAGE to

indicate that a change, which may be
of interest to the user, has been detected.
(a change in one or more calculated or
measured parameters)
SAGE System
“Data Modification” Programs
Stored Record Maintenance
Maintenance of any input and
calculated data values.
◆ Delete Flight, Alert Output,
Initialization, or Compressed Records
◆ Modify Flight Input, Engine Notes,
Engine Maintenance, and
Engine Times & Cycles
OnWing Reprocessing
✽ Select flight records for:
◆ Reprocessing
◆ Compression
◆ Re-Initialization
SAGE System
“Configuration” Programs
Maintain System Data
User control of quantities of data stored
Maintain Alerting
✽ Create, modify, delete alerts &
alert limits
✽ Attach categories & reports to alerts
Maintain Smoothing
User control of smoothing constants
SAGE System
and parameters to be smoothed
Parameter Library
✽ Create Parameter Associations
◆ Parameters to store for each family
(both input and output)
◆ Units
✽ Manage Parameters for “Enter Data”

(manual data entry)
◆ Entry Sequence
◆ Minimum/Maximum Range Checking
◆ Required Parameters
✽ Maintain Parameter Definitions

◆ Add parameters
◆ Delete parameters
◆ Modify parameters (units, alias)
SAGE System
System Security
✽ Setup / Modify access permission for each SAGE user
✽ Create Program Dependencies
Reader Only reads

User Writes minimally
Expert Writes and controls
Admin Writes, controls and authorizes
➥ Each SAGE program & User assigned one security level, which is user controllable.
➥ Security System controls SAGE access by name and security level.
➥ Security levels stored in database.
➥ Program dependencies exist and can be modified.
➥ View Execution Status.
➥ Security Enforcement can be turned off.
SAGE System
“Installation” Programs
Create Database
Copy Access 7 file or Oracle script
(others available on request)
Install SAGE
User selected programs for client or
server installation
User selected aircraft/engines
UnInstall SAGE
Remove all SAGE directories and
SAGE System
files except SAGE database
Hardware and Software Requirements
Installation Considerations GE/CFMI Proprietary Information Page 1

Hardware Requirements
Minimum PC Requirements
◆ 100 MHz Pentium Processor
◆ 32Mb Memory
◆ 500Mb of disk available for SAGE
◆ Monitor with 1024x768 resolution
◆ CD-ROM access (for installation purposes)
Minimum UNIX Requirements

◆ 64Mb Memory
◆ 1Gb of disk available for SAGE
◆ 100 MHz
◆ CD-ROM access
Recommend
Recommendmore
morememory
memoryand
andmore
moreMHz,
MHz,whenever
wheneverpossible
possible!!
Hardware Requirements
“Minimum” system capability will not be sufficient when:
✽ Processing of more than 100 flight records at a time
✽ Server installations with more than 5 clients
✽ SAGE processing with other PC software executing

(e.g. email, Word, Excel, etc.)
✽ All SAGE interactive programs, background processing programs

and database reside on one desktop -- if processing large
quantities of data.
Larger
Largerfleets
fleetsrequire
requiremore
morememory
memoryand
andprocessor
processorspeed.
speed.
Software Requirements
Interactive Processing
✽ Win95 or WinNT operating system
(no Interactive capability on UNIX)
✽ SQL Compliant Database
(examples: MS Access, Oracle, Sybase, DB2)
✽ Open ODBC Driver
(Level 2.0 or higher)
Background Processing (OnWing Processing)

✽ UNIX, Win95, or WinNT operating system
✽ SQL Compliant Database
✽ Open ODBC driver
(Level 2.0 or higher)

Installation Considerations

SAGE Philosophy
Design Philosophy
] Bring the user interaction to the user’s desktop
] Operate on a desktop system
(such as a PC or UNIX workstation)
] Take advantage of today’s PC and workstation configurations
(Windows 95 or Windows NT, multi-tasking, multi-processing)
Computer Operating Environments

] Stand-alone
All software and database resident on one PC
] Networked
“User-selected” modules on each desktop, with a
networked database

SAGE Elements and System Requirements

å SAGE contains:
] interactive programs
] background processing programs
Elements
] analytical algorithms
å User provides:
] a 3rd party database
] ODBC driver compatible with the database
All interactive programs must reside on PC platforms

System Requirements
å
(either Windows 95 or Windows NT )
å Each desktop, which executes any SAGE program, must have an

ODBC driver to access the database.
å File transfer between platforms is the user’s responsibility.

Topics
å Hardware and Software Requirements
å Interactive versus Background Processing

] PC versus UNIX
å Desktop versus PC Servers

Interactive versus Background Processing
(PC versus UNIX)

SAGE Elements
Ê SAGE Interactive Programs SAGE
] must reside on Win95 or WinNT platform
Ë SAGE background processing programs

] perform analytical calculations
] can reside on Win95, WinNT or Unix
Ì A 3rd party database (e.g., Access, ORACLE, etc.)

] provided by the user
] can reside on Win95, WinNT, Unix or Mainframe
Í An ODBC driver compatible with the database

] provided by the user
] must reside on each desktop that executes any SAGE program

1. Interactive Programs Fleet

Interactive Reports
Fleet History
å Must reside on Win95 or WinNT Data Processing

Analyze Alerts
Data Entry
OnWing Processing
Enter Data
å Executed on demand Browse Input

AutoSAGE
Data Modification
Configuration
å Executed by an individual user Maintain System Data
Stored Record Maint.
OnWing Reprocessing
Maintain Alerting
Maintain Smoothing
Parameter Library
The Interactive Programs are: System Security
Analyze Alerts Maintain System Data

Browse Input Maintain Alerting
Enter Data Maintain Smoothing
Fleet History OnWing Re-processing
Fleet Management Parameter Library
History File Conversion (Import) System Security
Interactive Reports Stored Record Maintenance
2. Background Processing Programs

Fleet
Interactive Reports
Fleet History
å Could reside on Win95, Data Processing

Analyze Alerts
Data Entry
WinNT, or UNIX Enter Data
OnWing Processing
AutoSAGE
Browse Input
å Executed on demand or Data Modification

Configuration Stored Record Maint.
automatically Maintain System Data OnWing Reprocessing
Maintain Alerting
Maintain Smoothing
Parameter Library
The programs are: System Security
å OnWing Processing
] Input Processor å History File Conversion
] Single Record Function (Export)
] Initialization/Smoothing å GEM AIF to IP Conversion
] Alerting
] Compression
å Automatic Reporting
å AutoSAGE
3. SAGE Database
å Database can reside on:
] Win95
] WinNT
] UNIX
] MVS (if DB2)
å SQL Compliant (Structured Query Language)
å Supports ODBC Level 2 standards
GE/CFMI provides: User provides:

] Access 95 database ] database software
] Oracle 7 creation script ] database access software for network
or (i.e. tcp/ip, SQLNet)
] Creation script from ErWin 3.5 ] all database maintenance and backup

Database Issues
å Possible Databases
] Oracle
] DB2
] Sybase
] PC Databases, e.g. MS Access
å Spreadsheet is available to help estimate DB size

å ODBC driver can be obtained from DB vendor
or from a 3rd party vendor, e.g. Intersolv
Choose
Choosethe
theDatabase
Databasewith
withwhich
whichyour
yourcompany
companyis
ismost
mostfamiliar!
familiar!

4. ODBC Driver
ODBC -- Open Data Base Connectivity
å Driver typically provided by database software vendor
å Provides generic access to vendor without

vendor-specific interface
å Must be ODBC Level 2 or higher

Supports referential integrity, cascade deletes, cascade
updates, etc.

PC versus Unix
å Background Processing Programs and Database are the
only elements of SAGE that can reside on a Unix system
å When to use Unix:

] To take advantage of existing processes
u Daily/weekly backups
u Disaster recovery procedures
] To take advantage of Unix databases
u Unix databases may be more robust
u Unix databases may have additional capability
u Unix databases have strong multi-user access capability
] To take advantage of an airline’s existing Unix knowledge
] Unix platforms are more stable that PC platforms

SAGE Programs
Must reside on Win95 or NT Could reside on UNIX, Win95 or NT
å Analyze Alerts å OnWing Processing
å Browse Input u Input Processor
å Enter Data u Single Record Function
å Fleet History u Initialization/Smoothing
å Fleet Management u Alerting
u Compression
å History File Conversion (Import)
å Automatic Reporting
å Interactive Reports
å AutoSAGE
å Maintain Alerting
å Maintain Smoothing
å Maintain System Data
å OnWing Reprocessing
å Parameter Library
å System Security
å Stored Record Maintenance
Database
Databasecan
canreside
resideon
onUNIX,
UNIX,Win95,
Win95,WinNT,
WinNT,or
orMVS
MVS(if
(ifDB2)
DB2)
PC Client with PC Server

å Purpose:
] To create superset of SAGE programs
u Install all SAGE programs on server
u Each user installs a subset from the server installation
] To reduce the disk space required for each SAGE user

u Executables and supporting libraries reside on the server
] To allow the SAGE Programs to reside on one “server”

u Client installs can be installed to access all or a subset of the
Server’s SAGE programs
å PC Server could contain JUST interactive programs.

] Database and/or background processing may be on other equipment.

Summary
] Interactive Programs MUST reside on Win95 or

WinNT platform
] Background Processing Programs can reside on

Win95, WinNT, or UNIX platforms
] Database(s) can reside on Win95, WinNT, UNIX, or

mainframe platforms
(File transfer between platforms is the user’s responsibility.)

Database
&
ODBC Drivers
Database & ODBC GE/CFMI Proprietary Information Page 1

February 2002
Database & ODBC Drivers
✈ The Database/ODBC Relationship
✈ Searching for an ODBC Driver
✈ Creating SAGE ODBC Driver Definition
✈ Attaching a Database to the SAGE ODBC

Driver Definition

February 2002
The Database/ODBC Relationship
SAGE ODBC
User Database
SAGE
✈ SAGE communicates with database via generic interface
✽ Industry accepted interface
✽ Growth capability built in for other supported database software
✽ Database file location independent of SAGE software location
✈ Generic Interface is an Open ODBC driver (level 2.0 or higher)

✈ Database is a SQL compliant database

February 2002
Searching for an ODBC Driver
32 bit ODBC
Administrator icon
✈✈ 32
32bit
bitODBC
ODBCAdministrator
AdministratorIcon
Icon
16 bit ODBC
✽✽ Required
RequiredforforSAGE
SAGEinstallation
installation(not
(not16 16bit)
Administrator icon
bit)
✽✽ IfIfnot
notfound,
found,install
installper
perMicrosoft
Microsoft
Add/Remove Instructions
Add/Remove Instructions

February 2002
Creating SAGE ODBC Driver Definition
Provides driver definition for SAGE Use
1)1) Double
Doubleclick
clickon
on 2)2)Click
Clickon
on"Add"
"Add"ininData
Data
"32 bit ODBC" icon
"32 bit ODBC" icon Sources Window
Sources Window

February 2002
3)3)Select
Select"Microsoft
"MicrosoftAccess
AccessDriver"
Driver"
then click on ”Finish" in
then click on ”Finish" in
Create
CreateNew
NewData
DataSource
Sourcewindow
window

February 2002
(continued)
5)5) Select
Selectthe
thedata
database
base
by clicking on Select
by clicking on Select

February 2002

(continued)
6)6) InInthe
theC:\sage\Sage_Database
C:\sage\Sage_Database folder
folder
select
select the data base in this case: :
the data base in this case
Sage_Training.mdb
Sage_Training.mdb
Then
Thenclick
clickOK
OK

February 2002

(continued) 7)7) InInthe
theData
DataSource
SourceName
Namefield,
field,
type a name in this case
type a name in this case ::
The data base path is copied.
The data base path is copied.
- -Sage_training
Sage_training
The
TheDSN
DSNhas
hasto
tostart
startby
bySage_...
Sage_...
Then
Thenclick
clickOK
OK

February 2002

(continued)
8)8) The
TheDSN
DSN: :Sage
Sagetraining
trainingisiscreated.
created.
To
Tofinish
finishclick
clickOK
OK

February 2002
SAGE ODBC Functionality
SAGE ODBC Functionality

October 1998
3 GE Aircraft Engines Required ODBC Functionality for SAGE EFG
I. SQL Compliant Database Management
Required DDL and DML Support (continued)
System (DBMS)
II. Support for ODBC 2.0 or higher drivers 11) Null values
12) Fetch
III. Support for the following datatypes: 13) Searched Delete -- Delete from ... where ...
Integer, Float, Char, long char, memo, 14) Searched Update -- Update from ... where ...
varchar, Date, datetime 15) Insert ... into ... where
16) Cascade Delete (with primary key and foreign key
IV. Support for the following DDL and DML constraints)
including:
17) Cascade Update (with primary key and foreign key
1) Alter table -- ADD/Drop constraints)
2) Create (Unique) Index / Drop Index 18) Begin transaction ... End transaction
3) Create Table / Drop Table: 19) Rollback
• Not null 20) Locking mechanism
• Unique
21) Aggregate functions:
• Primary Key
• AVG
• Foreign Key
• COUNT
4) Create View / Drop View • MAX
5) Grant • MIN
• SUM
6) Connect, Open, Close
• DISTINCT
7) Commit
8) Select (all) (distinct) ... from ... where ...
9) Select (all) (distinct) ... from ... where ... group by ...
having ...
10) Subquery
GE/CFMI Proprietary Information § Technical Data General License TSU Applicable
(((
SAGE ODBC Functionality 1 Appendix B

SAGE Install
Appendix E
Install GE/CFMI Proprietary Information
Page 1
February 2002
Three (3) Types of Installs

➀ Local Install on Individual PC (could be a server)
➁ Server Install
✽ From the Server
✽ From a client PC to a server mapped disk
➂ Client Install
✽ Need to perform Server install first
✽ Executables stay on server
✽ Preferences are on client machine
Appendix E
Page 2
February 2002
Installation Process
❶Reboot your computer
❷Start the SAGE installation process.
❸Install the SAGE database.
❹Install the SAGE software system.
❺Configure the SAGE database.
Appendix E
Page 3
February 2002
Local “Full” Installation

Road Map
Install ODBC Install
driver database - Performed by SAGE
Access Other - Performed by Airline

database database
Move DB file
to DB server
Create database
Install Full on DB server
SAGE System
Create ODBC
Configure DSN on PC
database
Appendix E
Page 4
February 2002
Local “Custom” Installation
Road Map
Install ODBC Install
driver database - Performed by SAGE
Access Other - Performed by Airline

database database
Move DB file
Install Custom to DB server
SAGE System
Create database
on DB server
No GUI’s & Some GUI’s & Some GUI’s & All GUI’s & 1
All processing on server PC but
OnWing1 OnWing2 no OnWing3 no OnWing4 Create ODBC won’t use any the tools
2
DSN on PC All processing on PC but won’t
use all the tools
3
Processing not on PC and won’t
Configure use all the tools
4
database Processing not on PC and will
use all the tools
Appendix E
Page 5
February 2002
Server/Client Installation
Road Map
Same as Local
Full Install on - Performed by SAGE
Server
- Performed by Airline
Perform Client
Install on each
Client PC
Execute Client
Install program
on mapped
server disk
Install ODBC
driver on each
Client PC
Create ODBC
DSN on each
Client PC
Appendix E
Page 6
February 2002
Local Install
1. Reboot you machine and re-login.
Appendix E
Page 7
February 2002
Local Install (continued)

2. Start the Install process
Α Insert the SAGE CD into your CD-ROM tray.
Β By using the MS Explorer, traverse to the CD-ROM drive.
Χ Double click “setup.exe”.
Appendix E
Page 8
February 2002

Install Database
3. Select “Install SAGE Databases”
Appendix E
Page 9
February 2002

Install Database
4. Select “Next” to continue
Appendix E
Page 10
February 2002
3 EFG
GE Aircraft Engines
IfIfone
oneselect
select: :
Sage
SageInput
Inputdatabase
database
The
Theinstall
installprogram
programwillwill
create
createtwo twodata
databases
basesthethe
first
firstone
oneto tostore
storeall
allthe
thedata
data
processed.
processed.
The
Thesecond
secondone onewill
willreceive
receive
only
onlythethedata
databefore
beforeprocessing
processing
The
Theadvantage
advantagewill willbe
beto
toenable
enable
the
theuser
usertotowork
workon onSage
Sagewhen
whendata
data
are
areautomatically
automaticallystored.
stored.
IfIfthis
thisoption
optionisisselected
selectedto todatabases
databases
must
mustbe bemaintained.
maintained.
Appendix E
Page 11
February 2002
3 EFG
GE Aircraft Engines
Select
Selectthe
theappropriate
appropriate
database
database
Then
Thenclick
clickNext
Next
Appendix E
Page 12
February 2002
3 EFG
GE Aircraft Engines
By
Bydefault
defaultsage
sageproposes
proposesthethefollowing
following
folder
folderfor
fordata
database
baseinstallation
installation: :
-C:\Sage_Database
-C:\Sage_Database
Otherwise
Otherwiseselect
select:Browse
:Browse
and
andininthe
thewindow
windowbelow
belowselect
selectan
an
other
otherlocation.
location.
Appendix E
Page 13
February 2002
3 EFG
GE Aircraft Engines
Sage
Sageinstall
installprogram
program
displays the selected
options.
options.
Click
ClickNext
Nexttotocontinue
continue
Appendix E
Page 14
February 2002
3 EFG
GE Aircraft Engines
Sage
Sageinstall
installprogram
program
displays
displays the resultofof
the result
installation
installation
Click
ClickFinish
Finishto
tocontinue
continue
Appendix E
Page 15
February 2002
3 EFG
GE Aircraft Engines
The
TheDatabase
Databaseisisinstalled
installednow
now
the
theoption
optionInstall
InstallSAGE
SAGESystem
System
has to be selected.
has to be selected.
Appendix E
Page 16
February 2002
3 EFG
GE Aircraft Engines
Appendix E
Page 17
February 2002
3 EFG
GE Aircraft Engines
The
Theinstall
installprogram
programdisplays:
displays:
-Your
-YourPCPCconfiguration
configuration
--the
therecommended
recommendedconfiguration
configuration
Then
Thenclick
clickNext
Nextto
tocontinue
continue
Appendix E
Page 18
February 2002
3 EFG
GE Aircraft Engines
The
Theinstall
installprogram
programrequire
requirethe
the
Airline
Airlinename.
name.
Then
Thenclick
clickNext
Nextto
tocontinue
continue
Appendix E
Page 19
February 2002
3 EFG
GE Aircraft Engines
By
Bydefault
defaultsage
sageproposes
following
folder
folderfor
forSAGE
SAGEinstallation
installation: :
-C:\Sage
-C:\Sage
Otherwise
Otherwiseselect
select:Browse
:Browse
and
andininthe
thewindow
windowbelow
belowselect
selectan
an
other
otherlocation.
location.
Appendix E
Page 20
February 2002
3 EFG
GE Aircraft Engines
The
Theinstall
installprogram
programproposes
proposestwo
two
possibilities
possibilities: :
--The
TheFull
Fullinstallation
installation
(for
(forStand
Standalone)
alone)
--The
TheCustom
Custominstallation
installation
Where
Where user hasthe
user has the
possibility
possibilityto
toselect
selectwhich
which
Sage
Sagecomponent
componentmust mustbe be
installed.
installed.
Appendix E
Page 21
February 2002
3 EFG
GE Aircraft Engines
By
Bydefault
defaultsage
sageproposes
proposesthe
thefollowing
following
folder
folderfor
forOn
Onwing
wingdata
datainstallation
installation: :
-C:\Sage\Queue\Automatic
-C:\Sage\Queue\Automatic
Otherwise
Otherwiseselect
select:Browse
:Browse
and
andininthe
thewindow
windowbelow
belowselect
selectan
an
other
otherlocation.
location.
Appendix E
Page 22
February 2002
3 EFG
GE Aircraft Engines
The
Theinstallation
installationprogram
programasks
asksififthe
the
input
inputDatabase
Databaseoption
optionhas
hasbeen
been
chosen
chosenduring
duringthe
theprocess
processof
of: :
Install
InstallSAGE
SAGEDatabases
Databases
You
Youmust
mustselect
selectthe
thesame
sameoption
optionas
as
previousely.
previousely.
By
Bydefault
defaultSage
Sagepropose
proposethe
the
following option :
following option :
-NO
-NOI Iwill
willnot
notbe
beusing
usingaa
Sage
SageInput
InputDatabase
Database
Then
Thenclick
clickNext
Nextto
tocontinue.
continue.
Appendix E
Page 23
February 2002
3 EFG
GE Aircraft Engines
Sage
Sageinstall
installprogram
program
options.
options.
Click
ClickNext
Nexttotocontinue
continue
Appendix E
Page 24
February 2002
Appendix E
Page 25
February 2002

The
Theinstallation
installationprogram
programasks
asksififaa
PASSWORD
PASSWORDisisrequired.
required.IfIfthe
the
answer
answerisisyes
yesan
anadditional
additionalwindow
window
pops-up.
pops-up.
Then
Thenclick
clickNext
Nextto
tocontinue.
continue.
Then
Thenthe
theinstallation
installationprocess
processprovides
provides
the
theuser
userwith
withthe
thewarning
warningpanel
panelshown
shown
below. It will be explained after.
below. It will be explained after.
Appendix E
Page 26
February 2002

Sage
Sageinstall
installprogram
program
displays
displays the resultofof
the result
installation
installation
Click
ClickFinish
Finishto
tocontinue
continue
Appendix E
Page 27
February 2002
Appendix E
Page 28
February 2002

The
Theconfigure
configuredatabase
databaseoption
option
will
willfill
fillup
upyour
yourdata
database
basewith
withthe
the
airplanes
airplanesavailable
availableininyour
yourcompany.
company.
Select
Selectonly
onlythese
theseaircraft,
aircraft,otherwise
otherwise
the
thedata
database
basesize
sizewill
willgrow-up
grow-upvery
very
fast.
fast.
On
Onthis
thispanel
panelthe
thesoftware
softwareversion
versionisis
given.
given.
IfIfaadatabase
databasepassword
passwordhas
hasbeen been
entered
enteredyou
youhave
haveto
toenter
enterit.it.
Then
Thenclick
clickOK
OKto
tocontinue
continue
Appendix E
Page 29
February 2002
3 EFG
GE Aircraft Engines
General
Generalinformation
informationpanel
panel
click
clicknext
nextto
tocontinue
continue
Appendix E
Page 30
February 2002
List
Listof
ofavailable
available
A/C-Engine
A/C-Engine
List
Listof
ofavailable
available selected
selectedfor
foryour
your
A/C-Engine
A/C-Engineon on fleet.
fleet.
the
theCDROM.
CDROM. Currently
CurrentlyThere
There
isisnothing
nothingselected.
selected.
Appendix E
Page 31
February 2002
3 EFG
GE Aircraft Engines
2)
2)Click
Clickon
onthe
the
ADD
ADDbutton
button 3)
3)Your
Yourselection
selectionappear
appear
to
tomove
movethe
the
11))In
Inthis
thiswindow
windowselect
select ininthis
thiswindow.
window.
selected
selectedA/C
A/C
your
yourfleet
fleetconfiguration.
configuration. from
fromone
one Then
Thenclick
clicknext
nextto
tocontinue
continue
window
windowtotothe
the
other.
other.
Appendix E
Page 32
February 2002
3 EFG
GE Aircraft Engines
ItItisisalmost
almostfinish
finish! !
Then
Thenfinish
finishto
tocontinue
continue
Appendix E
Page 33
February 2002
Appendix E
Page 34
February 2002
IfIfone
oneisisupgrading
upgradingits
itsSAGE
SAGEversion,
version,
the
theold
olddatabase
databaseused
usedneeds
needstotobe
be
upgraded.
upgraded.To Todo
doso
soClick
Clickon
onthe
thelast
last
option
optionof ofthe
thewindow.
window.
Appendix E
Page 35
February 2002
Appendix E
Page 36
February 2002
This
Thisprocedure
procedurewill
willcopy
copyfrom
fromthe
theCDROM
CDROM
aadata
database.
base.Executing
Executingthethedatabase
databasewill
will
upgrade
upgradeyour
youralready
alreadyexisting
existingdatabase.
database.
Therefore
Thereforethe
theproper
properdatabase
databaseversion
versionhas
has
to
tobe
bespecified.
specified.
Then
Thenclick
clickNext
Nextto
tocontinue.
continue.
Appendix E
Page 37
February 2002
By
Bydefault
defaultsage
sageproposes
following
folder
folderfor
fordata
database
baseinstallation
installation: :
-C:\Sage_Database
-C:\Sage_Database
Otherwise
Otherwiseselect
select:Browse
:Browse
and
andininthe
thepoped
popedupupwindow
windowselect
selectan
an
other
otherlocation.
location.
Then
Thenclick
clicknext
nextto
tocontinue.
continue.
Appendix E
Page 38
February 2002
Sage
Sageinstall
installprogram
program
displays
displaysthe
theselected
selected
options.
options.
Click
ClickNext
Nexttotocontinue
continue
Appendix E
Page 39
February 2002
The
Thedata
database
basehas
hasbeen
beencopied
copied
Then
Thenupgrade
upgradeyour
yourdata
database
baseand
andthen
then
Perform
Performconfigure
configuredatabase
databaseinstall
install
option.
option.
Then
Thenclick
clickFinish
Finishto
tocontinue.
continue.
Appendix E
Page 40
February 2002
Upgrade an old data base
In the directory selected during

the Update existing SAGE database
process, in this case :
C:\Sage_Database
Double click on file :
Update Database database name.ext
In this case :
Update Database Access97.mdb
Appendix E
Page 41
February 2002
Click
Clickon
onthe
theUpdate
Update
Database
DatabaseButton.
Button.
Appendix E
Page 42
February 2002
Select
Selectthe
thedatabase
databasethat
thatneeds
needs
to
tobe
beupgraded.
upgraded.
Then
Thenclick
clickon
onOpen.
Open.
Appendix E
Page 43
February 2002
The
Thedata
database
baseisisupgraded
upgraded
Then
Thenclick
clickon
onOK
OKtotofinish.
finish.
Appendix E
Page 44
February 2002
SAGE Input Database
SAGE Input Database

February 2002
GE/CFMI Proprietary Information Page 1
Issues
n Enter Data writes its output to PC files, but...
How to get the files from the PC with Enter Data to the
platform with OnWing Processing?
o For ACARS/AIMS data processed on a mainframe and

routed to SAGE for processing...
How do you store data in the SAGE Database while
OnWing Processing is running?
Solution
The SAGE Input Database (a.k.a. SID)!
SAGE Input Database

February 2002
Entry of Flight Data without
SAGE Input Database
reads stores
SAGE Database
Enter Data
writes Input Processor
reads
ADEPT/SAGE Input Files

(Location is user-defined)
SAGE Input Database

February 2002
SAGE Input Database (SID)

➥ SID is a database that can reside anywhere that both
OnWing Processing -- Input Processor & Enter Data can
access it.
➥ A user preference configures Enter Data to write output to
the SID <or> to local files.
➥ User developed processes can also insert data into the SID.
➥ Input Processor stores data from files and from the SID.
✽ Use of the SID is transparent to the user.
➥ Data can be stored to the SID while OnWing Processing

is executing.
➥ Multiple instances of Enter Data can execute concurrently.
SAGE Input Database
February 2002
Entry of Flight Data
with the SAGE Input Database
reads
stores
SAGE Database
Enter Data stores
reads
reads Input Processor

(optional)
stores
SAGE Input Database
ADPET/SAGE Input Files

(Location is user-defined)
User Data Entry Process
(Mainframe, ...)
SAGE Input Database

February 2002
Creating the SID
➥ The SAGE Installation CD-ROM provides a MS-Access

format SID for use on a PC.
✽ The user has the option to not install a SID, if desired.
➥ For other DBMS’s, the CD-ROM includes a SQL “create”
script that can be used to create a SID.
➥ A separate ODBC data source name (DSN) must be
created to support the SID:
✽ The installation CD-ROM can create a DSN for MS-Access SID’s.
✽ A SID DSN must be created using the correct ODBC driver for
other DBMS’s.
SAGE Input Database

February 2002
Locating the SID
Example
ExampleofofSAGE
SAGEDatabase
Databaseand
andSID
SID
located in C:\sage_database directory.
located in C:\sage_database directory.
➥ The SID can reside in the same

directory as the SAGE database,
or a different directory and/or
machine, but…
➥ The PC or UNIX machine
executing SAGE On-Wing
Processing must have access to
SID via the correct ODBC driver.
SAGE Input Database
February 2002
3 EFG
Telling SAGE to use SID
GE Aircraft Engines
Checking
Checkingthethe“Save
“Saveinto
intoSAGE
SAGEInput
InputDatabase”
Database”
option activates the SID preferences tab.
option activates the SID preferences tab.
Select
Selectthe
theinput
inputdatabase’s
database’sDSN
➥ Preferences are set from the list on the SAGE
DSN
Input
from the list on the SAGE Input
automatically if SID is Database
Databasepreferences
preferencestab.
tab. Only
Only
chosen during install, but… input database DSN’s are displayed.
input database DSN’s are displayed.
➥ Non-Access databases
require that user’s select
the DSN manually.
SAGE Input Database
February 2002
SID Login
➥ When starting Enter Data or Browse Input for the first
time, you will be asked to login to the SID (in addition to
the normal SAGE database login).
➥ Subsequent Enter Data or Browse Input sessions will not

require the user to login to SID, provided that the SAGE
database and SID passwords (if used) are the same.
SAGE Input Database

February 2002
SAGE “Applications”
Applications GE/CFMI Proprietary Information Page 1

February 2002
What is an “Application”?
✈ The basic concept of an application: It represents the
combination of a specific engine type with a specific
aircraft type.
B777 with GE90 engines

B747-300 with CF6-80C2B1 engines B777 with GE90 engines
B747-300 with CF6-80C2B1 engines Owned and operated by British Airways
Owned and operated by ANA Owned and operated by British Airways
Owned and operated by ANA

February 2002
Purpose of Applications
✈ An application is used to select the system data used
to process flight data for each engine installation.
✈ This system data includes:

✽ Analytical function configuration data (“PIP” files)
✽ Alert tests and associated limits
✽ Smoothing parameters and smoothing coefficients
✽ Measurement units

February 2002
The “Keys” of an Application

✈ Specifically, an application is a unique combination of
four (4) GEAE/CFMI-defined and four (4) user-defined
parameters:
Application
Application
“Keys”
“Keys”
Aircraft type Aircraft operator
Engine type Aircraft owner
Hardware Config. + Engine owner
Control Selector
GEAE/CFMI-defined
GEAE/CFMI-defined and
and User-defined
User-defined values,
values,
controlled
controlled values, storedininthe
values, stored the created
created by the userwhen
by the user when
database during the Configure
database during the Configure using various SAGE
using various SAGE
Database
Databaseinstallation
installationstep.
step. interactive
interactiveprograms
programs

February 2002
“Default” Applications
✈ SAGE provides “default” applications for all
supported aircraft and engine type combinations,
using “GEAE/CFMI” for owner and operator fields.
✈ During the Configure Database installation step,

these “default” applications are loaded into the
SAGE database.

February 2002
“User” Applications
✈ A “user” application is created each time a new
combination of the four (4) user-defined parameters
is specified for a selected combination of the four (4)
GEAE/CFMI-defined parameters.
✽ During Fleet Management engine installation, the aircraft
owner, engine owner and aircraft operator (and maybe the
“selector” field) are entered or selected.
✽ SAGE copies a default application based on the user’s choice
of the four GEAE/CFMI parameters, and then...
✽ SAGE creates a “user” application, including the user entered
values of the four user-defined parameters.

February 2002
Creation of “User” Applications

“GEAE/CFMI
“GEAE/CFMIdefault”
default”applications.
applications.
Application Aircraft Type Engine Aircraft Aircraft Engine Hardware Control Selector
ID Type Operator Owner Owner Config.
GE0009 DC-10-10/-30 CF6-50C GEAE/CFMI GEAE/CFMI GEAE/CFMI PRE-P100
GE0010 DC-10-10/-30 CF6-50C GEAE/CFMI GEAE/CFMI GEAE/CFMI P100
U00001 DC-10-10/-30 CF6-50C XYZAIR XYZAIR XYZAIR PRE-P100
U00002 DC-10-10/-30 CF6-50C XYZAIR XYZAIR XYZAIR P100
These
These“user”
“user”applications
applicationsare
arecopied
copiedfrom
from
default applications during the first engine
default applications during the first engine
installation
installationfor
forthe
thegiven
givenset
setofofapplication
application“keys”.
“keys”.
User
Userapplications
applicationsare
arecopied
copiedfrom
fromGEAE/CFMI
GEAE/CFMIdefault
defaultapplications.
applications.

February 2002
Applications and System Data

Application Aircraft Type Engine Aircraft Aircraft Engine Hardware Control Selector
ID Type Operator Owner Owner Config.
GE0009 DC-10-10/-30 CF6-50C GEAE/CFMI GEAE/CFMI GEAE/CFMI PRE-P100
GE0010 DC-10-10/-30 CF6-50C GEAE/CFMI GEAE/CFMI GEAE/CFMI P100
U00001 DC-10-10/-30 CF6-50C XYZAIR XYZAIR XYZAIR PRE-P100
U00002 DC-10-10/-30 CF6-50C XYZAIR XYZAIR XYZAIR P100
U00003 DC-10-10/-30 CF6-50C XYZAIR XYZAIR XYZAIR P100 ALERTS
Analytical Smoothing Alerts Units

PIP's
The
Thesystem
systemdata
dataused
usedto
toprocess
processflight
flightdata
datais
isselected
selectedby
byApplication
ApplicationID.
ID.
February 2002
Example APPLICATION Table

February 2002
Points to Remember
✈ Each engine on an aircraft has an associated application.
✈ The application determines the system data that will be

used in performing all analytical functions.
✈ Any modification to system data -- including alert limits,

smoothing constants, units definitions, etc. -- are generally
made for a specific application.

February 2002
History File Conversion
H istory F ile C o n v e rsion G E /C F M I Proprie ta r y Informatio n Page 1

August 1998
What is History File Conversion?

o History File Conversion is used
to migrate existing ADEPT 10
fleets into a SAGE database.
o History File Conversion
performs three key actions:
a) It extracts fleet data from an
ADEPT 10 history file.
b) It prompts the user for
additional information required
for proper fleet definition within
SAGE, such as aircraft owner.
c) It loads the extracted fleet into
the SAGE database.

August 1998
When do I use History File Conversion?
o You want to move some or all of your existing

ADEPT 10 aircraft, and associated flight data
into a SAGE database.

August 1998
History File Conversion “Toolbox”
o Conversion “Tools”
– Typical
• Extract aircraft, engines and flight data from an existing ADEPT 10
history file, and import them into a SAGE database.
– Import Only
• Load the SAGE database by importing text data files with a specific
GEAE defined format.
– DB Load Errors
• Review any errors generated during either of the above processes.

August 1998
Steps of the Conversion Process
o Performing a history file conversion requires three steps:

1) Select the ADEPT 10 history file to convert from.
2) Select the aircraft to be converted; define the operator and
aircraft and engine owners.
3) Specify whether or not to convert flight records for each aircraft
selected in step 2.

August 1998
Converting from ADEPT 10, Step 1

1) Select Typical from the History File
Conversion switchboard. The ADEPT
Fleet Selection screen is displayed.
2) Any fleets located will be displayed in
the ADEPT Fleet drop down list.
3) Select one of the displayed fleets.
4) Alternately, use the Browse… button
to locate the directory of another
ADEPT fleet, then choose any file in
that directory and select OK.
5) Once the fleet to be imported is
shown in the ADEPT Fleet field,
select OK. The Aircraft Configuration
Selector is displayed.

August 1998
Converting from ADEPT 10, Step 2,
Aircraft Configuration
1) Choose the aircraft that you want to import, or use the Select All Aircraft
button to select all aircraft.
2) Enter the desired owner and operator information for these aircraft and
their engines in the fields at right.
3) Select OK. The Aircraft Flight Record Selector screen is displayed.

August 1998
Converting from ADEPT 10, Step 3,
Flight Record Selection
1) If you want to import an aircraft’s
flight data (along with the definition
of the aircraft and its engines),
select the aircraft on this screen.
2) Use the Same as Aircraft Config
button to automatically select the
same aircraft as on the previous
screen.
3) When you are finished, select OK
to begin the import process.
N O T E : O nce the O K button is clicked,

proce s s ing can take s e v e ral h o u rs to
comple te , depending upon the size of the
A D E P T 10 history file being converted.

August 1998
Reviewing Database Load Errors

1) Select the button labeled DB Load Errors on the switchboard.
2) Carefully read the error log. Look for errors that may have prevented
aircraft or engine definitions, or transfer of flight records.

August 1998
History File Conversion Usage Guidelines
o When converting an ADEPT 10 fleet containing a mix of owners

and/or operators, convert aircraft in separate batches based on those
attributes.
o Since processing can take several hours, it is strongly recommended

that no other activities be performed on the PC used for the
conversion during this time.
o If load errors occur preventing the definition of certain aircraft or

engines, you should define them using Fleet Management.
o If load errors occur preventing the transfer of flight records, we

recommend starting trending with new data for the affected aircraft.
H istory F ile C o n v e rsion G E /C F M I Proprie ta r y Informatio n P a g e 10

August 1998
Conversion Tools
Conversion Tools Appendix G

August 1998 GE/CFMI Proprietary Information Page 1
Conversion Tools
å History File Conversion
] Utility programs to copy historical data from history files to a
SAGE database.
u ADCONV for ADEPT
u RUNHFC for GEM
å Input File Conversion

] Utility program to convert the GEM Airline Input File (AIF) data
into a SAGE input file.
u AIFIP


ECM History SAGE DB

uter puter
Comp
GE Com
ECM SA
History File
Extract Conversion
Import Option
ASCII Files ASCII Files

For all users
å Specify delimiter character to be used.
MUST match value in SYSCON
å Select Fleet (configuration) data, Flight data, or both.

å Converts aircraft and engine types to SAGE standards.
å Convert subsets of total fleet, in separate phases.
å “Extract” process on the present ECM computer.
å “Import” process on a SAGE interactive computer.
For ADEPT users For GEM users

å Select by Aircraft. å Select by Engine.
å Enter Operator and Owner å Execute RUNHFC.
information.
å Execute ADCONV.

Information copied
] Identification data
u Aircraft IDs
u Engine Positions
u Engine Serial Numbers
u Engine Installation Dates & Times
] Cruise, Takeoff and Climb (GEM only) OnWing flight data

u Input parameters
u Output parameters
u Smoothed parameters
u Compressed data
u Initialization data (GEM “Maiden points”)

å Information not copied

] Alerts
] Errors (NSI’s)
] Maintenance data
å Information converted to SAGE standards

] Aircraft types
] Engine types
] Parameter names

ADEPT History File Conversion
Caution
] Aircraft selection
u If no Aircraft ID’s are specified, then all aircraft in the
History File will be extracted.

GEM History File Conversion
Cautions
] Engine serial numbers
u GEM Engine History is extracted only by Engine Serial Number.
u If no engine serial numbers are specified, no data are extracted.
u If an engine serial number is specified, be sure to specify each of the
other engine serial numbers installed on that same aircraft.
] Installation levels
u Fleet and Flight information are extracted only from the most
recent installation level (current level) of each selected engine.
u GEM has no concept of an engine being ONWING, SPARE or
UNSERVICEABLE; all engines selected for conversion are
assumed to be ONWING.
u If a selected engine serial number has been removed and not yet
reinstalled (in GEM), any data converted for that engine will be
associated with the Aircraft ID and Engine Position where it was
Conversion Tools
last installed. Appendix G
GEM History File Conversion
Cautions (continued)
] Parameter names
u GEM airline parameter names (“alias names”), from PLISTs in the SCF, are
used for SAGE parameter names.
u User-modified airline parameter names must be reset to their original GEM
parameter names.
u For CFM56 data, change ZT495 to ZT49 before converting.
u If parameter name changes are necessary, modify a copy of the production
GEM SCF. This will allow for parallel operation of GEM and SAGE.
u All parameters must be defined in SAGE.
] Configuration information
u Identification information is extracted from the most recent flight data
available for each selected engine serial number.
u Aircraft Functions are determined during extraction, by examination of the
Datatype parameter values stored in each engine’s flight data records.
Input File Conversion

GEM Airline Input File Conversion

SCF
EDF
ter puter
pu Com
M Com SAGE
EC
AIFIP
SAGE Polling Directory
Climb Climb
Takeoff Takeoff
AIF .SGE files
Cruise Cruise
.SGE files
.SGE files .SGE files
.SGE files .SGE files

ADEPT Input File Conversion
SAGE accepts ADEPT input files without any conversion.

] .DT1 extension for ADEPT 8 (Mode 1, 3-line format)
] .DT2 extension for ADEPT 10 (Mode 2, 7-line format)
No
Noconversion
conversionneeded!
needed!

GEM Airline Input File Conversion

å Each AIF containing data to be input to SAGE must be converted.
å Conversion takes place on the GEM computer.
å Recommended to follow customer’s AIF Generation processing.
å Resulting SAGE input files must be transferred to the user’s

identified polling directory for SAGE processing.
] Creates separate files for CRUISE, TAKEOFF and CLIMB.
] .SGE extension required, when placed in polling directory.
] Transfer of files is the user’s responsibility.

Error Files
Error FilesError Files GE/CFMI Proprietary Information

February 2002 Page 1
Purpose of Error Files
Error files are generated to provide:
✽ Verification of execution
✽ Verification of each program’s version
✽ Information for troubleshooting problems

Source of Error Files
✈ Each program creates or appends information to an error file.
✈ All background processing programs generate error files,
even if executed by an interactive program:
◆ OnWing Processing -- Input processor
◆ OnWing Processing -- Single Record Function
◆ OnWing Processing -- Initialization/Smoothing
◆ OnWing Processing -- Alerting
◆ OnWing Processing -- Compression
◆ Automatic Reports
◆ SAGELoad (from History File Conversion)
◆ Application History
◆ Update Compress Counter
◆ Migrate database
3 GE Aircraft Engines
Example of Error_Log Folder EFG
“Error_log” folder
- contains “error files” from previous (2) * days -- * default setting
Keys: program.exe_yyyy_mm_yy.err
owp -- OnWing Processing
\sage
repgen -- Report Generation
\files alert -- Alerting Step
comp -- Compression Step
\log_files
initsmth -- Initialization / Smoothing Step
\error_log ip -- Input Processor Step
srf -- Single Record Function Step
Contents of Error Files
Installed SAGE Version & Version of the program
************************************************** Installed SAGE Version & Version of the program
that
SAGE Version 3.0.1 thatisisexecuting
executing
OWP_INPUT_PROCESSOR Version V3.0.1
************************************************** Information
Airline Name : AIRLINE'S NAME INSERTED HERE Informationfrom fromthetheuser’s
user’ssystem
system----
• • airline’s
Installation Level : server airline’sname
name
Processor : Intel Pentium • operating system,
• operating system,
• • client
Operating System : Microsoft Windows 95 4.0 (Build 950)
clientversus
versusserver
serverinstall
install
Physical Memory : 64992 • • memory
Client Drive : c:,Fixed, FAT, Total: 2146631680, Free: 657915904 memory
• • drive
drivespace
space
Server Drive : c:,Fixed, FAT, Total: 2146631680, Free: 657915904
**************************************************
Info 07/17/98 17:25:44 Input_Processor MAIN
Start time: 07/17/98 17:25:44
Medium 07/17/98 17:25:46 IP_SETS_CONTROLLER Is_Overwrite_Allowed
Not allowed to overwrite existing input/output for aircraft A as system constant ALLOWOVERWRITEINPUT = NO
Medium 07/17/98 17:25:46 GENERIC_CONTROLLER Process_Flight_Data
Error processing flight data for aircraft A flight_phase CRUISE on 01-02-1996 08:00:00 (record 2) - skipping record in data file
c:\sage301\queues\automatic\A_CRUISE_SET1.sge
Medium 07/17/98 17:25:46 FLIGHT_DATA Validate_Db_Keys
Aircraft_id DOGGY is not defined in the database Level
Medium 07/17/98 17:25:46 FLIGHT_DATA Process_Flight_Data Levelofofthetheerror
errormessage:
message:
Info for informational
Unable to validate database storage keys for aircraft DOGGY flight_phase CRUISE on Info
03-02-1996 informationalonly
for08:00:00 only
Medium 07/17/98 17:25:46 GENERIC_CONTROLLER Process_Flight_Data Low
Low Probably invalid
Probably invalid datadata
Error processing flight data for aircraft DOGGY flight_phase CRUISE on 03-02-1996Medium May impact
08:00:00 (record calculated values
Medium May3)impact
- skipping record in data
calculated file
values
c:\sage301\queues\automatic\A_CRUISE_SET1.sge High Must
Must be corrected before executingagain
be corrected before executing
Medium 07/17/98 17:25:46 IP_SETS_CONTROLLER Is_Date_Time_Valid High again
Date/time of the error
Date/time of the error
Date ( 04-02-1976 08:00:00 ) must be >= to the minimum system date (01-01-1980)
Medium 07/17/98 17:25:46 FLIGHT_DATA Validate_Db_Keys
Class
Classand andoperation
operationgenerating
generatingthe theerror
error
Invalid flight date/time 04-02-1976 08:00:00 Additional explanation of the error
Additional explanation of the error condition condition
Medium 07/17/98 17:25:46 FLIGHT_DATA Process_Flight_Data

SAGE
Interactive Features
SAGE Interactive Features

Common Interactive Program Features

➥ All SAGE interactive programs use a consistent “look & feel”.
➥ The following features are common to every interactive program:

✽ Start/exit behavior
✽ Security login
✽ “Switchboard” concept
✽ “Toolbox/Tools” concept
✽ Toolbars
✽ Screen navigation
✽ Preferences
✽ Error logs
✽ Help
✽ Security status
✽ Status messages
✽ Date and time display
General Window Arrangement
“Frame” window
“Frame” window
Help menu
Help menu
Menus
Menus
“Frame” Toolbar
“Frame” Toolbar
“Sheet” Toolbar
“Sheet” Toolbar Minimize, maximize and close icons.
Minimize, maximize and close icons.
“Sheet” window
“Sheet” window Switchboard
Switchboard
Security status indicators

Security status indicators
Status message area

Status message area
Date and time

Date and time
Starting an Interactive Program

➥ A SAGE interactive program is
started in the same manner as
any other Windows 95 program.
SAGE Program Group
SAGE Program Group
➥ The easiest method is the “Start”
menu
Programs
Programs
SAGE Programs
Start menu SAGE Programs
Start menu

Program Login
➥ You will see the Application Login

screen each time you start a SAGE
interactive program.
➥ Your login serves three purposes:

1) If you have multiple databases, you
can select the one you want to
access.
2) It initiates the connection to the
database, and
3) It validates your user name,
if security is enabled.

“Toolboxes” and “Tools”
“Toolboxes” are groups of

related functions, or “Tools”.
Toolboxes and tools are

accessible via menus, toolbar
buttons or the switchboard.

Toolbars
➥ Toolbars are groups of buttons that provide quick
access to program functionality.
➥ The “Frame” toolbar contains the items in the
Toolbox menu, and an Exit button.
➥ The “Sheet” toolbar contains the items in the Tools
menu, a window Close button, and occasionally
other buttons such as Print.
➥ Toolbars can be positioned at the top or bottom, left
or right, or as a “floating” palette.
➥ You can make the toolbar smaller by not displaying
the button text.

The Interactive Program’s “Switchboard”

Interactive programs use a control center window called the “switchboard”.
“Tabs” on the switchboard provide

“Tabs” on the switchboard provide
access to a program’s “toolboxes”.
access to a program’s “toolboxes”.
The buttons on
The buttons on
the right side of
the right side of
the switchboard
the switchboard
access the
access the
“tools” available
“tools” available
in the selected
in the selected
“toolbox”.
“toolbox”.
You can use the Exit button on the The “Process Flow” diagram is used
You can use the Exit button on the The “Process Flow” diagram is used
switchboard to quit an program. to indicate the major selections and
switchboard to quit an program. to indicate the major selections and
screens available for each tool.
screens available for each tool.
3 EFG
GE Aircraft Engines
Screen Navigation
➥ SAGE interactive programs can

be navigated using the keyboard
as well as the mouse.
“Mnemonics” keys for both menu
“Mnemonics” keys for both menu
items and buttons are underlined.
items and buttons are underlined.
➥ When data entry is required, it is
generally more convenient to
navigate the screen without
reaching for the mouse.
➥ “Mnemonics” keys, used in

combination with the <Alt> key,
are available for most buttons and “Accelerator” keys are available to
“Accelerator” keys are available to
select functions in the toolbox
select functions in the toolbox
menu items. without opening the toolbox.
without opening the toolbox.
In the above “mnemonics” example, while holding down

➥ “Accelerator” keys , used in In the above “mnemonics” example, while holding down
the <Alt> key, the combination of <B> followed by <E>
the <Alt> key, the combination of <B> followed by <E>
triggers the Engine menu item in the ToolBox.
combination with the <Ctrl> key, triggers the Engine menu item in the ToolBox.
In this case, the Engine menu item can also be selected
In this case, the Engine menu item can also be selected
are available to select functions. by holding down the <Ctrl> key in combination with <E>.
by holding down the <Ctrl> key in combination with <E>.

Preferences
➥ The Preferences screen is a special Toolbox, accessible from any
interactive program.
➥ Preferences allow the user to configure the current desktop,
not the whole SAGE system.
Click on a tab to view

Click on a tab to view
preferences for that category.
preferences for that category.
To make your changes temporary,

To make your changes temporary,
click the Use Temporary checkbox
click the Use Temporary checkbox
before selecting the OK button. The Reset SAGE Defaults button
before selecting the OK button. The Reset SAGE Defaults button
will revert all preferences to their
will revert all preferences to their
original, as delivered settings.
original, as delivered settings.
Use Reload ALL Options to load preferences

Use Reload ALL Options to load preferences
from the most recently saved user preference
from the most recently saved user preference
Selecting OK saves the current preferences. file, replacing any temporary settings.
Selecting OK saves the current preferences. file, replacing any temporary settings.

General Preferences
“Miscellaneous” items control
“Miscellaneous” items control
the “prompt level” when using
the “prompt level” when using
SAGE interactive programs.
SAGE interactive programs.
“Edit Masks” can be used to set
“Edit Masks” can be used to set
preferred date and time formats.
preferred date and time formats.
Checking the Use Regional

Checking the Use Regional
Settings checkboxes will match
Settings checkboxes will match
date and/or time formats to your
date and/or time formats to your
computer’s regional settings.
computer’s regional settings.
“Toolbars” options alter toolbar

“Toolbars” options alter toolbar
position and text attributes.
position and text attributes.
“Debug” preferences control the amount of detail

“Debug” preferences control the amount of detail
written to the interactive program log files. The
written to the interactive program log files. The
number of debug files retained for each interactive
number of debug files retained for each interactive
program is also controlled here.
program is also controlled here.

Viewing Error Messages
➥ Whenever an interactive program is used,

it writes a log (or “error”) file.
➥ Log files are used in diagnosing errors.
➥ Use the
View -> Error Messages…
menu item to access an error
log file.
➥ Select the error file to view,
then select Open.

SAGE Online Help

➥ Online help has information on
each interactive program.
Access
Accesstotohelp
helpisisavailable
available
from
from the Help menuofofany
the Help menu any
interactive
interactive program (andthe
program (and the
Windows 95 Start menu,
Windows 95 Start menu,
too!).
too!).
➥ Online help is designed to
assist users in completion
of on-screen tasks.
➥ Online help is NOT the
user’s manual in “online
form”.

Exiting
Exit SAGE interactive programs as you would any Windows 95 program.
Exit toolbar button
Exit toolbar button
Corner ‘X’
Corner ‘X’
File menu -> Exit

File menu -> Exit
Switchboard Exit button

Switchboard Exit button

Fleet Management
Fleet Management GE/CFMI Proprietary Information Page 1

February 2002
What is Fleet Management?

o Fleet Management is the
“control center” for your
SAGE fleet of aircraft and
engines.
o Using Fleet Management

you create, modify and
delete aircraft and engines,
and perform engine
installations and removals,
within the SAGE database.

February 2002
When do I use Fleet Management?

o When you need to add a new aircraft to your SAGE fleet.
o When you need to alter an engine’s thrust rating.
o When you want to stop (or start) execution of a specific

analytical function for an aircraft.
o When you are notified of an engine change and you need to

update the SAGE database with that information.
o When you need to correct an erroneous engine installation.
o When a previously ‘unserviceable’ engine returns from overhaul

or repair and becomes a ‘spare’.

February 2002
Fleet Management Aircraft “Toolboxe”

o Aircraft “Tools”
– Define
• Define a new aircraft within the SAGE database by selecting
the aircraft type and manually entering all required information.
– Copy
• Define a new aircraft within the SAGE database by copying an
existing aircraft’s definition. (Less typing required that Define)
– Modify
• Modify any aircraft attribute, except for aircraft_id.
– Delete
• Delete an aircraft’s definition (and potentially its engines and
flight data) from the SAGE database.
– Removal/Install
• Remove and/or install ‘spare’ engines on an aircraft.
– Set Incident Flag
• Set an aircraft’s incident flag to prevent modification to its data
via SAGE interface applications or background process
applications.
February 2002
Defining an Aircraft

February 2002
Defining an Aircraft
1) Select the Aircraft tab on the SAGE
switchboard, if not selected already.
2) Select the button labeled Define.
3) Enter or select the new aircraft’s attributes.
4) When finished, select OK.
5) The Select Analytical Functions screen will
be displayed next.

February 2002
Define Aircraft - Select Analytical Functions

1) Choose the flight phases for which you will receive data for this aircraft.
2) Select the desired analytical functions within those flight phases.

February 2002
Define an Aircraft using Copy button

February 2002

Filter screen

February 2002

Filter screen : B737-400 selected 3 A/C id possible

February 2002

Filter screen : B737-400 selected DAHLL will be copied

February 2002
Aircraft
Aircraftidentifier
identifier
Registration
RegistrationIDID
fields
fieldshas
hastotobe
befilled
filledup
up
the
theother
otherfield
fieldare
arecopied
copied
from
fromAircraft
Aircraftselected.
selected.
The
Thenext
nextstep
stepwill
willbe
bethe
the
definition
definitionofofthe
the
ANALYTICAL
ANALYTICALFUNCTIONS
FUNCTIONS

February 2002
Modify an existing Aircraft

February 2002
Modify an existing Aircraft
Aircraft
Aircraftidentifier
identifierCannot
Cannotbe
be
modified.
modified.
All
Allthe
theother
otherfields
fieldscan
canbe
bemodified.
modified.
The
TheANALYTICAL
ANALYTICALFUNCTIONS
FUNCTIONS
are
areaccessible
accessiblewith
withthe
the
Edit
EditFunctions
Functionsbutton
button

February 2002
Delete an Aircraft

February 2002
Remove or install an engine

February 2002

February 2002

February 2002

February 2002
Incident flag

February 2002
Incident flag
o An incident flag is a discrete value i.e. it has only two
position true false or on OFF possibility.
o When an incident flag is set to on that will prevent onWing

processing to process the data for this particular engine.
o This is useful if one think that there are some spurious

values in the flight records to process.
o These flight data will be kept in C:\Sage\Queue\Automatic

(generic folder ) until the incident flag is removed.

February 2002
Incident flag

February 2002
Fleet Management Engine “Toolboxe”

February 2002
Fleet Management Engine “Toolboxe”

o Engine “Tools”
– Define
• Define a new engine within the SAGE database by selecting
the engine type and manually entering all required
information.
– Copy
• Define a new engine within the SAGE database by copying
an existing engine’s definition. (Less typing required that
Define)
– Modify
• Modify any engine attribute, except for engine_id.
– Delete
• Delete an engine’s definition and associated flight data from
the SAGE database.
– Removal/Install
• Remove and/or install ‘spare’ engines on an aircraft.
– Delete Installation
• Delete an erroneous engine installation, often for the
purpose of correctly “re-installing” using Removal/Install.
February 2002
Defining an Engine using Define Engine

February 2002
Defining an Engine using Define Engine

1) Select the Engine tab from
the SAGE switchboard.
2) Select the button labeled
Define.
3) Enter or select the new
aircraft’s attributes.

February 2002
Defining an Engine using Copy Engine

February 2002
Defining an Engine using Copy Engine

1) Select the Engine tab from the
SAGE switchboard.
2) Select the button labeled Copy.
The Engine ID Selection screen
will be displayed.
3) Select an engine to copy from
(I.e., the source engine). Then
select OK.
4) Enter the new engine’s
identification number, and modify
any attributes that differ from the
source engine’s values.

February 2002
Modify an engine

February 2002
Modify an engine
The
Theengine
engineID
ID
cannot
cannotbe
bemodified
modified

February 2002
Modify an engine
The
Theengine
engineID
ID
cannot
cannotbe
bemodified
modified

February 2002
Remove install an engine

February 2002
Making an Engine Change, Step 1:
Select Aircraft & Engine Position
1) Select either the Engine or Aircraft

tab from the SAGE switchboard.
Remove/Install. The Aircraft ID
Selection screen will be displayed.
3) Select the aircraft on which to
perform an engine installation,
then select OK.
4) Select the button labeled Remove
for the desired engine position.
The Remove Engine screen will
be displayed.

February 2002
Performing an Engine Change, Step 2: Engine Removal
1) Enter the date and time of

the engine removal, any
available hours or cycles
information (optional), and
a reason for this removal.
2) Select the appropriate
engine status, either
‘Spare’ or ‘Unserviceable’.
4) The Remove Engine screen
will close, and the
Remove/Install Engines
screen will be active.

February 2002
Making an Engine Change, Step 3: Engine Installation
1) Select the button labeled Install

for an “open” engine position.
2) On the Install Engine screen,
select the engine to be installed
from the Engine ID drop down list.
3) Enter or select other installation
details as applicable.
4) If this is the first time that the
selected engine type has been
installed on the selected aircraft
type, the Copy Application screen
will be displayed.

February 2002
Making an Engine Change, Step 4: Copy Application

1) To see details about the tables and files to be associated with this
application select the button labeled View Application Details.
2) Select OK on the Application Settings screen to return to Copy Application.
3) Enter a description in the text area of the screen, then select OK.
4 A “user” application will be created within the database.
4) Engine installation is complete.

February 2002
Delete Installation

February 2002
Delete Installation

February 2002
Delete Installation

February 2002
Fleet Management Usage Guidelines

o Remember! All changes impact the database IMMEDIATELY.
o Pay special attention to entering date/time values when removing or
installing an engine.
o The attributes Aircraft ID, and Engine ID cannot be changed once the
respective aircraft or engine is created.
o Deleting an engine will also delete any flight data associated with
every installation of that engine.
o Engine or aircraft attribute changes are entered into the database using
the “Effective Date”. Take care to make sure this date is correct.
o When executing background process applications, analytical calculations
will not be performed for aircraft unless all engine positions are “installed”.

February 2002
Enter Data
Enter Data GE/CFMI Proprietary Information Page 1

February 2002
What is Enter Data?

o Enter Data is a program for
entering input via the keyboard.
o Input data is written to a

computer file, which is then
available for processing through
On-Wing Processing.
o Enter Data supports entry of the

following types of input data:
– Flight data for any applicable
flight phase
– Engine change information
– Engine maintenance actions
– Engine hours and cycles records

February 2002
When do I use Enter Data?

o When you have a problem that prevents acquisition of
automatically generated data.
o When flight data is only provided on cockpit “coupons”.
o When you want to track maintenance actions within SAGE.
o When, for security reasons, you want personnel to enter data

without directly accessing the database.

February 2002
Enter Data “Toolboxes” (1/2)

o Flight Data “Tools”
– Flight
Type in takeoff, climb or cruise data from the keyboard.

February 2002
Enter Data “Toolboxes” (2/2)
o Maintenance “Tools”
– Engine Change
• Enter engine removal and
installation information.
– Maintenance
• Enter line maintenance actions.
– Times and Cycles

• Enter engine hours and cycles.

February 2002
Entering Flight Data
o Entering flight data is a simple three (3) step process:

1) Select the aircraft for which you want to enter data
2) Select the flight phase of the data
3) Type in the data values

February 2002
Entering Flight Data, Step 1:
Selecting an Aircraft
o Select the button labeled Flight on the Flight Data tab of the
switchboard. The Aircraft ID Selection screen is displayed.
o Select the first aircraft for which you have data.
o Select OK, the Flight Data Entry screen is displayed.

February 2002
Entering Flight Data, Step 2:
Selecting a Flight Phase
o Select the flight phase of your data using the Flight Phase
drop down list.
Flight
FlightPhase
Phasedrop
dropdown
downlist
list

February 2002
Entering Flight Data, Step 3: Data Entry

The Flight Data Entry screen is designed for navigation
You can select a new Aircraft ID, The Flight Data Entry screen is designed for navigation
You can select a new Aircraft ID, using the keyboard (instead of the mouse) . Use the <tab> Enter Flight Datetime
without going back to the selector, using the keyboard (instead of the mouse) . Use the <tab> Enter Flight Datetime
without going back to the selector, key to move forward one field, and use the combination of accurately, using all
using the drop down list of same key to move forward one field, and use the combination of accurately, using all
using the drop down list of same <shift>+<tab> to move backwards one field. available precision.
type aircraft. <shift>+<tab> to move backwards one field. available precision.
type aircraft.
You can click the

You can click the
bleed discrete drop
bleed discrete drop
down lists to select a
down lists to select a
setting, OR, type the
setting, OR, type the
first letter of the
first letter of the
setting you want
setting you want
(e.g. “E” for Econ),
(e.g. “E” for Econ),
OR, use the up and
OR, use the up and Required parameters will
down arrows. Required parameters will
down arrows. be displayed in RED.
be displayed in RED.
If you prefer to
If you prefer to
move down the
move down the
list of parameters
list of parameters
for each position,
for each position,
uncheck the
uncheck the
Traverse...
Traverse...
checkbox.
checkbox.
Use the Clear buttons to erase

Selecting OK will save your data into a “.SGE” format Use the Clear buttons to erase
Selecting OK will save your data into a “.SGE” format errant data from an engine position.
data file, in directory specified in your preferences. errant data from an engine position.
data file, in directory specified in your preferences.
February 2002
Enter data Engine change

February 2002
Enter data Engine change
33
11
22

February 2002
Maintenance action

February 2002
Maintenance action

February 2002
Maintenance action

February 2002
Times & Cycles

February 2002
Times & Cycles

February 2002
Enter Data Usage Guidelines

o Be sure to check the selected Flight Phase before entering data.
o Remember to accurately enter each record’s flight date and time.

Any records with identical date/time values, for the same aircraft id
and flight phase, will be rejected.
o Use the keyboard navigation features to speed data entry.
o If you are entering data for several aircraft of the same type,
use the Aircraft ID drop down list to select a new tail number.

February 2002
Browse Input
Browse Input GE/CFMI Proprietary Information Page 1

February 2002
What is Browse Input?

o Browse Input is used to view
delete and delete flight records
from input files.
o Using Browse Input you can:

– View flight records in the
.DT1, .DT2 and .SGE input
files
– Delete flight records in the
.DT1, .DT2 and .SGE input
files
– Modify flight record from .SGE
input file

February 2002
When do I use Browse Input?

o When you want to view the input data of flight records before they
are inserted into the SAGE database.
o When you want to delete flight records before they are inserted into
the SAGE database.
o When you want to modify flight records before they are inserted into
the SAGE database
o When you want to navigate your directory structure to view/delete
flight records when they are not in the regular SAGE input directory.

February 2002
Browse Input “Toolboxe”

o Browse Input “Tools”
– Flight
• View/Modify/Delete input flight records before they are in the SAGE
database

February 2002
View modify or delete a SAGE Input file
o There are two (2) steps to viewing an input file:

1) Select the particular input file
2) View/Delete the flight records in the input file.

February 2002
View modify delete file, Step 1: Select
the file
1) Select the button labeled Flight from the switchboard. The File Selector
screen is displayed.
2) Find your desired input file(s) from the middle panel.
3) Select this file(s).
4) Select the Add button to put this file in the right panel.
5) Select the OK button. The Browse Flight Data screen is displayed.

February 2002
Select the file
Flight
Flightdata
dataentered
enteredby byenter
enterdata
data
Automatic generic
genericsage
sagefile.
file.ItItisisan
anASCII
ASCIIfile.
Automaticdownloaded
downloadedfilefile file.
from
fromaircraft.
aircraft.Extention
ExtentionDT2
DT2
ItItisisalso
alsoan
anASCII
ASCIIfile.
file.
The
Thefolder
folderhas
hasbeen
beenselected
selected
during
duringthe
theinstall
installprocess.
process.
Here
Hereititisisthe
thegeneric
genericsage
sagefolder.
folder.

February 2002
View file, Step 2: View/Delete flight records
1) Use the Next Record and Previous Record buttons to traverse the flight records
in all of the selected input files.
2) If at any point you want to Delete Current Record, Delete Remaining Records
or Delete All Records, select on of these buttons.
3) When finished select the OK button.

February 2002
View file, Step 2: View/Delete flight records

February 2002
View file, Step 3: Delete or Modify flight

records
This
Thispanel
panelisisdisplayed
displayedwhen
whenone
one This
Thispanel
panelisisdisplayed
displayedwhen
whenone one
uses
usesthe
theoption
optiontotodelete
deletemore
morethan
than uses
usesthe
theoption
optionto tomodify
modifyone
one
one
oneflight
flightrecord
recordfrom
fromaaDT2
DT2file.
file. flight
flightrecord
recordfrom
fromaaSGE
SGEfile.
file.

February 2002
Browse input view delete Engine change

February 2002
Browse input view delete Engine change

February 2002
Browse input View /Modify maintenance data

February 2002
Browse input View /Modify maintenance data

February 2002
Browse input View /Modify Times and cycles

February 2002
Browse input View /Modify Times and cycles

February 2002
Browse Input Usage Guidelines
o Flight Data can be modified by this tool on the last version of Sage.
o After OnWing Processing has run, the data will be in the database.
At this point, Stored Record Maintenance should used to modify
the data.

February 2002
Input Data for SAGE
Input Data for SAGE GE/CFMI Proprietary Information Page 1

3 EFG
GE Aircraft Engines
Typical SAGE Operation
Enter Data
Data Source
Enter Data
Automated
Data Formatting Enter flight data:
(User Provided)
Via Enter Data program OR
Input Files
Via user created input file
OnWing Processing
Analyze Alerts Interactive Reports
- Provided with SAGE
- Provided by User
The Input Files
➥ Input data can be formatted on any platform in the
user’s environment.
➥ User is responsible for transferring files to

“OnWing Processing” platform
✽ Files are in ASCII (readable text) format to ease in transfer
Data Source
✽ Files can be transferred as automatic process implemented
by user
➥ GEM Users can execute SAGE’s AIF_to_IP program to

convert binary AIF to SAGE ASCII file.
➥ If “OnWing Processing” platform is not a PC,

user is responsible for transfer of Input Files
generated via “Enter Data”

SAGE Input Formats

ADEPT “Mode 1” and “Mode 2” input files
✽ single or multi-record data file ADEPT File Extensions
.DT2 -- ADEPT Mode 2 (ADEPT 10)
✽ cruise and takeoff records only .DT1 -- ADEPT Mode 1 (ADEPT 8)
(maintenance records are ignored)
SAGE “Generic” Input

✽ single or multi-record data file
✽ cruise, takeoff, climb or maintenance records
✽ format -- parameter names, followed by values
✽ files can be generated either:
◆ outside of SAGE system (e.g. user developed software)
◆ using “Enter Data”
SAGE File Extensions
.SGE -- SAGE Generic Input
Data Files

Sample ADEPT “Mode 1” Input Format
Details defined in ADEPT 7, ADEPT 8 and ADEPT 10
Technical Memorandums
✽ Cruise or Takeoff data
✽ 3 lines per flight record
✽ Maintenance and engine change records ignored
✽ File extension of .dt1 or .DT1
A1234 30586 30 31030 0 0-327353700603600 0 0 0 0 0 0
21602140 0 0 835 835 0 0 889 889 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0211001100000
A1234 30586 50 2 0 0 2 17 0 0 0788 0 0 0 0 0 0
0 0 0 0 0 902 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0001000000000
A1234 30586 50 2 0 0 1 17 0 0774 0 0 0 0 0 0 0
0 0 0 0 901 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0010000000000
A1234 30686 100 2 0 0 2 10 0 0 0716 0 0 0 0 0 0
0 0 0 0 0 836 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0001000000000
A1234 30686 100 2 0 0 1 10 0 0705 0 0 0 0 0 0 0
0 0 0 0 842 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0010000000000
A1234 30786 40 31040 0 0-297403500590583 0 0 0 0 0 0
22402180 0 0 822 820 0 0 878 880 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0211001100000

Sample ADEPT “Mode 2” Input Format
Details defined in ADEPT 10 Technical Memorandum
✽ Cruise or Takeoff data
✽ 7 lines per flight record
✽ Maintenance and engine change records ignored
✽ File extension of .dt2 or .DT2
B1234061193120402 9 180232 88814826815853
0878108782087810878209690973097209710000
1111 0 147 147
0
0037300373003730037300088000880008800088
B12340406930339031733 -3838193901669675664702 -060 -120 -070 -090

1296131312951328085350853508535085350903090609050905 0 2 2 1 6 815 3
62 59 61 6048524346 1111 0 077 078
087008700870086007300770077007600920092009200920119131122139
0002200022000220002200006000060000600006
001002002001002005009002312212158264271201137285
*Comment line
B1234040793041303 -4088143901661669659689 -040 -090 -050 -070
1261127712611291084370843708437084370897089908990899 1 1 2 1 5 416 3
60 56 58 5648524446 1111 0 080 078
086008700870086007200760077007500940093009300930112124117133
0002900029000290002900008000080000800008
002002002001001002009001251172169273242193151298

Sample “Generic” SAGE Input Format

Delimiter DELIMITER = #
*FORMAT
AIRID#A#FPHASE#A#FDATE#A#
Input IBE1#I#IBE2#I#IVS12#I#ZALT#R#ZT1A#R#ZPCN12-1#R#ZPCN25-
1#R#ZT49-1#R#
Parameters ZPCN12-2#R#ZPCN25-2#R#ZT49-2#R
{
Input
Values
Multiple
records
*VALUES
B777#CLIMB#11-Jun-1997 14:48:43#
0#0#0#20000#-2#91#101#701#92#102#702
*VALUES
B777#CLIMB#12-Jun-1997 15:00:00#
0#0#0#20000#-2#91#101#701#92#102#702
*VALUES
B777#CLIMB#13-Jun-1997 12:30:15#
0#0#0#20000#-2#91#101#701#92#102#702
{ One Flight Phase
Per File
*VALUES
B777#CLIMB#14-Jun-1997 16:10:45#
0#0#0#20000#-2#91#101#701#92#102#702
*VALUES
B777#CLIMB#15-Jun-1997 18:48:14#
0#0#0#20000#-2#91#101#701#92#102#702
See Appendix for Details

Required File Extensions
ADEPT Mode 1 ADEPT Mode 2
.dt1 .dt2
.DT1 .DT2
SAGE Generic FILES WITH OTHER

EXTENSIONS ARE
.sge IGNORED
.SGE

Directories used by Input Processor
Needs to be on the
computer platform with
“OnWing Processing”
FILES TO BE PROCESSED
GO HERE

Summary
➥ Input data can be formatted by the user on any platform
➥ Three (3) input file formats are acceptable
➥ Properly formatted input files must ultimately reside on

the same platform as the “OnWing Processing” software

OnWing Processing
OnWing Proc GE/CFMI Proprietary Information

Page 1
February 2002
What is OnWing Processing?
o OnWing Processing is the

operation for processing
Cruise, Climb and Takeoff
data used for Engine
Condition Monitoring.

Page 2
February 2002
When do I use OnWing Processing?
“On-Wing Processing” is a “background” operation

to process engine monitoring data.
✽ on demand -- input data in the queue are processed
upon the manual execution of the
“On-wing Processing” function
✽ automatically -- input data in the queue are processed
at pre-set times / intervals based on
the settings in Auto SAGE

Page 3
February 2002
OnWing Processing
OnWing Processing
These are the number

Data Source Enter Data Input
crunching programs
n Processing which perform the actual
condition monitoring
Automated calculations.
Data Entry Single
o Record
Functions
Initialization
Input Files &
p Smoothing
OnWing Processing -- DOS Window

(indicates progress from step to step)
Alerting
q
Third Party Database

r Compression
Report Files
Auto
s Reports
(Optional)

Page 4
February 2002
OnWing Processing
Automated OnWing
OnWingprocessing
processing
Data Entry window
window
ItItisisaaDOS
DOSprogram.
program. Auto
AutoReports
Reports
(Optional)
(Optional)
Input Files
Analyse
Analyse
OnWing Processing Alerts
Alerts
Third Party Database :

-Access
-Oracle
-…..
Report Files
Error log

Page 5
February 2002
OnWing Processing
Input Processor Alerting
✽ Loads flight data ✽ Tests for alert conditions
✽ Loads engine removals/installations (user-specified)
✽ Handles maintenance records ✽ Allows for combination alerts

✽ Uses generic and ADEPT file formats ✽ Cancel alerts for status changes
(optional)
Single Record Function Compression

✽ Performs analytic calculations ✽ Compresses records in data base
(pre--selected by user) ◆ automatically per user criteria
✽ Provides limit checking validation ◆ “on demand” per user selections
✽ Calculates parameter divergences ✽ Allows user defined parameters
(usually “smoothed” trend levels)
Initialization and Smoothing Automatic Reporting

✽ Performs initial average calculations ✽ Generates default reports for newly
✽ Performs exponential smoothing processed data
✽ Allows for re-initialization (cruise, takeoff, and/or climb records)
✽ Calculates OATL with cruise update

(optional)
Page 6
February 2002
Input Processor Functionality

o Reads files of flight data from queue directory
sage\queues\automatic
o Performs mass units conversion by aircraft_id (where applicable)
o Stores data to database ready to be processed

o Moves input file to either
sage\files\data_files\processed
or
sage\files\data_files\rejected
o Writes error messages to a daily log file

sage\files\log_files\error_log\owp_ip_todaysdate.err

Page 7
February 2002
Directories used by Input Processor
AFTER PROCESSING FILES

MOVED TO ONE OF THESE
ERROR LOGS
FILES TO BE PROCESSED
GO HERE

Page 8
February 2002
Where did my input files go?

✽ Processing is successful if any reading in input file is
stored to the database.
✽ If processing successful, input file moved to
✽ sage\files\data_files\processed
✽ Otherwise, moved to
sage
✽ sage\files\data_files\rejected
files
data_files
processed rejected

Page 9
February 2002
SAGE Input -- 3 Formats Accepted

ADEPT “Mode 1” and “Mode 2” input files
✽ single or multi-record data file File Extensions to Indicate ADEPT Format
.DT2 -- ADEPT Mode 2 (ADEPT 10)
✽ cruise and takeoff records only .DT1 -- ADEPT Mode 1 (ADEPT 8)
SAGE “Generic” Input

✽ single or multi-record data file
✽ cruise, takeoff, climb or maintenance records
✽ format -- parameter names, followed by values
✽ files can be generated either:
◆ outside of SAGE system (e.g. user developed software)
◆ using “Enter Data”
File Extension to Indicate “Generic” Format
Data Files .SGE -- SAGE Generic Input

Page 10
February 2002
Storage Criteria
o Aircraft must have all engines installed for

flight data to be stored
o Flight data already stored in database
✽ not overwritten
✽ unless “ALLOWOVERWRITEINPUT” switch = YES

Page 11
February 2002
SAGE Monitoring Functionality

Cruise Takeoff
✽ Cruise Trending ✽ Takeoff Performance
(OATL /EGT Margin)
✽ Oil Monitoring
✽ Takeoff Derate
✽ Vibration Monitoring
✽ Divergence
(ETOPS)
Climb (only CFM56-3 & GE90)
✽ VSV Monitoring ✽ Margins for MCT Operation
✽ OATL with Cruise Update (ETOPS)
✽ Divergence ✽ Climb Derate

✽ Divergence
Varies
Varies by
by engine
engine model
model and
and data
data availability
availability
Page 12
February 2002
Initializing Trends
o Calculation similar to ADEPT
2-sigma screening to eliminate outliers
o Invalid records ignored

when missing critical parameters (NSI 7001, 7002 )
o Looks for “NUMRECSTOINIT” good records

o Forces initialization in
“MAXRECSTOCHECKINIT” records
o User control of data storage
Page 13
February 2002
Initialization Example
Store input values associated
Store input values associated
NUMRECSTOINIT = 10 * with the initialization records
with the initialization records
(optional)
* default value / user controlled (optional)
aircraft_id engine_position flight_datetime ZALT ZT1A ZXM ZPCN12 ZPCN25 IBE1 IBE2...
3EK02 1 8/18/96 10:56:00 PM
flight_datetime DEGT Used?
3EK02 1 8/19/96 3:31:00
8/18/96PM10:56:00 PM -15.98668 NO
3EK02 1 8/20/96 4:13:00
8/19/96PM3:31:00 PM -8.561707 YES
3EK02 1 8/22/96 3:45:00
8/20/96PM4:13:00 PM -10.58099 YES
3EK02 1 8/22/96 8:29:00
8/22/96PM3:45:00 PM -8.746704 YES Store raw
number of flight Store raw
number of flight 3EK02 1 8/23/96 6:18:00
8/22/96PM8:29:00 PM -8.445496 YES values used
records used values used
records used 3EK02 1 8/25/96 1:21:00
8/23/96PM6:18:00 PM -5.963196 YES in initialization
in initialization in initialization
in initialization 3EK02 1 8/26/96 5:19:00
8/25/96PM1:21:00 PM -0.48999 YES calculations
3EK02 1 8/27/96 6:23:00 PM5:19:00 PM calculations
8/26/96 -6.410706 YES (optional)
3EK02 1 8/27/96 6:42:00
8/27/96PM6:23:00 PM -5.963196 YES (optional)
3EK02 1 8/27/96 7:03:00
8/27/96PM6:42:00 PM 1.88999 NO
3EK02 1 8/28/96 2:19:00
8/27/96PM7:03:00 PM -6.410706 YES
8/28/96 2:19:00 PM -5.003113 YES
DEGT initialization value: -6.85758
First ten* records do not meet the 2-sigma criteria,

thus additional records are used.
Page 14
February 2002
Exponential Smoothing Technique
smoothed
smoothednew = smoothed ++α α((raw - smoothed ))
new = smoothedold
old rawnew
new - smoothedold
old
decreasing α less sensitivity to raw data variation

increasing α more sensitivity to raw data variation
Recommended
Recommendedsmoothing
smoothingconstant:
constant: 0.2
0.2 (pre-configured)
(pre-configured)

Page 15
February 2002
Smoothing with Outlier Protection

Raw Values Smoothed Values
-15..-10...-5....0....5 -15..-10...-5....0....5
G G
G negative outlier, G
G then positive outlier; G
G trend not updated G
G G
G G
G G
G G
G G
G G
G G
G G
G second point confirms true shift; G
G trend updated for both records G
G G
G G
G G
G G

Page 16
February 2002
Generating Alerts
o Generates “Individual” and “Combination” alerts

o Generates alerts on input, raw calculated, or smoothed
parameters
o Alerts now include Numerical Status Indicators (NSI’s)
✽ warnings of data processing problems / errors
✽ examples: missing data which are required, out-of-range data
o Constituent alerts used to generate “combination” alerts

also include Numerical Status Indicators

Page 17
February 2002
Compressing Data
Purpose of Compression
✽ Free up database space
✽ Speed up processing
✽ Summarize historical data
Copies one flight record per month of

smoothed data -- same as in ADEPT 10
✽ Saves user definable parameters for the
compression record
✽ Saves alert output quantities for the month
aircraft_id engine_position flight_phase installation_datetime flight_datetime alert_code engine_serial_number quantity
NAV03 3 CRUISE 1/1/81 12:01:00 AM 9/1/85 10018 740179 3
NAV03 3 CRUISE 1/1/81 12:01:00 AM 8/1/85 10018 740179 1
NAV03 3 CRUISE 1/1/81 12:01:00 AM 8/1/85 10005 740179 1
NAV03 3 CRUISE 1/1/81 12:01:00 AM 5/1/85 10018 740179 2

Page 18
February 2002
Generating Reports
o Cruise, Takeoff, or Climb report generated for
each with newly processed data
o Report output in sage\reports\repprnt
(or other user controlled file)
o Each aircraft / report in a separate file

o Report formats
◆ 13 cruise
◆ 4 takeoff
◆ 3 climb
Page 19
February 2002
1
REPORT ID: CRTRND GE ENGINE CONDITION MONITORING PROGRAM SAGE V2.1 PC Dec 1997 REPORT DATE: 1/ 8/98
CRUISE PERFORMANCE MONITORING - MOST RECENT RECORDS PAGE: 1
AIRTYP ENGTYP ENGSN INSDAT N1MOD TCC FNRAT CONFIG CONTROL SELECTOR
3EK04 -1 DC10-10/-30 CF6-50C2 455237 960717 ** * ******* PRE_P100 (SCALES VARIED)
SMOOTH -30..-20..-10...EGT..10...20...30 -1....X....0....X...N2....X....2....X....3 CRZ OIL OIL MAINT ALT
DATE VIB..1....2....3 -6...-4...-2...F/F...2....4....6 3....4...VSV...6....7 SLOATL TMP PRS CODES CTR
72596A R= .9 V= .2 -11.2 1.41 VSV=-999.00 N2= .60
72596B R= .9 V= .2 -11.2 1.41 VSV=-999.00 N2= .60
80296C .V R G . . F . 2 X
83196 .V R G . . F . X 2 100 52. 2
90196 .V R G . . F . X 2 103 56. 4
90196 .V R G . . F . X 2 91 55. 2
90296 .VR G . . F . X 2 100 55. 2
90296 .VR G . . F . X 2 90 54. 2
90396 .V R G . . F . X 2 102 51. 3
90396 .V R G . . F . X 2 90 50. 2
90396 .V R G . . F . X 2 88 50. 1
90496 .V R G . . F . X 2 95 53. 1
90596 .VR G . . F . X 2 90 55. 2
90696 .V R G . . F . X 2 94 55. 2
90696 .V R G . . F . X 2 102 53. 1
90696 .VR G . . F . X 2 98 53. 2
90796 .VR G . . F . X 2 102 53. 1
90996 .V R G . . F . X 2 100 50. 1
90996 .V R G . . F . X 2 90 50. 1
91096 .V R G . . F . X 2 100 50. 1
91196 .V R G . . F . X 2 93 53. 2
91196 .V R G . . F . X 2 93 53. 1
91196 .V R G . . F . X 2 102 53. 2
91496 .V R G . . F . X 2 97 51. 1
91596 .V R G . . F . X 2 85 55. 2
91696 .V R G . . F . X 2 95 50. 1
91796 .V R G . . F . X 2 103 54. 1
91896 .VR G . . F . X 2 100 55. 2
91896 .V R G . . F . X 2 86 54. 1
91996 .V R G . . F . X 2 96 52. 2
92096 .VR G . . F . X 2 100 52. 1
92096 .V R G . . F . X 2 92 51. 1
92096 .V R G . . F . X 2 90 51. 1
92196 .V R G . . F . X 2 105 55. 2
92296 .V R G . . F . X 2 89 55. 2
92396 .V R G . . F . X 2 92 54. 2
92396 .V R G . . F . X 2 97 54. 3
92396 .V R G . . F . X 2 92 51. 2
RAW DATA -30..-20..-10...EGT..10...20...30 -1....X....0....X...N2....X....2....X....3 CRZ MODULE CHG ALT
DATE VIB..1....2....3 -6...-4...-2...F/F...2....4....6 3....4...VSV...6....7 SLOATL MAINT CODES CTR
91896 .V R G . . F . X 2 1
91996 .V R G . . F . X 2 2
92096 *V G . . F . X 2 1
92096 .V R G . . F . X 2 1
92096 .V R G . . F . X 2 1
92196 V R G . . F . X 2 2
92296 .V R G . . F . X 2 2
92396 .V R G . . F . X 2 2
92396 . V R G. . F . X 2 3
92396 . V R . G . F . X 2 2

Page 20
February 2002
REPORT ID: CRDATA GE ENGINE CONDITION MONITORING PROGRAM SAGE V2.1 PC Dec 1997 REPORT DATE: 1/ 8/98
CRUISE PERFORMANCE DATA - MOST RECENT RECORDS PAGE: 1
AIRCRAFT AIRCRAFT ENG SERIAL ENGINE INSTALL N1 THRUST TCC

ID TYPE POS NUMBER TYPE DATE MOD RATING TMR CONFIG CONTROL SELECTOR
D B777-200 1 D1 GE90-76B 941014 ** ****** * BLOCK 3
2 D3 GE90-76B 960219 ** ****** * BLOCK 3
-------------------------- FLIGHT DATA -------------------------- ------ RAW DEVIATIONS -------
ENG A/C ISO -MAX CONT--
DATE/ BLD PK VLV ADP OIL FUEL BLEED FF VSV N2 EGT EGT N2 ALT
GMT TAT ALT MACH 1234 123 LRC 12 N1 PRES FLOW VSV N2 EGT N1K RATIO DOP (%) ( ) (%) (C) MAR MAR CTR
22796-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
22896-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
22896-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
900-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
22896-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
1000-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
30196-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
30296-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
30396-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
30496-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
30596-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
30696-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
30796-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
30896-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
30996-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
31096-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
31196-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
31296-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
31396-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
31496-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
31596-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
31696-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
31796-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
31896-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
31996-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0
32096-1 -5.0 37000. .830 11 11 1 00 90.00 62. 6550. .00 107.0 770. 93.26 .77 -99. 4.8 .00 4.7 43.1 -23. -2.9 1
800-2 90.00 62. 6180. .00 102.0 720. 93.26 .77 -5. -1.1 .00 -.2 -6.9 27. 2.0 0

Page 21
February 2002
Running OnWing Processing

o To run now
✽ Put input file(s) in automatic
processing folder
✽ Execute OnWing Processing
o To run at regular interval AutoSAGE

“running”
✽ Use AutoSAGE / Wait until interval

Page 22
February 2002
AutoSAGE
Controls time and conditions at which
OnWing Processing will automatically run
✽ At fixed intervals or
at well-defined times
✽ On user-defined
days of the week
✽ Not at all:
Can temporarily
disable the scheduler
✽ Should not run if
OnWing Processing
already active
✽ Starts at “boot”
Page 23
February 2002
Interactive Reports
Interactive Reports GE/CFMI Proprietary Information Page 1

February 2002
What is Interactive Reports?

o Interactive Reports is used to create
graphical and tabular reports for
output to the screen or to a printer.
o Using Interactive Reports you can:
– Generate and view standard
“ADEPT” style trend plots.
– Create graphical or tabular reports
for user-selected aircraft or engines,
for user-selected parameters.
– Export selected data to a Microsoft
Excel spreadsheet.

February 2002
When do I use Interactive Reports?

o When you need to view reports that were automatically
generated during on-wing processing, without printing them.
o When you want to do a quick review of a specific engine’s or

aircraft’s trend levels.
o When you want to make a specific engine’s data available

outside of the SAGE database for further analysis.
o When you want to view a histogram of accumulated data for a

parameter.

February 2002
Interactive Reports “Toolboxes” (1/2)

o Generate “Tools”
– Graph
• Generate a trend graph for selected parameters.
– Spreadsheet
• Select and export data to a Microsoft Excel spreadsheet.
– Accumulator
• Create a histogram for a particular parameter from accumulated data.
(NOT
NOT Currently Available)
– Trend/Tabular
• Generate traditional “ADEPT” trend plots for selected aircraft and/or engines.
– No DATA
• Find Aircraft/engines for which there are no data processed for a given time.

February 2002

February 2002
o
oDisplay
Display“Tools”
“Tools”
–– View
View
•• Select
Selectand
andview
viewor
or
print
print“ADEPT”
“ADEPT”trend
trend
plots
plotson-screen.
on-screen.

February 2002
Creating a Graph
o There are four (4) steps to creating a graph:

1) Select the engines for which you want to graph data.
2) Select the number of records and/or a date range over which
to graph the selected parameters.
3) Choose the parameters to graph.
4) For each parameter, elect to plot raw values, smooth values,
or both, then display your graph!

February 2002
Creating a Graph

February 2002
Creating a Graph, Step 1: Select Engines

1) Select the button labeled Graph
from the switchboard. The
Aircraft and Engine Selector
2) Select an aircraft using the
filters at the top of the screen
and/or in the “Additional
Filters” box.
3) Select one or more engines by
clicking on its row in the
“Filtered Data” list at left.
4) Select Add > to move engines
to the “Items Selected” list, or
< Delete to remove them from
that list.
5) When finished, select OK. The
Select Parameters screen is
displayed.
February 2002
Creating a Graph, Step 2: Report Definition

1) Select the flight phase for this
graph from the drop down list.
2a) Enter the number of records
to process in the Data
Selection Criteria box, after
selecting “Plot most recent”
option, or...
2b) Select the “Plot last” or “Plot
all records within date range”
options and enter a from and
to date in the Date Range box.
Q:
Q:Why
Whyisn’t
isn’tthe
theParameter
ParameterName
NameSelection
Selectionscreen
screen
displayed
3) Select the button labeled displayedfirst,
first,BEFORE
BEFOREthe
theReport
ReportDefinition
Definitionscreen?
screen?
A:A:By
Parameter Selection. The Byusing
usingthe
theSave
SaveReport/Load
Report/LoadReportReportfeature,
feature,the
the
Parameter
ParameterSelection
Selectionscreen
screenwill
willnot
notbe
beaccessed
accessedas as
Parameter Name Selection frequently
frequentlyas
asthe
theReport
ReportDefinition
Definitionscreen.
screen.We
Wehave
have
assumed
assumed that users will prefer this method to oneinin
that users will prefer this method to one
screen is displayed. which
whicheach
eachgraph
graphisiscreated
created“from
“fromscratch.”
scratch.”

February 2002
Creating a Graph, Step 3: Select Parameters

1) If desired, use the Filter
Criteria at right to limit the
parameter names shown.
(This list may already be
filtered by flight phase if
previously selected.)
2) Select a parameter from the
Available Parameters list,
and use the down arrow
button (or double-click a
name) to move it to the
Selected Parameters list.
3) Continue until you have
selected all desired
parameters.

February 2002
Creating a Graph, Step 4:
Select Raw or Smooth Data
1) For each parameter, click the
appropriate checkbox for raw
or smooth values, or both.
2) For each parameter, decide if
you wish to plot that
parameter, tabulate it, or both.
3) After 1 and 2 are completed for
each parameter, select OK.
One Graph screen will be
displayed for each Engine ID
selected.

February 2002
Creating a Graph, Step 4:
Save your report (optional)
o Giving a name to your report you will have the possibility to
recall that particular report on an other Aircraft/engine in the
future.
o In this example the name indicates what parameters will be

plotted.

February 2002
The drop down lists at the top of the
The drop down lists at the top of the
The Graph Screen

screen can be used to dynamically
screen can be used to dynamically
change the graph. Likewise, the
change the graph. Likewise, the
record count in the box at right can
record count in the box at right can
be changed.
be changed.
The parameter drop down lists

The parameter drop down lists
can be used to dynamically
can be used to dynamically
select a new parameter to be
select a new parameter to be
displayed in this column.
displayed in this column.
Click on a data point to see the

Click on a data point to see the
values for all parameters
values for all parameters
displayed here in the “Points
displayed here in the “Points
Selected” box.
Use this button to Selected” box.
Use this button to
switch between plot
switch between plot
and table views.
and table views.

February 2002
Exporting Data to a Spreadsheet

February 2002
Exporting Data to a Spreadsheet

o Interactive Reports can be used to export data to a spreadsheet.
o The process involves four (4) steps:
1) Select the engines for which you want data.
2) Select the number of records and/or a date range for the data.
3) Choose the parameters to export.
4) For each parameter, elect to export raw values, smooth values,
or both, then select OK to export!
o Steps 1 through 3 are the same as performed for creating a graph.
You must have Microsoft Excel version 5 or

later loaded on your PC to use this feature.

February 2002
Exporting Data to a Spreadsheet, Step 4:
Select Raw and Smooth Data
1) For each parameter, decide
if you want to export raw or
smooth values, or both.
2) Select the appropriate
checkbox for raw and/or
smooth values.
3) Select OK. Microsoft Excel
is opened automatically,
and each engine serial
number’s data is
transferred to a worksheet
within Excel.

February 2002

February 2002
Accumulator

February 2002
Accumulator 1

February 2002
Accumulator 2

February 2002
Accumulator 3

February 2002
Accumulator 4
o With the window shown one
can change the Bands
values.

February 2002
Generating Trend Plots

February 2002
Generating Trend Plots

o Interactive Reports can be used to generate traditional ADEPT
trend plots “on demand”.
o There are four (4) steps required to generate them:

1) Select the aircraft (or engines) to plot.
2) Select desired trend plots from a list of 20 available types,
and define the date range for which you want data.
3) Select the trend plots to view.
4) View the trend plots using the Report Viewer.
o In addition to on-screen viewing, the trend plots may also be printed.

February 2002
Generating Trend Plots, Step 1:
Select Aircraft or Engines
1) Select the button labeled Trend/Tabular
from the switchboard. The Aircraft and
Engine Selector screen is displayed.
2) Restrict items in the “Filtered Data” list
using the filters at the top of the screen
and/or the “Additional Filters” box.
3) Select items by clicking on their row
in the “Filtered Data” list.
4) Select Add > to move an item to the
“Items Selected” list, or <Delete to
remove them from that list.
5) When finished, select OK. The Generate To directly select engines instead of
Trend Selector screen is displayed. aircraft, click on the Engines radio button.

February 2002
Generate Trend Plots, Step 2:
Select Plot Type(s) and Date Range
1) Select one or more reports from the list at left.
2) Enter or select “From” and “To” dates to define a range of data

to plot.
3) Select OK when finished. The Report Viewer screen will be

displayed.

February 2002
Generate Trend Plots, Step 2:
Select Plot Type(s) and Date Range
The Select Standard Set

button automatically selects
the trend report for Climb,
Cruise and Takeoff data.

February 2002
Generate Trend Plots, Step 3: Select Reports to View
1) Select one or more plots

to view by clicking on
rows in the Report Viewer
screen.
Reports can be sorted
by Name, Size, Type,
or Modified Date for
easier selection.

View to display the
selected trend plot(s).
Each will be displayed
on its own screen.

February 2002
Generate Trend Plots, Step 3: Select Reports to View

February 2002
Generate Trend Plots, Step 4: View Reports

o Each report will be displayed
on its own screen.
o Each report can be:
– closed
(or all reports closed)
– zoomed larger or smaller
(or all reports zoomed)
– Printed
– Save As a local file

February 2002
An
Analert
alerthas
has
been
beengenerated
generated
as
asshown
shownininthis
this
Column
Column

February 2002

February 2002
No Data Available

February 2002
No Data Available

February 2002
No Data Available

February 2002
View reports after On Wing processing

February 2002
View reports after On Wing processing

February 2002
Interactive Reports Usage Guidelines

o Save time! Use the Save Report/Load Report feature to save
common report (or export) definitions for re-use.
o Try the various selector screen filters if you are having trouble
locating a specific engine or aircraft.
o Remember that you can use Interactive Reports to view both plots
generated “on demand” and automatically generated trend plots.
o When plotting data for multiple aircraft or engines it is easy to

“lose” a screen. Use the “Windows” menu to directly select the
screen you want to see.

February 2002
Analyze Alerts
Analyze_Alerts GE/CFMI Proprietary Information Page 1

February 2002
What is Analyze Alerts?

o Analyze Alerts is used to
view/discover generated alerts
and to view the fleet alert
summary.
o Using Analyze Alerts you can:
– View existing alerts.
– Obtain details for the alert.
– Obtain a fleet alert summary.
– View engine alert history.
– Create engine notes.
– Put an engine on a watchlist.
– Generate reports associated with
a particular alert

February 2002
When do I use Analyze Alerts?
o After a run by OnWing Processing to determine the health of

your engines.
o When you want to determine the cause for a particular alert.
o When you want to determine alerting trends in a particular engine.
o When you want to determine alerting trends in your fleet.

February 2002
Analyze Alerts “Toolboxe”
o Alert Summary “Tools”
– Engine Alerts
• View Alerts by Engine
• View Alert Details
• View Engine History
• Change Alert Status
• Create Engine Note
• Put Engine on Watchlist
• Generate Trend Report
– Fleet Alerts
• View summary of alerts for your fleet

February 2002
Analyze Alerts “Toolboxe”

February 2002
View Generated Engine Alerts
o There is but one step to accomplish:

1) Select the Engine Alert switchboard button.
2) The Engine Alerts screen appears.

February 2002
View Generated Engine Alerts

February 2002
View Details of a Particular Alert

View Details from Engine
Alerts screen.
2) The Alert Details screen
appears.
3) Observe the Limits and the
Parameter value.

February 2002
Individual alerts

February 2002
Individual alerts

February 2002
Individual alerts
Smooth
Smooth 0
-12,83534
Raw
Raw
-5 +5
9,238245
-3,597095

February 2002
NSI alerts

February 2002
NSI ALERT
AAparameter
parameterisismissing
missing
as
asshown
shownby bythe
thevalue
value
equal
equalto
to-999,0
-999,0

February 2002
Combination alerts

February 2002
Combination alerts

February 2002
Combination alerts

February 2002
View Fleet Alert History

February 2002
o There are two (2) steps to show the fleet history:

1) Determine the Fleet and Date range criteria.
2) View the results.

February 2002
Alert History, Step 1: Select Criteria

1) Select the button labeled Fleet Alerts from the switchboard.
The Define Fleet Alert Report screen is displayed.
2) Select the Date Range.
3) Select Fleet/Alert Criteria.
4) Select the OK button.

The Fleet Alert Summary screen is displayed.

February 2002

February 2002
Alert History, Step 2: View Results
1) Alerts are summed by alert code within alert

category within flight phase.
2) You can Save or Print the results.

February 2002

February 2002
Engines on Watchlist

February 2002

February 2002

February 2002

February 2002
Analyze Alerts Usage Guidelines

o For Fleet Alert Summary, one should limit the selection criteria
(date range and fleet/alert criteria) to avoid memory problems.
o On the Preference screens, choosing no preferences results in

a retrieval of everything.
o The Engine History screen shows more than just alert history.
o The number of View Details screens are limited to 10 at a time.

February 2002
Stored Record Maintenance GE/CFMI Proprietary Information Page 1

August 1998
What is Stored Record Maintenance?

o This program is where you maintain your aircraft and
engine data in the database.
o Store Record Maintenance is used to:

– Correct inaccurate input measurements
– Delete flight data, initialization data, alert output and
compressed data
– Edit maintenance actions, times & cycles data and engine notes

August 1998
When do I use Stored Record Maintenance?
o When you realize an input parameter’s value is incorrect and

you want to correct its value and reprocess the data.
o When you want to delete “orphaned” flight records.
o When you want to delete an initialization record to allow for an new
“original” initialization record, instead of re-initializing.
o When you want to edit already entered maintenance actions.
o When you want to correct the hours and cycles values for an engine.

August 1998
Stored Record Maintenance “Toolboxes”
o Flight Data
– Modify Flight Records
• Modify erroneous measurement
values to correct a flight record.
– Delete Flight Records
• Delete one or more flight records
– Delete Alert Output
• Delete alert output
– Delete Initialization
• Delete and initialization record
– Delete Compressed Data
• Delete compressed data

August 1998
Stored Record Maintenance “Toolboxes”

o Engine Data
– Maintenance
• Edit or delete past
maintenance actions
– Notes
• Edit or delete past
engine notes
– Times & Cycles
• Edit or delete engine
hours and cycles data

August 1998
Modifying Existing Flight Records
o To modify existing flight data, follow these three (3) steps:

– 1) Select the aircraft.
– 2) Select the flight record(s) to modify.
– 3) Edit the flight record input data.
– 4) Confirm your changes.

August 1998
Modify Flight Data, Step 1: Select Aircraft

Flight Data on the switchboard.
The Aircraft Selector screen is
displayed.
2) Select the aircraft you want.
3) Select OK. The Flight Record
Selector screen is displayed.

August 1998
Modify Flight Data, Step 2:
Select Flight Records
1) Select the desired Flight Phase
from the drop down list.
2) Select the flight record(s) you
want to modify by clicking its
row, or use the date range
fields to specify a “From” and
“To” date then select Apply.
3) Select OK. The Flight Record

August 1998
Modify Data
1) Locate the parameter(s) that need to
be modified, and make the changes
from the keyboard.
2a) Select the Apply to Current Record
button to confirm your changes, or,
2b) If these changes ought to apply to all
remaining records, select the Apply
to Remaining Records button.
3) Navigate forward and backward
through the list of selected flight The
TheModify
ModifyData
Datascreen
screenisisessentially
essentially
records using the Previous Record the
thesame
sameasasthe
theEnter
EnterData
Datascreen.
screen.
and Next Record buttons.
4) When finished, Select OK.

August 1998
Confirm Changes
1) A confirmation screen will appear
after you select OK on the
Modify Data screen.
2) If you are sure you want to make

your changes, select OK.
Changes
Changesmade madeusing
usingModify
ModifyData
Datawill
willbebe
applied
appliedtotothe
thedatabase
databaseimmediately
immediatelyafter
after
you
youselect
selectOK.
OK.However,
However,the thedata
datawill
willnot
not
be processed until the next execution of
be processed until the next execution of
On-Wing
On-WingProcessing.
Processing.

August 1998
Stored Record Maintenance Usage Guidelines
o Remember that, unlike Enter Data, changes take effect in the

database IMMEDIATELY upon confirmation.
o Altered records will not be processed until the next execution of

On-Wing Processing.
o For tips on using the Modify Data screen, review the Enter Data
program module.

August 1998
On-Wing Reprocessing
OnWing Reprocessing GE/CFMI Proprietary Information Page 1

August 1998
What is On Wing Reprocessing?

o On-Wing Reprocessing marks user selected flight records
for reprocessing.
o Three types of reprocessing can be performed:
– Reprocess flight data through the standard background processes.
– Compress an engine position’s flight data “on demand”.
– Reinitialize an engine’s flight data to create new starting average
values for trending.

August 1998
When do I use On-Wing
Reprocessing?
o When you update alert limits,
and want to reprocess data to
see the effects.
o When you alter smoothing
coefficients, and want to
reprocess data to see the
effects.
o When you want to compress
flight data on demand.
o When you want to reset trend
initial levels.

August 1998
On-Wing Reprocessing “Toolbox”

o Reprocess “Tools”
– Flight Data
• Select flight records
for reprocessing, and
set the level of
reprocessing.
– Compression
• Select flight records
for compression.
– Re-initialization
• Select the oldest
record desired for use
in initialization.

August 1998
Flight Data Reprocessing
o Reprocessing Flight Data requires three (3) steps:

1) Select aircraft for reprocessing.
2) Select flight records for the selected aircraft.
3) Choose the level of reprocessing to be performed.
4) Confirm your selections.

August 1998
Flight Data Reprocessing, Step 1:
Select Aircraft
Flight Data on the
switchboard. The
Reprocess Selector
2) Select the aircraft, or
engines, for which you
want to reprocess data.
3) Select OK. The Reprocess
Flight Data screen is
The
Thetotal
totalnumber
numberofofrecords
recordscurrently
currentlymarked
marked
displayed. for
for any level of reprocessing are displayedinin
any level of reprocessing are displayed
the
thelower
lowerright
rightcorner
cornerofofthe
thescreen.
screen.

August 1998
1) Limit the Flight Phase using
the drop down list, if desired.
2) Specify a date range using
the date fields, if desired and
select the Apply button.
3) Select flight records using the
list box on the left by clicking
on one or more rows, or use
the Select All button.
The
Thetotal
totalnumber
numberofofrecords
recordscurrently
currentlymarked
markedforforany
any
level of reprocessing are displayed in the lower right
level of reprocessing are displayed in the lower right
corner
cornerofofthe
thescreen.
screen.This
Thisdoes
doesNOT
NOTinclude
includethe
the
records being selected in this session.
records being selected in this session.

August 1998
Select Reprocessing Level
1) Select the level of
reprocessing by clicking on
one of the three radio buttons
in the “Set Reprocessing
Options” box.
The Reprocess Confirmation
>>ALL
ALLselected
selectedflight
flightrecords
recordswill
willbe
bemarked
markedusing
usingthethechosen
chosenoption.
option.
>>Complete Reprocessing and Re-smooth and Re-alert
Complete Reprocessing and Re-smooth and Re-alert will cause will cause
the
theselected
selectedrecords
recordsand
andALL
ALLsucceeding
succeedingrecords
recordstotobe
bereprocessed,
reprocessed,and
and
the succeeding records are NOT counted in the records-to-reprocess
the succeeding records are NOT counted in the records-to-reprocess count count
>>Reprocessing
Reprocessingoccurs
occursatatthe
thenext
nextexecution
executionofofOn-Wing
On-WingProcessing.
Processing.

August 1998
Confirm Selections
1) Review the summary of records selected in this session, and for
the entire database.
2) Review the definition of the option selected at right if you are
unsure of the implications of this option.

August 1998
Compress Flight Data
o “On Demand” compression requires two (2) steps:

1) Select the engine to compress.
2) Select flight records for the selected engine.

August 1998
Compress Flight Data, Step 1: Select Engine

Compression on the
switchboard. The Engine
2) Select the engine for which you
want to compress data.
3) Select OK. The Compress Flight
Data screen is displayed.

August 1998
Compress Flight Data , Step 2:
1) Limit the Flight Phase using
the drop down list, if desired.
2) Select the most recent record
to compress by clicking its
row, or use the Compression
Options and select Apply.

August 1998
Re-Initialize Flight Data

o Re-Initialization takes two (2) steps:
1) Select the engine for re-initialization.
2) Select oldest flight record in the date range over which
you want to re-initialize.

August 1998
Re-Initialize Flight Data , Step 1:
Select Engine
Re-Initialization on the
switchboard. The Engine
2) Select the engine you want
to re-initialize.
3) Select OK. The Re-initialize
Flight Data screen is displayed.

August 1998
Re-Initialize Flight Data , Step 2:
1) Select the Flight Phase
using the drop down list.
2) Select the record with the
oldest date/time where you
want re-initialization to begin
by clicking its row, or use
the date/time field provided.

August 1998
On Wing Reprocessing Usage Guidelines
o Remember! Selecting Complete Reprocessing or Re-Smooth

and Re-Alert will cause all succeeding flight records to also be
reprocessed in the same manner.
o Remember! Reprocessing does not occur until the on-wing

processing background process is executed.

August 1998
Fleet History
Fleet History GE/CFMI Proprietary Information Page 1

August 1998
What is Fleet History?

o Fleet History is used to view the
installation history of a particular
aircraft or of a particular engine.
o Using Fleet History you can:

– View all the engines that have
been installed on all the positions
of a particular aircraft
– View all the aircraft (and their
positions) that a particular engine
has been installed.

August 1998
When do I use Fleet History?
o When you want to view all the engines that have ever been
installed on a particular aircraft.
o When you want to view all the aircraft that a particular engine
has been installed.

August 1998
Fleet History “Toolboxes”

o Fleet History “Tools”
– Engine Installation History
Fleet History Process Flow
• View the history of a particular engine
Engine Aircraft
– Aircraft History History History
• View the engine installation history of
Installation
a particular aircraft History
Aircraft
Selector
Engine
Selector
View Aircraft/
View Installation Engine Installation
History History

August 1998
View an Engine Installation History
o There are two (2) steps to viewing an engine history:

1) Select the particular engine
2) View the engine history

August 1998
Engine History, Step 1: Select engine
1) Select the button labeled Engine

Installation History from the
switchboard. The Engine ID
2) Find your desired engine.
3) Select this engine.
4) Select the OK button. The
Engine Installation History

August 1998
Engine History, Step 2: View Installation History
1) Observe the Engine History.

2) If a print out of this information is
desired select the Print button.
3) When finished select the OK button.

August 1998
Fleet History Usage Guidelines
o At this point, installation history can be observed only 1 aircraft

or 1 engine at a time. Fleet history is not available.
o A similar method to the above can be employed to view a

particular aircraft’s history. Select Aircraft History from the
switchboard to accomplish.

August 1998
Parameter Library
Parameter Library GE/CFMI Proprietary Information Page 1

August 1998
What is Parameter Library?

o Parameter library provides a tool to
manage the trending parameters
stored in the SAGE database.
o Within Parameter Library you can:
– Define new engine or aircraft
parameters, including:
• Input/Output state
• User name (alias)
• Required status
• etc.
– Associate parameters with their

related aircraft or engine families

August 1998
When do I use Parameter Library?

o When you want to change the displayed name of a parameter
(the “user alias”)
o When you want to add a new parameter for SAGE to store

(It can then be smoothed, alerted and plotted on graphs or exported.)
o When you want to change the entry sequence of a parameter

(effects Enter Data only)
o When you want to alter the minimum or maximum limits for a parameter
(effects Enter Data only)
o When you want to delete parameters

(to save storage space, for instance)

August 1998
Parameter Library “Toolboxes” (1/2)
o Associations “Toolbox”
– Aircraft
• Modify aircraft parameter(s)
data entry sequence
– Engine
• Modify engine parameter(s)
data entry sequence.
– Parameter
• Modify a parameter’s
associations and data entry
sequence.

August 1998
Parameter Library “Toolboxes” (2/2)
o Parameter Definitions “Toolbox”

– View/Modify
• Create (add) a new parameter
• Modify an existing parameter
• Delete a parameter

August 1998
Adding a New Parameter
o There are four (4) steps involved in adding a new parameter:

1) Create the parameter
2) Select the family or families to associate with this parameter
3) Set parameter attributes
4) Define the new parameter’s data entry sequence (if applicable)
The
Thefollowing
followingexample
exampleisisfor
foran
anaircraft
aircraftinput
inputparameter.
parameter.

August 1998
Adding a New Parameter, Step 1:
Create the Parameter
1) Select the View/Modify button on the Parameter Definitions tab. The
Parameter Definition screen is displayed.
2) Select the Add button. The Add Parameter screen is displayed.
IfIfyou
youfirst
firstselect
selectaaparameter
parameterrow,
row,that
thatparameter’s
parameter’sdefinition
definition
will
willbe
becopied
copiedandandused
usedas
asthe
thebasis
basisofofyour
yournew
newparameter.
parameter.

August 1998
Adding a New Parameter, Step 1 (Continued):
Create the Parameter
1) Enter the new parameter’s
attributes in the “New
Parameter” column.
2) When finished select OK.

The Parameter Definition
3) Select Cancel on the

Parameter Definition
screen to return to the
switchboard.

August 1998
Choose Engine/Aircraft Association(s)
1) Select the Associations tab
on the switchboard.
2) Select the Parameters button
on the Associations tab.
3) Locate your new parameter in
the parameter list. Use the
Parameter Type and
Parameter Source lists to
“filter” the list of available
parameters.
4) Select your new parameter’s To
Toselect
selectonly
onlysmoothed
smoothedparameters,
parameters,click
clickhere.
here.
row, then select OK. The
Associations for Parameter

August 1998
Choose Engine/Aircraft Associations
1) Select the Add Associations button.

The Association Selection screen is
displayed.

August 1998
Choose Engine/Aircraft Associations
1) Select the Aircraft Family (or

Engine) , the Function Type
and the Flight Phase with
which you want this parameter
to be associated.
2) When complete, select OK. The

Family Association screen is
displayed.
E a ch fie ld is required, and associa tions must be made one

E a ch fie ld is required, and associa tions must be made one
a t a time for each family/function/phase combina tion.
a t a time for each family/function/phase combina tion.

August 1998
Set Input Parameter Attributes
(This page describes attribute settings for input parameters, only.)
1) Set this parameters required status to Yes or No, using the drop down list.
2) Set this parameter’s minimum and maximum limits
When finished, select OK. You will be returned to the Associations for
Parameter screen.

August 1998
Set Data Entry Sequence (Input Only)
1) On the Family Association screen,

select the new parameter’s row,
then select the Entry Sequence
button. The Entry Sequence
2) On the Entry Sequence screen,

select the Sequence Aircraft (or
Engine) button. The Modify Entry
Sequence screen is displayed.

August 1998
Set Data Entry Sequence (Input Only)
1) To change a parameter’s entry
sequence, select it’s row and
drag it to the new position in
the sequence.
2) To add another, existing input
parameter to the sequence,
select the Add button. You
Youcan
canalso
alsotype
typethe
the
new entry sequence
3) To delete a parameter from new entry sequence
number
numberininthis
thiscolumn
column
the sequence, select the totore-order parameters.
re-order parameters.
parameter’s row, the select
the Delete button.
4) When finished select OK. You
will be returned to the Entry After
Afterspecifying
specifyingthe
theentry
entrysequence,
sequence,the
thenewnew(input)
(input)
parameter
parameterisisnow
nowcompletely
completelydefined
definedtotothe
thesystem.
Sequence screen. Repeat
system.
Repeatsteps
steps11through
through44for
foreach
eachaircraft/engine
aircraft/enginefamily,
family,
flight
flightphase
phaseand/or
and/orfunction
functiontype
typecombination.
combination.

August 1998
Parameter Library Usage Guidelines
o When adding new parameters to SAGE, be sure to both:

– Define the parameter, AND...
– Associate the new parameter with the appropriate aircraft or
engine family
o If frequently used parameters have names that are not

meaningful to you, change their “user name” to what you want.
o Remember! If you delete a parameter, or association, data are

lost for ALL aircraft (or engines) using that parameter name.

August 1998
Maintain Smoothing
Maintain Smoothing GE/CFMI Proprietary Information Page 1

August 1998
What is Maintain Smoothing?

o Maintain Smoothing is used to control
the attributes (coefficients, outliers, etc.)
associated with smoothed parameters.
o Using Maintain Smoothing you can:

– View/Print all existing smoothing
parameters and their attributes
– Create, modify and delete smoothed
parameters.
– Assign smoothed parameters to
particular aircraft/engine combination.
– Modify the numerical values associated
with smoothed parameters.

August 1998
When do I use Maintain Smoothing?
o When you need to modify the smoothing coefficients.
o When you want to create additional smoothing parameters.
o When you want to permanently delete an existing

smoothing parameter.
o When you want to view existing smoothing parameters and

their attributes.

August 1998
Exponential Smoothing Technique
smoothed
smoothednew = smoothedold ++α
α((raw - smoothed ))
new = smoothedold rawnew
new - smoothedold
old
decreasing α less sensitivity to raw data variation

increasing α more sensitivity to raw data variation
Recommended
Recommendedsmoothing
smoothingconstant:
constant: 0.2
0.2 (pre-configured)
(pre-configured)
Maintain Smoothing GE/CFMI Proprietary Information

August 1998
Smoothing with Outlier Protection
Raw Values Smoothed Values

-15..-10...-5....0....5 -15..-10...-5....0....5
G G
G negative outlier, G
G then positive outlier; G
G trend not updated G
G G
G G
G G
G G
G G
G G
G G
G G
G second point confirms true shift; G
G trend updated for both records G
G G
G G
G G
G G
Maintain Smoothing GE/CFMI Proprietary Information

August 1998
Maintain Smoothing “Toolboxes”
o Smoothing “Tools”
Maintain Smoothing Process Flow
– Configure for an Application Configure Configure View
for an App. for a Param. Smoothing
• Control Smoothing Parameters Constants
for a particular Application Select Select Display ALL
Application Parameter Smoothing
Constants for
– Configure for a Parameter Select All Apps. and
Select Parameters
• Control All Applications for a Parameter
Application
particular Parameter Add Application Select Phase
Modify
Add Parameter Modify App. Constant
– View Smoothing Constants Modify Parameter Delete App. s
• View existing constants Delete Parameter Add Phase Select Phase
• Print existing constants

August 1998
Modifying Smoothing Constant for an Application
o There are three (3) steps to modifying a smoothing constant:

1) Select the particular smoothed parameter that you want to modify.
2) Select the application that you desire.
3) Modify the smoothed parameter’s values.

August 1998
Modify values
Step 1: Select the Smoothing Constant
1) Select the button labeled Configure

for a Parameter from the
switchboard. The Parameter Name
Selection screen is displayed.
2) Find your desired Parameter.
3) Select this parameter.
4) Select the OK button. The Display
Applications for Smoothed
Parameter screen is displayed.

August 1998
Modify values
Step 2: Select the Application
1) Find your desired application.

2) Select this application.
3) Select the button labeled Modify.
The Modify Smoothing Parameter

August 1998
Modify values
Step 3: Change Smoothing Values
1) Enter the appropriate values in

the middle column
OR
2) Select the Reset to Defaults
button to acquire the GE/CFMI
original defaults.

August 1998
Maintain Smoothing Usage Guidelines
o The method described above works best, if one wants to change the
attributes of a particular smoothed constant for many applications.
o If you want to modify smoothing constants for a particular application,

the Configure for an Application option would be the best choice.
o Deletion of a smoothed parameter can cause the deletion of past

smoothed output, initialization and compressed records too.

August 1998
Maintain Alerting
Maintain Alerting GE/CFMI Proprietary Information Page 1

August 1998
What is Maintain Alerting?

o Maintain Alerting is used to
control the alerts that the SAGE
system will generate.
o Using Maintain Alerting you can:

– Create, modify and delete alerts.
– Assign alerts to particular
aircraft/engine combination.
– Modify the numerical limits that
cause alerts.
– Temporarily disable the
generation of alerts.
– Maintain alert categories,
urgencies and statuses

August 1998
When do I use Maintain Alerting?

o When you need to modify values to control the generation of alerts.
o When you want to create and permanently delete alerts.
o When you want to add (delete) another alert to a particular
aircraft/engine combination.
o When you want to temporarily disable the generation of an alert.
o When you want to assign an alert a different urgency, category,
status or corresponding report.
o When you want to modify the choice of possible urgencies,
categories and statuses permitted for your alerts.

August 1998
SAGE Alert Types
o Individual Alerts - Alerts generated when a particular test condition

is found with the raw and/or smoothed flight data.
o Combination Alerts - Alerts generated when 2 or more other alerts
occur on the same flight.
o NSI Alerts - Alerts generated by the occurrence of bad flight data,
calculation problems, etc.
o All alerts are user configurable.

August 1998
Maintain Alerting “Toolboxes”

o Alerts “Tools”
– Maintain Alerts By Application
• Control Alerts for a particular Application
– Maintain Alerts By Alert Code
• Control All Alerts for All Applications
– Maintain Alert Category
• Control the possible Alert Categories
– Maintain Urgency
• Control the possible Alert Urgencies
– Maintain Status
• Control the possible Alert Statuses

August 1998
Modifying an Alert Limit for an Application
o There are three (3) steps to modifying an alert limit:

1) Select the particular alert that you want to modify.
2) Select the application that you desire.
3) Modify the Alert Limit value.

August 1998
Modify Limit, Step 1: Select the Alert
1) Select the button labeled Maintain

Alert by Alert Code from the
switchboard. The Existing Alerts
2) Find your desired Individual alert.
3) Select this alert.
4) Select the Configure Alert button.
The Display Configured Individual
Alert screen is displayed.

August 1998
Modify Limit, Step 2: Select the Application
1) Find your desired application.

2) Select this application.
3) Select the button labeled Modify
Alert Limits. The Modify
Configured Individual Alert screen
is displayed.
4) NOTE: On this screen is where
one could Disable an alert for a
particular application.

August 1998
Modify Limit, Step 3: Change Limits
1) Enter the new value for Upper

Limit Value or Lower Limit Value
OR
2) Select a parameter by selecting
the Select Upper Parameter
and/or Select Lower Parameter
button.

August 1998
Maintain Alerting Usage Guidelines
o The method described above works best if one wants to change

the limits of a particular alert for many applications.
o If you want to modify alert limits for a particular application, the

Maintain Alerts by Application option would be the best choice.
o Deletion of an alert can cause the deletion of alert generated

information too.
o Hiding an alert results in the alert being created but not displayed
by Analyze Alerts. Appropriate if the alert is a constituent of a
combination alert.

August 1998
Maintain System Data
Maintain System Data GE/CFMI Proprietary Information Page 1

August 1998
What is Maintain System Data?
o Maintain System Data is used to

help airlines:
– Maintain their System Configuration
Constants.
– Maintain their SAGE Applications
o Using Maintain System Data you can:

– Set the System Configuration Constants
to their desired values
– View, Create, Delete SAGE Applications
o Note: This applies to all SAGE

programs and all users tied to the
current database.

August 1998
When do I use Maintain System Data?

o When you want to view the current System Configuration values.
o When you want to modify the current System Configuration values.
o When you want to reset the System Configuration values to the
default GE/CFMI settings.
o When you want to view the existing GE/CFMI and User created
SAGE Applications.
o When you want to add another SAGE Application.
– Note: SAGE Applications may also be added when installing an engine
on an aircraft in the Fleet Management tool.
o When you want to delete a SAGE Application.

August 1998
Maintain System Data “Toolboxes”
o System Data “Tools”

– System Constants
• Modify
• Reset to GE/CFMI settings
– Applications
• Add more Applications
• Delete application

August 1998
Modify System Configuration Constants
o To accomplish:
1) Select the System Constants
switchboard button.
2) The Modify System Constants
screen appears.
o At this point, one can:

Modify or Reset these values.

August 1998
View Existing SAGE Applications
o To accomplish:
1) Select the Applications
switchboard button.
2) The Display Applications
screen appears.
o At this point one can:

View, Add, or Delete
SAGE Applications.

August 1998
Create new SAGE Application
o To accomplish:
1) Select an application on the
Display Applications screen.
2) Select the Copy button on the
Display Applications screen.
o At this point, the Copy New

Application screen appears.

August 1998
Maintain System Data Usage Guidelines
o Be aware that these modifications affect all

SAGE programs for all SAGE users.

August 1998
SAGE Database Maintenance
DB Maintenance GE/CFMI Proprietary Information Page 1

August 1998
Maintaining Database Performance

( An “index” is a “pointer” created by a database during
normal operation to speed access to frequently
needed data.
( During normal, day-to-day operation, indices are
created each time SAGE is run.
( As the number of indices grows, database
performance slowly degrades...
( …unfortunately, most databases do not “clean-up”
the old, unneeded indices.
( Maintaining database performance requires periodic
removal of the “old” indices.
August 1998
Tools for Database Maintenance

( Most database programs include utilities for
periodic maintenance.
( Larger database packages, such as Oracle, are
maintained by dedicated administrators.
( Desktop databases, like Microsoft Access, require
the user to perform the maintenance using their
built-in utilities.

August 1998
Compacting an Access Database

( The Microsoft utility that cleans up an existing
database by removing excess indices is called
“Compact Database…”
( There are three (3) steps in compacting a database
in Microsoft Access:
Œ Open Microsoft Access and select “Tools -> Database
Utilities -> Compact Database…”
• Choose which database to compact
Ž Enter a name for the compacted database

August 1998
How to Compact an Access Database

Œ Open MS Access, then select:
Open MS Access, then select:
Tools -> Database Utilities -> Compact Database...
Tools -> Database Utilities -> Compact Database...
•
Select
Selectthe
theSAGE
SAGEdatabase
databasetoto
compact,
compact, then clickon
then click onCompact.
Compact.
Ž Enter
Enteraaname
database,
namefor
forthe
thecompacted
compacted
database,then
thenclick
clickSave.
Save.

August 1998
After Compacting...
( Compaction can take from 5 to 20 minutes. When
finished, the status message will read “Ready”.
( When complete, delete the old database, and rename

the new, compacted database using the old name.

August 1998
Backing-up the SAGE Database

( There is no “built-in” tool to backup the SAGE database.
( To create a backup of your current SAGE database
perform these steps (MS Access example):
] Compact the database within MS Access.
] Use Windows Explorer to created a duplicate of the database
using the “copy” command. This becomes the “backup” database.
] Use a data compression tool like WinZip to compress the
backup file to minimum size (optional).
] Copy the backup file to a different disk
(another, networked disk, or removable media).

August 1998
SAGE Security
SAGE Security GE/CFMI Proprietary Information Page 1

August 1998
What is SAGE Security?

o SAGE Security is used to help airlines
in implementing procedures in order to
properly protect and manage their
ECM data.
o Using Security you can:
– Identify valid users of SAGE
– Identify each SAGE program that each
user can execute.
– Identify SAGE programs that cannot
run when another program is executing
o The above criteria will be enforced are

run-time

August 1998
When do I use SAGE Security?

o When you want to add, delete or modify Security Levels.
o When you want to add, delete or modify SAGE users.
o When you want to change the Security Level of a SAGE user.
o When you want to change the Security Level of a SAGE program.
o When you want to change the execution dependencies between
SAGE programs.
o When you want to determine which SAGE programs are currently
executing.

August 1998
SAGE Security “Toolboxes”

o Security “Tools”
– Security Configuration
Security Configuration Process Flow
• Security Roles
• SAGE Users Security Roles SAGE Users
Security by
Program
Program
Dependencies
Running
Programs
• Security by Program
Maintain Maintain Maintain Maintain Current
• Program Dependencies Security
Roles
Sage
Users
Program
Security Level
Program
Dependencies
Execution
Status
• Running Programs
Add Add Add Add Refresh
Modify Modify Modify Modify Delete
Delete Delete Delete Delete Delete

All

August 1998
View Existing Security Levels
o To accomplish:
1) Select the Security
Roles switchboard
button.
2) The Maintain Security
Roles screen appears.
o At this point one can Add,
Modify or Delete roles.

August 1998
View Existing SAGE Users
o To accomplish:
1) Select the SAGE Users
switchboard button.
2) The Maintain SAGE
Users screen appears.
Modify or Delete users.

August 1998
View Security Levels for SAGE
Programs
o To accomplish:
1) Select the Security by
Program switchboard button.
2) The Maintain Program
Security Levels screen
appears.
o At this point one can Add, Modify
or Delete SAGE Programs.

August 1998
View Dependencies between SAGE
Programs
o To accomplish:
1) Select the Program
Dependencies
switchboard button.
2) The Maintain Program
Dependencies screen
appears.
Modify or Delete SAGE
Dependencies.

August 1998
View Running SAGE Programs
o To accomplish:
1) Select the Running Programs
switchboard button.
2) The Current Execution Status
screen appears.
o At this point one can Refresh the
list, Delete logged entries or Delete
all entries.

August 1998
Security Levels of SAGE Programs

Pre-configured security level
for each SAGE program
at installation
User-Configurable
Reader User Expert Admin

Enter Data Analyze Alerts Fleet Management Configure Database
Fleet History AutoSAGE History File Converter Maintain System Data
Interactive Reports OnWing Processing Maintain Alerting Parameter Library
Maintain Smoothing SAGE System Security
OnWing Re-Processing
SAGE Security GE/CFMI Proprietary Information
August 1998
SAGE Security Usage Guidelines
o The run-time enforcement can be disabled by turning the two

System Configuration Constants OFF, (ENABLESECURITY and
VALIDATEDEPENDENCIES ).
o SAGE Security does NOT replace your database’s security.
o SAGE Users must match the database username.
o Logon to SAGE Programs with valid SAGE Users even if

ENABLESECURITY is turned off.

August 1998
SAGE UnInstall
Appendix F
Uninstall GE/CFMI Proprietary Information
Page 1
August 1998
Purpose of UnInstall
To remove the SAGE components from the

user’s computer system.
Appendix F
Page 2
August 1998
SAGE Components
The SAGE folder (directory)

structure.
Do not modify/delete any of these
files.
Appendix F
Page 3
August 1998
SAGE Components
The SAGE database folder, database file, and the
SAGE ODBC32 Data Source Name (DSN).
Database
File
Database
Folder
SAGE ODBC
Data Source Names (DSN’s)
Appendix F
Page 4
August 1998
SAGE Components
SAGE program group in

the Windows95
Start Menu
Appendix F
Page 5
August 1998
SAGE Components
AutoSAGE in the Windows Start Up group
AutoSAGE
Appendix F
Page 6
August 1998
SAGE Components
The “sage.ini” file in “C:\windows”.
The contents of the sage.ini file
Appendix F
Page 7
August 1998
UnInstalling SAGE
¶ Terminate all SAGE activity on your computer.
These are SAGE
applications
UnInstall cannot remove SAGE if any of the SAGE applications are running
Appendix F
Page 8
August 1998
UnInstalling SAGE
Ë Start the SAGE UnInstall program.
Appendix F
Page 9
August 1998
UnInstalling SAGE
¸ Don’t forget about AutoSAGE...
…. then pick “YES”.
Appendix F
Page 10
August 1998
UnInstalling SAGE
Í Select “YES” again.
Appendix F
Page 11
August 1998
UnInstalling SAGE
º UnInstall SAGE
A full screen appears showing you the
status of the uninstall process as it
proceeds. It indicates what was
removed. It also tells that some of the
components were NOT removed.
Now Select “OK”
Appendix F
Page 12
August 1998
UnInstalling SAGE
» You may now want to reboot, select “OK”.
All of the SAGE files have been deleted.
Appendix F
Page 13
August 1998
UnInstalling SAGE
¼ UnInstall Process is finished, select
“FINISH”.
The UnInstall Process is completed!

Appendix F
Page 14
August 1998
Removed Components
( The entire SAGE directory (folder) structure
on the hard drive
( SAGE Program group in the Windows95 Start
Menu
( “AutoSAGE” in the Windows Start Up
program group
( “sage.ini” file in C:\windows
Appendix F
Page 15
August 1998
Remaining Components
( The SAGE Database folder and constituent file
( The ODBC drivers that may have been installed
Leave these drivers on your system.
( The ODBC32 “SAGE” data source names
(DSN’s) in the ODBC32 list in the Control Panel.
They do not have to be removed.
Appendix F
Page 16
August 1998
Support of SAGE
Support of SAGE GE/CFMI Proprietary Information

Page 1
August 1998
Contents
( Distribution and Licensing
( Training
( SAGE Support
] Support Channels
GE and CFMI
] Levels of Support
u Normal Support
u Special Support

Page 2
August 1998
SAGE Distribution and Licensing
( Distribution of SAGE 3.0 software & manuals

] Provided as a replacement for current ADEPT & GEM installations
] General distribution started during July, 1998
] Provided at the time of the user’s SAGE training
( SAGE 3.0 software is distributed with a usage license.

] This basic software license permits usage to monitor / support
GE and/or CFMI products operated by the user’s company.
] Questions concerning any additional monitoring needs to be
handled by each airline’s Customer Support Manager.

Page 3
August 1998
SAGE Training
( Training is available at:
] GEAE training location in Cincinnati, Ohio
] Snecma Training School in Melun Montereau, France
( Training sessions
] generally two 3-day classes per month per site
] focus on transition to SAGE software
( Recommend that users be ready to start transitioning

to SAGE after training
] have required hardware and software installed before training
] register for training by contacting Customer Support Manager

Page 4
August 1998
SAGE Support
( Support available from GEAE and CFMI

] Schedule & Business Issues
] SAGE Technical Assistance
( Levels of SAGE support

] Normal
] Special

Page 5
August 1998
SAGE Support Channels
GEAE Snecma
– Schedule & Business Issues – Schedule & Business Issues
(Availability, Training, Licenses, etc.) (Availability, Training, Licenses, etc.)
Contact CSM Contact CSM
– Technical Questions – Technical Questions

(Installation, Operation, Problems, (Installation, Operation, Problems)
Network Advice)
E-Mail: SAGE.SUPPORT@ae.ge.com E-Mail: SAGE.SUPPORT@teck.snecma.fr
Phone: 1-513-552-3171 (ECM Support Line) Phone: 33-1-6414-8472 (SAGE Support Line)
Fax: 1-513-552-3153 Fax: 33-1-6414-8765

Page 6
August 1998
Normal SAGE Support

Normal support available - provided with software
] Standard information on hardware/software requirements and
installation options
] Standard training materials and training for 2 users per customer
at GEAE or CFMI training sites
] Standard information related to input requirements and/or
general interpretation of output
] Responses to reported problems in a timely manner
] Communications related to Frequently Asked Questions, known
problems, and shared user information
] Necessary software modifications to fix general program problems
] Updates for new engine/model applications within user’s fleet
Page 7
August 1998
Special SAGE Support
Special support - quote upon request

] Support to work through installation issues beyond
standard options
] Support to integrate SAGE into a customized Engine
Condition Monitoring configuration
] Training for additional users and/or customized training
] On-site validation of installation, additional training, ...
Contact
Contactyour
yourCustomer
CustomerSupport
SupportManager
Manager
for
foradditional
additionalinformation
information

Page 8
August 1998
Frequently Used Terms
Frequently Used Terms

October 1998
3 GE Aircraft Engines SAGE Frequently Used Terminology EFG
Term Definition
ADEPT Aircraft Data Engine Performance Trending
Standard engine condition monitoring computer program, used widely to monitor CF6, CFM56, and GE90 engines.
AIF Aircraft Input File – Binary file of input records prepared in accordance with the GEM “Standard Input Record Format”.
Background process A computing process that proceeds out of view, without preventing operation of other interactive computer processes.
Client A “networked” computer that has neither the SAGE database nor background programs installed.
Each “client” computer must connect to a “server” across a network to access the SAGE database.
Database A computer storage file/s for a collection of information, i.e. SAGE data (examples – MS Access, Oracle, DB2).
Delimiter A symbol used to separate values in a data file.
Directory A named location on a computer storage device (hard disk, CD-ROM, floppy disk, etc.) that contains other computer files.
For example: C:\Sage_Database is the directory where the SAGE database file is located.
File This may be a program, an application library, a data file, a database, or any other type of computer file.
GEM Ground-based Engine Monitoring
A special engine condition monitoring program with expanded capability and flexibility (limited number of users).
PC A “personal computer”, which for SAGE use, must be a 100% IBM-compatible and must meet the requirements listed in
the “Preparing for SAGE” section.
Interactive program Any SAGE program that requires user interaction to function. SAGE interactive programs run ONLY on a PC, though they
may access a SAGE database on another PC or a UNIX computer system.
Network A group of interconnected computer platforms, in this context each containing one or more elements of the SAGE system.
ODBC Open DataBase Connectivity
A set of standards describing methods by which computer programs communicate with a database.
ODBC “drivers” Library files which interpret SQL messages, errors, and commands between the calling program and the database.
OnWing Processing A set of SAGE background programs. Data acquired in-flight (on-wing) are processed in sequence through the programs,
including loading data, and performing analytical calculations, smoothing, alerting, compression, & automatic reporting.
The “OnWing Processing” program may reside on computer platforms with UNIX, Win95 or Win NT operating systems.
SAGE System for the Analysis of Gas turbine Engines – A new engine condition monitoring system for GE / CFMI engines.
Screen An individual “window” of an interactive computer program, or in some contexts, the entire display.
Server A “networked” computer on which the SAGE database and/or background processing programs are installed and
executed. The “server” is accessed across the network by “client” computers. A “server” will often contain the database
and all programs (interactive and background).
SQL Structured Query Language
A high-level language used to communicate with SQL “compliant” database programs (an industry accepted interface).
Stand-alone A SAGE installation on a single PC, containing the entire SAGE system and database.
UNIX A multi-user, multi-tasking computer operating system (used in reference to “workstation” computer platforms).

(((
SAGE Frequently Used Terminology 1 Appendix D
Aircraft / Engine Types
Aircraft / Engine Types

October 1998
3 GE Aircraft Engines SAGE 3 -- Aircraft/Engine Combinations (as of January 31, 1999) EFG
Aircraft Type Engine Type Hardware Config Control Aircraft Type Engine Type Hardware Config Control
DC10-10/-30 CF6-6D
DC10-10/-30 CF6-6D1A B747-200 CF6-80C2B1
DC10-10/-30 CF6-6K B747-300 CF6-80C2B1
B747-400 CF6-80C2B1F
DC10-10/-30 CF6-50A B767-200 CF6-80C2B2
A300B CF6-50C PRE_P100 B767-300 CF6-80C2B2
A300B CF6-50C P100_CONTROL B767-300ER CF6-80C2B2
DC10-10/-30 CF6-50C PRE_P100 B767-200 CF6-80C2B2F
DC10-10/-30 CF6-50C P100_CONTROL B767-300 CF6-80C2B2F
A300B CF6-50C2 PRE_P100 B767-300ER CF6-80C2B2F
A300B CF6-50C2 P100_CONTROL B767-200 CF6-80C2B4
DC10-10/-30 CF6-50C2 PRE_P100 B767-300ER CF6-80C2B4
DC10-10/-30 CF6-50C2 P100_CONTROL B767-200 CF6-80C2B4F
DC10-10/-30 CF6-50C2F PRE_P100 B767-300ER CF6-80C2B4F
DC10-10/-30 CF6-50C2F P100_CONTROL B747-400 CF6-80C2B5F
B747-200 CF6-50E B767-300ER CF6-80C2B6
B747-300 CF6-50E B767-300ER CF6-80C2B6F
B747-200 CF6-50E2 B767-300ER CF6-80C2B7F
B747-300 CF6-50E2
MD11 CF6-80C2D1F
B767-200 CF6-80A
B767-200 CF6-80A2 A330-300 CF6-80E1A2
A310-200 CF6-80A3 A330-200 CF6-80E1A4
A300-600 CF6-80C2A1 DC-8 CFM56-2-C1 870 DEGC EGT

A310-200 CF6-80C2A2 DC-8 CFM56-2-C1 905 DEGC EGT
A310-300 CF6-80C2A2
A300-600 CF6-80C2A3 B737-300 CFM56-3-B1
A300-600 CF6-80C2A5 B737-400 CFM56-3-B1
A300-600ER CF6-80C2A5F B737-500 CFM56-3-B1
A300-600ST CF6-80C2A8 B737-300 CFM56-3B-2
A310-200 CF6-80C2A8 B737-400 CFM56-3B-2
A310-300 CF6-80C2A8 B737-300 CFM56-3C-1

(((
SAGE Available Aircraft/Engine Types 1 Appendix
Aircraft Type Engine Type Hardware Config Control Aircraft Type Engine Type Hardware Config Control
B737-400 CFM56-3C-1
B737-500 CFM56-3C-1 A340-200 CFM56-5C4
A340-300 CFM56-5C4
A320-100 CFM56-5-A1
A320-200 CFM56-5-A1 B737-600 CFM56-7B18
A320-100 CFM56-5-A1/F B737-600 CFM56-7B20
A320-200 CFM56-5-A1/F B737-600 CFM56-7B20 DAC
A320-100 CFM56-5A3 B737-600 CFM56-7B22
A320-200 CFM56-5A3 B737-600 CFM56-7B22 DAC
A319 CFM56-5A4 B737-700 CFM56-7B20
A319 CFM56-5A4/F B737-700 CFM56-7B22
A319 CFM56-5A5 B737-700 CFM56-7B24
A319 CFM56-5A5/F B737-800 CFM56-7B24
B737-800 CFM56-7B26
A321-100 CFM56-5B1 B737-800 CFM56-7B27
A321-100 CFM56-5B2 B737-800 CFM56-7B27/B1
A321-100 CFM56-5B3 BBJ (-700) CFM56-7B26 (B1) BIZ-JET
A320-100 CFM56-5B4 BBJ (-700) CFM56-7B27 (B3) BIZ-JET
A320-200 CFM56-5B4
A319 CFM56-5B5 B777-200 GE90-76B BLOCK 2
A319 CFM56-5B6 B777-200 GE90-76B BLOCK 3
B777-200 GE90-76B BLOCK 3 PRP
A340-200 CFM56-5C2 B777-200 GE90-76B BLOCK 4
A340-300 CFM56-5C2 B777-200IGW GE90-85B BLOCK 3
A340-200 CFM56-5C2/F B777-200IGW GE90-85B BLOCK 3 PRP
A340-300 CFM56-5C2/F B777-200IGW GE90-85B BLOCK 4
A340-200 CFM56-5C2/G B777-200IGW GE90-90B BLOCK 3
A340-300 CFM56-5C2/G B777-200IGW GE90-90B BLOCK 3 PRP
A340-200 CFM56-5C3/F B777-200IGW GE90-90B BLOCK 4
A340-300 CFM56-5C3/F
A340-200 CFM56-5C3/G CRJ CF34-3A1
A340-300 CFM56-5C3/G
A340-200 /-300 CFM56-5C2/4 to
(10 applications) CFM56-5C3/G4

(((
Other “Aircraft / Engine Combinations” can be added before these
additional applications enter revenue service.

(((
Input Data Formats
Input Data Format

October 1998
3 GE Aircraft Engines SAGE Input File Formats EFG
SAGE Input Formats Generic SAGE Input Format Specifications
The process of acquiring and formatting the input data is General Requirements
up to the individual airlines to implement. SAGE will The file is a self-describing file. This means that the
currently accept input files in ADEPT mode 1 or 2 record structure is first described before the actual data
formats. The file extension of each input files is used by values are supplied. This may be thought of as a
the SAGE system to determine how to read the file. “Format” section (for the record definition), followed by a
Therefore, the following file extensions are required for “Values” section which contains the actual data values.
the input formats:
• The first line of the file must state the delimiter to be
Description File used in the subsequent records.
Extension • The format section will contain a list of every input
ADEPT Mode 1 (ADEPT 7 or 8) .DT1 parameter and its datatype (real, integer or
ADEPT Mode 2 (ADEPT 10) .DT2 character).
SAGE generic format .SGE • Each values section contains the data for a record
from an aircraft and its engines, with each value
File extensions can be upper or lower case. For separated by the delimiter defined in the format
specifications of the ADEPT formats, please see the section.
appropriate ADEPT user’s manual. Maintenance records • Multiple value sections may follow the format section,
in ADEPT mode 1 and mode 2 files will be ignored. but each value section must map exactly to the format
section.
• A value cannot be split between lines.
• If the delimiter is in a value string, it must be enclosed
with double quotes (“ “). If blanks, commas, or other
special characters are in a value string, it is advisable
to use double quotes. Dates do not need to be
enclosed in double quotes.
• Dates must be given in this format: dd-MMM-yyyy
hh:mm:ss

(((
SAGE Input File Formats 1 Appendix A
General Requirements (continued) Format Section
• MMM in the format is the English 3-character This section starts on a new line and starting in column 1,
abbreviation for months. contains the following:
• Dates cannot be influenced by the date mask in the
general preferences file or by regional settings. • Section keyword “*FORMAT”
• A list of the parameters to be found in the
General File Format Requirements: values section, and their type
• The file is to be ASCII text format. The format lines should look like :
• Lines may be any length with no imbedded
control characters such as carriage return or PAR1cTYPE1cPAR2cTYPE2c...PARncTYPEn
line feed characters.
• Each line in the file is to be terminated with a where
2-byte CRLF (carriage return line feed).
• The required file extension is “.sge”. c = delimiter character (field
separator) for the file as defined by
the Delimiter keyword.
Delimiter Section PARx = parameter name for xth
parameter
The first line in the file is the delimiter line. The format is: TYPEx = datatype of xth parameter.
DELIMITER=c
where c is the delimiter character to be used throughout Accepted datatypes will be:
as the field separator.
I = integer
R = real or float
A = alphanumeric or character string.

(((
Format Section Values Section
No parameter name or value can be divided between This section contains the data values for a single record
lines. Parameters that are not stored or used by the from an aircraft or test cell. The following rules apply to
system can be included in the file and will be ignored. the construction of the values section:
No parameters should be included that will not have
values in the values section. The user may provide a • The section starts on a new line and in column
“missing value” by consecutive delimiters, ex “,,” means 1, keyword “*VALUES”.
there is no value (assuming comma is the delimiter). • The values must be in the same order and of
the same type as that declared in the format
All engine parameters must have a suffix designating the section.
engine position (i.e. XYZ-2). The order of the engine • No parameter value can be divided between
parameters is not important. lines.
• Parameters that are not stored or used by the
The user parameter names are assumed to be SAGE system can be included in the file, but that
alias parameter names. If the name is not found in the name cannot be included in the SAGE alias or
alias list, the SAGE parameter list is then searched. If parameter list.
the parameter name is not found, it is simply ignored. • No values can be included that are not also
included in the format section. In other words,
every value should have its parameter defined
in the format section. Values cannot contain
the delimiter unless it is a string value enclosed
in double quotes.

(((
SAGE Generic Files
Values Section (continued)
Once the data is properly formatted, all that is required is The generic format will currently support six types of
for the file(s) to be moved into the input data:
\sage\queues\automatic or the directory specified in the
polling directory in the SAGE preferences. The user may 1) Flight_Data
then execute on-wing data processing by executing the 2) Normal_Line_Maintenance
owp.exe program (or select from the Windows taskbar 3) Engine Times/Cycles
menus for SAGE). Alternately, and generally preferable, 4) Engine Removal
the user will have configured the "AutoSAGE" system to 5) Engine Installation
periodically process data. 6) Engine Change
AutoSAGE can be set to run at specific times on specific The following sections describe the required format for
days, or every X hours, at the users option. When each record type.
processing kicks off, all recognized files in the
\queues\automatic directory will be processed. Flight Data Section
If the format section contains parameters

FPHASE, AIRID and FDATE then the Input
Processor assumes it is of this type.

(((
Normal Line Maintenance Section Engine Times/Cycles Section
If the format section contains parameters If the format section contains parameters
FPHASE, engine_id, maint_datetime, ata_code FPHASE, engine_id, and hrs_cyc_datetime then
OR alias_code, ata_classification and family the IP assumes it is of this type. FPHASE must be
then the IP assumes it is of this type. FPHASE “HOURS AND CYCLES”. Optional parameters
must be “LRU MAINTENANCE” (from the PHASE are:
database table).
hrs_since_install
These parameters may be required: cyc_since_install
ata_code hrs_since_new
(must be supplied if alias_code is missing/null) cyc_since_new
alias_code hrs_since_overhaul
(must be suppled if ata_code is missing/null) cyc_since_overhaul
estimated_flag
Note: If ata_code is supplied, alias_code is
ignored. If ata_code is missing, it is deduced using
the alias_code, ata_classification and family.
Optional parameters are:
reason (should be given if available)

(((
Common Engine Change, Installation, Removal
Section
For Engine Installations, FPHASE must be
The following parameters are common for all 3 “ENGINE CHANGE” (from the PHASE table),
types. Parameters needed for each type are Install_datetime must be non-NULL,
summarized below. Removal_datetime must be NULL.
FPHASE, These parameters are required and must be non-

aircraft_id, NULL:
engine_position,
aircraft_id
install_datetime, engine_position
engine_id, install_datetime
thrust_rating, engine_id
hrs_at_install,
cyc_at_install, These parameters may be required if needed for
number_removals, valid data processing:
number_shop_visits
thrust_rating (based on aircraft type/engine
removal_datetime, type)
hrs_at_removal,
cyc_at_removal, These parameters are optional:
reason_for_removal,
engine_status, hrs_at_installation
cyc_at_installation
control, number_removals
config, number_shop_visits
selector control (control, config, and selector must be
given if available)
config
selector

(((
Common Engine Change, Installation, Removal
Section (continued)
For Engine Removals, FPHASE must be For Engine Change, FPHASE must be “ENGINE
“ENGINE CHANGE” (from the PHASE table), CHANGE” (from the PHASE table) and both
Install_datetime must be NULL, Install_datetime and Removal_datetime must be
Removal_datetime must be non-NULL. non-NULL.
These parameters are required and must be non- These parameters are required and must be non-
NULL: NULL:
aircraft_id aircraft_id
engine_position engine_position
removal_datetime removal_datetime
engine_status install_datetime
engine_id
These parameters are optional: engine_status
hrs_at_removal All other keys are optional. Refer to the

cyc_at_removal descriptions of engine installation and removal for
reason_for_removal details.

(((
Sample Content of SAGE Generic Files
SAGE generic file format for Flight Data Entry: SAGE generic file format for Line Maintenance
Action:
----------- BEGIN OF FDE.SGE-----------
----------- BEGIN OF MAINTENANCE.SGE -----------
DELIMITER = #
DELIMITER = #
*FORMAT
AIRID#A#FPHASE#A#FDATE#A# *FORMAT
IBE1#I#IBE2#I#IBE3#I#IBE4#I#IVS12#I#AGW#R#CAS#R# FPHASE#A#ENGINE_ID#A#MAINT_DATETIME#A#FAMILY#A#
IATSI#I#SAT#R#TLA#R#ZALT#R#ZT1A#R# ALIAS_CODE#A#ATA_CLASSIFICATION#A#
CYCLES-1#I#EGTDIV-1#R#TNCDIV-1#R#CYCLES-2#I# ALIAS_DESCRIPTION#A#REASON#A
CYCLES-3#I#CYCLES-4#I
*VALUES
*VALUES LINE MAINTENANCE#455342#07-Apr-1997 11:48:35#A310#
NAV02#CRUISE#07-Jan-1997 11:01:58# 840240#420#
0#1#0#1#0#220000#440# ENGINE-COMPRESSOR#"TEST FOR ANNOTATION FIELD"
30#25#26#90#30000#-10#
12#20#25#300#
342#4005 ----------- END OF MAINTENANCE.SGE -----------
----------- END OF FDE.SGE----------- The FPHASE values MUST be LINE MAINTENANCE.

The names in the *FORMAT lines must MATCH the
The FPHASE values MUST be a valid flight phase – actual column names as defined in the
CRUISE, TAKEOFF or CLIMB. ENGINE_MAINTENANCE table in the SAGE database.
The names in the *FORMAT lines must MATCH either

the user define parameter names stored as the values
for alias in the PARAMETER_LIST table in the database
OR the parameter_name as stored in the
PARAMETER_LIST Table. The user may identify
parameters by either the SAGE names or the alias name.
SAGE will search for a match first on the alias name,
then the SAGE name.

(((
SAGE generic file format for Engine Times and SAGE generic file format for Remove Action on
Cycles: Engine Change:
----------- BEGIN OF HRS_CYCLES.SGE ----------- -------- BEGIN OF ENG_CHANGE.SGE -----------
DELIMITER =# DELIMITER = #
*FORMAT *FORMAT
FPHASE#A#ENGINE_ID#A#HRS_CYC_DATETIME#A# FPHASE#A#AIRCRAFT_ID#A#ENGINE_POSITION#I#
HRS_SINCE_INSTALL#I#CYC_SINCE_INSTALL#I# REMOVAL_DATETIME#A#HRS_AT_REMOVAL#I#
HRS_SINCE_NEW#I#CYC_SINCE_NEW#I# CYC_AT_REMOVAL#I#ENGINE_STATUS#A#
HRS_SINCE_OVERHAUL#I#CYC_SINCE_OVERHAUL#I# REASON_FOR_REMOVAL#A
ESTIMATED_FLAG#A
*VALUES
*VALUES ENGINE CHANGE#GEKPK#1#
HOURS AND CYCLES#455237#07-Apr-1997 11:59:46# 07-Apr-1997 13:51:31#22#
22#23# 22#SPARE#
24#25# "REMOVED FOR TESTING "
26#27#
NO
-------- END OF ENG_CHANGE.SGE -----------
----------- END OF HRS_CYCLES.SGE ----------- The FPHASE values MUST be ENGINE CHANGE.
The FPHASE values MUST be HOURS AND CYCLES. The names in the *FORMAT lines must MATCH the
actual column names as defined in the
The names in the *FORMAT lines must MATCH the ONWING_ENGINE table and/or APP_HISTORY tables
actual column names as defined in the in the SAGE database.
ENGINE_TIMES_CYCLES table in the SAGE database.

(((
SAGE generic file format for Install Action on Engine SAGE generic file format for Remove-Install Action
Change: on Engine Change:
-------- BEGIN OF ENG_CHANGE.SGE -------- -------- BEGIN OF FILE ENG_CHANGE.SGE -----------
DELIMITER = # DELIMITER = #
*FORMAT
FPHASE#A#AIRCRAFT_ID#A#ENGINE_POSITION#I# *FORMAT
INSTALL_DATETIME#A#ENGINE_ID#A#THRUST_RATING#R# FPHASE#A#AIRCRAFT_ID#A,ENGINE_POSITION#I#
HRS_AT_INSTALL#I#CYC_AT_INSTALL#I# ENGINE_ID#A#INSTALL_DATETIME#A#HRS_AT_INSTALL#I#
NUMBER_REMOVALS#I#NUMBER_SHOP_VISITS#I CYC_AT_INSTALLATION#I#REMOVAL_DATETIME#A#
HRS_AT_REMOVAL#I#CYC_AT_REMOVAL#I#ENGINE_STATUS#A#
*VALUES REASON_FOR_REMOVAL#A
ENGINE CHANGE#W4679#1#
23-FEB-1998 12:57:47#858115#22# *VALUES
500#125# ENGINE CHANGE#J1456#1#
6#2 695121#07-Apr-1997 16:34:44#23#
23#07-Apr-1997 16:34:27#
11#11#SPARE#
"REMOVED FOR TESTING"
-------- END OF ENG_CHANGE.SGE -----------
-------- END OF FILE ENG_CHANGE SGE -----------
The FPHASE values MUST be ENGINE CHANGE.
The FPHASE values MUST be ENGINE CHANGE.
The names in the *FORMAT lines must MATCH the

actual column names as defined in the
ONWING_ENGINE table and/or APP_HISTORY tables
in the SAGE database.

(((
SAGE Generic Files Examples
Following are examples of single reading and multi-

reading .SGE files (NOTE: Not all available input
parameters are shown.):
Example of a single reading .SGE file... Example of a multi-reading .SGE file...

DELIMITER = #
*FORMAT DELIMITER = #
AIRID#A#FPHASE#A#FDATE#A# *FORMAT
IBE1#I#IBE2#I#IVS12#I#IBP1#I#IBP2#I#ZALT#R#ZT1A#R# AIRID#A#FPHASE#A#FDATE#A#
ZXM#R#ZPCN12-1#R#ZPCN25-1#R#ZPOIL-1#R#ZT49-1#R# IBE1#I#IBE2#I#IVS12#I#IBP1#I#IBP2#I#ZALT#R#ZT1A#R#
ZWF36-1#R#ZPCN12-2#R#ZPCN25-2#R#ZPOIL-2#R# ZXM#R#ZPCN12-1#R#ZPCN25-1#R#ZPOIL-1#R#ZT49-1#R#
ZT49-2#R#ZWF36-2#R ZWF36-1#R#ZPCN12-2#R#ZPCN25-2#R#ZPOIL-2#R#ZT49-2#R#
ZWF36-2#R
*VALUES
OLB19#CRUISE#12-Sep-1997 08:43:20# *VALUES
1#1#1#1#1#35000#-10# OLB19#CRUISE#12-Sep-1997 08:43:20#
0.78#90#88#50#650# 1#1#1#1#1#35000#-10#
1400#90#88#50# 0.78#90#88#50#650#
650#1400 1400#90#88#50#650#
1400
*VALUES
OLB19#CRUISE#12-Sep-1997 09:43:20#
1#1#1#1#1#35000#-10#
0.78#90#88#50#650#
1400#90#88#50#650#
1400
*VALUES
OLB19#CRUISE#12-Sep-1997 10:43:20#
1#1#1#1#1#35000#-10#
0.78#90#88#50#650#
1400#90#88#50#650#
1400

(((
SAGE
“Types & Families”
Families GE/CFMI Proprietary Information Page 1

August 1998
“Type” Defined
A specific model of an engine or aircraft is called a type.
Engine types generally represent specific thrust ratings:
] For example, the CF6-80C2B1F, CF6-80C2B4F and
CF6-80C2B6F are three unique engine types.
] NOTE: The CFM56-3-B1, CFM56-3B-2 and CFM56-3C-1
are exceptions to this rule, because of the unique method
used to adjust thrust rating on “classic” 737 aircraft.
Aircraft types represent specific models of the same

basic airframe:
] For example, the A330-200 and A330-300 are two unique
aircraft types.
The
Theuser’s
user’sselection
selectionof
ofaircraft
aircrafttype
typeand
andengine
enginetype
typeprimarily
primarilydetermine
determine
the
theanalytical
analyticalcalculations
calculationsand
andsupporting
supportingdata
data(“PIP”)
(“PIP”)files
filesused
used
for
foreach
eachengine
engineposition
positionbeing
beingmonitored.
monitored.
August 1998
Engine “Family” Defined

Engine families contain engine types that share common
hardware or turbomachinery design:
] For example, the CFM56-5A engine family includes the
CFM56-5-A1, CFM56-5-A1/F, CFM56-5A3, CFM56-5A4,
CFM56-5A4/F, CFM56-5A5 and CFM56-5A5/F engine types.
All
Alltypes
typeswithin
withinaafamily
familyshare
sharecommon
commondesign
designattributes
attributesand
and
measurement
measurementsystems.
systems.

August 1998
Aircraft “Family” Defined

Aircraft families are groups of aircraft types that share the
same basic airframe and system attributes:
For example, the A320 aircraft family

currently includes the A319, A320-100,
A320-200 and A321 aircraft types.
All
Alltypes
typeswithin
withinaafamily
familyshare
sharecommon
commondesign
designattributes
attributesand
and
measurement
measurementsystems.
systems.

August 1998
Why both Types and Families?

The concept of families is used to save computer
processing resources.
How? By eliminating redundant definitions of input and
output parameters. For example:
] There are currently 14 engine families, comprising a total
of 78 engine types.
] For each family there are approximately 50 parameters
needed for basic CRUISE trending functions.
] Using families, the total rows required to define these
parameters in the PARAMETER_LIBRARY table is
50 x 14 = 700. If entries existed instead for each engine type,
3900 total rows would be required (50 x 78).

August 1998
An Example of Parameter Associations

Œ The
Theparameter
parameterZPCN12
ZPCN12
(FAN_SPEED_INDICATED)
(FAN_SPEED_INDICATED)isis
available
availabletotoengine
enginetypes
typesofof
BOTH
BOTHCF6-80C2FADEC
CF6-80C2FADECand and
CF6-80C2 engine families.
CF6-80C2 engine families.
Family
Œ Family
CF6-80C2FADEC
CF6-80C2FADEC CF6-80C2
CF6-80C2
CF6-80C2B1F CF6-80C2B1
CF6-80C2B4F
CF6-80C2B4
CF6-80C2FADEC Types
CF6-80C2 Types
•
CF6-80C2B6F CF6-80C2A2
• The
Theparameter
parameterZPN12P
ZPN12P(FAN_SPEED_ACTUAL)
(FAN_SPEED_ACTUAL)isisavailable
available
CF6-80C2B8F only
CF6-80C2B8F onlytototypes
typesofofthe
theCF6-80C2FADEC
CF6-80C2FADECengine
enginefamily.
family.

August 1998
How are they used?

( When parameters are defined or modified (using the
Parameter Library program), they are associated with
one or more families.
( Once defined, ALL types of the associated families
will use that parameter’s definition, which includes the
parameter name, alias, units, limits, etc.
( In addition, maintenance codes are defined and
associated with aircraft families.

August 1998

CTC-220 Sage

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CTC-220 Sage

Uploaded by

Copyright:

Available Formats

3 GE Aircraft Engines EFG

Copyright  1998 by GE Aircraft Engines and CFM International

Technical Data General License TSU Applicable

All Rights Reserved

GE/CFMI Proprietary Information

1 Overview 18 Interactive Reports

GE/CFMI Proprietary Information

✈ Plan -- Focus primarily on normal usage & getting started

SAGE - System for the Analysis of Gas turbine Engines

Engine Condition Monitoring System :

✽ Interactive, “windows-like” monitoring system

Use routinely to monitor current “health” of engines:

✽ Assess and trend overall engine performance

Sage typical window

✽ Combines elements of old softwares (ADEPT & GEM)

✽ Takes advantage of today’s computing configurations

✽ Runs on a PC ….. either stand-alone or networked

New program -- more user-friendly

✽ Expanded flexibility to address user requests

✽ Use “as delivered” or as “customized” by the user

SAGE Monitoring System

✽ Uses existing analytical routines to assess performance

Enhances monitoring system

✽ Can be configured & customized to suit individual users

SAGE Monitoring Functionality

SAGE is Not … a Single Program

Each SAGE “program”

“User Reviewer” Volunteers: Review meeting for GEM Users:

Review meeting for “Beta” Functionality: SAGE Installation Seminar:

The SAGE System

Each SAGE “program”

Categories of SAGE Programs

Fleet Management Data Analysis

Automatic Maintain Alerting

Stored Record Maint.

Less Frequently Used

✽ Display Installation History for an Engine or an Aircraft

“Data Entry” Programs

✽ ( by using the “Parameter Library”)

Data Source Enter Data

Third Party Database :

“Data Processing” Programs

The user can temporarily

“Data Analysis” Programs

“Data Analysis” Programs

Alert: A message generated by SAGE to

✽ Manage Parameters for “Enter Data”

✽ Maintain Parameter Definitions

Reader Only reads

Hardware and Software Requirements

Installation Considerations GE/CFMI Proprietary Information Page 1

Minimum UNIX Requirements

✽ Processing of more than 100 flight records at a time

✽ Server installations with more than 5 clients

✽ SAGE processing with other PC software executing

✽ All SAGE interactive programs, background processing programs

Background Processing (OnWing Processing)

Installation Considerations GE/CFMI Proprietary Information Page 4

Installation Considerations GE/CFMI Proprietary Information Page 1

Computer Operating Environments

Installation Considerations GE/CFMI Proprietary Information Page 2

SAGE Elements and System Requirements

All interactive programs must reside on PC platforms