Tech Session (Board Repair) - Ryan Michelson - Portfolio

jumentousklipitiklopSoftware and s/w Development

Oct 30, 2013 (4 years and 8 days ago)

109 views

0








Software Functionality, Use Cases, Migration Options, and Workflow Improvements

This re
port documents the functionality of the repair station management software “Progress”
and repair stati潮 business pr潣esses that it supp潲ts. Additi潮ally, the rep潲t analyzes
upgrade vs. migrati潮 潰ti潮s and rec潭mends impr潶ements t漠existing w潲kfl潷.



Universal Avionics


Repair Station


1


1.

Introduction

Our team of five Master’s in Information Systems students from the University of Arizona was
contracted by Universal Avionics
to document the functionality of

the
ir repair station’s work flow
management software, “Progress.”
The current version of Progress licensed to Universal Avionics
runs on Windows server 2000; a platform that Microsoft no longer supports.
Due to this fact, upper
management has

mandate
d

t
hat all departments migrate to newer,
fully
supported software in the
near future. One option is to upgrade the company’s enterprise license to allow operation on the
latest version of Windows server. Alternatively, the repair station could transition aw
ay from
Progress completely and customize an out
-
of
-
the
-
box software solution to meet its workflow needs.


In addition to documenting the repair station’s functional requirements, this report
outlines
advantages and drawbacks to the various migration and u
pgrade options and analyzes

the
feasibility of substituting a commercial off the shelf
product.


Lastly,
our analysis provides suggest
ions for improving upon existing business process
es

at
Universal Avionics and the extent to which each software implemen
tation can accommodate these
changes.
The repair station’s w
orkflow is tightly integrated with software functionality; as
extensive customization of the

Progress

application has been performed on demand throughout the
12 years of its operation.



1.1.
Project

Information


Project Title:

Universal Avionics Repair Station Work Flow


Prepared by:


Bradley Demirjian, Seong Rog Do, Nivedita
Kamat, Shruti Singh, Ryan Michelson


Date:


May
4, 2011


1.1.1


Stakeholders




Position

Title/Name/Organization

E
-
mail

Project

Sponsor

David E. Pingry

pingry@email.arizona.edu

Project Sponsor

Andy Seaton

N
/
A

Program Manager

Lewis Butler

lbutler@uasc.com

Key Stakeholders

Fred Schmidt

Bill Froehlich

Dan Borboa

Michael Wegrzynowski

N
/
A


2

1.1.2


Team Overview

