1. Information Technology Division Executive Office for Administration and Finance Shared Application Infrastructure (SAI) Program Overview

2. 8/12/20152 Agenda Vision Open Source Roadmap Acquisition Approach

3. Vision and Goals Work collaboratively to develop shared infrastructure services that can be used by multiple agencies to support Service Oriented Architecture (SOA) applications Goals – Achieve efficiencies through reuse – Enable appropriate data sharing across agencies – Facilitate the implementation of modular system development – Develop agile, flexible infrastructure and systems – Implement effective cross-agency governance for shared infrastructure

4. Vision – Key Aspects Phased Approach – See Roadmap Organizational Impact – Establish SOA outreach & education program – Build organizational competency – Define governance and repeatable processes Plan for Scalability – Establish integration and interoperability specifications – Support federation requirements

5. 8/12/20155 Vision - High Level SAI Component Model* Enterprise Service Bus Adapters Multi-Channel End User Apps Reports &Analytics Service Registry/Repository Identity Management** Service Governance Business Services Service Orchestration Business Process Mgt (BPM) XML Aware Edge Device * Architectural pattern shared with MassTax2 RFR ** Rudimentary Implementation

6. Open Source – Enterprise IT Acquisition Policy For all prospective IT investments, agencies must consider as part of the best value evaluation all possible solutions, including open standards compliant open source and proprietary software as well as open standards compliant public sector code sharing at the local, state and federal levels.

7. Open Source – SAI Components Enterprise Service Bus – Progress Software (Iona) - Fuse ESB – JBoss – JBoss ESB – MuleSource – Mule – Sun Microsystems – OpenESB Registry/Repository – MuleSource – Mule Galaxy – Apache – jUDDI* Identity Management – Sun Microsystems – OpenDS and OpenSSO Service Governance – MuleSource – Mule HQ *Not clear if viable option – immature implementation

8. Roadmap

9. Acquisition Approach Phase 1 - RFI and RFQ(s) Issue RFI Establish baseline requirements Evaluate open source alternatives Issue RFQ(s) for necessary COTS solutions