PTC - Choosing a procedure

As mentioned above, procedure managers should expose an efficient way of allowing the idea holder to identify which procedure is appropriate. It would be great to have a browser decision form whose questions direct the project requester to the correct procedure, but we do not have this yet. Therefore base the decision on the chart below and ask at the email addresses given.

Below is a flat way of looking at all work coming in, DATA needs to decide is this is the correct view of the world, or propose anothre view.

An immediate issue is how do long procedures apply project acceptance thresholds which require technical input to decide.

PTC choosing a procedure

PTC Choosing a procedure chart, where

DATA Daily work definition - questionnaire

Daily work looks like a procedure, work items can be specified by non-DATA (e.g. by the CTRL-ICI instrument contact or controls-integration@xfel.eu which inserts a ticket into Controls’ Redmine) or DATA (e.g. EEE-PLC request to update loop f/w) personnel and the ability of DATA to perform daily work depends on the availability of resources.

The table below are DATA group and team answers to: ‘What work would be done w/o the need for it to be in a procedure project?’. The CTRL-ICI example answer given avoids having an empty definition column.

The table prompts an additional question: ‘Are Group or Team abbreviations correct and are any missing?’. Whilst inserting definitions please update the column. The abbreviations need to be clarified as they are frequently used by the PTC interface, e.g. in the PMO cost estimate.

Group or Team Daily work definition
CTRL  
CTRL-ICI An item requiring no more than 1/2 a day which can be scheduled during the next 2 weeks.
CTRL-DEV  
DA  
DETOP  
DETOP-CAL  
EEE  
EEE-EDS  
EEE-FET  
EEE-PLC  
ITDM  
ITDM-DAQ  
ITDM-INFRA