Tag Archive for: ISO 26262

Whether you’re just entering the automotive market or looking to improve your development process, you’ll need to become extremely familiar with the ISO 26262 standard.

In 2011, ISO 26262 was created to set the standard for the automotive industry and its suppliers around functional safety in electrical and electronic systems development. To address the industry’s rapid evolution and to ensure that these new electronic functions remain functionally safe in the new environment, the International Organization for Standardization (ISO) recently introduced a second edition of ISO 26262 in December 2018.

There are plenty of updates to sort through in the ISO 26262 2018 version, from building motorcycles to providing more guidance for the semiconductor industry.

Given that the first edition of ISO 26262 hung around for roughly seven years before it received an update, you can expect the most recent version to be the standard for driving quality and reducing risk in automotive functional safety for at least the foreseeable future.

What follows is a non-comprehensive overview to help familiarize you with important ISO 26262 second edition updates. However, it’s imperative that developers for the automotive electronics industry independently study and understand the updates and how their process must evolve to accommodate.

Expansion of the ISO 26262’s Scope

With the implementation of the second edition of ISO 26262, all road vehicles are now included – not just those with four wheels and a maximum vehicle gross mass of up to 3500 kg, as was the case in the first edition.

Motorcycles, trucks, buses, trailers and semi-trailers are now all covered in detail. Your development teams will need to familiarize themselves with the specifics. This webinar from Automotive World provides a good summation of the major changes with a particular focus on motorcycle and commercial vehicle development, and we’ll quickly touch on some of the key points.

Whereas passenger vehicles must adhere to an Automotive Safety Integrity Level (ASIL), the latest version of ISO 26262 introduces a Motorcycle Safety Integrity Level (MSIL). And, as such, the hazard analysis and risk assessment for motorcycles been altered to account for the differences. One thing worth noting is since motorcycles are so unique in their performance, there’s a larger emphasis placed on the responsibility of the rider versus the machine itself. For instance, whereas most cars are expected to still perform well in ice and snow, motorcycles are not, and so if a rider makes the choice to drive in those conditions, they are purposely accepting a higher degree of risk.

Since trucks and buses, on the other hand, are primarily defined by their larger size and mass, those factors tie into their controllability and, therefore, exposure to risk. For example, when a large truck is loaded with cargo, it’s going to have few issues with things like wheel spin on a steep hill than when it’s completely empty. And because different trucks, buses and semi-trailers all have unique purposes for use (for instance, long-haul semi-trucks versus city buses) and are typically exposed to different conditions and environments, the second edition of ISO 26262 makes distinctions between the base vehicle types of each. In terms of controllability, for example, concrete trucks should be able to withstand something like an unpaved construction site, whereas buses don’t regularly encounter that sort of terrain.

Software Tools Confidence Levels

Development software that’s used to create components for automotive systems must be qualified to do its job in a functional safety design environment. The qualification and classification requirements are described in Clause 11 of ISO 26262, Part 8. Software tools receive a certified qualification report if they are fit for purpose.

It’s worth noting that Jama Connect™ has already been certified fit for developing safety-related products according to ISO 26262 (up to ASIL D) by internationally-recognized testing body TÜV SÜD. That means Jama customers can use the TÜV SÜD certificate as an argument for software solution qualification in projects, instead of having to spend time qualifying it themselves. Jama is the first vendor that is both SaaS and Agile to receive the certification. You can read more about the benefits of this distinction here.

Learn how Jama Software worked with TÜV SÜD on our ISO 26262 certification process, and how you can lower the costs and risks of complying with functional safety standards, by watching our webinar.

Functional Safety and Cybersecurity

In response to increasing security concerns in connected devices in automobiles, ISO 26262 now requires a management plan that incorporates effective communication channels between functional safety and cybersecurity. These necessary channels have been identified at both the functional safety management level and at the system level for product development.

Guidelines for Semiconductors

The first edition of ISO 26262 did not include specific guidelines for semiconductors used in automotive application. This caused some confusion and led many automotive teams to create their own functional safety requirements for their semiconductor suppliers.

Now, a new section provides guidelines on and definitions for semiconductor components and semiconductor technologies used in automotive application. This should not only eliminate uncertainty, but also create uniformity when it comes to the design, verification and validation of semiconductors for the automotive industry.

What’s Not Included

One thing that was left out of the second edition is “the non-systematic and random safety issues that will occur with autonomous systems using neural networks.” Semiconductor Engineering explains that this is because a new standard coming later this year – SOTIF, Safety Of The Intended Functionality – will include new automation technologies for things like autonomous vehicles not covered in ISO 26262:2018.

