User Manual & Training Notes Ramp Error Decision Aid

AVIATION RESOURCE MANAGEMENT SYSTEM
SAFETY & QUALITY MANAGEMENT SUB-SYSTEM (SQMS)

V 2.5
User Manual & Training Notes

RAMP ERROR DECISION AID
Document Revision No: 1.0

Date of Release: 07/02/2017
Document File Name: UM_ARMS V2.5_SQMS_REDA-R1
© Sheorey Digital Systems Pvt. Ltd., Mumbai, India/ 2011~2019. All Rights Reserved
ARMS® and InfoPrompt® are Registered Trademarks of Sheorey Digital Systems Pvt. Ltd.
Action: Prepared By Checked By Approved By
Signature:
Name: Arvind V Jomon Sebastian Sk.Md. Riyaz

Designation: Project Manager Business Analyst Vice President
Department: Project Implementation & Delivery (PID) Project Implementation & Delivery (PID) Software Development (SWD)
SHEOREY DIGITAL SYSTEMS PVT. LTD.

An ISO 9001:2008 and ISO 27001:2005 Certified Software Company
Tarabai Hall, 1st Floor 97 Marine Drive Mumbai 400002 India
Tel: (+91-22) 2281 9198/ 2281 1086 Fax: (+91-22) 2281 9226
Website: www.sds.co.in
ARMS® - Aviation Resource Management System Safety & Quality Management Sub-System
USER MANUAL & TRAINING NOTES RAMP ERROR DECISION AID
CONTENTS
Section Page No.

1 Introduction 1
2 Accessing ARMS® V2-REDA 2
3 Data Flow Diagram - REDA 3
4 Explanation Notes On Screen Interface
4.1 Accessing REDA 4
4.2 REDA Interface 5
4.3 Introduction To Dashboard Filters and Columns 6
4.4 Dashboard Filter 7
4.5 Create REDA From Selected eReports 8
4.6 New REDA Reporting (Without eREPORT) 9
4.7 Create New REDA Report From a Single eReport 10
4.8 Create New Occurrence from Multiple eReport 11
4.9 REDA Report Management 12
4.10 REDA Details 13
4.11 Linked eReports 14
4.12 MOR Report Editor/ Report/ Notification 15
4.13 Occurrence Requisition 16
4.14 Evidence/ Attachments 17
4.15 Add Testamentary Evidence 18
4.16 Add Physical Evidence 19
4.17 Add Documentary Evidence 20
4.18 Add General Evidence 21
4.19 To Link & Unlink Items 22
4.20 REDA Checklist 23
4.21 Closure Summary 24
4.22 Cancel Occurrence 25
4.23 REDA Report 26
4.24 Event Log 27
4.25 Status Report 28
4.26 Action Response/ CAPA 29
4.27 Email Notification 33
INTENTIONALLY LEFT BLANK
1 INTRODUCTION
1.1 ARMS® V2 SQMS is a Sub-System of ARMS® V2 system with REDA as a module. This section of the User Manual explains
how to manage Ramp Error related incidents using REDA (including Initial Assessment, Part-B Investigation and MOR
Reporting) in an Organization. Since all the Sub-Systems of ARMS® V2 are integrated with each other, ARMS® V2.5 SQMS
(REDA) can be integrated with other Sub-Systems of ARMS® V2.5.
REDA – Ramp Error Decision Aid
1.2 Admin: Admin section is basically for the configuration and settings required to be done one time and at the starting of
application. Following are the features contained in this module.
1.2.1 Settings:
1.2.2 SQMS User Management.
1.2.3 User Group Mapping.
1.2.4 Color Manager.
1.2.5 Airline.
1.2.6 User Menu Rights.
ARMS® - SQMS/ REDA: Version: 2.5/ Revision: 1.0 Page 1 of 33

2 ACCESSING ARMS® V2 - REDA

2.1 ARMS® V2 HOME PAGE
Figure 1
2.1.1 Purpose: The purpose of the interface is to access the REDA Module.
2.1.2 Notes on the Screen Interface:
1 Click on ARMS® start button.
2 Place the cursor on SQMS, a drop-down menu will appear.
3 Click on REDA.
Page 2 of 33 ARMS® - SQMS/ REDA: Version: 2.5/ Revision: 1.0

