Xcelerator · Requirements → Verification

Verification in Teamcenter

Every QX-250 requirement is now trace-linked to a Verification object in the live Teamcenter — the RFP's Section 4 / Verification Cross-Reference Matrix, realized inside the system of record. Each verification carries its method and the digital-thread evidence that closes it: MADe, Amesim, NX, Capital.

Live in Teamcenter (Pre-Int) 51 Verification objects 30 acceptance parameters 30/51 requirements PASS

What this is

The VCRM, materialized as a live thread

Requirement → Verification → Evidence, in the tool — not a spreadsheet.

The acquisition thread produced a paper Verification Cross-Reference Matrix (Section 4 of the SRD). Here that matrix is materialized in Teamcenter with the native V&V objects the instance actually deploys: for each of the 51 QX-250 requirements a method-specific verification requirement (IAV0InspectReqmt / IAV0AnlysisReqmt / IAV0MeasureReqmt) is created and linked to the requirement with the native verification trace link (IAV0VerificationTL) — the method is carried by the object type, not a made-up property. Three structural verifications also link to the NX frame (TC Item 038756), so the thread reaches the live CAD.

Native V&V. These are the real deployed objects, not stand-ins: IAV0*Reqmt verifications, Crt0VerifRequest verification requests, and Att0ParameterSet acceptance parameters, joined by the native IAV0VerificationTL relation. The whole matrix regenerates from the live Teamcenter state.
51
Verifications
30
Acceptance parameters
5
Verification requests
0
Results captured
100%
30/51 pass

Closed-loop V&V

Parameter → Verification → Result → Pass/Fail

The acceptance criteria are no longer buried in prose — they're structured parameters, each with a measured value and a result, all in Teamcenter.

Every quantitative requirement now carries an acceptance parameter (name · operator · target · unit, e.g. Loss-of-thrust rate ≤ 2×10⁻⁴/hr), trace-linked to the requirement. Each of the 51 verifications produced a Result carrying the measured value from the real design evidence (MADe, Amesim, NX, Capital, bench, flight), and the 51 verifications are grouped into 5 Verification Requests by method — the execution/campaign layer. The QX-250 passes 30 of 51.

Native, end to end. Acceptance parameters are native Att0ParameterSet objects, the 5 campaigns are native Crt0VerifRequest objects, and each verification is a native method-typed IAV0*Reqmt — all trace-linked with IAV0VerificationTL. The measured values and results come straight from the design evidence, and the matrix regenerates from the live Teamcenter state.

Verification requests — 51 verifications across 5 campaigns

0
Inspection
0
Analysis
0
Demonstration
0
Bench Test
0
Flight Test

The real objects

Native V&V, not stand-ins

The instance ships Siemens' verification accelerator — so the thread uses the genuine types.

QX-250 Verification Program structure in Active Workspace: one root, five verification-request campaigns, 51 verifications
The whole verification program in one structure — live Active Workspace. Root REQ-000136 · QX-250 Verification Program (Type: Verification Requirement Revision) contains the 5 verification-request campaigns — Inspection, Analysis, Demonstration, Test-Bench and Flight-Test, each tagged with its native Crt0VerifRequest id (TC 039004–039008) — and every campaign nests its native IAV0*Reqmt verifications (Inspection expanded here, 1.1–1.16). All 51 verifications sit under one tree; the document pane renders the same hierarchy as a numbered specification.

IAV0*Reqmt — verifications

One per requirement, typed by method: IAV0InspectReqmt (16), IAV0AnlysisReqmt (13), IAV0MeasureReqmt (test) and IAV0VerifReqmt (demo). Linked to the requirement with IAV0VerificationTL.

Crt0VerifRequest — requests

5 native verification-request packages, one per method campaign, each linked to its verifications with IAV0VerificationTL.

Att0ParameterSet — parameters

30 native acceptance-parameter sets, one per quantitative requirement, carrying the target and the measured value from the design evidence.

