Skip to content
Arc
Menu

Defence

Requirements management for defence programmes.

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

Book a demo

02Engineering challenges

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.

03How Arc helps

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.

Inspect the fictional supplier requirement

Illustrative engineering example: a fictional supplier proposes a connector pin-assignment change. The same interface, safety, hazard and qualification records remain connected through review.

This example supplies no customer programme, qualification pass, hazard reduction or compliance verdict. Information-handling and deployment suitability require a separate programme assessment.

Illustrative engineering example · Supplier connector change

Candidate interface

IF-04

Supplier and interface review

Pending

  • IF-04reviewed against

    Safety requirement

    SAF-07

    Safety owner

  • IF-04contributes to

    Hazard context

    HAZ-03

    Safety review

  • IF-04supported within prior scope by

    Qualification record

    QUAL-02

    Previous configuration · evidence owner

Awaiting interface, safety and evidence review

Requirement record
Supplier interfaceIF-04Candidate revision
Proposed change
Connector pin assignment
Source obligation
Contract and supplier acceptance criteria to review
Safety requirement
SAF-07
Hazard control context
HAZ-03
Qualification reference
QUAL-02, previous configuration
Owner
Supplier and interface owners

Awaiting interface, safety and evidence review

Illustrative engineering example. Contract and supplier review remain separate from safety assessment and evidence applicability.
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.

Inspect the fictional interface comparison
Illustrative engineering example · Supplier connector change

IF-04 supplier connector proposal

Connector pin assignment

Current

Previous assignment · detail not supplied

Proposed

Candidate assignment for review

Affected records

  • IF-04 supplier connector proposal

    SAF-07

    Safety requirement review

  • IF-04 supplier connector proposal

    HAZ-03

    Hazard-control assessment

  • IF-04 supplier connector proposal

    QUAL-02

    Applicability of previous-configuration evidence remains pending

  • The example specifies no pin numbers or accepted interface change.
  • Contract and supplier acceptance review are separate from safety and evidence applicability decisions.

Awaiting interface, safety and evidence review

Full change comparison
IF-04 supplier connector proposal
Record / valueCurrentProposed
Connector pin assignmentPrevious assignment · detail not suppliedCandidate assignment for review
Safety requirement referenceUnchangedSAF-07SAF-07
Hazard context referenceUnchangedHAZ-03HAZ-03
Qualification recordUnchangedQUAL-02, previous configurationQUAL-02, previous configuration

Unchanged constraints

  • The example specifies no pin numbers or accepted interface change.
  • Contract and supplier acceptance review are separate from safety and evidence applicability decisions.

Affected records

SAF-07
Safety requirement review
HAZ-03
Hazard-control assessment
QUAL-02
Applicability of previous-configuration evidence remains pending

Awaiting interface, safety and evidence review

Illustrative qualitative comparison. No hazard reduction, qualification pass or accepted interface revision is implied.

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.

Inspect the fictional agent proposal
Illustrative engineering example · Supplier connector change

Sources

  • IF-04
  • SAF-07
  • HAZ-03
  • QUAL-02

Finding

The prior qualification record does not resolve its applicability to the proposed connector assignment.

Proposed action

Ask the interface, safety and evidence owners to assess the candidate, record their dispositions and identify any further verification before acceptance. Keep contract and supplier review explicit.

Engineer review

Awaiting interface, safety and evidence review

This fictional finding does not establish hazard reduction, compliance or information-handling suitability. Risk acceptance remains with the programme’s responsible authority.

Source and proposal detail

Sources

  • IF-04

    Candidate supplier connector pin-assignment revision.

  • SAF-07

    Connected safety requirement requiring responsible review.

  • HAZ-03

    Connected hazard-control context.

  • QUAL-02

    Evidence covers the previous configuration only.

Finding

The prior qualification record does not resolve its applicability to the proposed connector assignment.

Proposed action

Ask the interface, safety and evidence owners to assess the candidate, record their dispositions and identify any further verification before acceptance. Keep contract and supplier review explicit.

Awaiting interface, safety and evidence review

This fictional finding does not establish hazard reduction, compliance or information-handling suitability. Risk acceptance remains with the programme’s responsible authority.

Illustrative sourced proposal. It is not an executed assurance assessment or a risk-acceptance decision.
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.

Inspect the fictional assurance trail
Illustrative engineering example · Supplier connector change
  1. 01

    Candidate interface revision

    IF-04

    Connector pin-assignment proposal

    Pending

    reviewed against
  2. 02

    Safety requirement

    SAF-07

    addresses
  3. 03

    Hazard-control context

    HAZ-03

    supported within prior scope by
  4. 04

    Qualification record

    QUAL-02

    Previous configuration

    reviewed for candidate applicability
  5. 05

    Applicability and acceptance decision

    Awaiting interface, safety and evidence review

    Pending

QUAL-02 retains its previous-configuration scope. Any new verification and the acceptance decision remain open.

Illustrative assurance trail. Previous qualification scope is retained. Applicability to the candidate is pending.

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.

Inspect the fictional acceptance review
Illustrative engineering example · Supplier connector change
Main developmentProposed branch
  1. 01Source records

    Previous IF-04 / QUAL-02 scope

    Main development
  2. 02Supplier proposal

    IF-04 candidate assignment

    Proposed branch
  3. 03Review

    Contract and supplier acceptance criteria

    Proposed branch
  4. 04Safety review

    SAF-07 / HAZ-03

    Proposed branch
  5. 05Pending evidence review

    QUAL-02 applicability

    Proposed branch
  6. 06Awaiting review

    Interface, safety and evidence owners

    Proposed branch
  7. 07Pending decision

    Merge only after acceptance

    Proposed branch

Responsible review

  • Supplier and interface owners
Baseline and configuration detail
Main developmentProposed branch
  1. 01Source records

    Previous IF-04 / QUAL-02 scope

  2. 02Supplier proposal

    IF-04 candidate assignment

  3. 03Review

    Contract and supplier acceptance criteria

  4. 04Safety review

    SAF-07 / HAZ-03

  5. 05Pending evidence review

    QUAL-02 applicability

  6. 06Awaiting review

    Interface, safety and evidence owners

  7. 07Pending decision

    Merge only after acceptance

Programme baseline
Meaning
The named requirement, interface and assurance state assessed at a programme review, including unresolved findings and their dispositions.
Assessed configuration
Meaning
The equipment and software state covered by qualification evidence. QUAL-02 covers the previous configuration, not an approved candidate.
Illustrative review path. Accountable review precedes acceptance. It supplies no approved baseline or completed merge.
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.

04Standards and assurance scope

Keep the invoked assurance scope and its owners clear.

Apply MIL-STD-882E where invoked for system safety, alongside programme-specific requirements, assurance and configuration obligations.

Link invoked tasks and contract obligations to requirements, allocated owners and evidence. Keep safety assessment, supplier acceptance and risk-acceptance decisions separately identifiable.

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.

Agree supplier exchanges, API access and deployment.

Retain contract sources and supplier revisions beside their interface and acceptance records. Define interchange mappings and information-handling permissions for the programme.

APIMCPSecurity and deployment
API and MCP
Connect supported records through the API, or give a compatible agent permitted programme context and tools through MCP. Agree mappings, permissions and 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.

05FAQ

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 API or MCP 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.

06Engineering resources

Engineering resources

Browse the blog
  1. Change review in ArcFollow branch changes through review before merge.Product
  2. Security and deploymentReview hosting, access, AI processing and rollout responsibilities.Product
  3. Requirements traceability guideFollow a requirement from its source through allocation, results and evidence.Guide

07Next step

Review your programme workflow in Arc.

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

Book a demo