Made byBobr AI

Systems Engineering: Mechanical & Electrical Principles

Master systems engineering with this guide on V-Models, GD&T, ISO standards, maintenance strategies, and project control metrics including EVM and FMEA.

#systems-engineering#mechanical-engineering#iso-15288#v-model#gd-and-t#fmea#reliability-engineering
Watch
Pitch

Engineering Task Validation: Type, Scope, and Requirements Analysis

Detailed Methodology for Mechanical & Electrical Systems Engineering (INCOSE & IEC Standards)

Compliant with IEEE 15288 & ISO 9001 Frameworks

Made byBobr AI

The Systems Engineering V-Model: Detailed Phases

Decomposition (Left Side)

1. User Requirements: What the customer needs (e.g., 'Must withstand 100°C').

2. System Requirements: converting user needs into technical specs (e.g., 'IP67 Rated Enclosure').

3. Architecture Design: High-level system blocks (e.g., Power Unit, Control Unit).

Integration (Right Side)

1. Unit Testing: Testing individual components (e.g., Resistor continuity check).

2. Sub-system Integration: Connecting parts (e.g., Wiring harness to motor).

3. Acceptance Testing: Does it meet the User Requirements?

Critical Note for Level 3 Engineering: The 'Verification' phase checks if the product was built correctly (Technical Standard Check), while 'Validation' checks if the right product was built (Client Needs Check). Errors found on the right side usually originate from poor definition on the left.
Made byBobr AI

Maintenance Strategies & Condition Monitoring

1. Corrective Maintenance (Run-to-Failure)

Action is taken only after functional failure occurs. Suitable only for non-critical items like light bulbs or fuses where failure consequence is low. Risk: Unexpected downtime and secondary damage to other components.

2. Preventive Maintenance (Time-Based)

Scheduled tasks based on intervals (e.g., changing oil every 5000 hours). Issue: Can lead to 'over-maintenance', wasting useful life of parts, or 'infant mortality' if reassembly is incorrect.

3. Predictive Maintenance (Condition-Based)

Uses real-time data to detect the P-F Interval (time between Potential Failure and Functional Failure).
Techniques:
• Vibration Analysis (detects bearing faults)
• Thermography (detects overheating execution)
• Ultrasonic Analysis (detects air leaks/arcing)

Made byBobr AI

Project Control: Earned Value Management (EVM)

EVM provides an objective snapshot of project health. For T-Level engineers, understanding the difference between Planned and Earned value is critical for project control.

Interpreting the Indices

  • SPI (Schedule Performance Index) = EV ÷ PV
    - If SPI < 1.0: Behind Schedule (We have done less than planned).
    - If SPI > 1.0: Ahead of Schedule.
  • CPI (Cost Performance Index) = EV ÷ AC
    - If CPI < 1.0: Over Budget (We spent more than the work was worth).
    - If CPI > 1.0: Under Budget (Efficiency is high).

Engineering Impact: A CPI of 0.8 means for every £1.00 spent, we only achieved £0.80 of value. This requires immediate root cause analysis.

Chart
Made byBobr AI

Requirements Engineering: ISO/IEC 29148

In professional engineering, vague requests lead to project failure. We use standard frameworks (ISO/IEC 29148) to ensure requirements are SMART (Specific, Measurable, Achievable, Relevant, Time-bound).

Functional Requirements

Defines what the system must do.

  • Input: "The system shall accept 24V DC power."
  • Process: "The PLC shall process the sensor signal within 10ms."
  • Output: "The motor must generate 50Nm torque at 1500 RPM."

Non-Functional Requirements

Defines how the system must perform (Quality Attributes).

  • Reliability: "MTBF must exceed 50,000 hours per MIL-HDBK-217F."
  • Safety: "Must meet SIL 2 integrity level."
  • Environmental: "Must operate between -20°C and +60°C."
Made byBobr AI

Life Cycle Analysis: The Bathtub Curve

The Three Phases of Component Life

1. Infant Mortality (Early Failure)

Failures caused by manufacturing defects or installation errors. The failure rate decreases over time. Addressed by 'Burn-in' testing.

2. Constant Failure Rate (Useful Life)

Random failures caused by stress or external events. The failure rate is constant. This is where MTBF (Mean Time Between Failures) applies.

3. Wear Out (End of Life)

Failures due to fatigue, corrosion, or friction. The failure rate increases rapidly. Addressed by preventive replacement.

Chart
Made byBobr AI

Safety Requirements: IEC 61508 & SIL

Functional Safety is probabilistic. Safety Integrity Levels (SIL) dictate the required Probability of Failure on Demand (PFD).

SIL LevelPFD (Low Demand)Risk Reduction Factor
SIL 410-5 to 10-410,000 - 100,000
SIL 310-4 to 10-31,000 - 10,000
SIL 210-3 to 10-2100 - 1,000
SIL 110-2 to 10-110 - 100

