Addendum 3.pdf
PDF 306 KB Posted
- Solicitation number
- RFP-128518
- Issued by
- Fairfax County, Virginia
About this file
Addendum No. 3 to RFI 2000004463 is issued by Fairfax County Public Schools' Financial Services Office of Procurement Services for a Computerized Maintenance Management System (CMMS). The addendum extends the closing date from October 23, 2026 at 7:00 A.M. to October 28, 2026 at 7:00 A.M. The RFI is an information-gathering exercise that does not constitute a formal solicitation or guarantee issuance of a future Request for Proposal. FCPS processes over 100,000 work orders annually and seeks a modern CMMS to replace its legacy platform, managing all physical assets including buildings, equipment, and approximately 450 fleet vehicles. The system must support multiple user roles, offline mobile capabilities for technicians, five satellite stockroom locations, preventive maintenance scheduling from 471 unique PM Task IDs, and workflow processes including work request submission, routing, approval, and closure. Required integrations include a Purchase Order module to replace the current in-house application, but no integration with FCPS's SAP ERP ECC 6.0 system is required.
FCPS has not established an approved budget range, formal project schedule, or target deployment date for the CMMS solution. Vendors must provide cost estimates both with and without data migration; however, historical data migration is not required as FCPS plans to start fresh in the new system and maintain a separate internal archive database for legacy records. The RFI seeks information on solution capabilities, implementation timelines, ongoing support and maintenance options, and estimated costs appropriate for a large school district environment. Prospective offerors must acknowledge receipt of all addenda as part of their response. The current legacy platform lacks advanced functional capabilities, enhanced security features, and vendor update support, and FCPS anticipates increasing work order volume, total building square footage, and managed asset counts over the next 3–5 years.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Addendum 4.pdf | ||
| Addendum 2.pdf | ||
| 2000004463.pdf | ||
| Addendum 1.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
Financial Services Office of Procurement Services
8115 Gatehouse Road, Suite 4400 Falls Church, VA 22042
10/21/2026
ADDENDUM NO. 3
TO: ALL PROSPECTIVE OFFERORS
REFERENCE: RFI# 2000004463
FOR: Computerized Maintenance Management System
CLOSING DATE/TIME: October 28, 2026 @ 7:00 A.M.
RFI MODIFICATION:
The referenced Request for Information is amended to revise the closing date from October 23, 2026 at 7:00 A.M., to October 28, 2026 at 7:00 A.M.
RFI CLARIFICATIONS:
The following are responses to questions received via e-mail.
Q1. What integration methods are available for systems that will remain in use, and which integrations are required at initial go-live?
A1. This is not applicable to this RFI.
Q2. For the estimate with migration, should vendors price migration of all historical data, or may they propose a defined history period with older records archived?
A2. Historical data migration is not required. OFM plans to start fresh in the new CMMS and will maintain a separate internal archive database for legacy records.
Q3. What data cleansing, deduplication, and mapping work should vendors include in the migration estimate?
A3. This is not applicable to this RFI.
Q4. How many preventive maintenance schedules are currently active, and must their history be migrated?
A4. Active preventive maintenance (PM) schedules are created from a master list of 471 unique PM Task IDs. Many PM Task IDs contain multiple frequencies. Example, a single PM Task ID may have 3 separate weeks assigned. Historical PM schedule data migration is not required.
Q5. What are the required work order workflows for dispatch, approvals, after-hours call-outs, contractors, and closure?
A5. Typical workflow is for a Requestor (school or office staff member) to submit a work request. The Work Order Section team will assign a Trade Code (HVAC, Plumbing, etc.) and route it to a Satellite office. The Satellite office will then approve and prioritize the work. Once completed by a technician, it is routed to their supervisor and then to Work Order Section team for closure. After-hours call-outs are
FD
10/21/2026
Addendum No. 3
RFI# 2000004463
routed from the Safety & Security Office to on-call trades staff. The Logistical Services team creates work orders for contractors on their behalf to record details and costs.
Q6. Is offline mobile operation required for technicians? If so, which functions must work offline?
A6. Yes, offline mobile operation is required. Core offline capabilities must include submitting non- stock parts requests and updating active work orders.
Q7. What inventory locations and processes must be supported, including stock issuance to work orders, transfers, and replenishment?
A7. The CMMS must support all 5 FCPS satellite stockroom locations: Sideburn (5025 Sideburn Rd, Fairfax, VA 22032), Edison (5805 Franconia Road, Alexandria, VA 22310), Herndon (397 Herndon Parkway, Suite 400, Herndon, VA 20170), Merrifield (8435 Lee Highway, Merrifield, VA 22031), and Woodson (9515 Main Street Fairfax, VA 22031).
Q8. What purchasing functions must the CMMS perform, and what transactions must integrate with FCPS financial systems?
A8. The CMMS must include a Purchase Order (PO) module to replace the current in-house PO application.
Q9. Do you currently use ServiceNow in any capacity within the organization?
A9. No, FCPS does not currently use ServiceNow.
Q10. Is there a predefined and approved budget range for this project?
A10. This RFI is issued for information-gathering and planning purposes only. FCPS has not established an approved budget range, a project schedule or target deployment date for a future CMMS solution.
Q11. What are the next steps in the process? Can you share a timeline of events?
A11. This RFI is issued for information-gathering and planning purposes only. FCPS has not established a formal schedule or deployment timeline for a future CMMS solution.
Q12. What business problems or opportunities is this solution expected to address?
A12. The current legacy platform lacks advanced functional capabilities, enhanced security features and vendor update support. FCPS seeks a modern, secure CMMS with intuitive, user-friendly reporting, drill-down analytics, asset tracking via barcode scanning and Geographic Information System (GIS) capabilities along with proactive recommendations for continuous system improvements.
Q13. What factors prompted the decision to issue this RFI at this time?
A13. This RFI is issued for information-gathering and planning purposes.
Q14. How do you expect your needs to evolve over the next 3-5 years?
A14. FCPS anticipates increasing work order volume, total building square footage, and managed asset counts.
Q15. Please describe the current call-out process (e.g., after-hours emergency dispatch, on-call rotations, callback time tracking) and the functions the CMMS must support.
A15. Each department supervisor is responsible for confirming their department’s weekly on-call staff rotation. Weekday callout coverage runs from 3:30 p.m. to 7:00 a.m. the following morning, while weekend coverage begins Friday at 3:30 p.m. and ends Monday at 7:00 a.m. For early releases, callout coverage begins when the early release starts. Holidays occurring during the week follow the weekend callout schedule. When the Office of Safety and Security receives an emergency call, FCPS staff review the callout schedule to identify the appropriate trade and contact the assigned employee. The employee must respond within an appropriate timeframe, assess the situation, isolate or perform repairs as needed, complete any necessary cleanup, and notify the on-call supervisor, manager, or the Office of Safety and Security of the outcome.
Q16. What employee information and functions are expected in "Employee Management" A16. Expected data fields and functional requirements include personal information, employment information, assigned trade, labor rate, and note.
Q17. Please describe how non-stock items are currently requested, approved, purchased, and tracked.
A17. When a work order is submitted for a repair or preventive maintenance task, the technician identifies any parts or materials needed from an outside vendor and submits a non-stock request.
The request is routed to the appropriate supervisor for approval. Once approved, the system automatically forwards the request to the Procurement Office. Requests submitted by supervisors or higher-level personnel are automatically routed directly to the assigned buyer.
Once the items arrive at the stockroom, stockroom personnel verify the shipment for accuracy and receive the items into the stockroom system. If discrepancies, damaged materials, or other delivery issues are identified, stockroom personnel coordinate with the vendor and the assigned buyer to resolve the issue and ensure the correct materials are received.
After receipt, the Sideburn Support Center stockroom coordinates the delivery of parts and materials to the appropriate facility stockrooms serving the technicians who submitted the non-stock requests. This process helps ensure that the requested items reach the correct location so technicians can complete the associated repair or preventive maintenance work.
Q18. Can you identify which of the integrations listed in section 3.2 are part of an ERP? Additionally, which financial system does FCPS use (name and version)? What data objects must be exchanged (e.g., purchase orders, invoices, account codes, labor costs), and in which direction and frequency?
A18. FCPS along with Fairfax County use SAP ERP ECC 6.0 running on the SAP NetWeaver technology stack. No integration with this system is required.
Q19. Is the Custodial Request System separate from maintenance work orders (different users or workflow)? Are FM Surveys customer-satisfaction surveys or facility condition surveys?
A19. The Custodial Request System is accessible via a separate web portal interface but shares the underlying database and user base. FM Surveys are customer-satisfaction surveys.
Q20. For FM Refrigerant Web, please describe the required data and reports.
A20. Required data elements and report fields include: Work Order ID, Location, Trade, Notes, Time, Refrigerant Type, Refrigerant Quantity, Employee ID, Charge Type, Measurement, and Asset Tag.
Q21. For Mechanics Backorder Web, Non-Repairable Equipment Web, Asset Formula Page, and Data Access Pages, please briefly describe the purpose and users of each of these applications.
A21. Mechanics Backorder Web is a supply/material reservation system that tracks technician requests for out-of-stock items. Orders are fulfilled based on the weekly replenishment report, which identifies items for general stock replenishment. Users are Warehouse/Stockroom and Procurement staff.
“Non-Repairable Equipment Web” tracks assets that are determined to be beyond repair, either physically or financially including the replacement asset. Users are Operations staff (technicians to management), Procurement, Finance, Stockroom/Warehouse, Asset Management staff and Custodial Manager.
“Asset Formula Page” contains backend parameters for each asset type; parameters are entered to establish a fully functional asset category. This is used by the Asset Management Manager.
“Asset Forecast App” provides the current deferred maintenance costs and an individual 10-year projected replacement cost for a predetermined set of assets. Users are the Asset Management and IT teams.
“Data Access Pages” is a program that contains four pages, the “Asset Formula Page” (described above), “Data Update Page”, “VA Inspection Page”, and “Vehicle Update Page”. These pages allow for quick access to update specific asset information for individuals responsible for specific data. “Data Update” includes additional backend data and live data, “VA Inspection” includes certification data related to pressure vessels, and “Vehicle Update Page” includes information on fleet vehicles. Users are the Asset Management Manager and IT teams (all pages), Business Operations Administrators & Facility Management Sr. Manager (all except, Asset Formula Page).
Q22. What does Fuel Oil Web track (e.g., deliveries, tank levels, consumption, vendor invoices, costs by building)?
A22. Fuel Oil Web records and validates tank measurements, deliveries, and generates reports on consumption.
Q23. Addendum one stated “FCPS desires for all physical assets to be managed.” Does this include fleet vehicles and motorized equipment maintained by OFM? If so, approximately how many vehicles and pieces of equipment?
A23. Yes, The Office of Facilities Management has approximately 450 vehicles.
All other terms and conditions remain unchanged.
Delphine Lambert Contracts Manager
THIS ADDENDUM IS ACKNOWLEDGED AND IS CONSIDERED A PART OF THE SUBJECT REQUEST
FOR INFORMATION:
Name of Firm
(Signature) (Date)
File details come from the government source that posted it. Updated .