Holarch

Control & Reviews

Product Lines and Configurations

Model several products in one project with features and configurations, say which items apply to which products with Applies To and effectivity, view and edit the model as one configuration, and generate documents, RVTMs and baselines per configuration.

How to use it →

On this page
  1. Overview
  2. Concepts
    1. Features
    2. Configurations
    3. Verdicts
    4. Completeness
    5. Completeness per stage
    6. Releasing a configuration
    7. Releasing through a change request
    8. The released definition
    9. Applies To and effectivity
    10. Shared identity and configuration values
    11. The 150 % view
  3. How to use it
    1. When and why
    2. Start a product line
    3. Create a configuration
    4. Say which items belong to which products
    5. View and edit one configuration
    6. Give a configuration its own value
    7. Generate a specification for one configuration
    8. Worked example: the CubeSat EO-1 demo
    9. Tips and good practice
    10. Common mistakes
    11. How it connects to other features
  4. The Product Line page
    1. Page header
    2. Features
    3. Configurations
    4. Empty states
    5. Keyboard
    6. Screen readers
  5. Applies To
    1. The field
    2. The Choose… dialog
    3. The Applies To expression
    4. Expression messages
  6. View as Configuration
    1. The menu
    2. The banner
    3. What each page shows
    4. Screen readers
  7. Editing in a configuration view
    1. Create and change items
    2. Remove and delete
    3. Add an existing item
    4. What is not available in a view
    5. Released and retired configurations keep their values
    6. Undo and history
    7. Working with others
  8. Configuration values
    1. Which fields can differ
    2. In a configuration view
    3. In All configurations
  9. Effectivity
    1. Fields
    2. View at a serial number or date
    3. Effectivity messages
    4. Revisions of an item
  10. Documents, RVTM and verification
    1. Export a document for one configuration
    2. The document outline
    3. RVTM
    4. Test Center
    5. Diagrams and trade studies
  11. Baselines and change requests
    1. Baselines per configuration
    2. Change requests
  12. Model Checks
  13. Search, import and export
  14. REST API and MCP
  15. Plans
  16. SysML v2 projects
  17. Limits
  18. Related pages

Overview

A product line is a family of products that share most of one design. Model the shared design once, mark where the products differ, and define each product as a configuration. Every page can then show the model as one configuration, and every change to the shared design reaches every product.

You work with product lines in these places:

  • Control & Reviews → Product Line: the features, their rules, and the configurations built from them.
  • The inspector's Product Line group: Applies To and effectivity for the selected item.
  • View as ▾ in the top bar: show and edit the model as one configuration.
  • Documents, the RVTM, the Test Center, Baselines & Versions and Change Requests: output and control per configuration.

Product lines are part of the Individual and Team plans. Baselines per configuration, configuration owners and the configurations a change request affects are part of the Team plan. See Plans.

Concepts

Features

A feature is a choice that differs between products, such as "X-band Downlink" or "Propulsion". Features form a tree: a parent feature groups related choices.

Each feature has:

  • Kind: Mandatory (every configuration that has the parent has it too) or Optional (chosen per configuration). New features are Optional.
  • Children: the rule over its child features. Any number (choose freely), Choose one (exactly one child per configuration) or Choose at least one (one or more). New features have Any number.
  • Rules: a feature requires another feature, or excludes it. Excludes works both ways.
  • Constraint: an optional rule that must hold in any configuration that selects the feature, written like Applies To.

Configurations

A configuration is one product: a selection of features. Each configuration has:

  • A number and a name, such as CFG-2 EO-1 Lite.
  • Status: Draft, Released or Retired. New configurations are Draft, and so is a copy of a Released configuration (Duplicate, copy and paste, import into an open project): it has no release record of its own. A retired configuration can be viewed but not edited. A configuration is released with Release Configuration… (see Releasing a configuration).
  • Stage (optional): the lifecycle stage it is in, such as Preliminary design or CDR. The stage decides which completeness rules apply.
  • Owner (optional, Team plan): the person or team who must approve change requests that change it.
  • Effectivity (optional): the serial numbers or build dates of the units built to it.

A configuration's effective selection is more than the features you tick:

  • the selected features;
  • their parent features, up to the root;
  • the Mandatory children of every selected feature;
  • the Mandatory features at the root of the tree.

Verdicts

Holarch checks every configuration against the feature rules and shows a verdict:

  • Valid: the selection follows every rule.
  • Breaks: …: a rule is broken, for example "Breaks: Encrypted Downlink requires X-band Downlink."
  • Incomplete: …: a choice is missing, for example "Incomplete: choose a Downlink (choose one)."

When several rules fail, the verdict names the first one in this order: a Mandatory feature that another selected feature excludes, a Choose one group with no choice or more than one, a Choose at least one group with no choice, an unmet requires, a broken excludes, a false Constraint.

Completeness

A Valid verdict covers the feature rules only. Completeness checks the items a configuration contains:

  • every leaf requirement in it is verified by an item in it (a test case that applies to it);
  • every connection (Conduit) in it has both ends in it, and every relationship with its own Applies To has both ends in the configurations it applies to;
  • every item in it has its parent in it.

Each configuration reads Complete or the number of gaps, such as "3 gaps". Retired configurations are not checked. Completeness ignores effectivity: an item belongs to a configuration when it applies to it.

Completeness per stage

A configuration's Stage chooses how much is checked. Each stage uses one of five levels:

LevelDefault stageChecks
1ConceptEvery item's parent is in the configuration.
2Preliminary designLevel 1, every connection has both ends in it, and every leaf requirement is satisfied by an item in it.
3Detailed designLevel 2, and every leaf requirement is verified by an item in it.
4TestLevel 3, every verifying test case has a procedure (a description or test steps) and a result for this configuration.
5ProductionLevel 4, every verifying test case Passed for this configuration, and no open issue is linked to its items.

With an SE Process, the Stage list holds its review gates instead (SRR, PDR, CDR, TRR and so on), each with a level: SRR is 1, PDR 2, CDR 3, TRR 4, and production and operational reviews 5. Without a Stage, completeness uses the rules above under Completeness (requirements verified, connection ends, parents).

To change the level of a stage, open the Product Line page's ⋯ → Settings… and choose a level under Stages. A single Undo takes the change back.

The Completeness row shows model completeness and verification separately, for example "Complete at CDR · 12/40 verified": the first part is the check for the stage, the second the requirements with a Passed result in this configuration. Verification is shown from level 3 on and without a Stage.

Releasing a configuration

A configuration is released with Release Configuration…: on the Product Line page, open the configuration's column ⋯, or press ⌘K / Ctrl+K and type "Release". Setting Status to Released in the inspector or the Database opens the same dialog.