Engineers must calculate the PFD of the 'Safety Instrumented Function' (SIF), which includes the Sensor, Logic Solver, and Final Element.

Made byBobr AI

Reading Technical Drawings: GD&T Basics

Geometric Dimensioning and Tolerancing (BS 8888 / ASME Y14.5) is the international language for describing part intent. It replaces simple +/- tolerancing with precise control frames.

The Feature Control Frame

A rectangular box divided into compartments:

  • Compartment 1 (Symbol): Geometric characteristic (e.g., ⌖ Position, ⟂ Perpendicularity).
  • Compartment 2 (Tolerance): Total tolerance zone value (e.g., 0.05mm). Often preceded by Ø for cylindrical zones.
  • Compartment 3+ (Datums): Reference letters (e.g., A, B, C) defining the frame of reference.

Why Use GD&T?

  • Functionality: Focuses on how the part works, not just how it measures.
  • Bonus Tolerance: MMC (Maximum Material Condition) modifiers allowed for extra tolerance if the hole is larger than its smallest limit.
  • Cost Reduction: Prevents rejecting functional parts that would fail coordinate measurement but pass GD&T.
Made byBobr AI

Identifying Issues: FMEA Methodology

Failure Mode and Effects Analysis (FMEA) in Practice

FMEA is a bottom-up systematic method to identify potential failures. Engineers must score three variables on a scale of 1-10:

  • Severity (S): How bad is the effect? (1 = Noticeable, 10 = Hazardous/Safety Risk).
  • Occurrence (O): How often does it happen? (1 = Never, 10 = Frequent/Inevitable).
  • Detection (D): Can we find it before it reaches the customer? (1 = Certain detection, 10 = Undetectable).
Risk Priority Number (RPN) = S × O × D

Action Rule: Any RPN > 100 or Severity score of 9-10 usually requires mandatory design changes or mitigation.

Chart
Made byBobr AI

Constructing a Fault Tree Analysis (FTA)

Step 1: Define the Top Event

Identify the catastrophic failure you want to analyze (e.g., 'Hydraulic Press Fails to Stop').

Step 2: Determine Immediate Causes

What direct events could cause the top event? Use logic gates to connect them.

Step 3: Boolean Logic Gates

  • OR Gate (Curved Base): Event happens if any input happens. Increases probability of failure.
    Example: Sensor failure OR Wire break.
  • AND Gate (Flat Base): Event happens only if all inputs happen. Increases safety/redundancy.
    Example: Guard switch failed AND Emergency Stop failed.
Calculation Note: For T-Level calculations, probabilities are usually multiplied for AND gates (P = A × B) and added for OR gates (P ≈ A + B, for small probabilities).
Made byBobr AI

Conclusion: The Cost of Definition

