COSC_ATT_E_Requirments.xlsx
XLSX spreadsheet 129 KB Posted
- Attached to
- Enterprise Resource Planning (ERP) Software and Implementation Services State and local contract opportunity
- Solicitation number
- 2026-027
- Issued by
- Polk County, Florida
About this file
Summary of City of St. Cloud ERP Functional Requirements Document
This document is a comprehensive functional requirements spreadsheet for the City of St. Cloud, Florida's Enterprise Resource Planning (ERP) system procurement, containing 1,623 detailed system requirements across Finance, Human Resources, Procurement, and Capital Asset Management modules. The City seeks an integrated ERP solution with tight integration between Finance and HR/Payroll functions to replace its legacy AS 400-based Central Square system (in use since 2005) and several ancillary systems including OpenGov (budget), Cognos (reporting), HRIS, ExecuTime (timekeeping), and NeoGov (recruitment). The RFP was released on April 19, 2026, with a non-mandatory pre-response conference scheduled for May 4, 2026, a question submission deadline of May 18, 2026, and a proposal response deadline of June 9, 2026, at 10:00 a.m. submitted electronically through the City's e-Procurement portal. Committee evaluation commences June 15, 2026, with interviews and software demonstrations scheduled for the weeks of July 20, August 3, and August 10, 2026. A Notice of Intent to Award is anticipated by August 28, 2026, with contract negotiations expected between September and October 2026. Implementation is targeted to begin in November 2026, with a go-live date of October 2028.
The functional requirements document outlines specific system capabilities across 19 functional areas, including general ledger setup, budget control, journal entries, financial reporting, vendor management, invoice processing, accounts payable and receivable, asset management, human resources administration, benefits management, payroll processing, time entry and approval, procurement workflows, capital improvement planning, and treasury management. The requirements specify integration points with retained systems including Operative IQ (fire department assets), CityWorks (work orders), RecTrac (facility rentals), WasteWorks (utilities), and LaserFiche (document storage). Data conversion requirements span multiple modules with estimated record volumes ranging from 10 to 100,000 records. The City, with an annual budget of approximately $214.8 million and approximately 730 permanent and seasonal staff, does not disclose a specific award value or budget range. All proposers must demonstrate financial stability, provide current insurance certificates, and comply with federal requirements under 2 CFR Part 200 Uniform Guidance and Florida statutory requirements regarding public entity crimes, E-Verify compliance, drug-free workplace certification, and debarment standards. Multi-vendor proposals are permitted with clearly defined roles and responsibilities.
View the file
Other files for this state and local contract opportunity
Show all 20
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
Functional Requirements City of St. Cloud, FL
| Attachment E: Functional Requirements | |||||||
| Column E: Available Responses | |||||||
| Y | Requirement Met and Proposed (Standard features in the generally available product) | ||||||
| Y-ND | Requirement Met and Proposed (Features that are not offered as a generally available product or require custom development) | ||||||
| N | Requirement Not Met with Proposal | ||||||
| I | Need More Information/Discussion | ||||||
| Column F: Available Responses | |||||||
| S | Requirement and Feature Supported by Software Developer | ||||||
| TPS | Requirement and Feature Supported by Third Party | ||||||
| NS | Requirement and Feature Not Supported | ||||||
| NOTE: | All exceptions and assumptions should be listed in the comments field | ||||||
| Req.# | Function | Process | Requirement | Implementation Response | Support Response | Module / System | Comments |
| 1 | ACC | General Ledger Set Up | System will provide a chart of account structure with multiple independent segments | ||||
| 2 | ACC | General Ledger Set Up | System will provide a chart of account structure that accommodates project/grant tracking | ||||
| 3 | ACC | General Ledger Set Up | System will provide budgeting capabilities that are directly integrated to the General Ledger and all accounting structures | ||||
| 4 | ACC | General Ledger Set Up | System will provide general and project ledgers that use alpha numeric chart of account segments | ||||
| 5 | ACC | General Ledger Set Up | System will provide a validation process of segment combinations on system transactions | ||||
| 6 | ACC | General Ledger Set Up | System will provide two-way feeds with real-time information for its General, Budget, and Projects/Grants Ledgers | ||||
| 7 | ACC | General Ledger Set Up | System will provide Chart of Accounts segments for "Programs" that can extend across the entire organization (as needed) | ||||
| 8 | ACC | General Ledger Set Up | System will provide grant ledgers for tracking grants | ||||
| 9 | ACC | General Ledger Set Up | System will provide project ledgers, or similar, for tracking project details | ||||
| 10 | ACC | General Ledger Set Up | System will enable segments of the Chart of Accounts to be grouped on a user-defined basis into multiple reporting hierarchies (by object for fund) | ||||
| 11 | ACC | General Ledger Set Up | System will designate an account as active (available for posting, budgeting) | ||||
| 12 | ACC | General Ledger Set Up | System will designate an account as inactive (not available for posting and budgeting) | ||||
| 13 | ACC | General Ledger Set Up | System will only allow transactions to post to active accounts within any open period | ||||
| 14 | ACC | General Ledger Set Up | System will restrict certain types of activity from posting to accounts (e.g., can't use PO against salary account) | ||||
| 15 | ACC | General Ledger Set Up | System will prevent accounts from being deleted if any activity is posted to them | ||||
| 16 | ACC | General Ledger Set Up | System will enable department requests for changes/additions to the Chart of Accounts | ||||
| 17 | ACC | General Ledger Set Up | System will provide a different review and approval process based on the structure, or segment, of the requested change (e.g., Grant request to Grants office) | ||||
| 18 | ACC | Budget Control | System will provide a budget control soft error setting (e.g., Warn user but allow) | ||||
| 19 | ACC | Budget Control | System will provide a budget hard error setting (e.g., Do not allow user) | ||||
| 20 | ACC | Budget Control | System will provide budgeting at one level while controlling at a different level (Example: budget by account/object but conduct budget control at program level) | ||||
| 21 | ACC | Budget Control | System will enable budget control at summary roll up of account/object | ||||
| 22 | ACC | Budget Control | System will enable budget control at summarized roll up categories | ||||
| 23 | ACC | Budget Control | System will enable departments to track detail at a lower level than budget control is established in a segment | ||||
| 24 | ACC | Budget Control | System will provide budget control for project and grant ledgers | ||||
| 25 | ACC | Journal Entry | System will enable journal entries to be entered by departments and routed through workflow for review, approval and posting | ||||
| 26 | ACC | Journal Entry | System will provide journal entries that are posted in real time and are available for reporting | ||||
| 27 | ACC | Journal Entry | System will run reports separately on posted or unposted journal entries | ||||
| 28 | ACC | Journal Entry | System will enable multiple line items for journal entries (please indicate any limitations in the notes column) | ||||
| 29 | ACC | Journal Entry | System will ensure that journal entries record the source of the transaction (e.g., manual entry or automated entry from another module) | ||||
| 30 | ACC | Journal Entry | System will ensure that journal entries are validated against the chart of account structure for valid accounts | ||||
| 31 | ACC | Journal Entry | System will ensure that journal entries are validated against available funds (budget check or cash availability check) | ||||
| 32 | ACC | Journal Entry | System will provide approved overrides for budget checks and restrictions (i.e. Finance) | ||||
| 33 | ACC | Journal Entry | System will validate journal entries against balancing entries (making sure all entries balance) | ||||
| 34 | ACC | Journal Entry | System will enable users to import journal entries from spreadsheets or text files (e.g., Microsoft Excel, Text) | ||||
| 35 | ACC | Journal Entry | System will ensure imported journal entries from interfaced systems go through budget and edit checks for each transaction | ||||
| 36 | ACC | Journal Entry | System will ensure imported transactions from spreadsheets are validated using the same business rules as transactions made in the system | ||||
| 37 | ACC | Journal Entry | System will batch post journal entries | ||||
| 38 | ACC | Journal Entry | System will provide “segregation-of-duties” checks so that users cannot post journal entries they created to the General Ledger | ||||
| 39 | ACC | Journal Entry | System will enable creating journal entries from previously entered journal entry formats (copy journal) by line item | ||||
| 40 | ACC | Journal Entry | System will enable creating journal entries from previously entered journal entry formats (copy journal) by entire journal entry | ||||
| 41 | ACC | Journal Entry | System will enable users to reverse journal entries with appropriate security and approvals | ||||
| 42 | ACC | Journal Entry | System will provide scheduled auto-reversals (deferrals at year-end) | ||||
| 43 | ACC | Journal Entry | System will provide "required" data fields for journal entries and will prevent transactions from posting until all "required" fields are completed | ||||
| 44 | ACC | Journal Entry | System will enable users to attach files to journal entries with a predefined retention period | ||||
| 45 | ACC | Journal Entry | System will enable the posting of transactions for multiple fiscal years at the same time (with proper permissions) | ||||
| 46 | ACC | Journal Entry | System will provide security that restricts the accounts users can post journal entries to | ||||
| 47 | ACC | Journal Entry | System will prevent duplicate journal entries and will provide effective dating for journal entries and scheduling (e.g., posting does not occur until effective date). | ||||
| 48 | ACC | Journal Entry | System will automatically balance journal entry by cash | ||||
| 49 | ACC | Recurring Journal Entry | System will provide templates and notifications for recurring journal entries | ||||
| 50 | ACC | Recurring Journal Entry | System will provide templates and notifications for recurring journal entries with the same dollar value | ||||
| 51 | ACC | Recurring Journal Entry | System will provide templates and notifications for recurring journal entries with varying dollar amounts | ||||
| 52 | ACC | Recurring Journal Entry | System will provide setting recurring journal entries occur at regular frequencies (e.g., setting start and stop dates) | ||||
| 53 | ACC | Recurring Journal Entry | System will enable journal entries to be scheduled (e.g., lease/debt schedules) | ||||
| 54 | ACC | Recurring Journal Entry | System will provide the ability to process a “trial post” Journal Entry, without truly posting to the GL, so the users can see the impact of the JE, and if there is a mistake before they finalize | ||||
| 55 | ACC | Month End Close | System will provide closing of months | ||||
| 56 | ACC | Month End Close | System will provide a month-end checklist noting needed actions (e.g., pulling in investment revenue) to help users complete all necessary tasks. | ||||
| 57 | ACC | Internal Transfers | System will create automated "due to/due from" transactions | ||||
| 58 | ACC | Internal Transfers | System will create inter-entity billings based on direct transaction costs | ||||
| 59 | ACC | Internal Transfers | System will create inter-entity billings based on indirect transaction costs | ||||
| 60 | ACC | Internal Transfers | System will create inter-entity billings based on cost allocations | ||||
| 61 | ACC | Internal Transfers | System will ensure all inter-entity transactions are self-balancing | ||||
| 62 | ACC | Internal Transfers | System will ensure all inter-entity transactions are facilitated by departmental approvals | ||||
| 63 | ACC | Annual Close | System will provide an annual closing process | ||||
| 64 | ACC | Annual Close | System will provide the capability to accrue payables/receivables to the proper period | ||||
| 65 | ACC | Annual Close | System will provide multiple periods, beyond 12, for adjusting entries and annual reporting (please specify how many periods the system can support) | ||||
| 66 | ACC | Annual Close | System will roll encumbrances to next year carrying forward budget | ||||
| 67 | ACC | Annual Close | System will roll encumbrances to next year carrying forward encumbrance | ||||
| 68 | ACC | Annual Close | System will remove any unspent funds and carries forward the budget when rolled purchase orders are closed in the new year | ||||
| 69 | ACC | Annual Close | System will provide multiple types of period closes (i.e., Year-End, Month End, Quarter-End) | ||||
| 70 | ACC | Annual Close | System will provide internal controls that can limit access (e.g., only allow the Finance department to make adjustments after the financial period is closed). | ||||
| 71 | ACC | Financial Reporting | System will provide a flexible reporting and query capability on any segment(s) within the financial structure | ||||
| 72 | ACC | Financial Reporting | System will provide an inquiry function that can drill down (or across) from summaries to details within the financial structure | ||||
| 73 | ACC | Financial Reporting | System will provide Statement of Revenues and Expenditures | ||||
| 74 | ACC | Financial Reporting | System will provide annual financial report: Government-Wide Statements: Statement of Net Assets | ||||
| 75 | ACC | Financial Reporting | System will provide annual financial report : Government-Wide Statements: Statement of Activities | ||||
| 76 | ACC | Financial Reporting | System will provide annual financial report : Balance Sheet - All Governmental Funds | ||||
| 77 | ACC | Financial Reporting | System will provide reconciliation of Balance sheet - Governmental funds to statement of net assets. | ||||
| 78 | ACC | Financial Reporting | System will provide narrative drafting capability for annual financial report (Management's Discussion & Analysis, Transmittal Letter, Notes, Statistical Section) with the ability to link to data from financial statements | ||||
| 79 | ACC | Financial Reporting | System will provide annual financial report : Statement of Revenues, Expenditures, and Changes in Fund Balances - Governmental Funds | ||||
| 80 | ACC | Financial Reporting | System will provide annual financial report : Statement of Revenues, Expenditures, and Changes in Fund Balances - Budget to Actual - by Governmental Funds | ||||
| 81 | ACC | Financial Reporting | System will provide annual financial report : Statement of Net Assets - Proprietary Funds | ||||
| 82 | ACC | Financial Reporting | System will provide annual financial report : Statement of Revenues, Expenses, and changes in net assets - proprietary funds by fund | ||||
| 83 | ACC | Financial Reporting | System will provide annual financial report : Statement of Revenues, Expenses, and changes in net assets - proprietary funds by function | ||||
| 84 | ACC | Financial Reporting | System will provide annual financial report : Statement of Cash Flows - Proprietary Funds | ||||
| 85 | ACC | Financial Reporting | System will provide annual financial report : Statement of Net Assets | ||||
| 86 | ACC | Financial Reporting | System will provide annual financial report : Statement of Activities by function | ||||
| 87 | ACC | Financial Reporting | System will provide annual financial report: Schedule of Revenue, Expenditures, and Changes in Fund Balance - Budget to Actual | ||||
| 88 | ACC | Financial Reporting | System will provide accruals conversion to support GASB reporting standards | ||||
| 89 | ACC | Financial Reporting | System will enable report scheduling for distribution to specific system users | ||||
| 90 | ACC | Financial Reporting | System will enable the import/export of Microsoft Office documents (i.e. Word, Excel, PDF) for appending to reports for distribution throughout the system | ||||
| 91 | ACC | Financial Reporting | System will enable conversion entries to ensure funds balance (e.g., to get the data to a place where staff can create a government wide-statement in the “ACFR Builder” systems) | ||||
| 92 | ACC | Financial Reporting | System will provide monthly interim reports (budget/actual information) | ||||
| 93 | ACC | Financial Reporting | System will provide reconciliation of the Statement of Revenue, Expenditures, and Changes in Fund Balances of Governmental Funds to the Statement of Activities | ||||
| 94 | ACC | Financial Reporting | System will generate a report that shows the City's cash position. | ||||
| 95 | AP | Vendor File | System will use one vendor file for purchasing, accounts payable, and credit cards | ||||
| 96 | AP | Vendor File | System will provide multiple telephone numbers (types), and multiple email addresses | ||||
| 97 | AP | Vendor File | System will link vendor files to customer files for accounts receivable | ||||
| 98 | AP | Vendor File | System will prevent duplicate vendors using multi-field checks (e.g., Tax ID, legal name, other identifiers) | ||||
| 99 | AP | Vendor File | System will prevent duplicate vendors by identifying duplicate vendor EINs | ||||
| 100 | AP | Vendor File | System will prompt users to collect additional information from vendors when necessary | ||||
| 101 | AP | Vendor File | System will enable users with security access to temporarily deactivate vendors | ||||
| 102 | AP | Vendor File | System will deactivate vendors that have not been used within a City-defined timeframe | ||||
| 103 | AP | Vendor File | System will enable users with security access to merge two vendors, including each vendor's history | ||||
| 104 | AP | Vendor File | System will provide parent-child relationships between vendor records | ||||
| 105 | AP | Vendor File | System will maintain multiple address types | ||||
| 106 | AP | Vendor File | System will maintain multiple location addresses for each vendor | ||||
| 107 | AP | Vendor File | System will maintain foreign addresses | ||||
| 108 | AP | Vendor File | System will identify default payment remittance addresses | ||||
| 109 | AP | Vendor File | System will identify 1099 vendors | ||||
| 110 | AP | Vendor File | System will maintain multiple types of 1099 vendors | ||||
| 111 | AP | Vendor File | System will identify cumulative purchase history by vendor to identify common vendors | ||||
| 112 | AP | Vendor File | System will maintain different types of vendors (onetime, ongoing, etc.) and report based on the “type” of vendor | ||||
| 113 | AP | Vendor File | System will enable users to place all vendor payments on hold | ||||
| 114 | AP | Vendor File | System will store vendor payment preferences (e.g., ACH, check, or virtual pay) | ||||
| 115 | AP | Vendor File | System will identify vendor-specific terms and conditions for purchase orders | ||||
| 116 | AP | Vendor File | System will confirm that vendors are not City employees | ||||
| 117 | AP | Vendor File | System will store vendors' Certificate of Insurance | ||||
| 118 | AP | Vendor File | System will auto-populate vendors' information based on W-9s | ||||
| 119 | AP | Vendor File | System will track MBE/WBE designations | ||||
| 120 | AP | Vendor Self-Service | System will enable vendors to upload related documents to match POs | ||||
| 121 | AP | Vendor Self-Service | System will enable vendors to register with the City as a prospective vendor | ||||
| 122 | AP | Vendor Self-Service | System will enable vendors to update contact information | ||||
| 123 | AP | Vendor Self-Service | System will enable vendors to classify goods/services using City commodity codes and NIGP codes | ||||
| 124 | AP | Vendor Self-Service | System will enable vendors to upload W-9 and other documentation through self-service | ||||
| 125 | AP | Vendor Self-Service | System will enable vendors to access purchase orders and submit invoices | ||||
| 126 | AP | Vendor Self-Service | System will enable vendors to access and submit bids/quotes | ||||
| 127 | AP | Vendor Self-Service | System will enable vendors to access payment status | ||||
| 128 | AP | Vendor Performance | System will track vendor performance information and include a comment field | ||||
| 129 | AP | Vendor Performance | System will enable users to place vendors in debarment status | ||||
| 130 | AP | Invoice Processing | System will be configured to add differing levels of approvers | ||||
| 131 | AP | Invoice Processing | System will scan and process invoices for approval | ||||
| 132 | AP | Invoice Processing | System will provide automated approval workflows | ||||
| 133 | AP | Invoice Processing | System will generate status notifications | ||||
| 134 | AP | Invoice Processing | System will fill information for invoices from purchase orders | ||||
| 135 | AP | Invoice Processing | System will enable users to enter direct claims without purchase orders | ||||
| 136 | AP | Invoice Processing | System will provide approval workflows for invoices from purchase orders and invoices without purchase orders | ||||
| 137 | AP | Invoice Processing | System will route invoices for approval based on amount | ||||
| 138 | AP | Invoice Processing | System will route invoices for approval based on point of entry (entered by department vs. AP) | ||||
| 139 | AP | Invoice Processing | System will route invoices for approval based on PO vs no PO | ||||
| 140 | AP | Invoice Processing | System will route invoices for approval based on chart of account information | ||||
| 141 | AP | Invoice Processing | System will enable users to make partial invoice payments | ||||
| 142 | AP | Invoice Processing | System will apply credit memos to invoices for incorrect invoices or POs | ||||
| 143 | AP | Invoice Processing | System will enable payment of multiple purchase orders from one invoice | ||||
| 144 | AP | Invoice Processing | System will enable multiple invoices to be received and processed for one purchase order | ||||
| 145 | AP | Invoice Processing | System will automatically check for and prevent duplicate invoice numbers for the same vendor to avoid double-payment | ||||
| 146 | AP | Invoice Processing | System will enable files to be attached to invoices (e.g., scanned image of invoice) | ||||
| 147 | AP | Invoice Processing | System will provide OCR of scanned invoices | ||||
| 148 | AP | Invoice Processing | System will not limit characters on invoice numbers (Please note limitations, e.g., special characters, formatting, etc.) | ||||
| 149 | AP | Invoice Processing | System will enable users to check status of submitted invoices | ||||
| 150 | AP | Invoice Processing | System will enable users to search invoice by project code, item description, or creator | ||||
| 151 | AP | Invoice Processing | System will process payments to one-time customers | ||||
| 152 | AP | Credit Memo | System will process refunds to one-time customers | ||||
| 153 | AP | Credit Memo | System will enable users to upload refund payments from other systems/third-party applications | ||||
| 154 | AP | Credit Memo | System will enable users to apply credit memos to invoices | ||||
| 155 | AP | Credit Memo | System will set a minimum dollar amount checks can be issued for | ||||
| 156 | AP | Matching | System will provide 2 way matching (e.g., purchase order, invoice) | ||||
| 157 | AP | Matching | System will provide 3 way matching (e.g., purchase order, receiving document, invoice) | ||||
| 158 | AP | Matching | System will provide matching at the line-item level | ||||
| 159 | AP | Matching | System will enable limits on PO and invoice prices for matching based on percentages and limits (e.g., invoice can't be greater than 105% of purchase order or $5 [whichever is greater]) | ||||
| 160 | AP | Matching | System will exclude freight and shipping charges from matching requirements | ||||
| 161 | AP | Matching | System will provide notifications when there is not a match | ||||
| 162 | AP | Payment Process | System will enable the creation of templates for recurring AP invoices with pre-defined account distribution | ||||
| 163 | AP | Payment Process | System will schedule approved invoices using configurable drivers (e.g., invoice date, user-entered date, grouped by department) | ||||
| 164 | AP | Payment Process | System will print checks on pre-printed check stock | ||||
| 165 | AP | Payment Process | System will print checks with MICR encoding | ||||
| 166 | AP | Payment Process | System will print checks with electronic signatures | ||||
| 167 | AP | Payment Process | System will pay vendors electronically (e.g., ACH, wire transfer, etc.) using standard NACHA formats (ctx) | ||||
| 168 | AP | Payment Process | System will enable printing of checks without any impact on other users in system | ||||
| 169 | AP | Payment Process | System will print checks based on regular schedule (pay cycle) | ||||
| 170 | AP | Payment Process | System will print on-demand checks (single check printing) | ||||
| 171 | AP | Payment Process | System will create/sort checks based upon chart of account information (e.g., fund or department) | ||||
| 172 | AP | Payment Process | System will create/sort checks based upon vendor | ||||
| 173 | AP | Payment Process | System will create/sort checks based upon payment type (e.g., employee reimbursement, one time vendors, etc.) | ||||
| 174 | AP | Payment Process | System will automatically save check images | ||||
| 175 | AP | Payment Process | System will send electronic remittance advice for EFT payments to vendor through email | ||||
| 176 | AP | Payment Process | System will enable users to issue multiple checks to one vendor in a single check run | ||||
| 177 | AP | Payment Process | System will enable users to issue one check for multiple invoices in a single check run | ||||
| 178 | AP | Payment Process | System will itemize invoices (including the vendor invoice number) on the remittance advice | ||||
| 179 | AP | Payment Process | System will enable users to place payments on hold | ||||
| 180 | AP | Payment Process | System will enable users to broadcast messages that will appear on all AP check stubs | ||||
| 181 | AP | Payment Process | System will enable users to enter messages for specific vendors that appear on their specific check stubs | ||||
| 182 | AP | Payment Process | System will provide positive pay (Status and Vendor Name - Payee Positive) | ||||
| 183 | AP | Payment Process | System will provide a service date field on invoices | ||||
| 184 | AP | Payment Process | System will ensure the General Ledger records transactions according to GAAP standards | ||||
| 185 | AP | Payment Process | System will enable users to download records from the system/cloud while ensuring data security | ||||
| 186 | AP | Employee Reimbursement | System will enable employees to enter pre-travel and travel advance requests | ||||
| 187 | AP | Employee Reimbursement | System will provide pre-travel (advance request) approval workflows | ||||
| 188 | AP | Employee Reimbursement | System will provide GSA per diem and mileage amounts for travel | ||||
| 189 | AP | Employee Reimbursement | System will provide self-service reimbursement requests with receipt/document upload abilities in one process | ||||
| 190 | AP | Employee Reimbursement | System will link employee reimbursement requests with travel advances | ||||
| 191 | AP | Employee Reimbursement | System will ensure all expense reimbursements follow approval workflows | ||||
| 192 | AP | Employee Reimbursement | System will track and reimburse multiple types of reimbursements (e.g., travel, training, mileage, uniform, etc.) | ||||
| 193 | AP | Employee Reimbursement | System will include per diem travel amounts in employees' paychecks (not a separate check) | ||||
| 194 | AP | Retainage | System will automatically calculate retention amounts and remove them from invoices | ||||
| 195 | AP | Retainage | System will automatically apply retention amounts to invoice payments from vendor files, contracts, and purchase orders | ||||
| 196 | AP | Retainage | System will release retainage by selected payments, based on user-defined approval | ||||
| 197 | AP | Retainage | System will release retention by amount | ||||
| 198 | AP | Void and Cancel | System will enable users to cancel warrants, and will automatically correct all accounting entries to reverse payment, including contract balances | ||||
| 199 | AP | Void and Cancel | System will enable users to void checks and re-issue replacement checks | ||||
| 200 | AP | Void and Cancel | System will enable users to cancel prior years' checks, only void current year checks, and will automatically credit back designated accounts | ||||
| 201 | AT | General Requirements | System will provide drill-down capabilities for recruitment candidates' profiles | ||||
| 202 | AT | General Requirements | System will track performance management records and provide role-based security for accessibility | ||||
| 203 | AT | General Requirements | System will purge records based on user-defined timeframes | ||||
| 204 | AT | Job Announcement | System will create job announcements to fill any open positions and job classifications | ||||
| 205 | AT | Job Announcement | System will create job announcements that contains all City required data (data may be different for each job announcement) | ||||
| 206 | AT | Job Announcement | System will classify pre-requisite information as either mandatory or desired | ||||
| 207 | AT | Job Announcement | System will create job posting announcements with position module information and will enable users to add/edit unique information | ||||
| 208 | AT | Job Announcement | System will include salary/comp ranges for positions job postings | ||||
| 209 | AT | Job Announcement | System will route job announcements through approval workflows prior to posting | ||||
| 210 | AT | Job Announcement | System will track posting dates for job announcements | ||||
| 211 | AT | Job Announcement | System will provide automatic job postings (post-approval) to third party sites (please list the job boards that the postings will automatically post to in the comments) | ||||
| 212 | AT | Job Announcement | System will restrict users access to recruitment based on their business criteria (e.g. PD, Fire, City) | ||||
| 213 | AT | Job Announcement | System will integrate with social media for application pool/recruiting (e.g. Linked In, etc.) | ||||
| 214 | AT | Job Announcement | System will provide text communications throughout the recruitment process | ||||
| 215 | AT | Job Announcement | System will provide digital signature functionality | ||||
| 216 | AT | Job Announcement | System will enable authorized users to import/export data from the system | ||||
| 217 | AT | Job Announcement | System will be accessible in multiple languages | ||||
| 218 | AT | Job Announcement | System will be ADA compliant | ||||
| 219 | AT | Job Announcement | System will process information in real-time | ||||
| 220 | AT | Job Announcement | System will feed job postings (system-created) to other third-party systems | ||||
| 221 | AT | Job Announcement | System will pull job postings created in other third-party systems | ||||
| 222 | AT | Job Application | System will manage different application templates for different recruitment types (e.g., temporary, internal, full time, etc.) | ||||
| 223 | AT | Job Application | System will include job application templates that contain Citywide questions and standard information | ||||
| 224 | AT | Job Application | System will enable users to add position-specific questions to the job application templates | ||||
| 225 | AT | Job Application | System will enable applicants to save multiple resumes | ||||
| 226 | AT | Job Application | System will enable applicants to create and save profiles/applications, even if they are not ready to apply for a specific job at that time | ||||
| 227 | AT | Job Application | System will enable applicants to apply to more than one position, and/or allow City staff to recommend the applicant to other jobs besides the one they originally applied for | ||||
| 228 | AT | Job Application | System will accept applications for volunteers and/or non-compensated positions such as Boards, Committees, etc. | ||||
| 229 | AT | Job Application | System will prompt applicants in the application pool to update their resume after a user-defined space of time | ||||
| 230 | AT | Recruitment Plan | System will purge/remove applications that are in the application pool after a user-defined space of time | ||||
| 231 | AT | Recruitment Plan | System will query applicant pool for certain characteristics (e.g., certifications) | ||||
| 232 | AT | Recruitment Plan | System will enable staff to analyze minimum qualifications against job classification characteristics and qualifications | ||||
| 233 | AT | Recruitment Plan | System will provide detailed reporting metrics for the City’s user-defined recruitment goals | ||||
| 234 | AT | Recruitment Plan | System will extract and analyze data from job descriptions, candidate applications, and current employee pay structures within the same grade to produce fair and data-supported compensation recommendations for all scenarios | ||||
| 235 | AT | Recruitment Plan | System will confirm vacant positions at the time of recruitment | ||||
| 236 | AT | Applicant Self-Service | System will enable users to apply for positions via the web | ||||
| 237 | AT | Applicant Self-Service | System will send automatic notifications when applications are completed, submitted by applicant, and received | ||||
| 238 | AT | Applicant Self-Service | System will enable applicants to upload files to web application (e.g., resume, certification, etc.) | ||||
| 239 | AT | Applicant Self-Service | System will enable users to create profiles and apply to multiple jobs without re-entering information | ||||
| 240 | AT | Applicant Self-Service | System will track interview dates | ||||
| 241 | AT | Applicant Self-Service | System will enable applicants to review where they are in the hiring process | ||||
| 242 | AT | Applicant Self-Service | System will enable applicants to schedule and confidentially track assessments, interviews, screenings, pre-employment medicals/fitness exams, etc. | ||||
| 243 | AT | EEO Reporting | System will track all EEO information | ||||
| 244 | AT | EEO Reporting | System will manage EEO questionnaires | ||||
| 245 | AT | EEO Reporting | System will hide EEO data from non-authorized users via role-based access (including recruiting managers) | ||||
| 246 | AT | Applicant Tracking | System will pre-screen applicants to determine eligibility based on key requirements | ||||
| 247 | AT | Applicant Tracking | System will retain applications for durations required by law | ||||
| 248 | AT | Applicant Tracking | System will track the application process | ||||
| 249 | AT | Applicant Tracking | System will enable users to add comments about application status | ||||
| 250 | AT | Applicant Tracking | System will identify applicants as past or current employees | ||||
| 251 | AT | Applicant Tracking | System will prevent unauthorized users from viewing confidential information (criminal history, medical info, etc.) | ||||
| 252 | AT | Applicant Tracking | System will notify applicants when positions have been filled or pulled | ||||
| 253 | AT | Applicant Tracking | System will notify departments when positions have been filled or pulled | ||||
| 254 | AT | Applicant Tracking | System will notify departments when applicant statuses have changed (e.g. 'hired' or 'offer accepted' or 'declined') | ||||
| 255 | AT | Applicant Tracking | System will track employee history and applicant's application history (track the number of jobs an applicant has applied for by department) | ||||
| 256 | AT | Applicant Tracking | System will track the history of applicants, including reasons they weren't hired or didn't proceed in the application process (not hired, failed PT test) | ||||
| 257 | AT | Applicant Tracking | System will track exam/assessment scores from third party systems where exams were taken | ||||
| 258 | AT | Eligibility Lists | System will enable users to manually add to or remove applicants from eligibility lists | ||||
| 259 | AT | Eligibility Lists | System will route eligibility lists for approval (e.g., certification by City Manager) | ||||
| 260 | AT | Eligibility Lists | System will maintain referral lists (i.e., applicants that are a good fit for the position) | ||||
| 261 | AT | Eligibility Lists | System will track dates for adding/removing applicants from eligibility lists | ||||
| 262 | AT | Eligibility Lists | System will enable the administration of separate eligibility lists for each job classification | ||||
| 263 | AT | Eligibility Lists | System will enable users to override the system-generated eligibility list | ||||
| 264 | AT | Eligibility Lists | System will manage rolling eligibility lists (list stays active but applicant drops off list after set period of time) | ||||
| 265 | AT | Eligibility Lists | System will maintain multiple eligibility lists for each classification including a main list | ||||
| 266 | AT | New Hire (Onboarding) | System will enable new hires to receive and acknowledge City policies and the employee handbook during onboarding | ||||
| 267 | AT | New Hire (Onboarding) | System will manage personal and City emails for applicants/new hires | ||||
| 268 | AT | New Hire (Onboarding) | System will include an onboarding portal/page for welcome notices, etc. | ||||
| 269 | AT | New Hire (Onboarding) | System will manage pre-requisite new hire training | ||||
| 270 | AT | New Hire (Onboarding) | System will automatically report through/with E-Verify | ||||
| 271 | AT | New Hire (Onboarding) | System will track when level 2 fingerprinting expire | ||||
| 272 | AT | New Hire (Onboarding) | System will assign Employee ID numbers | ||||
| 273 | AT | New Hire (Onboarding) | System will generate notifications when benefits selections are completed | ||||
| 274 | AT | New Hire (Onboarding) | System will change new hire status | ||||
| 275 | BUD | General | System will provide comparative reporting and inquiries throughout the budget process | ||||
| 276 | BUD | General | System will provide an automated iterative communication process throughout budget development (e.g., for changes and updates to budget structures and values) | ||||
| 277 | BUD | General | System will provide unlimited versions (or levels) of the budget both for departmental and city wide requests | ||||
| 278 | BUD | General | System will provide multiple year budgeting and reporting | ||||
| 279 | BUD | General | System will provide multiple year budgeting for projects/grants | ||||
| 280 | BUD | General | System will integrate with MS Excel and MS Word for analysis and documentation | ||||
| 281 | BUD | General | System will provide analysis tools for trend analyses based on budget history | ||||
| 282 | BUD | General | System will integrate with project and grant accounting to provide data for capital budget development and tracking | ||||
| 283 | BUD | General | System will provide multi-year funding source budgeting | ||||
| 284 | BUD | General | System will provide revenue budgeting | ||||
| 285 | BUD | General | System will provide parallel operating and capital budget development processes | ||||
| 286 | BUD | General | System will warn users when budget lines are projected to exceed budget | ||||
| 287 | BUD | General | System will manage line-item budget requests and versioning | ||||
| 288 | BUD | General | System will track multiple funding sources for a single line item | ||||
| 289 | BUD | General | System will enable changes to funding sources after their initial selection | ||||
| 290 | BUD | General | System will translate budget data using visualization tools | ||||
| 291 | BUD | General | System will manage decision-making variables (e.g., FTEs') related to budgeting | ||||
| 292 | BUD | General | System will split revenue between multiple departments and make allocations based on user-defined percentages | ||||
| 293 | BUD | General | System will track budget requests at the line-item level | ||||
| 294 | BUD | General | System will use AI (machine learning) for financial reporting (Explain functionality in comments) | ||||
| 295 | BUD | General | System will use AI (machine learning) for reporting recurring journal entries (Explain functionality in comments) | ||||
| 296 | BUD | General | System will use AI (generative) for reporting unusual/non-recurring journal entries (Explain functionality in comments) | ||||
| 297 | BUD | General | System will use AI (generative) for reporting recurring journal entries (Explain functionality in comments) | ||||
| 298 | BUD | Budget Requests | System will accommodate entering departmental budget details (by accounting structure within a department) | ||||
| 299 | BUD | Budget Requests | System will enable departments to include narratives in their budget requests | ||||
| 300 | BUD | Budget Requests | System will maintain versioning, identifying who makes changes in the system | ||||
| 301 | BUD | Budget Requests | System will enable users to maintain version history while promoting one version for submission to budget development process | ||||
| 302 | BUD | Budget Requests | System will enable users see prior years actuals and prior year budgets in the budget module | ||||
| 303 | BUD | Budget Requests | System will provide ad-hoc and dashboard reporting | ||||
| 304 | BUD | Budget Requests | System will integrate with the HR/payroll system to provide staffing budget data, and FTEs | ||||
| 305 | BUD | Budget Requests | System will provide workflow approvals | ||||
| 306 | BUD | Budget Requests | System will enable entering budget details for project budgets (over multiple years - up to life of project) | ||||
| 307 | BUD | Budget Requests | System will pre-populate budget entry fields with the previous year's adopted budget | ||||
| 308 | BUD | Budget Requests | System will pre-populate budget entry fields based on various user preferences | ||||
| 309 | BUD | Budget Requests | System will prepare budgets for revenues and expenses | ||||
| 310 | BUD | Budget Requests | System will enable departments enter budget requests, including requested budget amounts | ||||
| 311 | BUD | Budget Requests | System will enable departments enter budget requests, including changes/additions/deletions of positions | ||||
| 312 | BUD | Budget Requests | System will enable departments enter narrative information with budget requests (E.g., department goals, challenges, highlights of major changes, etc.) | ||||
| 313 | BUD | Budget Requests | System will enable departments attach documentation when entering budget requests | ||||
| 314 | BUD | Budget Requests | System will group budget requests into decision packages (e.g., multiple line items that go together) | ||||
| 315 | BUD | Budget Requests | System will enable budget requests to be identified as supplemental requests | ||||
| 316 | BUD | Budget Requests | System will prioritize budget requests (decision packages) | ||||
| 317 | BUD | Budget Requests | System will enable users to create different budget projections/scenarios (e.g., what if 5% cut?) | ||||
| 318 | BUD | Budget Requests | System will enable users to apply percentages, fixed amounts, or other formula-driven increases/decreases to budgeted figures on a line-by-line basis | ||||
| 319 | BUD | Budget Requests | System will enable users to flag one-time budget events that it automatically removes from the next years' budget | ||||
| 320 | BUD | Budget Requests | System will integrate with the contracts module to ensure future year costs for multi-year contracts are included in departmental budget requests | ||||
| 321 | BUD | Budget Requests | System will manage multi-year contracts that renew every year (please explain functionality in the comments) | ||||
| 322 | BUD | Budget Requests | System will enable users create multiple versions of budget requests for "what if" scenario simulation | ||||
| 323 | BUD | Budget Requests | System will lock the requested budget based on the object code | ||||
| 324 | BUD | Program Budgeting | System will enable users to prepare budgets by program (can be across multiple departments) | ||||
| 325 | BUD | Program Budgeting | System will prioritize program budgets | ||||
| 326 | BUD | Program Budgeting | System will link project budgets to strategic goals | ||||
| 327 | BUD | Program Budgeting | System will track performance measures on each program | ||||
| 328 | BUD | Program Budgeting | System will track program narrative and goals for each program | ||||
| 329 | BUD | Budget Development | System will automatically roll department worksheets into the organization-wide master budget | ||||
| 330 | BUD | Budget Development | System will maintain history of multiple budget versions (e.g., requested, recommended, adopted, revised, etc.) | ||||
| 331 | BUD | Budget Development | System will enable users modify all departmental budget worksheets, via security and workflow approvals | ||||
| 332 | BUD | Budget Development | System will provide revenue and expenditure forecasting with scenario modeling capabilities | ||||
| 333 | BUD | Budget Development | System will provide forecasting based on benefits costs and collective bargaining/known future benefit changes | ||||
| 334 | BUD | Budget Development | System will forecast debt scenarios | ||||
| 335 | BUD | Budget Development | System will create exportable budget books from entered data | ||||
| 336 | BUD | Budget Development | System will automate budget book updates based on changes during budget development | ||||
| 337 | BUD | Capital Budgeting | System will facilitate the development of a multi-year capital improvement plan, up to 10 years | ||||
| 338 | BUD | Capital Budgeting | System will prioritize capital projects by year | ||||
| 339 | BUD | Capital Budgeting | System will roll up project budgets to create departmental capital budgets and the overall capital improvement plan | ||||
| 340 | BUD | Capital Budgeting | System will provide multi-year capital project budgeting | ||||
| 341 | BUD | Capital Budgeting | System will utilize multiple funding sources to develop capital budgets | ||||
| 342 | BUD | Capital Budgeting | System will identify spending information on bond related issues, especially for bonds that fund multiple projects | ||||
| 343 | BUD | Capital Budgeting | System will feed individual capital project budgets into the budget module | ||||
| 344 | BUD | Capital Budgeting | System will enable users to identify ongoing operating costs for each capital project | ||||
| 345 | BUD | Capital Budgeting | System will enable users to reconcile and report against project accounting and General Ledger | ||||
| 346 | BUD | Personnel Budgeting | System will project and budget tax and benefit costs based on current employee salary and current benefit elections | ||||
| 347 | BUD | Personnel Budgeting | System will project and budget tax and benefit costs based on position salary range and default benefit elections | ||||
| 348 | BUD | Personnel Budgeting | System will enable users request new positions in proposed budgets | ||||
| 349 | BUD | Personnel Budgeting | System will enable proposing changing position statuses as part of budget development (e.g., funded - unfunded positions) | ||||
| 350 | BUD | Personnel Budgeting | System will enable users to propose salary amount changes based on security and permissions (i.e., reclassification ) | ||||
| 351 | BUD | Personnel Budgeting | System will automatically adjust benefits/tax amounts with changes to salary amounts | ||||
| 352 | BUD | Personnel Budgeting | System will enable allocation of position costs to multiple segments of the Chart of Accounts (e.g., organizational codes, programs, projects, grants, etc.) | ||||
| 353 | BUD | Personnel Budgeting | System will calculate personnel based on FTE | ||||
| 354 | BUD | Personnel Budgeting | System will provide different fixed cost distribution based on percentage allocation to a department | ||||
| 355 | BUD | Personnel Budgeting | System will mirror personnel budget with position control structure in the HR module | ||||
| 356 | BUD | Personnel Budgeting | System will project equipment costs (i.e., vehicles, software, hardware) associated with new requested positions | ||||
| 357 | BUD | Personnel Budgeting | System will project ongoing maintenance equipment costs associated with new requested positions | ||||
| 358 | BUD | Personnel Budgeting | System will notify internal service departments of new positions requested by operating departments so they can increase their budgets for equipment and maintenance based on system projections | ||||
| 359 | BUD | Budget Projections | System will calculate budget estimates to project spending during the remainder of the fiscal year | ||||
| 360 | BUD | Budget Projections | System will project revenues and expenses | ||||
| 361 | BUD | Budget Projections | System will provide budget projections based on user-defined parameters | ||||
| 362 | BUD | Budget Projections | System will provide straight-line projections | ||||
| 363 | BUD | Budget Projections | System will provide projection methods based on last year actuals | ||||
| 364 | BUD | Multi-Year Budgeting | System will manage a two-year budget, roll the change, and adjust for the second year within the system. | ||||
| 365 | BUD | Multi-Year Budgeting | System will roll dates (e.g. benefit allocations) from one year to the next. | ||||
| 366 | BUD | Multi-Year Budgeting | System will provide different scenarios for years one and two | ||||
| 367 | BUD | Budget Adjustments | System will enable departments to propose internal budget transfers, via workflow approvals and notifications, for capital and operating budgets | ||||
| 368 | BUD | Budget Adjustments | System will provide workflows based on transferring party and receiver (e.g., within department/division or between department/division) | ||||
| 369 | BUD | Budget Adjustments | System will provide workflows based on transfers within or between budget categories (e.g., salary/supplies/materials/etc.) | ||||
| 370 | BUD | Budget Adjustments | System will enable departments to propose additional budget requests (after the budget is approved) | ||||
| 371 | BUD | Budget Adjustments | System will validate and enforce rules that all budget amendments and transfers must balance | ||||
| 372 | BUD | Budget Adjustments | System will provide funds availability check when entering budget amendments | ||||
| 373 | BUD | Budget Adjustments | System will enable users to view workflow status of a pending budget adjustment request | ||||
| 374 | BUD | Budget Projections | System will track KPIs/Performance (especially non-numeric values) | ||||
| 375 | BUD | Budget Adjustments | System will generate a summary of changes in the dashboard | ||||
| 376 | BUD | Budget Adjustments | System will provide an exclusive executive-level dashboard | ||||
| 377 | BUD | Capital Budgeting | System will enable users to drill down and view detailed Pcard/expense information | ||||
| 378 | BUD | Capital Budgeting | System will incorporate scoring criteria to prioritize capital projects. | ||||
| 379 | BUD | Capital Budgeting | System will track and show contingencies for capital projects | ||||
| 380 | BUD | Capital Budgeting | System will enable departments to view capital project requests | ||||
| 381 | BUD | Capital Budgeting | System will track revenue and expenditures in a subledger | ||||
| 382 | BUD | Capital Budgeting | System will enable users to monitor both hard and soft costs for a project | ||||
| 383 | CA | Asset Set Up | System will track capitalized items | ||||
| 384 | CA | Asset Set Up | System will sort assets by funding type (e.g., grants) | ||||
| 385 | CA | Asset Set Up | System will track non-capitalized items (items valued below the depreciation threshold amount) and is able to differentiate these items from capital assets | ||||
| 386 | CA | Asset Set Up | System will identify assets based on capitalization threshold | ||||
| 387 | CA | Asset Set Up | System will enable different capitalization thresholds for each asset type | ||||
| 388 | CA | Asset Set Up | System will integrate asset functionality with all other system-based financial functions (e.g., procurement and payables, project/grant accounting and budget/GL) | ||||
| 389 | CA | Asset Set Up | System will enable assets to have multiple account distributions (including multiple funds) | ||||
| 390 | CA | Asset Set Up | System will track infrastructure assets in bulk (e.g., roads, pipes, apertures, etc.) | ||||
| 391 | CA | Asset Set Up | System will automatically generate a unique asset number for each city asset | ||||
| 392 | CA | Asset Set Up | System will enable multiple unique IDs for a single asset (e.g., Asset ID, Department ID, or ID from another application) | ||||
| 393 | CA | Asset Set Up | System will generate tags for attaching to assets | ||||
| 394 | CA | Asset Set Up | System will track asset information including description, dates, relevant numbers (VIN, serial, barcode, etc.), location, method of acquisition, etc. | ||||
| 395 | CA | Asset Set Up | System will track asset disposal information | ||||
| 396 | CA | Asset Set Up | System will track the Catalog of Federal Domestic Assistance (CFDA) number to the asset | ||||
| 397 | CA | Asset Set Up | System will enable users to attach pictures and documents to assets | ||||
| 398 | CA | Asset Set Up | System will track and identify the finance sources of assets | ||||
| 399 | CA | Asset Set Up | System will track leased assets in compliance with GASB 87, 96, and any other legal or industry requirements | ||||
| 400 | CA | Asset Set Up | System will track subscription-based software | ||||
| 401 | CA | Asset Set Up | System will provide barcode technology for asset identification and inventory | ||||
| 402 | CA | Asset Set Up | System will manage barcode, image recognition, and RFID technology for asset inventory management (e.g., smart phone readers, barcode, etc.) (Please provided all available options in the comments) | ||||
| 403 | CA | Asset Set Up | System will integrate with the City's GIS platform for asset location and/or descriptions | ||||
| 404 | CA | Asset Set Up | System will provide parent-child relationships for assets | ||||
| 405 | CA | Asset Set Up | System will reference old assets to replacement assets | ||||
| 406 | CA | Asset Set Up | System will enable assets in the "Construction in Progress" phase to be held in a CIP account and not placed in service until completed/officially accepted | ||||
| 407 | CA | Asset Set Up | System will identify assets from the CIP file | ||||
| 408 | CA | Asset Set Up | System will track asset acquisition dates | ||||
| 409 | CA | Asset Set Up | System will track asset expiration dates | ||||
| 410 | CA | Asset Set Up | System will track asset warranty information | ||||
| 411 | CA | Asset Set Up | System will track software licenses in compliance with GASB 96 and all relevant GASB standards | ||||
| 412 | CA | Asset Set Up | System will enable assets to be owned by multiple funds (governmental and enterprise) by a percentage share | ||||
| 413 | CA | Asset Set Up | System will identify asset custodians (e.g., cell phone identifies user) | ||||
| 414 | CA | Asset Set Up | System will flag assets that have restrictions (e.g., bond-funded or grant-funded assets) | ||||
| 415 | CA | Asset Set Up | System will flag assets per allowable and unallowable users | ||||
| 416 | CA | Asset Set Up | System will identify multiple assets from a requisition, purchase order, or invoice | ||||
| 417 | CA | Asset Set Up | System will communicate between departmental stakeholders | ||||
| 418 | CA | Asset Acquisition | System will provide approval workflows for adding new assets | ||||
| 419 | CA | Asset Acquisition | System will provide effective date posting for asset acquisitions | ||||
| 420 | CA | Asset Acquisition | System will identify potential fixed assets from the purchasing module (purchase order) by chart of accounts (purchased from capital account) | ||||
| 421 | CA | Asset Acquisition | System will identify potential fixed assets from the budgeting module by chart of accounts (purchased with approved project) | ||||
| 422 | CA | Asset Acquisition | System will identify potential fixed assets from the purchasing module by dollar amount | ||||
| 423 | CA | Asset Acquisition | System will enable users to manually identify/flag potential fixed assets from the purchasing module | ||||
| 424 | CA | Asset Acquisition | System will identify potential fixed assets from the accounts payable module by chart of accounts (payment from capital account) | ||||
| 425 | CA | Asset Acquisition | System will identify potential fixed assets from the accounts payable module by dollar amount | ||||
| 426 | CA | Asset Acquisition | System will enable the manual creation of assets that do not flow through purchasing or accounts payable (e.g., assets below threshold or donated assets) |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .