12-Exhibit - RFP-10255 Scope- FINAL.pdf

PDF 174 KB Posted

Attached to
RFP#: 10255-Facilities Management System
Solicitation number
US.261480
Issued by
Philadelphia County, Philadelphia City, Pennsylvania

About this file

This Scope of Work document outlines the requirements for RFP #10255, issued by the Community College of Philadelphia for a Facilities Management System (FMS) to be delivered as a Software-as-a-Service (SaaS) solution. The College seeks a comprehensive system to manage work orders, preventive maintenance, compliance inspections, key and lock tracking, space management integrated with AutoCAD drawings, facility condition assessments, and asset management across approximately 11 buildings, 1,600 rooms and spaces, and 800 employees. The system will replace the current FAMIS (Accruent) platform and serve approximately 25 daily Facilities staff users plus unlimited campus users submitting maintenance requests. The RFP opened November 13, 2026, with queries due December 11, 2026, vendor responses to queries due December 22, 2026, and proposals due January 27, 2027 at 12:00 p.m. EDT. Finalist interviews are scheduled for the week of February 4, 2027, with bid award announcement on March 1, 2027. The initial contract term is three years from the execution date, with options to extend for up to two additional one-year periods, for a maximum possible contract term of five years.

The College requires vendors to provide complete pricing proposals identifying all costs separately, including initial setup and implementation, software license or subscription fees, user licenses (specifying whether campus users submitting requests require paid licenses), data migration, AutoCAD integration, drawing preparation services, training, ongoing technical support and maintenance, individual module costs, optional services, and annual costs for all five potential years. Vendors must clarify which costs are one-time versus recurring and state whether the system is available through cooperative purchasing contracts such as Sourcewell or PA COSTARS. The College currently uses FAMIS as its existing system and AutoCAD drawings for floor plans, with room assignment records maintained by individual departments on spreadsheets. The College prefers a vendor-hosted cloud system with United States data storage and requires vendors to provide SOC 2 Type II reports or equivalents, completed HECVAT assessments, accessibility conformance reports (VPAT), and customer references from colleges or universities currently using the proposed system, with preference for community colleges, Mid-Atlantic institutions, and former FAMIS users.

View the file

Other files

Show all 17

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

Scope of Work RFP#10255: Facilities Management System

The College is seeking proposals from qualified vendors to provide, set up, and support a Facilities Management System that meets the needs described in this Scope of Work.

1. Project Overview The College is looking for one central software system to help the Facilities Department manage its daily work, maintain College buildings and equipment, and plan for future facility needs. The system will be used to manage:

• Work orders and maintenance requests.

• Scheduled preventive maintenance.

• Required compliance inspections and inspection records.

• Key and lock tracking.

• Building, room, and space information connected to the College’s existing AutoCAD drawings.

• Room assignments and occupant records for College employees.

• Facility condition assessments and deferred maintenance planning.

• Equipment and asset records.

The system should reduce paperwork and separate spreadsheets, improve recordkeeping, and make it easier for Facilities staff to find and use accurate information. It must be practical and easy for technicians, supervisors, and campus users to use with minimal training (see Section 3.9).

1.1 Current Environment

The following information is provided to help vendors size their proposals. All figures are approximate.

• Current system: FAMIS (Accruent), which holds the College’s current work order, maintenance, and key records. The new system will replace FAMIS.

• Buildings and facilities: 11.

• Rooms and spaces: approximately 1,600.

• Occupants: approximately 800 employees assigned to offices and workspaces. Some offices, including adjunct faculty offices, are shared.

• Daily system users: approximately 25 Facilities staff. The number of campus users who submit requests is not limited.

• Floor plans: AutoCAD (DWG) floor plans for College buildings. Most are current; some need updates.

• Keys: physical keys on Schlage lock hardware.

• Room assignment records: currently kept by individual departments, mostly on spreadsheets. Human

Resources and Information Technology provide periodic spreadsheet exports of employee and phone extension data.

2. Project Goals The College’s goals for this project are to:

• Bring Facilities Department information and work processes together in one system.

• Make it easier to submit, assign, track, and complete maintenance requests.

• Plan and track routine maintenance before equipment or building systems fail.

• Track required inspections and keep inspection records ready for auditors, insurers, and code officials.

