Customers & services
The customer relationship and the services relevant to a commercial request.
Home / Architecture / Ontology & AI Context
ONTOLOGY & AI CONTEXT
Give AI the context
to support your business.
An offer is connected to more than a price. It relates to products, customers, eligibility, orders and the services behind them. Taranga’s operational ontology provides a shared model of these relationships, helping connect AI-assisted work to the commercial context.
Opens an editable email draft. No request is sent or meeting reserved.
WHY CONTEXT MATTERS
A business request needs more than a text response.
A request such as “Help me prepare an offer for these customers” needs context: which customers, which proposition, what conditions apply and what the operator is asking the system to do.
Shared meaning helps relate the request to relevant information and commercial concepts. It does not by itself establish that the underlying data is complete, current or correct.
AN ILLUSTRATIVE WORKFLOW
From a commercial question to a proposal for review.
“Help me prepare an offer for these customers.” Follow the questions behind the request.
- Understand the request
Identify the audience, commercial objective and information needed.
- Connect the context
Relate the relevant customer, product, offering and service concepts within the adopted scope.
- Check applicability
Use the configured eligibility and business rules to assess the intended proposition.
- Review the proposed action
Present the supported action for operator review, with the applicable permissions, checks and approval requirements.
- Execute and retain the result
If authorised, the registered action invokes the responsible systems. Execution receipts record the action and its result within the supported workflow.
This is an illustrative relationship between context, rules and governed action, not a claim that every step is available as one automated workflow. Demonstrate the intended use case and integration boundaries before adoption.
HOW CONTEXT CONNECTS TO ACTION
Shared meaning. Governed actions. Defined execution.
Each layer has a distinct responsibility.
Ontology supplies context
Describes business concepts and relationships. It helps make the commercial context explicit.
Governance controls actions
Registered actions, permissions, preconditions and approvals determine what may proceed. The ontology does not replace these controls.
Transactional systems execute
The responsible services carry out ordering, billing and other agreed steps. Charging and connectivity remain external where defined by the deployment scope.
MODERNISE WITH CONTEXT
Build shared meaning across the agreed system landscape.
Progressive modernisation brings capabilities together over time. A shared model helps describe the relationships between the commercial concepts involved, while systems retain their defined responsibilities.
Existing systems still require agreed mappings, interfaces, data ownership and integration work. Validate model coverage, access boundaries and data quality for each use case. Do not assume that a shared ontology automatically connects every legacy system.
FROM ARCHITECTURE TO BUSINESS
See context in the commercial workflow.
Explore how propositions are defined and brought to relevant audiences.
Watch the marketing workflow demonstration
DEFINE YOUR USE CASE
Start with the business question.
Discuss the model coverage, data sources, supported actions and integration boundaries relevant to your workflow.
Opens an editable email draft. No request is sent or meeting reserved.