Introducing NominalAnalyst

The AI agent for people building hardware

Nominal Analyst is an AI agent for engineers building hardware in Nominal. It helps teams ask questions about their data, build editable analyses, and turn test plans into pass/fail checks, with sources and calculations engineers can review.

Read the blog

Start with the question that matters

Ask about a test result. Analyst brings together the requirement, measurements, and evidence behind it.

Battery pack BP-17

This battery pack failed its latest test. Which requirement failed, and when?

Reviewing BP17-044 against Thermal Test Plan §4.2

The temperature-spread check failed. Spread exceeded the 8 °C limit for 102 consecutive seconds during sustained load. The requirement allows less than 10 seconds above that limit.

THERM-04Fail · 102 seconds above limit

BP-17 Thermal Test Plan · Rev C · §4.2

Spread across T01–T06 must not exceed 8 °C for 10 consecutive seconds during sustained load.

Ask Analyst anything about your data…

Check results against the test plan

Analyst reads the requirement in your test plan, stored in Nominal. It turns the limit into a pass/fail check, runs it, and links the result to its source.

Battery pack BP-17

PreviouslyThe temperature-spread check failed. Spread exceeded the 8 °C limit for 102 consecutive seconds during sustained load. The requirement allows less than 10 seconds above that limit.

Does this meet the temperature-spread requirement?

Reading BP-17 Thermal Test Plan✓ Creating check✓ Running against BP17-044

No. BP17-044 fails THERM-04. During the evaluated sustained-load interval, spread exceeded 8 °C for 102 consecutive seconds. The test plan prohibits 10 consecutive seconds or longer above that limit.

THERM-04 · BP17-044Fail · 102 seconds above limit

Evaluated interval · sustained load

60–240 s elapsed (end exclusive) · 0–180 s after load start

Above limit · 138–240 s elapsed · 102 consecutive seconds

BP-17 Thermal Test Plan · Rev C · §4.2

Ask Analyst anything about your data…

Follow the result to the measurements

Move from an overall test result to the signals and physical locations worth examining.

Battery pack BP-17

PreviouslyNo. BP17-044 fails THERM-04. During the evaluated sustained-load interval, spread exceeded 8 °C for 102 consecutive seconds. The test plan prohibits 10 consecutive seconds or longer above that limit.

Which measurements account for the larger spread?

Comparing six temperature signals at peak spread

At 150 seconds after load start, T04 measured 56.4 °C and T01 measured 44.0 °C. These were the hottest and coolest measured locations, giving a spread of 12.4 °C.

Measured temperatures · BP17-044°C

T01T02T03T04T05T06

Ask Analyst anything about your data…

Bring context into the investigation

Compare the recorded conditions and identify what additional evidence would help explain the result.

Battery pack BP-17

PreviouslyAt 150 seconds after load start, T04 measured 56.4 °C and T01 measured 44.0 °C. These were the hottest and coolest measured locations, giving a spread of 12.4 °C.

Could different cooling conditions explain this?

Comparing recorded coolant and ambient conditions

The recorded coolant-flow and inlet-temperature settings match the previous tests. That doesn’t establish whether cooling behaved the same during the run. This dataset has no coolant-flow trace to evaluate that explanation.

Coolant flow setting5 L/min

Coolant inlet setting25 °C

Ambient condition25 °C

Missing evidence: coolant-flow measurements during the run.

Ask Analyst anything about your data…

Leave with a clearer next step

Keep the findings, supporting analysis, and open questions together so your team can continue the investigation.

Battery pack BP-17

PreviouslyThe recorded coolant-flow and inlet-temperature settings match the previous tests. That doesn’t establish whether cooling behaved the same during the run. This dataset has no coolant-flow trace to evaluate that explanation.

Summarize what we know and what we should investigate next.

Preparing the investigation summary

The spread exceeded the requirement and was larger than in the three comparison tests. T04 and T01 define the peak difference; the cause remains unresolved.

Open questionWhat caused the larger temperature difference?

Next checksVerify the temperature measurements and examine recorded cooling behavior.

Keep for reviewThe test comparison, temperature traces, and requirement result.

Ask Analyst anything about your data…

In the hands of engineers

More time for the work that moves hardware forward

NominalAnalyst

“I've saved hours and hours by using Analyst. It's been a huge improvement to our iteration speed.”

Cooper DiamondStaff Systems Engineer, Wisk Aero

NominalAnalyst

“As a new employee it made it very easy to navigate the large dataset and understand which variables were most useful for analyzing certain situations and root causing issues.”

Spencer SharpeFlight Test Engineering Intern, Mach Industries

Mach Industries team working on aircraft in their facility

