CRB ROMs for Review May 28 2010 ROMs

CRB ROMs for Review May 28, 2010

ROMs for Review Agenda q Previous CRB Top Five Priorities q Audit Change Requests / Additional Changes in Discussion 2

Recap: CRB Top Five Change Requests q At the beginning of the last CRB meeting, these were the top five CRs: Change Request Hour Estimate CR 29: Include Voucher # and SWDN on 50 hours payment update e. Form CR 30: Add Contract ID to the DO 48 hours CR 41: CFO Received Date 496 hours CR 53: Buyer Password Reset 700 hours CR 86: Default the checkbox to be unchecked 40 hours Total 1, 334 hours 3

CR 29: Include Voucher # and SWDN on payment update e. Form Ø Current Challenge: When a disbursement is completed directly in FLAIR, the “Paid in FLAIR” checkbox will be marked on the associated Invoice Reconciliation (IR). Users will then utilize the Payment Update e. Form to enter the FLAIR payment details for that disbursement. Currently, users have the ability to enter the Warrant Number and Warrant Date for each payment associated to the IR. Users have requested the ability to update the Voucher Number and Statewide Document Number on the Payment Update e. Form. Ø Proposed Solution: Add the Voucher Number and Statewide Document Number to the Payment Update e. Form. These new fields will not be required on the e. Form. Users will be allowed to enter a value or leave the Voucher Number and Statewide Document Number fields blank. If the user enters a value for these fields, then the value will be updated on the Payment and associated Invoice Reconciliation (IR) accounting objects. Ø Estimated ROM: 50 hours 4

CR 30: Add contract ID to the DO Ø Current Challenge: Customers have requested the display of the following on the print view of a Requisition: • Both the State Contract ID and Agency Contract ID • Line item commodity code, commodity description and PUI Currently, only the Agency Contract ID is displayed on the print view. Ø Proposed Solution: Add the above fields to the print view of a Requisition and PO. Ø Estimated ROM: 48 hours 5

CR 41: CFO Received Date Ø Current Challenge: • Currently, when the DFS calculates an agency’s prompt payment they do not have particular fields available to them from My. Florida. Market. Place (MFMP) (i. e. , the date that the Invoice Reconciliation (IR) is received by the auditor). • Instead, they are utilizing a date not provided by MFMP (CFO Received Date) that is captured after the auditors have approved the transaction for payment. • This causes the prompt payment report to include the agency’s processing time and the auditor’s processing time as a part of the agency’s 20 -day timeframe for invoices audited in MFMP. 6

CR 41 continued CR 41: CFO Received Date Ø Proposed Solution: • • In order to accurately report an agency’s prompt payment percentage for MFMP audited invoices, changes will be made in both MFMP and FLAIR. In MFMP, changes will be made to store a date at the header level of new Invoice Reconciliations (IRs) to reflect the MFMP calculated CFO Received Date. Changes will also be made in MFMP for all disbursement transaction (51 S, 53 S and 70 S) interface transactions so that the “MFMP CFO Received Date” is submitted to DFS for calculation. This “MFMP CFO Received Date” will be entered by the MFMP interface in the “CKDT” (check date) field when submitting a disbursement transaction to FLAIR. Ø Estimated ROM: 496 hours 7

CR 53: Buyer Password Reset Ø Current Challenge: Currently, if a buyer forgets his or her MFMP password, the agency system administrator must reset the password utilizing the Password Change e. Form. Agencies are requesting the ability for a buyer to reset his or her password without contacting the agency system administrator. The functionality would be similar to the vendor password reset enhancement. Ø Proposed Solution: MFMP will implement an automated password reset function for buyer customers, similar to the VIP vendor password reset already in place. Ø Estimated ROM: 700 hours* *Note: Expect the ROM for CR 53 to increase – we intend to refine this ROM to include tougher security to ensure it will not result in a future audit finding. 8

