Professional Development Program

CER Example Registry

October 2005
INTRODUCTION

A Career Episode Report (CER) is a documented component of your professional experience. It

indicates the attainment of experience related to relevant Elements of Competency as outlined in the
Chartered Status Applicants Handbook.

The significance of individual career episodes varies. A minor career episode may cover a relatively
short period of time (several months) and be advanced to claim some Elements of Competency. A
major career episode (a large or lengthy project for example) can be advanced to demonstrate an
entire Unit of Competency.

Each CER should emphasise problems identified and the problem solving techniques you utilised in
overcoming them. It should be prepared in narrative form, using the first person singular and should
describe the specific contributions you have made.

Reports should emphasise:

your personal contribution and responsibilities.
the problems you faced
the solution(s) you found.
the engineering judgments you made and
the impact your solution(s) and judgments generated.

This document is a compilation of CERs from a variety of engineering disciplines, industry sectors and
occupational categories. It is our intention to add new reports to this registry on a regular basis.

Please note that this document is for generic reference only. It is intended to give applicants for
Chartered Status an overview of the type and style of documentation required and is not to be used as
a mechanism of comparison or moderation against other reports.

Due to privacy considerations, consent has been obtained from the author of each individual CER. All
CERs in this document have been edited to ensure anonymity of people, places and names.

Career Episode Report Example Registry October 2005 2

CER INDEX

1 Title: Flare Knock Out Drum Level

Industry Keywords: Energy, Resources, Electrical, Instrumentation
Competency Elements Claimed: C2.2 , C2.5

2 Title: Fuel Oil to Distillate Conversion Engineering Study

Industry Keywords: Energy, Resources, Chemical, Process, Mechanical
Competency Elements Claimed: E4B1, E4B.2 , E4B.3 , E4B.4

3 Title: Project X
Industry Keywords: Structural, Civil, Construction, Building
Competency Elements Claimed: C2.3 , C2.5 , C2.4

4 Title: Low Frequency Analysing and Recording Program

Industry Keywords: Software, Electronics, Information Technology, Defence
Competency Elements Claimed: C2.1 , C2.3 , C2.4

5 Title: Working with Technical Change using CITRIX

Industry Keywords: Software, Information Technology, Defence
Competency Elements Claimed: E7.1, E7.2 , C3.6 , E7.3

6 Title: Root Cause Failure Analysis of JJ100 Crude Charge Pump Motor
Industry Keywords: Energy, Resources, Electrical, Instrumentation
Competency Elements Claimed: E4B.1 , E4B.2 , E4B.3 , E4B.4

CER Index: 1
Industry Keywords: Energy, Resources, Electrical, Instrumentation
Competency Elements Claimed: C2.2 , C2.5

Career Episode Title: Flare Knock Out Drum Level Competency

Element Claimed
Dates of Career Episode: 02/02/2004 08/08/2004
A Flare Knock Out drum is a vessel which exists immediately upstream of the flare.
The drum provides a volume and hence an amount of residence time to allow any
liquid that is carried over from the process into the flare system to be pumped away.
This prevents liquid from being sent up the flare, which once alight has the potential
to cause grass fires and dangers to personnel. High level alarming in the flare knock
out drum is particularly critical as it alerts the operations staff to the possibility of this
event occurring.

