OCTO Agile Enterprise Team Higher achievement through better business/technology alignment

Crossroads  Widespread adoption of uniform technology architecture addresses many District business challenges High-level vision is defined by CTO and Enterprise Architect However, path from high-level enterprise architecture vision to actual implementation is unclear  CAPStat (DCStat) Service-oriented Architecture (SOA) implementation is realization of architecture vision While an essential enabler, enterprise SOA isn’t core CAPStat value proposition New projects are underway that appear compliant, but are in fact non- conforming systems  District is slipping backward toward ‘accidental architecture’

Urgent Need  Agencies are sponsoring technology programs  These programs are underway… CAPStat Accountability Sessions EOM Fusion Center DCRA CPMS MPD LEIMS & RMS NCRI DEH  …and are diverging—rather than converging—architecture Redundant SOA services are now in production Disconnected ESB infrastructure instances are now online Incompatible and incomplete information is now published Requests by agencies for support and guidance are unanswered Regional project is proceeding without District specifications

OCTO leadership  Initiative: Create new Agile Enterprise Team  Mission: Provide guidance, governance and access to coordinated enterprise-level information and technology resources that promote District business goals  Strategy: Encourage and support agency-sponsored, conforming development initiatives Examine projects in the pipeline and identify application components with business cross-function capability Guide and coordinate agencies as they build processes and systems that align with customer needs Coordinate and provide governance on enterprise-level standards Administer and provide access to shared SOA infrastructure assets Promote development approaches that enable efficient reuse of component services Promote enterprise integration practices that increase information portability and opportunities for exchange Negotiate licensing terms favorable to the District for enterprise solutions

Services provided  Architecture design, review and education  Design and govern Information Model (ontology, vocabulary, schema, namespace, metadata)  Administer ESB domain and nodes  Administer component services (registration, provisioning, security, monitoring)  Software service development assistance/education (asynchronous model, content-based routing)  Note: CapStat EDW and Business Objects are expected to go to separate Data Warehouse program

Benefits  District Agencies Agility and improved services through business-aligned systems Teams empowered to deliver reliable systems more quickly and at lower cost Create new business processes and composite applications from existing services Access continually-expanding, timely information library Access as a service to established enterprise assets (e.g.; search, alerts, messaging, ERP, SMP) Assistance implementing OCTO-specified technology standards  CAPStat Program Fast access to more agency-published information Factor several enterprise-level responsibilities out of program More developers building reusable component services  OCTO Increase reuse of assets (e.g.; share common systems, component software services) Strategy and approach to incrementally implement SMPs Incremental, immediate benefit realization rather than rip & replace Extend life and versatility of existing assets Reduce risk of project failure Lower costs through more efficient licensing Maximum ROI on CAPStat accomplishments and knowledge capital

Resource reassignments  Staff Program manager/SOA architect Enterprise architect Analyst/project manager Sonic ESB administrator Enterprise Information modeler/developer SOA developer  Assets Sonic Enterprise Service Bus (ESB) FAST Data Search Access to CAPStat development environment TeleLogic

Next steps  Organize OCTO’s strategic enterprise architecture personnel resources and technology assets into one Agile Enterprise team  Rebrand ‘DCStat Architecture’ and develop ‘SOA franchise model’ to promote rapid, coordinated adoption across agencies  Form ‘advance team’, immediately engage with MPD, DCRA & EOM projects and support according to need  Develop formal agency working groups and provide representation to NCRI technical board  Establish plan to amplify learning through sharing guidelines, methodologies, processes