CR 86: Default the checkbox to unchecked Ø Current Challenge: Currently, when creating a comment on a Requisition, the “include comment/attachment(s) on purchase orders” checkbox is defaulted to checked. . Ø Proposed Solution: Changes will be required to the comment functionality within MFMP to default the “include comment/attachment(s) on purchase orders” to be unchecked when adding a new comment to a Requisition. Ø Estimated ROM: 40 hours 9

Updated: CRB Top Five Change Requests q The group opted to swap CR 86 for CR 114 (formerly 260014) Green/Recycled Reporting Change Request Hour Estimate CR 29: Include Voucher # and SWDN on payment update e. Form 50 hours CR 30: Add Contract ID to the DO 48 hours CR 41: CFO Received Date 496 hours CR 53: Buyer Password Reset 700 hours CR 114: Green / Recycled Reporting 200 hours Note: This is now a statutory change per House Bill 7243 and must be implemented before September 31, 2011 Adjusted Total 1, 494 hours 10

CR 114 Wrap-Up CR 114 (formerly 260014): Green and Recycled Reporting Ø Current Challenge: Agencies are currently seeking a uniform reporting mechanism that will allow them to prepare annual summaries of statewide purchases delineating those with recycled content to be submitted to the Governor, the President of the Senate, and the Speaker of the House of Representatives. Currently, “green” and recycled content is identified for catalog items only in MFMP. Therefore, MFMP reporting can only provide reporting for “green” and recycled purchases made from catalogs. Ø Proposed Solution: With this change request, agencies will now have the ability to designate a non-catalog as “green” and/or recycled. However, agencies will not have the ability to select the My. Green. Florida certification type for a “green” non-catalog item. In addition, “green” and recycled items will be loaded into Analysis as part of the 9 r 1 upgrade. After the 9 r 1 upgrade, agencies will be able to create reports within the Analysis application to identify both “green” and recycled purchases made for catalog and noncatalog items. Agencies will also have the ability to designate a Punchout item as “green” and/or recycled. Similar to non-catalog items, agencies will not have the ability to select the My. Green. Florida certification type for a “green” Punchout item. Ø Estimated ROM: 200 hours 11

Additional CRs Enterprise Customer-Driven ROM Estimate Audit Findings CR 108: PO Start Date / End Date 40 hours CR 110: Buyer Password Complexity 360 hours CR 111: VIP Password Complexity 392 hours CR 112: Updates to the VIP Change Log Solution 1: 200 hours Solution 2: 600 -800 hours CRB Requested CR 115: Require Contract # based on MOP 120 hours Invoice Workgroup Requested CR 116: Improvements to the Invoice e. Form 48 hours Total Additional CR Hours (not including the CRB top five) 12 1, 160 hours OR 1, 560 -1, 760 hours

CR 108: PO Start Date / End Date Validation on Requisitions Ø Current Challenge: Currently, when creating a requisition there is no validation on the PO start date and end date fields; a PO start date can be after the end date. Ø Proposed Solution: With this change request, validation will be added to the PO start and end date fields so that the start date must be before or on the same day as the end date. Ø Estimated ROM: 40 hours 13

CR 110: Updates to Buyer Password Complexity Ø Current Challenge: Currently, Buyer passwords are required to be 7 -8 characters in length. DMS has requested the complexity of Buyer passwords be updated. Ø Proposed Solution: With this change request, Buyer passwords will be still be 7 -8 characters in length but will also be required to include one of each of the following: • One uppercase letter • One lowercase letter • One digit • The above validation will be applied when users are prompted to change an expired password as well as on the Password Update e. Form. In to the above validation, users will no longer be able to re-use the last five passwords. Ø Estimated ROM: 360 hours 14

