Reliability decisions · Inspectable methods · Traceable evidence

Reliability analysis that shows its work.

Perdura connects reliability requirements, prediction, test planning, life and field data, system risk, maintenance, and reporting in one workspace. Results retain their assumptions, uncertainty, diagnostics, and source analysis so engineers can judge whether an answer is adequate for the decision—not merely whether a calculation completed.

perdurare — Latin, “to endure, to last.”

18+reliability analysis modules
13supported life distributions
24accelerated-life model classes
0central project-data stores
Engineering workflow

From reliability requirements to field performance

Reviewable analysis

  • Keep inputs, assumptions, parameterization, units and results in the same project.
  • Inspect equations, algorithms, API contracts and methodology records.
  • Distinguish verified, approximate, screening and unsupported method scopes.
  • Package exports with optional checksums, software identity and analysis fingerprints.

Connected decisions

  • Set reliability or MTBF targets and apportion requirements to subsystems.
  • Use prototype, qualification, field and warranty evidence in the appropriate model.
  • Evaluate system configurations, failure paths, conditions of use and maintenance strategies.
  • Carry fitted distributions and predicted rates into downstream analyses without re-entry.

Qualified results

  • Check model eligibility, convergence, identifiability and supported data regimes.
  • Attach uncertainty to the engineering quantity being used where supported.
  • Compare fit and diagnostics instead of selecting a model by one score alone.
  • Use sensitivity and importance measures to expose the assumptions driving a conclusion.
Verification & model assurance

Quality is tied to evidence, not test count

Perdura checks model identity, equations, capability coverage, statistical calibration, adverse numerical regimes, and end-to-end result semantics. Standards implementations identify their mapped scope and exclusions; unsupported inference is disclosed rather than silently presented as an ordinary result.

Reliability information & reporting

Carry analysis evidence into the design review

Named projects retain inputs, units, models, results and analysis relationships across modules. The Report Builder combines plots, tables, method context and engineering rationale into paginated PDF or interactive HTML. Optional verification packages bind exported bytes to software, project and analysis metadata using deterministic SHA-256 records.

  • Preserve analysis state in human-readable JSON project files
  • Identify stale results when an upstream input or analysis changes
  • Standardize recurring reviews with reusable report templates
  • Verify packaged artifacts independently using their provenance manifest
Review analysis capabilities

Put Perdura into your reliability workflow

Download a packaged release with its build evidence for Linux, macOS or Windows. Build from source when the implementation itself is part of the review.