Skip to content

Can this hardware fly, and how do you know?

IPAC reads your quality record, your approved vendor list and the conditions across the window, and returns the one thing no PLM or spreadsheet gives you: a flight-readiness call with the pedigree, the open nonconformances and the evidence attached to it.

Powered by Schubring Global Solutions

ipac / space-systems / command-center
Elevated risksynthesized 06:14

Three conditions stand between MV-1 and the window.

Build state is nominal; forward readiness is elevated. Pedigree gaps on installed thermal-protection tiles, one nonconformance still awaiting a Material Review Board disposition, and a composites vendor approaching qualification expiry are driving the posture.

3
Decisions requiring attention
6
Installed parts missing pedigree
2
Open nonconformances
9d
Until the window opens
CRITICAL93%· High

Close pedigree gaps on installed TPS tiles

Affected
6 serialized parts
Vendor
Tessera Composites
Mission
MSN-004
Why this matters

6 tiles already bonded to the aeroshell have a certificate of conformance on file but no material certification, so their pedigree chain is incomplete at the point it would be examined.

Recommended action

Request the missing material certifications from Tessera Composites and hold the flight-readiness review until the six chains close or the tiles are dispositioned.

Risk of inaction

A readiness review that cannot evidence material provenance for installed hardware, eight days before the window opens.

Review DecisionView Evidence7 supporting records

What changed · since yesterday

  • Installed parts missing a material cert+4worse
  • Nonconformances awaiting MRB−1better
  • Single-source parts on the critical path+2worse
  • Vendor qualifications expired0unchanged

What IPAC is watching next

  • Tessera Composites · NADCAP composites renewalin 21d
  • MSN-004 · rideshare window opensin 9d
  • NCR-2026-0148 · MRB disposition duein 18h

IPAC Command Center, Space Systems Intelligence lens. Representative interface, reference environment data.

Another dashboard isn't the answer.

Nobody building flight hardware is short of records. The certificate of conformance arrives. The material cert arrives. The first-article report, the nonconformance, the calibration recall, the vendor audit finding. All of it arrives, most of it on time, and most of it into a different system from the last one.

What does not arrive is the judgment. Which of those things actually changes the readiness of a vehicle. What it puts at risk in this window. Whether it can wait until after the review. And when a prime or an auditor asks eighteen months later, what the basis for the call actually was.

A dashboard hands that work back to the quality lead, arranged more neatly. It moves the problem; it does not finish it. So the team buys another one, and the number of screens goes up while the number of defensible readiness calls stays exactly where it was.

More signal has never once produced more clarity. IPAC is built the other way round: it starts from the call that has to be made before the window and works backwards to the evidence that justifies it.

Flight readiness is a judgment, not a status field.

One path from a receiving inspection to a call that holds up.

Every decision IPAC produces runs the same path, whether it starts at a lapsing vendor qualification, a nonconformance on a bonded tile, or a range forecast three days before the window opens.

  1. 01

    Signal

    Observations arrive continuously and fold into one evolving thread per condition. One thread for a lapsing vendor qualification, not a fresh alert every morning about the same lapse.

    government · commercial · your own quality record

  2. 02

    Context

    Each thread is bound to what it actually touches: this serialized part, this approved vendor, this vehicle, this launch window.

    part · vendor · vehicle · mission

  3. 03

    Exposure

    Scoring converts the condition into what it puts at risk, against a baseline that means something in hardware: pedigree coverage, open nonconformances, qualification currency.

    scored against baseline

  4. 04

    Recommendation

    A specific, time-bound action, with the confidence behind it and what it costs to carry the condition past the window.

    confidence · risk of inaction

  5. 05

    Evidence

    The action, its inputs, and the records it relied on are captured as one versioned decision record, with every document referenced by its digest.

    versioned · reviewable · durable

Export control

What IPAC holds, and what it will not hold.

IPAC stores metadata, cryptographic hashes, and non-technical documents. It does not host ITAR-controlled technical data. Drawings, models, analysis, and test data stay in your systems; IPAC references them by SHA-256 digest, so a decision record can prove exactly which revision it was made against without the file ever leaving your control. The hosting reality behind that statement: IPAC runs on Google Cloud in us-central1, with no Assured Workloads enclave and no US-persons access control. If your program requires either, IPAC is not the place to put controlled technical data today. We would rather say that here than have you find it in week six.

What is stored, what is not, and where it runs

Most hardware risk is legible before it is urgent.

