For automotive manufacturers, compliance to safety standards is important, but it is not the only factor when delivering safe and reliable products to market. To achieve compliance, organizations need defined processes for automotive development and production and detailed traceability, from the high-level user needs through to test management.
In the automotive industry, the cost of being late to market is not just about your bottom line or market share. Today’s consumers have high expectations and won’t have the patience to wait for your solution. Leaders seek to spend less time on paperwork and more on innovation as part of an effort to streamline their product development and simplify compliance.
Over the coming months, we’ll be publishing a 6-part series on best practices for automotive development and how Jama Connect for Automotive can help teams align to industry standards, simplify functional safety compliance processes, and accelerate time to market. Below you’ll find a description of what you can expect from this series, and what topics will be covered.
Part I: Thursday, September 10th: Automotive Spice (ASPICE)
Modern automobiles are complex systems of systems that must be reliable and safe. One of the ways to increase reliability and safety is for automotive OEMs and suppliers to follow established development processes. In this post, we’ll discuss how Jama Connect for Automotive aligns with Automotive Spice (ASPICE) and other regulatory standards.
Part II: Thursday, September 17th: Functional Safety (ISO 26262)
Functional safety is a key part of the overall safety of a system or piece of equipment in automotive development. Functional safety is crucial for automotive developers who aim to eliminate risk. In this post, we’ll detail how automotive development teams can build safety-critical products, while accelerating time to market with frameworks and templates aligned to functional safety industry standards.
Part III: Thursday, September 24th: Collaboration Across the Ecosystem
Effective collaboration with your customers and suppliers is crucial for automotive developers. In this blog post, we’ll discuss how with Jama Connect for Automotive, developers are able to collaborate across the ecosystem with requirements exchange, including standard Req-IF based data exchange.We’ll demonstrate how automotive developers can use Jama Connect for Automotive while effectively interfacing with other requirements management tools, avoid manual rework, and verify that all requirements are met, regardless of their original source.
Part IV: Thursday, October 1st: IATF 16949
IATF 16949:2016 (replaces ISO/TS 16949:2009) is a standard that establishes the requirements for a Quality Management System (QMS) in automotive development. In this blog post, we’ll discuss how Jama Connect for Automotive aligns with IATF 16949 and how developers can speed development with a platform designed specifically for automotive development.
Part V: Thursday, October 8th: TÜV SÜD
Jama Connect is certified by internationally recognized testing body, TÜV SÜD, as suitable for use in the development of safety-related software according to EN 50128, IEC 61508, and/or ISO 26262 up to SIL 3 or ASIL D. Jama Software provides a certification by TÜV SÜD for each cloud and self-hosted release. In this post, we’ll discuss what this certification means, and how it can help your team.
Part VI: Thursday, October 15th: Requirements Engineering for Remote Automotive Teams
In the final post of our 6-part series, we’ll discuss how to increase early stakeholder visibility and participation in the review process. We’ll demonstrate how teams can leverage Jama Connect for Automotive to exchange requirements data to collaborate with remote engineering teams, customers, and suppliers.