About SE-Training
Systems Engineering and Project Management are core engineering disciplines used to enable the delivery of complex projects within schedule and cost expectations.
Delivering complex projects demands cross-functional engineering disciplines such as Systems Engineering, Project Management, Safety Engineering, Product Development and Design Thinking. SE-Training has been founded to offer specifically tailored solutions that support the drive, ambition and success in providing innovate and high-quality products and services.
There are a high number of engineering organisations based across Europe with diverse needs; SE-Training addresses these unique needs through expert project coaching, process development, enterprise organisational design & training courses provided by expert engineering professionals and academics.
Systems Architecting Course Objectives
- What is systems architecture and how does it differ from the system design?
- How does systems architecture relate to Systems and Holistic Thinking?
- What makes a good architecture: how many architectures do we need?
- What makes up a good architecture so important in the context of complex systems?
- Why are Interfaces such a fundamental concept in Systems Architectures?
- What is the relationship between the Operational Architecture and systems control?
- Can/should we develop the architectures for a system and its Digital Twin together?
- How does it help with decision making for an uncertain development environment?
- Why is it important to develop variants and provide variation points and how do they relate to the interfaces?
- What is a logical and repeatable methodology to develop architectures?
- How can we model the architectures? Do we need MBSE? Do we need tools?
- How can we ensure that the models are consistent and connected?
- Where can one customise the architectures?
- When is an agile approach permissible, when should you take extreme caution?
- How do architectures help developing the system for safety, reliability, availability, maintainability, and inspectability?
- Why is it important to separate the system’s (sometimes called “logical”) from the physical architectures?
- How do all architecture map to the others? Why is mapping a powerful mechanism in developing for complexity?
- What is the timing relationship between the various system (logical) architectures and the physical design?
Schedule
Day 1
- 09:00 - Introduction: Systems Thinking, Architectures and Architects
- 11:00 - Break
- 11:15 - Workshop: Context Analysis
- 12:15 - Lunch
- 13:00 - Operational Architecture
- 15:00 - Break
- 15:15 - Workshop: Operational Architecture
Day 2
- 09:00 - Functional Architecture
- 11:00 - Break
- 11:15 - Workshop: Functional Architecture
- 12:15 - Lunch
- 13:00 - Deriving Operational, Functional and Performance Requirements
- 15:00 - Break
- 15:15 - Workshop: Deriving Requirements and Verification Planning
Day 3
- 09:00 - Logical Architecture and Logical Interfaces
- 11:00 - Break
- 11:15 - Workshop: Logical Architecture and Logical Interfaces
- 12:15 - Lunch
- 13:00 - Physical Architecture, Integration and Physical Interfaces
- 15:00 - Break
- 15:15 - Workshop: Physical Architecture, Integration and Physical Interfaces
Trainer Bio:
Marco has had many roles in Systems Engineering: Professor at a technical university, Consultant, and Work in the development of complex systems for large scale research programmes and automotive innovation projects.
Professional Experience:
- Professor of Systems Engineering at TH Ingolstadt
- Management of projectglobe ltd, London, a consultancy specialising in the support of research driven industry (automotive and robotics) and publicly funded projects (nuclear fusion research).
- Expert in model-based systems engineering and information modelling.
- Head of development for CLOSE, a MBSE methodology based on a semantic graph that integrates Experimentable Digital Twins for reducing cycle times.
- Inventor of a fractal data model that allows for unlimited scalability in managing complex information from any domain.