3 DATA FLOW DIAGRAM - REDA
Figure 2

INTENTIONALLY LEFT BLANK
4 EXPLANATION NOTES ON SCREEN INTERFACE

4.1 ACCESSING REDA
Figure 3
4.1.1 Purpose: The purpose of the interface is to access the REDA.
1 Click on the ARMS start button.
2 A drop-down menu will appear; click on SQMS.
3 Click on the REDA.

4.2 REDA INTERFACE
1 6 7
3
4
8 9
Figure 4
4.2.1 Purpose: The purpose of the interface is familiarizing the REDA interface.
1 REDA side menu items
2 To Do List:
 EIS Dashboard: Over all status on Occurrence Reports raised and managed.
 New REDA Reporting: The REDA User can create and save a new Occurrence.
3 Dashboards: For accessing and managing the following.
 All Requisition: Details of the Requisitions sent by the User.
4 Event Log: Log on the actions carried out by the User in the module.
5 Forwarded eReport: all Forwarded eReport from REDA will display.
6 eReport Summary:
 Details of Source-wise eReports
 Status-wise count e.g. Accepted, Rejected, etc.
7 REDA summary: Status-wise count, MOR statistics, MOR ageing statistics.
8 eReport Dashboard to display all REDA eReports with status.
9 REDA reports Dashboard to display all REDA Occurrence Reports based on status.

4.3 INTRODUCTION TO DASHBOARD FILTERS AND COLUMNS
3
2
Figure 5
4.3.1 Purpose: The purpose of the interface to brief the Dashboard Preferences and Dashboard Filters.
1 This section contains the Dashboard Filters where using the required criteria the reports can be filtered.
2 This section contains Quick Filter to filter the reports within the grid view menu.
3 This section contains Column Settings to appear and dis-appear the headers of the grid view menu.

4.4 DASHBOARD FILTER
6
7
9
5
Figure 6
4.4.1 Purpose: The purpose of the interface to familiarize the Dashboard Filters and the Column settings.
1 Dashboard filter can be accessed by clicking the top right corner Occurrence filter dashboard button.
2 This option allows to filter Dashboard grid view by Occurrence ID, Reference no, Occurrence Title Date, etc.
3 This option allows to filter based on Date, Time and also predefined Last 10 days and Last 30 days filter.
4 Allows filtering based on Occurrence accepted date.
5 Also filter based on reported by, Ac Reg., etc.
6 Click on the Apply button to apply the filter criteria

Click on the Apply & Save button to apply the filter criteria and save it.
Click on the Clear button to clear the filter criteria
7 Contains Grid view column filter to set the desired column preference. Click on the reset button to appear
the default settings.
8 Select the columns to be displayed in the Dashboard grid view.
9 Click on the Save button to save the preference.

4.5 CREATE REDA FROM SELECTED eREPORT
Figure 7
4.5.1 Purpose: The purpose of the interface to show how to create the REDA from eReport.
1 eReport can be filtered based on report Id, Report Type, Source, Status, Saved by/Submitted by, who
submitted it etc.
2 Select the eReport by checking the box.
3 Click on the Create REDA button to create.

4.6 NEW REDA REPORTING (WITHOUT eREPORT)
4 3 2
Figure 8
4.6.1 Purpose: The purpose of the interface is to show how to perform the reporting of a new REDA.
1 Click on the New REDA Reporting side menu.
2 A New Occurrence Reporting popup opens up.
3 Click on the cancel button to discard the form.
4 Once the data is filled in the available section, click on the REDA Reporting button.
5 An Occurrence is created and the form is redirected to the REDA Report More info.

4.7 CREATE NEW REDA REPORT FROM A SINGLE eREPORT
2 3 4
Figure 9
4.7.1 Purpose: The purpose of this part of interface is to show how to create a new REDA from an eReport.
1 Select a submitted eReport in the grid view of the Dashboard.
2 Create new Occurrence by clicking on the Create new REDA button against eReport.
3 Click on the NFA button if the user wants to suspend the eReport.
4 Click on the Forward to ASR Manager, selected eReport will be forwarded to Safety system Admin.

