Which evidence applies to each variant?
Flow Engineering documents branches for isolated proposals, required reviews before merge, immutable baseline snapshots and product variants. These Branching descriptions were rechecked on 12 November 2026. For a supplier change, inspect which requirement revision and verification result applies to each configuration. A branch or variant label alone does not establish that evidence can be reused.
Arc is also a documented candidate for connected requirements and architecture, controlled review decisions and configuration-linked V&V evidence. Compare the same accepted state, proposed supplier option and applicability rationale in each product. Arc publishes this vendor-authored guide and has a commercial interest in its selection. The variant matrix is fictional and no review or qualification was executed. Earlier API sources retain their 5 October 2026 review date.
How do baseline, branch and applicability differ?
An accepted baseline identifies the record set accepted by the programme’s authorised process. A working branch holds a proposal relative to that state. Applicability states which requirement revision, supplier option, hardware/software configuration or evidence record belongs to which variant. Those three concepts serve different purposes.
A merge can update a controlled record set when permitted by the accepted process; it does not by itself establish engineering acceptance or contractual release. A variant label also needs a definition. “Supplier B” alone cannot identify the as-built and as-tested state that a verification result represents.
What does Flow document for configuration?
Flow Engineering’s Branching page describes required reviewers, a record of who approved each merge, timestamped immutable baselines and variants without duplicating engineering work. It also documents branch exports as PDF, DOCX and CSV. Confirm role, administrator and API exception paths for the actual deployment. The older 5 October API review is separate from this 12 November Branching check.
The 5 October 2026 pricing snapshot, rechecked 6 October, documents one configuration for Basic and unlimited configurations for Pro. Those are package allowances. They do not establish how requirements, supplier changes and test evidence are controlled in the chosen environment. Use the commercial scope guide to confirm entitlement separately from technical acceptance.
What does the two-variant scenario test?
Fictional variant method. Variant A retains the accepted supplier arrangement in B1. Variant B is a proposed alternative supplier arrangement under review. Both must meet the identified electrical interface; no assertion is made that either has completed qualification. The shared baseline definition and power change supply the original IDs and arithmetic.
Here the new decision is applicability, not another full power exercise. Treat supplier identity, article configuration and requirement revision as explicit fields. Variant B’s proposal does not alter Variant A’s accepted state. The deliberately incomplete thermal relationship remains unresolved for the affected proposal; introducing variant labels does not repair it.
What belongs in the variant matrix?
Original on-page resource: variant applicability matrix, FT-P06. “B1 accepted revision” and “proposed revision” are descriptive states for the fictional protocol, not invented version labels. Potential result references below are evidence to identify in a real evaluation; no test result has been produced here.
| Requirement / state | Supplier configuration | Verification activity | Result revision / status | Disposition | Authority and rationale |
|---|---|---|---|---|---|
| PAY-PWR-014, B1 accepted revision. | Variant A, accepted supplier arrangement. | TEST-PWR-02 for the B1 condition. | Actual result/revision not supplied in this protocol. | Preserve B1 and original evidence scope. | Systems and test owners identify any real result’s original article and condition. |
| PAY-PWR-014, proposed revision/context. | Variant B, alternative supplier proposal. | TEST-PWR-02 scope requires review for the proposal. | No executed Variant B result. | Evidence applicability unresolved; no automatic carry-over. | Test owner determines analysis or test work needed for the changed configuration. |
| IF-PWR-003, B1 interface requirement. | Both variants are intended to satisfy the interface; proof is separate. | TEST-IF-03. | No shared result or qualification claimed. | Compare article/setup and supplier implementation before reuse. | Interface and test owners record the applicability rationale. |
| PAY-THM-005, thermal requirement. | Variant B proposal; investigate affected scope. | AN-THM-04 is available, with a deliberately incomplete relationship. | No thermal applicability result. | Keep the missing relationship and physical assessment open. | Thermal owner supplies and reviews the dependency model. |
For real records, add actual revision IDs, source baseline, serial or build references, procedure revision, result and review decision. A row is accepted only when the responsible authority can explain its applicability; an empty evidence field remains unknown.
How do we propose the supplier change?
Capture Variant B’s proposed requirement and supplier context in a controlled branch. Inspect differences against the identified source baseline, affected interfaces and proposed verification work. Reviewers should see which variant changes and which accepted records remain unchanged.
Arc records the proposal, review context and attributable decisions before a controlled baseline change. Require an actual evaluation to show reject/revise/accept state and the authorised decision. An administrator permission or merged record is not a substitute for the programme’s engineering and contractual authority.
Can we reuse the historical evidence?
Compare requirement revision, supplier implementation, hardware/software build, test setup, environment, procedure and acceptance criteria. If the differences are irrelevant under a justified applicability rationale, the responsible owner can accept reuse. If they change the verified condition, plan the needed analysis or test. If their significance is unknown, keep reuse unresolved.
The earlier result stays linked to its original scope; it does not disappear because a proposal changes. The evidence-applicability guide separates accepted design, realised unit and test configuration. No result for Variant A automatically closes Variant B’s verification row.
Can we reconstruct the variant decision?
In an actual evaluation, ask a reviewer to identify each accepted baseline, proposed supplier change, requirement revision, evidence scope and rationale from the approved package. Record which relationship and review information is in the export and what remains in the application. A PDF or CSV format label alone does not prove complete programme reconstruction.
The protocol execution-status section explains the evidence needed. No screenshots or executed variant exports are published here. When a proof is missing, record it rather than declaring the exercise passed.
Which specialist systems remain authoritative?
The configuration authority matrix distinguishes engineering requirements from CAD, PLM, BOM, build and test records. Arc maintains the configuration-specific requirement, review and evidence context; the agreed specialist system can remain authoritative for product definition or realised-unit data.
Before adoption, reconcile baseline membership, identifiers, applicability relationships, historical decisions and references to specialist records. Retain a mandated PLM or established Flow workflow when it already preserves those controls or cannot yet be reconciled. Choose Arc for the stated criteria once the actual variant workflow and operating boundary are accepted; product choice alone does not qualify hardware or approve a contractual baseline.
Frequently asked questions
Is a branch an accepted baseline?
No. A branch can hold a proposed change. An accepted baseline is the identified record set accepted by the authorised process. Review disposition, permissions and the resulting accepted state must be explicit before proposed content becomes authoritative.
Does one test result apply to both variants?
Only with a justified engineering applicability decision. Compare requirement and procedure revisions, supplier configuration, article, setup and operating conditions. Preserve the original result and record the rationale for any reuse; a linked report does not automatically verify another variant.
Do Flow Engineering configuration allowances establish workflow capability?
No. Flow Engineering’s displayed limits checked on 12 November 2026 match the 2 November snapshot: Basic has one configuration and Pro has unlimited configurations. Those allowances describe package scope. Demonstrate variant-specific review, preservation of the accepted baseline and evidence applicability separately in the proposed plan and deployment.
Can Arc replace the authoritative PLM record?
Arc controls configuration-specific engineering requirements, baselines and evidence. That does not establish ownership of CAD, BOM, serialised manufacturing or authoritative PLM records. Keep the agreed specialist authorities and reconcile their references unless a different boundary is separately accepted.
Does keeping the same 28 V interface justify evidence reuse for both suppliers?
No automatic reuse follows from that shared requirement. Compare the supplier implementation, article and hardware/software build, setup, environment, procedure and acceptance criteria. Preserve the original result and record the responsible owner’s applicability rationale, new work or unresolved decision for the proposed variant.