The gap is rarely that a signal was missing. It is that the signals were individually unremarkable, arrived on different days, sat with different people, and nobody was holding them together against the window.

ipac / space-systems / predictions
TrajectoryRising+12 risk points week over week
46%
Disruption probability
118
Risk points
9
Active signals
2
Signal correlations
Disruption probability · last 15 snapshots21% to 46%

Signal correlations

  • Vendor Qualification Risk

    CRITICAL
    81%· Moderate7d windowquality + logistics

    A quality escape and two late deliveries from the same approved vendor inside one window, against parts on the critical path.

    Open a supplier corrective action and qualify a second source before the next build.

  • Schedule Compression Risk

    HIGH
    74%· Moderate14d windownonconformance + calibration

    An open Material Review Board item and a lapsing calibration on the acceptance test stand may compress the pre-window schedule.

    Sequence the MRB disposition ahead of the calibration recall, not after it.

What IPAC is watching next

  • Tessera Composites · NADCAP composites renewalin 21d
  • MSN-004 · rideshare window opensin 9d
  • NCR-2026-0148 · MRB disposition duein 18h

Neither correlation above would have raised an alert on its own.

Predictions surface. Representative interface, reference environment data.

01Correlation across weak signals
A late delivery is noise. A quality escape is noise. Inside the same window against the same approved vendor, they are a qualification problem. IPAC carries named composite rules that fire on the combination, not the parts.
4 composite rules · 3 to 30 day windows
02Trajectory, not snapshot
Posture is scored on every run and kept. What matters is not today's number but its direction and rate of change across the last thirty, which is what turns a reading into a warning.
disruption probability · week-over-week delta
03Dated forward watch
Qualifications expire, calibrations come due, first articles get scheduled, windows open and close. IPAC holds the calendar of things that will become decisions and surfaces them while there is still room to act.
next material event · time to act
04Scenario simulation
Ask what happens if a vendor is disqualified, a lot is scrapped, or a qualification is suspended. IPAC walks the entity graph to the parts and missions actually downstream and returns a blast radius with a recovery window.
graph-backed · recovery window · stated basis

These are scored heuristics over your own graph, not a forecasting model with a track record. The recovery windows are industry ranges and are labeled as such in the product. IPAC will tell you what is converging and how much room you have left against the window; it will not tell you what Tuesday holds.

What comes out

This is the output.

Not a chart that has moved. A named action, on named parts and named vendors, with the confidence behind it, the cost of waiting past the window, and the records it stands on.

Six thermal-protection tiles are already bonded to the aeroshell and each one is short a material certification. IPAC names the six, not the hundred that are fine.

ipac / space-systems / missions / MSN-004 / readiness

Hold flight readiness pending pedigree closure

DEC-2291 · MV-1 · MSN-004 · window opens in 9d

CRITICAL
6
Parts missing pedigree
91%
Pedigree coverage
2
Open nonconformances
9d
To window open
Vehicle
MV-1
Launch provider
rideshare, manifest pinned
Why this matters

Pedigree coverage across installed serialized parts is 91%. The 6 open chains are all thermal-protection tiles from one vendor, and all of them are already bonded.

Recommended action

Hold the readiness review, request the missing material certifications, and put the six tiles in front of the Material Review Board if the certs do not arrive within four days.

Risk of inaction

A readiness signature given on hardware whose material provenance cannot be evidenced, with a fixed window and no rework time behind it.

Review DecisionView Evidence7 supporting records

Installed parts

93%· High
Serialized parts installed on MV-1, with station and how many of the three required pedigree documents are on file.
PartStationDocs
MV1-TPS-0142SN 0007Aeroshell 42 / 3
MV1-TPS-0142SN 0009Aeroshell 42 / 3
MV1-STR-0885SN 0031Frame 123 / 3
MV1-AVN-0310SN 0004Bay 23 / 3

Every serialized part carries a public pedigree address, so a prime or a payload customer can confirm provenance without an account.

Representative IPAC interfaces reproduced from the shipped product. Reference environment data throughout: Meridian Orbital Systems and MV-1 are fictional.

One lens, built for one industry, and we would rather it were deep than broad.

The engine is shared: ingestion, entity context, scoring, decisioning, evidence. What the Space Systems Intelligence lens brings is the baseline that makes a hardware signal mean something, and the shape of the decision at the end of it.


SSI

Space Systems Intelligence