4.8 CREATE NEW OCCURRENCE FROM MULTIPLE EREPORT
2 4 5
Figure 10
4.8.1 Purpose: The purpose of this part of interface is to show how to update the details for a new REDA Occurrence.
1 Select the multiple reports from the Dashboard by selecting the checkboxes, choose the type of Occurrence
report to be created by selecting the Occurrence type from the Create New Occurrence drop-down Tab.
2 Click on the Create REDA button.
3 A pop-up opens up with the report ID of the reports selected, Select the report of which details is required
for the new Occurrence creation.
4 Click on the Ok button to save the selection.

Note: Of all the selected reports one report will be selected for Occurrence Creation. The remaining
selected reports will be linked to this Occurrence.
5 Click on the cancel button to discard the action.

4.9 REDA REPORT MANAGEMENT
Figure 11
4.9.1 Purpose: The purpose of the interface is show how to perform the Analysis, Detail Gathering and Assessment of the
REDA.
1 REDA Management Dashboard – All REDA related links are displayed in addition to various tools to manage
the Occurrence is provided.
2 REDA details related links are grouped. User can view or update details by selecting any of the required
links.
3 REDA analysis related links are grouped. User can view or update details by selecting any of the required
links.
4 Under Conclusion, User can conclude the assessment of Occurrence and close the Occurrence.
5 Under Remedial action plan report, all assigned actions across the request can be seen with all the possible
root cause and CAPA details.
6 Log details can be viewed in Event Log and Status Report links.

4.10 REDA DETAILS
2
1
6 7 8
3
4
Figure 12
4.10.1 Purpose: The purpose of the interface is to show how to update the REDA Details.
1 On click of REDA Details side menu in REDA Management Dashboard, REDA details form is displayed.
2 eReport details are displayed for reference.
3 REDA details from is displayed.
4 Select MOR Action Yes or No.
5 Click on the New Request/ View Request to send the REDA request.
6 Click on the Update button to update the details.
7 Click on the Cancel button to discard the changes.
8 Click REDA Report button to generate the report.

4.11 LINKED EREPORTS
1
3
6
8
Figure 13
4.11.1 Purpose: The purpose of the interface is to show how to link Occurrence with an eReport, Occurrence, Hazard, Audit,
investigation and Requisition.
1 Click on the Linked eReports side menu.
2 In the Occurrence links section, Expand the linkable items tree and select Occurrence.
3 Selected Occurrence details can be viewed in this section.
4 Linked Occurrence: In this section, Occurrence linked in the past can be viewed.
5 Linkable Occurrence: Select the linkable items e.g. eReport, Occurrence, Hazard, Audit, investigation,
Requisition to link with the Occurrence Report.
6 Click on the Report Id to find the linked items details in the bottom section.
7 Click on the Link/Unlink item to link.
8 View Link Items can be used for reference.

4.12 MOR REPORT EDITOR/ REPORT/ NOTIFICATION
1
3
5
2
7
4
11
6
10
9
3
Figure 14
4.12.1 Purpose: The purpose of the interface is to show how to create a MOR Report and email it to the regulator.
1 Once the REDA work item has been saved under MOR category, Click on the MOR button.
2 Click the Report Editor tab. The first of the three tabs gets opened.
3 The Edit report offers a draft view of the MOR that has to be submitted to the regulator. The User can edit
the report.
4 Click on the Save button after editing the report.
5 Click on the Report tab to access the edited MOR report.
6 MOR Report details in the Regulator specified format.
7 Click on the Reporting Tab.
8 An email is composed with the MOR already attached for dispersal.
9 Enter the Message.
10 Enter the Address email ID and click on the Save button.
11 Click on the clear button to reset the form.

4.13 OCCURRENCE REQUISITION
6
2
7
1
Figure 15
4.13.1 Purpose: The purpose of the interface is to show how to send a FDMA Report Request.
1 Click on the New Request button to create and send a Requisition.
2 Enter the Requisition details in this section.
3 Select the check box to for considering for closure.
4 Click on the Send Requisition button to send request.
5 Requisition Dashboard: All requests with status will be displayed here.
6 Request Response from: On click of the View Response Action Party response will be displayed.
7 Click on the Save & Close button to save the response.

