<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Edge Case Research on Medium]]></title>
        <description><![CDATA[Stories by Edge Case Research on Medium]]></description>
        <link>https://medium.com/@edgecaseresearch?source=rss-e32e1c367ae------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*u8X9kugPLASeP0YmA3o4PA.png</url>
            <title>Stories by Edge Case Research on Medium</title>
            <link>https://medium.com/@edgecaseresearch?source=rss-e32e1c367ae------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:25:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@edgecaseresearch/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Edge Case Defense — How We Enable Warfighter Safety]]></title>
            <link>https://edgecaseresearch.medium.com/edge-case-defense-how-we-enable-warfighter-safety-301a3074edfe?source=rss-e32e1c367ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/301a3074edfe</guid>
            <category><![CDATA[safety-software]]></category>
            <category><![CDATA[safety-system]]></category>
            <category><![CDATA[mil-std-882]]></category>
            <dc:creator><![CDATA[Edge Case Research]]></dc:creator>
            <pubDate>Wed, 01 Mar 2023 17:17:09 GMT</pubDate>
            <atom:updated>2023-03-13T12:31:58.904Z</atom:updated>
            <content:encoded><![CDATA[<h3>Edge Case Defense — How We Enable Warfighter Safety</h3><h3>ECD System Safety Process Overview</h3><p>Edge Case Defense (ECD) has a mission of enabling warfighter safety across the US DoD, and we do this by ensuring the safety of the systems the DoD acquires. We use our expertise and experience to apply <em>MIL-STD 882, DoD Standard Practice — System Safety</em> to systems of all types, with a focus on complex, software-intensive vehicle and weapon systems. As a spin out from the Carnegie Mellon National Robotics Engineering Center, many of the systems we work on are some combination of robotic, unmanned, and autonomous.</p><p>ECD safety engineering capabilities are specifically tailored to facilitate DoD acquisition. The lifecycle-enablement found in our approaches are a critical multiplier in a time where system autonomy is ever increasing, software dependency continues to grow, and there is pressure to deploy and update systems rapidly. This article details the ECD MIL-STD 882 process along with insights and pitfalls we’ve noted over the years.</p><h3>MIL-STD 882 background and overview</h3><p>MIL-STD 882 specifies the system safety process as including the eight elements in Figure 1. From a high level it’s easy to see the eight elements and how they impact the entire system lifecycle, from cradle to grave.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*26g6ZUnLKvDySj_PaugWYw.png" /><figcaption>Figure 1 — MIL STD 882 eight elements of the system safety process</figcaption></figure><p>The elements have a sequential relationship but as with many systems engineering processes there are iterative feedback loops which update, refine, and improve as the system lifecycle progresses.</p><p><strong><em>ECD insight:</em></strong> Safety risk management has many similarities to more general program risk management in that risks are identified, documented, mitigated, and accepted. Tracking the status of the safety program and its associated risks in a clearly documented manner is critical to success of the program.</p><h3>MIL-STD 882 normative sections and highlights</h3><p>The details of the eight elements are further discussed in sections 4.2 and 4.3 of the MIL-STD where requirements for the system safety program are captured. A highlight from the requirements in section 4.2 is that all functional disciplines (e.g., systems engineers, software engineers, hardware engineers, test engineers, etc) are responsible for applying system safety measures to their area.</p><p><strong><em>ECD Insight:</em></strong> Safety engineers should have insight into the specifications and designs of all functional areas to ensure safety process adequacy throughout the system. Safety requirements are a key feedback mechanism for safety engineers to influence system designs.</p><p><strong><em>ECD Pitfall:</em></strong> Commercial Off-the-Shelf (COTS), Government-Off-the-Shelf (GOTS), Non-Developmental Item (NDI), Government-Furnished Equipment (GFE), and Government-Furnished Information (GFI) commonly lack adequate evidence of safety. However, MIL STD 882 applies to these items, and they must be addressed for safety implications.</p><h3>System safety process requirements</h3><p>Section 4.3 covers all of the eight elements of the system safety process.</p><p>Documenting the system safety approach is most commonly achieved through safety planning documents like a government System Safety Management Plan (SSMP) and developing contractor System Safety Program Plan (SSPP). Initiating a Hazard Tracking System (HTS) in this phase allows continuous monitoring of the state of the safety program and its risks as they are identified and managed.</p><p><strong><em>ECD Insight:</em></strong> The government Program Office will capture their intended management process for the system safety program in a System Safety Management Plan (SSMP). The developing contractor responds to the SSMP with their System Safety Program Plan (SSPP). Ask the government customer if a SSMP is available for review before finalizing the SSPP.</p><h3>Types of hazard analysis vs techniques for hazard analysis</h3><p>Safety process elements 2 through 5 in Figure 1 rely heavily on a number of hazard analyses, which are a key aspect of system safety engineering. It’s common for DoD contracts to cite MIL-STD 882 200 series tasks as contract deliverables in order to show how these process elements were achieved. These 200 series hazard analysis tasks largely describe types of hazard analysis, to include goals, scopes, and specific risks to be included. The performer is required to specify the methods and techniques intended to be used for each required hazard analysis type. For example, Task 205 System Hazard Analysis describes identifying hazards in the integrated system design. Since Task 205 requires consideration of independent, dependent, and simultaneous events that could increase risk, a Fault Tree Analysis (FTA) is a natural fit for the technique to be used.</p><p>A primary result of hazard analysis is the identification of safety requirements. This might flag existing requirements has having safety impact or identify new mitigating requirements such as those for detecting and responding to unsafe conditions. Identifying and tracking safety requirements is necessary to enable later safety verification which results in credible reduction of safety risk.</p><p><strong><em>ECD Insight:</em></strong> Functional Hazard Analysis (FHA) is described in MIL STD 882 Task 208. A tabular technique for FHA is described in detail in the <em>Joint Services — Software Safety Authorities (JS-SSA) Software System Safety Implementation Process and Tasks Supporting MIL-STD 882E </em>(further discussed here as the JS-SSA Implementation Guide (IG)). This FHA technique is powerful for complex systems, especially those levying safety requirements on a combination of hardware, software, and human interactions. By focusing on functions rather than component types, failure modes can be simplified using guidewords and concepts from Nancy Leveson’s Systems Theoretic Process Analysis (STPA) method. STPA was originated with software intensive control systems in mind. Unsafe functionality resulting from missing, inadvertent, late, or similar guidewords can be considered without needing to focus on the originating causal factor and, for example, the complexities in software that may have caused the unsafe functionality. As described in Task 208, the FHA should be initiated as early in the systems engineering process as possible (which can precede system detailed design).</p><p><strong>ECD Insight:</strong> ECD loves FHA as a technique. The FHA technique can be useful for other types of hazard analysis such as Subsystem Hazard Analysis (SSHA) where a tabular method is appropriate. When using FHA as a technique, the difference in the hazard analysis types can be defined by the scope and boundary of where the analysis starts and ends. For example, the Task 208 FHA may consider the system and its subsystems, while the Task 204 SSHA may provide a deeper dive into the low-level functions of those subsystems identified as safety critical.</p><h3>Risk definition and risk acceptance summary</h3><p>It’s important to note the risk assessment definitions in section 4.3.3 (shown below in Table 1, Table 2, and Table 3) and how those risks are accepted.</p><p><strong><em>ECD Insight: </em></strong>Some government program offices have approved modifications for severity, probability, risk assessment, or risk acceptance definitions and processes. Modifications should be supported with justification / rationale. If the government program office does not have an approved set of modifications, it’s wise to assume the MIL-STD definitions apply.</p><p><strong><em>ECD Pitfall:</em></strong> Software contribution to system risk is handled separately per section 4.4 and uses software Level of Rigor tasks evidences to adequately mitigate software risk rather than quantifying reduction in likelihood of unsafe software functionality. Application of probabilities to software failures is cited as “hard at best” in the MIL-STD and should generally be avoided.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PzE4jF79Ia-elONzWa5VMg.png" /><figcaption>Table 1 — MIL-STD 882 Hazard Severity Categories</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_zkfBiJvnV-noEF4ZVvm1Q.png" /><figcaption>Table 2 — MIL-STD 882 Hazard Probability Categories and example quantification</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3qbslDBXKThvclW3g5Wexg.png" /><figcaption>Table 3 — MIL-STD 882 Risk Assessment Matrix</figcaption></figure><p><strong><em>ECD Insight: </em></strong>Since many DoD vehicles and weapon systems have the potential to cause loss of life due to unsafe system functionality, it is not uncommon to have hazards with Catastrophic severity based on considering the credible worst-case result of unsafe functionality. Related to this is the common DoD stance that hazards are not reduced in severity (or eliminated) without changes to the system such that the energy source is inherently modified or removed. For example, a laceration risk may be eliminated if a sharp edge is removed from the design and replaced by a rounded surface. More often, high severity risks can be mitigated to reduce their probability. In this way, hazards with Catastrophic potential are commonly targeted for reduction to Improbable likelihood, which results in a generally acceptable Medium risk.</p><p><strong><em>ECD Insight:</em></strong> Note that the Improbable probability level is cited as “less than one in a million” likelihood of mishap with an unspecified time frame. It’s important to define and clarify how this will be assessed with stakeholders. For example, the one in a million could be in the lifetime of an item, the lifetime of a fleet, or per demand of a safety critical functionality. The lifetime may look at a fielded system lifecycle or consider shorter events like demonstrations or tests.</p><p><strong><em>ECD Insight:</em></strong> Safety assessment can be qualitative, quantitative, or a combination. Each approach has advantages and disadvantages. MIL STD 882 states that quantitative safety analysis and assessment is generally preferred over qualitative. An advantage of a quantitative approach is that there are clear assessment thresholds. Disadvantages of a quantitative approach include that manufacturer failure data can lack supporting claim evidences and software failures are difficult to quantify. Advantages of a qualitative approach are that more scrutiny can be applied on analyses that indicate the number of defeated interlocks that are required to cause a hazard and it is consistent with some aspects of software safety assessment. A disadvantage of a qualitative approach is potential ambiguity of the probability assessments.</p><h3>Software safety and level of rigor summary</h3><p>Section 4.4 details software contribution to system risk. The standard states that determination of the probability of failure of a single software function is difficult at best. Hence, it requires a different approach for assessing software and handling of those software items which are determined to have safety significance. New terminology is introduced, including:</p><p>Software Control Category (SCC), defined in Table 4 — A simpler way to consider SCC is: for a given software function, if unsafe functionality occurs how many other unsafe actions from other independent functions (i.e., independent interlocks) must occur to have a mishap occur? The fewer other interlocks, the higher the level of software control of safety. This is shown later in Table 7 — Software hazard causal factor risk assessment criteria.</p><p>Software Criticality Index (SwCI), defined in Table 5 — SwCI (often pronounced “swicky”) uses the SCC and considers the credible worst-case hazard(s) the software function could cause. Based on the severity and the SCC, the SwCI is determined. Note that a SwCI rating of 1 is “red”, but this is not a risk rating or unacceptable. The SwCI just determines the development that is required for the software.</p><p>Level of Rigor (LoR), with LoR tasks defined in Table 5 — The LoR tasks and resulting evidences are required for a given software item based on its assigned SwCI. An LoR task template is also provided in the JS-SSA IG and is the default task list starting point for most program offices.</p><p><strong><em>ECD Pitfall: </em></strong>Its critically important to be aware of the nature of software LoR tasks and their expected evidences prior to committing to a safety concept within the system architecture. Allocating LoR 1/2 to overly complex software can lead to safety designs that are not able to be adequately verified and result in elevated safety risk.</p><p><strong><em>ECD Insight:</em></strong> Using Functional Hazard Analysis, as discussed in MIL STD 882E App B, is incredibly useful in determining how software functions may contribute to system level hazard and hence identifying the necessary SwCIs correctly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nrKUgXO_rvcWehlH0R918Q.png" /><figcaption>Table 4 — Software Control Categories</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jC8iww1Uy86ukhtaTaknsg.png" /><figcaption>Table 5 — Software Safety Criticality Matrix</figcaption></figure><p><strong><em>ECD Pitfall: </em></strong>Avoid assessing SCC autonomy levels based on the concept of operations for uncrewed systems. SCC levels of autonomy are related to the level of direct control that a software function has over a hazard or mishap. For example, a teleoperated robot with no autonomous mobility control may still have autonomous SCC software responsible for detection and failsafe handling of lost radio link scenarios where the operator has no way to intervene. It’s important to use an analysis like FHA to assess each software function and find its appropriate SCC and SwCI.</p><p>As the software engineering lifecycle is executed, the identification of the appropriate LoR tasks for each software item allows identification of the required software safety LoR evidences. These evidences span the software development lifecycle to include planning, specification, design, coding, and verification. Early identification of safety critical software is a key enabler of success. Failure to provide evidence of the necessary LoR tasks requires consideration of Table 6 to assess the safety risk impact.</p><p><strong><em>ECD Pitfall:</em></strong> Developing and verifying safety critical software is resource intensive. As much as possible, architecting to minimize safety critical software (e.g., use more easily verifiable electromechanical mitigations instead of software) and where safety critical software is required, aim to isolate it from non-safety software. Failure to architect the system in this manner can result in safety critical functionality being scattered throughout the design and causing the associated schedule and budget resources to multiply rapidly.</p><p><strong><em>ECD Insight:</em></strong> LoR tasks can be tailored as described in the JS-SSA IG, but must be agreed upon by the developer, acquirer, and any other relevant government safety assessors. Rationale / justification should be provided to tailor LoR tasks.</p><p><strong><em>ECD Insight:</em></strong> MIL-STD 882 has less to say about hardware in safety critical functions compared to its software safety guidance. Other standards like ISO-26262 and ISO-13849 have detailed, quantifiable hardware safety guidance that is worth considering as a best practice. This includes redundancy-based architecture with fault detection and response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0iGopYICDnrXxBdwzMGMpw.png" /><figcaption>Table 6 — Relationship between SwCI, Risk Level, LoR Tasks, and Risk</figcaption></figure><h3>Verification, validation, and documenting risk reduction</h3><p>As previously mentioned, safety requirements will result from the hazard analysis process and require complete and methodical verification. In addition to verifying the system achieves its mission, verification of safety requirements will demonstrate that off nominal, unexpected, or anomalous conditions are handled in a safe manner. Safety significant software also has unique evidence requirements as mandated by the identified LoR, such as structural coverage of the software code. The results of verifying safety requirements can be captured in the HTS and hazard risk reduction credit can be gained based on traceability from the safety requirement to the hazards it helps to mitigate.</p><p><strong><em>ECD Insight:</em></strong> Software LoR evidence is commonly a combination of process documentation, analytical evidence, and test evidence from a number of environments like unit testing, integration testing, and system testing.</p><p><strong><em>ECD Insight</em></strong>: Careful consideration should be given to simulator verification, validation, and accreditation (VV&amp;A) with stakeholders as early as possible. The state space and accuracy in simulators needed to verify complex functionality is challenging. For example, environment simulation to verify and validate perception functionality in an autonomous vehicle has a much larger state space than that of a weapon simulator used to test a vehicle weapon interface. Gaining acceptable confidence in the simulator(s) to enable use for safety evidence collection is resource intensive for smaller scopes of simulation. For autonomous systems, simulation may need to aid in gaining coverage and volume of test cases across a much larger number and range of variables. Stakeholder VV&amp;A expectations should be elicited before counting on simulator data as part of the safety story.</p><h3>Accepting and documenting risk</h3><p>A number of events throughout the system lifecycle will require acceptance of safety risk. Examples might be acquisition milestone based (e.g., to support design reviews or milestone decisions) or based on warfighter usage of the system (e.g., demonstrations, test events, or fielding events). For all of these, it’s common for the developing contractor to deliver a Safety Assessment Report (SAR). The SAR takes a snapshot of the safety story at a point in time, for a (set of) specific system configuration(s), in a defined set of environments and use cases. This commonly includes the latest HTS, and associated hazard analyses and verification data used to populate the HTS.</p><p><strong><em>ECD Insight:</em></strong> Specifically for autonomous systems — understanding how the system works and how it might fail is critical to enabling sufficient hazard analysis and safety risk reduction. Using emerging industry standards <em>like UL 4600 — Standard for Safety — Evaluation of Autonomous Products</em> can accelerate this learning. Additionally, given the novel implementation methods often required for autonomous systems, some level of safety consideration for unknown unknowns is likely required. Focusing on system robustness via methods like fault insertion is critical to ensure complex autonomous functionality can recognize and handle edge cases.</p><p><strong><em>ECD Pitfall:</em></strong> The SAR is sometimes the primary or only safety deliverable on contract. However — A SAR without the associated safety process artifacts will merely be a shell that does not hold up under assessor scrutiny. A critical eye on safety deliverables in the government Request for Proposal is necessary to ensure the right technical information is able to be generated and is supported with adequate schedule and budget.</p><p>Appendix B provides additional software system safety guidance. Table 7 and Figure 2 below provide useful concepts and visuals for considering interlock counts in risk assessment and how to integrate software, hardware, and operator elements into risk assessment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5riYjnI4VCjxP8qE56nHxQ.png" /><figcaption>Table 7 — Software hazard causal factor risk assessment criteria</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1gurSS1T3CAjSQsgeM3qpA.png" /><figcaption>Figure 2 — Assessing software contribution to system risk</figcaption></figure><h3>Safety engineering in the systems engineering lifecycle</h3><p>ECD executes system safety within the program systems engineering lifecycle to ensure that adequate planning, resourcing, and risk decision making occurs. Successful programs recognize that system safety is not a result of a certain test event at the end of development, but rather a holistic process that includes safety considerations from program inception.</p><p><strong><em>ECD Pitfall:</em></strong> Missing/weak systems or software engineering core practices can be a blocker to a successful system safety program. System decomposition, traceability, configuration management, quality assurance, and verification &amp; validation for all functionalities are table stakes for developing DoD weapon and vehicle systems.</p><p>Figure 3 shows ECD’s system safety process which is categorized into Safety Planning, Safety Analysis, Safety Verification, and Safety Reporting. Additional detailed writeups will be available for commonly executed MIL-STD 882 tasks including: SSPP, HTS, Preliminary Hazard Analysis, System Hazard Analysis, Subsystem Hazard Analysis, System Requirements Hazard Analysis, Operations &amp; Support Hazard Analysis, Safety Verification and Validation &amp; Software Level of Rigor evidences, and SAR.</p><p><strong><em>ECD Insight:</em></strong> Given the rise in level of system autonomy and inclusion of complex or black box functionality like machine learning, developers and acquirers will benefit from discussing risk with stakeholders early and often. Planning for elevated risk acceptance when needed and understanding missions where elevated risk can be accepted will enable the acquisition effort to take early steps to success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Scsal7B0FUyw5j-SlKXUA.png" /><figcaption>Figure 3 — ECD system safety process</figcaption></figure><p><strong>About Edge Case Research:</strong></p><p>At Edge Case Research, we believe that complex systems should be built safely from the ground up. Founded in 2014 by leaders in autonomous vehicle safety, our expert team provides system safety engineering services, nLoop Live Safety Case software, and risk management solutions. Our clients include government agencies and developing contractors in the aerospace and defense industries, as well as automotive and trucking OEMs, Tier 1 suppliers, and insurance providers. For more information, visit <a href="https://www.ecr.ai/">ecr.ai</a> or <a href="https://www.ecr-defense.ai/">ecr-defense.ai</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=301a3074edfe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Key Additions to the Edge Case Risk Management Team]]></title>
            <link>https://edgecaseresearch.medium.com/announcing-key-additions-to-the-edge-case-risk-management-team-24f908ba50aa?source=rss-e32e1c367ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/24f908ba50aa</guid>
            <category><![CDATA[safety-engineering]]></category>
            <category><![CDATA[insuretech]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[autonomous-vehicles]]></category>
            <dc:creator><![CDATA[Edge Case Research]]></dc:creator>
            <pubDate>Thu, 25 Aug 2022 14:00:16 GMT</pubDate>
            <atom:updated>2022-08-26T12:20:55.445Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KiDMdkVeugl4z5S04TnYDw.png" /></figure><p><em>Meet the experts on our advisory board and key members of the Edge Case Risk Management team, who are building and delivering insurance for safer autonomous vehicles</em></p><p><em>By Benjamin Lewis, Vice President of Insurance &amp; General Manager of Edge Case Risk Management</em></p><p>Earlier this year, <a href="https://edgecaseresearch.medium.com/how-were-encouraging-safer-autonomy-through-insurance-496a27e1c27f">Mike and I shared that Edge Case Research has set out to establish Edge Case Risk Management (ECRM)</a>, an insuretech managing general agent (MGA) that underwrites insurance for autonomous vehicle (AV) developers and fleets. ECRM will offer insurance that is thoughtfully constructed to recognize and reward safer autonomy and meaningfully support the industry’s plans to commercialize and go to market in the coming years. We’re hard at work building this new venture and crafting insurance solutions that are powered by safety cases, engineering principles, and standards — tools that Edge Case has used for almost ten years to help AV companies build their systems safely from the ground up. To drive this exciting work forward and develop better AV insurance solutions, we have assembled experts on both the team and our new advisory board. It is my pleasure to introduce you to a few of the key leaders on our team and our stellar set of advisors. All bring exceptional experience and expertise to Edge Case.</p><p><strong>Key Team Members:</strong></p><p><strong>Emily Fitts, CPCU — Autonomous Systems Underwriter</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*wlPJPy5x3M1Z9eOqXdkeoQ.png" /></figure><p>Emily leads the development and execution of underwriting strategy and tactics at ECRM. In addition to her focus on underwriting, Emily is also lending her expertise to insurance product and program development. She collaborates closely with our System Safety Engineering team to translate technical measures of AV risk into underwriting decisions and insurance product and pricing features. Before joining ECRM, Emily honed her skills as a Technology &amp; Life Science underwriter at The Hartford and an Emerging Technology underwriter and AV specialist at Travelers Insurance. She graduated with high honors from Gustavus Adolphus College with a degree in Economic Analysis and holds a Chartered Property Casualty Underwriter designation.</p><p><strong>Jacob Nelson — Director of Risk Engineering</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*6pd3iuOn7i-TkGQeqvXUaw.png" /></figure><p>Jacob has been at the forefront of solving complex autonomous and embedded software system safety engineering challenges ever since he joined Edge Case in 2015. He led the construction of safety cases for multiple autonomous system developers and helped insurers and other stakeholders to meaningfully assess the risks of such systems. Jacob now applies this wealth of experience to integrate safety cases and safety engineering into every aspect of Edge Case Risk Management’s processes and products. An expert in UL 4600, SOTIF, and MIL-STD-882E (among other standards), Jacob holds an MS in Electrical &amp; Computer Engineering from Carnegie Mellon University.</p><p><strong>Maximilian Schöffer — Director of Strategy &amp; Business Development</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*dTn0lJQBUblOrGNMT2Nk_w.png" /></figure><p>With his entrepreneurial talents gained from roles at multiple tech and mobility startups, Max has been a key contributor to Edge Case’s growth since joining the company in 2020. As a former Mobility-as-a-Service operations practitioner, Max has a knack for understanding what matters most to autonomy and mobility companies looking to scale. He is responsible for managing and growing some of Edge Case’s most successful account relationships with autonomous system developers. Max joined the ECRM team to continue leading efforts to refine product-market fit and build fruitful relationships with AV customers seeking better insurance. Based in Edge Case’s Munich office, Max serves as ECRM’s representative in Europe. He holds a master’s degree in Global Entrepreneurial Management from the University of San Francisco.</p><p><strong>Advisory Board Members:</strong></p><p><strong>Amy Wagner — Former Head of North America Insurance at Uber Technologies</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*e_z1rYXVEz6tjUSmJgxcqg.png" /></figure><p>Amy is a seasoned senior executive who has held leadership roles across multiple disciplines and industries throughout her career, including corporate finance, investor relations, and risk management/insurance. She started her career with a 16-year span at Ryder System, a leading transportation and logistics company with one of North America’s largest fleet of trucks. There, Amy rose through the ranks to become vice president of Risk Management &amp; Insurance Operations, as well as vice president of Finance during a more recent stint at the company. Most recently, she joined Uber Technologies as head of North America Insurance from 2020 through Q2 2022. In this role, she oversaw Uber’s United States and Canada Mobility and Delivery insurance programs, corporate risk management and insurance procurement strategy, as well as the company’s in-house North America Insurance, Claims, and Risk Management teams.</p><p>Amy brings immense expertise in sophisticated risk management as an advisor to ECRM. Her time at Ryder and Uber gives her unique insights into the needs of risk managers at complex logistics, trucking, and Mobility-as-a-Service companies. I first started working with Amy (over Zoom) when she joined Uber two years ago. In the time since, I learned a lot about leadership and savvy risk management from her. The team and I are thrilled to have her on board to impart yet more expertise to ECRM.</p><p><strong>Liam Jones — SVP &amp; Head of Business Development at Mosaic Insurance</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*mewmIsoYIVXsQYHvKBIY3w.png" /></figure><p>Liam is a member of the leadership team of Mosaic Insurance — a global specialty insurance hybrid carrier startup, anchored in Lloyd’s of London. Liam drives product innovation at Mosaic while also overseeing the interface between underwriting and technology, working with all product units to enhance Mosaic’s pioneering insuretech platform. Liam is also tasked with developing Mosaic’s Syndicated Capital Program, which pairs trade and risk capital partners with insurance risk through Mosaic’s agency operations. With 16 years of experience in global specialty underwriting, he has worked extensively in the Lloyd’s, US, and Bermuda marketplaces. Previously, he served as head of Underwriting Strategy for Liberty Specialty Markets Bermuda, where he also ran the financial lines, healthcare, and special risks divisions. During his time at Liberty, Liam developed complex and innovative multi-line insurance programs for some of the world’s largest companies, including household names in the technology and software industries. On top of his role at Mosaic, Liam is a mentor in the Lloyd’s Lab and holds advisory positions at a number of insuretech companies.</p><p>We are elated to work with Liam because of his invaluable experience crafting specialty lines insurance for complex and emerging risks, connections across the Lloyd’s, US, and Bermuda markets, and his ability to harmonize underwriting and technology. I first met Liam at a dinner event in 2018 that I was invited to because of my efforts to build insurance for autonomous vehicles. It turned out that he had an AV submission on his desk at that exact moment and we worked on it together in the weeks that followed. I am looking forward to collaborating with Liam on AV insurance once again.</p><p><strong>Rob Higgins — Chief Product &amp; Strategy Officer at Openly</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*4ipc6_eDsetes2wr0GUUIg.png" /></figure><p>Rob leads product and strategy at Openly, a technology-enabled homeowners insurance startup that is backed by top venture capital funds. Prior to Openly, he spent nine years at Liberty Mutual Insurance as a senior leader in Finance, Claims, and Product. Rob was most recently head of US Financial Planning &amp; Analysis for Liberty’s Global Retail Markets division and a member of the executive team who oversaw the formation and management of Liberty’s Mobility Practice. Earlier in his career, Rob worked as a strategic consultant to CEOs and Private Equity firms with The Parthenon Group and as an international equity analyst at Putnam Investments. Rob is a CFA Charterholder and received a BA in Biology from Harvard and an MBA from the Tuck School of Business at Dartmouth, where he was an Edward Tuck Scholar.</p><p>Rob’s extensive and diverse leadership experience, including at an insuretech startup that successfully scaled and evolved from operating as an MGA to establishing a full carrier, is highly relevant to our efforts at Edge Case Risk Management to go to market as an AV insurance MGA. I have admired Rob’s thoughtful and strategic leadership style ever since we first collaborated on the formation of Liberty Mutual’s Mobility Practice, and I am glad to work with him again in this capacity.</p><p>It is an exceptional privilege to work with these and all of the Smart, Helpful, and Friendly members of the Edge Case team. Please stay tuned for more on Edge Case Risk Management’s efforts to build and deliver insurance solutions for autonomy in the real world and look out for our team at mobility, safety, and insurance events throughout the remainder of 2022. We will be the ones ready to discuss insurance for safer AVs.</p><p><strong>About Edge Case Risk Management:</strong></p><p>Edge Case Risk Management (ECRM) is an autonomous vehicle insuretech offering insurance and risk solutions that help companies go to market with safe, reliable, and trustworthy autonomy. Powered by pioneering work conducted by Edge Case Research in the field of autonomous system safety, ECRM combines engineering expertise and risk analytics with underwriting know-how to deliver insurance that recognizes and rewards safer autonomy. Edge Case Risk Management is a subsidiary of Edge Case Research, Inc. For more information, visit ecr.ai.</p><p><strong>About Edge Case Research:</strong></p><p>At Edge Case Research, we believe that every autonomous vehicle should be built safely from the ground up. We help companies go to market with autonomous mobility that is safe, reliable, and trustworthy. Founded by leaders in autonomous vehicle safety, our expert team provides system and safety engineering services, nLoop Live Safety Case software, and risk management solutions to software driver developers, automotive and trucking OEMs, Tier 1 suppliers, insurance providers, and the aerospace and defense industries. For more information, visit ecr.ai.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24f908ba50aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Edge Case Defense: Safety for Systems Empowering Warfighters]]></title>
            <link>https://edgecaseresearch.medium.com/edge-case-defense-safety-for-systems-empowering-warfighters-912c6063be98?source=rss-e32e1c367ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/912c6063be98</guid>
            <category><![CDATA[autonomous-vehicles]]></category>
            <category><![CDATA[aerospace-and-defense]]></category>
            <category><![CDATA[mil-std-882e]]></category>
            <category><![CDATA[safety-assessment]]></category>
            <category><![CDATA[systems-engineering]]></category>
            <dc:creator><![CDATA[Edge Case Research]]></dc:creator>
            <pubDate>Mon, 28 Mar 2022 17:16:44 GMT</pubDate>
            <atom:updated>2022-03-28T17:16:44.417Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By Frank Fratrik and Michael Wagner</em></p><p>The United States Department of Defense is rapidly deploying advanced systems — often with high levels of autonomous control — to maintain an advantage over our adversaries. However, the growing complexity of these systems poses unique challenges for safety engineering.</p><p><a href="https://www.ecr-defense.ai/">Edge Case Defense</a> (ECD) is here to help. We thrive at the intersection of complex systems and rigorous safety engineering. Our safety solutions are tailored to satisfy <a href="https://www.dau.edu/cop/armyesoh/DAU%20Sponsored%20Documents/MIL-STD-882E.pdf">MIL-STD 882</a> requirements and can help your organization to meet or exceed its schedule and budget goals.</p><p><strong>Growing DoD System Complexity, Autonomy, and Rate of Production</strong></p><p>The DoD increasingly deploys sophisticated technologies to meet the challenges of modern warfare. Autonomous vehicle mobility is expanding across every operational domain. A more diverse set of payload capabilities use autonomous control authority. Artificial intelligence and machine learning bring incredible gains in performance and functionality.</p><p>All of these new technologies must meet the requirements of the MIL-STD-882 safety standard. Complying with this rigorous standard is a resource-intensive process that requires specialized safety knowledge and expertise. As systems grow more complicated, these safety engineering requirements become harder and harder to satisfy. This particularly applies to autonomy. Without the right expertise and tools, the risk of missed technical, schedule, and budget constraints grows exponentially. Often, these deficiencies aren’t recognized until late in the development process — multiplying the cost of correcting them.</p><p>At the same time, new features are being added to already-deployed systems at a faster and faster rate. Systems that used to receive software updates a few times a year are now transitioning to the continuous updates of the DevSecOps model. Program Offices look to implement Continuous Integration/Continuous Deployment processes to more rapidly meet the needs of Warfighters. Systems that are still under development face pressure for more frequent and broader demonstrations. In some cases, they undergo an expedited acquisition process to speed up their deployment. Despite this pressure, MIL-STD 882 safety assessment and risk acceptance from each safety stakeholder remains a required gatekeeper for deploying these systems in the field.</p><p><strong>Edge Case Defense Fulfills the Need for Verifiable System Safety</strong></p><p>ECD’s team of expert safety engineers provides MIL-STD 882 lifecycle system safety engineering with a focus on successful Safety Assessment Reports. To help you build and maintain your safety story, we’ll draw upon our experience as Army safety assessors, Carnegie Mellon University safety researchers, and implementers of safety processes across multiple industries.</p><p>ECD’s broad safety expertise spans the entire range of MIL-STD 882 tasking. We are aided by safety case thinking to ensure that your Safety Assessment Report covers all needed aspects of this standard. Our system safety analysis and activities follow the three pillars of the ECD safety case:</p><p><em>Live It Right</em> — Begin with a strong safety plan to create an organization’s safety culture and set the stage for a safe system lifecycle. Manage system safety deliberately.</p><p><em>Engineer It Right</em> — Define the system, its CONOPs, and its use cases. Methodically identify hazards and causal factors. Apply mitigations throughout. Verify the implementation and effectiveness of these mitigations. Assess risks accurately and communicate effectively with stakeholders. Support informed decisions about deployment risks.</p><p><em>Operate It Right</em> — Enable Warfighters to safely use these systems. Ensure that operators understand and follow operational safety constraints. Measure the effectiveness of safety mitigations and ensure that safety assumptions hold true.</p><p>This framework scales to systems with a wide range of sizes and capabilities. ECD’s expertise in software system safety and Level of Rigor provides guidance on compliance with the Joint Software System Safety Engineering handbook, the Joint Services — Software Safety Authorities Software System Safety Implementation Guide, AOP-52, and similar software-focused safety guidance. We’ve seen what <em>right</em> looks like and can help you build compliant evidence. We can also assist you to successfully navigate safety assessments by the US Army Test and Evaluation Command (ATEC), the Navy Weapon System Explosive Safety Review Board, the Joint Weapon Safety Review Board, and command safety offices throughout the DoD.</p><p><strong>Edge Case Defense — A Trusted Source for Ensuring Safe Systems</strong></p><p>Since 2014, ECD has been leading DoD program safety efforts, generating safety artifacts, and authoring Safety Assessment Reports. ECD’s safety efforts focus on Systems Engineering, System Architecture, Hardware Safety, Software Safety, Safety Verification and Validation, and Human Factors Safety. As a team, ECD has over 120 years of experience in assessing the safety of DoD systems and over 150 years of experience in executing system safety engineering.</p><p>This deep experience leads to safety efforts that are both effective and efficient. For example, by providing guidance on safety concepts, system architecture, and operational procedures, we significantly reduced the safety critical function count for a system prototype demonstration. We ensured that soldier demonstration goals were met while gaining ATEC Safety Release approval. The efficiency gain was estimated at a 60% cost reduction from the initial estimate of required safety resources.</p><p>ECD demonstrated its safety leadership as the safety lead for multiple complex robotic and autonomous systems, including some with weapons payloads. We’ve led efforts to generate safety language for use in Requests for Proposal and Statements of Work. We also have a growing trend of winning government bids with our safety engineering proposals.</p><p>ECD is a proven leader in the DoD safety and MIL-STD 882 space. We drew upon this experience as the primary authors of UL4600 — the first standard for assessing the safety of autonomous systems. With the release of UL4600 in 2020, we’re in an excellent position to build upon these organizing principles to ensure a complete safety effort and approved Safety Assessment Report for autonomous DoD systems and safety stakeholders.</p><p>Our approach is backed by over $15M in DoD research and development funding to progress our safety thinking into safety tools. To build these tools, ECD’s in-house safety engineering and software development experts draw upon lessons learned and technology from on-road and off-road commercial autonomous vehicle applications.</p><p>ECD is ready to plan, manage, execute, and deliver lifecycle system safety. We are here to ensure safety for your systems that empower Warfighters.</p><p><strong>About Edge Case Research:</strong></p><p>At Edge Case Research, we believe that complex systems should be built safely from the ground up. Founded in 2014 by leaders in autonomous vehicle safety, our expert team provides system and safety engineering services, nLoop Live Safety Case software, and risk management solutions. Our clients include software driver developers, automotive and trucking OEMs, Tier 1 suppliers, insurance providers, and the aerospace and defense industries. For more information, visit ecr.ai or ecr-defense.ai.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=912c6063be98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Locomation and Edge Case Research Team Up to Deliver Safer Autonomous Trucking]]></title>
            <link>https://edgecaseresearch.medium.com/locomation-and-edge-case-research-team-up-to-deliver-safer-autonomous-trucking-168f3b17b16?source=rss-e32e1c367ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/168f3b17b16</guid>
            <dc:creator><![CDATA[Edge Case Research]]></dc:creator>
            <pubDate>Thu, 24 Mar 2022 17:06:40 GMT</pubDate>
            <atom:updated>2022-03-24T17:24:58.404Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.ecr.ai/">Edge Case</a> is proud to work with Locomation to help build a robust ANSI/UL 4600-conformant safety case for their Autonomous Relay Convoy (ARC) system. The ARC system is intended to alleviate some of the key challenges in the trucking industry. Helping Locomation to deliver on the commitments made to their partners and customers to deliver a safe, reliable, and scalable system is exactly what we mean by our mission statement: to deliver the promise of autonomy.</p><blockquote>Edge Case Research collaborated with industry and government to pioneer the development of ANSI/UL 4600, the leading standard to address safety principles and a process for assessing autonomous vehicle safety using the safety case approach. Locomation partnered with Edge Case to develop our safety case based on Edge Case’s experience developing leading autonomous vehicle safety cases. We share the common mission of delivering safe autonomous technology to help solve some of society’s biggest problems.</blockquote><blockquote>Locomation used Edge Case’s <a href="https://www.ecr.ai/"><em>nLoop safety case framework</em></a>, multiple industry standards, and best practices to shape the ARC safety case. The joint team then mapped the safety case to the ARC operational concept and developed a roadmap to ensure safety was the driving focus for the design, development, testing, and operation of the ARC system. Following a safety case based approach will speed the development and adoption of ARC technology, which in turn will help relieve some of the demand and capacity burden facing the trucking industry.</blockquote><p>For the full release, authored by Locomation CEO &amp; Co-founder Çetin Meriçli and Edge Case CEO Michael Wagner, please go here: <a href="https://locomation.ai/locomation-and-edge-case-research-team-up-to-deliver-safer-autonomous-trucking/">https://locomation.ai/locomation-and-edge-case-research-team-up-to-deliver-safer-autonomous-trucking/</a></p><h3>About Locomation</h3><p>Locomation is re-engineering the world’s supply chain for autonomy with a portfolio of AV products and a suite of tools that enable our clients to implement an operating model for autonomous vehicles. Launched in 2018 by veterans of Carnegie Mellon’s National Robotics Engineering Center, the Locomation team includes some of the world’s foremost experts in robotics technology, artificial intelligence, trucking, freight optimization, safety, and automotive. Learn more at <a href="https://locomation.ai/">https://locomation.ai</a> or follow us on Twitter at @LocomationAI or on LinkedIn at <a href="http://linkedin.com/company/locomation.">linkedin.com/company/locomation</a>.</p><h3><strong>About Edge Case Research</strong></h3><p>At Edge Case Research, we believe that every autonomous vehicle should be built safely from the ground up. We help companies go to market with autonomous mobility that is safe, reliable, and trustworthy. Founded in 2014 by leaders in autonomous vehicle safety, our expert team provides system &amp; safety engineering services, nLoop Live Safety Case software, and risk management solutions to software driver developers, automotive and trucking OEMs, Tier 1 suppliers, insurance providers, and the aerospace and defense industries. For more information, visit <a href="https://www.ecr.ai/">ecr.ai</a> or <a href="https://www.ecr-defense.ai/">ecr-defense.ai</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=168f3b17b16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We’re Encouraging Safer Autonomy Through Insurance]]></title>
            <link>https://edgecaseresearch.medium.com/how-were-encouraging-safer-autonomy-through-insurance-496a27e1c27f?source=rss-e32e1c367ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/496a27e1c27f</guid>
            <dc:creator><![CDATA[Edge Case Research]]></dc:creator>
            <pubDate>Tue, 01 Mar 2022 00:08:02 GMT</pubDate>
            <atom:updated>2022-03-01T00:08:02.096Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introducing Edge Case Risk Management</h3><p><em>By Benjamin Lewis and Michael Wagner</em></p><p>Safety is the most important hurdle that autonomous vehicle technology faces as we prepare for its deployment on our highways and into our neighborhoods. Polls consistently show the public is concerned about the safety of autonomous vehicles despite recent progress across the industry. Just last year, <a href="https://newsroom.aaa.com/2021/05/drivers-should-know-if-they-are-sharing-the-road-with-self-driving-test-vehicles/">AAA and Harvard Kennedy School’s Belfer Center for Science and International Affairs found that, among surveyed U.S. drivers, 36% opposed autonomous vehicle testing on public roads, with safety cited as their top concern</a>. Clearly, the issue of safety must be a top priority for the industry if acceptance and adoption of autonomous vehicles are to be achieved.</p><p>For autonomy to deliver on promised benefits, the industry must validate that its technology is safer than human drivers, as the losses on our roads today are significant and many crashes have preventable causes. These losses have continued to increase, even as we have all driven less amid the pandemic, with <a href="https://www.nhtsa.gov/press-releases/traffic-fatalities-estimates-jan-sept-2021">NHTSA estimating that 31,720 people died in motor vehicle crashes from January through September 2021</a>, an increase of approximately 12% over the same period in 2020. That is the highest percentage increase during the first nine months of any year since NHTSA implemented its current reporting system in 1975. While it is very likely autonomous vehicles will do better and address many of those preventable causes, meeting this residual risk threshold with such novel technology at scale is an enormous challenge.</p><p>Two years ago, Edge Case Research partnered with UL Standards and a panel of industry leaders to define, for the first time, how to validate the safety of autonomy. The UL 4600 standard is the result of that effort. UL 4600 lays out a long list of expectations in its three hundred pages, but what it doesn’t provide is step-by-step instructions for exactly how to meet those expectations.</p><p>Six years before UL 4600 was published, Edge Case was founded to define those instructions and build the evidence-based safety arguments autonomous vehicle technology developers need in order to answer the question “is it safe enough to deploy?” Since 2014, our team has pioneered techniques and technologies that assess the safety of autonomy in smarter and more scalable ways. More recently, we built nLoop so that members of the industry can measure, manage, and communicate the safety of their autonomous vehicle technology as it is developed, tested, and operated on our roadways. At the same time, leading players in the autonomy industry have been standing up top-notch teams to manage safety processes across their organizations. This is fantastic progress. However, significant investments are still needed to meet the industry’s risk objectives.</p><p><strong><em>Insurance can drive smart investments in safety</em></strong></p><p>Autonomy promises to reduce fleet operating costs, of which insurance is a major component. Today, however, insurance carriers cannot price premiums in a way that accurately and specifically reflects the risk profiles of autonomous fleets. Software drivers and their creators are evaluated by insurers in much the same way as traditional vehicle risks because the complex engineering processes and technology behind autonomous vehicles must be met with equivalent technical expertise that lies outside of the insurance industry itself.</p><p>In short: how can insurers and reinsurers properly weigh and price the risk of systems for which there is a lack of historical data and in-house expertise to evaluate what data there is? How can brokers advocate for better rates on behalf of their clients without a compelling, evidence-based argument and an intelligible framework to communicate those claims to underwriters?</p><p>Realistic, technical, data-driven assessments of autonomous vehicle risk will enable the insurance industry to price risk accurately, benefitting insurance buyers as well. This is where we see opportunity. <strong>We intend to build an insurance market that offers actionable insights to risk managers and rewards real reductions in residual risk with lower premiums</strong>. Such a market will incentivize and reward developers and operators who invest in safety engineering.</p><p>Some may ask why we, a company steeped in engineering and technology, have decided to embark on this journey to build a business centered on insurance for autonomous vehicles.</p><p>One reason is that, after safety, liability is top of mind for the public and policymakers when it comes to autonomous vehicles. The <a href="https://newsroom.aaa.com/2021/05/drivers-should-know-if-they-are-sharing-the-road-with-self-driving-test-vehicles/">2021 AAA and Harvard survey found that liability determination in the event of a crash was a close second</a> among the concerns of those opposed to autonomous vehicle testing on public roads. At Edge Case, we believe the two issues are interconnected and our techniques and technologies are tailor-made to bring clarity to both.</p><p>Another reason lies in our experience. Over the past four years, Edge Case has partnered with some of the world’s leading insurers and reinsurers to help them meet the complex insurance and risk management needs of the emerging autonomous vehicle ecosystem. As Edge Case expanded our business with insurance companies, we identified three areas where we could add value:</p><ol><li>Proactive mitigation during the development process as a key tool to manage the risks posed by modern software-enabled products. Historical actuarial data remain significant, but the residual risk of an autonomous vehicle could shift constantly as new versions of software are delivered over the air. Over reliance on historical data will delay the recognition of evolving risk and inhibit insurers’ ability to offer rewards for mitigation.</li><li>The shift to highly correlated risks stemming from software drivers. Insurers’ actuaries can reliably model claims rates from a huge population of independent human drivers. But carriers will now need to assess and price systemic risks that span entire fleets of vehicles equipped with the same software driver. The same methods applied to price driving risk today will not be sufficient in the world of widespread autonomous mobility.</li><li>Speed to market. Autonomous vehicles are driving on our roads today, and operations will scale dramatically in the next few years. Yet insurance products have not kept pace. Now is the time for the industry to make and sustain substantial investments in safety, and for insurers to similarly invest in understanding the risk the technology presents.</li></ol><p>The remaining question is: how can we build such a market?</p><p>Ever seeking solutions, and in support of safer autonomy, Edge Case is announcing a major step to meet these needs. In partnership with primary insurance carriers, reinsurers, and brokers, <strong>we are establishing Edge Case Risk Management, a managing general agent (MGA) that will be dedicated to underwriting autonomous vehicle developers and their customers</strong>.</p><p>We will begin by offering insurance products that tie directly to companies’ safety cases and the associated metrics. Our business will scale with our customers as they go to market. While we expect that autonomous trucking fleets will be the first large-scale deployments, we will also expand into ride-hailing, goods delivery, and other segments where autonomy is likely to be adopted at scale. In the US, the market for auto liability insurance alone generates well over $300b in gross premiums annually, and it is expected that a significant portion will be displaced as autonomous vehicles become prevalent on our roads. With our partners, we aim to take a leading position as this market solidifies and be there for customers as they commercialize in the coming years.</p><p>Edge Case Risk Management underwriting will leverage the expertise of the global Edge Case team, which has more than a century of combined experience assessing and developing safety arguments for autonomous systems. Prior to joining the company, members of our talented team helped build simulation infrastructures for Uber ATG and Argo AI, advised on safety at Aurora, tested combat systems at the U.S. Army Aberdeen Proving Ground, and researched the implications of safety-critical AI at Carnegie Mellon University. Building on that, the Edge Case team has successfully helped four major automotive OEMs, a half-dozen software driver developers, four Tier 1 suppliers, and a number of other market participants to make their systems safer and more reliable. Our team of system safety engineers also outnumbers even large autonomous vehicle developers.</p><p>All of this means that Edge Case has the scale, the software, and the experience to be able holistically assess the risk of any autonomous system, to evaluate the validity of a safety argument, and to help our customers understand and pursue what thresholds they need to meet to make deployment decisions based on safety.</p><p>We will continue to provide that valuable safety engineering support and software alongside the insurance coverage that customers will be able to access via Edge Case Risk Management; all in order to deliver the promise of autonomy.</p><p>We hope you will join us on this journey to recognize and encourage safer autonomy. We have begun building a network of insurance brokers, carriers, actuaries, and technology providers. If you are committed to building autonomy safely from the ground up, we’d love to work with you, too.</p><p><strong>About Edge Case Research:</strong></p><p>At Edge Case Research, we believe that every autonomous vehicle should be built safely from the ground up. We help companies go to market with autonomous mobility that is safe, reliable, and trustworthy. Founded in 2014 by leaders in autonomous vehicle safety, our expert team provides system &amp; safety engineering services, nLoop Live Safety Case software, and risk management solutions to software driver developers, automotive and trucking OEMs, Tier 1 suppliers, insurance providers, and the aerospace and defense industries. For more information, visit <a href="https://www.ecr.ai/">ecr.ai</a> or <a href="https://www.ecr-defense.ai/">ecr-defense.ai</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=496a27e1c27f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Edge Case Defense selected to support DoD safe AI efforts under $249 million BPA]]></title>
            <link>https://edgecaseresearch.medium.com/edge-case-defense-selected-to-support-dod-safe-ai-efforts-under-249-million-bpa-473a9b2edc41?source=rss-e32e1c367ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/473a9b2edc41</guid>
            <category><![CDATA[autonomous-vehicles]]></category>
            <category><![CDATA[defense]]></category>
            <category><![CDATA[safety-engineering]]></category>
            <category><![CDATA[trucking]]></category>
            <category><![CDATA[safety]]></category>
            <dc:creator><![CDATA[Edge Case Research]]></dc:creator>
            <pubDate>Mon, 07 Feb 2022 15:07:31 GMT</pubDate>
            <atom:updated>2022-02-07T17:59:32.568Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Edge Case Defense logo" src="https://cdn-images-1.medium.com/max/1024/1*8ntn2oJAon33QIVNwb8_BA.png" /></figure><p><em>$249 million Blanket Purchase Agreement funding vehicle to allow Edge Case to deploy its industry-leading expertise and software to build safer AI systems for federal agencies</em></p><p>Edge Case Defense is proud to announce that it has been selected to receive a T&amp;E BPA (Blanket Purchase Agreement) to support the U.S. Department of Defense’s Joint Artificial Intelligence Center (<a href="http://ai.mil/">JAIC</a>). This award allows <a href="https://www.ecr-defense.ai/">Edge Case Defense</a> to easily offer its software and lifecycle System Safety Engineering services to DoD and other federal government customers.</p><p>The JAIC’s focus is to enable the implementation of machine learning applications within DoD. This contract vehicle positions the DoD to efficiently and flexibly engage with <a href="https://www.ecr.ai/">Edge Case</a> and other companies to support testing and evaluation of autonomous systems. Its focus on AI Test and Evaluation solutions and Independent Verification &amp; Validation services fit seamlessly into Edge Case Defense’s core competence. It also represents significant, long-term codevelopment opportunities to further develop our technology to expand our reach both inside and outside the federal government.</p><p>Since 2015 Edge Case Research has been engaged in helping our partners in the DoD as well as prime contractors to build safety into autonomous vehicles and other complex software systems. Our team’s unparalleled expertise in both autonomous system safety and the <a href="https://www.dau.edu/cop/armyesoh/DAU%20Sponsored%20Documents/MIL-STD-882E.pdf">MIL-STD-882E</a> standard deliver high-quality risk assessments and smart hazard mitigations to autonomous vehicle programs like Expedient Leader-Follower (ExLF).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*xE6Zh2Of84rph6XO.jpg" /><figcaption><a href="https://www.usarmygvsc.com/new-autonomous-technologies-at-camp-grayling-greatly-reduce-risks/">Expedient Leader-Follower trucks being tested</a> at Fort Grayling, MI in June, 2021.</figcaption></figure><p>Edge Case has received over $15 million in prior R&amp;D funding to develop T&amp;E software in partnership with entities like TRMC. Our nLoop live safety case software supports risk assessments of autonomous systems by providing safety argumentation support and provides a way to monitor level of rigor evidence data from a variety of sources.</p><p><strong>About Edge Case Defense</strong></p><p>At Edge Case Defense, we deliver lifecycle system safety engineering for defense programs. We help our customers identify smart hazard mitigations through MIL-STD-882E conformant safety assessment reports so that they can improve safety without compromising system performance. Edge Case’s streamlined processes were designed by a team holding over 100 combined years of IV&amp;V experience. We incorporate that expertise in nLoop, the first Live Safety Case management software. For more information, visit <a href="https://www.ecr-defense.ai/">ecr-defense.ai</a>.</p><p><strong>About Edge Case Research</strong></p><p>At Edge Case Research, we believe that every autonomous vehicle should be built safely from the ground up. We help companies go to market with autonomous mobility that is safe, reliable, and trustworthy. Founded in 2014 by leaders in autonomous vehicle safety, our expert team provides system &amp; safety engineering services, nLoop Live Safety Case software, and risk management solutions to software driver developers, automotive and trucking OEMs, Tier 1 suppliers, insurance providers, and the aerospace and defense industries. For more information, visit <a href="https://www.ecr.ai/">ecr.ai</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=473a9b2edc41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Benjamin Lewis joins Edge Case Research as Vice President of Insurance]]></title>
            <link>https://edgecaseresearch.medium.com/benjamin-lewis-joins-edge-case-research-as-vice-president-of-insurance-a94555a49446?source=rss-e32e1c367ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/a94555a49446</guid>
            <category><![CDATA[autonomous-cars]]></category>
            <category><![CDATA[insurance]]></category>
            <category><![CDATA[autonomous-vehicles]]></category>
            <category><![CDATA[safety]]></category>
            <dc:creator><![CDATA[Edge Case Research]]></dc:creator>
            <pubDate>Mon, 31 Jan 2022 14:13:59 GMT</pubDate>
            <atom:updated>2022-01-31T14:13:59.249Z</atom:updated>
            <content:encoded><![CDATA[<p>We are excited to announce that Edge Case Research has hired <a href="https://www.linkedin.com/in/rpibenjaminlewis/">Benjamin Lewis</a>, CPCU, as Vice President of Insurance. Ben will lead efforts to offer autonomous vehicle insurance and risk management products and services that build on the company’s existing solutions.</p><p>Ben joins us from Liberty Mutual Insurance, where he most recently served as Senior Director of Automotive &amp; Mobility Strategic Partnerships in the insurer’s Mobility Practice. There, he built and managed strategic relationships with some of the world’s leading autonomy and mobility companies and championed autonomous vehicles as an emerging market, leading Liberty Mutual to write its first risks in the space as an early mover.</p><p>With his innovative thinking, years of experience working at the intersection of autonomy and insurance, and his robust industry relationships, Ben brings valuable insurance domain knowledge to complement the safety engineering expertise and technology Edge Case provides.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yX8bwWAoIupQXQoLwwF5WQ.jpeg" /></figure><p>“We have known Ben for years as a great partner and an insightful professional in the insurance industry. We are now lucky enough to have his experience, expertise, and passion for developing novel solutions for the autonomous vehicle industry at Edge Case, where he will expand our ability to support our customers’ risk management needs.” Edge Case CEO Michael Wagner said.</p><p>Beyond serving the autonomy ecosystem, Edge Case is committed to helping insurance brokers better serve their customers while ensuring that carriers have the right information to navigate the complexities of autonomous vehicle technologies and risks.</p><p>“I am very excited to join the exceptional team at Edge Case as we define, enable, and encourage safe autonomy in collaboration with customers and partners,” said Ben. “We already offer valuable solutions to autonomous vehicle developers, and I am eager to help us expand on that robust foundation to add insurance and risk management solutions that meaningfully support autonomy customers and insurance partners.”</p><p><strong>About Edge Case<br></strong>At Edge Case Research, we believe that every autonomous vehicle should be built safely from the ground up. We help companies go to market with autonomous mobility that is safe, reliable, and trustworthy. Founded in 2014 by leaders in autonomous vehicle safety, our expert team provides system &amp; safety engineering services, nLoop Live Safety Case software, and risk management solutions to software driver developers, automotive and trucking OEMs, Tier 1 suppliers, insurance providers, and the aerospace and defense industries. For more information, visit <a href="https://www.ecr.ai/">ecr.ai</a> or <a href="https://www.ecr-defense.ai/">ecr-defense.ai</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a94555a49446" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Edge Case Research Raises $12M Series A Round to Make Autonomy Safer]]></title>
            <link>https://edgecaseresearch.medium.com/edge-case-research-raises-12m-series-a-round-to-make-autonomy-safer-da36c0374d7a?source=rss-e32e1c367ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/da36c0374d7a</guid>
            <category><![CDATA[investment]]></category>
            <category><![CDATA[edge-case-research]]></category>
            <category><![CDATA[safety-case]]></category>
            <category><![CDATA[autonomous-vehicles]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Edge Case Research]]></dc:creator>
            <pubDate>Wed, 15 Sep 2021 17:54:13 GMT</pubDate>
            <atom:updated>2021-09-15T18:18:28.481Z</atom:updated>
            <content:encoded><![CDATA[<p>by Michael Wagner, CEO, Edge Case Research</p><p>I am excited to announce that over the last year we’ve completed our $12M Series A round. We are pleased that Yabeo Capital, based in Munich, led the round and will now take a seat on our board of directors. We thank our existing investors Ansys, Lockheed Martin Ventures, Blue Tree Allied Angels, and Liberty Mutual Strategic Ventures for their generous ongoing support. And finally, we are excited to welcome Reinforced Ventures, Monozukuri Ventures, and 412 Ventures to the Edge Case team!</p><p>The investment also facilitated the rapid <a href="https://pr-97195.medium.com/edge-case-research-expands-in-the-european-market-aa9981e52768">expansion of our team in Munich, Germany</a> through the addition of the <a href="http://yabeo.de/en/2020/08/05/successful-exit-yabeo-edge-case-research-acquires-machine-learning-competence-centre-terraloupe/">Yabeo portfolio company Terraloupe</a> and its outstanding people and technology. I want to thank our amazing team’s efforts in creating a single, unified Edge Case Research through the challenges presented by the pandemic.</p><p>Our new colleagues in Munich join our amazing team of product developers, software developers, and system safety experts to support our growing customer base in the U.S., Europe, and Asia. While physically separated, it has been incredibly gratifying to see our team come together over the course of the last year and a half.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1gy_U2tfpY54bOMs" /><figcaption>Edge Case’s nLoop product will give users, team leaders, executives, and other stakeholders a way to structure, manage, and view the state of their safety case. Along with direct connections to sources of evidence, this live safety case allows internal and external stakeholders to make informed decisions about safety and risk.</figcaption></figure><p>With investment, we’ve built the nLoop platform and started getting it into the hands of customers in the automotive and defense markets. Our vision for nLoop is ambitious: to provide <a href="https://edgecaseresearch.medium.com/delivering-live-safety-cases-for-an-ever-changing-world-e0c8f454aee2">live safety cases</a>, backed by evidence, to help our customers to define, measure, and communicate the safety of their autonomous system. nLoop enables our customers to communicate risk and safety metrics to stakeholders inside and outside their organization while maintaining the confidentiality and integrity of their intellectual property.</p><p>Of course, in order to fulfill this vision our team has grown and will continue to grow substantially. Edge Case is now about 80 people globally, including seasoned leaders experienced in developing complex software products, and we intend to grow even more. To facilitate that growth, Edge Case is moving into its new headquarters at <a href="https://www.google.com/maps/place/2555+Smallman+St,+Pittsburgh,+PA+15222/@40.4553902,-79.9822602,17z/data=!3m1!4b1!4m5!3m4!1s0x8834f3c46320429f:0xa677a7995d458aac!8m2!3d40.4553861!4d-79.9800715">2555 Smallman Street</a> in Pittsburgh’s Strip District, a hub for autonomous vehicle development.</p><p>We’ve come a long way from the days when we were a handful of Carnegie Mellon engineers working on projects in a small office near campus. Our Safety Solutions team consists of world-class experts in safety engineering from the U.S. Government, the automotive industry, and academia. In addition to working closely with our customers, and continuing to support standards such as UL 4600, the Safety Solutions team makes their expertise available through safety case frameworks available on the nLoop platform.</p><p>As I mentioned, the Edge Case team is continually changing and growing. One important change is that Edge Case’s co-founder, Phil Koopman, has parted ways with us to pursue other opportunities. We wish him the best!</p><p>As recent announcements from our customers indicate, autonomous mobility is progressing rapidly. Autonomy will affect how goods are shipped on highways and how we are driven through our neighborhoods. We’re proud to contribute to the industry to make autonomy safer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da36c0374d7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A User’s Guide to Vehicle Automation Modes]]></title>
            <link>https://edgecaseresearch.medium.com/a-users-guide-to-vehicle-automation-modes-4bdd49b30dc0?source=rss-e32e1c367ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bdd49b30dc0</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[safety]]></category>
            <category><![CDATA[vehicles]]></category>
            <category><![CDATA[self-driving-cars]]></category>
            <category><![CDATA[autonomous-vehicles]]></category>
            <dc:creator><![CDATA[Edge Case Research]]></dc:creator>
            <pubDate>Thu, 28 Jan 2021 01:20:46 GMT</pubDate>
            <atom:updated>2021-01-28T13:31:06.226Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The responsibilities and liability of a self-driving vehicle user</em></p><p>By: Dr. Philip Koopman, Edge Case Research &amp; Carnegie Mellon University</p><figure><img alt="Vehicle Automation Modes. Image CC BY 4.0 https://creativecommons.org/licenses/by/4.0/" src="https://cdn-images-1.medium.com/max/1024/1*nahHivMp4adkczIkljZI8Q.gif" /></figure><p>If you follow self-driving car technology it’s likely you’ve encountered the SAE Levels of automation. The SAE Levels range from 0 to 5, with higher numbers indicating more capable driving automation technology. Unfortunately, in public discussions there is significant confusion and misuse of that terminology. In large part that is because the SAE Levels are primarily based on an engineering view rather than the perspective of a person driving the car.</p><p>We need a different categorization approach. One that emphasizes how drivers and organizations will deploy these vehicles rather than the underlying technology. This is not a replacement for the engineering use of SAE levels, but rather a complementary tool for public discussions of the technology that emphasizes the practical aspects of the driver’s role in vehicle operation.</p><p>If you doubt that another set of terminology is needed, consider the common informal use of the term “Level 2+,” which is undefined by the underlying SAE J3016 standard that sets the SAE Levels. Consider also the fact that different companies mean significantly different things when they say “Level 3.” In some cases Level 3 follows SAE J3016, meaning that the driver is responsible for monitoring vehicle operation and being ready to jump in — even without any notice at all — to take over if something goes wrong. In other cases vehicles described as Level 3 are expected to safely bring themselves to a stop even if the driver does not notice a problem, which is more like a “Level 3+” concept (also undefined by SAE J3016).</p><p><strong>Other Safety</strong></p><p>Even more importantly, the SAE Levels say nothing about all the safety relevant tasks that a human driver does beyond actual driving. For example, someone has to make sure that the kids are buckled into their car seats. To actually deploy such vehicles, we need to cover the whole picture, in which driving is critical but only a piece of the safety puzzle.</p><p><strong>The Four Operational Modes</strong></p><p>In creating a driver-centric description of capabilities, the most important thing is not the details of the technology, but rather what role and responsibility the driver is assigned in overall vehicle operation. We propose four categories of vehicle operation: Assistive, Supervised, Automated, and Autonomous.</p><figure><img alt="Woman driving with both hands on the wheel." src="https://cdn-images-1.medium.com/max/1024/1*HmtPNZdqAMtbMnQooAiTqg.jpeg" /></figure><p><strong>Assistive: </strong><em>A licensed human driver drives, and the vehicle assists.</em></p><ul><li>Human Role: Driving</li><li>Driving: Human</li><li>Driving Safety: Human</li><li>Other Safety: Human</li></ul><p>The technology’s job is to help the driver do better by improving the vehicle’s ability to execute the driver’s commands and reduce the severity of any impending crash.</p><p>This might include anti-lock brakes, stability control, cruise control, and automatic emergency braking. The driver always remains in the loop, exerting at least some form of continuous control over speed, lane keeping, or both. Most passenger vehicles on the road today are Assistive. Generally, this maps to SAE Level 1 and some portions of SAE Level 2.</p><figure><img alt="Woman hands off the steering wheel. Eyes on the road monitoring the vehicle" src="https://cdn-images-1.medium.com/max/1024/1*0i2BodqvEZOoMt8HkCqIUg.jpeg" /></figure><p><strong>Supervised: </strong><em>The vehicle drives, but a human driver is responsible for ensuring safety.</em></p><ul><li>Human Role: Eyes ON Road</li><li>Driving: Vehicle</li><li>Driving Safety: Human</li><li>Other Safety: Human</li></ul><p>Technology normally handles all aspects of the driving task. However, a licensed human driver is responsible for continuous monitoring of driving safety and taking over control instantly if something goes wrong. The driver is not expected to perform a continuous control function such as steering or speed control while in this operating mode. An effective driver monitoring system is required to ensure driver ability to take over when required. Tesla “Autopilot” and GM Super Cruise are examples of Supervised operating modes. Generally, this maps to SAE Levels 2 and 3. Achieving safety will depend on getting sufficient driver engagement and avoiding having the vehicle put the driver into an untenable recovery situation.</p><figure><img alt="Man reading with eyes off the road as vehicle performs driving tasks" src="https://cdn-images-1.medium.com/max/1024/1*d4v_kRYEbWqtdYktuPYcPg.jpeg" /></figure><p><strong>Automated: </strong><em>The vehicle performs the complete driving task.</em></p><ul><li>Human Role: Eyes OFF Road</li><li>Driving: Vehicle</li><li>Driving Safety: Vehicle</li><li>Other Safety: Human</li></ul><p>A human driver is not required to operate the vehicle in this mode. However, a responsible person is required to ensure other aspects of vehicle safety such as buckling up the kids, proper securing of any cargo, and post-crash response. Simply put, in this operation mode the vehicle does the driving, but a responsible human is still the <strong>“captain of the ship”</strong> for handling everything except the driving. In some cases, there might be an expectation that a human driver moves the vehicle under manual control during portions of a trip that are not suitable for Automated operation. Examples of Automated operation include a heavy truck on divided highway portions of its route, and low speed shuttles that require human conductors for passenger safety. Generally this maps to SAE Levels 4 and 5. Achieving safety will depend on the automated driver being able to handle everything that might occur during driving, and ensuring the vehicle takes safe actions even with no driver intervention when its driving capabilities have been exceeded.</p><figure><img alt="No human behind the wheel. Vehicle is driving and is completely capable of operation with no human monitoring." src="https://cdn-images-1.medium.com/max/1024/1*1gAxT7uLk-9h76Jc16RDJA.jpeg" /></figure><p><strong>Autonomous: </strong><em>The whole vehicle is completely capable of operation with no human monitoring</em>.</p><ul><li>Human Role: No Human Driver</li><li>Driving: Vehicle</li><li>Driving Safety: Vehicle</li><li>Other Safety: Vehicle</li></ul><p>The vehicle can complete an entire driving mission under normal circumstances without human supervision. If something goes wrong, the vehicle is entirely responsible for alerting humans that it needs assistance, and for operating safely until that assistance is available. Things that might go wrong include not only encountering unforeseen situations and technology failures, but also flat tires, a battery fire, being hit by another vehicle, or all of these things at once. People in the vehicle, if there are any, might not be licensed drivers, and might not be capable of assuming the role of “captain of the ship.” Examples of Autonomous vehicles might include uncrewed robo-taxis, driverless last mile delivery vehicles, and heavy trucks in which the driver is permitted to be asleep. Achieving safety will depend on the autonomous vehicle being able to handle everything that comes its way, for example according to the UL 4600 safety standard. Generally this maps to SAE Levels 4 and 5 in addition to handling vehicle safety issues beyond the scope of SAE J3016.</p><p><strong>Driver Roles:</strong></p><p>No simple set of descriptive terms like this can be perfect, and this approach will inevitably have its shades of gray. However, it has the distinct advantage that human drivers will have clear expectations of their roles:</p><ul><li>Assistive: Human drives.</li><li>Supervised: Human monitors and takes over if needed.</li><li>Automated: Human can ignore driving, but ensures other aspects of vehicle safety.</li><li>Autonomous: No human involvement needed to ensure safety.</li></ul><p><strong>Driver Liability:</strong></p><p>Another related advantage is that it provides a more straightforward way to describe potential human driver liability:</p><ul><li>Assistive: As with conventional human driving.</li><li>Supervised: The human driver is responsible for safety unless the vehicle does something dangerous that is beyond a reasonable human driver capacity to intervene.</li><li>Automated: The human driver is not responsible for driving errors, but is responsible for non-driving aspects of safety such as passenger safety, proper cargo loading, and post-crash situation management.</li><li>Autonomous: There is no human driver to blame for mistakes.</li></ul><p><strong>Multiple Operational Modes:</strong></p><p>A single vehicle can employ various operational modes across its Operational Design Domain (ODD). What is most important is that at any particular time the vehicle and the driver both understand that the vehicle is in exactly one of the four operational modes so that the driver’s responsibilities remain clear. As a simplified example, the same car might operate as Autonomous in a specially equipped parking garage, Automated on limited access highways, Supervised on designated main roads, and Assistive at other times. In such a car it would be important to ensure that the human driver is aware of and capable of performing accompanying driver responsibilities when modes change.</p><p>We think it would benefit consumers and other stakeholders if discussions regarding vehicle automation capabilities encompassed a driver&#39;s point of view using the terms: Assistive, Supervised, Automated, and Autonomous. That could help reduce confusion and even reduce the loss of life caused by misunderstanding the responsibilities of the driver in different operational modes.</p><p><strong>About Edge Case Research:</strong></p><p>The mission of Edge Case Research is to ensure that everyone stepping into a self-driving car gets a safe ride and that every autonomous vehicle traveling through our neighborhoods is built safely from the ground up. We work closely with our customers to achieve this vision. Our customers demand scalable, data-driven risk management solutions to help them go to market with autonomous mobility that is safe, reliable, and trustworthy. Edge Case delivers value to our customers by packaging the know-how of our team of experts into innovative products that accelerate safety engineering and monitor the safety of fleet operations to inform critical product readiness and underwriting decisions. Edge Case is headquartered in Pittsburgh with an office in Munich, Germany. See more information at <a href="https://edge-case-research.com/">https://www.ecr.ai</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bdd49b30dc0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Honoring our Veterans]]></title>
            <link>https://edgecaseresearch.medium.com/honoring-our-veterans-7e96129cbcc3?source=rss-e32e1c367ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e96129cbcc3</guid>
            <category><![CDATA[safety]]></category>
            <category><![CDATA[defense]]></category>
            <category><![CDATA[autonomous-system]]></category>
            <category><![CDATA[veterans-day]]></category>
            <category><![CDATA[unmanned-systems]]></category>
            <dc:creator><![CDATA[Edge Case Research]]></dc:creator>
            <pubDate>Wed, 11 Nov 2020 15:28:56 GMT</pubDate>
            <atom:updated>2020-11-11T15:38:38.853Z</atom:updated>
            <content:encoded><![CDATA[<h3>Honoring Our Veterans</h3><p><strong><em>Delivering safety for their safety</em></strong></p><p>On this November 11th, Veterans Day, we honor our beloved veterans and share our appreciation for those that served and continue to serve our country with honor and pride. Today we reflect on the many years that we have worked alongside our U.S. military to support the overall mission of advancing autonomous technologies that will modernize the military and keep our warfighters safe. We also take this opportunity to thank our Edge Case veterans including Phil Koopman, CTO, (U.S. Navy Submarine Force 1983–1987), and Eric Felix, Defense Account Manager, (U.S. Army Field Artillery 2010–2016) who honorably served to defend our country and our freedom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*9diMm-hxeq4YBpHXAK3TlQ.jpeg" /><figcaption>Former Captain Eric Felix receives honors for a series of U.S. and Romanian-led joint airborne operations.</figcaption></figure><p>The safety experts at Edge Case have a long history of collaborating with the U.S. Department of Defense and today, we are proud to partner with them on many of the leading-edge AI and unmanned system projects including the U.S. Army’s:</p><ul><li>Autonomous Ground Resupply (AGR) program</li><li>Coalition Assured Autonomous Resupply (CAAR) program</li><li>Expedient Leader Follower (ExLF)</li><li>Route Clearance Interrogation System (RCIS)</li><li>Squad Multipurpose Equipment Transport (SMET) system</li></ul><p>These programs are just a few of our many efforts to ensure safety and dependability are built into innovative vehicles for the future battlefield.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/0*vTOleC3-buBulJzu" /><figcaption><em>Expedient Leader Follower (ExLF) US Army: Edge Case has helped make safety an integral part of Army leader-follower technology, to ensure that warfighters get autonomy they can rely upon.</em></figcaption></figure><p>Our journey with the military started in 2008, when our founders, Michael Wagner and Prof. Philip Koopman, while at Carnegie Mellon’s National Robotics Engineering Center (NREC) began building out a safety case for NREC’s Autonomous Platform Demonstrator (APD) that pioneered autonomous vehicles technologies for the U.S. Army Tank Automotive Research, Development, and Engineering Center (TARDEC). Mike and Phil led this innovative safety program to obtain a groundbreaking Safety Release for this large, fast, and highly capable autonomous vehicle, and they proved their methods could achieve program targets without hindering the vehicle’s advanced capabilities development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MDEgNpzPqykb6ny3.jpg" /><figcaption><em>Photo credit: Carnegie Mellon University NREC’s Autonomous Platform Demonstrator (APD)</em></figcaption></figure><p>The APD team implemented a holistic system safety engineering and test effort for unmanned systems to augment more traditional vehicle test approaches which focused on system level testing. This system level test paradigm breaks down with autonomy as software is both vastly more complex and simultaneously has much greater or total control authority over the vehicle. Our founders leveraged their expertise to implement new autonomous safety best practices and methodologies for the military. Their success resulted in 10 years of follow up projects for the Office of Secretary of Defense that led to the Automated Stress Testing for Autonomy Architectures, as well as the Robustness Inside Out Testing program, which both increased the DoD’s ability to evaluate the inherent complexity of autonomous systems and improve the robustness of real-world systems.</p><p>Mike and Phil launched Edge Case Research realizing the need to continue these efforts to support the development and deployment of autonomous systems outside academia that delivered on safety. Since our founding in 2014, our partnership with the U.S. Army has resulted in numerous advances including the development of an innovative “safety checker” architecture along with safety cases that have iterated with capabilities under development. Both milestones are critical in realizing our shared goal with the DoD to build the necessary foundation for rapid development of autonomous systems while simultaneously achieving safety assurance.</p><p>Our mission for Edge Case Research is to deliver the promise of autonomy. Our team works tirelessly to ensure that warfighters get autonomy they can rely upon. As our veterans are committed to protecting our country’s safety, we are committed partners with the U.S. Department of Defense to help make next-generation military systems more reliable, capable, and safe.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e96129cbcc3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>