CAMP 30 Manual

CAMP 3.
0 Online Users Guide
CAMP Systems International, Inc.

Long Island MacArthur Airport
999 Marconi Avenue
Ronkonkoma, NY 11779
Toll Free Phone 877-411-CAMP
Phone 631-588-3200
Fax 631-588-3294
This Page Intentionally Left Blank
Table of Contents
Log of Revisions ....................................................................................................................... i
Welcome to CAMP 3.0 Maintenance Tracking Application ................................................iii
About the Maintenance Tracking Service ..............................................................................iv
Navigating the System ............................................................................................................. 2
Navigation Panel .................................................................................................................... 2
General Application Architecture ............................................................................................ 5
Manipulating Filter Panels ...................................................................................................... 6
Column Headers .................................................................................................................... 7
Report Processing.................................................................................................................. 8
Application Tools .................................................................................................................... 9
User Settings ........................................................................................................................10
Managing the Aircraft .............................................................................................................11
Aircraft Home Page ...............................................................................................................11
Task/Status ...........................................................................................................................16
Task History ..........................................................................................................................18
Due List.................................................................................................................................20
Processing Compliance Information ......................................................................................23
Generating Logs ...................................................................................................................33
Discrepancies .......................................................................................................................37
Work Orders..........................................................................................................................45
Email Alerts ...........................................................................................................................54
Managing System Fleets ........................................................................................................56
Fleet Access .........................................................................................................................56
Fleet Overview ......................................................................................................................57
Fleet Actual Times ................................................................................................................61
Fleet Task/Status ..................................................................................................................61
Fleet Due List ........................................................................................................................64
Fleet Work Center .................................................................................................................66
Fleet Discrepancies...............................................................................................................67
Fleet Update Transactions ....................................................................................................69
Fleet Management ................................................................................................................74
Engine Health Monitoring .......................................................................................................76
Engine Health .......................................................................................................................76
Fleet EHM Status ..................................................................................................................84
Appendix 1 Features Specific to Pratt and Whitney Canada engines ............................ 1-1
Appendix 2 - Features Specific to Honeywell engines ....................................................... 2-1
Log of Revisions
Rev No.
Rev Date
Description
Processed By
List of Affected Pages
3.01
3.1
01-MAY-2010
03-OCT-2010
Original Issue
CESCOM Access
Steve E. Attard
Steve E. Attard
3.1.1
3.1.2.1
3.1.2.2
N/A
3.1.2.3
3.1.2.4
3.1.2.4.1
3.1.2.4.2
3.1.2.4.3
3.1.2.5
3.1.2.5.1
3.1.3
03-MAR-2011
20-MAR-2011
24-APR-2011
26-May-2011
24-Aug-2011
30-Sep-2011
26-Oct-2011
02-Dec-2011
22-Jan-2012
25-Mar-2012
11-Jun-2012
26-Jun-2012
Minor Release
Minor Release
Minor Release
Modified Cover
Quarterly Release
Minor Release
Minor Release
Minor Release
Patch Release
Minor Release
Maintenance Log
Major Release
Ellen Lepore
Ellen Lepore
Ellen Lepore
Ellen Lepore
Ellen Lepore
Ellen Lepore
Ellen Lepore
Ellen Lepore
Steve E. Attard
Ellen Lepore
Ellen Lepore
Ellen Lepore
3.1.3.0.1
3.1.4
3.1.4.1
3.1.4.2
3.1.4.3
3.1.5
3.1.5.1
3.1.5.2a
3.1.5.2c
3.1.5.3
3.2
09-Aug-2012
20-Oct-2012
14-Jan-2013
23-Jan-2013
22-Feb-2013
09-Jun-2013
07-Jul-2013
04-Oct-2013
22-Feb-2014
21-Mar-2014
30-Mar-2014
Patch Release
Major Release
Patch Release
Minor Release
Minor Release
Major Release
Minor Release
Minor Release
Minor Release
Minor Release
Major Release
Ellen Lepore
Ellen Lepore
Ellen Lepore
Ellen Lepore
Ellen Lepore
Ellen Lepore
Steve E. Attard
Ellen Lepore
Ellen Lepore
Ellen Lepore
Ellen Lepore
3.2.0.1
EHM SP
1.10.3
07-Jan-2015
11-Jun-2015
Clerical correction
Major Release
Ellen Lepore
Ellen Lepore
All
Added Pgs 10,27,28,29.
Edited Pgs - iii, iv,3,9,12,13,14,18, 22, 23,
24, 35,45,48.
N/A
N/A
N/A
Cover Page
N/A
N/A
N/A
N/A
N/A
Edited Pgs 3,8,10,48
N/A
Added Pgs 27,28,29,A-1,A-2
Edited Pgs 3,6,9,16,18,22-23,39
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Added Pgs 34-36,54-55,72-78
Edited Pgs iii,23,27,29
Deleted Pgs B-1- B-5
Edited Pgs A-1
Added Pgs 83,84,1-1,1-2,1-3,1-4,2-1,2-2
Edited Pgs 76-82
Deleted Pgs A-1,A-2
ii
Welcome to CAMP 3.0, the newest Maintenance Tracking Application offered to the
customers of CAMP Systems International. This application has been designed using
direct customer input to offer a system meeting all of the aviation industrys
maintenance tracking needs irrespective of size and operational nature. The result is
an application which is inviting in appearance, simple to navigate, and one which
presents relevant data with minimal effort. Its web based design ensures that it is
available 24/7 from any access point in the world.
If questions arise which this document fails to address, do not hesitate to call CAMP
and ask for either a Customer Support Engineer or an Aircraft Analyst for additional
assistance. For a listing of geographic office locations nearest to you, select the
Contacts link located in the upper right corner of the application header.
iii
- Welcome to CAMP 3.0 -
Welcome to CAMP 3.0 - Maintenance Tracking Application
- About the CAMP Service -
About the Maintenance Tracking Service
The CAMP 3.0 application represents the latest in web based tracking systems which is
easily leveraged by operators to solely manage the maintenance against their fleet of
aircraft. The true value however is realized when the customer supplements this
system with the maintenance tracking service which CAMP avails with each purchased
subscription. Relying on CAMP to assist with the daily management of each aircraft is
where the bankable efficiencies can be found.
The analyst services begin with a dedicated team assigned to each aircraft model type.
Team members are considered experts on the aircraft to which they are assigned with
each specializing in a specific function making for a cohesive group fully capable of both
accurately and efficiently managing the aircraft under their charge. To better
understand the general relationship in place between the customers, the application and
the analyst reference the general process cycle shown above.
The process begins with the aircraft operator logging into the application and accessing
a Due List against a specific aircraft. This application immediately returns a screen
displaying all tasks calculating due within the projected frame of time. From this view
both Work Cards (signoff forms) and procedural text are generated which are then
disseminated among available maintenance personnel. Upon completion of the work
the signoff forms are faxed to CAMP using one of our geographically based toll free
numbers. Upon receipt of the cards, each are associated with their respective aircraft at
which time they are formally staged for processing. The analyst services team then
performs the task updates and the secondary quality review before applying the
changes to the aircrafts status. When complete, within 24 hours of initial receipt, the
system is refreshed paving the way for the next data extract on the operators behalf.
iv
Page | 0
Page | 1
When first logging into the application the system automatically directs the User to the
Home Page of the first aircraft listed within the Users assigned default fleet. For many
individuals the home page will display enough information that there will be little need to
navigate further into the system, although to access any of the systems additional
screens it is necessary to interact with the Navigation Panel located on the left side of
the screen.
Navigation Panel
Regardless as to where the user may be situated within the application, repositioning
oneself to a new screen is as simple as accessing the navigation panel located on the
left side of the system. The panel serves information using a logically organized order of
hierarchy which first presents all available Fleet listings, each containing functions
allowing users to present data at a multi-aircraft level, followed by access to all
individual Aircraft within these fleet which carry their own functions as well. The panel
also makes accessible all uninstalled spares under the control of the operator. These
take the form of engines, propellers, and auxiliary power units.
New to this application is the ability to have multiple windows open at any given time.
Within a particular fleet, aircraft, or spare the system will serve new pages in the form of
individual tabs allowing for quick access to each and a more efficient experience
extracting data from the application.
I.
Panel Structure:
Using the image on the opposite page as a reference, the Navigation Panel is anchored
on the left side of the screen and will default to the open position whenever the individual
accessing the application has access to more than one aircraft. In this example the panel
firsts lists the All Aircraft* fleet, and each aircraft within the fleet, followed by all other fleets
created by the operator along with any spares applicable to the operation via the Major
Assemblies label 1. When access exists only for one aircraft the system will default the
panel to the parked position and only aircraft information will be displayed. Please note that
the panel can be toggled by the user to both the Open/Closed positions using the double
caret located in the upper right corner of the screen.
Below is a listing of these three major components of the Navigation Panel with a brief
description of each of their underlying functions;
i. Fleet Listings:
All Aircraft* Aircraft fleets, whether they be the CAMP default or those created
by the customer, will appear first within the navigation panel for selection. The
number in parentheses directly to their right indicates the amount of aircraft included in
each. While the system will always expand the default fleet automatically, the user
The default CAMP fleet is actually referred to as All Aircraft*. The asterisk positioned at the end
provides CAMP a means to differentiate between a fleet of the same name that an Operator may have
created.
Page | 2
- Navigation -
Navigating the System
can manually expand any other fleet within the selection by clicking on the single caret
positioned to its left. Doing so will present the below listed fleet functions.
a.
Fleet Actual Times Quick access to Total Time edits.
b.
Fleet Task/Status View tasks common to all aircraft.
c.
d.
e.
f.
g.
Fleet Due List One due list which presents all due tasks for entire fleet.
Fleet Work Center Single point access to all fleet work orders.
Fleet Discrepancies Visibility into fleet-wide squawks.
Fleet Update Transactions Historic and pending update information.
Fleet Management Allows the addition of aircraft to a fleet.
h.
Fleet Groups Collection of aircraft task groups.
ii. Aircraft Listings:

Aircraft All aircraft specific to a fleet are listed directly under the fleet level
functions and may be accessed by clicking on the registration. As shown via the
navigation panel on page 4, aircraft N1260D has been selected from the My Fleet
fleet listing. Note each of the functions associated with this aircraft.
a.
Documents Operator access to all general documentation loaded by

departmental personnel, historic task & work order file attachments,
applicable elogbook records, and all compliance records.
b.
Task/Status Access to all scheduled tasks tracked against the aircraft.
c.
Due List A page within the application that will present all tasks
scheduled due within the time projections preset by the operator.
Update/Maintenance Log/MTR Allows operators to update work
accomplished information against all tasks within the application.
d.
e.
Work Orders
A workflow module within the application available
to system users.
f.
Discrepancies
All unscheduled maintenance activity is organized
through this feature.
g.
Other The Other selection contains access to additional areas within
the application that are less frequently accessed, but which remain important to
the user.
History This page serves as a storage feature for all historic task
update transactions. Users typically access this information directly
from the task via the Tasks/Status function.
Flight Log A page within the application used to store historic total
time data imported via integrated dispatch applications or by manual
input.
Task Groups A utility that provides the operator a means to

physically group tasks within the application when such groupings
make sense from a tracking perspective.
iii. Major Assemblies:

Major Assemblies Contain access to all engines, propellers and APUs that are
considered spares within the operators domain. Each described unit will list with its
own home page and respective functions identical to the aircraft listings described
above.
Page | 3
II. Accessing an Aircraft:

Upon entering CAMP 3.0, the system defaults the user to the Aircraft Home Page of the
first available aircraft within the individuals assigned default fleet. When a different aircraft
is desired the user need only choose the registration of the aircraft theyre interested in
viewing and the application will respond by opening the home page for that aircraft in place
of the first. In the below example, N1260D is being displayed.
i. The navigation panel will open with a listing of all fleet/aircraft for which the user has
permission to view. Note that N1260D is highlighted in the navigation panel and that
the system has responded by opening its respective home page in the Center
Display area.
ii. Also note that under the registration within the navigation panel all major functions
associated with the aircraft remain available. Clicking on any of these links will open a
new screen in the Center display each of which will have their own identifiable tab. 2
The CAMP 3.0 system is capable of maintaining multiple functional screens simultaneously. Each will
be associated with their own identifying tabs allowing the user to move freely among all without negatively
affecting the speed of the system.
Page | 4
General Application Architecture

