Exhibit_2_-_Integration_Inventory.xlsx
XLSX spreadsheet 13 KB Posted
- Attached to
- Enterprise Asset Management - Software & Implementation State and local contract opportunity
- Solicitation number
- RFP 26-0007
- Issued by
- Maricopa County, Phoenix City, Arizona
About this file
The document is an integration inventory exhibit from the City of Phoenix's Enterprise Asset Management (EAM) solicitation, detailing current system interfaces and data integration points across multiple departments. The contract is for EAM software and implementation, with a proposed five-year term commencing on or about May 1, 2026, and will be awarded through the City's Procurement Portal. The solicitation covers comprehensive software and implementation services, with the final contract dependent on City Council award and signature recording by the City Clerk's department.
The exhibit reveals extensive current integrations involving systems such as eChris (PeopleSoft), HARS, SCADA, SAP, GIS, AutoCAD, Dynamics365, and Building Automation Systems. These interfaces support data exchanges across departments including Water Services (WSD), Information Technology Services (ITS), Street Transportation, and Public Works, with varying connection types like DBLink, JDBC, FTP, and web services. The integrations handle diverse data flows including employee and wage information, process control data, work requests, catalog items, requisitions, and building system communications, with frequencies ranging from on-demand to daily batch processes. The document suggests a complex technological ecosystem requiring modern platform updates with enhanced integration, interoperability, security, and performance capabilities.
View the file
Other files for this state and local contract opportunity
Show all 50
Enterprise Asset Management - Software & Implementation has more files on GovTribe.
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
Exhibit 2
| EXHIBIT 2. | CURRENT EAM INTEGRATIONS | |||||||
| Interfaces across all systems shall be updated to modern platforms, adopting industry-standard protocols and design practices to enhance integration, interoperability, security, and performance. | ||||||||
| Interface | Type of Connection | Frequency | How data is fetched | Average per day / Description | Dept. | Direction WAM/WACS | Notes | |
| eChris (PeopleSoft) | DBLink -- Grant to two eChris view having 1,400 rows of data each | Once a day | A custom procedure will insert/update data into SYNERGEN tables | 2,800 | Employee and Wage Interface into WAM | HR | Inbound | |
| HARS | DBLink -- Grant to two HARS tables/views having 800 rows and around 3 million rows | Once a day | A custom procedure will insert/update data into SYNERGEN tables | 800 | Process Control Data (SCADA) into WAM. Same Asset will have multiple Readings per day, 754 unique Point ID's. | WSD | Inbound | |
| UCOS | JDBC connection inserting data into SYNERGEN | On demand | A custom procedure of WAM database is invoked and data inserted to WAM | 1 | Create Work Request into WAM | WSD | Inbound | |
| SAP Transaction file | FTP between SAP and ITS | 4 times a day | A custom http method will read the file and insert data into SYNERGEN tables | 100 | Checkout Issues coming into WAM | ITS | Inbound/Outbound | Column D refers to Inbound but there is transactions both ways between SAP and WAM. |
| SAP Catalog file | FTP between SAP and ITS | Every 6 hours | A custom http method will read the file and insert data into SYNERGEN tables | 5,000 | SAP Catalog Items and Item Details (every 6 hours) | ITS | Inbound/Outbound | Column D refers to Inbound but there is transactions both ways between SAP and WAM. |
| Checkout request | Web service | On demand | Web service is invoked via http method via stored procedures called from forms | 100 | Checkout Requests are sent to SAP | WSD | Outbound | |
| Requisition | Web service | On demand | Web service is invoked via http method via stored procedures called from forms | 5 | Requisitions from WAM to SAP | WSD | Outbound | |
| GIS | DBLink | Once a day | A batch job invokes web service via http method through stored procedure | 200 | WSD | Inbound/Outbound | ||
| SAP Follow On | Web service | Once a day | A batch job invokes web service via http method through stored procedure | 5 | Shopping Carts for Items that are not carried in the Storeroom. Requisitions created in WAM, PO is created in SAP, Invoice in SAP. Return SAP shopping cart number to WAM | WSD | Inbound/Outbound | |
| AutoCAD Suite | N/A | |||||||
| GIS | Webservice | On demand | multiple webservices to provide location based information (Street names, Block #, District #, etc) | Street Transportation Department, Public Works Department | Inbound/Outbound | |||
| SAP | Webservice | On demand | Submit crew report details (Employees hours and material consumption) | Street Transportation Department | Inbound/Outbound | |||
| Dynamics365 | Webservice | On demand | Receives the requests submitted by the public relevant to Street Maintenance Issues and Downed traffic signs, triggers Citizneserve to create work orders and automatically assigns them to crews | Street Transportation Department | Inbound | |||
| Building Automation Systems (e.g. Trane, Delta) | BACnet | On demand | Staff utilize the platform to monitor building systems on an as-needed basis. | Enables different building systems (e.g. HVAC, lighting, and fire safety) to communicate and be controlled from a single platform | Public Works Department | N/A | A data communication protocol for building automation and control networks. |
File details come from the government source that posted it. Updated .