Ramco Aviation So lution Version 5 - Air Indiatmro-test.airindia.in/Extui/extui/RAMCOAVIATIONONLINEDOCUMENTATION... · Ramc. o En. h Avia. t Versi. o. anceme. n Offline Fi. e. ion

RRamco

Enh

o Aviat

Versio

hancemen

Offline Fie

tion So

on 5.6

nt Notificat

eld System

olution

6

tion

n

Enhancement Notification

© Copyright 2013, Ramco Systems Ltd. www.ramco.com Ramco Aviation Solution

DISCLAIMER

©2013 Ramco Systems Ltd. All rights reserved. All trademarks acknowledged.

This document is published by Ramco Systems Ltd. without any warranty. No part of this document

may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any

purpose without the written permission of Ramco Systems Limited.

Improvements and changes to this text necessitated by typographical errors, inaccuracies of current

information or improvements to software programs and/or equipment, may be made by Ramco

Systems Limited, at any time and without notice. Such changes will, however, be incorporated into

new editions of this document. Any hard copies of this document are to be regarded as temporary

reference copies only.

The documentation has been provided for the entire Aviation solution, although only a part of the

entire solution may be deployed at the customer site, in accordance with the license agreement

between the customer and Ramco Systems Limited. Therefore, the documentation made available to

the customer may refer to features that are not present in the solution purchased / deployed at the

customer site.


Contents

WHAT’S NEW – OFFLINE FIELD SYSTEM .................................................................................................. 5

OFFLINE FIELD SYSTEM ..................................................................................................................................... 5 Background ............................................................................................................................................. 5 Change Details ......................................................................................................................................... 5 Exhibit‐1 ................................................................................................................................................... 6

PRE‐REQUISITES TO USE OFFLINE FIELD SYSTEM ..................................................................................................... 6 Exhibit‐2 ................................................................................................................................................... 6 Offline Parameters .................................................................................................................................. 7 Exhibit‐3 ................................................................................................................................................... 8 Exhibit‐4 ................................................................................................................................................... 8 Exhibit‐5 ................................................................................................................................................... 9

CONFIGURATOR SCREENS ................................................................................................................................ 10 Manage Offline Area ............................................................................................................................. 10 Exhibit‐6 ................................................................................................................................................. 11 Associate Work Center to Offline Area .................................................................................................. 11 Exhibit‐7 ................................................................................................................................................. 11 View Associated Offline Warehouse ...................................................................................................... 12 Exhibit‐8 ................................................................................................................................................. 12 Manage Offline Operations ................................................................................................................... 12 Exhibit‐9 ................................................................................................................................................. 13 Evaluation .............................................................................................................................................. 13 Initialization of Offline Area .................................................................................................................. 14 Note: ...................................................................................................................................................... 15 Release of additional Aircraft and Work Centers to Offline Area .......................................................... 15 Return of Aircraft and Work Centers ..................................................................................................... 15 Termination of Offline Area ................................................................................................................... 16 Force Termination of Offline Area ......................................................................................................... 16 Exhibit‐10 ............................................................................................................................................... 16 Exhibit‐11 ............................................................................................................................................... 17 Impacted Transaction List ..................................................................................................................... 17 Exhibit‐12 ............................................................................................................................................... 18 View Operational History ...................................................................................................................... 18 Exhibit‐13 ............................................................................................................................................... 18 Transfer Data......................................................................................................................................... 18 Operation Mode Selected as “Extract” .................................................................................................. 19 Exhibit‐15 ............................................................................................................................................... 19 Process Flow for Extraction Status ........................................................................................................ 19 Exhibit‐14 ............................................................................................................................................... 20 Operation Mode Selected as “Load” ..................................................................................................... 20 Exhibit‐17 ............................................................................................................................................... 21 Process Flow for Load Status ................................................................................................................. 21 Exhibit‐16 ............................................................................................................................................... 22 Exhibit‐18 ............................................................................................................................................... 23 Exhibit‐19 ............................................................................................................................................... 23

WHAT’S NEW IN AIRCRAFT .................................................................................................................. 24

FACILITY TO RESTRICT PARAMETER VALUES UPDATE IN MAIN BASE FOR OFFLINE AIRCRAFT & COMPONENTS .................... 24 Background ........................................................................................................................................... 24

Page 3 of 43


Change Details ....................................................................................................................................... 24

WHAT’S NEW IN MAINTENANCE SETUP? ............................................................................................. 25

FACILITY TO RESTRICT THE MODIFICATION OF OFFLINE WORK CENTER ATTRIBUTES IN THE MAIN BASE. ........................... 25 Background ........................................................................................................................................... 25 Change Details ....................................................................................................................................... 25

WHAT’S NEW IN FLIGHT LOG? ............................................................................................................. 26

FACILITY TO TRACK AIRCRAFT JOURNEY LOGS AS PART OF OFFLINE OPERATIONS ........................................................... 26 Background ........................................................................................................................................... 26 Change Details ....................................................................................................................................... 26 Main base and Offline Field base transactions supported for an Offline Aircraft ................................. 28 Amendment of approved journey logs having source as “Offline” will be restricted in offline base if the data has been transferred to main base. .................................................................................................................. 28 Amendment of journey logs having source as “Online” is restricted from offline field base. ............................... 28 Journey Logs in “Under Amendment” status can be approved or amended only in the respective operational base where its amendment was done. ................................................................................................................ 28

WHAT’S NEW IN AIRCRAFT MAINTENANCE EXECUTION? ..................................................................... 30

FACILITY TO PERFORM AIRCRAFT MAINTENANCE EXECUTION AS PART OF OFFLINE OPERATIONS ....................................... 30 Background ........................................................................................................................................... 30 Change Details ....................................................................................................................................... 30