- Architecture -
Functional Tabs
Navigation Panel
Filter Pane
Center Display
Reports Panel
Lower Display
CAMP 3.0 has been designed with the express intent of providing users with both a
productive and positive experience each and every time it is accessed. A quick review
of the above screen showcases the structural elements of the system and lays the
foundation of the general design for the remaining areas of the application.
I.
Navigation Panel The navigation panel is located on the left side of the screen. It is
defaulted to the open position for most users and provides direct access to both fleet and
aircraft level functionality.
II. Center Display The central display is the area that presents the page associated with the
function chosen by the user via the navigation panel.
III. Filter Pane Many of the functional areas chosen by the user will prompt a small filter
screen to open in the lower left corner of the system. This filter pane typically acts as the
search mechanism for the page chosen although it can take different forms depending on
the requirements of the page supported. For example it acts as the due projection grid for
the due list and the update tree when the update screen is enabled.
IV. Lower Display The lower display is active when tasks are present within the center
display and it is always defaulted to the closed position. Only when a user selects a task by
clicking on the task number via the center display will the system trigger the lower display to
open to present the tasks details and/or any other pertinent data.
V. Functional Tabs - CAMP 3.0 supports more than one active functional screen at a given
time by managing each through tabs for easy retrieval by the user. This feature ensures
the user will never lose track of where they are within the application and considerably
boosts system performance. Tabs are used in many places throughout the application.
VI. Reports Panel System reports are accessed via a docked menu associated with the right
side of the screen. All the user need do is click on the right side of the screen and the
panel will open to present all system reports in addition to the report queue.
Page | 5
- Filter Panels -
Manipulating Filter Panels
Filter panels provide the user the ability to input search criteria allowing the application
to retrieve the system information desired. The only action the individual need take is to
enter the search criteria and click Go to trigger the system to search and render the
results.
Due to the limited space dedicated to the panel, only a finite number of fields can fit the
screen at any given time. To accommodate each users preferences the application will
allow each to select the fields most important to them. The chosen fields will always
appear each time the filter is accessed.
I.
Altering Filter Fields In the below example the field Show Ex Items is not relevant to our
users needs and he/she wishes to swap the fields with Task Type which is much more
desirable.
i. Select caret positioned to the right of the Show Ex Items label.
ii. Search for the Task Type field within the resultant menu.
iii. Choosing the Task Type field will trigger the system to replace the field and to display
it each subsequent time the user accesses the filter.
Page | 6
- Column Headers -
Column Headers
Many of the systems data display screens make use of common column headers to
provide consistent presentation throughout the system. While these headers are
logically oriented there is also a certain amount of flexibility that is available to each user
as described within this section.
I.
Sorting By Column Header After any screen loads data

may be sorted to achieve an alternative perspective on the
displayed items. Selecting the column header will trigger
the system to sort all of the displayed records on that
selection. Toggling it again reverses the sort order. Note
that the column header controlling the sort is identified with
a caret.
II. Adding/Removing Columns The general set of available

headers typically extends beyond the default display and is
available to individual users via the menu driven off the
caret located on the right side of each header element.
Simply select the caret and a menu will appear that will
present a columns selection. Off this, the user can either
add or remove specific columns to customize the view to
their particular liking.
III. Repositioning Columns Once the desired columns are

chosen it may be preferred to reposition them in a different
order. This is easily accomplished by grabbing the header
with a left click of the mouse and dragging it to the new
location. The system will remember the new positions so
when accessed again all remains the same.
Page | 7
- Report Processing -
Report Processing
While many reports are accessible using the various menu functions integral to each of
the systems functional screens, clear and direct access to all system reports is
provided via the vertical reports strip located at the rightmost edge of the application.
The reports panel is purposefully defaulted to the collapsed position until one of its tab
elements are selected from the strip. When triggered, it will remain open and available
until the user directs his/her attention to a different area of the system.
I.
Report Categories The screen is subdivided into four

major category types. Selecting a tab associated with any
one of the categories presents a list of all applicable
derivative reports. For any one chosen, the system will
then present that reports criteria screen at the top of the
panel.
Category Types;
Status
Due
Workcard
Other
II. Report Queue The report queue is also an integral

element on this screen. Its function is to provide a
chronological list of all reports run within a seven day
window in addition to presenting the user with options to
download, print or email each using the caret associated
with the file extension of listed document.
Page | 8
- Application Tools -
Application Tools
While navigating the system, different tools are encountered that assist with controlling
the data displayed. These tools are accessible by identifying and using the icons that
have been assigned to them. Below is a listing of each of these icons with a brief
description of their function.
I.
Tool Key:
Full/Narrow Screen size adjustment.
Caret Click to expand/display additional functions.
Increase/Decrease Always associated with panel sizing.
Filter Drives a menu to filter information within the various panels & tabs.
Show/Hide Icon Set I Used to show/hide individual panes/panels.
Show/Hide Icon Set II Used to show/hide individual panes/panels.
Expand/Collapse Used to expand/collapse individual data displays.
Add New Shortcut to creating a new Work Order/Discrepancy.
Refresh Used to refresh the data within a current pane/panel.
II. Center Display - Menu Options:
View - Used to filter, sort and/or group information.
Print Menu driven options for screen associated reports.
Update/Maintenance Log /MTR Function that stages all selected tasks to the
Update screen.
Add To Used to add a task to a Task Group/Work Order.
Other Actions - Gives the ability to perform additional functions.
III. Lower Display - Menu Options:
Show All Information displayed on separate tabs may be combined to show on one
Details tab.
Action - Gives the ability to perform additional functions against the displayed data.
Page | 9
- User Settings -
User Settings
The My Settings feature is available to all users and provides the opportunity to
personalize the system to their individual requirements and tastes. Any change made
will only affect the look and feel of the application for that specific user and will not
impinge upon the settings of others from within the same organization.
I. Activating Fleet Functions The system by default loads only four fleet
functions for any newly created logon although there are more that are
readily available. Each are described in detail within the Managing
System Fleets section of this manual, reference page 56, although to
change the presentation the user must access the Fleet Links frame
under My Settings to choose what they wish to display.
II. Controlling Search Fields Also within the users control is the ability to set specific criteria
fields as their personal defaults for any search filter that is available within the system.
Page | 10
Managing the Aircraft
- Aircraft Home -
Aircraft Home Page
Each time access is gained to an aircraft, the system defaults to that aircrafts Home
Page which represents the first screen the customer has an opportunity to view. To
this end, the page has been designed to display as much useful information as possible
to help each user assess the state of that aircraft at the given moment.
I.
Panel Descriptions:
The home page is constructed of a series of smaller panels each of which present data
relevant to the user.
i. Aircraft Information Provides specific information on the aircraft to include model
type, registration & serial, important dates in addition to direct access to the CAMP
analyst responsible for the aircraft.
Page | 11
ii. Aircraft Status The status panel is very important in that it hosts vital information as
to the state of airworthiness of the aircraft at the given moment.
a. Aircraft Times The total time of the aircraft is listed at the top of the panel.
Space limitations permit only aircraft hours and landings to be directly listed
along with the date associated with the relative age of these values. To view all
additional total time values relevant to the aircraft simply position the mouse so
that it is on top of the A/C Times link. This will provide a window listing the
values for each unit of measure (UOM). Clicking the link will open a pop up that
will allow the values to be edited.
Note that the colored icon displayed in the Other column provides an
indication of the relative age of the oldest unit measure received. If anything is
older than 30 days the icon will display yellow providing the operator with a
direct indication that there are one or more values in need of revising. Keeping
these times current is critical to maintaining an accurate due list.
b. Projected The values associated with the term Projected denote the current
monthly projections associated with each UOM. These reference the
anticipated utilization of the aircraft and are fundamental to the due list
calculations. For instance when the operator runs a due list that projects out 3
months the system will take the 30 Hours per Month listed in the example and
multiply it by a factor of 3 to pull all hourly items that are 90 hours beyond the
current total time of the aircraft. Here it can be expected that the system will
display all tasks indicating hourly due values out to 145 A/C Hours; 55 Hours
Total Time plus the 90 Hour projection.
Page | 12
c. ADU In direct comparison to the projected values, the system lists the
average daily utilizations as calculated using historic data for a period that is
determined by the Operator. Also with the customers control is the choice as to
whether the aircraft will base all of its due calculations off these historic
averages instead of the monthly projections as described in the previous
paragraph. Simply contact your analyst to verify and change this setting.
Clicking on the chart icon will open a pop up of the utilization plot for the period
as specified in the window at the top of the screen.
d. Due Items When the Aircraft Home Page is first opened the Aircraft Status
panel shows a single row of data associated with the due items listing. The
example shows that there are values associated with each of the three column
header units of measure (UOM) in addition to a colored icon for each as well.
The color of the icon can be green, yellow or red depending on when tasks are
falling due within each of the categories. Green indicates no concern as
nothing is falling due within the defaulted 7 day warning window. Yellow
provides a visual warning that at least one item is coming due within the seven
day window. Red is a direct indicator that there is at least one task overdue
(OVD) within the category and warns that an action needs to be taken before
further flight activity is considered. 3
The values associated with each colored icon represent when the first task is
coming due within that UOM. Since it is likely that many tasks will be falling
due within the yellow warning window, or out into the future under the green
state, the system will always list the time associated with the earliest task falling
due within each category providing the operator with a direct indication as to
what is of immediate concern. Clicking on the icon will open a listing of the
tasks driving the icon.
A fourth state of Orange exists which indicates that a tolerance driven task is within the positive
tolerance window. This state is only relevant to aircraft whose requirements are padded by tolerances as
called out by the manufacturer.
Page | 13
It is also important to note that to the left of the due items label there is also an
icon of a plus; +. When this is clicked the system will expand the listing
providing an inventory of all of the task types assigned to the aircraft. Types
such as components, services, and inspection packages are listed among
others each of which have their own indicators and closest due values as well.
Such functionality allows the operator to identify the seven day airworthiness
status of the aircraft with nothing more than a simple click of the mouse.
iii. Calendar Tab The calendar located at the bottom of the aircraft home page works in
concert with the Aircraft Status panel in that it provides for the visual placement of
tasks coming due within a rolling 31 Day window.
a. Unit of Measure Listing - In the provided image the calendar is vertically
expanded using the + icon to the left of the registration number in the upper
left hand corner. This is evident as the icon is now displaying as a minus, -,
indicating that it can be collapsed. In this mode the system lists the Date,
Hours, Landings/Cycles, as well as the Other UOM within each of the row
headers. Note that each of these headers are color coded either green, yellow,
or red providing the same warning window indication as displayed in the aircraft
status panel as previously described. Green indicates nothing is falling due
within the defaulted seven day warning window, yellow indicates something is
due within the window and red indicates that there is at least one overdue task.
b. Calendar Cells The system will highlight the calendar cells when tasks are
calculated due on a particular date providing a direct visual indication as to the
upcoming maintenance activity on the aircraft. The cells are color coded to
provide a general indication of task type and will provide due values when the
requirement is anything other than date driven. Note in the provided example
that on September 17th at least one task is calculating due at 75 Hrs. Clicking
on the cells will open a new tab that will list all of the items falling due within the
31 Day calendar window with those tasks driving the cell in question highlighted
in blue.
Page | 14
iv. Recent Maintenance Summary The recent maintenance summary provides a

comprehensive listing of all task updates looking back 30 days. It lists the task, the
date of compliance and the transaction date and provides the user with the linked
compliance records via the icon on the right side of the screen. If the user wishes to
filter for a different date range, this can be done via the filter icon positioned in the
upper right corner of the panels header bar.
v. Program Changes Program changes record physical changes made to a task

outside of the typical update. Events such as creating or deleting a task are captured
as well as changing the requirement in any way. The panel displays the task, the date
the change was made, and provides a descriptive label as to the type of change made
as indicated in the below image. This also defaults to a 30 day window with the
additional filter capability when the operator wishes to search a specific date range.
II. Additional Tabbed Functionality:

