Abstract
1. Introduction to Entities
In Pingwire, an entity is the subject of investigation or monitoring. An entity represents an individual, business, account, or product (asset) that your rules and workflows are applied to.
Entities are the foundation of the system: every request, rule, ping, or case is ultimately tied to one or more entities.
Importantly, entities in Pingwire are interconnected. This means that relationships between entities can be mapped — for example, linking an individual to one or more accounts, or connecting a business to its associated products and individuals.
Each entity can be monitored individually, or multiple entities can be monitored together as a collective group, depending on your monitoring needs and rule configuration.
2. Types of Entities in Pingwire
Pingwire supports four different entity types:
- Accounts - Represents a financial or user account, such as a bank account, customer account, or internal system account. The unique identifier in the plattform is usually IBAN.
- Businesses - Represents a legal entity such as a company, organization, or institution. The unique identifier in the plattform is usually Business Name or Organisation Number.
- Individuals - Represents a natural person in the system. The unique identifier in the plattform is usually a SSN (Social Security Number) or similar identifier.
- Products - Represents an asset or item, such as financial products, digital assets, or physical goods. The unique identifier in the plattform is usually Product Description.
3. Relationships Between Entities
Entities in Pingwire can be linked to reflect real-world relationships and dependencies. This connectivity allows for more powerful monitoring and risk assessment across different dimensions of your data.
Examples include:
- An Individual linked to multiple Accounts (for example, a person owning several bank accounts).
- A Business connected to multiple Individuals (for example, employees, owners, or authorized representatives).
- A Product associated with both an Account and a Business (for example, a financial product offered to a corporate customer).
These relationships make it possible to:
- Identify and investigate networked risks (e.g., shared ownership or usage across entities).
- Create rules that trigger based on activity across related entities rather than only one.
- Aggregate and visualize monitoring results at the entity level or across groups of related entities.
In practice, this means you can track, analyze, and act on data per entity or across connected entities, providing a complete and flexible view of your ecosystem.
In short: an entity is the “who” or “what” you are monitoring. In Pingwire, entities can be Accounts, Businesses, Individuals, or Products, and they can all be connected, monitored separately, or monitored collectively as part of a broader risk or operational view.