act – fourth months later… prepared by: martin gastal jim cook 22/03/20111jim cook & martin...
TRANSCRIPT
Jim Cook & Martin Gastal 1
ACT – Fourth months later…
Prepared by:Martin Gastal
Jim Cook
22/03/2011
Jim Cook & Martin Gastal 2
Agenda→Activity Coordination Tool - Introduction→Project Status→Operational statistics & incidents→Use cases
→1. Shutdowns & Extended Technical Stops→2. Operation, Machine development periods,
Technical Stops, Short accesses→Next steps
22/03/2011
Jim Cook & Martin Gastal 3
ACT Introduction• Project started in 2009• Goals: – Provide a web based application to manage Work
Packages in the CMS Experimental Area– Build up the memory of the experiment
• Application to handle data exchange with various CERN/CMS databases
• Continuous improvement process driven by user feedback
22/03/2011
Jim Cook & Martin Gastal 4
ACT Introduction• Database created to fill all long term needs• Fourth version of the ACT is now available• Specs
– Locate on “CMS on-line” server– Back-end: Oracle– Front end: JavaScript– Development environment: JDeveloper– Portability: Optimised for Internet Explorer, Safari (mac &
iPhone), Opera, Google Chrome and FireFox• Core team:
– Software Engineer: Jim Cook– DB Administrator: Frank Glege– Application Developer: Stephane Bally
22/03/2011
Jim Cook & Martin Gastal 522/03/2011
ACTCore
module
EquipmentTraceability
module
Notification module
Engineering Integration
module
Toolingmodule
Risk Asses.module
Short Accessmodule
Documentlibrary
module IncidentManagement
module
Advancedplanningmodule
AccessControlmodule
Surveymodule
RPSurveymodule
✔✚
CompleteOn-goingPlanned
✔
✔
✔
✚
✚
✚
✚
✔
✚
✚✚
VisitsManagement
module
Jim Cook & Martin Gastal 6
3 key functionalities: 1. request a WP 2. modify/clone a submitted WP 3. browse the list of submitted WPs
Connect to EMDbRetrieve equipment tree structuresMonitor equipment moves in/out of RP designated areasInventory managementBuffer zone management (bar code)
Radio Protection measurementsALARA analysis (Collective dose) RP measurement in buffer area
Notify group of users by Email/SMSTypical messages: Your WP request has been accepted Your WP has been modified You are requested to provide more info on your WP Short access imminent… VIC organised…
22/03/2011
ACTCore
module
EquipmentTraceability
module
Notification module
EngineeringIntegration
module
Toolingmodule
Risk Asses.module
Short Accessmodule
Documentlibrary
module IncidentManagement
module
Advancedplanningmodule
AccessControlmodule
Surveymodule
RPSurveymodule
Program PADs for General Access
Connect to CatiaDisplay 3D geographic/ configuration viewsTrack changes in integration models
Connect to MTFDisplay tooling specsCheck tooling certifications
Gantt chartDay by day schedule
Risk/location/configuration matrixList of preventive actions
PicturesWork procedures
Archive Survey reportsLink to on-line alignment community
Create and advertise new accessManage the use of operational dosimetersManage the RP sweep
Track incidentsFollow up corrective actions
Jim Cook & Martin Gastal 7
Operational Statistics• Downtime ~2.5 days– ACT in operation 119 days, ~98% availability
• 534 Work Packages processed by ACT since 24 November 2010
• 526 people named on Work Packages– From 1 to 44 Work Packages per person, average of 3.5
• 112 visits requested via ACT with at least 221 visitors– Since start of year, 121 visits plus 16 VIP visits (including
visits not requested via ACT)• Work Package requests– ~80% by PH/CMS personnel
22/03/2011
Jim Cook & Martin Gastal 8
Downtime and Incidents• Database maintenance 14 and 15 December 2010
– Portal (CMS online) not available– No Work Packages could be viewed, requested or administered
• Offline Database maintenance 19 January 2011– Access control system inoperable
• Issue with streaming 14 February 2011– Access control information lagged by ~3 days
• Portal offline for ~1 hour 4 March 2011– Though no complaints made ;0)
• Access control system slow to update 7 March 2011– Reason not fully understood– Actions being taken to diagnose future issues– Problem solved for short accesses
• Hardware faults of offline database 11 and 15 March 2011– Both main hardware and backup hardware (supervised by IT) failed
22/03/2011
Jim Cook & Martin Gastal 9
Use Case 1• Managing shutdown and extended technical stops– Flow
22/03/2011
WP declaration Insert in long term plan
Risk AssessmentALARA
Insert in short term plan
VIC Workexecution
WP completion
Jim Cook & Martin Gastal 10
Use Case 1• Managing shutdown and extended technical stops– Flow: WP declaration
22/03/2011
WP declaration Insert in long term plan
Risk AssessmentALARA
Insert in short term plan
VIC Workexecution
WP completion
Done by the CreatorCan be modified at any timeby both the Creator and theWork Supervisor
Jim Cook & Martin Gastal 1122/03/2011
Cables to be installed between theUXC55 and the USC55
Example – PLT work declaration
Jim Cook & Martin Gastal 1222/03/2011
Predefined accesses
Jim Cook & Martin Gastal 1322/03/2011
List of personnelPartial information Enough at that stage
WP number
To keep track of the max number of keysTo be used
Jim Cook & Martin Gastal 1422/03/2011
State of CMS magnet
All locations to beaccessed during installation
Location tree is experiment specific
Jim Cook & Martin Gastal 1522/03/2011
Systems affectedby WP
System tree is experiment specific
Jim Cook & Martin Gastal 1622/03/2011
Equipment needed toexecute the WP
Jim Cook & Martin Gastal 1722/03/2011
RP traceabilityinventory items are identified and assignedto a move typeIn, Out, Relocate
Item IDLinked to EMDbusing bar code
Jim Cook & Martin Gastal 1822/03/2011
Most relevant for ALARA
Jim Cook & Martin Gastal 1922/03/2011
Basic risk matrix inplaceWill get updated withconfiguration of detector
Jim Cook & Martin Gastal 2022/03/2011
Most relevant when safety systemsor subsystems are affected
Jim Cook & Martin Gastal 2122/03/2011
Summary pageAll sections can be edited individually
Option toforward to TIOC
Notification sent to WP actors
Jim Cook & Martin Gastal 22
Use Case 1• Managing shutdowns and extended technical stops– Flow: WP acceptance and insertion in long term plan
22/03/2011
WP declaration Insert in long term plan
Risk AssessmentALARA
Insert in short term plan
VIC Workexecution
WP completion
Through Technical Coordinationmeetings, decision made to schedule the workStatus update take place throughSuper user interface
Jim Cook & Martin Gastal 23
Use Case 1• Managing shutdowns and extended technical stops– Flow: Work package analysis meeting
22/03/2011
WP declaration Insert in long term plan
Risk AssessmentALARA
Insert in short term plan
VIC Workexecution
WP completion
Review of the method of workRisk assessmentUpdate of relevant sections:
Risk, Alarms, Personnel…
Jim Cook & Martin Gastal 24
Use Case 1• Managing shutdowns and extended technical stops– Flow: Insert in short term Plan
22/03/2011
WP declaration Insert in long term plan
Risk AssessmentALARA
Insert in short term plan
VIC Workexecution
WP completion
Link to day by day scheduleMade available on ACT Main pageHyperlinks to ACT to be available shortly
Jim Cook & Martin Gastal 25
Use Case 1• Managing shutdowns and extended technical stops– Flow: Work package execution monitoring
22/03/2011
WP declaration Insert in long term plan
Risk AssessmentALARA
Insert in short term plan
VIC Workexecution
WP completion
Monitoring of WP by CMS shiftersDaily list of active WPs and authorisedpersonnelLink to access control system forUXC55 Access management
Jim Cook & Martin Gastal 26
Use Case 1• Managing shutdowns and extended technical stops– Flow: Work package completion
22/03/2011
WP declaration Insert in long term plan
Risk AssessmentALARA
Insert in short term plan
VIC Workexecution
WP completion
WP supervisor to close WP upon completionand to add a comment eg 100% complete,reduced scope, will have to be restartedduring next technical stop…
Jim Cook & Martin Gastal 27
Use Case 2• Managing Operation, Technical Stops, Machine development
periods, and short accesses– Flow:
22/03/2011
Create and advertise
access
Risk AssessmentALARA
VIC
Workexecution
WP completionWP declaration Schedule WP
Jim Cook & Martin Gastal 28
Use Case 2• Managing Technical Stops, Machine development periods, and short
accesses– Flow: Create and advertise an access/MD period
22/03/2011
Create and advertise
access
Risk AssessmentALARA
VIC
Workexecution
WP completionWP declaration Schedule WP
Edit existing access/MDP
Create access/MDPMagnet state is essential
Lifting the Radiation VetoMax Dose measured during sweep
Jim Cook & Martin Gastal 29
Use Case 2• Managing Technical Stops, Machine development periods, and short
accesses– Flow: WP declaration
22/03/2011
Create and advertise
access
Risk AssessmentALARA
VIC
Workexecution
WP completionWP declaration Schedule WP
Time window:TStop, Next short access, MDP
Duration and working hours
Foreseen impact
Jim Cook & Martin Gastal 30
Use Case 2• Managing Technical Stops, Machine development periods, and short
accesses– Flow: WP scheduling
22/03/2011
Create and advertise
access
Risk AssessmentALARA
VIC
Workexecution
WP completionWP declaration Schedule WP
Specific access/MDP
Swift editing functionalities
Acceptance done during TC meetings and TECOPA
Jim Cook & Martin Gastal 3122/03/2011
Jim Cook & Martin Gastal 32
Next steps• Complete EMDb module.
– Designed by S bally– Based on existing EMDb (using APEX)– Developed independently from other modules– Fully integrated into ACT
• Start working on Incident Management module– To be done by German Technical Student
• Complete RP Survey module– To be done by Jim based on requirements from RPEs– To handle operational dosimeters plus material in the
buffer zone
• Design the Visits module– To be done by Jim based on requirements from Dawn– To include management of key cabinet
22/03/2011