MBSE Modeler

The opportunity

WSP is seeking an experienced Model-Based Systems Engineering (MBSE) Modeler to support the development, maintenance, and governance of integrated system models for complex transportation, rail, infrastructure, and multidisciplinary engineering programs.

Working with System Architects, Systems Engineers, Requirements Managers, Interface Managers, and subsystem Subject Matter Experts, the successful candidate will translate engineering structures, requirements, functions, and interfaces into a coherent, traceable, and auditable SysML model. The role helps project teams identify integration risks and model inconsistencies before they become design, delivery, cost, or schedule issues.

What you will do

• Translate Product Breakdown Structures (PBS) into logical SysML package structures and model hierarchies.
• Translate PBS and System Breakdown Structures (SBS) into blocks, Block Definition Diagrams, Internal Block Diagrams, and related architectural views.
• Represent safety related functional breakdowns, activities, system behavior, and allocations across system and subsystem levels to permit safety requirement apportionment between subsystems. Interface Hazard analysis and Interface Description Documents illustrations (Flow diagrams and Interface Diagrams)
• Model hardware, software, logical, physical, and functional architectures based on input from architects, systems engineers, and SMEs.
• Create and maintain packages, interface schematics, requirement containers, interface matrices, and traceability relationships.
• Structure requirement containers to support synchronization (import / Exports) with requirements management platforms such as
• IBM DOORS or DOORS Next.
• Maintain sufficient traceability among models, requirements, functions, components, interfaces, to trigger the generation of “Trees of Consequences” by the Requirement Management Tool based on the modification identified in the model up to verification methods, and supporting evidence.
• Apply project modeling conventions, naming standards, configuration controls, and the Configuration Management Plan to maintain consistent model granularity and baselines.
• Perform model audits and impact assessments to identify interface clashes, boundary effects, domino effects, duplicate elements, traceability gaps, and architectural inconsistencies. The Model Audit will be based on the standard audit functions coming with the chosen project MBSE tool or implemented and maintained by the MBSE tool to audit the Model.
• Analyze and report anomalies detected during model development or modification, and support resolution with the responsible technical teams. The MBSE team reactivity is important to be able to detect potential border effects in design modification before any modification is approved and becomes complex to undo.
• Participate in architecture workshops, model reviews, design reviews, interface reviews, and technical assurance activities.
• Generate model reports, diagrams, matrices, and documentation for technical and non-technical stakeholders.
• Contribute to reusable libraries, modeling methods, governance, and continuous improvement of MBSE practices.

Key deliverables

• SysML Model packages and structured model trees
• Block Definition Diagrams,Internal Block Diagrams, Flow Diagrams
• Functional, logical, physical, hardware, and software architecture point of views
• Interface schematics, interface matrices, and internal/external interface definitions
• Requirement containers and traceability structures
• Configuration-controlled model baselines The Modeler collaborates with the MBSE Administrator to stabilize a baseline from the branches and by participating in branch merging sessions to resolve conflict and “Diif” (Differences).
• Model quality, audit, anomaly, and impact-assessment reports including real time reactivity and communication with teh design team when a clash is identified and participation in resolution.
• What you will bring
• Required qualifications and experience
• Bachelor’s degree in Systems Engineering, Software Engineering, Electrical Engineering, Computer Engineering, Mechanical Engineering, Aerospace Engineering, or a related discipline.
• Practical experience developing and maintaining models for complex engineering or technology systems.
• Working knowledge of systems engineering lifecycle processes, requirements management, system architecture, interface management, configuration management, and verification and validation.
• Experience using SysML v1 and/or SysML v2 to represent system structure, behaviour, interfaces, requirements, and allocations.
• Ability to interpret multidisciplinary engineering information and convert it into a structured and auditable model.
• Experience collaborating with architects, systems engineers, discipline leads, SMEs, and project stakeholders.
• Strong written communication, documentation, analytical, and problem-solving skills.
• Technical knowledge and tools
• Experience with one or more MBSE platforms such as Cameo Systems Modeler / MagicDraw, IBM Rhapsody, Capella, Sparx Enterprise Architect, PTC Modeler, or an equivalent SysML-compliant tool.
• Familiarity with requirements management platforms such as IBM DOORS, DOORS Next, or an equivalent system.
• Familiarity with Configuration Management Practices and the notions of CheckOut, Check In branches, tags, merges, diff and conflict resolution. Those competencies are essential for controlled asynchronous delocalized intervention on the models.
• Knowledge of UML is valued. Software engineers with strong UML modeling experience and the ability to apply systems thinking are encouraged to apply.
• Understanding of model governance, reusable libraries, configuration control, model quality checks, and digital engineering practices.

Preferred industry experience

• Rail and transit systems or transportation infrastructure
• Aerospace or avionics
• Defence or military programs
• Industrial plants, production lines, oil and gas facilities, pipelines, or refineries
• Other large-scale, safety-critical, multidisciplinary systems integration programs

Key competencies

• Systems thinking and the ability to understand relationships, dependencies, and change impacts across complex systems.
• Attention to detail, consistency, traceability, and model quality.
• Ability to work effectively without being the subsystem SME, while accurately interpreting and modeling the work of SMEs, System Engineers, and System Architects.
• Clear communication and effective collaboration across technical disciplines and geographically distributed teams.
• Curiosity, sound technical judgment, accountability, and a continuous-improvement mindset.
• Ability to explain model content and findings to both technical and non-technical stakeholders.