IMWG - LHC machine 1

LHC machineSchedule, coordination & WAT

K. ForazMarch 22nd, 2011

March 22nd, 2011

IMWG - LHC machine 2

WGIM

Initial « constat »

Beginning of last year, situation was:• On the intervenants side:

– Information to the different coordination teams– Edition in the TIOC list– Negotiation to get a date– Safety analysis: VIC, fiche de tache…– Edition of ADI– Edition of AOC, fire permit…– Performance of the task (hopping that nobody is sick..else re-ADI)– Progress report to different coordination teams

March 22nd, 2011

IMWG - LHC machine 3

WGIM

Initial « constat »

• On the coordination sides:– Edition of the information in our own system

• Coming from mails, phone calls, meetings

– Check information with the other system• i.e. with TIOC

– Scheduling– Safety check with safety coordinators– Check in EDH that ADIs were correctly signed by the OP group !!!

• Vocabulary problems• Some work scheduled and approved were rejected• Some work not scheduled were rejected

– LHC operator granted access thanks to the ADI numbers (awful job)

March 22nd, 2011

IMWG - LHC machine 4

WGIM

Initial « constat »

• Discussions were held between OP, EN and GS– We need a tool

• As time was running towards the end of the year, We took the decision to start simple: create and test a tool, which was respecting a simple workflow, not linked to objects, but to activities (as a first stage), allowing us to :– Avoid multiple edition of the same information– Have an accurate control of activities– Ease the access

March 22nd, 2011

IMWG - LHC machine 5

WGIM

General Workflow

March 22nd, 2011

Request

Technical Approval

Scheduling

Safety preparation

Follow-up

Closure

IMWG - LHC machine 6

WGIM

1. Intervenants make a Work Request (1/2)

Same type of work covering different areas in the machine

• What– Title– Type: consolidation, upgrade, inspection, maintenance, repair, test…

– System type: based on the LHC naming convention

– Long description

• Technical Approval from LMC needed

• Who– Work responsible– Max participants per location (needed to estimate the number of keys)

– Number of teams (needed for schedule purposes)

– Participants names

March 22nd, 2011

IMWG - LHC machine 7

WGIM

• When• Date constraints• Intervention date• Intervention period type• Duration per area• Comments

• Locations

• Safety• Activity risks (anoxia, Chemical/industrial hygiene, Compressed air, Cryogenics, Electrical,

Fire/Explosion, Gas, Ionizing radiation, Mechanical. Non Ionizing radiation)• & compensatories measures • Lock-out type: CV, compressed air, cryogenics, DIMR, electrical lock-out level 2, electricily, Fire

permir, Gas, IS37, RP

1. Intervenants make a Work Request (2/2)

March 22nd, 2011

Send

IMWG - LHC machine 8

WGIM

2. Coordination team analyzes the request

• Can add activity risks/ Locations / Participants

• Can specify whether AET is needed or not

• WAT generates automatically tasks with the same characteristics as its Work Request, but for the spectrum of location defined.

March 22nd, 2011

IMWG - LHC machine 9

WGIM

3. Scheduling phase (1/3)

• From all the requests– 1. Constraints schedule

• Identification and schedule of the blocking activities

March 22nd, 2011

IMWG - LHC machine 10

WGIM

3. Scheduling phase (2/3)

– Schedule of the other activities w.r.t.• The constrainsts schedule• Resources available• Minimize co-activities

• First draft in MsProject….. But not all the participants read it…

– Insert correct dates in WAT, thanks to an excel sheet

March 22nd, 2011

IMWG - LHC machine 11

WGIM

3. Scheduling phase (3/3)

• Extraction from WAT in Excel….. Macro…– Schedule under excel readable by all

March 22nd, 2011

IMWG - LHC machine 12

WGIM

4. Safety preparation

• Each Work Request is discussed in preparation meetings with work responsible and safety coordinators

• If an AET is needed, then – Automatic generation of the AET(one week before the start), thanks to

the information already edited in WAT– For the last Xmas break, derogation from HSE to have all the AET send

only for approval…– Else it will have followed the AET-EDH workflow (future presentation

by Serge ?)– If AET is approved, then the task is approved

March 22nd, 2011

IMWG - LHC machine 13

WGIM

5. Access and Progress

March 22nd, 2011

• Providing that today• One has the access right to the machine• A work for a specific location

• Declared• accepted technicaly• Scheduled• approved in matter of safety

• Access will be granted• If access is in restricted, this person will be

delivered a key

• Schedule is updated through the Excel schedule

Request

Technical Approval

Scheduling

Safety preparation

Access & Follow-up

Closure

EDH

Access

IMWG - LHC machine 14

WGIM

WAT Inside: Work Request Workflow

March 22nd, 2011

IMWG - LHC machine 15

WGIM

WAT Inside: Task Workflow

March 22nd, 2011

IMWG - LHC machine 16

WGIM

WAT Inside: Integration with existing systems

March 22nd, 2011

WATEDH Layout Database

ADAMS

Foundation

Access Control (person/place/time)

LHC Locations

Access Points

Notifications

Signatures

Persons, Organic Units

Excel

Schedule Export, Bulk Update (Upload)

IMWG - LHC machine 17

WGIM

WAT Inside: Integrating the AET (EDH)

March 22nd, 2011

EDH buttons: authorization without leaving WAT (or still from within EDH)

EDH Document status / Info lines

Direct URL to access a task

Adams access control

IMWG - LHC machine 18

WGIM

WAT debriefing after the break

• Powerful Tool

• Very good feed-back form all the actors: users, coordination teams, access control…

• Strong control of activities with flexibility for users (intersite doors opened, addition of intervenient..)

• The operator is no longer a bottleneck with multiple access points in simultaneous access request, and more importantly no more waiting times of several minutes for the users to get the operator attention to get by.

• Very good support form AIS

• Some improvements already done and other in the queue

March 22nd, 2011

IMWG - LHC machine 19

WGIM

Conclusion

• The Work Acceptance tool has demonstrated its usefulness and its performance

• Before going to far… it would be nice to get your impression, and develop a common tool to fulfill the desire of our hard worker partners.

Thank you

March 22nd, 2011