Skip to content
Tagged articles

Systems Engineering

23 articles · Page 1 of 1
Fighter's World
Fighter's World
Nov 3, 2026 · Industry Insights

Workflow, Not Workers: Palantir CTO Reveals Why AI Fails to Scale Enterprise Productivity

Palantir CTO Shyam Sankar argues that enterprise AI value comes from redesigning workflows, not just boosting individual productivity, introducing dual flywheels for model intelligence and business productivity, and emphasizing operational learning, ontology, and systems engineering to turn model capabilities into sustained economic value.

AI ProductivityEnterprise AIForward-Deployed Engineering
0 likes · 36 min read
Workflow, Not Workers: Palantir CTO Reveals Why AI Fails to Scale Enterprise Productivity
Leo Talks Systems Thinking
Leo Talks Systems Thinking
Nov 2, 2026 · Fundamentals

Why UML/SysML Modeling Matters: Resolving Ambiguity, Dependencies, and Change Impact

This article traces the historical origins of UML and SysML to explain why modeling languages were created: to resolve semantic conflicts in software design, address UML's inability to handle hardware constraints and quantitative analysis, and provide a rigorous way to capture system dependencies that text documents cannot, offering three concrete signals for when modeling is necessary.

SysMLSystems EngineeringUML
0 likes · 16 min read
Why UML/SysML Modeling Matters: Resolving Ambiguity, Dependencies, and Change Impact
Leo Talks Systems Thinking
Leo Talks Systems Thinking
Oct 23, 2026 · Fundamentals

Architecture Beyond Diagrams: ISO 42010's Meta-Model for Stakeholder Conflict Resolution

This article explains ISO 42010's architecture meta-model, showing that architecture starts with stakeholder concerns and conflicts, not structure diagrams, and details how viewpoints, views, and architecture descriptions address concerns, using an automotive domain controller case study to illustrate trade-offs and the architect's four core tasks.

ISO 42010Systems Engineeringarchitecture decision records
0 likes · 24 min read
Architecture Beyond Diagrams: ISO 42010's Meta-Model for Stakeholder Conflict Resolution
Leo Talks Systems Thinking
Leo Talks Systems Thinking
Oct 20, 2026 · R&D Management

Six Steps to System Concept Design: From User Needs to Frozen Baseline

This article presents a six-step methodology for creating system concept documents based on the Arcadia framework, distinguishing concepts from requirements and architecture through operational analysis, boundary definition, black-box capabilities, trade studies, and baseline freezing with concrete automotive examples.

Arcadia methodSystems Engineeringarchitecture description
0 likes · 17 min read
Six Steps to System Concept Design: From User Needs to Frozen Baseline
Leo Talks Systems Thinking
Leo Talks Systems Thinking
Oct 10, 2026 · R&D Management

Architecture's Hidden Cost: Not Wrong Tech, But Misaligned Concepts

This article reveals how ambiguous concept boundaries—not technical mistakes—drive architecture costs, using automotive examples to show how clarifying intension, extension, and system concepts enables clear responsibilities, shared language, risk analysis, and organizational knowledge.

ISO 15288Systems Engineeringarchitecture
0 likes · 15 min read
Architecture's Hidden Cost: Not Wrong Tech, But Misaligned Concepts
Data Bricklaying Diary
Data Bricklaying Diary
Oct 7, 2026 · R&D Management

Mission Engineering 12: Scaling from One Cup to Ten — What Carries Over to Complex Delivery?

This article explores how mission engineering methods scale from brewing a single cup of coffee to serving ten people and fulfilling complex orders, emphasizing that while definitions and recipes can be reused, goals, timing, resource capacity, handoffs, and success evidence must be re-validated for each new scenario, using OPM and ontology to trace cross-system collaboration and emergence.

EmergenceOPMProcess Scaling
0 likes · 24 min read
Mission Engineering 12: Scaling from One Cup to Ten — What Carries Over to Complex Delivery?
Data Bricklaying Diary
Data Bricklaying Diary
Oct 4, 2026 · Fundamentals

Mission Engineering 07: Baseline First — Test Process Changes Before Buying Gear

This article demonstrates Mission Engineering principles by using a morning coffee routine to show how to establish a baseline, compare isolated process changes (pre-preparation vs. detailed recording), design a run matrix for experimentation, and define abandonment criteria before investing in new equipment.

