Skip to content
Tiatra, LLCTiatra, LLC
Tiatra, LLC
Information Technology Solutions for Washington, DC Government Agencies
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact
 
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact

XaaS isn’t everything — and it isn’t serviceable

XaaS is, regrettably, defined as, “any computing service that is delivered via the internet and paid for in a flexible consumption model rather than as an upfront purchase or license.”

Do some Googling about XaaS and you’ll find much repetitive gushing, but for the more jaundiced among us, it’s hard to avoid concluding that XaaS is, in fact, little more than the intersection of cloud-based computing and charge-backs.

And yet in all of the discussion, that XaaS is the logical outcome of services-oriented architecture (SOA) seems to have been ignored.

Also strange is that XaaS excludes the part of “everything” that the uninitiated might think of as the most important set of services IT provides, namely, everything business analysts, IT internal consultants, and application development and support staff do for a living.

Which I guess means “Everything” as a Service is really “A Few Things as a Service” (AFTaaS), or maybe “Everything Except Effort as a Service” (EEEaaS).

What XaaS should really mean

What XaaS ought to refer to is the logical application of SOA principles to just about everything that gets done in the enterprise.

It should, for example, include what services firms call business process outsourcing (BPO). It should also include what we might dub “business process insourcing” but usually call “shared services.”

Work as a Service (WaaS), anyone?

XaaS should, that is, include not only the technology itself but also the business results the technology supports.

But not who pays, and how. Architecture is about how solutions are put together, not about financing them.

‘Work as a Service’: Shared services as architecture

Here’s the thing: BPO isn’t new, and has made paying by the drink for work an option since its inception.

And just as IT can provide SaaS to its business users either by way of commercial cloud or in-house provisioned applications, so business functions can make their services available to the rest of the business by way of organizing as in-house provisioned shared services, or through use of a BPO vendor.

But a shared services group isn’t just like a BPO only internal. The difference between them? Contracting with a BPO provider isn’t an architectural decision. Organizing as an internal shared service most assuredly is.

Like most other outsources, the decision to engage a BPO provider is usually an admission of management failure. It hands off responsibility for a business function that internal management couldn’t properly oversee to a contract.

This doesn’t always mean organizing as a collection of shared services is the right choice, though.

Among the downsides: An in-house shared-services business architecture, unlike a BPO, has, when carried to its logical conclusion a reductio ad absurdum outcome, where every business department charges every other business department for the services it provides. For example, IT might charge HR a monthly fee for use of the HRIS, while HR might reciprocate by charging IT for recruiting, benefits management, and payroll services.

Ubiquitous shared-services can turn the enterprise into a giant financial ouroboros.

Business services oriented architecture: One size fits no one

BPOs and XaaS do share a characteristic that might, in some situations, be a benefit but in most cases is a limitation, namely, the need to commoditize. This requirement isn’t a matter of IT’s preference for simplification, either. It’s driven by business architecture’s decision-makers’ preference for standardizing processes and practices across the board.

This might not seem to be an onerous choice, but it can be. Providing a service that operates the same way to all comers no matter their specific and unique needs might cut immediate costs but can be, in the long run, crippling.

Imagine, for example, that Human Resources embraces the Business Services Oriented Architecture approach, offering up Human Resources as a Service to its internal customers. As part of HRaaS it provides Recruiting as a Service (RaaS). And to make the case for this transformation it extols the virtues of process standardization to reduce costs.

Imagine, then, that you’re responsible for Store Operations for a highly seasonal retailer, one that has to ramp up its in-store staffing from Black Friday through Boxing Day. Also imagine IT needs to recruit a DBA.

I trust it’s clear the same process won’t work for both recruiting store staff by the hundreds and for hiring a single, highly specialized technical professional.

“Standardize” is easy to say but hard to make work right. And that’s before the HR manager responsible for recruiting tries to explain what they need the HRIS to do.

In this, what we might call a business-services-oriented architecture isn’t that different from adopting SOA (along with microservices, its teeny brethren), for your application architecture. In both cases, enforcing standardization on a single version is one-size-fits-no-one engineering.

IT Strategy


Read More from This Article: XaaS isn’t everything — and it isn’t serviceable
Source: News

Category: NewsJuly 28, 2022
Tags: art

Post navigation

PreviousPrevious post:Novanta CIO Sarah Betadam on the CIO-CEO relationshipNextNext post:Qu’est-ce que le leadership transformationnel? Un style de gestion pour susciter l’innovation

Related posts

Barb Wixom and MIT CISR on managing data like a product
May 30, 2025
Avery Dennison takes culture-first approach to AI transformation
May 30, 2025
The agentic AI assist Stanford University cancer care staff needed
May 30, 2025
Los desafíos de la era de la ‘IA en todas partes’, a fondo en Data & AI Summit 2025
May 30, 2025
“AI 비서가 팀 단위로 지원하는 효과”···퍼플렉시티, AI 프로젝트 10분 완성 도구 ‘랩스’ 출시
May 30, 2025
“ROI는 어디에?” AI 도입을 재고하게 만드는 실패 사례
May 30, 2025
Recent Posts
  • Barb Wixom and MIT CISR on managing data like a product
  • Avery Dennison takes culture-first approach to AI transformation
  • The agentic AI assist Stanford University cancer care staff needed
  • Los desafíos de la era de la ‘IA en todas partes’, a fondo en Data & AI Summit 2025
  • “AI 비서가 팀 단위로 지원하는 효과”···퍼플렉시티, AI 프로젝트 10분 완성 도구 ‘랩스’ 출시
Recent Comments
    Archives
    • May 2025
    • April 2025
    • March 2025
    • February 2025
    • January 2025
    • December 2024
    • November 2024
    • October 2024
    • September 2024
    • August 2024
    • July 2024
    • June 2024
    • May 2024
    • April 2024
    • March 2024
    • February 2024
    • January 2024
    • December 2023
    • November 2023
    • October 2023
    • September 2023
    • August 2023
    • July 2023
    • June 2023
    • May 2023
    • April 2023
    • March 2023
    • February 2023
    • January 2023
    • December 2022
    • November 2022
    • October 2022
    • September 2022
    • August 2022
    • July 2022
    • June 2022
    • May 2022
    • April 2022
    • March 2022
    • February 2022
    • January 2022
    • December 2021
    • November 2021
    • October 2021
    • September 2021
    • August 2021
    • July 2021
    • June 2021
    • May 2021
    • April 2021
    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    Categories
    • News
    Meta
    • Log in
    • Entries feed
    • Comments feed
    • WordPress.org
    Tiatra LLC.

    Tiatra, LLC, based in the Washington, DC metropolitan area, proudly serves federal government agencies, organizations that work with the government and other commercial businesses and organizations. Tiatra specializes in a broad range of information technology (IT) development and management services incorporating solid engineering, attention to client needs, and meeting or exceeding any security parameters required. Our small yet innovative company is structured with a full complement of the necessary technical experts, working with hands-on management, to provide a high level of service and competitive pricing for your systems and engineering requirements.

    Find us on:

    FacebookTwitterLinkedin

    Submitclear

    Tiatra, LLC
    Copyright 2016. All rights reserved.