Change Management Software.
Engineering changes under control.
Manage engineering change requests, change orders, affected BOMs, CAD references, approvals and implementation tasks in one connected platform. Nora IPLM Change Management software provides configurable workflows, guided Change Cockpit visibility and traceable product change history.

Change Management Software.
One connected engineering workspace.
Configurable Change Workflows
Configure the review and implementation path for each type of engineering change. Route ECRs and ECOs through defined stages, approval checkpoints and assigned work while keeping the affected product record connected.

Notifications and Task Ownership
Notify reviewers and change owners when a decision or task needs attention. Keep group assignments, pending approvals, responsibility and progress visible without relying on scattered email threads.
Your engineering changes.
Every decision connected.
Keep the product record and the work around it in view as you move through each stage.
Streamline Product Change Management Across the Entire Lifecycle
Connect change requests, affected items, approvals, and downstream updates so teams can move faster with fewer handoff gaps.

End-to-End Change Tracking for Full Visibility
Full Visibility
Track each change request from identification through review, approval, implementation, and release. Teams can see what changed, why it changed, who approved it, and which product data was affected.

Individual & Group Task Assignments
Task Ownership
Assign change tasks to specific users or functional groups so every review, approval, and implementation step has clear ownership and accountability.

Change Management Software Features.
Move beyond a standalone ECR form. Nora IPLM connects decisions, affected product data, workflows, implementation tasks and auditable history throughout the engineering change lifecycle.
Engineering Change Requests and Orders
Capture proposed changes as ECRs, authorize implementation with ECOs, and retain the decision and execution records together.
Approval and Signoff Control
Route each change to the right engineering, quality, manufacturing and product reviewers, with traceable decisions.
Change Cockpit and Readiness
See connected change objects, the current process stage, unresolved blockers and the next valid action in one view.
Affected Items and BOM Visibility
Identify the parts, drawings, requirements, EBOMs, MBOMs and variants affected by a proposed modification.
Impact and Risk Assessment
Use baseline comparisons and linked impact or risk information to support informed decisions before release.
Change Tasks and Implementation
Assign engineering or manufacturing tasks to people and groups, monitor completion and track resulting revisions.
Workflow Flexibility and Quick Changes
Use governed workflows for complex updates or supported standalone tasks when a limited change requires less process overhead.
Change Reporting and History
Review task ownership, lifecycle status, author and date history; export available change reports for handoffs and review.
How Nora IPLM Change Management Software Works
The Change Management module brings Engineering Change Requests, Engineering Change Orders, approvals, affected items and implementation tasks into a connected PLM workspace. Instead of tracking a decision in one tool and product revisions in another, teams can work with the related records and lifecycle states together.
Change Cockpit helps users review the active change context, readiness checks and next available actions. Configurable workflows coordinate approval and implementation, while affected-item relationships, baselines and change history preserve the product definition behind each decision. For a scenario-led walkthrough, explore the engineering change management use case.

