|
** Please Note The Rfp Is Only Available To Download From Merx***** Please Go To Www.Merx.Com To Download And Submit The Rfp ***Deliverables Simon Fraser University (Sfu) Is Seeking A Qualified Proponent To Supply, Implement, Integrate, And Support A Comprehensive Campus Card And Mobile Credential System. The Solution Must Provide Secure Identification, Access Control, Stored-Value Payments, And Mobile Services That Support Daily Campus Operations. The Solution Will Serve All Students, Faculty, And Staff Across The University. This Section Outlines The Scope Of Work And Deliverables That Describe The Full Functional, Technical, Operational, And Service Requirements Expected From The Successful Proponent.For Additional Information Regarding The Current Environment, Please Refer To Appendix F – Current State Overview.Scope Of Workthis Project Aims To Modernize Sfu’S Campus Credentialing Ecosystem And Establish A Unified, Secure, And Scalable Identity Platform That Supports Both Current And Future Functional Needs Across All Sfu Campuses. The Proponent’S Solution Must Meet Sfu’S Operational, Technical, And Privacy Requirements While Providing Seamless User Experience For Students, Employees, And Guests.Sfu Is A Multi‑Campus Institution Serving Approximately 35,000 Students And 7,000 Faculty And Staff, As Well As Additional Affiliates, Contractors, Alumni, And Guests; The Proposed Solution Must Be Capable Of Supporting This Population And Scaling Appropriately Over The Term Of The Agreement.Sfu Plans To Implement Similar Functionality (Plus Photo Upload Capabilities) To What Is Currently In Place As Part Of The Initial Rollout, Targeting Spring 2027. Other Functionality Will Be Rolled Out In Phases With Full Project Completion Targeted For Fall 2027. It Is Expected That The Core Functionality That Enables Future Modules Will Be Rolled Out As Part Of The Initial Phase.Note: If Functionality Requested For Fall 2027 Is Included As Part Of The Core Functionality In A Bundled Package At The Same Cost, It Does Not Necessarily Need To Be Disabled At Launch And Should Be Highlighted To Be Specifically Addressed During The Interview Phase. We May Explore The Feasibility And Expected Costs Of Disabling It At That Time.2.1.1 System Overviewthe Solution Must Support:Spring 2027Physical Card Issuance And Managementintegration With Sfu Systems And Campus Operationsonline User Account Managementadministration Tools For Sfu Staffreal-Time Or Near Real-Time Data Synchronizationfall 2027Mobile Credentials On Ios And Android Nfc Or Equivalent Mobile Access Technologies Stored Value Accounts (Printing, Dining, Vending, Retail, Recreation, And Other Services) The System Must Be Able To Serve All Sfu Campuses, Users, And Operational Units Connected To Identification, Access, And Payment Services.2.1.2 Identification & Credentialing The Proponent Must Provide A System That:Spring 2027Supports Personalized Physical Cardsdisplays A Human‑Readable Card Number In Addition To A Scannable, Machine‑Readable Identifier On Physical Cards, To Support Systems Requiring Manual Identifier Entry (E.G., Ezproxy Authentication). The Same Identifier Requirements Apply To Physical And Mobile Credentials.Fall 2027Supports Digital/Mobile Credentialsallows Issuing, Reissuing, Suspending, Revoking, And Restoring Credentialsautomatically Deactivates Older Credentials When New Ones Are Issuedsupports Multiple User Affiliations (Student, Staff, Contractor, Alumni, Temporary Visitor)Support Issuance Of Temporary Or Limited‑Purpose Credentials (Physical Or Digital) For Guests, Visitors, And Affiliates, With Configurable Duration, Access Rights, And Optional Fees.Provides Secure Authentication For Identity-Based Transactions And Campus Access2.1.3 Stored Value & Payment Servicesthe System Must:Fall 2027Support Declining Balance Accounts For Campus Servicesprovide Balance Visibility, Transaction History, And Secure Online Reloadssupport On-Campus Pos Integrationsupport Optional Off-Campus Merchant Programsmaintain Pci-Compliant Handling Of All Financial Transactionsensure Sfu Systems Do Not Store Credit Card Informationsupport Offline Transaction Processing At On-Campus Pos Locations In The Event Of Temporary Network Or System Outages, With Secure Deferred Posting Once Connectivity Is Restoredsupport Hybrid Meal Plans That Combine All You Care To Eat (Aycte) Access With Declining Balance Components Within A Single Credentialsupport The Purchase Of Meal Value Packs Through The Mobile App, With Immediate Availability Of Funds2.1.4 Door Access & Physical Security Integrationthe System Must Provide:Fall 2027Integrate With Sfu’S Existing Access Control Infrastructuresynchronize Entitlements Based On User Statussupport Mobile Access (Nfc Or Equivalent) Where Compatibleprovide Audit Logs And Reporting Needed For Security Compliancedoor Access Systems Must Continue To Function During Temporary Network Outages2.1.5 Mobile Credential & Mobile App Servicesthe Proponent Must Provide:Fall 2027An Sfu-Branded Mobile Credential Appability To Use Mobile Phones For Payments And Future Door Accessoptional Mobile Ordering Integration For Sfu Retail And Food Service Providerspush Notifications And Configurable User Messaging (Preferred)Mobile Credentials Must Display The Card Number In A Human‑Readable Format And Support Presentation Of A Scannable, Machine‑Readable Identifier, To Accommodate Systems That Require Manual Entry Or Automated Capture Of The Identifier (E.G., Ezproxy Authentication).2.1.6 Online Account Managementthe Solution Must Include:Spring 2027Administrative Tools For Card Office Operationsweb-Based Management Consoles For Authorized Sfu Stafffall 2027User Portal For Balances, Reloads, Transaction History Automated Workflows For Student/Employee Onboarding And Offboardingall Web Portals, Mobile Apps, And Administrative Consoles Must Comply With Wcag 2.1 Aa.Provide A Secure Guest Deposit Flow To Allow Non‑Sso Payers (E.G., Parents) To Add Funds To A User’S Sva.2.1.7 Integration Requirementsrequired Integrations Include, But Are Not Limited To:Spring 2027Sfu Identity Management (Sso, Mfa, Ldap/Ad)Sfu Erp / Student Information Systems (Peoplesoft)Hr Systems For Employee Data Residence And Housing Systems (Starrez)Athletics And Recreation (Fusion)Library Services (Alma)Printing Systems (E.G., Papercut)Pos Systems (Food Service, Bookstore, Parking, Vending, Recreation)Fall 2027Event Access (Ticketing To Replace Eventbrite)Door Access And Security Systems (Lenel And Honeywell)All Integrations Must Support Api, Sso, Secure Data Exchange, And Real-Time Or Near Real-Time Synchronization.2.1.8 Hosting, Security & Privacy – All For Spring 2027Mandatory Security & Privacy Requirementsthe Proponent Must, At Minimum:Demonstrate Compliance With Bc Freedom Of Information And Protection Of Privacy Act (Fippa)And Applicable Privacy Legislationstore And Process All Sfu Personal Information In Canada (On Premise, On Cloud Or Hybrid), Unless A Pia Has Been Conducted.Provide A Current Soc 2 Type Ii, Iso 27001 Certification, Or Equivalent Independent Security Assessmentmaintain Documented Incident Response, Vulnerability Management, And Patching Processesnotify Sfu Promptly Of Any Security Incident Or Breach Involving Sfu Data Or Systemsmaintain Third-Party Risk Management Practices, And An Updated List Of All Subcontractors With Access To Sfu Datacomply With Secure Payment Processing (Pci Dss)Commit To Ongoing Security Support And Advance Notice Of Product End Of Lifecomply With Sfu Security, Privacy, And Data Governance Policieshave Data Encryption In Transit And At Restdemonstrate Adoption Of Information Security Controls Aligned With An Industry‑Recognized Information Security Governance Framework (E.G., Iso/Iec 27001/27002, Nist Cybersecurity Framework, Or An Equivalent Framework).2.1.9 Reporting & Analytics – All For Spring 2027The Solution Must Provide:Financial And Transactional Reportsreconciliation Reports For Sva Accountscard Activity Reportsaudit Logs (Access, Issuance, Security)Exportable Formats For Finance, Audit, And Campus Operations2.1.10 Performance & Reliability – All For Spring 2027The Solution Must:Maintain 99.9% Uptime Availabilitysupport High Availability And Redundancy For Critical Servicesfollow Secure Disaster Recovery And Business Continuity Practicesscale To Support Sfu’S Population (Students, Staff, Affiliates, Guests)2.2 Phased Implementation And Timelinesthe Successful Proponent Must Deliver The Following Components, Services, And Outputs In Accordance With The Phased Implementation Timelines Described Below.2.2.1 System Delivery, Installation & Configurationspring 2027Full Deployment Of All Software And Hardware Components To Enable Functionality Covered In Section 1Configuration Of Credentialing, Integrations, User Portals, And Security Controlssetup Of Administrative And Reporting Modulesfall 2027Configuration Of Svadelivery Of Mobile Credential Functionality2.2.2 Implementation Servicesa Complete Project Plan Including Milestones, Timelines, Dependencies, And Resource Requirementstechnical Architecture Design And Documentationdata Mapping And Migration Assistancesystem Integration With All Sfu-Required Platformsfull Testing (Unit, Integration, User Acceptance, Performance, Failover)Production Cutover And Go-Live Supportpost-Implementation Stabilization Period (Minimum 30 Days)2.2.3 Card Production & Credential Toolscarding Software And Hardware Compatible With Sfu Environmentssupport For Sfu Card Branding And Multiple Card Design Templatesability To Source Photos Via Camera, Upload, Or Online Submissiontools For Encoding And Issuing Credentialsautomatic Deactivation Of Replaced Credentialssfu Prefers Solutions That Can Leverage Existing Card Production, Access Control, And Pos Hardware Where Feasible. Proponents Are Requested To Identify Any Existing Equipment That Can Be Reused, Along With Any Limitations Or New Hardware Requirements.2.2.4 Non-Production Environmentsprovide At Least One (1) Non-Production Environment For Testing, Training, And Upgradesmirror Production Data Structures And Integrations As Closely As Possible2.2.5 Training & Knowledge Transferinitial Training For Administrators, Card Office Staff, And It Staff As Specified By Sfu. (Train The Trainer).Ongoing Training For New Features, Upgrades, And Onboardingwritten And Video Documentation For Staff And End Userstechnical Documentation For Integrations, Architecture, And Configuration2.2.6 Support, Maintenance & Slaa Defined Service Level Agreement (Sla) Including:Response Time Commitmentsresolution Time Commitmentsescalation Proceduressupport Hours (Minimum 8Am–5Pm Pacific)Options For Extended Or 24/7 Support For Critical Issuesongoing Maintenance, Bug Fixes, And Patchesregular Feature Updates And Enhancementsa Dedicated Account Managercvs For All Individuals That Will Be Working On Implementation Of The Product And Their Role In The Implementation. 2.2.7 Security, Privacy & Compliance Deliverablesprivacy Impact Summarydata Flow Diagramssystem Architecture Diagramsencryption And Access Control Documentationconfirmation Of Fippa Compliancepci Compliance Attestation (If Applicable)2.2.8 Roadmap & Product Lifecyclea Software Development Roadmap Outlining Potential Future Enhancements.Notifications Of Major Releases, Changes, And End-Of-Life Componentscommitment To Ongoing Product Improvements Over The Contract Term2.2.9 Reporting & Analytics Toolsdashboards For Operational Visibilityfinancial Transaction Reporting For Reconciliationexport Tools For Sfu Finance And Departmental Auditsaccess Logs And Activity Reports2.2.10 Project Close-Outfinal Deliverables Package Including Configuration Documents, Training Materials, Project Reports, And Acceptance Sign-Offknowledge Transfer To Sfu It And Card Office Teamsfinal Issue Resolution Prior To Project Closurepricing
|
