PTC - ERD projects

The ERD procedur workflow is shown below and a simplified PTC version follows.

EEE's ERD procedure workflow chart

EEE’s ERD procedure workflow

PTC's simplified ERD procedure workflow

PTC’s simplified ERD procedure workflow

ERD workflow as seen by DATA

As stated in the ‘big picture’ chapter PTC acts as an observer to the ERD and CRD short procedures. The single proviso is that the short procedures must comply with PTC’s inteface requirements. For ERD this should be quickly achievable as PTC tooling was initially developed by dry-running a ERD like workflow definition with the CRD workflow joining later. The PTC interface requirements on ERD are related to the following points:

  • the Redmine representation of a request task is defined to be a single task injected into Redmine via an email (address?) with template content specifying key elements of the requested project.
  • the Redmine task and sub-task structure is defined for the different equipment type implementations (Karabo s/w and no PLC, PLC with existing Karabo s/w interface, and PLC with new Karabo s/w interface).
  • the ‘Elvis’ Redmine tracker type is used for workflow tasks with its statuses and developer and manager allowed transition definitions.

Role definitions

PTC:

  • is an observer viewing the ERD procedure through the PTC interface
  • performs DATA resource scheduling with ERD PEPs and GL using ERD and other procedure views

PEPs:

  • ensure that new equipment is fed through the ERD procedure
  • comply with the PTC interface requirements
  • ensure that the ERD procedure (tasks execution, meetings, etc.) is efficiently and managed
  • assign developers to tasks based on DATA resource scheduling decisions

PTC tooling assisted management actions

PTC tooling should be used to assist management actions.

The Redmine task count in 50 ERD implementation workflows analysed currently lies in the range 10 - 30. Manually creating and managing these tasks is a significant workload which can be reduced with:

  • workflow_injection to inject workflow tasks (subject, assignee, etc.) defined in a spread sheet into Redmine.
  • workflow_update to update the spreadsheet from Redmine during and on closeout of the project.

Other assist options are:

  • migrating Cancelled and Rejected projects to their final Redmine locations
  • tune the PTC interface configuration options to match the needs of the procedure to produce project status summaries, meeting agendas, etc.

Project scheduling

This activity is a responsibility of the PEPs concerned albeit with the requirement that a consensus of scheduling is reached with DATA’s PTC.

Project closeout

ERD projects should be relatively short, this should be confirned by ensuring that time spent information is aggregated during project closeout.

ERD meetings

ERD decision meetings are currently held twice per month and PTC will attend these meetings.

PTC email lists

The SYMPA mailing list service is used to assist communication by defining

  • ptc-erd, the ERD-PEP contacts

Mail filters applied to the email subject are used to shape PTC activity.

  • PTC-ERD, for PTC communication