1. Page 1 Virginia e-WIC Kick-off Meeting June 14, 2011

2. Page 2 Agenda – Day 1 – AM TimeTopicFacilitator 10:00 – 10:15Welcome  Opening Comments Facilitator: 10:15 – 10:30Introductions 10:30 – 11:45Solution Overview  EPPIC e-WIC Solution Overview  Network Solution Overview  Account Setup Overview  Retailer Settlement Overview Facilitator: 11:45 – 12:00Break/Pickup Box Lunches Working Lunch 12:00 – 1:15 12:00 – 12:45Project Overview  Summary of Project Objectives  Summary of Scope  Project Success Criteria and Benefits  Role Definition  Communication Structure  Retailer Enablement Facilitator:

3. Page 3 Agenda – Day 1 – PM TimeTopicFacilitator Working Lunch 12:00 – 1:15 12:45 – 1:15Project Timeline  Wall Walk Facilitator: 1:15 – 3:00Project Management  Critical Assumptions, Risks, & Dependencies  Deliverable Submission  Review Cycles  Acceptance Criteria  Milestones and Deliverables  Change Management Process Overview Facilitators: 3:00 – 3:15Break 3:15 – 3:45Requirements Validation and Methodology  Requirements Process  Requirements Validation Sessions  Requirements Management Methodology  Artifacts Facilitator: 3:45 – 4:15ACS Test Methodology  Overview Facilitator: 4:15 – 4:45Wrap up  Upcoming Events  Decision Points  Takeaways Facilitator:

4. Page 4 ACS Senior Vice President and Managing Director ACS, a Xerox Company State Enterprise Solutions (SES) Opening Comments

5. Page 5 Introductions Senior VP and Executive Director Vice President Government Solutions Director Card Services Program/Project Manager Implementation Manager Product Manager WIC SME Technical Coordinator Electronic Payment Services Delivery Center Payment Services Group Delivery Center Electronic Payment Group Delivery Center – Technical and Operations Team ACS Corporate Oversight Retail Manager Technical System Lead TBD Deputy Program Manager System Test Mgr

6. Page 6 Solution Overview ACS Technical Coordinator

7. Page 7 Project Overview ACS Program/Project Manager

8. Page 8 Summary of Project Objectives In parallel with the implementation of the new Crossroads MIS system, replace the current paper-based method of issuance and redemption with a leading edge online e-WIC system that allows participants more flexibility with their shopping experience while reducing the stigma typically associated with paper checks. – Coordinated development of e-WIC system and the Crossroads MIS system – Develop the proper interfaces and provide technical services to support Virginia e-WIC – Integrated testing and implementation with the Crossroads MIS system – Retailer enablement, integration and certification – Compliance with the Technical Implementation Guide, Operating Rules and Universal Interface Specification

9. Page 9 Summary of Project Scope Virginia e-WIC In scope System Requirements, Business Requirement Document, Interface Control Document and Functional Specification Document Development of real-time interfaces with the Crossroads MIS system User Acceptance Testing (UAT) training and support Train the Trainer training and support Coordinated training with Crossroads team Commonwealth staff training for reports and administrative terminal Automated Response Unit (ARU) training and participant training materials Retailer enablement Stand beside POS installation and training Retailer integration support Third Party Processor (TPP) retailer support for Kentucky shared retailers Pilot implementation and full e-WIC project rollout support Ongoing operation of the e-WIC system

10. Page 10 Project Success Criteria and Benefits Success Criteria: – Successful requirements and design documents approval – Successful completion of UAT approved by Virginia Department of Health (VDH) and USDA Food and Nutrition Services (FNS) – Successful pilot – Successful full e-WIC project rollout Expected benefits: – Seamless integration with Crossroads MIS system – Flexibility in benefit redemption for participants – Reduced stigma for participants – Improved transaction processing for retailers – Stronger reporting capabilities – Improved agency and clinic efficiency allowing a greater focus on nutrition education