CHANGES IN LOGISTICS ....................................................................................................................... 39

WHAT’S NEW IN DOCUMENT NUMBERING CLASS? .............................................................................. 39

ABILITY TO SPECIFY UNIQUE DOCUMENT NUMBERING PATTERN FOR EACH OFFLINE AREA .............................................. 39 Background ........................................................................................................................................... 39 Change Details ....................................................................................................................................... 39 Exhibit I .................................................................................................................................................. 39

WHAT’S NEW IN STORAGE ADMINISTRATION? .................................................................................... 40

FACILITY TO IDENTIFY MOBILE WAREHOUSE THAT CAN OPERATE OFFLINE ................................................................... 40 Background ........................................................................................................................................... 40 Change Details ....................................................................................................................................... 40 Exhibit I .................................................................................................................................................. 40 Exhibit II ................................................................................................................................................. 41

WHAT’S NEW IN STOCK MANAGEMENT? ............................................................................................. 42

Background ........................................................................................................................................... 42 Change Details ....................................................................................................................................... 42

CHANGES IN FINANCE .......................................................................................................................... 43

ACCOUNTING IN FIELD BASE ............................................................................................................................. 43

Page 4 of 43


Page 5 of 43

WWHHAATT’’SS NNEEWW –– OOFFFFLLIINNEE FFIIEELLDD SSYYSSTTEEMM

OOfffflliinnee FFiieelldd SSyysstteemm

Background

Despite the advancements in the satellite communications, there are still a significant number of places in the world where reliable & continuous connectivity is not available.

With the introduction of Offline Field System, Ramco is now providing a solution to overcome this challenge for operators having remote operations where internet connectivity is intermediate or even no connectivity.

Ramco's Offline Field System will enable users in remote locations to perform required transactions without any necessity to connect with the main system. Here, the Offline laptop will act as the local server using SQL Server Express.

Offline Field System will allow the user to perform transactions in asynchronous mode in Offline Field base or Main base without affecting data integrity. The transactional data can be transported between the offline and the main systems through any data transfer media such as email, flash drive, CD or DVD.

Ramco’s Offline Field System can run on Windows 7 Laptops with MS SQL Server Express. Screens are rendered using Ramco’s Desktop UI technology.

Change Details

New business process “Offline Field System” and business component “Configurator” are added in Ramco Aviation Solution with following activities to address Offline Field System requirements.

Manage Offline Area

Manage Offline Operations

Transfer Data

Configure Offline Parameters


Exhibit-1

New Business Process, Components and its Activities

PPrree--rreeqquuiissiitteess ttoo uussee OOfffflliinnee FFiieelldd SSyysstteemm

The Offline System Applicable? drop-down list box must be selected as “Yes” in Set Global Parameter Screen (Finance Setup > Installation Parameter Setup > Set Global Parameters).

Exhibit-2

The Offline System Applicable? drop-down list box in Set Global Parameters Screen

Page 6 of 43


All offline parameters except system defined parameters need to be configured for categories “Offline Configurator Options” and “Aircraft Maintenance Options“ in the Configure Offline Parameter screen (Offline Field System > Configurator > Configure Offline Parameter)

Note: In Offline laptops, additional category “Permitted Transaction List” is only available. This will display all the transactions allowed in Offline Field System.

Offline Parameters

Category Offline Configurator Options

Usage Mode: This parameter gives the context of system, whether "Online" or "Offline".

Offline Area #: If Usage mode is "Offline" system will display respective Offline Area associated to the Laptop / System.

No. of instances to package: This option controls clubing of last extracted data package file for each extraction.

Email IDs for notifications: This option enables sending of offline area alerts. System sends alerts to the email id entered.

Lead time to initiate production database backup: If initialization is done “As per Schedule”, then system will process the request on entered time.

Set Extract Path: The system extracts data packages to this path

Set Load Path: The system extracts data packages to this path

Set Extract Path for Backup/Archive: This option enables user to specify the path to which System Backups/Archives Extracted data packages.

Set Load Path for Backup / Archive: This option enables user to specify the path from which System Backups/Achieves Loaded data packages.

Root Folder for Laptop Induction: The system extracts first time cut data packages to this folder on Initialization of Offline Area.

Category Aircraft Maintenance Options

Closure of Completed Packages: This option enables user to define the closure of completed Aircraft Maintenance Execution Ref packages at Mainbase o Offline Base.

Allow Part change close for Offline usage: This option controls whether 'Part Change - Close' is permitted for discrepancies from "Record Aircraft Maintenance Execution Ref.", offline operations.

Permitted Package type for Offline usage: The user must enter valid package types applicable for offline operation.

Page 7 of 43


Allow utilization of Holds for Offline Usage: The user can control the hold capability available in "Record Aircraft Maintenance Execution Ref. ". for offline operation.

Allow usage of Cannibalization for Offline Usage: Cannibalization of components in "Record Aircraft Maintenance Execution Ref. " is performed based on this set option for offline operations.

Process Off wing jobs for Offline Usage: This option controls addition of "Off-Wing" tasks to a package from "Record Aircraft Maintenance Execution Ref. " for offline operation.

Allow addition of Repair tasks for Offline Usage: This option controls addition of tasks having repair agency reference alone from "Record Aircraft Maintenance Execution Ref. " for offline operation.

Exhibit-3

The Offline Configurator Options category in Set Configure Offline Parameter Screen

Exhibit-4

The Aircraft Maintenance Options category in Set Configure Offline Parameter Screen

Page 8 of 43


Exhibit-5

The Permitted Transaction List category in Set Configure Offline Parameter Screen

List of Transactions Permitted in Offline Field System

1. Journey Log

