myfloridamarketplace myfloridamarketplace user meeting march 8, 2005

MyFloridaMarketPlace

MyFloridaMarketPlace User Meeting

March 8, 2005

Page - 2

Agenda

Welcome / Introduction

Action Plan Update from 2/08 User Meeting

Aspire Update

Next Steps Regarding SPURS Sunset

Change Request Discussion

Scanning and Attachment Guidelines

Master Agreement Discussion

Next Meeting Time / Location

Page - 3

Agenda



Aspire Update






Page - 4

Agenda



Aspire Update






Page - 5

Aspire Update

The Aspire and MyFloridaMarketPlace teams are focused on integration testing of the application as well as transition activities that impact agency users

Master Agreements can be automatically encumbered in Aspire through MyFloridaMarketPlace (vs. manual process in place today)

Page - 6

Agenda



Aspire Update






Page - 7

SPURS Sunset Update

Agencies are continuing to transition from the PO creation function in SPURS

12 additional agencies will be transitioned from SPURS PO Creation during the month of March

PO and Requisition Functions are turned off for all agencies as of Friday, 7/29/05

Blanket Purchase Orders for FY 2005 – 2006 should not be created in SPURS- they should be created and maintained in MyFloridaMarketPlace

Agencies will continue to have the ability to add P-card vendors and “non traditional” vendors to the statewide vendor file via SPURS

Page - 8

Nov ’04 Jan ‘05

Nov ‘05Mar ‘05 Sep ‘05May ‘05

During 3/05: Additional agencies transition off SPURS PO Creation

11/2004: DMS & STO transitioned off SPURS PO Creation

Between now and 7/29: Agencies need to enter all multi-year purchase orders and/or contracts into MyFloridaMarketPlace, and make sure that any open purchase orders that can be closed have been closed *

During 5/05: Final set of agencies transition off SPURS PO Creation

Jul ‘05

1/10/05: Formal Memo to Agency Liaisons

1/14/05: DJJ, DOT, DVA, and Citrus transitioned off SPURS PO Creation

As of 7/29/05: All SPURS PO functions shutoff

SPURS Sunset Update

* Exception is Wave 1 agencies for Aspire. There will be separate communications from the Aspire team regarding dates by which SPURS and MyFloridaMarketPlace activity must be closed out.

Page - 9

SPURS Sunset: Agency Transition

AgencySPURS Cutoff Date

(Transition from PO Creation)

Department of Management Services Complete

Department of Transportation Complete

State Technology Office Complete

Citrus Complete

Department of Health Complete

Department of Juvenile Justice Complete

Department of Children and Families 3/15/05

Department of Veterans Affairs Complete

Executive Office of the Governor Complete

Agency for Health Care Administration Complete

Department of Education 3/15/05

Division of Administrative Hearings 3/15/05

Department of Environmental Protection 5/16/05

Agency for Workforce Innovation Complete

State Courts N/A

Page - 10

SPURS Sunset: Agency Transition (cont.)

AgencySPURS Cutoff Date (Transition from PO

Creation)

Department of Community Affairs 5/16/05

Highway Safety and Motor Vehicles 3/15/05

Lottery Complete

Department of State 3/15/05

Florida Department of Law Enforcement 3/15/05

Department of Business and Professional Regulation Complete

Department of Corrections 5/16/05

Fish and Wildlife 5/2/05

Department of Military Affairs 5/2/05

Department of Elder Affairs 5/2/05

Department of Revenue 5/2/05

Florida School of the Deaf and Blind 5/16/05

Public Service Commission 5/16/05

Parole Commission 5/16/05

Department of Financial Services 5/16/05

Dept of Agriculture 5/16/05

Attorney General and Legal Affairs 5/16/05

Page - 11

SPURS Sunset: Functionality Transition

Agencies are being transitioned off of PO creation in a phased approach, with all agencies being transitioned by 5/16/05.

SPURS Function Transition Timeframe *

Purchase Order Creation

End date for this function is currently set for 7/29/05.

The exception is Wave 1 Aspire agencies. There will be separate communications from the Aspire team regarding dates by which SPURS and MyFloridaMarketPlace activity must be closed out.

Purchase Order and Requisition Functionality

Transaction History will be available in SPURS and / or SPURSView.

Purchase Order History

End date for this function is currently scheduled to be June 30, 2006.

Statewide Vendor File Updates

* As dates / timeframes change, these will be communicated to agencies

Page - 12

SPURS Sunset: Agency Activities

Open Orders (including multi-year purchase orders):

Guidance: All purchase orders, including blanket purchase orders and multi-year purchase orders will be maintained in MyFloridaMarketPlace going forward. For those orders that are currently open in SPURS, agencies should force receive/close by 7/29/05. Any purchase orders that will not be fully received and closed prior to 7/29/05 should be entered into MyFloridaMarketPlace.

Agency Activity: Each agency should review and develop a “close out plan” for open orders. Identify any open orders that need to stay open past the end of the fiscal year and begin keying them into MyFloridaMarketPlace. Wave 1 Aspire agencies should coordinate with their Aspire team contacts to confirm timeframe available for reviewing open orders.

Blanket Purchase Orders:

Guidance: Blanket Purchase Orders for the current fiscal year that exist in SPURS can remain in SPURS (as the PO edit functionality will continue to exist until August 1st for non Wave 1 Aspire agencies). New Blanket Purchase Orders that are being created for FY 2005 – 2006 will be entered in MyFloridaMarketPlace.