4.14 EVIDENCE/ ATTACHMENTS
1
6
2
3 4
7
Figure 16
4.14.1 Purpose: The purpose of the interface is to show how to add Testamentary Evidence.
1 On click of the Evidence/Attachment request link in Occurrence Management Dashboard and Evidence/
Attachment request form is displayed.
2 Click on the Evidence Link in the tree view menu and then click on the Testamentary.
3 Testamentary evidence page – contains Attach button to add files.
4 Attach window – To browse and attach the required file.
5 Attached files (or evidence) are displayed in this section.
6 Click on the Save button to save the attachments and Cancel button to discard the attachments.
7 Attached files are displayed in tree under Testamentary Evidence.

4.15 ADD TESTAMENTARY EVIDENCE
1 3
Figure 17
4.15.1 Purpose: The purpose of the interface is to save the Testamentary Evidence back to the Desktop.
1 Click on the Testamentary Evidence in the tree view menu. The evidence details form opens up.
2 Click on the view button to view the attached Testamentary Evidence.
3 Click on the Save As button to save a copy of the Testamentary Evidence.
4 A separate window opens to browse and save the Testamentary Evidence in the Desktop.

4.16 ADD PHYSICAL EVIDENCE
7 8
2
1 3
4
5
6
Figure 18
4.16.1 Purpose: The purpose of the interface is to add Physical Evidence.
1 Click on the Physical Evidence from the Evidence Tree view menu.
2 In the Physical Evidence Section, Fill the Evidence name in the text box.
3 Fill the Evidence description in this area.
4 Fill the Evidence location in this area.
5 Add button: To add evidence name, description and location details.
6 All Physical Evidence details are displayed in this section.
7 Click on the Save button to save the attachments.
8 Click on the Cancel button to discard the attachments.

4.17 ADD DOCUMENTARY EVIDENCE
4 5
2
1
Figure 19
4.17.1 Purpose: The purpose of the interface is to add Documentary evidence.
1 Click on Documentary Evidence from the Evidence Tree view menu.
2 In the Documentary Evidence section, Click on the Attach button to browse and add evidence files.
3 Attached files are displayed in this section.

4.18 ADD GENERAL EVIDENCE
4 5
2
1
Figure 20
4.18.1 Purpose: The purpose of the interface is to add General Evidence.
1 Click on the General Attachment from the Evidence Tree view menu.
2 Click on the Attach button to browse and add evidence files.
3 Attached files are displayed in this section.

4.19 TO LINK & UNLINK ITEMS
2
1
4
3
5
8
6
Figure 21
4.19.1 Purpose: The purpose of the interface is to Link and Unlink Occurrence with eReport, Occurrence, Hazard, Audit,
Investigation and Requisition.
1 Click on the Linked eReport from the side menu.
2 The Occurrence details can be viewed in this section.
3 Select linkable items from the tree view menu e.g. eReport, Occurrence, Hazard, Audit, investigation and
Requisition to link with the Occurrence report.
4 Linked Items: Linkable items linked in the past can be viewed.
5 New Linkable Items can be viewed in this Dashboard.
6 Click on the report Id to find the linked items details in the bottom section.
7 Click on the Link item to link the occurrence.
8 Click on View button to view the reports.
9 Click on the Unlink button to remove the linked incidents.

4.20 REDA CHECKLIST
4 5
2
1
3
Figure 22
4.20.1 Purpose: The purpose of the interface is to Create/ View the REDA checklist.
1 Click on the REDA Checklist side menu.
2 REDA Results form appears in this section.
3 Update the checklists in the General Information section.
4 Click on the Save button to save the changes.
5 Click on the Cancel button to discard the changes.

4.21 CLOSURE SUMMARY REPORT
2
4
3
7
8
5
10
11
Figure 23
4.21.1 Purpose: The purpose of the interface is to view the Closure Summary Report for the REDA work item.
1 Click on the Conclusion & Closure in the side menu.
2 Fill the remarks in the Occurrence conclusion field available.
3 Click on the Save button to save the Conclusion.
4 Click on the Close REDA Report to precede the closure.
5 Occurrence validation report while closing is displayed.
6 All validation items and status are displayed in the table.
7 This section contains Closure remarks fields.
8 Click on the Close REDA Report button to close the REDA work item.
9 Occurrence reopen tab - To reopen the closed REDA work item.
10 Fill the reason for reopening the REDA work item.
11 Reopen button - To re-open the REDA work item.

