{"id":4779,"date":"2018-06-27T02:45:29","date_gmt":"2018-06-27T09:45:29","guid":{"rendered":"https:\/\/www.connixt.com\/5-ways-to-handle-eam-upgrade-vs-doing-something-now\/"},"modified":"2023-11-19T10:56:48","modified_gmt":"2023-11-19T18:56:48","slug":"5-ways-to-handle-eam-upgrade-vs-doing-something-now","status":"publish","type":"post","link":"https:\/\/www.connixt.com\/5-ways-to-handle-eam-upgrade-vs-doing-something-now\/","title":{"rendered":"5 Ways to Handle EAM Upgrade vs. Doing Something Now"},"content":{"rendered":"

\u201cThis makes sense\u201d.<\/em><\/p>\n

<\/p>\n

That is the consistent message from transit agencies at conferences and in one-on-one discussions about using mobile apps to digitize and automate SGR and maintenance inspections, inventorying, facilities condition assessment, and reporting.\u00a0 Business users \u2013 including,\u00a0 technicians and mechanics \u2013 see\u00a0 immediate value in eliminating paper, manual data entry, filing, and the grunt work involved in collating data to generate mandatory reports and more.<\/p>\n

Although the need for an EAM upgrade is commonly acknowledged, the \u201cwe need to wait\u201d mentality is quick on the heels of the acknowledgement.\u00a0\u00a0 In the past, the justification for this \u201clet\u2019s wait\u201d approach was based on the time, resources, and budget it takes to upgrade or migrate the back-end system.\u00a0 This often leads to a situation where the business users need something now that they see as a substantial win vs the IT need to first evaluate and implement an enterprise system.<\/p>\n

Times and technology have changed, and it doesn\u2019t have to be an either-or dilemma.\u00a0 Transit agencies and utilities are seeing substantial wins from immediate deployment of mobile tech while planning on their larger scale EAM deployment.<\/p>\n

\n

A large Metro and Connixt <\/strong><\/em>customer<\/em><\/a> reports 20% savings in labor-hours in the first few months of implementing iMarq, the Connixt cloud-mobile system.\u00a0 The payback is obvious.<\/em><\/strong><\/h4>\n<\/div>\n
\n

Here are 5 reasons why:<\/p>\n

    \n
  1. Quick wins are possible on the front-end<\/strong><\/li>\n<\/ol>\n

    Front-end technicians and mechanics can use mobile apps to run much of their daily work.\u00a0 Cloud-mobile technology makes deployment possible within weeks rather than the months or years it takes for large scale EAM deployments.\u00a0 Those months and years don\u2019t have to be a dead-zone of no change and no gains.<\/p>\n

      \n
    1. Integration is not the challenge it used to be<\/strong><\/li>\n<\/ol>\n
      Cloud-mobile technology like iMarq is system-agnostic; it is not hard-coded integration to a single EAM, rather its open enterprise architecture allows seamless integration with whatever back-end system is deployed.\u00a0 IT is correct to point out that this is not \u201ceasy\u201d, but it is certainly not the challenge it used to be.\u00a0 Most new EAM systems come with standard web-services, APIs, or middle-ware that make this integration far easier than it ever was.<\/div>\n
      \n

      One CIO likens mobile apps to the gun-sights that make the big-guns (EAM deployments) effective.<\/strong><\/em><\/h4>\n<\/div>\n
      \n
        \n
      1. Low tech deployment today<\/strong><\/li>\n<\/ol>\n

        Immediate deployment can be with the existing legacy system or managed from the cloud entirely with CSV files or other formats provided for the back-end.\u00a0 Either way deployment is quick, with low IT overheads.\u00a0 Once the new system is ready, the integration switches to the new environment seamlessly with no front-end impact.\u00a0 There are two great benefits that come from this (see 4 and 5 below).<\/p>\n

          \n
        1. Change management is minimized with a mobile front end<\/strong><\/li>\n<\/ol>\n

          Technology is only half the challenge (or less) for successful deployment; the rest of it is always user adoption.\u00a0 Users on a mobile system are already used to digitized and automated processes with their mobile apps.\u00a0 They see no change to their front-end \u2013 no matter what has happened on the back-end \u2013 because any switching takes place in the IT realm.\u00a0 With no changes to their front-end experience, end-users see no change in their work or processes.\u00a0 That means there is no learning curve to use it or resistance to change.<\/p>\n

            \n
          1. Fine-tune and digitize processes \u2013 get them system-ready<\/strong><\/li>\n<\/ol>\n

            Whatever the back-end system is\u2013 legacy, new, old, home-grown, green-screen \u2013 front-end mobility can be deployed today to make end-user life easier, more productive and highly efficient.\u00a0 Digitizing processes allows those processes to be fine-tuned, as well as re-designed forms, and faster approvals, with no impact on the back-end system.\u00a0 All of this goes toward making the final EAM deployment that much more productive.<\/p>\n

            Mobile technology deployments can deliver immediate productivity gains and large-scale EAM deployments don\u2019t have to delay these gains.\u00a0 Don\u2019t limit your choice of mobile technology.<\/u><\/em><\/p>\n

            Connixt digitizes and automates maintenance, inspection, inventorying and condition assessment processes for large<\/a> and small transit agencies<\/a> and utilities<\/a>.<\/p>\n

            Find out more <\/a>\u00a0about how Connixt customers show 20% labor-hour gains while waiting on their EAM upgrades\/migration and contact us<\/a> today.<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

            Cloud-mobile technology like iMarq is system-agnostic; it is not hard-coded integration to a single EAM, rather its open enterprise architecture allows seamless integration with whatever back-end system is deployed.<\/p>\n","protected":false},"author":2,"featured_media":4611,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[309,321],"tags":[82,106,146,130,38,104,147,152,150],"_links":{"self":[{"href":"https:\/\/www.connixt.com\/wp-json\/wp\/v2\/posts\/4779"}],"collection":[{"href":"https:\/\/www.connixt.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.connixt.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.connixt.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.connixt.com\/wp-json\/wp\/v2\/comments?post=4779"}],"version-history":[{"count":2,"href":"https:\/\/www.connixt.com\/wp-json\/wp\/v2\/posts\/4779\/revisions"}],"predecessor-version":[{"id":5641,"href":"https:\/\/www.connixt.com\/wp-json\/wp\/v2\/posts\/4779\/revisions\/5641"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.connixt.com\/wp-json\/wp\/v2\/media\/4611"}],"wp:attachment":[{"href":"https:\/\/www.connixt.com\/wp-json\/wp\/v2\/media?parent=4779"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.connixt.com\/wp-json\/wp\/v2\/categories?post=4779"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.connixt.com\/wp-json\/wp\/v2\/tags?post=4779"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}