The dialog shows:

  • Stage: the stage the release is for. Completeness is checked for it.
  • Feature rules and Revisions: a configuration that breaks a rule, or has two revisions in effect together, cannot be released: "CFG-2 cannot be Released. Breaks: Wallbox requires Large pack. Change its selection on the Product Line page first."
  • Completeness at the stage, with Show gaps, and Verification (how many requirements are verified in it).
  • Open high risks, only at a stage of completeness level 5 (Production): the risks and hazards in the configuration that are open at a high level (the residual level where one is set), for example "Risk RSK-1 Battery fire: High, Open". It is a warning: it does not block the release and needs no reason. A Risk counts while its Status is Open and it is not an Opportunity; a Hazard counts until it is Accepted or Closed.
  • Release condition, only while the configuration is not complete: a Reason (10 to 2,000 characters) and the Approver. Release stays disabled until both are given.

Click Release. The configuration's Status becomes Released, and Holarch keeps a release record: the stage, the completeness and verification at release, the accepted gaps, the reason and approver, and the released definition (see below). A single Undo takes back both the release and its record.

Completeness and verification are recorded as Holarch computed them in your browser at release. Holarch online checks that the released definition matches its SHA-256 digest and refuses a release whose file does not; it does not check completeness again yet.

Who approves:

  • Desktop app: type the approver's name. It is recorded as entered by name; this copy of Holarch has no accounts.
  • Holarch online, Individual plan: you approve your own release; the server records your account and the time.
  • Holarch online, Team plan: the configuration's Owner approves, or a project owner when it has none. An incomplete release waits as Pending approval until the approver opens Release Configuration… on it and clicks Approve Release (Holarch asks for their password). You approve your own request only when the project allows self-approval (Change Requests → Settings). A complete release needs no approval.

The server refuses a Status change to Released that does not come with a release record, so an API client or an older page cannot skip the dialog. It also refuses a project save that removes or changes a release record, also from a project owner.

Withdraw Release… (column ⋯, or setting Status back to Draft or Retired) asks for a reason. The release record stays and its log gets the withdrawal; a release record is never deleted. Releasing again makes release 2.

Record Release… (column ⋯) is offered for a configuration that was Released before release records existed. It records the configuration's state today as its release, marked "recorded later".

  • Setting Status on several configurations at once (Database → Attributes…) names the ones that break a rule, which stay Draft, and opens Release Configuration… for each of the others, one after the other.
  • Withdraw a release in the live model, not in a change request. To release a configuration through a change request, stage the release (see Releasing through a change request). A change request that only sets a configuration's Status to Released does not release it when it is applied; the configuration keeps its Status and the rest of the change request applies.
  • An AI or MCP proposal cannot release a configuration: its review says "Needs a release record" and offers Release Configuration…; applying the proposal applies its other changes.

Releasing configurations of SysML v2 projects is not available yet.

Releasing through a change request

A release can be part of a change request, so the board that approves the changes also approves the release. While you work in a change request (or have it open), stage the release:

  • On the change request, Add Change ▾ → Release a Configuration…, then choose the configuration.
  • On the Product Line page, the configuration's column ⋯ → Release with CR-12….
  • In the inspector or the Database, set Status to Released.

The dialog is the same, titled "Release CFG-2 with CR-12". It checks completeness at the chosen stage, and lists open high risks at level 5, against the model as the change request would leave it, and warns when the stage reports less than the last release or leaves gaps at the next stage. While the configuration is not complete, enter the Reason; the request's approvers take the place of the Approver. Click Add to CR-12: the release is staged as one change ("Release CFG-2 at CDR"), the configuration stays Draft until then (its column's Status chip says "Release staged in CR-12"), and the configuration counts as affected by the request, so its Owner's approval is needed where approval rules apply.

When the approved request is applied, Holarch releases the configuration and keeps its release record, with the stage, reason and accepted gaps as staged, and the request's approvers and via CR-12. A single Undo takes back both the applied request and the release. Holarch does not release a configuration when, at apply, it was deleted or retired, is already released or waits for approval, breaks a feature rule, or has gaps the request did not accept. The rest of the request still applies, and the request's log and the result say why. Stage the release again after fixing it.

Holarch online records the approvals from the request's votes (accounts and times from the server), never from names typed in the page. An incomplete release approved by the request needs no separate Approve Release. Only the person who applies the request can record its releases, within an hour of the approval check; a project save or an API client cannot add a release through a change request.

The released definition

Each release record keeps the configuration as released: its items and relationships with their values, the selection, the library features and configurations it used, the linked items in other projects as read at release, and the verification results. It is stored in the project as a compressed file with a SHA-256 digest.

