Architecting increasing technical capabilities across RRDQ&O implementing such as a D-FMEA SAAS tool suite to all new projects. Managed the technical assessments of all projects as part of project governance.

Initially brought into Dyson Automotive to bring systems engineering management to this complex and ambitious project. Then once moved to the home businesses tasked with leading a ‘New Category’ product using a multidisciplinary team on a significantly challenging project, including robotics and machine learning in a highly regulated market domain.

Created and deployed the systems engineering strategy and technology roadmaps for end to end systems engineering within JLR. Aim was to migrate all users from various lesser controlled and coordinated systems engineering and ALM environments to a cohesive IBM DNG, RTC, RQM and Rhapsody based system. Considerable verifiable progress made.Led the DevOps team for RMDV², the design and verification management system for the vehicle delivery process employed by over 8500 users. Managed standards, regulations, feature reflections and the authority to test for all teams. Owned all requirements authoring and management systems.Designed and rolled out the design information model to meet the company’s priority of efficiently managing the increased design complexity resulting from the creation of autonomous driving and feature-oriented systems.

Redeployed to support critical activities to architect the future of High Voltage Battery Control Systems for all the MLA platform implementations. In this role I am reverse engineering the multiple disparate PHEV and BEV HV Battery technologies into a singular functional architecture. I am doing this to allow applications to the greatly increasing number of future variants without the headcount increase applied to previous projects.

With the successes of improving the EMS processes I took on the challenge to deploy systems engineering improvements to the wider audience of all of PowerTrain. Working with the software quality team I developed the Functional Layer teams to deploy systems engineering into Core Engines development. Working with the ASPICE team and criteria the following documentation of what I believe is an excellent documentation of coherent processes including SIPOCs and RASICs that exists in JLR was documented to support these new teams.https://sites.google.com/jaguarlandrover.com/function-layerWith the JLR Standard for Requirements Quality published I coded this into a standalone Requirements Checker tool. This tool allows requirements to be assessed programmatically against a compressive list of criteria that requires should comply to and informs the user if they meet them or not. This tool has been added to standard processes across JLR and is planned to be integrated into DOORS for all areas.To support the commonisation across PT I established the company wide working group representing the core engineering departments with key involvement with the ADAS and Chassis teams. In this forum we have worked to solve shared common challenges and developed improved tactics for persuasion to adopt the improved working practises. From this group we now have common requirement templates, naming conventions, content authoring tools and hierarchy that all CoCs are now working towards in the SSCD and the Technology Projects areas.I have also supported the Bosch - JLR workshops where we have used the time to align how JLR communicates with our biggest software supplier. With them we have developed the Requirements Exchange Process to support effective communication. I have also taken this process and mechanised, with the Engineering Strategy & Transformation team, it into a proposed formal service level process to greatly simplify and improve our tracking of supplier agreements.

As an evolution of my first role within JLR I recognised a key gap in capability that we needed to support improved verification within JLR. So I formed a small team to develop and code a complete end-2-end Data Acquisition and collection and Processing System called DAPS. This was the first data mining capability for bulk network data in JLR and proved vital in the delivery of the hybrid-electric vehicle programmes, with over 1.5 million miles worth of useful data collected and processed. At the end of this role I developed this system into a more widely recognised and supported commercial tool-set, Diadem.

In my initial role within JLR I was tasked with developing the vehicle and system level verification strategy for the first JLR hybrid-electric cars, the Range Rover and Range Rover Sport. This included developing and deploying the test methodology, authoring and reviewing of all the test cases. I performed a high number of these tests to gain significant coverage of the hybrid software and system, in the most complex commercially available vehicle of the time.