• Keep accurate records of keys, locks, and who has been issued each key.

• Know who is assigned to each office and workspace, and which keys each person holds.

• Connect building and room information to existing AutoCAD drawings.

• Record building conditions, needed repairs, and estimated future repair or replacement costs.

• Maintain an inventory of buildings, equipment, and other facility assets.

• Improve reports and information used for daily management and budget planning.

• Provide a system that Facilities employees and approved campus users can use effectively and consistently.

3. Scope of Services and System Requirements The selected vendor must provide the software, licenses, setup, implementation, data transfer, training, and ongoing support needed to put the system into operation. The proposed system must include the functions described below. Each function must be available in the vendor’s current production release as of the proposal due date. Functions planned for a future release must be identified as such and will not be considered available.

3.1 Work Order Management

The system must allow Facilities staff and approved College employees to submit, assign, follow, and complete maintenance requests.

• Allow campus users to submit maintenance requests online.

• Provide request forms that can be configured by request type, such as a repair request or a key request.

• Allow Facilities staff to create work orders and assign them to individual employees, work groups, or outside contractors.

• Allow staff to set priorities based on urgency and importance.

• Support approval steps for requests that need supervisor or budget approval.

• Show the status of each request from submission through completion to Facilities staff and to the requester.

• Record labor hours, materials, equipment used, and costs.

• Track work assigned to outside contractors separately from in-house work, including contractor costs.

• Allow users to attach photographs, documents, and notes.

• Keep maintenance history by building, room, equipment, or location.

• Send automatic email updates to the requester, assigned staff, contractors, and other people named on the request when the status changes.

• Provide reports showing open and completed work orders, response times, backlog age, and outstanding requests.

3.2 Preventive Maintenance

The system must help the College schedule and track routine maintenance so that equipment and building systems are properly maintained.

• Set up recurring maintenance schedules.

• Automatically create work orders when maintenance is due.

• Assign maintenance tasks to employees, work groups, or outside contractors.

• Set schedules by calendar date, fixed time interval, or meter reading, such as equipment run hours.

• Include inspection checklists and maintenance instructions.

• Track completed, upcoming, and overdue maintenance.

• Keep maintenance history for buildings, equipment, and assets.

• Send reminders for upcoming or overdue maintenance.

• Provide reports showing preventive maintenance activity and completion rates.

3.3 Key and Lock Management

The proposed system must include built-in key and lock management. This function must be part of the proposed system and not depend on an unrelated third-party application.

• Maintain an inventory of College keys, locks, and related hardware.

• Track key numbers, types, quantities, and locations.

• Model the College’s existing master key system, including key hierarchy, keyways, and cores.

• Link keys to the doors, locks, cores, and rooms they open.

• Record which employees, contractors, or departments have been issued keys.

• Track keys when they are issued, returned, transferred, or replaced.

• Identify master keys and keys with restricted access.

• Record lost, stolen, or unreturned keys.

• Record lock changes and rekeying work, and update the affected key, door, and core records.

• Create rekeying and core change work orders directly from key records.

• Keep key holder acknowledgment and accountability records.

• Provide reports showing current key assignments and outstanding keys.

• Show every key held by a given person, and every key that opens a given door or room.

• Identify keys held by employees who have left the College or moved offices, so those keys can be recovered.

• Restrict access to key cut codes and master key data to authorized users.

• Allow Security staff limited, read-only access to look up key holders.

Vendors must state whether key management is included in the base system or requires an additional module or license. Key management provided through a separate third-party application does not meet this requirement.

3.4 Space Management and AutoCAD Integration

The system must help the College manage building, floor, room, and space information using its existing AutoCAD drawings.

• Import and use the College’s existing AutoCAD drawings, including applicable DWG and DXF files.

• Connect floor plans to building, floor, and room records.

• Keep drawings and room records in sync in both directions: changes to room records update drawing labels, and changes to drawings update room records.

• Identify differences between drawings and room records, such as rooms that appear in one but not the other, or changed square footage.

• Maintain a searchable list of College buildings and rooms.

• Record room numbers, departments, room types, occupants, and square footage.

• Allow users to view floor plans in a web browser, without an AutoCAD license, and locate individual rooms and spaces.

• Allow room and space information to be updated when changes occur.

