1. MyFloridaMarketPlace CRB Meeting November 28, 2006

2. Page 2 Agenda Review  CR 27 - Negative receiving (editing receipts > 24 hrs)  Negative receiving has been voted into the upgrade  CR 28 - Regeneration of Workflow  Clarify the intent and design  Review of CR Design Team Roles/responsibilities  Review of Groups/Roles & discussion  General upgrade status  System Test Pass (STP) 1 results to-date  Upcoming significant events (STP 2, UAT prep, Training prep)  Closing comments & What’s next

3. Page 3 CR 27 – Negative Receiving in the Upgrade!  Subsequent to discussions with MFMP and DMS Management, opportunity identified to postpone data scoping in exchange for including Negative receiving as presented 11/9/06 to CRB  Email to CRB Distributed 11/17/2006 to vote  6 agencies responded in favor of negative receiving  2 agencies responded in favor of data scoping  4 agencies did not respond  Design review summary  Assignment of Design Approval Team  Data Scoping will be re-addressed with full CRB involvement 1 st quarter of next FY

4. Page 4 Regeneration of Workflow during Approvals  CR 28 - Regeneration of Workflow  Subsequent to 11/9 CRB, some discussion or confusion on the intent of the CR  What is the intent?  The intent is to minimize the number of times an approver sees a requisition  During the approval process (either initial or change order), if a requisition is edited and a change is made to the PR meeting any of the 4 conditions (business rules below), the PR will not be sent back through the approval flow  4 business rules to bypass regeneration Adding a line item not requiring specific approver or less than 10% total PR dollar value Deleting a line item Changing the total dollar value by less than 10% Changing commodity code not requiring special approver  This design does not remove the approval flow for a Change Order on a Purchase Order unless:  Person making the change has the role of “CO No Workflow”  Changes to the PO are limited to the 53 prescribed changes

5. Page 5 CR Design Approval Team Roles/Responsibilities  For each CR, Design Approval Team selected  Generally, Design Approval Team selected from CRB members  Design Approval Team involved in design review, testing and post implementation survey. Specifically, the team will:  Review, provide input to, and approve designs  Conduct user acceptance testing after development is complete  Complete a system enhancement survey after the acceptance of the CR

6. Page 6 8.2.2 Group and Role Structure Groups  Group is a collection of permissions  Assign one group v. many roles  Designed groups:  Analysis,  Contract Manager,  Purchasing,  Requester,  Approver,  Reporting,  Receiving  and Invoicing Roles  Roles allow additional functionality  Reduce the number of roles  For example:  Requester-No eQuote,  Requester eQuote,  Requester-No eQuote-No Accounting Edit  and Requester-eQuote-No Accounting Edit

7. Page 7 8.2.2 Group and Role Structure Requester Group Change Create eQuote Role Edit Search Accounting Edit Role Central Receiver Role

8. Page 8 Ariba Buyer 8.2.2 Upgrade – Plan Stage Status Plan Train Deploy Design AccomplishmentsIn progressUpcoming  Development of 7.1 customized components  Review of 8.2 test conditions  System Test Pass 1  Finalization of workflow analysis  Change Request evaluation  Review final upgrade scope  System Testing – 3 passes beginning (11/3 – 2/9/07)  Design of new key groups/roles/permissions  Data center relocation negotiations  Enterprise reporting assessment  CR Designs  Go/No go decision for April 07 (1/19)  Implementation planning  Ariba Sourcing upgrade planning  UAT Script preparation  Training preparation * Bold indicates CRB participation may be requested Test Build Technical Infrastructure

9. Page 9 What’s Next?  December 19, 2006, Kirkman Building (HSMV); 2900 Apalachee Parkway, Room A427  Any closing discussion Thank you!