New System Function – Development of Clear Requirements
Development of Clear Requirements:
Exploring System Functions in Vehicle Feature Development
In the realm of vehicle feature development, it is paramount to clearly define the System Function. Furthermore, this article continues the discussion on how Feature Functions dictate fundamental requirements at the vehicle level, guiding the architecture’s Systems towards optimal performance.
Continuing with the Feature allocation strategy, each executive System receives a tailored requirement, shaping its unique System Function. However, in scenarios where multiple Features demand similar functionalities, the System must adopt a Total Vehicle approach to cater to diverse needs effectively.
Additionally, by examining the interplay between Feature Functions and System Functions, we gain insights into the intricate mechanisms driving innovation in vehicle design and functionality.
Understanding the Significance of System Function in Vehicle Development
It is crucial to note that the focus lies primarily on Functions, Signals, and Usecases at both the Feature and Systems levels. This entails understanding the intricacies of data acquisition, algorithms, power availability, and applications without being tied to any specific technology.
Until the Total Vehicle Function is thoroughly defined and the signals necessary for execution are fully comprehended, Features and Systems remain technology-agnostic. Only then can Subsystem requirements be formulated to accommodate the necessary technology for execution. This approach ensures a holistic understanding and seamless integration of technology into the vehicle development process.
Defining System Function: Key Element in Vehicle Architecture
Defining the System Function is pivotal for the overall Vehicle Architecture. It encapsulates the intended output, defined signals, and information sets crucial for executing higher functions. Leveraging the available technology set and equipped with appropriate algorithms, the System Function efficiently collects and processes predefined data sets from the environment.
At the helm of this process is the Executive System, tasked with managing subsystems to facilitate seamless data acquisition, processing, and communication with interfaces, all aimed at meeting feature requirements. For instance, consider the monitoring of seat belt usage for various seating positions. Regardless of the feature, the System Function remains consistent, adapting to different applications across the vehicle model. This Total Vehicle application underscores the versatility and adaptability of System Function within the vehicle architecture.
Unveiling the Essence of Systems Engineering: A Philosophical Approach - Metaphysics
Delving into Systems Engineering execution methods requires a philosophical lens to define “what it is.” It begins by comprehensively outlining the function, starting from the vehicle level (Feature) down to the System level, ensuring testability. Understanding all applications (Usecases) is imperative, integrating them into the function definition.
Conversely, it’s crucial to understand what Systems Engineering execution isn’t. It’s not tailored for a single use case or failure mode but rather aims at addressing a defined function with specific requirements. It doesn’t follow a top-down development approach or rely solely on off-the-shelf technology. Instead, it involves comparing options for the feature architecture to execute the function effectively.
Moreover, Systems Engineering execution isn’t about optimization until the initial model is capable of fulfilling its intended function. This philosophical perspective underscores the meticulous approach required to define and execute complex systems within vehicle engineering.
Referencing Metaphysics: https://georgedallen.com/unveiling-the-essence-of-engineering-metaphysics-in-the-world-of-creation/
Unveiling the Essence of Systems Engineering: A Philosophical Approach - Epistemology
Once the Feature and System functions are defined, as well as the signal flow and the intended output, only then the “How does it work?” can be looked at. The reasons for it are:
- everything assumed above does not yet have any physical embodiment, i.e. technology agnostic
- all of the failure modes are related to the signals and signals’ flow, i.e. logic and Higher-level implementation algorithm
- this allows to develop the System level Design Failure Modes Analysis documentation, which will drive the Subsystem allocated Requirements
Referencing Epistemology: https://georgedallen.com/epistemology-in-engineering-systemic-knowledge/
Conclusion – System Function Definition
In conclusion, the development of the System level Engineering documentation and analysis work is largely abstract. The parallel development of the of simulation modeling cannot be overstated. This approach facilitates the preparation of necessary documentation and enables simulation-based development, crucial for addressing verification and testing challenges across various environmental conditions, use cases, and failure modes.
Drawing from industry experiences, it’s evident that manufacturers often overlook or misunderstand this critical development phase, resulting in systemic shortcomings. These shortcuts often manifest as incomplete integration of sensors or failure to comprehend all use cases, ultimately impacting vehicle performance and reliability.
The creation of the “first prototype” for the intended function is pivotal, regardless of the technology used, as it serves as a model for refining requirements and capabilities. Only when the function’s capabilities is established can subsystem-level requirements for mechanical, electrical, software, and interfaces be adequately outlined. Whether developed with specific technology or not, addressing limitations and translating requirements for subsequent steps are imperative for seamless system integration and optimal vehicle performance.
References:
- The Systems Engineering Method: https://georgedallen.com/navigating-chaos-systems-engineering-in-vehicle-occupant-sensing/
- 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.