• Track space assignments and room use.

• Provide reports by building, floor, department, or room type.

The system must also track who is assigned to each space:

• Assign one or more employees to each office or workspace, including shared offices.

• Keep a record for every assigned occupant, whether or not that person logs in to the system. Occupant records that are created only when a person logs in do not meet this requirement.

• Record each occupant’s department and phone extension.

• Keep a history of room assignments, with start and end dates.

• Update occupant records in bulk from periodic Human Resources and Information Technology spreadsheet exports, and flag new hires, separations, and transfers.

• Connect occupants to the keys they hold, so a move or separation shows which keys must be returned.

• Report vacant spaces, occupancy by department, and square footage by department.

• Display floor plans shaded by department, room type, or vacancy.

• Support future space utilization and departmental cost allocation reporting.

Vendors must explain how drawings are imported, updated, and maintained in their system, including any limits or additional costs. Vendors must also state whether College staff without advanced CAD training can maintain the drawings after implementation; what preparation the College’s drawings will need, such as polylines or layer standards, and whether the vendor provides that service; how records are updated after a renovation changes a floor plan; and whether Revit or BIM models are supported.

If space management or AutoCAD integration is provided through a partner product, the vendor must name the product, describe how it shares data with the proposed system, and price it separately.

3.5 Facility Condition Assessments

The system must help the College record and track the condition of its buildings, building systems, and major components. This information will help identify needed repairs, set priorities, plan replacements, and prepare future budgets.

• Maintain an inventory of buildings and major building components.

• Record the age and condition of building components.

• Document inspections and facility assessments.

• Assign condition ratings to buildings, systems, and components.

• Attach photographs, inspection reports, and notes.

• Record estimated repair and replacement costs.

• Track outstanding repairs and deferred maintenance.

• Prioritize facility needs based on condition and urgency.

• Calculate a Facility Condition Index (FCI) by building and by campus.

• Show the projected cost of deferring repairs over time.

• Convert assessment findings into capital requests or projects.

• Keep records of past inspections and assessments.

• Import condition data from third-party assessment reports.

• Provide multi-year capital renewal forecasts and other reports to support maintenance and long-term capital planning.

Vendors must state whether they provide on-site facility condition assessment services, directly or through a partner. If offered, these services must be priced separately as an optional item.

3.6 Asset and Equipment Management

The system must allow the College to maintain an inventory of its equipment and other facility assets.

• Record asset descriptions and identification numbers.

• Record manufacturer, model, and serial number information.

• Identify the building and location of each asset.

• Record installation dates and warranty information.

• Flag assets under warranty when a work order is created, so the College does not pay for covered repairs.

• Track asset condition and expected useful life.

• Keep maintenance and repair history.

• Connect assets to work orders and preventive maintenance schedules.

• Support barcode or QR code asset tags that can be scanned with a mobile device.

• Record equipment replacements and disposals.

• Import asset data from contractor closeout documents at the end of a construction or renovation project, including COBie and spreadsheet formats.

• Provide reports on assets and their maintenance history.

3.7 Reports and Management Tools

The system must provide standard reports and dashboards to help Facilities managers monitor work, identify needs, and make informed decisions.

• Work order activity and completion.

• Preventive maintenance schedules and completion rates.

• Labor hours and maintenance costs.

• Key inventory and assignments.

• Building and room inventories.

• Space use and occupancy.

• Facility condition assessments and deferred maintenance.

• Equipment and asset inventories.

• Compliance inspections and open deficiencies.

• System use by user, such as logins and work orders updated.

Authorized users must be able to create custom reports without programming or vendor assistance, export information to common formats such as Excel and PDF, and schedule reports to be emailed automatically.

Dashboards must be configurable by role, such as director, manager, and technician.

3.8 Compliance Inspections and Records

The system must help the College schedule required inspections and keep inspection records ready for review by auditors, insurers, and code officials.

• Schedule recurring code-required inspections and tests, such as fire extinguisher, fire sprinkler, emergency generator, elevator, and stormwater inspections.

• Track inspections performed by outside contractors as well as by College staff.

• Attach inspection reports, test results, certificates, and permits to the related building or equipment record.

• Record deficiencies found during inspections and create work orders to correct them.