4.22 CANCEL OCCURRENCE
Figure 24
4.22.1 Purpose: The purpose of the interface is to cancel the REDA work item.
1 Click on the Cancel REDA work item button to discard the REDA Report.
2 Fill the cancelation remark in the available field.
3 Click on the Ok button. Status will be changed in canceled REDA.

4.23 REDA REPORT
3
4
Figure 25
4.23.1 Purpose: The purpose of the interface is to Display the REDA Report.
1 On click of REDA Report, Report is displayed.
2 REDA Report display area.
3 Click on the Export button to export the REDA Report.
4 Click on the Print button to print the REDA Report.

4.24 EVENT LOG
Figure 26
4.24.1 Purpose: The purpose of the interface is to show how to access the Event Log Details.
1 Click on the Event log side menu from the Log Details home group menu.
2 Event Log tab from is displayed.
3 Log details of every event of MEDA are also displayed.

4.25 STATUS REPORT
Figure 27
4.25.1 Purpose: The purpose of the interface is to show how to display current status report.
1 On click of the Current Status link in REDA Management Dashboard Current Status tab is displayed.
2 Current Status of REDA is displayed.
3 All action statuses, activities and date of activities are displayed.

4.26 ACTION RESPONSE/ CAPA
4.26.1 ACTION RESPONSE/CAPA DASHBOARD
1 2
Figure 28
4.26.1.1 Purpose: The purpose of the interface is to show how to display all actions assigned to user from different modules.
4.26.1.2 Notes on the Screen Interface:
1 Click on the Action Response status home group menu.
2 In the Executive Information Systems (EIS): All actions will be classified as Module wise, Types, CAPA Types
and Status wise.
3 Action Dashboard: Click on the particular Action ID link to view the Action details.

4.26.2 REQUISITION RESPONSE
11 3 4
5
6 10
7
2
Figure 29
4.26.2.1 Purpose: The purpose of the interface is to show how to display the User Response to a Requisition.
1 Fill the appropriate fields in the Request Details section.
2 Click on the Request Source Details link from the Source ID to view the source details in a separate tab.
3 In the Occurrence Request Details tab, select the Part B Action requirement as Yes or NO from the drop-
down list box.
4 Select the MOR Action as Yes or NO from the drop-down list box.
5 Click Part B Investigation to proceed with Investigation.
6 Fill the Response submission Remarks in the field available.
7 Fill the Root Cause in the field available.
8 Fill the Add Corrective Action in the field available.
9 Fill the Add Preventive Action in the field available.
10 Click on the Browse button to add an attachment if required.
11 Click on the Submit Response button to send the response.

4.26.3 REDA INVESTIGATION
7 1
5 6
Figure 30
4.26.3.1 Purpose: The purpose of the interface is to show how to use the REDA (Ramp Error Decision Aid) to perform an
investigation.
1 Click on the PART-B investigation button.
2 The form is redirected to the REDA Investigation tool comprising of checklist items. Click on the node and
details can be entered for the same.

3 Fill the checklist.
4 Click on the Update button after the checklist had been filled.
5 Enter the corrective and preventive action implemented in the available field.
6 Click on the Browse button to attach document, if any.
7 Click on the Submit Response button to submit the response.
Note: REDA is a widely accepted tool devised by Boeing and is provided in CAPA under Occurrence
Requisition, it can be used as a tool in investigation.

4.26.4 EMAIL NOTIFICATION
# Notification Type Event description Recipients
1 Request Sent REDA request send for Assessment To the email submitter and
acceptor.
2 Request Submitted When REDA request been responded. To the email submitter and
acceptor
3 Request accepted When an REDA request is accepted. To the email submitter and
acceptor
4 Request response rejected When an REDA request response rejected. To the email submitter and
acceptor
5 REDA e report submission When an REDA eReport is reported. To the email submitter and
acceptor
6 report accepted as REDA When an REDA eReport is accepted. To the email submitter and Rejecter
7 eReport rejected by REDA When an REDA eReport is rejected by REDA All request action parties
Manager Manager.