In addition to the above mentioned panels there are also four additional tabbed panels
associated with the lower portion of the screen.
i. Major Assemblies Lists the engines, propellers, and any auxiliary power unit installed
along with its installation details.
ii. Security Displays all organizations that have access to the aircraft in addition to the
users within each having access as well.
iii. Tracked Tasks Lists all tasks from the application that have the tracked flagged set
for the express purpose of bringing these tasks into continuous view.
iv. Operator Action This page lists all of the tasks which require additional information.
These exist in either of two forms which are Insufficient Tasks, those which are
missing critical information and which cannot calculate a next due, and the New
Requirements tasks, those which require more accurate information such as the total
time of the aircraft on the effective date of an AD or simply to just bring the task to the
users attention. Resolving operator actions typically require discussion with the
aircraft analyst.
Page | 15
- Task/Status -
Task/Status
The Task/Status screen serves as the backbone of the system as all system functions
look to this area for information. It stores the most current information associated with
all routine tasks within the application which include Components, Services, Inspection
Packages and AD/SI tasks for each aircraft and major subcomponent. 4
I.
Default View:
Clicking the Task/Status link from within the navigation panel produces a new tab that
displays all of the ATA Chapters along with their individual tasks counts. Expanding a
chapter using the plus icon + will display all of its tasks.
II.
Filtering for Tasks:

Most maintenance personnel accessing the Task/Status area do so with the intent on
researching information against a specific task. The most efficient method to locate the
task is with the Task/Status Filter.
i. Example Find the Standby Altimeter Calibration
and any related tasks.
ii. Search Filters Relevant information must be
typed into one or more of the filter fields in order to
generate the desired results. The user
understands that the task would most likely be
associated with ATA Chapter 34 (Navigation),
that there is a high probability its description would
contain Altimeter and because it is a calibration it
would probably be considered a Service.
Each engine, propeller and APU has its own unique status file very much like that of an aircraft. When
any one of these major assemblies are installed on an aircraft their status blend with the status of the
aircraft so that to the end user the combined body appears to be one.
Page | 16
III. Task Structural Display:

Using the stated filter criteria the system was able to correctly identify and display task
341106, the Calibration Test of the Standby Altimeter.
i. Center Display The ATA tree listing from the original image has now been replaced
with the search results based on the filter criteria. From the below image it can be
seen that the upper center display presents the most critical task information.
Task Number
Task Description
Compliance Values
Active Interval
Next Due Values Includes maximum limits when tolerances are applicable.
Time Remaining Values
Part/Serial Information
ii. Lower Display Only when the user clicks the task number from within the center
display will the system undock and open the lower display. When this is accomplished
the application will present additional in-depth information on the task in the form of
four tabs that can actively be toggled by the individual viewing the page.
a. Detail Tab Displays references to both the requirement and procedural source
documents, update notes, attachments, and historic transaction information.
b. Related Tasks Lists all of the tasks related to the driving task in the center
display. In this example we can see that there are two tasks listed, the primary
and an associated task.
c. Req/Parts Presents all requirements assigned to the task and any assigned
allowable parts.
d. History Provides direct access to all historic updates to the task.
Page | 17
IV. Task Functions:

Functions are directly available via the Task/Status screen which can be applied against
any task displayed within the listing. It is a simple matter of highlighting the tasks to fill in
the checkboxes on the left side of the screen and then to either right mouse click to enable
an on the fly menu or to choose from the options listed within the docked menus located at
the top of the center display area.
i. Selecting Tasks:
The below methods allow the user to choose multiple task selections on the fly.
a. Mouse Select;
Directly click the checkboxes or task header bar.
Directly click task header bars.
Hold Shift key and click the checkboxes or the header bars.
Selectively depress the Control key and select random tasks.
b. Keyboard Select;
Use mouse to position first selection.
Hold Shift key and arrow either up or down.
Arrow up and down and depress the Control key followed by clicking
Enter to select random tasks.
ii. Menu Functions:
The following is a listing of available menu functions.
a. Update/Maintenance Log/MTR Sends the tasks directly to the update function.
b. Add/Edit Tasks
c. Add Tasks to Work Orders or Task Groups
d. Print Status, Work Cards, or Logbook Reports
iii. Deselecting Tasks:
Selecting tasks essentially places them in a storage area so that the user may run new
filter criteria and continue choosing different tasks. To deselect the body access the
Items Selected menu at the top right corner of the screen and choose Clear
Selection.
Page | 18
Task History
- Task History The History feature provides detailed historic information associated with all task
updates dating back to the period when the aircraft was initially activated in CAMP.
I.
Access Points Historic compliance information can be accessed from three separate
areas within the application.
i. Task/Status Bridges a path to all historic compliance information associated with the
task accessed via the History tab at the task detail level.
ii. Aircraft Home - MTX Summary Each task listing will immediately open the history tab
to display the specific compliance information associated with the referenced update.
iii. Other Menu To enter the history module with no initial point of reference click the
Other link and then History. The user will then need to search for the task using the
provided History Filter.
II.
Page Layout If the history screen is accessed from either a task or directly from the
history link the system will list each historic instance chronologically in the lower portion of
the screen. The user must choose the correct date at which time the application will
present all of the tracked information at the top of the screen.
III. History Detail The following data is offered for review as indicated in the above example.
Date Updated
Modified By The name of the individual that updated the task.
Compliance Documents Link to the documents that drove the update.
Attachments Links to attachments associated during the update.
Technician/Inspector
Labor/Cost
Installed/Removed Part As applicable.
System Notes System generated notes as well as notes contributed by the user.
Page | 19
- Due List -
Due List
The Due utility queries from Task/Status all items scheduled due within the projected
frame of time.
I.
Default View:
Clicking the Due List link from within the navigation panel produces a new tab that
displays all items falling due within the default projection parameters. As shown on the
screen above the due list filter will appear with its default settings which then renders the
task listing as shown within the center panel.
II.
Editing the Projection Parameters:

Most maintenance personnel will not be satisfied with the default projection and will look to
edit the parameters to satisfy the specific projection that they are interested in.
i. Example Modify the due parameters.
ii. Due List Filter The filter projections are very
easily modified and require nothing more than a
change to either one or more of the values already
present in the available fields. For instance
changing the value in the Project field from 2 to 3
will signal the system to project out 3 months from
the current date. It will also automatically change
the utilization values based on the projected
monthly utilizations established on the Aircraft
Home page.
Page | 20
III. Filtering the Results:

Upon rendering the due results the user has the option of further filtering the display to view
the tasks by category using the pull down located in the top left corner of the page.
i. All vs. Category Views The due list naturally displays showing all items identified as
being either overdue or coming due within the projected criteria. Many maintenance
personnel however prefer to take this view and to segregate the task listings into
smaller groups common to the requirement type. These individual requirement
classifications are referred to as Categories and are easily accessed and controlled
by the pull down as indicated by the arrow within the image below. Only those
categories that are relevant to the task body within the display will be available within
the pull down.
Note: Within the image below the task display has already been filtered by the Hours
UOM. Each of the tasks within the listing has an hourly requirement.
Page | 21
IV. Due List Functions:

Because the due list screen is structured similarly to the task/status screen the same
function properties are available on both. In the example below the menus are pulled from
the column headers to showcase the various ways in which actions can be performed
against the task listing. As mentioned earlier the user must begin by selecting tasks.
i. Selecting Tasks:
The below methods allow the user to choose multiple task selections on the fly.
a. Mouse Select;
Directly click the checkboxes or task header bar.
Directly click task header bars.
Hold Shift key and click the checkboxes or the header bars.
Selectively depress the Control key and select random tasks.
b. Keyboard Select;
Use mouse to position first selection.
Hold Shift key and arrow either up or down.
Arrow up and down and depress the Control key followed by clicking
Enter to select random tasks.
ii. Menu Functions:
The following is a listing of available menu functions.
a. Update/Maintenance Log/MTR Sends the tasks directly to the update function.
b. Add/Edit Tasks
c. Add Tasks to Work Orders or Task Groups
d. Print Due List, Work Cards, or Logbook Reports
iii. Deselecting Tasks:
Selecting tasks essentially places them in a storage area so that the user may
run new filter criteria and continue choosing different task. To deselect the
body access the Items Selected menu at the top right corner of the screen
and choose Clear Selection.
Page | 22
Processing Compliance Information

- Task Updates The processing of compliance information serves the general purpose of recording how
often a task has been accomplished and when it will again calculate a next due. Each
tracked aircraft has either one of two processes assigned to it which is controlled by the
program to which its enrolled. The traditional CAMP aircraft will follow the standard
Update or alternative Logbook Entry process while CESCOM aircraft are bound to the
Maintenance Transaction (MTR) routine.
Access Points Both types of updates, CAMP & CESCOM, can be accessed from almost any
screen within the system using similar menu features on each of the pages.
The following lists all points of access;
Update/Logbook Entry/MTR Link Prompts for a task search and manual load.
Task/Status Tasks are manually selected and automatically loaded using menus.
Task Groups - Tasks are manually selected and automatically loaded using menus.
Due Lists Tasks are manually selected and automatically loaded using menus.
Work Orders Tasks are manually selected and automatically loaded using menus.
Discrepancies Squawks are manually selected and automatically loaded using menus.
Page | 23
CAMP Update Routine Standard CAMP aircraft follow a traditional update process initiated by
the customer who delivers completed Work Compliance Forms for processing. These forms are
scanned and attached directly to the aircraft to set the stage for the analyst. While it is true that
most updates are performed by CAMP personnel, many customers choose to control this
process internally as it is simple and it allows the operator to maintain a level of control thats
important to many. This section sets the foundation for customers wishing to update tasks
directly through the application using the standard CAMP Update Routine.
I.
Page Layout Regardless as to how the screen is accessed the layout will always be the
same. The update feature is dedicated to one full page that has both an upper and lower
section.
i. Upper Section - Task addition/deletions and all global input are performed on the
upper section which will load to the lower upon command.
ii. Lower Section - This area is dedicated to the input of data specific to each task
present. The system uses indenting to show relationships between various tasks.
iii. Update Tree The update screen converts the

traditional filter pane into an Update Tree
allowing individuals to spatially visualize the
relationships between the tasks loaded to the
lower section. It also provides a method by which
to navigate tasks in the lower pane as each task
listing can be clicked which will force the lower
section to automatically scroll to the selected task
both highlighting it and bringing it into view. This
is very convenient when many tasks have been
loaded for updating.
Page | 24
II. Initiating the Update Accessing the update function from the navigation pane will open an
Update tab and prompt the user to search for tasks. To execute the search type either the
task number or the task description into the field and choose from the suggested list. As
more information is input the system will automatically narrow the selection. When all tasks
have been selected and all corresponding global input has been added manually depress
the Load button to load all of the tasks and information to the lower portion of the screen.
III. Entering Task Specific Information - The lower section will display the chosen tasks and
any additional related tasks driven by the relationship logic within the application. It is the
Users responsibility to make sure all compliance information is correctly entered before
submitting the update with the Update button at the bottom of the page.
Note: All fields listed in bold require input.
i. 262002, Cockpit Halon Fire Extinguisher Parent Task (Component):
a. Part/Serial Removed/Installed 5
b. Reason Removed
c. Warranty, Time Since, Technician/Inspector Information
d. General Notes
ii. 262012 Hydrostatic & 262014 Empty/Inspect Services (Secondary):
Both of the below services were brought into the update due to the relation logic set
within the application. Note the Include/Exclude buttons on the page allowing the
user to bypass the update for any task listed within this lower window.
If the operator subscribes to the CAMP Inventory module, the installed part information will be staged
via the suggest menus at each point of input. This will also auto-populate the Time Since Information.
Page | 25
IV. Update Processing When satisfied that all of the information has been entered, selecting
the Update button at the base of the screen will initiate the systems update routine. While
not completely necessary, it is good practice to fax copies of the compliance records to
CAMP to provide the assigned analyst the opportunity to physically attach each to their
corresponding tasks for future verification purposes. For a toll free geographic listing of
CAMP fax numbers click the Contacts link located in the upper right application header.
V.
Update Transactions Screen As soon as the system completes the processing of an