On Baselines & Versions, the Releases card lists every release with its configuration, stage, completeness, approver, date and state. Its ⋯ menu offers:

  • Open Released Definition: the released items with their values as released (for example a configuration's own Mass), read only.
  • Verify: checks that the record matches its digest (intact) and rebuilds the configuration from the record's own inputs (reproduced exactly): its snapshot, the library features and configurations it froze, and the schema it resolved with. Later edits, new library releases, changed linked items and renamed classes, attributes or relationships do not change the result.
  • Compare with Today: what the configuration shows now compared with the release, including libraries that moved to another release (named with their release labels) and linked items that changed since.
  • Export (JSON): the record with its definition.
  • Withdraw…

Applies To and effectivity

Two fields on any item or relationship say which products it belongs to:

  • Applies To says which configurations include the item. It is an expression of features and configurations, such as F-4 and not F-5. Empty means every configuration.
  • Effectivity says from which unit or date the item is in effect: serial numbers such as 1-20, 25, 40-, a date range, or both. Empty means always.

The two are independent and combine: an item is in a view when it applies to the configuration and is in effect at the view's serial number or date.

Shared identity and configuration values

An item is one item in every configuration. Its Name, Number, Class, Labels and Assignee are the same everywhere, and so are its place in hierarchies, document order and diagram layout.

Its Description and its attribute values can differ. A configuration value is an item's own value for one configuration, such as a Daily Data Volume of 1 GB in EO-1 Lite while the other configurations keep 3 GB. A configuration without its own value uses the item's base value.

The 150 % view

All configurations (no configuration chosen) shows the whole product line: every item of every product, with base values. Fields that differ by configuration are marked Varies. This is the view in which you renumber, restore baselines and delete items everywhere.

How to use it

When and why

Use a product line when several products share most of their requirements, functions and architecture: a flight unit and a lighter variant, export versions, customer options, block upgrades. One model keeps the shared parts in step. Each configuration still gets its own specification, RVTM and baselines.

A good order of work:

  1. Model the shared design as usual.
  2. List the points where products differ as features, with their rules.
  3. Add one configuration per product and check that each is valid.
  4. Mark the items that only some products have with Applies To, and the values that differ with configuration values.
  5. Generate documents and verify each configuration.

If your products differ in nothing but build dates or serial numbers, create a single configuration (for example "Production") and use effectivity only.

Start a product line

  1. Press ⌘K / Ctrl+K and choose Start a Product Line…: it opens the page and the New Feature dialog. Or create a Feature or Configuration item with + New Item in the Database. You see Control & Reviews → Product Line in the navigation rail, and a Product Line group in the inspector of every item.
  2. On the Product Line page, click + New Feature and type the feature's name, such as "Downlink". Press Enter. The name is saved and a new sibling row starts.
  3. Type the next feature's name. To make it a child of the row above, press ⌥⇧→ / Alt+Shift+→. ⌥⇧← / Alt+Shift+← moves it back out.
  4. Set each feature's Kind and Children in the inspector (press Enter on its row).
  5. Add rules from the row's ⋯ menu: Rules… for requires and excludes, Constraint… for a constraint.

The Product Line page, the inspector group and the Applies To column stay hidden until a project has its first Feature or Configuration. They hide again when the last one is deleted, except on items that still hold an Applies To or effectivity value.

Create a configuration

  1. On the Product Line page, click + New Configuration. Type a name, such as "EO-1 Lite". A new column appears in Configurations.
  2. Tick the features this product has. For a Choose one group the cells are radio buttons: choosing one replaces the other. Cells marked as implied are included because of another feature (a parent or a Mandatory child); they cannot be changed.
  3. Read the Verdict row under the column. Fix the selection until it reads Valid.
  4. Read the Completeness row. Point at a gap count to see the gaps.
  5. Click Check Configurations to check every configuration at once.

To start from an existing product, open the configuration's column header ⋯ menu and choose Duplicate. The copy has the same selection and the same configuration values.

Say which items belong to which products

  1. Select an item, such as a requirement, and open the inspector's Product Line group.
  2. In Applies To, type a feature or configuration number, such as F-4. Pick from the suggestion list with ↓ and Enter. The line under the field reads, for example, "Applies to 1 of 2 configurations: CFG-1".
  3. Combine terms with and, or, not and parentheses: F-3 and not F-5.
  4. Or click Choose… and pick configurations or features from a list.

Leave Applies To empty for items every product has. Most items stay empty.

View and edit one configuration

  1. Click View as ▾ in the top bar and choose a configuration. You see a banner: "Viewing configuration CFG-2 EO-1 Lite. New items apply to CFG-2 only; changed values become CFG-2's." Every page now shows only the items of CFG-2, with CFG-2's values.
  2. Work as usual. New items apply to CFG-2. A changed description or attribute becomes CFG-2's own value when other configurations have the item too.
  3. Click Leave in the banner to see all configurations again.

The choice belongs to the browser tab. Other people and other tabs keep their own view. See Editing in a configuration view for every rule.

Give a configuration its own value

  1. Choose the configuration in View as ▾.
  2. Select the item and change the attribute in the inspector. While you edit, the hint under the field reads, for example, "Saved for CFG-2 only. Other configurations keep 3 GB." After the change the field shows a CFG-2 value chip.
  3. To undo the difference, open the chip's menu and choose Use Base Value.

Generate a specification for one configuration

  1. Open the document, click Deliver ▾ and choose a Word template, such as Specification (Word). You see the Export to Word dialog.
  2. Set Configuration to the product, and Effectivity to Any unit, a Serial number or a Date.
  3. Export the document. The document leaves out sections that do not apply, numbers the rest as shown, and names the configuration on the title page, in the footer and in the file name.

Worked example: the CubeSat EO-1 demo

The CubeSat EO-1 demo project has two products: EO-1 Flight, with an X-band downlink and encryption, and EO-1 Lite, with the S-band downlink. Create the demo with Project Files ▾ → New Demo Project on Manage Projects.

  1. Open Control & Reviews → Product Line. You see the features Downlink (Mandatory, Choose one) with S-band Downlink and X-band Downlink, Encrypted Downlink (Optional, requires X-band Downlink) and Propulsion (Optional, requires X-band Downlink).
  2. Look at the configurations CFG-1 EO-1 Flight (X-band and Encrypted Downlink, serial numbers 1–2) and CFG-2 EO-1 Lite (S-band, serial numbers 3 and later). Both verdicts read Valid.
  3. In the CFG-2 column, tick Encrypted Downlink. The verdict changes to "Breaks: Encrypted Downlink requires X-band Downlink." Press ⌘Z / Ctrl+Z.
  4. Open the requirement 4.4 Downlink Encryption. Its Applies To is the Encrypted Downlink feature (F-4), so it is only in EO-1 Flight. 1.5.2 S-band Transmitter, its interfaces IF-08 and IF-12, and 5.1 S-band Downlink Rate apply to F-2; 1.5.3 X-band Payload Radio, its interfaces IF-08.1 and IF-12.1, 5.5 X-band Downlink Rate and its test case TC-21 X-band Link Test apply to F-3.
  5. Choose View as ▾ → CFG-2 EO-1 Lite and open the requirement 5.4 Daily Data Volume. Its description reads "at least 1 GB" with a CFG-2 value chip. In EO-1 Flight it keeps the base text, "at least 3 GB".
  6. Open the test case TC-11 UHF Command Test. It holds one result per configuration: Passed in EO-1 Flight, In Progress in EO-1 Lite.
  7. Open 1.3.2 Battery Pack and look at its characteristics Thermostat Heater Power (2 W, effectivity SN 1) and Software-Controlled Heater Power (3 W, SN 2 and later): the heater changed from the second spacecraft on.
  8. Open Control & Reviews → Baselines & Versions. EO-1 Flight PDR is a baseline of CFG-1 (Team plan).
  9. Open Verification → Model Checks in All configurations. The Product line rules warn that Propulsion is selected by no configuration (ProductLine.4). The demo leaves it unselected on purpose, as the example of that check.

Tips and good practice

  • Keep features about the product, not about documents: "X-band Downlink", not "Section 5 option".
  • Prefer feature terms in Applies To. F-3 stays right when you add a third product with an X-band downlink; CFG-1 does not.
  • Group many related options under a parent feature instead of writing long expressions.
  • Give configuration values only to values that really differ. Everything else stays shared.
  • Use Released for configurations under control, and Retired for products no longer built.
  • Model a part change from a serial number on as two items, the old and the new one, each with its own effectivity.

Common mistakes

  • An item disappears from a view after an edit. Its Applies To or effectivity no longer includes the configuration. The toast names it; click Undo, or find it in All configurations.
  • A configuration stays Incomplete. A Choose one or Choose at least one group has no choice. Tick a child of that group.
  • An item is in no configuration. Its Applies To names features no configuration selects. Model Checks reports it (ProductLine.2).
  • A move changes every product. Structure is shared: moving or re-ordering an item in a configuration view moves it in all configurations.

How it connects to other features

  • Documents: generate per configuration and serial number or date.
  • RVTM and Test Center: record results per configuration; "verified" means verified for that product.
  • Model Checks: the Product line rule set checks expressions, verdicts, effectivity and revisions (supersedes).
  • Baselines & Versions (Team): baseline one configuration and compare configurations.
  • Change Requests (Team): see which configurations a request changes; owners approve.
  • Search: appliesto:CFG-2 and varies:yes find items by configuration.
  • REST API and MCP: read the model as one configuration.

The Product Line page

Control & Reviews → Product Line shows the features on the left and the configurations on the right. Under 1,100 px wide the two regions are stacked.

ControlWhat it does
+ New FeatureAdds a feature with the next number (F-1, F-2, …) at the end of the tree.
Check ConfigurationsLists every configuration with Valid or its first problem, and Complete or its gaps.
+ New ConfigurationAdds a configuration column with the next number (CFG-1, CFG-2, …).
⋯Export CSV (features by configurations, with Selected or Implied and the verdicts) and Help.

Features

A tree grid with the columns Feature (number and name), Kind, Children and Used by (how many items name the feature in Applies To). Rules show as small tags in the row, such as "requires F-3".

Set a feature's Kind and Children in the inspector: press Enter on the row to open it there.

Row ⋯ menu:

  • Add Child Feature…
  • Rename (F2)
  • Rules…: Requires and Excludes checklists
  • Constraint…: an Applies To expression that must hold when the feature is selected
  • Show Items Using It
  • Delete…

Configurations

A grid with one row per feature (in tree order) and one column per configuration. Each column header shows the number, name and Status, and the owner on the Team plan.

Cells:

  • A checkbox for features you choose freely.
  • A radio button for the children of a Choose one feature.
  • An implied mark for features included by another one. The tooltip names it, for example "Included because F-1 is selected."

The Verdict row at the bottom shows Valid or the first problem (the feature rules). The Completeness row under it shows Complete or the number of gaps; its tooltip lists them (see Completeness).

Column header ⋯ menu:

  • View as This Configuration
  • Rename…
  • Effectivity…
  • Owner… (Team): opens the configuration in the inspector.
  • Baseline CFG-2… (Team): saves a baseline of this configuration (see Baselines per configuration).
  • Duplicate: copies the selection and every configuration value, and a single Undo takes it all back. The copy is a Draft named "<name> (copy)".
  • Retire, or Restore to Draft on a retired configuration. A retired configuration's view is read-only.
  • Delete…: moves the configuration to the Trash. Items keep its values, so Restore brings it back intact.

Empty states

  • No features: "No features yet. Add the first feature: a choice that differs between products."
  • No configurations: "No configurations yet. A configuration is one product: a selection of features."

Keyboard

KeysWhereWhat they do
TabPageMoves between the header actions and the two grids. It never indents.
Home / EndFeaturesFirst or last row.
↑ / ↓FeaturesPrevious or next row.
← / →FeaturesCollapse or expand.
EnterFeaturesWhile naming: saves the name and starts a new sibling below. On a selected row: opens the feature in the inspector.
F2FeaturesRenames the feature in place. Esc, or leaving the name empty, adds nothing.
⌥ / Alt+↑ / ⌥ / Alt+↓FeaturesMoves the feature up or down among its siblings (the two features swap numbers).
⌥⇧→ / Alt+Shift+→ / ⌥⇧← / Alt+Shift+←FeaturesIndents or outdents the feature, as in the document outline.
DeleteFeaturesDeletes the feature, after a confirmation.
Arrow keysConfigurationsMove from cell to cell.
SpaceConfigurationsTicks or clears the cell.
EnterConfigurationsOn a column header: opens its menu.
Home / EndConfigurationsFirst or last column.

Screen readers

The features are a tree grid named "Features". The configurations are a grid named "Configurations by feature"; each cell reads, for example, "F-3 X-band Downlink in CFG-1 EO-1 Flight: selected". Changes are announced: "X-band Downlink selected for CFG-1.", "CFG-2 breaks a rule: Encrypted Downlink requires X-band Downlink.", "CFG-2 is valid."

Applies To

Applies To says which configurations include an item. It is in the inspector's Product Line group (after the attribute groups), in the Item View, and as a Database column. Not yet: editing a relationship's Applies To in the relationship panel.

The field

  • Applies To: the expression. Empty shows "All configurations".
  • Choose…: pick configurations or features from a list instead of typing.
  • The preview line under it: "Applies to 2 of 4 configurations: CFG-1, CFG-3" or "Applies to every configuration".
  • When a configuration view has added or removed the item, chips such as Removed from CFG-2 and Added to CFG-4. Click ✕ on one to clear it: the item follows Applies To again for that configuration.
  • A warning when the expression names a deleted feature or configuration (shown by its old number).

Feature and Configuration items have no Applies To.

In the Database, the Applies To column appears once any item uses Applies To (hide it from its ▾, add it back from Columns). Double-click a cell, or press Enter or F2, to edit it with the same field.

Typing opens a list of matching features and configurations, then the operators. ↓/↑ move, Enter or Tab inserts, Esc closes the list, a second Esc reverts the field. Enter saves; leaving the field saves when the expression is valid.

The Choose… dialog

Applies To — <item> offers three choices:

  • Every configuration: clears the expression.
  • These configurations: tick configurations; writes CFG-1 or CFG-3.
  • Features: tick features and choose All (writes F-2 and F-5) or Any (writes F-2 or F-5).

The resulting expression shows below. Edit as Expression puts it in the text field without saving it. Apply saves it, and a single Undo takes it all back.

The Applies To expression

You typeMeans
F-3 or "X-band Downlink"A feature, by number or by name in quotes. True when the configuration's effective selection contains it.
CFG-2 or config "EO-1 Lite"A configuration. True for that configuration only.
and, or, not, ( )Combine terms. &, | and ! work too and are shown as words. not binds first, then and, then or.
all, noneEvery configuration, or none.

Case does not matter. Holarch stores the expression with the items' ids, so renaming or renumbering a feature never breaks it. It shows numbers, or the name in quotes for an item without a number.

A deleted or unknown feature is false, and Model Checks reports it as an error.

Expression messages

An invalid expression is never saved. The field keeps your text, marks the error, and the last valid value stays in effect. Positions count characters from 1.

MessageWhat to do
No feature or configuration named “F-9”. Choose one from the list, or create the feature first.Check the number, or create the feature.
Expected a feature or configuration after “and” (character 12).Add a term after the operator.
Expected a feature or configuration at character 1.Start with a term, not or (.
Expected “and” or “or” before “F-5” (character 9).Join the two terms with an operator.
Missing “)” for the “(” at character 5.Close the parenthesis.
“)” at character 9 has no matching “(”.Remove the extra parenthesis.
Missing closing quote for the name at character 4.Close the quoted name.
“Wallbox” matches 2 features (F-3, F-11). Use the number.Two features share the name; type the number.
Applies To is too long. Use at most 200 features and configurations; group them with a parent feature instead.Shorten the expression.

View as Configuration

View as ▾ shows the whole model as one configuration. It is in the top bar, left of the save status, once the project has a configuration.

The menu

  • All configurations: the whole product line.
  • One entry per configuration, with its Status and a mark when it breaks a rule or is incomplete.
  • Effectivity ▸: Any unit, Serial Number…, Date… or Serial Number and Date…. See View at a serial number or date.
  • Manage Product Line: opens the Product Line page.

The menu opens with Enter, Space or ↓; arrow keys move, Enter chooses and Esc closes. ⌘K / Ctrl+K has View as Configuration…, View All Configurations, Set Effectivity…, Go to Product Line, New Feature…, New Configuration… and, in a view, Add Existing to CFG-2….

The banner

While a configuration is chosen, a banner under the top bar reads, for example, "Viewing configuration CFG-2 EO-1 Lite at SN 23. New items apply to CFG-2 only; changed values become CFG-2's." It shows how many items are in the view ("1,204 of 1,350 items") and has:

  • Change ▾: the same menu as View as ▾.
  • Leave: back to All configurations.

When you also work in a change request, the change request's banner comes first and the configuration's second.

What each page shows

  • Items and relationships that do not apply to the configuration, or are not in effect at the view's point, are left out.
  • Items with configuration values show those values.
  • Counts, rollups, budgets, simulation, quality scores and Model Checks are computed for the configuration.
  • Document outlines, generated documents and the RVTM number the items as shown. Stored numbers do not change; exports state "Numbering as shown in CFG-2."
  • Search and queries run on the view.

The choice belongs to the browser tab and is kept when you reload it. Switching views is not an edit, so Undo skips it.

Screen readers

The button reads "View as: CFG-2 EO-1 Lite". The banner is a region named "Configuration view". Entering, leaving and changing the point are announced, for example "Viewing configuration CFG-2 EO-1 Lite. 1,204 of 1,350 items apply." and "Viewing all configurations."

Editing in a configuration view

You edit in a configuration view as everywhere else. Holarch turns each edit into a change of the whole product line, so the other configurations keep what they had. Each action can be undone with a single Undo.

Create and change items

You doWhat happens
Create an item (any way: + New, a diagram, a document, a Database row, paste, duplicate, a template, an import, an applied AI or MCP proposal)The item applies to this configuration only. With only one configuration, Applies To stays empty.
Duplicate, or Copy with ChildrenEach copy applies to this configuration and takes the values shown as its base values.
Change Name, Number, Class or LabelsChanges them for every configuration. The field shows a Shared icon; the change is announced as, for example, "Name changed for all configurations."
Change the Description or an attribute of an item other configurations haveSaved as this configuration's own value. A value equal to the base value removes the own value. Retired configurations count as other configurations, so they keep their values.
Change the Description or an attribute of an item only this configuration hasSaved as the base value.
Change Applies To or effectivityChanges them for every configuration. The fields show a Shared icon, and while you edit, the hint reads "Changes Applies To for every configuration, not only CFG-2." When the item no longer belongs in the view, it leaves it: "R-4.2 no longer applies to CFG-2." with Undo.
Add a relationshipAdded to the product line. It is limited to this configuration when its two ends are also together in another configuration.
Change a relationship's attributeAs for an item's attribute.
Move, re-order, indent, outdent or re-parentChanges the shared structure for every configuration: "Moved for all configurations."
Change diagram layoutShared by every configuration.
Record a test resultSaved as this configuration's result, also when no other configuration has the test case. Run Suite says "Recording results for CFG-2."
Edit the schema, project settings, sharing or library subscriptionsShared, as in All configurations.

Remove and delete

You doWhat happens
Delete an item other configurations haveA confirmation asks, for example, "Remove R-4.2 from CFG-2? It stays in CFG-1 and CFG-3." Remove from CFG-2 takes it out of this configuration only; Delete Everywhere… deletes it to the Trash.
Remove such an item that has childrenAlso remove its 3 children from CFG-2 (on by default). Off: the children stay in the configuration and show at the next level up.
Delete an item only this configuration hasDeleted to the Trash, as usual.
Remove a relationship other configurations haveRemoved from this configuration only: "Removed the link from CFG-2. It stays in 2 other configurations."
Remove a relationship only this configuration hasDeleted, as usual.
Remove from DiagramRemoves the item's relationship to the diagram for this configuration. On diagrams that only list their shapes, the dialog says "Removes the shape from this diagram in every configuration."
Restore from TrashRestores the item to the product line. If it does not apply to the configuration: "Restored R-4.2. It does not apply to CFG-2."

When an edit takes the selected item out of the view, focus moves to the next item in the same list and the toast says where the item went.

Add an existing item

The pickers for adding an existing item to a diagram, document or relationship list the items in the view. To bring in an item that does not apply to the configuration, use Add Existing to CFG-2… in ⌘K / Ctrl+K or the banner's Change ▾ menu: "Added Battery to CFG-2."

What is not available in a view

  • Renumber…, Renumber from Here… and Renumber children…: numbers are shared by all configurations. Renumber in All configurations.
  • Restore Baseline and Restore Earlier Version: "Leave the configuration view to restore a baseline."
  • Every edit in a Retired configuration: "CFG-1 is retired. Copy it to make changes." A Released configuration stays editable unless configuration control locks it.

Released and retired configurations keep their values

An edit elsewhere never changes what a Retired configuration shows, and changes a Released configuration only through a change request. When you change an item's base value (in All configurations, with Make This the Base Value, or by an import or an applied AI or MCP proposal), each Retired configuration, and each Released one outside a change request, that has the item and no own value gets the old value as its own value as part of the same change. A base value that was empty is not kept.

Locked, library-mounted and controlled items keep their usual rules for configuration values too.

Undo and history

  • Undo works across view switches. When the step was made in another view, the toast names it: "Undid a change made in CFG-2: Mass of Battery."
  • History shows "In CFG-2" next to each change made in that view.

Working with others

Two people in different configurations never overwrite each other's values or removals. A base edit and a configuration value never clash. Two people changing the same field for the same configuration: the later change wins, as for any field.

When someone deletes the configuration you are viewing, your tab returns to All configurations: "CFG-2 was deleted. Showing all configurations."

Configuration values

A configuration value is an item's own Description or attribute value for one configuration.

Which fields can differ

FieldCan differ by configuration
Description, every attribute, relationship attributesYes
Name, Number, Class, Labels, AssigneeNo: they identify the item
Applies To, effectivity, Feature and Configuration attributes, selects, requires, excludesNo: they define the configurations
Attributes with an approval workflow (such as Requirement Status under approvals)No: one approval record per item
Quality results, review data and computed valuesNo: computed for each view
Diagram layout and document settingsNo

In a configuration view

  • A field with this configuration's own value shows the chip CFG-2 value. Its menu:
    • Use Base Value (3 GB): removes the own value.
    • Make This the Base Value: makes this value the base; other configurations' own values stay.
    • Values in All Configurations…
  • A field that never differs shows a Shared icon ("Shared by all configurations.").
  • While you edit a field of an item other configurations have, the hint reads "Saved for CFG-2 only. Other configurations keep 3 GB."

In All configurations

A field with own values shows Varies (2). Its menu has Values in All Configurations… and Clear Configuration Values.

While you edit a field that can differ, the hint says which configurations the change reaches, for example "Changes CFG-2 and CFG-3. CFG-1 (Released) keeps 1,400. CFG-4 keeps its own value."

Values in All Configurations… lists the Base value first, then each configuration with its Value and Source ("own value" or "base"). Edit a row in place and press Enter to save it.

In the Database, a cell with an own value has a corner mark. History, change lists and comparisons name a configuration value as, for example, "Mass (CFG-2)", and a membership change as "In CFG-2".

Effectivity

Effectivity says from which unit or build date an item, relationship or configuration is in effect. The effectivity fields appear once the project has a configuration.

Fields

In the inspector's Product Line group, under Applies To, and in a configuration's Effectivity… dialog:

  • Serial Numbers: a list such as 1-20, 25, 40-. 40- means 40 and later. Leave empty for every unit.
  • Effective From: the first build date it applies to (YYYY-MM-DD).
  • Until (not including): the first build date it no longer applies to.

A summary under the fields reads, for example, "In effect for SN 1–20 and 25, and SN 40 on." Tags elsewhere read "SN 1–20, 25, 40– · From 2027-03-01". With serial numbers and dates both set, both must hold.

Serial numbers are stored sorted and merged. Up to 200 ranges, numbers up to 1,000,000,000,000. Not yet: a project serial prefix, for typing numbers such as SN-0021.

A configuration's effectivity names the units built to it. It does not filter that configuration's items.

View at a serial number or date

  1. Choose View as ▾ → Effectivity ▸ → Serial Number… (or Date…, or Serial Number and Date…), or ⌘K / Ctrl+K Set Effectivity….
  2. Enter the serial number, the build date or both. The banner adds the point: "Viewing configuration CFG-3 Block 2 at SN 23."

A serial number and a build date together describe one unit: "SN 75 built 2027-06-15". An item is then shown when both hold, each where the item sets it. Serial Number… keeps a date already chosen and Date… keeps a serial number; Any unit clears both. Documents (Serial number and date in the Export dialog), the RVTM and the API (effectivity=sn:75,date:2027-06-15) take the same point.

Item hasView at a serial numberView at a date
Serial numbers onlyShown when the number is in its listShown, with its tag
Dates onlyShown, with its tagShown when the date is in its range
BothShown when the number is in its listShown when the date is in its range
NeitherShownShown

Choosing a serial number with All configurations picks the configuration whose serial numbers contain it. When several do, the menu lists them ("SN 23 is in CFG-2 and CFG-3. Choose one."). When the point is outside the chosen configuration's own effectivity, the banner warns: "SN 23 is outside CFG-2's effectivity (SN 1–20)."

Effectivity messages

MessageWhat to do
“x” is not a serial number or range. Use numbers and ranges such as 1-20, 25, 40-.Fix the part named.
The range “20-1” goes backwards. Write the lower number first.Swap the numbers.
Use at most 200 serial ranges.Merge ranges.
Serial numbers go up to 1000000000000.Use a smaller number.
“x” is not a date. Use YYYY-MM-DD.Fix the date.
Effective Until must be after Effective From.Change one of the dates.
Write serial numbers as ranges such as 1-20, 25, 40-.Shown under the field; fix the ranges.
Until must be after From.Shown under the field; change one of the dates.
SN 12–30 overlaps CFG-3 (SN 21–40).A warning on configurations, not blocking: two products share serial numbers.

Revisions of an item

When a part changes from a serial number or date on, model the old and the new part as two items, each with its own effectivity, and relate the new one to the old one with supersedes (the inverse is superseded by). A chain such as rev C supersedes rev B supersedes rev A makes them revisions of one position. Holarch never chooses between revisions: it reports where their effectivity overlaps or leaves units without a revision.

  • Banner: when two revisions are both in effect at the view's point, the banner warns: "Overlapping revisions: A-20 Cooling unit has 2 in effect at SN 75 (A-20A, A-20B)."
  • Model Checks: Revisions in effect together (ProductLine.13) on each of the two revisions, with the serial numbers and dates they share; Units with no revision in effect (ProductLine.14) on the item the revisions decompose (or the oldest revision), with the units between the first and the last revision that have none, for example "SN 1–49 from 2027-07-01".
  • Release and baselines: a configuration cannot be set to Released or baselined while two of its revisions overlap: CFG-1 cannot be Released: A-20A and A-20B are both in effect for SN 50–99 from 2027-06-01 until 2027-07-01. Change one revision's effectivity, then release.

Overlaps and gaps are checked within each configuration both revisions apply to, inside that configuration's own effectivity.

Documents, RVTM and verification

Export a document for one configuration

In a project with at least one configuration, a Word template under Deliver ▾ (such as Specification (Word)) and ⌘K / Ctrl+K Export Document to Word open a short Export to Word dialog first. Projects without configurations export in one click, as before.

  • Configuration: All configurations, or one configuration ("CFG-2 EO-1 Lite"). Retired configurations are listed last, marked "(Retired)". The choice starts with the configuration your tab views.
  • Effectivity: Any unit, Serial number (such as 23; "SN 23" works too) or Date. It starts with the view's point.
  • Show applicability (All configurations only, on by default): adds "Applies to: CFG-1, CFG-3" under each section that only some configurations have. Retired configurations are not counted.

All Exports… → Document (Word) has the same choices in its Product line group (not for a baseline export).

A configuration's document contains:

  • Only the sections that apply to the configuration and are in effect at the chosen unit or date, with the configuration's own values.
  • A section under a left-out section moves up to the nearest section that is kept.
  • View numbers: an item after a left-out sibling is renumbered in the same style (4 becomes 3, and 4.1 becomes 3.1). Stored numbers do not change. The file says "Numbering as shown in CFG-2." under the title.
  • On the title page and in the footer: "Configuration CFG-2 EO-1 Lite · Serial number 23" (or "· Effective 2027-03-01"). A company Word template can place it with the field {{Configuration}}.
  • The file name names the configuration: "SRS – CFG-2 EO-1 Lite.docx".
  • Without a unit or date, a section with effectivity shows its tag under the title, such as "Effective SN 21 and later".

Printing or saving a PDF in a configuration view puts the configuration and point in the printed footer too.

The document outline

  • In a configuration view the outline shows view numbers. Renumber… and Renumber from Here… are disabled: "Numbers are shared by all configurations. Renumber in All configurations." Automatic renumbering after adds and moves is off in a view.
  • View ▾ → Columns offers Applies To and Effectivity columns once the project uses them.
  • ReqIF export of a document writes Applies To and effectivity as string attributes. The dialog says "Applies To and effectivity are exported as string attributes. Configuration values are not exported."

RVTM

  • In a configuration view: the configuration's requirements and results, so "verified" means verified for that product. The # column shows view numbers. Export ▾ names the configuration in the file name ("RVTM – CFG-2 EO-1 Lite.csv") and in the Word title.
  • In All configurations: a Configuration column group with one rolled-up status per configuration that is not retired. "—" means the requirement is not part of that configuration (tooltip "Does not apply to CFG-1"). CSV and Excel exports add one "Status in CFG-1" column per configuration ("Does not apply" when it is not part of it).
  • Effectivity Column: a toggle, hidden by default, kept per tab.
  • Only a configuration's own results count. A result recorded without a configuration (before the configuration existed, or in All configurations) verifies no configuration. In a configuration the test case shows as not run, and the requirement's status says "A result without a configuration (TC-1) does not count for CFG-2." The same note is in the configuration column's tooltip, in exports and in documents generated for a configuration. To verify the configuration, run the test again while viewing it.
  • At a serial number: the status comes from the latest run recorded for that serial number (Test Article "23", "SN 23" or "SN-0023") in the viewed configuration, with the note "Results recorded for SN 23 first". Test cases without such a run keep their status. Exports use the same statuses.

Test Center

  • Run Suite in a configuration view says "Recording results for CFG-2." and fills in Configuration / Build with "CFG-2 EO-1 Lite". At a serial number it also fills in Test Article. Results are saved as that configuration's values, so one test case holds one result per configuration.
  • Import Results… in a view shows the same note and fills in the same fields.
  • In All configurations, Run Suite and Import Results… ask Record results for: choose the configuration the test ran on, or No configuration (verifies none). Nothing is chosen at first, and no result is recorded until you choose. Results for a configuration are saved as its values, as in a view of it; a test case that is not in the chosen configuration is not recorded and says why. Results for no configuration are saved as the test case's values for All configurations; a configuration view shows them as a note under the test case's status, not as its result.
  • A results file may have a Configuration column. A row's value (a configuration's number, name or both) records that row for that configuration; a value that names no configuration skips the row and lists it in the dialog.
  • Reuse Result… (under a test case's status): counts a result from another configuration for a configuration on which the test did not run, when you can justify it, for example because the same unit design was tested. Choose the result to reuse (a configuration's result, or a result without a configuration), the configuration it is for (in a configuration view, the viewed one; in All configurations, any configuration the test case is in that has no result of its own) and enter a Justification (required). The result is copied to that configuration with your name, the date and the justification, and a single Undo takes it all back (toast "Reused the CFG-1 result for CFG-2.", with Undo).
  • A reused result is never silent. In the configuration it shows Reused with "from CFG-1 by Ann Lee on 2026-10-28: same motor and cooler" under the test case's status; the RVTM of the configuration says "Result reused from CFG-1 (TC-1): …" under the requirement's status; in All configurations the configuration column says "reused" (the justification is its tooltip); exports and documents generated for the configuration add the same note; Model Checks lists it as ProductLine.17. Stop Reusing takes it back (the test shows Not Run again), and running the test in the configuration replaces it with the configuration's own result.
  • A test case's Configuration attribute suggests the project's configurations while you edit it (inspector, Item View, Run Suite, Import Results). It stays free text: a build such as "Build 2.4.1" still works.

Diagrams and trade studies

  • Show applicability (diagram toolbar, LML projects, in All configurations): tints the shapes of items with Applies To or effectivity and writes their applicability under them, such as "Applies to F-4 · Effective SN 30 and later". The setting is kept per tab, and it is not offered inside a configuration view.
  • Trade Studies → + From Configurations… (under Alternatives) adds the product line's configurations as alternatives, and a single Undo takes it all back. Retired configurations start unticked. Toast: "Added 2 alternatives."

Baselines and change requests

These are part of the Team plan. Without it the commands are disabled with "Baselines per configuration are part of the Team plan. The project owner's plan decides."

Baselines per configuration

  1. Open Control & Reviews → Baselines & Versions.
  2. Click Baseline a Configuration…. While you view a configuration, the button reads Baseline CFG-2… and skips the choice.
  3. Choose the Configuration and enter a Name (it starts as "CFG-2 baseline 1"). Click Save Baseline. The toast reads "Baseline of CFG-2 saved." The table's Document column reads, for example, "Configuration CFG-2 EO-1 Lite".

The baseline records the whole product line, labelled with the configuration, and the effectivity point when you view at one. You can compare and restore it like any baseline. Not yet: a released-definition record of the configuration's verdict, choices and approvals.

Every baseline also records what the project used from other projects: the release of each library in use, and each link to an item in another project with that item's last change at the time. When Features come from a shown library, Compare → Configuration ▾ resolves a baseline against the library release it recorded, not the release in use now, so an item that left the configuration with a newer release shows as a change. A baseline saved before baselines recorded library releases resolves against the releases in use now, and the page says so. Restoring a baseline does not change which library releases the project uses.

Compare has two choices for product lines:

  • Configuration ▾: compares what one configuration shows. It picks the configuration's two newest baselines, or its newest baseline and the current model.
  • Compare with ▾: compares two configurations inside the From version, such as "What differs between CFG-2 and CFG-1 in EO-1 Flight PDR".

A project baseline made in a configuration view still records the whole product line.

Change requests

  • A change request page has a Configurations card: "Changes items in 2 of 4 configurations: CFG-2, CFG-3", with Show by Configuration (the changed items per configuration). A change to a base value does not count for configurations that have their own value.
  • Diffs name configuration values "Mass (CFG-2)", "Description (CFG-2)" and "In CFG-2", and list "Applies To" and "Effectivity" changes.
  • Owners as approvers: when a changed configuration's Owner names a project member, the request needs that person's approval too. The rule line reads "CFG-2's owner (Lee) must approve: this request changes CFG-2.", and screen readers hear "Approval needed from Lee for CFG-2". An owner that names no project member adds no rule.
  • Configuration control: with change control on, a configuration that is Released and in the latest baseline is controlled. Its own values on items change only through a change request ("… released, in the latest baseline").
  • Applicability of controlled items: an approved or baselined item's Applies To, Effectivity, and putting it in or taking it out of a configuration in a configuration view change only through a change request, like its other fields. The same holds for a relationship whose source is controlled. On the hosted service the server also checks changes made offline.
  • Libraries: the features and configurations of a mounted library release count in Applies To, configurations and views. They are read-only.

Model Checks

Verification → Model Checks runs the built-in rule set Product line once a project has a Feature or Configuration.

RuleHeadingSeverity
ProductLine.1Applies To names a missing feature or configurationError
ProductLine.2Items in no configurationWarning
ProductLine.3Configurations that break a rule or are incompleteError
ProductLine.4Features no configuration selectsWarning
ProductLine.5Items in a configuration their parent is not inWarning
ProductLine.6Relationships whose ends are never in one configurationWarning
ProductLine.7Configurations with overlapping serial numbersWarning
ProductLine.8Effectivity outside the item’s configurationsWarning
ProductLine.9Values for configurations the item is not inWarning
ProductLine.10Requirements not verified in a configurationWarning
ProductLine.11Connections with an end missing in a configurationWarning
ProductLine.13Revisions in effect togetherWarning
ProductLine.14Units with no revision in effectWarning
ProductLine.15Test results without a configurationWarning
ProductLine.16Released configurations with requirements not verified in themError
ProductLine.17Test results reused from another configurationWarning

The completeness rules check every configuration from All configurations, without switching the view. ProductLine.10 names the configurations a requirement is not verified in, such as "Not verified in CFG-2, CFG-3 (Released)". ProductLine.11 names the configurations and the missing end, such as "In CFG-2: A-11 Coolant pump is not in the configuration". ProductLine.3 says "Released configuration." for a released one, and "It cannot be Released until this is fixed." for a draft. ProductLine.16 lists the requirements a Released configuration does not verify.

ProductLine.13 and 14 check revisions linked by supersedes (see Revisions of an item): "Overlaps A-20B for SN 50–99 from 2027-06-01 until 2027-07-01" on each of two overlapping revisions, and "No revision in effect for SN 1–49 from 2027-07-01" on the item they decompose.

ProductLine.15 lists test cases whose Status was recorded without a configuration, with the configurations it does not count for, such as "Passed without a configuration; does not count for CFG-2". Run the test again while viewing each configuration.

ProductLine.17 lists test cases whose result counts for a configuration through Reuse Result…, with the justification, such as "CFG-2: Reused from CFG-1 by Ann Lee on 2026-10-28: same motor and cooler". Review the justification, or run the test while viewing the configuration to replace the reused result.

For ProductLine.9, Fix → Remove Values lists the values, such as "Mass (CFG-2): 1,520", and removes them, and a single Undo takes it all back.

In the CubeSat EO-1 demo, the feature Propulsion is left unselected on purpose: it is the example of ProductLine.4.

Search, import and export

  • Search and queries: appliesto:CFG-2 finds the items that apply to CFG-2; varies:yes finds items with configuration values.
  • JSON: keeps every field.
  • CSV: the Database export adds four columns after the others, Applies To (as you would type it), Serial Effectivity, Effective From and Effective Until, once the project uses product lines. Import reads the same column titles (Map step: the Product line group). An unknown feature or configuration, a bad serial range or a bad date is reported for that row, and that field is left out.
  • ReqIF: Applies To and effectivity as string attributes; configuration values are not exported.
  • Invalid Applies To or effectivity values in an imported file are left out.

REST API and MCP

  • list_configurations (MCP) and GET …/configurations (REST) list the features, the rules and the configurations with their verdicts.
  • Read routes and MCP read tools take configuration (number, name or id) and effectivity (sn:23 or date:2027-03-01). The answer is that configuration's view. Without them, items carry appliesTo, effectivity and their configuration values.
  • Not yet: the Product line rules (ProductLine.1–9) in Model Checks through the API (run_model_checks, GET …/model-checks). Run them in Verification → Model Checks.
  • Writes take appliesTo and effectivity. With configuration, a write is made as in that configuration's view; an AI client's proposal made this way says "Apply in CFG-2: new items apply to CFG-2; changed values become CFG-2's."

See REST API: Product lines for every field and message.

Plans

FeatureFreeIndividualTeam
Reading a project as one configuration through the API✓✓✓
Product Line page, View as ▾, Applies To, configuration values and effectivity, read-only✓✓✓
Editing the product line: features, configurations, selections, Applies To, configuration values, effectivity, documents and RVTM per configuration, writes through the API—✓✓
Baselines per configuration, Compare by configuration, the configurations a change request changes, configuration owners——✓

The project owner's plan decides. An academic email address or a class organization keeps all rows.

Without the plan the product line is read-only and nothing is deleted:

  • The Product Line page shows the features, the configurations, the matrix and the verdicts. Check Configurations, Export CSV and a column's View as This Configuration work. + New Feature, + New Configuration, the matrix and the row and column commands that change something are disabled. The page says "Read only: editing product lines is part of the Individual and Team plans. The project owner's plan decides." with Choose Plan….
  • View as ▾ shows one configuration read-only. The banner says the same line.
  • The inspector shows Applies To, effectivity and configuration values read-only. Feature and Configuration items are read-only.
  • ⌘K / Ctrl+K New Feature…, New Configuration… and Start a Product Line… stay listed and say why they do not run.
  • Exports keep every field. A new use is refused with "Product lines are part of the Individual and Team plans. The project owner's plan decides." A configuration owner without the Team plan: "Configuration owners are part of the Team plan. The project owner's plan decides."

SysML v2 projects

SysML v2 has variability built into the language: variation points, variants and configurations (@HolarchConfiguration usages). A SysML v2 project uses the same Product Line page and View as ▾ control:

  • Product Line page: the variation points tree, the configurations matrix with a Verdict row, the Rules (the product line's assert constraints, read-only, with Open in Editor), Insert Variation Point… (opens the Editor), Check Configurations and + New Configuration. Choosing a variant writes, for example, part :>> charger = charger::wallbox; in the configuration.
  • View as ▾: lists the configurations of each product line with their verdicts. Every view, the Database, the inspector and the Product Line page follow it.
  • On Free the Product Line page is read-only as in an LML project: Insert Variation Point…, + New Configuration and the matrix's choices are disabled, and New Configuration… in the Browser, the inspector and ⌘K / Ctrl+K say why. The model's text stays editable in the Editor.
  • Editing in a configuration view (Individual and Team; read-only on Free): every edit is a SysML v2 text edit checked by the checker, and a single Undo takes it all back. A changed attribute becomes the configuration's own value; new parts belong to the configuration; deleting an inherited optional element writes part :>> roofBox[0];.
  • Holarch data next to the model, such as risks and tasks, applies to every configuration, except items created while a configuration is shown: they apply to that configuration. Editing Applies To on them is not available in SysML v2 projects yet. Effectivity is set on model elements and configurations (the inspector's Effectivity section).
  • Not yet: Make a SysML v2 Copy… of an LML project leaves its features and configurations out (the report lists them under Not converted). Model the variants again in the copy.

See SysML v2 Variants and Configurations.

Limits

  • Applies To: at most 2,000 characters, 200 terms and 32 levels of parentheses.
  • Serial numbers: at most 200 ranges, numbers up to 1,000,000,000,000.
  • Name, Number, Class, Labels, Assignee and structure cannot differ by configuration.
  • Each structure (parents and order) is shared by every configuration. Not yet: a structure per configuration.
  • ReqIF exports leave out configuration values.
  • Not yet: a project serial prefix, and Applies To on relationships in the relationship panel.
  • Not yet: effectivity that tells approval, effective, as-built and retrofit dates apart. Effectivity is one serial-number range list and one build-date range.
  • Not yet: a configuration baseline as a released definition. It records the product line labelled with the configuration, not the configuration's verdict, choices and approvals as a separate record.
  • Not yet: converting features and configurations when making a SysML v2 copy of an LML project.
  • Expressions do not contain serial numbers or dates; use effectivity for those.