2. Aircraft Maintenance Execution (AME)

3. Material Request

4. General Issue

5. Maintenance Issue

6. Unplanned Issue

7. General Return

8. Maintenance Return

9. Unplanned Return

10. Inter Wh. Stock Transfer

11. Intra Wh. Stock Transfer

12. Stock Transfer Receipt

13. Material Loss

14. Stock Correction

15. Record Shipping Note

16. Record Fuel & Oil Log

Page 9 of 43


Page 10 of 43

CCoonnffiigguurraattoorr SSccrreeeennss

Following are the activities and Screens available in Configurator Component.

Activity Name Associated Screens Manage Offline Area Manage Offline Area

Manage Offline Area Associate Work Center to Offline Area Manage Offline Area View Associated Offline Warehouse Manage Offline Operations Manage Offline Operations Manage Offline Operations Impacted Transaction List Manage Offline Operations View Operation History Transfer Data Transfer Data Transfer Data View Extracted Data Transfer Data View Data Transfer History Configure Offline Parameters Configure Offline Parameters

Manage Offline Area

An “Offline Area” is necessary to start using Offline Field System.

Offline Area is a virtual area, which can accommodate work centers and aircraft. An Offline Area can be a Geographical Area or Aircraft number as per business requirements.

Depending up on the offline operation performed “Assignment Type” can be defined.

If aircraft moves in various geographical areas, Assignment type can be defined as “Aircraft” and Offline Area will be Aircraft number. Heli logging is a typical case for such A/C assignments.

If different aircraft are used to perform offline operation in same geographical area, then Assignment type can be defined as “Work Center” and Offline Area will be geographical area. For example, in case of mining operations aircraft are assigned to the same geographical area.

Note: Progressive release of aircraft and work centers will be made available in future releases.

This screen can be used to create new Offline Area and edit existing Offline Area.


Exhibit-6

The Manage Offline Area Screen

Associate Work Center to Offline Area

This screen can be used to add additional work centers to the Offline Area. To activate offline area at least one work center association is mandatory.

Note: Work center association for an offline area with operational status as “Operational”, cannot be removed.

Exhibit-7

The Associate Work Center to Offline Area Screen

Page 11 of 43


View Associated Offline Warehouse

This screen displays work centers with warehouses, which are associated to the Offline Area.

Exhibit-8

The View Associated Offline Warehouse Screen

Manage Offline Operations

This Screen can be used to manage the Offline Operations, such as

1. Evaluation

2. Initialization of Offline Area

3. Release of additional Aircraft and Work Centers to Offline Area

4. Return of Aircraft and Work Centers

5. Termination of Offline Area

6. Force Termination of Offline Area

Page 12 of 43


Exhibit-9

The Manage Offline Operations Screen

Evaluation

Evaluation is done for verifying Open transactions and completion of master data setup before performing release and return of aircraft and work centers.

The transactions which are considered Open are listed in below table. This transaction will be listed as “Action Required” items in Impacted Transaction List screen.

Transaction Status AME - Package / Log Card In progress, Planned.

AME - Discrepancy Under resolution , Pending deferral AME - Tasks In-progress, Incomplete, Planned. AME - CR Fresh AME - MR Authorized , Partially Issued AME - MR Issue Fresh AME - MR Return Draft , Fresh Journey Log Fresh , Under Amendment Aircraft Configuration Fresh Aircraft Program Fresh Component Configuration Fresh Component Program Fresh Record Oil / Fuel Log NA Material Request Draft, Fresh, Authorized, Partially

Issued, Partially received Stock Issue(General, Maintenance, Repair, Exchange, Loan/ Rental Unplanned)

Draft, Fresh

Stock Return (General, Maintenance, Unplanned)

Draft, Fresh

Page 13 of 43


Inter Wh. Stock Transfer Draft, Fresh, Authorized, Partially Issued

Intra Wh. Stock Transfer Draft, Fresh Transfer Receipt Draft, Fresh Material Loss Draft, Fresh Opening Balance Draft, Fresh Stock Correction Draft, Fresh Part Serial Change Analyzed, Error, Initiated, In-

progress Stock Status conversion Draft, Fresh Physical Inventory Draft, Confirmed Cycle Count Confirmed, Partially Counted,

Counted, Partially Recounted, Recounted

The system displays “Informational” message for following cases in Impacted Transaction List screen:

Aircraft Maintenance Programs in Fresh/Returned/Inactive/Confirmed status.

Component Maintenance Programs in Fresh status for component(s) attached in aircraft and available in warehouses going offline

Aircraft Configuration in Open status

Component Configuration in Open status for component(s) attached in aircraft and available in warehouses going offline.

Timesheet Authorization pending for Execution Ref #.

Part change close for Offline usage is disallowed

CoM Issuance is switched off for Offline Usage.

Automatic pegging of Open Material Requests is disallowed for offline usage

"Auto Return of Parts" is enabled for Offline Usage

Note: If all “Action Required” validations are cleared, “Rel. / Ret. Allowed” column for respective aircraft or work center will be displayed as “Yes”. If “Action Required” validations are not cleared “Rel. / Ret. Allowed” will be displayed as “No”.

Initialization of Offline Area

Offline Area needs to be initialized for each field operation from the Main base.

As part of Initialization, the system will validate for Open transactions and Master Data Setup completion.

Once all the “Action Required” validations available in Impacted Transaction List screen are cleared, the user can invoke the “Initiate Field Ops” button. This will create

Page 14 of 43


“Initialization Request #” and the system will start processing the request based on the value of the radio button in the “Initiate Field Operations” cluster.

If radio button value is selected as “Immediate”, the Ramco’s CDT (Change Data Transfer) tool will start processing the Initialization Request # immediately.

