T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso 1 TRACKING THE BRICK HANDLING From extraction to development

T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso 2 Requirements Knowing the brick localization at any timeKnowing the brick localization at any time Knowing the entry/exit(?) of the brick in each work stationKnowing the entry/exit(?) of the brick in each work station Giving a way of accessing this set of information from anywhere :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”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 movementSoftware or network failure does not stop the process  Offline update will synchronize the brick movement Procedures have to be clearly definedProcedures have to be clearly defined For the tracking, basic information as timestamp is neededFor 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 viewsBasic views for tracking only : Bricks or Work station views More detailed views including the full informationMore detailed views including the full information Some logistic in some area (Shielded Area) will have to be foreseenSome logistic in some area (Shielded Area) will have to be foreseen

T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso 3 From Extraction to Development/Re-Insertion Work Stations Brick Actions BMS/Supervisor/BMM current responsibility :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 basketAll 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 stateAll 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. Surface Lab Walls BasketCandidatesBricks BasketCandidatesBricks XRayMarkingShieldedArea CosmicPitDev.Lab

T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso 4 XRay Marking Work Stations Actions Bricks in the basket used for extraction have to be markedBricks 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 markedIdeally, 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 timestampEach 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 areaThis 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 :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 ? Surface Lab Walls BasketCandidatesBricks BasketCandidatesBricks XRayMarkingShieldedArea CosmicPit Dev.Lab

T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso 5 Shielded Area Actions(1) Probably the place where the amount of bricks will be the biggestProbably the place where the amount of bricks will be the biggest Many bricks in different states :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 What about the new CSBox association  1.Keep the old one  a)a way for retrieving easily the CSBox b)How to replace a broken one ? 2.associate a new one  a)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 AssociationWhat about the CSBox/Brick Association Surface Lab Walls BasketCandidatesBricks BasketCandidatesBricks XRayMarkingShieldedArea CosmicPitDev.Lab

T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso 6 Shielded Area Actions(2) A dedicated organization is needed :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 triggerAgain, matrix code reader is the trigger Some logistic is neededSome 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. Surface Lab Walls BasketCandidatesBricks BasketCandidatesBricks XRayMarkingShieldedArea CosmicPitDev.Lab

T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso 7 Shielded Area Actions(3) Workflow proposition When a brick get in :When a brick get in :  Matrix Code reading and shelf bar code reading  brick shelf association Brick State : Waiting for CS resultBrick State : Waiting for CS result Shelf management can be seen as the wall managementShelf management can be seen as the wall management Modifying the brick state :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 :When a brick get out :  Locating on a display the concerned brick location (matrix code typed by hand)  2 options : 1. Waiting the next trigger from the next work station 2.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. Surface Lab Walls BasketCandidatesBricks BasketCandidatesBricks XRayMarkingShieldedArea CosmicPitDev.Lab

T. Le Flour LAPP OPERA Collaboration Meeting Gran-Sasso 8 Work Stations Actions From the BMM/brick life cycle point of viewFrom 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 componentInformations about the shipment could be managed by a dedicated component Surface Lab Walls BasketCandidatesBricks BasketCandidatesBricks XRayMarkingShieldedArea CosmicPitDev.Lab

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

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“Real Time” tracking Procedures well defined at any work stationProcedures 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 entryEach 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 placeLogistics has to be foreseen at some place  Ie : Shielded Area,… Information access allowed from anywhere to anybodyInformation access allowed from anywhere to anybody  WEB Access Software components in-line with the procedureSoftware components in-line with the procedure Final decision concerning the software development will impact the LAPP development teamFinal decision concerning the software development will impact the LAPP development team