Agency Activity: All Blanket Purchase Orders for the upcoming fiscal year should be created in MyFloridaMarketPlace

Page - 13

Agenda



Aspire Update






Page - 14


The MyFloridaMarketPlace team is reviewing the list of historically submitted Change Requests to create a plan for prioritization for future implementation.

As this plan is created, the team is taking into account the focus of the Aspire Integration.

Team is continuing to focus on resolution of system defects / issues and release those into Production as they are resolved.

Once a preliminary Change Request prioritization plan is updated, it will be reviewed with frequent MyFloridaMarketPlace users to confirm current priority.

As we move out of an Implementation Phase and into an Operations Phase, we will continue to revisit this topic, and will plan to discuss it further during the April User Meeting.

Page - 15

Agenda



Aspire Update






Page - 16

Agenda



Aspire Update






Page - 17


Overview of Master Agreements

Different Levels of Master Agreements

System Demonstration

Scenarios

Entering Master Agreements Prior to Aspire Transition

Page - 18

Overview of Master Agreements

Master Agreements provide agencies with the ability to do the following: Track spend against agency contracts Restrict the scope of purchases against contracts Encumber large dollar amounts against which releases can be issued

Once an agreement is established and approved within MyFloridaMarketPlace, an agency or agencies can begin generating purchase orders (e.g. releases) against the agreement

The use of Master Agreements helps to ensure that contracted prices are applied to releases and enforces agreement usage across the agency or agencies

Master Agreements can be set up at “different levels” which allow flexibility for agency needs: Supplier Level Commodity Level Item Level

BPO indicator was developed to facilitate agency blanket order purchases (that are set up as Master Agreements) in that it eliminates workflow from releases

Page - 19

Master Agreement: Different Levels

Commodity Level allows orders of any commodities specified from a given supplier. Pricing terms defined in the agreement apply to specific commodity codes selected in the agreement. May have percentage discounts or tiered pricing terms. Multiple commodity codes may be within the same agreement and each commodity code within the agreement may have its own pricing terms.

Supplier Level is the broadest option and it allows orders to a specific supplier. Pricing terms defined in the agreement apply to all of the supplier's goods and/or services they offer to the State. May have percentage discounts or tiered pricing terms.

Types of Master Agreements

Commodity Level

Supplier Level

Item Level

Item Level allows orders of only specific items from a specific supplier. Pricing terms defined in the agreement apply to specific items selected in the agreement. May have percentage discount, tiered, or fixed pricing terms. Multiple items may be within the same agreement and each item within the agreement may have its own pricing terms.

Page - 20

Master Agreement: Different Levels

Deciding which level to use: The appropriate approach is the one that creates the least amount of effort while still specifying what is being purchased, from whom, and for how much.

General Guidelines: As the number of line items go up for a Master Agreement, the more

appropriate a Supplier Level Master Agreement is to use.

As the number of line items go down for a Master Agreement, the more appropriate an Item Level Master Agreement is to use.

Page - 21

Master Agreement: System Demonstration

There are five steps to complete when creating a Master Agreement Request. These steps are: Set Definitions Set Limits Define Pricing Terms Define Accounting Define User Access Attach Required Documents

These steps will be reviewed as we step through the system demonstration.

The following scenarios will be reviewed as part of the system demonstration: Supplier Level Example Item Level Example Commodity Level Example

Page - 22

Master Agreement: Scenarios for Discussion

Scenario Description: Several locations across the state need to utilize the Master Agreement and create POs against it (e.g., multi-fiscal year copier agreement)

Agency Need: Encumber a large dollar amount for statewide use, and then individual locations will be creating POs against that agreement

Recommendation: Determine the extent to which the individual agency locations are going to own the creation of purchase order details (e.g., correct pricing terms, quantity, etc.) As a consideration, the agency should also consider the degree of control and flexibility needed at the individual location level. Option 1: If agency prefers increased flexibility for individual locations to set up

PO terms, use Supplier Level Agreement

Option 2: If agency prefers restriction for individual locations with regard to PO terms (e.g., only certain types of machines at certain prices), use Item Level Agreement

Option 3: Agency can set up a PO, with a line item for each copier, and tag monthly invoices to the PO

Page - 23

Master Agreement: Scenarios for Discussion

Scenario Description: Need to set up an agreement for a vendor that invoices frequently (e.g., DHL), and agency wants to encumber a single dollar amount for a fiscal year, and wants to set up a blanket purchase order for that vendor

Assumption: No way to initially determine that there is any meaningful item level information that could be included as part of an Item Level Agreement

Recommendation: Option 1: Agency can set up a Supplier Level Master Agreement, and each

agency location can set up a PO to encumber for fiscal year (e.g., X amount at $1 each), and each location just invoices against their individual PO

Option 2: If multiple commodity codes are used for courier services, and the agency wants to enforce tracking against that, set up a Commodity Level agreement

Page - 24


Tuesday, April 12, 2005

Carr Building, Room 170

9 a.m. – 11 a.m.

Meetings will include a monthly update of SPURS Sunset activities and

an Aspire Update

myfloridamarketplace myfloridamarketplace user meeting march 8, 2005

Documents

spurs po creation112004

spurs po creationjul

spurs po creationbetween

spurs po creationas

spurs sunset update

accenture llp

additional agencies

spursthis information