Enterprise systems are complex:
ERP systems are often of a broad functional scope and with lots of back-end integrations, and will thus adopt SaaS later than other software category; and
Examples seen so far cover a single process or module (e.g., payroll, SFA, transportation rates, etc.), not whole suites with all integrations needed.
Several of IFS focused verticals such as Aviation & Defense (A&D) and Utilities, have security restrictions limiting the possibilities to run externally managed applications.
However, IFS does see an interest for "intranet/extranet SaaS" where a configured and integrated application is delivered as a service by a central information technology (IT) organization to other departments, suppliers, and contractors in the supply chain. An example could be Lockheed Martin (LM) delivering an enterprise asset maintenance (EAM) solution as a service to LM itself, LM subcontractors, the United States Department of Defense (DoD), and other parties involved in performing maintenance.
In this respect, the upcoming Aurora UI, which we will be described in a separate blog post, is important, as it is possible to be delivered as a service over the inter-/intra-/extranet using web deployment and standard internet protocols. This should enable some on-demand delivery of IFS Applications though existing infrastructure.