Correctly defining Type, Scope, and Requirements reduces 'Technical Debt'. The cost to fix an error increases exponentially by a factor of 10x through each phase of the project lifecycle (Boehm's Curve).

Chart
Made byBobr AI
Bobr AI

DESIGNER-MADE
PRESENTATION,
GENERATED FROM
YOUR PROMPT

Create your own professional slide deck with real images, data charts, and unique design in under a minute.

Generate For Free

Systems Engineering: Mechanical & Electrical Principles

Master systems engineering with this guide on V-Models, GD&T, ISO standards, maintenance strategies, and project control metrics including EVM and FMEA.

Engineering Task Validation: Type, Scope, and Requirements Analysis

Detailed Methodology for Mechanical & Electrical Systems Engineering (INCOSE & IEC Standards)

Compliant with IEEE 15288 & ISO 9001 Frameworks

The Systems Engineering V-Model: Detailed Phases

Defining the 'Type, Scope, and Requirements' is not administrative; it is the foundation of the Systems Engineering V-Model. Failure to rigorously define the left side of the V-Model results in integration failures on the right side. We utilize ISO/IEC 15288 processes to ensure technical integrity.

<strong>Critical Note for Level 3 Engineering:</strong> The 'Verification' phase checks if the product was built correctly (Technical Standard Check), while 'Validation' checks if the right product was built (Client Needs Check). Errors found on the right side usually originate from poor definition on the left.

Maintenance Strategies & Condition Monitoring

<b>Corrective (Reactive):</b> Run-to-failure. Valid only when failure consequence is negligible (Low Criticality).

<b>Preventive (Time-Based):</b> Scheduled intervention regardless of condition. Assumes failure probability increases with time (wear-out).

<b>Predictive (Condition-Based):</b> Uses CBM data (vibration analysis, thermography). Intervention occurs at the P-F Interval.

Project Control: Earned Value Management (EVM)

Engineering scope is not merely a task list; it is a measurable baseline. All tasks must be quantified using EVM metrics to track Schedule Variance (SV) and Cost Variance (CV).

Schedule Performance Index (SPI) = EV / PV

Cost Performance Index (CPI) = EV / AC

Requirements Engineering: ISO/IEC 29148

Adherence to ISO/IEC 29148 differentiates professional engineering from tinkering. Requirements must be Atomic, Complete, Concise, and Verifiable.

<strong>Functional Requirements:</strong> What the system must DO. <br><em>Example:</em> The servo motor must provide 15 Nm torque at 3000 RPM within 50ms of signal.

<strong>Non-Functional Requirements:</strong> How the system must BE. <br><em>Example (Reliability):</em> MTBF > 20,000 hours per MIL-HDBK-217F.

Life Cycle Analysis: The Bathtub Curve

The hazard rate λ(t) is fundamental to defining maintenance intervals. The Weibull Distribution function R(t) = e^-(t/η)^β models these phases.

Safety Requirements: IEC 61508 & SIL

Functional Safety is probabilistic. Safety Integrity Levels (SIL) dictate the required Probability of Failure on Demand (PFD).

<table style='width:100%; border-collapse:collapse; font-size:20px;'><thead><tr style='background:#34495e; color:white;'><th style='padding:15px; border:1px solid #ddd;'>SIL Level</th><th style='padding:15px; border:1px solid #ddd;'>PFD (Low Demand)</th><th style='padding:15px; border:1px solid #ddd;'>Risk Reduction Factor</th></tr></thead><tbody><tr style='background:#ecf0f1;'><td style='padding:15px; border:1px solid #ddd; text-align:center;'>SIL 4</td><td style='padding:15px; border:1px solid #ddd; text-align:center;'>10<sup>-5</sup> to 10<sup>-4</sup></td><td style='padding:15px; border:1px solid #ddd; text-align:center;'>10,000 - 100,000</td></tr><tr><td style='padding:15px; border:1px solid #ddd; text-align:center;'>SIL 3</td><td style='padding:15px; border:1px solid #ddd; text-align:center;'>10<sup>-4</sup> to 10<sup>-3</sup></td><td style='padding:15px; border:1px solid #ddd; text-align:center;'>1,000 - 10,000</td></tr><tr style='background:#ecf0f1;'><td style='padding:15px; border:1px solid #ddd; text-align:center;'>SIL 2</td><td style='padding:15px; border:1px solid #ddd; text-align:center;'>10<sup>-3</sup> to 10<sup>-2</sup></td><td style='padding:15px; border:1px solid #ddd; text-align:center;'>100 - 1,000</td></tr><tr><td style='padding:15px; border:1px solid #ddd; text-align:center;'>SIL 1</td><td style='padding:15px; border:1px solid #ddd; text-align:center;'>10<sup>-2</sup> to 10<sup>-1</sup></td><td style='padding:15px; border:1px solid #ddd; text-align:center;'>10 - 100</td></tr></tbody></table>

Engineers must calculate the PFD of the 'Safety Instrumented Function' (SIF), which includes the Sensor, Logic Solver, and Final Element.

Reading Technical Drawings: GD&T Basics

Interpreting drawings requires understanding Geometric Dimensioning and Tolerancing. Standard coordinate tolerancing results in a square tolerance zone, whereas GD&T allows for a circular zone, increasing the usable tolerance area by 57%.

<ul><li><b>Datums (A, B, C):</b> Define the reference frame (6 degrees of freedom).</li><li><b>Position (⌖):</b> Controls location of features relative to datums (LMC/MMC modifiers).</li><li><b>Profile (⌓):</b> Controls the outline of a surface.</li></ul>

Geometric Dimensioning and Tolerancing (BS 8888 / ASME Y14.5) is the international language for describing part intent. It replaces simple +/- tolerancing with precise control frames.

Identifying Issues: FMEA Methodology

Failure Mode and Effects Analysis (AIAG/VDA Standard)

RPN = Severity (S) × Occurrence (O) × Detection (D)

<ol><li><b>Failure Mode:</b> How could the component fail? (e.g., Short circuit, Fracture).</li><li><b>Effect:</b> What is the consequence? (e.g., System shutdown, Fire).</li><li><b>Cause:</b> What is the physical mechanism? (e.g., Fatigue, Dielectric breakdown).</li></ol>

Constructing a Fault Tree Analysis (FTA)

FTA is a top-down, deductive failure analysis using Boolean logic. It quantifies the probability of the Top Event (System Failure).

<b>OR Gate:</b> Failure occurs if ANY input fails. <br>P(A OR B) ≈ P(A) + P(B)

<b>AND Gate:</b> Failure occurs only if ALL inputs fail (Redundancy). <br>P(A AND B) = P(A) × P(B)

Conclusion: The Cost of Definition

Correctly defining Type, Scope, and Requirements reduces 'Technical Debt'. The cost to fix an error increases exponentially by a factor of 10x through each phase of the project lifecycle (Boehm's Curve).

  • systems-engineering
  • mechanical-engineering
  • iso-15288
  • v-model
  • gd-and-t
  • fmea
  • reliability-engineering