1. UPDATE: Progress since Leading Age Nashville, Oct., 2014… Nurse Call System Added Sept, 2015 Medication eMAR System Added July, 2015

2. UPDATE: Progress since Leading Age Nashville, Oct., 2014… New POS System Nov, 2015 Resident Engagement System & Digital Signage Dec, 2015

3. UPDATE: Progress since Leading Age Nashville, Oct., 2014… Analyzing Fault Tolerance - Our Comcast Fiber Product Critical Systems -Nurses Stations, eMAR -Failover to Cellular Hot Spots CORE LAYER ISP REDUNDANCY

4. Project Costs Estimated vs Implemented

5. –Rose Villa Process for selecting a telephony vendor –Lessons learned from selecting equipment –Evaluating Fiber Internet Service Providers (ISP) –Getting objective advice from your IT consultant Telephone/ISP Vendor Analysis

6. Questions residents asked: and what we said: –Why can't you bring Fiber to each and every unit? –Will Rose Villa Management monitor my Internet Traffic? –What uptime can I expect? –How many devices can I plug into the new network Navigating Resident Concerns

7. 1.There’s no magic bullet, you have to upgrade and do the work 2.It’s costing more than we thought it would 3.GM estimated $900k for wiring existing construction, we pulled it out of the GMP and did it for half that. 4.The overall project had 5% contingency in the contractors GMP and then an additional 5% owners contingency – this appears that it will be adequate but low voltage has so many unknowns. Higher contingency for this space is necessary. Lessons Learned: Construction

8. –"WHO'S OUTAGE IS IT?" Dropped call incident of July –Lessons Learned: Symbiotic Partnerships vs. Pointing Fingers Navigating Costly Troubleshooting Fostering IT Vendor Teamwork Lessons Learned: Communication Tools

9. Resident Phone Equipment Selection –If it’s not in your hand, you can’t know how small it really is VS. Lessons Learned: Handset Selection

10. IT Vendors Don’t Speak Senior –Of 6 new residents, one wanted voicemail –Case study conducted 10% of resident community was out dated before system selection process was complete –Create extensive census and keep it updated Lessons Learned: Listening to Residents

11. Had Big Ideas of VoIP System Usage Quick keys for services (Dining, Transportation, etc.) –Did not fit our staffing model –Handsets too complicated and expensive –Short life cycle –Residents wanted multiple handsets and selection choices –Alternate hardware/delivery systems are better suited WiFi based communication for Service Teams –Hardware issues –VoIP app clunky, slow Lessons Learned: Choosing Solutions that FIT

12. New Residents- Complementary 2 hrs of IT support first 30 days  Pre- move technology intake  Setup and configuration upon move in  30 day follow up test & tune Complementary 1 hr of IT support/year $50/hr beyond Resident IT Group, Ongoing “tech nights” Creating Resident Services Portfolio Technology Services Model

13. Principles rather than B&W rules Make the choices explicit. If the community wants an FTE IT support, what will we give up to have this in place? Or how much are residents willing to pay to have this service? Should the whole community subsidize or have residents pay individually? Each year IT reassesses what IT equipment we support Note: Review of current resident equipment found 10% would not be supported today Need point person who owns this (not the maintenance guy who is “good with computers”) Survey tech usage every year to stay on top of trends Creating Resident Services Portfolio Technology Services Model

14. Creating Resident Services Portfolio How far can we go?

15. Managing the Project Scope Guiding Principles –Maintaining focus- What is Mission Critical? What can be delayed? –Campus wide Card Key access –Extensive CCTV placement –Extensive Digital Signage placement Risk Tolerance –Fire suppression- IT Room –Redundancy/back up systems Concluding thoughts…

16. Q&A