Editor’s note: This is the 29th article in the “Real Words or Buzzwords?” series from SecurityInfoWatch.com contributor Ray Bernard about how real words can become empty words and stifle technology progress.
The API economy has been a hot term in recent years and enough has been written about it in Forbes magazine and elsewhere that there is no doubt these are real words and not just an empty phrase. There is something of value behind them. There are companies whose names have “API” in them and recently a new website emerged on the subject: TheAPIEconomy.com.
But despite the realities behind the term, enough misunderstanding and foggy thinking has entered the picture, resulting in business initiatives that didn’t achieve their intended results. It prompted Ed Anuff, then senior vice president of strategy at Apigee (a company providing an API platform and tools, now part of Google), to write an article for TechCrunch titled, “Almost everyone is doing the API economy wrong.”
So, given past history, what are the chances that we’ll get it right in the physical security industry?
You probably already know that API stands for “application programming interface.” It’s a way that applications can talk to each other. APIs have been around for decades. We use them for integrating various components of physical security systems. So, it’s nothing really new, right? Then, why all the hype? Is it just marketing departments rebranding SDKs (software development kits) and making a big deal out of them? Is it just a cloud application term that’s getting over-hyped up like other things in IT?
There has been enough hype around APIs that, in his Forbes article titled, “2017 is Quickly Becoming the Year Of The API Economy”, Louis Columbus was prompted to write, “Senior management teams need to de-hype the entire issue of APIs.” So, at the same time that The API Economy is reaching its highest peak to date, many people are getting it wrong and hype abounds.
Origin of “The API Economy”
The term came about as a way to label the real-world phenomenon that the success of some entire businesses evolves around the APIs they use to conduct business. Decades ago, you had to walk into a store or have a sales representative come to visit you. Nowadays, we pick up our phone or tablet computer and click on a few buttons.
Those few button-clicks use APIs to initiate actions in the company’s information systems. The company’s web pages use an API to take your order. The company’s “order department,” which has been virtualized into software, accepts the order, and sends the information to other business applications to ship the product. The company’s business applications arrange the shipping via the APIs of UPS or another shipper, and notify the customer by text message or email, using another set of APIs, that the order is being shipped and provides a link to the shipper’s web page that will display the real-time status of the shipment (the link uses the shipper’s APIs). All of this you already know about and have experienced, except perhaps for thinking about the APIs that do the work behind the scenes.
Using APIs, Boeing and General Electric jet engine systems send real-time engine status and diagnostics information to their databases, and the set of applications analyze the data. The companies notify their airline customers’ service departments of service required so that service technicians can be ready and waiting with the right parts and tools to perform service the instant the plane lands. This is all accomplished by the use of APIs.
What the API Economy Means
There are various types of APIs and some standards around them, but the point of this article is not about the technical bits and pieces of APIs. (That’s mostly what you find on the Web on this subject.) The point is that large parts of our global and local economies are API-driven.
Thus, the term The API Economy came to mean several things:
- That part of the economy whose business and financial transactions are enabled by APIs.
- The way that APIs can positively affect an organization's profitability.
- A perspective for thinking about application interaction from a business-value perspective rather than a technical perspective.
I haven’t seen the third definition written anywhere else, but it’s a critical one for the physical security industry, and we’ll circle back to it in a moment.
Some businesses do business together without humans having to talk to one another. It’s all handled through their business system APIs instantly, anytime.
“Getting one’s API Economy act together” means figuring out how APIs can be used to further the purposes of the business, accomplish more transactions at high speeds and scales, and either directly drive revenue or drive results that support expanded or continued revenue generation. These can be customer service improvements, for example. I’ll be touching on this theme again in two upcoming articles in Security Dealer & Integrator magazine, on Total Cost of Ownership and Total Cost to Serve. Believe it or not, there are API Economy factors at work impacting both types of costs for security industry manufacturers, service providers, and customers.
The API Economy and the Security Industry
The danger for the security industry is that we’ll think we already know all about APIs and thus nothing will change. The problem is that our thinking around SDKs and APIs has been limited to the very narrow scope of traditional security systems integration, such as having an access alarm trigger the display of a video image. There is nothing wrong with that idea. But it’s a decades old thought and commonplace now.
In keeping with definition #3 above, the most important question we can ask ourselves about APIs is this: How can we use APIs to interface with other applications in ways that bring these kinds of added value?:
- Enhanced security risk mitigation
- Security operations improvements
- Greater end-user convenience
- Business operations improvements
- Actionable business insights
Who in your company will be the chief sponsor of API Economy thinking and strategy? Who will foster those discussions and gather all the ideas for consideration and follow-up action?
There are two important questions to be asking:
- What value can other applications bring to our applications?
- What value can our applications provide to other applications?
This is about enablement. What can other applications enable your application to do that they can’t do now? And vice versa.
I understand that we’re talking about systems integration, but discussions about systems integration in the past have always been narrowly focused, as I said earlier. We need to think beyond our previous thoughts and maybe break a few of our own rules.
Coopetition
Ilissa Miller, CEO of iMiller Public Relations, defined the term “coopetition” this way:
“Coopetition” is a term used to describe unconventional collaboration and cooperation within an otherwise competitive field of players.
For decades in the security industry, competitors would not interface with each other’s products. They just wouldn’t use or support in any way products made by a competing company.
Yet, for example, look at the business that Cox Cable does by using APIs to provide Netflix movies to its cable customers. Cox is now providing more value to its customers by adding value to their investment in TV big screen hardware, making it simpler and easier for customers to manage a wider range of movies on the TV using the Cox remote control. Why make it hard on customers to do what they want to do and will probably do anyway, but dislike you for making it hard to do? I’m sure you can find other examples.
Coopetition is the term that I thought of when I learned this week that S2 Security Corporation’s NetBox 4.10 new release supports Bosch intrusion detection panels. What? Bosch is a competitor to S2! Yet John Moss and others at S2 realized that their integrator partners install many Bosch intrusion systems, and this would simplify things for those partners, contributing to a lower Total Cost to Serve. This is an example of some of the things I’m seeing that give me hope for the security industry in the 21st century.
Hope for the Security Industry
About a year ago, Steven Van Till, president & CEO at Brivo, wrote an article titled, “Physical Security and the API Economy.” Out of the hundreds of pages I’ve read about The API Economy, Van Till’s statement is the simplest and best summary I have seen: “Call it the sharing economy for applications.” When you read his article, you’ll get an idea of how Brivo is participating in The API Economy.
Some other companies who have open APIs and are similarly benefiting are Milestone Systems, Eagle Eye Networks, and now Lenel Systems as well. What is interesting to me is that fact that the founders of S2, Milestone, Eagle Eye, Brivo and Lenel: (a) came from outside of the security industry and (b) had strong backgrounds in IT. I apologize for leaving out a few companies, but these are enough to make my point: Their leaders are focused on how to create more value for their integration partners and their end user customers.
There is a lot happening in the business world resulting from the strong IT focus on adding value through “the sharing economy for applications.” Thus, I can safely say that the future of the physical security industry will be determined in large part by what drives the designs of industry company APIs. How many new capabilities for integrators and end-user customers will be enabled by application integration?
Security’s API Economy Picture
I put together a reminder illustration of the key factors of The API Economy for physical security. I intended to provide a list of action words relating to security and business value, but found I ran out of space at just over two dozen words, with more than a hundred left over!
In applying this illustration, make a list of the new functionality you’d like to have your application provide, and include a short statement of the additional value the integration will then bring to security integrators, end users, and end user customer companies. For example, see how Ticto (ticto.com) is using access control system APIs to establish real-time presence control for critical asset areas and for people protection. Think even further how this could be extended to other types of personnel and customer security, such as for home health care providers giving customers the Ticto app. Ticto is just getting started, and coming from outside the security industry, their founders’ thinking is not limited by legacy industry constraints.
Your thinking shouldn’t be limited either, because The API Economy and the technologies behind it are making things possible that were never possible before. Let’s make the most of it!
About the Author:
Ray Bernard, PSP CHS-III, is the principal consultant for Ray Bernard Consulting Services (RBCS), a firm that provides security consulting services for public and private facilities (www.go-rbcs.com). He is the author of the Elsevier book Security Technology Convergence Insights available on Amazon. Mr. Bernard is a Subject Matter Expert Faculty of the Security Executive Council (SEC) and an active member of the ASIS International member councils for Physical Security and IT Security.