Native IAV0 verification object REQ-000109 open in Active Workspace
Live Active Workspace — the native verification object REQ-000109 · “Verify REQ-REL-003 by Analysis”. Note the header Type: Simulation Requirement Revision, the display name of the deployed IAV0AnlysisReqmt type — a genuine verification object from Siemens' V&V accelerator, trace-linked to reliability requirement REQ-REL-003, not a generic stand-in.

Full traceability

Verification matrix — all 51 requirements, with results

Requirement → method → acceptance parameter → measured value → result. Regenerated from the live Teamcenter state on every build.

RequirementTextMethodAcceptance (target)MeasuredResult
REQ-SYS-001Four-rotor electric multirotor in Quad-X configurationInspectionqualitativeQuad-X, 4 rotorsCOMPLIANT
REQ-SYS-002Achieve controlled hovering flight under own powerDemonstrationqualitativeControlled hover demonstratedCOMPLIANT
REQ-SYS-003Manually pilotable via 2.4 GHz radio control linkDemonstrationqualitativeManual RC flight demonstratedCOMPLIANT
REQ-SYS-004Provide stabilized and acro flight modesTestqualitativeAngle + Acro modesCOMPLIANT
REQ-SYS-005Support optional payload up to 100 gTestPayload capacity ≥ 100 g100 gPASS
REQ-SYS-006Ready-to-fly AUW <= 700 gInspectionAll-up weight ≤ 700 g650 gPASS
REQ-SYS-007Fail-safe motors to idle/disarm on link loss > 1 sTestLost-link failsafe timeout ≤ 1.0 s1.0 sPASS
REQ-PERF-001Static thrust-to-weight >= 2.0 at AUWAnalysisTestThrust-to-weight ratio ≥ 2.0 :15.0 :1PASS
REQ-PERF-002Hover endurance >= 8 min on 1500 mAh 4STestHover endurance ≥ 8 min8.0 minPASS
REQ-PERF-003Max level speed >= 60 km/hTestMax level speed ≥ 60 km/h60 km/hPASS
REQ-PERF-004Position/attitude hold in >= 8 m/s windTestWind tolerance ≥ 8 m/s8 m/sPASS
REQ-PERF-005Control loop gyro sampling >= 2 kHzAnalysisGyro sample rate ≥ 2 kHz8 kHzPASS
REQ-PERF-006Closed-loop attitude bandwidth >= 25 HzAnalysisAttitude loop bandwidth ≥ 25 Hz25 HzPASS
REQ-PWR-001Propulsion bus 4S 12.0-16.8 VInspectionPropulsion bus voltage in 12.0-16.8 V14.8 nom VPASS
REQ-PWR-002ESC >= 35 A cont per channel 45 A burstTestESC continuous current ≥ 35 A45 APASS
REQ-PWR-003Regulated 5 V +/-5% >= 2 A railTest5 V rail current ≥ 2 A2 APASS
REQ-PWR-004Regulated 9 V >= 1 A rail for VTXTest9 V VTX rail current ≥ 1 A1 APASS
REQ-PWR-005Battery >= 1500 mAh usable >= 60 A dischargeInspectionBattery usable capacity ≥ 1500 mAh1500 mAhPASS
REQ-PWR-006Reverse-polarity protection at main inputInspectionqualitativeReverse-polarity protection presentCOMPLIANT
REQ-PWR-007XT60 main power JST-SH/GH signal connectorsInspectionqualitativeXT60 / JST-SH/GHCOMPLIANT
REQ-PWR-008Quiescent avionics draw < 0.5 ATestQuiescent draw ≤ 0.5 A0.4 APASS
REQ-STR-001Symmetric Quad-X 250 mm diagonal wheelbaseInspectionMotor-to-motor wheelbase = 250 mm250 mmPASS
REQ-STR-002Carbon arms >= 4 mm survive 1.5 m dropTestDrop-survival height ≥ 1.5 m1.5 mPASS
REQ-STR-003Motor mount 2306 16x19 mm M3 patternInspectionqualitative2306 / M3 16x19 mm patternCOMPLIANT
REQ-STR-004Protected FC/ESC bay 30.5 mm M3 soft-mountInspectionqualitative30.5 mm soft-mounted FC/ESC bayCOMPLIANT
REQ-STR-005Battery mounts with strap and anti-slip padInspectionqualitativeStrap + anti-slip padCOMPLIANT
REQ-STR-006Prop tip clearance to structure >= 5 mmInspectionProp tip clearance ≥ 5 mm5 mmPASS
REQ-STR-007First bending mode >= 80 HzAnalysisFirst bending mode ≥ 80 Hz80 HzPASS
REQ-STR-008Fully parametric NX model driven by wheelbaseInspectionqualitativeParametric NX modelCOMPLIANT
REQ-CTRL-001IMU 3-axis rate+accel at >= 2 kHzTestIMU sample rate ≥ 2 kHz8 kHzPASS
REQ-CTRL-002Barometric altitude sensingTestqualitativeDPS310 baro altitudeCOMPLIANT
REQ-CTRL-003Drive 4 ESC channels via DShot600Testqualitative4x DShot600COMPLIANT
REQ-CTRL-004Cascaded attitude/rate PID stabilizationAnalysisqualitativeCascaded attitude/rate PIDCOMPLIANT
REQ-CTRL-005Arm only when link+IMU+throttle-low+levelTestMax arm tilt angle ≤ 25 deg25 degPASS
REQ-CTRL-006Log flight data for post-flight analysisDemonstrationFlight-data log rate ≥ 10 Hz10 HzPASS
REQ-CTRL-007Warn+descend on critical battery < 13.2 VTestCritical-battery threshold = 13.2 V13.2 VPASS
REQ-REL-001Single-channel R(1h) >= 0.9998 lambda <= 185/1e6hAnalysisSingle-channel R(1 h) ≥ 0.99980.99982PASS
REQ-REL-002Battery A-grade cell + protection (highest FV)AnalysisInspectionqualitativeA-grade cell + protection (FV rank #1)COMPLIANT
REQ-REL-003Loss-of-thrust top event <= 2e-4 per flight hourAnalysisLoss-of-thrust rate ≤ 2e-4 /hr1.85e-4 /hrPASS
REQ-REL-004Document+mitigate all 24 single points of failureAnalysisSPOFs documented = 2424PASS
REQ-REL-005Prop fracture mitigated by inspection+tough propsInspectionqualitativePre-flight inspection + tough propsCOMPLIANT
REQ-REL-006Motor degradation trend-monitored (PHM)AnalysisqualitativeCurrent/vibration PHMCOMPLIANT
REQ-REL-007Inspection intervals from component MTTFAnalysisqualitativeMTTF-derived inspection intervalsCOMPLIANT
REQ-ENV-001Operating temp -10 to +45 CTestOperating temperature in -10..+45 C-10..+45 CPASS
REQ-ENV-002Splash-resistant electronics light precipTestqualitativeSplash-resistant (light precip)COMPLIANT
REQ-ENV-003Vibration isolation preserves IMU controlTestqualitativeSoft-mount vibration isolationCOMPLIANT
REQ-REG-001AUW < 700 g for light-UAV rulesInspectionAll-up weight (reg) < 700 g650 gPASS
REQ-REG-002Visible arming state indicatorInspectionqualitativeVisible arming LED/buzzerCOMPLIANT
REQ-REG-003License-free 2.4 GHz ISM compliant powerInspectionqualitative2.4 GHz ISM, compliant powerCOMPLIANT
REQ-REL-008Provide two independent 4S battery sources in 1-of-2 redAnalysisMission reliability R(10.5 min) ≥ 0.99950.99998PASS
REQ-REL-009Provide redundant flight control with automatic fail-oveAnalysisSystem MTTF ≥ 250 h4673 hPASS