If radio button value is selected as “As per Schedule”, Ramco’s CDT (Change Data Transfer) tool will start processing the Initialization Request # up on the time which is defined for parameter “Lead time to Initiate Production database back up” in Configure Offline Parameter screen.

Note:

i. If “As per Schedule” option is selected for Initiation, Extract cannot be done for other offline areas which are in Operational status till Initiation is completed.

ii. Once Offline Area is “Initialized”, for released aircraft and work center(s) usage mode will be changed to “Offline”.

iii. Once Ramco’s CDT (Change Data Transfer) tool finishes the first stage of initiation process, configuration of offline laptop can be initialized. Refer installation manual provided for first time Offline Area set up.

Release of additional Aircraft and Work Centers to Offline Area

Once Offline Area is operational, based up on the business requirement, the user can release additional aircraft and work centers to the Field base from Main base.

Before releasing additional aircraft and work center(s), the system will validate for Open Transactions and completion of master data set up.

Once aircraft and work center(s) are released, “Move. Status” will be changed to “Released” and “Operational status” will be kept as “Operational”

Return of Aircraft and Work Centers

In an offline Field base, once field operations are complete, the user can return the aircraft and work center to the Main base. Return can only be done from a Field base.

Before returning aircraft and work centers from the Field base, the system will validate for Open transactions and ask user to close the same, if any.

On return of aircraft and work centers, the “Move Status” will be changed to “Returned” and “Operational status” will be kept as “Operational”

Note: Once aircraft and work center(s) are returned, usage mode for it will be changed from “Offline” to “Online”. After return, transactions cannot be created on returned aircraft and work center(s).

Page 15 of 43


Termination of Offline Area

In the Main base, once all aircraft and work center(s) released to Field have been received back, user can terminate the Field Operation. The termination of field operation can only be done from the Main base.

If the aircraft is visiting the Main base for heavy check, the offline area may not be terminated.

Once offline Area is terminated, “Operational status” is set as “Terminated” and “Move. Status” will be retained as “Returned”.

Force Termination of Offline Area

In case of scenario like damaged laptop, the user can Force Terminate the Offline Field Operation. Force Termination of field operation can only be done from the Main base.

Note: Force Termination will result in loss of data; hence the same Offline Area cannot be used for receiving any data.

Exhibit-10

Process Flow for Operational Status

Page 16 of 43


Exhibit-11

Process Flow for Move Status

Impacted Transaction List

This Screen lists the “Informational” and “Action Required” validations upon evaluation for,

Initialization

Release

Return

User need to clear all the “Action Required” validations displayed in this sScreen to proceed.

Page 17 of 43


Exhibit-12

Impacted Transaction List Screen

View Operational History

This screen can be used to view Operation history of respective Offline Area and its associated Aircraft and Work Centers.

Exhibit-13

View Operational History Screen

Transfer Data

This screen can be used to Extract and Load data in Offline Base and Main base in all data transfer scenarios except Offline Area Initialization.

Page 18 of 43


Operation Mode Selected as “Extract”

If the user selects Operation Mode as “Extract” and invokes the “Initiate Operation” button, the system identifies the latest change details from last Extract and extracts it to the Extract Path mentioned in “Configure Offline Parameter” Screen.

Exhibit-15

Transfer Data Screen with Operation Mode selected as “Extract”

Process Flow for Extraction Status

Extract-Initiated: Once user clicks the “Initiate Operation” button with Operation Mode selected as “Extract”, Data Extract / Load Request # will get generated and status will change to “Extract-Initiated”.

Extract-In progress: Once system starts processing the Request #, the status will be changed as “Extract-In progress”.

Extracted: Once extraction is completed successfully, Status will be changed as “Extracted”.

Extract-Failed: If extraction got failed, Status will be displayed as “Extraction-Failed” with the reason for failure in “Message Center”.

Page 19 of 43


Exhibit-14

Process Flow for Extraction Status

Operation Mode Selected as “Load”

On copy and paste of Extracted files from Source to Destination “Load Path”,

The system will pick up the request and Status will be changed to “Load-Requested”.

The system can load the data packages itself, if Load scheduler is configured for “Auto Loading”.

If Auto-Load is not configured or Load is failed, the user can manually initiate Load operation by invoking “Initiate Operation”.

Page 20 of 43


Exhibit-17

Transfer Data Screen with Operation Mode selected as “Load”

Process Flow for Load Status

Load-Requested: Once the user copies and pastes data packages received from Source to “Load Path” defined for Destination, system will identify the packages and display it in Transfer Data multiline along with Status as “Load-Request” if Auto-Load is not configured.

Load-Initiated: Once the system start processing the request # for loading, Status will be changed to “Load-Initiated”.

a. If Auto Load is configured, status will be changed to “Load-Initiated” by system after copying and pasting data package to “Load Path” defined in destination.

b. If Auto Load is not configured, the user needs to manually invoke the “Initiate Operation” button for data package with “Load-Requested” Status. Once “Initiate Operation” button is invoked status will be changed to “Load-Initiated”.

Page 21 of 43


Exhibit-16

Process Flow for Load Status

Load-In progress: Once system starts loading data package from “Load Path”, Status will be changed to Load-In progress.

Loaded: If data package is loaded successfully to the system, the status will be changed to “Loaded”

Load-Failed: If Load got failed, Status will be displayed as “Load-Failed” with the reason for failure in “Message Center”.

View Extracted Data: View Extracted data Screen can be used to View extracted data details for the last Extraction.

Page 22 of 43


Exhibit-18

View Extracted Data Screen

Exhibit-19

View Data Transfer History screen

This screen can be used to View the Data Transfer History for the Offline Area and Main base.

