BRITEDATA Reporting with Business Intelligence for BriteCore 1
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
BRITEDATAReporting with
Business Intelligence for BriteCore
1
CHRIS REYNOLDS10/20/2014BRITEDATA
Guess What…BRITEDATA
2
BriteData is LIVE
CHRIS REYNOLDSBRITEDATA
4
CHRIS REYNOLDSBRITEDATA
5
CHRIS REYNOLDS10/20/2014BRITEDATA
It took a village…BRITEDATA TEAM
6
CHRIS REYNOLDS10/20/2014BRITEDATA
Coverage A Report by Zip CodeREPORT 1
7
Scenario:
You want to see the total inforce premium and limits for Coverage A by Zip Code
CHRIS REYNOLDS10/20/2014BRITEDATA
Coverage Report By EverythingREPORT 2
8
Scenario:
You want to see the total inforce premium and limits for Coverage A by EVERYTHING.
CHRIS REYNOLDS10/20/2014BRITEDATA
Property/Liability ReportREPORT 3
9
Scenario:
You need to produce a report that shows your premium broken down by Property or Liability, where only certain line items are counted.
CHRIS REYNOLDS10/20/2014BRITEDATA
Reinsurance CAT Property ReportREPORT 4
10
Scenario:
It’s September, and your reinsurer needs the Property CAT Exposure Report
CHRIS REYNOLDS10/20/2014BRITEDATA
Reinsurance CAT Property ReportREPORT 4
11
Scenario:
Property Cat Report that’s much more involved…
CHRIS REYNOLDS10/20/2014BRITEDATA
Limit ProfileREPORT 5
12
Scenario:
You need to produce a Limit Profile where the limits are divided into various “ranges”.
CHRIS REYNOLDS10/20/2014BRITEDATA
Things to knowGOTCHA’S
13
• JS error for long loads
• This is still BETA, there will be things…
• If you run a report, and you don’t see it in the report status page, you should re-run it.
CHRIS REYNOLDS10/20/2014BRITEDATA
The Future Of BriteDataWHAT’S NEXT?
14
• Accounting Data
• Quote and App Data (Non-Committed Policies)
• Custom Queries are EOL after December.
• DW Extractions for Nov and Dec will be by request.
• Custom Premium/Limit Extracts will be EOL after Dec 1.
CHRIS REYNOLDS10/20/2014BRITEDATA
The Future Of BriteDataWHAT’S NEXT?
15
• Share your recipes!!!
• User Inputs for dates
CHRIS REYNOLDS10/20/2014BRITEDATA
A LiJle HistoryBRITEDATA
16
• Traditional Data Warehouse • Need a maintainable infrastructure • Business Users don’t do SQL Queries • Waiting on monthly extractions is awful • Fact and Dimension Tables are awesome
CHRIS REYNOLDS10/20/2014BRITEDATA
A LiJle HistoryBRITEDATA
17
• Pandas (Python Data Analysis Library) • Wicked-Fast • Data Extracts & Agency Experience Report • Huge, vibrant community doing cutting-edge things
• Knockout.js & Bootstrap • Faster, more robust User Interface • Easier to maintain
CHRIS REYNOLDS10/20/2014BRITEDATA
A LiJle HistoryBRITEDATA
18
• BriteData • We use Fact/Dimension concept from DW • Data is available on-the-fly through Pandas • No Queries are needed • The engine does all the hard work (date/date-range) • Testable, Sharable, Maintainable • The interface is so easy to use