Beyond BIM: Data Driven Construction_Part 6_System Engineering apply to Construction

System Engineering

SE coordinate and integrate teams, comprised of performers accros varied technical disciplines, to deliver solutions while addressing challenges dealing with increased system complexity.

1. Interdisciplinary Approach:

• Systems engineering integrates knowledge and techniques from multiple engineering disciplines, such as mechanical, electrical, software, and industrial engineering, as well as other fields like mathematics, physics, and economics.

2. Holistic Perspective:

• It takes a holistic view of systems, considering not only individual components but also their interactions, dependencies, and emergent behaviors as a whole.

3. Lifecycle Focus:

• Systems engineering addresses the entire lifecycle of a system, from concept and requirements definition through design, development, testing, production, operation, and maintenance to disposal.

4. Requirements Management:

• It involves eliciting, analyzing, documenting, and managing stakeholder requirements to ensure that the system meets the needs and expectations of its users.

5. Systems Thinking:

• Systems engineers apply systems thinking principles to understand complex relationships within systems and identify opportunities for optimization and improvement.

6. Risk Management:

• It includes identifying potential risks and uncertainties associated with the system and developing strategies to mitigate or manage them effectively.

7. Modeling and Simulation:

• Systems engineers use modeling and simulation tools to represent, analyze, and validate system designs and behaviors before physical implementation, reducing costs and risks.

8. Configuration Management:

• It involves managing changes to the system's design and configuration throughout its lifecycle to ensure consistency, traceability, and control.

9. Verification and Validation:

• Systems engineers verify that the system meets its requirements and validate that it performs as intended under real-world conditions.

10. Continuous Improvement:

• Systems engineering emphasizes continuous learning and improvement, using feedback from previous projects to refine processes and methodologies.

System Engineering V Model in Construction

The construction industry is witnessing unprecedented levels of complexity in its projects, driven by advanced architectural designs and engineering requirements. Traditional document-based approaches to information management are proving insufficient to handle the escalating volume and intricacy of data. Model-Based Systems Engineering (MBSE) offers a robust alternative by employing models to encapsulate the diverse aspects of system development.

While the V-model is commonly associated with software development, its principles can be adapted and applied to other fields, including construction projects. Let's see how the V-model can be utilized in the context of construction:

1. Requirements Analysis:

• Top of the "V": At the top of the V-model, the project requirements are gathered, analyzed, and documented. This includes client needs, regulatory requirements, budget constraints, and project objectives.

2. Design Phase:

• Left Branch of the "V": Based on the requirements, the design phase involves creating detailed plans and specifications for the construction project. This encompasses architectural, structural, mechanical, electrical, and other design aspects.

3. Detailed Design Verification:

• Bottom of the "V" (Left Branch): Once the detailed design is completed, verification activities are carried out to ensure that the design meets the specified requirements. This may involve peer reviews, design walkthroughs, and technical analysis.

4. Implementation (Construction):

• Bottom of the "V" (Center): The construction phase involves the physical realization of the design. Contractors and construction teams execute the building process according to the approved design documents.

5. Integration and System Testing:

• Bottom of the "V" (Right Branch): As construction progresses, integration testing is performed to ensure that individual components of the project (e.g., structural elements, mechanical systems) integrate correctly and function as intended.

6. Validation and Acceptance Testing:

• Top of the "V" (Right Branch): Once construction is complete, validation and acceptance testing are conducted to verify that the constructed project meets the client's requirements and expectations. This may involve inspections, performance testing, and client walkthroughs.

(MBSE) Model Based System Engineering

Model-Based Systems Engineering (MBSE) is a methodology that employs models to support the entire lifecycle of complex systems. This approach shifts the focus from traditional document-based methods to the use of detailed, integrated models that represent the various aspects of the system being developed. MBSE has emerged as a powerful methodology that utilizes comprehensive models to support the entire lifecycle of complex systems. The increasing complexity of construction projects, both in architecture and engineering, necessitates innovative information management strategies.

The intention of this article is to make a first and slight approximation, where I will analyze the main concepts of the methodology, in order to be able to put on the table the feasibility in complex construction projects.

Concepts