• Report open deficiencies with their age and status.

• Retrieve the inspection history for a building or piece of equipment for a selected date range.

3.9 Ease of Use and Mobile Access

The system must be practical for daily use by technicians, supervisors, and campus users. Vendors must describe how the proposed system meets each item below.

• Provide a mobile application for iOS and Android devices that allows technicians to receive, update, and close work orders, record labor and materials, and attach photographs.

• Allow technicians to keep working on a mobile device where there is no network connection, with changes saved when the connection returns.

• Allow a campus user to submit a request and check its status without training.

• Allow College system administrators to add users, change request forms, create preventive maintenance schedules, and build reports without vendor services or programming.

• Use consistent screens and navigation across all functions.

3.10 Integrations and Data Exchange

The system must exchange information with other College systems as follows:

• Support single sign-on with the College’s identity provider, such as Microsoft Entra ID (Azure AD), using SAML 2.0 or a comparable standard.

• Import employee, department, and phone extension data from spreadsheet or CSV files, on a schedule or as needed.

• Provide an application programming interface (API) for data exchange with other systems.

Vendors must also describe the following. These items are not required, and any cost must be priced separately:

• Read-only reporting access for business intelligence tools such as Power BI.

• Integration with building automation systems so that equipment alarms can create work orders. Name the platforms integrated in production at client sites.

• Integration with the College’s ERP system, Ellucian Banner.

3.11 Items Not Included in This Scope

The following functions are not part of this Scope of Work:

• Event and room reservation scheduling. The College uses 25Live for this function.

• Construction project management. The College uses Procore for this function. Vendors may price a project management module as an optional item.

4. System Setup and Implementation The selected vendor will be responsible for setting up the system so it meets the College’s approved needs. The vendor’s work must include:

• Holding an initial project meeting and reviewing the College’s requirements.

• Reviewing current Facilities Department processes.

• Setting up and configuring the system.

• Creating user accounts and access permissions.

• Setting up work order categories, priorities, and approval steps.

• Setting up the requester portal, request forms, and email notification templates.

• Setting up preventive maintenance schedules.

• Setting up key, space, asset, and facility assessment information.

• Loading occupant and room assignment records.

• Importing and connecting AutoCAD drawings.

• Setting up the mobile application for technicians.

• Transferring agreed-upon existing data.

• Testing the system with College staff.

• Helping the College launch the system and providing support after launch.

The vendor must assign a project manager and provide an implementation schedule showing major tasks, responsibilities, and expected completion dates.

The vendor must state the College staff time needed during implementation, by role and hours per week, and any data cleanup the College must complete before the project begins. The vendor must also describe the support it provides to help staff adopt the new system, such as communication materials and check-ins after launch.

5. Data Migration The vendor must explain how it can transfer the College’s existing information, including records currently held in FAMIS, into the new system. Information that may be transferred includes:

• Existing work orders and maintenance history.

• Preventive maintenance schedules.

• Building and room information.

• AutoCAD drawings and related space information.

• Key and lock inventories.

• Room assignment and occupant records from department spreadsheets.

• Equipment and asset inventories.

• Facility condition assessment records, if any.

• Related documents and photographs.

The vendor must explain the data transfer process, identify what information the College must provide, and describe how transferred information will be checked for accuracy. The College and selected vendor will agree on which records will be transferred.

Vendors must state how many clients they have moved from FAMIS to the proposed system and name up to three of them. Vendors must also identify which FAMIS records transfer directly and which must be rebuilt or entered manually.

6. Training The vendor must train College employees so they can use the system effectively. Training must be available for:

• System administrators.

• Facilities supervisors and managers.

• Maintenance employees and technicians.

• Employees who manage keys and locks.

• Employees who manage building and room information and maintain floor plan drawings.

• Employees who complete facility condition assessments.

• Approved campus users who submit maintenance requests.

The vendor must provide user guides and training materials for future reference. The vendor must also explain how the College can train new employees after the system is launched, and state whether refresher training, train-the-trainer sessions, and recorded training are included.

7. Technical and Security Requirements The proposed system must meet the College’s technology, security, and accessibility requirements. At a minimum, it must:

• Provide secure user accounts and access permissions.

• Allow different access levels based on each user’s job responsibilities.