To further assist in mitigating risks in the development process and maintaining compliance with automotive functional safety standards, learn how to mitigate common ISO 26262 mistakes with our whitepaper, “Top 15 ISO 26262 Snafus.” 

Complex development projects are a little like putting together a massive jigsaw puzzle: All the pieces are there, but sometimes how they fit together doesn’t become clear until real progress is already made.

The complexity is magnified when the project in question involves intricate microelectronics, software with billions of lines of code and hundreds of development teams who must work harmoniously to ensure functional safety standards are met. Not to mention hitting moving regulatory targets and the ever-present pressure to quickly deliver a complete, industry-compliant product to market.

We’re talking about a technology that not long ago was the stuff of science fiction; autonomous vehicles, systems for which code failure can lead to actual tragedy.

Bringing Teams (and Data) Together

When developing for a system with so many moving parts, every member of the development team using the same processes and platforms is a must to ensure safety compliance. To hedge against mistakes, teams must also be in sync, irrespective of core skill set or geography.

For companies whose businesses are based on constant innovation, getting all of these ducks in a row is a challenge.

As we detail at length in our recent paper, Driving Compliance with Functional Safety Standards, a Fortune 100 semiconductor company recently faced many of these hurdles, and deployed Jama Software to help clear them.

The semiconductor company knew this, and put together an integrated ALM solution supporting ISO 26262 compliance with Jama Software at its core.

Simplification as a Productivity Booster

Standardization of processes includes reducing oversized sets of tools and applications into a manageable roster of best-in-class solutions. Eliminating cumbersome or unnecessary apps enhances process efficiency for development teams at every stage.

The ALM solution they deployed enabled end-to-end requirements, functions, implementations and tests throughout the life-cycle process, as well as providing support for new functional safety and quality regulations, ensuring development teams can pass product audits and avoid costly delays due to rework.

The result was a well-oiled development machine. By hitting requirements the first time, the semiconductor company was able to accelerate its development cycles, delivering better finished products while achieving higher customer satisfaction.

Incorporating the proper toolsets to track development and document product safety compliance— a necessary step to avoid being buried by the challenges in a complex development project— further facilitated the process.

The standardization of toolsets and platforms meant that with each handoff on the developer chain, the teams could see their counterparts were all following processes as laid out by functional safety requirements.

Projects of this magnitude inherently put pressure on developers to keep their eye on the prize without being distracted by the countless shiny objects drifting across their line of sight. By simplifying processes, homing in on the best tools for the job and facilitating communication with partners and consortiums, development teams can tend to their own gardens.

Download "Driving Compliance with Functional Safety Standards for Software-Based Automotive Components" Now

On today’s fast moving road to innovation requirements management can feel like a burdensome, yet necessary evil. For those of you who manage requirements with spreadsheets, word docs and power point, this process can feel even more unwieldy. Possibly worse? Using a heavy-handed tool like DOORS that adds extra overhead and requires additional skillsets for an already complex process. As products get smarter and connected, requirements management will only become more necessary. But it doesn’t need to be evil.

How? One way is by making sure everyone is working from the same, up-to-date information. Doing so lessens the burdens around requirements reviews. You can eliminate the waiting for the necessary stakeholders to provide input, or give approval. Teams can understand change as it happens, and analyze the up- or downstream impact of that change BEFORE change happens.

Why does it matter? The increased burden of regulations and compliance adds additional overhead to the product development process. Especially in the automotive industry where we are seeing rapid growth and leaps in innovation.  Organizations who haven’t had to confront functional safety standards are having to learn regulatory standards, like ISO 26262, on the fly without missing deadlines or features to deliver on time for their customer.

Part of that additional overhead comes from how these teams are managing requirements and tracing validation & verification back to their requirements. Often times teams retroactively trace their data. With a solution like Jama you can pre-build your relationships, so traceability is automated, reducing the manual effort associated with building your traceability, and reducing your regulatory overhead in the process.

Bonus points for using a “fit for purpose” certified solution. A certified solution reduces the manual effort associated with validating your process for ISO 26262 Certification. As AFuzion CEO Vance Hilderman states: “Products labeled ‘safety-critical’ used to be a small niche, but today almost all devices are critical, with many requiring adherence to certification standards…We need to validate and qualify not just the software we build for our client but our development tools as well,” Read more about the Jama Validation and Software Compliance Kit.

