Engineering, manufacturing and test

Connect the requirement to the result.

Scope the integration, build, test or study around the decision it needs to support. Start with a defined boundary and the evidence the work needs to produce.

What you can buy.

CC-100 mission systems

Power, control and local computing for remote operations. Add the core to installed equipment or define a complete site.

The work
Core Retrofit or Continuity Node, with the operating policy and acceptance scope defined together.
Where to start
Power sources, connected loads, workload priorities and recovery requirements.
Explore the configurations

FORGE production and qualification

Manufacturing, inspection and test for the hardware your system depends on.

The work
A build or test scope tied to the article, its configuration and its acceptance requirements.
Where to start
Drawing revision, materials, article interfaces, environmental conditions and the result you need.
Explore FORGE

NEXUS infrastructure studies

Compare what to build, what to buy and how the mission's dependencies connect.

The work
A sourced brief, dependency map and structured comparison.
Where to start
The infrastructure decision, operating assumptions and alternatives under consideration.
Frame a study

WIRES power-transfer measurement

Connect a power-transfer question to the boundary, method and evidence needed to answer it.

The work
A measurement boundary, method and instrumentation scope.
Where to start
The sending and receiving interfaces, operating conditions and quantity to measure.
Define a measurement

Everlight cislunar infrastructure

Power and navigation for lunar operations, with communications and awareness in the same architecture.

The work
A mission infrastructure scope covering the operating site and the interfaces it needs.
Where to start
The mission, power and timing needs, communications path and operating environment.
Explore Everlight

Work scopes

Find the right starting point.

8 work scopes

Mission systems

System integration

Connect source conditions, load priorities and application behavior around a defined operating policy.

Scope output
Interface map, configuration baseline and integration scope.
Starting requirement
Bring the equipment interfaces, workload requirements and recovery priorities.
Map an integration

Mission systems

Configuration acceptance

Turn expected system behavior into a repeatable acceptance sequence for a defined site and workload.

Scope output
Acceptance criteria, event sequence and evidence requirements.
Starting requirement
Define normal operation, resource constraints, disconnection and return to service.
Define acceptance

Mission systems

Fleet energy architecture

Scope the power and charging boundary around an uncrewed operation's duty cycle, site resources and equipment interfaces.

Scope output
Site energy architecture, charging priorities and an interface scope.
Starting requirement
Start with the fleet's energy demand and the operating schedule.
Scope fleet power

FORGE

Manufacturing and integration

Bring a defined hardware requirement into the same scope as its manufacturing, inspection and configuration record.

Scope output
A build scope, inspection plan and article record.
Starting requirement
Start with the drawing revision, material requirements and acceptance criteria.
Discuss a build

FORGE

Optical and thermal-vacuum campaigns

Define optical and environmental measurements around the article, the operating conditions and the engineering decision.

Scope output
A test scope, measurement conditions and evidence package.
Starting requirement
Specify the environment, article interfaces and result you need to resolve.
Scope a test

FORGE

Power and interface test

Specify how a power event, control interface or restart sequence will be observed against a defined requirement.

Scope output
Test boundaries, event cases and a configuration-linked result format.
Starting requirement
Bring the operating sequence and the conditions the system needs to handle.
Define a test sequence

NEXUS

Mission infrastructure studies

Compare power, communications and logistics dependencies with their sources, assumptions and system boundaries attached.

Scope output
A sourced brief, dependency map and structured comparison.
Starting requirement
Start with the infrastructure decision and the alternatives under consideration.
Frame a study

WIRES

Power-transfer measurement

Define what enters a power interface, what reaches the receiving side and how the measurement will account for uncertainty.

Scope output
A measurement boundary, method and instrumentation scope.
Starting requirement
Name the interface, operating conditions and quantity the measurement must resolve.
Define a measurement

The FORGE program

Keep the build and its record together.

Connect the engineering requirement to the build, the inspection and the test record. FORGE brings manufacturing and qualification into the same conversation as power and control.

Inside FORGEExplore published methods

Support the next revision.

Keep follow-on work tied to a defined configuration, measurement or interface change.

  1. Configuration changes

    Scope the effect of a new component, drawing revision or operating policy on integration and acceptance.

  2. Repeat measurement

    Define a repeat campaign against the same boundary and method so results remain comparable.

  3. Interface updates

    Review a changed interface against the equipment, documents and tests that depend on it.

Discuss continuing support

Start a conversation

Bring us the operating requirement.

The sources. The loads. The work that matters. Start with what your system needs to do.

Start a technical discussion