Systems: Is a demarcated part of the things around us and the connection between these things, is a set of interacting or interdependent components forming an integrated whole, organized to achieve a specific purpose. Systems can be natural or man-made, simple or complex, and they operate within an environment and are influenced by external factors.

Models: simplified representation of a system, object, phenomenon, or process, designed to describe, explain, predict, or control its behavior or characteristics.

Information Building Blocks: In order to describe a system and it is creation in a unambiguous and cohesive manner, a common language is need it. A formal language means that computers can interpret information stored in this language.

For system engineering models, it is use a formal language that use 2 types of information: elements and relations.

Elements: refers to a fundamental or discrete component of a system. These elements can be physical parts, software modules, processes, or even organizational units that, when combined and interacting, form the complete system.

Types of Elements:

• Physycal Objects (Structural Wall)
• Function of a system (Protection against floods)
• Information (Management Plan)
• Space (Limited Construction Site)
• Objective (0 Accidents on site)
• Activity (Pouring Concrete)

Types of relations:

• ...is executor of....
• ...is part of...
• ...is a type of...
• ...has a part of...
• ....is executed by....

Is important to distinguish between Software Models that describe how the software should work, and the Content Model which arise through applying the software. System Engineering model is usually a combination of both models.

Model Based vs Document Based

As it has been told, model based is a representation of the reality n computer model. This approach instead of the Document Based method allows us to have better clarity and visualizations of the information, consistency and synchronication, easy versioning an updates, possible automation and analysis of the data, collaboration between users, as others. In cons we can have learning curve, tool/technology depending, version control challenge, accessibility.

MBSE - Tools | Language | Methodology

Model-Based Systems Engineering (MBSE) utilizes various tools, languages, and processes to support the development and management of complex systems.

Tools

Modeling Tools: These tools provide graphical interfaces and frameworks for creating, editing, and analyzing system models. (Cameo o MatLab)

Requirements Management Tools: These tools facilitate the capture, analysis, and traceability of system requirements throughout the development lifecycle. (DOORS o Jama connect)

Simulation and Analysis Tools: These tools enable engineers to simulate system behavior, perform analysis, and validate system designs. (AnyLogic o ANSYS)

Languages

Systems Modeling Language (SysML): SysML is a graphical modeling language used in MBSE to represent system architectures, requirements, behaviors, and relationships among system elements

Unified Modeling Language (UML): While originally developed for software engineering, UML diagrams are often used in MBSE to represent aspects of system architecture, behavior, and interactions

Domain-Specific Languages (DSLs): DSLs are specialized languages tailored to specific domains or industries

Methodology:

Requirements Engineering: Involves eliciting, analyzing, documenting, and managing system requirements using MBSE tools and techniques.

System Architecture and Design: Entails creating system architecture models using SysML or other modeling languages to represent system components, interfaces, and interactions.

Model Verification and Validation: Involves verifying that the system model accurately represents the desired system behavior and validating that the system meets its requirements.

Model-Based Testing: Utilizes system models to generate test cases, execute tests, and evaluate system behavior against expected outcomes.

Configuration Management: Encompasses managing changes to system models, tracking version control, and ensuring the consistency and integrity of system artifacts throughout the development lifecycle.

Conclusions

1. Models serve as a single source of truth, ensuring consistency and traceability of information throughout the project lifecycle.
2. MBSE is an efficient approach to rationalize complex systems development as a Mega Project.
3. The system model connects al engineering disciplines and provides full traceability.
4. MBSE allows engineers/architects to focus on the product rather than documentation.
5. Emphasizing verification and validation activities early in the project lifecycle, issues and discrepancies can be identified and addressed promptly, reducing the likelihood of costly rework later on.
6. The structured approach of the V-model ensures that all project requirements are thoroughly verified and validated, resulting in a higher quality end product.
7. Clear documentation of requirements and design specifications facilitates communication among project stakeholders, including clients, designers, contractors, and regulatory authorities.
8. Systematically verifying and validating project components throughout the construction process, risks associated with design errors, construction defects, and non-compliance with regulations can be mitigated.
9. The V-model promotes traceability between project requirements, design decisions, construction activities, and testing results, enabling better accountability and project management.
10. The V model focuses on verification and validation activities early in the life cycle thereby enhancing the probability of building an error-free and good quality product.