Keep the evidence and continue the investigation

Return to the editable analysis, review the requirement result, and bring the open questions to your team.

Thermal investigation

Temperature spread · °C

Temperature spread · aligned at load start°C

BP17-041BP17-042BP17-043BP17-044

Module temperatures · BP17-044 · °C

Measured temperatures · BP17-044°C

T01T02T03T04T05T06

Thermal test results

Peak spread during sustained load for the four tests
Test	Peak spread	Check
BP17-041	4.8 °C	Pass
BP17-042	5.7 °C	Pass
BP17-043	6.2 °C	Pass
BP17-044Current	12.4 °C	Fail

Requirement · THERM-04

FailBP17-044 · 102 seconds above 8 °C

Spread across T01–T06 must not exceed 8 °C for 10 consecutive seconds during sustained load.

BP-17 Thermal Test Plan · Rev C · §4.2

Cause unresolved. Verify temperature measurements and examine recorded cooling behavior.

Battery pack BP-17

This battery pack failed its latest test. Which requirement failed, and when?

Reviewing BP17-044 against Thermal Test Plan §4.2

The temperature-spread check failed. Spread exceeded the 8 °C limit for 102 consecutive seconds during sustained load. The requirement allows less than 10 seconds above that limit.

THERM-04Fail · 102 seconds above limit

BP-17 Thermal Test Plan · Rev C · §4.2

Spread across T01–T06 must not exceed 8 °C for 10 consecutive seconds during sustained load.

Does this meet the temperature-spread requirement?

Reading BP-17 Thermal Test Plan✓ Creating check✓ Running against BP17-044

THERM-04 · BP17-044Fail · 102 seconds above limit

Evaluated interval · sustained load

60–240 s elapsed (end exclusive) · 0–180 s after load start

Above limit · 138–240 s elapsed · 102 consecutive seconds

BP-17 Thermal Test Plan · Rev C · §4.2

Which measurements account for the larger spread?

Comparing six temperature signals at peak spread

At 150 seconds after load start, T04 measured 56.4 °C and T01 measured 44.0 °C. These were the hottest and coolest measured locations, giving a spread of 12.4 °C.

Measured temperatures · BP17-044°C

T01T02T03T04T05T06

Could different cooling conditions explain this?

Comparing recorded coolant and ambient conditions

Coolant flow setting5 L/min

Coolant inlet setting25 °C

Ambient condition25 °C

Missing evidence: coolant-flow measurements during the run.

Summarize what we know and what we should investigate next.

Preparing the investigation summary

The spread exceeded the requirement and was larger than in the three comparison tests. T04 and T01 define the peak difference; the cause remains unresolved.

Open questionWhat caused the larger temperature difference?

Next checksVerify the temperature measurements and examine recorded cooling behavior.

Keep for reviewThe test comparison, temperature traces, and requirement result.

What can Analyst do?

Find the right data, build an analysis, and check results against your requirements inside Nominal.

Build and edit analyses

Create and update Nominal workbooks with plots, derived signals, tables, and layouts.

Turn test plans into automations

Read specs and test plans in Nominal, define pass/fail checks with thresholds, run them against test data, and review violations.

Compare tests and calculate signals

Overlay tests, apply filters and derivatives, and run frequency analysis such as FFT, PSD, and Bode plots.

Write custom analysis code

Calculate statistics across tests, explore trends across months of testing, and create visualizations for questions that need more context.

Use your engineering documents

Find relevant specs and test plans in Nominal Drives and cite the documents behind the analysis.

Find the right data

Locate tests, hardware, signals, and existing analyses in your Nominal workspace.

FAQ

More about Analyst

What is Nominal Analyst?

Is Analyst ready for my team?

Analyst is available today in preview for engineers building on Nominal. Engineers are already using it today.

What data can Analyst use?

Your tests, hardware, signals, analyses, and checks in Nominal, plus the specs, test plans, and design documents your team keeps in Nominal.

What can Analyst see and change?

Analyst acts with your permissions. It can only see and edit what you allow it to.

Can I customize how Analyst works?

Yes. Write skills that describe your team's analysis methods, review steps, or reporting conventions, and share them across your workspace so everyone's Analyst works the same way.

Can I check its work?

Yes. You can inspect the calculations, code, and sources behind every analysis, edit the results in Nominal, or ask Analyst to refine them.

Is my data used to train models?

Your data is not currently used to train models, but we do keep traces and product analytics to improve the product.

How do I get access?

Request a demo to see Analyst with the Nominal team. Already on Nominal? Ask your account team about preview access.

How is Analyst different from a general-purpose AI assistant?

