home.social

#safetycritical — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #safetycritical, aggregated by home.social.

  1. I'm excited to announce that the library my team is working on has been released as #opensource this week. It is a base level C++ library intended for use in Safety Critical software, including Automotive software, so complies woth AUTOSAR guidelines. It includes fixed-capacity containers without dynamic allocation, as well as backports of recent library features like span and mdspan. See github.com/woven-by-toyota/are docs woven-by-toyota.github.io/aren #cplusplus #cpp #safetycritical

  2. Safety-critical development is more than picking the right language - it consists of requirements management, testing, structural coverage analysis, & more.

    Alex Senier & Manuel Hatzl (@ferrous) work through the software safety lifecycle at Oxidize 2026 in their hands-on workshop, to create a project scaffold for safety-critical development using Ferrocene & open-source Rust tooling.

    🔗 oxidizeconf.com/sessions/safet

    #Oxidize2026 #RustLang #Ferrocene #FunctionalSafety #Embedded #SafetyCritical

  3. Safety-critical development is more than picking the right language - it consists of requirements management, testing, structural coverage analysis, & more.

    Alex Senier & Manuel Hatzl (@ferrous) work through the software safety lifecycle at Oxidize 2026 in their hands-on workshop, to create a project scaffold for safety-critical development using Ferrocene & open-source Rust tooling.

    🔗 oxidizeconf.com/sessions/safet

    #Oxidize2026 #RustLang #Ferrocene #FunctionalSafety #Embedded #SafetyCritical

  4. Safety-critical development is more than picking the right language - it consists of requirements management, testing, structural coverage analysis, & more.

    Alex Senier & Manuel Hatzl (@ferrous) work through the software safety lifecycle at Oxidize 2026 in their hands-on workshop, to create a project scaffold for safety-critical development using Ferrocene & open-source Rust tooling.

    🔗 oxidizeconf.com/sessions/safet

    #Oxidize2026 #RustLang #Ferrocene #FunctionalSafety #Embedded #SafetyCritical

  5. Safety-critical development is more than picking the right language - it consists of requirements management, testing, structural coverage analysis, & more.

    Alex Senier & Manuel Hatzl (@ferrous) work through the software safety lifecycle at Oxidize 2026 in their hands-on workshop, to create a project scaffold for safety-critical development using Ferrocene & open-source Rust tooling.

    🔗 oxidizeconf.com/sessions/safet

    #Oxidize2026 #RustLang #Ferrocene #FunctionalSafety #Embedded #SafetyCritical

  6. Safety-critical development is more than picking the right language - it consists of requirements management, testing, structural coverage analysis, & more.

    Alex Senier & Manuel Hatzl (@ferrous) work through the software safety lifecycle at Oxidize 2026 in their hands-on workshop, to create a project scaffold for safety-critical development using Ferrocene & open-source Rust tooling.

    🔗 oxidizeconf.com/sessions/safet

    #Oxidize2026 #RustLang #Ferrocene #FunctionalSafety #Embedded #SafetyCritical

  7. On our latest episode, we're joined by Philip Koopman to explore how embedded systems are evolving into embodied and intelligent devices. The conversation dives deep into the safety challenges and critical considerations that come with designing intelligent, embodied technology.

    🎧 Listen here: embedded.fm/episodes/514

    Here's an excerpt:

    #EmbeddedSystems #IoT #AI #SafetyCritical #TechLeadership #EngineeringEducation #Policy #Law #TechBooks #EmbeddedFM #Engineering #Testing

  8. Philip Koopman joined us to talk about embedded systems becoming embodied and intelligent. We focused on the safety considerations of making an intelligent and embodied device.

    Don't miss out this intriguing conversation; listen here: embedded.fm/episodes/514

    Read the transcript here: embedded.fm/episodes/514

    Here's Phillip's favorite tip:

    #EmbeddedSystems #IoT #policy #AI #law #TechLeadership #EngineeringEducation #SafetyCritical #TechBooks #EmbeddedFM #embedded #engineering #testing

  9. Philip Koopman joined us to talk about embedded systems becoming embodied and intelligent. We focused on the safety considerations of making an intelligent and embodied device.

    Don't miss out this intriguing conversation; listen here: embedded.fm/episodes/514

    Read the transcript here: embedded.fm/episodes/514

    #EmbeddedSystems #IoT #policy #AI #law #TechLeadership #EngineeringEducation #SafetyCritical #TechBooks #EmbeddedFM #embedded #engineering #testing

  10. Philip Koopman joined us to talk about embedded systems becoming embodied and intelligent. We focused on the safety considerations of making an intelligent and embodied device.

    Don't miss out this intriguing conversation; listen here: embedded.fm/episodes/514

    #EmbeddedSystems #IoT #policy #AI #law #TechLeadership #EngineeringEducation #SafetyCritical #TechBooks #EmbeddedFM #embedded #engineering #testing #embedded

  11. 🎃 No tricks, just type safety.

    At Ferrous Systems, we believe code should be safe, not scary.

    Happy Halloween! 👻🦀

    #Rust #Ferrocene #SafetyCritical

  12. Announcement:

    Codethink is delighted to announce the publication of its baseline Safety Assessment report for Codethink Trustable Reproducible Linux (CTRL OS).

    The report validates Codethink’s safety argument for the use of CTRL OS in safety-critical and mixed-criticality systems up to SIL 3/ASIL D, and independently confirms that Codethink’s approach satisfies the expectations of both IEC 61508 and ISO26262.

    → Read the report: codethink.co.uk/news/trustable

    #SafetyCritical #FunctionalSafety

  13. Announcement:

    Codethink is delighted to announce the publication of its baseline Safety Assessment report for Codethink Trustable Reproducible Linux (CTRL OS).

    The report validates Codethink’s safety argument for the use of CTRL OS in safety-critical and mixed-criticality systems up to SIL 3/ASIL D, and independently confirms that Codethink’s approach satisfies the expectations of both IEC 61508 and ISO26262.

    → Read the report: codethink.co.uk/news/trustable

    #SafetyCritical #FunctionalSafety

  14. Announcement:

    Codethink is delighted to announce the publication of its baseline Safety Assessment report for Codethink Trustable Reproducible Linux (CTRL OS).

    The report validates Codethink’s safety argument for the use of CTRL OS in safety-critical and mixed-criticality systems up to SIL 3/ASIL D, and independently confirms that Codethink’s approach satisfies the expectations of both IEC 61508 and ISO26262.

    → Read the report: codethink.co.uk/news/trustable

    #SafetyCritical #FunctionalSafety

  15. Announcement:

    Codethink is delighted to announce the publication of its baseline Safety Assessment report for Codethink Trustable Reproducible Linux (CTRL OS).

    The report validates Codethink’s safety argument for the use of CTRL OS in safety-critical and mixed-criticality systems up to SIL 3/ASIL D, and independently confirms that Codethink’s approach satisfies the expectations of both IEC 61508 and ISO26262.

    → Read the report: codethink.co.uk/news/trustable

    #SafetyCritical #FunctionalSafety

  16. The current development of autonomous vehicles can never meet the aims that the research by Nick Reed outlines. They are mutually incompatible. Calling for transparently safe vehicles to work within a legal framework is correct, how they're being made will not hit those aims.
    Yet the public are told they are safe. Lies. Lots and lots of lies.

    #AutonomousCars #AutonomousVehicles #SafetyCritical #SafetySystems

    transportxtra.com/publications

  17. The legal expert cited, Professor William Widen, and Professor Phil Koopman have offered their thoughts on attributing liability (between the vehicle and the human driver), as linked to in the article.

    That work is here: papers.ssrn.com/sol3/papers.cf

    It is a sensible proposal and Professor Koopman is one of the foremost experts in #SafetyCritical systems, #robotics and #AutomatedDriving systems.

    Still, I submit that no proposal can quantifiably protect consumers with this type of system.

    Why?

  18. @lolgop Constantly. Constantly this is done.

    It is beyond exhausting.

    And it has actually proved to be extraordinarily dangerous when #Musk lies about the capabilities and availability of #Tesla's #FSDBeta product, in particular.

    The press often allows Wall Street analysts, that are not competent in #SafetyCritical systems, to advance Musk's dangerous lies.

    The #SystemsSafety community has been battling this for years.

  19. Remember: YouTube videos and personal testimonials can **never** show positive safety progress in the context of a #SafetyCritical system.

    Never.

    Videos and personal testimonials can only display safety-related **issues**.

    And even with organized efforts by many prominent #FSDBeta "testers" in the #Tesla community to only publish what they feel are the most visually-performant drives... I have never seen a video that did not contain serious safety-related issues (many which are "unseen").

  20. Alright. A few background notes.

    With respect to #SafetyCritical systems, "positive assumptions of safety" are incompatible with the analysis of these systems - particularly by those outside of a systems safety lifecycle.

    #Tesla is included here as well since, per my previous threads on the matter, Tesla is not maintaining a systems safety lifecycle with their #FSDBeta program.

    The assumption **must** be made that the Tesla vehicle would have blown the stop sign.

    Case closed on that.

  21. Hmm. Not sure about the wisdom of this...

    There are physical assets at risk and sometimes, arguably oftentimes, #SafetyCritical systems concerns here.

    I would need to see a safety case, at minimum.

    And I expect I would not receive it.

    #OPCUA #IIoT #ChatGPT

  22. First off, #cars are **not** smartphones.

    I cannot say that enough.

    And if you hear anyone describing them as such, it almost certainly means that they are (knowingly or not) hand-waving away the incomparable #SystemsSafety differences between a consumer electronic device and a #SafetyCritical system.

    That makes reports like this on #Tesla's hiring preferences **very** concerning: washingtonpost.com/technology/

  23. Oh memories.

    Taking a break from #Musk's Hate Train on the Hellsite to recall this series of Tweets from a few years ago.

    While under-appreciated then and now, the Tweet thread by Musk posted below contains an extremely damning #SystemsSafety admission and it displays the considerable #PublicSafety blind spot associated with remotely updating #SafetyCritical systems without oversight.

    Musk has no clue what he admitted to here, but systems safety experts do.

    #Tesla

  24. @EricPaulDennis @CrackedWindscreen A high #NCAP rating may actually point to a problematic system, deceptively.

    And NCAP has no ability to quantify that - which is always unacceptable in the context of any #SafetyCritical system.

  25. @mimsical But the immense complexity of the roadways are a given and they should be a given to #ADS developers and fleets.

    System developers and fleets cannot unilaterally change that.

    There is no technical value in trying to fix "fault" on any roadway participant (as the #NHTSA does, which is partly why the US #RoadwaySafety record is abysmal).

    The obligations of systems developers are to validate their #SafetyCritical system in a selected physical environment - with its warts and all.

  26. Let's talk about some of the core issues with the #J3016 standard, though.

    The first, most important problem is that it is not a safety standard.

    It is just a basic taxonomy of capabilities for #AutomatedDriving systems (ADS).

    But what good is a capability in a #SafetyCritical system if there cannot be a foundational safety case built around it?

    There is none.

    That leaves the door open for various laypeople to see safety, explicitly or implicitly, as a secondary concern.

  27. #SafetyCritical systems, like commercial aircraft and #SelfDrivingCars, are designed to operate in a certain physical environment under certain conditions.

    In industry, these sets of physical conditions go by various names, but in #AutomatedDriving systems, the term Operational Design Domain or ODD is commonly-used.

    Certain weather conditions, times-of-day, traffic conditions, geographical conditions, times-of-year and so on.

    The combination of all of these get put into the ODD.

  28. One of the major misconceptions with #AutomatedDriving systems is that they are an "AI".

    But they are not.

    They are #SafetyCritical systems.

    Such systems carry additional burdens that are foreign to more consumer/business-level #MachineLearning systems - in particular, the need to exhaustively quantify "the unseen" through objective analysis.

    It is something that, most notably, #Tesla fails to recognize with respect to their #FSDBeta program, likely by design.

    Let's explore two examples.

  29. #Tesla's self-driving software is buggy and Dan O'Dowd of #Greenhills Software is arguing, with good evidence, that it's irresponsible to debug super complex safety critical software by pushing it into wide distribution. However, Greenhills software is not the panacea O'Dowd claims it is. It is reliable, but it requires a large amount of less reliable software to work with it to do anything useful.
    #safetycritical #integrity

  30. Time for another #SystemsSafety Monday!

    #OTA (Over-The-Air) software updates and remote #telemetry mechanisms for #SafetyCritical systems are an under-appreciated public safety hazard when unregulated - as they are today.

    Some automakers already have these mechanisms available on existing vehicles and many more equipped vehicles are now coming to market.

    Very soon, these mechanisms will be commonplace.

    🧵 ⬇️

    #Automotive #SystemsSafety #RoadwaySafety

    1/6