1 / 30

RFID Shelving

19 Mar 2007. ADD Presentation:. RFID Shelving. www.cs.bgu.ac.il/~iditger. Guy Shtub Idit Gershoni. Table Of Content. Refresh your memory – What is the project all about System requirements. System architecture. Classes & relationships. User Interface. Tests. Task list.

zohar
Télécharger la présentation

RFID Shelving

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 19 Mar 2007 ADD Presentation: RFID Shelving www.cs.bgu.ac.il/~iditger • Guy Shtub • Idit Gershoni

  2. Table Of Content • Refresh your memory – What is the project all about • System requirements. • System architecture. • Classes & relationships. • User Interface. • Tests. • Task list.

  3. About the project • The project takes place in Intel’s Fab 18 - A factory for manufacturing integrated circuits devices.

  4. Some basic terms • Reticle - An optical template inserted into the manufacturing machines in the Lithography area. • RFID – Radio Frequency identification is a technology that uses devicesattached to objects that transmit data to a (RFID) receiver. Alternative tobar coding. Its advantages include data capacity, read/write capability, and noline-of-sight requirements. Lithography = The process of imprinting patterns RFID chip Reticle

  5. The Problem • New Reticles are being used. These Reticles are large in size and don’t fit in the old reticle storing and transportation system. • The technicians manually bring the reticles from the storage room to the work stations. • Human errors can occur. Reticles may get lost (reticle cost can reach to 150K $). No control. • The project aims at preventing critical human errors from occurring.

  6. System Requirements (1) • Main Goal: • To automize today’s manual procedure in which technicians in the clean room are requested to move reticles from their storage to Tools and back. • This will be achieved by developing a system which includes a 3rd party solution of reticle shelves based on RFID technology. • The system will communicate with the 3rd party hardware and the manufacturing, control & command systems of the Fab.

  7. System Requirements (2) • POD Association Station (PAS) : • Update reticle data in the system • Establish the Control System: • Reticle removal from the Cabinet. • Reticle insertion to the Cabinet.

  8. System Architecture The MTUI system is an interface for the technician in the clean room. The technicians use it to create orders for Reticles The Control System interacts with the CDIS (Intel’s employee DB) by Web Services. The orders from the MTUI are transferred to the RTS and its WART Database (Oracle). The Control System is responsible for the communication between the different components and for the logic. Reticle shelves & Gate (Hardware provided by the 3rd party vendor)

  9. Main Classes Control System

  10. Main Classes General Controller Tibco Listener Identification Controller Removal Controller Insertion Controller

  11. Connectors

  12. Main Classes – Cont. PAS Package PAS Controller

  13. Tibco Listener Class • TIBCO protocol is a broadcast protocol, therefore a listener is needed in order to capture its messages. • The responsibility of the TIBCO Listener class is to listen to the communication passing from the PDA through TIBCO protocol. • When a message received the listener will identify it and forward the message to the GeneralController class for further use. • 3 types of messages that can be transferred: Employee passing through the gate, reticle removal and reticle placed.

  14. General Controller Class • The General Controller is responsible for receiving information from the 3rd party hardware, through the TIBCO listener and passing this information to the specific controller responsible for the use case. • Sends information from the Control System to the 3rd party Hardware through the TIBCO Connector.

  15. Identification Controller Class • The Identification Controller is responsible for handling the identification of a user that passes the gate. • It receives information from the General Controller, regarding the user that passed the gate. • It communicates with the CDIS Connector to receive data regarding the user. • This class is used in both the Reticle Insertion and Reticle Removal use cases.

  16. Insertion Controller Class • The Insertion Controller is responsible for handling the Reticle Insertion from Cabinet use case. • It receives information from the General Controller, specifically the RFID tag num of the inserted Reticle. • It then queries the PAS DB through the PAS DB Connector about the reticle’s ID.

  17. Removal Controller Class • The Removal Controller is responsible for handling the Reticle Removal from Cabinet use case. • It receives information from the General Controller, and handles the logic of the use case. • It communicates with the TIBCO Connector to request it to indicate where the desired Reticle is located and with the PAS DB connector and RTS System to update data of removed Reticle.

  18. PAS Controller Class • The PAS Controller is responsible for handling update of Reticle data in the system. • When a reticle is placed in the PAS it receives the Reticle RFID tag number from the RFID reader. • It then queries the PAS DB, through the PAS DB Connector about this Reticle. • The received information is passed to the GUI and displayed to the user. • If a user enters reticle data through the GUI this data is relayed to the PAS Controller which updates this information in the PAS DB.

  19. PAS Data Base Main Purpose: Associate Reticle ID With RFID tag num MS – SQL Data Base

  20. User Interface • Logon Screen: • Web page • .aspx file

  21. User Interface • Administrator Page: Used to create and update associations between RFID tags and Reticles. When a RFID tag is placed in the RFID reader, the reader reads its data and the tag ID is displayed to the user 2 options for the user

  22. Testing (1) • Functional Testing: • Reticle insertion to the Cabinet: • Passing with an employee RFID tag through the gate. • Insert a reticle POD (with RFID tag attached to it) to a shelf. • Check that the data was updated in both RTS and PAS systems. • Reticle removal from the Cabinet: • making an order for a reticle. • Passing with an employee RFID tag through the gate. • remove the reticle from the correct shelf. • Check if indeed the reticle is the one that was ordered. • Update reticle data in the system.

  23. Testing (2) • Non Functional Testing: • Speed, Capacity & Throughput. • Availability.

  24. Task List • Prototype establishment including subtasks: • Build PAS Database. • Implement PAS GUI. • Interfaces to Databases and hardware using TIBCO and RFID reader/writer • Implementation of System control component

  25. Task List (2) • Testing plan document. • Unit-tests. • Integration & Integration tests.

  26. Task List (3)

  27. The End Questions?

  28. Thank You

  29. Bonus Slide #1 • Due to financial reasons, Intel has decided to freeze the project. Bad News

  30. Bonus Slide #2 – The Prototype • What we will have: • Access to Intel’s servers, systems & databases. • What we will not have: • Shelves, Gate, PDA. • What we might have (need to negotiate): • RFID reader, Shelves demo/simulation, PDA simulation.

More Related