1 / 31

Infor EAM for the CERN Conference Rooms Service

Thomas Baron CERN Infor EAM User Meeting 26 June 2013. Infor EAM for the CERN Conference Rooms Service. Why Infor EAM ? Conception and Deployment Operation Integrations and Reporting What’s next ?. Conference Rooms Service. Conference Rooms Service. Born in Q4 2011 Activities

viveca
Télécharger la présentation

Infor EAM for the CERN Conference Rooms Service

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Thomas Baron CERN Infor EAM User Meeting 26 June 2013 Infor EAM for the CERN Conference Rooms Service

  2. Why Infor EAM ? Conception and Deployment Operation Integrations and Reporting What’s next ?

  3. ConferenceRooms Service

  4. Conference Rooms Service • Born in Q4 2011 • Activities • Equipment standardisation • Meeting room A/V design • Meeting room installation coordination • Equipment monitoring • Preventive maintenance • Corrective maintenance and Technical support • User support

  5. Conference Rooms Service • Service coverage • Staffing: • 2 staff • Outsourced team of 2 for the direct user support

  6. WhyInfor ? Need an inventory Need to tracklocation and move of equipment Need to store/archive equipmentrelated documents Need to easilytrack and plan investment Need to keeptrack of maintenance Need to organise preventive maintenance Need to centralise this information in order to easilyintegratewithothertools Startingfromsharepointlists… …thenheard about Infor EAM

  7. Conception • Timeline • First contact with GS (David and Tahar: Jan 2012) • Test area: Jan 2012 • Production: April 2012

  8. Conception • Lot of workwithInfor support (Tahar) • Data structure • Positions • Assets • Custom attributes • Parts • Stores • Regular/preventive maintenance • Conception of stickers and selection of tools

  9. Conception • Selected Tools • Sticker printer • Brady BBP11 300dpi; ribbon 65mm • LabelMark 5 software • Barcode scanner • CS-3070 ; blutooth and USB • iPad

  10. Conception Organicgrowth, not everythingwasdesignedfrom the beginning New use cases arise with production

  11. Deployment • Initial data input • Fromsharepointlistsusing the Infor EAM Upload Utility • Only for VC devices, PCs • Thenmanually • «Tour des salles», inventory and manual ingest • From April 2012 to April 2013

  12. Deployment • User Training • Service managers and technicians • By GS from April to July 2012 • Lots of face to face sessions • Sometimes the trainer is as lost as the student…

  13. Deployment Documentation in internal wiki

  14. Operation: Use Cases • New rooms (web interface) • Equipment order • Reception and information collection • Creation of room and positions • Creation of assets and link to positions • Often use «Copy record» • Edition, printing and sticking of barcode labels • Workorder (DE - Design) • Archive plans and all documents in EDMS

  15. Operation: Use Cases • Room upgrades • Reception of new equipment • Registration in Infor in a dedicated store • Replacement of oldasset • Workorder (CA - Correctif Amélioration) • Corrective maintenance • Repair and replacement of faultyequipment • Workorder (CD – Correctif Dépannage)

  16. Operation: Use Cases • Preventive maintenance • Projectorlamphoursexceeded • Workorder (PC – Préventif conditionnel) • Not yetregular maintenance

  17. Operation: Stock Management • List of parts • Tracked by asset • PCs • projectors • Or not • Lamps • Batteries • Splitters • Used in WOs • Regularlychecked and ordered

  18. Operation: Some Figures • Structure • 1038 positions • 881 assets • 142 parts • 5 stores • Work • 233 WOs

  19. Reporting • InforEAMintegratedreporting a bit clumsy • Need for a dashboard-style reporting for users and managers • Integration in a drupal module using • Direct Oracle queries • Python and Google charts

  20. Reporting

  21. Integration • Using the equipment data in other service related applications • In order to have a single source of information; master repository • Using SQL queries

  22. Integration: RAVEM RAVEM (Room AV Equipment Manager)

  23. Integration: Room Control App

  24. General comments (issues) • The standard interface isoverlycomplex and lacks good user guide whichwouldgive an overview on the concepts and philosophy • The support team should setup a FAQ or dedicated guide for userswithspecific CERN use cases. • A lot of issues with the standard web interface • The standard interface worksonly on IE !!! • One can open only one windowat a time !!! • Sometimeyoustart a searchwhichtakesages and blocks the whole interface. That’sespeciallywhen in the exploratory phase. • Asset/position numberingisclumsy for the user (shouldbeautomated) • EDMS integration

  25. General comments (positive) Very flexible Adapts to all use cases Excellent EAM light interface Strong support Good codification guidance Could not do withoutit

  26. Whatcould have been donebetter • Better configuration of the operators web interface (simplification) • Managers should have the possibility to do thatthemselves • Integration to Room Control App ? • Fullydedicated AV input interface

  27. What’sNext ? • Still a long way to go! • Using the regular/preventive maintenance module • Alreadyconfigured • Regular «tour des salles» with checklist • Betterreporting • Investmenttracking/profiling • Better tickets analysis • Extend the use to other collaboration services • Public Information Screens • Webcast • IntegrationwithSNow

  28. Conference Rooms Service • info • http://cern.ch/conference-rooms • status page • http://avc-dashboard.web.cern.ch/Conference%20rooms • contact • conferencerooms-support@cern.ch

  29. Thank you for your attention Contact me: Thomas Baron (IT-CIS-AVC) Thomas.baron@cern.ch

More Related