update the Fleet Update Transactions screen will present all related transactional
information in one convenient and organized view. This supplements the Recent MTX
Summary panel from the aircraft home page by presenting all of the details for each
update in one centralized location. It is accessible by selecting its corresponding link from
the fleet section from within the left navigation panel. 6
This page also serves a dual purpose for all operators taking advantage of the optional
internal QC review process. For more information reference the fleet update transactions
section of this manual on page 69.
The Fleet Update Transactions feature is a fleet function and is only available when the user has
access to more than one aircraft.
Page | 26
Logbook Entry Routine This alternative process is similar to that of the CAMP update process
except that the screens are different in both form and in sequencing. One of the big advantages
associated with this process is that the Logbook Entry serves as an online form that prints
exactly as it appears on screen allowing customers to use this as the formal logbook entry for
their aircraft.
I. Initiating the Logbook Entry The Logbook Entry process
can be initiated from almost any screen within the system.
If there is a task listing, it is likely that the user will have the
ability to load the body of tasks onto either a new or preexisting Logbook Entry. Note that within the image to the
right the system provides a Logbook Entries node within
the left navigation panel which triggers the Logbook Entry
feature when selected. In the below example the user has
chosen the node to open a new Logbook Entry which is
displaying the screen as depicted.
II.
Initiating a Task Search within the Logbook Entry With the new Logbook Entry form
opened the user will input the compliance information in the header. This includes relevant
Aircraft, Engine and APU times in addition to the date and the location in ICAO format
where the work was performed. The next natural step is then to load the tasks that have
been addressed onto the form which is done using the Add Items pull down where the
various task types are presented for selection.
Page | 27
III. Selecting and Processing a Task Choosing Component from the transaction type pull
down triggers the system to present a pop up screen that will walk the user through
identifying a specific component task and also with populating that task with relevant data.
The task type controls the available search filters making identifying the targeted task as
easy and as simple as possible.
IV. Entering Task Specific Information Upon selection of the task the user must complete at a
minimum all of the mandatory fields, however it is strongly encouraged that all fields be
addressed in an effort to be as thorough as possible. Those that are mandatory within the
Logbook Entry process will always be identified in bold.
In this example the user has chosen to update the Left Nose Gear Tire which is task
324003. Note that the application is recognizing the relationship between this component
and another that is closely associated with it which is the wheel as there is no way to
change the tire without directly affecting the wheel. Selecting this task will draw it onto the
Logbook Entry for compliance as well which is what the user decides to do.
Page | 28
V.
Logbook Entry Processing Upon sequencing through the series of task selections and
data entry screens the Logbook Entry populates with the entered data as depicted within
the below image. When satisfied that all is in order the user will choose a signoff statement
and enter the technician & inspector information accordingly. Upon completion the
Logbook Entry is submitted using the Send to CAMP & Print button which will
automatically produce the logbook entry in PDF format. This submission also stages the
data for the aircraft analyst who will ensure that the tasks are updated accordingly or the
tasks will update immediately depending on the Users profile.
Page | 29
CESCOM MTR Routine Aircraft enrolled on the CESCOM program manage task
updates using the traditional Maintenance Transaction Record commonly referred to as an
MTR. This process is similar to that of the CAMP update process except that the screens are
different in both form and in sequencing. One of the big advantages associated with this
process is that the MTR serves as an online form that prints exactly as it appears on screen
allowing customers to use this as the formal logbook entry for their aircraft.
VI. Initiating the Maintenance Transaction The MTR process
ability to load the body of tasks onto either a new or preexisting MTR. Note that within the image to the right the
system provides a MTR node within the left navigation
panel which triggers the MTR feature when selected. In
the below example the user has chosen the node to open a
new MTR which is displaying the screen as depicted.
VII. Initiating a Task Search within the MTR With the new MTR form opened the user will
input the compliance information in the header. This includes relevant Aircraft, Engine and
APU times in addition to the date and the location in ICAO format where the work was
performed. The next natural step is then to load the tasks that have been addressed onto
the form which is done using the Transaction Type pull down where the various task types
are presented for selection.
Page | 30
VIII. Selecting and Processing a Task Choosing Component from the transaction type pull
identifying a specific component task and also with populating that task with relevant data.
The task type controls the available search filters making identifying the targeted task as
easy and as simple as possible.
IX. Entering Task Specific Information Upon selection of the task the user must complete at a
minimum all of the mandatory fields, however it is strongly encouraged that all fields be
addressed in an effort to be as thorough as possible. Those that are mandatory within the
MTR process will always be identified with a red asterisk.
In this example the user has chosen to update the Left Nose Gear Tire which is task
324003. Note that the application is recognizing the relationship between this component
and another that is closely associated with it which is the wheel as there is no way to
change the tire without directly affecting the wheel. Selecting this task will draw it onto the
MTR for compliance as well which is what the user decides to do.
Page | 31
X.
MTR Processing Upon sequencing through the series of task selections and data entry
screens the Maintenance Transaction Record populates with the entered data as depicted
within the below image. When satisfied that all is in order the user will choose a signoff
statement, enter the technician & inspector information and date the MTR accordingly.
Upon completion the MTR is submitted using the Submit Button which will automatically
produce the logbook entry in PDF format. This submission also stages the data for the
aircraft analyst who will ensure that the tasks are updated accordingly.
Page | 32
- Logbook Entries -
Generating Logs
The Logbook Entries feature not only provides a means of updating tasks but also
allows existing compliance information to be generated without resubmitting the
information to CAMP.
Access Points The ability to print logbook entries for existing compliances can be accessed
from almost any screen within the system using similar menu features on each of the pages.
The following lists all points of access;
Logbook Entries Prompts for a task search and manual load.
Task/Status Tasks are manually selected and automatically loaded using menus.
Task Groups - Tasks are manually selected and automatically loaded using menus.
Due Lists Tasks are manually selected and automatically loaded using menus.
Work Orders Tasks are manually selected and automatically loaded using menus.
Discrepancies Squawks are manually selected and automatically loaded using menus.
History Tasks are manually selected and automatically loaded using menus.
Page | 33
I.
Initiating the Logbook Entry The Logbook Entry process

ability to load the body of tasks onto either a new or preexisting Logbook Entry. Note that within the image to the
right the system provides a Logbook Entries node within
the left navigation panel which triggers the Logbook Entry
feature when selected. In the below example the user has
chosen the node to open a new Logbook Entry which is
displaying the screen as depicted.
II.
Initiating a Task Search within the Logbook Entry With the new Logbook Entry form
opened the user will input the compliance information in the header. This includes relevant
Aircraft, Engine and APU times in addition to the date and the location in ICAO format
where the work was performed. The next natural step is then to load the tasks that have
been addressed onto the form which is done using the Add Items pull down where the
various task types are presented for selection.
Page | 34
III. Selecting and Processing a Task Choosing Component from the transaction type pull
identifying a specific component task. The task type controls the available search filters
making identifying the targeted task as easy and as simple as possible.
IV. Entering Task Specific Information Upon selection of the task the user will not be able to
enter any new compliance information as this is just a means of adding the task to the
logbook entry with the existing compliances. The fields displayed will not be editable.
Page | 35
V.
Logbook Entry Processing Upon sequencing through the series of task selections and
subsequent screens the Logbook Entry populates with the entered data as depicted within
the below image. When satisfied that all is in order the user will choose a signoff statement
and enter the technician & inspector information accordingly. Upon completion the
Logbook Entry is generated by using the Print button which will automatically produce the
logbook entry in PDF format.
Page | 36
Discrepancies
- Discrepancies Non-Routine tasks identified against the airframe and/or its major subcomponents may
be tracked using the systems Discrepancy feature. 7 Such items are typically
managed by customers and are to be categorized as Non-Deferred, Watchlist/Deferred
or Minimum Equipment List (MEL) items.
I.
Default View:
Selecting the Discrepancies link within the navigation panel triggers the system to open a
tab dedicated strictly to the management of system generated squawks.
II.
Access Points:
The discrepancies feature is a major component of the application and as a result there are
multiple points of access as described below.
i. Create New;
a. Left Navigation Panel Add New icon to the right of the discrepancies link.
b. Discrepancies Tab Add New Discrepancy button at the top left in the header.
c. Work Orders Feature New Discrepancy selection from the Add Items menu.
d. Fleet Discrepancies Add New Discrepancy To function.
ii. Open Existing;
a. Left Navigation Panel Via the discrepancies link.
b. Due List Display Via the discrepancy number displayed on the due list.
c. Calendar Display Via any calendar cell containing a discrepancy.
d. Work Order Via the discrepancy number displayed within the work order.
e. Fleet Discrepancies Via the fleet discrepancy link. Reference the fleet section
of this manual on page 67 for more information on this feature.
Major subcomponents are limited to Engines, Propellers and APUs.
Page | 37
III. Filtering Discrepancies:

As with all other major areas within the application, it is vitally important that the feature
provide users the ability to search for and identify specific squawks. This is accomplished
using the filter mechanism located in the lower left corner of the screen.
i. Example Identify all open squawks against the
aircraft which are related to interior furnishings.
ii. Search Filters Understanding that Equipment and
Furnishings is associated with ATA Chapter 25
choosing this as filter criteria in addition to Open
in the Status field limits the return strictly to these
items.
IV. Discrepancy Structural Display:

The above stated search produces only one open squawk associated with cleaning the
interior carpet and which is identified within the system as N1260D100305-25. Selecting
this number opens the discrepancy dedicated to its own tab. The main structural panels of
this view are described as follows.
i. Center Display The upper central display will provide a truncated list of all of the
discrepancies matching the given filter criteria. This frame is intended to present only
a brief synopsis of each item which includes the below listed elements;
Discrepancy Number - May be set to auto-generate from the application or
manually entered.
Discrepancy Description A brief narrative of the recorded issue.
Category Type Non-Deferred, Watchlist/Deferred, & MEL
Status Either Open or Closed
Interval
Logbook Times
Next Due Values
ii. Lower Display Selecting the discrepancy number from the upper display opens the
discrepancy detail within the lower panel presenting a very organized tabbed view
similar in structure to that used on the Task/Status screen.
a. Details Tab Will provide reference to all of the core discrepancy information
and access to an Action menu located in its header allowing for a series of
actions to be performed specific to the squawk. Examples include;
Edit/Delete Discrepancy
Add to Work Order
Track Items
Print Work Card
Update
b. Resolution Tab Upon completion of the squawk the resolution tab presents all
of the information associated with the disposition.
Page | 38
V.
Discrepancy Build Process:

Creating a discrepancy is designed to be as simple as possible and requires very few
steps. Upon using one of the described access points the technician simply enters the
information making sure that, at a minimum, all of the required fields are addressed. 8
When complete the Save button is selected at the bottom of the screen and the system
responds by generating the squawk.
As additional information is identified through the analysis of the issue, the discrepancy may
be further modified so that it always represents the true state of the problem at any given
moment. For instance, if it is decided that engineering needs to review the issue a notation
can be made to the Note to record the decision. If later the engineering department
produces an EO taking control of the disposition, it may be loaded to the discrepancy using
the attach feature where it will made available to anyone with access to the module.
i. Field Descriptions:
The below lists the various discrepancy fields and provides a brief description as to the
relevance of each;
Date Logged This is auto-populated by the system with the ability to edit.
Discrepancy # May be manually created or auto-generated by the application.
The latter requires setup by the system administrator.
Applies To A mandatory field that associates the squawk with the either the
airframe, engine, propeller, or auxiliary power unit.
ATA Chapter A mandatory field that uses the Air Transport Associations
referencing guide to categorize the main subject/system affected by the issue.
Sub ATA Non-mandatory ATA sub-categorizations.
Discrepancy Type A customizable pull down that lists the source of the issue
such as PIREPS, MIREPS, Shop Finding, etc.
Reported By A customizable suggest which lists the reporting individual.
Required fields are displayed in Bold throughout the application.
Page | 39
Description A mandatory free flowing text field that describes the nature of the
issue.
Note A memo field allowing the user to record any type of notation associated
with the squawk. Used often to record instructional notes and troubleshooting
activity.
Add to Work Order Directly associate any open Work Order on the aircraft by
choosing it from the pull down listing.
Labor Hours/Cost A field for estimated labor and cost.
ICAO Lists the location where the work is to be performed.
Category Classifies as Non-Deferred, Watchlist/Deferred, or MEL.
Logbook Reference References the squawks source documentation.
Attachments Allows for an unlimited number of external documents to be
associated with the discrepancy.
Page | 40
ii. Discrepancy Categories:

