Service and Service Model
The service, the expected outcome, the terms of provision and consumption. The running service instance and the service level agreement are delegated.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterprisePRD
- Industry
- Cross-industry
- Tags
- EM-PRD-02W1subjectServiceServiceOfferingServiceConsumptionServiceDependency
What it is Filled
The service, the expected outcome, the terms of provision and consumption. The running service instance and the service level agreement are delegated.
Why it exists Filled
The service, the expected outcome, the terms of provision and consumption. The running service instance and the service level agreement are delegated.
Distinguishing features Derived, awaiting review
- The consumer is not the technical API client
- A service does not contain a copy of the runtime
- The expected outcome is separated from the measured one
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: An API endpoint is automatically declared a business service.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Руководитель продукта
Master systems
- Каталог продуктов
- discovery
- PLM
Links to other meta-models Filled
neighbor
- EM-PRD-01
- EM-RSK-04
- EM-TEC-04
- EM-TEC-05
- EM-TEC-06
references
- WM-ACT-004 - conceptual-candidate
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- Service
- ServiceOffering
- ServiceConsumption
- ServiceDependency
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- TM Forum SID: product/service/resource and commercial roles
- IDTA AAS: physical assets and composite descriptions
- Product management and engineering configuration; compare selected PLM and software practices
Open questions
- How does a service differ from a product and a process?
- Can an internal service have no price?
- How is one service linked to several providers and implementations?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-prd-02/brief.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.