The “Source” radio button available in “Search Criteria” cluster can be used to filter the search results based on the source of Data Transfer.

Page 23 of 43


Page 24 of 43

WWHHAATT’’SS NNEEWW IINN AAIIRRCCRRAAFFTT

FFaacciilliittyy ttoo rreessttrriicctt ppaarraammeetteerr vvaalluueess uuppddaattee iinn MMaaiinn bbaassee ffoorr OOfffflliinnee AAiirrccrraafftt && CCoommppoonneennttss

Reference: AHBD-6125

Background

To maintain consistency in parameter values of offline aircraft and components, it is necessary to restrict re-initialization and new mode parameter value updates from Main base.

Currently in the Ramco Aviation solution, the user can update parameter values for offline aircraft and components with update option as “Re-initialize / New / Delta / Correction”.

Change Details

With the introduction of this feature, system does not allow parameter value update in Main base, if the update option is set as “Re-initialize / New”, for

Offline aircraft

Components attached to offline aircraft

Components available in offline warehouse

Component removed from offline aircraft but pending for return.

Note: An aircraft is offline, if it is located in an offline Field base i.e. ‘Mode of Usage’ as “Offline” in the “Aircraft” business component.


Page 25 of 43

WWHHAATT’’SS NNEEWW IINN MMAAIINNTTEENNAANNCCEE SSEETTUUPP??

FFaacciilliittyy ttoo rreessttrriicctt tthhee mmooddiiffiiccaattiioonn ooff OOfffflliinnee WWoorrkk CCeenntteerr aattttrriibbuutteess iinn tthhee MMaaiinn bbaassee..


Background

To initiate the Operations in the Offline Field base, it is mandatory to associate the Work Center to the Offline Field base. This change is made to ensure the data concurrency between Offline Field base and Main base after transferring the Work Center to Offline Area.

This change will prevent the modification of specific Work Center attributes if the Work Center is set as Offline.

Change Details

If the Work Center is flagged as Offline in the Main base, the modification of the following Work Center attributes are not allowed:

The modification of Work Center Status and Work Center Class are not allowed.

The modification of already mapped Warehouses and mapping of new Warehouses” are not allowed.

The addition and modification of “Execution Capability” are not allowed.


Page 26 of 43

WWHHAATT’’SS NNEEWW IINN FFLLIIGGHHTT LLOOGG??

FFaacciilliittyy ttoo ttrraacckk aaiirrccrraafftt jjoouurrnneeyy llooggss aass ppaarrtt ooff oofffflliinnee ooppeerraattiioonnss


Background

When an aircraft is being operated from an offline Field base, tracking of its journey logs is a necessity as this data is required for aircraft maintenance planning. Ramco’s aviation solution supports journey log management during offline operations of an aircraft.

Change Details

1. Create Journey Log: For offline aircraft, Journey Log creation shall be allowed in the respective Offline Field base alone.

Creation of Journey Logs from Main Base will be restricted for offline aircraft.


2. Edit Journey Log: Edit of Journey Logs having source as “Offline” (ie, created from offline Field base) shall be allowed from offline Field base alone.

Edit of journey logs created from offline field base shall be prevented in Main Base

Edit of journey logs created from offline field base shall be prevented in Main Base

3. Approve Journey Log: Approval / Cancellation / Edit of Journey Logs having source as “Offline” (ie, created from offline Field base) shall be allowed from offline Field base alone.

Edit of Journey Logs having source as “Offline” shall be restricted in Main Base.

Cancellation of Journey Logs having source as “Offline” shall be restricted in Main Base. Approval of logs having source as “Offline”

shall be restricted in Main Base.

Page 27 of 43


4. Amend Journey Log: Offline Field base operations - Approved Journey Logs having source as “Offline” shall be allowed for amendment in offline Field base only if the respective data has not been transferred to Main base. Amendment of journey logs having source as “Online” is restricted from offline Field base.

Journey Logs already amended (ie, journey log status is “Under Amendment”) from an operational base (Main base / Offline Field base) shall be allowed for approval / amendment from the respective operational base alone.

Main base and Offline Field base transactions supported for an Offline Aircraft

Transaction JL Status JL Source Allowed in Main base?

Allowed in Field base?

Create Journey Log - - No Yes Edit Journey Log Fresh Online No No Edit Journey Log Fresh Offline No Yes Approve / Cancel Journey Log

Fresh Online No No

Approve / Cancel Journey Log

Fresh Offline No Yes

Amend Journey Log Approved, Under Amendment

Online Yes No

Amend Journey Log Approved Offline Yes No (If data has been transferred to Main base)

Journey Logs in “Under Amendment” status can be approved or amended only in the respective operational base where its amendment was done.

Amendment of journey logs having source as “Online” is restricted from offline field base.

Amendment of approved journey logs having source as “Offline” will be restricted in offline base if the data has been transferred to main base.

Page 28 of 43


Amend Journey Log Approved Offline - Yes (If data has not been transferred to Main base)

Amend Journey Log Under Amendment

Offline No Yes

Note: Journey Logs created / amended from Main base will have source as “Online” & Journey Logs created from Offline Field base will have source as “Offline”. Journey Log source is not visible in application and is tracked in the background.

Page 29 of 43


Page 30 of 43

WWHHAATT’’SS NNEEWW IINN AAIIRRCCRRAAFFTT MMAAIINNTTEENNAANNCCEE EEXXEECCUUTTIIOONN??

FFaacciilliittyy ttoo ppeerrffoorrmm aaiirrccrraafftt mmaaiinntteennaannccee eexxeeccuuttiioonn aass ppaarrtt ooff oofffflliinnee ooppeerraattiioonnss


Background