Connected change records and product scope
Explore the common types of controlled product changes managed across engineering and manufacturing.
- Engineering Change Request (ECR)Capture and evaluate a proposed product or engineering change before approval.
- Engineering Change Order (ECO)Authorize and control the implementation of an approved change.
- BOM ChangeModify parts, quantities, assemblies or product structures.
- Document ChangeUpdate specifications, drawings, work instructions or technical documents.
- Configuration ChangeControl updates to product variants, options or configuration rules.
- Manufacturing ChangeCoordinate approved product updates with downstream manufacturing information.
Why connected change information matters
- Reduce uncontrolled or undocumented product changesUse a documented ECR and ECO process so design edits cannot bypass the agreed review and authorization stages.
- Identify affected items before approvalTrace the proposed change to parts, assemblies, BOM occurrences, drawings and released configurations before selecting a solution.
- Coordinate reviews across engineering, quality and manufacturingRecord cross-functional feedback and assignments so engineering, quality, procurement and manufacturing evaluate the same proposal.
- Keep decisions, approvals and implementation history traceableKeep the change rationale, approval decisions, resulting revisions and implementation evidence linked to the original request.
- Reduce downstream errors caused by incomplete change communicationConfirm that release packages, manufacturing structures and relevant work instructions reflect the approved change.
- Accelerate release by standardizing repeatable change workflowsUse clear responsibilities and verification checkpoints to prevent completed work from waiting on ambiguous handoffs.
Configure the request-to-release workflow
- Identify the ChangeCapture the reason for the change, supporting information and the product data involved.
- Assess ImpactReview affected parts, BOMs, documents, requirements, configurations, baselines and downstream processes.
- Define OwnershipAssign reviewers, approvers and implementation responsibilities.
- Review and ApproveRoute the change through the required technical and business approval workflow.
- Plan ImplementationDefine tasks, dependencies and the product information that must be updated.
- Execute the ChangeUpdate affected product records and complete assigned implementation tasks.
- Verify CompletionConfirm that the approved change was implemented correctly across affected data.
- Release and Preserve HistoryMove the updated product information forward while retaining the full decision and change history.
Engineering Change Request vs Engineering Change Order
The request and order stages serve different decisions in a controlled engineering change process.
- Engineering Change Request (ECR): evaluate the proposalAn ECR records the problem, proposed change, affected product data and an initial assessment of cost, risk and feasibility. Reviewers decide whether to approve, reject, defer or revise the proposal. An ECR does not, by itself, authorize implementation. Read the ECR guide.
- Engineering Change Order (ECO): execute the approvalAn ECO controls the approved scope, owners, tasks, affected revisions, verification activities and release decision. It provides a record of what was implemented and when the updated definition becomes effective. Read the ECO guide.
- A connected handoffThe approved ECR should supply the ECO with the decision rationale and affected items; the ECO should return implementation results, verification and release status. Compare ECR and ECO in detail.
From change request to release.Every impact accounted for.
Consider an illustrative design revision: assembly testing identifies a fit issue with a pump housing used in two equipment variants. Engineering opens an ECR linked to the affected item, drawing and BOM occurrences. Change owners assess the possible replacement revision, review affected variants and assign the required technical approvals.
Within Nora IPLM, the connected change records and Change Cockpit give reviewers a way to follow scope, ownership, readiness and outstanding decisions. Once approved, an ECO governs resulting revisions, engineering tasks and verification before release.
Managing a design revision
Follow an illustrative housing revision through the software workflow, from ECR to impact review, approval, ECO execution and release.
Assembly testing identifies a fit issue in a pump housing used by two product variants.
Change impact analysis before approval
Review connected product data before approving a change. Select a category to see its review focus.
Review affected components and assemblies before any replacement is approved.
Change Cockpit.
A guided view of the next action.
Nora IPLM Change Cockpit connects the change context, affected records, readiness checks and active tasks. Teams can see what is complete, what is blocked, and which governed action can move the change forward.
Connected change context
Review the active Change Context together with affected items, assessments, ECRs, ECOs and related tasks. Work from connected product information rather than reconstructing the process across separate records.
Readiness and blockers
See lifecycle requirements, missing information, outstanding relationships and ownership gaps before trying to advance the change. Resolve the actual prerequisite, not just the visible symptom.
Approvals and rework
Review the current decision stage, approvers, recorded outcomes and rework requirements within the same change context. Keep authorization distinct from completed engineering work.
Implementation and evidence
Follow change tasks, assigned owners, release readiness and the evidence supporting completion. Preserve a traceable connection from the proposed modification through the resulting product definition.
Explore the dedicated Nora IPLM Change Cockpit page for the guided interface, process paths, readiness checks and available actions. The exact steps depend on your configured change process.
How Change Management Software Improves Product Control
Controlled change management protects product integrity while helping teams move approved updates through the lifecycle efficiently. By keeping impact, ownership, approvals and implementation connected, teams can reduce rework and make change decisions with greater confidence.
Reduce change-related risk
Review affected product information before approved changes move downstream.
Keep teams aligned
Keep engineering and manufacturing teams aligned around controlled updates.
Maintain lifecycle control
Maintain approvals, change traceability and a complete history of product decisions.
Accelerate implementation and release
Move approved changes through repeatable workflows with clearer ownership.
Explore the workspace.
Follow the product context.
Engineering change guides for the next step.
Explore dedicated guides for ECR evaluation, ECO execution and the ECR-to-ECO handoff. For a practical engineering scenario, see the Change Management use case.
Engineering Change Request (ECR)
Learn what a change request should contain, how teams assess feasibility and impact, and how a proposal moves through review before an ECO is created.
Explore the ECR processEngineering Change Order (ECO)
See how an approved proposal becomes an implementation plan with assigned owners, updated product records, verification and controlled release.
Explore the ECO processECR vs ECO: Understand the distinction
Compare the goals, typical reviewers, expected outputs and decision gates of an ECR and ECO to avoid mixing evaluation with authorized execution.
Compare ECR and ECOKeep CAD data, product configurations and approval workflows connected to each change so the updated product definition remains understandable across departments.
Change Management
Software FAQs
Answers about change workflows, affected items, Change Cockpit, reporting, and engineering release control in Nora IPLM.
What does Nora IPLM Change Management software manage?
The module connects ECRs, ECOs, affected product records, approval workflows, change tasks, implementation status and release history. Teams can manage controlled product updates without separating the decision record from the underlying item or BOM data.
How does Change Cockpit help with engineering changes?
Change Cockpit provides a guided view of the active Change Context, connected records, readiness checks, blockers, approvals, tasks and next valid actions. Available steps depend on the configured change process and the status of related records.
Can teams configure different change approval workflows?
Yes. Nora IPLM supports configurable change workflows, review and approval routing, assignee-based tasks and different paths for changes with different governance needs. Review and implementation remain connected to the product data being changed.
How are BOMs and CAD files connected to change records?
Change records can reference affected items, BOM structures, drawings, CAD data and other managed records. This helps reviewers identify the scope, coordinate revision updates and retain traceability between the original and resulting product definitions.
Can Nora IPLM compare baselines during change impact analysis?
Yes. Baselines can be used to compare product states and assess changes that affect configurations, variants and requirements. The result supports impact review before the proposed change is approved for implementation.
Can small changes be handled without a full change process?
Nora IPLM supports standalone change tasks for appropriate quick or limited updates. The permitted path depends on the organization’s configured workflows and governance requirements; critical changes may still require formal review and approval.
What change reporting and history does Nora IPLM provide?
The module supports change-task and assignee-based reporting, export of change reports to Excel, and logs that preserve information such as author, date, status and the history of lifecycle decisions and work.
Can change implementation tasks be assigned to teams?
Yes. Tasks can be assigned to individuals or functional groups, helping engineering, manufacturing, quality and other owners track the work required after approval and verify completion before release.
Change Management Software.
See the entire change in context.
Explore Nora IPLM workflows, Change Cockpit, impacted product data and accountable implementation tasks with a 30-day trial or live sandbox.