IAB Interactive Standardized Equipment List   return to main tree

Search Interactive SEL:



SEL Number: 04AP-11-SAAS
Title: Applications, Software as a Service


Last Updated: 8/20/2021 11:16:13 AM

Previous SEL Number: 04AP-11-SAAS

Description: Sometimes referred to as "on-demand software", SAAS applications run on the provider's servers, delivering functionality via the internet to any device having connectivity and the required browser or interface. Access to the application is obtained via a service subscription rather than outright purchase, with all updates and configuration requirements handled by the service provider. Some example SAAS applications include equipment tracking and maintenance, intra-application communication among client devices, and specialized software such as plume modeling. Note that purchasers of SAAS should consider the security aspects of the planned usage, particularly availability and the protection of sensitive information stored remotely. Internet connectivity is required to utilize SAAS applications unless specific failover measures such as a "hybrid cloud" are available. In addition, data is stored remotely on vendor equipment. Use of SAAS for mission critical applications should be thoroughly vetted before implementation.

ImportantFeatures: Generally available by monthly or annual subscription.
May execute on a variety of portable and mobile platforms, including notebooks, pads, and smart phones.
May allow real-time scalability (users, functions) with automatic corresponding changes in billing rates


Operating Considerations: Consider contingency planning for loss of Internet connectivity or a provider service outage. Risk assessment may dictate that some applications are too critical to be cloud-based unless local backup or alternate functionality exists.
Consider client-side requirements. Is the application browser based? If so, is it compatible with existing browsers (Explorer, Safari, Chrome, Edge, Firefox, etc.)? If client software is required, what hardware/operating system is needed.
Consider operating environment and ability to access the application, including factors such as RF interference, touch screen requirements (particularly in PPE), and weather conditions.
Consider contractual obligations such as term of contract and termination fees, as well as ownership of data and liability for data loss.
Consider access control and security. Determine the number of users who require access and avoid sharing any common passwords.


Training Requirements: Varies with complexity of application and provider's training program.
Initial Training: Minimal (<1 day)
Sustainment Training: None


Mandatory Standards:

Applicable Standards and References:

MSSL:
  • HazMat: Response Team
  • Preventive Rad/Nuc Detection
  • Medical Point of Dispensing
  • Basic Life Support
  • Advanced Life Support
  • Pre-Hospital
  • Hospital
  • Public Health