With the resurgence of systems engineering in full swing, Guy Johns, Lead Technologist at CFMS, explores the promise of web technologies
The emergence of new complex products requires innovation and collaboration, not to mention the requirement to deliver traceability and validation across an increasing supply chain. This creates a number of challenges, and through the use of modern IT architecture, the vision of systems engineering is to close this gap.
The discipline of systems engineering has been in existence for more than a decade, and whilst its techniques and methodologies have certainly evolved over the years, it has failed to keep pace with the level of changes that have taken place within IT during that time. These changes centre on the somewhat significant shift in how systems are deployed, set-up and, critically, how they scale. That last point – one of scale – leads us to the discussion of web technologies and the subsequent move from desktop applications and into private cloud-based applications.
Many of the vendors responsible for driving system engineering forward five years ago remain focused on that same desktop architecture, signalling to the industry that they are hesitant to embrace the idea that compute and storage can be scaled up on demand – an idea presented by web technologies. Within that domain, Google and the Microsoft Azure platform have had a dramatic impact on the technologies being used by companies like Netflix, while Oracle has influenced business trends by encouraging migration to its cloud infrastructure. Having taken note of this, there is a real momentum gathering in the modelling and engineering industry and it’s one that is simply impossible to ignore.
When we acknowledge the need for larger, scalable and more collaborative teams to address our complicated systems engineering tasks, we find ourselves turning to a potential solution like web technologies. The sheer scalability afforded by the web seems to make it an obvious choice, but is it a choice that is truly resonating within the industry? One of the barriers to the use of web technologies is the skills base, as many of the skills in web development and design have been developed around the media piece – specifically the streaming of certain services.
Systems engineering is a difficult discipline to begin with because it covers several domains like data modelling, engineering and product design, and so should we be asking systems engineers to develop these tools or should we bring in the experts from the web domain to provide us with understanding of those use cases? Essentially, the question is whether we can look at a sector with massive scale and evaluate the approaches and methods they’re using and then apply those same techniques to our industry. At CFMS we believe that we can, but making that knowledge and skillset digestible for a sector as notoriously risk adverse as engineering is a challenge. If we are able to achieve that, however, there’s the opportunity to engage in a radical rethink of the design space – as long as we have the tools, techniques and compute readily available to us.
Another element to consider, however, is the scalability of the methodology itself. In a previous whitepaper entitled A through-lifecycle approach to system engineering I explored the potential of systems engineering to capture data and use it to inform the next conceptual design, but there are certain hurdles that need to be overcome when dealing with large teams. A system will often be broken up into logical pieces that are then assigned to the relevant smaller teams, and so if 100 system engineers are working on one project, there would need to be 100 distinct pieces in order for work to take place concurrently on that system. Cross-discipline design optimisation in the system engineering piece often presents problems as we have a system-wide thinking approach that states the whole is more than the sum of its parts. But, by structurally splitting up a system we’re unable to conduct whole-system optimisations and this is where we step into unknown territory.
CFMS is taking traditional systems engineering tools and exploring what happens when we have a conceptual design systems model that we then roll forward to a maintenance model, and then we bring in another product which is a derivative. The question is whether we can reuse some of that previous work or if we are dealing with a new model – where do these whole lifecycle approaches join up from a methods and tools perspective? Every new design undoubtedly includes lessons learned, but they often come from the personal experience of the design engineer rather than being carried forward by the methods and tools themselves. The exploitation of those skills and knowledge is a popular topic of conversation within the industry, and yet we’re not hearing many solutions.
Web technologies are a way forward but a further challenge is the security piece that surrounds them. Despite the fact that organisations are more at risk from someone coming into their premises with a USB stick than they are from someone hacking into their system, the perception of threat is there. One of the ways of addressing this is to have a private cloud, which is something we’ve set-up at CFMS in order to gently migrate people into the environment of web scale whilst ensuring they’re confident their data is secure.
One final consideration is that web technologies are quite disruptive when it comes to their licencing model. There is a rise in the ‘freemium’ model where the majority of users are free users who essentially act as marketing for the company. The premium users who pay for the service have access to extra features and are essentially funding the development of the platform. A similar model exists around privacy as users can have access to the various tools for free as long as their data is public. To maintain private data, users have to pay. Traditional vendors have often backed feature-based licences but unfortunately those don’t tend to scale in business. For example, a costly single seat licence that has five add-on licences for special system engineering features becomes prohibitively expensive when scaled-up to 100s of users. Not only is that a barrier to the adoption of large-scale system engineering, it provides another piece of the puzzle as web-based models are quite attractive in terms of their ability to scale.
All things considered, we do believe there will continue to exist a mix of licence models as the industry looks to powerful desktop client-rich applications. Within the next five years, this will move to local data centres and private clouds. In the next 10 years, we expect to see the majority of businesses hosting in public/private clouds – possibly within a data centre owned by the company itself, or through a partnership with an organisation, such as Oracle, offering a dedicated service. If we look at the number of developers and their skillsets it certainly seems as though computing is being pushed in this direction. In fact, even the operating systems are driving towards constant connectivity and the same applies to security where the latest security patch is installed just by the user logging on rather than a dedicated IT professional coming in to reboot each individual system. This background connection is rapidly becoming an accepted way of working, and that will be expected from system engineering software as well.
It’s an exciting time because we are seeing some definite movement towards a web-based, integrated current user system design approach. There aren’t any mature products out on the market yet but there is a relatively new specification called the Lifecycle Modelling Language (LML) which aims toreduce design costs and enable more rapid product development by providing organisations with a structured and behavioural language. Visionaries within industry are looking at projects ranging from putting people on Mars to the development of autonomous vehicles and in order to deliver these complicated systems within a reasonable timeframe we need to unlock the full potential of system engineering.
In theory, if we can scale out across the business for any particular design point, then we should be able to move forward or backwards throughout the product lifecycle and design, and have true through-life engineering. As a neutral, independent and not-for-profit organisation, CFMS is here to help facilitate, educate and drive the message that modelling and simulation is the future of engineering system design. We are at the hub of high value engineering design and we want to take this topic to a wider audience and engage in as many discussions as possible.
When it comes to through-life system engineering, some methods and tools are missing but we believe they do exist in other sectors and all we need to do is bring them together and scale to the level offered by web technologies. All the ingredients are there – we just need to create that recipe.