Attachment_13_Interfaces_062724.xlsx
XLSX spreadsheet 32 KB Posted
- Solicitation number
- S-KS0043-00010843
- Issued by
- Marion County, Oregon
About this file
The document is an Attachment describing the anticipated interfaces for an Enterprise Resource Planning (ERP) Software Implementation Services contract for Montgomery County Public Schools. The attachment lists 30 different interfaces between the ERP system and various third-party applications covering areas such as asset management, payment portals, budget development, employee scheduling, utility billing, and other public-facing services. The interfaces vary in frequency, method, solution type, and level of consultant and client work effort. The related state and local contract opportunity is RFP No. 245050 for ERP Software and Implementation Services, issued by the State of Oregon.
The document provides details on the specific interface requirements, including whether the interface is inbound, outbound, or bi-directional, the frequency of data exchange, the method of integration (direct or file-based), the type of solution required (configurable or customized), and the anticipated consultant and client work effort in hours. It also indicates whether the interface is in scope and included in the pricing. The type of support required for each interface is also specified, including whether it is supported by the software developer, a third-party, or not supported.
View the file
Other files
Show all 23
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| Anticipated Interfaces | |
| Interface Plan: Available Responses | |
| Permanent | System cannot be replaced by ERP. Permanent interface is required |
| Temporary | System must temporarily exist during implementation |
| Go-Away | System is replaced |
| Type of Solution: Available Responses | |
| C | Configurable Solution |
| P | Customized developed program |
| Type of Support: Available Responses | |
| S | Requirement and Feature Supported by Software Developer |
| TPS | Requirement and Feature Supported by Third Party |
| NS | Requirement and Feature Not Supported |
| Vendor Response Section | ||||||||||||||
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | |||||||
| NO. | Main Application | Interface Description | Inbound, Outbound or Both | Frequency | Method | Interface Plan | Type of | |||||||
| Solution | Consultant Work Effort (in hours) | Client Work Effort (in hours) | In Scope? | Included in Price? | Type of | |||||||||
| Support | Comments | |||||||||||||
| 1 | AssetWorks (Fleet Maintenance) | Asset acquired in ERP |
Asset maintained in AssetWorks Depreciation calculated in ERP Value maintained in ERP
| Summary cost data received from AssetWorks to ERP | Both | Monthly | Direct (currently File) | |||
| 2 | Authorize.net (LibCal Payment Portal) | Revenue receipt data | Inbound | Daily | Direct (currently File) | |
| 3 | USBank | ERP sends payment requests to bank |
ERP reconciles deposits with bank
| Multiple bank accounts for different issuers | Both | As Required | File |
| 4 | BOARD (Budget Development and Reporting) | ERP receives budget data for control |
ERP maintains budget amendments and adjustments ERP sends budget amendments and adjustments to BOARD
| ERP sends detailed actuals revenue and expenditure data to BOARD | Both | Daily | Direct | |||
| 5 | CDM (Loans and Liens) | Summary revenue data | Inbound | Monthly | File | |
| 6 | CitePay (MuniCourt Payment Portal) | Revenue receipt data | Inbound | Daily | Direct (currently File) | |
| 7 | Cityworks | Stock numbers |
Employee labor costs Asset data Material data
| AP Supplier Lists | Both | Daily | Direct (currently File) | |||
| 8 | Comprise (Library Kiosk) | Revenue receipt data | Inbound | Daily | Direct (currently File) | |
| 9 | Converge (Special Event Payment Portal) | Summary revenue data | ||||
| Revenue receipt data | Inbound | Daily | Direct (currently File) | |||
| 10 | CrewSense (Advanced Scheduling for Fire and Library) | ERP maintains employee record. Sends employee base data to CrewSense |
CrewSense sends leave data to ERP. Time and leave data are maintained in ERP
| Both | Daily | Direct (currently File) | ||||
| 11 | DebtBook (Subscriptions and Liens) | Summary revenue data | Inbound | Monthly | File | |
| 12 | Ebuilder | Revenue receipt data | ||||
| Accounting information (projects and grants) | Both | Daily | Direct or File | |||
| 13 | Elavon (Payment Portal) | Revenue receipt data | Inbound | Daily | Direct (currently File) | |
| 14 | Flowbird (Parking Meters) | Revenue receipt data | Inbound | Daily | File | |
| 15 | GovQA (Public Records Request Portal) | Revenue receipt data | Inbound | Daily | Direct (currently File) | |
| 16 | LibCal (Library Management) | Summary revenue data | Inbound | Daily | Direct (currently File) | |
| 17 | FullCourt Enterprise MuniCourt (Court Citation Records) | Summary revenue data | Inbound | Daily | Direct (currently File) | |
| 18 | NeoGov (Recruitment and Onboarding) | ERP maintains job data and sends job data to NeoGov |
Recruitment and onboarding is maintained in NeoGov NeoGov sends recruitment and onboarding data to ERP
| Both | Daily | Direct (currently File) | |
| 19 | PacPortal (Permits Payment Portal) | Summary revenue data | |
| Revenue receipt data | Inbound | Daily | Direct (currently File) |
| 20 | PayN (custom Miscellaneous Receipts/Cashiering Payment Portal) | Summary revenue data | |
| Revenue receipt data | Both | Daily | Direct and File |
| 21 | ScheduleAnywhere | ERP maintains employee record. Sends employee base data to ScheduleAnywhere. ScheduleAnywhere sends leave data to ERP. Time and leave data are maintained in ERP | |
| None | None | None | |
| 22 | SpryPoint (Utility Billing) | Consumable inventory maintained in ERP |
Utility Customers maintained in SpryPoint Utility Billing maintained in SpryPoint Detailed utility receivables maintained in SpryPoint
| Summary receivables maintained in ERP | Both | Monthly | Direct and File | |||
| 23 | Paymentus | City's Enterprise Payment Processor, sends Summary revenue data and Revenue receipt data | Both | Daily | Direct and File | |
| 24 | ArmorLink | Fire arms | Inbound | Daily | Direct | |
| 25 | Target Solutions (CheckIT) | Fire inventory items | Inbound | Daily | Direct | |
| 26 | Granicus AMANDA | City's Enterprise Permit and License Management solution. Sends Summary revenue data and Revenue receipt data | Inbound | Daily | File | |
| 27 | Parks and Rec (custom, public facing) | Parks event and facility scheduling/sign-up/payment solution Sends Summary revenue data and Revenue receipt data | Inbound | Daily | File | |
| 28 | Center 50 Plus (custom public facing) | Center 50+ event sign-up and payment solution. Sends Summary revenue data and Revenue receipt data | Inbound | Daily | File | |
| 29 | CMO Payments (custom, public facing) | Registration and payments for Mayor's State of the City event. Sends Summary revenue data and Revnue receipt | Inbound | Daily | File | |
| 30 | Printshop Application (custom) | Order fullfillment and billing system used by the City's Reprographics group to bill other City departments. Sends Summary revenue data and Revenue receipt data | Inbound | Daily | File |
&"-,Bold"&14Attachment 8: Anticipated Interfaces Montgomery County Public Schools Enterprise Resource Planning Software Implementation Services
&"-,Bold"&14Attachment 8: Anticipated Interfaces Montgomery County Public Schools Enterprise Resource Planning Software Implementation Services
&F
&"-,Bold"&14Attachment 8: Anticipated Interfaces Montgomery County Public Schools Enterprise Resource Planning Software Implementation Services
&"-,Bold"&14Attachment 10: Anticipated Interfaces Montgomery County Public Schools Enterprise Resource Planning Software Implementation Services
ATTACHMENT 8 | &P OF &N
ATTACHMENT 8 | &P OF &N
&A
ATTACHMENT 8 | &P OF &N
ATTACHMENT 8 | &P OF &N
&F &P OF &N
File details come from the government source that posted it. Updated .