Download
myfloridamarketplace n.
Skip this Video
Loading SlideShow in 5 Seconds..
MyFloridaMarketPlace PowerPoint Presentation
Download Presentation
MyFloridaMarketPlace

MyFloridaMarketPlace

2 Views Download Presentation
Download Presentation

MyFloridaMarketPlace

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. MyFloridaMarketPlace MyFloridaMarketPlace User Meeting February 10, 2004

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

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

  4. Updated Deployment Approach • February: Leverage User Meetings to review agency system issues / preferred system enhancements. • February 16th – March 26th: Conduct “Lab Sessions” that allow agencies to execute day to day business tasks and to gain additional comfort with MyFloridaMarketPlace (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). • March 1st – March 26th: Implement agency pilots of MyFloridaMarketPlace with those agencies that express a desire to move forward with fielding activities prior to March release. • End of March: New system functionality included in March release (Release notes will be available to review specific changes included). • March 29th – May 21st: Implement MyFloridaMarketPlace at agencies (focus being those agencies that are “in process” right now) • June: Conduct second round of Lab Sessions (focus being on agencies going live after July 6). • July 6th – August 27th: Complete the initiation of agency go-live activities.

  5. Revised Operational Acceptance Test (OAT) Approach • Will take the form of “Lab Sessions”: • Allows agencies to execute day to day business tasks and to gain additional comfort with MyFloridaMarketPlace • 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 16th and run through March 26th • Lab Session 2 will take place in the month of June (specific dates TBD) • 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) • Session 2 Attendees will focus primarily on those agencies that have yet to begin pre-implementation tasks (DEA, DFS, Attorney General, Department of Agriculture) • Will seek agency approval at end of lab sessions that system will meet agency business needs (replacing Operational Acceptance Test)

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

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

  8. 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 • 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 One month 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 Two months prior • High degree of flexibility in changing content of Release Schedule • Change Requests / SIRs have been prioritized, but most development work has yet to start Three months prior

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

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

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