Pegasystems Inc. · NASDAQ:PEGA

Pegasystems — PegaWorld iNspire 2023

30 slides from Pegasystems's conference presentation, 2023

  1. Slide 1: Enterprise Low Code in a Modular Landscape: How Rabobank Builds for the Future with Pega

    Enterprise Low Code in a Modular Landscape. How Rabobank Builds for the Future with Pega Ralph van de Rijt – Tech Lead, Rabobank Vincent Pijpers – Business Architect, Rabobank Paul Barnes – Sr Director Business Excellence, Pega © 2023 Pegasystems Inc.

  2. Slide 2: Pega is Being Used Differently Today

    Pega is Being Used Differently Today Microservices, low code, cloud, generative AI and mature tooling are accelerating this change CRITICAL Trending towards more agile apps Automate Automate Act Decide Decide ENTERPRISE UNGOVERNED GOVERNED LOB APPS GRADE COMPLEXITY Personal apps “Citizen / configura

  3. Slide 3: Guiding Principles for Modern Enterprise Reuse in Pega

    Guiding Principles for Modern Enterprise Reuse in Pega Build the blocks, assemble the blocks Interoperable Leverage the same building blocks across authoring experiences, and across applications Updateable Build the “blocks” Seamlessly update individual building blocks without impacting overall appl

  4. Slide 4: Example

    Example Customer journey [applications] Launched directly from the online banking website and application. They represent a request a customer would make Microjourneys [applications] Complex service Launched as part of another customer Change address Apis & Fulfil request request streaming journey a

  5. Slide 5: Guiding Principle Benefits

    Guiding Principle Benefits BUILD AND ASSEMBLE BLOCKS LEVERAGE CONSISTENT EXPAND RESOURCE POOL WITH A MODULAR MINDSET FIELD BEST PRACTICES BASED ON STRATEGY • Build business function blocks • Consistent approach focused on • Pro Dev Low Code experience to in Dev Studio encapsulation and extensibility

  6. Slide 6: It's Never Too Late to Improve Your Reuse Practices!

    It’s Never Too Late to Improve Your Reuse Practices! How to start adopting this approach • Should you throw away you existing framework architecture immediately and adopt this architecture? You can, but we wouldn’t recommend it • Instead, consider how your existing stacks can be broken down – If you

  7. Slide 7: faba

    faba aa

  8. Slide 8: Rabobank at a Glance

    Rabobank at a Glance Situation on June 30, 2022 Our mission Growing a better world together Almost 9.6 million customers 8.9 million Dutch customers 0.7 million international customers Rabobank in the Netherlands What we offer in the Netherlands Domestic Retail Banking (amounts in EUR billions) Dutc

  9. Slide 9: A Cooperative Bank with a Mission

    A Cooperative Bank with a Mission Growing a better world together Food transition Climate & energy transition Transition to a more inclusive society Banking4Food Sustainable Sustainable Energy Financially entrepreneur- living transition healthy living ship Together with partners, ensure Stimulate su

  10. Slide 10: Wholesale & Rural Clients

    Wholesale & Rural Clients W&R is structured as a matrix with global business lines and presence in five regions 10

  11. Slide 11: Rabobank Group Also Delivers International Services via DLL

    Alongside W&R, the Rabobank Group Also Delivers International Services via DLL, with Vendor Finance Solutions in More Than 30 Countries 11

  12. Slide 12: Some history

    aa, Some history PegaWorldiNspire

  13. Slide 13: Background: Context of Pega at Rabobank

    Background Context of Pega at Rabobank Transaction ZRF Vendor finance RANZ monitoring Payment exception and investigation Special asset solution for management to automating and support customers CDD for complex Case management streamlining in times of onboarding in the for sales & service investiga

  14. Slide 14: Some architecture

    Some architecture 14

  15. Slide 15: From WFM Monoliths to Decoupled Architecture

    From WFM Monoliths to Decoupled Architecture Original situation Target situation Journeys Forms …. WFM 2 Banking services Siebel Custom (CRM + build java WFM) WFM 1 WFM Integration monolith Technology platform Core infrastructure services (mainframe, serverparcs etc) 15

  16. Slide 16: From WFM Monoliths to Decoupled Architecture

    From WFM Monoliths to Decoupled Architecture Original situation Target situation Journeys Forms …. WFM 2 Banking services Siebel Custom (CRM + build java WFM) WFM 1 WFM Integration monolith Technology platform …. Pega Cloud Core infrastructure services (mainframe, serverparcs etc) Cloud platform (Az

  17. Slide 17: From WFM Monoliths to Decoupled Architecture

    From WFM Monoliths to Decoupled Architecture Original situation Target situation Journeys Forms …. WFM 2 Banking services Customer … Onboard new clients Siebel Custom verification (CRM + build java WFM) WFM 1 WFM Customer …. Accept & sign service recognition Integration monolith Technology platform

  18. Slide 18: From WFM Monoliths to Decoupled Architecture

    From WFM Monoliths to Decoupled Architecture Original situation Target situation Journeys Forms Pega orchestrated … … customer journeys …. WFM 2 Banking services Customer … Onboard new Clients Siebel Custom verification (CRM + build java WFM) WFM 1 WFM Customer …. Accept & Sign service recognition I

  19. Slide 19: Technology Integrations

    Integrations Each layer has its own characteristics and needs its own strategic choices Integrations on enterprise level Technology platform • Kafka connection for async communication Pega Coud • OneIdentity (Azure AD), to enable both SSO and all other authorisations • Splunk connections for operati

  20. Slide 20: Technology Integrations

    Integrations Each layer has its own characteristics and needs its own strategic choices Banking services …. Onboard new clients Integration on business service level • API’s exposed via Kong api gateway for sync communication Customer Accept & sign service recognition • Additional Splunk connections

  21. Slide 21: Technology Integrations

    Integrations Each layer has its own characteristics and needs its own strategic choices Integrations on customer journey level • DX API connected via our own interpreter to our frontend system • Offload data to our Global Data Platform Journeys Pega orchestrated journeys • Utilize API’s via Kong api

  22. Slide 22: How Pega Applications are Decentralized on Pega Cloud

    How Pega Applications are Decentralized on Pega Cloud Pega Cloud platform 22

  23. Slide 23: How Pega Applications are Decentralized on Pega Cloud

    How Pega Applications are Decentralized on Pega Cloud Deployment zones Stack A Stack B Customer Business Customer Business Journey X Service A Journey Y Service B Pega Cloud platform Stack Application 23

  24. Slide 24: How Pega Applications are Decentralized on Pega Cloud

    How Pega Applications are Decentralized on Pega Cloud Deployment zones Stack A Stack B Stack A Stack B Shared repository Party Integration Integration API / Kafka v1 API / Kafka Integration API / Kafka Customer Publish Customer Business Business Reusable Reusable Journey X Service A Journey Y Servic

  25. Slide 25: Some governance

    Some governance 25

  26. Slide 26: Delivering Awesome Software with Pega!

    Delivering Awesome Software with Pega! Component Re-use any component we create to maximize Component strategy Ownership in quality speed and prevent re-inventing the wheel. Autonomous teams Engineering culture strategy Coordinate with other squads to prioritize needed changes Ownership in Every squ

  27. Slide 27: Guild Structure

    Guild Structure Formed for knowledge sharing, best practices, and agreements on collaboration Monthly Pega chapter meeting Testing/QA Guild Monitoring Guild DX Guild Overarching LSA Guild LSA Guild LSA Guild LSA Guild Drivers in the Guilds are key in CRM Squad Squad 4 Squad 4 Squad 2 Squad 2 Squad 4

  28. Slide 28: LSA Guild(s)

    LSA Guild(s) LSA Overarching LSA Guild LSA LSA LSA Some numbers LSA LSA LSA LSA LSA (Pega Cloud only) 4 domains Tribe Tribe Tribe (tribes) LSA LSA LSA 9 Areas LSA LSA LSA LSA LSA LSA 40 squads 320 engineers Area 1 Area 2 Area 3 Area 1 Area 2 Area 3 Area 1 Area 2 Area 3 28

  29. Slide 29: Outcomes of a Modular Enterprise Landscape

    Outcomes of a Modular Scalability Enterprise Landscape The guild structure makes our organisation scalable Resiliency ~3M+ Euros annual Roles are more interchangeable, reducing key- savings in person risk and bottlenecks development costs Collaboration ~2x-3x faster speed to Forces documentation and

  30. Slide 30: {\SABRRREEE an

    {\SABRRREEE an \\ SE ww a se PEGA PegaWorldiNspire Rabobank

Pegasystems — PegaWorld iNspire 2023 on 6ix