Software as a Service SaaS - Revision history

Designing Buildings at 10:06, 3 August 2022

2022-08-03T10:06:59Z

← Older revision		Revision as of 10:06, 3 August 2022
Line 69:		Line 69:
	* Work order management system.		* Work order management system.

−	[[Category:DCN_Definition]] [[Category:DCN_Software]] [[Category:Definitions]] [[Category:Roles_/_services]]	+	[[Category:DCN_Definition]] [[Category:DCN_Software]] [[Category:Definitions]] [[Category:Operations]] [[Category:Roles_/_services]]

Editor at 18:38, 23 December 2021

2021-12-23T18:38:47Z

Editor at 19:21, 20 December 2021

2021-12-20T19:21:50Z

← Older revision		Revision as of 19:21, 20 December 2021
Line 60:		Line 60:
	* Enterprise resource planning ERP.		* Enterprise resource planning ERP.
	* Facilities management.		* Facilities management.
		+	* Light as a Service LaaS.
	* Maintenance.		* Maintenance.
	* Maintenance and operational strategy.		* Maintenance and operational strategy.

Editor at 18:53, 1 November 2021

2021-11-01T18:53:04Z

← Older revision		Revision as of 18:53, 1 November 2021
Line 51:		Line 51:
	The use of a Service Level Agreement (SLA) may also impede the success of the Software as a Service approach. While an SLA is traditionally associated with product delivery, this type of contractual infrastructure can also be applied to the Software as a Service delivery method. The goal of the SLA is to set realistic expectations for both the service provider and the customer, however, this is a relatively new method of conducting business, which means it may be difficult to determine accurate parameters for the delivery of the service despite the need.		The use of a Service Level Agreement (SLA) may also impede the success of the Software as a Service approach. While an SLA is traditionally associated with product delivery, this type of contractual infrastructure can also be applied to the Software as a Service delivery method. The goal of the SLA is to set realistic expectations for both the service provider and the customer, however, this is a relatively new method of conducting business, which means it may be difficult to determine accurate parameters for the delivery of the service despite the need.

−	= Related articles on Designing Buildings ~~Wiki~~ =	+	= Related articles on Designing Buildings =

	* Computer aided facilities management.		* Computer aided facilities management.
Line 63:		Line 63:
	* Maintenance and operational strategy.		* Maintenance and operational strategy.
	* Property management.		* Property management.
		+	* Safety as a Service.
	* Service level agreement SLA		* Service level agreement SLA
	* Work order management system.		* Work order management system.

	[[Category:DCN_Definition]] [[Category:DCN_Software]] [[Category:Definitions]] [[Category:Roles_/_services]]		[[Category:DCN_Definition]] [[Category:DCN_Software]] [[Category:Definitions]] [[Category:Roles_/_services]]

Editor at 15:08, 6 September 2021

2021-09-06T15:08:20Z

← Older revision		Revision as of 15:08, 6 September 2021
Line 56:		Line 56:
	* Computerised managed maintenance system CMMS		* Computerised managed maintenance system CMMS
	* Construction project management software.		* Construction project management software.
		+	* Drones as a Service DaaS.
	* Enterprise asset management.		* Enterprise asset management.
	* Enterprise resource planning ERP.		* Enterprise resource planning ERP.

Designing Buildings: Reverted edits by 103.92.202.139 (talk) to last revision by Editor

2021-08-22T15:07:57Z

Reverted edits by 103.92.202.139 (talk) to last revision by Editor

← Older revision		Revision as of 15:07, 22 August 2021
Line 45:		Line 45:
	* Requirements and consequences associated with maintenance and training.		* Requirements and consequences associated with maintenance and training.

