IBM Maximo NAPA Parts Interface Proposal.pdf
PDF 296 KB Posted
- Attached to
- NAPA Interface Implementation for IBM Maximo
- Solicitation number
- 18081-26
- Issued by
- Duval County, Florida
About this file
This Statement of Work outlines an IBM Maximo NAPA Parts Interface implementation project between Maven Asset Management and the City of Jacksonville, Florida. The project objective is to convert the existing TPH (The Parts House) vendor interface to support NAPA Auto Parts, maintaining the same functional behavior while addressing technical requirements for the new vendor. Key deliverables include providing file format guidance through up to two coordination meetings with NAPA, updating a Windows shell script to support sFTP file collection and archival with hourly scheduling, duplicating and configuring existing Tivoli integration components with NAPA-specific naming conventions, conducting five complete end-to-end test cycles in a non-production environment, deploying the updated configuration to production, and providing up to 10 hours of on-call support during the week of go-live deployment. The City of Jacksonville is responsible for provisioning the sFTP site, ensuring network connectivity, providing the non-production testing environment, conducting User Acceptance Testing, and approving any scope changes through written change orders.
The project is priced on a Time and Materials basis with a not-to-exceed total of $16,030, comprised of project management (12 hours at $195/hour), file format guidance and coordination (8 hours at $185/hour), shell script updates (12 hours at $185/hour), integration component configuration (16 hours at $185/hour), non-production testing and validation (20 hours at $185/hour), production deployment (8 hours at $185/hour), and go-live support (10 hours at $185/hour). All work will be performed remotely, and Maven resources will be scheduled upon project approval. NAPA is expected to provide data in the same format previously used by TPH, with no data mapping or transformation changes included in scope. The implementation assumes the existing TPH file format specification is available and requires no reconstruction prior to sharing with NAPA.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| SS Justification Form (9).pdf | ||
| 18081-26_SUPPLIER.pdf | ||
| 7-1-24 Protest Procedures.pdf | ||
| Supplier Letter - 2026.pdf |
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
Statement of Work
July 1, 2026
City of Jacksonville
NAPA Interface Implementation
Submitted By:
Maven Asset Management 104 Myrtle Ridge Road Lutz, FL 33459
Chris Lloyd, Client Relationship Leader Email: chris.lloyd@mavenasset.com
CITY OF JACKSONVILLE
NAPA INTERFACE IMPLEMENTATION
The objective of this effort is to convert the existing TPH (The Parts House) interface to support a new vendor, NAPA Auto Parts. This interface is used to automatically import material and parts usage onto work orders within Tivoli. While the functional behavior of the interface remains unchanged, this effort addresses the technical changes required to support the new vendor, including updated file retrieval, integration component configuration, and go-live support.
1. File Format Guidance to NAPA Maven will provide NAPA with the existing file format specification that was previously used by TPH. Maven will conduct up to two review meetings with the NAPA team to walk through the specification, answer questions, and confirm NAPA's understanding of the required data format prior to testing. No changes to the format specification are anticipated, as NAPA is expected to provide data in the same structure previously used by TPH.
2. Windows Shell Script — sFTP Collection and File Archival Maven will update the existing Windows shell script that was used to collect the inbound data file from the TPH FTP site. The updated script will:
• Use WinSCP command-line to connect to the new NAPA sFTP site (replacing the prior unsecured FTP connection)
• Retrieve any available inbound files from the designated sFTP directory
• Archive or remove files from the inbound directory upon successful retrieval to prevent duplicate processing
• Be configured to run on an hourly schedule (rather than daily) to support more frequent data availability
Maven will test and validate the updated shell script in a non-production environment to confirm successful connectivity and file retrieval prior to any production deployment.
3. Integration Component Duplication and Configuration Maven will duplicate the following existing Tivoli integration components from the TPH configuration, applying an updated naming convention to reflect the NAPA vendor:
• External System
• Enterprise Service
• XML File Consumer
• Cron Task Setup
• Automation Script (error handling and reprocessing)
No functional or mapping changes are anticipated. The duplication is intended to preserve the existing processing logic while establishing a clean, vendor-specific configuration for NAPA.
4. Non-Production Testing and Validation Maven will perform end-to-end testing in a single non-production environment. Testing will consist of five complete end-to-end test cycles to validate that the full process from file retrieval through material and parts import onto work orders functions as expected. Any issues identified during testing will be resolved prior to production deployment.
5. Production Deployment and Go-Live Support Following successful non-production validation, Maven will deploy the updated configuration to the production environment. Maven will provide up to 10 hours of on-call support during the week of go-live to assist with any issues that may arise following deployment.
1. The sFTP site will be provisioned and available for connection prior to the start of non-production testing. This is considered outside of Maven's scope.
2. The City of Jacksonville will ensure that the Tivoli server has network connectivity to the NAPA sFTP site prior to testing.
3. NAPA will provide files in the same format previously used by TPH. No data mapping or transformation changes are included in this scope.
4. The existing TPH file format specification is available and does not require reconstruction prior to sharing with NAPA.
5. Testing will be conducted in a single non-production environment provided by the City.
6. The City will be responsible for User Acceptance Testing (UAT) and for reporting any defects to Maven for resolution.
7. All work will be performed remotely.
8. All changes in scope require a written change order approved by both parties.
9. Go-live support is on-call in nature; the 10 hours represents a not-to-exceed allocation for the week of deployment.
10. Maven resources will be scheduled upon approval of this effort.
NAPA INTERFACE IMPLEMENTATION
All work will be completed on a Time and Materials basis, with totals not to exceed the amounts listed herein.
Project Task Hours Rate Total Cost
Project Management 12 $195 $2,340
File Format Guidance / NAPA Coordination (up to 2 meetings + prep)
8 $185 $1,480
Shell Script Update (sFTP, archival, hourly scheduling) 12 $185 $2,220
Integration Component Duplication and Configuration 16 $185 $2,960
Non-Production Testing and Validation (5 end-to-end cycles)
20 $185 $3,700
Production Deployment 8 $185 $1,480
Go-Live Support (on-call, week of deployment) 10 $185 $1,850
Total 86 $16,030
ACCEPTED BY:
Maven Asset Management City of Jacksonville
Authorized Signature Authorized Signature
Name Name
Title Title
Date Date
| TASKS |
| assumptions |
| Project costs |
| Maven Asset Management City of Jacksonville |
File details come from the government source that posted it. Updated .