Tracking of discrepancies and complied tasks is critical for flight safety during offline operations of an aircraft. Clear visibility on pending component replacements and part requirements helps in smooth aircraft maintenance during offline operations. Current enhancement facilitates tracking of aircraft maintenance execution from an offline Field base.

Change Details

System behavior for offline aircraft in Main base and Offline Field base is as explained below:

1. Main base operations:

1.1 Open Items tree (Record Aircraft Maintenance Execution Details page):

Package execution on offline aircraft from the Record Aircraft Maintenance Execution Details activity is primarily controlled by displaying locks in the Open Items tree.

Open Items tree with locked nodes:


All Discrepancies (Log Card Discrepancies, Unprocessed Discrepancies and Package Discrepancies) listed in 'Open Items' tree will be displayed as locked in Main base.

"Planned" / "In-Progress" packages having 'Source' as "Offline" will be locked.

"Completed" packages having 'Source' set as "Offline" will be locked in Main base if process parameter - 'Closure of Completed Packages' in 'Configure Offline Parameters' activity ('Configurator' business component) is set as "Offline Base".

Note: Packages created from Main base and Offline Field base will have ‘Source’ set as “Online” and “Offline” respectively. Package source is not visible in the application and is tracked in the background.

1.2 Due List tree (Record Aircraft Maintenance Execution Details page):

For offline aircrafts, addition of due tasks and discrepancies is restricted in Main base.

1.3 Execution Record Details section (Record Aircraft Maintenance Execution Details page):

System shall restrict creation of A/C Maint. Exe. Ref. Documents referring an Offline Work Center in Main base.

System shall allow closure of offline packages in Main base if "Closure of Completed Packages" option in ‘Configurator’ business component is set as “Main base”.

1.4 Discrepancy section (Record Aircraft Maintenance Execution Details page):

Discrepancy reporting / re-opening / transfer across packages is restricted in Main base for offline aircraft.

Page 31 of 43


1.5 Work Information section (Record Aircraft Maintenance Execution Details page):

Unplanned addition of due tasks for Offline Aircraft is always restricted in Main base.

Auto-addition of overdue tasks & incomplete tasks based on process parameter setting for Package Type entity shall not function in Main base for offline aircraft.

1.6 Component Replacement section (Record Aircraft Maintenance Execution Details page):

Component Replacement transactions are restricted in Main base for offline aircraft.

1.7 Material Request section (Record Aircraft Maintenance Execution Details page)

Generation of material requests in Main base is prevented for packages referring an offline work center.

1.8 Enhancements in Record Part Consumption & Return activity

Update Consumption / Reconcile prevented from Main base for packages referring to an offline work center. Return Parts prevented from Main base for

packages referring to an offline work center.

Page 32 of 43


1.9 Enhancement in Manage Work Assignments and Reporting activity:

1.9.1 Review Work tab

Report Work Actuals will be allowed for offline packages in Completed status if ‘Closure of Completed Packages’ option in Configurator component is set as “Offline”.

Update Plan will be allowed for offline packages in Completed status if ‘Closure of Completed Packages’ option in Configurator component is set as “Offline”.

Hold will be allowed for offline packages in Completed status if ‘Closure of Completed Packages’ option in Configurator component is set as “Offline”.

1.9.2 Manage Employee Work tab

Authorize Booking will be allowed for offline packages in Completed status if ‘Closure of Completed Packages’ option in Configurator business component is set as “Offline”.

Update Assignments / Time Booking will be allowed for offline packages in Completed status if ‘Closure of Completed Packages’ option in Configurator business component is set as “Offline”.

2. Offline Field base operations

Note: As part of this release, a new activity – ‘Record Aircraft Execution Details’ (Business Process – Aircraft Maintenance, Component – Aircraft Maintenance Execution)

Page 33 of 43


has been engineered. This activity is suggested only for offline mode of operations using Ramco Desktop application.

2.1 Open Items tree (Record Aircraft Maintenance Execution Details page):

Packages having 'Source' as "Online" will be locked for editing in Offline Base.

Completed Packages having 'Source' as "Offline", will be locked in Offline Base, if process parameter - 'Closure of Completed Packages' in 'Configure Offline Parameters' activity ('Configurator' business component) is set as "Main base" & data has been transferred to Main base.

Discrepancies associated to following packages will be locked in offline Field base:

a. Online Packages (non-log cards) (or)

b. Offline Packages (non-log cards) in “Completed” status with data transferred to Main base & process parameter - 'Closure of Completed Packages' set as "Main base".

On click of unlocked discrepancy nodes (Log Card / Package Discrepancies), th system shall transfer associated Exe. Ref. # details into Execution Record Details section only if source* of the A/C Maint. Exe. Ref. Document is set as "Offline" and:

a. Data has not been transferred to Main base, (or)

b. Data has been transferred to Main base & process parameter - 'Closure of Completed Packages' in the interacting 'Configurator' business component is set as "Offline Base".

Note: Packages created from Main base and Offline Field base will have ‘Source’ set as “Online” and “Offline” respectively. Package source is not visible in the application and is tracked in the background.

2.2 Due List tree (Record Aircraft Maintenance Execution Details page):

The addition of off-wing due tasks in offline Field base is controlled based on process parameter - "Process Off wing jobs in AME for Offline Usage" set in “Configurator” business component. If the process parameter, packaging of off-wing tasks is allowed, the system shall package the off-wing tasks as on-wing tasks.

2.3 Execution Record Details section (Record Aircraft Maintenance Execution Details page):

The system shall allow closure of offline package in offline Field base, if "Closure of Completed Packages" option is set as “Offline Base” respectively.

Page 34 of 43