There are three discrepancy category selections that may be chosen all of which
control the squawks due characteristics.
a. Non-Deferred;
By design each new discrepancy defaults to the most critical category defined
as Non-Deferred. This serves to immediately call the item on the due list
effectively prompting maintenance personnel to address the issue as quickly as
possible. If not resolved by midnight on the day reported, the system labels the
item as overdue from that point forward.
Field Descriptions:
Logbook The non-deferred category presents fields associated with
recording the aircraft times at the time the discrepancy is identified. The
values can either be manually input or the user can choose to depress
the Actuals button to populate the fields with the aircrafts current total
time. Note that this input is not mandatory for this category.
b. Watchlist/Deferred;
When the squawk is one that does not require immediate attention its
classification may be set to Watchlist/Deferred. This requires the technician to
input the appropriate deferral criteria best meeting the needs of the stated
condition.
Field Descriptions:
Interval The technician specifies the interval that the system will use to
calculate a next due for each relevant UOM.
Logbook The log times are utilized to calculate a next due and are
mandatory for this classification category.
Extension Allows the due time to be extended forward.
Watchlist Number A field that provides the opportunity to record a
tracking number external to the system.
Non-Essential Equipment & Furnishings (NEF) Selecting the checkbox
classifies the item as NEF allowing the operator to defer the
maintenance as defined within their approved program.
Due Calculation The system defaults to First although Last may be
chosen as merited. This dictates when the system will present the
discrepancy on the due list by comparing the Due Point for each UOM
and triggering the display either immediately when the first UOM
calculates or afterwards after the last UOM calculates due.
Restriction/Exception This is a text field that will allow a restriction to be
entered that will follow the discrepancy throughout the system.
Page | 41
c. MEL;
When a discrepancy is generated against a designated MEL item the
application offers a means by which the system can tag the squawk with the
MEL classification. This designation differs from that of the Watchlist in that it
has the typical MEL deferral categories preprogrammed in the application as
individual tabs. The B, C, and D categories defer the squawk 3, 10 and
120 days from the logbook times respectively and the A category allows the
operator to further define any deferral criteria relevant to the condition.
VI. Discrepancy Update/Maintenance Log/MTR Process:

Upon completing the discrepancy, just like any task within the application, it must be
processed using the Update/Maintenance Log/MTR feature to formally record all final
compliance information and to change its state effectively removing it from the systems due
list. The process below highlights the CAMP Update process although it is important to
note that Maintenance Logs and MTRs are initiated in the same manner for CESCOM
aircraft. Please reference page 27 and 30 respectively, for more information concerning
the processing of Maintenance Logs and MTR forms.
i. Initiating the Update As is the case with all tasks, a discrepancy update may be
initiated directly from the Update screen, the Due List, Work Orders, or from the
Discrepancy control. In the example shown below the update is triggered by selecting
the discrepancy from the listing and depressing the Update selection located within
the header bar at the top of the screen.
ii. Entering Compliance Information Update information is entered in the same manner
as that for any task the only difference being that discrepancies have different and
unique fields not found against normal system tasks.
a. Upper Section - The top portion of the update screen is dedicated to the general
compliance information. Relevant fields include but are not limited to
compliance values, work performed both internally or externally and the
individual performing the work.
Page | 42
b. Lower Section The lower portion of the screen displays the discrepancy and a
corrective action section containing both a Corrective Action Note and an
Observation field. The note displays all of the notations made as the
discrepancy was physically worked and it allows additional information to be
added as the item is formally closed via this process. The observation field
presents two selections from a pull down. If nothing was identified during the
initial analysis of the squawk, the technician simply selects No Fault Found
which may later be used for statistical reporting purposes.
Selecting the Fault Identified option in the observation field triggers the system
to serve an altogether new field named Action that offers the opportunity to
select from the below listed options;
Expendable Installed - This selection presents an entry allowing all

expendable and consumables used during the physical compliance to be
permanently recorded and associated with the squawk.
Service Performed Provides an entry that prompts the system to

search the status for system services so that these tasks may be
updated and permanently associated with the discrepancy.
Rotable Changed Provides an entry that triggers the system to search

for installed components matching the Part/Serial input so that all
tracked component tasks may also be updated and associated with the
discrepancy.
As soon as the part information is typed into the Removed field the
system will initiate a search of the aircraft status for all the component
tasks that record the part/serial installed. As matches are identified the
system will present each prompting the user to choose what may be
relevant at which time the application will associate the task as a subitem to the discrepancy. Once loaded all pertinent update information
may be entered.
Page | 43
iii. Completing the Update This association process can be repeated many times using
the Add link within the Corrective Action block. When all are complete and the
Update button is depressed the discrepancy and each of the newly associated tasks
will be processed by the application. The system will immediately take the user back
to the discrepancy screen where its status will now be listed as C/W and where it can
be opened for review. Note that in the below example it is clear that a Secondary
Door Seal task has been permanently associated with the discrepancy.
Page | 44
Work Orders
- Work Orders To facilitate the processing of work within the maintenance environment the application
avails a Work Order feature which provides a means to schedule, organize and
complete all required maintenance on any aircraft. The feature ties directly into all of
the major functional areas of the system and is readily available to all customers.
I.
Default View:
Selecting the Work Orders link from within the left navigation panel produces a new tab that
displays a listing of all open Work Orders. Note that the filter mechanism is presented as
soon as the screen opens setting the stage for a search.
II.
Filtering for Work Orders:

The most efficient means by which to search for and access an individual Work Order is to
use the Work Order Filter located in the lower left corner of the page.
i.
Example Identify all Open Work Orders against

the aircraft that are related to the APU.
ii. Search Filters Relevant information must be

typed into one or more of the filter fields in order to
generate the desired results. In the example to the
right the user decided to input APU in the
description field and to search for all Work Orders
with an Open status.
Page | 45
III. Work Order Structure:

Using the stated filter criteria the system was able to correctly identify and display Work
Order # N1260D-26 which is the APU Fuel Tube Replacement body of work. Selecting
this number triggers the system to open the Work Order Detail which further presents data
using the traditional double panel display as described below.
i.
Center Display When physically in a Work Order the upper central display is
collapsed by default although it can be opened using the Show/Hide icon located in
the upper right corner of the title bar. When in full view this section will present
scheduling information to include;
In/Out Times The time slot dedicated to the work activity.

Job Type Scheduled/Unscheduled.
ICAO Location Where the work is being performed.
Service Center Information As applicable
Assigned Technician
Estimated Labor/Cost
ii. Lower Display The lower central display lists all of the tasks assigned to the
maintenance activity. It provides the technician the ability to add/remove tasks from
the body of work, perform functions supportive of processing each of the stated items,
all the while presenting a view into the status of the work body as the tasks are
systematically addressed by maintenance personnel. Key elements include;
a. Checkboxes Allows the user to select a task to perform an action.
b. Sequence Numbers Establishes item sequencing and relationships between
the items exclusive to the Work Order.
c. Task Type Displays the type of task listed.
d. Status The state of each item can be either Open/In-Process/Complied-With.
Page | 46
IV. Work Order Build Process:

Initiating a Work Order is a two step process that begins with the physical scheduling of a
body of work via the upper Center display. The build process is triggered upon the
selection of either the Add New icon which is positioned directly to the right of the work
order link within the left navigation panel or via the Add New Work Order menu button
located in the Work Order header. Both access points serve to open an empty work order
header directly in the edit mode. The technician need only complete the mandatory fields
although it is recommended to provide as much information as possible. 9 Selecting the
save button will open the Work Order at which time the system prompts the user to import
tasks.
Field Descriptions:
Number A mandatory field that enforces a unique number to the work order.
Date In A mandatory field that establishes the start date for the work.
Date Out Establishes a completion date for the work.
ICAO Lists the location where the work is to be performed.
Time Zone Can be set to UTC, Local to the ICAO selection, or to the
designated Base location.
Description A free flowing text field describing the nature of the work.
Post to External Systems A checkbox that triggers CAMP to export the body of
work to an authorized third party integrated application.
Service Center Information If the work is to be performed at a Service Center
the Owner/Operator may list this information.
Department A drop down selection that provides departmental information.
Labor/Costs Provide general Estimated/Actual Labor & Cost information.
File Attachment Allows the Owner/Operator to attach multiple files to the body of
work. Typical files can include engineering orders, photographs, and/or other
instructional documents.
Required fields are displayed in Bold throughout the application.
Page | 47
V.
Task Functions:
The lower Center display offers a variety of task functions that provide for the effective
processing of scheduled work. They are accessible either directly from within the header or
with a right mouse click to enable an on-the-fly menu.
i.
Selecting Tasks:
The below methods allow the user to choose multiple tasks.
a. Mouse Select;
Directly click the Task checkboxes or the All checkbox in the header
or, directly click Task Header bars
or, hold Shift key and click the checkboxes or the header bars
or, selectively depress the Control key and choose random tasks.
b. Keyboard Select;
Use mouse to position first selection
or, hold Shift key and arrow either up or down
or, arrow up & down and depress the Control key followed by
depressing Enter to select random tasks.
ii. Functions - Description:

The following is a descriptive listing of the available menu functions.
a. Adding Individual Items - Adding items to the body of the Work Order is as
simple as selecting the Add Items menu button, choosing the area from where
the item is to be pulled, and selecting the item from the resultant screen. If the
user wishes to add an item as a Sub-Item to a preexisting task within the work
order, the user must start the process by selecting the task within the work
order as that will act as the parent in the relationship.
In the below example the user selects 2006-24-01, the APU Fuel Tube Leaks
Airworthiness Directive, followed by clicking on the Add Items button in the
header. Choosing Status from the menu selection then triggers the system to
open a tasks filter screen allowing for the search/selection of the Center Fuel
Firewall Valve. Choosing the Add Sub-Item to (2006-24-01) button in the
header then adds the item, 282047, into the work as a child to the AD and lists
it as 2.2 within the work orders task sequence system.
Step #1 Select Task & Choose Add Items:
Page | 48
Step #2 Search for Desired Task & Select Using Checkbox:
Page | 49
b. Printing Prior to the physical commencement of the work, maintenance

personnel will typically look to the application for a series of reports that will
assist with defining its scope. Three such popular reports are the Work Order
Contents, the Work Order Preparation, and the Logbook reports all of which
are available off the Print menu selection.
Work Order Contents Provides a task listing of all of the work which
honors the individual relationships set within the work order. All pertinent
task information such as Task Number, Description and Next Due
are listed in the report.
Work Order Preparation Report For all of the listed items within the
work order this report will list the Allowable Parts, Required Tools, and
Access Panels in an attempt to assist with the preparation phase of the
assigned work.
Logbook A logbook report may be generated for any individual item or

all of the items within the work order.
c. Work Cards & Procedural Text Another type of report that may be generated
from within the work order are Work Cards and the Procedural Text. Work
Cards are commonly used by technicians to provide signoff information for the
CAMP Analyst and are accessible from the Print menu selection. If the
customer receives Procedural Text, this will present itself as an option during
the print. Note that the menu depicted in the below image only appears when
the Print Workcard option is selected. The Quick Print Workcard selection
simply skips the menu and produces both the signoff and the procedural text.
Page | 50
Step #2 Procedural Text & Signoff:
d. Requesting Parts - If the operator subscribes to the CAMP Inventory system,

part requests may be initiated from within the Work Order. Requests may be
made against any line item which will prompt inventory personnel to issue the
requested items electronically directly to the Work Order. This issuance serves
to stage the parts for the end user at the time of the physical task update.
Step #1 Select Task & Choose View/Create Requests:
Step #2 Complete Form and Submit:
Step #3 Initial Request Complete Part Flagged as Ordered:
Page | 51
e. Complying with Tasks within the Work Order As the work is performed on the
aircraft the technical staff may wish to update tasks individually. As the tasks
are updated their Status will change within the work order providing a visual
progress indicator to those with oversight authority.
To initiate the update the targeted tasks need to be chosen using the
appropriate checkboxes and the Update/MTR function needs to be selected
either from the main header bar or via the right mouse driven menu as indicated
in the below image. The process below highlights the CAMP Update process
although it is important to note that MTRs are initiated in the same manner for
CESCOM aircraft. Please reference page 30 for more information concerning
the processing of MTR forms.
Step #1 Select Task & Choose Update from the Menu:
Step #2 Provide all Necessary Compliance Information:
Page | 52
Step #3 Update Complete - Note the Status Change to C/W:
Page | 53
- Email Alerts -
Email Alerts
The Email Alerts feature is available to Administrators and provides the opportunity to
initiate emails based on various system activity to any contact listed within their
company.
I. Subscribing to Email Alerts Alerts can be added by clicking on the Subscribe to New Alert
button. Select the type of alert, aircraft, subscriber and desired frequency.
Alert Descriptions:
New Requirement Added Advises when a New Requirement has been added.
Monthly Reports Alerts the User when monthly reports have been generated and
are available for access within the system..
Compliance Records Indicates when compliance records have been received.
Completed Updates Alerts the user to updates that have been successfully
processed.
Service Center Assignment Advises when one or more Service Centers have
been added to an aircraft. It notifies who created the assignment, the active
assignment date ranged and the level of access that was granted.
Due List NotificationAllows the customer to set both a maintenance projection
and the frequency in days that the system will deliver the alert which displays
when the next set of tasks are coming due. The application will follow this cycle
unless something changes on the aircraft that in turn alters the due list in advance
of the next scheduled delivery. In such a case the message will trigger between
Page | 54
scheduled deliveries to provide the customer with up to date information on their