Alternative AnalysisBaselineCoffee Case Study
0 likes · 25 min read
Mission Engineering 07: Baseline First — Test Process Changes Before Buying Gear
Data Bricklaying Diary
Data Bricklaying Diary
Oct 4, 2026 · R&D Management

Mission Engineering 06: Who Does What, With Which Tools — From Paper Plans to Verified Execution

This article demonstrates how to translate mission tasks into concrete engineering threads by assigning specific people, tools, and actions to each step, using a coffee-making example to expose resource contention, handoff gaps, and the difference between paper parallelism and real-world feasibility.

Execution PlanningHandoff VerificationMEG 2.0
0 likes · 22 min read
Mission Engineering 06: Who Does What, With Which Tools — From Paper Plans to Verified Execution
Data Bricklaying Diary
Data Bricklaying Diary
Oct 3, 2026 · R&D Management

Mission Engineering: Why Memorizing Steps Fails — Defining Task Inputs, Outputs, and Dependencies

This article uses hand-drip coffee as a case study to demonstrate mission engineering task analysis: decomposing tasks, specifying inputs/outputs/start conditions/completion criteria for each step, linking dependencies via quality gates, handling missing items, and distinguishing material independence from resource contention, all while remaining implementation-agnostic.

Coffee Case StudyDependency MappingImplementation-Agnostic Design
0 likes · 16 min read
Mission Engineering: Why Memorizing Steps Fails — Defining Task Inputs, Outputs, and Dependencies
Data Bricklaying Diary
Data Bricklaying Diary
Oct 2, 2026 · R&D Management

Mission Engineering: Who Decides If the Coffee Is Good? Defining Success Metrics Beyond Timing

This article uses a morning coffee scenario to illustrate mission engineering's three-tier metric framework (MOS, MOE, MOP), showing how to define verifiable success criteria, separate stakeholder acceptance from process completion, and create traceable metric definitions that link overall outcomes to specific performance measurements.

MOPMOSMoE
0 likes · 22 min read
Mission Engineering: Who Decides If the Coffee Is Good? Defining Success Metrics Beyond Timing
Data Bricklaying Diary
Data Bricklaying Diary
Oct 2, 2026 · R&D Management

Mission Engineering 02: Why Weekend vs. Weekday Coffee Requires Separate Scenario Analysis

This article uses pour-over coffee to illustrate mission engineering's scenario and vignette framework, showing how to define participants, goals, time constraints, starting conditions, verified facts, assumptions, and measurement boundaries so that weekend and rushed weekday mornings can be fairly compared and improved.

Assumption TrackingConstraint ManagementProcess Measurement
0 likes · 18 min read
Mission Engineering 02: Why Weekend vs. Weekday Coffee Requires Separate Scenario Analysis
Data Bricklaying Diary
Data Bricklaying Diary
Oct 1, 2026 · Fundamentals

Mission Engineering: Steps Done ≠ Mission Accomplished — A Coffee Lesson

This article introduces Mission Engineering through a coffee-making analogy, emphasizing that completing steps doesn't guarantee mission success; it outlines a structured approach using a Mission Description Card to define goals, stakeholders, constraints, and success criteria, and advocates iterative experimentation over rigid processes.

Coffee AnalogyDoD GuideIterative Experimentation
0 likes · 19 min read
Mission Engineering: Steps Done ≠ Mission Accomplished — A Coffee Lesson
Data Bricklaying Diary
Data Bricklaying Diary
Jul 3, 2026 · Artificial Intelligence

Building Industry AI Semantic Foundations: MBSE Guides OPM & Ontology

The article argues that an industry AI semantic foundation requires MBSE to define system boundaries and verification loops, OPM to model objects, processes, and state changes, and ontology to consolidate unified semantic assets, providing a five-step implementation path for continuous model-data resonance.

Industry AIMBSEModel-Data Resonance
0 likes · 20 min read
Building Industry AI Semantic Foundations: MBSE Guides OPM & Ontology
Frontline Investigation
Frontline Investigation
Jun 16, 2026 · Industry Insights

AI Agents Need More Than Models: The Digital Infrastructure Gap

This article argues that successful AI agent deployment depends not on model size but on coordinated digital infrastructure—network, compute, edge, data, and security—citing China's 2026-2028 policy, agent capabilities (context, tools, integration, auditability), dynamic compute placement, data governance, and three maturity criteria: stability, process integration, and compliance.

