Confirm which Altium application holds the source before exporting. The current Requirements Portal and the legacy-labelled Requirements & Systems Portal have different documented contexts. A specification document may be a useful deliverable, but it is not automatically a portable system model or review archive.
Which Portal and entitlements are in scope?
Record the product name, subscription, workspace, revision and whether the project originated in Valispace. Altium marks the older Requirements & Systems Portal documentation legacy; confirm the actual application's feature set with the owner. Inventory requirement IDs, parameters, verification activities, links into ECAD designs and any system-design objects used by the programme.
Which export is available?
Altium documents a Requirements Portal document export for selected requirements and specifications. Compare the chosen template and scope with the source inventory. Ask the vendor or administrator what structured interchange is available in the exact subscription if live relationships must move. Do not prescribe a CSV or API path without that confirmation.
How do we preserve electronics context?
Choose a synthetic power-board requirement linked to a schematic and a system-level thermal limit. Verify requirement text, identifiers and verification method in the output. Then inventory the ECAD link and the design revision it points to. A document export may communicate the requirement while the live design link remains in Altium; decide whether it stays authoritative there.
Which legacy and approval records remain?
For a Valispace-origin programme, inspect parameter formulas, blocks, scripts and verification records before assuming parity in the current Portal or a destination. Keep historical approvals and release artefacts in a read-only archive if they cannot be represented as native destination records. Establish a new baseline only after discipline owners accept the mapping.
What should the Arc import preserve?
Arc's direct import list does not name Altium. A project-specific agreed exchange is required. Arc can govern cross-discipline requirement and verification context, while Altium remains the electronics design authority; make link ownership explicit.
Frequently asked questions
Which Altium application should the export plan identify?
Name the exact current or legacy application, workspace and subscription. Altium calls the current Portal a successor, while its Requirements & Systems Portal documentation is labelled legacy.
Does document export preserve live ECAD links?
Do not assume it does. Inventory design links and revisions separately from exported requirement text.
Can Arc import Altium natively?
A native Altium adapter is not in the approved direct import scope. Confirm a supported exchange for the particular deployment.
Evaluate a representative import in Arc
Agree the record mapping and reconciliation for a representative source package. Arc connects accepted requirement records to system context, controlled changes and verification evidence.
Luc will email from luc@archelps.com to arrange setup. Agree scope and data handling before adding programme information.