11. Page 11 Project Roles RoleAssigned ToAssignment Specifics ACS Program/Project Manager Single point of contact for VDH Customer-facing delivery management role that ensures the contract obligations are tracked and customer relationships are maintained. Primary contact and manager of deliverables submitted to VDH as well as coordinator of all meetings with VDH. Works closely with VDH Project Managers. ACS Technical Coordinator Participates in kickoff meeting as Technical Coordinator representing ACS as technical Subject Matter Expert and primary technical resource. Technical lead and facilitator of the Requirements Validation sessions (RV). Ongoing primary technical resource and subject matter expert for project. ACS Implementation Manager Develops, Maintains and Tracks the overall technical project plan from project initiation through project implementation completion. Major activities include resource management, schedule management, cost management, critical path management, quality management, risk management, issue management and action management.

12. Page 12 Project Roles (cont.) RoleAssigned ToAssignment Specifics ACS Business Analyst Owner/lead of the Requirements Phase and Processes. Ensures RFP Requirements are captured, validated and refined into Business Requirements and Functional Specifications/Technical Requirements. Works closely with the Implementation Team Manager to ensure requirements issues are addressed and resolved timely, and that review/approval timelines are agreed upon to ensure timely completion of the requirements phase and start of development. ACS Product Manager Ensures definition of the strategic content of the product. WIC Subject Matter Expert, will support project kickoff and Requirements Validation Sessions with the Commonwealth. Will engage in requirements reviews as needed. Ongoing resource for project. ACS Retail Manager Leads retailer enablement efforts. Will manage scheduling and installation efforts of e-WIC point of sale devices. Coordinates retailer meetings.

13. Page 13 Communication Structure ACS Program/Project Manager VDH Project Manager Sylvia Mitchem ACS Business Analyst ACS Implementation Mgr ACS Technical Coordinator VDH EBT Coordinator Natasha Miller Primary communicator with VDH: Deliverable delivery VDH review communications Project status Risk, Issue, Action tracking All VDH/ACS meeting content, agendas, minutes Status Risks, Issues, Actions Requirements Validation, Requirement Deliverables, and clarifications / questions Requirements Validation Facilitator Technical resource Solution expert Virginia Department of Health

14. Page 14 Retailer Enablement ACS works with retailers to provide a solution that best meets their needs Coordinated efforts by ACS with retail service providers and third party processors provide many retailers with the option of integrating with their existing system Direct connect POS devices and an integrated direct connect option provides savings to retailers that choose those options Retail Manager, Ed Yorkavich coordinates enablement efforts and provides strong support for retailers The Retailer Portal provides instant access to transaction and settlement reports 24/7 retailer helpline is provided to answer questions and/or troubleshoot issues Integration support for testing and certification. Currently certified with several TPPs and Electronic Cash Register (ECR) systems. Retailer Benefits Faster settlement, usually within 24 hours System approves only prescribed WIC items (fewer errors) Fewer administrative tasks i.e., no batching paper, no retailer stamps, no rejected checks Reduced risk of non-compliance and/or program violations Reduced training for personnel, less time to train cashiers

15. Page 15 Project Timeline ACS Implementation Manager

16. Page 16 MayJuneJulyAugSeptOctNovDecJanFebMar SEEPPR Project Planning RV BRD ICD Use Cases Report Specs SDRDDRTRR VA WIC (Crossroads) Development/System Testing Retailer/TPP Certification FNS Cert IVR Call Flow Updates IVR DevelopmentSetupIntegration Testing CSI Call Flow Approvals Retailer Outreach (i.e. survey and pre-cert efforts) RAPS/AIMS Requirements and DesignRAPS/AIMS Testing and Deployment Call Center Training - Retailer/Client Install/Train Pilot POS Deploy CSI solution Kickoff Meeting Commonwealth Approvals Retailer Call Center Go Live Project Toll Gates VA WIC (Crossroads) Req. / Design IVR Planning Siebel DesignSiebel DevelopmentUnit TestIntegration Testing Networking Hardware & Telecom Installation and Testing Siebel BRD / ICD / Use Cases Approval of Final Design Approval of Final Test Plans Approval of Final Test Plans Design Test PlanningSystem TestingRegression Testing Development, Unit Test, Integration Test Crossroads / EPPIC Integration Testing VA WIC Wall Walk PSG LOB CSI EPS

17. Page 17 VA WIC Wall Walk (cont.) 2012MarAprilMayJuneJulyAugSeptOctNovDec PRR Client OutreachClient Call Center Go-Live Retailer Outreach Pilot Operations Statewide Operations PCRORR Install/Train State POS (Stand-Beside) User Acceptance Testing and Report Validation PSG LOB CSI EPS UAT / Pilot Support