aircraft.
Revision Completions Informs the customer of all requirement and/or
publication revisions that are received and processed by CAMP against the
targeted aircraft. The name of the publication, the revision number and the date
in which it was both received and completed are all presented within the alert.
Discrepancy Additions Distributes notification as discrepancies are generated
against each targeted aircraft. The frequency of delivery can be adjusted to suit
how often the messages are triggered although the message will not be sent
when there is nothing logged during the period as it does not make sense to
deliver an empty email. Note that a setting has also been provided that will limit
the message delivery to those created using iCAMP. This is especially useful for
those customers that are only interested of squawks logged when the aircraft is
away from home.
Page | 55
Managing System Fleets

- Fleet Access -
Fleet Access
I.
Accessibility:
All system Fleets are accessible directly from the Left
Navigation Panel and are positioned immediately above the
Aircraft or Major Assembly unit specific listings. To access
any fleet or a fleet function, selecting the appropriate link
within the tree structure will prompt the system to display the
selected page. Reference page 10 for information on
enabling available non-defaulted fleet functions.
The image to the right is presenting four individual fleets; All
Aircraft*, Islip Fleet, Spare APUs, and Spare Engines. 10
II. Fleet Functions An Overview:

i. Fleet Name (i.e. Islip Fleet) Comparative due calendar/
tracked task listing. Referred to as the Fleet Overview.
ii. Fleet Actual Times Quick access to Total Time edits.
iii. Fleet Task/Status Task presentation across fleet.
iv. Fleet Due List Due presentation across fleet.
v. Fleet Work Center Fleet centric Work Order display.
vi. Fleet Discrepancies Visibility into fleet squawks.
vii. Fleet Update Transactions Historic/Pending update info.
viii. Fleet Management Non-default fleet control.
ix. Fleet Groups Collection of aircraft Task Groups.
10
All Aircraft* - This fleet is system generated and includes all aircraft within the operation.
Page | 56
- Fleet Overview -
Fleet Overview
The Fleet Overview is accessible using the link within the left navigation panel
associated with the fleet name. It will open a one month due list calendar display
against all aircraft integral to that fleet in addition to a listing of all of the tasks
intentionally tracked within the application.
I.
Calendar Display:
The upper Center panel is dedicated to displaying a rolling 31 Day Due List for each
aircraft within the fleet. The calendars that are used are identical to that which are
displayed on the Aircraft Home tab and serve to bring all of the aircraft together into one
comparative view.
II.
General Calendar Elements:

i. Status Indicators All aircraft have status indicators that present the state of flight-readiness at any given
moment using underlying system data.
a. Green No tasks are calculating due within the
defaulted seven day warning window.
b. Yellow Tasks are calculating due within the
warning window.
c. Red At least one task is overdue on the
aircraft.
Page | 57
ii. Cell Indicators

Individual calendar cells will remain blank unless the system determines that one or
more tasks are falling due on that date. When this occurs the application will change
the color of the cell based on the task type driving the due display. 11
a. Collapsed Mode When the aircraft calendar is in the collapsed mode, as
indicated by the + icon to the left of the registration number, the system
presents items coming due on a specific date only by changing the color of the
cell.
b. Expanded Mode When the calendar is expanded, as indicated by the - icon,

the system displays individual calendar rows for each unit of measure (UOM).
The row header indicates the UOM dedicated to that row and includes Date (D),
Hours (H), Cycles (C), and Other (Other) as shown in the below image. While
in this mode, when tasks are calculating due for all units except the date unit,
the system will present the due value for the task directly within the cell. This
can be seen in the below image as the system is calculating, based on
predetermined aircraft utilizations, that there is a task with a due time of 147
Airframe Hours which is estimating due on April 2nd of 2010.
c. Color Coding & Calendar Filtering The color

key that is driving the cells is accessible via the
calendar filter located at the base of the left
navigation panel. This filter mechanism, as its
name implies, provides an opportunity to control
the types of tasks that display on the calendar.
By selecting or deselecting the items in the list
the system will display only what is required.
Work Orders are dedicated to the top row
of the calendar.
Flight Activity is also assigned to its own
row although it displays only when the
system is integrated with an approved
dispatch application.
11
Note that all defined inspection packages take priority over all other tracked tasks within an individual
cell of the calendar display.
Page | 58
iii. Calendar Functions

While the calendar presents a visual indication of all items displaying on the due list, to
view a detailed listing of the underlying data the user need only click on the cell to
trigger a separate tab that will provide the task listing.
a. Prior Period The first calendar column listed directly to the right of the aircraft
status indicator represents the period prior to the current display. Since the
calendar displays a rolling thirty one days, tasks that remain unaddressed and
which eventually fall overdue will list within this period. When the aircraft status
indicator displays red the system will also place a P in this cell. Clicking on
the P will open a new tab that will list all overdue items. The below example
lists the tasks that are overdue for aircraft N1264D.
b. Current Period The current period describes the thirty one day display always
available for view. The user can click on any cell that indicates a task is due to
open a new tab that will provide the details of that task. In the example below
the user has chosen the April 2nd cell. The system has opened a tab listing all
of the tasks due for the calendar period and it has highlighted the task
associated with this date in blue.
c. Future Period The far right column of the calendar is labeled with an F and
displays the due date for the first items falling due beyond the scope of the
current calendar view. Selecting this date will open a new tab that will list these
future tasks. Selecting the April 20th date for N1260D prompts the system to
display the below task listing with the targeted task highlighted.
Page | 59
III. Tracked Tasks:

The lower Center panel on the Fleet Overview screen displays all of the tasks that have
been flagged as Tracked for each aircraft within the fleet. It is up to the operator to
determine how frequently to monitor these tasks although the feature is very useful with fast
paced operations.
Field Descriptions;
Reg No Lists the specific aircraft that the task is associated with.
Item # Lists the manufacturers task number.
Task Type Displays the type of task; i.e. Component (PN), Service (SMC),
Inspection Package (PKGOP), Airworthiness Directive (AD), Service Bulleting (SB),
Discrepancy (DISC).
Description Lists the manufacturers description of the task.
Next Due Indicates the next due calculation of each task.
Due In Displays how much time is remaining for each UOM of each task.
Page | 60
- Fleet Actual Times -
Fleet Actual Times
The Fleet Actual Times feature offers the operator the opportunity to monitor and/or
edit the total time of any fleet aircraft, its installed engines, propellers and auxiliary
power unit all from one convenient location. Spares may also be managed through the
default fleets directly below the Major Assemblies classification.
General Functionality:
Selecting the Fleet Actual Times link from within the left navigation panel triggers the system
to open a tab that will present an alphanumeric list of all contained aircraft each of which may be
further expanded to bring the total times of each into clear view. Choosing the corresponding
Edit button offers a menu allowing the values to be manually edited. Presenting all fleet
aircraft in one convenient location makes the daily management of the aircraft times both simple
and efficient.
Page | 61
- Filter Task/Status -
Fleet Task/Status
The Fleet Task/Status feature provides an opportunity for an individual to search for
and display specific tasks across all aircraft within the fleet. This feature is especially
useful when it is necessary to review/compare either the last compliances or the next
due of targeted tasks across all aircraft within the fleet.
I.
Filtering for Tasks:

Most maintenance personnel accessing the Task/Status area do so with the intent on
researching information on a specific task. The Fleet Task/Status Filter, like all filter
mechanisms, was designed to be intuitive to use making locating tasks a simple matter.
i.
Example Identify that next due information

associated with the right engine fire extinguisher
hydrostatic test.
ii. Filter Criteria - Relevant information must be typed

into one or more of the filter fields in order to generate
the desired results. In the example provided, the user
has entered Hydro in the description field and
Package in the task type field which rendered both
the left and right engine hydrostatic inspection
packages for two of the three aircraft in the fleet.
Upon reviewing the task numbers, 059223L and
059223R, the filter input is then modified by placing
the % symbol in the item number field followed by
an R to further refine the search so that only the
right codes remain. 12
12
The % symbol is used as a wildcard in all CAMP applications. It simply means everything and is
equivalent to the asterisk as used within Windows based applications.
Page | 62
II.
Fleet Task Display:

Using the described filter criteria the system correctly lists the Right Engine Fire Bottle
Hydrostatic Test tasks, 059223R, for two aircraft within the fleet. Because the third aircraft
is not equipped with the traditional fire extinguishing setup, it is eliminated from the search
results. The user now only need analyze the data as it is presented on screen.
i.
Upper Center Display Displays the task listing sorted by item number in the same
manner that the Task/Status feature is displayed at the aircraft level. One noticeable
difference however is the inclusion of the aircraft registration number within the listing.
Relevant Fields;
Aircraft Registration
Task Number
Task Description
Compliance Values
Active Interval
Next Due Values Include maximum limits when tolerances are applicable.
Time Remaining Values
Part/Serial Information As required by task type.
ii. Lower Center Display When it is necessary to further research task data, selecting
the task number serves to undock the lower central display providing direct access to
the tasks core tabs.
a. Details Tab Displays references to both the requirement and procedural
source documents, update notes, attachments, and historic transaction
information.
b. Related Tasks Lists all related tasks.
c. Req/Parts Presents all task requirements and allowable parts.
d. History Provides direct access to all historic task updates.
Page | 63
- Fleet Due List -
Fleet Due List
The Fleet Due Utility provides insight into all due items affecting the body of fleet
aircraft via a single tab view.
I.
Default View:
The fleet due utility is accessed by selecting the Fleet Due List link within the fleet area of
the left navigation panel. The systems projection parameters default to a seven day view
and the resultant return lists all rendered tasks in order of priority as this is the standard
used throughout the application. The principal difference with the fleet view as compared to
the equivalent aircraft specific view is that it will display the aircraft registration number to
the left of each task.
II.
Editing the Projection Parameters:

Altering the projection parameters to accurately display pending work against the fleet is
identical to the same activity at the aircraft level the only difference being that at the fleet
level the system will not display the projection parameters as these differ across the various
aircraft. As a result these fields remain hidden from the Fleet Due Filter.
i.
Example Extend the projection parameters from the

7 Day default to a 3 Month outlook. This will help
management personnel plan for long term
maintenance.
ii. Fleet Due Filter - The filter projections are easily

modified by changing either one or more of the values
already present within the fields displayed. In this
example, the value in the Project field must be
changed from 7 to 3 and the Days selection must
be changed to Months. The user may also
alternatively choose to change the projection date
when something specific is desired.
Page | 64
III. Fleet Due List Display:

The result of the extended projection renders significantly greater results. Note that the
task count increases from seventeen tasks to twenty eight tasks spanning the two aircraft
within the fleet.
i.
Grouped By Aircraft By default the system displays the fleet due list grouped by
aircraft with all internal task sorting by estimated due date from the earliest to the
latest due.
ii. Changing the Display View To change the sorting or grouping options for a different
view simply use the View menu selection to choose one of the options.
Page | 65
- Fleet Work Center -
Fleet Work Center
The Fleet Work Center provides a window in which all scheduled Work Order activity
may be viewed across all fleet aircraft.
I.
Default View:
This utility is accessible via the Fleet Work Center link within the fleet area of the left
navigation panel. On initial access the page defaults to all open work orders grouped first
by Registration and then by Date In.
II.
Work Order Functions:

All of the work order functions available at the aircraft level are also available at the fleet
level.
i.
Adding Adding a new Work Order can be performed by

selecting the Add New Work Order button from the top
menu bar. This presents a menu that requests the user
choose an aircraft upon which the system will open a
new tab specific to the new work order.
ii. Open Existing Simply clicking on a work order number

will open it in a new tab providing users with the same
functionality presently available at the aircraft level.
Page | 66
- Fleet Discrepancies -
Fleet Discrepancies
Managing discrepancies across a fleet is an extremely simple and efficient process

using the Fleet Discrepancies feature. This area is dedicated to system squawks and
affords the individual in charge of the airworthiness status of the organizations aircraft a
comprehensive oversight tool that allows for the quick analysis and disposition of
anything written up against fleet aircraft from the field.
I.
Accessing Fleet Discrepancies:

