Over the next five years, BriteCore plans to completely rewrite its software suite. By making the suite more modular, stable, and scalable, BriteCore will be able to support the needs of all insurers globally.
5. Current Strengths
• Integrated: As an integrated suite, BriteCore supports all departments
efficiently without fragmentation, integration, and coordination concerns.
• Modern: Modern architecture and infrastructure allows customers to take
advantage of current technology.
• Managed: Fully managed architecture outsources DevOps and IT infrastructure
while offering incredible security, durability, availability, and scalability at a fraction
of traditional hosting costs.
6. Current Strengths
• Platform: API-driven platform supports simple expansion and integration through
web requests. Customers can easily expand the base system to support tools such
as unique underwriting models, external data sources, and custom distribution sites.
• Open Source: Open source model allows customers and vendors to take control of
their own timelines and initiatives through source code contribution.
• Single Source: Single Source web service ensures that all clients are always on the
latest release of the software eliminating code silos and code islands.
• Continuous Delivery: BriteCore enjoys over 1,000 merged Pull Requests annually
which means our customers are constantly receiving new value from a vibrant and
evolving platform.
7. Current Weaknesses
• Monolith: BriteCore is currently a single web service with a common repository
and database for all modules which means modularization requires code
modification.
• Business Rules: Business rules are either coded directly into source code or are
managed via settings which means rule triggers and effects require source code
modification.
• Risk Model: Supported lines were originally small schedule property and liability
only which lead to limitations in the risk model.
8. Current Weaknesses
• Workflow: BriteCore’s workflow tools were originally built for small teams
without complex authority limits, task routing, or permissions.
• Internationalization: BriteCore is currently built for domestic US and Canada.
While global address services are utilized, the database requires some location
modifications to support international addresses. Currencies are all dollars and
language is all English.
• Capabilities: General capabilities are tuned for a limited subset of the insurers,
limiting our ability to easily implement many types of insurance companies.
9. Barriers
• Resources: Implementations and new projects tend to fall under significant time
and financial constraints, competing for resources.
• Timeline: Near-term needs and ROI are much more apparent to community.
• Scope: Projects at the largest scope are intimidating.
• Complexity: Solutions require deep domain expertise across insurance,
operations, process analysis, technology, deployment along with predictions
about what the market will demand in the future.
• Uncertainty: Scope and timelines are inherently unknown.
12. Universal
• 100%: BriteCore should be capable of supporting the needs of all insurers
globally. This requires both enhancement to current modules such as Policies
and the addition of new modules such as Tasks.
• Sales: Sales are at an all time high, broadening our exposure. We have been
compiling global requirements across demos and RFIs. New clients today
already write auto, workers comp, commercial cargo.
• SMEs: We have engaged directly with Ernst&Young, Gartner, Novarica, and
Strategy Meets Action and have been in ongoing discussions to supplement our
subject matter expertise for business we don’t currently support.
13. Modular
• Targeted: Allows us to tailor the system to the needs of each client.
• Tooling: Bring the best possible tools and technology to each functional area of
the system.
• Simplicity: Reduce the complexity of any one module, allowing engineers to
gain expertise quickly.
• Replaceable: Surround each module with a clear API to allow simple
substitutions in the future.
14. Stable
• Resilient: Services outages are less severe in a decoupled world.
• Testing: Decoupling functionality from business rules promotes test coverage.
• Versioned: Replace entire modules with stable API endpoints for versioning.
• Logging: Routing all events and messages through a central bus provides
granular debugging.
• Monitoring: Cluster health can be monitored at a granular level to decrease
incident response time.
15. Scalable
• Tunable: Decoupled services can be tuned individually.
• Targeted: Deploy each functional area using the best possible tools.
• Parallel: Server-less deployment allows for massive parallel concurrency.
• Upmarket: New features are being built to support large scale workflows.
18. BriteHub BriteDocs
BriteDrive BriteRules BriteData
BriteTasks BritePrint BriteContacts
BriteApps BritePolicies BriteClaims
BriteBilling BriteQuoteBriteLines
BriteAuth
• Users: Centralized user management
• Login: System login with password management and recovery
• SSO: Single Sign On supported through web tokens
• MFA: Multifactor authentication through apps and text
• Services: Support for federated services and active directory
• Permissions: Route-based, field-based, scope-based, range-based
19. BriteAuthBriteHub BriteDocs
BriteDrive BriteRules BriteData
BriteTasks BritePrint BriteContacts
BriteApps BritePolicies BriteClaims
BriteBilling BriteQuoteBriteLines
• Events: Event publication with job association
• Messaging: Pub/Sub with topics and retry logic
• Search: Allow events to be easily filtered, queried, and watched
• Service Discovery: Register services and determine health
• API Brokerage: Middleware layer to broker and translate APIs
20. BriteAuth BriteHubBriteDocs
BriteDrive BriteRules BriteData
BriteTasks BritePrint BriteContacts
BriteApps BritePolicies BriteClaims
BriteBilling BriteQuoteBriteLines
• HTML Templating: Edit HTML templates for documents with syntax highlights
• PDF Templates: Import PDF templates, mapping inputs with data points
• Relationships: Supports Inheritance and includes
• Data Browser: Introspect the data model for initiating service
• Rendering: Outputs rendered PDFs from templates
21. BriteAuth BriteHub BriteDocsBriteDrive
BriteRules BriteData
BriteTasks BritePrint BriteContacts
BriteApps BritePolicies BriteClaims
BriteBilling BriteQuoteBriteLines
• Storage: Online storage for documents and files
• Organization: Organize files and folders with unlimited depth
• Indexing: Automatic association with records and document templates
• Permissions: Granular or rules-based permissions restrict access
• Sharing: Open files and folders to remote services
22. BriteAuth BriteHub BriteDocs
BriteDrive
BriteRules
BriteData
BriteTasks BritePrint BriteContacts
BriteApps BritePolicies BriteClaims
BriteBilling BriteQuoteBriteLines
• Rules Engine: Enterprise business rules engine for decision making
• Conditions: Conditions based on any supplied record facts
• Consequences: Consequences route to API endpoints
• Capacity: Supports millions of rules combinations quickly
• Chaining: Supports forward and backward chaining
23. BriteAuth BriteHub BriteDocs
BriteDrive BriteRules
BriteData
BriteTasks BritePrint BriteContacts
BriteApps BritePolicies BriteClaims
BriteBilling BriteQuoteBriteLines
• Data Warehouse: All services write data to the warehouse
• Stock Reports: NAIC stock reports built from warehouse
• Custom Reports: Custom report definitions through interface
• Schedules: Automatically run and deliver reports
• Dashboards: Graphics dashboards connected to reports
• Exports: Direct export of warehouse tables
24. BriteAuth BriteHub BriteDocs
BriteDrive BriteRules BriteData
BriteTasks
BritePrint BriteContacts
BriteApps BritePolicies BriteClaims
BriteBilling BriteQuoteBriteLines
• Tasks: Tasks support owners, topics, comment threads, lists, templates, dates
• Automation: Tasks generated from rules or events
• Queues: Sorted user queues
• Load Balancing: Task assignments distributed by load
• Reassignment: Bulk reassignment for sick days, vacations, and terminations
25. BriteAuth BriteHub BriteDocs
BriteDrive BriteRules BriteData
BriteTasks
BritePrint
BriteContacts
BriteApps BritePolicies BriteClaims
BriteBilling BriteQuoteBriteLines
• Queue: Review queue sorted dynamically prior to release
• Drivers: Support for standard single or duplex print drivers
• Trays: Assign pages or document types to trays
• Exceptions: Exception processing such as silence, print now, email, etc.
• Delivery: View log of delivery status for success or failed print jobs
26. BriteAuth BriteHub BriteDocs
BriteDrive BriteRules BriteData
BriteTasks BritePrint
BriteContacts
BriteApps BritePolicies BriteClaims
BriteBilling BriteQuoteBriteLines
• Contacts: Generalized contact management and data model
• Roles: Assigned roles with data model extensions
• Configurable: Configurable data elements
• Associations: Relationships between contacts and modules
• Aggregation: Centralized aggregation of events, messages, and records
27. BriteAuth BriteHub BriteDocs
BriteDrive BriteRules BriteData
BriteTasks BritePrint BriteContacts
BriteApps
BritePolicies BriteClaims
BriteBilling BriteQuoteBriteLines
• Self-Service: Policyholder self-service platform
• Deployment: Deployed via web, mobile web, and mobile app
• Integration: Inquiry for policies, claims, billing, and drive
• Message Center: Manual and automated push notifications
• Payments: One-time and recurring EFT and credit card payments
• Printing: Replace paper delivery with full electronic delivery
28. BriteAuth BriteHub BriteDocs
BriteDrive BriteRules BriteData
BriteTasks BritePrint BriteContacts
BriteApps
BritePolicies
BriteClaims
BriteBilling BriteQuoteBriteLines
• Facts: Enter and version policy facts such as risk schedules and details
• Rating: Rate against policy facts using high performance rating
• Underwriting: Enforce underwriting rules against policy facts
• Distribution: Quote, bind, submit with interactive underwriting
• Endorsements: In and out of sequence endorsements with diff highlighting
• Renewals: Process and schedule renewals, cancellations, reinstatements, etc.
29. BriteAuth BriteHub BriteDocs
BriteDrive BriteRules BriteData
BriteTasks BritePrint BriteContacts
BriteApps BritePolicies
BriteClaims
BriteBilling BriteQuoteBriteLines
• FNOL: First notice of loss with dynamic templating
• Claim facts: Loss facts with dynamic types
• Diary: History of claims activity
• Loss Accounting: Reserves, payments, and recoveries
• Authority Limits: Authority limits with automated task generation
• Loss Events: claims aggregated into loss events for large schedules
30. BriteAuth BriteHub BriteDocs
BriteDrive BriteRules BriteData
BriteTasks BritePrint BriteContacts
BriteApps BritePolicies BriteClaims
BriteBilling
BriteQuoteBriteLines
• Ledger: Ledger of debits and credits on policy
• Payments: Electronic and manual payments with bulk and sweep payments
• Account Bill: Aggregate billing across multiple policies
• Direct Bill: Automatic billing directly to policyholder
• Agency Bill: Batch billing through agency integrations
• Equity Bill: Earned and pay-as-you-go
31. BriteAuth BriteHub BriteDocs
BriteDrive BriteRules BriteData
BriteTasks BritePrint BriteContacts
BriteApps BritePolicies BriteClaims
BriteBilling BriteQuote
BriteLines
• Products: Define data model for insurance products
• Rating: Rating calculations and processing
• Rules: Matrix and complex underwriting rules
• Forms: Forms management for products including templating options
• Versioning: Product, rate, and rule versioning
• Inheritance: Data models can inherit from other data elements
32. BriteAuth BriteHub BriteDocs
BriteDrive BriteRules BriteData
BriteTasks BritePrint BriteContacts
BriteApps BritePolicies BriteClaims
BriteBilling
BriteQuote
BriteLines
• Agent Quoting: Generalized wizard for agent quoting
• Customization: Custom templates and workflows
• Straight-through: Straight-through processing for automatic issuance
• Enforcements: Hard, soft, and authority-based rule enforcements
• Versioning: Allow multiple versions of policy quotes
• Endorsements: Quote and submit mid-term endorsements