• Support single sign-on (SSO), as described in Section 3.10.

• Protect College information when it is sent and stored.

• Keep records of user activity and changes made in the system.

• Provide regular data backups and a plan for restoring service after an outage or disaster.

• Work on standard desktop computers and mobile devices.

• Allow the College to export all of its data, including attachments, in a standard, non-proprietary format at any time.

• Meet applicable College IT security and accessibility requirements.

Vendors must provide information about where the system is hosted, how information is protected and backed up, system availability, and disaster recovery. The College prefers a vendor-hosted (cloud) system with data stored in the United States. Vendors must state the guaranteed system availability (uptime) and provide a current SOC 2 Type II report or equivalent, a completed Higher Education Community Vendor Assessment Toolkit (HECVAT), and an accessibility conformance report (VPAT).

8. Ongoing Maintenance and Technical Support The vendor must provide software updates, maintenance, and technical support throughout the contract.

Vendors must explain:

• When technical support is available.

• Whether support staff are based in the United States.

• How College employees report problems or request help.

• Expected response times for support requests.

• How urgent problems are handled and escalated.

• How software updates and improvements are provided, and how much notice the College receives before changes.

• Whether there are additional costs for support or system improvements.

• Whether the College will have a named account or customer success contact.

The vendor must identify its support contacts and explain how the College will receive ongoing assistance.

9. Vendor Qualifications and Experience Vendors must show that they have experience providing and setting up Facilities Management Systems for organizations with similar needs. Proposals should include:

• Company background and experience.

• Experience implementing Facilities Management Systems.

• Experience working with colleges, universities, or similar organizations.

• Number of community colleges currently live on the proposed system.

• Experience connecting systems to AutoCAD drawings.

• Experience with key and lock management.

• Experience with facility condition assessments.

• Qualifications of the proposed implementation team.

• At least three customer references from colleges or universities currently live on the proposed system. Each reference must include the institution name, contact name and title, phone number, email address, functions in use, and go-live date. References from community colleges, institutions in Pennsylvania or the Mid- Atlantic region, and former FAMIS users are preferred.

The College may contact any listed reference.

10. Vendor Proposal Requirements Vendors must submit a proposal explaining how their proposed system meets the requirements in this RFP.

Each proposal must include:

• Company background and qualifications.

• Description of the proposed software.

• Explanation of how the system meets each required function, using the response codes in the RFP

Response Note.

• Identification of features included in the standard system and features that require additional modules or services.

• Explanation of AutoCAD integration and occupant tracking.

• Description of the implementation process and estimated timeline.

• Description of the data transfer process.

• Training and ongoing support information.

• Technical and security information.

• The security and accessibility documents listed in Section 7.

• Customer references.

• The vendor’s product plans for the next 24 months.

• Complete pricing proposal.

• Any limitations, additional requirements, or services that are not included.

Vendors must clearly identify any requirement they cannot meet. Vendors must also identify whether a feature is included in the proposed price, requires an additional fee, requires customization, or depends on another product.

11. Contract Term and Renewal Options The initial contract term will be three (3) years, beginning on the date the contract is signed or another start date agreed to by the College and vendor.

• At the end of the initial three-year term, the College may choose to extend the contract for up to two (2) additional one-year periods.

• The maximum possible contract term is five (5) years.

• Any extension will be at the College’s sole discretion and must be approved in writing before the current contract term ends.

• Extensions are not automatic, and the College is not required to exercise either option.

• Vendors must provide pricing for the initial three years and each optional extension year (Years 4 and 5).

• Vendors must identify any annual price increases or other pricing changes that may apply during the initial term or extension periods, including the maximum annual increase.

The College may consider vendor performance, satisfaction with the system, and its ongoing needs when deciding whether to exercise an extension option.

12. Pricing Requirements Vendors must provide a complete pricing proposal showing all costs to purchase, set up, use, and maintain the proposed system. Pricing must separately identify:

• Initial setup and implementation costs.

• Software license or subscription fees.

• User license costs, the licensing model (named or concurrent users), and any limits on the number of users.

Vendors must state whether campus users who only submit and track requests require a paid license.

• Data migration costs.

• AutoCAD integration costs.

• Drawing preparation services, if needed.

• Training costs.

• Ongoing technical support and maintenance costs.