The lens in detail
Who it is for
Spacecraft and launch-vehicle operators, satellite and payload manufacturers, and the aerospace suppliers who have to evidence what they shipped.
The nouns it speaks
Missions and launch windows, serialized parts and lot numbers, approved vendors and their qualifications, certificates of conformance and material certifications, first-article inspection, nonconformances and Material Review Board dispositions, and part pedigree.
The call it supports
Flight readiness: whether this vehicle is ready to fly in this window, and what the basis for saying so actually is.

Written for the industry rather than the product: space and aerospace.

The architecture in detail

Built for scrutiny

A recommendation without evidence is just another opinion.

Anything IPAC recommends can be opened. The factors that produced it and their weight. The sources, and when each was last retrieved. The confidence, stated as a number. The documents cited, with their digest, their version, and their review state, including the one that is missing.

The record is versioned, so a revision bump does not rewrite the readiness call that relied on the earlier revision. Eighteen months later the question “what did we know, and when” has an answer that does not depend on anyone’s memory.

ipac / space-systems / decisions / DEC-2291 / basis

Basis · Close pedigree gaps on installed TPS tiles

DEC-2291 · 2026-08-20 06:14 UTC
Contributing factors
  • pedigree coverage gap
    critical
  • open nonconformance
    high
  • vendor qualification currency
    medium
  • range conditions across window
    low
Evidence cited
3 items · 1 unresolved gap · 100% integrity checked
  • Certificate of conformance · MV1-TPS-0142 SN 0007
    v2 · reviewed · superseded v1 retained
    77ff05b2…a5035dverified
  • FAI report AS9102 · TPS-LOT-2291
    v1 · reviewed
    5b20e7c4…9d0f31verified
  • Material certification · SN 0007 to SN 0012
    gap · requested from vendor 2026-08-14
    noneevidence gap
Retained activity
  • 06:14Decision synthesized · confidence 93%
  • 05:02Ingestion run completed · 4 sources · 0 failures
  • Aug 18Evidence review state set to reviewed · K. Alvarez
  • Aug 17Certificate of conformance v2 uploaded · digest recorded
Chain anchor
entry 4,182 · prev 4,181
9b3c17aef2d40c8e5a71b0d94f2c6e8813ab5d7f0c2e94a16b3d8f5027ce41ab

Append-only SHA-256 chain. Each entry chains to the previous, so a later alteration is detectable. Internal, not a public ledger.

Decision basis view. Representative interface, reference environment data.

Part pedigree, checkable by people who will never log in.

A prime, a payload customer, an auditor. IPAC publishes a single claim at an unguessable address: part number, serial, revision, vendor, qualifications, and the digest of every document on file. Nothing else about the tenant it came from, and never the documents themselves.

How the security model is built
/verify/part/51595c91…
Pedigree verified
Confirmed 2026-08-15 · 04:12 UTC
Part number
MV1-TPS-0142
Serial number
SN 0007
Revision
C
Approved vendor
Tessera Composites
Vendor qualifications
AS9100D · NADCAP composites
Lot
TPS-LOT-2291
First article
AS9102 FAI accepted 2026-05-18
Installed on
MV-1 · aeroshell station 4
Documents on file
  • Certificate of conformance
    v2 · reviewed
    77ff05b2…a5035dverified
  • Material certification
    v1 · reviewed
    c41a9de0…12bb47verified
  • FAI report (AS9102)
    v1 · reviewed
    5b20e7c4…9d0f31verified
Certificate of conformance (SHA-256)
77ff05b24dc3c187acb74031955de4811ebfbcb22c566c17f69e79f9bea5035d

Metadata and digests only. No drawing, no analysis, no test data. Those stay in the operator’s systems and are referenced here by hash.

Public pedigree page at /verify/part/:token.

Independently examined under SOC 2 Type 1 and Type 2 by Sensiba.Type 2 period March 5 to June 5, 2024Scope and limits

Built by operators. Powered by SGS.

IPAC is developed by Schubring Global Solutions, whose work sits across security, risk, intelligence, and technology for organizations where being approximately right is not the same as being defensible.

That shows up in the product as a bias: state the limit instead of softening it, attach the evidence instead of asserting the conclusion, and never claim a capability the codebase does not have.

About IPAC and SGS

Bring us a readiness call your team made later than it should have.

We will walk it end to end: the signals that existed at the time, the exposure it carried against the window, and the record the call would have left behind. If IPAC would not have caught it earlier, we will say so.