Guide · MBSE practice
Configuration management and change control in MBSE
Configuration management keeps a system's agreed definition and its real state in step: what each item is, which version was agreed, who may change it and how, and proof that the product matches the record. This guide explains the five functions, baselines, the change board, classes of change and what a change request must hold, then walks one requirement change on a CubeSat model from request to audit.
On this page
What configuration management is
A system under development changes every week. Requirements are refined, parts are swapped, interfaces are renegotiated, software gets new builds. The trouble starts when nobody can say which version of the requirements the design was checked against, which drawing the flight unit was built to, or whether the test that passed last month still applies. Configuration management is the discipline that answers those questions at any moment.
It rests on a simple idea: some states of the system are agreed, and an agreed state changes only through a controlled, recorded decision. Items must be identified before they can be agreed; the agreement is captured as a baseline; changes to a baseline go through a request and a decision; the records show where each item stands; and audits check that the records and the product match.
The standards say much the same thing in their own words. ISO/IEC/IEEE 15288 describes configuration management as a technical management process (clause 6.3.5) whose outcomes include identified configuration items, established baselines, controlled changes, available status information and completed audits. ISO 10007 gives guidance for configuration management in organizations of any kind, and SAE EIA-649 sets out its principles for products, with a strong emphasis on consistency between requirements, product and product information. The NASA Systems Engineering Handbook covers it in section 6.5, and the INCOSE Systems Engineering Handbook lists it among the technical management processes.
The five functions
Most descriptions divide configuration management into five functions. They are not phases; all five run for the life of the program.
| Function | Question it answers | Typical output |
|---|---|---|
| Planning and management | How will this program control its configuration, and who decides? | A configuration management plan: items, baselines, board, authority levels, records |
| Identification | Which items are controlled, and how is each one named and versioned? | A list of configuration items with identifiers, owners and the documents that define them |
| Change control | How is a change to an agreed item proposed, evaluated, decided and carried out? | Change requests, impact assessments, board decisions, implementation records |
| Status accounting | What is the current approved configuration, and what is pending? | Baseline records, the change log, the status of each request, effectivity |
| Verification and audit | Does the product match its requirements and its documentation? | Functional and physical configuration audit reports, discrepancies and their closure |
Identification
A configuration item is anything the program decides to control as a unit: a system, a subsystem, a software build, a specification, an interface definition. Identification gives each item a unique identifier, an owner and a defining set of information, and decides how versions are named. Control at too high a level hides changes inside large items; too low a level buries the board in paperwork. A common rule is to make an item of anything that is separately specified, separately verified or separately delivered.
In a model, identification is partly done for you. Each requirement, function, component and test already has an identifier and a number, and the relationships say which items belong together. What remains is the decision of which items are agreed and therefore controlled.
Baselines
A baseline is an agreed description of the system at a point in time, formally reviewed and approved, that serves as the basis for further work and changes only through change control. Programs usually build three in sequence:
- Functional baseline: the approved system-level requirements, typically after the System Requirements Review (SRR) or System Functional Review.
- Allocated baseline: the requirements allocated to each subsystem and the interfaces between them, typically after the Preliminary Design Review (PDR).
- Product baseline: the build-to and code-to definition of each item, typically after the Critical Design Review (CDR), confirmed at the physical audit.
Each baseline adds to the previous ones: after PDR, a change to a system requirement still goes through the board.
Status accounting
Status accounting is the record-keeping that lets anyone answer "what is the current approved configuration, and how did it get here?" It holds the baselines, every change request with its status and decision, the version of each item, and the effectivity of each change: which units or serial numbers it applies to.
Verification and audits
Two audits close the loop near the end of development. The functional configuration audit checks, from the verification records, that each item meets the requirements in its baseline. The physical configuration audit checks that the item as built matches its product definition: drawings, parts lists, software versions. Both depend on records: an audit cannot confirm what was never written down.
The change board
The configuration control board (CCB, or change board) is the group with authority to approve or reject changes to a baseline. It is usually chaired by the program manager or chief engineer, with the systems lead, the owners of the affected subsystems, verification, quality, and, where a change touches cost or contract, someone who can commit those.
A few principles keep a board useful:
- Authority matches scope. A change inside one subsystem that touches nothing outside it can be decided by that subsystem's board or lead. A change to a system requirement, an external interface or the contract goes to the program board, and some go further to the customer.
- The requester does not decide alone. The engineer who wants a change prepares the case; someone independent decides. A solo or very small team may approve its own changes, but it should still write down the reason and the impact.
- Decisions rest on an impact assessment. A board asked to approve a change without knowing what it touches is guessing.
- Every decision has a record: who decided, when, on which version of the request, with what conditions.
A board that meets weekly to approve typo fixes slows the team without protecting anything; tiered authority keeps the program board's time for changes that matter.
Classes of change
Programs classify changes so that each goes to the right authority and gets the right depth of review. The names vary, but most schemes follow the same split:
| Class | What it covers | Usually decided by |
|---|---|---|
| Major (often Class I) | Affects form, fit or function, a requirement or external interface in a baseline, safety, cost, schedule or a contractual term | The program board, and the customer where the contract says so |
| Minor (often Class II) | Corrects or clarifies documentation, or changes a design detail without affecting the items above | The item owner or a lower-level board, with the program board informed |
| Editorial | Spelling, formatting or numbering with no change of meaning | The document owner, recorded but not reviewed in depth |
Two related records are often confused with changes. A deviation is permission, before an item is built, to depart from a requirement for a limited number of units or a limited time. A waiver accepts an item already built that does not meet a requirement. Neither changes the baseline: the requirement stays as it is, and the departure is recorded against it. If the same deviation is requested again and again, the requirement itself probably needs a change request.
What a change request holds
A change request is the unit of change control. Whatever the form, a complete one answers these questions:
| Field | What to write |
|---|---|
| Identifier and title | A unique number and a short statement of the change ("Raise 3.2 Battery Capacity to 80 Wh"), not the problem ("battery issue") |
| Originator and date | Who raised it and when |
| Reason | Why the change is needed and what it should achieve, with the evidence |
| Affected items | The items that change, by identifier |
| Proposed change | The exact old and new text or values, not a description of them |
| Impact | What else the change touches: requirements, design, analyses, verification, interfaces, documents, cost, schedule and risk |
| Classification and urgency | The class of change and how soon a decision is needed |
| Effectivity | Which configurations, units or serial numbers it applies to, and from when |
| Disposition | Approved, approved with conditions, rejected or returned, with the approvers and their notes |
| Implementation record | When and how the change was carried out, and the follow-up actions with owners |
The change control process
The process has two halves around the decision. Before it, the request is prepared and its impact assessed. After it, the change is carried out and followed through until nothing affected by it is left unchecked.
- Raise the request. State the change exactly, with the reason.
- Assess the impact before approval. Trace forward and backward from each changed item, search for the value where no link reaches, and size each consequence. The change impact analysis guide describes this step in detail.
- Classify and route. Decide the class of change and send the request to the authority that matches it.
- Decide. The board approves, rejects or returns the request, on the record, against the exact version it reviewed. If the request changes after a vote, the vote no longer applies.
- Implement under control. Apply exactly what was approved, as one recorded step tied to the request.
- Follow through. Check every dependent item against the new definition: review the flagged trace links, re-run the verification that was judged against the old value, update the documents, and close the actions the board attached.
- Record and close. Update the status records and baselines, and close the request only when its follow-up actions are done or owned.
Step 2 and step 6 use the same trace links in opposite directions of time. The requirements traceability guide explains how those links are built and why suspect links appear after a change.
What changes in a model-based project
In a document-based program, the configuration items are documents and the baselines are document revisions. In a model-based program, the controlled items are model elements, and the documents are views of them. That changes the practice in four ways:
- Control at the element level. An approved requirement or a baselined component can be locked individually, while drafts around it stay open for work.
- Impact comes from the links. The relationships give a first impact list at once; it is only as complete as the links.
- Baselines are snapshots of the model. A baseline captures every item and relationship at once, and comparing two baselines lists exactly what changed between them.
- A change can be prepared as a draft of the model. Instead of describing the change in a form, the engineer edits a private copy, and the board reviews the model as it would be after the change.
Worked example: a battery requirement change on EO-1
The example uses EO-1, a fictional 6U CubeSat that images farmland, built as an LML project in Holarch. It is the same model as the end-to-end MBSE example. Its system requirements are in SRS-001 EO-1 System Requirements Specification, with a document baseline SRR Baseline. The latest project baseline is EO-1 Flight PDR, taken at PDR and labelled with the configuration CFG-1 EO-1 Flight. The model also holds a product line with two configurations, CFG-1 EO-1 Flight (serial numbers 1 and 2) and CFG-2 EO-1 Lite (serial 3 on), and one draft change request, CR-1 Shorten the planning cycle. A new request therefore becomes CR-2.
On the hosted service, configuration control comes with the Individual and Team plans; approval rules, change boards and working in change requests come with the Team plan. The desktop app has no plans.
Turn on configuration control
In the demo, configuration control starts off. A project owner opens Control & Reviews → Change Requests, clicks Settings and ticks Changes to approved and baselined items require a change request. From then on, approved requirements and items in the latest project baseline can no longer be edited, deleted or linked directly. Comments, reviews, requirement approvals and link-review marks stay open, because the review of a change needs them.
The same dialog holds the approval rules: Approvals required (1 to 3), Who approves (project owners, owners and editors, or a change board of named project members on the hosted service) and whether authors may approve their own requests. For EO-1, a program board might be the program manager and the systems lead, with two approvals required and no self-approval. On the hosted service without the Team plan, a project owner's approval decides, and the author may approve their own request, which suits one person working alone.
Raise CR-2
Requirement 3.2 Battery Capacity reads "The battery shall store at least 77 Wh at beginning of life", with the rationale that it covers the 36-minute eclipse at 30 percent depth of discharge with margin for fade. It is Approved and part of both baselines. The model also records a part change: from serial number 2 on, the battery pack heater is software-controlled and draws 3 W instead of 2 W, which adds to the energy the battery supplies in eclipse. The power engineer asks for 80 Wh to keep the margin.
The request is raised from Control & Reviews → Change Requests → + New Change Request, or from Propose Change… in the Item View of 3.2. Its Title is "Raise 3.2 Battery Capacity to 80 Wh" and its Reason states the evidence: the heater change from serial 2 and the depth-of-discharge margin it erodes. After Create, Add Item… adds 3.2 to the Affected Items, and Holarch lists the items traced to it with a + to add each one that changes too.
Two changes are staged with Add Change ▾ → Change an Item… and Stage Change:
- 3.2's description: 77 Wh becomes 80 Wh, shown as a word diff, with the rationale updated through the Attribute and Value fields of the same dialog or a second change.
- TC-07 Battery Capacity Test's Expected Result: "Capacity ≥ 77 Wh" becomes "Capacity ≥ 80 Wh", so the test threshold moves with the requirement instead of lagging behind it.
Nothing in the model has changed yet. The battery pack itself is a design decision (new cells, or a ninth cell) that needs its own trade; the board can approve the requirement with an action to raise the design change as a follow-up request.
Read the Impact list before approval
Each staged change carries an Impact list: the items that trace to it, computed before anyone votes. Its heading shows the counts, and the rows are grouped into requirements, tests and verification, interfaces, documents, diagrams, items in other projects and other items. Each row is marked Affected (one relationship from the changed item, or a document or diagram that shows it) or Check (one step further).
For the change to 3.2, the affected rows include the items that satisfy it (1.3.2 Battery Pack, F3 Generate and Store Power and F3.2 Store Battery Energy), the test that verifies it (TC-07), the section it belongs to and the specification SRS-001 that shows it. One step further, the check rows reach what those items connect to, among them 3.3 Depth of Discharge (also verified by TC-07), the battery's Rated Capacity value of 77 Wh and the battery power interface IF-21.
The board reads that list as a set of questions. Can the battery pack, rated at 77 Wh, meet 80 Wh? It cannot, so the design follow-up is real work. Does TC-07's last result, 78.3 Wh, still count? Not against the new value. Does 3.3 change? No; the depth-of-discharge limit stays at 30 percent, which is the point of the change, and the record should say it was checked. Does the change reach both products? 3.2 applies to every configuration, so it does; if only EO-1 Flight needed the larger battery, the request could change a configuration value for CFG-1 instead.
The note under the heading states the list's limits: it follows modeled relationships only, and it names the revision it was computed against. Items that quote 77 Wh without a link, such as a power budget table or an operations procedure, will not appear; a search for the value covers them.
Approval and "Needs re-review"
Submit for Review sends CR-2 to the approvers. On the hosted service they get a notice and an entry under My Work → To decide. An approver opens the request, reads the staged changes and their Impact lists, and clicks Approve… or Reject…; a rejection needs a reason.
Because 3.2 is in a baseline, the Approve… dialog also lists the verification items and documents that trace to it under Needs re-review: here TC-07 and SRS-001. That list is the follow-through the approver is committing the team to. A good approval note names it: "Approved. Battery pack change to follow as a separate request; re-run TC-07 on the new pack."
The review card shows Approvals: N of M, and the request becomes Approved when it has enough. On the hosted service each vote asks for the approver's password and records who decided, when, the note and the exact staged changes the vote covers. If someone edits the staged changes after a vote, that vote no longer counts and the approvers are asked again.
Apply, then follow through
An editor or owner opens the approved request and clicks Apply Changes. Both staged changes are applied together as one undo step, and each changed item's history records the change "via CR-2". The request keeps each change's Impact list as it was immediately before applying, as a record of what was considered.
Applying is where the follow-through starts, not where it ends:
- 3.2 was Approved and its text changed, so it moves back to In Review with the note "Text changed after approval". It needs a fresh approval as a requirement.
- Its satisfied by and verified by links are marked for review. Needs & Requirements → Links to Review lists them: the battery pack, F3, F3.2 and TC-07. Diff shows the text change; Mark Reviewed… records the check with a comment. F3 and F3.2 still hold as functions; the battery pack link stays open until the design request is decided, and so does TC-07 until it is re-run.
- The follow-up request for the battery pack is raised with its own reason and impact.
CR-2 is complete when those actions are closed or owned, not when the text of 3.2 changed.
Status accounting and audit evidence
An auditor, or the next review board, asks three questions: what changed, who approved it, and is the record consistent with the model? The model answers each from its own records.
- The change log. Export ▾ on the Change Requests page saves every request as Excel or Word, with its changes and history; the Word export includes the saved Impact lists. Each request's History records who did what and when, including "impact recorded" with the counts.
- Item history. History… in 3.2's Item View lists each version with its author and what changed; the version made by CR-2 says so, and the word diff shows 77 struck out and 80 inserted.
- Baseline comparison. In Control & Reviews → Baselines & Versions, Compare on EO-1 Flight PDR sets it as From and the current model as To. The table lists every item and relationship changed since PDR, with a word diff, and Export XLSX saves it. For the specification alone, Version ▾ → Compare Versions… in SRS-001 compares it with the SRR Baseline and offers Changes (Excel) and Redline (Word).
- A new baseline. Once the follow-up work is done and approved, + Save Baseline… records the new agreed state, for example before CDR. With the Team plan, Baseline a Configuration… records one labelled with a configuration, and Compare can show what one configuration contains.
A functional configuration audit then reads the verification status against the current baseline: TC-07 shows that 3.2 is verified only after the re-run against 80 Wh. A physical audit compares each serial number's battery pack as built with its definition, heater included.
Working in a change request (Team)
Staging changes in dialogs works well for a few precise edits. Larger changes, such as a reworked function flow or a new interface with its diagrams, are easier to make by editing the model directly. Working in a change request allows exactly that: your edits go to a draft request instead of the live model, and the live model changes only when the request is approved and applied. A project owner turns it on in the Change Requests Settings with Work in change requests: edit in a draft and apply after approval; on the hosted service it is part of the Team plan. The demo has it on.
The demo's CR-1 shows the result. Its reason is "Farm customers asked for alerts within 90 minutes of an overpass", and its edits change requirement 6.5 Planning Cycle Time and the measure MOE-7 from 100 to 90 minutes. Opening it under Change Requests shows two tabs:
- Details holds the request, staged changes, review, comments and history.
- Changes compares the model before the request with the model as the request would make it: count tiles, one row per changed item with changed text word by word, the documents that hold a changed item with Compare Versions…, and each changed diagram with Show Before and After.
Preview in Model opens the whole model as it would be after the request, read only, with a banner such as "Previewing CR-1 (read only)." A reviewer can open the RVTM, a matrix or the generated specification and see the change in place, then click Leave. Work in This Change Request enters the draft for editing; a banner names the request and counts its changes, and items it changed carry a CR marker.
A draft can live for days while the live model keeps moving, so Apply Changes first compares the request's edits with the live model as it is now. Changes to different fields of the same item merge without asking. A real conflict, such as the same field changed on both sides, opens Resolve Conflicts, where an approver chooses per item:
- Keep Live: the item stays as the live model has it.
- Use Change Request: the request's value of every field it changed; fields only the live model changed keep their live value.
- Combine: a choice per field between Live and Change request.
Each choice goes into the request's History.
Common mistakes
| Mistake | What goes wrong | Better |
|---|---|---|
| Controlling drafts | Every early edit needs a request, and the team routes around the process. | Control approved and baselined items; let drafts change freely. |
| Baselining late | The design is checked against requirements that were never agreed. | Baseline at each major review, starting with the requirements. |
| Approving without the impact | The board learns the cost after it is committed. | Read the impact list and the re-review list before voting. |
| Changing the requirement but not its evidence | The requirement says 80 Wh while the test threshold still says 77 Wh. | Stage every value that must move in the same request. |
| Closing at apply | Flagged links, re-tests and documents are left for "later". | Close the request when its follow-up actions are done or owned. |
| Records outside the model | The change log, the model and the documents disagree at the audit. | Keep the requests, approvals and baselines with the items they control. |
Frequently asked questions
Is configuration management the same as change control?
No. Change control is one of its five functions. Configuration management also covers identifying what is controlled, establishing baselines, keeping the status records and auditing the product against them. Change control without baselines has nothing to protect.
What does a change control board do?
It decides whether a proposed change to a baseline is approved, rejected or returned, based on the change's reason and its assessed impact, and records the decision with any conditions.
What is the difference between a change request and a change order?
Many organizations split the request (the proposal with its justification and impact, often called an engineering change request) from the order or notice (the instruction to implement an approved change, often called an engineering change order or notice). A model-based tool can keep both in one record.
Does a small team need a change board?
It needs the decision step, not necessarily a meeting. In a two-person project the "board" may be the other engineer, or the owner approving their own request with the reason and impact written down. What matters is that agreed items change only by a recorded decision.
How does configuration management work with product variants?
Each variant is a configuration of a shared model, and each change states its effectivity: which configurations and serial numbers it applies to. Baselines can be labelled per configuration, and a change request shows which configurations it changes. The product-line method itself is a topic of its own.
Try it in Holarch
- Create the demo with Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering).
- Open Control & Reviews → Change Requests, click Settings and tick Changes to approved and baselined items require a change request. Then try to edit 3.2 Battery Capacity directly and read why it is refused.
- Click + New Change Request, enter a title and reason, untick Work in it now if it is shown, and click Create. Add 3.2 with Add Item…, then stage its new description with Add Change ▾ → Change an Item… and TC-07's Expected Result the same way.
- Open the Impact list under each staged change and sort its rows into "changes", "check only" and "no impact".
- Click Submit for Review, then Approve… and read the Needs re-review list. Apply with Apply Changes.
- Open Needs & Requirements → Links to Review and review the links from 3.2. Open History… in 3.2's Item View to see "via CR-2".
- In Control & Reviews → Baselines & Versions, click Compare on EO-1 Flight PDR and export the differences. Export the change request log with Export ▾.
- With the Team plan, open CR-1 Shorten the planning cycle, read its Changes tab and click Preview in Model.
The full reference is in Change Requests (including Impact and working in a change request), Links to Review, baselines and version comparison, history and revert and baselines and change requests in a product line.
Where to go next
- Change impact analysis: the method for sizing a change before the board decides, and for resolving suspect links after.
- Requirements traceability: the links that impact lists and suspect links are computed from.
- Interface change control: how interface changes go through the same loop.
- Deviations and waivers: recording departures from a requirement without changing it.
- Working together in one model: roles, reviews and change requests for teams.