• Costs for each module, listed as a separate line item, and for any third-party software.

• Optional services and future enhancements.

• Optional on-site facility condition assessment services, if offered.

• Hosting costs, if not included in the subscription fee.

• Annual costs for Years 1 through 5, including both optional extension years.

Vendors must identify all additional or recurring costs the College may have to pay during the contract. Pricing should make clear which costs are one-time and which costs will continue each year.

Vendors must state whether the proposed system is available through a cooperative purchasing contract, such as Sourcewell, E&I Cooperative Services, or PA COSTARS, and provide the contract number and pricing under that contract.

13. Implementation Schedule and Project Deliverables Vendors must provide an estimated schedule showing how long it will take to set up, test, and launch the system. The schedule should include:

• Project kickoff and review of College requirements.

• System setup and configuration.

• Data transfer.

• AutoCAD integration.

• Loading occupant and room assignment records.

• System testing.

• Employee training.

• System launch.

• Support after launch.

The vendor must provide the following project deliverables:

• A project plan and implementation schedule.

• A fully set-up Facilities Management System.

• Transfer of agreed-upon College data.

• Imported and connected AutoCAD drawings.

• Loaded occupant and room assignment records.

• Configured work order, preventive maintenance, compliance inspection, key, space, occupant, asset, and facility assessment functions.

• User accounts and access permissions.

• System testing and confirmation that required functions work.

• Employee training and training materials.

• System and administrator documentation.

• Support during launch and after implementation.

14. Testing and Final Acceptance The College will review and test the system before accepting the completed work. The vendor must show that the required functions work as agreed. Testing may include:

• Creating, assigning, tracking, and completing work orders.

• Completing a work order on a mobile device, including without a network connection.

• Scheduling and tracking preventive maintenance.

• Logging a compliance inspection with attached documents.

• Issuing and tracking keys.

• Producing a report of every key held by a departing employee.

• Viewing and managing spaces using imported AutoCAD drawings.

• Updating occupant records from a Human Resources spreadsheet file.

• Completing and saving facility condition assessments.

• Maintaining equipment and asset records.

• Creating required reports.

• Confirming that user access and permissions work correctly.

The vendor must correct problems identified during testing before final acceptance. The College will provide final acceptance after the system is working as required, the agreed deliverables have been provided, and outstanding issues have been satisfactorily resolved.

15. Product Demonstrations The College may invite vendors to give a live demonstration of the proposed system. Demonstrations will follow a script and scenarios provided by the College. The College may also ask vendors to run College scenarios during the demonstration that were not provided in advance.

Demonstrations must use the vendor’s current production software, not slides, videos, or mock-ups. The College may treat a function claimed in the proposal but not shown during the demonstration as unverified. The vendor’s proposed project manager should attend.

RFP RESPONSE NOTE

Vendors must respond to each requirement in this Scope of Work using one of the following codes, with a brief explanation:

• Included — available in the proposed system at the proposed price.

• Additional Module or Fee — available for an additional cost, shown in the pricing proposal.

• Customization — requires custom development; state the cost and timeline.

• Third-Party — provided through another company’s product; name the product.

• Future Release — not in the current production release; state the planned release date.

• Not Available — the proposed system cannot meet this requirement.

A requirement left without a response will be treated as Not Available.

1. Project Overview
1.1 Current Environment
2. Project Goals
3. Scope of Services and System Requirements
3.1 Work Order Management
3.2 Preventive Maintenance
3.3 Key and Lock Management
3.4 Space Management and AutoCAD Integration
3.5 Facility Condition Assessments
3.6 Asset and Equipment Management
3.7 Reports and Management Tools
3.8 Compliance Inspections and Records
3.9 Ease of Use and Mobile Access
3.10 Integrations and Data Exchange
3.11 Items Not Included in This Scope
4. System Setup and Implementation
5. Data Migration
6. Training
7. Technical and Security Requirements
8. Ongoing Maintenance and Technical Support
9. Vendor Qualifications and Experience
10. Vendor Proposal Requirements
11. Contract Term and Renewal Options
12. Pricing Requirements
13. Implementation Schedule and Project Deliverables
14. Testing and Final Acceptance
15. Product Demonstrations

File details come from the government source that posted it. Updated .