>
> I have put the functional description for customer contracts into the Wiki:
>
That looks interesting. We are working on a contract module specifically
designed
to manage insurance contracts (which includes a lot of specific data /
treatments),
but I find a lot of shared concepts with the "Service Contract".
Here are some insights on what we have been doing :
- Contracts are build from an Offered
- Contracts have a list of Options, which are more or less services to
which the
contract's subscriber is entitled
- Options are build from Coverages, of which a list is defined on the
Offered
If we use the example of a mobile phone subscription :
- you will subscribe to a packaging of services
- this package (the offered) will contain the following available
services (the coverages) :
+ Calling time (1 / 2 / 3 / 4 hours per month)
+ SMS (100 / 150 / 200 per month)
+ Data Plan (1 / 2 GB per month)
- your contract will activate the following services (the options) :
+ Calling time : 2 hour / month, active today
+ SMS : 100 / month, active today
+ Data : 1 GB / month, active next month
Offered + Coverages are a template from which we create Contract + Options.
We built a logic of "rules" on offered / coverages which defines the
different
aspects of the contract (pricing / eligibility / documents /
resiliation...). We also
include the notion of "Delivered Service" which is activated when a client
needs
a service provided by his contract (assuming the service is available and
the client
is eligible for it).
When you bill the contract, you actually ask the offered to bill the
contract. It will look
for configured pricing rule and billing rules in all the active services on
the contract, then
calculate the resulting amount.
Everything which defines the way the contract must behave (price,
eligibility, resiliation,
renewal...) is configured in the offered / coverages from which the
contract was created.
We are ready to discuss our model and offer our input regarding this new
module.
Jean CAVALLO
Coopengo
