MyFloridaMarketPlace MyFloridaMarketPlace User Group Meeting March 2, 2004

Page - 2 Agenda Part 1 of User Meeting (For Live and Non-live agency representatives):  Welcome / Introduction  Agency Fielding Approach / OAT Update  ASPIRE update  Change Request / Agency Issues Update  Change Request 160  Update on Other Issues / Change Requests Part 2 of User Meeting (For Live Agency User Group Participants):  Design Review / Change Request Discussion

Page - 3 Agency Fielding Approach Update  Continuing to meet with agencies regarding preferred timeframes for Operational Acceptance Test and revised go-live dates  Upcoming Agency “Go-Lives”:  March timeframe: AWI (Week of 3/8), AHCA (Week of 3/15)  April timeframe: DOE (Week of 4/5), DOAH (Week of 4/21)  Prior to end of fiscal year: DEP, FDLE  Agencies are encouraged to participate in the Operational Acceptance Testing sessions as a step in the implementation process, and will schedule this with their project team liaison  Project Team Liaisons will continue to reach out to Agency Liaisons to discuss implementation tasks and status of agency issues / requests

Page - 4 Operational Acceptance Test Update Purpose  Operational Acceptance Test (OAT) is a task that agencies will complete prior to their go- live date  OAT includes agency “sign off” on a checklist of items, with the focus being on executing scripts related to system business functions  “Lab Sessions” will be used to facilitate this process and will allow agencies to execute day to day business tasks in MyFloridaMarketPlace Expectations  Agencies will review the OAT cover sheet, and execute the suggested scripts  Once the scripts have been executed successfully, the agency will signoff on each individual script.  If an agency has already completed this function and is comfortable with the functionality, it is not required that the agency run the script; however, the agency will be asked to sign-off on that script Outcomes  Increased comfort level by agency users as indicated by a “signed off” OAT checklist  Provides supporting documentation for Agency Readiness / Go-Live decision

Page - 5 Feedback Opportunities: Process Summary Document Agencies will note “Full,” “Partial,” or “No Acceptance” as part of the Process Summary form SAMPLE

Page - 6 Feedback Opportunities: Process Summary Document Agencies can use the Process Summary to also document any “Blocker Issues” or “Change Requests” noted during the Lab Session

Page - 7 Change Request Discussion  CR 160: Create Approval Requirements for Requesters when Canceling an order.  Design Change:  ‘Cancel’ Button will have approval rule logic  ‘Cancel Order eForm’ will be available for requesters to cancel orders outside of their dollar threshold, or for other Purchasing Agents to cancel orders.

Page - 8  CR 157: AWI has requested that agency’s Purchasing Agents have the ability to determine when a Purchase Order should have a workflow on a change order when adding/deleting line item  Policy Concern  Audit Concern  Is this met by other change requests (e.g. CR 85) Change Request Discussion

Page - 9 Change Request Discussion  CR 151: Department of Health has requested that the frequency of receiving notifications be increased from weekly to 2-3 times/week  Originally, notifications were daily, this was deemed excessive. Thoughts?

Page - 10  CR 174: AWI has asked to increase the threshold at which an change order’s line item price regenerates the workflow. Currently, the threshold is 5%.  This is a statewide setting.  Policy/Audit Concerns Change Request Discussion

Page - 11 Change Request Discussion  CR 163: Dep’t of Corrections has asked that the approvers in a requisition workflow be notified if a requisition is denied during the approval process.  Volume  Potential Confusion as status changes frequently  Currently, requester is notified, and requester is responsible for re-submitting requisition.