Click Here for free registration
RFP 0501 - To Provide Software and Implementation Services for an Enterprise Asset Management (EAM) Software Systems Environment Attachment: RFP 0501 - EAM.pdf 
Louisiana > Jefferson Parish Government
RFP: 68572887

IMPORTANT ANNOUNCEMENTS

Bid Law Requirement Update: Act 406
Vendors will be required to submit certain documentation with RFP submission, i.e. affidavits, proof of insurance, etc. These requirements will be outlined specifically in the instructions of each RFP package. Vendors should continue to carefully read and respond accordingly per the requirements of the RFP packages. These changes are pursuant Louisiana Public Bid Law more specifically, Act 406 of the 2016 Louisiana Legislative Regular Session. For the purposes of this communication, this change applies to Jefferson Parish Government bid solicitations only. For more information, please call Jefferson Parish Purchasing at 504-364-2678.

Electronic Bond Submission May Be Required
If the RFP documents require a surety, vendors submitting responses to Jefferson Parish through this site must submit an electronic bond through the respective online clearinghouse bond management system(s). You may click the link below to use: https://www.centralauctionhouse.com/central-bidding/bid-bonds
RFP Submittal Formats:

While this site accepts various file types, sizes and quantities, the preferred method for delivering all of the appropriate and required RFP documents is one single scanned PDF file. Vendors submitting a RFP with multiple uploaded images/photos of bid responses are solely responsible for clarity. If uploaded images/documents are not legible, the vendors submission will be rejected. Please note all requirements in this SUBMITTAL package for electronic RFP submission.
NOTICE:

TO RESPOND TO THIS SOLICITATION, PLEASE PRINT THE ENTIRE RFP FORM INCLUDING THE INSTRUCTIONS. COMPLETE THE RFP FORM AND ATTACH ANY SPECIFICATIONS OR ADDITIONAL REQUIRED DOCUMENTS. SCAN THE ENTIRE RFP RESPONSE AND UPLOAD TO THE ONLINE BIDDING SITE. ENSURE THAT YOU HAVE REVIEWED ALL INSTRUCTIONS THAT APPLY TO THIS RFP, AS THE REQUIREMENTS FOR BOND SUBMISSIONS HAVE CHANGED.
Listing Information/Advertisement
REQUEST FOR PROPOSAL
 RFP 0501
 
Jefferson Parish Department of Purchasing is soliciting Request for Proposals (RFPs) from qualified firms to provide Software and Implementation Services for an Enterprise Asset Management (EAM) Software Systems Environment for the Jefferson Parish Department of Electronic Information Systems.
 
Jefferson Parish (Parish) is soliciting Proposals from Proposers capable of satisfying the needs for software and consulting services to implement a new software systems environment to address the Parish’s needs related to Enterprise Asset Management (EAM).
 
All proposals will be evaluated on criteria such as vendor’s technical proposal, qualifications and experience, financial profile and proposal responsiveness and other criteria more specifically defined in the RFP document.  The maximum total points for each proposal are set at 100 points
                   
PRE–Proposal Conference: A pre-proposal conference will be held at 11:00 a.m. cst. on April 8, 2025 at the General Government Building 200 Derbigny Street, Suite 3503/3506, Gretna, LA 70053. Perspective Proposers that are interested in participating in the Pre-Proposal Vendor Teleconference shall contact BerryDunn in writing ([email protected]) to request the teleconference information.
 
RFP specifications may be obtained by visiting the Jefferson Parish Purchasing Department webpage at http://www.jeffparish.gov/464/Purchasing and selecting the LaPAC Bid Publishing & Downloads tab or the Request for Proposal Announcements tab. RFPs may also be viewed and submitted online free of charge at: www.jeffparishbids.net or www.centralbidding.com.
 
Submissions will only be accepted electronically via the Parish’s e-Procurement system, Central Bidding, www.jeffparishbids.net. Responses will be received until 3:30 p.m. cst. on April 25, 2025. Jefferson Parish no longer accepts manual submissions. All vendors will be required to register with Central Bidding, https://www.centralauctionhouse.com/SignUp.
 
The Jefferson Parish Council reserves the right to accept or reject any and all proposals, in whole or part, pursuant to the law.  Jefferson Parish and its partners as the recipients of federal funds are fully committed to awarding a contract(s) to firm(s) that will provide high quality services and that are dedicated to diversity and to containing costs.  Thus, Jefferson Parish strongly encourages the involvement of minority and/or woman-owned business enterprises (DBE’s, including MBE’s, WBE’s and SBE’s) to stimulate participation in procurement and assistance programs.
 
   
 
Renny Simno
Director                                                                                                                           
Purchasing Department
 
Misty A. Camardelle
Assistant Director
Purchasing Department

ADV: The New Orleans Advocate: March 19, 26, and April 2, 2025
 
For additional information, please visit the Purchasing Webpage at http://purchasing.jeffparish.net or you may call 504-364-2678.
 

