Site work for an educational facility in Detroit, Michigan. Completed plans call for site work for a educational facility.

Wayne State University invites you to participate in its Request for Proposal process to provide Digital Sign 2024, for the Computing & Information Technology and Marketing & Communications, per the specifications contained herein the Request for Proposal. This service is expected to commence on November 1, 2024 additional pre bid meeting note: Attendance will be taken during the Prebid Meeting. When Pre-proposal Meetings are Optional, nominal scorecard points will be awarded for attendance. We hope you can join us at the Optional pre-proposal meeting. Please have a copy of this Request for Proposal for your reference during the meeting. Should you have any questions or concerns about this invitation, please contact me at (313) 577-3712, or email: Rfpteam3@wayne.edu. Thank you for your interest in doing business with Wayne State University. All questions concerning this Request for Proposal are to be directed to Robert Kuhn, Senior Buyer, Email; Rfpteam3@wayne.edu. The deadline for questions is August 9, 2024, 12:00 noon. Project Requirements and Specifications: The university currently has 120 digital signs in various locations around campus. Most have similar hardware with a few signs as outliers (positioned vertically, multiple display arrays, touch screen or have audio capabilities). The hardware is currently Windows PCs (Dell) and we are open to changing the hardware for a lower cost or ease of deployment/maintenance. Ideally all signs are on their own network isolated from campus traffic and any firewall rules would need to be outlined to ensure security. The software is controlled centrally and is managed by C&IT. Centralized control of all the signs on campus is necessary to determine the status of each sign, confirm the live visuals, and to deploy or restart signs. The schedule and content of each sign is controlled centrally by Marketing and Communications. This groups works with the communicators within each unit to determine the content needs of each sign, and to design the templates that ensure our branding is consistent with university style. Each sign has a schedule of templates that loop throughout the day with special templates that are scheduled on specific date/times based on need. The templates pull content from the public web through RSS feeds (format of these data feeds can be adjusted to the system needs) that each School/College communicator manages through the centralized content management system. This ensures the titles, graphics and timing of each item is stored in a single central location and promoted consistently across various mediums on campus. Only the C&IT team and Marketing team will need direct access to the signage software, the communicators will be managing content through the University Content Management System (CMS). The University uses Rave for emergency messaging and each sign must allow for a trigger from Rave or from an RSS feed or webhook to switch over within a minute of being deployed to switch the signs to an emergency alert with the text from the triggered message. This RFP is intended to establish a preferred supplier for an enterprise solution for interactive digital signage with the ability to integrate with RAVE for emergency messages and safely manage the content that gets displayed on the devices and provide a secure and seamless method of doing so. The solution should provide the ability for future growth. o A cloud-based solution is preferred, however on-premises solutions may be considered. o The University seeks to engage on a three-year basis, with two (1) year renewal options for years four and five. Pricing shall be firm for the first three (3) years. o This project will primarily be focused on the replacement of an existing FourWinds Software solution with approximately 120 Windows 10/11 based signs/players. There is a potential need to replace up to one third of the existing endpoint hardware. o We intend to continue to use the existing Windows 10/11 based endpoint hardware. o Up to one third of the existing endpoints are nearing EOL. o While not required, vendor demos including deploying endpoints, publishing, and updating content, and other management functions are preferred. o Vendors should provide a preferred migration plan from the existing solution to the proposed solution including implementation timelines. o Technical support costs should be included per Service Level below: Service Level Business Day Work Hours are Monday - Friday, 8:00 am - 5:00 pm. Response times as : o 4 Hour Emergency o Next Business Day Specifications: Cloud Hosted Preferred Product is scalable Multi-screen support Update hardware device remotely WIFI support Touchscreen display support Multi-user support Role-based permission support Multiple users update, schedule & edit content Support for image slideshows Customizable template support 1080p or above display support Support screen division (Optional) Support for sound Ideal hardware environment Use on a variety of players: Windows 10/11 x64, Android, Apple tvOS/iOS/macOS, BrightSign, Raspberry Pi, and WebOS. Works with EMS Scheduling (room scheduling) software. Compatible with Wayne State's content management system through RSS, JSON, XML or other web tools Templates are stored in the native signage platform All content will exist at web-based URLs and fed into each template Compatible with Emergency messaging: RAVE or RSS feed Ability to flip each sign over to an emergency template displaying content from the message Some signs would be excluded from this functionality Use on our existing PC players: Dell Open to hardware changes based on switching costs and maintenance Use on a variety of players: Windows 10 x64, iOS, Android, AppleTVOS/iOS/MacOS, BrightSign, Raspberry Pi, and WebOS. Remote monitoring and administration Only 4-6 people would need access to manage the signs and the system Content owners would not need access, they have existing access to manage content fed into the templates on a third-party content management system through public data feeds Ideally the signs should turn off/sleep from 11pm to 6am each day Ease of use to manage 120 players 1920x1080 - 105 signs 1080x1920 - 6 signs 2 4-display arrays Able to work with our network and firewall rules 3 to 4 templates per player (some examples in place now below) Each sign has a unique list of templates and rotation of content based on time of day, content available or special events The ability to feed a live video feed (RTSP) within a template Full screen images that cycle through images based on a set interval and content feed through an XML or JSON feed General template that has an overall frame and feed various content in from news, events, weather, time and graphical promotions with adjacent text, each from their own XML feeds. A full screen web view (public URL that is displayed full screen without any browser chrome). This is for customized layout that adapt to the screen resolution and for touch screen signs Full screen video played through YouTube with embed URL that ensures captions are turned on Skippable templates if no content is available (example: slideshow of images that comes from an XML feed, if there are images, they are displayed for X seconds each, if there are none, the template is skipped in the timeline) Implementation Methodology Vendors should provide detailed information on the implementation services for the successful implementation of the proposed software. Include, at a minimum, the following information: 1. An overview of your education and knowledge-sharing methodologies 2. An overview of data migration methodology and tools 3. A high-level project timeline and deployment methodology Post-Implementation Support/Value Added Services Vendors should provide detailed information of available ongoing support of the proposed software. Include, at a minimum, the following information: 1. Post-Go-Live Support Services (Help) 2. Support turnaround time or resolution time for support incidents and escalation procedures 3. Upgrade release methodology Customer Participation and Communication Vendors should provide detailed information on the available ongoing support options for the proposed software. Include, at a minimum, the following information: 1. How does your company show your commitment to customers 2. How do customers participate and have input into new functionality 3. How does your company notify customers of updates 4. How does your company publish future roadmaps Prospective vendors should respond to all items in the attached Excel workbook. For each specified feature or capability in the various tabs, choose the option that best represents the capabilities of your products; only provide additional caveats or notes if it is necessary to elaborate. The contract(s) will be for a three-year period ending on September 30, 2027. Thereafter, the UNIVERSITY may, at its option, extend the contract, on a year-to-year basis for up to two one-year periods, through September 30, 2029. VENDORS must state maximum price increases (if any) for years two and three on Cost Schedule C