Develop New System Content Proposal – Craft Advanced Tech

Develop New Proposal: Craft Advanced Tech:
Introduction - Development of the System Content via Holistic Approach
In the realm of total vehicle content development, defining the intersection of the intended Vehicle functions and physical content is paramount. Sequentially, this article continues the discussion on how the execution of the governing Feature Functions assigned to the System Content bear the development of necessary content for the fundamental requirements at the vehicle level. Fundamentally, the scoping of the project development with holistic comprehension of requirements is the Systems Engineering task.
Generally, the variety of requirements (sets) are coming from various areas related to the Vehicle Lifecycle. Specifically, the Systems Engineering development process captures the Functional and Interface Requirements. Consequently, following with the description of them in User Interfaces in various parts (graphs and tables) of the System Specification.
The Vehicle Lifecycle phases and requirements associated with them:
- Development – preproduction
- Production – Assembly processes / Tooling / Ergonomics / Initial calibration
- Active Utilization – normal use / durability / wear and tear / fatigue
- Environmental Impact
- Post Production – planned-required maintenance / service
- Safety – crash / occupant protection
- Region of sales, specific states and countries
- Other requirements
Furthermore, the advanced Feature may require specifically new functionality. Consequently, it will require a system management of new and carry-over subsystems. Additionally, the System Content will have to be developed and spelled out in the respective System Technical Specification. Then allocated to the respective subsystems for the sourcing and further implementation.
Definition of the System Content:
System Content is: a concert of new and existing subsystems with mechanical and electrical elements of assembly, with their own specific functions and capabilities, however managed by overall algorithms aligned for the system’s specific goals of arranging the proper signal flow from inputs to outputs and ultimately serving the vehicle defined behavior, governed by the Vehicle Feature.
Ordinarily, in some cases, OEMs use an existing electrical and mechanical content to achieve a certain vehicle function, where an onboard ECU would function as processor with specific new logic related to it. Consequently, as an example, for the function of Seat Belt Monitoring on the 2nd row seat, the following Usecase is applied:
The incoming occupant opens the rear door. Then upon seating closes it. The rudimentary Vehicle function is to use the sensor capability in the latch assembly to verify the Seat Belt application, when utilized.
Moreover, this Feature is using already available content and newly created algorithm, which monitors the described activities of the occupant and the elements of the vehicle assembly. Fundamentally, this function is necessary to manifest the engagement of the seat belts on the 2nd row seats to the vehicle. However, the actual occupants’ presence and the proper routing are assumed. Generally, this system has many opportunities for the False Positives. Consequently, it may still work for the Buckle to Ride Feature.
Understanding the Prerequisites for System Content
Consequently, for more complex functions and higher level of reliability, there will be a need for:
- Firstly, employment of the new sensor or sensor arrays and understanding their specific capabilities
- Followed by the development of the library of signals and capabilities to operate using them within the defined logic
- Next, necessary Algorithms for the Data Acquisition, Processing, Analysis and Decision Making placed in the responsible subsystems
- With mapped Communication between the processing units, etc.
- And other elements of “new” technology
Comprehensively, the very initiation of the product development activities should account for all of the described aspects, including:
- Continuous use of the carry-over Hardware and Technology
- Establishment of the available knowledge (sets) related to lessons learned
- Necessary Scoping and planning to assess yet not available information – knowledge which needs to be developed / generated
- Generation of the benchmarks related to the intended Vehicle level function
- In addition, necessity to be open minded and work to requirements, not technology
Understanding the Development Cycles of Scoping and Planning
Initially, the “scoping” of the advanced project should develop steps which would lead to the development of the first system level proposal. Surprisingly to many Team members, the comprehensive development may take two or three preliminary steps related to the description of the highest intended function and allocations to the participating system. Followed by the set of the verification activities – either physical or in some type of simulation environment.
Therefore, starting from abstract set of Usecases transitioned into the defined Vehicle Function, which can be tested, there is a potential for several iterations. Additionally, these iterations maybe related to:
- primarily, the original technology used vs. intended technology
- Then, the total assembly used vs. the potentially different actual content etc.
Finally, the purpose of the original iteration (s) is not to gear toward the technology used in the evaluations, but the development of the high-level requirements, which would correlate to the accepted benchmarks, along with the development documentation.
Moreover, every next iteration would benefit from the previous, hence it is important to scope the goals for each step, aiming to complete the necessary preparations related to the decision making in choosing the technology and the provider of it.
Applied Philosophy - Objectivism in Action
Fundamentally, two Philosophical concepts are driving activities related to the scoping and planning:
- Metaphysics – what it is – the final definition of the proposal with the defined content and documentation of the requirements and all of the defined production development processes, preparation for the Statement of Requirements
- Epistemology – how do you know it will work? – generation of all of the levels of the design and process failure modes along with verification / validation activities, which would cover all of the potential applications and conditions; define the performance and capability margins for the content
Developing the Simulation Capabilities: Employment of Virtualization and AI
Continuing the discussion related to the development of the simulation capabilities and application of AI tools related to the advanced vehicle function, it’s worth mentioning that these capabilities are the paradigm shift for the streamlined development of any vehicle application.
Furthermore, the following notes are applicable to the readiness of the development resources:
- The capability for the adopting and rendering the Total Vehicle Math into the virtual simulation
- The library of developed occupant characters
- The database of the Usecases and Vehicle applications for occupants’ behavior
- The Vehicle Crash related Usecases
- The developed requirements (for perception) related to the sensor data acquisition for the Occupants’ behavior, Vehicle Autonomous conditions, other known Usecases
All of the above is necessary to develop and not yet available as “off the shelf” knowledge sets, waiting for the technical leadership to work on.
Conclusion – System Content proposal Development
In conclusion, driven by the market needs to bring new and advanced Vehicle content, the development teams would benefit greatly by adopting the Philosophy of Objectivism into the Systems Engineering Method. Furthermore, this will allow to make an early assessment of the resources and scope of work related to a specific project goal. Moreover, often with the “complex” problems it becomes obvious that certain knowledge is missing, in order to make progress in the content definition.
Consequently, the definition of proper System Content and verification of its proper functionality is the paramount goal of the preproduction advanced development phase.
Moreover, this “knowledge generation” step often overlooked and actually missed entirely, driving the development toward the available technology and / or supplier. Additionally, missing requirements lead to missing failure modes and result is possibly limited product functional capabilities, actual performance and the unwanted final product issues, i.e. warranty and recalls.
Finally, the sophistication and readiness of the simulation tools is necessary to aid in the rapid development and productionizing of the System Content. Fundamentally, this is the area of the potential growth for all of the OEMs and Supply-base participants.
References:
- The Systems Engineering Method: https://georgedallen.com/navigating-chaos-systems-engineering-in-vehicle-occupant-sensing/
- Develop System Requirements: https://georgedallen.com/new-system-function-development-of-clear-requirements/
- Objectivist Metaphysics: https://georgedallen.com/unveiling-the-essence-of-engineering-metaphysics-in-the-world-of-creation/
- Objectivist Epistemology: https://georgedallen.com/epistemology-in-engineering-systemic-knowledge/
- Development of Prerequisites: https://georgedallen.com/development-of-the-prerequisites-new-passive-safety-features/
- Development of Usecases: https://georgedallen.com/usecases-development-of-the-prerequisites-new-databases/
- Virtualization: https://georgedallen.com/virtual-development-embracing-tomorrow-today/
- “Virtualization” definition: https://en.wikipedia.org/wiki/Virtualization
About George D. Allen Consulting:
George D. Allen Consulting is a pioneering force in driving engineering excellence and innovation within the automotive industry. Led by George D. Allen, a seasoned engineering specialist with an illustrious background in occupant safety and systems development, the company is committed to revolutionizing engineering practices for businesses on the cusp of automotive technology. With a proven track record, tailored solutions, and an unwavering commitment to staying ahead of industry trends, George D. Allen Consulting partners with organizations to create a safer, smarter, and more innovative future. For more information, visit www.GeorgeDAllen.com.
Contact:
Website: www.GeorgeDAllen.com
Email: inquiry@GeorgeDAllen.com
Phone: 248-509-4188
Unlock your engineering potential today. Connect with us for a consultation.