SafeTTy Systems™

At SafeTTy Systems, we help our customers to develop software for reliable space-based systems, automotive systems (including autonomous vehicles), industrial control systems, medical systems, railway systems, sports equipment …

We do this using an industry-proven engineering process that integrates ‘Time-Triggered‘ (TT) software architectures with patented run-time monitoring techniques. 

The designs that we support are typically based on low-cost, off-the-shelf microcontrollers, provided by a range of different semiconductor manufacturers (our technology is not tied to any particular hardware platform).

Where required, we help our customers to achieve compliance with one or more international safety standards: ISO 26262, IEC 61508, ISO 13849, IEC 62304, IEC 60730 …

We offer:

We are a UK company with a worldwide customer base.



[Latest SafeTTy news]

exida® Automotive Symposium 2021m 2021

The exida® Automotive Symposium 2021 will take place at the Arabella Alpenhotel (Germany) from 22-24 September 2021.

On 24 September, the focus of this event will be on the use of Linux and similar large Open-Source software packages in safety-related systems.  Various organisations have been invited to contribute to this session including Apex, Aptiv, ARM, BMW, Codethink, Red Hat, SafeTTy Systems and Vector.

During this session, Dr Michael J. Pont (Founder and CEO, SafeTTy Systems) will give a presentation entitled: “Dealing with ‘SOUP’ and ‘HOUP’ in safety-related and safety-critical embedded systems using TT Wrappers”.

In this presentation, Michael will argue that: [i] there is an important class of safety-related / safety-critical systems that can be viewed as a combination of a PUCS (Potentially Unsafe Component or System) and an SMCS (Safety Monitoring and Control System); [ii] examples of a PUCS include not only traditional electro-mechanical systems but also Software of Unknown Provenance (SOUP) – including Linux – and Hardware of Unknown Provenance (HOUP) – including COTS processors and customised SoC designs; [iii] ‘TT Wrappers’ provide an effective way of implementing an SMCS.

Michael will also review an example of a traditional PUCS design and explore some of the challenges involved in determining the specification for the SMCS in situations where the PUCS consists of SOUP and / or HOUP.   

[20 August 2021]