On this page

Flow Engineering Excel Integration: Cells, Formulas and Requirements

Which records move and which stay in Excel?

Flow Engineering documents an Excel integration that connects spreadsheets, maintains versioning and checks specific cell values against requirements. The Excel entry in Flow Engineering’s integration catalogue was rechecked on 12 November 2026. It establishes that documented scope. Demonstrate update direction, cell identity, permissions and failure handling for the proposed connection before relying on write-back or synchronisation.

Excel can remain the calculation authority. Arc is an option when approved requirement imports need connected architecture, controlled review and configuration-linked V&V evidence. Arc imports approved formats including CSV. That does not establish a native Excel connector or preservation of workbook formulas. Arc publishes this vendor-authored guide and has a commercial interest in its selection. The workbook examples are fictional and no connector run is reported. Earlier API and import sources retain their 5 October 2026 review date.

What does Flow document for Excel?

Flow Engineering’s catalogue describes spreadsheet versioning and cell-value checks against requirements. This narrow catalogue check does not establish every trigger, direction, write-back rule, retry or permission behaviour. The workbook authority map below separates stable requirement IDs from cell coordinates and keeps formula logic with its controlled workbook.

Ask for a demonstration on the exact workbook, selected edition and permitted environment. A named integration is useful evidence of category scope; it is not proof that a renamed sheet, deleted cell or failed update will preserve the authority your programme needs. The same evidence standard applies to an Arc import or approved interchange route.

Who owns requirements and workbook behaviour?

A requirement row has an ID, text, revision, owner, parent/allocation and verification relationships. A budget cell may contain a formula whose result depends on multiple inputs. Comments can explain a calculation without being an approval record. Attachments and release history carry meaning that a CSV value does not represent.

Declare one owner for each category. For example, Excel owns the power-budget calculation; Arc owns the approved requirement and review record; a controlled file revision supports the calculation result cited by that record. Do not leave both a cell and a programme field editable as competing authorities without an accepted update direction and conflict rule.

What happens when a cell changes or disappears?

Original on-page resource: workbook authority map, FT-P05. The fictional workbook is a coexistence test, not an executed connector result. Stable requirement IDs are distinct from sheet names and cell coordinates. For each row retain the source revision, mapped field and relationship meaning before any update.

Fictional Flow Engineering Excel evaluation workbook FT-P05: source cells, stable requirement IDs and operating ownership. Illustrative power values are in watts (W). No connector execution is reported.
Sheet/rangeRecord ID / revisionValue or formulaOwner and mapped fieldRetained file / relationshipReconciliation and failure case
Requirements!A12:G12WB-REQ-012; workbook Rev A.Requirement text, unit and parent ID are record values.Systems owner; requirement text, unit and parent relationship.Controlled Rev A workbook; parent ID becomes a typed link.Compare ID/text/link endpoints; reject a duplicate ID or unresolved parent.
Budget!C8WB-SRC-008; Rev A → proposed Rev B.Input value changes from 7 W to 9 W, fictional.Power owner; source value/reference, not automatic baseline acceptance.Both workbook revisions retained; analysis source for the affected requirement.Inspect the changed value and provenance; review before changing an accepted record.
Budget!C20WB-CALC-020; workbook Rev A.SUM formula producing a budget total.Power owner; Excel remains calculation authority.Controlled workbook with formula logic; programme record cites result and revision.Recompute in Excel and reconcile exported value; do not label CSV as formula preservation.
Checks!D5WB-SRC-005; missing in proposed Rev B.Previously accepted source value has disappeared.Source owner; missing-source disposition.Retain last accepted value and Rev A provenance.Acceptance rule requires a visible exception; no silent deletion or zeroing.
Review note / attached drawingWB-DEC-003 and attachment reference.Comment/file and attributable approval have different meanings.Review owner; map supported record categories separately.Original file and review context retained.Reconcile attachments and historical decisions; a cell value does not establish completeness.

For the changed cell, require the proposed value and source revision to be visible before acceptance. For the missing cell, require an explicit exception with the last accepted state preserved. Those are evaluation acceptance rules; no particular connector behaviour has been demonstrated here.

How do we map records into Arc?

Arc imports CSV, Word, Jira, Git and Confluence within the approved source scope. Define persistent IDs, hierarchy, units, custom fields and relationship endpoints before importing. A column containing several IDs requires a declared link meaning and endpoint reconciliation, not merely a copied text field.

