BDM Architecture Principle 12: Principle: Maximize Use of Core Technology Statement: Consider leveraging capabilities and functionality of the Core Technology (Cùram Social Program Management) before considering other solutions and applications for common benefit processing and service delivery. Rationale: Leveraging investment in the platform and making use of OOTB business logic and processes will greatly improve ESDC agility and ability to implement new benefits and implement changes to existing benefits and processes. Additionally, this will reduce complexity of implementation and cost of ownership minimizing the need for integration with other dependant applications. Implications: • Business may have to accept that not all requirements will be fully met by the Core Technology solution. • Design of some future state business processes may need to be adjusted to leverage OOTB business logic and processes. • Evolving business needs may require moving away from specific capabilities of the Core Technology solution in the future. This situation would trigger changes in architecture, transition to either specialized best of breed or enterprise solutions and possibly procurement. Principle #11: Architecting for Agility mitigates this implication. • Core Technology solution architecture becomes the architecture for the Common Benefit Delivery Platform. • Enables alignment of the BDM solution evolution and improvements with the Cùram Social Program Management product roadmap and plans for future improvements. • Supports an MVP approach. • Caveat: Increased risk of vendor lock-in. BDM EA WG: The remaining principles would lead to the same conclusions and outcomes. The principle is redundant. Curam Capabilities Prototype did surface and supports the principle. Recommendation: Consult BDM ARC