My Florida Market Place User Meeting February 10

My. Florida. Market. Place User Meeting February 10, 2004

Agenda q Welcome and Introduction q Updated Deployment Approach / Agency Support q Release Schedule Planning Process / Change Request Process q Continue review of Agency Issues / Change Request Submissions q Next Meeting Time / Location 2

Agenda q Welcome and Introduction q Updated Deployment Approach / Agency Support q Release Schedule Planning Process / Change Request Process q Continue review of Agency Issues / Change Request Submissions q Next Meeting Time / Location 3

Updated Deployment Approach q February: Leverage User Meetings to review agency system issues / preferred system enhancements. q February 16 th – March 26 th: Conduct “Lab Sessions” that allow agencies to execute day to day business tasks and to gain additional comfort with My. Florida. Market. Place (focus being those agencies that are “in process” right now- DOE, FDLE, DEP, DOAH, DOC, HSMV, AHCA, DOR, AWI, FWC, DBPR, DOL, DCA, DMA, DOS). q March 1 st – March 26 th: Implement agency pilots of My. Florida. Market. Place with those agencies that express a desire to move forward with fielding activities prior to March release. q End of March: New system functionality included in March release (Release notes will be available to review specific changes included). q March 29 th – May 21 st: Implement My. Florida. Market. Place at agencies (focus being those agencies that are “in process” right now) q June: Conduct second round of Lab Sessions (focus being on agencies going live after July 6). q July 6 th – August 27 th: Complete the initiation of agency go-live activities. 4

Revised Operational Acceptance Test (OAT) Approach q q Will take the form of “Lab Sessions”: Ø Allows agencies to execute day to day business tasks and to gain additional comfort with My. Florida. Market. Place Ø Provides an overview of the system - but will primarily be self-paced using mock scenarios and scripts as well as agency-supplied transactions Ø Provides additional training opportunities / support for an agency’s users (within constraint of available seats and sessions offered) Sessions will occur in a central location with DMS and Accenture resources in attendance Ø Lab Session 1 will begin on February 16 th and run through March 26 th Ø Lab Session 2 will take place in the month of June (specific dates TBD) q Session 1 will focus on those non-live agencies that are wrapping up pre-implementation tasks (DOE, FDLE, DEP, DOAH, DOC, HSMV, AHCA, DOR, AWI, FWC, DBPR, DOL, DCA, DMA, DOS) q Session 2 Attendees will focus primarily on those agencies that have yet to begin preimplementation tasks (DEA, DFS, Attorney General, Department of Agriculture) q Will seek agency approval at end of lab sessions that system will meet agency business needs (replacing Operational Acceptance Test) 5

My. Florida. Market. Place Support Process Steps Transition Period • Agency user identifies issue: • Contacts Agency Liaison or • Contacts CSD Production Support • Agency Liaison/CSD • Resolves Issue, or • Contacts Tier 2 Support Agency Liaison Tier 2 Agency Support Buyer Adoption • Tier 2 Agency Support • Works with Prod Support • Works with Buyer Adoption • Communicates Resolution Agency User Agency CSD • Tier 2 Agency Support and Agency Liaisons • Review open issues weekly My. Florida. Market. Place • Identify new concerns 6

Agenda q Welcome and Introduction q Updated Deployment Approach / Agency Support q Release Schedule Planning Process / Change Request Process q Continue review of Agency Issues / Change Request Submissions q Next Meeting Time / Location 7

Release Schedule Planning Process Release Planning works within a 3 month planning horizon. The Change Requests and SIRS within releases are evaluated weekly and reprioritized as needed. Months prior to System Release One month prior § High degree of certainty regarding Release Schedule § Change Requests / SIR development is being finalized / tested for release date § Release Notes are created to describe the changes that will be incorporated Two months prior Three months prior § Some degree of flexibility in changing content of Release Schedule § Work is already in progress for most Change Requests/ SIRS scheduled in the release § High degree of flexibility in changing content of Release Schedule § Change Requests / SIRs have been prioritized, but most development work has yet to start 8

Agenda q Welcome and Introduction q Updated Deployment Approach / Agency Support q Release Schedule Planning Process / Change Request Process q Continue review of Agency Issues / Change Request Submissions q Next Meeting Time / Location 9

Agenda q Welcome and Introduction q Updated Deployment Approach / Agency Support q Release Schedule Planning Process / Change Request Process q Continue review of Agency Issues / Change Request Submissions q Next Meeting Time / Location 10

Next Meeting Time / Location q Next User Meeting: Week of February 16 th q Location: Carr Building q Notice will be sent out to Agency Liaisons (including call-in information) Project Contact Information: q Neal Morris: morrisa@dms. state. fl. us q Ken Granger: grangek@dms. state. fl. us q Rebecca De. La. Rosa: Delaror@dms. state. fl. us q Vince Ackerman: ackermv@dms. state. fl. us q Paul Lavery: Paul. M. Lavery@accenture. com q Rick Thompson: Patrick. W. Thompson@accenture. com q Kim Koegel: Kimberly. M. Koegel@accenture. com 11