# Arc

> Current Arc product and public API evidence, with complete discovery of published engineering articles, event guides and UK testing facility pages.

Updated: 6 October 2026

## Canonical identity

Arc is requirements management and verification software for fast-moving space engineering teams. It connects requirements, architecture, systems, interfaces, risks, verification activities and evidence in one programme model. Arc supports controlled engineering change and configurable AI assistance while engineers retain authority over reviews, approvals and programme baselines.

Arc's authenticated public REST API lets teams read programme context and carry out supported platform actions from custom clients. Teams can use it to connect Arc with their delivery, design, test and reporting tools, or to support external AI analysis and reviewable proposals. REST API actions, Arc's native agents and the Arc MCP server provide workflows for custom clients, platform assistance and compatible AI tools.

- Organisation: Arc
- Product: Arc requirements management and verification software
- Audience: Fast-moving space engineering teams
- Website: https://www.archelps.com/

## Product overview

- [Arc requirements management software for space teams](https://www.archelps.com/product/): Canonical product walkthrough, intended teams, workflow and supporting evidence.
- [Arc MCP server](https://www.archelps.com/mcp/): Permission-aware access for compatible AI tools to search programme records, navigate traceability, assess change impact and propose controlled updates.
- [Arc public REST API](https://www.archelps.com/content-for-ai/#capability-public-api): Read programme records, create branches, preview and apply supported changes, and manage pull requests through the authenticated public API.
- [Custom workflows across a team's stack](https://www.archelps.com/content-for-ai/#api-workflows): Practical delivery, design, test, reporting and external AI examples using Arc's API and other tools' interfaces.
- [Arc product evidence](https://www.archelps.com/product/#capabilities): Direct links from the product walkthrough to Arc's reviewed capability and security evidence.
- [Arc website](https://www.archelps.com/): Organisation overview and current requirements-management questions.
- [Content for AI](https://www.archelps.com/content-for-ai/): Canonical, reviewed product claims with delivery modes, engineering workflows and stable citation anchors.
- [Requirements management questions](https://www.archelps.com/#faqs): Current answers about migration, change, review, verification and deployment.

## Free Arc Skills toolkit

- [Arc Skills — 100 free systems and hardware engineering skills](https://www.archelps.com/skills/): Browse 99 worked task pages with copyable prompts, inputs, outputs and sources. Local MCP tools and standalone instructions; AI reasoning runs in the connected assistant.
- [Allocate requirements to systems and subsystems](https://www.archelps.com/skills/allocate-requirements-systems/): Propose requirement-to-system allocations with a reasoned ownership boundary.
- [Build a tender compliance matrix](https://www.archelps.com/skills/build-tender-compliance-matrix/): Organize bidder response obligations against tender clauses with evidence and unresolved exceptions.
- [Check whether a requirement is verifiable](https://www.archelps.com/skills/check-requirement-verifiability/): Assess whether objective evidence could decide a requirement at the stated level and configuration.
- [Clean and map a requirements spreadsheet](https://www.archelps.com/skills/clean-requirements-spreadsheet/): Prepare a source-preserving column map and reviewed import proposal from a messy requirements spreadsheet.
- [Compare child requirements to parent requirements](https://www.archelps.com/skills/compare-child-parent-requirements/): Assess whether existing children preserve, cover, or exceed a parent requirement.
- [Compare two versions of a requirements specification](https://www.archelps.com/skills/compare-requirements-specification-versions/): Produce a semantic change register between two controlled specification versions.
- [Define acceptance criteria for a requirement](https://www.archelps.com/skills/define-acceptance-criteria/): Turn an approved requirement into observable pass/fail criteria without inventing thresholds.
- [Derive interface requirements from an interface definition](https://www.archelps.com/skills/derive-interface-requirements/): Turn an agreed system boundary and exchanged items into candidate interface obligations.
- [Derive sub-requirements from a parent requirement](https://www.archelps.com/skills/derive-sub-requirements/): Propose child requirements that partition an approved parent obligation without losing or inventing intent.
- [Extract requirements from a customer document](https://www.archelps.com/skills/extract-customer-requirements/): Extract candidate obligations from a customer document with exact source trace and ambiguity flags.
- [Identify conflicting requirements in a specification](https://www.archelps.com/skills/identify-conflicting-requirements/): Find requirements whose simultaneous obligations cannot be reconciled under the same conditions.
- [Identify duplicate requirements in a specification](https://www.archelps.com/skills/identify-duplicate-requirements/): Identify exact and semantic duplicates while preserving distinct conditions and source obligations.
- [Identify missing requirements from operational scenarios](https://www.archelps.com/skills/identify-missing-scenario-requirements/): Find unsupported scenario transitions and exceptions that need requirement decisions.
- [Identify undefined terms in requirements](https://www.archelps.com/skills/identify-undefined-requirement-terms/): Find terms whose missing or inconsistent definitions materially change interpretation or verification.
- [Import requirements and links from ReqIF](https://www.archelps.com/skills/import-reqif-requirements-links/): Map ReqIF objects and relations into a reviewed local requirements proposal while preserving external IDs.
- [Resolve TBDs and TBCs in requirements](https://www.archelps.com/skills/resolve-requirement-tbds-tbcs/): Prepare source-backed decisions for unresolved requirement placeholders without silently choosing values.
- [Review a requirement against ECSS-E-ST-10-06](https://www.archelps.com/skills/review-requirement-ecss/): Review one requirement against an inspected, applicable edition of ECSS-E-ST-10-06 and return source-grounded findings.
- [Review a requirement against the INCOSE Guide for Writing Requirements](https://www.archelps.com/skills/review-requirement-incose/): Review one requirement against a user-accessible licensed INCOSE guide edition without inventing rules.
- [Review requirement rationale](https://www.archelps.com/skills/review-requirement-rationale/): Assess whether rationale explains the obligation and supports future change decisions.
- [Review supplier compliance claims against evidence](https://www.archelps.com/skills/review-supplier-compliance-evidence/): Challenge supplier claim strength against exact requirement, configuration, and supplied proof.
- [Rewrite a requirement using EARS](https://www.archelps.com/skills/rewrite-requirement-ears/): Rewrite a requirement in an appropriate EARS pattern while preserving its engineering intent.
- [Trace requirements back to stakeholder needs](https://www.archelps.com/skills/trace-requirements-stakeholder-needs/): Build an evidence-backed trace from technical requirements to stated stakeholder needs.
- [Allocate an end-to-end performance budget](https://www.archelps.com/skills/allocate-performance-budget/): Allocate a system performance limit across contributing stages and calculate remaining margin.
- [Allocate system functions to subsystems](https://www.archelps.com/skills/allocate-system-functions/): Perform functional allocation: allocate stated system functions to responsible subsystems and reveal unowned or overlapping behavior.
- [Build a system mass budget](https://www.archelps.com/skills/build-system-mass-budget/): Build a mass budget from component estimates, configuration, and a stated system allowance.
- [Build a system power budget](https://www.archelps.com/skills/build-system-power-budget/): Build a mode-specific electrical power budget from loads and source capability.
- [Check engineering margins against requirements](https://www.archelps.com/skills/check-engineering-margins/): Calculate signed engineering margin and judge it only against stated requirements and conventions.
- [Check units and dimensions in engineering calculations](https://www.archelps.com/skills/check-units-and-dimensions/): Check calculation expressions for unit consistency, conversions, and physical dimensional meaning.
- [Compare architecture alternatives in a trade study](https://www.archelps.com/skills/compare-architecture-alternatives/): Compare feasible architectures against stated decision criteria, assumptions, and evidence.
- [Decompose a system into subsystems](https://www.archelps.com/skills/decompose-system-into-subsystems/): Perform functional or product decomposition: propose a System hierarchy from responsibilities and physical or logical boundaries.
- [Define a system boundary and external actors](https://www.archelps.com/skills/define-system-boundary/): Define a system-of-interest boundary, external actors, and crossings from a stated mission or product scope.
- [Develop operational scenarios and off-nominal scenarios](https://www.archelps.com/skills/develop-operational-scenarios/): Write normal and off-nominal operational scenarios with triggers, actions, responses, and recovery paths.
- [Perform a make-or-buy technical assessment](https://www.archelps.com/skills/assess-make-or-buy/): Assess technical feasibility and integration consequences of building versus buying a component.
- [Review a functional architecture for missing functions](https://www.archelps.com/skills/review-functional-architecture/): Find missing or weakly allocated functions by walking scenarios, requirements, and function flows.
- [Review single points of failure in an architecture](https://www.archelps.com/skills/review-single-points-of-failure/): Identify architecture elements whose single failure may defeat a stated function or mission outcome.
- [Review system modes and transitions](https://www.archelps.com/skills/review-system-modes/): Review operating modes, guards, transitions, and recovery for ambiguous or unreachable behavior.
- [Write a concept of operations](https://www.archelps.com/skills/write-concept-of-operations/): Draft a concept of operations (ConOps) connecting actors, goals, phases, modes, and outcomes for a defined system.
- [Compare supplier and customer interface specifications](https://www.archelps.com/skills/compare-interface-specifications/): Compare two parties’ interface specifications and record matches, conflicts, and missing evidence.
- [Define an interface between two systems](https://www.archelps.com/skills/define-system-interface/): Define an engineering exchange between two Systems and propose its Interface relationship content.
- [Diagnose an integration failure from test evidence](https://www.archelps.com/skills/diagnose-integration-failure/): Use integration logs and configuration evidence to narrow a failure and propose discriminating checks.
- [Identify missing interface requirements](https://www.archelps.com/skills/identify-missing-interface-requirements/): Find interface behaviors that lack an explicit, allocated, verifiable Requirement.
- [Plan system integration order](https://www.archelps.com/skills/plan-system-integration-order/): Sequence subsystem integration using dependencies, test access, and fault-isolation needs.
- [Review a data interface specification](https://www.archelps.com/skills/review-data-interface/): Review a data exchange for syntax, semantics, timing, state, and error behavior.
- [Review a mechanical interface specification](https://www.archelps.com/skills/review-mechanical-interface/): Review mating geometry, loads, tolerances, access, and installation assumptions across two Systems.
- [Review an electrical interface specification](https://www.archelps.com/skills/review-electrical-interface/): Review an electrical interface for complete, consistent power, signal, grounding, and fault parameters.
- [Review interface timing and latency budgets](https://www.archelps.com/skills/review-interface-latency-budget/): Review end-to-end interface latency by tracing stages, bounds, clocks, and operating conditions.
- [Write an interface control document](https://www.archelps.com/skills/write-interface-control-document/): Draft an interface control document (ICD) from agreed System endpoints and controlled exchange details.
- [Assess whether test results demonstrate a requirement has been met](https://www.archelps.com/skills/assess-test-results/): Assess executed data against a specific requirement and approved acceptance rule.
- [Build a requirements verification matrix](https://www.archelps.com/skills/build-verification-matrix/): Build a traceable matrix from requirements to planned verification evidence.
- [Check whether a test procedure verifies a requirement](https://www.archelps.com/skills/check-test-procedure-coverage/): Compare an existing procedure’s actions and criteria with the full requirement obligation.
- [Define entry and exit criteria for a test campaign](https://www.archelps.com/skills/define-test-campaign-entry-exit/): Draft auditable readiness and completion gates for a bounded verification campaign.
- [Identify requirements without verification coverage](https://www.archelps.com/skills/identify-unverified-requirements/): Find baseline obligations lacking adequate planned Tests or current evidence.
- [Check verification evidence and plan re-verification after a change](https://www.archelps.com/skills/plan-change-reverification/): Choose targeted re-verification actions after a change using actual affected obligations and evidence.
- [Review a verification matrix against ECSS-E-ST-10-02](https://www.archelps.com/skills/review-verification-matrix-ecss/): Review matrix completeness and source-grounded ECSS-E-ST-10-02 obligations for a controlled edition.
- [Review environmental qualification test coverage](https://www.archelps.com/skills/review-environmental-qualification-coverage/): Check that qualification evidence spans approved environments, configurations, and requirement limits.
- [Review verification evidence configuration and applicability](https://www.archelps.com/skills/review-verification-evidence-configuration/): Decide whether existing verification evidence applies to the current requirement and product configuration.
- [Select a verification method for a requirement](https://www.archelps.com/skills/select-verification-method/): Choose a defensible inspection, analysis, demonstration, or test approach for one requirement.
- [Write a test procedure for a requirement](https://www.archelps.com/skills/write-requirement-test-procedure/): Draft executable steps and records that can verify a requirement on a defined article.
- [Write a verification close-out report](https://www.archelps.com/skills/write-verification-closeout-report/): Synthesize verification status and open exceptions for a named baseline and article.
- [Assess whether an engineering tool needs qualification](https://www.archelps.com/skills/assess-engineering-tool-qualification/): Assess qualification need from a tool’s intended use, output credit, and downstream error detection.
- [Check hardware assurance evidence against DO-254 objectives](https://www.archelps.com/skills/check-do254-hardware-assurance-evidence/): Assess airborne electronic hardware evidence against the approved DO-254/ED-80 basis and hardware DAL.
- [Check software assurance evidence against DO-178C objectives](https://www.archelps.com/skills/check-do178c-software-assurance-evidence/): Map supplied software lifecycle evidence to the applicable DO-178C objectives for an approved software level.
- [Review a NASA software requirements mapping matrix](https://www.archelps.com/skills/review-nasa-software-mapping-matrix/): Check applicability, tailoring, evidence, and approval in an NPR 7150.2D Appendix C mapping matrix.
- [Review a safety argument against its evidence](https://www.archelps.com/skills/review-safety-argument-evidence/): Challenge the links among safety claims, assumptions, subclaims, and configuration-specific evidence.
- [Review a standards applicability and tailoring matrix](https://www.archelps.com/skills/review-standards-applicability-tailoring/): Review the basis, scope, rationale, and approval of an engineering standards applicability matrix.
- [Review an ECSS compliance finding and its proposed closure](https://www.archelps.com/skills/review-ecss-compliance-closure/): Assess whether a proposed closure addresses a stated ECSS finding using current, applicable evidence.
- [Review development assurance level allocation rationale](https://www.archelps.com/skills/review-development-assurance-allocation/): Review the reasoning and authority trail for functional, item, software, and hardware assurance allocations.
- [Assess common-cause failures between redundant systems](https://www.archelps.com/skills/assess-common-cause-redundant-systems/): Examine shared exposures and dependencies that can defeat claimed redundancy in a defined architecture.
- [Build a fault tree for a hazardous event](https://www.archelps.com/skills/build-fault-tree-hazardous-event/): Construct a traceable Boolean fault tree for one defined top event and analyze its minimal cut sets and assumptions.
- [Derive safety requirements from a hazard analysis](https://www.archelps.com/skills/derive-safety-requirements-hazard-analysis/): Turn approved hazard controls into proposed measurable safety requirements with traceable rationale.
- [Perform a failure modes and effects analysis](https://www.archelps.com/skills/perform-failure-modes-effects-analysis/): Analyze credible item failure modes, their local and system effects, detection, and existing controls for a configured design.
- [Perform a functional hazard assessment](https://www.archelps.com/skills/perform-functional-hazard-assessment/): Assess loss and malfunction of intended functions across operating conditions and document candidate failure conditions.
- [Perform a preliminary hazard analysis](https://www.archelps.com/skills/perform-preliminary-hazard-analysis/): Identify credible early lifecycle hazards and record assumptions, controls, and follow-up evidence for a defined system concept.
- [Review an FMEA for missing failure modes](https://www.archelps.com/skills/review-fmea-missing-failure-modes/): Find credible omissions in an existing FMEA against actual functions, interfaces, and operating modes.
- [Review fault detection isolation and recovery logic](https://www.archelps.com/skills/review-fault-detection-isolation-recovery/): Review FDIR sequences against fault effects, timing, safe-state behavior, and verification evidence.
- [Review hazard mitigations and closure evidence](https://www.archelps.com/skills/review-hazard-mitigations-closure-evidence/): Check whether each claimed hazard control has applicable, current, and sufficient implementation and verification evidence.
- [Allocate a system reliability target to subsystems](https://www.archelps.com/skills/allocate-system-reliability-target/): Propose traceable subsystem reliability budgets that satisfy an approved system success target under explicit architecture assumptions.
- [Calculate system reliability from component data](https://www.archelps.com/skills/calculate-system-reliability-component-data/): Calculate a bounded system reliability estimate from component data and a defined success model.
- [Review a reliability block diagram](https://www.archelps.com/skills/review-reliability-block-diagram/): Check whether a reliability block diagram represents the actual success logic, dependencies, and mission scope.
- [Review maintainability requirements](https://www.archelps.com/skills/review-maintainability-requirements/): Check maintainability requirements for measurable repair, access, support, and operating context.
- [Assess the impact of a requirement change](https://www.archelps.com/skills/assess-requirement-change-impact/): Trace a proposed Requirement revision to affected design, interfaces, tests, and evidence.
- [Assess the impact of an interface change](https://www.archelps.com/skills/assess-interface-change-impact/): Trace a proposed Interface revision across both endpoints, requirements, integration, and evidence.
- [Build a requirement traceability matrix](https://www.archelps.com/skills/build-requirement-traceability-matrix/): Build a requirement traceability matrix (RTM) from stable IDs, recorded links, and verification evidence.
- [Check the completeness of a configuration baseline](https://www.archelps.com/skills/check-configuration-baseline-completeness/): Check whether a proposed baseline contains the intended scope, revisions, documents, and review evidence.
- [Compare two engineering baselines](https://www.archelps.com/skills/compare-engineering-baselines/): Compare two exact engineering baselines and explain material model and evidence changes.
- [Prepare an engineering change request](https://www.archelps.com/skills/prepare-engineering-change-request/): Prepare a reviewable engineering change request with rationale, exact deltas, impacts, and validation.
- [Review a deviation or waiver request](https://www.archelps.com/skills/review-deviation-or-waiver/): Review a proposed deviation or waiver against a specific requirement, configuration, evidence, and authority.
- [Build a technical review action closure matrix](https://www.archelps.com/skills/build-technical-review-action-closure-matrix/): Track review actions from finding to evidence-backed closure recommendation without losing original board decisions.
- [Define technical performance measures and monitoring thresholds](https://www.archelps.com/skills/define-technical-performance-measures/): Define a small set of decision-useful TPMs with sources, trends, and project-approved action thresholds.
- [Perform a technical risk assessment](https://www.archelps.com/skills/perform-technical-risk-assessment/): Identify and assess credible technical risk scenarios against project objectives and existing controls.
- [Prepare a critical design review](https://www.archelps.com/skills/prepare-critical-design-review/): Prepare a CDR packet assessing whether detailed design and build-to data are mature for implementation and integration.
- [Prepare a preliminary design review](https://www.archelps.com/skills/prepare-preliminary-design-review/): Prepare a PDR packet that tests preliminary architecture, interface choices, margins, and path to detailed design.
- [Prepare a system requirements review](https://www.archelps.com/skills/prepare-system-requirements-review/): Prepare a decision-ready SRR packet focused on requirements completeness, feasibility, and baseline readiness.
- [Prepare a test readiness review](https://www.archelps.com/skills/prepare-test-readiness-review/): Prepare a TRR packet checking test article, facility, procedures, personnel, safety, and data capture readiness.
- [Prepare an operational readiness review](https://www.archelps.com/skills/prepare-operational-readiness-review/): Prepare an ORR packet assessing deployed system, support products, people, procedures, and contingency readiness.
- [Review a risk register for missing or weak risk statements](https://www.archelps.com/skills/review-risk-register-statements/): Find missing technical risks and rewrite vague entries as cause-event-consequence statements.
- [Review a supplier technical deliverable](https://www.archelps.com/skills/review-supplier-technical-deliverable/): Review a specific supplier engineering deliverable against agreed content, interfaces, evidence, and configuration.
- [Review technology readiness evidence](https://www.archelps.com/skills/review-technology-readiness-evidence/): Evaluate claimed TRL or technology maturity against what was demonstrated in the relevant environment.
- [Write a risk mitigation plan](https://www.archelps.com/skills/write-risk-mitigation-plan/): Plan concrete actions, triggers, and evidence to reduce a stated technical risk scenario.

## Capability reference

- [Connected programme model](https://www.archelps.com/content-for-ai/#capability-programme-model): Native connected records for requirements, architecture, systems, interfaces, risks, verification activities and evidence.
- [Requirements traceability](https://www.archelps.com/content-for-ai/#capability-traceability): Native bidirectional links, coverage views and downstream change-impact context.
- [Controlled engineering change](https://www.archelps.com/content-for-ai/#capability-change-control): Native branches, record-level diffs, reviews, approvals, merges and baseline history.
- [Formal reviews and attributable approvals](https://www.archelps.com/content-for-ai/#capability-reviews-approvals): Native named reviewers, due dates, contextual comments and authenticated decision records. Arc records attributable engineering decisions. Agree contract-specific validation with Arc.
- [Verification and test management](https://www.archelps.com/content-for-ai/#capability-verification-test): Native verification planning, test cases, procedures, configurations, executions, results, evidence and coverage.
- [Risk, defect and anomaly workflows](https://www.archelps.com/content-for-ai/#capability-risk-defects): Configurable risk, FMEA, FTA, defect, anomaly and mitigation records connected to requirements and verification.
- [Variants and configuration baselines](https://www.archelps.com/content-for-ai/#capability-variants-configurations): Native applicability, variant context and configuration-specific baseline and coverage views.
- [Integrations and interchange](https://www.archelps.com/content-for-ai/#capability-integrations-interchange): Custom workflows through the public REST API, plus import from CSV, Word, Jira, Git and Confluence. Teams configure integrations around the connected tools' interfaces, permissions, mappings and deployment.
- [Controlled migration](https://www.archelps.com/content-for-ai/#capability-migration): Import-agent support for CSV, Word, Jira, Git and Confluence, with architecture and traceability built into a living graph.
- [Human-controlled AI](https://www.archelps.com/content-for-ai/#capability-ai-governance): Configurable agent permissions, review gates, model choice, isolated retrieval context and self-hosted inference.
- [Deployment and security controls](https://www.archelps.com/content-for-ai/#capability-deployment-security): Multi-tenant SaaS, on-premises and air-gapped application models, with BYODB available across each as a data-ownership configuration.
- [Arc MCP server](https://www.archelps.com/content-for-ai/#capability-mcp): Authenticated, permission-aware search, traceability navigation, impact analysis and reviewable actions through Model Context Protocol.
- [Arc public REST API](https://www.archelps.com/content-for-ai/#capability-public-api): Programme reads, branch creation, preview and application of supported item, relationship and field-definition changes, and pull-request actions subject to current permissions and revision controls.

## Public API actions and integration workflows

Public contract reviewed: 1 October 2026

- [API guide](https://app.archelps.com/api-guide): Public API workflow guidance.
- [Interactive API documentation](https://api.archelps.com/api/v1/public/docs): Current operations, parameters and payloads.
- [OpenAPI contract](https://api.archelps.com/api/v1/public/openapi.json): Machine-readable public REST API contract.

The public API reads accessible organisations and programmes, branches, item types, field definitions, relationship types, paginated items, item details, relationships and pull requests. Branch model and record reads can select a revision.

Supported writes create a branch from an existing branch, preview a proposed change, apply item, relationship and field-definition changes, and create, close or merge pull requests where permitted. Programme tokens are created in Program -> Settings -> API with read or write access, remain bound to the programme and follow the owner's current permissions. Write actions require programme edit permission. Use real model and type IDs and `expected_head_revision` for changes. Apply changes on a working branch, then use the programme's review and merge workflow to update the baseline.

For a controlled write workflow, read the model and current revision, create a working branch, map the proposed records and relationships, preview and inspect the diff, graph, impacts and effects, then apply the supported change at the expected revision. Create a pull request for the programme's review process. The team retains authority over close and merge actions. Engineers review the proposed engineering content before baseline merge.

Custom integrations can map Jira issue keys, GitHub commit or pull-request references, CAD/PLM/MBSE element revisions, external test-report references and dashboard data into or out of permitted Arc records. Teams configure each custom workflow around the connected tools' interfaces, permissions and field mappings. External test references use item fields and relationships to connect reports and configuration identifiers to requirement context.

An authorised external AI tool can analyse permitted reads and draft candidate item or relationship changes through the same branch and preview workflow. External AI provides analysis and proposals, Arc's native agents provide assessment and suggestions in the platform, and MCP tools support compatible AI clients.

## Product workflow evidence

- [Connected programme model](https://www.archelps.com/product/#single-source-of-truth): Arc connects requirements, architecture, systems, interfaces, risks, tests and evidence in one configurable programme model.
- [Get started with Arc](https://www.archelps.com/product/#import-migrate): Import and migrate without reformatting, data loss or a six-month migration project; build the connected model, collaborate in context and use agents to surface risks.
- [Controlled change and attributable history](https://www.archelps.com/product/#branching-merging): Branches, record-level diffs, contextual discussion, review and merge preserve who changed what, why and when before work enters the baseline.
- [Downstream change-impact context](https://www.archelps.com/product/#capability-change-control): Arc surfaces affected requirements, interfaces, system elements, verification records and evidence; engineers decide the response.
- [Human-controlled AI programme intelligence](https://www.archelps.com/product/#agents): Read-only and drafting agents can surface context, check records and propose work within configured permissions; engineers review and approve controlled changes.
- [Model Context Protocol workflow](https://www.archelps.com/mcp/): Compatible AI clients can use Arc context and tools without bypassing record permissions, review gates or baseline control.
- [Exportable audit history](https://www.archelps.com/security/#protection-audit-logs): Access, changes, approvals and AI actions can be exported for review under the customer's configured retention and audit policy.

## Security and deployment

- [Security and deployment for controlled space programmes](https://www.archelps.com/security/): Deployment controls, AI privacy, encryption, access controls and the standards workflows Arc can support.

Arc supports three application deployment models: multi-tenant SaaS, on-premises and air-gapped. Bring your own database is available across all three as a data-ownership configuration. Customer content is never used by Arc or enabled providers to train models. Arc supports engineering workflows around the programme's applicable standards, tailoring and review process.

## Requirements software selection

- [Requirements management software comparisons](https://www.archelps.com/compare/): Hub for Arc's sourced comparison library, buyer guide, methodology and reviewed evidence dates.
- [Best requirements management tools for aerospace and space teams](https://www.archelps.com/blog/best-requirements-management-tools-aerospace-space.html): Ten-option, evidence-reviewed buyer guide for fast-moving space teams, with contractual, ecosystem and evidence-freshness gates made explicit.
- [Arc vs Altium Requirements Portal (Valispace successor)](https://www.archelps.com/blog/arc-vs-altium-requirements-portal.html): First-party comparison of the current requirements and electronics context; legacy-documented Block, vali and parametric functions are separated and require current-availability confirmation.
- [Arc vs IBM DOORS](https://www.archelps.com/blog/arc-vs-ibm-doors.html): Arc for greenfield programmes and contained modernisation; DOORS remains relevant where legacy formats or ELM dependencies are mandatory.
- [Arc vs Jama Connect](https://www.archelps.com/blog/arc-vs-jama-connect.html): Arc's controlled branching, connected verification and deployment options compared with an established Jama operating model.
- [Arc vs PTC Codebeamer](https://www.archelps.com/blog/arc-vs-ptc-codebeamer.html): Arc's space-specific programme workflow compared with broader PTC lifecycle standardisation.
- [Arc vs Siemens Polarion ALM](https://www.archelps.com/blog/arc-vs-siemens-polarion-alm.html): Arc for focused space-team adoption compared with Siemens-wide lifecycle standardisation.
- [Arc vs Visure Requirements ALM](https://www.archelps.com/blog/arc-vs-visure-requirements-alm.html): Arc's connected programme context, controlled change and AI governance compared with a validated Visure estate.
- [Arc vs Jira for requirements management](https://www.archelps.com/blog/arc-vs-jira-requirements-management.html): Arc as the engineering source of truth while Jira can remain the delivery backlog.
- [Arc vs open-source requirements tools](https://www.archelps.com/blog/arc-vs-open-source-requirements-management-tools.html): The commercial Arc platform compared with source-owned requirements tools and the separate MIT-licensed Arc Skills assistant toolkit. Updated 2026-10-02.
- [Arc vs requirements spreadsheets](https://www.archelps.com/blog/arc-vs-requirements-spreadsheets.html): Arc as the next step when relationships, parallel change and verification evidence exceed rows and tabs.

Arc publishes these comparisons. Each page states its methodology, uses first-party product sources where available and identifies constraints that could change the recommendation.

## Selected engineering articles

- [ECR vs ECO vs ECN](https://www.archelps.com/blog/ecr-vs-eco-vs-ecn.html): An organisation-aware, closed-loop engineering change process spanning request, assessment, approval, effectivity, implementation, re-verification and closure.
- [Engineering decision record template](https://www.archelps.com/blog/engineering-decision-record-template.html): An ungated design-rationale template with alternatives, assumptions, evidence, uncertainty, authority, dissent, consequences and supersession.
- [Verification vs validation for space systems](https://www.archelps.com/blog/verification-vs-validation-space-systems.html): NASA and ECSS terminology, methods, evidence, configuration and authority, with their different treatments kept explicit.
- [As-designed vs as-built vs as-tested configuration management](https://www.archelps.com/blog/as-designed-as-built-as-tested.html): Three configuration states, authorised departures, evidence applicability and system-of-record boundaries.
- [Requirements management for space teams](https://www.archelps.com/blog/what-is-requirements-management-space-teams.html): Programme hierarchies, ECSS and NASA practices, contracting, traceability, change and verification evidence.
- [Requirements traceability matrix](https://www.archelps.com/blog/requirements-traceability-matrix.html): Traceability direction, RVM comparison, coverage and a representative CubeSat example.
- [Requirements traceability matrix XLSX template](https://www.archelps.com/downloads/requirements-traceability-matrix-template.xlsx): Ungated workbook for adapting requirement, relationship, verification and evidence fields to a programme's own authority model.
- [AI vs traditional requirements management tools](https://www.archelps.com/blog/ai-vs-traditional-requirements-management-tools-space.html): A source-grounded comparison of deterministic and AI-assisted requirements workflows, with human authority and evaluation boundaries made explicit.
- [Systems engineering for AI-enabled space systems](https://www.archelps.com/blog/systems-engineering-ai-enabled-space-systems.html): Requirements, verification and continuous-assurance guidance for space systems that include AI-enabled functions.
- [Engineering change impact assessment](https://www.archelps.com/blog/requirements-change-impact-analysis.html): Worked spacecraft-interface change spanning requirements, architecture, verification, evidence, owners and approval.
- [How to write verifiable spacecraft requirements](https://www.archelps.com/blog/how-to-write-verifiable-spacecraft-requirements.html): Before-and-after requirements with verification methods and failure modes.
- [SRR, PDR and CDR requirements-readiness checklist](https://www.archelps.com/blog/srr-pdr-cdr-requirements-readiness-checklist.html): Review-stage evidence, traceability, change and verification-readiness criteria.
- [Concurrent engineering for space systems](https://www.archelps.com/blog/concurrent-engineering-space-systems.html): An ESA-informed protocol for multidisciplinary sessions, live decisions and controlled follow-up changes.
- [Continuous verification for hardware](https://www.archelps.com/blog/continuous-verification-agile-hardware.html): Configuration-aware evidence status, reopening rules and freshness.
- [Agile requirements management for NewSpace](https://www.archelps.com/blog/agile-requirements-management-newspace.html): A three-layer control model for invariant constraints, design targets and experiment hypotheses.
- [Requirements scoping for iterative space hardware](https://www.archelps.com/blog/requirements-scoping-iterative-space-hardware.html): An evidence-budget method for must, learn, defer and delete scope decisions.
- [Reduce requirements administration](https://www.archelps.com/blog/reduce-requirements-administration.html): A 30-day workflow redesign with authority mapping, baseline measures and bounded automation.
- [Functional and non-functional requirements](https://www.archelps.com/blog/functional-vs-non-functional-requirements-space.html): A decision guide with space-system edge cases and verification considerations.
- [OceanGate Titan systems-engineering lessons](https://www.archelps.com/blog/oceangate-titan-systems-engineering-lessons.html): Five assurance failures cross-checked against official investigation findings.
- [Skunk Works principles for space engineering](https://www.archelps.com/blog/skunk-works-principles-space-engineering.html): Seven modern engineering principles derived from Kelly Johnson's 14 rules.

## Industry events

- [Space events for engineering teams](https://www.archelps.com/space-events/): Entry point to Arc's consolidated space-event directory. Verify time-sensitive details against the official organiser linked from each event record.

## Contact

- Email: luc@archelps.com
- LinkedIn: https://www.linkedin.com/company/archelps

## AI and agentic systems engineering foundations

- [What Is Agentic Systems Engineering? A Practical Guide for Hardware Teams](https://www.archelps.com/blog/agentic-systems-engineering-hardware-guide.html): Understand agentic systems engineering through a spacecraft power-change example, a practical reference architecture and a reusable agent task contract.
- [AI in Systems Engineering: Applications, Benefits and Limitations](https://www.archelps.com/blog/ai-in-systems-engineering.html): Map AI assistance across the space systems-engineering lifecycle, understand practical benefits and limitations, and choose an evidence-based first application.
- [AI Requirements Management: How It Works for Space Engineering Teams](https://www.archelps.com/blog/ai-requirements-management-space-teams.html): See how AI requirements management works through an annotated CubeSat requirement review, accepted and rejected suggestions, and a practical evaluation rubric.
- [MBSE, Requirements Management and AI: How They Fit Together](https://www.archelps.com/blog/mbse-requirements-management-space.html): Connect MBSE, requirements management and AI through clear information ownership, a synchronisation contract and a worked spacecraft power-change example.
- [AI Agents vs Copilots vs Automation in Systems Engineering](https://www.archelps.com/blog/ai-agents-vs-copilots-vs-automation-systems-engineering.html): Compare an engineering copilot, adaptive AI agent and fixed automation on the same spacecraft task, with a decision table and clear authority boundaries.
- [AI Agents for Systems Engineering: Six Practical Workflows](https://www.archelps.com/blog/ai-agents-systems-engineering-use-cases.html): Six practical AI agent workflows for space systems engineering, with specific inputs, reviewable outputs and a worked CubeSat power-change example.
- [Digital Thread vs Digital Twin: Foundations for AI-Assisted Engineering](https://www.archelps.com/blog/digital-thread-vs-digital-twin.html): Distinguish connected engineering records from digital representations of a system, with a spacecraft change diagram and practical foundations for AI assistance.
- [Human-in-the-Loop AI for Systems Engineering: Reviews and Approvals](https://www.archelps.com/blog/human-in-the-loop-ai-systems-engineering.html): Design meaningful human reviews of AI-assisted engineering changes, with an approval checklist, exceptional cases and a worked space-programme decision.
- [How to Introduce AI into Systems Engineering: A Practical Adoption Guide](https://www.archelps.com/blog/ai-adoption-systems-engineering.html): Plan a bounded 30-day AI pilot for a space engineering team, with a reusable charter, evaluation cases, decision criteria and a practical fallback.

<!-- SEARCH_INTENT_START -->
## Alternatives, reviews, migration and role guides

- [Which IBM DOORS alternative fits our team?](https://www.archelps.com/blog/ibm-doors-alternatives-aerospace.html): Legacy exchange formats and an ELM estate can favour DOORS; teams prioritising faster adoption, connected verification and controlled AI should test modern alternatives.
- [Which Jama Connect alternative fits our team?](https://www.archelps.com/blog/jama-connect-alternatives-aerospace.html): Jama can suit established review and requirements processes; alternatives differ most in programme modelling, branching, deployment and the effort engineers face in daily use.
- [Which Polarion alternative fits our team?](https://www.archelps.com/blog/polarion-alternatives-systems-engineering.html): Polarion can fit Siemens-standardised lifecycle estates; alternatives may be stronger for a focused engineering graph, lighter adoption or space-specific change and verification work.
- [Which Codebeamer alternative fits our team?](https://www.archelps.com/blog/ptc-codebeamer-alternatives-aerospace.html): Codebeamer can fit a broad PTC lifecycle strategy; aerospace teams should compare alternatives on traceability depth, verification evidence, configuration control and rollout burden.
- [Which Altium Requirements Portal alternative fits our team?](https://www.archelps.com/blog/altium-requirements-portal-alternatives.html): Requirements Portal may fit teams centred on Altium’s electronics ecosystem; alternatives differ in whole-programme modelling, controlled change and cross-discipline verification.
- [Which Visure alternative fits our team?](https://www.archelps.com/blog/visure-requirements-alternatives.html): Visure can suit tailored or validated requirements environments; alternatives should be compared on engineering context, adoption, deployment and review workflow.
- [What should we use alongside Jira for requirements?](https://www.archelps.com/blog/jira-requirements-management-alternatives.html): Jira is a strong delivery backlog, but engineering teams often need a separate source of truth for requirement hierarchy, traceability, baselines and verification evidence.
- [What should we use after a requirements spreadsheet?](https://www.archelps.com/blog/requirements-spreadsheet-alternatives.html): Spreadsheets remain useful for small flat lists; move when relationships, parallel changes, approvals and evidence can no longer be trusted across rows, tabs and copies.
- [IBM DOORS or Jama Connect: which fits our team?](https://www.archelps.com/blog/ibm-doors-vs-jama-connect.html): Choose around the real estate: DOORS is strongest where legacy exchange and IBM dependencies dominate; Jama is often easier to evaluate around collaborative review and modern requirements workflows.
- [Jama Connect or Polarion ALM: which fits our team?](https://www.archelps.com/blog/jama-connect-vs-polarion-alm.html): Jama usually merits attention for collaborative requirements and reviews; Polarion is more compelling where a Siemens-wide ALM and application-lifecycle strategy already exists.
- [IBM DOORS or Polarion ALM: which fits our team?](https://www.archelps.com/blog/ibm-doors-vs-polarion-alm.html): DOORS favours continuity with a long-lived requirements estate; Polarion favours teams seeking a broader web-based ALM platform and Siemens ecosystem alignment.
- [Codebeamer or Polarion ALM: which fits our team?](https://www.archelps.com/blog/codebeamer-vs-polarion-alm.html): The central choice is usually ecosystem and operating model: PTC lifecycle standardisation versus Siemens ALM standardisation, tested against the same engineering change and evidence workflow.
- [Does Jama Connect fit our requirements workflow?](https://www.archelps.com/blog/jama-connect-review-aerospace.html): Jama Connect is a serious requirements and review platform; the buying question is whether its workflow, deployment, verification and change model fit the programme.
- [Does Polarion ALM fit our engineering workflow?](https://www.archelps.com/blog/polarion-alm-review-systems-engineering.html): Polarion provides broad ALM coverage and ecosystem value, with the main evaluation risks concentrated in configuration complexity, engineer usability and programme-specific modelling.
- [Does PTC Codebeamer fit our aerospace workflow?](https://www.archelps.com/blog/ptc-codebeamer-review-aerospace.html): Codebeamer deserves consideration for organisations standardising on PTC lifecycle tooling; evaluate the day-to-day aerospace requirements, review and evidence workflow rather than the feature list alone.
- [Can Jira support our requirements workflow?](https://www.archelps.com/blog/jira-requirements-management-review.html): Jira can coordinate delivery work, but a credible requirements setup must prove hierarchy, traceability, baselines, formal review and verification evidence beyond issue links.
- [How do we export requirements from IBM DOORS?](https://www.archelps.com/blog/how-to-export-requirements-from-ibm-doors.html): Export a bounded module with stable IDs, attributes and links first; reconcile the package before importing it into a new controlled baseline.
- [How do we export requirements from Jama Connect?](https://www.archelps.com/blog/how-to-export-requirements-from-jama-connect.html): Start with a representative project and export requirements, relationship information, attachments and review context as separate reconciled inventories.
- [How do we export requirements from Polarion?](https://www.archelps.com/blog/how-to-export-requirements-from-polarion.html): Preserve Polarion work-item IDs, custom fields, hierarchy and links, then verify counts and relationship direction before setting a destination baseline.
- [How do we export requirements from Codebeamer?](https://www.archelps.com/blog/how-to-export-requirements-from-codebeamer.html): Treat Codebeamer trackers, fields, references and attachments as a connected export rather than flattening the programme into one spreadsheet.
- [How do we migrate requirements from Jira?](https://www.archelps.com/blog/how-to-migrate-requirements-from-jira.html): Separate genuine requirements from delivery tasks, then map issue keys, hierarchy, links, decisions and verification records into an engineering-owned model.
- [How do we migrate requirements from Excel?](https://www.archelps.com/blog/how-to-migrate-requirements-from-excel.html): Freeze the source workbook, identify the authoritative sheet and IDs, normalise relationship columns and reconcile every imported record before rollout.
- [How do we export from Altium Requirements Portal?](https://www.archelps.com/blog/how-to-export-requirements-from-altium-requirements-portal.html): Inventory requirements, parameters, links and electronics context before export, then prove what transferred and what needs a controlled reconstruction.
- [Which requirements tool suits systems engineers?](https://www.archelps.com/blog/requirements-management-software-for-systems-engineers.html): Systems engineers need a navigable programme model: intent, allocation, interfaces, change impact, verification and accountable decisions in one connected context.
- [Which requirements tool suits engineering managers?](https://www.archelps.com/blog/requirements-management-software-for-engineering-managers.html): Engineering managers need trustworthy status without presentation reconstruction: ownership, open decisions, affected work, review state and evidence gaps tied to source records.
- [Which tool suits requirements managers?](https://www.archelps.com/blog/requirements-management-software-for-requirements-managers.html): Requirements managers need controlled identifiers, hierarchy, attributes, reviews, baselines and exchange without becoming the manual switchboard for every engineer.
- [Which requirements tool suits hardware engineers?](https://www.archelps.com/blog/requirements-management-software-for-hardware-engineers.html): Hardware engineers need requirements in subsystem context, with interfaces, design decisions, test evidence and change impact available without database archaeology.
- [Which tool suits configuration managers?](https://www.archelps.com/blog/requirements-management-software-for-configuration-managers.html): Configuration managers need attributable baselines, branch and merge history, applicability, review authority and a clear connection between approved intent and evidence.
- [Which requirements tool suits a space startup?](https://www.archelps.com/blog/best-requirements-management-software-space-startups.html): Space startups should prioritise fast adoption, connected change and verification, exportability and a path to stronger controls without buying an enterprise transformation programme.
- [Which requirements tool suits verification teams?](https://www.archelps.com/blog/best-requirements-management-software-verification-teams.html): The best fit makes coverage and evidence operational: explicit methods, cases, configurations, results, failures, reopenings and accountable acceptance.
- [Which requirements tool suits a small aerospace team?](https://www.archelps.com/blog/best-requirements-management-software-small-aerospace-teams.html): Small aerospace teams need a low-administration system that preserves technical rigour, grows with programme complexity and does not force every discipline into a specialist database workflow.
<!-- SEARCH_INTENT_END -->
<!-- ECSS_RELEASE:START -->
## ECSS and agentic engineering

- [ECSS Standards Explained: A Practical Guide for First-Time Space Suppliers](https://www.archelps.com/blog/ecss-standards-first-time-space-suppliers.html): Understand ECSS standards for space suppliers: contractual applicability, tailoring, project records and a practical path from first tender to engineering evidence.
- [Your First ECSS Contract: What to Check Before You Bid](https://www.archelps.com/blog/first-ecss-contract-tender-checklist.html): Review ECSS tender requirements before bidding: source editions, deliverables, engineering effort, capability gaps and clarification questions for your first contract.
- [ECSS Applicability and Tailoring: How to Build an EARM](https://www.archelps.com/blog/ecss-applicability-tailoring-earm.html): Work through ECSS tailoring, applicability decisions and an EARM example, preserving source editions, rationale and customer agreement.
- [How to Build an ECSS Compliance Matrix: A Worked Supplier Example](https://www.archelps.com/blog/ecss-compliance-matrix-example.html): Build an ECSS compliance matrix with a worked supplier example, downloadable CSV, source references, evidence, gaps, actions and review decisions.
- [AI and ECSS Standards: What Agentic Engineering Changes](https://www.archelps.com/blog/ai-ecss-standards-agentic-engineering.html): Explore AI for ECSS compliance: useful engineering tasks, controlled source context, evidence quality and the decisions engineers retain.
- [ECSS Compliance Agents: How They Work and What Engineers Should Check](https://www.archelps.com/blog/ecss-compliance-agents.html): Learn how to scope ECSS compliance agents, inspect proposed edits and evaluate findings against relevant clauses, project requirements and engineering evidence.
- [ECSS Verification Control Document: Planning and Evidence with AI Assistance](https://www.archelps.com/blog/ai-assisted-ecss-verification.html): Build a useful ECSS Verification Control Document by connecting requirements, methods, levels, stages and evidence, with a worked example of AI-assisted review.
- [ECSS Change Control with AI Agents: Baselines, Impacts and Approvals](https://www.archelps.com/blog/ecss-change-control-ai-agents.html): Assess an ECSS requirement change against its baseline, affected engineering work and verification evidence, using AI proposals within an engineer-led review.
- [ECSS Project Templates: How to Start Your First Space Project in Arc](https://www.archelps.com/blog/ecss-project-templates-arc.html): Use Arc ECSS project templates as a starting point, then adapt the project to your contract, applicable clauses, requirements, verification work and review decisions.
- [ECSS Compliance Software: How Arc Supports Your Engineering Workflow](https://www.archelps.com/blog/how-arc-supports-ecss-projects.html): Evaluate Arc for ECSS projects: connect applicable obligations, requirements, verification and evidence, with ECSS templates and agents that propose edits for review.

## First European space contracts

- [Your First ESA Contract: From esa-star Registration to Tender and Delivery](https://www.archelps.com/blog/first-esa-contract.html): Prepare for your first ESA contract: understand esa-star registration, programme eligibility, national support, tender review and engineering delivery readiness.
- [Your First UK Space Contract: UKSA, ESA and Supplier Routes Explained](https://www.archelps.com/blog/first-uk-space-contract.html): Choose a UK space supplier route: direct procurement, UKSA grants, national support for ESA activities or subcontracting, then prepare the engineering response.
- [Your First Space Contract in Denmark: ESA Tenders, Danish Support and Readiness](https://www.archelps.com/blog/first-space-contract-denmark.html): Understand Denmark’s ESA supplier route, national support and activity-level funding, then prepare the technical scope and evidence for a first space contract.
- [Your First CNES Contract: A Practical Guide for Space Suppliers](https://www.archelps.com/blog/first-cnes-contract.html): Prepare a first CNES tender using its supplier portal, understand the DMC, CCAP and CCTP, and connect the technical response to deliverables and ECSS evidence.
- [Your First Space Contract in Germany: DLR, ESA and Supplier Routes](https://www.archelps.com/blog/first-space-contract-germany.html): Navigate German space supplier routes: the German Space Agency at DLR, national programmes, ESA, DLR purchasing and SME partnerships, with a technical readiness plan.
- [Your First ASI Contract: Preparing an Italian Space R&D Tender](https://www.archelps.com/blog/first-asi-contract.html): Prepare for an Italian Space Agency R&D tender with a historical ASI document walkthrough, bid checklist and practical route from proposal to engineering evidence.
- [Your First ESA Contract from the Netherlands: NLSA Support and Tender Readiness](https://www.archelps.com/blog/first-esa-contract-netherlands.html): Plan a first ESA contract from the Netherlands: choose a programme, understand NLSA support timing and prepare a coherent business case and engineering response.
- [Your First Space Contract in Spain: AEE Support and ESA Tendering](https://www.archelps.com/blog/first-space-contract-spain.html): Understand AEE support for Spanish ESA bidders through dated GSTP and ARTES examples, a programme-fit checklist and a practical engineering-readiness exercise.
- [Your First Space Contract in Norway: ESA Opportunities, NORKAP and National Support](https://www.archelps.com/blog/first-space-contract-norway.html): Understand ESA opportunities for Norwegian suppliers, the specific NORKAP technology route and how to prepare a first engineering proposal with traceable evidence.
- [Your First Space Contract in Sweden: Rymdstyrelsen Support and the ESA Route](https://www.archelps.com/blog/first-space-contract-sweden.html): Plan a first Swedish ESA opportunity with Rymdstyrelsen guidance, funding authorisation and a worked transition from research evidence to supplier readiness.
<!-- ECSS_RELEASE:END -->

## Space funding and bids

- [Your First UK Space Contract: UKSA, ESA and Supplier Routes Explained](https://www.archelps.com/blog/first-uk-space-contract.html): Choose a UKSA grant, ESA or supplier route for your first UK space project, then prepare the scope, interfaces and evidence behind your bid.
- [UK Space Strategy 2026: Funding Routes for Hardware Teams](https://www.archelps.com/blog/uk-space-strategy-2026-funding-hardware-teams.html): Understand the September 2026 UK Space Strategy, distinguish funding allocations from open calls, and choose the next bid-preparation task for a hardware team.
- [C-LEO Funding: Preparing Call 2 and Call 3 Technical Proposals](https://www.archelps.com/blog/c-leo-funding-technical-proposal.html): Separate C-LEO Call 2 ARTES and Call 3 national routes, check the September 2026 application stages, and build an active-antenna evidence plan.
- [NSIP Call 3: Preparing Your Full Technical Proposal](https://www.archelps.com/blog/nsip-funding-technical-proposal.html): Prepare an NSIP Call 3 full proposal with consistent work packages, milestones, risks and evidence, using a fictional robotic-tool project.
- [Technology Readiness Levels for Space Funding: Building the Evidence](https://www.archelps.com/blog/space-technology-readiness-levels-evidence.html): Build a space TRL evidence ledger that separates achieved results from planned tests, records configuration and environment, and exposes maturity gaps.
- [Your First ECSS Contract: What to Check Before You Bid](https://www.archelps.com/blog/first-ecss-contract-tender-checklist.html): Check invoked ECSS editions, agreed applicability, deliverables, verification effort and unresolved customer decisions before committing to a space bid.
- [Joining a C-LEO Consortium: A Hardware Supplier’s Bid Checklist](https://www.archelps.com/blog/c-leo-consortium-hardware-supplier-checklist.html): Define a C-LEO supplier work package with clear scope, interfaces, evidence, handovers and stage-change questions before joining a consortium proposal.
- [ISAM Funding in the UK: Preparing a Demonstration Project](https://www.archelps.com/blog/isam-funding-uk-demonstration-project.html): Prepare an in-orbit servicing, assembly or manufacturing demonstration with a customer case, host interfaces, payload evidence and clear opportunity status.
- [UK Space Domain Awareness Requirements: A Sensor Supplier’s Technical Readiness Checklist](https://www.archelps.com/blog/uk-space-domain-awareness-sensor-requirements.html): Map public UK space domain awareness requirements to proposed sensor contributions, with interface, calibration, uncertainty and evidence questions.

## Testing facilities

- [UK testing facilities](https://www.archelps.com/testing-facilities/): Directory of testing capabilities and locations. Evidence coverage and access arrangements vary by entry.
- [TS-Space Systems Test House](https://www.archelps.com/testing-facilities/ts-space-systems-test-house/): Operator sources reviewed on 29 September 2026. Thermal-vacuum cycling, monitored bakeout and outgassing, with source-linked equipment limits and configuration qualifications. This review date applies to this guide only.

<!-- EVENT_RESOURCES_START -->
## Complete event discovery

- [Space Industry Events List](https://www.archelps.com/space-events/): 407 curated event records through January 2030, including past, ongoing and future editions and selected aerospace, defence, electronics, test and manufacturing events.
- [Published Space Event Guides](https://www.archelps.com/events/llms.txt): Complete machine-readable index of all 216 published event-detail pages. Index refreshed 2026-10-06; source snapshot date remains 2026-08-25.
<!-- EVENT_RESOURCES_END -->

<!-- AI_BLOG_INDEX_START -->
## Complete published article index

All 112 published Arc engineering articles are individually linked below.

- [Arc or Altium Requirements Portal: which fits our team?](https://www.archelps.com/blog/arc-vs-altium-requirements-portal.html): Compare Arc with Altium Requirements Portal and its legacy Valispace systems environment across electronics context, verification, AI and change. Published 2026-09-04; updated 2026-10-02.
- [Arc or ECLIPSE Suite: which fits our space team?](https://www.archelps.com/blog/arc-vs-eclipse-suite.html): Compare Arc with ECLIPSE RVM and related modules for space requirements, verification, reviews and ECSS workflows, with sources, pricing and trial guidance. Published 2026-10-01.
- [Arc or IBM DOORS: which fits our team?](https://www.archelps.com/blog/arc-vs-ibm-doors.html): Compare Arc with IBM Engineering Requirements Management DOORS and DOORS Next across governance, traceability, change workflows, AI and adoption. Published 2026-08-09; updated 2026-10-02.
- [Arc or Jama Connect: which fits our team?](https://www.archelps.com/blog/arc-vs-jama-connect.html): Compare Arc and Jama Connect across live traceability, stakeholder reviews, verification, change workflows, AI, deployment and programme fit. Published 2026-08-11; updated 2026-10-02.
- [Arc or open source: which fits our requirements workflow?](https://www.archelps.com/blog/arc-vs-open-source-requirements-management-tools.html): Compare the Arc platform, Arc Skills and open source requirements tools across traceability, AI review, approvals, deployment and operating effort. Published 2026-08-07; updated 2026-10-02.
- [Arc or PTC Codebeamer: which fits our team?](https://www.archelps.com/blog/arc-vs-ptc-codebeamer.html): Compare Arc and PTC Codebeamer across requirements, risk, testing, product lines, AI, traceability, administration and aerospace programme fit. Published 2026-08-13; updated 2026-10-02.
- [Arc or Siemens Polarion ALM: which fits our team?](https://www.archelps.com/blog/arc-vs-siemens-polarion-alm.html): Compare Arc and Siemens Polarion ALM across requirements, workflows, reuse, traceability, change review, AI, administration and engineering fit. Published 2026-08-17; updated 2026-10-02.
- [Arc or Visure Requirements ALM: which fits our team?](https://www.archelps.com/blog/arc-vs-visure-requirements-alm.html): Compare Arc and Visure Requirements ALM Platform across traceability, risk, testing, compliance, AI, change review and aerospace programme fit. Published 2026-08-15; updated 2026-10-02.
- [Arc vs Flow Engineering: Requirements and Verification for Space Teams](https://www.archelps.com/blog/arc-vs-flow-engineering.html): See why space teams should consider Arc for connected requirements, controlled change and verification, with a sourced Flow Engineering comparison and pricing. Published 2026-10-01; updated 2026-10-02.
- [Can Jira support our requirements workflow?](https://www.archelps.com/blog/jira-requirements-management-review.html): Jira can coordinate delivery work, but a credible requirements setup must prove hierarchy, traceability, baselines, formal review and verification evidence beyond issue links. Published 2026-09-15; updated 2026-10-02.
- [Codebeamer or Polarion ALM: which fits our team?](https://www.archelps.com/blog/codebeamer-vs-polarion-alm.html): The central choice is usually ecosystem and operating model: PTC lifecycle standardisation versus Siemens ALM standardisation, tested against the same engineering change and evidence workflow. Published 2026-09-15; updated 2026-10-02.
- [Do we need a digital thread or a digital twin?](https://www.archelps.com/blog/digital-thread-vs-digital-twin.html): Distinguish connected engineering records from digital representations of a system, with a spacecraft change diagram and practical foundations for AI assistance. Published 2026-09-05.
- [Does Flow Engineering fit our next milestone?](https://www.archelps.com/blog/flow-engineering-space-teams-review.html): Assess Flow Engineering’s documented workflow against a space review milestone using an original fit card, evidence-applicability checks and supported Arc mechanisms. Published 2026-10-06.
- [Does Jama Connect fit our requirements workflow?](https://www.archelps.com/blog/jama-connect-review-aerospace.html): Jama Connect is a serious requirements and review platform; the buying question is whether its workflow, deployment, verification and change model fit the programme. Published 2026-09-15; updated 2026-10-02.
- [Does Polarion ALM fit our engineering workflow?](https://www.archelps.com/blog/polarion-alm-review-systems-engineering.html): Polarion provides broad ALM coverage and ecosystem value, with the main evaluation risks concentrated in configuration complexity, engineer usability and programme-specific modelling. Published 2026-09-15; updated 2026-10-02.
- [Does PTC Codebeamer fit our aerospace workflow?](https://www.archelps.com/blog/ptc-codebeamer-review-aerospace.html): Codebeamer deserves consideration for organisations standardising on PTC lifecycle tooling; evaluate the day-to-day aerospace requirements, review and evidence workflow rather than the feature list alone. Published 2026-09-15; updated 2026-10-02.
- [How can AI help us review requirements?](https://www.archelps.com/blog/ai-requirements-management-space-teams.html): See how AI requirements management works through an annotated CubeSat requirement review, accepted and rejected suggestions, and a practical evaluation rubric. Published 2026-08-29; updated 2026-09-05.
- [How do Dutch companies prepare for ESA contracts?](https://www.archelps.com/blog/first-esa-contract-netherlands.html): Plan a first ESA contract from the Netherlands: choose a programme, understand NLSA support timing and prepare a coherent business case and engineering response. Published 2026-09-07.
- [How do ECR, ECO and ECN differ?](https://www.archelps.com/blog/ecr-vs-eco-vs-ecn.html): Understand ECR, ECO and ECN, then use a closed-loop engineering change process for assessment, approval, effectivity, implementation and verification. Published 2026-09-04.
- [How do functional and non-functional requirements differ?](https://www.archelps.com/blog/functional-vs-non-functional-requirements-space.html): Classify functional vs non-functional requirements for space systems with a decision tree, edge cases, hardware examples and verification guidance. Published 2026-08-29; updated 2026-08-30.
- [How do MBSE, requirements and AI fit together?](https://www.archelps.com/blog/mbse-requirements-management-space.html): Connect MBSE, requirements management and AI through clear information ownership, a synchronisation contract and a worked spacecraft power-change example. Published 2026-08-29; updated 2026-09-05.
- [How do space teams manage requirements?](https://www.archelps.com/blog/what-is-requirements-management-space-teams.html): What is requirements management for space teams? Learn how ECSS standards and NASA contracts affect traceability, change control and verification. Published 2026-08-21; updated 2026-09-08.
- [How do verification and validation differ?](https://www.archelps.com/blog/verification-vs-validation-space-systems.html): Understand verification versus validation for space systems, including NASA and ECSS terminology, evidence, configuration and a hypothetical spacecraft example. Published 2026-09-04; updated 2026-09-08.
- [How do we assess a requirements change?](https://www.archelps.com/blog/requirements-change-impact-analysis.html): A worked spacecraft-interface change and reusable assessment template covering requirements, architecture, verification, evidence, owners and approval. Published 2026-08-29; updated 2026-09-08.
- [How do we build a requirements traceability matrix?](https://www.archelps.com/blog/requirements-traceability-matrix.html): Learn how an RTM links requirements to architecture, verification and evidence, compare RTM and RVM fields, and explore a worked CubeSat example. Published 2026-08-10; updated 2026-09-08.
- [How do we build an ECSS compliance matrix?](https://www.archelps.com/blog/ecss-compliance-matrix-example.html): Build an ECSS compliance matrix with a worked supplier example, downloadable CSV, source references, evidence, gaps, actions and review decisions. Published 2026-09-07.
- [How do we compare Flow and Arc evaluation costs?](https://www.archelps.com/blog/flow-engineering-pricing-evaluation.html): Read Flow’s dated USD editor-price snapshot, calculate five-editor list rates and scope the review, configuration and evidence workflow before requesting terms. Published 2026-10-06.
- [How do we connect Jira to engineering records?](https://www.archelps.com/blog/flow-engineering-jira-integration.html): Use a ticket-to-engineering authority matrix and connector acceptance cases to separate Jira closure, controlled requirement approval and verification evidence. Published 2026-10-06.
- [How do we control ECSS changes with AI agents?](https://www.archelps.com/blog/ecss-change-control-ai-agents.html): Assess an ECSS requirement change against its baseline, affected engineering work and verification evidence, using AI proposals within an engineer-led review. Published 2026-09-07; updated 2026-10-01.
- [How do we engineer an AI-enabled space system?](https://www.archelps.com/blog/systems-engineering-ai-enabled-space-systems.html): A practical guide to requirements, traceability, verification and continuous assurance for spacecraft and ground systems containing AI or autonomy. Published 2026-08-31.
- [How do we evaluate a payload power change?](https://www.archelps.com/blog/flow-engineering-change-impact-evaluation.html): Use an exact fictional payload power change to evaluate traceability, controlled review and evidence applicability, including a deliberate missing thermal relationship. Published 2026-10-06.
- [How do we evaluate baselines, variants and evidence?](https://www.archelps.com/blog/flow-engineering-baselines-configurations.html): Evaluate supplier variants with a baseline and evidence-applicability matrix, preserving accepted states while reviewed changes and historical results remain distinct. Published 2026-10-06.
- [How do we export from Altium Requirements Portal?](https://www.archelps.com/blog/how-to-export-requirements-from-altium-requirements-portal.html): Inventory requirements, parameters, links and electronics context before export, then prove what transferred and what needs a controlled reconstruction. Published 2026-09-15; updated 2026-10-02.
- [How do we export requirements from Codebeamer?](https://www.archelps.com/blog/how-to-export-requirements-from-codebeamer.html): Treat Codebeamer trackers, fields, references and attachments as a connected export rather than flattening the programme into one spreadsheet. Published 2026-09-15; updated 2026-10-02.
- [How do we export requirements from IBM DOORS?](https://www.archelps.com/blog/how-to-export-requirements-from-ibm-doors.html): Export a bounded module with stable IDs, attributes and links first; reconcile the package before importing it into a new controlled baseline. Published 2026-09-15; updated 2026-10-02.
- [How do we export requirements from Jama Connect?](https://www.archelps.com/blog/how-to-export-requirements-from-jama-connect.html): Start with a representative project and export requirements, relationship information, attachments and review context as separate reconciled inventories. Published 2026-09-15; updated 2026-10-02.
- [How do we export requirements from Polarion?](https://www.archelps.com/blog/how-to-export-requirements-from-polarion.html): Preserve Polarion work-item IDs, custom fields, hierarchy and links, then verify counts and relationship direction before setting a destination baseline. Published 2026-09-15; updated 2026-10-02.
- [How do we introduce AI into systems engineering?](https://www.archelps.com/blog/ai-adoption-systems-engineering.html): Plan a bounded 30-day AI pilot for a space engineering team, with a reusable charter, evaluation cases, decision criteria and a practical fallback. Published 2026-09-05.
- [How do we join a C-LEO consortium?](https://www.archelps.com/blog/c-leo-consortium-hardware-supplier-checklist.html): Define a C-LEO supplier work package with clear scope, interfaces, evidence, handovers and stage-change questions before joining a consortium proposal. Published 2026-09-08; updated 2026-10-01.
- [How do we keep engineering decisions connected?](https://www.archelps.com/blog/engineering-communication-requirements-management.html): Why engineering communication becomes a requirements, traceability and change-impact problem when complex hardware teams scale across tools and disciplines. Published 2026-07-31; updated 2026-09-04.
- [How do we keep verification current as hardware changes?](https://www.archelps.com/blog/continuous-verification-agile-hardware.html): Build a configuration-aware continuous verification evidence ledger, with explicit evidence states, reopening rules and freshness metrics for hardware teams. Published 2026-08-29; updated 2026-09-08.
- [How do we manage requirements in agile hardware work?](https://www.archelps.com/blog/agile-requirements-management-newspace.html): A three-layer agile requirements management model for NewSpace, separating invariant constraints, design targets and experiment hypotheses by consequence. Published 2026-08-29; updated 2026-08-30.
- [How do we migrate requirements from Excel?](https://www.archelps.com/blog/how-to-migrate-requirements-from-excel.html): Freeze the source workbook, identify the authoritative sheet and IDs, normalise relationship columns and reconcile every imported record before rollout. Published 2026-09-15; updated 2026-10-02.
- [How do we migrate requirements from Jira?](https://www.archelps.com/blog/how-to-migrate-requirements-from-jira.html): Separate genuine requirements from delivery tasks, then map issue keys, hierarchy, links, decisions and verification records into an engineering-owned model. Published 2026-09-15; updated 2026-10-02.
- [How do we plan an ECSS VCD with AI?](https://www.archelps.com/blog/ai-assisted-ecss-verification.html): Build a useful ECSS Verification Control Document by connecting requirements, methods, levels, stages and evidence, with a worked example of AI-assisted review. Published 2026-09-07.
- [How do we prepare a C-LEO proposal?](https://www.archelps.com/blog/c-leo-funding-technical-proposal.html): Separate C-LEO Call 2 ARTES and Call 3 national routes, check the September 2026 application stages, and build an active-antenna evidence plan. Published 2026-09-08; updated 2026-10-01.
- [How do we prepare an ISAM demonstration bid?](https://www.archelps.com/blog/isam-funding-uk-demonstration-project.html): Prepare an in-orbit servicing, assembly or manufacturing demonstration with a customer case, host interfaces, payload evidence and clear opportunity status. Published 2026-09-08; updated 2026-10-01.
- [How do we prepare an NSIP Call 3 proposal?](https://www.archelps.com/blog/nsip-funding-technical-proposal.html): Prepare an NSIP Call 3 full proposal with consistent work packages, milestones, risks and evidence, using a fictional robotic-tool project. Published 2026-09-08; updated 2026-10-01.
- [How do we prepare for ECSS NextGen and Issue D?](https://www.archelps.com/blog/ecss-nextgen-issue-d.html): ECSS Issue D is planned for Q4 2026, subject to approvals. Understand NextGen restructuring, digitalisation and tailoring, with a practical preparation checklist. Published 2026-10-02.
- [How do we prepare for our first ASI contract?](https://www.archelps.com/blog/first-asi-contract.html): Prepare for an Italian Space Agency R&D tender with a historical ASI document walkthrough, bid checklist and practical route from proposal to engineering evidence. Published 2026-09-07.
- [How do we prepare for our first CNES contract?](https://www.archelps.com/blog/first-cnes-contract.html): Prepare a first CNES tender using its supplier portal, understand the DMC, CCAP and CCTP, and connect the technical response to deliverables and ECSS evidence. Published 2026-09-07.
- [How do we prepare for our first ESA contract?](https://www.archelps.com/blog/first-esa-contract.html): Prepare for your first ESA contract: understand esa-star registration, programme eligibility, national support, tender review and engineering delivery readiness. Published 2026-09-07.
- [How do we prepare for SRR, PDR and CDR?](https://www.archelps.com/blog/srr-pdr-cdr-requirements-readiness-checklist.html): Use this vendor-neutral SRR, PDR and CDR checklist to assess requirements, traceability, changes, verification evidence, ownership and review readiness. Published 2026-08-30; updated 2026-09-08.
- [How do we pursue a space contract in Denmark?](https://www.archelps.com/blog/first-space-contract-denmark.html): Understand Denmark’s ESA supplier route, national support and activity-level funding, then prepare the technical scope and evidence for a first space contract. Published 2026-09-07.
- [How do we pursue a space contract in Germany?](https://www.archelps.com/blog/first-space-contract-germany.html): Navigate German space supplier routes: the German Space Agency at DLR, national programmes, ESA, DLR purchasing and SME partnerships, with a technical readiness plan. Published 2026-09-07.
- [How do we pursue a space contract in Norway?](https://www.archelps.com/blog/first-space-contract-norway.html): Understand ESA opportunities for Norwegian suppliers, the specific NORKAP technology route and how to prepare a first engineering proposal with traceable evidence. Published 2026-09-07.
- [How do we pursue a space contract in Spain?](https://www.archelps.com/blog/first-space-contract-spain.html): Understand AEE support for Spanish ESA bidders through dated GSTP and ARTES examples, a programme-fit checklist and a practical engineering-readiness exercise. Published 2026-09-07.
- [How do we pursue a space contract in Sweden?](https://www.archelps.com/blog/first-space-contract-sweden.html): Plan a first Swedish ESA opportunity with Rymdstyrelsen guidance, funding authorisation and a worked transition from research evidence to supplier readiness. Published 2026-09-07.
- [How do we reconcile as-designed, as-built and as-tested?](https://www.archelps.com/blog/as-designed-as-built-as-tested.html): Distinguish as-designed, as-built and as-tested states, reconcile authorised departures, and keep space-hardware evidence tied to the correct configuration. Published 2026-09-04; updated 2026-09-08.
- [How do we record an engineering decision?](https://www.archelps.com/blog/engineering-decision-record-template.html): Use an engineering decision record to preserve design context, alternatives, evidence, uncertainty, rationale and authority, with a worked spacecraft example. Published 2026-09-04; updated 2026-09-08.
- [How do we reduce requirements administration?](https://www.archelps.com/blog/reduce-requirements-administration.html): Reduce requirements administration in 30 days with a waste taxonomy, baseline metrics, workflow migration and bounded automation that preserves control. Published 2026-08-29; updated 2026-09-04.
- [How do we review AI engineering proposals?](https://www.archelps.com/blog/human-in-the-loop-ai-systems-engineering.html): Design meaningful human reviews of AI-assisted engineering changes, with an approval checklist, exceptional cases and a worked space-programme decision. Published 2026-09-05.
- [How do we run concurrent space engineering?](https://www.archelps.com/blog/concurrent-engineering-space-systems.html): An ESA-inspired concurrent engineering protocol for space teams, covering session readiness, live decision logs, multidisciplinary trades and controlled deltas. Published 2026-08-29; updated 2026-08-30.
- [How do we scope an iterative hardware project?](https://www.archelps.com/blog/requirements-scoping-iterative-space-hardware.html): Use an evidence-budget method for requirements scoping in iterative space hardware, with must, learn, defer and delete decisions plus a worked scope gate. Published 2026-08-29; updated 2026-09-08.
- [How do we start an ECSS project in Arc?](https://www.archelps.com/blog/ecss-project-templates-arc.html): Use Arc ECSS project templates as a starting point, then adapt the project to your contract, applicable clauses, requirements, verification work and review decisions. Published 2026-09-07.
- [How do we support a space TRL claim?](https://www.archelps.com/blog/space-technology-readiness-levels-evidence.html): Build a space TRL evidence ledger that separates achieved results from planned tests, records configuration and environment, and exposes maturity gaps. Published 2026-09-08; updated 2026-10-01.
- [How do we tailor ECSS and build an EARM?](https://www.archelps.com/blog/ecss-applicability-tailoring-earm.html): Work through ECSS tailoring, applicability decisions and an EARM example, preserving source editions, rationale and customer agreement. Published 2026-09-07; updated 2026-10-01.
- [How do we win our first UK space contract?](https://www.archelps.com/blog/first-uk-space-contract.html): Choose a UKSA grant, ESA or supplier route for your first UK space project, then prepare the scope, interfaces and evidence behind your bid. Published 2026-09-07; updated 2026-10-01.
- [How do we write verifiable spacecraft requirements?](https://www.archelps.com/blog/how-to-write-verifiable-spacecraft-requirements.html): Learn to write verifiable spacecraft requirements with 25 before-and-after examples, including methods, evidence and the ambiguity each rewrite removes. Published 2026-08-30; updated 2026-09-08.
- [How does Arc support ECSS projects?](https://www.archelps.com/blog/how-arc-supports-ecss-projects.html): Evaluate Arc for ECSS projects: connect applicable obligations, requirements, verification and evidence, with ECSS templates and agents that propose edits for review. Published 2026-09-07.
- [How does SpaceX manage requirements?](https://www.archelps.com/blog/spacex-requirements-management-development-approach.html): A practical look at the publicly described SpaceX approach to requirements, design criteria, responsible engineers and continuous verification. Published 2026-07-31; updated 2026-09-04.
- [How should Excel work with Arc or Flow?](https://www.archelps.com/blog/flow-engineering-excel-integration.html): Separate Excel calculation authority from imported requirement records with a source-cell map, update acceptance tests and explicit formula and connector boundaries. Published 2026-10-06.
- [How should we review an ECSS compliance agent?](https://www.archelps.com/blog/ecss-compliance-agents.html): Learn how to scope ECSS compliance agents, inspect proposed edits and evaluate findings against relevant clauses, project requirements and engineering evidence. Published 2026-09-07.
- [IBM DOORS or Jama Connect: which fits our team?](https://www.archelps.com/blog/ibm-doors-vs-jama-connect.html): Choose around the real estate: DOORS is strongest where legacy exchange and IBM dependencies dominate; Jama is often easier to evaluate around collaborative review and modern requirements workflows. Published 2026-09-15; updated 2026-10-02.
- [IBM DOORS or Polarion ALM: which fits our team?](https://www.archelps.com/blog/ibm-doors-vs-polarion-alm.html): DOORS favours continuity with a long-lived requirements estate; Polarion favours teams seeking a broader web-based ALM platform and Siemens ecosystem alignment. Published 2026-09-15; updated 2026-10-02.
- [Jama Connect or Polarion ALM: which fits our team?](https://www.archelps.com/blog/jama-connect-vs-polarion-alm.html): Jama usually merits attention for collaborative requirements and reviews; Polarion is more compelling where a Siemens-wide ALM and application-lifecycle strategy already exists. Published 2026-09-15; updated 2026-10-02.
- [Should our hardware team use agile or waterfall?](https://www.archelps.com/blog/agile-vs-waterfall-hardware-development.html): A practical comparison of agile and waterfall hardware development, including why software iteration is faster and how requirements can support safer learning loops. Published 2026-07-31; updated 2026-09-04.
- [Should our requirements tool use AI?](https://www.archelps.com/blog/ai-vs-traditional-requirements-management-tools-space.html): Compare AI and traditional requirements management tools for space teams across baselines, traceability, change impact, verification, control and migration. Published 2026-08-31.
- [Should requirements live in Arc, Jira or both?](https://www.archelps.com/blog/arc-vs-jira-requirements-management.html): Compare Arc and Jira for requirements management, traceability, verification, engineering change, delivery planning, AI and aerospace toolchain fit. Published 2026-08-19; updated 2026-10-02.
- [Should we use an agent, a copilot or automation?](https://www.archelps.com/blog/ai-agents-vs-copilots-vs-automation-systems-engineering.html): Compare an engineering copilot, adaptive AI agent and fixed automation on the same spacecraft task, with a decision table and clear authority boundaries. Published 2026-09-05.
- [Systems Engineering Skills: An Open Source Requirements Management Toolkit](https://www.archelps.com/blog/systems-engineering-skills-open-source-requirements-management.html): Explore Arc Skills: 100 free systems engineering skills for requirements review, traceability and verification, with local file tools and human-reviewed proposals. Published 2026-10-02.
- [What can engineers learn from the A380 delay?](https://www.archelps.com/blog/airbus-a380-requirements-communication-failure.html): A careful look at the A380 schedule and wiring challenges, and what complex hardware teams can learn about interfaces, configuration and requirements communication. Published 2026-07-31; updated 2026-09-04.
- [What do the Titan investigations teach engineers?](https://www.archelps.com/blog/oceangate-titan-systems-engineering-lessons.html): An official-investigation crosswalk of five OceanGate Titan assurance failures spanning design basis, qualification, monitoring, change and governance. Published 2026-08-29; updated 2026-08-30.
- [What does UK Space Strategy 2026 mean for hardware teams?](https://www.archelps.com/blog/uk-space-strategy-2026-funding-hardware-teams.html): Understand the September 2026 UK Space Strategy, distinguish funding allocations from open calls, and choose the next bid-preparation task for a hardware team. Published 2026-09-08; updated 2026-10-01.
- [What is agentic systems engineering?](https://www.archelps.com/blog/agentic-systems-engineering-hardware-guide.html): Understand agentic systems engineering through a spacecraft power-change example, a practical reference architecture and a reusable agent task contract. Published 2026-08-29; updated 2026-09-05.
- [What must an SDA sensor supplier demonstrate?](https://www.archelps.com/blog/uk-space-domain-awareness-sensor-requirements.html): Map public UK space domain awareness requirements to proposed sensor contributions, with interface, calibration, uncertainty and evidence questions. Published 2026-09-08; updated 2026-10-01.
- [What should we check before our first ECSS bid?](https://www.archelps.com/blog/first-ecss-contract-tender-checklist.html): Check invoked ECSS editions, agreed applicability, deliverables, verification effort and unresolved customer decisions before committing to a space bid. Published 2026-09-07; updated 2026-10-01.
- [What should we use after a requirements spreadsheet?](https://www.archelps.com/blog/requirements-spreadsheet-alternatives.html): Spreadsheets remain useful for small flat lists; move when relationships, parallel changes, approvals and evidence can no longer be trusted across rows, tabs and copies. Published 2026-09-15; updated 2026-10-02.
- [What should we use alongside Jira for requirements?](https://www.archelps.com/blog/jira-requirements-management-alternatives.html): Jira is a strong delivery backlog, but engineering teams often need a separate source of truth for requirement hierarchy, traceability, baselines and verification evidence. Published 2026-09-15; updated 2026-10-02.
- [When should we move requirements from Excel to Arc?](https://www.archelps.com/blog/arc-vs-requirements-spreadsheets.html): Compare Arc with Excel and other requirements spreadsheets across setup, traceability, change control, collaboration, verification and cost. Published 2026-08-20; updated 2026-10-02.
- [Where can AI help systems engineers?](https://www.archelps.com/blog/ai-in-systems-engineering.html): Map AI assistance across the space systems-engineering lifecycle, understand practical benefits and limitations, and choose an evidence-based first application. Published 2026-09-05; updated 2026-10-02.
- [Where can AI help with ECSS engineering?](https://www.archelps.com/blog/ai-ecss-standards-agentic-engineering.html): Explore AI for ECSS compliance: useful engineering tasks, controlled source context, evidence quality and the decisions engineers retain. Published 2026-09-07.
- [Which Altium Requirements Portal alternative fits our team?](https://www.archelps.com/blog/altium-requirements-portal-alternatives.html): Requirements Portal may fit teams centred on Altium’s electronics ecosystem; alternatives differ in whole-programme modelling, controlled change and cross-discipline verification. Published 2026-09-15; updated 2026-10-02.
- [Which Codebeamer alternative fits our team?](https://www.archelps.com/blog/ptc-codebeamer-alternatives-aerospace.html): Codebeamer can fit a broad PTC lifecycle strategy; aerospace teams should compare alternatives on traceability depth, verification evidence, configuration control and rollout burden. Published 2026-09-15; updated 2026-10-02.
- [Which ECSS standards apply to our first contract?](https://www.archelps.com/blog/ecss-standards-first-time-space-suppliers.html): Understand ECSS standards for space suppliers: contractual applicability, tailoring, project records and a practical path from first tender to engineering evidence. Published 2026-09-07.
- [Which engineering tasks can AI agents help with?](https://www.archelps.com/blog/ai-agents-systems-engineering-use-cases.html): Six practical AI agent workflows for space systems engineering, with specific inputs, reviewable outputs and a worked CubeSat power-change example. Published 2026-09-05.
- [Which Flow Engineering alternative fits our space team?](https://www.archelps.com/blog/flow-engineering-alternatives.html): Choose a Flow Engineering alternative using a six-approach shortlist, review and evidence criteria, and clear reasons to retain a useful installed workflow. Published 2026-10-06.
- [Which IBM DOORS alternative fits our team?](https://www.archelps.com/blog/ibm-doors-alternatives-aerospace.html): Legacy exchange formats and an ELM estate can favour DOORS; teams prioritising faster adoption, connected verification and controlled AI should test modern alternatives. Published 2026-09-15; updated 2026-10-02.
- [Which Jama Connect alternative fits our team?](https://www.archelps.com/blog/jama-connect-alternatives-aerospace.html): Jama can suit established review and requirements processes; alternatives differ most in programme modelling, branching, deployment and the effort engineers face in daily use. Published 2026-09-15; updated 2026-10-02.
- [Which open-source requirements tool fits our team?](https://www.archelps.com/blog/open-source-requirements-management-tools.html): Compare seven open source requirements management tools for engineering teams, including setup, traceability, Git workflows, deployment and AI agent support. Published 2026-08-10; updated 2026-10-02.
- [Which Polarion alternative fits our team?](https://www.archelps.com/blog/polarion-alternatives-systems-engineering.html): Polarion can fit Siemens-standardised lifecycle estates; alternatives may be stronger for a focused engineering graph, lighter adoption or space-specific change and verification work. Published 2026-09-15; updated 2026-10-02.
- [Which requirements tool should our space team use?](https://www.archelps.com/blog/best-requirements-management-tools-aerospace-space.html): Compare twelve requirements management approaches for aerospace and space teams by traceability, configuration, evidence, reviews, AI and operating model. Published 2026-08-21; updated 2026-10-01.
- [Which requirements tool suits a small aerospace team?](https://www.archelps.com/blog/best-requirements-management-software-small-aerospace-teams.html): Small aerospace teams need a low-administration system that preserves technical rigour, grows with programme complexity and does not force every discipline into a specialist database workflow. Published 2026-09-15; updated 2026-10-02.
- [Which requirements tool suits a space startup?](https://www.archelps.com/blog/best-requirements-management-software-space-startups.html): Space startups should prioritise fast adoption, connected change and verification, exportability and a path to stronger controls without buying an enterprise transformation programme. Published 2026-09-15; updated 2026-10-02.
- [Which requirements tool suits engineering managers?](https://www.archelps.com/blog/requirements-management-software-for-engineering-managers.html): Engineering managers need trustworthy status without presentation reconstruction: ownership, open decisions, affected work, review state and evidence gaps tied to source records. Published 2026-09-15; updated 2026-10-02.
- [Which requirements tool suits hardware engineers?](https://www.archelps.com/blog/requirements-management-software-for-hardware-engineers.html): Hardware engineers need requirements in subsystem context, with interfaces, design decisions, test evidence and change impact available without database archaeology. Published 2026-09-15; updated 2026-10-02.
- [Which requirements tool suits systems engineers?](https://www.archelps.com/blog/requirements-management-software-for-systems-engineers.html): Systems engineers need a navigable programme model: intent, allocation, interfaces, change impact, verification and accountable decisions in one connected context. Published 2026-09-15; updated 2026-10-02.
- [Which requirements tool suits verification teams?](https://www.archelps.com/blog/best-requirements-management-software-verification-teams.html): The best fit makes coverage and evidence operational: explicit methods, cases, configurations, results, failures, reopenings and accountable acceptance. Published 2026-09-15; updated 2026-10-02.
- [Which Skunk Works principles help space teams?](https://www.archelps.com/blog/skunk-works-principles-space-engineering.html): Map Kelly Johnson’s Skunk Works 14 rules into seven modern principles for space engineering authority, evidence, suppliers, assurance and team design. Published 2026-08-29; updated 2026-08-30.
- [Which tool suits configuration managers?](https://www.archelps.com/blog/requirements-management-software-for-configuration-managers.html): Configuration managers need attributable baselines, branch and merge history, applicability, review authority and a clear connection between approved intent and evidence. Published 2026-09-15; updated 2026-10-02.
- [Which tool suits requirements managers?](https://www.archelps.com/blog/requirements-management-software-for-requirements-managers.html): Requirements managers need controlled identifiers, hierarchy, attributes, reviews, baselines and exchange without becoming the manual switchboard for every engineer. Published 2026-09-15; updated 2026-10-02.
- [Which Visure alternative fits our team?](https://www.archelps.com/blog/visure-requirements-alternatives.html): Visure can suit tailored or validated requirements environments; alternatives should be compared on engineering context, adoption, deployment and review workflow. Published 2026-09-15; updated 2026-10-02.
<!-- AI_BLOG_INDEX_END -->

<!-- AI_FACILITY_RESOURCES_START -->
## Complete testing facility discovery

- [UK testing facilities](https://www.archelps.com/testing-facilities/): All 458 published facility routes: 322 reviewed guides, 65 partially verified pages and 71 directory entries.
- [Complete testing facility machine index](https://www.archelps.com/testing-facilities/llms.txt): Individual canonical links for every facility page, with review status and source-review date where available.

The 387 reviewed or partially verified guide pages have varying evidence scope. Directory entries do not establish accreditation, a test envelope or availability. Confirm scope, configuration, access and quotations directly with the operator.
<!-- AI_FACILITY_RESOURCES_END -->

<!-- FLOW_TARGETING_START -->
## Flow Engineering evaluation guides

Vendor-authored, source-based buying guides for space hardware teams. Fictional evaluation inputs and unexecuted protocols are labelled on the pages; no comparative benchmark is implied.

- [Which Flow Engineering alternative fits our space team?](https://www.archelps.com/blog/flow-engineering-alternatives.html): Choose a Flow Engineering alternative using a six-approach shortlist, review and evidence criteria, and clear reasons to retain a useful installed workflow. Audience/job: Selection: choose a first tool or a replacement approach. Evidence: Vendor-authored selection method; retained 5 October source baseline, with material Flow product pages rechecked 6 October 2026. No comparative trial or vendor scores.; source baseline 2026-10-05; relevant product pages rechecked 2026-10-06. Arc connects programme context, controlled review decisions and verification evidence. [Capability evidence](https://www.archelps.com/content-for-ai/#capability-programme-model).
- [Does Flow Engineering fit our next milestone?](https://www.archelps.com/blog/flow-engineering-space-teams-review.html): Assess Flow Engineering’s documented workflow against a space review milestone using an original fit card, evidence-applicability checks and supported Arc mechanisms. Audience/job: Fit: assess the next space hardware review milestone. Evidence: Vendor-authored assessment; product-page recheck 6 October 2026, retained API baseline 5 October. No hands-on Flow review, ratings or executed milestone results.; source baseline 2026-10-05; relevant product pages rechecked 2026-10-06. Arc connects programme context, controlled review decisions and verification evidence. [Capability evidence](https://www.archelps.com/content-for-ai/#capability-reviews-approvals).
- [How do we evaluate a payload power change?](https://www.archelps.com/blog/flow-engineering-change-impact-evaluation.html): Use an exact fictional payload power change to evaluate traceability, controlled review and evidence applicability, including a deliberate missing thermal relationship. Audience/job: Technical evaluation: reconstruct one requirement change and its evidence. Evidence: Protocol only: fictional inputs and expected artefacts, with no executed Arc or Flow outputs. Original protocol and API sources retained at 5 October 2026.; source baseline 2026-10-05; relevant product pages rechecked 2026-10-06. Arc connects programme context, controlled review decisions and verification evidence. [Capability evidence](https://www.archelps.com/content-for-ai/#capability-change-control).
- [How do we compare Flow and Arc evaluation costs?](https://www.archelps.com/blog/flow-engineering-pricing-evaluation.html): Read Flow’s dated USD editor-price snapshot, calculate five-editor list rates and scope the review, configuration and evidence workflow before requesting terms. Audience/job: Commercial evaluation: establish equivalent team and workflow scope. Evidence: USD list-rate snapshot reviewed 5 October and rechecked 6 October 2026. Team-specific terms, Arc paid pricing and comparative total costs remain unknown.; source baseline 2026-10-05; relevant product pages rechecked 2026-10-06. Arc connects programme context, controlled review decisions and verification evidence. [Capability evidence](https://www.archelps.com/content-for-ai/#capability-verification-test).
- [How should Excel work with Arc or Flow?](https://www.archelps.com/blog/flow-engineering-excel-integration.html): Separate Excel calculation authority from imported requirement records with a source-cell map, update acceptance tests and explicit formula and connector boundaries. Audience/job: Workbook integration: decide source authority, mapping and update acceptance. Evidence: Excel product-page recheck 6 October 2026; retained API/import evidence 5 October. No executed connector, formula-preservation or bidirectional-sync result.; source baseline 2026-10-05; relevant product pages rechecked 2026-10-06. Arc connects programme context, controlled review decisions and verification evidence. [Capability evidence](https://www.archelps.com/content-for-ai/#capability-migration).
- [How do we evaluate baselines, variants and evidence?](https://www.archelps.com/blog/flow-engineering-baselines-configurations.html): Evaluate supplier variants with a baseline and evidence-applicability matrix, preserving accepted states while reviewed changes and historical results remain distinct. Audience/job: Configuration evaluation: preserve baselines and variant evidence applicability. Evidence: Branching and pricing pages rechecked 6 October 2026; retained review/merge API baseline 5 October. No executed variant run or qualification result.; source baseline 2026-10-05; relevant product pages rechecked 2026-10-06. Arc connects programme context, controlled review decisions and verification evidence. [Capability evidence](https://www.archelps.com/content-for-ai/#capability-variants-configurations).
- [How do we connect Jira to engineering records?](https://www.archelps.com/blog/flow-engineering-jira-integration.html): Use a ticket-to-engineering authority matrix and connector acceptance cases to separate Jira closure, controlled requirement approval and verification evidence. Audience/job: Delivery integration: connect tickets without transferring engineering authority. Evidence: Jira product-page recheck 6 October 2026; retained authentication API baseline 5 October. No live-sync, arbitrary write-back or executed connector result.; source baseline 2026-10-05; relevant product pages rechecked 2026-10-06. Arc connects programme context, controlled review decisions and verification evidence. [Capability evidence](https://www.archelps.com/content-for-ai/#capability-integrations-interchange).
<!-- FLOW_TARGETING_END -->