5G-AAI agentsAI maturity criteria
0 likes · 11 min read
AI Agents Need More Than Models: The Digital Infrastructure Gap
Thought Artisan
Thought Artisan
Jan 27, 2026 · Fundamentals

Six Core Traits of Engineering Practice: A Framework for Robust Systems

The article defines six core traits of engineering practice — efficiency, ambiguity, fragility, resilience, maintainability, and safety — each categorized into hard, soft, and chaotic types, illustrated with historical case studies and structured methods for managing them.

EfficiencyEngineering PracticeResilience
0 likes · 26 min read
Six Core Traits of Engineering Practice: A Framework for Robust Systems
Leo Talks Systems Thinking
Leo Talks Systems Thinking
Jan 1, 2026 · Industry Insights

Splitting Functions from Implementation: Layered Verification in Automotive E/E Architecture

Industry experts discuss how automotive electronic architecture uses layered function-requirement decomposition, logical architecture, and bidirectional traceability to verify designs, comparing tools like Capella and Preevision, and analyzing a high-voltage power-down fault caused by missing indirect function-chain analysis.

Arcadia CapellaISO 26262Requirements Engineering
0 likes · 11 min read
Splitting Functions from Implementation: Layered Verification in Automotive E/E Architecture
Model Perspective
Model Perspective
Nov 8, 2025 · Operations

How Mathematical Modeling Powers China’s New Fujian Aircraft Carrier

From its 2018 construction kickoff to its 2025 commissioning, the Fujian aircraft carrier’s development showcases a timeline of milestones, while the article delves into the critical mathematical models—covering electromagnetic launch, energy storage, fluid dynamics, stability, scheduling, radar, and reliability—that underpin its design and operation.

Aircraft CarrierElectromagnetic LaunchSystems Engineering
0 likes · 18 min read
How Mathematical Modeling Powers China’s New Fujian Aircraft Carrier
Leo Talks Systems Thinking
Leo Talks Systems Thinking
Apr 13, 2025 · Fundamentals

Automotive Software Requirements Engineering: Core Concepts, V-Model & Traceability

This article introduces automotive software requirements engineering fundamentals, covering user need elicitation techniques, distinguishing real requirements from solutions, system concepts like emergence and interfaces, requirements types, V-model lifecycle traceability, modeling for analysis, and the importance of early verification over late testing.

ASPICERequirements EngineeringSystems Engineering
0 likes · 16 min read
Automotive Software Requirements Engineering: Core Concepts, V-Model & Traceability
Architects Research Society
Architects Research Society
Jul 3, 2023 · Operations

Enterprise Engineering: A Comprehensive View, Planning, Governance, and Systems of Systems

The article explains MITRE's enterprise engineering approach, describing a comprehensive perspective, enterprise planning and management, technology and infrastructure, information‑intensive systems, systems‑of‑systems, mission‑assurance engineering, transformation planning, and governance, while highlighting the need for adaptable, scalable solutions across large, interdependent organizations.

Enterprise EngineeringGovernanceSystems Engineering
0 likes · 13 min read
Enterprise Engineering: A Comprehensive View, Planning, Governance, and Systems of Systems
21CTO
21CTO
Apr 7, 2023 · Cloud Computing

Beyond AI: First‑Principles Strategies for the Emerging Digital Age

In this thought‑leading talk, Microsoft China CTO Wei Qing explores how first‑principle thinking, information theory, and cloud‑native architectures can guide organizations through the unknown digital era, emphasizing practical engineering, data integration, and the shift from hype to real‑world technology empowerment.

Systems Engineeringcloud computingdigital transformation
0 likes · 42 min read
Beyond AI: First‑Principles Strategies for the Emerging Digital Age
Architects Research Society
Architects Research Society
Apr 1, 2023 · Fundamentals

Enterprise Architecture and Systems Engineering: Component or Relationship Disciplines

The article examines the relationship between enterprise architecture and systems engineering, discussing overlapping frameworks such as TOGAF, DoDAF, UPDM, and model‑based approaches, and argues that while they share terminology and goals, EA focuses on business transformation and IT alignment, whereas SE emphasizes technical system development.

DODAFSystems EngineeringTOGAF
0 likes · 12 min read
Enterprise Architecture and Systems Engineering: Component or Relationship Disciplines