User Manual & Training Notes Ramp Error Decision Aid

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

User Manual & Training Notes Ramp Error Decision Aid

Uploaded by

Copyright:

Available Formats

AVIATION RESOURCE MANAGEMENT SYSTEM

SAFETY & QUALITY MANAGEMENT SUB-SYSTEM (SQMS)

User Manual & Training Notes

Document Revision No: 1.0

Action: Prepared By Checked By Approved By

Name: Arvind V Jomon Sebastian Sk.Md. Riyaz

SHEOREY DIGITAL SYSTEMS PVT. LTD.

Section Page No.

1.2.2 SQMS User Management.

1.2.3 User Group Mapping.

1.2.4 Color Manager.

1.2.6 User Menu Rights.

ARMS® - SQMS/ REDA: Version: 2.5/ Revision: 1.0 Page 1 of 33

2 ACCESSING ARMS® V2 - REDA

2.1.2 Notes on the Screen Interface:

1 Click on ARMS® start button.

2 Place the cursor on SQMS, a drop-down menu will appear.

Page 2 of 33 ARMS® - SQMS/ REDA: Version: 2.5/ Revision: 1.0

3 DATA FLOW DIAGRAM - REDA

ARMS® - SQMS/ REDA: Version: 2.5/ Revision: 1.0 Page 3 of 33

4 EXPLANATION NOTES ON SCREEN INTERFACE

4.1.1 Purpose: The purpose of the interface is to access the REDA.

4.1.2 Notes on the Screen Interface:

1 Click on the ARMS start button.

2 A drop-down menu will appear; click on SQMS.

3 Click on the REDA.

Page 4 of 33 ARMS® - SQMS/ REDA: Version: 2.5/ Revision: 1.0

4.2 REDA INTERFACE

4.2.2 Notes on the Screen Interface:

1 REDA side menu items

5 Forwarded eReport: all Forwarded eReport from REDA will display.

8 eReport Dashboard to display all REDA eReports with status.

ARMS® - SQMS/ REDA: Version: 2.5/ Revision: 1.0 Page 5 of 33

4.3 INTRODUCTION TO DASHBOARD FILTERS AND COLUMNS

4.3.2 Notes on the Screen Interface:

Page 6 of 33 ARMS® - SQMS/ REDA: Version: 2.5/ Revision: 1.0

4.4 DASHBOARD FILTER

4.4.2 Notes on the Screen Interface:

4 Allows filtering based on Occurrence accepted date.

5 Also filter based on reported by, Ac Reg., etc.

6 Click on the Apply button to apply the filter criteria

8 Select the columns to be displayed in the Dashboard grid view.

9 Click on the Save button to save the preference.

ARMS® - SQMS/ REDA: Version: 2.5/ Revision: 1.0 Page 7 of 33

4.5 CREATE REDA FROM SELECTED eREPORT

4.5.2 Notes on the Screen Interface:

2 Select the eReport by checking the box.

3 Click on the Create REDA button to create.

Page 8 of 33 ARMS® - SQMS/ REDA: Version: 2.5/ Revision: 1.0

4.6 NEW REDA REPORTING (WITHOUT eREPORT)

4.6.2 Notes on the Screen Interface:

1 Click on the New REDA Reporting side menu.

2 A New Occurrence Reporting popup opens up.

3 Click on the cancel button to discard the form.

ARMS® - SQMS/ REDA: Version: 2.5/ Revision: 1.0 Page 9 of 33

4.7 CREATE NEW REDA REPORT FROM A SINGLE eREPORT

4.7.2 Notes on the Screen Interface:

1 Select a submitted eReport in the grid view of the Dashboard.

Page 10 of 33 ARMS® - SQMS/ REDA: Version: 2.5/ Revision: 1.0

4.8 CREATE NEW OCCURRENCE FROM MULTIPLE EREPORT

4.8.2 Notes on the Screen Interface:

2 Click on the Create REDA button.

4 Click on the Ok button to save the selection.