As with all fleet functions this tab is enabled by selecting the Fleet Discrepancies link
which is listed as one of the selectable nodes within the left navigation panel under the fleet
tree.
II.
Default View:
The view is very similar to the discrepancy listing at each
individual aircraft and differs only via the reference to the
aircraft. The default view includes filtering the list to include
only those that are Open.
III. Filtering for Discrepancies:

Upon access, maintenance personnel have the option of
controlling the records returned by the system using the
provided filter mechanism. In this case the planner decides to
limit the view to only deferred discrepancies against N1260D
by selecting the registration number in the Reg # field and
the Non Deferred checkbox provided by the system.
Page | 67
IV. Fleet Discrepancy Display:

Using the described filter criteria the system correctly lists both the Fire Detection False
Alarm squawk identified as discrepancy number N1260D-100406-26 and the Pitot Tube
Cover item listed as item N1260D-100329-26 as well.
i.
Upper Center Display The system will list all of the discrepancy records fitting the
filter criteria. All functions remain available via the header menu or the right mouse
generated menu functions.
ii. Lower Center Display To physically open the discrepancy simply select the
discrepancy number from the upper display. The system will then undock the lower
display to present the discrepancy detail as indicated in the below image. For more
information on managing discrepancies please reference the section of this document
dedicated to Discrepancies beginning on page 37.
Page | 68
- Fleet Update Transactions -
Fleet Update Transactions
Of vital importance to any flight operation is the ability to quickly identify and review the
details associated with historic task updates. While the Recent MTX Summary on the
aircraft home page presents a truncated view of the same information, a more
advanced view with filtering capabilities is immediately available using the Fleet Update
Transactions feature.
I.
Reviewing Processed Update Transactions:

All customers with access to more than one aircraft have the ability to utilize the Fleet
Update Transactions feature as presented within the left navigation panel. This feature
provides a means by which to identify historic instances of task updates the details of which
can then be opened for further analysis. This is very useful when there is a need to clearly
review the data which drove an update that may be in question. Users may also leverage
the logbook generation feature to create historic log entries available here as well.
i.
Default View - When the screen is first enabled it opens displaying all fleet
transactional information for a period looking back 30 days grouping all listed tasks by
aircraft. The system typically presents all Applied transactions when first opened
unless the user is a designated QC Reviewer at which time the system defaults the
task listing to those which are in the Pending state. For more information on the
quality review process reference Paragraph II on page 71.
Page | 69
ii. Transaction Search & Identification - When a specific instance of a task update is
sought the filter mechanism located in the lower left corner of the screen may used to
query specific instances of task updates as the default view will not always
immediately present the targeted transaction.
a. Example In this example the technician is
interested in identifying the last instance of the
left outboard tire change on aircraft N1260D.
b. Update Transactions Filter To query the
system to present the correct transactional
record the user selects the serial number
associated with the aircraft, inputs 32 in the
item number field as this will limit the search
results to only the landing gear tasks, chooses
the Items Applied checkbox and selects
ATTAS6454 from the inserted by pull down
knowing that it was this individual that
processed the update.
iii. Transaction Presentation - The above filter criteria produces the below record set.
Note that the tire has been changed more than once so it is important for the user to
identify the correct transactional instance of the update. Selecting the expansion icon
(+) associated with the 03-APR-10 transaction presents the detailed results of the
information used to drive that instance of the task update. The example below
indicates that the left outboard tire, task 324011, on aircraft N1260D was replaced on
24-FEB-10 at 134:40 A/C Hours and 130 Landings. The technician and the inspector
responsible for the work are identified along with the installed and removed tire
part/serials.
Page | 70
II.
Update Review Optional Internal Quality Process:

An optional feature available to operators that have internally defined quality processes
allows select users the ability to review, edit and accept all updates performed within their
organization. With this feature enabled, the system presents designated review personnel
a modified update screen supportive of this process. The Fleet Update Transactions
feature performs the additional purpose of acting as the portal to launch this review process
for all designated reviewers.
When properly set by CAMP, all individuals within an organization will fall under one of two
update categories; Primary Level Maintenance Technicians perform the initial task update
which is then staged for the Secondary Level QC Inspectors who will review and either
accept or reject the input. Only upon quality acceptance will the system process the task
update.
i.
Step #1 - Primary Level Maintenance Technician Update - The process of updating

tasks for the primary level maintenance technician is almost identical to that which
requires no review. The only deviation is that the system only partially processes the
updates by placing them in the Pending state for the secondary level quality review.
When this occurs the maintenance technician can then access the fleet update
transactions screen to view the tasks and to run logbook reports as required. Note
that in the below image the status of the updates is set to pending.
For more information on the initial update process, reference the Task Updates
section of this manual on page 23.
ii. Step #2 Secondary Level QC Inspector Review It is now the responsibility of the
secondary level quality reviewer to monitor the system and to initiate the review
process against all Pending updates as presented by the system.
Page | 71
a. Pending Updates - Monitoring - This can be accomplished by continuously

monitoring the fleet update transactions screen or by keeping a close eye on
the registration listings in the left navigation panel. Anytime an item is staged
for review the system will place the image of a clock next to the aircraft
registration. Positioning the mouse over the clock will display the underlying
task count. Selecting the clock will immediately launch the Fleet Update
Transactions screen specific to that aircraft as displayed below. The reviewer
only need select the tasks to launch the update review screen.
b. Pending Updates - Review and Acceptance/Rejection - As soon as the tasks

that are targeted for review are selected the system will load each, along with
all formal relations, onto the update review screen. Quality review personnel
now have full insight into the data that was input during the initial technician
level update. Each task update can be accepted as is, edited and accepted, or
altogether canceled based on the reviewers best judgment.
b1.
Task Review;
Editable Fields All of the fields on the update screen are now under
the direct control of the reviewer and may be edited.
View Errors/Warnings All errors and warnings experienced by the
primary level technician along with their responses to each are
presented to the reviewer who has the ability to alter the actions
taken on each.
b2.
Task Actions;
Accept Button Triggers the system to accept the update along with
all of the corrections performed during the review process.
Reject Button Serves to terminate the update action against the
task and each of its direct relations.
Pending Button This is only used when the reviewer decides that
the task should be reviewed at a later date and time. It simply places
the task back into the staging queue for another separate and full
review.
Page | 72
b3. Processing the Updates Depressing the Update button at the base of
the screen will signal to the system to process each of the listed tasks as
per the button settings along with any data modifications made by the
reviewer. As long as the update is not altogether cancelled, or the
pending button is not selected against any individual task, the system will
then change the status listing of each transactional listing on the fleet
update transactions screen from pending to applied.
Page | 73
- Fleet Management -
Fleet Management
Fleet Management allows users to control the various fleets to which they have
access.
I.
Accessibility:
Default fleets created by CAMP are intentionally locked down and are not equipped with
this feature. The default fleets are strictly limited to the All Aircraft* and the Spare
Engines, Propellers, and APU fleet.
II.
Management Functions:
Users have the ability to create a new fleet and/or edit existing aircraft counts within a fleet
to the extent permitted by their security privileges.
i.
Fleet Creation
To create a new fleet access the chevron to the right
of the Aircraft label at the top of the left navigation
panel. This will provide a menu that will allow the
user to initiate the fleet build process.
ii. Adding/Removing Aircraft

This is a two step process requiring the user to select either the Remove Items or the
Add Items icons to manipulate the aircraft within a fleet. The top panel represents
what is included within the fleet and the bottom panel lists the exclusions. Please
reference the image at the top of this page.
Page | 74
Page | 75
Engine Health Monitoring

- Engine Health Monitoring -
Engine Health
CAMP has created an integrated system that allows aircraft operators to access their
aircraft engines trend and health information alongside their aircrafts maintenance
information. This is a significant extension of the CAMP Maintenance Tracking
application and provides you direct access to your engine health status as well as
detailed engine performance, fault code and oil13 analysis. You also have the ability to
upload your engine data files directly through the application. Finally, it provides a
means by which you can subscribe to receive a variety of engine related email alerts
and also interact with your EHM analyst through the system as actionable
recommendations are generated and corrective actions are taken.
I.
Aircraft Home Screen:

i.
13
Lets begin with what you

as the customer will see
when first logging into the
system. The CAMP MTX
application will always
initially place you on the
Aircraft Home screen of
your aircraft or of the first aircraft listed within your fleet when you are operating more
than one. It is this screen that clearly presents the engine health state for each
installed engine within the newly developed Engine Trend Status panel as indicated
See Appendix 2 for details
Page | 76
within the image above. This panel is being placed in the position of the Program
Changes panel on the right side of the screen which in turn has been repositioned at
the bottom of the screen alongside the Calendar tab for all EHM designated aircraft.
This new panel serves to present you with your critical engine health information for
each installed engine through the implementation of colored icons which can range
from green through red based on what is taking place on each engine at that point in
time.
The colored status indicator represents the state of well-being of the engine at the
moment in time that the screen is opened. It is based upon the EHM analysts
interpretation of the recorded operating parameters of the engine as defined by the
engine manufacturer. The green state is the most desirable and will be the most
common as it is a positive affirmation that everything is normal with the engine. If there
is a situation detected by the analyst where any single engine parameter, or
combination of parameters, begins to deviate away from the designated baseline, the
green state will likely be changed as defined by the guidelines established by the
engine manufacturer. This is simply a warning state which will be issued in conjunction
with a recommended corrective action by your EHM analyst consistent with the OEM
Instructions for Continued Airworthiness (ICA). All EHM recommendations that are
made in conjunction with state changes are designed to mitigate the exceedances
before they actually become costly problems. When the corresponding corrective
actions do not produce the desired effect of drawing the engine back into its designed
baseline configuration, the warning states will likely be maintained to require additional
actions. The current state is reflected through the Engine Trend Status panel on the
Aircraft Home screen for each EHM participating aircraft.
II. Engine Trend Status Screen:
While the view on the Aircraft Home screen is useful, it provides little more than the
current state of each engine. When there is a state degradation, you will be obligated to
select the engine to open a new tab dedicated to presenting all of the in-depth EHM
information referred to as the Engine Status view.
With the Engine Status screen open the options of reviewing and taking action on your
analyst recommendations are made available as well as monitoring the results of the
engines oil analysis program and the ability to review any recorded exceedances for the
engine. Each is addressed through sub-tabs on the screen respectively titled Trend
Status, SOAP 14 and Fault Code.
Access to each OEM Manufacturers Troubleshooting Portal15 is made by selecting the
link in the upper right corner of the screen.
14
15

Page | 77
III. Responding to a Trend Alert:
i.
Trend Status - As soon as you drill into the engine and land on the Trend Status subtab you are provided with immediate access to the corrective action recommendations
as generated by the EHM Analyst. Here you are presented with a listing of all required
actions as determined by the EHM analysts in addition to the history of actions that
you have taken and pushed back to them as well. The page also lists the analysts
historic acknowledgements of the actions taken throughout the operational life of the
engine.
The view that will most likely be frequently visited on this page will be the Action
Required view. This is where you will come to access the analysts recommendations
and the manufacturers troubleshooting portal so that you may take the necessary
actions to bring the engine back into conformity. When completed the expectation is
that you will respond through the system using the Trend Response feature which
will communicate the actions that you have taken.
Page | 78
Higher on the Trend Status sub-tab, you have access to the same chart data that the
EHM analyst actively reviews via the Plot hyperlink. This opens a second parallel tab
that will provide you with a view into the data that has been trended over time.
ii. Fault Code - Back on the Engine Status screen positioned to the right of the Trend
Status tab is another sub-tab that can be directly related to the recommendations as
provided by the EHM analyst. It is referred to as the Fault Code view and it lists all of
the historic exceedances as recorded by your engine hardware. The screen sorts by
upload date and provides a brief description of the nature of the fault detected. 1617
16
17
Severity status for Fault Codes is only available for Honeywell engines.
Fault Codes status only affect the overall status for Honeywell TFE731 engine models.
Page | 79
IV. Access to Engine Trend Reviews:

The user will have the ability to review the EHM status of the aircraft each time the engines
are reviewed by the analyst. A new report will be generated and stored for the individual
aircraft each time a review is conducted, providing the user with a historical log of the health
of the engines.
i.
Documents - The user can download, save, and print any of the EHM Reports stored
within the Engine Health Monitoring Review Log sub folder beneath the Documents
link.
V. Instantaneous EHM Fleet Summary Reports:

