Product
How SourcePilot does the engineering.
Four capabilities on one version-controlled model: requirements, the system model, agents on branches, and the physics down to the eBOM.
Requirements management
Requirements an engineer can build to.
From a customer brief or your existing specifications to structured, testable requirements, each checked, owned and traced from the first line.
See it on your product →From any source
Customer briefs, specifications and DOORS or Polarion exports become structured requirements.
Written to be tested
EARS pattern, acceptance criteria and a verification method on every requirement.
Checked as you go
INCOSE quality rules flag ambiguity, conflicts and gaps before design starts.
Owned by a subsystem
Each requirement flows down to the subsystem responsible for meeting it.
System modelling
One system model, from functions to parts.
The product is decomposed into what it must do, then allocated to the subsystems that do it, with typed interfaces and a completeness check at every layer.
See it on your product →Functions first
What the product must do is settled before anyone chooses how.
Nothing unowned
Every function has a performer, and the completeness check closes each layer.
Typed interfaces
Mechanical, electrical, hydraulic and data ports must match to connect.
Your data model
Add node types, attributes and rules for your own products, by configuration.
Agents and branches
Engineers and agents, each on a branch.
The whole design is version-controlled, down to the eBOM. Engineers work on their own branches; agents explore alternatives on theirs and come back with proposals.
See it on your product →Your own branch
Each engineer changes the design on a branch, never on the released version.
See the other branches
What colleagues are changing, and what it touches, is visible before it merges.
Agents in parallel
Send agents to explore architectures or options; each returns a proposal with its trade-offs.
Merge on approval
Diff, review, merge. Every step records who proposed it and who approved it.
Physics and eBOM
From the physics to the part on the line.
The physics engine computes what each part must do. That becomes a specification, the specification is matched against real candidates, and the result is a traced eBOM.
See it on your product →Computed attributes
Forces, torques, power and energy derived from the requirements in one energy-based model.
Part specifications
Each attribute becomes a specification the part must meet, with its margin.
Matched candidates
Candidates from your libraries and approved suppliers, checked against the specification. You choose.
A traced eBOM
Part number, specification and source on every line, traced to its requirement and exported to your PLM.
Apply it to your products.
Bring one product family. We build its model on your data and show you the engineering work coming back.