92
Competency Seminar Competency Pathways – Control Systems Standard Launch Masonic Centre, Sydney April 2015 August 2015
Competency Seminar Competency Pathways – Control Systems Standard Launch Masonic Centre, Sydney
April 2015August 2015
Welcome Jennifer Duxbury Industry Engagement Coordinator
August 2015
- Transport NSW Asset Standards 00VERNMEl'1T Authority
Emergency evacuation procedure
IF YOU HEAR THE FOLLOWING ALARMS:
ALERT ALARM
Action : All wardens to respond. Staff to check immediate area for signs of darmger and stand by. (Outside normal working hours immediately evacuate on sounding of the Alert Alarm)
EVACUATION ALARM I~ 2ooi>wnoop
Action : All staff evacuate via the nearest exit and proceed to the assembly area.
KNOW YOUR EXITS
FOR YOUR SAFETY MAKE SURE YOU KNOW THE LOCATION OF THE NEAREST EMERGENCY EXIT
ASSEMBLY AREA
LIVERPOOL STREET
1-w w a: t;
GOULBURN STREET
Hyde Park
August 2015
Asset Standards Authority Progressing across all modes Jim Modrouvanos, Executive Director
April 2015August 2015
TfNSW update
Freight, Strategy & Planning
Deputy Secretary Freight, Strategy &
Planning
Executive Director Bureau of Statistics &
Analytics
Executive Director Transport Strategy
Executive Director Freight Industry
Executive Director Transport Policy
Executive Director National Policy & Priority Initiatives
Executive Director Transport Networks
Executive Director Asset Standards
Authority
Executive Director Centre for Road
Safety
Executive Director Safety, Environment
& Quality
Our challenges ahead
• Governance across transport modes
• Defining ASA’s technical role across all transport modes
Setting The Scene – The Competency Imperative……. Mark Smith Principal Manager Industry & Technical Development
August 2015
Agenda
• Background • Mark Smith, Principal Manager, Industry & Technical Development • Steve Lemon, Signalling & Control Systems Manager • Fiona Love, Principal Manager, Capability Services, Organisational
Development
• Launch • Omer Saricilar, Principal Engineer, Control Systems • Jocelyn Edwards, Manager Competency Systems
• Demonstration
• Jocelyn Edwards, Manager Competency Systems
• Wrap up
• Mark Smith, Principal Manager Industry & Technical Development
August 2015
Purpose of Seminar
We recognise competency is a popular subject…
Above all else - we want to hear from you regarding competency, our approach and our documentation. Key Objectives
• To focus on the AEO population • To reframe the strategic imperative to broaden the competitive supply
chain for the provision of critical services • To articulate the TfNSW position & intent • To clarify the role of TfNSW and TfNSW engaged entities • To launch the ‘Competency Pathways – Control Systems’ Standard (T
MU CY 04000 ST) & guide • To test elements of the standard in a workshop environment &
feedback accordingly • Start to establish a common language
August 2015
The Assurance Game - Many pieces to build….
AEO Capability Profile
Maturity ratings summary 5.0
0.0
1.0
2.0
3.0
4.0
Engineering Management
Competency Management
Configuration Management
Quality Management Systems Engineering
Documented Average Deployed Average Combined Average Highest average
TfNSW competence, compliance and accreditation framework
(/) :i... Q)
> ·;:::: 0
Q) c urn ·- :l "'O ta "O Q) Eoo :i... ;:
0 Cl. 0 ~c ~
rn c
'Vi c Q) u ~
National Laws
TfNSW Competency Requirements
(Generic)
NSW Laws
individual to work
August 2015
TfNSW Collaborative Competency Delivery Model – Who Does What?
TfNSW Asset
Standards Authority
O&M Agencies
(e.g. Sydney Trains)
TfNSW Organisational Development
Sets the Generic competency requirements for specific (critical) functions & publish on behalf of TfNSW for the AEO population
Provides the Product and Domain competency requirements & information
Supports the provision of education, competency and training products and services to enable industry to meet the competency requirements
August 2015
Stephen Lemon Signalling & Control Systems Manager Sydney Trains
August 2015
Collaborative Competency Delivery Model
TfNSW Asset
Standards Authority
O&M Agencies
(e.g. Sydney Trains)
TfNSW Organisational Development
Provides the Product and Domain competency
Supports the provision of Sets the Generic competency education, competency requirements for specific requirements & and training products and (critical) functions & information services to enable publish on behalf of industry to meet the TfNSW for the AEO competency requirements population
The Operator / Maintainer Perspective
The importance of rigour of assessment. • Sydney Trains need AEOs to be able to demonstrate
they have assured themselves that competent people will deliver the work in control systems
• The network is complex and the consequences are high risk
August 2015
The Operator / Maintainer Perspective
Road to authorisation
• Sydney Trains are working with ASA & OD to determine the gaps in domain & product knowledge.
• Authorisation to work on the network follows meeting the Standard and addressing the gaps.
Fiona Love Principal Manager - Capability Services Organisational Development, TfNSW
August 2015
Collaborative Competency Delivery Model
Sets the Generic Provides the Product and competency Domain competency education, competency requirements for specific requirements & and training products and (critical) functions & information services to enable publish on behalf of industry to meet the TfNSW for the AEO competency requirements population
TfNSW Asset
Standards Authority
O&M Agencies
(e.g. Sydney Trains)
TfNSW Organisational Development
Supports the provision of
& the problem
The Clients and the Problem clients
The problem they h ave: • No well targeted or useable educational pathway • No defined competence standards in some areas • Opaque internal systems that allow contractors to be productive The scale of the problem: • Across all industry sectors.
August 2015
Our challenge is …
Competency & Capability
-
No formal trsiJning cur·1reriH)' exists
August 2015
Create a Capability Framework
August 2015
Rail Control Systems
Competency~;(· 'I Corn~~ B I i C«npe!eocy C
I I I
I
AQF l1Wt:)I 0 Graduate ColtlflcaM In Rall Control Systamt.
Develop a series of e-learning modules
August 2015
Develop a series of elearning modules
Develop an Assessment Framework for Recognition of Current Competence
August 2015
Develop an Authorisation Process
August 2015
AQF aligned
•• •• •• ..... •• ••
Competency Framawork
Step
4
Develop an authorisation process
The Solution…
August 2015
Generic Rail Control Systems Program
•
Product-specific Program - ATRICS
Step
4
Evidence Portfolio
Rail Control Systems Capability Framework
Generic (AQF)
Underpinning engineering qualification
Graduate Certificate in Rail Control Systems AQF 8
ASA Competency Pathway – Control Systems.
Underpinning e knowledge Course Underpinning Knowledge
Intro Rail Networks, Infrastructure and Terminology Control Systems Interlocking Telemetry System
Design - Scoping The Project - Designing Control System Data - Designing Infrastructure.
Build Build Infrastructure Load Software
Test - Testing Control Systems - Commissioning Control Systems
(Specific to Sydney Trains)
Products and Systems Training and Accreditation
ATRICS Phoenix VICOSS SIGVIEW
Core Functionality Systems Data Manager Classes of Data Data design /infrastructure design modules Deployment and Commissioning.
Product
Domain (Enterprise)
SX52 – Safely Access Rail Corridor (RISI) Access to live locations. Safety Management System (Sydney Trains SMS) ST Specific Training in Configuration Design, Infrastructure Design & Control and Test.
Authorisation and
commissioning
What else is happening?
• Sieving exercises to develop domain and product programs • Broader access to Transport Training Centre • Exploring new learning technologies such as e-learning
info/graphics, apps • Ensuring greater use of required capability frameworks such as
Engineers Australia to minimise barriers to recognition of professional standards knowledge
• Advising and collaborating with major AEO’s to design accreditation
• How are systems that are risk base accessible and support efficiency and productivity
• Establishing a glossary of terms for all parties within the transport cluster
August 2015
Sieving exercises to develop domain and product programs
August 2015
Broader Access to Transport Training Centre
August 2015
Exploring new learning technologies such as e-learning info/graphics, apps
• Build 10 e learning modules (Generic)
August 2015
Ensuring greater use of required capability fr ameworks such as Engineers Australia to minimise barriers to recognition of professional standards knowledge
Advising and collaborating with major AEO’s
August 2015
How are systems that are risk based accessible and support efficiency and productivity
August 2015
Establishing a Glossary of Terms
TtNSW - Glossary or 1 erms
evieUonsl Oe•CriptiODS .,,,,. 'O 20 10
"""9d4atlon
~edCoorse
-eo
\Of
"'9essment (of ::ompetenco)
iluthorisation.
Competence
A mocMI lot lndiclt.ng a combination of on Iha Job. oo.c:lllng and formal teaming lj)l)loacll to development.
Accteclllaban Is IN> process In wl1lch cerllficaban of competence. authority. 0< equivalency ls presented that oomplles ...th defined standards_
A prcgram of leaming that oomprises one°'"""" oompononts (e.g. units of competency. modules°' subjecls) lhat has been endorsed by an accredb1g atfhonty.
An lndMdual who hos demonstrelod """"*""'" and been deemed ...-to hold Ille accreditation by an AEO (tnd " required, a RIM)
AtJthorlsed ~Organisation. A IUlll*erol •defined eng1neG1V>g seMce or product that has been assessed and granted AEO status by TINSW
AUSlr.lian Oualificatlons FrameWO<I<.
Assel Standanls Authonty
Austrdan Slub Oua111y Autho<lty The - ~tor fO< Auslrella'• vocabonll oduca1ion and training -
The pn>cess ol oolleclong a range of oY!dence and malting )\Jdgements on whether competence has been - to confirm that an lndMdual can petform to Ille standards expected In Iha """1<placa.
Tile Internal process vmereby a responsible entity deems a produc:t. service °' ondMdual compliant to requifMlenls and regulatory and legislatrve mandates.
The~ slulls and obthlles to perform a - effectively. The venl'lcaban and aUlhentlcatlon of a -· en~1lement to recogn4IOn
The aystemabe proce11 of ensumg thal al equiprl*1t and systems pertorm onteracbvely according to the de$i!jll in1Bnl and the operational andUSe<-ts.
The idenlific:aban and application or know1edge, Skits and behaviours requred to petform laSks 10 the standards "'1'*9d,
''Q·filOv.au
August 2015
Omer Saricilar Principal Engineer, Control Systems Asset Standards Authority
August 2015
Presentation Structure
1. Something Simple
2. Train Control Systems • Design Examples • Components • Competency Examples
3. Customisation
4. Questions
August 2015
An Analogy…….. Control Systems are normally very complex. We will start with something everybody knows and uses…….
When you buy a car: • You know the reasons behind common functionalities, such why the car
should have a powertrain, what the powertrain does, what are the parameters of powertrain.
• Using the common knowledge, you can understand the common specific functionalities of the powertrain of the specific car and you can make a comparison.
• Without such common knowledge, you may not understand the specific functionalities, such as what is rev, torque, cylinders, kW, hp etc…
• Only common knowledge is transferable between cars – for example knowledge about turbo charge may not transferable, unless it is common to all cars.
August 2015
An Analogy – cont’d
All vehicles may have the following minimum components: • Powertrain • Transmission capabilities • Steering capabilities • Braking capabilities • Etc…
All cars have the minimum components • All vehicles’ minimum components • Signalling capabilities • Seating capabilities • Night driving capabilities • Protection against weather • Etc…
August 2015
An Analogy– cont’d There are levels of knowledge: • Generic: applicable for all levels which are specialisations of this knowledge
such as vehicle.
• Domain specific: may not be transferable to other domains, such as bicycle vs car.
• There could be more layers depending upon the system’s complexity and configuration.
It is normally assu med that • Generic knowledge is transferable, re-usable and an enabler for domain
knowledge.
• Domain specific knowledge is not directly transferable, re-usable and an enabler for other domain knowledge. But it enhances and supports the generic knowledge and creates experiences.
August 2015
Venn Diagram - 1880 by John Venn
August 2015
Train Control Systems (TCS)
August 2015
Production Components of TCS • Generic Product – normally software and associated tools
• Infrastructure – environment the product and its configuration reside and perform:
• IT and associated software/firmware • Networking • Interfacing to signalling systems • Electrical • Environment
• Configuration – adapts the generic product and its infrastructure to the specific
application: • Signalling • Operation • Infrastructure
• Testing - needs to cover all three areas.
August 2015
ATRICS Infrastructure &nr.-lleld
Sl:nltl'lfl!ld &;nal &oc Comra4 R"'°""
~ ......... -· B )
_,,,.. -.c; -·
~
r.,,._ -· Canmmtl11a1il:xl
Backbone
... _ -·
(Homlibusi"t Ccc-Jrct COl!IJe Con:lml ~
!:pplns \'lla'b!Dlkr>
---- ·
-.u -· ---·
--~ --·
·-
August 2015
PHOENIX Infrastructure
August 2015
Proposed Main West Infrastructure
,-----------------' I I I I I I
......
·---------------------------
-· ·- --! -----~-----------~-----------
August 2015
Infrastructure Components
UNCOMMON COMPONENTS
• Overall design • Types of Servers • Types of Workstations • SOE (Standard Operating
Environment) • Types of Routers/Switches/Firewalls• Network Configurations • Telemetry Interfaces • Electrical Interfaces • Etc…
COMMON COMPONENTS
• Overall design • Servers • Workstations • SOE (Standard Operating
Environment) • Routers/Switches/Firewalls
• Network Configurations • Telemetry Interfaces • Electrical Interfaces • Etc…
August 2015
Common Engineering Knowledge • Understanding business requirements
o Signalling o Operational o Maintenance
• Translating business re quirements to specific control systems’ requirements
• Translating non-functional requirements to specific control systems’ requirements (such as RAM)
• Translating safety requirements to specific control systems’ requirements
• Translating control systems requirements to components’ requirements
• Design or modify the existing design to implement component requirements
• Etc…
August 2015
Common Engineering Knowledge – cont’d
• Information Technology
• Networking Technology
• Electrical Engineering
• Electronic Engineering
• EMI
• RAMS
• Testing
August 2015
A TCS Example
• Business Requirements: Modification and expansion of the existing train
yard with an additional interlocking – more tracks, points and new operational rules.
• Control Systems Requirements – Element 2: Adding and modifying maps, IO tables, rules, alarms Addition of new interlocking Safety and non-functional performances Etc…
August 2015
A TCS Example– cont’d
• Infrastructure Requirements – Element 3:
• Handling new interlocking • Handling new workstation – existing workstation can
not handle it due to limited real estate. • Modification of network to handle new workstation • Not affecting the existing RAM requirements due to
new hardware • Not introducing new hazards and affecting existing
hazard • Etc…
August 2015
A TCS Example– cont’d
Elements
3 E51ablishes
infra51ructure design and
construction
requirements
3.1
Evidence criteria
Identifies and allocates
infrastructure related
requirements from the Project
Scope and Control systems
Funct1onal Specification to:
determine the functionality required by existing or new
1nfrastruaure components
determine what infrastructure
needs to be installed, modified and disposed of to ensure all operation,
maintenance, trainin&. suppon and disposal
requirements have been
addressed
ldentJfy and update RAM requirements
ensure hardware specification
factors are incorporated and
accommodated
establish wflether
components outside the
standard operatirc environment will be required
identify hazards or allocate
hazards or both related to t he
infrastructure
Functions
y y y N N 2, 3, 4,
12, 13,
14
E $
3.2
3.3
3.4
Analyses control systems
f\.nctional specifications, control
systems cil"cuit books and any
other relevant input documents to
Identify and confirm: . staging requirements for the design . impacts on and of other
projects . impacts on testing, training
and s141port systems . other relevant
implementation issues
Identifies and analyses
infrastructu re inte rfaces and the
system integration at a detailed
leve l. Identifies project, system,
and safety hazards and creates or upd.ates sa fety cases accordingly.
Conducts site surveys to: . confirm location and current
state of documented
infrastructure . confirm that existing •As-&JilT" are current . evaluate the capacity and
compatibHity of existlne system to accommodate the
proposed changes . identify site hazards and
potential obstades in meetinc
desi&n requirements . confirm requirements for
meeting desien specifications
'C ~
i >
"" ~ t: 11
c ! 2 ii .. ~ 0
.~ R ~ j !~ y y y N N 2, 3, 4,
U ,13,
14
y y y N N 2,3, 4,
12,13,
14
y y y N N 2, 3, 4,
12,13,
14,15
Elements Evidence criteria
Functions
... .. 1 21
1 ..
N .. -
August 2015
A TCS Example– cont’d
Infrastructure Design – Element 4: • Workstation only:
• Existing workstation design will be used with brand new hardware – since not available anymore. Check and verify against
• Applicable standards, • Identified interfaces, • Required RAM • Existing or newly identified safety hazards • Addressing existing issues/problems
improvements • Proposed testing plan • Create and submit type approval document.
August 2015
A TCS Example- cont'd
Functions
a: ~ tl i al
c
I g i ·§ ~
!IP ~ ~ ~ R ·c:
~a .t: ~ 9- 8 4.4 Evaluates the feasibility of all y y y N N 4, 12,
Elements Evidence criteria possible design solutions and 13,14
'$ selects the optimum design which
) :i; .. ...,.
i "C ... .. u .i ..... >-
a: ~
tl 11 11 Q :;r
~ 0 5 ~ ;; E
~ ~ ·c } ~ j] ~ ~
meets identified design,
construction, maintenance, and
business constraints.
4.5 Identifies designs and develops y y y N N 4, 12,
preliminary tests in order to 13,14 4 Develops a 4.1 Identifies, interprets and analyses y y y N N 2, 3, 4,
desien and the relevant desi:n, industry and 12
construction reeulatory standards and design
mitigate previously identified risks~
safety and interface issues.
solution that th• infrastructuro solutions to 4.6 Assesses whether or not • type y N N N N 4, 12,
m•ots proj•ct comply. approval" is required for any a.ssets 13,14
r•quirem• nts 4.2 Analyses previously produc•d y y y N N 2, 3, 4, and initiate type approval
project documents to determine: 12,13, 4.7 Initiates "ASA concession• process y N N N N 4, 12, . th• compl•xities and risks of 14 if the design does not comply with 13,14
th• intorfacos and standards.
intord•pond•ncies with existing control systems
infrastructure and rail
4.8 Identifies analyses a nd documents y y y N 4, 12,
all new or modified confi~ration N 13,14
operations data applicable to the new or
. dosign options and solutions modified systems for the
infrastructure. . applicable RAMS
requireme nts desien 4.9 Documents the design, using y N N N N 1, 4,
constraints and construction appropriate software tools to 12,
limitations produce detailed diagrams and 13,14 . appropriate precedent desiens drawings.
that could be replicated for 4.10 Validates design quality and y y y N N 4, 12, the rurrent pro,,ect completeness, ensuring that: 13,14 . protection and isolation of the
safetY critical systems . it meets the requirements of
the Control Systems . potontial businoss continuity Functional Speafication problems and mitigation . it complies with all relevant
4.3 Applies knowled&e of enginee ring y y y N N 4,12, standard.s desoen concepts, principles, 13,14
theones and techniques to explore 4.11 Pre5ent5 the design solution, y N N N N 4, 12,
possibilities, solve design problems ensuring all stakeholders 13,14
and develop credible solutions understand the merits of the
which proporty address the critical design, and how it meets the
design issues and assumptions. project requirements.
--------------------------------------------
·~ ..... >
August 2015
Functions
Eleme nts Evidence criteria
'$ ~ l5 .. ...,.
i s ·c: g_ ..
What is a Standard?
• Common and repeated use of rules, conditions, guidelines or characteristics for products or related processes and production methods, and related management systems practices.
• The definition of terms; classification of components; delineation of procedures; specification of dimensions, materials, performance, designs, or operations; measurement of quality and quantity in describing materials, processes, products, systems, services, or practices; test methods and sampling procedures; or descriptions of fit and measurements of size or strength. http://www.nist.gov/standardsgov/definestandards.cfm
Is it voluntary to adopt:
• Some cases it is, e.g. “adoption of IEC standards by any country, whether it is a member of the Commission or not, is entirely voluntary.” http://www.iec.ch/standardsdev/publications/is.htm
• TfNSW cases it is mandatory.
August 2015
ASA Charter Functions
August 2015
• Technical Capability
• AEO Obligations
• Transport Agency Obligations
The Asset Life Cycle
t nterprise Life C ycle Stages .__R_ .. _,._;,_,.,_,._,._n_ .. _v_,._1n_P'_'_""_" _' _,, __ P_r_o1_· e_.<_.t _D_~_. _•n_lt_io_n __
: ·~~ Dcvclopmcn~: · .. :... Producticn """ Ltilis~tion ""' R.cti1c•m_'f1t • • Syste m Life Cycle Stages ,_ __ E_,._P_lo_ro_to~ry.;....•_· __ ....... ___ c_o_n~cc-'_P_t ·- ·--
1
c..,,..bili!>· Fea•lbllty I s,. ,. m P hases
•• 1s 0-1 s2aa. S tages
Stak&holder& UWY• NwY:.lli
- - -
R~~i:::~ Stmli>'Js -<~.l~~~~~;~h-' P~~1:":.~.~r¥ g~~"-9~~ = ~:~,~~~~~ ';~~::.~~~:~~ 10~"';~!.t' '' & <.;v,",",'~~,.,. O J _·r ~1hon,.. & r11~,111 .c11..t r1L:W D~~::~~~~r
~\_.. ___ P_I ___ -&-'--~~,---o~ .. =,....,..=~•"""'Jc,,=:~•P'S=-~\ : 0 S t y ...O·d 1· ,...._,... ati & D• '; ~ ~,nng \\ & M etres Optinn~ ~ •. - ,:_ • - .. :..J'~ ~ .. ~ !~ ' ' ' ...,.......· ore :\ Uutr:,;;~it:-:lt \~ ~'\nql~~&Trqri""°ll. , - -- ·=- . • : ~ • - • ~ .. - i;h~~:~~~~~1~ ~1:1~~~:~ /:
r e H ibility G=udy • - .~tatn u_,, , • • '-------------H------' f : : :..t=riqirir..--ririq ' V' rr1tHt r-I r .f ...,.( \ ff'm "' I fr• c .. ( d t" k :
: : ' --, · ~ : / 0"V'!rf'lt1r.Fa Requirements ..._ :... ;;_;r;"':~, \ . :_ . _ . ~l~c~o~ ~~te~1 .. ...L ·• ':::. ... ~l S)"Bt&rn
Va lidation Arcrillietu re : : : : • Acce pt• nce
Oc~lsn ~ · • ~ ~ l ! . T-~·P • y:: enficat10n •• :: \. \ t'iy~~·•• \ : Veriftjation (Sys1Efm lnterfacej3) 7'/ ~~:~ /:
--:;.._ Ph . I w- . - ··- - - . ·- . - - - . I ""' . I : . r \ .o.«hr:,. \. ~ l ~ < &T~::0 / ~
n e:H;ign : : : : : • : v.-.r iric{'tii:u'l ' : Subt)'••m v ::irlficatlon (SLbsystem) LI: S dii)fa;tem 1.'h :
: · -+ I r.vr.1 .: - • - • :- • - • ' I Lo~~ ;//. : • • \ c..;gn \\' ' ' ' I ntegrotion I/I. ' ; '-' ' ;, 1, ¥, & Teatg ///_ ;,
Design
vr: rlfication l\. . ~ I Jnll I'"'' '\~\>. Vcrificatioi1 (Un it) I : .nff I ••• 1 /~ l ;: ~\ Daiign ~ " - ·:- • -r Toala /// , :
r . ':"~" i / tf :: l Bui I~ ""'ij"'i:::== = = = !..:. : ,,_ :
Varificatio::' , _ \ P""Oci..,..,..e,._t. r•~ca~.: =.t?7i ~:::, M a111.n:ictu111tg /@ C on 1truction/ ln t<i; l::tlli:.·i...n /.~
Life Cycle
Baseline Ex lorato Coneeot Build Vel1dation Retirement Stage Gateways P ry P1chm1nary Pes t Build Op'"'"'"!!
August 2015
AEO Guide to Engineering Management
I ··-·-
S T AKEHOLDER & USER
REQUIR EMENTS TRAOEASIUTY
Eleplora'!cty ba&EChe galeway -----------
V ertncatton of De&gn stage Ou-.put
I - ~ ,_ i ~ . 12 I!!:!
. TR.".O~IUTY_
- . - . - . --·111!11.lll!l!!•i~!!ll;lll;r=ll!t;"\lll!ll'!!l!'llllfll!ll ... _.,A. blulod . -~-.Fo-r-~-SEl-i:u_n_:U_OCI_"~ IDaSE!lne
1:::--E
D~te<a ( conngpratlon ) garewa'.)' Gm.'emance Cor.:rol Gat e
FABRICATION,. "As Bullt"
I(') ~ !! a: I Ill: I ::;; !!;! .·u
CONSTRUCTION & INSTALL.A TION
D05'1-0una ._ ___ a_a&e1_,._1_ne ___ _. tt.a&efln.e
I I ..,
·I
ll'SSPECT. TEST & COMMISSION
g.ateway
va1Jda-.Jon °' lrr:egra-IE<I sy.s~em
I I m
I
I
1- . J
I
CONF IG U RATION MANAGEM ENT
R E CORDS
August 2015
Elements
vs A
sset Lifecycle Rail Industry Control Systems Functions
I I I rain ConLrol Systems Ocsagn
Systcrn Arch1tc:cturc Design
I ram Conl rol Systems Constructilblltt-y Review
System Architecture Design
System Architecture
Chcck/Rcvi~ / Verification/ Approve
O<Jta Configll'ation Design
Dota Config .. ation Check I Review
Data Configll'atioo Design Verification
Data Configll'ation Design Approve
Systems Software Design
Systems Software Design Check/ Review
Systems Software Design Verification
Systems Software Design Approve
Infrastructure Ocsign
Infrastructure Ocsign Check / Rcvic.w
lnfrastruct.urc Ocsign Verification
Infrastructure Ocsign Approve
Verification and Validation Design
Verification and Validation
Check/Review/Verification/Approve
Concept Draft
System Architecture Design
System Architecture
Check/Revl.,.,/Verlflcatlon/Approve
Conflg.,.atlon Design
Conflg .. atlon Checker / Review
Conflg.,.atlon Design Vcrlflcotlon
Conflg.,.otlon Design Approve
Systems Software Design
Systems Software Design Ched< / Review
Systems Software Design Verification
SystcmsSoftwore Design Approve
lnrrasl rucLUrc Design
lnrrasl ruclurc Design Check / Rcvic.w
lnfrasl ructurc Design Vcrif1cauon
Infrastructure Design Approve
Verification and Validation Design
Verificct:ion and Validation
Check/Revlcw/Verlflcatlon/Approv"
Design Ornft
ConfigLration lnstalla.ion
Softw are Installation
lnfrasl ruclurc Installation
Control System Integration
§' it
l
i
Control System Integration f I Control System Valida:ion ..
Control Systems Commissioni~ !
Control System Malntalncnance
Control System Commissioning
i i
f
I
D D "" ~
h .... .. .... :;.
.. :i: ~ ~ ~
0 "' Q.
ii ,. i'i
Q. i5'
" " ~ "' Q.
g "
Q Q. s-Q "' "' :;.
,. "
2' :; " 8. 2' 0
" " :l "' i5' a
I \ ...
August 2015
Elements vs Asset Lifecycle - cont
• Elements 01: Establishes design assurance requirements • Elements 02: Establishes control systems documentation • Elements 03: Establishes infrastructure design and construction requirements • Elements 04: Develops a design and construction solution that meets project
requirements • Elements 05: Develops the installation work packages and test plans • Elements 06: Undertakes peer or independent review or both • Elements 07: Procures and tests infrastructure components • Elements 08: Approves • Elements 09: Establishes and prepares installation requirements • Elements 10: Maintains quality control during installation works • Elements 11: Installs and configures infrastructure components and parts • Elements 12: Decommissions and removes existing infrastructure • Elements 13: Completes post installation activities • Elements 14: Verifies installed infrastructure • Elements 15: Audits installed infrastructure
August 2015
Is this a Straitjacket ? Each AEO and Transport Agency (may not be AEO) may have different: • Authorisation scope • Engineering framework • Processes and procedures • Competency framework • Products • Services • Culture
An example: • Based on ASA asset lifecycle guideline, procurement happens before the
design. Design is based on the procured or existing product
• An AEO may do design first and procure the product to meet design parameters.
August 2015
Customisation & Flexibility Normally all requirements within the standard must be complied • If an AEO can not comply the requirement, must seek “concession” from
ASA before the design phase, which may be accepted or rejected or standard may be updated.
• If an AEO’s implementation does not fulfil the standard’s requirements, it is called “non-conformant” & treated accordingly.
But this particular case, ASA is giving power to tailor the standard as detailed in T MU CY 01000 GU TfNSW Competency Standards Guidelines and Glossary v1.0 as long as: • Customisation to the standards must be justified and will be auditable by
ASA
• Unacceptable to customise the evidence criteria against elements.
August 2015
Competency Jocelyn Edwards, Manager Competency Systems
August 2015
How does it all fit together?
Competency Guidelines and Glossary
Competency Pathways Standards
August 2015
Ongoing Work Plans
• The Standard and Guidelines - collaborative development
• Structure of the standards, definitions and how the
variables work. • Further work is underway in Control Systems,
Signalling and Electrical.
August 2015
TfNSW Competency Pathways – Control Systems
• Version 1 - Published July 2015
• Effective October 2015
• A Standard which sets the minimum generic requirements
• Developed as a collaboration project between ASA, Sydney Trains and TfNSW OD.
August 2015
The Standard
• Establishes pathways and generic competency requirements to perform functions within the control systems discipline.
• Provides additional information to an AEO for the
development of its auditable competency management system (CMS).
• Provides guidance to enable assessment of
personnel who are required to demonstrate competency.
August 2015
Pathways
New entrants
• This pathway will identify the pre-requisite qualifications and training requirements for those personnel with little to no experience
Skilled and Experienced
• Personnel wit h current or previous experience working on the TfNSW rail network • Demonstrate
domain or product knowledge
Transferable Skills
• Personnel who are able to demonstrate they have some of the skills and knowledge to carry functions • Includes personnel
with National or/or International experience
August 2015
Roles Vs Functions
• The competency standards describe the generic competencies that are relevant to functions or tasks.
• ASA has elected to specify functions that exist over the Asset life Cycle as opposed to Roles.
Design
Design Engineer
Check
Approve Verify
August 2015
August 2015
Standards - ASA business activities
Alignment to
international and professional
standards
• Overseas Frameworks (e.g. IRSE) • Washington Accord Agreement • Professional Bodies &
Institutes
Alignment to AQF (where possible)
• Developing National Competencies & UOC’s • Vocational Education & Higher
Education alignment • Accreditation
TfNSW Competency Standards, Guidelines and Glossary
August 2015
Where can I find the standards and guide?
Here’s where you find them… http://www.asa.transport.nsw.gov.au/
August 2015
Published July 2015 Effective October 2015
Morning Tea
Competency: detailed overview Jocelyn Edwards, Manager Competency Systems
August 2015
Structure of the competency standards
Functions: A specialty area of a role usually comprised of a collection of tasks
Elements: Describes the activities or tasks for which a function might be needed to be competent
Evidence Criteria: Assigned under Elements and expresses an expectation of what a competent person would do in terms of observable results and behaviours.
Standard Title: The discipline area covered by the Standard.
Variables: References the variables, located in the following section of the Standard, and relevant to the Evidence Criteria. The variables contained within each list guides the user to the relevant domain/ product knowledge or further specific items to be selected and used for assessment.
August 2015
Variable Examples
Flexibility o f the standards
Can be tailored to fit AEO organisation
Language can be revised but careful not to lose the essence
Elements can be discounted
However…
Must be justified and will be auditable by ASA
No customisation of evidence criteria against elements
August 2015
Applicable: Since Element 10 is applicable, then 10.1 and 10.2 are applicable.
Not Applicable because: (a) The AEO is not authorised for de-commissioning (b) Site is new and there is no existing infrastructure to be decommissioned therefore this Element might be deemed not applicable.
Additional Notes • The specific competency attributes that underpin expected
performance are embedded within the Elements and Evidence Criteria.
• These are expected behavioural and ‘soft skill’ attributes. They are
common core competencies such as: • the ability to communicate effectively, • the capacity to problem-solve, • risk adversity • accept responsibility and accountability.
• This allows the Competency Standards to serve as a measure of
expected performance against which actual performance can be assessed and evidenced by an AEO.
August 2015
Proficiency levels
AEOs shall define the proficiency levels. The following proficiency levels have been provided as guidance: • Level 1
– can perform the identified competency independently and without supervision in complex activities. Can produce quality outcomes based on the relevant standards and AEO’s process and procedures.
• Level 2
– can perform the identified competency for less complex activities without supervision or can perform the identified competency in complex activities under supervision or both. Can produce quality outcomes based on the relevant standards and AEO’s process and procedures.
August 2015
Customisation of the standards
August 2015
Practical Exercise
We will carry out an exercise to demonstrate the use of the Standard and look at how it can be integrated into the AEO’s competency management system.
August 2015
Assessment
“The process of collecting evidence and making judgment's on the nature and
extent of progress towards the performance requirements set out in a standard or a learning outcome, and, at
the appropriate point, making the judgment as to whether the competency
has been achieved." VEETAC 1993
August 2015
Evidence – Getting the Balance Right
Summative Making a judgment based on all evidences, where learning has ended and cumulative evidences allow the assessor to determine competency sufficient to award a competency outcome.
August 2015
Types of Evidence It is important that the evidence is: Current Authentic Relevant Sufficient
Direct evidence • e.g. observation from previous work, references from employers or clients
Indirect • e.g. written or oral questions evidence
Supplementary • E.g. reports, logbook, project plans evidence
August 2015
Example
Comments Elements Evidence criteria Appropriate evidence examples
Develops a quality design and construction solution that meets project requirements
Identifies, interprets and analyses the relevant design, industry and regulatory standards and design the infrastructure solutions to comply
• design reports or plans
• interviews
• log books
• references
Undertakes peer review or independent review or both
Provides constructive feedback to the designer, questioning and challenging decisions made
• meeting minutes
• design review comments registers
• reports of corrective actions
• reassessment engineer reports
• Existing for employees?
• Ease of access in HR/HRIS
• Currency
• Sufficiency
August 2015
Workshop Example
• Work in groups according to your seating
• Elect spokesperson
• Use sample assessment tool to determine appropriate evidence types against the Elements of Competency – Consider relevancy and sufficiency of evidence – Consider proficiency levels
• Please record evidence types on the provided flip charts.
August 2015
Sample Assessment Tool
August 2015
Customisation of the standards
August 2015
Activity Feedback & Discussion
• What were the challenges? Sufficiency of information Quality of information Currency of information
• Type of evidences
• Assessors Finding suitable assessors Checking quality of assessment
August 2015
Thank you!
August 2015