SUBMITTAL INFORMATION
Creator Username: MCAMARD
Submittal Privacy: Response Encryption
Started: 19-Mar-2025 8:58:00 AM CDT
Ends: 25-Apr-2025 3:30:00 PM CDT ( 9d, 19h+ )
History: 865 Views, 5 Messages
Event Status: Open
Actions: Sign-In to Bid
Username:

Password:
Visitors: Visitors/Central Bidding Plan Holders
DOWNLOAD BID DOCUMENTS
RFP 0501 - EAM.pdf (538.1 KB)
RFP 0501 - EAM - Attachment A.docx (196.2 KB)
RFP 0501 - EAM - Attachment B.xlsx (172.2 KB)
RFP 0501 - EAM - Attachment C1.xlsx (61.0 KB)
RFP 0501 - EAM - Attachment C2.docx (60.4 KB)
TAGS
Jefferson Parish Government 29IT/Tech Consulting 2Computer, Software, Networking 20
PUBLIC MESSAGE BOARD
Discuss questions with the owner/creator of this Listing.
BrightlyRFP on 28-Mar-2025 3:20:36 PM CDT
Questions Regarding RFP 0501:

1. What is Berry Dunns involvement in vendor selection and post-award? Will Berry Dunn be involved in the evaluation and implementation?
2. If a vendor cannot meet one or more critical requirements, will the vendor be disqualified?
3. Has the Parish seen any product demonstrations in the last 18th months? If so, which products did you see?
4. Does the Parish have a budget threshold you are looking to stay within for this project?
5. Could you please share how the technical specifications were evaluated and decided upon for inclusion in the RFP?
AssetWorks on 31-Mar-2025 5:46:09 PM CDT
Would the Parish consider replacing CFA for fleet management with the proposed EAM solution?
Chad_IPS on 01-Apr-2025 8:08:59 AM CDT
Questions RFP 0501: Section 2.1.6 Number of Users
To support accurate planning and resource allocation, we need clarification on the user count in Table 2-03: Number of Users.
1. Are the 350 Work Order and Customer Service users included within the individual area breakdowns in Table 2-03? If not, can you specify how these users are distributed across the functional areas?
2. Regarding Mobile and Field Users:
• Are the 10 mobile/field users dedicated to handling Service Requests and Work Orders, or are these roles rotated among staff members?
• Do you anticipate any changes in the number of field users, particularly with the introduction of new functionalities?
Agelix on 09-Apr-2025 9:57:47 AM CDT
1. Will the Parish require bi-directional synchronization with Oracle or Lucity, or is one-way data migration sufficient for legacy data?

2. What specific Oracle Work Order version and schema is currently in use, and can schema documentation be provided to support mapping?

3. Does Lucity currently expose APIs or web services, or will data need to be extracted via database-level access or flat files?

4. Are there standard integration protocols or middleware platforms (e.g., MuleSoft, Boomi, SSIS) mandated or preferred by Parish IT for interfacing with internal systems?

5. Is there a need for real-time data exchange (e.g., REST API polling, webhook subscriptions) between the proposed EAM and systems like ESRI ArcGIS, or will nightly batch processing be acceptable?

6. Is Single Sign-On (SSO) integration expected to follow SAML 2.0, OAuth 2.0, or another protocol? And what is the current Identity Provider (IdP) platform (e.g., Azure AD, Okta, ADFS)?

7. How many years of historical data (e.g., work orders, service requests, asset maintenance logs) are to be retained and accessible in the new system?

8. Will legacy data require transformation (e.g., normalization, de-duplication, restructuring), or should it be preserved in its native structure for audit/compliance purposes?

9. Is there a requirement for live cross-querying between legacy and new systems (e.g., federated queries), or will legacy data be ingested and centralized into the EAM platform?

10. Are there any mandated reporting formats (e.g., federal compliance, FEMA, state-specific asset reports) that require templates or system configuration?

11. Should the reporting module support direct integration with existing Parish BI tools (e.g., Power BI via OData feeds or REST APIs)?

12. Is ad-hoc report generation expected to support advanced logic (e.g., conditional filters, cross-module joins, user-based data visibility)?

13. Will the Parish require mobile device management (MDM) compatibility for field use (e.g., iOS/Android device support, offline mode, GPS logging)?

14. Should the mobile application support barcode/RFID scanning for asset tagging or inventory tracking?

15. Are there specific logging and audit trail requirements (e.g., immutable logs, exportable audit history, tamper detection)?

16. Is FIPS 140-2 compliance required for encryption modules, or are general industry standards (e.g., AES-256) acceptable?

17. Should GIS integration support real-time map-based asset updates, or is static data sync sufficient (e.g., weekly sync with ArcGIS feature layers)?

18. Does the Parish require field-level GIS data editing from within the EAM system (e.g., editing geometry, attributes), or only viewing capabilities?

19. What level of in-house configurability is expected from the system (e.g., UI layouts, form logic, automated workflows), and what will require vendor development?

20. Are there existing workflow definitions or process diagrams that must be reproduced exactly in the new system (vs. process redesign allowed)?
AssetWorks on 11-Apr-2025 9:57:19 AM CDT
Would “future roadmap” items be considered to be meeting the requirements for the City?
UPDATE/ADDENDUM HISTORY
All updates/changes are listed below::