IT354 Final Project

1
IT354 Final Project

• Seth Coleman
• Carlos Morris
• Jon Hunter
• Nick Werner

2
Project Definition

• Consult with Airstream's quality group leader,
  and develop a prototype deviation line item
  tracking, collection and documentation system for
  future implementation.

3
Tasks

• User Profile
• Constraints
• Needs
• Problem Statement
• Task Analysis

4
User Profile

• Airstream Quality Team
• Rob Shook Quality Manager
• 4 additional members

5
Constraints

• Digital conversion of paper based system
• Short time period for development
• Technologically inexperienced labor

6
Needs

• Handheld, portable, with printing capability
• Security
• Confidentiality of database
• Defined user abilities and access
• Easy to use, modify and upgrade
• Poka-yoke (Mistake Proof)
• Scalability

7
Problem Statement

• Track, catalog, and document quality issues for
  statistical analysis.
• Define data to be tracked
• Obtain requirements from Airstream
• Spec equipment with appropriate abilities
• Considerations are
• Battery life, contrast, printing size and stock
  tackiness
• Develop prototype system
• Access database with VB.NET or XML based front
  end
• Test system with users, and note issues
• Refine system and submit

8
Task Analysis

• Develop, and refine a system of reliable data
  collection and documentation.
• Reliability
• System is easy to backup and restore
• System works with multiple brands of handheld
  device, or with no handheld at all (in case of in
  operable unit)
• User Level authentication for data security.

9

• -Collection
• Data is selected from an available list, forcing
  the user to use correct terminology.
• Forced selection allows for ease of
  categorization and mis-keying
• Use of forced location progression makes the user
  follow the process outline for inspection.
• Documentation
• Use of MS Access allows reports to be created
  for a variety of purposes very quickly and easily.

10
System Specifications

• Proposed Task list
• 1. Trailer VIN is scanned into device.
• 2. Quality member completes a walkaround of
  trailer as directed by the handheld, while
  inputting and labeling deviations with tags
  printed from mobile printer. (If the user notices
  a deviation in a location that has already passed
  in the order, they can press a button and amend
  the list, and print a label).
• 3. Handheld device is docked, and the data is
  downloaded to the database.

11

• 4. A deviation list is printed and posted on
  the vehicle.
• 5. The finish department is notified that the
  deviations have been cataloged, and repairs any
  deviations that they can, then sign off on the
  repaired deviations.
• 6. Group members come and repair the rest of the
  deviations, then sign off on the sheet.

12

• 7. When the sheet has been check completely off,
  an approved quality group member checks the
  trailer for deviation correction, and digitally
  notes the correct by scanning the barcode
  generated in the tagging phase.
• 8. The group member docks the handheld, enters
  their user ID and password to download the
  updated info to the database. When the trailer
  has been declared without deviation an email is
  sent to the sales department.

13
Software Details

• Either VB.NET and HT/XML
• VB.NET - Used for computer station software.
• XML Used for handheld device (input is webapp
  style)
• Every location of the vehicle has its own screen
  with a list of location specific deviations.
• Screens on the computer for initial deviation
  download, and deviation updating (along with
  Access reports).

14
Hardware specifications

• Current device considerations
• Intermec 700 series mobile computer (ruggedized
  PDA)
• Printers
• Intermec PL4 or PB20
• Some type of wedge scanner for emergency use
• More investigation is required in this area.

15
System Data Structure and Flow

• The proposed system will utilize both executable,
  and webapp based applications, and can be used
  wirelessly, or physically docked.
• When the user scans the VIN barcode into the
  software on the handheld, the device will try and
  connect via wireless connection to the
  workstation computer, and retrieve the data. If
  it is unable to do so, the device will require
  the user to dock it in order to retrieve the data
  via cable connection. The VIN is now considered
  open.
• While the user is creating deviation tags, the
  data is being logged in an XML base text file
  that is stored on the mobile device. When the
  tagging is finished, the user goes to the
  workstation computer, and attempts to retrieve
  the data from the mobile device. If it cannot
  connect, the device will require the user to dock
  it in order to retrieve the data via cable
  connection.

16

• After the database has been updated, the software
  will print a deviation line item sheet, listing
  all of the line items.
• Once the deviations have been repaired, the user
  goes to the workstation computer, and selects one
  of the open VINS (If there are multiples at any
  given time). The computer will then attempt to
  contact the handheld, If it cannot connect, the
  device will require the user to dock it in order
  to retrieve the data via cable connection. The
  computer will upload the list of deviations to
  the handheld (this way multiple handhelds can be
  used in the shop, and there isnt a need to use
  the same one for tagging and clearing), and mark
  the VIN as being finalized.
• The user will then scan all of the deviation tags
  to verify that the deviations have been
  corrected. When they user is finished, they will
  indicate that by selecting a button on the
  handheld. If there is a deviation listed in the
  database that was not scanned, then the user will
  be required to scan that or override the
  discrepency with a username and password.

17

• The user will then go to the workstation and
  select from the list of VINs that are being
  finalized. Then the user will enter a user ID and
  password, and then the communication process will
  take place again. Once the data has been sent to
  the database successfully, the VIN will be marked
  as finished. The sales department will receive
  an automated emailing detailing the vehicle, and
  the release.
• Reports will now be available for statistical
  analysis.
• As mentioned earlier, the system will be able to
  perform all of the above functions without the
  use of the handheld in case of technical issues,
  through the use of a wedge type scanner.