The ITAM industry has become more application-specific within the last decade. Beginning as a broad solution, IT Services Management had initially encompassed IT Asset Management as a practice and as a market. ITAM became a standalone market once there was enough critical mass to the market and application that it could be recognized that a select handful of major players were providing single solutions for IT hardware/software management. As ITAM has grown and matured, product offerings have become focused by vertical, asset type, workflow type, and whether the product is on premise, SaaS, or hybrid.
Further specialization is, of course, trending in the future, but once this reaches a certain maturity and the next generation platform begins to disrupt the current one, the entire structure and business practice will change drastically. Whether APIs and SaaS will be as prevalent as they are now may be entirely questioned, which may demand that applications either connect to the new platform if able or become obsolete.
So where does this put Oomnitza? If we hypothesize that APIs and cloud computing will maintain its footprint for at least the next decade, the basis of Oomnitza’s value proposition will be largely solid, and continued growth would theoretically be supported. In a more functional sense, Oomnitza is constructed to be flexible, and customize-able, with the full intention of adapting to the next platform of technology.
There are a few distinct examples of how Oomnitza targets adapting to leading technology development. Sub-platforms constructed around team collaboration software, business management programs, and communication are prime examples of tools to synergize with. Hence, in collaboration, Jira is directly integrated with Oomnitza, so that asset-related tasks can be communicated directly to the project management platform. For business management, Jasper is an IoT connectivity management platform that links to Oomnitza, in order to consolidate the collection of assets. Google apps and Slack are integrated with Oomnitza in order to relate correspondence within a team or company to the lifecycle of assets. These are just a few examples of how Oomnitza builds for the future. If you have any new integrations you think are important, please email firstname.lastname@example.org