For offline operations, the system shall load only applicable 'Package Type' set against the process parameter - "Permitted Package type for Offline usage" in the interacting 'Configurator' component.

2.4 Links section (Record Aircraft Maintenance Execution Details page):

Following links will not be available for offline Field base operations:

1 Bulk Material Request 2 Create Engg. Service Request 3 Record Employee Time Sheet 4 Report Resource Estimates / Actuals

5 Record Parameter Reading / Cond. Eval. Form

6 Issue Certificate of Maintenance 7 Upload Documents 8 Edit Package Additional Information 9 Edit References

10 View Associated Doc. Attachments 11 View Engg. Advice Note

2.5 Discrepancy section (Record Aircraft Maintenance Execution Details page):

Loading of "Part Change - Close" value in 'Action' drop-down will be controlled based on process parameter -“Allow part change close for Offline usage” available in 'Configurator' component.

New link to view Logbook report

Page 35 of 43


Page 36 of 43

The following links will not be available for offline Field base operations:

1 Edit Discrepancy Additional Information 2 Author Repair Procedure 3 Revise Deferral Limits 4 Upload Documents 5 View Documents 6 Record Work Hold

2.6 Work Information section (Record Aircraft Maintenance Execution Details page):

a. Addition of off-wing tasks is restricted in Offline Field base, if process parameter - "Process Off wing jobs in AME for Offline Usage" in the interacting 'Configurator' business component is set as "Not Allowed".

b. For Offline Aircraft, if process parameter - "Allow addition of Repair station tasks for Offline Usage" in 'Configurator' business component is set as "Not Allowed", system shall restrict addition of task if one of its child tasks in repair scheme is to be performed in a Repair Agency # (ie, no applicable Work Center # details are specified corresponding to the Child Task in Repair Scheme definition).

Links not available for offline Field base operations are given below:

1 Edit Task Additional Information 2 Author Repair Procedure 3 Record Parameter Reading / Cond. Eval. Form 4 View AMM Reference 5 Upload Documents 6 View Documents 7 Record Work Hold

New link to view Logbook report.

Job-Type drop-down will not have value - "Off-Wing" for Offline operations. Off-Wing tasks shall be processed as On-Wing jobs in Offline Field Base.


2.7 Utilization of Holds (Record Aircraft Maintenance Execution Details page)

During offline operations, system shall restrict application of holds on tasks and discrepancies for, if "Allow utilization of Holds for Offline Usage" in ‘Configurator’ business component is set as “Not Allowed”.

2.8 Component Replacement section (Record Aircraft Maintenance Execution Details page):

For Offline operations ‘Source’ combo shall not load “Cannibalize” as a value if process parameter - "Allow usage of Cannibalization for Offline Usage" in 'Configurator' business component is set as "Not Allowed".

Disposition codes having: "Removed Core Condition" set as "Phased-Out" (or) "Create Order on disposition" set as "Yes" shall not be loaded during offline operations.


1 Route Unserviceable to Repair 2 Update Removed Comp. Assembly 3 Update Installed Component Assembly 4 Create New Part Request 5 Inquire New Part Request Status

2.9 Material Request section (Record Aircraft Maintenance Execution Details page):

New Part Request generation is not supported as part of offline operations.

Material Requests can be confirmed in offline base only if the requested quantity is available in stock.

Auto-pegging of Open material requests based on process parameter definition for Package Type entity, is not supported as part of offline operations.

Page 37 of 43


New Part #? Combo shall not load value – “Yes” in offline field


1 Request Preferred Serial # / Lot # Info 2 Inquire New Part Request Status 3 View Part Maintenance Info

2.10 Enhancements in Record Part Consumption & Return activity:

Update of part consumption / reconciliation & return will be prevented in offline Field base for (a) online packages & (b) completed offline packages if ‘Closure of Completed Packages’ option in ‘Configurator’ business component is set as “Main base”.

Page 38 of 43


Page 39 of 43

CCHHAANNGGEESS IINN LLOOGGIISSTTIICCSS

WWHHAATT’’SS NNEEWW IINN DDOOCCUUMMEENNTT NNUUMMBBEERRIINNGG CCLLAASSSS??

AAbbiilliittyy ttoo ssppeecciiffyy uunniiqquuee ddooccuummeenntt nnuummbbeerriinngg ppaatttteerrnn ffoorr eeaacchh oofffflliinnee aarreeaa


Background

It is imperative to ensure that unique document numbers are generated within and across transaction to facilitate smooth data sync operation when data are transferred and received between Main base and Field base.

Change Details

To facilitate definition of numbering pattern for each offline area and a common numbering pattern for the Main base within a Numbering Type, three new columns are added in Numbering Pattern multiline grid. They are Offline?, Offline Area # and Offline Area Description.

For the common numbering pattern for Main base the drop down ‘Offline?’ needs to be set as “No”. For numbering pattern that pertain to a Field base the drop down ‘Offline?’ needs to be set as “Yes” and the corresponding Offline Area needs to be selected in the ‘Offline Area’ drop down.

Note: It is not possible to delete or modify a numbering pattern pertaining to an offline area once a cut is taken to setup the offline area i.e., Field base.

Exhibit I

Identifies the changes in Create Numbering Type screen


Page 40 of 43

WWHHAATT’’SS NNEEWW IINN SSTTOORRAAGGEE AADDMMIINNIISSTTRRAATTIIOONN?? WFFaacciilliittyy ttoo iiddeennttiiffyy mmoobbiillee wwaarreehhoouussee tthhaatt ccaann ooppeerraattee oofffflliinnee F

Reference: AHBD-4168 Reference: AHBD-4168

Background Background

