18-FINAL RFP 10255-Facilities Management Software.pdf

PDF 695 KB Posted

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

About this file

RFP #10255: Facilities Management System

This is a Request for Proposal (RFP) issued by the Community College of Philadelphia for a Facilities Management System (FMS) application to be delivered as a Software-as-a-Service (SaaS) model. The project encompasses implementation and ongoing support for work order and preventive maintenance management, built-in key and lock management, space management with AutoCAD integration, facility condition assessments, asset management, and reporting capabilities. The RFP opened on November 13, 2026, with queries due by December 11, 2026, at 5:00 p.m. EDT. The College will respond to all queries by December 22, 2026, at 5:00 p.m. EDT. Proposals are due on Wednesday, January 27, 2027, at 12:00 p.m. EDT, with finalist interviews scheduled for the week of February 4, 2027, and a bid award announcement on March 1, 2027. The initial contract term is three years from the contract execution date, with two optional one-year extension periods available at the College's discretion, for a maximum contract term of five years. The selected vendor will be responsible for system setup, configuration, data migration from the current FAMIS system, AutoCAD integration, user training, and ongoing technical support.

Vendors must provide comprehensive pricing proposals identifying all costs separately, including initial setup and implementation, software license or subscription fees, user licensing costs and models, data migration costs, AutoCAD integration costs, training costs, ongoing technical support and maintenance, costs for optional modules and third-party software, and hosting costs if not included in the subscription fee. The College seeks to include diverse, small, and local-based suppliers and encourages vendors to partner with MBE, WBE, DBE, MWDBE, SBE, and LBE subcontractors; however, no specific set-aside is identified in the RFP. The current environment includes 11 buildings, approximately 1,600 rooms and spaces, approximately 800 employee occupants, and 25 daily system users, with all current work order and maintenance records held in the FAMIS system by Accruent. The College is exempt from sales tax and requires vendors to maintain comprehensive insurance coverage, including cyber security liability insurance of $5,000,000 and professional liability insurance of $1,000,000 per occurrence and $3,000,000 aggregate. Vendors must demonstrate financial soundness, provide at least three customer references from colleges or universities currently using the proposed system, and clearly identify any requirements they cannot meet in their proposals.

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

Rev. 8.25.2023

RFP 10255: Facilities Management System Description: Software System for Maintenance

Operations

RFP Opens: November 13, 2026

Queries Due Date: Friday December 11, 2026 Time: 5:00pm (EDT)

CCP Response to Queries Due Date: Tuesday, December 22, 2026 Time: 5:00pm (EDT)

Proposal Administrator: R Jackson Purchasing Department, Room M1-4A Community College of Philadelphia 1700 Spring Garden Street Philadelphia, PA 19130

Email: CCPbidresponse.edu

Proposals Due Date: Wednesday, January 27, 2027 Time: 12:00pm (EDT)

Bid Award Announced Date: March 1, 2027

Rev. 8.25.2023

RFP XXXX

TABLE OF CONTENTS

I. REQUEST FOR PROPOSAL

II. INTRODUCTION

A. PURPOSE

B. SCOPE OF VENDOR’S PROPOSED SOLUTION & SERVICES

C. AVAILABLE BACKGROUND INFORMATION

D. PROJECT SCHEDULE

III. PROPOSAL CONTENT

A. QUALIFICATION AND TECHNICAL PROPOSALS

B. COST PROPOSAL

C. ASSIGNMENT OF KEY STAFF

D. SUPPLEMENTARY DOCUMENTS

IV. PROPOSAL PROCESS

A. PRE-PROPOSAL CONFERENCE

B. VENDOR’S CLARIFICATION AND QUESTIONS

C. PROPOSAL AS PROPERTY OF COLLEGE AND PENNSYLVANIA

RIGHT TO KNOW LAW

D. EVALUATION OF PROPOSALS

E. PROPOSAL SUBMISSION

F. WITHDRAWAL OF PROPOSALS

G. PROCEDURE FOR REVIEW OF PROPOSALS

H. WINNING PROPOSAL

I. INSURANCE

J. HOLD HARMLESS

K. PATENT LIABILITY

Rev. 8.28.23

RFP 10255

L. TAX EXEMPTION