In the end, the “old” way of working doesn’t fit the direction of the industry. Legacy tools and manual processes can’t keep up with market demands. You have too much to do to rely on an outdated way of working. If a modern requirements management solution can help you ease regulatory burdens by streamlining traceability, resulting in a more connected way of working that helps you understand the impact of change and can also provide a platform to shorten the requirements review process, isn’t that worth considering?

See Jama in action today! Check out our completely free 30-day Jama trial.

When I joined Jama as CEO earlier this year, I was excited to become part of a team that was passionate about our customers and solving their problems. The companies we get to work with are a major reason I wanted to join Jama to begin with — it’s an honor and a thrill to partner with them as they build products that will change their industries and the economy. I know I’m not alone in that enthusiasm: As I met individually with every employee during my first three months on the job, over and over again “our customers” was a top reason people cited for coming to work here.

Market Forces

Our customers span an array of critical industries — aerospace, financial and consulting services, medical devices, government, semiconductor, consumer electronics and automotive, to name a few. I’ve now had the privilege of meeting with dozens of them, and I’ve consistently heard them describe the following market forces in play:

The new generation of smart, connected products is increasing competition.

For the first time ever, when consumers buy something new, whether a phone, a thermostat or a car, they expect its capabilities to improve over time. They expect new features over the lifetime of the product, automatic fixes where there were previously recalls, and unprecedented options for customization. With each release of Jama, we’re rolling out new features and improvements that focus on enabling innovation for our customers. We invested in building our REST API to add more even customization and extend the functionality of our solution.

Increasing complexity and new regulation add new challenges.

Development cycles are more complicated than before, requiring close coordination of hardware and software teams, often using different tools and methodologies. Connected products introduce new security risks, often into industries that were previously immune to regulatory compliance. As software becomes an increasingly critical component of new cars, the automotive industry has responded with new compliance regulations such as ISO26262, and so have we. This year we achieved ISO 26262 fit-for-purpose certification by TÜV SÜD to give our customers confidence as they navigate the path to compliance in their product development process.

Systems development teams require a purpose-built product development platform and must take a continuous engineering approach to create products for the modern world.

ALM was built for software, PLM was built for hardware, but today’s product teams require a unified set of capabilities. Teams need contextual, ongoing collaboration and a single source of truth for their data and requirements. In June, we released Jama 8, kicking off a series of releases that will build on our core traceability and collaboration features. We’re also investing in our product ecosystem with the launch of our Partner Alliance Program, working with best-of-breed solution providers to better serve our customers.

At face value, these challenges are daunting. But we get to see our customers overcome them each day through disciplined, modern management of their development processes, which lets them better capitalize on industry trends. As they work to deliver the life- and economy-critical products that are going to change the way we live, we’re glad to be their partners and are eager to foster their success every step of the way.

Detroit, MI — April 12, 2016 —Jama Software –a product-development solution for automotive component suppliers developing complex systems— today announced at the 2016 Society of Automotive Engineers (SAE) World Congress, a partnership with an internationally recognized ISO 26262 testing body to obtain ISO 26262 “Fit-for-Purpose” certification.
Accreditation for the Jama solution will give automotive OEM and suppliers assurance that the workflows they follow to define, build and test automotive related products in the Jama solution meet critical functional safety requirements.
The company will also host a display booth (Booth 525) to demonstrate how its core functionality, including traceability, requirements verification and validation, and change management, can be easily configured to meet functional safety standards and processes including ISO 26262 and SPICE. As part of its tooling for safety-critical development, the Jama solution will continue to deliver a comprehensive tool for auditable traceability across developments phases.
“There’s pressure across the automotive original equipment manufacturer (OEMs) and supplier ecosystem to address this challenge of increased complexity along with functional safety. They don’t want lose their competitive advantage so they are seeking modern solutions that are both innovative and certified” said Derywn Harris, Jama Director of Product Marketing and co-founder.
The ISO 26262 standard has requirements that are challenging to interpret and implement. As a requirements management tool vendor, Jama pursued functional safety certification to instill confidence in its users that the software won’t introduce problems when developing to this standard.
“Certification implies a certain rigor in our own process along with additional documentation that we are satisfied will help automotive customers reduce risk of liability,” said Harris. “Too often, traceability is an afterthought, to be completed in hindsight after project completion. With Jama, companies can avoid that via built-in attention to process, decision making and change analysis in real time.”
Interested in learning more about Jama? Try it for free.