Crown Melbourne's Maintenance Management System Implementation FMA Maintenance Workshop 12th July 2013 Demara Jackson – General Manager Property Services
Crown Melbourne MMS Implementation Property Features 13 Bars and Nightclubs 1600 Hotel Rooms 38 Restaurants 2 World Class Spas Gaming and VIP Gaming 28 Shopping Outlets
Crown Melbourne MMS Implementation Property Infrastructure 900 electrical boards 130 lifts & escalators 229 air-conditioning pumps and 31 boilers 2900 air conditioning units 8 cogengenerators 27 air conditioningwater chillers
Crown Melbourne MMS Implementation Current Systems • Duplication • Customer experience • Cost control • Inventory Control • Labor utilisation • Asset maintenance costs • Work order management • Mobile – Wi Fi • Bespoke 4
Crown Melbourne MMS Implementation Project control • Get the Scope right early • Business representatives – Pull key individuals out of the business during the scoping phase. Backfill their roles and ensure they are part of the design and test team. • “Vanilla” requirements – Ensure your scope is not prescriptive. Standard configurations will likely fulfil your business requirements without customization Market review Finance approval Scope Tender Design, Build, Test, Go-Live Getting the scope fully documented gets the rest of the project on a good start
Crown Melbourne MMS Implementation Project control Steering Committee Project Sponsor IT Sponsor Vendor sponsor Project Manager Vendor Team Business Team Operations End Users Finance Integration Team Project Team Changeover ofproject team members during the project was a high risk to the project. Risk mitigation should have been much more strict.
Crown Melbourne MMS Implementation Project control Project Governance A signed project charter, executive steering committee, and Business resources are the key to eliminate scope changes. • Project Charter • Scope • Cost • Timeline • Signatures • Accountability • Operations • Finance • End Users
Crown Melbourne MMS Implementation Project Control Gated Project management process • Major project spend • Long development time • Enabled controlled spend when design to be delivered by the vendor
Crown Melbourne EAM Implementation AS IS • Process time requirements should be identified in scope. User expectations are that the new system will be the same or faster. Not achieving this will hamper user acceptance. • Processor speed of mobile devices is critical for some applications
Crown Melbourne EAM Implementation • Constraints • ERP Integration – • All financials needed to be fully integrated with Crown’s ERP Biztalk (ESB) Enterprise Service Bus Peoplesoft ERP Maximo EAM Roster Scheduling Fully understand the limitations of the other systems to be integrated
Crown Melbourne EAM Implementation Constraints • Mobile – Crown currently had a mobile solution Screen shot Old mobile devices WIFI – Store forward New mobile devices WIFI+3G – Always connected upgrade • Identify basic requirements around mobile screen usability and layouts. • Ensure connectivity for any Web based applications.
Crown Melbourne MMS Implementation TO BE - Maintenance
Crown Melbourne MMS Implementation The Outcome • Key requirements achieved • Project on time and within 1% of budget • No business interruption • Core system delivering requirements • Real time data for the first time • Cost recovery uplift that was totally un-forecast • Key issues being addressed • Some handheld devices have required replacement to enable outcomes • Work still required on some of the business process changes that had unintended consequences due to integrated system – high volume, low value work orders