My Florida Market Place User Meeting July 20

  • Slides: 18
Download presentation
My. Florida. Market. Place User Meeting July 20, 2004

My. Florida. Market. Place User Meeting July 20, 2004

Agenda q Welcome / Introduction q Summary of Agency Checkpoint Meetings q DFS Update

Agenda q Welcome / Introduction q Summary of Agency Checkpoint Meetings q DFS Update q Finance and Accounting Open Discussion q Update on Release 5. 2 q Open Discussion Time / Year End Debrief and Lessons Learned 2

Agenda q Welcome / Introduction q Summary of Agency Checkpoint Meetings q DFS Update

Agenda q Welcome / Introduction q Summary of Agency Checkpoint Meetings q DFS Update q Finance and Accounting Open Discussion q Update on Release 5. 2 q Open Discussion Time / Year End Debrief and Lessons Learned 3

Summary of Agency Checkpoint Meetings q The intent of the Agency Checkpoint Meetings is

Summary of Agency Checkpoint Meetings q The intent of the Agency Checkpoint Meetings is to “take the pulse” of how both live and pre go-live agencies are progressing through the My. Florida. Market. Place implementation process. q DMS, Accenture, and North Highland have met with 19 agencies to date. Plan is to wrap up remaining meetings this week. q Common themes have been identified across these agency meetings. q We want to share this feedback with you today, and will continue to follow up with each agency individually to address specific action items. 4

Summary of Agency Checkpoint Meetings Themes: Next Steps: Agencies are requesting additional Policy Guidance

Summary of Agency Checkpoint Meetings Themes: Next Steps: Agencies are requesting additional Policy Guidance on items such as Master Agreement Blanket Purchase Orders, P-card, and Electronic Record Retention / Scanning • DMS will focus on utilizing the User Meetings, Purchasing Director’s Meetings, and e-mail communication to relay policy guidance • Provide a summary of the policy issues raised by the agencies along with DMS guidance on these policies Finance and Accounting Attention • Will continue to conduct 2 User Meetings per month and will encourage F&A attendance and discussion • Propose to conduct break out sessions at the User Meetings for agency to agency “best practice” discussions FLAIR Integration Concerns • Will be publishing a job aid to highlight where issues are occurring and steps users can take to resolve (e. g. , ensure site code and entity in user profile has appropriate FLAIR userid / password as seen in the e. Form) 5

Summary of Agency Checkpoint Meetings Themes: Next Steps: Release Planning / Visibility into this

Summary of Agency Checkpoint Meetings Themes: Next Steps: Release Planning / Visibility into this Process • Provide insight into upcoming Releases via User Meetings • Agencies can provide feedback about prioritization and timing directly to Accenture and DMS liaisons • Project team will investigate options for helping to address agency concern regarding quicker turnaround time of changes Analysis • The additional data is currently available. Evaluation of tool and new information underway by DMS. • DMS is confirming pilot approach, and will communicate to the agencies • Agencies will identify super users, and those super users will be trained on how to create reports in Analysis Customer Service • Agencies are feeling comfortable with the efforts of DMS and Accenture in supporting the implementation • Project team will continue ongoing education and coaching sessions to help enhance the agency’s CSD experience 6

Agenda q Welcome / Introduction q Summary of Agency Checkpoint Meetings q DFS Update

Agenda q Welcome / Introduction q Summary of Agency Checkpoint Meetings q DFS Update q Finance and Accounting Open Discussion q Update on Release 5. 2 q Open Discussion Time / Year End Debrief and Lessons Learned 7

DFS Requirements General Comments q A Master Agreement (MA) or Direct Order (DO) is

DFS Requirements General Comments q A Master Agreement (MA) or Direct Order (DO) is required for contractual services in accordance with s 287. 058, FS. q Two-party written agreements entered into by an agency must be set up as Master Agreements (MA). q Supporting documents previously submitted to the Bureau in paper format must be scanned into My. Florida. Market. Place. q Electronic invoices for contractual services submitted through the Ariba Supplier Network (ASN) must include the dates of service in the comment field on the electronic invoice submitted by the vendor. 8

DFS Requirements Master Agreements q q Required Master Agreement fields for DFS’ audit purposes

DFS Requirements Master Agreements q q Required Master Agreement fields for DFS’ audit purposes Ø Start Date and End Date (if applicable) Ø Maximum Commitment Amount Ø Method of Procurement Ø Historical Amount Spent, where appropriate Ø Description Ø Contract Type For contracts less than or equal to $250, 000, either a Contract Summary Form or entire contract document may be scanned in and attached to the Master Agreement Request (MAR). If the entire contract is scanned in, a comment citing the page number of the payment criteria/method of payment section is needed OR the payment criteria/method of payment section may be scanned in as a separate document. 9