M. AUTHORITY TO DO BUSINESS IN PENNSYLVANIA

N. EQUAL EMPLOYMENT OPPORTUNITY

O. NON-COLLUSION AFFIDAVIT

P. USE OF COLLEGE’S NAME

Q. ALTERATIONS OR MODIFICATIONS

R. SAFETY

S. WORK STOPPAGE

T. EXCLUDED PARTIES AFFIDAVIT

U. SUBCONTRACTS

V. RIGHT TO AUDIT RECORDS

W. DISSEMINATION OF INFORMATION

X OBSERVANCE OF LAWS, ORDINANCES AND REGULATIONS

V. RESERVATION OF RIGHTS AND DISCLAIMERS

A. DISCLAIMERS

B. RESERVATION OF RIGHTS

VI. NON-COLLUSION AFFIDAVIT

VIII. VENDOR’S STATEMENT FOR PUBLIC DISCLOSURE

IX. CERTIFICATION OF EEO-1 FORM OR WORKFORCE DEMOGRAPHICS

AND COMPANY OWNERSHIP REPORT

X. STATEMENT OF EEO/AFFIRMATIVE ACTION COMPLIANCE

XI. EXCLUDED PARTIES AFFIDAVIT

XII. AFFIDAVIT OF VERIFICATION OF PROPOSAL

I. REQUEST FOR PROPOSAL

The Community College of Philadelphia (“College”) is soliciting proposals (each, a “Proposal”) for the delivery of a Facilities Management System (FMS) application, to be delivered in a “Software-as-a-Service” (SaaS) model (“Solution”), with implementation and ongoing services related to the Solution, including work order and preventive maintenance, built-in key and lock management, space management with AutoCAD integration, facility condition assessments, asset management, and reporting. The Solution and related services are hereinafter collectively referred to as the “Project”. The College reserves the right to award all, some or none of the Project services set forth in this Request for Proposals (“RFP”) to any one or more Proposers based on the College’s review and assessment of the Proposals meeting the criteria set forth herein. In the event the College awards Project services pursuant to this RFP, the Proposer selected by the College (the “Vendor”) may lead one or more subcontractors (“Subcontractors”) to perform the services requested by the College pursuant to this RFP.

II. INTRODUCTION

A. PURPOSE

The College is seeking a central software system to help the Facilities Department manage its daily work, maintain College buildings and equipment, and plan for future facility needs.

• Work orders and maintenance requests.

• Scheduled preventive maintenance.

• Key and lock tracking.

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

AutoCAD drawings.

• 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 should be practical and easy for employees to use

B. SCOPE OF VENDOR’S PROPOSED SOLUTION AND SERVICES

The College is seeking a vendor 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.

C. AVAILABLE BACKGROUND INFORMATION

Technical documents associated with the Project may be made available by the College to the Vendors if deemed necessary by the College for the Vendors to prepare a Proposal and evaluate the Solution and services required herein. The means of delivering the technical documents associated with this RFP must be uploaded to https://pennbid.net site for downloading by the Vendors.

The Vendors shall treat all information disclosed by the College or its agents to the Vendors pursuant to this RFP as confidential information and shall not disclose such confidential information except to the extent required by applicable laws. However, the Vendor shall not be obligated to treat any information as confidential if it (a) is available to the public as of the date hereof; (b) becomes available to the Vendor on a non-confidential basis from a source other than the College or its agents; or (c) is developed independently by the Vendor.

In addition, each Vendor must submit in its Proposal a list detailing the specific information, records and documents it will need from the College to perform the Project in the event that the Vendor is selected.

D. PROJECT SCHEDULE

The Vendor shall begin work on the date set forth in the Agreement after it is fully executed. The initial activities of the Vendor shall be to work with the College to review the Project schedule and budget and develop and present a work approach to the College.

A proposed schedule for the completion of the Project is set forth in Attachment 1 to this RFP and is incorporated herein. Each Vendor shall provide a detailed Project schedule including these milestones as part of the Proposal and discuss its ability to meet the proposed schedule in Attachment 1.

III. PROPOSAL CONTENT

While there is not a specific page limitation, the Proposals shall provide a straightforward, concise description of the Vendor’s ability to fulfill the requirements of the Project, as set forth in this RFP.

