AI for systems engineering
Ultramarine Work drafts the requirements, ICDs, calc packages, DFMEAs and test reports that your design reviews and audits depend on, from the specification files, drawings and test data already in the project folder.
Lug-margins-2400kg-case.xlsxExample| Check | Applied, Nd 3.0 | Allowable | MS | Source |
|---|---|---|---|---|
| Net-section tension | 61.2 kN | 112.0 kN | 0.83 | Drawing D-2207 rev B |
| Pin bearing | 61.2 kN | 98.5 kN | 0.61 | Drawing D-2207 rev B |
| Shear tear-out | 61.2 kN | 74.0 kN | 0.21 | D-2207 rev B, edge distance 28 mm |
| Bolt group, 4 × M12 10.9 | 61.2 kN | 134.9 kN | 1.20 | Fastener calc FC-031 |
| Fillet weld, 6 mm | 61.2 kN | 88.4 kN | 0.44 | Weld map WM-12 |
NoteTear-out MS is 0.21, under the 0.25 floor, so raise the edge distance to 34 mm, which brings it to about 0.61.
Ask it for
“Read the customer SOR in the folder and draft the system requirements as shall statements with unique IDs, rationale and a verification method for each.”
System-requirements-draft.docx“Draft the ICD tables for the instrument’s 28 V power and MIL-STD-1553B interfaces, with pin assignments, voltage ranges, ripple limits and RT addresses.”
ICD-instrument-power-1553.docx“Re-run the lug and bolt group margins for lifting the 2,400 kg transport case, tie each input to its source file, and list every margin of safety below 0.25.”
Lug-margins-2400kg-case.xlsx“Start the DFMEA rows for the flow meter board from the drawings and 12 field returns, fill in effects and causes, and leave the S, O and D ratings to the team.”
DFMEA-flow-meter.xlsx“Write the qualification report for the 50-cycle thermal run from the DAQ logs, checked against the protocol’s acceptance criteria, with deviations noted.”
Qual-report-TR-0142.docx“Score the four stow mechanism options against the weights the team locked in advance, run the sensitivity check, and show which judgment the ranking turns on.”
Trade-study-stow.xlsx
Inside the Product & Systems Engineering mode
Technical requirements and specifications
It drafts shall statements with unique IDs and rationale, then traces every requirement to the test or analysis that will verify it.
Interface control documents
The ICD tables it drafts and cross-checks carry connector pin-outs, voltage limits and message formats, with an owner named for every interface.
Engineering calculations and design basis
It assembles each calc package with load cases, inputs, the adopted code edition and margins, then reruns the arithmetic independently.
Decision analysis and trade study
For a trade study it scores the options against the weights the team agreed before scoring, then perturbs each weight and flags where the ranking flips.
FMEA and control plan
DFMEA and PFMEA rows come drafted from drawings, field returns and past failures, and every line stays linked to the control plan the PPAP submission needs.
Hazard analysis
You get the HARA, HAZOP and MIL-STD-882E worksheets laid out with causes, consequences and safeguards, while every risk rating stays with the review team.
Design review package
Before PDR or CDR it checks your design data against the standard’s entrance and success criteria, and lists the gaps that would draw a RID at the board.
Design of experiments
Run sheets cover screening fractions through response-surface designs, with factor levels, center points and the analysis approach named before the first run.
Verification test plans and reports
Every requirement in the DVP&R gets a verification method and acceptance criterion, and the test reports state deviations and failed data plainly.
Engineering change request and impact
Where-used searches over drawings and BOMs feed the ECR it drafts, which spells out form-fit-function, disposition options and what needs re-validation.
Root cause analysis and CAPA
From your failure data it writes the CAPA record, ties the evidence to each suspected cause and drafts the effectiveness check before you act.
Product compliance technical file
The compliance file builds up clause by clause against the UL, IEC, FCC and CE standard PDFs you supply, with test reports and risk assessment mapped in.
Proposals and RFP responses
Every Section L and M requirement goes into the compliance matrix first, and the technical volume is written against it, row by row.
Project schedule
The WBS and logic-linked schedule it builds show the critical path through the reviews and tests, and the buffer goes where it protects the dates.
Project budget and cost forecast
Actuals and commitments become monthly cost reports with a bottom-up EAC and the fee burn your chief engineer asks about.
- Office skills
- Excel, Word, PowerPoint, PDF
- Tools
- Read, edit and write files, Search files, Run code, Search and read the web, View images
- Connectors
- SharePoint, Google Drive, Gmail, and additional custom connectors
- House style
- Your fonts, layouts and rules, on every file
How it works
- 1
Open the program folder
It reads the folder the way your team keeps it: the SOR and SOW, specifications, ICDs, drawings, the calc workbook, last program’s test reports and the standards you hold licenses to.
- 2
Ask for the document
Name the artifact and its constraints, and it builds the workbook or document in your house format, with each input traced to the file it came from and the assumptions written out for you to challenge.
- 3
Review like a checker
Every number carries its source file and every clause the edition you adopted, so the trail is there for your spot checks before you sign. Ultramarine Work never signs, approves or files anything, and nothing reaches the board unread.
Who it’s for
Mechanical, electrical, electronics, hardware, test, reliability, aerospace, systems and biomedical engineers who develop products and systems, through chief engineers.
Questions
Can I trust the calculations it runs?
The numbers come from code it writes and executes, not from the model predicting an answer, and every input names the file it came from. You check the output the way you would a new engineer’s work, because the checker sign-off on the calc package stays yours.
Will it invent standards clauses or cite the wrong edition?
No, it cites the document and clause behind every statement, and it reports anything it cannot find or reconcile rather than filling the gap. Put the PDFs of the standards in the folder with the editions you adopted, then confirm each citation before the file leaves you, because what it quotes is what you supplied.
Can we put ITAR-controlled technical data in it?
That call belongs to your export control office, not to the tool or its maker. Ultramarine Work changes files only in the project’s folder. When a request needs it, it can read files elsewhere on your computer, never passwords, keys or app data, and you can turn that off in settings. The model runs on Paper Instruments’ servers, so the content it works on is sent there to be processed. Paper Instruments is SOC 2 Type II, and our security and compliance details are on our compliance page.
Who signs the calc package and the FMEA?
You sign the package, every time. Ultramarine Work drafts, checks and organizes the work, and the approval is yours. Review every file it touched before the package goes to the review board or the customer, because the engineering decision on each hazard, margin and change is yours.
Will new documents match our templates?
Yes, provided your templates and a recent document are in the folder for it to work from. It follows the fonts, layouts and conventions it finds there, so the DVP&R it drafts looks like the one your board approved last time.