1 / 11

TRACKING THE BRICK HANDLING From extraction to development

TRACKING THE BRICK HANDLING From extraction to development. Requirements. Knowing the brick localization at any time Knowing the entry/exit(?) of the brick in each work station Giving a way of accessing this set of information from anywhere : For each brick For any work station

kasi
Télécharger la présentation

TRACKING THE BRICK HANDLING From extraction to development

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. TRACKING THE BRICK HANDLINGFrom extraction to development T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso

  2. Requirements • Knowing the brick localization at any time • Knowing the entry/exit(?) of the brick in each work station • Giving a way of accessing this set of information from anywhere : • For each brick • For any work station • Brick movement has to be tracked in “real time” • Matrix code reading will trigger a dedicated software component • Software or network failure does not stop the process  Offline update will synchronize the brick movement • Procedures have to be clearly defined • For the tracking, basic information as timestamp is needed • All sub-systems could enrich the basic information by linking is own set of information • Dedicated Graphical Displays could be proposed : • Basic views for tracking only : Bricks or Work station views • More detailed views including the full information • Some logistic in some area (Shielded Area) will have to be foreseen T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso

  3. Surface Lab Basket Candidates Bricks Walls XRay Marking Shielded Area Cosmic Pit Dev. Lab Basket Candidates Bricks From Extraction to Development/Re-InsertionWork Stations Brick Actions • BMS/Supervisor/BMM current responsibility : • Maintaining the detector content • Perform the brick extraction from the wall to the basket • All steps during the extraction are time stamped : Extraction from wall, Insertion in the basket • All the bricks in the basket containing “candidates” are in well-known state • BMM knows exactly what are the bricks expected outside • A way to avoid the human error  only bricks in this list should be manipulated outside the basket. T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso

  4. Surface Lab Basket Candidates Bricks Walls XRay Marking Shielded Area Cosmic Pit Dev. Lab Basket Candidates Bricks XRay MarkingWork Stations Actions • Bricks in the basket used for extraction have to be marked • Ideally, before each marking, reading the matrix code insure that only right brick will be marked • Each matrix code reading set the brick in a new state with a timestamp • Ie. : Brick received in XRay marking area at 00:00:00 00:00 • This action should also fill in a electronic logbook associated to the XRay area • In order to keep track of the brick path , a standard procedure has to be defined : • Manuals and automatic operations and the order have to be always the same . • REMARK : Do we need to know when the brick leaves this area ? T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso

  5. Shielded Area Actions(1) Surface Lab Basket Candidates Bricks • Probably the place where the amount of bricks will be the biggest • Many bricks in different states : • Brick waiting for CS scanning result • Brick waiting to be re-inserted in a basket (because of negative CS result) • What about the new CSBox association  • Keep the old one  • a way for retrieving easily the CSBox • How to replace a broken one ? • associate a new one  • Use existing one previously associated to a developed brick  we have then to accept an non one-to-one association between brick and CSBox • Brick waiting to be send to development lab. • Brick waiting to be separated from its CS box. • What about the CSBox/Brick Association Walls XRay Marking Shielded Area Cosmic Pit Dev. Lab Basket Candidates Bricks T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso

  6. Surface Lab Basket Candidates Bricks Walls XRay Marking Shielded Area Cosmic Pit Dev. Lab Basket Candidates Bricks Shielded Area Actions(2) • A dedicated organization is needed : • To locate precisely the brick location • To identify quickly the state of all the bricks • To avoid human errors,… • Again, matrix code reader is the trigger • Some logistic is needed • Build around a shelves organization • Each place on shelves is uniquely identified • Each brick is associated to one and only one shelf place • Dedicated displays representing shelves, brick associated to shelve and brick state. T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso

  7. Surface Lab Basket Candidates Bricks Walls XRay Marking Shielded Area Cosmic Pit Dev. Lab Basket Candidates Bricks Shielded Area Actions(3)Workflow proposition • When a brick get in : • Matrix Code reading and shelf bar code reading  brick shelf association • Brick State : Waiting for CS result • Shelf management can be seen as the wall management • Modifying the brick state : • In order to change a brick state , some external software may have access to perform a change state. • When a brick get out : • Locating on a display the concerned brick location (matrix code typed by hand) • 2 options : • Waiting the next trigger from the next work station • If knowing the release date is important from the current work station, operator will have to be done before the brick leaves the current area. T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso

  8. Surface Lab Basket Candidates Bricks Walls XRay Marking Shielded Area Cosmic Pit Dev. Lab Basket Candidates Bricks Work Stations Actions • From the BMM/brick life cycle point of view • End of the brick life • Marked as developed (Timestamp) • Informations about the shipment could be managed by a dedicated component T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso

  9. Last Run Architecture for the XRay Marking and basic actions ORACLE DB SERVER WORK STATION AREA ORACLE DB Retrieve the information corresponding to all the bricks expected at this specific area for display Dedicated JAVA GUI (BMM Dev.) Serial connection ORACLE DB 1 Check if the read matrix code is in the expected list and validate the brick transition if possible BMM Computer 3 Read the brick matrix code with the connected matrix code reader Brick Life Cycle Manager Component 2 T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso

  10. An Example of display T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso

  11. Summary • “Real Time” tracking • Procedures well defined at any work station • To reduce human errors • Each work station has to know the brick count, the brick’s state and the brick’s identification expected at the entry • Logistics has to be foreseen at some place • Ie : Shielded Area,… • Information access allowed from anywhere to anybody • WEB Access • Software components in-line with the procedure • Final decision concerning the software development will impact the LAPP development team T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso

More Related