−	Another risk associated with Software as a Service is the dependence on a ~~[https://saaspirate.com/~~ single vendor]. This presents a problem if the vendor goes out of business but still holds the organisation’s data (which becomes even more complicated when the customer needs to retrieve data from a system that is no longer supported - or even operating).	+	Another risk associated with Software as a Service is the dependence on a single vendor. This presents a problem if the vendor goes out of business but still holds the organisation’s data (which becomes even more complicated when the customer needs to retrieve data from a system that is no longer supported - or even operating).

	One way to protect against data loss is to adopt the process of Software as a Service data escrow. This option backs up data with a third party that is not affiliated with the Software as a Service provider.		One way to protect against data loss is to adopt the process of Software as a Service data escrow. This option backs up data with a third party that is not affiliated with the Software as a Service provider.

103.92.202.139 at 13:12, 22 August 2021

2021-08-22T13:12:02Z

← Older revision		Revision as of 13:12, 22 August 2021
Line 45:		Line 45:
	* Requirements and consequences associated with maintenance and training.		* Requirements and consequences associated with maintenance and training.

−	Another risk associated with Software as a Service is the dependence on a single vendor. This presents a problem if the vendor goes out of business but still holds the organisation’s data (which becomes even more complicated when the customer needs to retrieve data from a system that is no longer supported - or even operating).	+	Another risk associated with Software as a Service is the dependence on a [https://saaspirate.com/ single vendor]. This presents a problem if the vendor goes out of business but still holds the organisation’s data (which becomes even more complicated when the customer needs to retrieve data from a system that is no longer supported - or even operating).

	One way to protect against data loss is to adopt the process of Software as a Service data escrow. This option backs up data with a third party that is not affiliated with the Software as a Service provider.		One way to protect against data loss is to adopt the process of Software as a Service data escrow. This option backs up data with a third party that is not affiliated with the Software as a Service provider.

Editor at 19:27, 16 March 2021

2021-03-16T19:27:58Z

← Older revision		Revision as of 19:27, 16 March 2021
Line 57:		Line 57:
	* Construction project management software.		* Construction project management software.
	* Enterprise asset management.		* Enterprise asset management.
		+	* Enterprise resource planning ERP.
	* Facilities management.		* Facilities management.
	* Maintenance.		* Maintenance.

Editor at 16:31, 7 October 2020

2020-10-07T16:31:09Z

← Older revision		Revision as of 16:31, 7 October 2020
Line 55:		Line 55:
	* Computer aided facilities management.		* Computer aided facilities management.
	* Computerised managed maintenance system CMMS		* Computerised managed maintenance system CMMS
		+	* Construction project management software.
	* Enterprise asset management.		* Enterprise asset management.
	* Facilities management.		* Facilities management.
Line 63:		Line 64:
	* Work order management system.		* Work order management system.

−	[[Category:~~Definitions~~]] [[Category:~~DCN_Definition~~]] [[Category:Roles_/_services]]	+	[[Category:DCN_Definition]] [[Category:DCN_Software]] [[Category:Definitions]] [[Category:Roles_/_services]]

Designing Buildings at 06:35, 16 June 2020

2020-06-16T06:35:21Z

← Older revision		Revision as of 18:38, 23 December 2021
Line 3:		Line 3:
	= Introduction =		= Introduction =

−	Software as a Service (SaaS) is a cloud-based approach to technology that allows clients to purchase certain types of software on a subscription basis. Since the arrangement is cloud-based, clients can access the service anywhere, as long as they have a valid ~~license~~ and access to the Internet.	+	Software as a Service (SaaS) is a cloud-based approach to technology that allows clients to purchase certain types of software on a subscription basis. Since the arrangement is cloud based, clients can access the service anywhere, as long as they have a valid licence and access to the Internet.

−	Using the ~~Software as a Service~~ approach typically involves paying a monthly per user fee for a ~~license~~. The software vendor hosts the software, and users generally access it through the Internet with a web browser.	+	Using the SaaS approach typically involves paying a monthly per user fee for a licence. The software vendor hosts the software, and users generally access it through the Internet with a web browser.

−	Open SaaS is a variation of ~~Software as a Service (~~SaaS), that uses open source, rather than proprietary software. Open SaaS is generally also web-based, with users collaborating to its development~~, however~~, a single primary service provider manages official product upgrades.	+	Open SaaS is a variation of SaaS that uses open source, rather than proprietary software. Open SaaS is generally also web-based, with users collaborating on its development. However, a single primary service provider manages official product upgrades.

	= History =		= History =
Line 13:		Line 13:
	In the 1960s, it was unusual for businesses to own and operate their own computers. The hardware and software were expensive, and for small to medium sized businesses, owning a computer was not practical.		In the 1960s, it was unusual for businesses to own and operate their own computers. The hardware and software were expensive, and for small to medium sized businesses, owning a computer was not practical.

−	However, some organisations found they could tap into the power of computers by using a method referred to as time sharing. This became one of the primary methods of computing in the 1970s. Conceptually, it was very similar to ~~Software as a Service~~ (which wouldn't be available for several decades).	+	However, some organisations found they could tap into the power of computers by using a method referred to as time sharing. This became one of the primary methods of computing in the 1970s. Conceptually, it was very similar to SaaS (which wouldn't be available for several decades).

	As computers became less expensive, businesses could afford to purchase them, and eventually, desktop personal computers became more common.		As computers became less expensive, businesses could afford to purchase them, and eventually, desktop personal computers became more common.
Line 21:		Line 21:
	= SaaS for facility management =		= SaaS for facility management =

−	Since about 2015, there has been a significant move to cloud-based computing for many facilities and building management processes, and ~~Software as a Service~~ has been gaining market share. Many offerings are available for tablets or mobile devices, which makes them suitable for onsite use. As a result, Software as a Service has become a more common delivery model for computer aided design (CAD), building information modelling (BIM), collaboration tools, project management, construction management, enterprise resource planning (ERP) and work order management.	+	Since about 2015, there has been a significant move to cloud-based computing for many facilities and building management processes, and SaaS has been gaining market share. Many offerings are available for tablets or mobile devices, which makes them suitable for onsite use. As a result, Software as a Service has become a more common delivery model for computer aided design (CAD), building information modelling (BIM), collaboration tools, project management, construction management, enterprise resource planning (ERP) and work order management.

−	For facility management departments,~~Software as a Service~~ can be helpful when users do not have extensive technical knowledge of IT systems as an external vendor is in charge of the technical aspects. Facility managers can often request customisation that is tailored to their needs, meaning they pay only for the services that are required, rather than paying for a full software package.	+	For facility management departments, SaaS can be helpful when users do not have extensive technical knowledge of IT systems as an external vendor is in charge of the technical aspects. Facility managers can often request customisation that is tailored to their needs, meaning they pay only for the services that are required, rather than paying for a full software package.

	Additional features of SaaS for facility management include:		Additional features of SaaS for facility management include:
Line 35:		Line 35:
	= Position in the market =		= Position in the market =

−	Despite its flexibility, ~~Software as a Service~~ is still lagging in terms of adoption. In facilities management and other areas, the great majority of software sold still remains locally-based.	+	Despite its flexibility, SaaS is still lagging in terms of adoption. In facilities management and other areas, the great majority of software sold still remains locally based.

−	There are a number of factors that may be responsible for the slow acceptance of ~~Software as a Service~~:	+	There are a number of factors that may be responsible for the slow acceptance of SaaS:

	* Connectivity issues (including lagging delivery) due to power failures or Internet outages.		* Connectivity issues (including lagging delivery) due to power failures or Internet outages.
	* Security of data (particularly as it relates to data protection regulations) and vulnerability due to possible breaches.		* Security of data (particularly as it relates to data protection regulations) and vulnerability due to possible breaches.
−	* Problems with ~~licenses~~ and compliance (particularly if users are not authorised to access copies of the software).	+	* Problems with licences and compliance (particularly if users are not authorised to access copies of the software).
	* Reluctance to adopt updates and upgrades based on vendor's timetables (not based on the user’s willingness or ability to accommodate the change).		* Reluctance to adopt updates and upgrades based on vendor's timetables (not based on the user’s willingness or ability to accommodate the change).
	* Requirements and consequences associated with maintenance and training.		* Requirements and consequences associated with maintenance and training.

−	Another risk associated with ~~Software as a Service~~ is the dependence on a single vendor. This presents a problem if the vendor goes out of business but still holds the organisation’s data (which becomes even more complicated when the customer needs to retrieve data from a system that is no longer supported - or even operating).	+	Another risk associated with SaaS is the dependence on a single vendor. This presents a problem if the vendor goes out of business but still holds the organisation’s data (which becomes even more complicated when the customer needs to retrieve data from a system that is no longer supported - or even operating).

−	One way to protect against data loss is to adopt the process of ~~Software as a Service~~ data escrow. This option backs up data with a third party that is not affiliated with the Software as a Service provider.	+	One way to protect against data loss is to adopt the process of SaaS data escrow. This option backs up data with a third party that is not affiliated with the Software as a Service provider.

−	The use of a Service Level Agreement (SLA) may also impede the success of the ~~Software as a Service~~ approach. While an SLA is traditionally associated with product delivery, this type of contractual infrastructure can also be applied to the ~~Software as a Service~~ delivery method. The goal of the SLA is to set realistic expectations for both the service provider and the customer, however, this is a relatively new method of conducting business, which means it may be difficult to determine accurate parameters for the delivery of the service despite the need.	+	The use of a Service Level Agreement (SLA) may also impede the success of the SaaS approach. While an SLA is traditionally associated with product delivery, this type of contractual infrastructure can also be applied to the SaaS delivery method. The goal of the SLA is to set realistic expectations for both the service provider and the customer, however, this is a relatively new method of conducting business, which means it may be difficult to determine accurate parameters for the delivery of the service despite the need.

	= Related articles on Designing Buildings =		= Related articles on Designing Buildings =
Line 63:		Line 63:
	* Maintenance.		* Maintenance.
	* Maintenance and operational strategy.		* Maintenance and operational strategy.
		+	* Products as a Service PaaS.
	* Property management.		* Property management.
	* Safety as a Service.		* Safety as a Service.

← Older revision		Revision as of 06:35, 16 June 2020
Line 35:		Line 35:
	= Position in the market =		= Position in the market =

−	Despite its flexibility, Software as a Service is still lagging in terms of adoption. In facilities management and other ~~business sectors~~, the great majority of software sold still remains ~~server~~-based.	+	Despite its flexibility, Software as a Service is still lagging in terms of adoption. In facilities management and other areas, the great majority of software sold still remains locally-based.

−	~~These~~ factors may be responsible for the slow acceptance of Software as a Service:	+	There are a number of factors that may be responsible for the slow acceptance of Software as a Service:

	* Connectivity issues (including lagging delivery) due to power failures or Internet outages.		* Connectivity issues (including lagging delivery) due to power failures or Internet outages.
−	* Security of data (particularly as it relates to data ~~governance~~ regulations) and vulnerability ~~(despite vendor promises and SLAs)~~ due to possible breaches.	+	* Security of data (particularly as it relates to data protection regulations) and vulnerability due to possible breaches.
	* Problems with licenses and compliance (particularly if users are not authorised to access copies of the software).		* Problems with licenses and compliance (particularly if users are not authorised to access copies of the software).
−	* Reluctance to adopt updates and upgrades based on vendor's ~~timetable~~ (not based on the user’s willingness or ability to accommodate the change).	+	* Reluctance to adopt updates and upgrades based on vendor's timetables (not based on the user’s willingness or ability to accommodate the change).
	* Requirements and consequences associated with maintenance and training.		* Requirements and consequences associated with maintenance and training.

−	Another risk associated with Software as a Service is the dependence on a single vendor. This presents a problem if the vendor goes out of business but still holds ~~onto~~ the organisation’s data (which becomes even more complicated when the ~~facility manager~~ needs to retrieve data from a system that is no longer supported - or even operating).	+	Another risk associated with Software as a Service is the dependence on a single vendor. This presents a problem if the vendor goes out of business but still holds the organisation’s data (which becomes even more complicated when the customer needs to retrieve data from a system that is no longer supported - or even operating).

	One way to protect against data loss is to adopt the process of Software as a Service data escrow. This option backs up data with a third party that is not affiliated with the Software as a Service provider.		One way to protect against data loss is to adopt the process of Software as a Service data escrow. This option backs up data with a third party that is not affiliated with the Software as a Service provider.

−	The use of a Service Level Agreement (SLA) may also impede the success of the Software as a Service approach. While an SLA is traditionally associated with product delivery, this type of contractual infrastructure can also be applied to the Software as a Service delivery method.	+	The use of a Service Level Agreement (SLA) may also impede the success of the Software as a Service approach. While an SLA is traditionally associated with product delivery, this type of contractual infrastructure can also be applied to the Software as a Service delivery method. The goal of the SLA is to set realistic expectations for both the service provider and the customer, however, this is a relatively new method of conducting business, which means it may be difficult to determine accurate parameters for the delivery of the service despite the need.
−		+
−	The goal of the SLA is to set realistic expectations for both the service provider and the ~~facility manager~~, however, this is a relatively new method of conducting business, which means it may be difficult to determine accurate parameters for the delivery of the service despite the need.	+

	= Related articles on Designing Buildings Wiki =		= Related articles on Designing Buildings Wiki =
Line 65:		Line 63:
	* Work order management system.		* Work order management system.

−	[[Category:Definitions]] [[Category:Roles_/_services]]	+	[[Category:Definitions]] [[Category:DCN_Definition]] [[Category:Roles_/_services]]