Heliwise Manual Rev - N PDF

THSS-189G0205X001 Rev.
Heliwise Service User Manual Page 1 of 386
Classification
UNCLASSIFIED
1 USER MANUAL
The following chapters describe the Heliwise interface and how to interact with it.
© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

This document contains information that is confidential and proprietary to Leonardo S.p.a. and/or Leonardo MW Ltd and/or AgustaWestland Philadelphia Corporation ('the Compa-
nies') and is supplied on the express condition that it may not be disclosed to any third party, or reproduced in whole or in part, or used for manufacture, or used for any purpose other
than for which it is supplied, without the prior written consent of the Companies. Every permitted disclosure, reproduction, adaptation or publication of this document in whole or in part
and in any manner or form shall prominently contain this notice.
THSS-189G0205X001 Rev. N
Classification
UNCLASSIFIED
1.1 CONNECT TO HELIWISE

Open Internet Explorer and connect to https://heliwise.agustawestland.com.
It is necessary to have the Microsoft Silverlight plug-in installed.
Figure 1: Site Address

Classification
UNCLASSIFIED
1.2 USER LOGIN

After inserting the web address the following page appears:
Figure 2: Login
.
To proceed with the login, both User name and Password must be inserted.

Classification
UNCLASSIFIED
Figure 3: Insert User name and Password
If the user name or password is not correct, the following message appears.
Figure 4: Login Error
After six consecutive attempts, Heliwise temporarily locks the user’s account.

Classification
UNCLASSIFIED
Figure 5: Account temporarily locked
To unlock the account click the Reset Password link. The window below opens.
Figure 6: Enter verification code
Insert the words that are displayed and then press the Verify button. If the words were entered correctly the
window below opens.

Classification
UNCLASSIFIED
Figure 7: Insert user name and email address
Insert the requested information and then press the Send Reset Code button. The window below opens.
Figure 8: Insert code

Classification
UNCLASSIFIED
Copy and paste the code that was sent to your email address into the Code area in the window and then
press the Check Code button. A new window opens displaying two options; choose the option you require to
proceed.
Figure 9: Unlock or change password
If you select the Unlock Password button the window displayed below opens, press Continue and it will now
be possible to log on using the unlocked password.
Figure 10: Account unlocked

Classification
UNCLASSIFIED
If you select the Change Password option the window below opens.
Figure 11: Change password
Enter the new password and then press the Change Password button. A window opens informing the user
that the password is being changed.

Classification
UNCLASSIFIED
Figure 12: Password changing
When the password has been changed a confirmation window opens and an email is sent to the user’s
account. Press Continue to log on using the new password.
Figure 13: Password changed successfully
At the end of the process of either unlocking the password or changing the password the window below
opens.
Figure 14: End of procedure message

Classification
UNCLASSIFIED
After logging on correctly the user is connected to the Heliwise application
Figure 15: Connecting to Heliwise
Once the site has loaded correctly the user is directed to the Heliwise Homepage.

Classification
UNCLASSIFIED
1.3 MAIN SCREEN

Once logged in, the Fleet Home page is displayed. All the helicopters in the fleet are displayed by default.
On this page it is possible to select a helicopter on which to carry out further actions.
Figure 16: Main Screen

Classification
UNCLASSIFIED
1.3.1 Main Menu

On the right side of the page, the web application always shows the main menu and each icon represents a
macro area of Heliwise’s capabilities.
N.B. Not all menu icons are available for all users as access to menu items is based on the profile assigned
to the Heliwise user logged-in.
Table 1: Main Menu Items
Menu Icon Description

Click here to return to the Home Page (or Main Screen).
Module dedicated to the analysis of Fleet HUMS data.

Classification
UNCLASSIFIED
Module dedicated to the monitoring of failures and usage data of a

selected helicopter.
Module dedicated to the analysis of Transmission Vibration Monitoring

information, such as Health Index and Accelerometers status.

Classification
UNCLASSIFIED

Module addressed to Rotor Track and Balance features and Structural
Vibration Monitoring pages.
Module containing features for downloading data from the DTD to PC

and for the processing of information in each download folder.
Module dedicated to advanced settings.
Module addressed to resources management such as user

credentials and aircraft data. It also contains the Heliwise settings.
Opens the Help Online.

Classification
UNCLASSIFIED

Clicking on the about window the user can get more information about
the software features introduced with the latest version.
Log-out button. Once clicked, the web site requests confirmation to

log out.
A tooltip provides information regarding the current session

information (user name, server and application time standard).
This area can host messages and notifications for the user.

Classification
UNCLASSIFIED
1.3.2 Content Area

The content area is a central section which hosts the aircraft fleet by default.
Figure 17: Content Area example
When the user navigates to another page, this area changes dynamically showing the requested page.

Classification
UNCLASSIFIED
1.3.3 Banner
A banner section is always visible at the top of the Heliwise application.
Figure 18: Banner Section
The banner also displays the user’s navigation history. By moving the mouse pointer over the clock, Heliwise
shows a transparent area which displays the pages which the user has navigated through in the current ses-
sion.
Figure 19: Navigation History
Another functionality placed in the banner is the ‘Smart-link’ button.
Figure 20: Smart-Link button
This button works differently depending whether you’re navigating the Main Screen or another specific dia-
log.
In the Main Screen, if the logged user is able to see different Customers, Locations or HC Variants, the but-
ton works as a filter and it is shown as below.
Figure 21: Fleet Filter button
By clicking on the ‘Fleet Filter’ button, the filter window opens and the user can select the required aircraft. In
the lower part of the filter there is a preview of the filtered aircraft.
Once the proper view parameters have been set, click to load the relevant data otherwise click to close
the window without applying the filter.

Classification
UNCLASSIFIED
Figure 22: Fleet Filter
On each specific dialog the aim of the Smart-Link button is to change the data set loaded on each page of
Heliwise. For example, while using the Fleet pages the user can use the Smart-Link to select which H/C to
be analysed. When analyzing the data the user can interact with this button to load another aircraft and
avoid going back to the home page. Therefore, the user should click on the button placed in the top right cor-
ner of the page and the following popup opens.
Figure 23: Smart-Link window example
The body of this popup changes according to the page currently loaded in Heliwise. It can host a list of air-
craft which can be selected to be analysed, an interval time period to be loaded for analysing the AC data
and a list of AC models.
Once proper view parameters have been set click to load the relevant data otherwise click to close the
window without applying the filter.

Classification
UNCLASSIFIED
1.4 HELP ONLINE

Clicking on the icon highlighted below, the Help Online opens:
Figure 24: User Manual icon
The help redirects itself automatically and shows the information about the page currently open by the
logged in user.
Figure 25: Help Online
The manual is navigable by means of the tool-bar placed in the upper side of the popup.

Classification
UNCLASSIFIED
The functionalities are described in the table below.
Table 2: Help Online Functionalities
Icon Functionality
Save the entire help Online as a PDF file.
Print the entire help Online. By clicking on it, a pre-

defined operating system window is shown.
These functions allow page navigation. The first icon

takes the user to the first page, the second one shows
the previous page, the third one shows the next page
and the last one goes to the last page.
In the middle, the user can type directly the page num-
ber to be shown.
A zoom function is available. The last three icons per-

mit to set a predefined view of the manual (one or two
pages).
Use the ‘Find’ area to search for specific text.

Classification
UNCLASSIFIED
1.5 RECURRENT ACTIONS

The following paragraphs describe a set of common features applicable to all pages in Heliwise.
Notifications
In the bottom right corner, Heliwise advises the user regarding each change applied to one aircraft of the
user’s fleet.
As shown in the images below, there are two types of notification.
The first one informs about the progress of an operation launched by the same user logged in. It closes by
itself when the operation finishes.
Figure 26: 1st Notification
The second one communicates the result of an operation executed by another user logged in.
In this case, you have to confirm the receipt of notification by clicking on the green tick icon as shown in the
figure below.
Figure 27: 2nd Notification
Filter Window
Each column in a table has a filter icon which allows the user to open a dedicated filter popup.
Figure 28: Header Filter

Classification
UNCLASSIFIED
See the table below for more details.
Table 3: Filter Functionalities
Filter Description
To open the filter window, double click on the relevant
icon.
The popup opens and it allows the filtering of the data

placed in the relevant column.
To select all options placed in the top area, tick the

check box labelled ‘Select all’ otherwise the user can
select the data to be shown by hand.
Another way in which the user can filter the data set
placed in the relevant column is using the combo box
placed below the current subtitle: ‘Show rows with
value that’.
The user can select the filter parameter to be used:
• ‘Is equal to’;
• ‘Is not equal to’;
• ‘Starts with’;
• ‘Ends with’;
• ‘Contains’;
• ‘Does not contain’;
• ‘Is contained in’;
• ‘Is not contained in’;
• ‘Is less than’;
• ‘Is less than or equal to’;
• ‘Is greater than’;
• ‘Is greater than or equal to’.

Classification
UNCLASSIFIED
Table 3: Filter Functionalities
Filter Description
Once the combo is filled properly, the user can type

the characters to be searched and the filter will search
the relevant string according to the selected filter.
Below this text box, the user can select the method to
combine multiple filters; it is possible to select ‘And’ or
‘Or’.
After that, the second parameter is configurable like

the first one.
At the bottom of the popup there are two buttons: ‘Fil-

ter’ and ‘Clear Filter’.
Use the first one to apply the parameters or the sec-
ond one to remove the already applied filters.
In case the column is hosting a date time information,

the user can filter using the calendar button placed in
the text box filter in which there is the label ‘Enter
date’.
Sorting Data
The user can sort data ascending/descending alphabetically or ascending/descending numerically. See the
table below for more details.

Classification
UNCLASSIFIED
Table 4: Definitions List
An upward pointing arrow appears above the col-

umn header text. This means the data in the col-
umn has been sorted in ascending alphabetical/
numerical order.
If you would like to sort the data in descending
alphabetical/numerical order click once on the col-
umn header showing the upward pointing arrow.
To return to the original order left click again and

the column header will return to its original format
without an arrow and the data in the column
returns to its original order.

Classification
UNCLASSIFIED
Group by Columns
Above some tables in the application there is the text ‘Drag a column header and drop it here to group by
that column’.
Figure 29: Group by Columns
Drag and drop the column header into the area labelled ‘Drag a column header and drop it here to group by
that column’.
For example, if you want to group the data shown by ‘Code’, drag the relevant column header and you will
see the grid grouped by Code.

Classification
UNCLASSIFIED
Figure 30: Group by 1st column
At the top of the table the text area ‘Grouped by’ identifies which are the grouped columns. The arrow above
the header text shows that the data has been automatically sorted into ascending alphabetical/numerical
order.
Figure 31: Header of grouping columns
To return to the original layout of the table click on the close button on the right side of the header. Repeat
the operation until all the grouped column headers have been closed and the table returns to its original lay-
out.
Figure 32: Ungroup columns

Classification
UNCLASSIFIED
Exporting
Through the exporting functionalities, the user is able to generate an external file which contains the same
content as the dialog currently shown.
The Exporting functionalities are placed in a contextual menu which appears over the dialogs used to
analyze the data. The image below shows its design.
Figure 33: Export and Reporting menu
After right clicking on a grid or a chart, the menu shown above appears. Moving over the “Export” option, the
available functionalities are shown. On a chart, you can also export as ‘PNG Image’ or ‘BMP Image’.
Figure 34: Export functionalities
After clicking on a format, the browser opens an operating system window in which the user can select the
path where save the file just created.
Reporting
The GS supports the user during the creation of a report, the relative features are contained in the same
menu used for exporting.
Right click on a table and then move the mouse over the “Reporting” option, the functionalities available are
shown below.
Figure 35: Reporting functionalities
Clicking on “Save Grid as PDF”, the browser opens a window in which to select the folder where to save the
file. The result is a PDF file which contains the selected grid and its content.
The others options allow the user to create and customize a new report. The user can navigate through the
dialogs and add the desired grids with the option “Add Grid to Report”. Once all grids have been added to

Classification
UNCLASSIFIED
the report, the user can save it as PDF and select the folder. Another feature named “Clear Report” allows
the user to clear the report of all selected grids.
Chart Capabilities
There are many dialogs which are based on a chart elaboration. It’s always possible to interact with a chart
by right clicking on it. The result is a contextual menu which is able to recognize the environment where it
has been used and retrieves a menu displaying the available functionalities. By right clicking on a chart the
following menu appears:
Figure 36: Chart Menu – Common buttons
The four options above the separator line are always visible because they are applicable to all types of
charts. Whereas the options below are dynamically shown according to the selected chart.
Zoom
Figure 37: Chart Menu – Zoom
The zoom can be adjusted by scrolling the mouse wheel. Select ‘Reset Zoom’ to return to the original set-
tings.

Classification
UNCLASSIFIED
Settings
Figure 38: Chart Menu – Settings
The ‘Chart Settings’ menu option applies to the modes in which the chart represents the information.
Select ‘Change series Type’ option to modify the way in which you view the chart.
It’s possible to set the visibility of the tooltip and the grid lines. The options work as on-demand requests,
they will not apply as default settings. Clicking on the first option “Change Series Type”, the user can set the
way in which the data is displayed in the chart.
Export
Figure 39: Chart Menu – Export
It is possible to export the chart as a PNG image, a BMP image or as CSV Data. In each case your browser
opens and you can select a destination in which to save the file.
The CSV data is not always visible, it depends on the applicability of the data contained in the chart.
Reporting
Figure 40: Chart Menu – Reporting
It is possible to report data by selecting ‘Reporting’ from the menu. Another menu opens and you can select
‘Save Grid as PDF’ or ‘Add Grid to Report’. Their functionalities are explained above in the previous chapter.

Classification
UNCLASSIFIED
Flip to Grid
One of the features applicable to a chart is called “Flip to Grid.
Figure 41: Chart Menu – Flip to Grid
As shown in the image above, the option allows flipping the view from a chart to a table.

Classification
UNCLASSIFIED
Close
The option “Close” closes a specific view of a chart. It is very useful in several dialogs when the user can
decide to view multiple charts on a single page.
Figure 42: Chart Menu – Close
Axes
The “Axis” option menu allows to change the view mode of values placed in both axes.
Figure 43: Chart Menu – Axes
As shown in the image above, the user can change the value represented in an axis.
The possibility to change both axes or only one depends on the current chart.

Classification
UNCLASSIFIED
Switch Harmonics/Sidebands
By clicking on the “Switch Harmonics/Sidebands” option, the user is able to identify which are the abscissas
in a specific point.
Figure 44: Chart Menu – Harmonics and Sidebands
As shown in the image above, once the contextual menu is opened the user has to click on “Switch Harmon-
ics/Sidebands”.
Clicking on it once, the “Harmonics” mode enables and each time the user clicks on chart the system shows
the relative abscissa.
Clicking on it twice, the “Sidebands” mode enables and each time the user clicks on chart the system shows
the relative abscissa and its multiple values.
Show/Hide Axis Cursor
Identifies the coordinate of a point in a chart.
Figure 45: Chart Menu – Show/Hide Axis Cursor
Once the contextual menu is opened, the user is able to click on “Show/Hide Axis Cursor”. Clicking on this
option, the chart enables a mode which shows the coordinates of the mouse pointer.

Classification
UNCLASSIFIED
Show/Hide Thresholds
To show the relative threshold.
Figure 46: Chart Menu – Show/Hide Thresholds
Once the contextual menu is opened, clicking on “Show/Hide Thresholds” the user is able to see the relative
thresholds according to the data loaded.

Classification
UNCLASSIFIED
1.6 HOME PAGE

Once a user has logged in, Heliwise shows the Helicopters assigned to the Customer fleet by default.
As shown in the image below, it’s possible to view general information about the Customer H/Cs.
The Aircraft are grouped according to status.
Figure 47: Fleet Home

Classification
UNCLASSIFIED
The possible H/C statuses are shown in the table below.
Table 5: H/C Status
Helicopter Status Definition

The H/C’s temporary condition during dynamic data
population and up to H/C acceptance: you can
insert/update/delete components and their metric
consumption details.
An H/C which is temporarily frozen because of anal-
ysis in progress or a problem with the aircraft.
The Helicopter is able to fly. It could have several

active arisings; however, the GS ensures that they
are not blockers.
The Helicopter is not able to fly. The active arising
blocks any type of flight, the user must clear the
event.
The H/C status while there is a download in process.
Each Helicopter is displayed in a dedicated section as shown below. Each section shows the tail number,
the serial code and the date of the last Heliwise update.
Figure 48: Helicopter in fleet
If there is a warning icon (as shown in the figure below) in front of the H/C image there is at least one DSN to
be processed.
Figure 49: Alert on Aircraft

Classification
UNCLASSIFIED
Four colour coded indicators are displayed on the right side of the section. These indicators represent macro
areas in which an arising could be active. When the indicator is green there is no active arising, when it is
amber or red there is an active arising; red meaning that the arising is more serious than amber.
Figure 50: Home Page – Contextual Menu
As shown in the image above, right clicking on the H/C the user can navigate to the analysis pages.

Classification
UNCLASSIFIED
Aircraft Details
By clicking on a single H/C, the user can view summary data of the selected H/C.
Figure 51: H/C Status
Near the image of the H/C, there are four indicators regarding the presence of arisings in each subsystem
(as in the Home Page). Below the image, the H/C status is displayed.
In the upper part of the page, the user can view a group box containing the following information about the
selected H/C:
• ‘Tail Id’; the tail identification number of the selected H/C.

• ‘HcSerialCode: the serial assigned to selected H/C.
• ‘Variant’; the variant of the selected H/C.
• ‘S/W Version’; the software version installed on the selected H/C.
• ‘Role’; an alphanumerical field which shows the roles used to define H/C configuration.
• ‘Environment’; the flying environment of the selected H/C.
• ‘Location’; the place where the H/C is situated.

Classification
UNCLASSIFIED
The group box on the right displays the following information regarding the last processed download:
• ‘Id’; number of the last download.
• ‘Date Time Start’; date and time references about the start of last download.
• ‘Date Time End’; date and time references about the end of last download. Being the end of
last download, it can be considered as the date until the Helicopter was updated with data
download from DTD.
• ‘FH start’; the indicator of flight hours when the last DSN was started.
• ‘FH End’; the end flight hours of last DSN. They can be considered as Total Flight Hours of
Helicopter.
Below the status, there are two icons. The first one is used to select the arising view and another one to view
the cumulative metrics values.
Figure 52: H/C Icons
By default the page shows a list of active arisings (status is ‘Open’ or ‘Pending’).
Figure 53: H/C Arising list
The column filter can be used to view arisings which have been cleared or rejected in the last 10 DSNs.
In this table you can view the following data:
• ‘DSN’; the Download Serial Number in which the Arising was raised.

Classification
UNCLASSIFIED
• ‘Description’; description of the arising.

• ‘Reason’; the type of TVM Exceedance. The cell is colored according to its type.
•
•
•
•
•
•
• ‘Update Time’; the recorded time of the last update.
• ‘Update Author’; who modified the arising the last time.
• ‘Number’; the arising ID (useful for carrying out a search in other parts of Heliwise).
• ‘Status’; the status of the arising. It can be ‘Open’, ‘Pending’, ‘Cleared’ or ‘Rejected’ and it is shown with
different colors.
• - Light brown shows a ‘Pending’ status. This means it is waiting user action.
• - Amber shows an ‘Open’ status.
• - Green shows a ‘cleared’ or ‘rejected’ status in which there are no further
actions to be carried out.
• ‘Remarks’; Any comments regarding the arising inserted by the user that debriefed the download.
Arising Management
By default the most critical arisings are displayed first. Here the user can manage the active arising by right
clicking on one of them.
Figure 54: AC Details – Contextual Menu
In the contextual menu, you can click on “Clear” to close the “Open” arising.
Otherwise, if the Arising has a “Pending” status and the options available will be “Accept” or “Reject”.
To quickly navigate to the analysis of TVM data, click on “Analyze...” and select “TVM Health Indexes”. For a
description of the page please refer to the Aircraft TVM Data module.

Classification
UNCLASSIFIED
Figure 55: AC Details - TVM shortcut
If the arising occurred due to an RTB exceedance, the web application allows the user to quickly navigate to
the RTB Health Index Trend by means of the ‘Analyze…’ option.
Figure 56: AC Details – RTB shortcut
If the arising was raised due to multiple occurrences of a fault, you can right click in the ‘Reason’ column and
select ‘Analyze..’ > ‘Faults’. In this way the user is taken directly to the ‘Faults’ page.
Figure 57: AC Details - Fault shortcut
Clicking on the icon you can view the table of cumulative values of the selected H/C.

Classification
UNCLASSIFIED
Figure 58: AC Details - Cumulative values
• ‘Description’, a description of the metric.

• ‘UoM’, the corresponding unit of measure.
• ‘Entry Date Time’, the date and time of entrance into the fleet.
• ‘Cumulative Value’, the cumulative value of the data displayed.

Classification
UNCLASSIFIED
1.7 SYSTEM ADMINISTRATION
The System Administration module manages personal information (such as the password for login) and
other system settings.
Figure 59: System Administration area

Classification
UNCLASSIFIED
1.7.1 User Audit Log

On this page the user can view the logs relevant to their navigation, and errors encountered during usage.
Figure 60: Audit Log
The creation of these files is linked to user access; each time a user accesses the application a new group
of rows is automatically generated.
Figure 61: User Audit Log columns

Classification
UNCLASSIFIED
As shown in the image above, the log file name consists of the date and time of the session recorded.
The page consists of a table showing the following columns:
• ‘File Date Time’; the date and time of the log file entry shown in DD_MM_YYYY HH.MM.
• ‘Date and Time’; the date and time of the action recorded by the log, shown in DD_MM_YYYY
HH.MM.SS.
• ‘Message’; information regarding the action recorded by the log.
• ‘Message Details’; the internal methods called to execute that action.
• ‘Category’; the category of the message.
• ‘Priority’; the priority of the message represented by a circle which can be green, grey or red.

Classification
UNCLASSIFIED
1.7.2 User Management
The following chapters describe the functions available in the Users Management area.
1.7.2.1 Users Button
By default the Users Management area opens on the ‘Users’ page (the Users button is highlighted). On this
page there is a list of users and details regarding each user. By selecting a user from the Users list it is pos-
sible to view the profile associated with the user and the group associated with the user.
Figure 62: Users Management - Users page
On the ‘User’ page there are three main areas: ‘Users’, ‘Group Detail’ and ‘Profile Details’.
At the top of the page there is a table which contains a list of users and information regarding these users. In
this table you can view the following information:
• ‘User Code’; an alphanumerical code given to the user.

• ‘Name’; the first name of the user

Classification
UNCLASSIFIED
• ‘Surname’; the last name of the user

• ‘Group’; the group code associated to the user profile
• ‘Profile’; the profile associated with the user
• ‘Supervisor Flag’; a check box which is flagged if the user is the Super Administrator of the GS
• ‘Enabled Flag’; a check box which is flagged if the user has been disabled
• ‘Password Change Flag’; a check box which you click if the user is required to change password at the
next log in
• ‘ReadOnly’; indicates if the user can only see the data in the web application without applying any type of
change, such as arising management
• ‘Email address’ the user’s email address
If the ‘Edit User’ button is clicked the ‘Users’ table flips around and displays the ‘Edit a User’ group box. In
this area it is possible to edit the following information for the selected user:
• ‘Name’; the first name of the user

• ‘Surname’; the second name of the user
• ‘Group’; a drop down menu displaying all the available group codes which can be associated with the
user
• ‘Profile’; a drop down menu displaying all the available profiles which can be associated with the user
• ‘Options’; a group box displaying the following check boxes which can be flagged to select them:
a. User read only
b. User in company
c. Enable AVDM
The user code and email address cannot be edited and are read only.
Two buttons are available on the right side of the ‘Edit a User’ group box: ‘Accept’ to save the changes and
return to the ‘Users’ table; ‘Cancel’ to return to the ‘Users’ table without saving the change.
Figure 63: Edit a User buttons

Classification
UNCLASSIFIED
The ‘Group Details’ area in the lower left side of the page displays the aircraft contained within the group
code that has been associated with the user. This area is not editable and displays the group details for the
user selected in the ‘Users’ table at the top of the page.
Figure 64: Users page - Group Details
The ‘Profile Details’ area in the lower right side of the page displays the profile associated with the user
selected from the ‘Users’ table at the top of the page. The user profile determines which areas of the Heli-
wise application a user has access to. All possible areas of the Heliwise application are listed in the ‘Profile
Details’ area, those which the selected user has access to have a flagged check box next to them. This area
is not editable.
Figure 65: Users page - Profile Details

Classification
UNCLASSIFIED
Users with the appropriate credentials can edit or delete a user from the ‘Users’ table at the top of the page.
The two tables below describe how to carry out the two actions.
Table 6: Edit user
Action to edit a user Description
Select a user to edit from the table.
When a user is selected the row is highlighted in

blue.
After clicking on the ‘Edit User’ icon the table flips

and displays the ‘Edit a User’ group box display-
Click on the ‘Edit User’ icon at the top of the table. ing the user’s details.
Edit the required fields and then click on the

‘Accept’ button.
The changes are saved and the ‘Edit a User’ area
flips back to the ‘Users’ table view.
Table 7: Delete a user
Action to Delete a user Description
Select a user to delete from the table.
When a user is selected the row is highlighted in

blue.

Classification
UNCLASSIFIED
Table 7: Delete a user
Action to Delete a user Description
After clicking on the ‘Delete User’ icon a pop up

window opens asking for confirmation to delete
Click on the ‘Delete User’ icon at the top of the the user.
table.
Click on the ‘OK’ button to confirm deletion of the After clicking the ‘OK’ button the selected user is
selected user. deleted and is removed from the list of users.

Classification
UNCLASSIFIED
1.7.2.2 Groups Button

After clicking on the ‘Groups’ button the ‘Groups’ page opens. On this page it is possible to add, edit or
delete a group. A group consists of a group code to which A/C are assigned. The group code can then be
associated with a user and therefore that user has access to those A/C in that group.
Figure 66: User Management - Groups page
At the top of the ‘Groups’ page there is a table displaying any existing groups. From this table it is possible to
add, edit or delete groups.
The table displays the following information for each group:
• ‘Group Code’; the name of the group

• ‘Description’; a brief description of the group
• ‘No. Aircraft’; the number of aircraft assigned to the group
Above the ‘Groups’ table there are three buttons which allow the user to add, edit or delete a group.

Classification
UNCLASSIFIED
Figure 67: Add, Edit, Delete H/C Group
After clicking on the ‘Add New H/C Group’ the table flips around and displays the ‘Add a new Group’ group
box. In this group box it is possible to insert the following information in order to create a new group:
• ‘Group Code’; insert an alphanumeric code for the group (max 30 characters)
• ‘Description’; insert a brief description of the group (max 30 characters
Figure 68: Add a new H/C group
To save the new group and return to the ‘Groups’ table click the ‘Accept’ button. To return to the ‘Groups’
table without saving the new group, click ‘Cancel’.
Figure 69: Add new H/C Group - buttons
Now it is possible to add H/Cs to the ‘Group Details’ area from the ‘H/C in Fleet’ area. Click on one or more
H/Cs to select or deselect them and then use the move arrows to put the selected H/Cs into the ‘Group
Details’ group. The new group is automatically saved.

Classification
UNCLASSIFIED
Figure 70: Group Details
To edit an existing group, select the group from the ‘Groups’ table and then press the ‘Edit H/C Group’ but-
ton. The table flips around and displays the ‘Edit a Group’ group box. In this group box it is possible to edit
only the description of the group; the group code is read only.
To save the edited group and return to the ‘Groups’ table click the ‘Accept’ button. To return to the ‘Groups’
table without saving the modifications, click ‘Cancel’.
Figure 71: Edit a Group
It is possible to add/remove H/Cs in the ‘Group Details’ area to or from the ‘H/C in Fleet’ area. Click on one
or more H/Cs to select or deselect them and then use the move arrows to put the selected H/Cs into the
‘Group Details’ group.
To delete a group select it from the table and then click on the ‘Delete Group’ button. A pop up window
opens asking for confirmation of the deletion. Click ‘OK’ to confirm or ‘Cancel’ to return to the table without
deleting the group.
Figure 72: Delete group pop up

Classification
UNCLASSIFIED
The following three tables provide a quick guide on how to add, edit or delete a group.
Table 8: Add a group
Action to add a group Description
After clicking on the ‘Add new H/C group’ button

Click on the ‘Add new H/C group’ button at the top the table flips and displays the ‘Add a new group’
of the table. group box.
Insert the data in the required fields and then click

on the ‘Accept’ button.
The changes are saved and the ‘Add a new group’
area flips back to the ‘Groups’ table view.
With the new group selected in the ‘Groups’ table.

Move the required H/Cs from the ‘H/C Fleet’ area When the desired H/Cs have been moved to the
to the ‘Group Details’ area using the move arrows. ‘Group Details’ area, the group is automatically
Multiple H/C can be selected or deselected by saved
clicking on them.

Classification
UNCLASSIFIED
Table 9: Edit a group
Action to edit a group Description
Select a group to edit from the table.
When a group is selected the row is highlighted in

blue.
After clicking on the ‘Edit H/C Group’ button the

Click on the ‘Edit H/C Group’ button at the top of table flips and displays the ‘Edit a group’ group
the table. box.
Edit the required fields and add/remove H/Cs from

the ‘Group Details’ area
Click on the ‘Accept’ button.

The changes are saved and the ‘Edit a group’
area flips back to the ‘Groups’ table view.

Classification
UNCLASSIFIED
Table 10: Delete a group
Action to Delete a group Description
Select a group to delete from the table.
When a group is selected the row is highlighted in

blue.
After clicking on the ‘Delete Group’ button a pop

up window opens asking for confirmation to delete
Click on the ‘Delete Group’ button at the top of the the group.
table.
Click on the ‘OK’ button to confirm deletion of the After clicking the ‘OK’ button the selected group is
selected group. deleted and is removed from the list of groups.

Classification
UNCLASSIFIED
1.7.2.3 Profiles
After clicking on the ‘Profiles’ button the ‘Profiles’ page opens. On this page it is possible to add, edit or
delete a profile. A profile consists of a set of pages on the Heliwise application that can be assigned to a
user, this means different users can have access to the areas of the application which are relevant to the
specific user.
After clicking on the ‘Profiles’ button the page opens displaying a list of profiles on the left and a list of Heli-
wise pages on the right. Once a profile has been selected from the table on the left, the pages which are
associated with that profile are flagged in the check box next to the page item in the list on the right.
Figure 73: User Management - Profiles page

Classification
UNCLASSIFIED
At the top of the page there are three buttons which allow the user to add, edit or delete a profile.
Figure 74: Profile add, edit, delete buttons
To Add a new profile click on the ‘Add New Profile’ button. The table on the left flips around to display the
‘Add a new profile’ group box. In this group box it is possible to insert the following information:
• ‘Profile Code’; an alphanumeric code for the new profile (max 30 characters)
• ‘Description’; a brief description of the new profile (max 30 characters)
Figure 75: Add a new profile
The table on the right is empty at this point and states: ‘Configure after creating a profile’. To create the new
profile click on the ‘Accept’ button. To return to the table without saving the profile click on the ‘Cancel’ but-
ton.
Once the profile has been created it is visible in the table on the left. Click on the new profile to select it and
then flag the check boxes of the pages which shall be assigned to the profile from the ‘Profile Details’ list on
the right of the page. The pages can be deselected by unflagging the check boxes. The selection is automat-
ically saved.

Classification
UNCLASSIFIED
Figure 76: Profile details
To edit an existing profile selected from the list on the left simply click on the ‘Edit Profile’ button at the top of
the page. The table on the left flips around to display the ‘Edit a profile’ group box. In this group box it is pos-
sible to modify the following information:
• ‘Description’; a brief description of the new profile (max 30 characters)
The ‘Profile Code’ is not editable.
Figure 77: Edit a profile
The pages assigned to the profile can also be edited by flagging or unflagging the check boxes in the ‘Profile
Details’ area as required. Click the ‘Accept’ button to save any changes made and return to the profiles list,
or click ‘Cancel’ to return to the profiles list without saving the modifications.

Classification
UNCLASSIFIED
To delete a profile select it from the table and then click on the ‘Delete Profile’ button. A pop up window
opens asking for confirmation of the deletion. Click ‘OK’ to confirm or ‘Cancel’ to return to the table without
deleting the profile.
Figure 78: Delete Profile
The following three tables provide a quick guide on how to add, edit and delete a profile.
Table 11: Add a profile
Action to add a profile Description
After clicking on the ‘Add New Profile’ button the

table flips and displays the ‘Add a new profile’
group box.
Click on the ‘Add New Profile’ button at the top of
the table.

The changes are saved and the ‘Add a new pro-
file’ area flips back to the ‘Profiles’ table view.
With the new profile selected in the ‘Profiles table.

When the desired pages have been selected, the
Flag the check boxes next to the required pages
profile is automatically saved
in the ‘Profile Details’ area

Classification
UNCLASSIFIED
Table 12: Edit a profile
Action to edit a profile Description
Select a profile to edit from the table.
When a profile is selected the row is highlighted in

blue.
After clicking on the ‘Edit Profile’ button the table

flips and displays the ‘Edit a profile’ group box.
Click on the ‘Edit Profile’ button at the top of the

table.

The changes are saved and the ‘Edit a profile’
area flips back to the ‘Profiles’ table view.
With the profile selected in the ‘Profiles table.

When the desired pages have been selected, the
Flag/unflag the check boxes next to the required
profile is automatically saved
pages in the ‘Profile Details’ area

Classification
UNCLASSIFIED
Table 13: Delete a profile
Action to delete a profile Description
Select a profile to edit from the table.
When a profile is selected the row is highlighted in

blue.
After clicking on the ‘Delete Profile’ button a pop

up window opens asking for confirmation to delete
Click on the ‘Delete Profile’ button at the top of the the profile.
table.
Click on the ‘OK’ button to confirm deletion of the After clicking the ‘OK’ button the selected profile is
selected profile. deleted and is removed from the list of profiles.

Classification
UNCLASSIFIED
1.7.3 System Settings

This pop-up allows the user to change personal settings regarding the current management of ESUM files,
synchronization of offline data and AW139 functions.
Figure 79: Heliwise Settings
See the table below for more details.
Table 14: Change Heliwise Settings
Setting Description
Use Heliwise Local Data Manager This setting refers to the Heliwise Sync Agent
application. Enabling the Local Data Manager the
user allows the application to auto-synchronize its
offline data with the online information.
This setting must be set to NO otherwise the offline

database will not be synchronized.

Classification
UNCLASSIFIED
Table 14: Change Heliwise Settings
Setting Description
Use Automatic ESUM File Manager Enabling this option the user allows Heliwise to
upload in the background its ESUM data to the
FHD server.
Activate Local ESUM File Logger Enable or disable the log tracing of ESUM files
upload.
AW139 functions
This area allows the user to set the DTD initialization mode, the debrief type and activate or not the AAD
data replication.
Figure 80: Heliwise Functions - AW139 Functions

Classification
UNCLASSIFIED
Table 15: AW139 Functions
Setting Description
DTD Initialization Mode if set on 'auto' the PCMCIA DTC will be automati-
cally initialized following a debrief
Debrief Type set on 'fast' to automatically debrief files following

an upload or 'slow' to manually debrief files
if set on 'yes' it enables the replication of the file

AAD Data Replication
during upload phase. See below for further details.
The AAD Data Replication folder must be set as follows:
32Bit OS
C:\Program Files\GE Aviation\Information Exploitation AW139 Client Software\AW139 Full DTD\
64Bit OS
C:\Program Files(x86)\GE Aviation\Information Exploitation AW139 Client Software\AW139 Full DTD\
To install the ‘AAD Client’ (always run as Administrator) under Windows 7/8/10 64 bit, please consider
merging a .key patch which can be provided by LH HUMS Support Team.
In addition, set the AAD Client Options as follow:
• Right Click on the AAD Client

• ‘Pause’ and ‘Turn Archiving On’ are displayed (as fig. below): left click on the labels to change their sta-
tuses
• On ‘Channel Options’ check that ‘Full DTD Only’ is selected
Figure 81: AAD Client Options

Classification
UNCLASSIFIED
The DTD backups will be stored in the following folder:
C:\ProgramData\AgustaWestland\HeliwiseClient\DSNManagement189

Classification
UNCLASSIFIED
1.8 DATA MANAGEMENT
Moving the mouse over the sixth icon placed in the main menu, the “Data Management” module expands.
Figure 82: Data Management area
The Data Management menu allows the user to transfer and process HUMS data coming from the aircraft
card to the Heliwise Web Site.
As shown in the image above, in Data Management, the following modules are listed in the menu:
• DTC Download: This module allows the user to download files from the local folder and upload them to the
Heliwise on line server.
• Data Debrief: This module allows the user to process the HUMS data previously uploaded and to review
the 5 most recent DSN downloads.
• DSN Management: [applicable only for AW169/AW189 helicopters]. This module allows the user to get
HUMS data via Wi-Fi or Ethernet from the DTD Panel. Only valid for AW169/AW189, however, in this sec-
tion the user is able to find the list of the most recent AW139 uploaded data. FULL button is to be ignored.
• PCMCIA Management: This module allows the user to initialize the card and to upload the INIT file (Initial
parameters) on the Helicopter.

Classification
UNCLASSIFIED
1.8.1 DTC Download

The following page is displayable by clicking on the menu item ‘DTC Download’ in the Data Management
module. Here you can transfer the MDS folder from your local PC to the online server.
Figure 83: DTC Download
Figure 84: DTC Download – include/exclude SUM files

Classification
UNCLASSIFIED
You can decide whether to upload SUM files or not. Since these files are big, uploading them could impact
on the time required to complete the downloading process. Heliwise automatically remembers the last
choice. By excluding the SUM files the ground station will upload the other data more quickly.
To upload the HUMS data placed on a USB, SSD or file system, click on “My Computer” and select the
folder which contains the download data. You should click on the ‘Select’ button when the single files are dis-
played in the central area.
Figure 85: Browse folder
Once the folder has been selected, the web application displays a message which requires user action.

Classification
UNCLASSIFIED
Figure 86: DTC Download – Full or QA
The user has to click on ‘Full’ to perform a debrief with file usage, otherwise click on ‘Quick’ to obtain a quick
overview of the TVM exceedances. In both cases the application closes the popup and proceeds to upload
the file to the Leonardo Helicopters’ server.
The system shows the progress and status of the process in the central area. Four steps are used to repre-
sent the entire process: Read, Compressing, Upload and Validation.
• Read: Heliwise is able to read the folder in which the download package is placed.
• Compressing: Heliwise compresses the files before uploading them on the Internet.
• Upload: Heliwise uploads the entire download folder (compressed) from the local operator PC to the
Leonardo Helicopters’ online server.
• Validation (applicable only to Full download): Heliwise checks the integrity of the downloaded data; soft-
ware version used to record it and it checks whether the tail code plugged in the HUMS data is actually
part of the AC fleet.
• Read HC Info Files (applicable only to Quick Access download). Heliwise reads the information placed
directly in the VM AUTO and VM RESULT files.
The page consists of a grid which shows all uploading files.

Classification
UNCLASSIFIED
Figure 87: Upload Files – DTC Content
As shown in the image above, the grid contains multiple columns to specify the files contained in the down-
load folder:
• Directory  path where is placed the download file.

• Name  The name of file validated.
• File Size  The size of file uploaded (In bit).
In the upper part of the area, you can see information about the total size of the download folder and the
type of DSN selected before.
Once the uploaded is completed, the pages can execute two different actions according to the type of pro-
cess (Full or QA).

Classification
UNCLASSIFIED
1.8.1.1 DSN Full Download

In this case, the application returns a message in which the name of the DSN row added in the Data Debrief
page is specified.
Figure 88: Upload Files – Operation completed
For its data processing refer to Data Debrief page.

Classification
UNCLASSIFIED
1.8.1.2 DSN Quick Assessment
In the case of QA, the page immediately opens a window in which the user can directly analyse the TVM
exceedances occurred from the last download.
Figure 89: Quick Access overview
As shown above, the ‘look and feel’ are similar to the Health Index page used for the analysis of TVM Aris-
ings. The upper part consists of information about the helicopter.
This section displays the following details:
• ‘Tail ID’; an alphanumeric field which exclusively identifies the H/C selected.
• ‘HC Status’; the current status of the H/C selected.
• ‘Variant’; the variant of the H/C selected.
• ‘AMMC Ver’; the version of AMMC.
• ‘Running Hours’; the operative hours in which the HUMS data were recorded.
• ‘Last DSN’; a sequential number which identifies the last DSN carried out.
• ‘Flight Hours’; the total flight hours of the selected H/C.
• ‘Last DSN End’; the date and time of the end of the last DSN (DD_MM_YYYY HH.MM.SS).
• ‘DSN Type’; reports the type of DSN.
Figure 90: H/C details

Classification
UNCLASSIFIED
To maximize the window, click on the square icon placed in the top right corner of the page.
In the central area of the page, the application plots the results obtained by processing the TVM data regard-
ing the selected helicopter. By default, the page shows the acquisition which contains at least one exceed-
ance and the relative HI exceeded (highlighted with a blue square).
Figure 91: QA page – HI list
To switch to another TVM acquisition you have to use the combo list placed above the plotting area.

Classification
UNCLASSIFIED
Figure 92: QA page – Acq. List
The TVM components are identified by the acquisition Id, Type, Description and Accelerometer, on the right
the user can see the presence and quantity of exceedances. By clicking on one of them, Heliwise automati-
cally plots the health index in which there is an exceedance.
Figure 93: QA page – Auto Plotting

Classification
UNCLASSIFIED
The left side of the area consists of the list of Health Indexes applicable to the selected TVM component. By
ticking them, the user can decide which HI to plot in the central area.
The user can hide this list by clicking on the button placed in the upper-left corner (red arrow).
Figure 94: QA page – Close HI List
To show the list, click again on the same button (meanwhile the arrow has become green).
Figure 95: QA page – Open HI List
Near the list of TVM Components, the user can see the Close Monitoring status regarding the selected
acquisition.
Figure 96: QA page – Close Monitoring
In the toolbar, by a calendar button the user can set whether to visualize one or two charts per view (as
shown below).
Figure 97: QA page – Plots number

Classification
UNCLASSIFIED
Each chart has a button placed in the upper part of the view, in which the user can set the legend of acquisi-
tions to be plotted.
Figure 98: QA page – Legenda
By default the HI plot shows the following data:
• Abscissa axis composed by Flight Hours indications;

• Value 0 of y-axis show with a green line;
• Blue, Amber and Red Steady Threshold - moving over the TH line, the chart shows the type of TH (tem-
porary, learned or permanent);
• Vertical line to indicate where the thresholds was reset (Permanent thresholds not included) due to parts
removal or manual reset;
• Vertical line to show where the Quick Assessment begins to display data.

Classification
UNCLASSIFIED
Furthermore, every point representing an acquisition has a tooltip. Moving over one of them, the application
shows the main information. In detail, the following information is displayed:
• DSN number to identify the download from which the acquisition was generated;
• Acq. Date Time to get out when the acquisition was tracked;
• Acq. Flight Hours to indicate how many FH were recorded when the acquisition was tracked;
• A/C Flight Hours to indicate the total number of Flight Hours recorded by the current DSN;
• Health Index to show which index is being showing;
• The Value of health index.
Figure 99: QA page – tooltip
By right clicking anywhere on the plot, you can select the option ‘Show Extended ToolTip’. As a result the
tooltip will display additional information such as IAS, Engine 1 Torque, Engine 2 Torque, Main Rotor Torque,
Tail Rotor Torque, Pitch and Roll degrees.
Figure 100: QA page – Extended Tooltip

Classification
UNCLASSIFIED
By clicking on an acquisition of HI plots, Heliwise shows the same acquisition in the other HI plots which are
already open. The selected acquisition is identifiable by a green circle around it.
Figure 101: QA page – Acq. Selection
To zoom select an plot area by dragging and dropping the mouse pointer, to reset the zoom click twice. Oth-
erwise, you can zoom the view by using the scroll wheel of the mouse.
Figure 102: QA page – Zoom an area

Classification
UNCLASSIFIED
As explained above, by right clicking on any point of the plot, the web application displays the following con-
textual menu:
Figure 103: QA page – Contextual menu
The menu contains the following functionalities:
• Zoom; to reset the zoom and focus on all acquisitions;

• Chart Settings.
Figure 104: QA page – Chart Settings

Classification
UNCLASSIFIED
It is possible to hide the automatic tooltip and the background coordinates and change the way in which the
acquisition is plotted. Following, an example of:
• XY Plot;
Figure 105: QA page – Chart with Plot
• QA page – Chart with Plot;
Figure 106: QA page – Chart with Step Area

Classification
UNCLASSIFIED
• Bar;
Figure 107: QA page – Chart with Bar

• Line;
Figure 108: QA page – Chart with Line

Classification
UNCLASSIFIED
• Line Symbols;
Figure 109: QA page – Chart with Line Symbols
• Export; export in PNG or JPEG of HI plot;

• Reporting; add of chart in the dynamic report available in Heliwise (as explained in the
“Common Functionalities” paragraph at the beginning of user manual chapter);
• Axis X; possibility to switch the value of abscissa from Acq. FH in Acq. Date time and vice
versa;
• Axis Y; possibility to switch the parameters of axis from linear to logarithmic and vice versa;
• Show/Hide Extended ToolTip; view or not the additional parameters in the ToolTip as
described above;
• Show/Hide Thresholds; choose to view or not the thresholds the thresholds;
• Show/Hide DSN Markers; possibility to hide the indicators of start DSN;
• Close; close the HI plot;
• Flip to Grid; report the values in a tabular format. Possibility to export in CSV the HI values
and relative parameters.

Classification
UNCLASSIFIED
Figure 110: QA page – Table view

Classification
UNCLASSIFIED
By right clicking on a row, you can open the contextual menu again, different options are available compared
to the previous one.
Figure 111: QA page – Contextual menu in table
The ‘Show Extended Grid’ option allows to detail the information adding several columns (IAS, Pitch, Roll,
MGB Oil Temperature, MGB Oil Pressure, TGB Oil Temp, IGB Oil Temp, MGB Bearing 1 Oil Temperature,
MGB Bearing 2 Oil Temperature, Engine 1 Torque, Engine 2 Torque, Main Rotor Torque, Tail Rotor Torque,
NR) in order to associate each TVM acquisition with relative Flight Condition and Torque indicators.
The ‘Open Acquisition Thresholds’ allows to get the specific value about the thresholds of selected acquisi-
tion.

Classification
UNCLASSIFIED
Figure 112: QA page – Acquisition Thresholds
The upper part consists of information about the helicopter. This section displays the following details:
• ‘Last DSN End’; the date and time of the end of the last DSN (DD_MM_YYYY HH.MM.SS).
Figure 113: QA page - Thresholds page

Classification
UNCLASSIFIED
The grid shows a list of applicable Health Indexes on that acquisition and each row consists of a HI Code
and a brief description.
Click on the plus icon placed near the HI code in order to view its thresholds.
Figure 114: QA – thresholds of HI
Each HI has two tabs in which the user can visualize the thresholds of steady and trend (this is not applica-
ble to QA).
The grid shown by default regards the threshold values of steady plots and it displays following data:
• Type: the type of steady threshold;

• Value: the current value of TH;
• Status: shows if the TH is permanent (PRM), temporary because its learning is not completed yet or LRN
indicating that the phase of auto-learning is terminated;
• Temp Value: in case of the status is not LRN yet, the TH inherits the temporary value from TH fleet;
• Start Date Time: from which the TH has begun to acquire the custom value;
• Start FH: the FH from which the TH has begun to acquire the custom value;
• Start Initiator: who started the learning of TH;
• Update Date Time: when the user has forced the re-learning;
• Update FH: the FH value when the user has forced the re-learning;
• Update Initiator: who forced the re-learn of TH.
To close the pop-up click on the cross placed in the top-right corner of the window.
Finally, to exit from the QA page click on the door icon placed in the top right corner of the page.

Classification
UNCLASSIFIED
Exceedance View
Below the area dedicated to HI plots, Heliwise displays the exceedance occurrences.
Figure 115: QA page – exceedance list
The grid details each occurrence with following data:
• Acq. Id: id of TMV acquisition.

• Acq. Description: name of TVM Acquisition.
• Threshold Value: value of TH exceeded.
• Highest Health Index Value: highest value of acquisition of that exceedance.
• Lowest Health Index Value: lowest value of acquisition of that exceedance.
• Exceeding Health Index: HI exceeded.
• Thresholds Status: to indicate if the TH is set by AW or is auto-learned in according to specific machine.
• Threshold Type: Red, Amber or Blue exceedance.
• Number of Red Threshold Exceedance: number of red exceedance.
• Number of Amber Threshold Exceedance: number of amber exceedance.
• Number of Blue Threshold Exceedance: number of blue exceedance.
• Downloaded Valid Acquisition: total valid acquisition for that HI.
By right clicking on a single exceedance a contextual menu opens.
Figure 116: QA – analyse exceedance menu
As shown in the image above, the action to be performed is to analyze the exceedance. Once clicked on it,
Heliwise reloads the page with the acquisition which generated the exceedance. On the left side, the HI
exceedance is automatically ticked.

Classification
UNCLASSIFIED
Below the grid, there are three indicators which allow user to get immediately an overview of the number of
red, amber and blue exceedance.

Classification
UNCLASSIFIED
1.8.2 DTC Download (AW139)

NOTE: in order to prepare the settings to allow AAD data replication it is necessary to open the window
which contains Heliwise settings and AW139 functions. Open this window by clicking on the ‘System Admin-
istration’ module icon and then selecting ‘System Settings’ from the menu. A pop up window opens where it
is possible to input the required settings. For a detailed description of the ‘System Settings’ window please
refer to the ‘System Settings’ chapter in this user manual.
Figure 117: System Settings window
The ‘DTC Download’ page can be displayed by clicking on the menu item ‘DTC Download’ in the Data
Management module. Here the user can transfer the MDS folder from the local PC or PCMCIA CARD to an
online server.

Classification
UNCLASSIFIED
Figure 118: AW139 - DTC Download
To upload the HUMS data placed on a USB, SSD or file system, click on My Computer and select the folder
which contains the download data. Once the folder is opened and its content is shown, the user shall click on
the Select button.

Classification
UNCLASSIFIED
Figure 119: AW139 - DTC download - Select folder
To upload the HUMS data from the PCMCIA CARD, click on the reader icon and then click on the blue triangle
on the right.
A confirmation popup appears in order to confirm the full upload of the files or to cancel the operation.
Figure 120: AW139 - DTC download - Choose DSN process
After pressing FULL, a DTC Overview window will be displayed.
If the sequence of the operations is congruent with the last processed Operation (OPN), a green light bullet
will be displayed. It is now possible to proceed with the download by clicking Proceed.
In this case, the application closes the popup and proceeds to upload the file to Heliwise server

Classification
UNCLASSIFIED
Figure 121: AW139 - DTC Download - Overview (correct)
A red bullet will be displayed if the helicopter is not present in the current Fleet and consequently the upload
Operations (OPN) will be discarded.
Figure 122: AW139 - DTC Download - Overview (not in fleet)
Also a red bullet will be displayed if the same operation has been found pending on the server.
The user can now commit them or discard the commit with the cancel button.

Classification
UNCLASSIFIED
Figure 123: AW139 - DTC Download - Overview (pending)
A blue bullet will be displayed if a time gap is detected between the last processed OPN and the new ones.
Figure 124: AW139 - DTC Download - Overview (time gap)
Once the upload operation has been launched with the Proceed button, the system displays the progress
and status of the process in the central area as shown in the figure below.
Nine steps are used to represent the entire process: Read, Validating, Analyzing, Compressing, Backup, Sav-
ing, Transfer, DTC Acknowledge Content and Begin Validation.

Classification
UNCLASSIFIED
• Read: Heliwise is able to read the folder in which the download package is placed.
• Validating: Heliwise validates the files before uploading them on the FTP server.
• Analyzing: Heliwise analyzes the files before uploading them on the FTP server.
• Compressing: Heliwise compresses the files before uploading them on the FTP server.
• Backup: Heliwise checks if the backup folder is present. If the backup folder is present, it proceeds to
upload the compressed files on AAD client. To modify the AAD service directory, the user shall access
Heliwise Settings section and change the path directory in AAD Data Replication field.
• Saving: Heliwise saves the files into the repository.
• Transfer: Heliwise uploads the entire download folder (compressed) from local operator PC to Leonardo
Helicopters secure FTP server.
• DTC Acknowledge Content: Leonardo Helicopters secure FTP server acknowledges the successful data
transfer.
• Begin Validation: Heliwise checks the integrity of the downloaded data, the software version used to
record and if the tail code recorded in the HUMS data are present among the AC fleet.
Figure 125: DTC Download - upload process
As shown in the image above, the grid contains multiple columns to specify the files contained in the down-
load folder:

Classification
UNCLASSIFIED
Directory The path where is placed the download file.

Name  The name of the validated file.
File Size The size of the uploaded file (in bit).
In the upper part of the area, the user can see the information about the total size of the download folder and
the type of the selected DSN previously selected.

Classification
UNCLASSIFIED
1.8.3 Data Debrief

In this page the user can process the HUMS Data previously uploaded to the server.
Once they data has been uploaded, Heliwise detects Tail Code, AMMC SW version and the date of down-
loads and, in this dialog, creates sub-rows for each H/C.
Figure 126: DSN Status
The page shows a list of all Helicopters placed in the fleet. To interact completely with this dialog the user
has to first upload any HUMS data and create a H/C with the relative serial number.
Procedures
Table 16: DSN List
Actions Description
First, identify the H/C to be debriefed through

the information shown in the grid (H/C model
and serial number). To help the user identify the
correct helicopter and its uploaded HUMS data
a warning icon appears inside the grid.
It indicates that the H/C has some HUMS data
uploaded but still not processed.
Once identified the H/C, expand its node by

clicking on the icon placed in the first column of
the row.
Here, all DSNs relative to the H/C are shown.

Classification
UNCLASSIFIED
The operations allowed on a DSN are shown by right clicking on it.

They are available or not according to the status of the DSN.
Figure 127: DSN List
Below there is a table containing the possible statuses and the relative operations allowed to proceed with
the debriefing. On all DSN statuses, it is possible to remove it by right clicking on the DSN (not applicable for
the DSN already processed).
Table 17: DSN Status
DSN Status DSN Status Description Operation al- Operation Description

lowed
Connected Start time of this DSN corresponds Automatic Debrief Debrief explained below.
with the end time of the last DSN
processed. No time gap is present
between them.
Unconnected Start time of this DSN does not cor- Connect DSN Clicking on it, the ground
respond with the end time of the system automatically cre-
last DSN processed. Time gap is ates a row named “Con-
present between them. nected By User” to cover
the gap with the previous
DSN. Once the gap is
debriefed, it becomes
“Connected” and ready to
process.
Connected By Manual Debrief Complete debriefing pro-
User cess manually, however
the steps shown are the
same used for the auto-
matic debriefing but the
metric have to be filled by
user.
Overlapped The date of this DSN is already No operation
covered by another one. allowed to pro-
ceed. Only the
removal DSN is
visible.

Classification
UNCLASSIFIED
Table 17: DSN Status
DSN Status DSN Status Description Operation al- Operation Description

lowed
Processed Already debriefed, operation fin- Historical Debrief Clicking on it, the debrief-
ished ing already processed is
shown and the user can
see the data already ana-
lysed.
Rejected
Debriefing The operation is in progress and it’s Resume Debrief Continue where the last
possible to resume it. time the debrief was
stopped.
Rollback Debrief To cancel and delete all
temporary data
The automatic debrief procedure is explained in the table below. The explanation is applicable also to Man-
ual Debrief because the wizard used is the same for both operations.
Table 18: Debriefing steps
Actions Description
Right click on a “Connected” DSN and select
“Automatic Debrief”.
Step one shows a summary of the data regard-

ing the H/C in the debrief process. By clicking on
the forward arrow at the top of the page you

can move on to step two.
On this page you can manually modify some of
the data regarding metrics, take off and landings
and crew.

Classification
UNCLASSIFIED
Table 18: Debriefing steps
Actions Description
To move on to step three you have to click on
the grey ticks of the ‘Metrics’ and ‘Take Off&
Landings, Crew’ areas.
When the grey tick is clicked it becomes green
. After clicking both ticks you can then move
on to step three by clicking on the forward arrow
Click “OK” to confirm the operation and commit
the DSN data.
In the last step, Heliwise shows eventual arising

occurred because of exceedance or failure on
board.
To finish, click on the tick icon placed in the top

area of the page.
The DSN status changes to “PROCESSED”.

Classification
UNCLASSIFIED
Design Description
Figure 128: DSN Status – Page design
The page is divided into two parts – a table and a calendar.

In the top part of the page there is a table containing the following data:
• In the first column you can select which H/C you want to view. Click in the box next to the relevant H/C
and this button will highlight the row selected.
• In the second column you can click on this button to open a table with the downloaded data for that
specific H/C. Always use it to close the table.
• ‘HC Model’; identifies the model of the A/C.
• ‘Serial Code’; the serial code of the selected A/C.
• ‘Tail Id’; shows the id of the H/C.
• ‘Status’; the current status of the selected H/C.
• ‘Pend DSN’; the number of debriefs waiting to be carried out.

Classification
UNCLASSIFIED
• In the fifth column you will see this symbol if the H/C status has not changed because downloads
are pending.
• ‘Total DSN’; the total DSN processed.
• ‘Total Flight Hours; the total flight hours of the selected H/C.
• ‘Last Download Type’; this column shows if the last download was ‘automatic’ or ‘manual’.
• ‘Last DSN Process Time’; the date and time the last DSN was processed.
• ‘Last DSN Start’, the date and time of the start of the last DSN.
• ‘Last DSN End’, the date and time of the end of the last DSN.
If you select an H/C on the table and then click the expand button, a new table opens which shows infor-
mation regarding the DSNs carried out or pending on that specific H/C.
Figure 129: DSN Status – DSN on H/C

• ‘DSN Id’; the DSN Id depends on the DSN status. If the DSN has a status the DSN Id will be
a sequential number exclusive to that specific H/C, for a brand new H/C the DSN Id will start from 1 and
increase after each data debrief. If the DSN status is not ‘processed’ then the DSN Id is a number which
corresponds to the date and time that the files were uploaded (YYYY_MM_DD HH.MM.SS_001) fol-
lowed by a number.
• ‘Download Type’; this column shows if the debrief is ‘AUTOMATIC’ or ‘MANUAL’.
• ‘Download Index’; this column shows a sequential number for the debriefings pending. It will be blank if
the debrief has a ‘processed’ status.
• ‘Download At’; these column shows the time which the debriefing was carried out.
• ‘AMMC 1’; a green circle shows if data was taken from this AMMC, a grey circle shows if it was not.
• ‘AMMC 2’; a green circle shows if data was taken from this AMMC, a grey circle shows if it was not.
• ‘Primary AMMC’; the AMMC from which the data derives.
• ‘DSN Status’, the ‘DSN Status’ can be the following:

Classification
UNCLASSIFIED
• CONNECTED;
• UNCONNECTED;
• REJECTED;
• OVERLAPPED;
• PROCESSED;
• DEBRIEFING;
• CONNECTEDBYUSER.
• ‘DSN Start’; the time the DSN started.
• ‘DSN End’; the time the DSN finished.
In the bottom area of the page, as already described there is a calendar with the aim to indicate in a time
frame bar the DSN.
It is possible to resize either the calendar or the table by dragging the icon highlighted in the image below.
Figure 130: DSN Status – Resize Area
Once an H/C is selected in the grid, you can visualize the situation of past and present debriefs on the calen-
dar. The calendar shows the first row as hours, the second as days, the third as months and fourth as years.
The colour of the selected debrief shown on the calendar depends on its DSN Status. It is possible to move
the calendar using the buttons in the top right corner as shown below.
Figure 131: DSN Status – Calendar buttons
Table 19: Description of Calendar buttons
Button Description
By clicking on this button you can increase the viewing size of the hours, days, months
and years.
By clicking on this button you can decrease the viewing size of the hours, days, months
and years.
By clicking on this ‘rewind’ button the calendar moves to the first recorded debrief.

Classification
UNCLASSIFIED
Table 19: Description of Calendar buttons
Button Description
By clicking on this button the calendar moves slightly to the left of the current position
and therefore to earlier hours/days/months/years.
By clicking on this button the calendar moves slightly to the right of the current position
and therefore to later hours/days/months/years.
By clicking on this ‘forward’ button the calendar moves to the last recorded debrief.

Classification
UNCLASSIFIED
Wizard Design Description
As explained in the “Procedures” section, to proceed with the debriefing process the ground station uses a
wizard.
Figure 132: Data Debrief Wizard – 1st step
The first step is shown in the image above. All three steps of the wizard keep the same design, therefore a
trace of the steps in the top area, an overview of H/C details and a central area which contains data to import
and analyse.
The trace of steps is useful to show the step you are currently in.
Figure 133: Data Debrief Wizard – Overview steps
As shown in the image above, on the right there are four buttons:

Classification
UNCLASSIFIED
• Use this button to cancel the process and rollback all data applied.
• Use this button.
• to move forward to next step.
• Use this button.to move to previous step.

• Use this button to accept HUMS data uploaded and finish the process.
In the second area on the page you can see details regarding the selected H/C.
Figure 134: Data Debrief Wizard – H/C details
In this area you can view the following information:
• ‘Tail ID’; the tail identification number of the selected H/C.

• ‘HC Status’; the current status of the H/C.
• ‘HC Serial’; the serial number assigned to the selected H/C.
• Variant’; the variant of the H/C model selected.
• ‘AMMC Version’; the version of the AMMC from which the data has been taken.
• ‘Running Hours’; the rotor hours of the H/C.
• ‘Flight Hours’; the total flight hours of the H/C.
• ‘Selected DSN’; the provisional name of the DSN selected.
• ‘Last OI End’; the end date and time of the last OI.
• ‘Selected DSN Start’; the date and time of the start of the selected DSN.
• ‘Selected DSN End’; the date and time of the end of the selected DSN.
DSN Flight Type (visible on 2nd e 3rd step); there are three available types:
• Avionic with just the avionic start up. No engine start.

• Ground with just APU data filled and no flight data.
• Flight if the Weight on Wheel detected parameter was at least one.These two areas placed in the top of
the page are always visible meanwhile the central area changes in according to step loaded.
In the first step, the central area displays a “Metrics Summary”.

Classification
UNCLASSIFIED
Figure 135: Data Debrief Wizard – Metrics Summary
Here you can view a table showing information regarding the metrics of the H/C selected, two tables labelled
‘AMMC1’ and ‘AMMC2’ and finally a chart showing information regarding the take-off/landings and DSN
Time. The AMMC highlighted in green is the AMMC from which the data displayed originates.
The default AMMC is AMMC 2, change this by right clicking on the table and selecting ‘Switch AMMC’ from
the menu which opens.
The metrics table shows the following information:
• ‘Metric Name’; the name of the metric in download.

• ‘UoM’; the relevant unit of measure.
• ‘AMMC1’; metric values recorded for AMMC1. If the AMMC is the primary AMMC this column is high-
lighted in green.
• ‘AMMC2’; metric values for data recorded for AMMC2 (selected by default). If the AMMC is the primary
AMMC this column is highlighted in green.
• ‘Difference %’; the difference in percentage for the metrics downloaded on each AMMC of the lower
value, considering the higher value to be 100%. If the difference is greater than 2% the value is high-
lighted in yellow.
• ‘Current Value’; the current value of the relevant metric.

Classification
UNCLASSIFIED
Figure 136: Data Debrief Wizard – Metrics table
You can right click on the data in each row and the menu shown in the table below opens.
Figure 137: Data Debrief Wizard – Switch AMMC
You can change the AMMC from which the displayed data is from by selecting ‘Switch AMMC’ from this
menu, or by double clicking on the relevant data in the table in the AMMC 1 or AMMC 2 column. The default
AMMC is AMMC 2.
In the two tables below the metrics table you can view the following information (the primary AMMC source
is highlighted):
• ‘Take Off’; the take off time, shown in DD_MM_YY HH.MM.SS.
• ‘Landing; the landing time, shown in DD_MM_YY HH.MM.SS.
• ‘Flight Hours’; the time recorded between take off and landing shown in HH.MM.SS.
Figure 138: Data Debrief Wizard – Switch AMMCs

Classification
UNCLASSIFIED
Below the two AMMC tables there is a chart. In this chart you can view the ‘take off/landings’ and ‘DSN Time’
of the selected H/C.
Figure 139: Chart DSN Time
On the right of the chart there is a legend containing colors used in the chart.
The next step of the wizard is labelled as “Metrics”. On this page you can manually modify some of the data
regarding metrics, take off and landings and crew.
Figure 140: Data Debrief Wizard – Metric Step

Classification
UNCLASSIFIED
There are three areas which make up this step:
• “Metrics”;
• “Take Off & Landings”;
• “SUM”.
Figure 141: Data Debrief Wizard – 2nd step
Metrics
Figure 142: Data Debrief Wizard – 2nd step, Metrics
If you open the ‘Metrics’ menu, there is an editable grid. You can modify where the cursor becomes a hand
and then double clicking. In the table there is the following data:
• ‘Metric Name’; a description of the metric;

• ‘Metric Type’; the type of metric;
• ‘UOM’; the unit of measure;
• ‘Cumulative Value’; the total value of the metric;
• ‘AMS Value’; the relative AMS value;
• ‘Current Value’; the current value according to the AMS.

Classification
UNCLASSIFIED
Take Off & landings
Figure 143: Data Debrief Wizard – 2nd step, Take Off and Landings
There is a chart in the top part of the area. In this chart you can view the ‘take off/landings’ and ‘DSN Time’
of the selected H/C.
Figure 144: Data Debrief Wizard – 2nd step, Take Off Chart
Below the shown chart, there is a table containing the flight sessions.
Figure 145: Data Debrief Wizard – 2nd step, DSN sessions
The grid shows the following data:
• ‘DSN Id’, the definitive identification number of the DSN;

• ‘Flight Id’, the identification number of the flight;
• ‘Take-off/Landing Id’, the identification number of the take-off and landing;
• ‘Take-off’, the date and time of take off, shown in DD_MM_YY HH.MM.SS;
• ‘Landing’, the date and time of landing, shown in DD_MM_YY HH.MM.SS;
• ‘Flight Fuel [kg]’, the amount of fuel consumed during the flight;
• ‘Flight Hours’, the time the H/C spent in flight between take-off and landing, shown in HH.MM.SS.

Classification
UNCLASSIFIED
In the table it is possible to modify data double clicking on it or add a new item to the table by clicking in the
row with the text ‘Click here to add new item’.
Above the grid, three buttons are placed:
• The add icon permits to add a new row in the table.
• The cancel icon allows canceling a temporary row or deleting an existing one. The same feature is
also achieved by right click on the row and select “Remove TO/L”.
• The approving icon allows saving a new row in the table.
SUM Data
The third area, placed in the bottom of the page, is named “SUM”.
Here you can view charts related to the relevant Structural Usage Monitoring files. The charts are in view
mode only and cannot be modified.
Figure 146: Data Debrief Wizard – 2nd step, SUM area

Classification
UNCLASSIFIED
In the top of the SUM area, there are two tables showing the ESUM files to upload. The left grid is regarding
the AMMC1 and another one about AMMC2.
The columns contained in each grid are:
• File Number  a progress number which identify uniquely an ESUM file.

• File Name  the name used to register an ESUM file.
• Start Date Time  start time of recording session in which the ESUM file are found.
• End Date Time  end time of recording session.
Below the area dedicated to grids, there is a button named “SUM Files”.
Figure 147: Data Debrief Wizard – 2nd step, SUM button
Clicking on it, it is possible to show a list of SUM files.
Figure 148: Data Debrief Wizard – 2nd step, SUM Files list
Click on one of them to show the relevant chart. Wait few second to permit the correct loading (the time of
loading depends on the complexity and size of option selected).

Classification
UNCLASSIFIED
Figure 149: Data Debrief Wizard – 2nd step, SUM Files Chart
You can choose whether you want to view data from both AMMC1 and AMMC2 or from either one or the
other. On the right of each chart there is a legend with two check boxes.
Figure 150: Data Debrief Wizard – 2nd step, Chart Legend
When the check box is ticked the AMMC is selected. To select or deselect, click in the check box. You
will view data originating from the AMMC(s) selected.
Each chart shows Value and Time of the file selected. It is possible to use the scroll bars to move to the left
and right of the chart or up and down. The name of the open file is shown at the top of the chart on the left.
N.B It is possible to view several charts simultaneously The SUM files list marks the files which are
currently open with a tick .

Classification
UNCLASSIFIED
Figure 151: Data Debrief Wizard – 2nd step, Charts Open

Arising
The last step shows the result of the download in terms of arisings. On this page you can view the arisings
for the selected H/C from the last download.
Figure 152: Data Debrief Wizard – 3rd step, Arising List

Classification
UNCLASSIFIED
The area consists entirely of a table showing the following data:
• ‘Number’, the number associated with the arising; a sequential number.

• ‘Code’, the identification code of the arising.
• ‘Author’, the personnel who created the arising.
• ‘Generated’, the date and time the arising was importing in the ground station.
• ‘Detected’, the date in which the technical event was detected during the recording.
• ‘Description’, a description of the arising.
• ‘LCN’, the relevant LCN.
• ‘ALC’, the relevant ALC.
• ‘Status’, the status of the arising. Possible statuses are the following:
• Pending: The arising has been acknowledged but with no change to the H/C status.
• Accepted: The arising requires maintenance action.
• ‘Remarks’, comments regarding the arising.

Classification
UNCLASSIFIED
1.8.4 Data Debrief (AW139)
The Data Debrief section opens as soon as the DTC download has been successfully completed.
The DSN H/C Status page is also reached after carrying out an automatic debrief from the DSN Status page
on a DSN with a Connected status. Right click on the DSN and a menu opens, on this menu click on the
‘Debrief DSN’ item. The DSN is debriefed and the user is taken to the ‘DSN H/C Status’ page.
Figure 153: DSN Status - Debrief DSN
The DSN H/C Status page displays a list of processed DSNs. The Last Processed DSN list shows the last
five processed DSN.

Classification
UNCLASSIFIED
In the Pending DSN section, the user can process the HUMS Data which has already been uploaded on the
server and those that are pending to be committed.
Figure 154: AW139 - Data debrief
Select a pending DSN and right click on it; a menu opens showing further actions which can be carried out
on the DSN.

Classification
UNCLASSIFIED
Figure 155: AW139 - Data debrief - pending DSNs
It is possible to commit one or more DSNs at the same time by selecting the last DSN and then right clicking
and selecting Commit DSN. The Commit operation will be performed on all the DSNs with a green bullet.
The commit DSN process will start from the oldest DSN to the newest one. While the commit operation is
being carried out a small window displaying the number of the DSN currently being processed is shown.
Figure 156: AW139 - Data Debrief - committing DSN
When committing process has finished, the DSN will be displayed as Processed and will be placed in the
upper list that shows the last five DSN processed for the selected helicopter.

Classification
UNCLASSIFIED
Figure 157: AW139 - Data debrief - Last processed DSN
It is possible for the user to preview the helicopter arisings, including the new ones generated from the most
recent download.

Classification
UNCLASSIFIED
Figure 158: AW139 - Data debrief - arising list
By right clicking on an arising a menu opens allowing the user to open the relevant TVM trends page.
Figure 159: AW139 - Data debrief - arising menu
The TVM trends page opens.

Classification
UNCLASSIFIED
Figure 160: AW139 - Data debrief - TVM trends

Classification
UNCLASSIFIED
1.8.5 DSN Management

In the ‘DSN Management’ page, you can transfer HUMS data from the H/C SSD (Solid State Drive) to the
local operator’s PC via Wi-Fi or Ethernet.
Figure 161: DSN Management
At the top of the page the section ‘DSN Local Repository’ contains the data which has already been down-
loaded from the DTD of the H/C.
The grid consists of the following information:
• HC Model: display the model of AC;

• Tail ID: display the Tail Code of AC contained in the downloaded files;
• Files: number which shows the total number of files;
• Total Size [B]; the size of downloaded folder (shown in byte);
• DSN Type: the type of download (Quick or Full);
• Upload Status: the status of the download folder. “NEW” if it’s still placed in the operator PC and has
never been uploaded from this PC before otherwise the term displayed is “UPLOADED”
• Uploaded: show when the user has uploaded the DSN;

Classification
UNCLASSIFIED
• Start/End Download; the date and time of download from the H/C SSD to operator PC;
• Full; upload data from local PC towards production server;
• Quick; proceed with QA process;
• RTB; use the RTB feature on that download.
By right clicking on a DSN, the system shows a contextual menu.
Figure 162: Remove Local DSN
By clicking on the “Remove Selected Item” option it’s possible to delete the DSN from the grid and erase the
physical files from the local PC.
Once a DSN has been selected in the upper grid and clicking on the flip icon ( ) the central area ‘DSN
Details’ is automatically filled. It is also possible to check DSN details by right-clicking on the required DSN
and selecting ‘View Dsn Detail’ in the context menu.
Figure 163: DSN Details
After clicking on ‘View Dsn Detail’ the files which make up the selected DSN are displayed. The following
information is displayed:
• File Name: shows the name of the file;

• File Size: shows the size of each file (in byte);
• AMMC: shows which is the AMMC involved;
• File Version: shows the version of the file;
• SW Version: shows the software version on board which was used to record;

Classification
UNCLASSIFIED
• Previous MDB Deletion: shows the date and time of previous deletion;
• DTC Allocation: shows the date and time of allocation on the DTD panel;
• CRC: shows if the CRC option is enabled or not.
By default in the central area of the page, the application shows the functionalities to download data from the
DTD via Wi-Fi or Ethernet.
First of all, the user has to connect to the DTD. If the intention is to download data by means of Wi-Fi con-
nection, the PC needs to connect to the DTD network as a common Wi-Fi Access Point. Otherwise, using an
Ethernet connection, you have to plug-in the Ethernet cable into your PC once it has been liaised with the
DTD.
Secondly, ensure the type of connection, IP address, user and password are corrected. As shown in the
image below, you are able to switch from Wi-Fi or Ethernet connection using the toggle switch. After that,
check the IP address with the DTD IP (by default it is 192.168.134.1 already set for the connection).
Leave the user ‘anonymous’ and no password.
Figure 164: Download a DSN via Wi-Fi
Figure 165: Download a DSN via Ethernet
Finally, click on ‘Connect’ and the light indicates if the connection is successful.
Figure 166: Connected to DTD
Once it is connected, click on the ‘Download’ button to start the downloading.

Classification
UNCLASSIFIED
Figure 167: Download Files
On the upper right side there is a progress bar showing the total progress of the operation.
“To Transfer (n)” area contains all files ready to be transferred while the area “Server Messages” reports the
feedback which a normal FTP client shows when connected to a server.
On the left side, the grid reports a log in order to trace the actions performed:
• Moving HC Failures List: moving the “AMSMNTFL….” Files to the mds path on DTD. They are ready to
be downloaded;
• Read HC Repository: checking the user permission to read the DTD content;
• Create Local Repository; creating a local repository on the operator PC;
• Download HC Maint Files; downloading the maintenance and usage files (applicable only on FULL
download);
• Download HC VMauto Files: downloading the TVM files;
• Download HC VMresult Files: downloading the TVM files already processed on board;
• Download HC SUMrecord Files download the Structural Usage Monitoring files (applicable only on FULL
download);
• Reading HC Info in Files: reading the information placed directly in the files of the download folder (appli-
cable only on Quick Access download);
• Verify HC Backup Folder: verifying the presence of ‘mdsbackup’ folder on SSD on board;
• Backup HC DSN Files: moving the files already downloaded to ‘mdsbackup’ DTD path. It creates a
queue consisting of all downloaded folders;
• Closing Download Procedure: shows the result and completion of the process.

Classification
UNCLASSIFIED
At the end of the process, the downloaded data is shown in the ‘DSN Local Repository’ grid as a DSN row.
The last download is placed as the first entry in order to immediately prepare the data to be uploaded to the
online server.
In the SSD on board, the mds folder has only the folders “sumrecord”, “vmauto” and “vmresult” and no data
is placed inside them. The DTD is ready to store other HUMS data.
Figure 168: DSN Management – mds on board
Once the download is complete, the DTD moves the HUMS files from the mds to the mdsbackup folder in
which the user can find on board the last 100 data downloaded.

Classification
UNCLASSIFIED
On Heliwise, inside the ‘DSN Local Repository’ grid, click on the ‘FULL’ button in order to upload the HUMS
data from the local PC to the online server. Depending which button is clicked, the processing will be per-
formed Full or Quick Access.
Figure 170: DSN Management – Process DSN
Once the user has clicked on the button, the system automatically redirects to the ‘Upload DSN Files’ page.
Figure 171: DTC Download – Uploading files

Classification
UNCLASSIFIED
It is not possible to change the path where the download files are selected.From the ‘DSN Management’ dia-
log Heliwise sets the local repository as default path.
Figure 172: DTC Download – SUM files
You can decide whether to upload also the SUM files or not. Since these files are big, their uploading could
impact the time required to complete the downloading process.
Click on the blue arrow to start with the upload process. The description of functionalities is contained in the
next chapter.

Classification
UNCLASSIFIED
1.8.6 PCMCIA Management
After clicking on the ‘PCMCIA Management’ menu item on the ‘Data Management’ menu, a window opens.
This window allows the user to format and prepare the PCMCIA after the data contained on it has been
downloaded. This window also opens after clicking on the ‘Init’ button on the ‘AW139 DTC Overview’ win-
dow from the ‘DTC Download’ page.
Figure 173: PCMCIA Management - Manage DTC
At the top of the window the user selects the folder by clicking on the select folder button.
Figure 174: PCMCIA Management - select folder button
Select the required folder from the pop up ‘Select a Folder’ window and then click on the ‘Select’ button.
When the folder has been selected it is possible to select the ‘DTC Type’ from the drop down menu.

Classification
UNCLASSIFIED
Figure 175: PCMCIA Management - select DTC Type
It is now possible to click on the ‘Initialize’ button and the formatting of the PCMCIA begins. However, if, for
example, a part has been replaced on the helicopter, it is necessary to upload the initial parameters to the
PCMCIA. In this case an extra file will be prepared and added to the list of files on the PCMCIA. To upload
initial parameters click on the arrow next to the ‘Upload Initial Parameters’ text and select the initial parame-
ters to set from the list that opens.
Figure 176: PCMCIA Management - Upload Initial Parameters
Click on the ‘Upload’ button to upload the file. Then click on the ‘Initialize’ button to continue preparing the
PCMCIA.

Classification
UNCLASSIFIED
During PCMCIA preparation the progress can be monitored on the progress bar.
Figure 177: PCMCIA Management - Progress bar
Due to the fact that the formatting process can be time consuming, it is possible to minimize the window in
order to continue using Heliwise. Click on the ‘Minimize’ button to reduce the size of the window. The win-
dow and the format progress will be visible at the top of the application.
Figure 178: PCMCIA Management
While the PCMCIA is being formatted it is not possible to carry out further actions in PCMCIA management.
If a user tries to carry out another action a warning window opens.

Classification
UNCLASSIFIED
Figure 179: PCMCIA Management - DTC is working window
The user can cancel the procedure at any time and a pop up will open reporting the user action.
Figure 180: PCMCIA Management - cancel DTC preparation
When the preparation procedure has completed successfully a window opens informing the user that the
procedure is complete. Click ‘OK’ to close the window.
Figure 181: PCMCIA Management - DTC preparation completed window

Classification
UNCLASSIFIED
1.9 STATUS
Once an aircraft has been selected from the available A/C in the fleet, the user can refer to this module to
find out more information relevant to the status of the helicopter.
Figure 182: Aircraft Status module

Classification
UNCLASSIFIED
1.9.1 Aircraft Arising

This page shows all data regarding the arisings for a selected H/C. The status of each arising can be one of
four available conditions:
• Pending  the system recognizes a threshold exceedance and generates a technical event.
It waits for a response by the user. The status of the H/C remains as before.
• Open  the maintainer checked the problem and accepted the technical event.
• Rejected  the maintainer checked the problem and decided not to apply any technical
events.
• Cleared  the maintainer resolves the technical event before opening it and closes
successfully the action.
N.B The page automatically loads the most recent DSN information. To change its time frame please
refer to the Smart link paragraph.
Figure 183: Aircraft Arising page

Classification
UNCLASSIFIED
The page is divided into three main areas; at the top of the page there are details regarding the H/C
selected.
Figure 184: Arising – H/C details
In this area you can view the following data:
• ‘Tail ID’; an alphanumeric field which exclusively identifies the tail code of selected aircraft.
• ‘HC Serial’; an alphanumeric field which exclusively identifies the serial code of selected aircraft.
• ‘Start DSN’; a sequential number which identifies the selected start DSN.
• ‘End DSN’; a sequential number which identifies the selected end DSN.
• ‘FH Start’; the flight hours recorded at the start of the selected DSN.
• ‘FH End’; the flight hours recorded at the end of the selected DSN.
• ‘Last Dsn End’; the date and time of the end of the last DSN (DD_MM_YYYY HH.MM.SS).
• ‘DSN Start’; the date and time of the start of the selected DSN (DD_MM_YYYY HH.MM.SS).
• ‘DSN End’; the date and time of the end of the selected DSN (DD_MM_YYYY HH.MM.SS).
Below the H/C details there is an area called ‘Aircraft Arising’.
Figure 185: Arising List

Classification
UNCLASSIFIED
In this area there is a table showing data regarding the arising recorded in the DSN(s) selected. In this table
you can view the following data:
• ‘DSN’; the download sequence number selected.

• ‘Number’ the sequential number given to each arising.
• ‘Code’; an identification code associated with an arising-
• ‘Type’; the type of arising, this can be: ‘EXCEED_CODE’, ‘FAULT_CODE’, ‘MANUAL’, ‘VMEXCEED-
ANCE’ or ‘VMMISSINGDATA’.
• ‘Created By’, the user logged on at the time of the relative download.
• ‘Generation Date &Time’; the date and time in which the arising was generated in the ground station.
• ‘Detection Date &Time’; the date and time in which the arising occurred.
• ‘Description’; a description of the arising.
• ‘Remarks’; a note of the arising.
• ‘LCN’; the logistic control number related to the arising.
• ‘ALC’; the alternate logistic control number related to the arising.
• ‘Status’; the status of the arising, this can be ‘Open’, ‘Pending’, ‘Cleared’ or ‘Rejected’.
To interact with the status of an arising placed in the table, just select one of them by clicking on it and then
right clicking.
A contextual menu opens as shown below.
Figure 186: Arising List – Contextual menu

Classification
UNCLASSIFIED
Select the operation to be applied from the contextual menu; the system processes the selected arising and
changes its status to another one. The following table shows how an arising status can be changed.
Table 20: Description of Arising Status
Source Status Target Status

Pending Accepted
Rejected
Open Cleared
Rejected “No action”
N.B. BY ACCEPTING AN ARISING THE STATUS OF THE AIRCRAFT COULD CHANGE TO “UNSERVICEABLE” IT
DEPENDS ON ITS SEVERITY AND IMPACT ON AIRCRAFT SAFETY.
The status of arising are coloured as shown in the images below:
• - Light brown shows a ‘Pending’ status. It expects an action by user.
• - Amber shows an ‘Open’ status with no impact on helicopter status.

actions to be done.
In the bottom area of the page, there is a section named “Aircraft Arising Details”. This area is automatically
populated according to the selected arising in the main grid. The mechanism used to value its fields is based
on the type of the selected arising.

Classification
UNCLASSIFIED
Exceed Code
Selecting an arising with type “Exceed_Code” the “Aircraft Arising Details” changes in order to detail this
type of arising.
Figure 187: Arising Details – Exceed Code
The first area labelled ‘Exceedance’ displays the following information:
• ‘Plant/SubSystem’; the on board system from which the alarm originates.

• ‘Description’ the description of the alarm.
• ‘Type Auth Status’; the relevant status given to the alarm which has been generated; this can be ‘Vali-
dated’, ‘Suspicious’ or ‘Rejected’.
• ‘Active’; the circle shows whether the exceedance is active (red circle) or deactivated (grey circle).
• ‘MCDU Message’; the message which showed on the MCDU.
• ‘On Board Alarm Type’; there are three types of alarm: ‘Warning’, Caution’ or ‘Alert’.
• ‘On Board Alarm’; the message generated by the alarm.
• ‘Detection Date &Time’; the date and time the occurrence was detected.
• ‘Total Occurrences’; a number which shows how many times the occurrence was recorded.
• ‘Cumulative Duration’; the total duration of the active status.
• ‘Longest Duration’; the status which remained active for the longest time.
• ‘Worst Value’; the worst recorded value of the worst recorded values.
Below the ‘Exceedance’ area there is a table showing the following data:
• ‘Number’; the number given to the occurrence.

• ‘Status’; the validity of the occurrence.
• ‘Start Date & Time’; the date and time which the occurrence started.
• ‘End Date & Time’; the date and time which the occurrence finished.
• ‘Worst Value’; the worst value recorded during the occurrence.

Classification
UNCLASSIFIED
Fault Code
If you select ‘Type’ equal to ‘FAULT_CODE’ the ‘Aircraft Arising Details’ area changes. As before, the area is
divided into two parts.
Figure 188: Arising Details – Fault Code
In the first area labelled ‘Fault’ you can view the following details:

• ‘Active’; the circle shows whether the fault is active (red circle) or deactivated (grey circle).
• ‘Event Detection Time & Date’; the time and date the occurrence was detected.
• ‘Total Occurrences’; a number which shows how many times the same arising has occurred.
Below the ‘Fault’ area there is a table showing the following data:


Classification
UNCLASSIFIED
VM Exceedance
If you select ‘Type’ equal to ‘VMEXCEEDANCE’ ‘the ‘Aircraft Arising Details’ area changes in order to detail
this arising type.
Figure 189: Arising Details – VM Exceedance
In the first area labelled ‘VM Exceedance’ there is the following data:
• ‘Acq Id’; the code which identifies the acquisition.

• ‘Acq. Description’; a description of the acquisition.
• ‘N. of detected exceedances’; corresponding to threshold type ‘Trend’.
• ‘Event Detection Date &Time’; the date and time the occurrence was detected.
• ‘Health Index Worst Value’; corresponding to threshold type ‘Steady’.
Below the ‘VM Exceedance’ area there is a table showing the following data:
• ‘Exceeding HI’; the relevant Health Index code in which the exceedance occurred.
• ‘Threshold Type’; the threshold type which can be ‘Steady’ or ‘Trend’.
• ‘Threshold Value’; the relevant threshold value.
• ‘Status’; the validity of the occurrence; a green circle shows if it is valid, a grey circle if it is not.

Classification
UNCLASSIFIED
Missing Data Close Monitoring
If you select ‘Type’ equal to ‘VMMISSINGDATACM’ ‘the ‘Aircraft Arising Details’ area changes in order to
details this arising type.
The area displays the following information:

• ‘Acq Type’; the type of TVM acquisition.
• ‘Close Monitoring Start FH’; it indicates the FH value when the close monitoring was started.
• ‘Close Monitoring Start Date Time’; the date of beginning of close monitoring;
• ‘Close Monitoring Planned End FH’; it indicates the FH value when the close monitoring was finished.
• ‘Close Monitoring Request Originator’; the indication.

Classification
UNCLASSIFIED
1.9.2 Aircraft Faults

On this page the user can view the faults list for the selected DSN.
N.B The page automatically displays the information relevant to the most recent DSN.
Figure 191: Aircraft Faults
The page is split into three main areas; the first one shows details regarding the selected aircraft.
Figure 192: Aircraft Faults – H/C details

Classification
UNCLASSIFIED
• ‘Running Hours’; the operative hours in which the HUMS data was recorded.
The second area placed in the main section of the page, contains a set of tabs describing different types of
faults. The first tab shows a list of arisings raised due to a consequent fault generation.
Arising Tab
Figure 193: Aircraft Faults - Arising tab
The table contains the following details:
• DSN: the DSN in which the arising was recorded.

• Number: the arising identification. By clicking on it, you will be redirect to the relevant fault description
using another tab placed in this table.
• Code: the fault code assigned to that arising.

Classification
UNCLASSIFIED
• Type: the arising type.

• Status: the status of each arising. The information is colored as following:
The ‘Pending’ status requires an action by user.
- The ‘Open’ status means there is an active arising on that fault code.
- Green shows a ‘cleared’ or ‘rejected’ status in which there are no further actions to
be done. ‘Cleared’ means the user has performed the action while the ‘Rejected’ status reports no warning
required. To change the status right click on the arising and a contextual menu opens as shown below.
Figure 194: Aircraft Faults - Arising Management
• Created by: the user code which processed the DSN which generated the arising.
• Generation Date&Time: the date and time of the DSN which generated the arising.
• Detection Date&Time: the date and time in which the arising occurred and was stored on the DTD.
• Description: a description of the arising.
• Remarks: an additional note that can be added by the user during the debriefing phase.
• LCN: the logistic control number related to the arising.
• ALC: the alternate logistic control number related to the arising.
Once an arising has been selected, the page automatically loads the relevant fault details in the grid at the
bottom of the page. The data displayed in the grid varies according to the type of arising selected. The sec-
tion is called ‘Aircraft Arising Details’.
Exceed Code

Classification
UNCLASSIFIED
In case of ‘EXCEED_CODE’ the following details are displayed:
• Plant/SubSystem: the on board system from which the alarm originates.

• Description: description of the failures
• Type Auth Status: the status given to the alarm which has been generated;
• Active: the circle shows whether the exceedance is active (red circle) or deactivated (grey circle).
• MCDU Message: the message shown in the MCDU display.
• On Board Alarm Type: type of alarm displayed on CAS
• On Board Alarm: the message displayed on CAS (if any).
• Detection Date & Time: when the fault was detected during AC activities.
• Total Occurrences: how many occurrences are detected relevant to that exceedance.
• Cumulative Duration; the total duration of the active status.
• Longest Duration; the longest duration of that exceedance.
• Worst Worst Value; the worst value among worst recorded values.
To report the list of the occurrences, the details area contains a table showing:
• Number: the identification number of the occurrence (progressive ID)

• Status: the validity of the occurrence.
• Start Date & Time: when the occurrence was started.
• End Date & Time: when the occurrence was stopped.
• Worst Value: the worst value recorded during the occurrence.
Fault Code
If you select an arising with type equal to FAULT_CODE the following details are shown:
• Plant/SubSystem: the involved on board system.

• Description: description of the alarm.
• Type Auth Status: the relevant status given to the alarm which has been generated
• Active: the circle shows whether the fault is active (red circle) or deactivated (grey circle).
• On Board Alarm Type: there are three types of alarm: ‘Warning’, Caution’ or ‘Alert’.

Classification
UNCLASSIFIED
• On Board Alarm: the message generated by the alarm.

• Event Detection Time & Date: the time and date the occurrence was detected.
• Total Occurrences: how many times the same occurrence occurred.
• Cumulative Duration: the total duration of the active status.
• Longest Duration: the status which remained active for the longest time.
At following more details about each occurrence.
• Number: the identification number of that occurrence (progressive ID).

• Start Date & Time: the date and time which the occurrence started.
• End Date & Time: the date and time which the occurrence finished.
Faults Tab
The second tab on the Aircraft Faults page contains the Faults list recorded during the selected DSN.
Figure 197: Aircraft Faults list
The faults table displays the following columns:
• DSN: the DSN from which the data derives.

Classification
UNCLASSIFIED
• AMMC SW Version: the SW version installed on that aircraft.

• AMMC Id: the AMMC used to record.
• Major Item Code: the relevant code referring to the sub-system from which the failure originates.
• Fault Code: the code which identifies the alarm created.
• Maintenance Name: the corresponding name of the fault in maintenance.
• First Occurrence Start Time: when first occurrence started.
• Last Occurrence End Time: when the last occurrence stopped.
• Total Occurrence: how many times the fault occurred.
• Cumulative duration: the total duration of selected fault.
• Longest Duration: the longest duration recorded for the selected fault.
• Occurrence Active: if the fault is still active a green circle displays otherwise the application shows a grey
circle.
• Arising number: the identification of assigned arising (in case it has been generated). The arising num-
ber is colored according to the arising status (ref to Arising page for more details). By clicking on a spe-
cific arising number you are taken to the ‘Arising’ tab where you can manage its status.
Once selected a row in the grid, the web application automatically loads its details below.
Figure 198: Faults Details
This area is split in three parts; the first one called ‘Occurrence Details’:

• MCDU Message: the message shown into the MCDU component.
• Total Occurrences: counter which indicates how many times that fault was recorded.
• Alarm Type: there are three types of alarm: ‘Warning’, Caution’ or ‘Alert’.
• Alarm: the message generated by the alarm.
The second part consists of a grid containing the following data:
• Number: a progressive number.

• Auth Status: the relevant status given to the alarm which has been generated;
• Occurrence Start Time: the time in which the occurrence started.
• Occurrence Stop Time: the time in which the occurrence stopped.
• Occurrence Duration: the duration of the occurrence.
• Parameter Details: if the occurrence has additional parameters.
The third table contains additional parameters about each single occurrence:

Classification
UNCLASSIFIED
• Parameter Name: name of additional parameter existing in the occurrence.

• UoM: unit of measure applicable to that parameter.
• Value: value of the parameter.
Exceedances Tab
On the third tab the user can find out more information about the recorded exceedances.
Figure 199: Aircraft Faults Exceedances.
This tab shows a list of exceedances registered during the last DSN time period.

Classification
UNCLASSIFIED
Figure 200: Exceedances Summary
The table in this area shows the following data:

• AMMC SW Version: the installed SW version on board.
• Fault Code: it reports the identifier code for a specific fault. The codes starting with 9 identify an exceed-
ance.
• Maintenance Name: description of the exceedance.
• First Occurrence Start Time: time of first occurrence.
• Total Occ.: how many times the exceedance occurred.
• Cumulative duration: the total time of the exceedance recorded.
• Longest Duration: the longest duration of an occurrence.
• Worst Worst Value: the worst value among worst recorded values.
• Occurrence Active: green circle means exceedance is active otherwise a grey circle is displayed.
• Arising number: the arising identifier assigned to that exceedance (if any). The cell can change its color
according to the arising status (pending, accepted or cleared/rejected).Clicking on it, the page redirects
to the first tab in which the arising list is more detailed.
The area at the bottom of the tab displays details regarding the exceedance selected in the main grid.
Figure 201: Exceedance Details
This area is split into three parts; the first one is called ‘Occurrence Details’ and contains the following data:

Classification
UNCLASSIFIED

• MCDU Message: the message shown on the MCDU.
• Total Occurrences: how many times that fault was recorded.
• Alarm: the ob board message generated by the alarm.
The second part consists of a grid showing the following data:

• Auth Status: the relevant status given to the alarm which has been generated.
• Occurrence Start Time: when the occurrence started.
• Occurrence Stop Time: when the occurrence stopped.
• Occurrence Duration: the duration of recorder occurrence.
• Worst Value: the worst value recorded in that time frame.
• Parameter Details: it reports if the occurrence has additional parameters.
• Parameter Name: name of additional parameter linked to that occurrence.

• UoM: unit of measure applicable to parameter.
• Value: value of parameter.

Classification
UNCLASSIFIED
Alarm Tab
The fourth tab contains a list of alarms recorded during the selected DSN.
Figure 202: Aircraft Alarm
The main table shows the following data:

• AMMC SW Version: the SW version installed on-board.
• Maintenance Name: the corresponding maintenance name of that alarm.
• First Occurrence Start Time: when the first occurrence started.
• Total Occ.: how many times the fault occurred.
• Occurrence Active: if the fault is still active a green circle is shown, otherwise the page reports a grey cir-
cle.
• Arising number: a progressive number assigned to each arising. Each arising is colored according to its
status. Clicking on it, the user is redirected to the first tab where more details are shown.

Classification
UNCLASSIFIED
In the bottom part of the page the user can find out more details about the selected alarm.
Figure 203: Alarm Detail
This area is split into two parts; the first one, on the left side, is labelled ‘Alarm Details’:

• Total Occurrences: how many times that alarm was occurred.
• Alarm: the on board message generated by the alarm.
The second part consists of a grid reporting the following information:

• Auth Status: status of the occurrence.

Classification
UNCLASSIFIED
Discrepancy Tab
In the fifth tab the user can find a list of all discrepancies recorded in the selected DSN.
Figure 204: Aircraft Discrepancy
The main grid displays the following details:

• MMC SW Version’; the SW version installed on AMMCs.
• Fault Code: the code identifies the alarm created.
• Maintenance Name: the corresponding maintenance name of that discrepancy.
• Total Occ.: a number which shows how many times the fault occurred.
• Occurrence Active: If the alarm is still active a green circle is shown otherwise a grey circle
• Arising number: the progressive number linked to each arising. It is colored in according to its status and
clicking on it the page redirect to the first tab in which the user can find more details about the arising.

Classification
UNCLASSIFIED
In the bottom part of the page, more details are shown about the selected discrepancy.
Figure 205: Discrepancy Detail

This area is split into two parts. The first one, on the left side, reports a set of fields to describe the discrep-
ancy in detail:
• Plant/SubSystem: on board system from which the alarm originates.

• Total Occurrences: how many occurrences were recorded.
• Alarm Type: there are three types of alarm: Warning’, Caution’ or ‘Alert’.
The second part consists of a grid and contains:

• Auth Status: the status of the generated alarm.
• Occurrence Start Time: when the occurrence was recorded.
• Own Value Boolean: Additional parameters reporting the existence of own value.
• Own Value Real: Additional parameters reporting the value of own parameter.
• Partner AMMC value: Additional parameters reporting the existence of partner value.
• Partner AMMC value: Additional parameters reporting the value of partner parameter.

Classification
UNCLASSIFIED
History Tab
The last tab contains the list of all events which occurred during the selected DSN.
Figure 206: Aircraft Faults History

• AMMC SW Version: the version of SW installed on AMMC.
• Maintenance Name: the corresponding maintenance name of the event.
• First Occurrence Start Time: the recorded time of first occurrence.
• Counter: how many times the event occurred.
• Occurrence Start Time: the start time of selected occurrence.
• Occurrence Stop Time: the end time of selected occurrence.
The details regarding the selected occurrence are shown in the bottom area ‘History Detail’.

Classification
UNCLASSIFIED
Figure 207: History Details
This area is split into two parts; the first one on the left side shows the following data:

• Total Occurrences: how many times that event was recorded.
• Alarm: the alarm message generated by the alarm.
The second part consists of a grid which shows the following data:

• Occurrence Duration: the duration of selected occurrence.
• Occurrence Active: if the occurrence is still active or not.

Classification
UNCLASSIFIED
Extended Grid
In the upper right corner of the grid, the user can extend the grid and therefore display more columns by
means of the dedicated button.
Figure 208: Aircraft Faults - Show Extended Grid
Clicking on the button highlighted in the image above, the user can view the following columns in addition to
those already displayed in the table:

The additional columns are filterable in order to allow complete searching of the information.
To hide this additional information click again on the button.

Classification
UNCLASSIFIED
1.9.3 Basic Usage and Operation Monitoring
Open the ‘Basic Usage and Operation Monitoring’ page by accessing it from the ‘Status’ > ‘Usage’ menu. On
this page it is possible to analyze usage data.
The page automatically loads the data relevant to the last session. Use the SmartLink button placed
in the top right corner of the page to change the period of time to be analysed by selecting a wider
DSN range.
Figure 209: Basic Usage Monitoring - General View
In the top part of the page, the user can view a summary of data set currently loaded.
Figure 210: Basic Usage Monitoring – H/C details

Classification
UNCLASSIFIED
The main part of the page is consists of a set of panels representing different types of usage information:
• Avionic Cycles: the number of start and stop of the avionic system on board.
• Electric Busses Cycles: the number of start and stop of the electric system.
• APU Cycles: the number of start and stop of APU.
• Engine Cycles: the start and stop of engines.
• Rotor Start/Stop Cycles: the number of start and stop of the rotors transmission.
• Rotor Braking Cycles: the number of application done on the rotor brake.
• Take off / Landing Cycles: how many take-off and landing performed in the last session.
• Touchdowns: the number of touchdowns performed during last flight.

Classification
UNCLASSIFIED
Avionic Cycles Tab
The first tab contains information about the avionic system.
Figure 211: BUOM - Avionic Cycles
The central area consists of a grid containing the following information:
• DSN: the number of Download Serial Number.

• AMMC: the AMMC which registered that event.
• Power On Date&Time: when the AMMC was turned on.
• Start Cycle: the role of the AMMC at start up.
• Power off Date&Time: when the AMMC was turned off.
• Stop Cycle: the role of the AMMC when it was turned off.
• Power on time: how many minutes the AMMC was running in that role.
In the bottom part of the page, you can get more information about the total counters. For each AMMC the
user can view:
• Total Power On as Master.

• Total Power On as Stand-by.
• Total Changes from Master to Stand-by.
• Total Changes from Stand-by to Master.
• Total Power Off as Master.
• Total Power Off as Standby.
• Total Power On Cycles.

Classification
UNCLASSIFIED
Electric Buses Cycles
In the second tab, the page shows the cycles recorded for the electric bus system.
Figure 212: BUOM - Electric Buses
This tab consists of a list of buses on the left side:
• Emergency buses;
• Essentials buses;
• Main buses;
• Non Essential buses.
Clicking on one of them, the page will display a green tick icon near the button in order to identify which is
the bus under analysis. On the right side the page displays a grid which loads the information according to
the bus loaded. The table consists of the following set of columns which never change:
• ‘DSN’: the number of DSN currently loaded (the last one by default).
• ‘AMMC’: the AMMC that recorded the cycle.
• ‘Start Date&Time’: start date of cycle.
• ‘Stop Date&Time’: stop date of cycle.
• ‘Running Time’: the amount of time the bus was running.

Classification
UNCLASSIFIED
In the bottom part of the page, the user can get more information about the total number of cycles for each
AMMC and the relevant Running Time.
APU Cycles
This section shows how many times the APU was started and then stopped.
Figure 213: BUOM – APU Cycles
The page contains the following columns:
• ‘DSN’: the number of the DSN in which the event was recorded. (the page loads the last DSN by
default).
• ‘AMMC’: the identifier of AMMC.
• ‘Start Date&Time’: when the AMMC was turned on.
• ‘Stop Date&Time’: when the AMMC was turned off.
• ‘Running Time’: how many minutes the APU was running.
• ‘APU NG at cycle start [%]’: the value of NG at APU start up.
• ‘APU NG at cycle stop [%]’: the value of NG when the APU was turned off.
• ‘Max. APU NG [%]’: the max value of NG registered.
In the bottom part of the page, the application shows a list of total counters representing:
• AMMC 1 Total Start/Stop Cycles.

• AMMC 2 Total Start/Stop Cycles.
• Total Running Time for both AMMC.

Classification
UNCLASSIFIED
Engine Cycles
Click on the ‘Engine Cycles’ tab to analyse the data recorded during each cycle of both engines.
Figure 214: BUOM – Engine Cycles
The page is split into two sections, one per engine. Both areas contain the same data.
The columns in the grids are the following:
• ‘DSN’: the DSN from which the data originates.

• ‘AMMC’: the AMMC which recorded that cycle.
• ‘Start Date&Time’: when the engine was turned on.
• ‘Stop Date&Time’: when the engine was turned off.
• ‘Running Time’: amount of time about the engine running.
• ‘Flight Performed’: column showing if the aircraft has performed a flight during that engine cycle.
In the bottom part of the page, you can get more information about the total number of cycles performed by
each engine recorded by the AMMCs and the relevant total running time.

Classification
UNCLASSIFIED
Rotor Start/Stop Cycles
The fifth tab contains information about the rotor cycles registered by each AMMC.
Figure 215: BUOM – Rotor Cycles
In the main grid, the user can get more information about:
• DSN: the number of DSN in which the information was recorded.

• AMMC: identifier of AMMC.
• Start Date&Time: the start date of rotor registered by the specified AMMC.
• Stop Date&Time: the stop date of rotor registered by the specified AMMC.
• Running Time: the amount of time the rotor was in action.
in the bottom part of the page the user can get more information about the total cycles performed by each
AMMC and relevant running time.

Classification
UNCLASSIFIED
Rotor Braking Cycles
The sixth tab shows more information about the cycles performed by the Rotor Brake during the last ses-
sion.
Figure 216: Rotor Braking Cycles
The main grid display the following data:
• DSN: the number of the DSN in which the data was recorded (last DSN loaded by default).
• AMMC: the AMMC which registered that values.
• Start Date&Time: when the rotor brake has been enabled.
• Stop Date&Time: when the rotor brake has been disabled.
• Rotor Braking Time: amount of minutes in which the rotor brake was applied.
• XMSN NR at Rotor Braking Start [%]: the value of NR [%] when the rotor brake was applied.
In the bottom part of the page Heliwise shows the total cycles performed by each AMMC.

Classification
UNCLASSIFIED
Take Off/Landing Cycles
Click on the ‘Take Off/Landings Cycles’ tab to analyse the data recorded during each TOL cycle.
Figure 217: BUOM – Take Off Landings & Landing Cycles
Into the main grid you can analyse the following data

• ‘AMMC’: identifier of the AMMC that has recorded that cycle.
• ‘Take Off Date&Time’: the date and time of take-off.
• ‘Landing Date&Time’: the date and time of landing.
• ‘Flight Time’: the amount of time the H/C was in flight.
• ‘Fuel at Take Off [kg]’: the amount of fuel aboard the H/C at take-off.
• ‘All Up Weight at Take Off [kg]’: the weight of aircraft at take off.
• ‘Fuel at Landing [kg]’: the amount of fuel aboard at landing.
• ‘All Up Weight at Landing [kg]’: the weight of aircraft at landing.
In the bottom part of the page, additional information is displayed relevant to the total counters. For both
AMMCs Heliwise displays the total number of TOL, total flight time and the maximum all up weight.

Classification
UNCLASSIFIED
Touchdowns
If you click on the ‘Touchdowns’ tab you can get information about the touchdowns performed during the last
session.
Figure 218: BUOM – Touchdowns
The main part of the page contains a grid showing:

• ‘AMMC’: identifier of AMMC which registered that cycles.
• ‘Touchdown Date&Time’: when the touchdown was recorded.
• ‘All Up Weight (kg)’: the weight of the aircraft at touchdown.
• ‘Vertical Speed (Ft/min)’: the vertical speed measured in feet per minute at touchdown.
• ‘True Air Speed (kts)’: the true air speed recorded at touchdown.
• ‘Vertical Speed Peak (Ft/min)’: the highest vertical speed measured in feet per minute at touchdown.
• ‘Vertical Acceleration Peak (g)’; the highest vertical acceleration measured in gravity at touchdown.
In the bottom part Heliwise displays how many touchdown was recorded by each AMMC during last DSN.

Classification
UNCLASSIFIED
1.9.4 Cumulative Torque Spectrum

Clicking on ‘Cumulative Torque Spectrum’ dialog you are taken to the page ‘TUM Cumulative Torque Spec-
trum’. On this page is possible to view all relative cumulative TUM data for the H/C selected. The data can
be viewed in table format or in chart format.
Figure 219: TUM Cumulative Torque Spectrum
The page is divided into two areas; the first area shows data regarding the H/C selected, the second area
‘TUM Torque Band’ is split into two tabs ‘Cumulated Time’ and ‘Percentage’ the tabs show the cumulative
TUM data in table format. The data viewed in this area in table format can be switched to chart format using
the icon in the top right corner of the area.

Classification
UNCLASSIFIED
In the first area of the page there is an area which shows the following data regarding the H/C selected:
• ‘HC Serial; an alphanumeric field which exclusively identifies the serial code of selected aircraft.
• ‘H/C Status’; the current status of the H/C selected.
• ‘Last Dsn End’; the date and time of the end of the last DSN (DD_MM_YYYY HH.MM.SS)

Classification
UNCLASSIFIED
The second and main area ‘TUM Torque Band’ is split into two tabs; the first, ‘Cumulated Time’ and the sec-
ond, ‘Percentage’. By default the page always opens showing the ‘Cumulated Time’ tab.
Figure 221: TUM Torque Band

Classification
UNCLASSIFIED
Cumulated Time Tab
In the ‘Cumulated Time’ tab you can view data regarding the cumulative time spent in every torque.
Figure 222: Cumulated Time
The table is divided into the following columns:
• ‘Engine Input Torque Bands’; the relevant engine torque band from which the cumulative data derives
(36 bands plus unavailable band).
• ‘MGBin1 TPC’; the torque path code name; this column shows the cumulative time spent in the corre-
sponding torque band for the Main Gear Box input engine 1.
• ‘MGBinT TPC’; the torque path code name; this column shows the sum of cumulative time relative to all
three of the previously mentioned TPC (MGBin1, MGBin2) for the corresponding torque band.
• ‘Main Torque Band [lbft]’; the relevant main torque bands from which the cumulative data in ‘MRD TPC’
derives -measured in lbs. and feet (36 bands plus unavailable band).
• ‘MRD TPC’; the torque path code name; this column shows the cumulative time spent in the correspond-
ing main torque band for the Main Rotor Drive.
• ‘Tail torque Band [lbft]’; the relevant tail torque bands from which the cumulative data in ‘TRD TPC’
derives – measured in lbs. and feet (36 bands plus unavailable time band).
• ‘TRD TPC’; the torque path code name; this column shows the cumulative time spent in the correspond-
ing main torque band for the Tail Rotor Drive.

Classification
UNCLASSIFIED
Percentage Tab
In the ‘Percentage’ tab you can view data regarding the cumulative time converted into a percentage spent
in every torque band.
Figure 223: TUM - Percentage
The table is divided into the following columns:
• ‘MGBin1 TPC’; the torque path code name; this column shows the percentage of cumulative time spent
in the corresponding torque band for the Main Gear Box input engine 1.
• ‘MGBinT TPC’; the torque path code name; this column shows the sum of the percentages of cumulative
time relative to all three of the previously mentioned TPC (MGBin1, MGBin2) for the corresponding
torque band.
• ‘MRD TPC’; the torque path code name; this column shows the percentage of cumulative time spent in
the corresponding main torque band for the Main Rotor Drive.
• ‘TRD TPC’; the torque path code name; this column shows the percentage of cumulative time spent in
the corresponding main torque band for the Tail Rotor Drive.

Classification
UNCLASSIFIED
Cumulative Torque Spectrum Charts
All of this data can be viewed in chart form by clicking on the button in the top right corner of the ‘TUM
Torque Band’ area or right clicking on any area of the tables and selecting ‘Flip to Chart’ from the menu
which opens.
Figure 224: Flip to Chart
By default the chart which opens is set to ‘Time’. After clicking the ‘Flip to Chart’ button the area switches to
a chart; the default for the initial viewing of the chart area is set to ‘MRD TPC’ viewed in ‘Linear’ mode with
the Y Axis displaying ‘Time’.
Figure 225: Torque Spectra Chart

Classification
UNCLASSIFIED
To view other data from the previous ‘TUM Torque Band’ area in chart form, click on the ‘Torque Spectra
Chart’ button at the top of the chart area.
Figure 226: Torque Spectra Chart button
When you click on this button a menu opens and you can select which cumulative torque data you would like
to view.
Figure 227: Torque Spectra Chart menu
The chart currently open is marked with a . To open one or more charts click on the relevant name on the
menu. Is also possible to view two or more charts simultaneously.

Classification
UNCLASSIFIED
Figure 228: Torque Spectra Multiple Charts
Each chart has scroll bars to enable complete viewing of an individual chart. There is also a scroll bar on the
right of the area which enables you to scroll through all the open charts.

Classification
UNCLASSIFIED
1.9.5 DSN Torque Spectra

On this page is possible to view all relative TUM data for the H/C selected and the DSN range selected. The
data can be viewed in table format or in chart format.
N.B The page automatically loads data regarding the last DSN. If you would like to change DSN
range use the SmartLink button.
Figure 229: TUM DSN Torque Spectra
The page is divided into two areas; the first area shows data regarding the H/C selected, the second,
labelled ‘TUM Torque Band’ is split into two tabs ‘Time’ and ‘Percentage’.
The data viewed in this area in table format can be switched to chart format using the icon in the top
right corner of the area. Only one DSN can be visualised at a time.
In the first area of the page there is an area which shows the following data regarding the H/C selected:

Classification
UNCLASSIFIED

The second and main area ‘TUM Torque Band’ is split into two tabs; the first, ‘Time’ and the second, ‘Per-
centage’. By default the page always opens showing the ‘Time’ tab.
Figure 231: TUM Torque Band

Classification
UNCLASSIFIED
Cumulated Time Tab
This tab shows cumulated data for the DSN selected.
Figure 232: TUM Torque Band Time
The table in this area is divided into the following columns:
• ‘MGBinT TPC’; the torque path code name; this column shows the sum of cumulative time relative to all
three of the previously mentioned TPC (MGBin1, MGBin2) for the corresponding torque band.
• ‘MRD TPC’; the torque path code name; this column shows the cumulative time spent in the correspond-
• ‘TRD TPC’; the torque path code name; this column shows the cumulative time spent in the correspond-

Classification
UNCLASSIFIED
Percentage Tab
In the ‘Percentage’ tab table you can view data regarding the cumulative time converted into a percentage
spent in every torque band for the selected DSN.
Figure 233: TUM Torque Band Percentage
• ‘MGBinT TPC’; the torque path code name; this column shows the sum of the percentages of cumulative
time relative to all three of the previously mentioned TPC (MGBin1, MGBin2) for the corresponding
torque band.
• ‘MRD TPC’; the torque path code name; this column shows the percentage of cumulative time spent in
the corresponding main torque band for the Main Rotor Drive.
• ‘TRD TPC’; the torque path code name; this column shows the percentage of cumulative time spent in
the corresponding main torque band for the Tail Rotor Drive.

Classification
UNCLASSIFIED
DSN Torque Spectra Charts
From the ‘TUM DSN Torque Spectra’ page you can view the data in the ‘TUM Torque Band’ area in chart
form by clicking the button or right clicking on any area of the tables and selecting ‘Flip to Chart’ from the
menu which opens.
Figure 234: TUM Torque Band – Flip to Chart
After clicking the ‘Flip to Chart’ button the area switches to a chart; the default for the initial viewing of the
chart area is set to ‘MRD TPC’ viewed in ‘Linear’ mode with the Y Axis displaying ‘Time’.
Figure 235: DSN Torque Spectra Chart

Classification
UNCLASSIFIED
To view other data from the previous ‘TUM Torque Band’ area in chart form, click on the ‘Torque Spectra
Figure 236: DSN Torque Spectra Chart button
When you click on this button a menu opens and you can select which cumulative torque data you would like
to view.
Figure 237: DSN Torque Spectra Chart menu
The chart currently open is marked with a .

To open one or more charts click on the relevant name on the menu. Is also possible to view two or more
charts simultaneously.

Classification
UNCLASSIFIED
Figure 238: DSN Torque Spectra Multiple Charts
On the right side of each chart, there is a legend which allows changing the view mode.
Figure 239: DSN Torque Spectra Chart Legenda

Classification
UNCLASSIFIED
1.9.6 TUM Tail Torque Timers

After clicking on the ‘Tail Torque Timers’ link on the ‘Status > Transmission Usage Monitoring’ menu you are
taken to the page ‘TUM Tail Torque Timer’. On this page it is possible to view all relative tail torque timer val-
ues for the H/C selected and the DSN range selected. The data can be viewed in table format or in chart for-
mat. To access this page you must first select an H/C from the ‘Fleet Home’ page. By default the page loads
data regarding the last DSN for the selected H/C. If you would like to change the DSN range, click on the
SmartLink button in the top right corner of the page.
Figure 240: TUM Tail Torque Timers
At the top of the page there is an area which displays the following details regarding the H/C selected:
• ‘H/C Serial’; the H/C serial number.
• ‘AMMC Ver’; the AMMC software version.
• ‘Running Hours’; the operational hours of the rotor.

Classification
UNCLASSIFIED
• ‘Last DSN End’; the date and time of the end of the last available DSN (DD_MM_YYYY HH.MM.SS)
• ‘DSN Start’; the date and time of the start of the last available DSN (DD_MM_YYYY HH.MM.SS).
• ‘DSN End’; the date and time of the end of the last available DSN (DD_MM_YYYY HH.MM.SS).
Figure 241: TUM Tail Torque Timers - H/C details
In the second and main area labeled ‘TUM Tail Torque Timer’ there is a grid showing the following data
:
• ‘DSN’; the DSN from which the data derives.
• ‘Total Tail Torque 3 MIN Time’; the total time spent in the 3 minute band for the selected DSN.
• ‘Total Tail Torque 95 MIN Time’; the total time spent in the 95 min band for the selected DSN.
• ‘DSN A/C Flight Hours’; the flight hours recorded for the selected DSN.
• ‘Rotor Starts’; the number of rotor starts recorded for the selected DSN.
Figure 242: TUM Tail Torque Timers - grid
View the data in the row selected in chart form by clicking ‘Flip to Chart’ in the contextual menu which opens
after right clicking on a row in the grid. Alternatively, click on the icon in the top right corner of the ‘TUM Tail
Torque Timer’ area to view the chart for the row selected.
Figure 243: TUM Tail Torque Timers - Flip to chart/grid icon
By default the chart opens showing both the 3 MIN and the 95 MIN Tail Torque Timers. The data is dis-
played as a histogram showing one column for each Tail Torque Timer. By default the histogram is dis-
played using a linear vertical scale with the X-axis displaying DSN A/C Flight Hours.

Classification
UNCLASSIFIED
Figure 244: TUM Tail Torque Timers - Chart
The legend on the right of the chart shows the colour codes of the data you are viewing and enables you to
select which data to view by flagging or unflagging the check boxes.
Figure 245: TUM Tail Torque Timers - Legend
Use the ‘Flip to grid’ icon at the top of the chart to return to the grid view.

Classification
UNCLASSIFIED
1.9.7 Structural Usage Monitoring Operations

In the ‘SUM Summary Data’ module you can access and view SUM data regarding a selected H/C. this page
is accessed by clicking in the ‘Status’ menu > ‘Structural Usage Monitoring’ > ‘SUM Operations’.
N.B THE PAGE AUTOMATICALLY LOADS DATA REGARDING THE LAST DATA DEBRIEF. IF YOU WOULD LIKE TO
CHANGE DSN RANGE USE THE S MARTLINK BUTTON.
Figure 246: Sum Main
At the top of the page you can see details regarding the selected H/C:

Classification
UNCLASSIFIED
Between the details and main area, there is section named ‘SUM Files’.
Figure 248: SUM Files area
As shown in the image above, the title is placed next to a button containing an arrow. Click on it to expand
the hidden area.
Figure 249: SUM Files grids

Classification
UNCLASSIFIED
Figure 250: SUM Details
This section contains two grids showing the SUM files placed in the specified DSN. Each grid is filled with
values coming from a single AMMC.
The columns shown are:
• ‘File Number’; a progressive number to identify each single file.

• ‘File Name’; the recorded file name.
• ‘Start Date Time’; the start time in which the SUM file was recorded.
• ‘End Date Time’; the time in which the SUM file was stopped.
Below the ‘SUM files’ section there is the ‘SUM Details’ section. This area contains information about flight
takeoff/landings.The columns shown are:
• ‘Flight Id’; the identification number of the flight.

• ‘Takeoff/Landing Id’; the identification number of the takeoff and landing.
• ‘Takeoff’; the date and time of takeoff, shown DD_MM_YY HH.MM.SS
• ‘Landing’; the date and time of landing, shown DD_MM_YY HH.MM.SS
• ‘Flight Fuel [kg]’; the amount of fuel consumed during the flight.
• ‘Flight Hours’; the time the H/C spent in flight between takeoff and landing, shown DD_MM_YY
HH.MM.SS
The main area of the page is composed by a blank area; it is filled in according to the selected parameter. As
shown in the image below, in the top left corner of this area there is a button labelled “SUM Files”.
Figure 251: SUM Files button
If you move the cursor over this button it becomes orange and a list of the Structural Usage Monitoring files
opens.

Classification
UNCLASSIFIED
Figure 252: SUM Files list
When the file has loaded you can view the corresponding chart.

Classification
UNCLASSIFIED
Figure 253: SUM File Chart
You can choose whether you want to view data from both AMMC1 and AMMC2 or from either one or the
other. On top of the area there is a legend with two check boxes. The legend can be hidden by clicking on
the button in the top left corner of the chart (red arrow).To show the legend click on the same button (now
with a green arrow).
Figure 254: SUM File Chart Legend

Classification
UNCLASSIFIED
Each chart shows Value and Time of the file selected. It is possible to use the scroll bars to move to the left
and right of the chart or up and down.
It is possible to view several charts simultaneously; the ESUM files list marks the files which are currently
open with a tick.
Figure 255: SUM Files Multiple Charts
It is possible to view a chart as a table by right clicking on the chart and selecting ‘Flip to Grid’ from the menu
which opens.

Classification
UNCLASSIFIED
Figure 256: SUM Files Chart to Table
The chart becomes a table and the information from the chart is displayed in six columns:
• ‘DSN’; the DSN Number.

• ‘Series Name’; the AMMC used to record the information.
• ‘File Name’, the ESUM file name.
• ‘Index Num.’, the index of values shown.
• ‘Date Time’, the date and time shown on the chart, recorded as DD_MM_YY HH.MM.SS.
• ‘Value’, the value shown on the chart.
Figure 257: SUM Files Table

Classification
UNCLASSIFIED
1.10 HEALTH
Once an aircraft has been selected from the available ones in the fleet, the user can refer to this module to
find out more information relevant to the health of the helicopter.
Figure 258: Aircraft health module

Classification
UNCLASSIFIED
1.11 TRANSMISSION VIBRATION MONITORING
In a very simplified scenario, the TVM data assessment can result in one of the situations listed in the follow-
ing table.
Assessment result Consequent action
The HI trend assessment indicates a potential Specific inspections are requested in order to
degradation of the monitored component investigate.
Arising could be left in Accepted status until
investigations conclusion.
At the present stage, the HI trend is not suffi- Leave the threshold values as they are.
cient to clearly discriminate between a false Clear the arising.
alert or a potential degradation. Start a Close Monitoring phase.
The exceedance is caused by excessive scat- Close the arising.

tering or by inappropriate threshold setting; no Threshold adjustment for the specific H/C can
negative trend is present. be considered, after evaluating the current
Steady threshold status if applicable.
The exceedance is caused by isolated spikes, Close the arising.

the normal behavior of the HI is consistently Leave the threshold values as they are.
below the thresholds

Classification
UNCLASSIFIED
1.11.1 TVM Exceedances
On this page you can view data regarding the TVM exceedances recorded in the DSNs selected. To access
this page click on ‘Health’ > ‘Transmission’ > ‘TVM Exceedances’.
N.B THE PAGE AUTOMATICALLY LOADS DATA REGARDING THE LAST DATA DEBRIEF. USE THE SMARTLINK TO
EXPAND OR CHANGE THE DSN TO BE LOADED.
Figure 259: TVM Exceedances
The page is divided into three areas; in the first one there is an area which shows the following data regard-
ing the H/C selected:

Classification
UNCLASSIFIED
The second area indicates information about the selected acquisition in grid. Therefore the content of this
area dynamically changes according to the selected TVM Acquisition.
Figure 261: TVM Exceedance – Location Details
In the top right corner of the area, there is a field named “arising generation” indicating the number of
required consecutive exceedances to generate an automatic arising.
The right side of this area consists of a section labelled “Location Details”. It is populated automatically once
the user selects a row in the main grid. This area gives information regarding the logistic details relevant to
the transmission component monitored by the selected exceeding Acq.ID. In this area you can view the fol-
lowing data:
• ‘Acq. ID’.
• ‘Acq. Type’.
• ‘Part Serial’; the associate serial number.
• ‘Part Code’; the associated part number.
• ‘LCN’; the associated Logistic Control Number.
• ‘ALC’; the associated Alternate Logistic Control Number.
• ‘Description’; a description of the LCN.

Classification
UNCLASSIFIED
Figure 262: TVM Exceedance – Main Grid
In the third area labelled ‘TVM Exceedances’ there is a table containing the following data:

• ‘Acq. ID’; the identification number of the acquisition.
• ‘Acq. Description’; a description of the relevant acquisition.
• ‘Acq. Type; the type of relevant acquisition.
• ‘CM Status; the status of close monitoring.
• ‘Threshold Value’; the threshold value of the relevant acquisition (Trend or Steady).
• ‘Highest Health Index Value’; the highest Health Index value recorded for the acquisition.
• ‘Lowest Health Index Value’; the lowest Health Index value recorded for the acquisition.
• ‘Exceeding Health Index’; the corresponding Health Index exceeded.
• ‘Threshold Status; the corresponding status of threshold. It can be filled with ‘Permanent’ or ‘Temporary’
for Steady Thresholds and ‘Learned’ relative to ‘Trend’ values.
• ‘Threshold Type’; the corresponding threshold type. It can be valued with Steady Red, Steady Amber,
Steady Blue, Far Trend and Close Trend.
• ‘Number of Red Threshold Exceedances’; Number of steady red exceedance.
• ‘Number of Amber Threshold Exceedances’; Number of steady amber exceedance.
• ‘Number of Blue Threshold Exceedances’; Number of steady blue exceedance.
• ‘Downloaded Valid Acquisitions’; Number of valid acquisition for that row.
• ‘Arising Number’; the arising linked to that exceedance.
• ‘Arising Status’; the status of the arising if generated.
By right clicking on the grid, it is possible to select the functionalities placed in the contextual menu.

Classification
UNCLASSIFIED
Figure 263: TVM Exceedances – Acquisition Thresholds
The ‘Show Threshold’ menu item allows the user to get the specific threshold values of a selected acquisi-
tion.
Figure 264: TVM Exceedances – Acquisition Thresholds
The grid shows a list of Health Indexes applicable to that acquisition and each row consists of a HI Code and
a brief description.

Classification
UNCLASSIFIED
Figure 265: TVM Exceedances – thresholds of Steady HI
Each HI owns two tabs in which the user can visualize the thresholds of steady and trend.
The grid shown by default regards the thresholds values of HI steady plots and it is composed by following
data:
• Type: the type of steady threshold.

• Value: the current value of TH.
indicating that the phase of auto-learning is terminated.
• Temp Value: in case of the status is not LRN yet, the TH inherits the temporary value from TH fleet.
• Start Date Time: from which the TH has begun to acquire the custom value.
• Start FH: the FH from which the TH has begun to acquire the custom value.
• Start Initiator: who started the learning of TH.
• Update Date Time: when the user has forced the re-learning.
• Update FH: the FH value when the user has forced the re-learning.

Classification
UNCLASSIFIED
Figure 266: TVM Exceedances – thresholds of Trend HI
While the Trend tab contained another grid which is composed by following information:
• Type: Close Trend or Far Trend.

• Value: the maximum distance allowed from the baseline.
• Base Value: the value auto-learned used as baseline.
• Base Reset Date Time: when the baseline was reset the last time.
• Base Reset FH: the FH reference when the baseline was reset the last time.
• Base Initiator: who reset the baseline the last time.
Another option placed in the contextual menu allows direct analysis of the exceeded Health Index (refer to
exceedances management paragraph in the ‘Health Index & dB Results chapter’).

Classification
UNCLASSIFIED
1.11.2 Aircraft TVM Trends

On this page it’s possible to analyse the health indexes data in terms of steady and trend plots.
The user can access to this dialog by means of the item in the main menu or synoptic chart and finally by
right clicking on the arising in the home page.
Figure 267: HI and dB page

The input and fundamental information is the TVM component to be analysed. You can select it through the
combo box placed in the upper-central part.
Figure 268: HI and dB page – Acq. List

Classification
UNCLASSIFIED
The TVM components are identified by the acquisition Id, Type, Description and Accelerometer, moving on
the right the user can see the presence and quantity of arising in according to their exceedance. The first
square shows the Accepted arising meanwhile the second one represents the Pending arising.
Clicking on one of them, Heliwise automatically plots the health index in which there is an arising generated
by an exceedance.
The left side of the area is composed by the list of Health Indexes applicable to the selected TVM compo-
nent. Ticking them, the user can decide which HI plotting in the central area.
As visible in the image above, the web site automatically ticks the HI where there is an arising.
The letter “S” and “T” shows where the exceedance was occurred and the relative colour displays the type of
exceedance (red, amber or blue). Finally, at the end of row, a counter shows how many arising are still
active on that Health Index.
Figure 269: HI and dB page – HI list
The user can hide this list, by clicking on the button placed in upper-left corner (red arrow).
Figure 270: HI and dB page – Close HI List
To show the list, click again on the same button (meanwhile the arrow has become green).

Classification
UNCLASSIFIED
Figure 271: HI and dB page – Open HI List
To select all HI check boxes with just one click, click on the second button with a green arrow (in the upper
right corner of the page).
Figure 272: HI and dB page – Select All HI
To remove the selection to all Health indexes in one click, use the same button as before. In this case the
arrow is red.
Figure 273: HI and dB page – Remove All HI

Classification
UNCLASSIFIED
Flight Condition Filter
The steady HI charts plotted in the central area of the page, can display the acquisitions in according to the
Flight Conditions in which was the aircraft when tracked the information.
You can set them using the funnel icon, placed always in the toolbar above the charts.
Figure 274: HI and dB page – Flight Filter Conditions
By clicking on it, the web site open a pop-up dedicated to filter the flight parameters. Here you can set which
band to be plotted for every Flight Condition.
Figure 275: HI and dB page – Filter conditions disabled

Classification
UNCLASSIFIED
First of all, the user can set if consider or not the flight condition in the plotting of HI values by mean of the
“Filter Switch” placed in the top-right corner. Enabling it, all the checkboxes becomes editable.
Figure 276: HI and dB page – Filter conditions enabled
To support the user in a more user-friendly selection, the web site allows to deselect with one click all check-
boxes. Other side, clicking on “Select All” the pop-up automatically tick all checkboxes.
The page reports the flight conditions using a table with following columns:
FC description; Flight Condition text.

Unit; the Unit of Measure used for displayed the near boundary values.
Low Boundary; the minimum value allowable.
Low Limit; the high boundary of low aircraft band for that Flight Condition.
High Limit; the high boundary of medium aircraft band for that Flight Condition.
High Boundary; the maximum value allowable.
Low
FC Band; checkbox to be ticked if consider the band from “Low Boundary” to “Low Limit”.
Mid
FC Band; checkbox to be ticked if consider the band from “Low Limit” to “High Limit”.
High FC Band; checkbox to be ticked if consider the band from “High Limit” to “High boundary”.
Once set the Flight Condition filters, you have to click on tick green icon placed in the top-right corner of the
pop-up.

Classification
UNCLASSIFIED
Figure 277: HI and dB page – FC plotting
The steady HI charts show with a blue colour the acquisition which satisfies the FC filters, by other side the
grey points regarding the acquisition tracked with other FC actually not displayed as filtered.
Plot capabilities
Each chart has a button placed in the upper part of the view, in which the user can set the legend of acquisi-
tions to be plotted.
Figure 278: HI and dB page – Steady HI charts
By default the HI Steady plots show the following data:


Classification
UNCLASSIFIED
• Blue, Amber and Red Steady Threshold - moving over the TH line, the chart shows the type of TH (tem-
porary, learned or permanent);
• Vertical line to indicate where the thresholds was reset (Permanent thresholds not included) due to parts
removal or manual reset;
Figure 279: HI and dB page – HI Steady Charts

Classification
UNCLASSIFIED
Instead, the HI dB Deviations charts display the following information:

• Close and Far Trend Distance allowable. if exceeded the web site generates an arising;
• DSN markers represented with vertical lines indicating the start of DSN;
• Vertical line to indicate when the baseline and far trend thresholds was reset due to parts removal or
manual reset;
Figure 280: HI and dB page – HI dB Deviations
In both views, every point has the tooltip automatically visible by default. Moving over one of them, the web
site shows the main information. In detail, the following information is displayed:
• Acq. Date&Time to get out when the acquisition was tracked;
• A/C Flight Hours to indicate the total number of Flight Hours recorded by the current DSN
• The Value of health index;
Figure 281: HI and dB page – tooltip

Classification
UNCLASSIFIED
By right clicking everywhere on the steady plots, you can select the option ‘Show Extended Tooltip’. As
result the tooltip will be composed by additional information such as IAS, Engine 1 Torque, Engine 2 Torque,
Main Rotor Torque, Tail Rotor Torque, Pitch and Roll degrees.
Figure 282: HI and dB page – Extended Tooltip
By clicking on an acquisition of Steady HI chart, Heliwise shows the same acquisition in the others HI plots
open. The selected acquisition is identifiable by a green circle around it.
Figure 283: HI and dB page – Acq. Selection
To zoom select an area of plot by drag and drop the mouse pointer, instead to reset the zoom view click
twice on chart.

Classification
UNCLASSIFIED
Figure 284: HI and dB page – Zoom an area
Otherwise, you can zoom the view by using the scroll wheel of mouse.
Figure 285: HI and dB page – Contextual menu
By right clicking on whatever point of the plot, the web site displays a contextual menu in which it’s possible
to change the values of axes:
• Axis X; possibility to switch the value of abscissa from Acq. FH in Acq. date time and vice versa.
• Axis Y; possibility to switch the parameters of axis from linear to logarithmic and vice versa.
And:
Close; close the HI plot.

Classification
UNCLASSIFIED
User Notes
To add a user note in the plot, you should click on the third icon placed in the top right corner of the page.
Figure 286: HI and dB page – Add User Note

Classification
UNCLASSIFIED
Once enabled the creation of notes, the user has to decide where place its annotation (as shown below).
Figure 287: HI and dB page – Place Note

Classification
UNCLASSIFIED
Once clicked where there will be the user notes, the following popup opens.
Figure 288: HI and dB page – Note Management
Here the user can add a new note and it will be shown as part of a chat indicating who has written and when.
Figure 289: HI and dB page – Chat

Classification
UNCLASSIFIED
The communication will be applied to all Health Indexes of that acquisition on which the user is adding a
note.
Figure 290: HI and dB page – Note Icon
Finally, the user will see a letter icon where the user has created a new communication channel and moving
the mouse pointer over that, Heliwise shows the last message by default.
Close Monitoring
The Close Monitoring functionalities are managed through the button placed in the upper part of the plots
area.
Figure 291: HI and dB page – Close Monitoring window
The user can open a CM phase clicking on the tick green icon placed on the left side. It’s placed also a
remark field in which the user can type more information relevant to this CM.

Classification
UNCLASSIFIED
Figure 292: HI and dB page – CM settings
Once opened, the user can close the CM whenever he wants just clicking on the Red Cross icon.
Figure 293: HI and dB page – Close CM

Classification
UNCLASSIFIED
Contextual Menu
By right clicking on whatever point of the plot, the web site displays the following contextual menu:
Figure 294: HI and dB page – Contextual menu
• Zoom; allow to reset the zoom and focus on all acquisitions.

• Chart Settings.
Figure 295: HI and dB page – Chart Settings
Possibility to hide the automatic tooltip or the background coordinates and change the manner in which the

Classification
UNCLASSIFIED
• XY Plot;
Figure 296: HI and dB page – Chart with Plot

• Step Area;
Figure 297: HI and dB page – Chart with Step Area

Classification
UNCLASSIFIED
• Bar;
Figure 298: HI and dB page – Chart with Bar

• Line;
Figure 299: HI and dB page – Chart with Line

• Line Symbols;
Figure 300: HI and dB page – Chart with Line Symbols

Classification
UNCLASSIFIED
• Export; export in PNG or BMP of HI plot.

• Reporting; add of chart in the dynamic report available in Heliwise (as explained in the “Common Func-
tionalities” paragraph at the beginning of user manual chapter).
• Axis X; possibility to switch the value of abscissa from Acq. FH in Acq. Date time and vice versa.
• Show/Hide Extended Tooltip; view or not the additional parameters in the Tooltip as described above.
• Show/Hide Thresholds; choose to view or not the thresholds the thresholds.
• Show/Hide DSN Markers; possibility to hide the indicators of start DSN.
• Open Acquisition Thresholds; it allows to get specific thresholds values of the selected acquisition
• Close; close the HI plot.
• Flip to Grid; report the values in a tabular format. Possibility to export in CSV the HI values and relative
parameters.
Figure 301: HI and dB page – Table view

Classification
UNCLASSIFIED
By right clicking on it, you can open again the contextual menu even if a couple of option are different
respecting the previous one.
Figure 302: HI and dB page – Contextual menu in table
The ‘Open Acquisition Thresholds’ allows to get the specific value about the thresholds of selected acquisi-
tion.

Classification
UNCLASSIFIED
Figure 303: HI and dB page – Acquisition Thresholds
The upper part is composed by information about the helicopter.This section displays the following details:
• Last DSN End’; the date and time of the end of the last DSN (DD_MM_YYYY HH.MM.SS
Figure 304: HI and dB page - Thresholds page
The grid shows a list of Health Index applicable on that acquisition and each row is composed by HI Code
and a brief description.

Classification
UNCLASSIFIED
Figure 305: HI and dB page – thresholds of Steady HI
Each HI owns two tabs in which the user can visualize the thresholds of steady and trend.
The grid shown by default regards the thresholds values of HI steady plots and it is composed by following
data:
• Type: the type of steady threshold.

• Value: the current value of TH.
indicating that the phase of auto-learning is terminated.
• Temp Value: in case of the status is not LRN yet, the TH inherits the temporary value from TH fleet.
• Start Date Time: from which the TH has begun to acquire the custom value.
• Start FH: the FH from which the TH has begun to acquire the custom value.
• Start Initiator: who started the learning of TH.
• Update Date Time: when the user has forced the re-learning.
• Update FH: the FH value when the user has forced the re-learning.

Classification
UNCLASSIFIED
Figure 306: HI and dB page – thresholds of Trend HI
While the Trend tab contained another grid which is composed by following information:
• Type: Close Trend or Far Trend.

• Value: the maximum distance allowed from the baseline.
• Base Value: the value auto-learned used as baseline.
• Base Reset Date Time: when the baseline was reset the last time.
• Base Reset FH: the FH reference when the baseline was reset the last time.
• Base Initiator: who reset the baseline the last time.

Classification
UNCLASSIFIED
Arising Management
Below the list of TVM components, Heliwise displays the arisings still active on that selected acquisition.
Figure 307: HI and dB page – Arising list
The arising grid is composed by the following columns:
• DSN; indicating the download Id in order to get out when the arising occurred;
• Description; containing the arising description.
• Reason; the type of exceedance which generated the arising. It can be: Far Trend, Close Trend, Steady
Red, Steady Amber, Steady Blue.
• Update Time; the date and time of last update.
• Update User Code; who has performed the last update.
• Number; the id of arising.
• Status; the status of arising. Since this grid shows only the still active arising, this value can be
“Accepted” or “Pending”.
• Remarks; eventual note typed by user during data download processing.
Once performed the analysis the user can clear the arising by right clicking on the arising and select “Clear”
or “Reject” (depends on previous status of arising).
Figure 308: HI and dB page – Clearance Arising
While this grid displays the arising for a single TVM component, you can see all arising for that helicopter
referring to the area expandable in the bottom-left corner of the page.

Classification
UNCLASSIFIED
Figure 309: HI and dB page – AC Arising hidden
By clicking on the arrow, the area expands. Click again to hide it.
Figure 310: HI and dB page – AC Arising visible
By right clicking on a single arising a contextual menu opens.
Figure 311: HI and dB page – AC Arising visible
As shown in the image above, the only action to be performed is to analyze the arising. Once clicked on it,
Heliwise reloads the page with the acquisition which generated the arising to be analyzed.

Classification
UNCLASSIFIED
Exceedances Management
It is possible to access the Aircraft TVM Trends page from the TVM exceedance page (by means of the con-
textual menu) the page is automatically opened in order to allow analysis of a single exceedance without the
concept of arisings.
By default the page shows the HI exceeded selected on the TVM exceedance page. Furthermore, in the HI
list, the exceedance has a blue square.
Figure 312: HI and dB page – Exceedances plots
To analyse another occurrences, the user can expand the area hidden in the bottom part of the page.
Here the grid shown is the same as the one in the TVM Exceedance page and by means of the contextual
menu the user can click on ‘analyse’. As a result the page re-loads the data changing the TVM Acquisition
and relative HI exceeded.
Figure 313: HI and dB page – Exceedances list
Using the flip icon placed in the bottom right corner of the page, you can return to analyse the arising.

Classification
UNCLASSIFIED
Signal analysis
In the plot, several points are displayed with an orange triangle.
By clicking on one of them, the web site loads the raw signal and, through a dedicated page, allows to per-
form the analysis of the signal.
Figure 315: HI and dB page – TVM Signal

Classification
UNCLASSIFIED
In the upper part of the page, Heliwise shows the following details:
• Id of TVM Component (moving the mouse over it, it’s possible to show the description of TVM compo-
nent);
• the DSN in which the signal was recorded;
• the date and time of recording;
• the relative aircraft FH value when the signal was recorded;
• File in which the signal is present;
• Plot Type to indicate which processing has been applied to plot the data.
N.B.
In the top-right corner of the page, you can quickly reload the other signals avail-
able for that TVM Component by mean of the blue arrows.
Also in this dialog, the chart is manageable through several functionalities placed above the graph:
• Axis Cursor; to enable the dynamic display of coordinates while moving the mouse cursor. When
• Tooltip; when enabled, the chart automatically creates a circle on the higher point of amplitude for each
frequency indicator. Moving over the circle, the user can see the precise coordinates.
• Harmonic (if applicable); first of all, once enabled, you have to select a frequency. Automatically Heliwise
calculates and show the respective harmonics.
• Sideband (if applicable); first of all, once enabled, you have to select two frequencies in order to dynam-
ically calculate the sideband.
• Reset; disabled the engaged functionalities.
• Ref. Orders (if applicable); show the reference orders.
All buttons have an amber background when they are engaged by user. Click again for disabling.
To zoom the chart, drag the mouse pointer on area of char.

To reset the zoom, you can click twice on the graph or select “Reset Zoom” in the contextual menu (right
click on chart).

Classification
UNCLASSIFIED
1.11.3 Accelerometer Status

On this page you can view status details for each specific accelerometer used by the TVM system.
N.B. On opening the page the DSN selected by default is the last DSN for the H/C selected. Click on
the SmartLink button in the top right corner to change the filter parameters.
Figure 316: TVM Accelerometer Summary
At the top of this page you can view the following data regarding the H/C selected:

Classification
UNCLASSIFIED

The main area is divided into four tables. The first table ‘TVM System Status Last D/L’ shows the following
data:
• ‘Component’; the identification code of the relevant accelerometer.

• ‘Location’; the location in which the component is found.
• ‘Ammc1’; a green circle shows if the data derives from this AMMC.
• ‘Ammc 2’; a green circle shows if the data derives from this AMMC.
• ‘Status’; the current status of the component; this can be ‘No Failures’ or ‘Fail’.
• ‘Arising Status’; the arising status if generated.
• ‘Failure Counter’; the number of failures occurred.
• ‘Occurrence Counter’; the number of occurrences.
• ‘Anomalies Counter’; the number of anomalies verified.
• ‘P/N’ the associated Part number.
• ‘S/N’; the associated Serial Number.
• ‘LCN’; the corresponding logistic Control Number.
• ‘ALC’, the corresponding Alternate Logistic Control Number.
• ‘LCN Description’; a description of the LCN.
Figure 318: TVM System Status Last D/L

Classification
UNCLASSIFIED
In this table you can select a component by clicking on the corresponding row, once selected it is highlighted
in blue. Further data for the component can be viewed in the tables below if available.
Right clicking on a row a contextual menu becomes visible.
Figure 319: TVM System Status Last D/L - Menu
Selecting ‘Show Acquisition’ a pop-up window opens showing an image of the component selected and its
corresponding acquisitions.
Figure 320: TVM System Status Last D/L – Acquisition window
On the left side is placed a table showing the following data:
• ‘Acquisition Code’; the corresponding identification code for the acquisition.

• Analysis Type Code’; the type code relevant to the acquisition (SYNC, THIST, FAVG or ENVE).

Classification
UNCLASSIFIED
The second table labelled ‘Missing Acquisiton Results - Last D/L’ is populated if any occurrences of missing
TVM data are detected in the last download for the Acq. Id performed with the selected accelerometer.
Figure 321: TVM System Status Missing Details Last D/L
This table contains the following data:
• ‘Component’; the aircraft component involved.

• ‘Acquisition ID’, the identification code of the associated acquisition.
• ‘Description’, a description of the acquisition.
• ‘Type’; the acquisition type (SYNC, THIST, FAVG or ENVE).
• ‘Last Valid Acq. Date-Time’; the date and time of the last valid acquisition (DD_MM_YYYY HH.MM.SS).
• ‘Last Valid Acq. FH’; the last valid acquisition recorded flight hours.
• ‘Last InValidAcq. FH’; the last invalid acquisition recorded flight hours.
• ‘Missing FH; the amount of missing flight hours.
• ‘Missing Threshold (Normal operation); the missing threshold value during normal operation.
• ‘Missing Threshold (Close Monitoring); the missing threshold value during close monitoring.
• ‘CM Status’; the close monitoring status.
• ‘Arising number’; the identification number of the arising generated.
• ‘Arising Status’; the status of the generated arising.
‘Failures Cross Correlation - Last D/L’ Tab
The second tab labelled ‘Failures Cross Correlation - Last D/L’ shows the results of any cross correlation
checks carried out in the last DSN for a specific component.’
Figure 322: TVM System Status Failures Cross Correlation Last D/L
As shown in the image above, the table is composed by three columns:

• ‘Cross Correlation Check Result’; the result of check about the cross correlation.

Classification
UNCLASSIFIED
‘Failure Details’ Tab
In the ‘Failure Details’ tab there are two. In these tables you can view data regarding the failures recorded for
the selected component. The data in the table in the right corresponds to the row at the same level of the
data in the table on the left. Therefore the occurrences in the table on the right refer to the fault in the same
row in the table on the left.
Figure 323: TVM System Status Failure and Acquisition Details
The table on the left shows the following data:
• ‘DSN’, the DSN from which the data derives.

• ‘Ammc’; the AMMC used to record.
• ‘Fault Number’; the identification number of the fault.
• ‘Fault Description’; a description of the associated fault.
• ‘Arising Number’; the number of the arising generated following the failure detection.
• ‘Occurrence Counter’; the number of occurrences recorded for the corresponding fault.
• ‘Occurrence Active’; if the fault is active a red circle displays, if it is not active a grey circle displays.
• ‘Cumulative Duration’; the total duration of all the occurrences.
• ‘Longest Duration’; the duration of the longest occurrence.
• ‘Remarks’; comments associated to the detected failure.
• The table on the right is populated after selecting a row in the main table on the left. This table shows the
following data regarding the failures:
• ‘Occurrence Start Time’; the recorded start time of the occurrence (DD_MM_YYYY HH.MM.SS).
• ‘Occurrence Stop Time’; the recorded stop time of the occurrence (DD_MM_YYYY HH.MM.SS).

Classification
UNCLASSIFIED
‘Acquisition Anomaly Details’ Tab
Click on the ‘Acquisition Anomaly Details’ tab to view the counters of the acquisition anomalies relevant to
the acquisitions performed with the selected accelerometer. The table shows the following data:

• ‘Acq. ID’; the acquisition identification code.
• ‘Accelerometer Low Signal Level Counter’; the number of corresponding occurrences.
• ‘A/D Converter Saturation Counter’; the number of corresponding occurrences.
• ‘Primary Azimuth Unlock Counter’; the number of corresponding occurrences.
• ‘Convergence Failure Counter’; the number of corresponding occurrences.
• ‘Timeout Counter’; the number of corresponding occurrences.
Figure 324: TVM System Status Acquisition Anomaly Details

Classification
UNCLASSIFIED
1.11.4 Azimuth Sensors Status

On this page you can view status data relevant to the two TVM system azimuth sensors.
Figure 325: TVM Azimuth Sensor Status

Classification
UNCLASSIFIED

In the first table labelled ‘Current Azimuth Sensor Status – Last D/L’ you can view the following data regard-
ing the two TVM system azimuth sensors.:
• ‘Component’; the identification code of the Azimuth sensor.

• ‘AMMC1’; a green circle shows if the data derives from this AMMC a grey circle shows if it does not.
• ‘AMMC 2’; a green circle shows if the data derives from this AMMC a grey circle shows if it does not.
• ‘Anomalies Counter’; the number of anomalies verified.
Figure 327: Azimuth Sensor Status

Classification
UNCLASSIFIED
‘Failures Cross Correlation Last D/L’ Tab
In the second area there is a tab labelled ‘Failures Cross Correlation Last D/L’ shows the results of any cross
correlation checks carried out in the last DSN for a specific component.
Figure 328: Failures Cross Correlation Last D/L

In the ‘Failure Details’ tab there are two tables. In these tables you can view data regarding the failures
recorded for the selected component. The data in the table on the right is populated after clicking on a row in
the table on the left.
Figure 329: Failure Details
As shown in the image above, the table on the left contains the following data:

• ‘Ammc’; the Ammc used to record.
• ‘Occurrence Active’; if the fault is active a green circle displays, if it is not active a grey circle displays.
• ‘Remarks’; comments associated to the detected failure.

Classification
UNCLASSIFIED
The table on the right is populated after selecting a row in the main table on the left. This table shows the fol-
lowing data regarding the failures selected:
Figure 330: Failure Details – Occurrences

Classification
UNCLASSIFIED
1.11.5 VDAM Board Status

On this page you can view status data relevant to the VDAM Board sensors used by the TVM system.
Figure 331: TVM VDAM Board Status

Classification
UNCLASSIFIED

In the second area there is a table labelled ‘Current VDAM Board Status Last D/L’ you can view the following
data regarding the TVM VDAM Board sensors:
• ‘Component’; the identification code of the VDAM sensor.

Figure 333: VDAM Board Status

Classification
UNCLASSIFIED
‘Failures Cross Correlation Last D/L’ Tab
In the second area there is a tab labelled ‘Failures Cross Correlation Last D/L’ shows the results of any cross
correlation checks carried out in the last DSN for a specific component.
Figure 334: Failures Cross Correlation Last D/L

In the final tab labelled ‘Failure Details’ there is a table.
Figure 335: Failure details
As shown in the image above, you can view the following data regarding the failures recorded for the
selected component:

• ‘Ammc’; the Ammc used to record.

Classification
UNCLASSIFIED
• ‘Occurrence Active’; if the fault is active a green circle displays, if it is not active a grey circle displays.
• ‘Remarks’; the comments related to the detected fault. Double click in the remarks column on the rele-
vant row to insert a comment.
The table on the right is populated after selecting a row in the main table on the left.
Figure 336: Failure details - Occurrences
This table shows the following data regarding the failures selected:

Classification
UNCLASSIFIED
1.11.6 Exceedances
On this page you can navigate through the TVM exceedances by means of a synoptic chart. Here the user
has an overview where the TVM exceedance occurred. The data displayed are relative to the last DSN.
Figure 337: Exceedances Synoptic Chart

Classification
UNCLASSIFIED
In the main area of the page there is a synoptic chart displaying the TVM components which on selection (by
clicking on it) open a window showing further details of the selected component.
The components are colour in according to the legenda shown in the right side:
Table 21: Exceedances Synoptic Legenda
Colour Code Definition
Green shows there are no DA threshold exceed-

ances present.
Blue shows the component which registered values
under the steady blue threshold.
Yellow shows at least one DS Steady Yellow

threshold exceedance was reported for the last
DSN.
Red shows at least one DA Steady Red threshold

exceedance was reported for the last DSN.
.
Purpose shows there was missing TVM data

reported for the last DSN.
It indicates a component under monitoring.
It indicates components with an expired monitoring.

Classification
UNCLASSIFIED
To view in more detail a specific component click on the corresponding component in the synoptic chart. A
window then opens showing the sensor selected and its associated acquisitions.
Figure 339: Exceedance Synoptic Chart – Component window
On the left of the window there is an image of the component showing the location of the sensor (through a
triangular shape) and the location of the relative acquisitions (through a circular shape).
Figure 340: Exceedance Synoptic Chart – Component image

Classification
UNCLASSIFIED
As the main window, on the right side there is a legenda containing the colour codes and below it there is a
list of the acquisitions.
Figure 341: Exceedance Synoptic Chart – Right side of component window
Select an acquisition by clicking on the relevant row in the list and once selected; details regarding it are
shown in a table in the lower area of the window.
Below the acquisition list there are buttons which provide a link to navigate directly to the relevant system
status browser or the TVM Health Index Summary Chart. The availability of each button depends on the
applicability of selected component
Below the browser link buttons there is a table which shows the following details of the acquisition selected
in the list:
• ‘Id’; the identification code of the selected acquisition.

• ‘Type’; the type of acquisition.
• ‘Description’; a description of the selected acquisition.

Classification
UNCLASSIFIED
1.11.7 Exceedances Arising
On this page you can navigate through the TVM exceedance generated arising by means of a synoptic
chart. Here, the user can explore how many arising are present due to TVM Exceedance.
Figure 342: Exceedances Arising Synoptic Chart
• ‘Last Dsn End’; the date and time of the end of the last DSN (DD_MM_YYYY HH.MM.SS)

Classification
UNCLASSIFIED
In the main area of the page there is a synoptic chart displaying the TVM system components which on
selection (by clicking on it) open a window showing further details of the selected component. The compo-
nents are colour coded in order to give an immediate view of the system status and arisings. The colour
code is shown in the legenda on the right side:
Table 22: Exceedance Arising Synoptic Legenda
Green shows there are no arising present.
Brown shows arising are present.
The yellow colour represents the arising which

does not impact on the H/C status.
The red colour represents the arising which

changes the H/C status to “Unserviceable”.
It shows if a specific component (which owns an
arising) is already monitored.
It shows if a component is still monitored even the

expiration date is expired.

Classification
UNCLASSIFIED
Figure 344: Exceedances Synoptic Charts – Component Window

Classification
UNCLASSIFIED
Figure 345: Exceedances Synoptic Charts – Component Image
On the right of the image there is further information.
Figure 346: Exceedances Synoptic Charts – Component details

Classification
UNCLASSIFIED
At the top there is a legend showing the colour code.Below the legend there is a list of the acquisitions
shown on the right. Select an acquisition by clicking on the relevant row in the list. Once an acquisition is
selected details regarding it are shown in a table in the lower area of the window.
Below the acquisition list there are buttons which provide a link to navigate directly to the relevant system
status browser or the TVM Health Index Summary Chart. Their availability depends on selected component
and its applicability.
Below the browser link button there is a table which shows the following details of the acquisition selected in
the acquisition list:


Classification
UNCLASSIFIED
1.11.8 System Status

On this page you can navigate through the TVM System Status by means of a synoptic chart.
The graphics display the registered on board failure relative to HUMS sensors of last DSN.
Figure 347: System Status Synoptic Chart

Classification
UNCLASSIFIED
nents are colour coded in order to give an immediate view of the system status:
Table 23: System Status Synoptic Legenda
Green shows there are no failures present.
Yellow shows the presence of anomalies.
Red shows that failures are present.

Classification
UNCLASSIFIED
Figure 349: System Status Synoptic Chart – Component window
Figure 350: System Status Synoptic Chart – Component details

Classification
UNCLASSIFIED
At the top there is a legend showing the colour code.
Below the legend there is a list of the acquisitions. Select an acquisition by clicking on the relevant row in the
list. Once an acquisition is selected details regarding it are shown in a table in the lower area of the window.
Below the acquisition list there is a button which provides a link to the relevant system status browser. Their
visibility depends in according to selected component. Clicking on them, the user is able to navigate directly
to another dialog with the component data as input parameter.
Below the browser link button there is a table which shows the following details of the acquisition selected in
the acquisition list:


Classification
UNCLASSIFIED
1.11.9 System Status Arising

On this page you can navigate through the TVM System Status Arising by means of a synoptic chart.
Here, the user can retrieve information about the active arising to be carried out because of failure on certain
HUMS sensors.
Figure 351: System Status Arising Synoptic Chart

Classification
UNCLASSIFIED
nents are colour coded in order to give an immediate view of the system status and arising. The colour code
is as follows:
Table 24: Status Arising Synoptic Legenda
Green shows there are no arising present.
Brown shows that pending arising is present.
The yellow colour represents the arising which

doesn’t impact with the H/C status.
The red colour represents the arising which

changes the H/C status to “Unserviceable”.
window then opens showing the sensor selected and its relevant acquisitions.

Classification
UNCLASSIFIED
Figure 353: System Status Arising Synoptic Chart – Component window
On the left side there is an image of the component showing the location of the sensor (through a triangular
shape) and the location of the relative acquisitions (through a circular shape)
Figure 354: System Status Arising Synoptic Chart – Component details
At the top there is a legend showing the colour code.

Classification
UNCLASSIFIED
Below the legend there is a list of the acquisitions shown on the right. Select an acquisition by clicking on the
relevant row in the list. Once an acquisition is selected details regarding it are shown in a table in the lower
area of the window.
Below the acquisition list there is a button which provides a link to the relevant system status browser.
The buttons are visible in according to selected component. They act as link to navigate to the relative dialog
with the component as input parameter.
Below the browser link buttons there is a table which shows the following details of the acquisition selected
in the acquisition list:

• ‘Type’; the type of selected acquisition.
• ‘Status’; the current status of the selected acquisition.
• ‘Installed P/N’ the part number installed (if available).
• ‘Installed S/N’; the serial number installed (if available).
• ‘LCN’; the associated Logistic Control Number.
• ‘ALC’; the associated Alternate Logistic control Number.
• ‘LCN/ALC Description’; a description of the relevant LCN/ALC.

Classification
UNCLASSIFIED
1.11.10 Close Monitoring

On this page you can identify which Helicopters and acquisitions are monitored by Heliwise.
Figure 355: Close Monitoring
The page is divided into two main areas; the first area shows details regarding the H/C selected.
Figure 356: Close Monitoring – H/C details

Classification
UNCLASSIFIED
The second area named ‘Close Monitoring Processes’ allows managing the process to monitor one or more
specific acquisitions of selected H/C.
Figure 357: Close Monitoring Processes

• ‘HI’; navigation button, clicking on it the user navigates directly to the Health Index Result page.
• ‘Acq.Id’; the unique id to identify each acquisition.
• ‘Description; description of selected acquisition.
• ‘Type’; the acquisition type; SYNC, THIST, FAVG or ENVE.
• ‘Status’; the status of the current process. Clicking on it, the user is able to change its status and set is as
“Closed”.
• ‘Start Date Time’; the date and time of process creation.
• ‘End Date Time’; the date and time of process end.
• ‘Start FH’; number of flight hours when the process was started.
• ‘End FH’; number of flight hour when process terminates.
• ‘Planned End FH’; number of planned flight hours in order to complete the process.
• ‘Request Originator’; who created the process.
• ‘Conclusion Originator’; who set the process as closed.
• ‘Remarks’; note to insert.

Classification
UNCLASSIFIED
Above the grid, there are three buttons needed to manage the set of data in grid.
Figure 358: Close Monitoring Buttons
In order to create and close a process the buttons placed have the following features:
• Click on to create a new row in the table. Once the user clicked on the button, below it appears an
area in which the user must insert the desired value.
Figure 359: Close Monitoring – Process creation
As shown in the image above, the fields are the same used into the grid below. The most of them are not
editable; therefore the user has to select only the ‘Acq.Id’ combo box. The ‘Remarks’ field is not mandatory
and the user can leave it empty.
Once the Acq.Id is selected is possible to accept the inserted value clicking on . Instead to cancel the
operation the user has to click on .
• Click on to accept the changes applied to a process. It becomes clickable when the user set as
“Close” the status of a row. Its target is to approve the change of status.
• Click on to cancel the changes applied to a process. It becomes clickable when the user set as
“Close” the status of a row. Its target is to reset the change of status and restore the previous data set.
Furthermore, clicking on the charts (placed in second column) you are automatically redirect to the HI plots
of that TVM component.

Classification
UNCLASSIFIED
1.11.11 Threshold Setting Check

On this page you can view the list of occurrences in which the Steady threshold and Far trend threshold set-
ting checks were not successfully passed. There are two tabs for the DA Steady threshold area and two tabs
for the DA Far Trend threshold area. In both areas the tabs are labelled ‘Threshold Anomalies’ and ‘Skipped
Checks’. The ‘Threshold Anomalies’ tabs list the potentially anomalous threshold values detected during the
check, the ‘Skipped Checks’ tabs list all of the Acq. Id/Health Index pairs where the threshold setting check
was skipped due to the lack of a sufficient number of valid results.
N.B. The results displayed correspond to the last valid health index.
Following the selection of a single A/C the application shall perform a statistical assessment of the DA
threshold values with respect to the last valid Health Indexes.
Figure 360: TVM Threshold Setting Check

Classification
UNCLASSIFIED
At the top area of the page there is a section which shows the following data regarding the H/C selected:

Classification
UNCLASSIFIED
DA Steady Threshold Check Results
In the ‘DA Steady Threshold Check Results’ area you can view data regarding the DA steady threshold
results. This area is divided into two tabs.
In the first tab labelled ‘Threshold Anomalies’ you can view the following data:
• ‘Acq. Id’; the acquisition identification code.

• ‘Description’; a description of the corresponding Acq. Id.
• ‘Health Index’; the corresponding health index code.
• ‘Threshold Type’; type of steady threshold, blue, amber or red.
• ‘Status’; the current DA Steady threshold status. Permanent or Temporary.
• ‘Value’; the current value.
• ‘Anomaly Message’; the relevant message associated with the anomaly.
• ‘Low Limit’; the low steady limit.
• ‘High Limit’; the high steady limit.
• ‘HI mean’; the computed HI mean value.
• ‘HI STD’; the computed HI standard deviation value.
• ‘STD_DIFF’; the computed standard deviation difference value.
• ‘Check Low Limit’; the steady threshold setting check low limit.
• ‘Check High Limit’; the steady threshold setting check high limit.
Figure 362: Steady Threshold Anomalies
In the second tab labelled ‘Skipped Checks’ you can view the following data:

• ‘Description’; a description of the corresponding acquisition code.
• ‘Threshold Type’.
• ‘Status’; the current DA Steady threshold status. Permanent or Temporary.
• ‘Value’; the current DA steady threshold value.
• ‘Remarks’; an indication of the reason for the check skip.

Classification
UNCLASSIFIED
Figure 363: Steady Skipped Check
DA Far Trend Threshold Check Results
In the second area you can view data regarding the DA far threshold check results. This area is divided into
two tabs. In the first tab labelled ‘Threshold Anomalies’ you can view the following data:

• ‘DA Far Trend Th.’; the current DA Far Trend threshold value.
• ‘Anomaly Message’; the relevant message associated with the anomaly.
• ‘dB Diff’; the current dB difference.
• ‘Low Trend’; the setting checks low trend value.
• ‘High Trend’; the setting check high value.
Figure 364: Far Threshold Anomalies
In the second tab labelled ‘Skipped Checks’ you can view the following data:

• ‘DA Far Trend Th.’; the current DA Far Trend threshold value
• ‘Remarks’; an indication of the reason for the check skip.

Classification
UNCLASSIFIED
Figure 365: Far Trend Skipped Checks

Classification
UNCLASSIFIED
1.11.12 Summary Report

The report is generated automatically on opening the page and provides Summary data for the following:
• TVM Exceedances.
• System Status Missing Data.
• System Status Accelerometer.
• System Status Azimuth.
• System status VDAM.
This is a single document containing all maintenance related information relevant to the TVM system for the
last recorded download.
Figure 366: TVM Summary Report

Classification
UNCLASSIFIED
The second and main area is dedicated to the actual report which is automatically generated for the H/C
selected.
At the top of this report, there is a tool bar which enables you to carry out further actions on the report.
Figure 368: Report toolbar
See the table below for a description of the commands on the tool bar.
Button Description
Click here to save the report. Your Browser opens and you select the destination.
save
Click here to print the report.
print
Click here to view the first page of the report.
first page
Click here to view the previous page.
previous page

Classification
UNCLASSIFIED
Button Description
Click here to view the next page.
next page
Click here to view the last page.
last page
Click here to reduce the size of the page.
zoom out
Click here to increase the size of the page.
zoom in
Is also possible to zoom in or out using the drop down menu. Choose the level of
zoom from this menu.
Click here so that the document fits the width of the page.
fit width
Click here to view one page at a time.
one page
Click here to view two pages at a time.
two pages
Type a word into the text field and the document will automatically find the word.
Click here to view the ‘found’ word in an earlier part of the document.
previous
Click here to view the next ‘found’ in the document. The words which have been
next found are highlighted.

Classification
UNCLASSIFIED
1.11.13 Signal Display & Analysis

On this page is possible to see the chart of signals contained in the DTD files. Here they are visible without
being processed in the ‘Health Index Results’.
Figure 369: TVM Signal Charts

Classification
UNCLASSIFIED
In the main area, the user is able to see the raw signal.

Classification
UNCLASSIFIED
Figure 371: TVM Signal Charts - Main area
Above the chart, there are three combo boxes to allow the user to filter which data to be shown.
The first field contains a list of all acquisitions present in the selected DSN.

Classification
UNCLASSIFIED
Figure 372: TVM Signal Charts – Acquisitions list
Once the user selects an acquisition, the next field is automatically populated in order to load the physical
file containing that acquisition.
Figure 373: TVM Signal Charts – DSN file

Classification
UNCLASSIFIED
The last field is always loaded according to the acquisition selected in the first field. It contains the plots
ready to be shown. The plots available are visible or not according to the applicability of the acquisition.
Figure 374: TVM Signal Charts – Plot
Once the user has selected the fields, the ground station is able to load the correct set of data and generates
the appropriate chart. To complete the operation, click on the tick icon placed at the end of toolbar ‘Apply’
button.
Right clicking on chart, it’s possible to save the chart as a PDF file.
Figure 375: TVM Signal Charts – Plot
In the bottom area of the page, the user can expand the Health Index view and see the Health Index values.
Figure 376: TVM Signal Charts – Health Index table
The data displayed is reported in tabular format showing the same columns as the Health Index Page.

Classification
UNCLASSIFIED
1.12 ROTORS AND AIRFRAME
In the RTB module the user can open the RTB Health index trends and RTB Vibration.
Figure 377: RTB Module

Classification
UNCLASSIFIED
1.12.1 Aircraft RTB Trends
On this page it’s possible to analyse the health indexes trend of Rotor Track and Balance. The user can
access to this page using the main menu ‘RTB Health Index Trend’ or through the contextual menu placed in
the home page.
In the central area the web application plots the results of processing RTB data relevant the selected heli-
copter.
Figure 378: RTB Trend – Central Area
Heliwise automatically plots the health index in which there is an arising generated by an exceedance.
The left side of the area is composed by the list of Health Indexes applicable to the selected RTB component
and relevant flight conditions:
• -“G”: Ground;
• -“H”: Hover;
• -“S”: Slow cruise;
• -“C”: Cruise;
• -“F”: Fast Cruise or VNE.

Classification
UNCLASSIFIED
The input data is the RTB channel to be analysed. You can select it through the combo box placed in the
upper-central part. Each row represents the proper acquisition on board and, on the right part of this list; the
user can get information about quantity of arising occurred on it.
The first square shows the Accepted arising meanwhile the second indicator represents the Pending ones.
Clicking on one of them, Heliwise automatically plots the health index in which there is an arising generated
by an exceedance.
Figure 379: RTB Trend – Acq. list
The left side of the area is composed by the list of Health Indexes applicable to the selected RTB acquisition.
Ticking them, the user can decide which HI plotting in the central area. As visible in the image above, the
web site automatically ticks the HI where there is an arising.
The squares show the Flight Condition in which the exceedance was occurred and the relative colour dis-
plays the type of seriousness (red or amber).
Finally, at the end of row, a counter shows how many arising are still active on that Health Index.
Figure 380: RTB Trend – HI list

Classification
UNCLASSIFIED
The user can hide this list, by clicking on the button placed in upper-left corned (red arrow).
Figure 381: RTB Trend – Close HI List
To show the list, clicking again on the same button (meanwhile the arrow is became green).
Figure 382: RTB Trend– Open HI List
To select all HI with just one click, select the button highlighted in red in the image below (placed in the top
Figure 383: RTB Trend – Select All HI
The HI charts plotted in the central area of the page, can display the acquisitions in according to the Flight
Condition in which was the aircraft when tracked the HI value.
You can set them using the funnel icon, placed always in the toolbar above the charts. The page can show
only one Flight Condition per time.

Classification
UNCLASSIFIED
Figure 384: RTB Trend – Flight Conditions
The last button placed on the right upper corner allows to flip the central view to others plots relevant to track
and lead/lag collected data.
Figure 385: RTB Trend - Flip Icon
The features are available only when the selected acquisition corresponds to ‘Main Rotor’ otherwise the icon
will be disabled.
This view allow the change the HI list showing the Blade Track and Blade lead/lag check-boxes.

Classification
UNCLASSIFIED
Figure 386: RTB Trend - Track and lead/lag
The plots containing the track of each blade assigning a colour for each ones:
• Black Rel. H
• Red Rel. H
• Blue Rel. H
• White Rel. H
• Yellow Rel. H
The green line is fixed on the 0 abscissa value to help the user during the data analysis.
The chart capabilities will be described in the next paragraph and are equal for both view.

Classification
UNCLASSIFIED
Plots capabilities
Figure 387: RTB Trend – Plots capabilities
By default the RTB Trend plots show the following data:
• X-axis composed by Flight Hours indications;

• Y-axis composed by IPS values;
• Amber and Red Threshold (if any);
Figure 388: RTB Trend – tooltip
Every acquisition point has a tooltip automatically visible by default. Moving over one of them, the web appli-
cation shows the main information. In detail, the following information displayed are:
• Flight Condition to confirm which is the selected condition;

• Acq. Date Time to get out when the acquisition was tracked;

Classification
UNCLASSIFIED
• A/C Flight Hours to indicate the total number of Flight Hours recorded by the current DSN
• The Value of health index;
• Rotor Speed [%]; the percentage value representing the speed of selected rotor.
• IAS [kts]; the value of Indicated Air Speed at time in which the acquisition was recorded;
• Acq. Type: the manner in which the acquisition point was recorded. It can be manual or automatic. The
user can find out which is the Acq. Type referring to the point used in the plot. As shown in the image
below, when the point is composed by a circle (i.e. on the right side) that means an automatic acquisition
otherwise a manual one (i.e. on the left side).
Figure 389: RTB Trend – Acquisition Types
result, the tooltip will be composed by additional information such as Radar Altitude, Vertical Accel., Pitch,
Roll and Yaw degrees.
By clicking on an acquisition of one plot, Heliwise shows the same acquisition occurrence in the others HI
plots open. The selected acquisition is identifiable by a green circle around it.

Classification
UNCLASSIFIED
Figure 390: Acquisition Green Circles

To zoom a plot section, select an area by drag and drop the mouse pointer, instead to reset its view click
twice on the chart.
Figure 391: RTB Trend – zoom
By right clicking on whatever point of the plot, the web site displays a contextual menu in which it’s possible
to:

Classification
UNCLASSIFIED
• Change the X axis value switching the indicators of abscissa from Acquisition Flight Hours to Acquisition
date time and vice versa.
Figure 392: RTB Trend – Contextual Menu

Classification
UNCLASSIFIED
User Notes
To add a user note in the plot, you should click on the second icon placed in the top right corner of the page.
Figure 393: RTB Trend – Add User Note
Once enabled the creation of notes, the user has to decide where place its annotation (as shown below).
Once clicked where there will be the user notes, the following popup opens.

Classification
UNCLASSIFIED
Figure 394: HI and dB page – Note Management
Here the user can add a new note and it will be shown as part of a chat indicating who has written and when.
Figure 395: HI and dB page – Chat

Classification
UNCLASSIFIED
The communication will be applied to all Health Indexes of that acquisition on which the user is adding a
note. Finally, the user will see a letter icon where the user has created a new communication channel and
moving the mouse pointer over that, Heliwise shows the last message by default.
Arising Management
Below the list of RTB acquisition and Flight Conditions, Heliwise displays the arising still active on that
selected acquisition.
Figure 396: RTB Trend – Acq Arising
The arising grid is composed by the following columns:
• DSN; indicating the download Id in order to get out when the arising occurred;
• Description; containing the arising description.
• Reason; the type of exceedance which generated the arising.
• Update Time; the date and time of last update.
• Update User Code; who has performed the last update.
• Number; the id of arising.
• Status; the status of arising.
• Remarks; eventual note typed by user during data download processing.
Once performed the analysis the user can clear the arising by right clicking on the arising and select “Clear”
or “Reject” (depends on previous status of arising). It’s possible to clear all just selecting the last option
‘CLEAR/REJECT ALL’.

Classification
UNCLASSIFIED
Figure 397: HI and dB page – Arising Clearance
While this grid displays the arising for a single RTB component, you can see all arising for that helicopter
referring to the area expandable in the bottom-left corner of the page.
Figure 398: RTB Trend – Aircraft Arising
By clicking on the arrow, the area expands. Click again to hide it.
By right clicking on a single arising a contextual menu opens.

Classification
UNCLASSIFIED
Figure 399: RTB Trend – analyse Arising
As shown in the image above, the only action to be performed is to analyse the arising. Once clicked on it,
Heliwise reloads the page with the selected arising as input data.
Contextual Menu
Figure 400: RTB Trend– Contextual menu
• Zoom; allow to reset the zoom and focus on all acquisitions.

• Chart Settings.

Classification
UNCLASSIFIED
Figure 401: RTB Trend – Chart Settings
acquisition are plotted. Following, an example of:

Classification
UNCLASSIFIED
• XY Plot;
Figure 402: RTB Trend – Chart with Plot

• Step Area;
Figure 403: RTB Trend – Chart with Step Area

Classification
UNCLASSIFIED
• Bar;
Figure 404: RTB Trend – Chart with Bar

• Line;
Figure 405: RTB Trend – Chart with Line

Classification
UNCLASSIFIED
• Line Symbols;
Figure 406: RTB Trend – Chart with Line Symbols
• Export; export in PNG or JPEG of HI plot.

• Axis X; possibility to switch the value of abscissa from Acq. FH in Acq. Date time and vice versa.
• Show/Hide Extended Tooltip; view or not the additional parameters in the Tooltip.
• As result, the tooltip will be composed by additional information such as Radar Altitude, Vertical Accel.,
Pitch, Roll and Yaw degrees.
• Show/Hide Thresholds; choose to view or not the thresholds the thresholds.
• Show/Hide DSN Markers; possibility to hide the indicators of start DSN.
parameters.

Classification
UNCLASSIFIED
Figure 407: RTB Trend – Table view
By right clicking on it, you can open again the contextual menu relevant to table view.
Figure 408: RTB Trend – Contextual menu in table

Classification
UNCLASSIFIED
The ‘Show Extended Grid’ option allows to detail the information adding several columns (Radar Altitude,
Vertical Accel., Pitch, Roll and Yaw degrees.) in order to associate each RTB acquisition with relevant HI val-
ues.
By using the export option, the user can obtain a CSV file in which you will save the information.

Classification
UNCLASSIFIED
1.12.2 RTB Vibration
This page displays information regarding RTB vibration. It is necessary to first select an H/C from the fleet
menu in order to be able to access the page from the ‘Rotors and Airframe’ menu. When the page opens it
is necessary to select the DSN on which to read the signals coming from the vibration sensors.
Figure 409: RTB Vibration - select DSN
• ‘H/C Serial’; the H/C serial code.

Classification
UNCLASSIFIED
• ‘Last DSN End’; the date and time of the end of the last DSN (DD_MM_YYYY HH.MM.SS)
Figure 410: RTB Vibration - H/C Details
On the left side of the page it is possible to set filter parameters and view details of the selection.
Figure 411: RTB Vibration - Filter and details
The area is dedicated to filtering and choosing the accelerometer to be shown and its relative viewing
parameters.
At the top it is possible to select the rotor, after which the list below is dynamically filled. The user can decide
which is the regime of flight and the unit of measure to apply on the FFT chart: gravity or inches per second.
The following information is displayed in the ‘Details’ area:

Classification
UNCLASSIFIED
• ‘Rotor’; the rotor involved in the acquisition.

• ‘Sensor’; the rotor involved in the acquisition.
• ‘Health Index’; the relevant health index.
• ‘Flight Regime’; the regime kept during flight.
• ‘Flight Hours’; the number of flight hours executed by the H/C until this acquisition.
• ‘Date&Time’; the date and time of recording.
• ‘Acq. Mode’; the mode of acquisition.
• ‘Rotor Speed’; the speed of the selected rotor.
• ‘Air Speed’; the outside speed received by sensors in knots.
• ‘Weight on Wheels’; identifies whether the helicopter was in flight or not.
• ‘Rad Alt’; the rad altimeters value.
• ‘Lat Accel’; the lateral acceleration speed.
• ‘Long Accel’; the longitude acceleration speed.
• ‘Vert Accel’; the vertical acceleration speed.
The central area consists of a group of charts and grids showing the source signal coming from
accelerometer sensors. Once a user has selected any filter parameters, the values are dynamically shown.

Classification
UNCLASSIFIED
Figure 412: RTB Vibration - main area
The charts show the signal coming from the selected indicator. Both charts display the amplitude of the
source signal. The first chart regarding the “Raw Signal” reads directly from the HUMS file, therefore its
abscissa is the value of the Raw Signal.
Whereas, the second chart shows the signal in another manner called “FFT Signal” in which the input is
converted to frequency (therefore, its abscissa is equal to the FFT Signal).
At the bottom of the area there are two grids containing the values shown in the charts.

Classification
UNCLASSIFIED
Figure 413: RTB Vibration - Signal grids
The “Raw Signal” grid contains the following columns:
• ‘Order’; a progressive number which identifies the X value.

• ‘Amplitude’; the amplitude value which identifies the Y value.
The “FFT Signal” grid contains the following columns:
• ‘Order’; a progressive number which identifies the X value.

• ‘Amplitude’; the amplitude value which identifies the Y value.
• ‘Phase’; the value of the frequency phase.

Classification
UNCLASSIFIED
1.13 HUMS FLEET MANAGEMENT
The ‘HUMS Fleet Management’ area, the user can visualize and group data by fleet.
Figure 414: HUMS Fleet Management menu item
As shown in the image above, the fleet HUMS area consists of six dialogs:
• Fleet Arisings
• Fleet Faults
• Fleet RTB Trends
• Fleet TVM Trends
• Fleet Close Monitoring
• Fleet TUM Torque Spectra

Classification
UNCLASSIFIED
1.13.1 Fleet Arising

Click on the menu item “Fleet Aircraft Arising” to open the dialog, the first window to open requires the user
to select the helicopters to be analysed.
Figure 415: HUMS Fleet Management Arising – H/C selection
The HUMS data will be loaded according to the selected parameters:
• Type: you can select the information type that generated the arising.
• DSN: select the range of DSN to analyse.
• Aircraft Model: select the aircraft model to filter dynamically the aircraft list below.
To complete the selection, confirm the operation by clicking on the green tick icon placed in the top right cor-
ner ( ). Otherwise, click on the red button to cancel ( ).
By clicking on the Smart Link button the user is able to change the filter parameters and select new view
parameters.

Classification
UNCLASSIFIED
Figure 416: Fleet Aircraft Arising
The main grid shows data regarding the arising recorded in the DSN(s) selected and relative aircraft. In this
table you can view the following data:
• ‘Tail Id’; to identify uniquely the aircraft involved.

• ‘DSN’; the download sequence number selected.
• ‘Number’ the sequential number given to each arising.
• ‘Code’; an identification code associated with an arising.
• ‘Type’; the type of arising, this can be: ‘EXCEED_CODE’, ‘FAULT_CODE’, ‘MANUAL’, ‘VMEXCEED-
ANCE’ or ‘VMMISSINGDATA’.
• ‘Created By’, the user logged on at the time of the relative download.
• ‘Generation Date &Time’; the date and time in which the arising was generated in the ground station.
• ‘Detection Date &Time’; the date and time in which the arising occurred.
• ‘Description’; a description of the arising.
• ‘Remarks’; a note of the arising.

Classification
UNCLASSIFIED
• ‘LCN’; the logistic control number related to the arising.

• ‘ALC’; the alternate logistic control number related to the arising.
• ‘Status’; the status of the arising, it can be ‘Accepted’, ‘Pending’, ‘Cleared’ or ‘Rejected’ and shown with
different colors.
To interact with the status of an arising placed in the table click on the desired arising and then right click.
A contextual menu opens as shown below.
Figure 417: Arising List – Contextual menu
By clicking on the operation to be applied the system processes the selected arising and changes its status
to another one. The following table shows how a status can be changed according to its source status.
Table 25: Description of Arising Status
Source Status Final Status

Pending Accepted
Rejected
Accepted Cleared
Rejected “No action”
N.B. After Accepting an arising the status of the aircraft becomes “Unserviceable” until the user
changes the arising status to Cleared.

Classification
UNCLASSIFIED
The status of arisings are colored as shown in the images below:
• - Light brown shows a ‘Pending’ status. It expects an action by user.
• - Amber shows an ‘Open’ status with no impact on helicopter status.

actions to be done.
In the bottom area of the page, there is a section named “Aircraft Arising Details”. This area is automatically
filled in according to the selected arising in the main grid. The mechanism used to value its fields is based on
the type of selected arising.
Exceed Code
Selecting an arising with type “Exceed_Code” the “Aircraft Arising Details” changes in order to detail this
type of arising.
In the first area labelled ‘Exceedance’ is detailed with following columns:

• ‘Active’; the circle shows whether the exceedance is active (red circle) or deactivated (grey circle).
• ‘Detection Date &Time’; the date and time the occurrence was detected.
• ‘Total Occurrences’; a number which shows how many times the occurrence was recorded.
• ‘Worst Value’; the worst recorded value of the worst recorded values.

Classification
UNCLASSIFIED
Below the ‘Exceedance’ area there is a table showing the following data:

• ‘Worst Value’; the worst value recorded during the occurrence.
Fault Code
If you select ‘Type’ equal to ‘FAULT_CODE’ the ‘Aircraft Arising Details’ area changes as occurred with the
“Exceed_Code” type. As before, the area is divided into two parts.
In the first area labelled ‘Fault’ you can view the following details:

• ‘Active’; the circle shows whether the fault is active (red circle) or deactivated (grey circle).
• ‘Event Detection Time & Date’; the time and date the occurrence was detected.
• ‘Total Occurrences’; a number which shows how many times the same arising has occurred.
Below the ‘Fault’ area there is a table showing the following data:


Classification
UNCLASSIFIED
VM Exceedance
If you select ‘Type’ equal to ‘VMEXCEEDANCE’ ‘the ‘Aircraft Arising Details’ area changes in order to details
this arising type.
In the first area labelled ‘VM Exceedance’ there is the following data:

• ‘N. of detected exceedances’; corresponding to threshold type ‘Trend’.
• ‘Event Detection Date &Time’; the date and time the occurrence was detected.
• ‘Health Index Worst Value’; corresponding to threshold type ‘Steady’.

Classification
UNCLASSIFIED
1.13.2 Fleet Faults
Click on the menu item “Fleet Faults” to open the dialog, the first window to open requires the user to select
the helicopters to be analysed.
Figure 421: HUMS Fleet Faults – H/C selection
The HUMS data will be loaded according to the selected parameters:
• Type: you can select the information type that generated the arising.
• DSN: select the range of DSN you would analyse.
• Aircraft Model: select the available aircraft model to filter dynamically the aircraft list below.
To complete the selection, confirm the operation clicking on the tick green icon placed in the top right corner
( ). Otherwise, click on the cross red button to cancel ( ).

Anyway clicking on the Smart Link button the user is able to change the filter parameters and select new
view parameters.

Classification
UNCLASSIFIED
Figure 422: Fleet Faults

Classification
UNCLASSIFIED
Arising Tab
Figure 423: Fleet Faults - Arising tab
The table contains the following details:
• Tail Id: the identification of the aircraft among fleet helicopter.

• DSN: the DSN in which the arising was recorded.
• NUMBER: the arising identification. By clicking on it, you will be redirect to the relevant fault description
using another tab placed in this table.
• Code: The fault code assigned to that arising.
• Type: The arising type.
• Status: The status of each arising. The information is colored as following:
- The ‘Pending’ status expects an action by user.
- The ‘Accepted’ status means there is an active arising on that fault code.
- Green shows a ‘cleared’ or ‘rejected’ status in which there are no further actions to
be done. ‘Cleared’ means the user has performed the action meanwhile the ‘Rejected’ status reports no
warning required. To change the status do right click on that one to be managed and a contextual menu
opens as shown below.

Classification
UNCLASSIFIED
Figure 424: Aircraft Faults - Arising Management
• Created by: the user who processed the DSN generating that arising.
• Generation Date&Time: the date and time of DSN generating that arising.
• Detection Date&Time: the date and time in which the arising was occurred and stored in DTD.
• Description: a description of the arising.
• Remarks: an additional note that could be typed by user during the debriefing phase.
• LCN: the logistic control number related to the arising.
• ALC: the alternate logistic control number related to the arising.
Once selected an arising, the page automatically loads the relevant fault details in the bottom part.
The data shown below are displayed in according to the type of selected arising. The section is called ‘Air-
craft Arising Details’.
Exceed Code
In case of ‘EXCEED_CODE’ the following details are displayed:

• Description: description of the failures
• Type Auth Status: the status given to the alarm which has been generated;
• Active: the circle shows whether the exceedance is active (red circle) or deactivated (grey circle).
• On Board Alarm Type: type of alarm displayed on CAS
• On Board Alarm: the message displayed on CAS (if any).

Classification
UNCLASSIFIED
• Detection Date & Time: when the fault was detected during AC activities.
• Total Occurrences: how many occurrences are detected relevant to that exceedance.
• Cumulative Duration; the total duration of the active status.
• Longest Duration; the longest duration of that exceedance.
• Worst Worst Value; the worst value among worst recorded values.
To report the list of the occurrences, the details area contains a table showing:
• Number: the identification number of the occurrence (progressive ID)

• Start Date & Time: when the occurrence was started.
• End Date & Time: when the occurrence was stopped.
• Worst Value: the worst value recorded during the occurrence.
Fault Code
If you select an arising having type equal to FAULT_CODE the following details are shown:
• Plant/SubSystem: the involved on board system.

• Description: description of the alarm.
• Type Auth Status: the relevant status given to the alarm which has been generated
• Active: the circle shows whether the fault is active (red circle) or deactivated (grey circle).
• On Board Alarm Type: there are three types of alarm: ‘Warning’, Caution’ or ‘Alert’.
• On Board Alarm: the message generated by the alarm.
• Event Detection Time & Date: the time and date the occurrence was detected.
• Total Occurrences: how many times the same occurrence occurred.
• Cumulative Duration: the total duration of the active status.
• Longest Duration: the status which remained active for the longest time.
At following more details about each occurrence.
• Number: the identification number of that occurrence (progressive ID).

• Start Date & Time: the date and time which the occurrence started.
• End Date & Time: the date and time which the occurrence finished.

Classification
UNCLASSIFIED
Faults Tab
The second tab on the Fleet Faults page contains the Faults list for the selected aircraft.
Figure 427: Fleet Faults list
The faults table displays the following columns:
• Tail Id: identifier of a single aircraft among fleet helicopters.

• AMMC SW Version: the SW version installed on that aircraft.
• Maintenance Name: the corresponding name of the fault in maintenance.
• First Occurrence Start Time: when first occurrence started.
• Total Occurrence: how many times the fault occurred.
• Cumulative duration: the total duration of selected fault.
• Longest Duration: the longest duration recorded for the selected fault.
• Occurrence Active: if the fault is still active a green circle displays otherwise the application shows a grey
circle.
• Arising number: the identification of assigned arising (in case it has been generated). The arising num-
ber is colored in according to the arising status (ref to Arising page for more details). By clicking on a
specific arising number you are taken to the ‘Arising’ tab where you can manage its status.

Classification
UNCLASSIFIED
Once selected a row in the grid, the web application automatically loads its details below.
Figure 428: Faults Details
This area is split in three parts; the first one called ‘Occurrence Details’:

• MCDU Message: the message shown into the MCDU component.
• Total Occurrences: counter which indicates how many times that fault was recorded.
The second part is composed by a grid containing the following data:

• Auth Status: the relevant status given to the alarm which has been generated;
• Occurrence Start Time: the time in which the occurrence was started.
• Occurrence Stop Time: the time in which the occurrence was stopped.
• Occurrence Duration: the duration of the occurrence.
• Parameter Details: if the occurrence is featured by additional parameters.
• Parameter Name: name of additional parameter existing into the occurrence.

• UoM: unit of measure applicable to that param.
• Value: value of parameter.

Classification
UNCLASSIFIED
Exceedances
On the third tab the user can find out more information about the recorded exceedance on the fleet.
Figure 429: Fleet Faults Exceedances.
It shows a list of exceedances registered during the last DSN time period. The table in this area shows the
following data:
• Tail Id: identifier of a specific aircraft among fleet helicopters.

• AMMC SW Version: the installed SW version on board.
• Fault Code: it reports the identifier code for a specific fault. The codes starting with 9 identify an exceed-
ance.
• Maintenance Name: description of the exceedance.
• First Occurrence Start Time: time of first occurrence.
• Total Occ.: how many times the exceedance occurred.
• Cumulative duration: the total time of the exceedance recorded.
• Longest Duration: the longest duration of an occurrence.

Classification
UNCLASSIFIED
• Worst Worst Value: the worst value among worst recorded values.
• Occurrence Active: green circle means exceedance is active otherwise a grey circle is displayed.
• Arising number: the arising identifier assigned to that exceedance (if any). The cell can change its color
in according with the arising status (pending, accepted or cleared/rejected).Clicking on it, the page redi-
rects to the first tab in which the arising list is more detailed.
The bottom part details the exceedance selected in the main grid.
Figure 430: Exceedance Details
This area is split in three parts; the first one called ‘Occurrence Details’ contains following data:

• Total Occurrences: how many times that fault was recorded.
• Alarm: the ob board message generated by the alarm.
The second part is composed by a grid showing the following data:

• Auth Status: the relevant status given to the alarm which has been generated.
• Occurrence Start Time: when the occurrence was started.
• Occurrence Stop Time: when the occurrence was stopped.
• Occurrence Duration: the duration of recorder occurrence.
• Worst Value: the worst value recorded in that time frame.
• Parameter Details: it reports if the occurrence is featured by additional parameters.
• Parameter Name: name of additional parameter linked to that occurrence.

• UoM: unit of measure applicable to parameter.
• Criteria: value of parameter.

Classification
UNCLASSIFIED
Alarm Tab
The fourth tab contains a list of alarm recorded during selected DSN on the fleet.
Figure 431: Aircraft Alarm
The main table shows the following data:
• Tail Id: identifier of a specific aircraft among fleet helicopters.

• AMMC SW Version: the SW version installed on-board.
• Maintenance Name: the corresponding maintenance name of that alarm.
• Total Occ.: how many times the fault occurred.
• Occurrence Active: if the fault is still active a green circle is shown, otherwise the page reports a grey cir-
cle.
• Arising number: a progressive number assigned to each arising. Each arising is colored in according to
its status. Clicking on it, the user is redirected to the first tab where more details are shown.

Classification
UNCLASSIFIED
In the bottom part of the page the user can find out more details about the selected alarm.
Figure 432: Alarm Detail
This area is split in two parts; the first one, on the left side, is featured ‘Alarm Details’:

• Total Occurrences: how many times that alarm was occurred.
• Alarm: the on board message generated by the alarm.
The second part is composed by a grid reporting the following information:

• Auth Status: status of the occurrence.

Classification
UNCLASSIFIED
Discrepancy Tab
In the fifth tab the user can find out a list of all discrepancy recorded into the selected DSN for the selected
aircraft.
Figure 433: Fleet Discrepancy
The main grid displays the following details:
• Tail Id: identifier of an aircraft among fleet.

• AMMC SW Version’; the SW version installed on AMMCs.
• Fault Code: the code identifies the alarm created.
• Maintenance Name: the corresponding maintenance name of that discrepancy.
• Total Occ.: a number which shows how many times the fault occurred.
• Occurrence Active: If the alarm is still active a green circle is shown otherwise a grey circle
• Arising number: the progressive number linked to each arising. It is colored in according to its status and
clicking on it the page redirect to the first tab in which the user can find more details about the arising.In
the bottom part of the page, more details are shown about the selected discrepancy.
Figure 434: Discrepancy Detail

This area is split in two parts.The first one, on the left side, reports a set of fields to describe the discrepancy
in detail.
• Plant/SubSystem: on board system from which the alarm originates.

Classification
UNCLASSIFIED

• Total Occurrences: how many occurrences was recorded.
• Alarm Type: there are three types of alarm: Warning’, Caution’ or ‘Alert’.
The second part is composed by a grid contains:

• Auth Status: the status of the generated alarm.
• Occurrence Start Time: when the occurrence was recorded.
• Own Value Boolean: Additional parameters reporting the existence of own value.
• Own Value Real: Additional parameters reporting the value of own parameter.
• Partner AMMC value: Additional parameters reporting the existence of partner value.
• Partner AMMC value: Additional parameters reporting the value of partner parameter.

Classification
UNCLASSIFIED
History Tab
The last tab contains the list of all event occurred during the selected DSN for the fleet.
Figure 435: Fleet Faults History
• Tail Id: the aircraft identifier.

• AMMC SW Version: the version of SW installed on AMMC.
• Maintenance Name: the corresponding maintenance name of the event.
• First Occurrence Start Time: the recorded time of first occurrence.
• Counter: how many times the event occurred.
• Occurrence Start Time: the start time of selected occurrence.
• Occurrence Stop Time: the end time of selected occurrence.

Classification
UNCLASSIFIED
The details regarding the selected occurrence are shown in the bottom area ‘History Detail’.
Figure 436: History Details
This area is split in two parts; the first one on the left side shows the following data:

• Total Occurrences: how many times that event was recorded.
The second part is composed by a grid which shows the following data:

• Occurrence Duration: the duration of selected occurrence.
• Occurrence Active: if the occurrence is still active or not.

Classification
UNCLASSIFIED
Extended Grid
In the upper right corner of the grid, the user can extend the grid adding more columns by means of a proper
button.
Figure 437: Fleet Faults - Show Extended Grid
Clicking on the button highlighted in the image above, the user can add more columns to the table:

The additional columns are filterable in order to allow a complete searching of the information.
To hide this additional information click again on the button.

Classification
UNCLASSIFIED
1.13.3 Fleet RTB Trends
Click on the menu icon ‘Fleet RTB Trends’. Heliwise opens a window in which you can select the aircraft to
be analyse.
Figure 438: Fleet RTB Trend - Popup for Aircraft Selection
The user can select all aircrafts, ticking the check-box ‘Select all Aircraft for this model’ once selected a
model in the upper part of the popup. On the contrary, the user can select each aircraft by selecting the rele-
vant box.
In the central area the web application plots the results of processing RTB Trend data relevant to selected
aircraft.

Classification
UNCLASSIFIED
Figure 439: Fleet RTB Trend - General Page
In the upper part of the page, Heliwise shows the aircraft selected for the comparison. Each AC is marked
with a colour used to identify it in the plot representation. Also the flight hours and S/N help the user to have
all set of data required for the analysis.
The following three variables are implied directly in the loading of plots data:
• Acquisition
On the upper part of the page, it’s placed a combo box containing a list of available acquisitions of rotors
channels. As shown in the image below the user can select the Main Rotor (loaded by default), Tail Rotor,
MGB Lateral and Rear Cabin Vert.

Classification
UNCLASSIFIED
Figure 440: Fleet RTB Trend - Acquisitions list
• Flight Condition
Below the acquisitions list, it’s placed a panel which contains several button. One per flight condition.
Clicking on them, the user can switch the view from a FC to another one.
You can select FPOG (on ground Acq.), HOVER, SL CRS (Slow cruise), Cruise, FAST CRS (VNE or fast
cruise), UNKNOWN.
• Health Index
To show at least one plot in the central area, the user has to tick the relevant health index on the left side.
This lists changes in according to the select RTB Acquisition. The user can tick more than one HI per time.
Clicking one of aircraft loaded in the upper part of the page, the system automatically highlights its samples
in the plots helping the user to identify the specific aircraft.
Figure 441: Fleet RTB Trend - Aircraft samples
As shown in the image above, the samples of the selected aircraft are colored in orange. To define how
many acquisitions have been stored in manual mode Heliwise displays a cross icon.

Classification
UNCLASSIFIED
To select all HI with just one click, select the button highlighted in red in the image below (placed in the top
Figure 442: Fleet RTB Trend – Select All HI
The central page can be filled with a maximum of two aircrafts. The user can click on the last button having
a calendar icon to change the number of plots shown per view.
Figure 443: Fleet RTB Trend - Charts per View
The first button which contains a grey circle allow to highlight the manual acquisition in the plots.
Figure 444: Fleet RTB Trend - Manual acquisitions

Classification
UNCLASSIFIED
The plots automatically highlights the samples stored with manual acquisitions and the circle icon placed in
the proper button changes its colour.
Moving the mouse pointer on a sample, the web application shows the relevant popup by default. It contains
several information regarding that point (AC Flight hours, HI Value, IAS, Rotor Speed).
To expand the information contained in this popup, you should do right click on the plot and selected ‘Show
Extended Tooltip’. In this way, the popup shows more information relevant to the altitude, acceleration and
rate.

Classification
UNCLASSIFIED
1.13.4 Fleet TVM Trends

Clicking on the ‘Fleet TVM Trends’ option in the main menu, the page opens a pop-up in which you have to
select the aircraft to be analysed.
Figure 445: Fleet TVM trends – Select Aircraft
First of all, you have to specify the AC model to which the helicopters are assigned.
After that, tick the AC to be analyzed (otherwise you can tick the option ‘Select all the Fleet’ in order to ana-
lyze all helicopters with that AC model.
Once ticked, you have to confirm by clicking on the green icon placed in the top right corner.

Classification
UNCLASSIFIED
Figure 446: Fleet HI – Default view
After a few seconds in waiting, the application loads the selected aircraft and in the upper part of the page
each helicopter is specified by means of serial code, flight hours and a colour.
Figure 447: Fleet HI – Selected Aircraft
By default the acquisition number 01 (SYNC 1st Stage Pinion LH) is selected and, to switch and view
another one, use the combo list and click on the acquisition. The TVM components are identified by the
acquisition Id, Type, Description and Accelerometer.

Classification
UNCLASSIFIED
Figure 448: Fleet HI – Acq. List

Classification
UNCLASSIFIED
Once clicked an acquisition, the page shows the applicable HI. However no HI is ticked and displayed by
default. Ticking them, the user can decide which HI plotting in the central area.
The user can hide this list, by clicking on the button placed in upper-left corned (red arrow).
Figure 449: Fleet HI page – Close HI List
Figure 450: Fleet HI page – Open HI List
In the toolbar, by a calendar button the user can set if visualize one or two charts per view (as shown below).
Figure 451: Fleet HI page – One Chart per View

Classification
UNCLASSIFIED
Figure 452: Fleet HI page – Two Charts per View
Every chart owns a button placed in the upper part of view, in which the user can set the legend of acquisi-
tions to be plotted (square without description means the average).
Figure 453: Fleet HI page – Legenda
By default the plots show the following data:
• Abscissa axis composed by Elapsed Flight Hours (most recent FH for each AC are placed in the right
side of plot).
• Value 0 o f y-axis show with a green line.
• Blue, Amber and Red Fleet Threshold.

Classification
UNCLASSIFIED
As listed above, by default the shown threshold regarding the entire fleet of H/C. However, to see the thresh-
old for a specific aircraft click on the relative helicopter icon in the upper part of the page.
By clicking on the AC, the page shows the aircraft threshold and all its acquisition are highlighted by means
of an orange colour.
Every point has the tooltip automatically visible by default. Moving over one of them, the web site shows the
main information. In detail, the following information are displayed:
• DSN number to identify the download from which the acquisition was generated.
• Acq. Date Time to get out when the acquisition was tracked.
• Acq. Flight Hours to indicate how many FH were recorded when the acquisition was tracked.
• A/C Flight Hours to indicate the total number of Flight Hours recorded by the current DSN.
• Health Index to show which index is being showing.
• The Value of health index.
Figure 454: Fleet HI page – tooltip
result the tooltip will be composed by additional information such as IAS, Engine 1 Torque, Engine 2 Torque,
Main Rotor Torque, Tail Rotor Torque, Pitch and Roll degrees.
Figure 455: Fleet HI page – Extended Tooltip
By clicking on an acquisition of HI plots, Heliwise shows the same acquisition in the others HI plots open.
The selected acquisition is identifiable by a green circle around it.

Classification
UNCLASSIFIED
Figure 456: Fleet HI Page – Acq. Selection
To zoom select an area of plot by drag and drop the mouse pointer, instead to reset the zoom view click
twice on chart.
Distribution Chart
Click on the flip icon placed in the upper right corner of the plots area.
Figure 457: Fleet HI – Flip view
The page automatically flips its view to another one called ‘Distribution’.

Classification
UNCLASSIFIED
Figure 458: Fleet HI Page – Distribution
The X axis is composed by total number of occurrences for each aircraft on that selected acquisition.
In this plot, the user can get out information about the density of data and understand which is the value
mainly reached by its aircraft fleet.
Contextual Menu
Figure 459: Fleet HI page – Contextual menu

Classification
UNCLASSIFIED
• Zoom; allows to reset the zoom and focus on all acquisitions.

• Chart Settings.
Figure 460: Fleet HI page – Chart Settings
• XY Plot;
Figure 461: HI and dB page – Chart with Plot

Classification
UNCLASSIFIED
• Step Area;
Figure 462: HI and dB page – Chart with Step Area
• Bar;
Figure 463: HI and dB page – Chart with Bar

Classification
UNCLASSIFIED
• Line;
Figure 464: HI and dB page – Chart with Line
• Line Symbols;
• Export; export in PNG or BMP of HI plot.


Classification
UNCLASSIFIED
• Axis X; possibility to switch the value of abscissa in Flight Hours, Acquisition Date Time and Elapsed
Flight Hours.
• Show/Hide Extended Tooltip; view or not the additional parameters in the Tooltip as described above.
parameters.
By right clicking on it, you can open again the contextual menu even if a couple of options are different
respecting the previous one.
Figure 466: QA page – Contextual menu in table

Classification
UNCLASSIFIED
1.13.5 Fleet Close Monitoring

On this page you can identify which steps are needed to monitor details of an acquisition about a fleet. The
page opens displaying a window from which the user has to select a helicopter model and the aircraft to be
viewed.
Figure 467: TVM Fleet Close Monitoring - Select A/C Model
Once the helicopters have been selected the main page is displayed.

Classification
UNCLASSIFIED
Figure 468: Fleet Close Monitoring
The main area named ‘Close Monitoring Processes’ allows to manage process to monitor one or more spe-
cific acquisitions.
• ‘Tail Id’; the tail id of the helicopter involved.

• ‘HI’; navigation button, clicking on it the user navigates directly to the Health Index Result page.
• ‘Acq.Id’; the unique id to identify each acquisition.
• ‘Description; description of selected acquisition.
• ‘Acq. Type’; the acquisition type; SYNC, THIST, FAVG or ENVE.
• ‘Status’; the status of the current process. Clicking on it, the user is able to change its status and set is as
“Closed”.
• ‘Start Date Time’; the date and time of process creation.
• ‘End Date Time’; the date and time of process end.
• ‘Start FH’; number of flight hours when the process was started.

Classification
UNCLASSIFIED
• ‘End FH’; number of flight hour when process terminates.

• ‘Planned End FH’; number of planned flight hours in order to complete the process.
• ‘Request Originator’; who created the process.
• ‘Conclusion Originator’; who set the process as closed.
• ‘Remarks’; note to insert.
Above the grid, there are two buttons needed to manage the set of data in grid.
Figure 469: Fleet Close Monitoring Buttons
In order to accept and close a process the buttons placed have the following features:
• Click on to accept the changes applied to a process. It becomes clickable when the user set as
“Close” the status of a row. Its target is to approve the change of status.
• Click on to cancel the changes applied to a process. It becomes clickable when the user set as
“Close” the status of a row. Its target is to reset the change of status and restore the previous data set.

Classification
UNCLASSIFIED
1.13.6 Fleet TUM Torque Spectra

Clicking on dialog “Fleet Torque Spectra”, the first window opens is regarding the selection of helicopter to
analyse.
Figure 470: HUMS Fleet Torque Spectra – H/C selection
In the first section of the dialog the user selects the aircraft model.
Each aircraft model is described using a set of data such as:
• The model name.

• The variant assigned.
In the second section of the dialog the user selects the desired aircrafts. The user can select all aircrafts for
a model by ticking next to “Select all Aircrafts for this Model”.
Each aircraft is described using a set of data such as:
• The tail number to identify the H/C.

• The total flight hours executed.
• The serial number assigned to the H/C.
The HUMS data will be loaded in according to the selected DSN and relative helicopter. To complete the
selection, confirm the operation clicking on the tick green icon placed in the top right corner ( ). Other-
wise,click on the cross red button to cancel ( ).

However, clicking on the SmartLink button the user is able to change the filter parameters and choose again
the data to load.

Classification
UNCLASSIFIED
Figure 471: HUMS Fleet Torque Spectra
The main area ‘TUM Torque Band’ is split into two tabs; the first, ‘Cumulated Time’ and the second, ‘Per-
centage’. By default the page always opens showing the ‘Cumulated Time’ tab.
Cumulated Time Tab
The ‘Cumulated Time’ tab shows first the fleet average for the cumulated time spent in every torque band
and then the same data for the selected H/C.

Classification
UNCLASSIFIED
Figure 472: TUM Torque Band Time
• ‘Tail Id’; the tail id which exclusively identifies the H/C(s) selected.
• ‘Engine Input Torque Bands’; the relevant engine torque band from which the data derives (36 bands
plus unavailable band).
• ‘MGBin1 TPC’; the torque path code name; this column shows the cumulated time spent in the corre-
• ‘MGBin2 TPC’; the torque path code name; this column shows the cumulated time spent in the corre-
• ‘MGBinT TPC’; the torque path code name; this column shows the sum of time relative to all three of the
previously mentioned TPC (MGBin1, MGBin2) for the corresponding torque band.
• ‘Main Torque Band [lbft]’; the relevant main torque bands from which the data in ‘MRD TPC’ derives -
measured in lbs. and feet (36 bands plus unavailable band).
• ‘MRD TPC’; the torque path code name; this column shows the cumulated time spent in the correspond-

Classification
UNCLASSIFIED
• ‘Tail torque Band [lbft]’; the relevant tail torque bands from which the data in ‘TRD TPC’ derives – mea-
sured in lbs. and feet (36 bands plus unavailable time band).
• ‘TRD TPC’; the torque path code name; this column shows the cumulated time spent in the correspond-
Percentage Tab
In the ‘Percentage’ tab table you can view data regarding the time converted into a percentage spent in
every torque band first as the fleet average and then for the selected H/C(s).
Figure 473: TUM Torque Band Percentage
• ‘Tail Id’; the tail id to identify the H/C(s) involved.

• ‘Engine Input Torque Bands’; the relevant engine torque band from which the data derives (36 bands
plus unavailable band).

Classification
UNCLASSIFIED
• ‘MGBin1 TPC’; the torque path code name; this column shows the percentage of time spent in the corre-
• ‘MGBin2 TPC’; the torque path code name; this column shows the percentage of time spent in the corre-
• ‘‘MGBinT TPC’; the torque path code name; this column shows the sum of the percentages of time rela-
tive to all three of the previously mentioned TPC (MGBin1, MGBin2) for the corresponding torque band.
• ‘Main Torque Band [lbft]’; the relevant main torque bands from which the data in ‘MRD TPC’ derives -
measured in lbs. and feet (36 bands plus unavailable band).
• ‘MRD TPC’; the torque path code name; this column shows the percentage of time spent in the corre-
sponding main torque band for the Main Rotor Drive.
• ‘Tail torque Band [lbft]’; the relevant tail torque bands from which the data in ‘TRD TPC’ derives – mea-
sured in lbs. and feet (36 bands plus unavailable time band).
• ‘TRD TPC’; the torque path code name; this column shows the percentage of time spent in the corre-
sponding main torque band for the Tail Rotor Drive.
Charts
From the ‘TUM Fleet Torque Spectra’ page you can view the data in the ‘TUM Torque Band’ area in chart
form by clicking the button or right clicking on any area of the table and selecting ‘Flip to Chart’ from the
menu which opens.
After clicking the ‘Flip to Chart’ button the area switches to a chart; the default for the initial viewing of the
chart area is set to ‘MRD TPC’ viewed in ‘Linear’ mode with the Y Axis displaying ‘Percentage’.

Classification
UNCLASSIFIED
Figure 474: Fleet Torque Spectra Chart
To view other data from the previous ‘TUM Torque Band’ table in chart form, click on the ‘Torque Spectra
Figure 475: Fleet Torque Spectra Chart - Button
When you click on this button a menu opens and you can select which torque data you would like to view.

Classification
UNCLASSIFIED
Figure 476: Fleet Torque Spectra Chart - Menu
The chart currently open is marked with a . To close a chart, click on the corresponding name in the menu.
To open one or more charts click on the relevant name on the menu. It is possible to view two or more charts
simultaneously.
Figure 477: Fleet Torque Spectra Chart – Multiple Charts

Classification
UNCLASSIFIED
It is possible to select or deselect the H/Cs you would like to view on the chart by clicking in the check boxes
in the legend on the right of the chart the charts also display the fleet average which you can select or dese-
lect in the same way.
Figure 478: Fleet Torque Spectra Chart – Legend

Classification
UNCLASSIFIED
1.14 OFF-LINE FEATURES

The Off-line plug-in allows to download data from the aircraft and process the information even with no Inter-
net connection.
The main features are:
• Full Download (when the aircraft is on ground and after a saving of Maintenance Logs on board);
• TVM QA (when the aircraft is on ground and with no need to save Maintenance Logs);
• Rotor Track and Balance;
To install the Heliwise plug-in on to your PC, navigate to the following web address:
https://heliwise.agustawestland.com/HeliwiseOfflineSetup.exe
Using the local Administrator account run the executable file and then follow the setup instructions to
install the Heliwise Offline application.
After installation a new icon to run the off-line version of Heliwise is available on the desktop.
Figure 479: Off-Line desktop icon
The following paragraphs describe the features plugged into the off-line version of the Heliwise web applica-
tion.

Classification
UNCLASSIFIED
1.15 OFFLINE DATA MANAGEMENT

Double click on the desktop icon labelled ‘HeliwiseWebSL Application’ to run the Off-line application.
The application shows the aircraft according to the on-line fleet visible to the user on the AgustaWestland
web site.
The Data Management module gives the user offline access to the following dialogs:
• DTC Download
• DSN Management
• RTB Adjustment Upload

Classification
UNCLASSIFIED
1.15.1 Offline Data Management - DTC Download
The following page is displays by clicking on the menu item ‘DTC Download’ in the Data Management mod-
ule. Here you can transfer the MDS folder from your local PC to on-line server.
Figure 481: DTC Download – exclude ESUM
You can decide whether to upload also the ESUM files. Since these files have a big size, their uploading
could have impact on the time required to complete the downloading process. Heliwise automatically
remembers the last choice.

Classification
UNCLASSIFIED
Excluding them, the ground station will upload the other data in a shorter time.
To upload the HUMS data placed on USB, SSD or file system, click on “My Computer” and select the folder
which contains the download data. You should click on ‘Select’ button when in the central area the applica-
tion shows the single files.
Figure 482: Browse folder
Once selected the folder, the web application prompts you a message in which request a user action.

Classification
UNCLASSIFIED
QUICK:automatically redirect the user to the TVM Quick Assessment (see chapter x)
RTB:automatically redirect the user to the RTB Data display (see chapter x)
CANCEL:close the form without any other actions.

Classification
UNCLASSIFIED
1.15.2 Offline Data Management - DSN Management
On the ‘DSN Management’ page you can transfer HUMS data from the aircraft DTD to the operator PC via
Wi-Fi or Ethernet.
Figure 484: DSN Management
At the top of the page the section ‘DSN Local Repository’ contains the data which has already been down-
loaded from the H/C DTD.
The grid displays the following information:
• HC Model: display the model of AC;

• Tail ID: display the Tail Code of AC contained in the downloaded files;
• Files Count: number which shows the total number of files;
• Total Upload Size [B]; the size of downloaded folder (shown in byte);
• DSN Type: the type of download recognized according to the availability of some files on board.
Full: MAINTUSG + TVMACQ+ VMRTR + MAINTTVM

Main: MAINTUSG + MAINTTVM
Quick: TVMACQ + VMRTR
Part: MAINTUSG + TVMACQ + MAINTTVM
Mixed: MAINTUSG + VMRTR + MAINTTVM
• Upload Status: the status of the download folder. “NEW” if it’s still placed in the operator PC and has
never been uploaded from this PC before otherwise the term displayed is “UPLOADED”;

Classification
UNCLASSIFIED
• Uploaded: shown when the user has uploaded the DSN;

• Start/End Download; the date and time of download from the H/C SSD to the operator PC;
• Process; these three fields contain the following buttons:
• Full; proceed with the upload of data towards the Online production server (the PC must be
connected to the Internet).The button is enabled when the download has one of the following
types: Full, Main, Part, Mixed
• Quick; navigate to the TVM QA page; the button is enabled when the download type is one of
the following: Full, Quick or Part
• RTB; go to the Rotor Track and Balance page; the button is enabled when the download type
is either Full or Mixed.
By right clicking on a DSN the system shows a contextual menu.
Figure 485: Remove Local DSN
Clicking on the “Remove Selected Item” option it’s possible to delete the DSN from the grid and erase the
physical files from the local PC.
By default, in the central area of the page, the application shows the functionalities to download data from
the DTD via Wi-Fi or Ethernet.
First of all, the user has to connect to the DTD. If the intention is to download data by means of Wi-Fi con-
nection, the PC needs to connect to the DTD network at a common Wi-Fi Access Point. Otherwise, using an
Ethernet connection, you have to plug-in the Ethernet cable into your PC once it has been liaised with the
DTD.
Secondly, ensure the type of connection, IP address, user and password are correct. As shown in the image
below, you are able to switch from Wi-Fi or Ethernet connection using the toggle switch. After that, check the
IP address with the DTD IP (by default it is 192.168.134.1 already set for the connection).
Leave the user ‘anonymous’ and no password.
Figure 486: Download a DSN via Wi-Fi

Classification
UNCLASSIFIED
Figure 487: Download a DSN via Ethernet
Finally, click on ‘Connect’ and the light indicates if the connection is successful.
Figure 488: Connected to DTD
Once it is connected, click on the ‘Download’ button to start the downloading.
Figure 489: Download Files
On the upper right side there is a progress bar showing the total progress of the operation.
The “To Transfer (n)” area contains all the files which are ready to be transferred while the area “Server Mes-
sages” reports the feedback which a normal FTP client shows when connected to a server.

Classification
UNCLASSIFIED
On the left side, the grid displays a log which traces the actions performed:
• Moving HC Failures List: moving the “AMSMNTFL….” Files to the mds path on DTD. They are ready to
be downloaded;
• Read HC Repository: checking the user permission to read the DTD content;
• Create Local Repository; creating a local repository on the operator PC;
• Download HC Maint Files; downloading the maintenance and usage files (applicable only on FULL
download);
• Download HC VM auto Files: downloading the TVM files;
• Download HC VM result Files: downloading the TVM files already processed on board;
• Download HC SUM record Files: downloading the Structural Usage Monitoring files (applicable only on
FULL download);
• Reading HC Info in Files: reading the information placed directly in the files of the download folder (appli-
cable only on Quick Access download);
• Verify HC Backup Folder: verifying the presence of the ‘mdsbackup’ folder on the SSD on board;
• Backup HC DSN Files: moving the files already downloaded to ‘mdsbackup’ DTD path. It creates a
queue consisting of all the downloaded folders;
• Closing Download Procedure: shows the result and completion of process.

Classification
UNCLASSIFIED
If the message “Foreign File found in HC” displays in the grid as shown below, the files have not been recog-
nized by Heliwise and will therefore not be downloaded from the DTD.
Figure 490: Downloading files - Foreign File found
At the end of the process, the downloaded data is shown in the grid ‘DSN Local Repository’ as a DSN row.
The last download is placed as the first entry in order to immediately prepare the data to be uploaded on the
Online server.
In the on board SSD the mds folder contains the folders “sumrecord”, “vmauto” and “vmresult” and no data is
placed inside them. The DTD is ready to store other HUMS data.

Classification
UNCLASSIFIED
Once download is completed, the DTD moves the HUMS files from the mds to the mdsbackup folder in
which the user can find the last 100 data files downloaded.
At the end of the download phase the following window will be displayed:
QUICK: automatically redirects the user to TVM Quick Assessment

RTB: automatically redirects the user to RTB Data display
CANCEL: closes the window without any further actions.

Classification
UNCLASSIFIED
1.15.3 Offline Data Management- RTB Adjustment Upload
Click on RTB Adjustment Upload. The following page will be displayed to the Operator.
Figure 494: Data Management - RTB Adjustment Upload
The operator has to fill in the IP address, User and Password fields. The user can then select whether to
upload the selected file in the RTB Adjustment Local Repository using a WiFi or an Ethernet connection
using the toggle button on the upper left side of the page.
The area in the lower part of the form displays the content of the selected file.

Classification
UNCLASSIFIED
Figure 495: Data Management - RTB Adjustment Upload - file contents

Classification
UNCLASSIFIED
1.16 OFFLINE HEALTH - TVM - QUICK ASSESSMENT
Click on the third icon placed in the main menu (Aircraft Health) and then click on ‘Quick Assessment’.
Figure 496: Off-line TVM QA Menu icon

Classification
UNCLASSIFIED
1.16.1 Offline TVM - Quick Assessment

The TVM Quick Assessment Wizard opens after selecting Health > TVM > Acquisitions Results and then
clicking on “Quick Assessment”.
The application opens a wizard to guide the user during the download of TVM Quick Assessment.
The first step contains a set of connection parameters to be filled in order to allow the connection with the
DTD through Wi-Fi or Ethernet.
Figure 497: TVM QA Wizard - Connection page
The user should ensure the IP address of DTD corresponds to one reported into maintenance manual of air-
craft. After a first setting the application will remember the right configuration.
Once the IP address, user and password are set it’s possible to continue with data download clicking on
‘Connect’ button.
Heliwise automatically downloads the required file to perform a Quick Assessment.

Classification
UNCLASSIFIED
Figure 498: Off-line TVM QA Downloading
At the end of download, the file placed on board will not be moved to ‘mdsbackup’ folder. They will be avail-
able for the next Full Download.
The QA download does not perform any backup on board.
When the application completes the download, the wizard shows the second step automatically. In this page
the user can get information about how many exceedance were detected into last time period.

Classification
UNCLASSIFIED
Figure 499: Offline TVM QA - Exceedance detection
As shown in the image above the grid shows all the exceedance found out into the last download and for
each entry the user can get more information about
• Name and Id of TVM acquisition;
• Name of exceeded Health Index.
• The threshold status on that HI and the relevant values recorded for which Heliwise reports an exceed-
ance.
• Number of red, amber and blue exceedance comparing with total samples downloaded.
The grid automatically orders the rows by their criticality (starting from Red Exceedance).
In the bottom part, Heliwise displays the total number of exceedance split for type.
To analyse the plot of each HI, the user has to navigate to the next and final step of wizard and this can be
reached in two ways:
• Right click on an exceedance and select ‘analyse’ option.
• Click on the blue arrow placed in top part of the wizard.
As shown in the image below, the third step allows to analyse the data by means of plots.

Classification
UNCLASSIFIED
Figure 500: Offline TVM QA - Exceedance plots
The application allows to analyse one TVM acquisition per time. First of all, the user can choose the acquisi-
tion using the list control placed above the plots.

Classification
UNCLASSIFIED
Figure 501: Offline TVM QA - Acq. list
On the right part of that list, the system shows the total number of exceeded HI and the status of Close Mon-
itoring task.
Once selected the acquisition, the web page loads the applicable HI on the left part of the screen. Also in
this case, each HI has a relative box which shows the number of occurrences registered.
In the bottom part of the page, the user can click on the ‘Exceedance’ button to display the list of exceed-
ance.
Figure 502: Offline TVM QA - Exceedance list
In this grid the user can get the same information shown into the previous step. To analyse directly an
exceedance, you can do right click on a row and then click on ‘analyse’. The page loads automatically the
acquisition and the HI exceeded.
At the end of Quick Assessment, you should click on green tick icon placed in the upper part of the wizard.
The application returns the user to the home page with its aircraft fleet.

Classification
UNCLASSIFIED
1.16.2 RTB Data Display

On this page it is possible to select the helicopter Configuration file for Rotor Track and Balance.
Figure 503: RTB Diagnostic – Choose RTB Config File
The Operator can select the proper Helicopter Configuration file by means of the proper drop-down list.

Classification
UNCLASSIFIED
Figure 504: Choose RTB Config File
After the selection, the Operator can accept or reject it using the relevant buttons.
Heliwise automatically plots the RTB Diagnostic view in which there is a presentation of the Helicopter
blades Track and Balance data.

Classification
UNCLASSIFIED
Figure 505: RTB Diagnostic
On the top of the form there is the overall data pane containing the Helicopter information in terms of Tail Id,
S/N, Variant, AMMC Version Running Hours and Status.
Following a drop down menu will permit the Operator to select the Main or Tail visualization.
Figure 506: Main/Tail Rotor Selection

Classification
UNCLASSIFIED
The last three panes will contain respectively the following views:
Left hand pane:helicopter measured Track and Balance graphics and values.
Central pane:helicopter adjusted Track and Balance by means of Automatic method
(left tab) or Manual method (right tab).
Right hand pane:options pane dedicated to choose Units of Measurements and adjustment Corrections or
Optimizations. In addition, the Operator will be able to Save RTB
adjustments and visualize final RTB Adjustment.

Classification
UNCLASSIFIED
1.16.2.1 Measured and Adjusted Panes (Automatic and Manual Adjustment)

On the left hand side of each graphic, a buttons toolbar will be available with following scope:
to flip view between Graphics and Tabular representation by means of the flip view button (example listed in
the picture below);
to reset zoom view
to zoom in the selected Graphic:
to zoom out of the selected Graphic;
Figure 507: Graphical / Tabular Flip View

Classification
UNCLASSIFIED
1.16.2.2 Options Pane

On the right side an Option Pane is available.
Figure 508: Main and Tail Rotor Options Pane
The following options can be selected by the Operator:
Change of RTB configuration:this drop box menu will permit the Operator to select a different RTB
configuration file.
Selected Acquisitions:it displays the type of acquisitions that can be selected using the SmartLink button.
Vibrations:possibility to change the graphical visualization in Acceleration
(g) or Inches per Second (ips). Track: possibility to change the graphical

Classification
UNCLASSIFIED
Unit of Measure; millimetres (mm) or inches.

Corrections:the Operator, clicking on the check symbol, can select or de-select the RTB adjustment in term
of Mass, Pitch Link and TAB (available only for Main Rotor).
Optimizations:this can be different for Main or Tail Adjustment. The MR Blade Measurements, present only
for the Main Rotor adjustment, take also in consideration Track Split
measurement together vibration data. If disable, the Resolve to Limits allow
to use a reduced vibration thresholds target (fine tuning). The Override TR Link
Constrains, valid only for the Tail Rotor adjustment, permits to split the
adjustment to two opposite blades and not only to contiguous blades.
Actions: It permits to save the RTB adjustment in a file that can be automatically uploaded on the helicopter at the
end of the Save procedure.
Predicted Adjustment:it displays, in tabular format, all the final calculated Main or Tail Rotor adjustments
1.16.2.3 SmartLink
Clicking on SmartLink button the RTB Data Selection form will be displayed:
Figure 509: Data Selection table

Classification
UNCLASSIFIED
Depending from the Acquisition selection following described, the Operator will be able to display or modify,
for Main and Tail rotor, each single input data parameter. In particular:
Manual Only:it considers only the manual acquisitions acquired on board.

Manual & Automatic:it both the manual and automatic acquisitions acquired on board. In case Manual and
Automatic are present for the same flight condition, the system will display
the Manual.
Averaged:it consider the average value, depending if Manual or Manual & Automatic are selected.
User Input:it allows to the Operator to manual insert all the vibration and track height for each blade and
flight condition.
The Operator can select or de-select each single flight condition by clicking on the check symbol (enable) or
X symbol (disable) on the left side of the form (Use column).
In addition, for each flight condition, the Operator can select, if available, different acquisitions by clicking on
the drop down menu of each flight condition.
At the end, the Operator can accept or reject the data modification/selection clicking on the following
buttons:
accept the modified/selected acquisitions and return to the RTB Diagnostics form
reject the modified/selected acquisitions and return to the RTB Diagnostics form.

Classification
UNCLASSIFIED
1.16.2.3.1 User Input

Clicking on the User Input form, the manual Acquisition input will be displayed:
Figure 510: Data Input table
On the right side of the form a button is available that permits to display or hide the blades and Split Track
acquisition:
valid only for Main Rotor, it permits to display and modifies all the acquisitions for each blade and the related
Track Split (display only)
it hides the blades and Track Split acquisitions.
The Operator can select or de-select each single flight condition by clicking on the check symbol (enable) or
X symbol (disable) on the left side of the form (Use column).

Classification
UNCLASSIFIED
All the field of this form can be modified except the Track Split; several option are available:
Copy Manual:all the data are copied from the manual acquisitions.
Copy Manual & Automatic:all the data are copied from the manual and automatic acquisitions.
Clear Input:set all the data at 0.
Acquisition Input:return to Data Selection visualization.
Figure 511: Data Modification table
When the blades and Track Split are display an indicator is visualized on the right side of the table:
Green indicator: the input data are coherent.
Yellow Indicator: some data are not coherent like the sum of the blades is not zero or the blades heights are
too small.

Classification
UNCLASSIFIED
Red Indicator: some data are not coherent like the sum of the blades is not zero and the blades heights are
too small.
1.16.2.4 RTB Data Modification

The Operator can modify the RTB adjustment by means of dedicated table, in order to apply the required
changes to Mass, PL and Tab orientation for the Previous Adjustment (Left hand Pane) or Manual
Adjustment (Centre hand Pane) in case the Manual Pane has been selected.
The following button can be used:
to enable edit of data inside the Initial Configuration table.
Figure 512: Adjustment table
Please note: if Tail Rotor is chosen, the table above shall only display Mass and PL data.
The following buttons can be used once data are modified:
Previous Adjustment
to return to the display mode

Classification
UNCLASSIFIED
to save the adjustment
to reset the adjustment
Manual Adjustment
to calculate the adjustment
to reload the previous adjustment values
to reset the adjustment

Classification
UNCLASSIFIED
1.16.2.5 Save RTB Adjustment

The Operator has the possibility to upload the RTB Adjustments by clicking on the Save RTB Adjustments
present on the RTB Diagnostics form.
The following form will be displayed:
Figure 513: Save RTB Adjustment
The Operator will have the possibility to save both the Main and Tail Rotor adjustments or separately Main
and Tail Rotor Adjustment by selecting the proper Radio Button on the top of the form.
In addition he shall insert a note in the proper field before to save the RTB Adjustment clicking on the Check
symbol.
In case the Operator need to reject this operation he shall press on the X symbol.
After the saving of the RTM Adjustment, the RTB Adjustment Upload menu will be displayed to the operator

Classification
UNCLASSIFIED
1.17 FAQ
To access the Heliwise FAQs navigate to the following address:
https://heliwise.agustawestland.com/FAQ.html
Figure 514: FAQ Address

Heliwise Service User Manual 386

Classification
UNCLASSIFIED
END OF MANUAL

nies') and is supplied on the express condition that it may not be disclosed to any third party, or reproduced in whole or in part, or used for manufacture, or used for any purpose
other than for which it is supplied, without the prior written consent of the Companies. Every permitted disclosure, reproduction, adaptation or publication of this document in whole
or in part and in any manner or form shall prominently contain this notice.

Heliwise Manual Rev - N PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Heliwise Manual Rev - N PDF

Încărcat de

Drepturi de autor:

Formate disponibile

THSS-189G0205X001 Rev.

Heliwise Service User Manual Page 1 of 386

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 2 of 386

1.1 CONNECT TO HELIWISE

Figure 1: Site Address

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 3 of 386

1.2 USER LOGIN

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 4 of 386

Figure 3: Insert User name and Password

Figure 4: Login Error

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 5 of 386

Figure 5: Account temporarily locked

Figure 6: Enter verification code

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 6 of 386

Figure 7: Insert user name and email address

Figure 8: Insert code

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 7 of 386

Figure 9: Unlock or change password

Figure 10: Account unlocked

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 8 of 386

Figure 11: Change password

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 9 of 386

Figure 12: Password changing

Figure 13: Password changed successfully

Figure 14: End of procedure message

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 10 of 386

After logging on correctly the user is connected to the Heliwise application

Figure 15: Connecting to Heliwise

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 11 of 386

1.3 MAIN SCREEN

Figure 16: Main Screen

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 12 of 386

1.3.1 Main Menu

Table 1: Main Menu Items

Menu Icon Description

Module dedicated to the analysis of Fleet HUMS data.

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 13 of 386

Table 1: Main Menu Items

Menu Icon Description

Module dedicated to the monitoring of failures and usage data of a

Module dedicated to the analysis of Transmission Vibration Monitoring

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 14 of 386

Table 1: Main Menu Items

Menu Icon Description

Module containing features for downloading data from the DTD to PC

Module dedicated to advanced settings.

Module addressed to resources management such as user

Opens the Help Online.

© Copyright 2017 Leonardo S.p.a., Leonardo MW Ltd, AgustaWestland Philadelphia Corporation

Heliwise Service User Manual Page 15 of 386