Users can now generate a report that gives them a quick overview of the EHM status of
their fleet. To generate the EHM Fleet Summary Report, click Status from the Reports
bar, select the Reports Menu, click EHM Reports and then select EHM Fleet Status
Summary. Click on the Go button to generate the report.
Page | 80
VI. Submitting EHM Data:

The system permits EHM data submittals in any of three formats 18 to satisfy your needs
based upon the configuration of your aircraft. Parameter data may be recorded for your
engines manually via your cockpit instrumentation and entered directly into the application
or the information can be captured automatically by installed equipment where it will only be
necessary to upload a file into CAMP MTX using your laptop.
i.
File Upload - If you are configured with automatic data transmission hardware 19, this
unit will gather the necessary electronic files and load them to the system without any
manual intervention.
If you are configured with automated data recording hardware, instead of sending
your downloaded files to the EHM analyst, you have the capability to upload the files
directly into CAMP MTX using the File Upload feature. To complement the upload
there is also a history tab that provides a historic listing of all files uploaded over time.
ii. Cruise Trend - When you manually record your data, you have the option of delivering
your completed forms to Trenddata@campsystems.com or you can enter the
information into the system using the Cruise Trend feature of the application. By
selecting the Cruise Trend node from the left navigation panel the system allows you
to directly enter your recordings via a system driven form. Simply enter the
information and complete the process by selecting the Submit button at the bottom of
the form
18
19
Manually entered data is not available for PW300 series engines.

Automatic data transmission hardware (FAST/DTU) are only available for select P&WC engines.
Page | 81
VII. View Upload History:

The complete history of the files that were uploaded to the system is also visible at this
location. It can be accomplished by clicking on the View Upload History tab.
This feature will default with the aircraft registration number pre-populated as well as the
last month of data in the range section. It is possible to refine the file search by using the
other filter parameters.
The file inputted to the system can be downloaded by clicking on the file name.
VIII. Engine Calibration Run and Power Assurance Check:

The EHM system makes it possible to enter Engine Calibration Run and Power Assurance
Check 20 information directly in the application. The location to do this is found in the Ground
Run tab nested in the Submit Trend Data tab.
20
Engine Calibrations and Power Assurance Checks are only available for PW300 series engines as well
as all Honeywell engines.
Page | 82
IX. Email Notifications:

The addition of the EHM integration has also permitted the expansion of the Email Alert
feature within the CAMP MTX application to allow for EHM specific email deliveries. The
engine trending alert emails are controlled through a separate frame located at the bottom of
the screen. Administrators can access the feature, select an alert type and assign users to
receive one or all of the available email types as defined below.
i.
Data Receipt Alert - This will trigger an email to each assigned user as data is
received into the system regardless as to the delivery channel or who submitted the
entry.
ii. Trend Alerts - These alerts are delivered each time the status of the engine has been
changed. The email notification provides you with the necessary details of the status
change.
iii. Trend Update - To compliment the Data Receipt Alert this alert delivers a message
each time the trend data is loaded to the application and processed by the EHM
analyst.
iv. EHM Fleet Status Report - Customers have the means to establish an email delivery of
an Engine Status Report that will provide a one page view into the state of each
engine on the aircraft, the latest comments as provided by the EHM analyst and a
summarized plot history of the engines over their life on the EHM program.
v. EHM Fleet Status Summary Recommended for large fleet operators, this report
shows the summary of the engine status (by color only) of the entire fleet.
vi. EHM Fault Code Alert 21 - The Options column forces the user to customize which
fault codes they would like to receive the alert for.
vii. Deficient Data Alert - In development. This report will send a notification to customers
who have not provided EHM data within the specified timeframe.
21
This is only available for PW300 series engines.
Page | 83
Fleet EHM Status
While the information at the aircraft adequately presents you with your EHM status
information for the individual aircraft, the Fleet EHM Status screen is available to view
multiple aircraft at the same time when you operate a fleet of any material size.
I.
Default View:
The Fleet EHM Status screen is available as a node within the Fleet section of the Left
Navigation panel and summarizes your engine trending information for all of the EHM
designated aircraft contained within the fleet. It provides a listing of the aircraft and their
engine states in addition to the historic trend recommendations. The data on this screen is
presented by a series of numbers which drive detailed views of the aircraft within the lower
half of the screen. These numeric values represent the worst case scenario for each aircraft
of the indicated model type. For instance if a particular model is presenting the value of 2
under the red icon at the top of the screen, it means that there are two aircraft with at least
one installed engine in a red state. On the same aircraft if there is another engine that is
green, this will not be presented at all within the top portion of the screen as the aircraft is
already accounted for through the engine that has been determined to be in the critical red
state. As can be easily seen, it is important to note that this area is dedicated strictly to
aircraft counts. Therefore in the image as provided, we can see that there are two Hawker
750/800XP/850XP /900XP aircraft in the fleet which has two engines in the red state and
one in the green as projected via the lower part of the screen. In the top left we see that the
model type is listed with only a 2 count under the red column indicator. This is correct as
there are only two aircraft in the fleet and these two aircraft have one-or-more engines
that are in a critical red state.
Since the fleet level screen is primarily intended to provide only an overview, more detailed
information on any engine is realized only by selecting the engine serials as displayed
within the lower panel. When accessed in this manner the Trend Status tab for the engine
will be opened allowing you to research the data driving that engine while at the same time
maintaining the fleet view.
Page | 84
Appendix 1
Appendix 1 Features Specific to Pratt and Whitney Canada engines

ADAS Logs
Aircrafts equipped with Aircraft Data Acquisition System monitors will be able to see the monitor
recording details using the ADAS Logs 22 tab nested in the Other tab.
- Appendix 1 The basic Information front page gives a broad description of the aircraft details as well as a
summary of the Upload Date, Trend Date, Event Date, Eng. Run Date, TSN 23 and Flag Date.
Upload Date
Clicking on this date brings you to the View Upload History tab with an initial filter of 1 month
for this specific engine. See section View Upload History in main body for details.
Trend Date
Clicking on the Trend Date loads a tab on the Asset Transmission Details section that
outlines the raw data that was inputted for a given initial filter of 1 day for that aircraft. Clicking
on the Graph Trends button brings you to the regular EHM graph.
22
23
ADAS Logs are only available for aircraft equipped with PWC Monitors.
TSN (Time Since New) is computed by the monitor and may not be the same as the TSN of the engine.
1-1
Appendix 1
By scrolling down and going to the rightmost column and clicking on the View tab for Sensor
Details, you can see complete details of all the sensors that were captured by the monitor. It will
open up a new tab under the Asset Transmission Details called Cruise Trend
Event Date
Clicking on the Event Date loads all the event information for the most recent date in the Asset
Transmission Details section. Clicking on the Plot icon will show the event graph.
1-2
Appendix 1
Eng. Run Date

Clicking on the Engine Run Date will populate a table in the Asset Transmission Details section
outlining the details of the latest engine runs. It pre-populates a list for the last month of data.
The ADAS asset name only shows a date for the Upload Date and Flag Date. The Upload date
for this asset indicates the last time the ADAS connected to EHM. The Flag Date will show basic
details of Flags that have been recorded on the ADAS. These relate to the performance of the
monitor and not the performance of the engines.
DTU Logs
The DTU Logs 24 page, nested directly above the ADAS Logs, shows the details of the DTU unit
itself regarding the installation ID as well as all relevant upload details.
24
DTU Logs are only available for aircraft equipped with this specific PWC Monitor.
1-3
Appendix 1
P&WC Alert Status Definitions

GREEN: Engine trends do not show any issue.
BLUE: Gradual trend shift has been detected. Shift is considered normal deterioration therefore
no engine troubleshooting required. Alert issued for information purposes only.
BROWN: A Data quality issue has been detected. Recommend instrumentation troubleshooting
at next convenient opportunity. B] Unreported maintenance is suspected of causing trend shift.
Recommend reporting of recent engine maintenance at next convenient opportunity.
YELLOW: Trend shift has been detected. Recommend engine troubleshooting to confirm trend
at the next convenient opportunity.
RED: Significant trend shift has been detected. Recommend engine troubleshooting at earliest
convenient opportunity.
1-4
Appendix 2
Appendix 2 - Features Specific to Honeywell engines

SOAP Analysis Tab
- Appendix 2 -
Performing regular oil analysis testing is often an integral part of an engine health
monitoring program as
determined by the
engine manufacturer.
Samples are typically taken
at scheduled maintenance
visits and shipped to
manufacturer certified
laboratories so that they can
be analyzed for materials that
may be indicative of
premature engine wear. The
findings are then
electronically delivered to CAMP
and presented through this tab.
This view not only provides access to your historic SOAP data, it also permits you the ability
to monitor the samples as they are being processed by the lab. When complete, the results
will be posted on the left side of the screen.
This view not only provides access to your historic SOAP data, it also permits you the ability
to monitor the samples as they are being processed by the lab. When complete, the results
will be posted on the left side of the screen.
2-1
Appendix 2
The OEM troubleshooting portal leads you to the Honeywell Diagnostic Application which
begins a session to troubleshoot the issue.
If the HDA is accessed from the aircraft landing page, the session will open to the general
HDA. If the session is accessed from the Fault Code page, the HDA opens directly to the
troubleshooting requirements for that particular fault code.
Honeywell Alert Status Definitions

GREEN: Engine trends do not show any issue.
CYAN: Engine trends show issue(s) related to the indication system, data quality or a possible
maintenance action. This status is used for notification purposes only.
BROWN: Engine trends show issue(s), related to matters such as the indication system, data
quality or a possible maintenance action. A customer action is recommended at the next
convenient opportunity.
AMBER: Performance advisory recommended by Honeywell.
RED: Critical performance alert confirmed by the Honeywell health indicator, requiring
immediate attention by the Operator.
2-2

CAMP 30 Manual

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

CAMP 30 Manual

Diunggah oleh

Hak Cipta:

Format Tersedia

CAMP 3.

0 Online Users Guide

CAMP Systems International, Inc.

This Page Intentionally Left Blank

This Page Intentionally Left Blank

List of Affected Pages

This Page Intentionally Left Blank

- Welcome to CAMP 3.0 -

Welcome to CAMP 3.0 - Maintenance Tracking Application

- About the CAMP Service -

About the Maintenance Tracking Service

This Page Intentionally Left Blank

Navigating the System

Fleet Actual Times Quick access to Total Time edits.

Fleet Task/Status View tasks common to all aircraft.

Fleet Groups Collection of aircraft task groups.

ii. Aircraft Listings:

Documents Operator access to all general documentation loaded by

Task/Status Access to all scheduled tasks tracked against the aircraft.

Task Groups A utility that provides the operator a means to

iii. Major Assemblies:

II. Accessing an Aircraft:

General Application Architecture

Manipulating Filter Panels

Sorting By Column Header After any screen loads data

II. Adding/Removing Columns The general set of available

III. Repositioning Columns Once the desired columns are

Report Categories The screen is subdivided into four

II. Report Queue The report queue is also an integral

II. Center Display - Menu Options:

View - Used to filter, sort and/or group information.

Print Menu driven options for screen associated reports.

Add To Used to add a task to a Task Group/Work Order.

Other Actions - Gives the ability to perform additional functions.

III. Lower Display - Menu Options:

Managing the Aircraft

Aircraft Home Page

iv. Recent Maintenance Summary The recent maintenance summary provides a

v. Program Changes Program changes record physical changes made to a task

II. Additional Tabbed Functionality:

Filtering for Tasks:

III. Task Structural Display:

IV. Task Functions:

Editing the Projection Parameters:

III. Filtering the Results:

IV. Due List Functions:

Processing Compliance Information

iii. Update Tree The update screen converts the

Update Transactions Screen As soon as the system completes the processing of an

Initiating the Logbook Entry The Logbook Entry process

Major subcomponents are limited to Engines, Propellers and APUs.

III. Filtering Discrepancies:

IV. Discrepancy Structural Display:

Discrepancy Build Process:

Required fields are displayed in Bold throughout the application.

ii. Discrepancy Categories:

VI. Discrepancy Update/Maintenance Log/MTR Process:

Expendable Installed - This selection presents an entry allowing all

Service Performed Provides an entry that prompts the system to

Rotable Changed Provides an entry that triggers the system to search

Filtering for Work Orders:

Example Identify all Open Work Orders against

ii. Search Filters Relevant information must be