Description: Proposal operates in a standardized technical environment within department guardrails and standards Scoring Guide: 0 = Creates an exception to established standards 1 = Adds to complexity but supports standards 2 = Supports standards. No impact on complexity 3 = Reduces complexity using a CI/CD pipeline supporting standards 4 = Reduces complexity of IT environment using a shared CI/CD pipeline impacting multiple systems/components while supporting standards WHY GC Enterprise Architecture Framework https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework Design for performance, availability and scalability ensure response times meet user needs, and critical services are highly available support zero‑downtime deployments for planned and unplanned maintenance use distributed architectures, assume failure will happen, handle errors gracefully, and monitor performance and behaviour actively establish architectures that supports new technology insertion with minimal disruption to existing programs and services control technical diversity; design systems based on modern technologies and platforms already in use Follow DevSecOps principles use continuous integration and continuous deployments ensure automated testing occurs for security and functionality include your users and other stakeholders as part of the DevSecOps process, which refers to the concept of making software security a core part of the overall software delivery process GC Enterprise Architecture Framework https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework Design for Interoperability design systems as highly modular and loosely coupled services expose services, including existing ones, through APIs make the APIs discoverable to the appropriate stakeholders Enable Interoperability expose data and functionality through service interfaces applications must communicate with each other via those interfaces services interfaces must be published and discoverable