# Arc > Canonical product evidence and selected engineering resources published by Arc. Updated: 7 September 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. - 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 evidence boundaries. - [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, boundaries and stable citation anchors. - [Requirements management questions](https://www.archelps.com/#faqs): Current answers about migration, change, review, verification and deployment. ## 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 does not present these as regulated electronic signatures. - [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): Integrated APIs, webhooks, connectors and controlled interchange; named connections are confirmed per 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. ## 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. - [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 boundaries, 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, not a fourth hosting model. Customer content is never used by Arc or enabled providers to train models. Arc publishes workflow-support claims rather than certifications or agency approvals. ## 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): Arc's supported controlled workspace compared with source-owned requirements-as-code approaches. - [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. - [The Future of Systems Engineering with AI: What Space Teams Should Prepare For](https://www.archelps.com/blog/future-of-systems-engineering-ai.html): A grounded outlook on AI in systems engineering: connected models, evidence-aware assistance, changing engineering work and investments space teams can make now. - [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. ## 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. ## 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.