1. CONNECT CCB Meeting May 16, 2012

2. Balancing current + future needs CONNECT needs to support the current 2012 production and operational needs of the Federal Partners and community. CONNECT needs to be positioned for the future operational, organizational and evolving Exchange needs as the open source community grows. CONNECT resources must balance: Sustainment and continued support for production Enhancement of CONNECT to support future requirements and operating model 2

3. Building Blocks to a Unified Track Supporting Sustainment and Evolution for CONNECT with a consolidated approach delivering a releasable product. Enhancing the current code base of CONNECT allows for increased synergy of resource investment. Modifying and refining the CONNECT code base while still leveraging certain components allows for benefits to be delivered near term while positioning CONNECT for the future. Scalability & performance improvements Modular code base to support code submissions Support for larger message payloads Simplify auditing & provide needed data Code improvements & technical debt removal Flexibility in tech stack options 3

4. CONNECT Future Functional Progression Approved by Transition Group/Partners, May 11 4 Adapter Current Functionality Progression Gateway * Current Functionality GlassFish Metro Apache CXF Open SAML Libraries for: GlassFish WebSphere WebLogic JBoss Large Payloads* Logging* Gateway Lighter Gateway Adapter Current Functionality Adapter Migrated Gateway Functionality** ** Optional until Adapter is modified Gateway Lighter Gateway Adapter Current & Migrated Functionality More Modular Architecture Adapter Community Adapter Adopter system feeds * Plus s coped in functionality from CCB

5. Proposed Next Release Package Enhancements and Deliverables 5 (#1)CONNECT adopters shall have the ability to increase the throughput targeting increased numbers of PD, QD, RD and DS transactions (GW-451) (#2)CONNECT adopters shall have the ability to run on additional application servers such as WebSphere and WebLogic to meet their environment needs (GW-453) (#3)CONNECT adopters shall have the ability to get more comprehensive performance logging and metric data (counts and duration) using improved logging in CONNECT (GW-472 and GW-1252) (#4)CONNECT adopters shall be able to determine the state of a transaction across messages in order to better troubleshoot and analyze the operation of CONNECT and their trading partners (GW-499) (#5)CONNECT adopters shall have the ability to exchange and process large payload sizes of up to 1 GB (GW-473) (#6)CONNECT adopters shall have the ability to minimize deployment load by supporting a lightweight gateway which allows smaller server footprint and use of system resources and allows the federal partners to maximize the use of their custom-built adapters (GW-1593) (#7)CONNECT adopters shall have the ability to provide a generic feed to their monitoring systems to assist with the notification of gateway performance (GW-452) (#8)CONNECT adopters shall be able to call a simpler interface (well defined API Adapter to Gateway) to integrate with CONNECT as quickly and as simply as possible (GW-1194) (#9)As a CONNECT user I need CONNECT to integrate with and support the DIRECT Project specifications (GW-860) Pre-CCB Proposed Scope Line for inclusion in the Next Release.

6. CONNECT Anticipated Release Plan CONNECT Development Contract Year Pending CCB Approval 6 Proposed Development During the Contract Year Next Release Next-next Release * Oct ’12 - Release candidate to IV&V * Dec ’12 – Available for Release Present Performance Improvements Platform independent framework Support WebLogic Support WebSphere Large Payloads Logging & Metrics Improvements Lightweight gateway * Feb ‘13 - Release candidate to IV&V * Mar ‘13 - Available for Release * Actual Dates TBD, depending on priorities, scope, team size and testing levels Performance Improvements Monitoring Tools Feed Simple Smart Adapter Direct Implementation

7. Platform Independence (5)** * OpenSAML (1) * ApacheCXF (1.5) Large Payload Support (3.5) Platform Independence (5)** * OpenSAML (1) * ApacheCXF (1.5) Large Payload Support (3.5) WebSphere (2) Separate lightweight gateway + adapter functionality (3) WebLogic (1) Logging + performance (1) May 7 Mar 29 Release Testing IV&V Round 1 Intervall for release readiness w/IV&V is TBD Next CONNECT Release CONNECT Development Progression Proposed Timeline – Pending CCB 7 Monitoring Tool Feed (3) Simple Smart Adapter (5) Monitoring Tool Feed (3) Simple Smart Adapter (5) IV&V Round 2 Release Testing IV&V Round 1 Interval for release readiness w/IV&V is TBD IV&V Round 2 Next-next CONNECT Release * Oct ’12 - Release candidate to IV&V * Dec ’12 – Available for Release * Feb ‘13 - Release candidate to IV&V * Mar ‘13 - Available for Release *Actual Dates TBD ** Estimated Sprints Dependent on priorities, scope, team size and testing levels

8. Sprint 83 – Guidance from May 11 th Transition Meeting CCB preparation + follow-up Release testing for 3.2.2 Add support for Apache CXF Transaction logging improvements Investigate support + options for large file transmission Reduce O&M backlog 8 Platform Independence * OpenSAML * Apache CXF * Large file Platform Independence * OpenSAML * Apache CXF * Large file

9. Additional Development Team Activities Code Improvements / Non-Functional Technical Debt Removal Partner and Community Support for 2.4.7, 2.4.8, 3.1, 3.2, 3.3 Support C&A Activities Support Community Outreach and Nurturing –Through blogs, forums, webinars, onsite support, code-a-thons, connectopensource.org, and the developer Wiki Development Process Improvements Transition Support 9

10. Questions and Discussion 10