In order to ensure a uniform review process and to obtain the maximum degree of comparability, it is required that the Proposals include the information and are organized in the manner specified below.

A. QUALIFICATION AND TECHNICAL PROPOSALS

As a component of the Proposal, each Vendor shall submit a “Technical Proposal” which shall include, without limitation, the information outlined in this RFP. The response under this section shall include the following:

1. A Proposal Form

Proposals shall be submitted online via email to Pennbid.net. Proposals shall acknowledge the Bidding Instructions, Terms and Conditions, and Specifications sections of this Proposal. A Proposal, which is incomplete, obscure, conditional, contains additions not called for, or has irregularities of any kind, including alterations, may be rejected as non-responsive.

2. Company Overview: Provide an overview of the prime firm.

3. Project Qualifications and Experience

a. The Vendor shall demonstrate its knowledge and understanding of the Project with specific examples of similar efforts. Include a summary of each such relevant project experience by the Vendor.

b. The Vendor shall submit at least three (3) of its clients (including names, email address and phone numbers) as references and describe the relevant project for such clients.

c. The Vendor shall indicate its local knowledge and understanding.

4. Project Team: Organization charts identifying (a) the Project Manager, (b) a description of staff roles, (c) a description of Subcontractor roles, and (d) the qualifications, experience and office address for each proposed individual that the Vendor will use to perform the Project (the “Project Team”). Résumés, limited to two (2) pages each, for each individual on the Project Team shall be included in an appendix to the Proposal.

5. Commitment to Diversity, Inclusion, and Philadelphia-Based Business Community. College of Philadelphia is committed to diversity and inclusion and is committed to including diverse and inclusive companies, including small and local businesses, in the bidding process whenever possible. The College encourages Vendor to actively recruit and contract with MBE, WBE, DBE, and MWDBE subcontractors or subcontractors with substantial representation from traditionally underrepresented individuals among their employees. The College also encourages Vendors to actively recruit and contract with SBE and LBE subcontractors. MBE, WBE, DBE, MWDBE, SBE and LBE companies are also encouraged to apply directly. The information provided in response to this section may be a factor considered by the College in determining which Vendor should be awarded this contract but will not automatically disqualify any Vendor from consideration.

a. Please indicate whether your company is registered and/or certified as a small business enterprise (SBE) or local business enterprise (LBE) in Philadelphia. The College recognizes and accepts the certifications of agencies acceptable to the City of Philadelphia. Please include proof of the SBE or LBE registration and/or certification.

b. Please provide the number and percentage of underrepresented minority and women employees in your company and state the percentage of your company that is owned by underrepresented minorities, women, or disabled individuals.

c. Please provide a description of MBE, WBE, DBE, MWDBE, SBE, and LBE subcontractors in projects at your company.

6. Project Approach: The Vendor shall describe its understanding and approach to completing the Project, including the following:

a. The Vendor shall detail the scope of work to be provided under each phase of work.

b. The level of effort under these tasks shall be based on an assumed number and extent of activities over the full Project time frame.

c. All work necessary to complete the work and not specifically identified in Article II, Section B of this RFP, including any impact on the Schedule shown in Attachment 1 to this RFP.

7. Schedule: The Vendor shall also provide a preliminary Project schedule showing the planned approach, key task activities and milestones necessary to meet the Project schedule. The Vendor shall identify significant potential risks that may impact the schedule with recommendations for the mitigation and/or elimination of such risks.

8. Financial Soundness of Vendor: The Vendor’s most recent certified annual report, including balance sheets and profit and loss statements, must be submitted with the Proposal. All information pertaining to the financial soundness of the Vendor shall be marked by the Vendor as “Confidential.”

The College will contract only with a Vendor found to be financially sound.

In addition, the College should be notified if there is (are) a major claim(s) against the Vendor that could affect its ability to perform the Project.

9. Litigation/Judgments – The Vendor must fully disclose all pending or closed litigation or investigations pending with any governmental agency in which it or any of its affiliates, members, or officers are currently involved and all matters that have occurred within five years of the date of the submission of the Proposal. Should there be no legal actions, suits, proceedings, claims or investigations pending with any governmental agency with which the Vendor has had or currently has a contractual relationship, include a statement to that effect.