DFS Requirements Master Agreements q For contracts greater than $250, 000, the entire contract

DFS Requirements Master Agreements q For contracts greater than $250, 000, the entire contract document is required to be scanned in and attached to the Master Agreement Request. A Contract Summary Form is not needed. A comment citing the page number of the payment criteria/method of payment section is needed or the payment criteria/method of payment section may be scanned in as a separate document. q Scanned documents needed, as appropriate Ø Invoice Ø Two-party written agreement Ø Contract Summary Form/payment terms for Master Agreement Ø Procurement documentation Ø Other documentation needed to fully document the transaction and/or show compliance with applicable laws, rules, and regulations 10

DFS Requirements Direct Orders q q Required Direct Order fields for DFS’ audit purposes

DFS Requirements Direct Orders q q Required Direct Order fields for DFS’ audit purposes Ø Start Date and End Date (if applicable) Ø Line items, including adequate description, units, and price/method of payment Ø Method of Procurement Ø State Contract ID, where appropriate on Non-catalog items Prior paid to date information must be provided either by providing information in Comment field on Exceptions Tab on the Invoice Reconciliation or by scanning in and attaching the Contract Summary Form to the Exceptions Tab or Invoice e. Form 11

DFS Requirements Direct Orders q Scanned documents needed, as appropriate Ø Invoice Ø Contract

DFS Requirements Direct Orders q Scanned documents needed, as appropriate Ø Invoice Ø Contract Summary Form Ø Procurement documentation Ø Other documentation needed to fully document the transaction and/or show compliance with applicable laws, rules, and regulations 12

Agenda q Welcome / Introduction q Summary of Agency Checkpoint Meetings q DFS Update

Agenda q Welcome / Introduction q Summary of Agency Checkpoint Meetings q DFS Update q Finance and Accounting Open Discussion q Update on Release 5. 2 q Open Discussion Time / Year End Debrief and Lessons Learned 13

Finance and Accounting Open Discussion Time A couple of questions / comments for the

Finance and Accounting Open Discussion Time A couple of questions / comments for the group… q During the Agency Checkpoint Meetings- there was a lot of discussion about agencies wanting to “share best practices” with other agencies- and that this could potentially address some of the F&A questions about how to most effectively complete processes in My. Florida. Market. Place. Comments from the group? q “Effective Scanning Processes” was also a popular topic during the Agency Checkpoint Meetings. Advice from the live agencies? q Other discussion topics? 14

Agenda q Welcome / Introduction q Summary of Agency Checkpoint Meetings q DFS Update

Agenda q Welcome / Introduction q Summary of Agency Checkpoint Meetings q DFS Update q Finance and Accounting Open Discussion q Update on Release 5. 2 q Open Discussion Time / Year End Debrief and Lessons Learned 15

Highlights of Release 5. 2 q Master Agreement accounting fields will be editable (SIR

Highlights of Release 5. 2 q Master Agreement accounting fields will be editable (SIR 14718) Ø When a user creates a master agreement, they will now have the ability to edit all of the accounting fields, which are accessed from the summary tab Ø The editablity will work the same as on a requisition q Ability to uncheck `Send to Vendor` checkbox for comments and attachments (CR 133) Ø Users will have the ability, when approving a transaction, to check or uncheck the `send comments` to vendor box Ø Frequently, a requester may check the `send to vendor` box, but a purchasing agent may wish to remove that comment before it goes to the vendor for numerous reasons q There were new roles added for this release: Ø 3600: Director of F&B, Ø 7300: Program Budget Approver Ø Super. CPLA Approver Ø These roles will be added to the job aid that currently exists on the Toolkit q Additional enhancements are included, and the detail is available via the 5. 2 Release 16 Notes

Agenda q Welcome / Introduction q Summary of Agency Checkpoint Meetings q DFS Update

Agenda q Welcome / Introduction q Summary of Agency Checkpoint Meetings q DFS Update q Finance and Accounting Open Discussion q Update on Release 5. 2 q Open Discussion Time / Year End Debrief and Lessons Learned 17

Next Meeting Time / Location q August 3, 2004 q Carr Building, Room 170

Next Meeting Time / Location q August 3, 2004 q Carr Building, Room 170 from 9 a. m. – 11 a. m. 18