A2__FRR_3__Purchasing_Requirements.xlsx
XLSX spreadsheet 46 KB Posted
- Attached to
- Enterprise Resource Planning (ERP) System State and local contract opportunity
- Solicitation number
- P-26-08-COC
- Issued by
- Brevard County, Clewiston City, Florida
About this file
This is a Functional Requirements document for a Purchasing Workflow Module within an Enterprise Resource Planning (ERP) system procurement for the City of Cocoa, Florida. The document outlines comprehensive system requirements across purchasing, vendor management, requisitions, purchase orders, contracts management, and reporting functions. The City seeks a modern, cloud-hosted SaaS solution to replace legacy systems and improve operational efficiency across financial management, human capital management, utility billing, community development, and asset management modules. The purchasing component must support encumbrance control, multi-approval workflows, integration with document management systems, real-time budget tracking, and automated purchase order generation. Key requirements include the ability to process multi-delivery and blanket requisitions, maintain vendor master files with separation of duties controls, support three-way matching for payment validation, track expenditures against credit cards and P-cards, and generate customizable reports by various parameters including vendor, commodity code, and account number.
The vendor portal requirements specify 24/7 operational capability with self-service vendor registration, electronic bid response submission, invoice submission, and payment status tracking. System security must include role-based access controls, encryption of sensitive information, mobile authentication with one-time passwords, and electronic signature generation. The purchasing module must provide real-time visibility into purchase order status, contract balances, and requisition workflows with configurable approval routing based on dollar thresholds and user-defined fields. Contract management functionality must track multiple contracts per vendor, support change orders with audit trails, monitor insurance and renewal dates with automated notifications, and reconcile payments against contract balances. The solution must integrate with the City's existing Esri GIS infrastructure, Laserfiche document management system, and support open APIs for seamless data flow between modules. Implementation requires a turn-key approach including data migration, system configuration, staff training, and post-go-live support.
View the file
Other files for this state and local contract opportunity
| File | Type | Posted |
|---|---|---|
| P2608COC_NOTICE_OF_INTENT_TO_SHORTLIST.pdf | ||
| 08272026_P2608COC_ERP_System_Meetingv2.pdf | ||
| Master_Bid_Tabulation_Sheet_P2608COC.pdf | ||
| Addendum_3_P2608COC_QA.xlsx | XLSX spreadsheet | |
| Addendum_2_P2608COC.pdf | ||
| Addendum_1_RFP_P2608COC.pdf | ||
| A1__Proposal_Response_Forms.docx | DOCX document | |
| A2_FRR_2__Finance_Accounting_and_Reporting_Requirements.xlsx | XLSX spreadsheet | |
| A2__FRR_1__General_System_Requirements.xlsx | XLSX spreadsheet | |
| A3__Terms_and_Conditions_P2608COC.docx | DOCX document | |
| A4__Combined_Proposer_Certifications_and_Affidavits.docx | DOCX document | |
| A2__FRR_4__Human_Resources_Management_Requirements.xlsx | XLSX spreadsheet | |
| A2__FRR_6__Citizen_Portal_Requirements.xlsx | XLSX spreadsheet | |
| A2__FRR_5__Utility_Billing_Requirements.xlsx | XLSX spreadsheet | |
| RFP_NO._P2608COC_Enterprise_Resource_Planning_System.pdf |
Show all 15
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Workflow
| Purchasing Workflow | |||
| # | Requirement | Response | Comments |
| General Requirements | |||
| 1 | Ability to support encumbrance control for budgeted funds. Ability to disallow encumbrances at the end of a projects availability. | ||
| 2 | Ability to support "soft" pre-encumbrance control, whereby a warning is given if sufficient funds are not available. | ||
| 3 | Ability to copy information from one process to another without rekeying (i.e., requisition to purchase order). | ||
| 4 | Ability to drill down to supporting documents within the purchasing system. | ||
| 5 | Ability to establish and maintain information concerning: Vendors; Commodities and a commodity coding structure (NIGP codes); Standards or specifications for items acquired; Standard text for terms and conditions of purchases. | ||
| 6 | Ability for receiving department to record receiving information: receiving staff, shipping carrier with tracking number, date and time received, complete/partial, and comments/notes. | ||
| 7 | Ability to record and maintain history of purchases, commodities, and volumes. | ||
| 8 | Ability to generate reports to show all historical transacations for a given PO number to ensure that the PO is not over expensed. | ||
| 9 | Ability to support workflow for purchasing approval process, including multiple approvals at the departmental and central purchasing levels. | ||
| 10 | Ability to support automatic entry into other modules as specified by the City. | ||
| 11 | Ability to maintain history of all purchasing processes including requisitions and multiple types of purchases. | ||
| 12 | Ability for end-users to check expenditures to date against encumbrances and budgets and see results on-line in real time prior to processing an expenditure request. | ||
| 13 | Ability to support updating general ledger accounts for all purchasing transactions. | ||
| 14 | Ability to look up real-time status of purchasing processes. | ||
| 15 | Ability to track expenditures against credit cards issued to employees. | ||
| 16 | Ability to pull Purchasing Cards (P-cards) data (i.e., purchaser, invoice number, amount, date) from the bank and automatically update A/P and detailed G/L. | ||
| 17 | Ability to restrict choice of account code against which employee can charge credit card expenditures to those valid account codes for his/her department. | ||
| 18 | Ability to allow specific departments to charge other departments for inhouse work and supplies | ||
| 19 | Ability to accommodate partial receipts. | ||
| 20 | Ability to allow City staff to enter and access delivery validation information. | ||
| 21 | Ability to route requisitions and purchase orders using workflow based on user-defined fields (e.g. dollar amount, commodity code). | ||
| 22 | Ability to assign effective date of transactions, either current or post-dating. | ||
| 23 | Provide an integrated Document Management System (or communicate with current Laserfiche system) where users can view all related documents within the Purchasing module (Requisition, PO, Invoice and A/P check). | ||
| 24 | Ability to close out / reverse encumbrances and purchase orders by user defined parameters. | ||
| 25 | Ability to view description, expenditure/Project Accounting Codes when receiving documents againts a Purchase Order. | ||
| 26 | System provides easy setting up and maintaining of workflows. | ||
| 25 | Ability to build workflow based on dollar amount. | ||
| 26 | Ability to reconcile purchase orders to general ledger for encumbrance balance. | ||
| 26 | Ability to prevent submissioin of requisitions until all required supporting documents are attached. | ||
| 26 | Ability to display approval routing paths prior to requisition or contract submission. | ||
| 26 | Ability to allow multiple users to edit the same requisition simultaneously with change tracking and audit history. | ||
| 26 | Ability to display real-time apporval status for requisitions, purchase ordres, and contracts. | ||
| 26 | Ability to automatically route requisitions, purchase orders, and contracts through configurable approval workflows. | ||
| 26 | Ability to automatically generate and distribute purchase orders to vendors upon approval. | ||
| Reporting & Querying | |||
| 27 | Provide an Open Purchase Orders Report by Expense Account; Date; Vendor; Commodity Code; Ship to location. | ||
| 28 | Ability to export mailing labels to MS Word and MS Excel for mail merge functionality. | ||
| 29 | Ability to accommodate user-defined contract alerts for key dates (renewal, expiration, rebid, Certificate of Insurance, etc.). | ||
| 30 | Ability to note contract revisions, including date and source. | ||
| 31 | Ability to allow ad hoc reporting on any field within the purchasing module. | ||
| 32 | Ability to generate a report of all activity with a vendor. | ||
| 33 | Ability to provide reporting capability of all sole source or emergency purchase orders. | ||
| 34 | Ability to generate all reports by user-defined date ranges that may occur over prior fiscal years. |
| Compliant |
| Alternative Method |
| Modification Required |
| Non-Compliant |
Vendor Management
| Vendor Management | |||
| # | Requirement | Response | Comments |
| General Requirements | |||
| 1 | Have the system utilize a separation of duties process for vendor setup – data entry and review/approval to ensure correct entry of vendor, banking (payment routing) information, W‐9 information (for 1099 processing). | ||
| 2 | Ability to establish and maintain Vendor information including: Names, Contact, Address, Website, Amount Owed, Status, Vendor Code. | ||
| 3 | Ability to support multiple email addresses and fax numbers for purchase orders and other vendor/procurement functions. | ||
| 4 | Ability to select from a master contract listing or common vendors listing. | ||
| 5 | Ability to support one master vendor file for all modules in the system, with security on the ability to change and/or update vendor records. | ||
| 6 | Ability to support multiple vendor records (e.g., remittance addresses) associated with one Federal Tax ID. | ||
| 7 | Ability to maintain a complete listing of historical vendors (i.e., including those no longer active) and be able to purge the list. | ||
| 8 | Ability to provide vendor file that tracks vendor information, including but not limited to: Vendor Number, Vendor Addresses, Vendor name, Type of Vendor, Vendor Tax ID, Multiple Email Addresses, Multiple Addresses, Designated Point of Contact, Memo Field, Commodity Code, Vendor Activity Status, Compliance Flagging, Vendor Withholdings, Bank Information, Discount Terms, Minority/Woman/Disadvantage Business indicator, litigation flag, HUB Vendor, HUB Vendor number. | ||
| 9 | Provide miscellaneous text fields to track information about vendors. | ||
| 10 | Ability to detect duplicate vendor information upon entry of vendor information. | ||
| 11 | Ability to allow transactions with valid vendors only. | ||
| 12 | Ability to allow the selective inactivation or purging of vendor records by user-defined criteria. | ||
| 13 | Ability to suspend, debar and reinstate vendors | ||
| 14 | Ability to support tracking of received goods and services againt purchase orders for vendor performance and payment validation. | ||
| Reporting & Querying | |||
| 15 | Ability to run a report/query to assess risk (how many critical and non-critical or high/medium/low third parties). | ||
| 16 | Ability to run a report/query to perform due diligence (how many, upcoming, any overdue or missing items). | ||
| 17 | Ability to run a report/query to monitor ongoing vendor activities. Record monitoring activities with notes, timestamps and user id information. | ||
| 18 | Ability to run a report/query to identify Emergency Preparedness and Response Vendors. | ||
| 19 | Ability to run a report/query for contracts information (upcoming renewals or terminations, any notable problems with critical or high risk third parties. |
| Compliant |
| Alternative Method |
| Modification Required |
| Non-Compliant |
Vendor Portal
| Vendor Self-Service Portal | |||
| # | Requirement | Response | Comments |
| General Requirements | |||
| 1 | Provide a configurable Vendor Self-Service Portal that can have a similar look and feel as the City's website. | ||
| 2 | Provide a Vendor Portal that is operational on a 24x7 basis. | ||
| 3 | Ability for vendors to submit electronic registration and update company information; workflow to predetermined approver for final approval. | ||
| 4 | Allow vendor to select commodity codes they wish to bid on. | ||
| 5 | Ability to notify vendor if a bid associated with the commodity code is posted. | ||
| 6 | Ability for vendors to request and check on submitted bids. | ||
| 7 | Allow vendors to electronically respond to bids. | ||
| 8 | Allow vendors to electronically submit invoices and check on payment status. | ||
| 9 | Ability to capture and track usage volume statistics for the Portal. | ||
| 10 | Ability to send an email notice of successful submission to a user that contains hyperlinks to the relevant areas of the Portal. | ||
| 11 | Ability to allow "online form submission" whereby users can complete fillable forms for electronic submission. | ||
| 12 | Ability to encrypt sensitive information. | ||
| 13 | Ability to allow documents to be attached to vendor profiles as well as online form submissions. | ||
| 14 | Ability to support vendor receipt of purchase orders through electronic delivery methods (e.g., email or vedor portal access). | ||
| User Management | - | ||
| 15 | Ability to enable user to register themselves. | ||
| 16 | Ability to highlight the mandatory fields to be filled for registration. | ||
| 17 | Ability to support mobile authentication with one time password for registration. | ||
| 18 | Ability to support mass registration through file upload for admin users. | ||
| 19 | After registered user logs in to the Portal, Portal should redirect user to the home page. | ||
| 20 | Provide a forgot password mechanismin the Login page. In case user forgets the password/wish to reset a link should be sent to user’s registered Email address or by sending OTP on registered mobile to reset password. | ||
| 21 | Provide an admin module using which Portal administrator(s) can create/edit/delete users and groups. | ||
| 22 | Provide the capability of feature blocking. User could be blocked for some activities and still can have access to other services. | ||
| 23 | Ability for Portal to provide user access logs. | ||
| Usability | |||
| 24 | Interactive Display: User interface should be interactive. Portal should support use of Modules/Widgets that can be placed onto pages that provide static, dynamic or interactive content. Users should be able to re arrange widgets on a portal page with easy to use drag and drop feature. | ||
| 25 | Ability to integrate with external email gateway and SMS (text message) gateway. | ||
| 26 | The solution should be able to store and display registered user’s last login, location, IP address, time, and date. | ||
| 27 | The solution will provide clear layout and organized displays. | ||
| 28 | The solution will provide consistent experience across all internet applications. | ||
| 29 | The solution should be optimized for integration with standard screen readers on the market. | ||
| 30 | The solution must be easy and intuitive to learn (The degree to which the solution can be used without specific training). | ||
| 31 | The solution will allow an agreed set of tasks to be completed by an administrator-configured duration (e.g., view status of an invoice, view payments). | ||
| Security | |||
| 32 | Provide a security-enabled functionality set (i.e., user ID and password required). | ||
| 33 | Ability to maintain permissions by user (need to inactivate a user) | ||
| 34 | Ability to set up vendors and classify them by "risk" - low risk, medium risk, high risk. | ||
| 35 | Ability to allow certain information to be restricted for viewing only by users logged-in with appropriate credentials. | ||
| 36 | Ability for users to employ a single username/password combination for all security-enabled functionality. | ||
| 37 | Ability to allow a user to save work in progress with the ability to edit prior to submission (i.e., log out and then log back in without losing information). | ||
| 38 | Ability to allow a user to view the status of a request/submission after logging in. | ||
| 39 | Ability to pre-populate basic identity fields based on the account information stored with the user's ID/password. | ||
| 40 | Ability to generate an electronic signature based upon approved login credentials. |
| Compliant |
| Alternative Method |
| Modification Required |
| Non Compliant |
Requisitions
| Requisitions & POs | |||
| # | Requirement | Response | Comments |
| General Requirements | - | ||
| 1 | Ability to electronically process multi-delivery, direct ship, blanket and non-blanket requisitions. Ability to have multiple budget lines on a Blanket PO, with or without unique account numbers. | ||
| 2 | Ability to display multiple account numbers AND project codes on any line item on requisitions. | ||
| 3 | Ability to perform the following requisition functions, with the appropriate security: Inquiry; Add; Change; Cancel; Delete. | ||
| 4 | Ability to provide for multiple lines of input per individual requisition. | ||
| 5 | Ability to provide reports to users and management on requisition status. | ||
| 6 | Ability to create and track all requisitions by: date, requester, budget, item, action item. | ||
| 7 | Ability to check against the budget and pre-encumber requisition per line item. | ||
| 8 | Ability to modify items ordered through change order (add or delete) including part, class, quantity, unit of measure, vendor, cost, project, fund, with the appropriate security. | ||
| 9 | Ability to track requisitions and automatically date and time stamp (received, accepted, returned, re-received) with notes and comments. | ||
| 10 | Ability to limit aqnd override G/L distribution accounts to only those valid for that department/user. | ||
| 11 | Ability to have multiple line items per purchase order with capability for one/multiple delivery schedules per line printed on purchase order. Valid for projects as well. If outside user department/division, route for additional approvals (e.g., A single invoice could have additional department/divisions needing payment). Ability to route for additional approvals from a single user input? | ||
| 12 | Ability to automatically or manually number requisitions with the ability to restart the numbering process with each fiscal year. | ||
| 13 | Ability to create purchase orders from requisitions. | ||
| 14 | Ability to request a budget transfer as part of the requisition process. | ||
| 15 | Ability to define unique workflow rules by department, dollar amount, G/L account or user. | ||
| 16 | Ability for user to check on status of workflow approval. | ||
| 17 | Ability to create a pick ticket if item is in inventory. | ||
| 18 | Ability to create requisition for a particular work order and task. | ||
| 19 | Ability to set and track the number and dollar amount of requisitions to a certain vendor and require a justification note if usage exceeds either limit in a set # of days. | ||
| 20 | Ability to accommodate a decentralized purchase requisition process that allows requisitions to be entered online by all City departments. | ||
| 21 | |||
| 22 | Ability to drill down to supporting documents or transactions all the way down to the image of the source document (ie. PO, invoices, checks, quotes, etc.). | ||
| 23 | Ability to display a required document checklist on the requisition entry screen. | ||
| 24 | Ability to search requisitions by vendor, amount, status, keyword, and other user-defined criteria. | ||
| 25 | Ability to export requisition data directly to Excel from inquiry screens. | ||
| 26 | Ability to allow uusers to copy an existing requisition to create a new requisition. | ||
| 27 | Ability to display all related documents, including purchase orders, invoices, and contracts, within the requisition record. | ||
| Purchase Orders | |||
| 28 | Ability to create PO user defined fields that are available during PO entry process. | ||
| 29 | Ability to customize one site-wide purchase order layout/format (and create templates). | ||
| 30 | Ability to perform a change order on an existing requisition/PO, and to require workflow approvals associated with total requisition/PO. | ||
| 31 | Ability to create PO change orders (modifications) to the original PO document and update G/L accordingly. | ||
| 32 | Provide for the following carry forward methods for POs at year end: GAAP; Budgetary; GAAP/Budgetary; Transfer. | ||
| 33 | Ability to disencumber the PO from the prior year; re-encumber and charge the expense to the current year. | ||
| 34 | Ability to convert a purchase order into a blanket purchase order. | ||
| 35 | Ability to cancel blanket purchase orders. | ||
| 36 | Ability to close all selected open purchase orders/encumbrances and requisitions/pre-encumbrances with user-defined parameters at year-end. | ||
| 37 | Ability to generate reports of all purchase orders based on calculated user-defined criteria (e.g., >$2500 or between 5/1/ and 6/1). | ||
| 38 | Ability to mass cancel selected POs prior to year end processing. Based on security so only authorized personnel can do so. | ||
| 39 | Ability to carry forward open encumbrances to the new year. | ||
| 40 | Ability to indicate on the PO if three-way matching is required. | ||
| 41 | Ability for PO receiving to automatically generate an inventory receipt transaction. | ||
| 42 | Ability to match open PO encumbrances to associated GL accounts. | ||
| 43 | Ability to have multiple line items on a PO. | ||
| 44 | Field to identify retainage percentage; automatically calculate on receiving |
reports and distribute across accounts.
| 45 | Allow receiver to submit retainage payable in the system and validate against balance. |
| 46 | With appropriate rights, allow for closing a PO with open retainage and a reason. |
| 47 | Ability to have multiple accounts on a PO line. |
| 48 | Ability to have unlimited description on PO line items. |
| 49 | Ability to have unlimited comment text on requisitions/POs. |
| 50 | Ability to define ship-to locations per PO line item. |
| 51 | Ability for a purchase order that has requisitions from multiple departments to have approvers from all involved departments. |
| 52 | Ability to change account information in an existing purchase order without cancelling the existing line item and creating a new line to update the account information. |
| 53 | Ability to add approvers to the approval workflow based upon cost threshholds being met. |
| 54 | Ability to add approvers to the approval workflow ad-hoc. |
| Punch Out to Approved Vendors | |
| 54 | Ability for Purchasing to establish a pre-approved punchlist of items with certain vendors that departments can order for just-in-time delivery. |
| 55 | Ability for departments to access pre-approved punchlists of items through the Purchasing module, place the order, and record the order in the system. |
| Reporting & Querying | |
| 56 | Ability to produce a Requisition Report, which can be sorted by buyer. |
| 57 | Ability to display and/or print any / all reports and screens. |
| 58 | Ability to generate vendor reports based upon user defined criteria. |
| 59 | Ability to track and report on requisition, purchase order and receiving information. |
| 60 | Ability to merge requisitions into single PO to be sent to vendor. |
| 61 | Ability to create an configurable number of user defined fields on a requisition. |
| 62 | Ability to create both current and next year requisitions with proper authorization. |
| 63 | Ability to copy line items within a requisition or copy the entire requisition to a new one. |
| 64 | Ability to establish shipping locations per line item. |
| Compliant |
| Alternative Method |
| Modification Required |
| Non-Compliant |
Contracts Management
| Contracts Management | |||
| # | Requirement | Response | Comments |
| General Requirements | |||
| 1 | Ability to enter, track and inquire basic contract information, including: Contract name; Contract number; Contract amount; Contract type (IFB, RFSP, RFQ); Contract amount; Contract changes (dollar amount); Audit required; Payments against the contract; Budget line item; Provider name and address; Contract balance; Contract starting date; Contract ending date; Contract extensions; Additions to the contract; Department; Commodity code; Bonds; Insurance; Cooperative contract (yes/no); Ordinance Number; Tax standing; Federal department; State registration status; Date approved by Council; Contract Renewal Date; Insurance Renewal Date. | ||
| 2 | Ability to track the following fields for a prime contractor: Contract name; Contract number/ID; Contractor name; Contractor address; Contractor contact info (phone, fax, email); Contract dollar amount; Contract start date; Contract end date; Release number; Ordinance number; Vendor number; Alternate emergency contact info (phone, fax, email). | ||
| 3 | Ability to attach and store supporting documents (e.g., contracts, packing slips, receiving documents) within the system. | ||
| 4 | Ability to route the specification documents electronically to the correct Department for review/revisions. | ||
| 5 | Ability to view and approve contracts within the system. | ||
| Contract Initiation and Approval Process | |||
| 6 | Ability to handle certifications of contracts over multiple fiscal years. | ||
| 7 | Ability to convert awarded bids to approved contract. | ||
| 8 | Ability to allow multiple contracts per vendor. | ||
| 9 | Ability to display approval routing paths prior to requisition or contract submission. | ||
| 10 | Ability to display real-time approval status for requisitions, purchase orders, and contracts. | ||
| 11 | Ability to automatically route requisitions, purchase orders, and contracts through configurable approval workflows. | ||
| 12 | Ability to allow for multiple items per contract. | ||
| Contract Entry & Tracking | |||
| 13 | Ability to track multiple contracts to a single project. | ||
| 14 | Ability to track a single contract to multiple projects. | ||
| 15 | Ability to budget and encumber contracts and project accounting data. | ||
| 16 | Ability to track several purchase orders or other reference documents within a single contract. | ||
| 17 | Ability to create Contract user defined fields. | ||
| 18 | Ability to track and flag contract expiration/extension dates. | ||
| 19 | Ability to provide functionality to administer a process whereby departmental input can be captured and tracked on vendor service performance against a contract. | ||
| 20 | Ability to attach comments to each contract for users with proper security to view and update. Comments could be free-form or standard user-defined (selected from a menu or drop-down list). | ||
| 21 | Ability for the system to notify Purchasing in advance (user-defined period) as to when a Contract is due for renewal. | ||
| 22 | Ability for the system to notify Purchasing when the vendor's insurance is expiring. | ||
| 23 | Ability to display contract expiration dates on the contract summary screen. | ||
| 24 | Ability to display contract total value and remaining balance in real time. | ||
| 25 | Ability to link contracts directly to requisitions and purchase orders. | ||
| 26 | Ability to display remaining contract balances within the purchase order screen. | ||
| 27 | Ability to display real-time purchase order status, including open, partially received, and closed. | ||
| 28 | Ability to allow partial receiving against a purchase order with tracking of remaining quantities and balances. | ||
| 29 | Ability to store copy of contract. | ||
| Contract Change Management | |||
| 30 | Ability to accommodate subsequent contract change orders to update dollar amounts and durations. | ||
| 31 | Ability to add comments for reason of change orders. | ||
| 32 | Ability to update requisitions, purchase orders, and contracts with appropriate audit tracking of changes. | ||
| 33 | Ability to maintain version history and change tracking for contracts. | ||
| 34 | Ability to provide reports on the history of the contract includng change orders. | ||
| Payments | |||
| 35 | Ability to view all payments at a detail level that are associated with a specific contract number. | ||
| 36 | Ability to print detailed payment information for a specific vendor name and distinguish payments to a vendor for different program activities. | ||
| 37 | Ability to track multiple encumbrances and payments against a single contract. | ||
| 38 | Ability to support tracking of received goods and services again purchase orders for payment validation. | ||
| 39 | Ability to generate payments to contractors based on unit pricing for multiple contract line items. | ||
| Deobligation/Decertification/Cancellation | |||
| 40 | Ability to decertify contracts. | ||
| 41 | Ability to decertify all selected contracts without having to access each individual PO for the contract. | ||
| 42 | Ability to maintain a decertification list with the following information: Contract type; Contract begin date; Contract end date; Vendor name; Vendor number; Funding; Contract name/description; Renewal date. | ||
| 43 | Ability to update purchase order and contract balances based on partial receipts, cancellations, or closeout activities | ||
| 44 | Ability to support closure or cancellation of requisitions, purchase orders, and contracts with appropriate audit tracking. | ||
| 45 | Ability to decertify by each line individually, and all lines in a batch. | ||
| Reporting & Querying | |||
| 46 | Ability to track (which step, date, etc.) the status of each step in the contracting process. | ||
| 47 | Ability to search and reports/queries on contract expiration dates given certain parameters (e.g., you should be able to look up all of a department’s contracts that are due to expire within the next 3 months, 6 months, 12 months). | ||
| 48 | Ability to report historical contracts in detail. | ||
| 49 | Ability to report all associated information on a contract, such as POs issued from that contract, payments made, free balance, contract expiration date, vendor, etc. | ||
| 50 | Ability to generate reports detailing every contract authorized along with the following information: Contract name; Contract type; Contract begin date; Contract end date; Vendor name; Vendor number; Contract information. | ||
| 51 | Ability to track and report, by account number, expenditures & revenue for each individual contract, including budget to actual comparisons by user-defined period (i.e., monthly, quarterly, daily, contract year, fiscal year, contract term). | ||
| 52 | Ability to allocate a contract by any segment of the GL account code. | ||
| 53 | Ability to allocate a contract by yearly dollar total. | ||
| 54 | Ability to roll non-expended contract amounts to the next year. | ||
| 55 | Ability to use both current and next year contract dollars while working in the current year. | ||
| 56 | Ability to generate milestones for contract events. | ||
| 57 | Ability to view all requisitions, purchase orders, and invoices ties to a contract and drill into these documents to view specific details. | ||
| 58 | Ability to export purchase order and contract data, including line-level detail, directly to Excel. | ||
| 59 | Ability to provide automated alerts and notifications for upcoming contract expirations. | ||
| 60 | Ability to view all requisitions, purchase orders, and invoices ties to a contract and drill into these documents to view specific details. |
| Compliant |
| Alternative Method |
| Modification Required |
| Non-Compliant |
File details come from the government source that posted it. Updated .