10. Conflicts of Interest – The Vendor must identify any past, current or anticipated contractual or financial relationship with the College, or its staff or board members, or any other contractual or financial relationship that may give the appearance of a conflict of interest.

B. COST PROPOSAL

Payment for services under this Project shall be on a not-to-exceed fee basis or a firm fixed fee basis.

The Proposal shall include a “Cost Proposal” which shall identify a schedule of the proposed hourly billing rates for each and every member and corresponding hours for each and every member of the Project Team as well as a total not-to-exceed fee for all of the Vendor’s services to complete the Project. The Proposal shall include a detailed spreadsheet showing the hours, labor costs, expenses and total cost for each task in the Project. The Cost Proposal shall include a not-to-exceed budget for reimbursable expenses that the Proposal contemplates it may incur. Expenses for mileage, parking, reproduction, telephone, fax, and computer charges will not be allowed. For the Vendors’ convenience, a Cost Proposal Form is included with this RFP as Attachment 2. The Vendor’s Cost Proposal shall be presented on the attached Cost Proposal Form. Any deviations, if required, shall be noted on the Cost Proposal Form.

Should a Vendor notice obvious omissions on the part of the College in the outline of services, such omissions should be included and noted in the Vendor’s Proposal. Hidden cost(s) revealed during the performance of contract will be construed as misrepresentation of service and may avoid award of Contract, at the discretion of the College. All quotes are to be F.O.B. Destinations. If the Vendor anticipates additional services not addressed in the Cost Proposal Form which, in its opinion, will be required for the Vendor to complete the Project, such additional services shall be noted on the Cost Proposal Form, with a general explanation of the services, a brief justification as to why such services may be required, and a corresponding proposal for the cost of such services.

The Vendor will invoice the College in accordance with the process set forth in the Cost Proposal as it is incorporated in the Contract for its performance of the Project. Unless otherwise approved in writing by the College’s Purchasing Department, the Vendor shall not be entitled to any payment from the College in excess of the not-to-exceed fee provided in the Cost Proposal and incorporated in the Contract.

The Vendor shall also provide a schedule of hourly billing rates in the event the College requests, in writing, that additional services be performed outside of the scope of services specified herein.

C. ASSIGNMENT OF KEY STAFF

The key member(s) of the proposed Project Team must be identified in the Proposal and assigned to the Project and must remain assigned and available to the Project for its duration unless such person leaves the employment of the Vendor or the College agrees in writing to modify the proposed Project Team. If a key member leaves the employment of the Vendor during the course of the Project, the College must be notified immediately, and the Vendor must submit the name and credentials of the person replacing the key member for approval by the College prior to that person starting work on the Project.

D. SUPPLEMENTARY DOCUMENTS

The Vendor shall execute a Non-collusion Affidavit, a Vendor’s Statement for Public Disclosure;

Equal Employment Opportunity Compliance Statement; Certification of EEO-1 Form or Workforce Demographics and Company Ownership Report; Verification of Proposal Affidavit; and an Excluded Parties Affidavit, as such documents are set forth below. Any Subcontractor identified in the Proposal shall also execute a Non-collusion affidavit, a Vendor’s Statement for Public Disclosure; Verification of Proposal Affidavit; and Excluded Parties Affidavit, as such documents are set forth below. All such executed documents shall be included with the Proposal.

IV. PROPOSAL PROCESS

By submitting a Proposal, each Vendor certifies that it has read the complete RFP, understands the Proposal process, and has full knowledge of the scope, nature and quality of work to be performed associated with this RFP, and accepts and agrees to all provisions of this RFP. Any and all expenses incurred by Vendors in submitting Proposals shall be borne solely by Vendors.

A. PRE-PROPOSAL CONFERENCE

N/A

B. VENDOR’S CLARIFICATION AND QUESTIONS

To ensure fair consideration for all Vendors, the College prohibits communication to or with any College official, department director, division manager, employee, or the Project Manager related to this RFP prior to the submission of the Proposal with the exception of those questions relative to interpretation of specifications or the Proposal process.

Interpretations of the meaning of the RFP documents made to any Vendor orally shall not be binding on the College or any other Vendor.