Arc preserves the confirmed IDs, relationships, attachments, baselines and historical review records within the agreed mapping. Reconcile those categories against the source and retain workbook behaviour separately where necessary. Use the existing Excel migration guide for the full method; this page concentrates on coexistence and integration acceptance.

What does a CSV value leave behind?

CSV is useful for field/value transfer. It does not carry formula logic, macros, workbook formatting, cell comments, permissions or approval semantics as functioning Excel behaviour. If a requirement cites a computed budget, retain the controlled workbook and its calculation revision as source evidence.

Do not promise arbitrary workbook round trips through PDF, Word, Excel or CSV merely because Arc exports those formats. Arc’s confirmed export scope includes PDF, Excel, Word, PowerPoint, Markdown, ReqIF, CSV and plain text; the content and machine-readable relationships in each specific package still need reconciliation. File-format availability is distinct from preserving every workbook function.

What should the update tests prove?

Flow Engineering Excel or Arc import acceptance cases: expected source/update evidence. This is an unexecuted protocol, not a write-back or synchronisation result.
Case to demonstrateAcceptance evidenceDecision if unresolved
Source value changesDirection, source revision, mapped field and controlled proposal are explicit.Keep the accepted programme value until the owner approves the update.
Sheet renamed or source cell removedStable source identification or visible missing-source exception.Retain provenance and resolve the source mapping.
Permission revokedNo unauthorised read/write; visible failure and accountable owner.Do not treat stale data as a successful refresh.
Interrupted update or retryWhich fields changed, failure state and duplicate prevention are inspectable.Reconcile before repeating or accepting the package.
Programme field and workbook both changeAccepted conflict/authority rule rather than silent last-write replacement.Stop dual entry for the affected authoritative field.

These are cases to prove on the chosen interface, not procedural instructions for an untested connector. Arc’s approved integration and interchange categories also require deployment-specific confirmation.

Can we review the imported requirement?

Use a representative imported requirement, its controlled source file and a verification activity. Propose a change, inspect differences and ask named reviewers to record the disposition. The verification owner then identifies which result, procedure and configuration remain applicable. A successfully imported row does not by itself demonstrate that workflow.

The change protocol provides the separate technical exercise. Where delivery work also uses Jira, the Jira authority guide keeps ticket completion distinct from engineering acceptance.

When should authority move?

Compare source and mapped record counts, unique IDs, required fields, relationship endpoints/meaning, attachment references, baseline membership and historical decisions. Record every exception with an owner and acceptance rationale. Confirm the retained workbook and how new approved calculation revisions will enter the programme record.

Retain Excel for a stable small requirement scope or an established calculation workflow when it already provides defensible control. Retain installed Flow integrations when they meet the accepted boundary. Choose Arc for connected requirements, reviewed change and applicable evidence only after the mapping and coexistence decision are accepted; this guide supplies no completed Flow-to-Arc transfer evidence.

Frequently asked questions

Does CSV preserve Excel formulas?

CSV transfers represented field values. Formula logic, macros, comments, formatting and approvals remain with the controlled workbook. Reconcile imported values against its source revision.

Does Flow Engineering’s documented Excel integration prove write-back?

No. Flow Engineering’s integration catalogue, checked 12 November 2026, describes connecting spreadsheets, maintaining versioning and checking specific cell values against requirements. Demonstrate update direction, mapped fields, permissions and failed-update behaviour before relying on write-back or two-way synchronisation.

Can Excel remain the calculation authority?

Yes. Keep calculation logic in the controlled workbook and identify its supporting revision. Agree which programme values and relationships Arc owns and how reviewed updates cross that boundary.

What should happen when a source cell disappears?

The acceptance rule should flag the missing source and retain the last accepted value with its provenance until an owner resolves the change. Do not silently delete or zero a requirement. Test the exact connector or interchange route before relying on that behaviour.

What should be proven when both Excel and a programme field can change?

Declare one authoritative owner and accepted update direction for the affected value. Demonstrate source revision, proposed change, permissions, provenance and conflict disposition; if the conflict cannot be explained, retain the accepted state and stop dual entry for that field until the owner resolves it.

Move faster without compromising engineering rigour.

Discuss agreed record mapping and reconciliation while your workbook’s calculations remain authoritative.