FRSolid & upgradeable architecture
efluid functional architecture
The efluid architecture has been designed with a view to durability and upgradability.
Its modularity and its component-based approach allow it to offer solutions adapted to all business processes.
Customer relationship management
Management of the business processes
prospecting, tracking of requests, complaints, etc.
Management of contracts
offers, commissioning, services, etc.
MDM technical functions
Management of meter readings
consumption, estimate, etc
Management of intervention requests
installation, removal of meter, etc.
Billing domain
Billing management
routing, supply, etc.
Management of quotes and requests
connection request…
Management of customer accounting
Management of payment
payment, miscellaneous transactions, outstanding items, etc.
Collection management
disputes, bailiffs, etc.
Other specific services
Flow recovery management
flow recovery, estimated metering, etc.
Customer relationship management through front and back office commercial functions
Manage business processes
- Prospecting and canvassing, on the supplier side,
- Contracts for tracking connection requests or work requests,
- All types of contracts triggering tracking of the customer request (complaint for example),
- …
Manage contracts
- For the supplier: management of regulated or market offers, integration of the sales proposal management cycle, integration of the commissioning or termination processes, management of service requests,
- For the network manager, administration of network access requests, handling of service requests (change of supplier, request for commissioning, termination, etc.),
- …
Management of meter readings
- Manage meters, hardware and equipment
- Manage recurring, real or estimated, event-based, regularization meter readings,
- …
Management of intervention requests
- Manage technical intervention requests in the field,
- Generate or integrate intervention reports communicated by the network managers,
- …
Billing functions
- Configure offers,
- Recurrent, event-based, corrective, collection billing,
- Bill services in the form of a quote, order, down payment,
- …
Customer account management
- Payments in all forms,
- Collection,
- Management of disputes, and bad debts,
- …
Miscellaneous functions
efluid manages a wide range of functions adapted to each activity sector concerned.
For example, efluid provides full flow recovery management for energy providers:
- entry to and exit from the area,
- consumption reports at the terminals of the balancing authority with publication of provisional graphs for the short- and medium-term (thus allowing the trading department to manage the financial exposure),
- calculation of energy provided but not billed,
- calculation of the future turnover by offer and service,
- …
The stakeholders are for example customers (individuals, corporations, local authorities, etc.), distributors, balancing authorities or partners.
By authorizing all business functions to access each object in this layer, efluid naturally allows 360° customer management, with three fundamental objectives:
- each stakeholder is unique (no duplicates),
- the customer file can be used to view the entire history associated with a customer, including when they have several contracts in various locations,
- the stakeholder also interacts with business objects (contracts, bills, etc.) via roles (holder, payer, applicant, owner, hirer, etc.).
These represent the supply locations on which the points of service (POS) will be constructed for each activity (gas, electricity, urban heating, water).
They are also perfectly visible to all business functions and thus contribute to the 360° vision of the customer relationship with two fundamental objectives:
- the POD is unique (no duplicates),
- the POD file can be used to view everything that can be known at this location, for all activities and services, retaining the view of the successive stakeholders in this location.
This essential data relates to routes or concessions, but can also represent aggregations on which energy and flows can be accounted for.
This will be used to model the company structure (work groups, business role, portfolio, etc.) and automatically generate tasks to be carried out for users of the IS (whatever the business functions).
efluid is designed based on software layers, with each layer accessing the layers of lower levels. Management of the reference is thus treated as a fundamental layer, essential for perfect control of the business functions. The “reference” layer manages the main business objects.
efluid is designed based on software layers, with each layer accessing the layers of lower levels. Management of the reference is thus treated as a fundamental layer, essential for perfect control of the business functions. The "reference" layer manages the main business objects.
This trace and history management component will control the manual or automatic tracing of changes to all business objects. It continuously enhances the customer relationship.
This component is used to manage processes, associating them with business steps in TP, B2B or batch processing.
This component manages bulk processing:
- in recurring processes (in connection with schedules managed by efluid),
- permanent processes (issuing of short-term daily forecasts, for example),
- occasional processes (marketing or information campaigns to customers, such as for example a review of changes to the regulations).
This component is used to generate the tasks to be carried out. These tasks are linked to business processes (in the event of anomalies, for example) and consist of processing lists assigned to users or work groups, in accordance with the organization configured in efluid.
The power of the IS, along with its capacity to address in detail the business problems of each utility, comes from access to all of these components from the business functions, and their inter-connectability.es problématiques métier de chaque utilities.
This layer contains the technical functions which will be used to manage, among other things:- access to the functions (authorizations) and risk management, - access to data (object / relational mapping),- access to the service layers. This layer will also include the technical components used to configure the inter-connection of the business objects, in complex processes.
This layer gathers and exploits the basic components of the Java JEE development.