coopengo: how we used tryton to build an insurance erp · no freedom from the erp vendor what we...

16
Oct 17, 2016 Coopengo: How we used tryton to build an Insurance ERP A brief history of the coog construction from the first tryton module to a fully featured scalable application 1

Upload: hakhuong

Post on 12-Dec-2018

227 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

Coopengo: How we used tryton to build an

Insurance ERP

A brief history of the coog construction from the first tryton module to a fully featured scalable application

1

Page 2: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

Speakers

2

● 15 years experience in ERP implementation projects

● 10 years experience in insurance projects

● Founding partner of Coopengo

● 13 years experience in Insurance solution development

● 3 years experience in project management at Coopengo

Page 3: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

Summary

● Why we created coopengo ● The Insurance business● What is needed in an Insurance ERP?● Why we chose tryton● A brief history of coog● What is coog?● Some realizations● Demonstration

3

Page 4: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

Why we created coopengo?

● Coopengo was created in 2012 by insurance software experts

● What was the market back then?● Locked-in market● High licence fee (50k€ to 2M€)● Long presales step (6 months to more than a year)● Small and mid-size customer can not afford to access to the market ● Customers stuck with 80’s AS400 solutions● No solution flexible enough● No freedom from the ERP vendor

● What we wanted to offer :● Free license solution● Fully flexible solution● Standard solution● Customer autonomy

4

Page 5: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

The Insurance Business 1/2

5

Insurer

Customer

Broker

Third Party Administrator (TPA)

asks for a premium comparison for an insurance

finds the best price on the market

subscribes a policy

informs

pays a periodic premium

$calculates the commissions

pays the commission $ pays back the

residual amount

Page 6: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

The Insurance Business 2/2

6

Insurer

Customer Third Party Administrator (TPA)

- checks eligibility- calculates the indemnification

asks for expert opinion

in case of a loss, opens a claim

pays the indemnification

$

Page 7: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

What is needed in an insurance ERP ?

● Contract management● Contract subscription● Endorsements (contract modification)

● Premium management● Calculate premium according to many criteria (age,

insured amount, distribution network, ….)● Calculate different commissions (fixed rate, variable

rate, pre-payment) between the different parties involved (insurer, broker, TPA, distribution, …)

● Generate periodic invoices on big database (1 M contracts -> 1 M invoices billed once a month)

● Generate bank file for direct debit payment (SEPA for Europe)

● Automatic dunning and contract resiliation if bill is unpaid.

● Rule & workflow engine to easily create new insurance products through configuration

7

● Quotation and coverage comparison

● Customer portal

● Business partners portal

Front Office Back Office

Page 8: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

Why we chose tryton (back in 2012) ?

● attractiveness of the language (python over java)

● modularity of the solution● more a framework than a plug & play

solution● scalable solution (more a leap of faith

than a rational choice at the time)● support & formation by the b2ck

company● price● Some kind of freedom (no string

attached)

8

Pros Cons

● no web client● timid community● specialized solution less known by end

users customers

Page 9: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

A brief history of coog

9

2011 2012 2013 2014 2015 2016 2017 2018

Framework benchmark

Tryton chosen

Tryton formation & first module : contract

release of the

coopengo solution

1.0

Coopengo creation

first customer

first customer going live

scalabilty issues with 50 users at the same

time

new architecture using nginx and redis

Benchmark Prototyping Project Industrialization Web

migration from hg to

git

450 000 contracts to migrate

in coog

smile benchmarked

coog and billed 1M contracts in 1

hour

quotation front app

oct jan apr jul jul dec dec oct nov dec jul sep nov dec oct

release of tryton proxy

SAAS offer

customers

Page 10: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

What is Coog

10

Page 11: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

Coog technical solution

11

JSON

RPC

JSON

RPC

REST

ServersClients

Web clients

Rich clients

http

https

Cache

Reverse P

roxy

Batch servers

Web AppWeb Services Servers

Database

http

https

http

App servers

AppData

Page 12: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

Some tryton functionalities sponsored by Coopengo

● Technical functionalities● trytond_celery● dict fields● Oracle backend (beta)● O2M cartesian product● client prevalidation● per user plugins● multi-selection widget● history browser● factor attribute on client views● global search● paste in editable list view ● allow to store the views in a XML file instead of the database

● Business functionalities● account move template● commission● bank● sepa payment● clearing● reconciliation wizard● tax rounding per line

12

Page 13: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

Some realizations

13

Page 14: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

Revision blame

14

Page 15: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

More information

● github.com/coopengo

● coopengo.com

● https://www.npmjs.com/~coopengo

15

Page 16: Coopengo: How we used tryton to build an Insurance ERP · No freedom from the ERP vendor What we wanted to offer : Free license solution Fully flexible solution Standard solution

Oct 17, 2016

Subscription Process Demo

16

Insurer

Customer

Broker

Third Party Administrator (TPA)

asks for a premium comparison for an insurance

finds the best price on the market

subscribes a policy

informs

pays a periodic premium

$calculates the commissions

pays the commission $ pays back the

residual amount