Which projects fit?
For comparing designs, diagnosing coupling or preparing tests. Establish an interpretable single-component, single-scenario baseline for higher-risk models.
Simulation Outsourcing
New Horizon supports design verification, alternative comparison and multidisciplinary integration with models, scenarios, configurations, raw results and analysis methods. Conclusions state parameter provenance, numerical settings and validity limits so recipients can rerun key results.
Last updated: 2026-10-13 · Provider: New Horizon Digital Outsourcing Team
View delivery and acceptance detailsIndex
Deliverables
| Type | Description |
|---|---|
| Scenarios and models | Scenarios, geometric/physical models, and parameter tables |
| Projects and scripts | Reproducible runnable projects (source-code scope by agreement) |
| Analysis materials | Metrics, curves, comparative findings, and risks |
| Acceptance materials | Reproduction steps, version baselines, and result verification records |
Our approach to value for money draws on years of project experience and lean team operations: reusing model libraries, scenario templates, and toolchains to reduce duplicated development. Our aspiration is “around 10% of the budget and 30% of the time, aiming for a 100% increase in efficiency.”
Buying software provides a tool license; outsourcing delivers scenarios, models, reproducible projects, and findings tailored to your task. New Horizon can also provide custom-development source code within an agreed scope.
It supports concept assessment, algorithm comparison, task-chain verification, and presentation and defense. Fixing metrics and scenario boundaries earlier reduces iteration costs.
Agree on interface versions, random seeds/initial values, operating-condition tables, and runtime environment inventories, then rerun key conditions step by step during acceptance.
Yes. Models and operating conditions developed through simulation can provide baseline inputs for digital twin operation. See the Digital Twin Outsourcing domain for details.
Validate session boundaries in a shared simulation service through non-interference between concurrent sessions, state reassociation after disconnection, and post-termination resource checks.
Check the path from algorithm outputs to monitoring displays through field identity, display sampling, alert definitions, and stored results.
Build an independently reviewable component integration workflow around algorithm boundaries, exchanged data, internal state, and execution order.
Define preconditions, configuration activation, and completion evidence for simulation states so the interface remains consistent with execution.
An AFSIM project must first clarify whether it serves public research, educational demonstrations, or authorized mission analysis, and confirm permissions to use the software, models, and data.
The key to electromechanical–thermal coupling is connecting mechanical loads, electrical losses, and temperature feedback.
A smaller time step does not necessarily produce credible results.
There is no fixed number of stochastic simulation runs that suits every project.
Coverage analysis should define the target area, time window, observation constraints, and statistical conventions.
Software-in-the-loop is suited to rapid checks of algorithms and interface logic; hardware-in-the-loop enables further checks of real controllers, communications, and timing behavior.
Establish an evidence chain covering simulation inputs, model assumptions, numerical checks, experimental comparisons, and applicability limits, rather than substituting animation for findings.
Compare simulation outsourcing with software procurement to help decide between external services and in-house modeling.
Other service domains
Engineering delivery brief
For comparing designs, diagnosing coupling or preparing tests. Establish an interpretable single-component, single-scenario baseline for higher-risk models.
Collect geometry and topology, materials and loads, initial and boundary conditions, target metrics and available test or analytical references. Separate measured values, supplier data and assumptions awaiting calibration.
Successful execution, plausible visuals and smooth curves are not physical validation. Without independent references, report numerical consistency and sensitivity rather than real-system accuracy.
Degrees of freedom, coupling, scenario count, computing resources and calibration data drive effort. Agree on error criteria and compute budgets before choosing meshes, time steps and experiment sets.
Acceptance Evidence
Review units, provenance, assumptions and validity ranges.
Acceptance Evidence
Fix versions, initial states, seeds and solver settings, then independently rerun key scenarios.
Acceptance Evidence
Retain raw outputs, metric extraction, convergence comparisons and reference errors; distinguish validated and uncalibrated items.
Related case study
Connect CAD preparation, material and boundary definitions, mesh comparisons and temperature-field review for a complex internally heated housing, with reproducible thermal-analysis deliverables.
Read the full case studyRelated standards and technical documentation for solution selection and implementation.
Describe your phase objectives and constraints without classified details, and we will provide scope recommendations.