Analyst works directly with your data and analysis tools inside Nominal. It builds analyses your team can edit, turns test plans into pass/fail checks and runs them, and follows the playbook your team teaches it through skills. Every conclusion traces back to the data or document behind it.

How is Analyst different from connecting my own AI agent to Nominal?

Both work in Nominal with your permissions. Nominal's MCP server gives the agent you already use, like Claude, Codex, or Devin, access to Nominal tools, which might be the right fit when your work spans other systems. Analyst is built for engineering work inside Nominal: it creates workbooks, writes and runs checks, derives signals, and grounds its work in your team's documents and skills.Already building with Claude, Codex, or Devin?Connect your own agent to Nominal through our MCP, the Model Context Protocol connection that lets external agents work in Nominal.Learn more about Nominal for Developers

Put Analyst to work on your data

Find relevant data, build comparisons, and check results against your engineering requirements.

Read the blog

Start with the question that matters

Ask about a test result. Analyst brings together the requirement, measurements, and evidence behind it.

Battery pack BP-17

This battery pack failed its latest test. Which requirement failed, and when?

Reviewing BP17-044 against Thermal Test Plan §4.2

The temperature-spread check failed. Spread exceeded the 8 °C limit for 102 consecutive seconds during sustained load. The requirement allows less than 10 seconds above that limit.

THERM-04Fail · 102 seconds above limit

BP-17 Thermal Test Plan · Rev C · §4.2

Spread across T01–T06 must not exceed 8 °C for 10 consecutive seconds during sustained load.

Ask Analyst anything about your data…

Check results against the test plan

Analyst reads the requirement in your test plan, stored in Nominal. It turns the limit into a pass/fail check, runs it, and links the result to its source.

Battery pack BP-17

PreviouslyThe temperature-spread check failed. Spread exceeded the 8 °C limit for 102 consecutive seconds during sustained load. The requirement allows less than 10 seconds above that limit.

Does this meet the temperature-spread requirement?

Reading BP-17 Thermal Test Plan✓ Creating check✓ Running against BP17-044

THERM-04 · BP17-044Fail · 102 seconds above limit

Evaluated interval · sustained load

60–240 s elapsed (end exclusive) · 0–180 s after load start

Above limit · 138–240 s elapsed · 102 consecutive seconds

BP-17 Thermal Test Plan · Rev C · §4.2

Ask Analyst anything about your data…

Follow the result to the measurements

Move from an overall test result to the signals and physical locations worth examining.

Battery pack BP-17

Which measurements account for the larger spread?

Comparing six temperature signals at peak spread

At 150 seconds after load start, T04 measured 56.4 °C and T01 measured 44.0 °C. These were the hottest and coolest measured locations, giving a spread of 12.4 °C.

Measured temperatures · BP17-044°C

T01T02T03T04T05T06

Ask Analyst anything about your data…

Bring context into the investigation

Compare the recorded conditions and identify what additional evidence would help explain the result.

Battery pack BP-17

PreviouslyAt 150 seconds after load start, T04 measured 56.4 °C and T01 measured 44.0 °C. These were the hottest and coolest measured locations, giving a spread of 12.4 °C.

Could different cooling conditions explain this?

Comparing recorded coolant and ambient conditions

Coolant flow setting5 L/min

Coolant inlet setting25 °C

Ambient condition25 °C

Missing evidence: coolant-flow measurements during the run.

Ask Analyst anything about your data…

Leave with a clearer next step

Keep the findings, supporting analysis, and open questions together so your team can continue the investigation.

Battery pack BP-17

Summarize what we know and what we should investigate next.

Preparing the investigation summary

The spread exceeded the requirement and was larger than in the three comparison tests. T04 and T01 define the peak difference; the cause remains unresolved.

Open questionWhat caused the larger temperature difference?

Next checksVerify the temperature measurements and examine recorded cooling behavior.

Keep for reviewThe test comparison, temperature traces, and requirement result.

Ask Analyst anything about your data…

More time for the work that moves hardware forward

NominalAnalyst

“I've saved hours and hours by using Analyst. It's been a huge improvement to our iteration speed.”

Cooper DiamondStaff Systems Engineer, Wisk Aero

NominalAnalyst

“As a new employee it made it very easy to navigate the large dataset and understand which variables were most useful for analyzing certain situations and root causing issues.”

Spencer SharpeFlight Test Engineering Intern, Mach Industries

Peak spread during sustained load for the four tests

Test

Peak spread

Check

BP17-041

4.8 °C

Pass

BP17-042

5.7 °C

Pass

BP17-043

6.2 °C

Pass

BP17-044Current

12.4 °C

Fail