Just requirements? You’d reply.
Another pause. ‘Yeah, I think so’ they’d answer.
You’d then faceplant your desk that a discipline so immense
and varied was summarised by just one word.
Thus sets the stage for the graduate systems engineering
course that took place at the start of May. Created by the Systems Integration
team at UKAEA, including our own resident graduate systems engineer Jess, the
course set out to answer the questions the graduates didn’t even know they had.
WHAT is systems engineering? WHY is systems engineering? WHOM is systems
engineering??
A cloud of intrigue and rumours had surrounded the course
from day one: why did Jess keep stockpiling lego on her desk? Why was she
asking for strange objects from all at RACE? The plot ever thickened as May 10th
grew closer, and 23 grads anxious to know what lay in store, gathered together
early in the morning to see the secrets revealed….
The graduates got stuck in straight away to a seemingly
harmless activity. Their task was to design and build a remotely operated
vehicle capable of rescuing people from a flooded village and delivering aid
supplies. All well and good; the teams ploughed on with their designs and had
finished products ready to show to visiting stakeholders when they arrived.
They approached the front with trepidation and lay their designs before them.
The tension in the room built. The stakeholders at long last shared a look,
turned to the teams and spoke.
‘Not impressed.’
What? How had this happened? The teams had followed the
instructions, completed their vehicles on time, had reasonable justifiable
designs. A debrief between teams and reflection on the comments from the
stakeholders revealed all the points the teams had missed in the design of
their vehicle. What about this? What about that? This project was more complex
than had first appeared, and the mornings approach just had not worked to
capture everything that the vehicle needed to do.
‘Teams hard at work in
the morning session’
A Systems Engineering lecture and lunchtime later, the grads
returned for take two. They would have to complete the same task as the
morning, only this time using systems engineering processes and practice. There
was a project schedule for the afternoon, with planned reviews at strategic
points in development, and document templates to complete, based off those that
are used in industry.
The groups started at the requirement definition phase and
sat down with the stakeholders to collect information on what they were looking
for in vehicle designs. They then worked together to turn these needs into
requirements, and to think about the wider context surrounding their vehicle.
They submitted a systems requirement document of their work so far, and then
onto the next phase!
The teams then entered the designing phases and worked to
use their requirements to design a new vehicle. They considered how their
vehicle would operate in the environment and how they would test their finished
design to ensure it met each of their requirements. The next two reviews passed
by in a blur and the teams were left with their finished designs and a stack of
work showing their use of systems engineering techniques to reach them. The
vehicles could take more passengers, could face (almost) any challenge thrown
at them, and crucially were what our customers were looking for.
‘Taking things very
seriously in the afternoon’
The vehicles were then taken over to the RACE aviary to be
tested. There, the vehicles were put through their paces in a race to save as
many people as possible. The hovercraft seemed to be quite zippy, and despite
some initial sticking problems managed to navigate the course. The drone design
on the other hand had some more mishaps, and attempted escape from the aviary
on several occasions.
After testing, with the grads heads all full of new
knowledge, the day drew to a close and the Remote Applications in Climate
Emergencies team was crowned the winner of the rescue challenge. The grads, now
equipped with more than just requirements in their systems engineering toolbox,
were released back into the world to go and change engineering projects for the
better.
‘Testing a hovercraft’
The feedback from this pilot was great, and the course will
potentially be rolled out across site in the future. Thanks to all the
graduates for being willing guinea pigs and to all those who had a hand in
making it happen.
Some thoughts on the day from the graduates:
‘At first glance it may have seemed a jovial day of friendly
chatting and playing with unspecified non-trademark children's construction
toys, but the day quickly took a harsh turn as the customers expressed their
/severe/ displeasure at the wonderful rescue machines we had crafted, which
sadly did not meet their requirements. Shocking and painful stuff, though
admittedly the construction and effectiveness of the early prototypes left
something to be desired. Truly this was a trial by fire, and we would need to
fully grasp the systems approach to put it out; if the interactive and fun
exercise, clear workbooks, helpful facilitators and step-by-step walk through
the entire systems engineering process wouldn't improve our chances at a
successful solution, then the threat of another childhood-destroying
evisceration of our beautiful models surely would.’ – Gareth ‘Is it Real Engineering
Though’ Hawkes
‘I'm pretty sure someone said 'Hannah is the best project
manager'.’ – Hannah ‘Can the Real Most Active Grad Please Stand up’ Todd
While the systems content was excellent, the biggest
takeaway may be that unless Mike is in charge of driving those trapped in the
floods are probably better off swimming.’ -
Jonathon ‘Needs More Dungeons and Dragons’ Witty
No comments:
Post a Comment