Skip to content

Defence

Requirements management for defence programmes.

Connect capability intent, supplier interfaces and verification evidence. Keep requirements, changes and programme decisions under review.

02

Carry programme intent through every handoff.

Acceptance reviews need the obligation, its owner and the evidence behind the decision.

  1. Obligations cross supplier boundaries

    Programme, prime and supplier requirements need a retained source, allocation and accountable acceptance owner.

  2. Variants outgrow earlier qualification

    An interface or component change can affect several equipment variants. Earlier qualification has a specific assessed scope.

  3. Open decisions reach the milestone

    Contract, safety and evidence decisions have different owners. Each unresolved review needs to remain visible.

03

Connect capability intent to programme acceptance work.

Retain the obligation, source and owner behind each requirement and review decision.

Capability and supplier context

Retain the source of each obligation.

Connect capability intent to allocated equipment requirements and supplier interfaces. Keep contract sources, revisions and acceptance responsibilities with the record.

Arc FOREST-3 demo requirements table with REQ-013 marked Needs re-verification
Arc FOREST-3 demo. REQ-013 has a candidate change from 150 to 200 W and is marked Needs re-verification.

Programme changes and agents

Follow the consequences of an interface change.

Trace the candidate revision into safety, hazard and qualification records. Keep supplier acceptance, safety review and evidence applicability as distinct decisions.

Review sourced agent proposals.

Agents help trace obligations and identify missing context or evidence. Programme engineers inspect the source records and decide which proposed actions to accept.

Arc FOREST-3 demo impact analysis showing a proposed branch and conflict notice
Arc FOREST-3 demo. The impact view shows an unapproved branch and a conflict notice for review.

Qualification and accountable review

Keep qualification scope identifiable.

Connect the requirement, assessed equipment configuration and qualification evidence. Retain the earlier scope while applicability to a candidate revision is reviewed.

Bring acceptance owners into the branch.

Review proposed work with supplier, contract, safety and verification owners. Keep pending decisions visible before accepting a programme baseline.

Arc FOREST-3 demo test record with a retained Pass marked Needs re-verification
Arc FOREST-3 demo. A retained Pass is marked Needs re-verification. The screenshot shows no rerun.

04

Keep applicable standards and guidance connected.

Select the standards and guidance invoked by the programme and contract, including MIL-STD-882E system safety activities where applicable.

Connect technical and process obligations to requirements, owners, reviews and assurance evidence. Monitor and report their status against the contract editions and tailoring, with supplier acceptance and risk acceptance assigned to the responsible authorities.

Use the editions, tasks and acceptance authorities agreed for the programme. Connected records support that process. Risk acceptance and compliance decisions remain with responsible authorities.

MIL-STD-882E
System safety activities and tasks invoked by the solicitation or contract.
Contract and supplier obligations
Agreed allocations, acceptance criteria, evidence and accountable authorities.
Information handling
Deployment, access, AI processing and handling requirements for the actual information involved.

Connect supplier and configuration records through the API.

Retain contract sources, supplier revisions and equipment configurations beside their interface and acceptance records. Use supported API operations with agreed mappings, information-handling permissions and engineer review.

API
Connect supported records and evidence references through API operations. Agree mappings, permissions and engineer review for the workflow.
Deployment and AI keys
Discuss deployment in your own AWS or Azure infrastructure under an agreed setup. Bring your own key is available for supported AI providers. Agree access, processing locations and retention for the programme.

05

Frequently asked questions

What does Arc connect for a defence programme?

Arc connects capability intent, contract and equipment requirements, supplier interfaces, proposed changes and verification evidence. Sources, allocations and owners remain available for programme and acceptance review.

How can Arc support a supplier interface-change review?

Trace the proposed revision through the affected equipment, safety, hazard and qualification records. Retain the earlier qualification scope and review candidate applicability. Contract and supplier acceptance decisions remain distinct from safety and evidence assessment.

Can Arc help organise MIL-STD-882E activities?

MIL-STD-882E activities and tasks apply where invoked by the solicitation or contract. Arc can connect those obligations to safety requirements, hazard records, evidence and review owners. The responsible programme authority retains risk-acceptance decisions.

Does earlier qualification evidence cover a changed equipment variant?

Earlier evidence retains the configuration and scope it assessed. Review the changed interface, requirement revision and intended use to determine what remains applicable and which further verification is required.

How can primes and suppliers coordinate requirement ownership?

Retain the source obligation, allocation, interface definition and accountable acceptance owner. An agreed branch review can expose the affected records and outstanding decisions across the programme and supplier handoff.

Who accepts a change suggested by Arc’s agents?

The responsible engineers and programme authorities review the sources, finding and proposed action. Agents help inspect requirements and evidence gaps, while contract, safety and risk-acceptance authority remains with the designated people.

Can Arc support an agreed customer-cloud deployment?

Discuss customer-owned AWS or Azure infrastructure, supported AI-provider keys and the supported API operations required for the programme. Agree access, processing locations and retention against the actual information-handling requirements.

What can we cover in a defence requirements demo?

A demo can follow a representative obligation through a supplier interface, proposed change and acceptance-evidence review. Book a demo to discuss the programme workflow and deployment scope.

Move faster without compromising engineering rigour.

See how requirements, supplier changes and acceptance evidence stay connected through review.