CR 111: Updates to VIP Password Complexity Ø Current Challenge: Currently, Vendor Information Portal (VIP) passwords are required to be 6 -15 characters in length. DMS has requested the complexity of VIP passwords be updated. Ø Proposed Solution: With this change request, VIP passwords will be still be 8 -15 characters in length but will also be required to include one of each of the following: • • One uppercase letter One lowercase letter One digit The above validation will be applied when vendor attempts to reset his or her password or a password is reset by a vendor admin. In addition to the above validation, vendors and administrators will no longer be able to re-use the last five passwords. • This enhancement will also include functionality to expire passwords after 120 days. Ø Estimated ROM: 392 hours 15

CR 112: Updates to VIP Change Log Ø Current Challenge: Currently, the Vendor Information Portal (VIP) system captures specific logging information as it relates to updates that are completed on a vendor’s registration by an administrator. DMS is requesting that the logging be expanded. Ø Proposed Solution #1: With this change request, VIP logging will be expanded to record the specific administrator as well as the date/time of following activities: • • • 1099 Name updates Contested 1099 Name status changes Registration status changes Location status changes Contact updates Location updates (including sequence or PIN updates) STC/SPA status changes Password resets Ariba Network ID updates Sourcing solicitation status changes VBS solicitation status changes Reluctant vendor status changes Ø Estimated ROM for Solution #1: 200 hours 16

CR 112 continued CR 112: Updates to VIP Change Log Ø Proposed Solution #2: This solution will include the extended logging described in the above section. In addition, specific change values (the “from” value as well as the “to” value) will be recorded. Ø Estimated ROM for Solution #2: 600 - 800 hours 17

Additional Changes Wrap-Up In addition to the CRs we’ve mentioned so far, we’re also considering the following: Change Request Hour Estimate CR 115 Require the Contract # based on MOP 120 hours CR 116 Improvements to the Invoice e. Form 48 hours 18

CR 115: Require Contract # based on Method of Procurement (MOP) Ø Current Challenge: Currently, when a non-catalog requisition is completed and the Method of Procurement is selected as an A or B, there is no mandatory requirement to enter the appropriate state term contract (STC) #. In addition, there are no options to enter the Alternate Contract Source (ACS) # or State Purchasing Agreement (SPA) # if the Method of Procurement of C or D is selected. Also, there are no options to enter an Agency ITB #, Agency RFP # or Agency ITN # if the Method of Procurements of H, H 1, I, I 1, J, J 1 are selected. Ø Proposed Solution: With this change request, an STC # (via a chooser) will be required (in • the existing field) when entering a Method of Procurement on a requisition that starts with “A” or “B”. With this change request, an ACS # or SPA# will be required (in a new field) when entering a Method of Procurement on a requisition that starts with “C” or “D”. In addition, we’re also considering requiring ITB #, RFP # or ITN # (in a new field) when entering a Method of Procurement on a requisition that starts with “H”, “H 1”, “I 1”, “J” or “J 1”. This new validation will apply to new requisitions as well as change orders initiated after the implementation of the change request. Ø Estimated ROM: 120 hours 19

CR 116: Improvements to the Invoice e. Form Ø Current Challenge: Currently, the invoice e. Form requires several unnecessary additional steps: • • • Ø Proposed Solution: Changes will be made to the invoice e. Form to complete the following: • • • Ø When a user enters the tab key on the header of the invoice e. Form after entering the “Invoice Number” field, the “Supplier Invoice Date” field validates (displaying an error “Value must be set!”). After generating the invoice, the cursor defaults to the “Line #” field on the Invoice Lines page. This field rarely requires updating but is often updated by mistake since it is the default for the cursor. When the “Quantity” field is changed on the Invoice Lines page and the tab key is entered, the cursor moves to the first line’s “Line #” field. The “Supplier Invoice Date” field will be validated once the invoice e. Form is submitted or the page is refreshed. After generating the invoice, the cursor will default to the “Quantity” field on the Invoice Lines page. When the “Quantity” field is changed on the Invoice Lines page and the tab key is entered, the cursor moves to the current line’s next field (“Part. No”). Estimated ROM: 48 hours 20