Commercial landscape
Relationships with the market, counterparties, opportunities, orders and channels.
Bundle → Layer → Finding → Questions Filled
2 bundles · 2 layers · 4 findings · 8 questions
Market and counterparties Who the organisation trades with and in which roles.
Parties and roles
One party record reused across customer, supplier and partner roles.
Party reuse
A counterparty appears once, with several roles.
- Is this counterparty already recorded under another role?
- Which roles does the party play, and in which business perimeters?
Grouping
Counterparties grouped by justified relationships.
- Which counterparties belong to the same group, and on what basis?
- Which group links are uncertain and kept as such?
Pipeline and fact Opportunities and forecasts set against confirmed orders.
Forecast versus order
Expected business kept apart from booked business.
Backed forecast
Forecast lines with or without supporting orders.
- Which forecast amounts are backed by orders?
- Which opportunities have no order yet?
Concentration
Dependence on a few customers or groups.
- What share of revenue comes from the largest group of related customers?
- Does the concentration figure avoid double counting a group?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise landscape
- Entry kind
- landscape
- Domain
- EnterpriseLND
- Industry
- Cross-industry
- Tags
- EM-LND-08W2landscapeCommercialLandscapeMarketScope
What it is Filled
Relationships with the market, counterparties, opportunities, orders and channels.
Why it exists Filled
Relationships with the market, counterparties, opportunities, orders and channels.
Distinguishing features Filled
- A counterparty is one party with several roles, never several unrelated records.
- Forecasts and booked orders are kept apart and never summed as one figure.
- Groupings of counterparties carry a justification and may remain uncertain.
- Distinct from the contract landscape, which maps obligations rather than market relationships.
What robots and AI may and may not do Filled
Must not
- Sum a customer and a supplier with the same identifier as two independent counterparties.
- Present forecast revenue as booked revenue.
- Merge counterparties into a group without a recorded basis.
- Hide uncertain group links by forcing them to yes or no.
Only with a human decision
- Confirming that two counterparty records denote the same party.
- Accepting a group relationship that affects credit or concentration limits.
May
- Show customer and supplier concentration per business perimeter.
- Flag counterparties that appear under several identifiers or roles.
- Separate forecast amounts from amounts backed by orders.
Moral aspects Filled
- Wrong grouping can misstate credit exposure and harm lenders, staff or counterparties.
- Counterparty records about sole traders contain personal data and need proportionate handling.
Who is affected
- Customers, suppliers and partners
- Sales and procurement staff
- Finance and credit risk teams
Owners Filled
Steward
A commercial information steward is accountable for landscape scope, counterparty identity, relationship quality and authoritative source references.
Master systems
- Counterparty master data registry.
- Customer relationship and opportunity management system.
- Supplier relationship management system.
- Order management system.
- Commercial channel registry.
- Financial accounting system.
Links to other meta-models Filled
references
- WM-ORG-014 - conceptual-candidate
- WM-ECO-020 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by a market scope identifier and version; counterparties by LEI where one exists, otherwise by registry number and jurisdiction.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A view of counterparties with roles, groups, opportunities and orders across perimeters.
- Often confused with a sales pipeline report or a supplier list.
Capabilities and actions required Filled
- Concentration can be computed per group without double counting.
- Multi-role counterparties can be shown with all their roles at once.
Hazards and failure modes required Filled
- Double counting when one party sits under two identifiers.
- Inflated outlook when forecasts are mixed with orders.
Standards and interfaces required Filled
- GLEIF LEI and its relationship data for legal entities and parent links.
- ISO 3166 for country codes of markets and counterparties.
- ISO 4217 for currency codes in order and forecast amounts.
Context of use required Filled
- Used in sales planning, supplier risk review and credit limit decisions.
- Relevant for groups operating several business perimeters with shared counterparties.
Sources Filled
- Vercy composition and whole-object: a separate landscape object and delegation
- ArchiMate/ISO 42010: views, questions and representation rules
- Compare participant subject models and the practical assembly of a permitted context
- Vercy Whole-Object Description Profile - Checked live (HTTP 200) on 2026-10-07.
- TMF629 Customer Management OAS - Carried over from the published world model wm-org-014-customer-account-relationship; checked live (HTTP 200) on 2026-10-09.
- Customer entities: Account and Contact - Carried over from the published world model wm-org-014-customer-account-relationship; checked live (HTTP 200) on 2026-10-09.
- Dataverse Account table reference - Carried over from the published world model wm-org-014-customer-account-relationship; checked live (HTTP 200) on 2026-10-09.
Open questions
- How to see concentration without double counting a group?
- Where does one counterparty play several roles?
- Which forecasts are not backed by orders?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-lnd-08/brief.json, ver-cy/world-models/card-supplements/em-lnd-08.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.