18. Page 18 Project Management ACS Program/Project Manager ACS Implementation Manager

19. Page 19 Critical Assumptions VDH will ensure coordination with Crossroads team for support of design, development and test phases (Crossroads integration) VDH will ensure coordination with Crossroads team to review ICD documents as applicable VDH will provide UAT test data Deliverables will be approved according to agreed upon review cycles Approvers will be named, available, and participating as needed Assigned VDH Staff will be available and coordinate with the Crossroads team when required by the work plan VDH is responsible for gathering and providing feedback on requirements from FNS to ACS. The timeline must include any review by FNS if content is expected to be included in the baselined requirements.

20. Page 20 Dependencies on VDH Infrastructure Review PC for Administrative Terminal FTP Server Firewall Setup/Configuration VDH Data Center for circuit installation Router (ACS will assist with setup) IT Telecom Questionnaire (ACS to provide) Outreach to clinics, cardholders, government offices and officials Timely review and approval of deliverables as outlined in the work plan User Acceptance Testing support

21. Page 21 Risks Inherent schedule flaws due to unknowns prior to entering each phase Increase in requirements during Plan and Design Change in project assumptions and/or requirements Extended review and approval of deliverables Concurrent development cycle with Crossroads Additional Modifications to Universal Interface Specifications, WIC Operating Rules and Technical Implementation Guide

22. Page 22 Deliverable Submission Document Submission: – Document will be delivered by the BA to the ACS Program/Project Manager for submission to the VDH e-WIC Project Manager – Document will be delivered via email – Document will include the name of the document followed by v.0x DRAFT to indicate that it is a draft document under review – Document revision history will reflect the date, author and relevant notes when submitted – Document will be submitted by end of the day ’12-midnight’ according to the deliverable milestone ‘day’ agreed to that triggers the review cycle – Midpoint through a review cycle, the ACS project team or VDH may request or agree to a review to discuss any questions or critical feedback as to not delay any initial understanding of the document or impact the remaining assumptions during the review

23. Page 23 Proposed Review and Approval Cycles Requirement Deliverables – 10/5/2 Initial 10 day Commonwealth review (BRD, ICD’s and larger documents) 5 business day ACS BA review/doc update 2 days of final review and Commonwealth approval/sign off – 5/2/2 (Functional Specs, Screen Mock-Ups, Report Specs etc) Initial 5 day Commonwealth review 2 business day ACS BA review/doc update 2 days of final review and Commonwealth approval/sign off

24. Page 24 Acceptance Criteria Acceptance suggestions: – Approved ‘as is’ (no updates required) – Approved with minor modifications (no major issues, open items) – Not Approved – Scope or major issues identified, update and re-review required – Acceptance/Approval is requested to be via email approval from the approvers identified during Requirements Validation. – The above assumes all comments from both Commonwealth and FNS are obtained in the acceptance. Commonwealth is responsible for gathering and providing FNS’ comments, or acting as the ‘proxy’ approver in their acceptance – Acceptance/Approval should be focused on material requirements content and questions related to completeness, validation and accuracy related to system functionality as discussed/agreed to during Requirements Validation etc. Grammatical or other minor corrections/agreed upon updates should not prevent a document from being accepted/approved.

25. Page 25 Sample Review Form Review Details Document Name: [Specify Document Name] Page #Section Review CommentAction (to be completed by BA) Document Updated/Resolution? Document Name: [Specify Document Name]

26. Page 26 VA e-WIC Deliverables Milestone Schedule

27. Page 27 VA e-WIC Deliverables Milestone Schedule (cont)

28. Page 28 VA e-WIC Deliverables Milestone Schedule (cont)

29. Page 29 Change Management Overview The Change Management Process is a systematic approach to managing impact to cost, scope, schedule, and quality during a project – Requests for changes to any approved item will be managed via the Change Management process VDH submits Change Request to ACS Project Manager ACS performs Impact Assessment on Change Request ACS submits and reviews Impact Assessment with VDH VDH either approves or rejects the Change Order May be submitted by VA e-WIC Project Manager or other preset arrangement Standardized process utilized to determine cost, schedule, and other impacts to the project Results of Impact Assessment provided to facilitate VDH decision on Change Request If approved, the project baseline is revised – if rejected, the Change Request is closed