The College is requesting that any questions or clarification requests be submitted in writing via e-mail, by 12:00 p.m. EST/EDT, Friday, December 11, 2026. All questions and associated correspondences should be submitted to: CCPBidResponse@ccp.edu. It is the College’s intent to review these questions, and provide a response to all of the Vendors (anonymously) by 5:00 p.m.

EST/EDT, Tuesday, December 22, 2026

After the Proposal has been submitted to the College, communications initiated by a Vendor to the College related to this RFP, the Proposal, or the Project shall be prohibited until a Contract has been executed by the College. Any communication between a Vendor and the College shall only be initiated by the appropriate College employee or agent in order to obtain information or clarification needed to develop a proper, accurate evaluation of the Proposal.

Any prohibited communications initiated by a Vendor may be grounds for disqualifying the offending Vendor from consideration for award of the Proposal and/or any future proposal.

C. PROPOSAL AS PROPERTY OF COLLEGE AND PENNSYLVANIA

RIGHT TO KNOW LAW

All Proposals become the exclusive property of the College upon receipt and will not be returned.

Responses to this Request for Proposal and documents entered into by the selected Vendor may be subject to Pennsylvania’s Right to Know Law (“RTKL”). Any “confidential proprietary information” or “trade secrets” (as defined under the RTKL) delivered to the College must be marked as such.

D. EVALUATION OF PROPOSALS

The award of the services associated with this RFP may or may not be made to the Vendor submitting the lowest price Cost Proposal. The award will be made to the Vendor whose Proposal is determined to be the most advantageous to the College, taking into consideration, without limitation the evaluation factors set forth below:

1. Price, Alternate Price and/or cost items deemed in the best interest of the College.

2. Experience, qualifications, and commitment of the Project Team:

a. The degree to which the personnel on the Project Team have held responsible project positions for similar projects;

b. The degree to which the Project Team brings experience in the full range of skills and expertise needed to accomplish the scope of work in all task areas;

c. The specific commitments made in the Proposal for staffing the Project Team, including percent of Project Manager’s time dedicated to the Project;

d. Experience within the local permitting region; and

e. Any other experience and/or criteria the committee deems relevant.

3. Experience and past performance of the Vendor and Project Team members on similar projects within the last seven years:

a. The experience of the Vendor and Project Team members in conducting projects of similar nature and complexity;

b. The ability of the Vendor to draw on this experience to benefit the Project; and

c. Any other experience and/or criteria the College deems relevant.

4. Method of accomplishing the scope of work:

a. Proposed organization of the work;

b. Unique capabilities that may influence the Project;

c. Understanding of the appropriate levels of effort required (hours) for various tasks;

d. Identification of Project risks and methods to mitigate or eliminate such risks to complete the Project within the proposed schedule, estimated budget and with the quality and/or performance specifications identified herein;

e. Appropriate Project financial and management controls including, but not limited to,

i. Clear method of meeting and tracking progress of schedule milestones, intended outcomes, and deliverables for each task

ii. Quality assurance

iii. Project financial controls and invoicing systems

5. Commitment to Diversity, Inclusion and support of small and local-based businesses

6. Any other experience and/or criteria the College deems relevant.

The College Selection Team will consist of representatives from Community College of Philadelphia Security, Information Technology, Facilities, Finance & Budgets and Purchasing staff.

E. PROPOSAL SUBMISSION

All documents are to be uploaded to Pennbid.net

F. WITHDRAWAL OF PROPOSALS

Proposals may not be modified after submittal. Proposals may be withdrawn after submittal, provided the Vendor makes its request to withdraw in writing and the request is received and acknowledged by the College in writing prior to the time specified for the Proposal Opening.

Negligence by Vendor in preparing its Proposal confers no right of withdrawal or modification of its Proposal after such Proposal has been opened. No claims on account of mistakes or omissions in any Proposal will be considered. Proposals are deemed a firm offer and each Vendor agrees that its Proposal shall not be withdrawn within one hundred twenty (120) days from the Proposal Opening.

G. PROCEDURE FOR REVIEW OF PROPOSALS

The College shall conduct a preliminary evaluation of all Proposals based on the information provided.

The College will first…

This is the start of the file's text. The full file is on GovTribe.

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