393SYS Airport Engineering Practice
Coursework 2: ISO9000 for airport baggage tracking QMS
Student grouping: 4-5
Hand-in: 26 April 2008 before 9:00pm
Weight: 15% of final mark
Purpose: Apply ISO9001 to design a QMS for an Airport Baggage Tracking System (ABTS).
Expected time spend: 10 hours with library and Internet research.
Use BS EN ISO 90001:2000, clauses 7.5.4 Customer property as guideline to develop:
1. A set of high level requirements. [10 marks]
2. Detail checklist for quality audit. [20 marks]
3. Base on the checklist, suggest a set of procedures, activities, data reports and/or exception reports for a new RFID enabled ABTS system (RFIDABTS)#. [30 marks]
4. Suggest one Reliability Program to monitor and control the performance of the RFIDABTS [30 marks].
5. List the reference and assumption used. [10 marks]
# As a student coursework, it is reasonable to simplify the FRIDABTS system model by making a few reasonable assumptions. Students may assume the FRIDABTS system starts at the originating airport passenger check-in where RFID are tagged on the baggage. The airlines and the connecting airports use the same RFIDABTS system and scanners to capture data specified by the student. For the passengers making transfers from one plane to another, the system should transfer baggage directly from one airplane to another without going through the airport facility. To enable the student to focus on reliability and technology issues, the security measures are considered outside the scope of this coursework. The RFIDABTS system ends when the baggage reunite with the passenger either at the carousel in the destination airport or deliver to their residents latter. It is reasonable to expect that the RFIDABTS can help airlines to track down lost bags.
Students can refer to the following links if they want to clarify some of the technical specification in this coursework:
RFID technical specification can reference to Texas Instrument’s smart labels site: http://www.ti.com/rfid/docs/manuals/brochures/Tag-it_Bro.pdf
Business model of airport baggage tracking system can reference to IBM report: https://www-935.ibm.com/services/us/gbs/bus/pdf/g510-6592-00-baggage.pdf
In addition to the text and lecture notes, FAA AC 120-17A can provide good guidance for development of Reliability Programs.
IATA and EPC have put together a number of standards that govern data format on RFID tags and physical format of tags for use in baggage.
Suggested format:
7.5.4 Customer property
High Level Requirement / Detail Checklist / Suggested Procedure
Example on making of high-level requirements(the Whats):
1 Analyze the International standard:
7.3.3 Design and development outputs
The outputs of design and development shall be provided in a form that enables verification against the design and development input and shall be approved prior to release.
Design and development outputs shall
a) meet the input requirements for design and development,
b) provide appropriate information for purchasing, production and for service provision,
c) contain or reference product acceptance criteria, and
d) specify the characteristics of the product that are essential for its safe and proper use.
2 Decompose the compounded requirements into simple requirements:
7.3.3 Design and development outputs
The outputs of design and development shall be provided in a form that enables verification against the design and development input and shall be approved prior to release.
The outputs of design shall be provided in a form that enables verification against the design input and shall be approved prior to release.
The outputs of design shall be provided in a form that enables verification against the design input.
The outputs of design shall be approved prior to release.
The outputs of development shall be provided in a form that enables verification against development input and shall be approved prior to release.
…
Design and development outputs shall
a) meet the input requirements for design and development,
b) provide appropriate information for purchasing, production and for service provision,
c) contain or reference product acceptance criteria, and
d) specify the characteristics of the product that are essential for its safe and proper use.
…
Consolidate with the guidelines and integrate into a set of simple high-level requirements
High Level Requirements / Detail checklist / Suggested procedures and activities7.3.3 Design and development outputs
High Level Requirement / Detail Checklist / Suggested Procedure
Design outputs shall be provided in a form that enables verification against the design input.
Development outputs shall be approved prior to release.
Design outputs shall contain or reference product acceptance criteria.
Development outputs shall specify the characteristics of the product that are essential for its safe and proper use.
Coursework 2 Page: 1