30. Page 30 Requirements Validation Sessions & Requirements Methodology Overview ACS Implementation Manager

31. Page 31 Requirements Process – A Closer Look Value & Goals of the Requirements Workshop & Requirements Phase The BA role & SME expectations Requirements Methodology & Management Process Artifacts, Reviews/Inspections & Approvals

32. Page 32 Methodology Value Points 1. Represents Industry Best Practices/Standards and CMMI Advancement Goals 2. Methodology has been proven through reduction of missed/invalid requirements by approx. 50% in the last 1.5 years in various EPS Client Implementations 3. Supports Upfront Quality and Ongoing Requirements Validation throughout the Requirements Phase 4. Supports Incremental Development and Testing more seamlessly 5. Allows for more contained and shorter client stakeholder review/approval timeframes

33. Page 33 Requirements Validation Sessions & Requirements Phase Goals To define ‘the what?’ To validate critical requirements/system functionality and any ‘gaps – enhancements/detailed rules etc’ to existing functionality To clearly identify Open Issues/Follow Up items with accountable owners and due dates that impact resolution of requirements To ensure completeness, accuracy and agreement of business ‘system’ requirements gathered across key ACS and VDH stakeholders and SMEs that will be designed, developed and delivered in the final solution that meets The Commonwealth’s business needs and objectives

34. Page 34 Artifacts – Gap Analysis : Documentation of gaps and further details refined from the RFP and based on WIC core product solution from the Requirements Sessions Note: This is not an approved document, but captures Validated Req’s, Actions, and Open Items that may require further discussion. – Interface Inventory – Teams identify all ICDs, systems, and frequency. This is an inventory only that goes in the BRD. – BRD – Business Requirements Document, Represents High Level Functional and Non-Functional System Requirements and Interfaces. (NOTE: it does not include operational requirements)  VALUE: the BRD is the document that locks down the ‘system scope’ of the project. BRD Inspection: Review and approval/sign off from key Commonwealth and ACS stakeholders. Once approved by the Commonwealth and ACS Technical team, it is base-lined as Version 1.0.

35. Page 35 Artifacts – Detailed Requirements : ICD’s, Report Specifications and Functional Specifications including: Use Cases, Business Rules, Screen Mock-Ups, Data Fields, Error/Dialog Message, Report Specifications (traced to higher level business requirements in the BRD)  VALUE: These are the artifacts that Development, Quality Assurance (QA), and UAT teams design, develop and write test and UAT scenarios from, thus it is critical these are correct, to ensure quality delivery and what is expected of the client. Detailed Requirements Inspection: Review and approval/sign off from key Commonwealth and ACS stakeholders; Identified documents are baselined as Version1.0 once approved by Commonwealth and ACS Technical teams.

36. Page 36 Artifacts Requirements Traceability Matrix (RTM): – Traces Requirements from RFP to BRD, Detailed Specifications, Design Documents and Test Cases. RTM: Updated as each deliverable artifact is completed, reviewed, and baselined by ACS, This document can be provided to the Commonwealth as a tool to reference requirements from the BRD to their locations in other documents. Note: This is not a formal deliverable and thus is not subject to formal review/approval.

37. Page 37 Commonwealth SMEs Availability & Time Allocation Requirements sessions and the requirements phase of the project require a high concentration of time and attention by all critical subject matter experts and reviewer/approver stakeholders WIC Policy/Operations SME: provide subject matter knowledge, documentation and validation of the Commonwealth’s operational process and the related functional requirements and/or gap details and rules to ensure requirements gathered are accurate Technical SME: provide information to ACS technical team for technical functionality, such as file transfer management, non-functional requirements, and other technical requirements to fulfill the project Assumptions: – Assigned VDH Staff will be available when required by the work plan. – Approvers will be named, available, and participating. – Time allocation historically has shown that reviews and collection of feedback may take anywhere between approx. 4 – 10 hours a week during the critical review cycle depending on the size of the document; i.e. a BRD review over 2 weeks may take 16 hours for review and approval.

38. Page 38 Wrap Up