Significant corrosion on the standpipe nozzles as well as unrevealed failures of the C2.2 Prepares
discrete high level and low level switches (due to clogging of small 1/2" nozzles) concept
necessitated the investigation into reliable high and low level alarming. proposal and
seeks
From a mechanical point of view, I determined there was a requirement to simplify advice on latest
the instrument bridle arrangement to prevent corrosion and from an instrumentation technology
perspective there was a requirement to provide a means for more reliable
measurement. Problems with this service included varying composition and density.

The possibility of high H2S within the drum also makes cleaning of the nozzles
possibly dangerous to personnel, and is traditionally done using breathing
apparatus.

I identified that a significant increase in process connection/nozzle size to prevent

clogging and remove the above cleaning risks would be required. However,
replacing like for like even with larger nozzles would have the corrosion eventually
recur. The use of discrete switches of any variety would still mean that failures would

Career Episode Report Example Registry October 2005 3

 be unrevealed and so I did not consider the use of these further. Instead I proposed
the use of a continuous instrument having the alarms set at the control system to
mitigate this. I investigated the use of a differential pressure (DP) instrument and
also guided (contact) radar and horn (noncontact) radar. The wide changes in
density ruled out the DP transmitter.

The refinery had little experience with Level Radar on such a service, but I had
confidence that this technology would be most appropriate. The vendor advised that
guided radar would be preferable to noncontact due to better performance on
liquids with low dielectric values. I had concerns with any system that would have
contact with a possibly viscous and unforgiving medium and so I sought advice
from our Senior Instrument/Electrical engineer, and I discovered that the liquid
components with low dielectric (such as LPG) would most likely have flashed off at
this point, due to the temperature in the system. Based on this I proposed the
noncontact solution and would also use this opportunity to trial a vendor who was
not on our recommended vendor list.

Once I had considered all the options, and come up with design satisfying the
engineering problem I put this forward at a formal design review, where all
disciplines and operations staff are made aware of the motivation, alternatives and
proposed solutions.

Prior to the formal design review, I marked up a P+ID and had it drafted and put into
the system as a project P+ID. This allows the proposed changed to be captured C2.5 Prepares and
within the document management system and makes others aware of the proposed maintains
change (prior to its implementation). During the design review and subsequent documentation
alarm review I made changes to this project P+ID and ensured that these were during
drafted and captured in the system. the design process

As this design required commissioning of a new analog loop and demolition of two
existing digital loops the appropriate suite of documentation needed to be updated.
Appropriate I/O and cores were identified by myself and reserved. At this point, I
made markups to the loops and associated junction box drawings needing
demolition.

For the new analog loop, I created a new loop drawing based on a standard drawing
and marked up the appropriate junction box drawings. In addition, an instrument
data sheet and entry into hazardous area register were created. I then had these
drawings drafted, captured within the system and approved for construction. Once
this was done workpacks for the installation work were created by myself and issued
to the INLEC contractor.

During installation, a conflicting need for I/O from a different project required the
design to be altered to use a different analog input point. Although the changes were
minimal, I made the appropriate change to the drawings, had them drafted and
reissued the drawings and affected workpack jobcards to the INLEC contractor.
Once work and the punchlisting were completed, the project P and ID was merged
into the system as the current and approved P+ID.

During construction and commissioning as builts were created, and integrated into
the system during closeout phase of the project.

The modification was successfully commissioned has been working as described for
a number of months.

Signature of Candidate:
Candidates Verifiers Name:
Engineers Australia Membership Number:
I verify that the above narrative is a true account of the candidates own work
Signature of Verifier:

Career Episode Report Example Registry October 2005 4

Career Episode Report Example Registry October 2005 5
CER Index: 2
Industry Keywords: Energy, Resources, Chemical, Process, Mechanical
Competency Elements Claimed: E4B.1 , E4B.2 , E4B.3 , E4B.4

Career Episode Title: Competency

Fuel Oil to Distillate Conversion Engineering Study Element Claimed
Dates of Career Episode: 1/12/2004 30.04.2005

The fuel oil to distillate conversion engineering study was undertaken to provide a Introduction
scope of what infrastructure and plant equipment modification is required in order to
convert the backup fuel system at the Acme Alumina Refinery from fuel oil to
distillate. A senior engineer, Mr John Engineer and I worked together to complete
this study.

A project kick off meeting was held with the stakeholder where the projects brief and E4B.1 Responds
deliverables was issued. I discussed the exact requirements in detail with the to/ Identifies
stakeholders and agreed on the acceptance criteria for the study. Following the Problems
meeting, John and I conducted a stakeholders analysis to identify possible sources
of information to assist in the study.

Due to the size of the study, the tasks were divided between the two of us. For my
section, I mapped out all the items that need to be investigated and set a target date
for completion against each of the item. I examined each deliverables in detail and
listed sub-tasks for action. Following that, I made an estimate of the time and
resources required for each of the identified sub-tasks.

The fuel oil to distillate conversion requires modification to the Calciner and
Powerhouse Boilers Burner Management System as well as other instrumentation
and electrical modification. I wrote up a list of deliverables and made a request in
writing to the Lead Electrical Engineer for the assistance of an Electrical Engineer in
the study.

I scheduled a meeting every fortnight to review our progress and discuss any E4B.2 Plans the
issues. A progress update meeting with the stakeholders is conducted monthly to investigation
evaluate the projects progress and direction.

The Calciners had gas burners installed and swappable with fuel oil burners if
required, while the Powerhouse has only fuel oil burners installed with gas ignition
systems. Both the existing systems require an upgrade because it does not comply
with the current safety standards and it poses a risk to operators. I was involved in
seeking out prospective burner vendors that could deliver the requirements of the
stakeholders. The vendors selection process was done in conjunction with the
stakeholders. Preliminary engineering for the burner was done in collaboration by
the vendor and I. Several burner options with different configurations were proposed
to the stakeholders taking into account environmental emissions, costs, safety
equipment compatibility and operability.

For the tasks of upgrading fuel supply piping systems in the refinery, I analysed the
current situation and identify any improvements or modifications required to E4B.3 Carries out
accommodate the proposed distillate system. Bearing in mind that the fuel oil the investigation
system still needs to be in service while the conversion is taking place. To start off
the investigation, I compiled a list of P&ID for the fuel supply system and begun
marking any required modifications/demolitions. These drawings are then passed on
to John for estimation and isometric sketching. Following that, I created a detailed
piping demolition list and a modification list.

For operational security and insurance purposes, the existing fuel oil system has to
remain functioning and in service while the distillate conversion is taking place. I
identified several options for installation tie in and a temporary fuel supply system for
the Powerhouse and Calciner as a result of consultation with the stakeholders and
John. These options are costed and included into the report.

Career Episode Report Example Registry October 2005 6

 The logistics of fuel supply to the Refinery involves the analysis of current fuel
supply system available to the refinery and fuel supply to various facilities in the
refinery itself. I consulted the fuel supplier and the logistics department to find out
the current fuel consumption and supply method to the refinery. Based on the
distillate consumption of the new burners given by vendor data, the estimated
monthly distillate requirements is determined. Because the new distillate
requirement is much higher due to the elimination of fuel oil. I researched and
proposed the option of increase distillate trucking frequency or supplying distillate by
rail. The stakeholders prefer the former option as the current rail logistics is fully
dedicated to alumina transfer to the Bunbury Port and could not accommodate
distillate transfer. Moreover, additional infrastructure has to be installed to facilitate
the rail transfer option.

On the bulk fuel storage tanks modification, I referred to the relevant Australian
Standards. I listed all the improvements required to make the bulk storage area
compatible to the current Standards. I then conducted some preliminary design for
improving the area and obtain budget costing from onsite contractors.

Once the scope of the project is finalised and John and I packaged our individual E4B.4 Draws
sections into various discipline work packs for ease of detail design and Conclusion and
construction. I compiled the project cost estimate (+/- 35%) and completed cash flow makes
forecast, taking into consideration of inflation, price increase of components, wage recommendation.
increases. These estimates were later reviewed by in-house estimators.

The report writing process began roughly halfway through the investigation phase. I
first began filling the report with information and results from my investigations and
research. Later, the report was consolidated with findings from John. The burner
conversion proposals from BurnConvert Pty Ltd and ABC-Combustion Pty Ltd were
also consolidated into the report. I spent the last few weeks of the study reviewing
and refining the report with assistance from John. The report was also sent to the
stakeholders for review and to ensure that all the deliverables are met.

The findings from the study were presented to the stakeholders and other refinery
representatives. Recommendations arising from the study and their justification
were made known to the stakeholders. This study has provided the stakeholders
with an idea of the cost of converting from fuel oil to distillate. The results of this
study concludes that the proposed fuel oil to distillate conversion should be
progressed into the feasibility stage, but more emphasis shall be placed on the
Commercial and Risk Mitigation Strategy by the Refinerys upper management.

After the presentation, the report is finalised and circulated to the stakeholders for
their signature.

Signature of Candidate:
Candidates Verifiers Name:
Engineers Australia Membership Number:
I verify that the above narrative is a true account of the candidates own work
Signature of Verifier:

Career Episode Report Example Registry October 2005 7

CER Index: 3
Industry Keywords: Structural, Civil, Construction, Building
Competency Elements Claimed: C2.3 , C2.5 , C2.4

Career Episode Title: Project X Competency

Element Claimed
Dates of Career Episode 16/02/04 07/10/04

This project consisted of the construction of a new medium-rise building in Sydney.

Our office was commissioned by the head office to complete several complicated
elements of the structure. My role in this project was to complete the majority of the
detailed design of the complex suspended ground floor slab.

After being briefed on the project by the chief project engineer, my first task was to
break down the entire floor system into an ordered set of discrete designable C2.3 Implements
elements such as slabs, bands and transfer beams. Next I used the RAPT computer Planning and
program to carry out the detailed design of each of the forty or so elements. This Design Process
involved measuring the span, dimensions and loading on each element and entering
this data to model it in the program. My aim was to make the models as accurate as
practicable, while still leaving some chance to incorporate any future changes. After
re-assessing the specified design criteria, I realised that the reinforcement cover I
had used did not satisfy fire resistance and durability requirements. Luckily, because
each design element was already set up as a computer model, it was simple enough
to change the covers and make the necessary design modifications. To ensure the
clarity of the design to others, I documented and ordered the calculations and
computer output in a lever arch file, including summary pages and assumptions
used.

Throughout the design process, it was my responsibility to produce, order and

maintain all the design documentation including computations and reinforcement C2.5 Prepares and
drawings. I arranged the calculations, numbering approximately 1000 pages, based Maintains
on the site grid system. The RAPT output for each element designed was sorted in Documentation
this system, with summary pages of input and conclusions provided for each. I Through the
clearly outlined content pages and the design concepts and philosophies at the front Design Process
of the documentation, while also including sections for superseded computations
and verification documentation.

It was also my task to draw up and update the reinforcement drawings. I produced a
sample markup which was checked by the chief project engineer and the clients to
ensure an acceptable format for the rest of the drawings. After we issued this
sample markup, the chief project engineer went on several weeks holiday, which left
me with the task of managing the timing and production of the rest of these
drawings, with minimal supervision from the department manager. Using the original
design computations as my basis, I drew up all the detailed reinforcement plans.
This approach allowed me to check and verify the comps as I went, and update the
drawings accordingly. Altered drawings were revised and re-issued as a next
revision, in many cases with copies of relevant calculations to show reasoning.
During this time the rest of my workload was light so, apart from one or two difficult
areas, I took the chance to push the drawings ahead and have the first revisions
largely ready before time. Whilst in the middle of this process, the client advised us
that the pile capping drawings needed to be issued earlier than anticipated, so I
diverted more of my time and resources to this task in order to get the drawings and
documentation ready for the deadline. The key documentation met this deadline,
with supporting section drawings being delivered a few days later.

The client was concerned about the deflection under load of the suspended ground
floor slab. I discussed my computer model results with the client and demonstrated C2.4 Reviews the
that the design case deflections were acceptable. I also showed that changing the Design to Achieve
design to provide less deflection would significantly increase construction costs. Acceptance
Another engineer completed an independent verification of the ground floor
structure. I then went through and addressed all the issues raised, making changes
where necessary. The head office also reviewed and directed many queries to our
chief project engineer. I was then given the task of reviewing and addressing many

Career Episode Report Example Registry October 2005 8

 of these issues and providing responses. The reviewed design was provided to the
client who advised that the design brief had been met.

By coincidence, a couple of months later I was on holiday in Sydney. I used this

opportunity to contact the head office and organise a site visit with one of their
engineers. At the time they were constructing the basement and foundations, so not
much of my design had been built yet. However the experience was still very
valuable to see the site and discuss my designs with the site engineer to unearth
any problems and ways he believed things could have been done better.

Signature of Candidate:
Candidates Verifiers Name:
Engineers Australia Membership Number:
I verify that the above narrative is a true account of the candidates own work
Signature of Verifier:

Career Episode Report Example Registry October 2005 9

CER Index: 4
Industry Keywords: Software, Electronics, Information Technology, Defence
Competency Elements Claimed: C2.1 , C2.3 , C2.4

Career Episode Title: Low Frequency Analysing and Recording Program Competency
Dates of Career Episode: 01/09/2003 - 05/03/2004 Element Claimed

The project consisted of upgrading the Low Frequency Analysing and Recording [Introduction]
(LOFAR) display program, currently used for underwater sound analysis. It was my
core responsibility to design a spectral analysis program for filtering the beam
spectral plots of passive signals received from the hydrophones. I was also required
to design an interface to display the spectral content of the received signals in time,
frequency and intensity (in decibels).

After seeing the old LOFAR program and talking to the users, I deduced that the
requirements were to design a real-time data analysing program with a friendly C2.1 Interprets and
Graphical User Interface (GUI). This requires using an improved data acquisition scopes design
process and thus new data acquisition cards were necessary. I then optimised minor requirements
features of the software program needed for the new software program to be
considered an upgrade. They are: to have selectable baseband frequencies;
continuously updating date and time display; print current screen function and also a
'smart-cursor' to read the current details on the graph.

The client outlined, via the main user, that desirable extra features of the program
would be: to have a save picture to file option (also showing the particular file
name), title and time of the display and a function to be able to set the time.

Initially, I developed a simple prototype program that would take external data and
display it on a time, frequency and intensity graph. I then determined the software C2.3 Implements
code for displaying the date the program was opened and then the code to planning and
continuously update the time every second. With the help of my supervisor, we design
developed the smart-mouse which contained code to display the frequency, time process
and dB co-ordinates on a mouse click. I then worked on the other requirements, one
by one until the complete software program represented what the user needed.

This preliminary software described above, was then installed in the system
containing the upgraded data acquisition cards. During testing stage, the software
program was vigorously tested. At this point, the program generated a number of C2.4 Reviews the
significant errors. For example, the DAQ had an auto memory which caused the design to achieve
program to crash every several hours; and the save option caused some trouble as acceptance
it automatically saved the screen into MATLAB format and not as pictures (.jpeg
or .gif). I investigated code for storing picture format profiles automatically and
remembering that MATLAB stores every information. I gave recommendations that
perhaps we should find code that would clean the programs memory at set intervals.
The software program was then vastly upgraded with these significant
improvements and then installed in the system containing the hydrophones. The
users then critically reviewed the whole system and suggested improvements to the
user friendliness, such as a changeable bandwidth and to fix the auto print button
(so that it prints landscape instead of portrait). Once I made the modifications the
system was accepted.

The described software engineered system above started with defining the
capability needed in the requirements phase, then the planning and minor tests
needed in the design stage and finally the design reviews, installation and system [Conclusion]
acceptance. This project was a success. The project was on-time, on-budget and
the software program reflected exactly what the user desired to do their job correctly
and professionally.

Signature of Candidate:
Candidates Verifiers Name:
Engineers Australia Membership Number:
I verify that the above narrative is a true account of the candidates own work
Signature of Verifier:

Career Episode Report Example Registry October 2005 10

CER Index: 5
Industry Keywords: Software, Information Technology, Defence
Competency Elements Claimed: E7.1, E7.2 , C3.6 , E7.3

Career Episode Title: Working with Technical Change using CITRIX Competency
Element Claimed
Dates of Career Episode: 08/03/2004 - 31/08/2004

My engineering rotation required planning, researching, implementing, managing [Introduction]

and recommending improvements in implementing technical change. Technical
change described in this Career Episode Report (CER), details a software system
called CITRIX and thin-client hardware. The CITRIX system provided remote access
to individual desktop computers, regardless of the operating system. Thin-client
computers use remote terminals to access information from a server to save local
memory space.

I participated in the planning stage of re-developing the test laboratory. The

laboratory has size restrictions, given the growing number of computers required in E7.1 Participates in
the laboratory. I participated in the planning process by providing ideas and planning the
researched to introduce technical changes to the laboratory. We then identified introduction of
possible opportunities available for the laboratory and it was my job to design the technical change
layout of the 'new and improved' laboratory with the new technology. The planning
stage also covered talking with personnel nearby about introducing technical change
to improve working in the area and the business objective.

Following on from the planning process, I researched possible design concepts to

include supportability, sustainability and interoperability. This investigation and E7.2 Develops
analysis covered several design options and concepts. Focusing on the design technically creative
requirements, I discovered an innovative solution incorporating open-systems and flexible
engineering (compatible for many types of computers) and the latest technology. On approaches and
advice from my engineering supervisor, technicians and other Engineers, I prepared solutions
a concept proposal covering a possible design solution with the use of a new
software program called CITRIX. CITRIX could be run with thin-client technology.
Collaboration with the manufacturer of the Citrix software allowed me to download a
sample program to test the functionality. Discussions with clients of the company in
Defence allowed me to overcome set-up and technical hurdles. After planning the
introduction of technical change, investigating and analysing possible design
concepts, CITRIX and thin-clients were chosen as the design outcome.

Once the technical analysis and design was implemented, the concept proposal
required managing. Management of this proposal required me to locate other
technical reviews (eg. papers) of CITRIX and the new equipment. On reviewing the C3.6 Manages
relevant information, I had to pinpoint the Internet/computing standards addressed Information
by the new technology and ensure the new concept abides by Defence standards
and processes. Furthermore, given that I had to download a trial version of the
CITRIX software, I then had to manage the transition to a full commercial license
version. Documentation of the design process, testing and outcomes were complied
into a report for the section. After the section had read the report, the information
and outcomes were analysed by all stakeholders to conclude with the permanent
installation of CITRIX with new technology.

The implementation described above shows how the laboratory and those working
in the area responded to changing technical needs of the section. These technical
changes are driven by the needs of the customer and re-enforced by the demand E7.3 Manages
through stakeholders. Throughout this technical change, we kept the section, emerging technical
stakeholders and the customers informed of the progress in the implementation of challenges and
change. We also recommended technical improvements for improving change in the opportunities
laboratory to the Project Manager. For example, we suggested that planning for
continuous, long-term incremental changes would help the personnel in the
laboratory cope with increases in their workload. Additionally, we pointed out that
changes can be time consuming to implement and this should be factored into the

Career Episode Report Example Registry October 2005 11

 timeline.

CER Index: 6
Industry Keywords: Energy, Resources, Electrical, Instrumentation
Competency Elements Claimed: E4B.2 , E4B.3 , E4B.4

Career Episode Title: Competency

Root Cause Failure Analysis of JJ100 Crude Charge Pump Motor Element Claimed

Dates of Career Episode: 10/04/2004 29/06/2004

Five crude charge pumps with electric drivers supply feed to Koalas Refinery's [Introduction]
Crude Distillation Units (CDU 1 and CDU 2). JJ100 is typically used to exclusively
feed CDU2.

Two successive bearing failures on JJ100, the second a week after repair, resulted E4B.1 Responds
in catastrophic winding damage and motivated the need to perform a Root Cause to/ Identifies
Failure Analysis (RCFA). I was involved intimately in managing the whole RCFA Problems
process.

A multidisciplinary RFCA team was assembled and led by our onsite RCFA expert.
This included representatives from onsite maintenance teams and the motor
repairer. During this session, an ordered approach was used to locate every
possible cause of failure.

Minutes from the RCFA were documented, and the actions were allocated to the
appropriate disciplines and parties including (Rotating Machinery Team, Motor
Repairer, Motor Manufacturer, Electrical Maintenance Technicians, Electrical Dept,
Operations). I was allocated the responsibility of planning the majority of the
investigation tasks (and also monitoring the progress and managing the completion
of the other parties actions.)

Given the previous catastrophic failure it was agreed between myself, the rotating
equipment department and operations that the root cause analysis process and
reporting would have to be completed prior to recommissioning of the motor. This
step would be essential in planning the tasks.

To begin, a skeleton plan for each task was created and I identified the most time
intensive tasks (i.e. communication with manufacturer in Finland), as well as the E4B.2 Plans the
tasks that needed to be coordinated with the various stages of repair. At this stage investigation
various parties, particularly the motor repairer were involved closely to ensure that
both the schedules of the analysis and the repair would not clash.
From this point, I was able to set deadlines for the completion of actions, which I
communicated to the various parties.

For each of the skeleton plans, both myself and the Rotating Machinery Engineer
devised the proposed testing regimes and equipment that would be required. At this
point, since mechanical clearances and their measurement predominated, I became
familiar with the mechanical arrangement of the motor and also in the use of dial
gauges to determine clearance measurements.

In some cases I devised methods in which unobtainable clearance measurements

were made inferentially. Many of the skeleton plans required additional research (for
instance I investigated bearing failures modes and lubrication extensively) in order
to be able to make judgment on such root causes.

Additionally particular consideration was given to the capabilities and availability of

the onsite technicians (particularly since the refinery was in a scheduled
maintenance shutdown at the time). This was achieved by close involvement with
the electrical and mechanical forepersons.

In many cases during the process, the proposed investigations did not yield the E4B.3 Carries out

Career Episode Report Example Registry October 2005 12

 required information, and as such I refined the procedures and had the individual the
investigations redone until the required result was achieved. investigation

For many of the individual investigations, particularly in the case of the Variable
Speed Drive, extreme care was taken to ensure that the safety risks and dangers
were communicated and mitigated. To do this I produced detailed test
procedures/workpacks.

During the process I made myself available to witness particular activities in order to
ensure that a level of independent assurance that the correct information was being
discovered.

When all the tasks in the investigation were complete, I revisited each root cause
item separately, and was able to identify as a first pass which items were not
contributing causes to the failure.

For each the contributing causes, each of these was considered in detail for the
severity of the contribution of the failure and ranked. In this particular case, axial
clearance issues due to an incorrect initial repair proved to rank much higher than
the other causes. This was deemed to be the root cause of the failure. Contributing
causes however were not dismissed.

From this analysis, I wrote a summary report detailing the investigation, root and
contributing causes and proposed a number of recommendations to prevent such a E4B.4 Draws
failure from occurring in the future. Prior to issuing this report internally and conclusions and
externally, I sought feedback from the original RCFA team. From this it was makes
determined that although I had captured the root cause sufficiently, I had not recommendations
communicated the importance of some of the contributing causes the report was
then amended and reissued.

Recommendations from the report were then enacted on for both the installation and
recommissioning of the motor. In addition to this, witnessing of various stages of
the repair of the motor allowed me to be confident that the root cause of failure
would not be present in this repair.

Close monitoring of winding temperatures was done by myself for the first week of
operation, and when they were deemed to be within an acceptable range for the
entire week, the motor was handed back to operations.

The motor has been working without issue for the past 8 months.

Signature of Candidate:
Candidates Verifiers Name:
Engineers Australia Membership Number:
I verify that the above narrative is a true account of the candidates own work
Signature of Verifier:

Career Episode Report Example Registry October 2005 13