This
report has been
prepared by a team comprised of five Master’s in Management Information
System’s students (Ryan Michelson, Bradley Demirjian, Shruti Singh, Nivedita Kamat, and Seong
Rog Do from the Eller School of Business at The University of Arizona. A profile of each
team
member and their resumes


are

provid
ed in Appendix
F

(Team Profile)
.

1.1.3


Method
ology

The team’s interaction with Universal Avionics included seven on
-
site

visits conducted by Ryan
Michelson and Bradley Demirjian, and one off
-
site visit with the entire team.
During the on
-
site
visits,
we were

able to experience the repair center process first
-
hand and interact with the actual
users of the system.


Due to
the

complexity of the process
es, we decided to document requirements at a high level
,
excluding granular fields and functions that were not critical.
The
methods employed

to document
existing processes

include
d

workflow diagrams, graphical and text
-
based
use
-
ca
ses, and
requirements matrices. Requirements obtained from company employees were recorded in a
requirements matrix and the associated component, related business process, and source of

the

requirement was noted. Items requested for future implemen
tation were labeled, “feature
requests,”

and included with related requirements in the matrix.


1.2.
Objectives

Our primary task was to analyze the current repair station system and provide upper management
with an overview of the application’s functionalities.
Furthermore, we were tasked with the
following ancillary objectives:



Identify and document the business processes that are currently performed by the Repair
Station.




Identify and document the functional and nonfunctional business requirements for a work
o
rder system supporting these business processes.




Prioritize the business requirements and processes, identifying which business processes
are critical to the operation of the Repair Station.




Determine and recommend whether work order functionality should

be custom built or
purchased and then customized.




Deliver the documentation necessary for the organization to make a strategic decision


In addition to fulfilling these objectives, our team has also

considered

the

advantages and
drawbacks to potential so
ftware upgrade options. To this end, we have also

provide
d

a short list of
recommended commercial software.


1.3.
Company Overview


Universal Avionics (UA), founded in 1981 is an international company headquartered in Tucson,
Arizona. The primary focus of the company is to manufacture, repair and maintain Flight
Management Systems. The organization is composed of four divisions namely
: the Manufacturing

3

and Marketing Division in Tucson, the Research/Development/Engineering Division in Redmond
and the Instrument Division in Duluth. UA has two repair stations. One is located in Tucson,
Arizona and the other in Wichita, Kansas. The main

features offered in these repair stations are:




Technical Support



Loaners



Rentals



Exchanges



OEM Support


The manufacturing and repair stations operate as separate business units. While the scope of this
project focused primarily on the Tucson based repair station, the company
-
wide impact of our
recommendations was taken into consideration.

2.

Business Problem


The
Progress

software application

was

developed on the fourth generation programming language

OpenEdge.


This platform is housed on a
Windows 2000 server environment;

which is no longer
supported by Microsoft.

The manufacturer
has discontinued all patch
es, updates, and technical
assistance

for the operating system
. The risks of operating on an un
-
supported platform are
significant enough that

UA

management has

decided to mandate that all departments migrate

to a
newer platform. While the recent version o
f Progress, Open Edge 10, is compatible with newer
versions of Windows Server, estimates of obtaining the required enterprise
-
wide license range
from $100,000
-

$300,000. Furthermore, the majority of departments within Universal Avionics
h
ave already phas
ed out Progress. Unfortunately, the lack of a coordinated migration strategy has
resulted in
a decentralized mix of disparate systems. Integrating Progress with these new system
architectures and establishing meaningful interactivity

between them is diff
icult.


Alternatively, UA could migrate the repair station’s software

to a new
er, more robust

platform
.
This

also has negative implications. The Progress software application d
eveloped for the Repair
Station

is the product of 12 years of extensive custom
ization. Functionality was tailored tightly to
business processes and was customer
-
driven. UA’s focus on

exceptional

customer service
prompted the development of interfaces and logic that were designed to accommodate the specific
needs and
idiosyncrasies

of clientele. Furthermore, the programming was performed by a single
UA employee and proper documentation was not kept. This has resulted in a complex system that
has significant inherent value, but is somewhat cryptic and highly difficult to replicate.

Reportedly,
there are over 1000 logical r
ules built into the code alone.


The organization is faced with a difficult decision to

either

upgrade the Progress system to Open
Edge 10
,

or migrate to a
separate

platform. Additional cost
-
benefit and implemen
tation
recommendations

of these options

are provided in the second half of proceeding analysis.


2.1.

Business Considerations


Any change made to the current

system will
have an impact on the entire organization. I
t is
important to recognize
the full impact of upgrad
ing

before the plan is implemented.



4

2.1.1


Core Business Activities Impacted


Core Business Activity

Impact on Core Business Activity

Repair Station

Provide a solution that maintains the functionality of the
current system and is scalable enough to furnish
future
sustainability of the process.

Information Security

Encourage the security of the organization’s information

by migrating off the unsupported software.

IT Development

Generate documentation to assist future development.


2.2.
Key Factors

Timing

Due to the instability of the current infrastructure, it is critical to implement the new system as
quickly as possible. The migration must be carefully planned as to minimize the disruption of
critical
process
es
.

Funding

Universal Avionics should be prepa
red to make a large investment in the final solution.
Extensive
costs should be expected from hardware, software, and labor.

Personnel

Depending on the technology, Universal Avionics may need to acquire additional personnel. Such a
high dependency on
one

s
enior programmer

for software development

is likely to
beco
me an issue
in the long run.

Customer Satisfaction

Universal Avionics prides
itself in customer satisfaction

and must
ensure

that
any potential solution
caters to

the short and long term needs of
i
ts
clients.

2.2.1


Constraints




Time (unsupported system

should not be used for much longer
)



Resources (lack of programmer
s
)



Effective communication (communication between

managers

and
executives
)



Integration

(how well can the system interact with other systems)

2.2.2


Risks


Low (1
-
3)


Medium (4
-
6)


High (7
-
10)





Risk Item

Risk Score


Budget


What level of risk does the proposed budget represent to the project?


2


5


Operating on un
-
supported software


What is the risk of maintaining the current system past the date of
Microsoft’s support?

6


Disruption to Business Activities


To what level will the implementation affect business activities?

9


Stakeholder Resistance


How much resistance will key stak
eholders have towards the
recommended solution?

10


3.


System Work Flow

The repair station
’s workflow is a complex process

that ensures that a unit sent in for repair is
received, the problem is thoroughly analyzed, fixed, documented, tested, and re
-
tested

and all of
this is done in full compliance with FAA standards and regulations. In order to achieve this and
accommodate specific requests from repeat customers, Progress contains an extensive set of logic
rules that guide a user through the repair proces
s and prevent the user from entering incorrect
information.


2.3.
High
-
Level Process Map

The diagram on the next page depicts a high
-
level view of the repair center process. It is apparent
from the workflow that there are multiple paths a unit sent in for repai
r can take. For example, if
the customer does not exist, the user is prompted to contact the marketing department. Also,
depending on the circumstance, a box can be categorized as a loner, rental, or repair. While each
box may take slightly different pa
ths, the overall process is very similar.

The following diagram

on the next page

depicts a high
-
level vie
w of the repair center process:










6


7


4.

Core Modules

In order to clearly convey the
function of each component process in Progress, we clustered specific
tasks into a set of processes referred to as core modules. Our team identified the following core
processes/modules:




Claim Order



Tech Session Board Repair




Tech Session




Stock Room




Expeditor




Quality Insurance




Administrative Tasks



Each
core module represents a primary function of the application and is consistent with business
process and separation of duties as a unit sent in for repair travels through repair process. Every
step

of the repair process is facilitated by the Progr
ess system.
O
ver 1,000 backend checks

have
been developed

to assure quality control and FAA compliance.

Though it was not feasible to
capture the entirety of these rules, the most significant ones have b
een recorded in the
requirements matrix under the component label, “Logic.”


For each core module, we have provided the following documentation:




Use Case Diagram





Represent the high level processes involved in the module.



Use Case Descriptions



Step
-
by
-
step breakdown of each Use Case.



Requirements Matrices





List of
requirements gathered

from meetings
.


The Use Case
diagrams demonstrate how a user interacts with a particular module and are
elaborated upon in the textual
descriptions

that follow. This outlines the steps that a user must
take in order to perform a specific function in the system.

The alphanumeric “ID” in parenthesis
,

following each use case instance
,

references the related requirement(s) from the matrix.


Disclaimer:

Due to limitations on our ability to access the system, the

following

use cases by no
means represent every possible function or feature; only a prioritized selection of them.
Additionally,
while the steps listed are representative of the act
ual process used in Progress, the field labels and
actions are not an exact match. They are merely summarizations; simplified to facilitate
easier
understanding.

The actual process of performing the listed functions in Progress is more complex than
state
d.


8


4.1.
Claim Order

The Claim O
rder module begins the repair process

and checks the unit in

after it has been
processed by the shipping department. An

initial inspection

to determine the extent of the repairs
needed

is

also

performed

at this point
. It is then marked as a loner, rental, or exchange and sent to
the
technician
s

for
repair.


4.1.1

Use

Case
s
: Claim
Order
























Receive Box for Repair (C0


C9, PI1


PI6, W1


W5)


1.

Open claim order entry screen

2.

Enter part and serial number

3.

Verify part number, serial number, customer exist

4.

System verifies purchase date

5.

System displays warranty
information

6.

Create new claim order

7.

Enter squawk and shipping information

8.

Open preliminary inspection sub
-
screen

9.

Inspect outer damages on box

10.

Enter condition of box from pre
-
canned statements

11.

On claim order screen, select ‘receive box’

12.

Stock transferred to
technician bin

13.

Place box on shelf for technicians to pick up


9

Alternate Flow (check customer NC2) [if part or serial does not exist]

1.

Open customer maintenance

2.

Search for customer

3.

Verify if customer exists

Alternate Flow (create new customer NC1


NC3, A1


A3) [if customer does not exist]

1.

Check denial list

2.

Enter new customer information

3.

Set credit limit



Receive Loaner/Rental/Exchange (C01


C09)


1.

Open claim order entry screen

2.

Pull up original work order

3.

Inspect outer damages on box

4.

Enter condition of box f
rom pre
-
canned statements

5.

Close work order

6.

Open new work order

7.

Inventory is transferred to stockroom BIN





4.1.2

Requirements Matrix
: Claim Order


ID

Component

Process

Source

Description

CO1

Logic

Claim
Order

3
-
4 Meeting

Pop up a notification that 90 day
warranty is current if
the unit has recently been in for repair

CO2

Fields

Claim
Order

3
-
4 Meeting

Allow a claim to be categorized based on the following
claim codes: Warranty or Non
-
Warranty, Consignment
Returns (units that we own that let people
borrow),
Scrap unit, Trade in Core Return(upgrade to newer
version), Known or Unknown Dollars, Loaner, Rental
Unit (based on warranty status), Exchange Codes
(warranty, non
-
warranty)

CO3

Logic

Claim
Order

3
-
4 Meeting

Filter fields based on claim code

CO4

Features

Claim
Order

3
-
4 Meeting

Track if an item has been received for processing

CO6

Features

Claim
Order

4
-
8 Meeting

Provide the ability to create a pick ticket for loaners and
an amended packing slip, similar to orders

C07

Features

Claim
Order

3
-
4 Meeting

Allow for three different types of boxes


repair, loaner,
or exchange

C08

Features

Claim
Order

3
-
4 Meeting

Allow for three different work order types
:

repair,
manufacturer, or brand new (p)

C09

Features

Claim
Order

3
-
4 Meeting

Provide
ability for employee to enter squawk
information

NC1

Features

New
Customer

3
-
4 Meeting

Allow customers to be categorized by type. The
customer type will determine the pricing


10

NC4

Features

New
Customer

3
-
4 Meeting

Ability to create accounts receivable rec
ords for the
customer. One for the billing account and one for the
shipping account.

PI1

Fields

Preliminary
Inspection

3
-
4 Meeting

Provide pre
-
canned statements about item condition
including: Quality Seal, Keying, Connection condition,
Lens Scratched

PI2

Logic

Preliminary
Inspection

3
-
4 Meeting

Trigger hidden damage inspection based on the
selection of specific condition keywords

PI3

Fields

Preliminary
Inspection

3
-
4 Meeting

Allow the entry of squawk details including red label, out
of box failure, et
c.

PI4

Integration

Preliminary
Inspection

3
-
4 Meeting

Pull service bulletin from UNINET and Dynamically
display the status for each part

PI5

Fields

Preliminary
Inspection

3
-
4 Meeting

Assign a turnaround date, 5
:
7 days unless otherwise
specified

PI6

Fields

Preliminary
Inspection

3
-
4 Meeting

Provide the ability to select a shipping method based on
a list of vendors

A1

Logic

Accounting

3
-
4 Meeting

Prompt accounting to place credit hold on account if it is
past due +60 days

FUTURE REQUIREMENTS

CO5

Feature
Requests

Claim
Order

2
-
18 Meeting

Provide the ability to have a customer create an order
request online to submit to UA

NC2

Feature
Requests

New
Customer

3
-
4 Meeting

Ability to check the denial list from inside the
application.

NC3

Feature
Requests

New
Customer

3
-
4 Meeting

Ability to send new customer requests electronically

A2

Feature
Requests

Accounting

3
-
4 Meeting

Provide the ability to interface with Four shift software,
specifically for credit hold information

A3

Feature
Requests

Accounting

3
-
4 Meeting

Generate Past purchase order summary for customer

W1

Feature
Requests

Warranty

4
-
8 Meeting

Electronically receive point
-
of
-
sale paperwork from
distributor including warranty card

W2

Feature
Requests

Warranty

4
-
8 Meeting

Automatical
ly extend warranty 90 days after a product
has been repaired.

W3

Features

Warranty

4
-
8 Meeting

Pop notification if product has been in for repair within
the last 90 days

W4

Feature
Requests

Warranty

4
-
8 Meeting

Create a module capable of accommodating
more
extensive and flexible warranty information

W5

Feature
Requests

Warranty

4
-
8 Meeting

Provide the ability to accommodate new extended
warranty purchase option



4.2.
Tech Session

The Tech Session is the module that the technician uses to perform
extensive
testing and
to
document the repairs made to the un
it. The majority of Progress’
functionality and features are
available
via the

Tech Session. The technician can view a full history of the board

including prior
repairs made
as

well as

components and boards
that have been swapped out of the unit.




11

4.2.1


Use Case
s
: Tech Session

















































12

Damage Inspection (TS1


TS3)


1.

Technician performs an ESD test prior to login to activate the system

2.

The technician logs into Progress by entering username and password

3.

The technician enters the work order number into the appropriate field

4.

Technician enters part # for the unit which triggers display of CMM Manual



View Historical Information Related to Unit (TS4


TS7, TS15,)


1.

Technician logs into the system

2.

Technician
enters work order # into the appropriate field.

3.

Basic Fields (Part #, Serial #, Customer Info) are pre
-
filled from previous Claim Order Entry.

4.

Summary Information from preliminary inspection is displayed including
squawk
.

5.

The user clicks on the History tab

to view unit and board history information



View Technical Specs (TS8, TS12, TS23)


1.

Technician logs into the system

2.

Technician enters work order # into the appropriate field.

3.

The user clicks on the board configuration tab to view the configuration specs
for th
e parts
that are
currently in the unit

4.

The user clicks on a particular component to view all service bulletins related to unit

5.

A reference list of Mods available is displayed



Perform ATE Tests (TS24, TS25)


1.

Technician logs into the system

2.

Technicia
n enters work order # into the appropriate field.

3.

Technician clicks on the Testing button

4.

A list of instructions for testing procedures is displayed

5.

Technician uses attached hardware to perform ATE tests.



Recording results of inspection (TS25, TS2
6
)


1.

Technician logs into the system

2.

Technician enters work order # into the appropriate field.

3.

Technician clicks on the inspection tab.

4.

The user selects from a list of pre
-
canned statements about item condition

5.

Additional
squawk

details are entered as necessar
y.

6.

A hidden damage inspection is triggered depending upon the condition selections made



Completing the Tech Session (TS14, CA2)


1.

Technician logs into the system


13

2.

Technician enters work order # into the appropriate field.

3.

Technician clicks on the “complete
” tab

4.

The unit is marked for return to vendor

5.

The technician prints labels to adhere to box via the “print” tab that pulls data entered in
fields into a pre
-
formatted label design.



4.2.2

Requirements Matrix
: Tech Session


ID


Component


Process


Source


Description

TS1

Logic

Tech
Session

3
-
4
Meeting

System dynamically checks to ensure technician logged in is
qualified for inspection

TS2

Logic

Tech
Session

3
-
4
Meeting

Ensure that ESD test is performed before technician can log in

TS3

Features

Tech
Session

3
-
4
Meeting

Entry of part # brings up CMM manual for each part

TS4

Logic

Tech
Session

3
-
4
Meeting

Information from basic fields brought over from Claim Order
Entry i.e. Part #, Serial #, Customer Info

TS5

Design

Tech
Session

3
-
4
Meeting

Provide
views of summary information from preliminary
inspection

TS6

Design

Tech
Session

3
-
4
Meeting

Provide pre
-
filled summary of
squawk

TS7

History

Tech
Session

3
-
4
Meeting

Provide the ability to view a complete history of the unit i.e.
Previous owners, prior
work completed

TS8

Features

Tech
Session

3
-
4
Meeting

Provide a reference of Mods available

TS9

Features

Tech
Session

3
-
4
Meeting

Provide the ability to run a report of unit and board failure
history

TS10

Features

Tech
Session

3
-
4
Meeting

Provide the
ability to print a summary of the work order

TS11

Features

Tech
Session

3
-
4
Meeting

Provide the ability to convert part # and serial #


14

TS12

Features

Tech
Session

3
-
4
Meeting

Show the configuration specs of boards that are currently in
unit

TS13

Logic

Tech
Session

3
-
4
Meeting

Scrapping a board automatically pulls it from the inventory
list

TS14

Fields

Tech
Session

3
-
4
Meeting

Provide pre
-
canned statemen
t

for “Send to Vendor”

TS15

Design

Tech
Session

3
-
4
Meeting

Provide the ability to view
squawk

and p
revious repairs for a
unit

TS16

Features

Tech
Session

3
-
4
Meeting

Allow the ability for a tech to make a granular listing for
charges including changed par

TS17

Fields

Tech
Session

3
-
25
Meeting

Provide the ability to denote status of Nav Database

TS18

Fields

Tech
Session

3
-
25
Meeting

Update ETI counter information on board denoting amount of
time that it has been functioning

TS19

Features

Tech
Session

3
-
25
Meeting

Provide the ability to enter pre
-
filled required FAA
information filtered by prior
selections

TS20

Fields

Tech
Session

3
-
25
Meeting

Allow entry of a BIN ordering form for smaller par; not a
board or box

TS21

Features

Tech
Session

3
-
25
Meeting

Par request by Part #, W/O, notes, quantity

TS22

Features

Tech
Session

3
-
25
Meeting

Provide
the ability to insert Service Bulletin commen
t

into the
work order

TS23

Features

Tech
Session

3
-
25
Meeting

View all service bulletin instructions related to component

TS24

Features

Tech
Session

3
-
25
Meeting

View all testing procedures

TS25

Features

Tech

Session

3
-
25
Meeting

Allow the technician to perform and record resul
t

of ATE tes
t

TS26

Logic

Tech
Session

3
-
4
Meeting

Trigger hidden damage inspection based on the selection of
specific condition keywords


15



4.3.
Tech Session


Board Repair

The board repair aspect of the tech session focuses on repairing individual components, primarily
adding, removing, and exchanging circuit boards.

The process is initiated when a technician
receives a component from a box.

4.3.1
Use Cases
: Tech Session (Board Repair)




TS27

Fields

Tech
Session

3
-
4
Meeting

Provide
pre
-
canned statements about item condition
including: Quality Seal, Keying, Connection condition, Lens
Scratched

TS28

Fields

Tech
Session

3
-
4
Meeting

Allow the entry of
squawk

details including red label, out of
box failure?

CA2

Labeling

Certified
Airman

2
-
25
Meeting

Send label information from field inputs to CodeSoft


16


Recording repairs made to unit/board (CB1, CB3, CB5, CB7, TS7, TS19)


1.

Technician logs
into the system

2.

Technician enters work order # into the appropriate field.

3.

Technician verifies that board # and serial # are accurate

4.

The user selects the particular board or component that has been repaired

5.

The user clicks on the repair action tab

6.

Fields
are provided for repair action taken, part number of component, and reason

7.

The technician selects from a list of canned descriptions to denote item condition

8.

Required FAA information fields are displayed based upon prior selections

9.

Technician finishes fil
ling out all fields

10.

Technician enters labor hours performed on the repair



Converting Parts (TS13, TS18, TS11, TS22,
CB8)



1.

Technician logs into the system

2.

Technician enters work order # into the appropriate field.

3.

Technician performs tests and records re
pairs made to each component

4.

The user navigates to the repair action tab

5a. The “convert” button allows entry of new part # / serial #

Alternate Flow (
add/remove parts CB8
)


5b.

The “add component” button allows entry of new part information

6.



ETI counter information denoting board operation time is adjusted

Removing boards and other components (TS13)


5c.
The “remove component” button allows removal of an existing part

6.
Boards that are removed and are no longer operational are marked as
“scrapped”

7.
Scrapped boards are automatically taken off of the inventory list



Updating the work order (TS16, TS17, TS18)


1.

Technician logs into the system

2.

Technician enters work order # into the appropriate field.

3.

Technician performs tests and
records repairs made to each component

4.

The user navigates to the update information tab

5.

Changes to unit configuration are made

6.

The Nav database is updated with the current information

7.

The technician is provided with a granular list of customer charges.

8.

Any

changed parts or information related to labor hours can be altered
, pro
-
rated, etc… to
reflect an
accurate list of costs




17

4.3.2

Requirements Matrix: Tech Session


Board Repair




4.4.
Expeditor

The expeditor receives the repaired unit and prepares it for the final stages in the process. It is in
this step where the majority of interaction with the customer occurs.

Examples of such interaction
are
cost quote
s when the unit has been marked as Hold

for

Cost.


4.4.1

Use Cases

:

Expeditor









ID


Component


Process


Source


Description

CB1

History

Tech
Session
-

Board

2
-
25
Meeting

Provide the ability to view the full history of a board, from
its serial number

CB2

Fields

Tech
Session
-

Board

2
-
25
Meeting

Distinguish between M, R, and P Types

CB3

Features

Tech
Session
-

Board

2
-
25
Meeting

Provide the ability to
auto fill

pre
-
canned descriptions of
board condition

CB4

Logic

Tech
Session
-

Board

2
-
25
Meeting

Board repair action window pops up when 0 is the first
alphanumeric of part number

CB5

Fields

Tech
Session
-

Board

2
-
25
Meeting

Provide fields for repair action taken, part number of
component, and reason

CB6

Features

Tech
Session
-

Board

2
-
25
Meeting

Track parts at the granularity of each individual component
on a board

CB7

Fields

Tech
Session
-

Board

2
-
25
Meeting

Allow
technician to enter labor hours performed on repair

CB8

Features

Tech
Session
-

Board

2
-
25
Meeting

Provide the ability to add a new part to the
work order

and
existing unit


18





























Expedite Tech Work Order (E1


E7)


1.

Open work order inquiry

2.

Enter claim order number

3.

Verify part and serial number

4.


View shipping information

5.

View customer information

6.

Determine if HFC

7.

Print Traveler slip

8.

Bring box to QA and scan barcode to transfer box to department

Alternate Flow (create cost quote E3) [if HFC]

1.

Open work order inquiry screen

2.

Enter claim order number

3.

Generate cost quote

4.

Print cost quote

Alternate Flow (create invoice
E3) [if high dollar value]

1.

Open work order inquiry screen

2.

Choose cost estimate template

3.

Add high
-
dollar comments


19

4.

Print cost estimate

5.

Send to customer



Alternate Flow (create final cost/invoice E3) [if customer fails to respond in 7 days]

1.

Add final cost co
mment to template

2.

Print final cost form

3.

Send final cost form to customer

4.

Create invoice

5.

Print invoice and hand over to marketing department

Alternate Flow (modify cost E3) [if cost incorrect]

1.

Open cost submenu inside claim order screen

2.

Add cost to work
performed by technician

3.

Save updated cost





Expedite Return to Vendor (E1


E7)


1.

Look up work order history for vendor and reason for RTV

2.

Open return to vendor screen

3.

Enter department, employee and property owner

4.

Enter Part and Serial Number

5.

System
creates MRF (material return form)

6.

System creates traveler

7.

Return # becomes PO (used to retrieve RMA number from vendor)

8.

Enter RMA number into system once it is received

9.

Print traveler slip

10.

Bring box to QA and scan barcode to transfer box to department



Receive Box from QA (E8)


1.

Open ‘Inventory Management’ screen

2.

Enter part and serial #

3.

Move inventory corresponding BIN

4.

Set new ship
-
by date





4.4.2

Requirements Matrix
: Expeditor

ID

Component

Process

Source

Description

E1

Features

Expeditor

3
-
18
Meeting

Provide the ability to change costs associated
with repairs

E2

Features

Expeditor

3
-
18
Meeting

Provide ability to search packing List


20



4.5.
Stock Room

The
stock room is in charge of all inventory trans
actions and purchase orders. E
mployees

in this
division

are responsible for maintaining adequate stock levels and providing technicians with
requested parts.

4.5.1
Use Cases
: Stock Room




























Receive Item by Purchase Order (S1:S9)


1.

Open inventory maintenance screen

E3

Features

Expeditor

3
-
18
Meeting

Provide ability to generate cost quotes based
on pre
-
canned values. Quote types
include
high dollar value, invoice, and final invoice.

E5

Features

Expeditor

3
-
18
Meeting

Provide ability to enter shipping information

E6

Features

Expeditor

3
-
18
Meeting

Provide ability to print traveler packet

E7

Features

Expeditor

3
-
18
Meeting

Ability to view Fed
-
Ex tracking number

E8

Features

Expeditor

3
-
18
Meeting

Ability to move parts to different inventory
locations

FUTURE REQUIREMENTS

E4

Feature
Requests

Expeditor

3
-
18
Meeting

Automatically send cost quote to customer


21

2.

Enter packing slip number

3.

Enter PO, cost, quantity, department, ticket#,
serial#, comments for each item

4.

Save item into inventory BIN

5.

Submi
t purchase order to accounting

Alternate Flow (create ‘P’ work order) [if item is not in a box]

1.

Open ‘Claim Order Entry’ screen

2.

Create ‘P’ work order used to trace part back to manufacturing

3.

Save work order



Receive Item by Move Ticket (S1


S9)


1.

Open inventory maintenance screen

2.

Enter Move Ticket number

3.

Enter PO, cost, quantity, department, ticket#, serial#, comments for each item

4.

Save item into inventory BIN



Issue Item (S1, S10)


1.

Open
part request screen

2.

Locate requested item and change status to ‘ready for pickup’

3.

Assign serial number, quantity, time, and work order to technician

4.

Item is moved into part request BIN

5.

When item is picked up, right click item and select ‘issue’



Move Item

(S2)


1.

Open ‘Inventory Changes’ screen

2.

Select item to be moved

3.

Select department/pit/area to be moved to

4.

Adjust price/quantity

5.

Add notes

6.

Save changes



Purchase Item (S3, S8)


1.

Open ‘Purchase Order Master’ screen

2.

Create purchase order

3.

Enter PO#, vendor, att
n., required date, and ref #

4.

Save changes

5.

System emails request to vendor






22

4.5.2

Requirements Matrix
: Stock Room





4.6.
Quality Assurance

The quality assurance department is responsible for the final inspection before the box is shipped
back to the customer.

This is a crucial piece of the puzzle and is
cr
itical to maintaining a
high level
of customer satisfaction.

Progress plays a big part in the success of this function by performing
checks
and balances behind the scenes.

4.6.2


Use Cases
: Quality Assurance














ID

Component

Process

Source

Description

S1

Features

Stock Room

4
-
8 Meeting

Provide ability to issue part to technician

S2

Features

Stock Room

4
-
8 Meeting

Provide ability to move inventory to different
logical locations

S3

Features

Stock Room

4
-
8 Meeting

Provide ability to create purchase orders

S5

Features

Stock Room

4
-
8 Meeting

Ability to search inventory

S6

Features

Stock Room

4
-
8 Meeting

Provide ability to print traveler packet

S7

Reporting

Stock Room

4
-
8 Meeting

Generate reports that show historical and
current inventory levels

S8

Features

Stock Room

4
-
8 Meeting

Ability to receive items into inventory

S9

Features

Stock Room

4
-
8 Meeting

Ability to create ‘P’ work orders that track a
box to the manufacturing department

S10

System

Stock Room

4
-
8 Meeting

Track issued parts

FUTURE REQUIREMENTS

S4

Feature
Request

Stock Room

4
-
8 Meeting

Provide automated inventory
control system
that leverages manufacturing department
visibility


23

Perform Final Inspection


1.

Scan work order #

2.

Review ATE results

3.

Review final inspection procedures

4.

Perform physical inspection of box per inspection procedures

5.

Print 8130 and work order

6.

Give box to
shipping


4.6.2


Requirements Matrix
: Quality Assurance


ID

Component

Process

Source

Description

QA1

User Controls

QA

4:8

Meeting

Prevent users from inspecting and approving their own
work

QA2

Fields

QA

4:8

Meeting

Provide the ability to describe the
condition of the keys
and how worn they are

QA3

Feature

QA

4:8 Meeting

Provide ability to print packing slip

QA5

Feature

QA

4:8 Meeting

Ability to receive item in for inspection

QA
6

Feature

QA

4:8

Meeting

Ability to review ATE results

QA8

System

QA

4:8

Meeting

Check if part was repaired in the last 90 days. If so, alert
the user.

FUTURE REQUIREMENTS

QA4

Feature
Request

QA

4:8 Meeting

Consolidate the screens necessary to perform duties

QA
7

F
eature
Request

QA

4:8

Meeting

Provide ability to update and
maintain inspection
manuals for multiple parts.



4.7.
Administration

The administration module allows system admins and managers to manage how Progress interacts
with its users. The QA manager can create and manage logic rules that facilitate increased
productivity and reduce errors. Granular triggers for these rules can be specified as well as the
user group that will see them. Also, in this module, system admins can manage user accounts, the
managers can electronically approve repairs performed durin
g the tech session, and the Nav
database records can be updated.

4.7.1
Use Cases
: Administration








24




















4.7.2

Requirements Matrix:
Administration



ID

Component

Process

Source

Description

A1

QA Manager

Administration

4
-
8

Meeting

Create a master list of products that require
printing an 8130

A2

QA Manager

Administration

4
-
8 Meeting

Create and manage pop
-
up rules and logic and the
triggers that display them to users

A3

QA Manager

Administration

4
-
8 Meeting

Create minimum
standards/requi rements for
technician to have to perform a repair

A4

Systems
Admin

Administration

4
-
8 Meeting

Provide the ability to add and delete users

A5

Systems
Admin

Administration

4
-
8 Meeting

Provide the ability to modify user information and
privileges

A6

Systems
Admin

Administration

4
-
8 Meeting

Assign all users groups of access privileges,
modules available, read and write access

A7

Nav
Database
Admin

Administration

4
-
8 Meeting

Manage
N
av

database and update records

A8

Nav
Database
Admin

Administration

4
-
8 Meeting

Provide the ability to add and remove
N
av

records


25

A9

Repair
Center
Manager

Administration

4
-
8 Meeting

Allow work to be certified/approved electronically
by a manager

A10

Repair
Center
Manager

Administration

4
-
8 Meeting

Allow
certain, qualified users to remove work
orders

A11

Repair
Center
Manager

Administration

4
-
8 Meeting

Store training records along with user information

A12

Repair
Center
Manager

Administration

4
-
8 Meeting

Allow training records to be managed and modified



5.

System Requirements

System level requirements are features that span across all core modules.

This includes
components like: search mechanisms, design specs, and security implementation.

They have been
grouped by component in the matrix below for convenience.



5.1.1


Requirements Matrix


ID

Component

Process

Source

Description

SY1

Features

System

2
-
25 Meeting

Store the CMM (Manual) for every product sold,
available for easy reference

SY2

Features

System

2
-
25 Meeting

Provide the ability to enter free form text in addition
to drop down menu

SY3

Features

System

2
-
25 Meeting

Provide the ability to populate text fields
automatically based on selections

SY4

Features

System

2
-
25 Meeting

Allow
inspection to be authorized by electronic
“signature” with time stamp

SY8

Features

System

3
-
4 Meeting

Allow for granular tracking and traceability of a
board for FAA regulation

SY13

Features

System

4
-
8 Meeting

Allow scanned documents and other files to b
e
attached to the part master

SY16

Features

System

4
-
8 Meeting

Allow files stored in the network share to be synced
on a daily basis

SY11

Search

System

4
-
8 Meeting

Provide the ability to search for the warranty file
based on part # and serial #

SY12

Search

System

4
-
8 Meeting

Provide search lookups by part # and serial #

SY7

Integration

System

3
-
4 Meeting

Verify P/N information from Part Master

SY17

Integration

System

3
-
25 Meeting

Provide the ability to interact with Manufacturing's
Four

shift

software

SY18

Integration

System

2
-
18 Meeting

Provide the ability to integrate with Sales Force,
used by marketing department

SY15

Notifications

System

4
-
8 Meeting

Provide the ability to store notifications associated
with a part that pop up
automatically for every user

SY5

Labeling

System

3
-
4 Meeting

Allow labels to be created for Board, Unit,
Configuration, Customer, and Return to Vendor


26

SY19

Design

System

2
-
18 Meeting

Allow fast customization of screens tailored to
customer accounts and t
heir specific needs

FUTURE REQUIREMENTS

SY9

Feature
Requests

System

3
-
4 Meeting

Provide automatic status updates to the customer
based on unit status

SY10

Feature
Requests

System

3
-
4 Meeting

Provide automatic tracking numbers to customers
after shipping

has been specified

SY14

Feature
Requests

System

4
-
8 Meeting

Provide the ability to maintain all part master
documents electronically, without the need for
paper copies



27


6.

Migrating vs. Upgrading


UPGRADE VS. MIGRATE : QUALITATIVE SCORECARD

















Migration

Upgrade



MIGRATION
-

OEM

UPGRADE
-

PROGRESS



Characteristic

Score

Weight



Total Value



Integrity of System
Architecture

4

2

3



12

6



Scalability

4

2

2



8

4



Support/Resources

4

1

4



16

4

Migration
-

Pros

Extensibility

3

2

5



15

10



Existing Department Systems

3

2

4



12

8



Potential for ERP integration

4

2

3



12

6



Documentation

5

1

4



20

4




Scale: 1
-
5 5=Best, 1 = Worst















Training Cost

1

5

4



4

20



Amount of Customization Required

1

5

4



4

20



Inherent Value of Software

1

5

3



3

15

Migration
-

Cons

Difficulty of Software Development

2

4

3



6

12



Disruption to
Business

2

5

5



10

25



Maintain Functionality

3

4

5



15

20



User Acceptance

2

4

4



8

16



Ease of Customization

2

3

4



8

12



















Grand
Total

153

182




28


The Migration Qualitative Scorecard analysis provides a list of important qualitative factors that
affect the decision of upgrading to vs. migrating to a new system. By scoring each option on a scale
of 1
-
5, 1 being the lowest and 5 the highest, we are ab
le to create a useful model that can be
tweaked according to information and characteristics derived from future research. In addition to
scoring each characteristic, a similarly rated weight is given to assess the relative importance of
each factor.


T
he results of this analysis given the 15 deciding factors listed in the table, is that upgrading the
Progress system to run on Windows Server 2008 is the best decision. This model excludes financial
factors such as license fee or related training costs.
Thus, it should not be used to make decisions;
but merely gauge intangible factors that are often difficult to quantify. A difference of only 29 points
on this scale translates to a very small 2% difference. Thus, the only thing we can conclude with
certa
inty is that the decision to upgrade or migrate is a very difficult choice.


6.1

Alternate Commercial
Options

6.1.1

Aircraft Maintenance Manager
:

Website:
http://www.aircraftms.com
.


Aircraft Maintenance Manager

by
Aircraft Maintenance Systems

is a potential alternative solution.
This software provides an enterprise level paperless solution for creating and tracking work orders.


Features:



Enterprise level s
oftware.



Designed for Operators, Maintenance, Repair and Overhaul organizations and
manufacturers



It is time efficient as well as cost effective solution for small to medium size operators.
Licenses are sold o
n a one time basis



Two versions: Lite and A
dvanced
dependent upon scope of operation.



Pricing based upon s
ystem chosen.



Customizable modules:
separate

modules can be used for different departments

with full
integration supported.



Tracking and managing
maintenance features:

o

Electronic signatures, AD tracker, automatic forecast lists, work reports, etc.



o

Automatic Work Order Creation,

Automatic Journey And Technical Logbook Entries

o

Electronic Signature Module

o

Complete History Tracking

Operat
ing Systems

Windows 95/98/ME
,
Windows CE
,
Windows XP/2000/NT

Databases

MySQL

Programming Languages

C# (C Sharp)
,
Delphi

Price Range

$2,500 to $30,000 starting

Product Types

Software

Pricing
Based Upon

System


29

o

AD, SB, SL etc.
Management

o

Tracking Number Attribution To Each Item at each and every step



User friendly interface

6.1.2


Jobscope Aviation Maintenance Software by Jobscope

Website:
http://www.jobscope.com/


The Airline Suite is another

good potential alternative to
Progress
.

It ha
s a number of integrated
modules

which cover maintenance, inventory

tracking
, purchase, repair
,

and work order
management.



Features:



Enterprise level software



Used

mostly

for

Aircraft M
aintenance Repair and Overhaul F
acilities



Addresses both whole aircraft and aviation component repair



Can handle a range of repair and t
eardown work orders



Quality Management System: c
omplies with
industry standards



Full Serial t
raceability


7.

Business Process Improvements


From our
analysis of the business processes used at
Universal Avionics and feedback obtained from
users during our requirements gathering meetings we can compiled a list of recommended
improvements to be included

in future system implementations.


7.1

Future Requirements

The following list of recommended business process improvements are a summarization of the
future requirements included at the end of the requirem
ents matrix for each core module. We have
also provided a complete list of these requirements in Appendix C (Complete List of Future
Requirements).


Operating Systems

OS/400
,
MS Windows Mobile 2003
,
MS Windows Server 2003
,
Windows 95/98/ME
,
Windows XP/2000/NT

Databases

IBM DB2
,
Microsoft SQL Server

Programming Languages

RPG
,
COBOL
,
C# (C Sharp)
,

C/C++
,
VBScript
,
VB.
net
,
HTML
,
Java
,
JavaS
cript
,
XML

Price Range

$ 70,000 to $350,000

Product Types

Software, ASP Hosted, Web
-
Based (Browser)

Pricing Based Upon

Users (# of seats)


30



Enterprise Wide System

(ERP):

A long
-
term strategy to integrate a
centralized

enterprise
resource planning

system

for the entire organization is highly recommended. The disparate
mix of decentralized systems operating in silo will likely cause problems in the near future
and severely limit the quality of investigative analyses and reports that can be performe
d.




Centralized Database:

The first step in moving toward integration is to develop a
centralized database that can accept inputs from the mix of software applications currently
in use across departments at Universal Avionics.





Vertical Integration (
Man
ufacturer & Dealer
)
:


A strong competitive advantage could
potentially be a higher degree of vertical integration with the manufacturer and with the
network of distributors. Economic Order Forecasting would help manufacturing determine
the quantity of pro
ducts and components to produce.




User Interface Aesthetic Upgrade:
By moving away from a strictly industrial design to a
more visually appealing user interface would improve ease of use and user satisfaction.
One important change that would improve e
fficiency and expedite the data entry process
would be to consolidate the module screens into a single centralized launch point.





Automation of Processes:

A number of processes
,

which are

currently performed
manually,
should

eventually

be automated.
A f
ew

of these processes

are as follows
:


o

Online Customer Order System

o

Denial List Check

o

Warranty Check

o

Economic Order Forecasting


The list of future requirements primarily contains additional information related to
automation of processes.




Customer N
otifications:

Currently there is no way to provide automated alerts to
customers. Because Progress tracks a unit at all points in the repair process, the data
needed to implement this feature is already being captured. A new level of customer
service and

satisfaction could be achieved by automatically notifying customers that a
return has been received, its estimated turn
-
around
-
time, hold
-
for
-
cost quotes, repair
status updates, invoicing, and tracking information.









31

8.

Appendix


A.
Glossary


AOG
: A

term in aviation maintenance indicating a proble
m

is serious
enough to prevent an aircraf
t
fr
om flying.


ASD
:

Aircraft Situation Display


Squawk
: Repair station term denoting the defect, or issue the box was submitted for repair.



Code Soft
:

A

label d
esign and integration software which
offers label printing in enterprise
environments.


Preliminary
Inspection
:

Casual Inspection and not thorough.


FAA
:

Federal Aviation Agency: an agency in the Department of Transportation that is responsible
for the safety of civilian aviation
.


Fourshift
:
W
orkflow and accounting software currently being u
sed in the accounting department
of Universal Avionics.



Repair M
anual
:
The Maintenance Manual provides maintenance personnel with procedures and
guidelines for
repairing units
.


Progress Open Edge
:

SaaS platform for simplifying and streamlining the deve
lopment, integration,
and management of business application
s for deployment in the cloud.


Red Label Unit
: U
nit that that does not yet have FAA approval

and is not authorized to fly.


RTV
:
Return to vendor is used to return received goods to a vendor for

the

purpose of obtaining a
credit
for unwanted goods or replacement for the goods that are to be replaced.


Service Bulletin
: A

notice issued by the manufacturer of an aircraft, engine or other equipment to
alert people to problems with that equipment


8
130 form
:

Airworthiness Approval Tag, identifies a part or group of parts for export approval and
conformity determination from production approval holders. It also serves as approval for return
to service after maintenance or alteration by an authorized
part 145 Repair Station, or a

U.S. Air Carrier having an approved Continuous Airworthiness Maintenance Program under part
135.






32


B.
Complete List of Requirements


ID

Component

Process

Source

Description

AC1

Logic

Accounting

3
-
4
Meeting

Prompt accounting to place
credit hold on
account if it is past due +60 days

AC2

Feature
Requests

Accounting

3
-
4
Meeting

Provide th
e ability to interface with Four

shift

software, specifically for credit hold information

AC3

Feature
Requests

Accounting

3
-
4
Meeting

Generate Past
purchase order summary for
customer

A1

QA Manager

Administration

4
-
8
Meeting

Create a master list of products that require
printing an 8130

A2

QA Manager

Administration

4
-
8
Meeting

Create and manage pop
-
up rules and logic and
the triggers that display
them to users

A3

QA Manager

Administration

4
-
8
Meeting

Create minimum standards/requi rements for
technician to have to perform a repair

A4

Systems
Admin

Administration

4
-
8
Meeting

Provide the ability to add and delete users

A5

Systems
Admin

Administration

4
-
8
Meeting

Provide the ability to modify user information
and privileges

A6

Systems
Admin

Administration

4
-
8
Meeting

Assign all users groups of access privileges,
modules available, read and write access

A7

Nav
Database
Admin

Administrat
ion

4
-
8
Meeting

Manage N
av database and update records

A8

Nav
Database
Admin

Administration

4
-
8
Meeting

Provide

the ability to add and remove N
av
records

A9

Repair
Center
Manager

Administration

4
-
8
Meeting

Allow work to be certified/approved
electronically by a manager

A10

Repair
Center
Manager

Administration

4
-
8
Meeting

Allow certain, qualified users to remove work
orders

A11

Repair
Center
Manager

Administration

4
-
8
Meeting

Store training records along with user
information

A12

Repair
Center
Manager

Administration

4
-
8
Meeting

Allow training records to be managed and
modified

CA1

Fields

Certified
Airman

2
-
25
Meeting

Provide fields to document a cursory inspection

CA2

Labeling

Certified
Airman

2
-
25
Meeting

Send label information from
field inputs to
CodeSoft

CA3

Features

Certified
Airman

2
-
25
Meeting

Allow pre
-
formatted labels to be printed
automatically from CodeSoft

CA4

Labeling

Certified
Airman

2
-
25
Meeting

Allow label to be marked Serviceable or Non
-
Serviceable

CA5

Labeling

Certified
Airman

2
-
25
Meeting

Allow unique versions of labels to be made based
on part type

CA6

Logic

Certified
Airman

3
-
4
Meeting

Ensure that a check is performed for serial
number match

CA7

Features

Certified
Airman

3
-
4
Meeting

Provide a guide for final physical inspection: Is
keying correct, Pins Straight? Dress Label

33

Applied, Rattle?

CO7

Features

Claim Order

3
-
4
Meeting

Allow for three different types of boxes


repair,
loaner, or exchange

CO8

Features

Claim Order

3
-
4
Meeting

Allow for three different work order types
-

repair, manufacturer, or brand new (p)

CO9

Features

Claim Order

3
-
4
Meeting

Provide ability for employee to enter squawk
information

CO1

Logic

Claim Order

3
-
4
Meeting

Pop up a notification that 90 day
warranty is
current if the unit has recently been in for repair

CO2

Fields

Claim Order

3
-
4
Meeting

Allow a claim to be categorized based on the
following claim codes: Warranty or Non
-
Warranty, Consignment Returns (units that we
own that let people borrow
), Scrap unit, Trade in
Core Return(upgrade to newer version), Known
or Unknown Dollars, Loaner, Rental Unit (based
on warranty status), Exchange Codes (warranty,
non
-
warranty)

CO2

Fields

Claim Order

3
-
4
Meeting

Allow a claim to be categorized based on
the
following claim codes: Warranty or Non
-
Warranty, Consignment Returns (units that we
own that let people borrow), Scrap unit, Trade in
Core Return(upgrade to newer version), Known
or Unknown Dollars, Loaner, Rental Unit (based
on warranty status), Excha
nge Codes (warranty,
non
-
warranty)

CO3

Logic

Claim Order

3
-
4
Meeting

Filter fields based on claim code

CO4

Features

Claim Order

3
-
4
Meeting

Track if an item has been received for processing

CO5

Feature
Requests

Claim Order

2
-
18
Meeting

Provide the
ability to have a customer create an
order request online to submit to UA

CO6

Features

Claim Order

4
-
8
Meeting

Provide the ability to create a pick ticket for
loaners and an amended packing slip, similar to
orders

NC1

Features

New Customer

3
-
4
Meeting

Allow customers to be categorized by type. The
customer type will determine the pricing

NC2

Feature
Requests

New Customer

3
-
4
Meeting

Ability to check the denial list from inside the
application.

NC3

Feature
Requests

New Customer

3
-
4
Meeting

Ability to
send new customer requests
electronically

NC4

Features

New Customer

3
-
4
Meeting

Ability to create accounts receivable records for
the customer. One for the billing account and one
for the shipping account.

PI1

Fields

Preliminary
Inspection

3
-
4
Meeting

Provide pre
-
canned statements about item
condition including: Quality Seal, Keying,
Connection condition, Lens Scratched

PI2

Logic

Preliminary
Inspection

3
-
4
Meeting

Trigger hidden damage inspection based on the
selection of specific condition keywords

PI3

Fields

Preliminary
Inspection

3
-
4
Meeting

Allow the entry of
squawk

details including red
label, out of box failure?

PI4

Integration

Preliminary
Inspection

3
-
4
Meeting

Pull service
bulletin

from UNINET and
Dynamically display the status for each part

PI5

Fields

Preliminary
Inspection

3
-
4
Meeting

Assign a turnaround date, 5
-
7 days unless
otherwise specified


34

PI6

Fields

Preliminary
Inspection

3
-
4
Meeting

Provide the ability to select a shipping method
based on a list of vendors

QA1

User
Controls

QA

3
-
25
Meeting

Prevent users from inspecting and approving
their own work

QA2

Fields

QA

3
-
25
Meeting

Provide the ability to describe the condition of
the keys and how worn they are

S1

Design

Stockroom

3
-
25
Meeting

Provide a module for the stockroom to receive
purchase orders

S2

Fields

Stockroom

3
-
25
Meeting

Allow entry of BIN location, Lot Code, and
receiving advice

S3

Feature
Requests

Stockroom

3
-
25
Meeting

Automatically submit receiving advice to
Accounting

S4

Fields

Stockroom

3
-
25
Meeting

Provide the ability to denote the status of an
inventory item using an: I or F depending on if it
is being used

S5

Fields

Stockroom

3
-
25
Meeting

Provide the ability to adjust the price of an
inventory item

S6

Feature
Requests

Stockroom

3
-
25
Meeting

Integrate with Manufacturing to control
Economic Order Quantity and integrated
planning capabilities

S7

Features

Stockroom

3
-
25
Meeting

Provide the ability to view all inventory items in
stock

S8

Features

Stockroom

3
-
25
Meeting

Provide the ability to export work order
information to Excel

SY1

Features

System

2
-
25
Meeting

Store the CMM (Manual) for every product sold,
available for easy reference

SY10

Feature
Requests

System

3
-
4
Meeting

Provide automatic tracking numbers

to
customers after shipping has been specified

SY11

Search

System

4
-
8
Meeting

Provide the ability to search for the warranty file
based on part # and serial #

SY12

Search

System

4
-
8
Meeting

Provide search lookups by part # and serial #

SY13

Features

System

4
-
8
Meeting

Allow scanned documents and other files to be
attached to the part master

SY14

Feature
Requests

System

4
-
8
Meeting

Provide the ability to maintain all part master
documents electronically, without the need for
paper copies

SY15

Notifications

System

4
-
8
Meeting

Provide the ability to store notifications
associated with a part that pop up automatically
for every user

SY16

Features

System

4
-
8
Meeting

Allow files stored in the network share to be
synced on a daily basis

SY17

Integration

System

3
-
25
Meeting

Provide the ability to interact with
Manufacturing'
s Four

shift

software

SY18

Integration

System

2
-
18
Meeting

Provide the ability to integrate with Sales Force,
used by marketing department

SY19

Design

System

2
-
18
Meeting

Allow fast customization of screens tailored to
customer accounts and their specific needs

SY2

Features

System

2
-
25
Meeting

Provide the ability to enter free form text in
addition to drop down menu

SY3

Features

System

2
-
25
Meeting

Provide the ability to
populate text fields
automatically based on selections

SY4

Features

System

2
-
25
Meeting

Allow inspection to be authorized by electronic
“signature” with time stamp


35

SY5

Labeling

System

3
-
4
Meeting

Allow labels to be created for Board, Unit,
Configuration,

Customer, and Return to Vendor

SY6

Security

System

3
-
4
Meeting

Provide the ability to have unique views for each
user type i.e. technician, manager

SY7

Integration

System

3
-
4
Meeting

Verify P/N information from Part Master

SY8

Features

System

3
-
4
Meeting

Allow for granular tracking and traceability of a
board for FAA regulation

SY9

Feature
Requests

System

3
-
4
Meeting

Provide automatic status updates to the
customer based on unit status

TS1

Logic

Tech Session

3
-
4
Meeting

System dynamically checks
to ensure technician
logged in is qualified for inspection

TS2

Logic

Tech Session

3
-
4
Meeting

Ensure that ESD test is performed before
technician can log in

TS3

Features

Tech Session

3
-
4
Meeting

Entry of part # brings up CMM manual for each
part

TS4

Logic

Tech Session

3
-
4
Meeting

Information from basic fields brought over from
Claim Order Entry i.e. Part #, Serial #, Customer
Info

TS5

Design

Tech Session

3
-
4
Meeting

Provide views of summary information from
preliminary inspection

TS6

Design

Tech
Session

3
-
4
Meeting

Provide pre
-
filled summary of
squawk

TS7

History

Tech Session

3
-
4
Meeting

Provide the ability to view a complete history of
the unit i.e. Previous owners, prior work
completed

TS8

Features

Tech Session

3
-
4
Meeting

Provide a reference
of Mods available

TS9

Features

Tech Session

3
-
4
Meeting

Provide the ability to run a report of unit and
board failure history

TS10

Features

Tech Session

3
-
4
Meeting

Provide the ability to print a summary of the
work order

TS11

Features

Tech Session

3
-
4
Meeting

Provide the ability to convert part # and serial #

TS12

Features

Tech Session

3
-
4
Meeting

Show the configuration specs of boards that are
currently in unit

TS13

Logic

Tech Session

3
-
4
Meeting

Scrapping a board automatically pulls it from the
inventory list

TS14

Fields

Tech Session

3
-
4
Meeting

Provide pre
-
canned
statement

for “Send to
Vendor”

TS15

Design

Tech Session

3
-
4
Meeting

Provide the ability to view
squawk

and previous
repairs for a unit

TS16

Features

Tech Session

3
-
4
Meeting

Allow
the ability for a tech to make a granular
listing for charges including changed par

TS17

Fields

Tech Session

3
-
25
Meeting

Provide the ability to denote status of Nav
Database

TS18

Fields

Tech Session

3
-
25
Meeting

Update ETI counter information on board
denoting amount of time that it has been
functioning

TS19

Features

Tech Session

3
-
25
Meeting

Provide the ability to enter pre
-
filled required
FAA information filtered by prior selections

TS20

Fields

Tech Session

3
-
25
Meeting

Allow entry of a BIN ordering

form for smaller
par; not a board or box

TS21

Features

Tech Session

3
-
25
Par request by Part #, W/O, notes, quantity


36

Meeting

TS22

Features

Tech Session

3
-
25
Meeting

Provide the ability to insert Service Bulletin
comments

into the work order

TS23

Features

Tech Session

3
-
25
Meeting

View all service bulletin instructions related to
component

TS24

Features

Tech Session

3
-
25
Meeting

View all testing procedures

TS25

Features

Tech Session

3
-
25
Meeting

Allow the technician to perform and record
resul
ts

of ATE tes
t

TS26

Logic

Tech Session

3
-
4
Meeting

Trigger hidden damage inspection based on the
selection of specific condition keywords

TS27

Fields

Tech Session

3
-
4
Meeting

Provide pre
-
canned statemen
t

about item
condition including: Quality Seal, Keying,
Connection condition, Lens Scratched

TS28

Fields

Tech Session

3
-
4
Meeting

Allow the entry of
squawk

details including red
label, out of box failure?

CB1

History

Tech Session
-

Board

2
-
25
Meeting

Provide the ability to view the full history of a
board, from its serial number

CB2

Fields

Tech Session
-

Board

2
-
25
Meeting

Distinguish between M, R, and P Types

CB3

Features

Tech Session
-

Board

2
-
25
Meeting

Provide the ability to
auto fill

pre
-
canned
descriptions of board condition

CB4

Logic

Tech Session
-

Board

2
-
25
Meeting

Board repair action window pops up when 0 is
the first alphanumeric of part number

CB5

Fields

Tech Session
-

Board

2
-
25
Meeting

Provide fields for repair action
taken, part
number of component, and reason

CB6

Features

Tech Session
-

Board

2
-
25
Meeting

Track parts at the granularity of each individual
component on a board

CB7

Fields

Tech Session
-

Board

2
-
25
Meeting

Allow technician to enter labor hours performed

on repair

CB8

Features

Tech Session
-

Board

2
-
25
Meeting

Provide the ability to add a new part to the
work
order

and existing unit

W1

Feature
Requests

Warranty

4
-
8
Meeting

Electronically receive point
-
of
-
sale paperwork
from distributor including
warranty card

W2

Feature
Requests

Warranty

4
-
8
Meeting

Automatically extend warranty 90 days after a
product has been repaired.

W3

Features

Warranty

4
-
8
Meeting

Pop notification if product has been in for repair
within the last 90 days

W4

Feature
Requests

Warranty

4
-
8
Meeting

Create a module capable of
accommodating

more
extensive and flexible warranty information

W5

Feature
Requests

Warranty

4
-
8
Meeting

Provide the ability to accommodate new
extended warranty purchase option






37


C.
Complete List of Future Requirements


AC2

Feature
Requests

Accounting

3
-
4
Meeting

Provide th
e ability to interface with Four

shift

software, specifically for credit hold information

AC3

Feature
Requests

Accounting

3
-
4
Meeting

Generate Past purchase order summary for

customer

CO5

Feature
Requests

Claim
Order

2
-
18
Meeting

Provide the ability to have a customer create an
order request online to submit to UA

NC2

Feature
Requests

New
Customer

3
-
4
Meeting

Ability to check the denial list from inside the
application.

NC3

Feature
Requests

New
Customer

3
-
4
Meeting

Ability to send new customer requests
electronically

S3

Feature
Requests

Stockroom

3
-
25
Meeting

Automatically submit receiving advice to
Accounting

S6

Feature
Requests

Stockroom

3
-
25
Meeting

Integrate with
Manufacturing to control Economic
Order Quantity and integrated planning capabilities

SY10

Feature
Requests

System

3
-
4
Meeting

Provide automatic tracking numbers to customers
after shipping has been specified

SY14

Feature
Requests

System

4
-
8
Meeting

Provide the ability to maintain all part master
documents electronically, without the need for
paper copies

SY9

Feature
Requests

System

3
-
4
Meeting

Provide automatic status updates to the customer
based on unit status

W1

Feature
Requests

Warranty

4
-
8
Meeting

Electronically receive point
-
of
-
sale paperwork from
distributor including warranty card

W2

Feature
Requests

Warranty

4
-
8
Meeting

Automatically extend warranty 90 days after a
product has been repaired.

W4

Feature
Requests

Warranty

4
-
8
Meeting

Create a module capable of
accommodating

more
extensive and flexible warranty information

W5

Feature
Requests

Warranty

4
-
8
Meeting

Provide the ability to accommodate new extended
warranty purchase option









38


D.
Un
iversal Avionics System Map






39


E.
Workflows


i.
Create New Customer





40


ii.
Claim Order Entry






















41

iii.


Tech
Session


Board Repair






42

F.



Team Profile

Bradley Demirjian

Bradley graduated from the Eller College of Management with an undergraduate degree in
Management Information Systems and Operations Management in 2010.

He currently holds the
position of

Senior

System Analyst at The University of Arizona. His areas of expertise include
network analysis, requirements analysis, and application development.


Shruti Singh

Shruti graduated from Eller College of Management
with an MS degree in MIS. She has an
undergraduate degree in Computer Science Engineering from University of Pune, India. She has
worked with few Indian IT companies like Infosys and Satyam. Currently she is heading for her
internship as a Data Analyst at
Qualcomm, San Diego, CA.


Seong Rog Do

Currently Seong is a MIS can
didate of 2011 at Eller College and received

his bachelor degree in
Computer Science and business

administration.
Before attending The University of Arizona, Seong

served as
Accounting O
ffi
cer at the Air Force of

Korea.

Nivedita Kamat

Nivedita has a Bachelor's in Electrical Electronics and a Master's in Human Resources and
International Business.

She has 5+ years of experience in the field of Human Resources and has
worked with Multi Nation
al's like Sun Microsystems, Thomson Reuters and EMC Data Storage.

She is currently pursuing MS in Management Information System with Project Management as area
of

specialization.

Ryan Michelson

Ryan has a BA in Film Production and is
pursuing

a dual degree

MBA/ MS
MIS.

He w
as employed
with
T
wentieth Century Fox Television as a Business Analyst.













43



44



45




46







47