Among several warehouses that are configured in the system, a clear distinction must be made between a fixed warehouse (which will be part of Main base) and a mobile warehouse. A mobile warehouse refers to a warehouse that can operate either as part of Main base or can go offline and operate in a remote location.

Among several warehouses that are configured in the system, a clear distinction must be made between a fixed warehouse (which will be part of Main base) and a mobile warehouse. A mobile warehouse refers to a warehouse that can operate either as part of Main base or can go offline and operate in a remote location.

Change Details Change Details

A new check box ‘Allow Offline Usage’ has been provided in Create Warehouse Information and Edit Warehouse Information screens. The check box needs to be selected for only those mobile warehouses that can operate offline.

A new check box ‘Allow Offline Usage’ has been provided in Create Warehouse Information and Edit Warehouse Information screens. The check box needs to be selected for only those mobile warehouses that can operate offline.

Secondly, to ensure integrity of the data in an offline warehouse (Field base), certain validations are added to restrict users from modifying warehouse definitions. For example, once a warehouse goes offline, the user will not be able to remove the mapped Part Type, Part Classification, Condition and Stock Status that are allowed in the warehouse. However, it is possible to map a new Part Type, Part Classification, Condition or Status. Similarly, a warehouse, zone or bin in the warehouse cannot be inactivated as long as the warehouse is offline. These changes could be accomplished only when the mobile warehouse comes to the Main base i.e., it is not offline anymore, and the required data is synchronized with the Main base.

Secondly, to ensure integrity of the data in an offline warehouse (Field base), certain validations are added to restrict users from modifying warehouse definitions. For example, once a warehouse goes offline, the user will not be able to remove the mapped Part Type, Part Classification, Condition and Stock Status that are allowed in the warehouse. However, it is possible to map a new Part Type, Part Classification, Condition or Status. Similarly, a warehouse, zone or bin in the warehouse cannot be inactivated as long as the warehouse is offline. These changes could be accomplished only when the mobile warehouse comes to the Main base i.e., it is not offline anymore, and the required data is synchronized with the Main base.

Also a new field “Mode of Usage” is provided in View Warehouse Information screen which will show if the mobile warehouse is currently online or not. Also a new field “Mode of Usage” is provided in View Warehouse Information screen which will show if the mobile warehouse is currently online or not.

Exhibit I Exhibit I

Identifies the changes in Create Warehouse Information screen Identifies the changes in Create Warehouse Information screen

WHHAATT’’SS NNEEWW IINN SSTTOORRAAGGEE AADDMMIINNIISSTTRRAATTIIOONN??

Faacciilliittyy ttoo iiddeennttiiffyy mmoobbiillee wwaarreehhoouussee tthhaatt ccaann ooppeerraattee oofffflliinnee


Exhibit II

Identifies the changes in View Warehouse Information screen

Page 41 of 43


Page 42 of 43

WWHHAATT’’SS NNEEWW IINN SSTTOOCCKK MMAANNAAGGEEMMEENNTT??

Reference: AHBD-4334, AHBD-4436

Background

Data synchronization happens between the Main base and the Field base. By virtue of the synchronization process, the Main base will be able to see all transactions that have happened in the Field base including the ones that are in-progress. However, it is imperative that adequate validations and logics are built in the system to ensure data pertaining to the Field base is not modified in the Main base.

Change Details

In order to ensure that a Field base transaction is not modified in the Main base, adequate logics and validations are built in the system. For example, a Stock Return document in ‘Draft’ status pertaining to a Field base will not be retrieved in the Main base for modification, cancellation or confirmation. The document would only be processed in the Field base. Following transactions are managed in a similar way:

Material Request

Stock Issue

Stock Return

Stock Transfer

Stock Receipt

Stock Correction

Though Main base cannot modify any of these Field base transactions, it is possible to view all of them.

Note:

i. Whenever parts are transferred between Main base and Field base, data extraction should be done to send the relevant data files for example, Stock Transfer Order and Stock Issue, so that Stock Receipt can be recorded.

ii. A mobile warehouse that can operate offline cannot participate in demand management functions.

iii. Material Requests raised in Field base cannot be used to initiate stock transfer or procurement in Main base.


Page 43 of 43

CCHHAANNGGEESS IINN FFIINNAANNCCEE

AAccccoouunnttiinngg iinn FFiieelldd bbaassee

Accounting for transactions in a Field base will be recorded but will not be posted to books of accounts. The transactions recorded and their related accounting will be posted to books of accounts in the Main base during synchronization of information from Field base to Main base.

There will be scenarios where the finance team is required to consider the transactions from Field base in order to finalize the financial statements for a period /year. In some cases, mostly in case of Period closures, they might decide to finalize their statements without considering transactions from Field bases. In such cases, transactions will be considered in subsequent months for finalization of books of accounts.

An option has been provided to the Finance team to decide on the processing of records from Field base.

Finance Setup > Company Parameter Setup > Set Parameters – Book Keeping

User can select the option – Allow Calendar Closure before Offline System

Processing

If set as No, system will not allow Calendar Closure before processing records from Offline System.

If set as Yes, system will allow Calendar Closure after end of period.

If the Option ‘Allow Calendar Closure before Offline System Processing’ is set as Yes, the user is required to provide the option to process records from Offline system after period closure. User has option to select

Current Period, to post transactions from Field base in the period in which synchronization is done.

Minimum Open Period, to post transactions from Field base in the latest Open financial period.

Corporate Office and R&D Center

Ramco Systems Limited, 64, Sardar Patel Road, Taramani, Chennai – 600 113, India Office + 91 44 2235 4510 / 3090 4000 Fax +91 44 2235 2884 Website ‐ www.ramco.com

© Copyright 2013, Ramco Systems Ltd. www.ramco.com Ramco Aviation Solution

http://www.ramco.com/