BLOG

On this page there are articles, presentations, news items and random thoughts by me about aspects of Systems Engineering.  It is divided into three sections, which represent the three different books I am hoping to write representing different perspectives on Systems Engineering

  1. Everything is a System
  2. The Practical Practice of Systems Engineering
  3. People Make Systems

1. Everything is a System

This section is about looking at anything (transport systems, aircraft, cities …) through the lens of systems - to show the generic system properties that explain how they work 'as a whole'. I know (as a nod to the systems thinking scientists) that everything isn’t a system, and even the definition of what is a system is a mental construct in the eye of the beholder. The theme of the book is everything, or anything, can be thought of as if it were a system; and often this provides useful or interesting insights
having some problems – so this is a quick test
I attended the INCOSE International Symposium in Ottawa (symposium dates 26th July – 31 July 2025). as a bit of fun I started to list the “systems” I felt involved in my visit. I admit to being inconsistent in my separation of specific things, but without trying too hard I found 37 separate things that can be thought of as a system, and were engineered by someone
This is a paper I wrote for INCOSE IS 2024 (in Dublin). The attachment is an adaptation of the paper presentation that I gave at the CAG Syntell Summer School in August 202 this title. The paper can be found in the INCOSE IS 2025 proceedings (and I may add to this blog later). The basic premise of the paper is seeing the “systems” issues in the Panama Canal, – but there are aspects that fit into the other categories in this blog: a) there is the practical practice issue of ensuring the realisation systems for your system are considered and prepared b) there are a lot of people / leadership issues in the Panama canal history (both good and bad) Anyway, I think that the history of the Panama canal makes an interesting systems canal. If this wets your appetite I thoroughly recommend the David McCullough book “The Path Between the Seas” which was the inspiration (it is pure history without the “systems lessons”) for the paper

2. The Prgamatic Practice of (Systems) Engineering

This represents my reflections and take on how Systems Engineering can be done in order to produce useful results - recognising Systems Engineering isn’t done for its own sake, but to increase the chance of producing / updating systems so that they work! Title changed to pragamatic (pratical and practice seemed to close).  And maybe pragmatism is the closest "philosphical" concept underpinning this (I did at one point contemplate a "Philosphy of Engineering", but I really am not any sort of philospher!)
based on what a vigoorous disucsison at INCOSE IS 25 I needed to re-consider this question and out of that thinking came this post Understanding the source and role of thrust in an aircraft requires a systems engineering perspective that considers the entie aircraft as a syste rather than isolated parts. I found this issue illustrates the complexity of defining requirements and the interplay between sub-systems as you engineer an overall aircraft. [Note – this also prompts thoughts about “holons” but that will be for another post!]
I was asked to give a presentation at EURO25 (European Operational Research conference, held in Leeds in June 2025). This is my presentation (photo of C-17 Hangar added morning of presentation as it fits and illustrates a key point (regardless of whether this was response to late discovered issue or . This is (insurprisingly) close to the basic structure of the book I am planning on the “Pragmatic Practice of (Systems) Engineering). unfortunately I have to put this up in pdf, which doesn’t allow the build on the requirements decomposition or the capability chessboard to be shown. I will add those step by step later!
it is commonly stated (assumed!) that making assumptions is a bad thing. In this post I argue that is not true – assumptions are vital to move forward. The danger is no realising you have made assujmption, and not doing actions to make timely validation of the assumption – and iterating around as the assumption is matured / updated with “true” value
the idea of the Requirements Sandwich comes (for me) from a paper by Jeremy Dick in 2004. I really like the concept, but consider that the requirements are not the “bread” in the sandwich, but the “filling” – and the requirement come from the environemtn / solution about. So whilst in a Systems Engineering process we start and end with requireemnts, in reality the system requirements start / derive from the real world and end as an element in the real world. so in my re-evaluation of the requirements sandwich a) the requirements are the “filling” – defining the next layer of “bread” b) the “bread” is either the real world, or the architecture / analysis / modelling of the relevant system layer Either way a key point is requirements for one layer trace to the solution the layer above not the requirements for the layer above
Information during system development is regularly updated / changed during system development, and there needs to be appropriate management. This post describes the data model (for any system element) that I recommend. Later posts will go into more detail about each data type, the connections between the data types, and the connections between system elements.
This is an article prompted by some material I read on Brainstorming. This technique is very much part of the practice of Systems Engineering, so it fits in this section. There is awful an amount of discussion on behaviours and making sure all get to contribute, so there is ‘people’ stuff in this as well.

3. People Make Systems

This area looks at the 'soft skills' and organization principles need to enable individual, teams and enterprises to effectively do and engage with Systems Engineering. To my mind this is the most important, and most challenging part of doing Systems Engineering.
This is an initial set of thoughts about the important aspect of how individuals professionally develop, starting with being honest and open about their weaknesses and shortcomings rather than just emphasing their strengths. I expect there will be a lot more to come in this arera. Edited mostly to correct typos and clarify a little June 2025

4. Other

This is an area for other material that doesn’t fit into any of the sections above.
Not really posting this in terms of it being a system (although of course it is) – but just celebrating the Gromit Unleashed 3 (2025) trail in and around Bristol and having photographed them all. The trail (for those that don’t know) is primarily fundraing for the Bristol Children’s Hospital Charity “The Grand Appeal”, and is based on the Aardman Animation characters from the Wallace and Gromit – specially decorated by a range of artists and sponsored and located around Bristol. This year there were 53 sculptures. As well as supporting the charity, it promotes local businesses, encourages a look around Bristol (including to places you might not have been) and is just good clean fun