BEPA is a company with an idea
Case 1: A Systems Engineering product maintenance project in a small company
A product maintenance project incorporating Engineering Change Management (ECM) and a process for Product Release Management (PRM) is a comprehensive endeavor.
It began with the identification of the ECM process, which involves the systematic review and modification of a product's specifications and documentation. Changes are carefully evaluated for their impact on the entire product lifecycle, from design to disposal. We set up an Engineering Change Request (ECR) role to identify if it was a document change, Bill of Material (BOM) change, or a request for later implementation. We then established a system for handling ECRs for later implementation in a PRM process.
The PRM then takes over to manage the release and distribution of the updated product in timeslots for 3-4 months per release. That included coordinating with various departments to ensure that the new version is manufactured, tested, and delivered effectively.
The final phase involves updating all relevant stakeholders about the changes and ensuring that the product continues to meet regulatory standards and customer expectations. This type of project requires meticulous planning, cross-functional collaboration, and a keen eye for detail to ensure a seamless transition to the new product version.
Case 2: A Systems Engineering New Product Development Project in a medium size Company
A Product Development project typically follows a structured engineering approach to ensure that the final product meets the required specifications and customer expectations.
The project begins with an Operational Concept Description (OCD), which outlines the intended use, operational scenarios, and user interactions with the Product. This is followed by the development of the Functional Architecture, which details the functions the system must perform and the relationships between these functions. The Logical Architecture then maps these functions onto logical statements, defining the system's structure without being tied to physical components. Finally, the Physical Architecture is created, specifying the actual hardware and software components that will be used to implement the system.
Throughout the project, systems engineering methodologies, such as holistic simulation, are applied to break down top-level requirements into sub-system and component requirements, ensuring that each part of the system integrates seamlessly to form a cohesive whole. The project concludes with rigorous testing and validation to confirm that the system performs as intended under real-world conditions.
Case 1: A Systems Engineering product maintenance project in a small company
A product maintenance project incorporating Engineering Change Management (ECM) and a process for Product Release Management (PRM) is a comprehensive endeavor.
It began with the identification of the ECM process, which involves the systematic review and modification of a product's specifications and documentation. Changes are carefully evaluated for their impact on the entire product lifecycle, from design to disposal. We set up an Engineering Change Request (ECR) role to identify if it was a document change, Bill of Material (BOM) change, or a request for later implementation. We then established a system for handling ECRs for later implementation in a PRM process.
The PRM then takes over to manage the release and distribution of the updated product in timeslots for 3-4 months per release. That included coordinating with various departments to ensure that the new version is manufactured, tested, and delivered effectively.
The final phase involves updating all relevant stakeholders about the changes and ensuring that the product continues to meet regulatory standards and customer expectations. This type of project requires meticulous planning, cross-functional collaboration, and a keen eye for detail to ensure a seamless transition to the new product version.
Case 2: A Systems Engineering New Product Development Project in a medium size Company
A Product Development project typically follows a structured engineering approach to ensure that the final product meets the required specifications and customer expectations.
The project begins with an Operational Concept Description (OCD), which outlines the intended use, operational scenarios, and user interactions with the Product. This is followed by the development of the Functional Architecture, which details the functions the system must perform and the relationships between these functions. The Logical Architecture then maps these functions onto logical statements, defining the system's structure without being tied to physical components. Finally, the Physical Architecture is created, specifying the actual hardware and software components that will be used to implement the system.
Throughout the project, systems engineering methodologies, such as holistic simulation, are applied to break down top-level requirements into sub-system and component requirements, ensuring that each part of the system integrates seamlessly to form a cohesive whole. The project concludes with rigorous testing and validation to confirm that the system performs as intended under real-world conditions.
Case 2
Case 3: Aircraft Systems Engineering: Requirements and Interface Management
In the realm of aircraft product development, the completion of this project was a significant milestone that encompassed a broad range of activities and disciplines. The project did involve the design and foundation for manufacture of a new aircraft model, which began with a comprehensive set of requirements.
These requirements were meticulously gathered, structured and managed to ensure that every aspect of the aircraft's performance, safety, and functionality meet the stringent standards of the aviation industry.
Interface management played a crucial role in this process, serving as the critical link between various systems and components. It ensures that all parts of the aircraft work together seamlessly, from the avionics and flight control systems to the landing gear and propulsion.
Throughout the project, rigorous testing and validation are conducted to verify that all requirements are met and that interfaces between different systems are robust and reliable.
Upon finalization, the project culminates in a series of certification processes, demonstrating that the aircraft is ready for mass production and, ultimately, for taking to the skies.
Offices in Vietnam
BEPA VN Office in Vung Tau city: Floor 4, 207 Le Hong Phong, Vung Tau Plaza building, ard 8, Vung Tau city, VN.
BEPA VN Office in Ho Chi Minh city:
92-94-96-98-100/2 Nguyen Cong Tru,
Nguyen Thai Binh ward, District 1,
Ho chi Minh city, VN.
Office in Denmark
Haslegaardsvej 8,
Building A, level 1
8210 Aarhus
Tel. +45 2240 2728
Company address
Case 3: Aircraft Systems Engineering: Requirements and Interface Management
In the realm of aircraft product development, the completion of this project was a significant milestone that encompassed a broad range of activities and disciplines. The project did involve the design and foundation for manufacture of a new aircraft model, which began with a comprehensive set of requirements.
These requirements were meticulously gathered, structured and managed to ensure that every aspect of the aircraft's performance, safety, and functionality meet the stringent standards of the aviation industry.
Interface management played a crucial role in this process, serving as the critical link between various systems and components. It ensures that all parts of the aircraft work together seamlessly, from the avionics and flight control systems to the landing gear and propulsion.
Throughout the project, rigorous testing and validation are conducted to verify that all requirements are met and that interfaces between different systems are robust and reliable.
Upon finalization, the project culminates in a series of certification processes, demonstrating that the aircraft is ready for mass production and, ultimately, for taking to the skies.
Case 3