Wednesday, February 18, 2015

Mexican ISP Telum gains operational advantages via better monitoring across vast network elements

The next edition of the HP Discover Podcast Series delves into how Telum in Northeast Mexico improves their ISP services delivery reliability through quality assurance and higher availability using advanced monitoring software.

Listen to the podcast. Find it on iTunes. Read a full transcript or download a copy.

To learn more about how they have matured their process, technology and IT culture, we are joined by Max Garza O'Ward, Head of IT Operations at Telum, an ISP based in Monterrey, Mexico. The discussion is moderated by me, Dana Gardner, Principal Analyst at Interarbor Solutions.

Here are some excerpts:

Gardner: Why are reliability and high performance are so important to your business?

O'Ward
O'Ward: It’s a very competitive business for the telecommunications industry. We're not the top dog in Mexico or Northeast Mexico. Everything that we put into our customer effort is to bring in customers that we need to keep. So reliability is a key part of our commitment to our customers.

Gardner: And you're not just using technology. You're delivering technology. So it seems essential to have a handle on what you have, what it's doing, and maybe even get out in front and have predictive capabilities when problems might arise.

O'Ward: That’s very true. Prediction is where we need to focus. To ensure good services we need to make sure that all those systems are up and running, and we use software to precisely do that.

Gardner: For our listeners who might not be familiar with your organization, tell us about your size, how many subscribers, how many services. Just give us a description of your organization, both in terms of the breadth of services and the size of your audience?

O'Ward: We're part of the Northeast Mexico market, basically Monterrey, which is the biggest city up north. We have three different customer markets. The residential market is roughly over 500,000 customers. We have small business or SOHO businesses, with between 3,000 and 6,000 customers. And we also have a large enterprise market, around 1,500 large enterprises.

Unwieldy network

Gardner: Let’s dig a little bit into the problems that you face. Several years ago, you were looking at a network that was perhaps a bit unwieldy, maybe not well-defined. You had some difficulties predicting how certain things that you did on your network would impact your customers. Perhaps you can walk us through your problem set, your challenges, and then how you started to solve them.

O'Ward: That’s a very good approach. In terms of network, we basically started noticing that we were committing a lot of unplanned outages, or unplanned downtimes. So we started to reinforce our monitoring solutions based on HP software. We came in and provided better solutions to what we were looking into as a network element point of view.

Based on that, we refurbished our inventory and made sure that all of our network elements were replaced promptly, based on events. So prediction was key to our better service-level agreement (SLA) offerings.

Gardner: Max, was this a function of changing just the software or was there a cultural component to this? Did you have to change the way you were thinking about monitoring and quality assurance in addition to employing some new technology?

O'Ward: Yes, it was a cultural change. As a matter of fact, just two years ago, we revamped the way the operations department is composed. So a big gap that was closed because of culture. Culture needed to be changed.
What secrets will your data tell you?
In the HP Toolkit for Operations Analytics
Previously, we had all these disparate teams working on only their solution. Once we came under one head of operations, we decided that service was the only thing that matters. So we bridged that gap and now we have all these cross-functional teams working for the same response, which is service offerings.
Now, it's a combination of culture, teamwork, and understanding where the failures are.

Gardner: So IT service management (ITSM) has led to the ability to maintain your quality and performance. Are there any indicators of how much -- perhaps the number of failures from one period to more recent failures?

O'Ward: There are a lot of numbers. I will give you top figures. IT is the department that I head, and most of these departments are based on different engineering groups.

When we started working toward service and focusing only on services, on video services, for example, we had over 10 percent failures globally, not every month, but throughout the year. Once we got under this new management and using our new HP tools, we have been bringing that number down consistently.

Now, it's a combination of culture, teamwork, and understanding where the failures are. Sometimes software tells us where the problem is and sometimes software is needed to understand where the problem is.

In this particular case, we soon understood what the problem was and we decided to change out equipment that was failing via either obsolescence or just a defective part.

Transparency and visibility

Gardner: In addition to changing culture, putting in some better processes and better tools, it seems to me that for a lot of companies that I speak to, a lot of the process involves getting to know yourself better, providing transparency and visibility.

Then, it's dashboarding that information so that people can access it, regardless of whether it’s firefighting or just ongoing maintenance. Tell me about this journey from having a lot of elements, perhaps not always visible, to getting this new-found ability to have greater inventory control.

O'Ward: To start off, transparency is key. Once you have an approach of letting the upper management know where your failures are, that creates concern. And in order for us to create business, we need to have a reputation to uphold.

We started with monitoring basic monitoring elements. We created awareness of where our failures were, and at the same time, we asked for more budget to focus on all these defective parts.
What secrets will your data tell you?
In the HP Toolkit for Operations Analytics
That, in turn, made management very aware of what the engineering departments were actually doing -- either as an IT department or as engineering by itself, which is basically hardware.

Once we had all these components, and they were publicly scrutinized or they were publicly shown in a quarterly meeting, that helped create a dashboard. Now, dashboards are really fun if you really know what you're talking about, but if you give upper management the wrong information, wrong decisions are going to be made. So that’s key.

We're working on creating a huge dashboard. Maybe this year is going to be the year. We have the elements and we're providing that information for the dashboard to be built, but we are waiting to do the next step.

Right now, we're focused on getting the elements straightened out, monitoring all of our key systems, and we have done just that in the last year. So we've upheld our end of the bargain, which is service, quality, and capacity. The next step is going to be providing automatic dashboards. Right now, dashboards are manual.

Gardner: So the good news is that you're getting much more reliable information about what's going on. The bad news is, is you have got a whole lot of information coming in.

O'Ward: That's correct.

Aligning data

Gardner: Big data is a big topic here at HP Discover. What are your thoughts about how to get that data, be it structured or unstructured, into an alignment so that you can improve on your situation, know more about it, get better predictions, and better analysis? I suppose the capstone for this is how important will big data become for you to maintain and improve on your reliability over time.

O'Ward: Big data is a big name, it’s a big trend, and everybody is talking about it. A lot of people, especially people who aren't technology-oriented, talk about it as if if they know it. The way big data is coming into our shop is focused more on customers.

If we're talking about big data, unstructured data, that’s coming in from our traps or alerts and stuff like that. Yes, we need to go into that particular scenario. We're looking at two different projects.

We're going to look into a big-data project that actually brings capacity and quality for our services. At the same time, there's going to be another effort from big data that is a customer-facing effort. So yes, it’s going to be a reality in the next year.
The software is awesome, just great software, and if you have the right people and the right potential, that software can bring you very good benefits.

Gardner: So it’s safe to say that big data is going to have an impact on your IT operations, but perhaps also in your marketing, to understand what’s going on in the field very quickly and then be able to react to it. Big data sort of ties together business and technology.

O'Ward: That's correct. That’s the way we're looking at it. As I said, there are two different teams of people working on it. We're going to be working on the operations part first and then at the marketing part as well.

Gardner: We're here at the beginning of HP Discover. Are there any things in particular that you're going to be out there looking for in terms of how to accomplish your goals over the next several years. What would you like to see HP doing?

O’Ward: Very much what they have been doing in the past. The software is awesome, just great software, and if you have the right people and the right potential, that software can bring you very good benefits.

Our head of operations for the whole company is here with us this week. I'm going to make sure he attends all these meeting in which we can talk about big data and how we can mold out all of the strengths and all of the key performance indicators (KPIs) that he needs. I hope that HP continues to be an innovative software company. I have really enjoyed working with them for the last five or six years.
What secrets will your data tell you?
In the HP Toolkit for Operations Analytics
Gardner: Okay, last question. Going from a failure rate of 5-10 percent down to less than 1 percent is enviable. A lot of people want to make those kinds of strides. Now that you have had experience in doing this, do you have any 20/20 hindsight? What would you suggest to other organizations that are also trying to get a better handle on their systems and their network, get to know their inventory, and gain visibility? What have you learned that you might share now that you have been through it?
O'Ward: It doesn't matter how much we monitor things or how many green lights or red lights we see on any given dashboard. If we're not focused on business processes and business outcomes, this isn't going to work.

My take would be to focus on a business process that you actually know it's critical and start from that. Go top-down from that. That would be the best approach. It's worked for us. It actually bridges a gap between management and the engineering departments. It also provided us with sound budgeting information. Once you understand what the problem really is, it gets approved easier.

So look at business processes first, get to know your business outcomes, and work on that toward your infrastructure.

Listen to the podcast. Find it on iTunes. Read a full transcript or download a copy. Sponsor: HP.

You may also be interested in:

Tuesday, February 17, 2015

California Natural Resources Agency gains agility through Software-Defined Data Center strategy

The next BriefingsDirect innovator case study interview explores how the California Natural Resources Agency (CNRA) in Sacramento gains agility from a software-defined data center (SDDC) strategy.

Learn how this large and diverse agency of state agencies uses the best of centralized and de-centralized IT resources, largely built on a common VMware-powered SDDC strategy.

Listen to the podcast. Find it on iTunes. Read a full transcript or download a copy.

 At the recent VMworld 2014 Conference in San Francisco, our moderator, Dana Gardner, Principal Analyst at Interarbor Solutions, interviewed Tony Morshed, Chief Technology Officer for the California Resources Data Center in the California Department of Water Resources, and Michael Hom, Data Center Chief in the IT Infrastructure Services Branch for the California Department of Water Resources.

Here are some excerpts:

Gardner: You’re from the largest US state. You have a large government, probably the size of what many countries have. Is there something different about the public sector in terms of accountability or response? How do you have a different set of requirements as a public organization and perhaps enterprises, too?

Morshed: We do have a difference. Our procurement is much harder. Getting people is much harder. We live within a lot of constraints that the private sector doesn’t realize. We have a hard time adjusting our work levels. Can we get more people now? No. It takes forever to get more people, if you can ever get them.
We live within a lot of constraints that the private sector doesn’t realize.

Gardner: So it’s doing more with less over and over again?

Morshed: Constantly doing more with less. Part of this virtualization is survivability. We would never be able to survive or give our business the tools they need to do their business without this. We would just be a sinking ship.

Gardner: So the whole philosophy, Michael, of SDDC and virtualization, is of doing more with less, of automating, of boiling out the manual processes and going to more real-time responsive technology driven infrastructure makes total sense for your organization?

Hom: Definitely. To go with what Tony says, we really don’t have much overhead when we need to respond to future projects. When there's an uptick in activity, there is no way to have more resources available. So we need to build that into our infrastructure to allow for that dynamic bandwidth to happen from a personal level.

 Gardner: Help us understand the size of your organization. This is a large state government department, but you're really a department of departments.


http://www.cold.ca.gov/agency_display.asp?ATRID=WTRRSC
Morshed
Morshed: Our department, Water Resources, consists of 3,500 people that are part of the agency that comprises many departments. The bigger ones are Parks and Rec, Cal Fire, and Fish and Wildlife. There are about 28 agencies and conservancies and 25,000 people.

Gardner: So in order to support all these people and all these different agencies, a common infrastructure is important, but also it sounds like you need to have differentiation and customization for their specific needs. How do you accomplish both the goal of a common infrastructure for efficiency, but also still be able to meet all your requirements for all those different people?

Morshed: When we started our consolidation effort, we decided to transform ourselves more to an ISP-style setup. We know that most departments have their own IT shops, and you know there is still that trust thing. So we just built the common infrastructure. We let them share the infrastructure, but they have their own security posture. We segregate all their traffic, so each department can still feel like they're autonomous, but yet we all share the infrastructure, in which case we all share the savings.

Mandate to consolidate

Hom: With that, we had a mandate to also consolidate. First, the State of California is really about cost savings. Each of the 25-plus organizations mostly had their own IT shops. By combining the infrastructure as a service (IaaS) in our multitenancy data center, they're able to reap the benefits of cost savings for infrastructure, but also concentrate each department's specific needs and applications.

Gardner: What are some of the challenges you have in terms of getting closer to a full SDDC? Are these technology, culture, process, or all of the above?

Morshed: At first it was technology, but the culture and the organizational mindset are the bigger challenge. You can find solutions and work through technology. We're IT people, and we’re used to the technology problems. For me, the greater organizational problems -- and the structure of your processes -- become the harder things, because we’re not as used to dealing with those things.

Gardner: Now, Michael, part of the adoption of a complex, long-term journey on IT is to show results early and get buy-in. Are there instances where you look at that? Maybe, it's the DR, where you can have a sense of better dependability on your resources? Any way to describe what you’ve done early on that has lead to a greater emphasis to adopt more aggressively?

Better service levels


Hom
Hom: Definitely. One of the key things with early wins is providing a better service level for provisioning, and that’s something that everybody has been struggling with. With the cloud infrastructure, we've been able to provision within days, if not a day. And that typically beats most of the service tools that each of the organizations have had. So that was an early win.

It’s things like that where we decrease overhead and make IT more accessible for business. That makes it a win, and starts to have the ball rolling as far as other features, such as DR, greater capacity, and things that would be tough for each individual organization to do on their own.

Gardner: Are you exploring software-defined storage, software-defined networking?

Morshed: When the software-defined stuff came out, for me, one of the big things was disaster recovery (DR). If I could stretch my data center into another facility, DR becomes a non-issue, because those workloads can shift between sites without any trouble with automation.

That was the next piece for us -- automation. We realize that we’re part-way there, but to get all the way there, we need to do fuller automation. This means that we need to quit tinkering with the network and storage every time we want to do something new.

Those were big driving factors for going to SDDC. To us, it means that we’re obfuscating the hardware. The hardware’s there. It’s just running. We’re working and tweaking everything at the software layer -- so we could be a lot more agile.

Separating the physical

Hom: For the SDDC we really wanted to provide a logical data center to each of our organizations. We wanted to separate the physical, which allows our folks to support more of a logical infrastructure, where they still have autonomy, but the physical layer is basically one and the same.

Today, from a functional point of view, they get what they’ve had before, but without the overhead of physical support. We've used the VMware vSphere and vCloud Suite to provide that software-defined queuing. Right now, we're embarking on a software-defined networking, using VMware NSX and third-party vendors to support that.

We’re looking to use automation soon to help us decrease overhead, and pass those savings on to each of the organizations.

Gardner: We’re here of course at VMworld 2014. There’s lot of news going on. Anything in particular piquing your interest, perhaps with the OpenStack support in the EVO Hyper-Converged Infrastructure? What is now on your agenda after hearing some news to reach those goals as you describe them?

EVO looks pretty nice

Morshed: There are a couple of things. EVO looks pretty nice. I was out on the floor and looking at it yesterday and talking with the CIO and I see it as something that we might be able to use for some of our outlying offices, where we have around 100 to 150 people. We can drop something like that in, put virtual desktop infrastructure (VDI) on it, and deliver VDI services to them locally, so they don't have to worry about that traffic going over the wide area network (WAN).

The other piece is the acquisition made recently with CloudVolumes and looking at how we can use that to leverage our VDI structure. We're using another product right now in that space, but again with CloudVolumes it’s been a part of VMworld. It’s more interesting, because we know that the chances of all the software being upgraded and updated in at the same time in interoperability is greater if it’s a VMware product.

For us, it’s been a real struggle to make sure that all the products that we use, interact and as there’s an upgrade, everything upgrades at the same time. To me, those are the two biggest things that I'm getting out of the announcements.
The business could come up with more dollars, but to be able to be more agile and more flexible is where it really pays off.

Gardner: Do you have any metrics of success that you can point to from your SDDC effort so far?

Morshed: We do have some tangible benefits. We have reduced our CAPEX by somewhere around 40 percent and our OPEX around 32 percent. I don’t have the numbers, but we have deployed VDI in the Department of Water Resources and we already virtualized about 600 to 800 desktops. Not only is it helping us save costs there; it’s also used as a strategy for a remote access as a strategy to help protect our server infrastructure by using VDI for admins.

So there are those tangible things that you can reach out and measure and those intangible things, where it’s allowing us to do something easier and more flexible. That, for me, is the bigger win. The business could come up with more dollars, but to be able to be more agile and more flexible is where it really pays off.

Gardner: So we get productivity, we have better DR, which reduces your risk, and we've got some hard savings and economics. It's pretty compelling. Michael, any thoughts about how those fit together, and which ones are more important to you?

More flexible

Hom: Definitely, this allows us to be more flexible, and there are some things that we're trying to do that we would never imagine without a SDDC. So they increased security, greater capacity, capabilities to our business.

Gardner: How about VMware specifically? Is there some differentiator in terms of how they produce this products that has allowed you to follow this journey? Is this more of a partnership than a procurement relationship? It sounds like the track that VMware takes in its strategy very much aligns with yours.

Morshed: It’s very much a partnership. In fact, we basically only want to work with business partners. We don’t want to work with vendors, because we don’t need someone to sell us something and walk away. VMware has been hand-in-hand with us for this whole journey.

When we look at other products for the mix, we look for the deep partners with VMware because we know virtual machines (VMs) are core. So, when we look in the storage partners and we’re looking at networking partner, we’re making sure that those partners are partners of VMware.
We don’t want to work with vendors, because we don’t need someone to sell us something and walk away. VMware has been hand-in-hand with us for this whole journey.

One of the things that we find is the inoperability once everything has been virtualized. Everything has to connect, and it’s not a single stack. So if one thing gets upgraded, we need to make sure that everything across a stack can accept that upgrade. Otherwise, we lose the ability to take the advantage of the upgrade until everybody else catches up.

Early on, we were in that position and we’re doing everything we can to remove ourselves from that position.

Hom: We consider VMware a strategic partner. A couple of things that illustrate that is that we’ve been involved with the VMware’s Excellware and Velocity program and that's been two-fold. For the velocity side, we have marked up a fully working SDDC with SX, with virtualized automation, operations in business as a stack.

Gardner: One of the things we've heard here at VMworld is be bold, be brave, be a little bit aggressive. Go out there and do these things. Any thoughts for other organizations that are just dipping their toes into the water? Is it higher risk than reward to be bold and brave in getting early? Or is it perhaps something that allows you to then be a differentiator and be better in your own environment, whether it’s a public or private sector?

Set in stone

Morshed: The first thing is always question what you’ve got that's set in stone, because most of it is not set in stone. We've all heard a lot of things that you can't do. You can’t virtualize Oracle, but you can. You can't do this, you can't do that, you can't get the network focused at the top of the storage. That's all that stuff that you actually can do.

You have to really look at it, peel it back, make sure that "you can't" is an actual thing, and then figure out how to get around it. The way I see it is that, as the world turns, things morph, and if you don’t move into this virtualization space, you're going to be left behind. You're going to be the guy making buggy whips. There are no buggy whips running around. There’s no use for them.

We’re all being asked to do so much more with the same resources or fewer resources. We're all being pushed to keep up with how the demand is going out there. Technology is just jumping, and this is the only way on the infrastructure side to keep up with that.
We’re all being asked to do so much more with the same resources or fewer resources. We're all being pushed to keep up with how the demand is going out there.

Gardner: Michael, any other thoughts in terms of 20/20 hindsight on your experience and why being aggressive and being bold has paid off?

Hom: Virtualization is definitely up and running, at least in state organizations. It’s probably something that we might do that or we might use as a toolset, but from looking at VMware this week, virtualization is the industry standard.

If you don’t take it on, then you really won’t be able to respond to business needs. What happens is that when the official IT organization becomes obsolete, there are going to be ad-hoc IT organizations and those would become the norm. If you want to be relevant, you have to use every tool set that you can to provide the business needs.

Listen to the podcast. Find it on iTunes. Download the transcript. Sponsor: VMware.

You may also be interested in:

Thursday, February 12, 2015

Networks: The new model for B2B business, a panel discussion

New business networks are unlocking the ability for companies to extend processes and insights broadly and affordably to customers, suppliers, and other partners. As a result, data-savvy B2B participants in these networks are better able to engage with their communities in new and innovative ways.

Listen to the podcast. Find it on iTunes. Read a full transcript or download a copy.

The latest BriefingsDirect discussion therefore explores the role and impact of business networks, the often virtual assemblages of interrelated business services, processes, and data that are transforming how companies and consumers conduct commerce.

We examine the ways that open markets and communities are rapidly becoming business platforms. And we'll see how today's consumer business models -- exemplified by Amazon, Uber, and Airbnb -- are extending to business-to-business (B2B) commerce, allowing buyers and sellers to find and know each other openly -- and accelerate B2B transactions and commerce efficiencies.

To learn more about the trends that are making business networks more powerful and more important than ever, BriefingsDirect recently sat down with Marshall Van Alstyne, Professor at Boston University School of Management and Research Scientist at the MIT Center for Digital Business, and also Tim Minahan, Chief Marketing Officer SAP Cloud and Line of Business. The panel is moderated by me, Dana Gardner, Principal Analyst at Interarbor Solutions.

Here are some excerpts:

Gardner: Professor Van Alstyne, this is a tricky time for companies. It seems that they want to retain what works, the business models that have been tried and proven for them. They like having big margins, of course, but in order to grow and to be part of the future they need to expose themselves to these networks, take some risks, maybe lose margin in the process, but perhaps get scale and automation as a payback.

How do you view that? How do you see companies adjusting? Is this a cultural thing where some companies will take this plunge and others don't? It does seem to be a perilous time for companies. I hope they're not just freezing in the headlights.

Van Alstyne
Van Alstyne: It’s a great question. There are a couple of elements and they vary based on the where the company is currently. If it’s a relatively virgin market, then it’s fairly straightforward for them to invite others in, create the platform, and expand out in that direction. If it’s an existing market for them, they really have to worry about managing the cannibalization question.

I know SAP has also had a very interesting example of that, as you move from on-premise services to hosted services. They're doing a nice job of managing that migration. It’s a little bit tricky in terms of how much you expand the market, but you really need to. You have to realize that the scale, the innovation, the customer engagement happens on these business platforms. Long-term, one really doesn't have a choice.

Platforms vs. products

One of the arguments that we typically make is that even weak platforms tend to beat very strong products. You can look at any number of examples, whether you take a look at the Blackberry, the Sony Personal PlayStation gaming device, or the Garmin device for GPS.

All of these functions are effectively absorbed into the platform. If you manage a platform ecosystem, where third parties can add value on your behalf, you'll grow faster. The platforms almost always will be products. So, in the long-term, companies don't have a choice. They have to move in this direction.

Gardner: So if it’s inevitable that you have to change, it sounds to me from what I've seen at SAP, that they're recognizing this. They're dealing with it themselves as a company, but they're trying to put together a safe path for enterprises to expand into the networked economy. At the same time, they can have trusted partners for automating a lot of the behind-the-scenes activity and allowing them to still function within their business verticals to know what their intellectual property is and to extend to it.

Let’s go back to Tim. Am I reading that right, Tim, that SAP is trying to be, in a sense, the arbiter between risk and exploration when it comes to the networked economy?

Minahan: That’s an accurate depiction, Dana. Think about our personal lives. Whether we're engaging family and friends on Facebook, buying a book or a blender on Amazon, or trying to capture transportation services to get downtown during rush hour on Uber, we're experiencing the scale and simplicity and convenience of personal networks.
At SAP, we believe that solving this inter-enterprise collaboration challenge is one of the biggest opportunities of our era.

We run our daily lives on them now. Unfortunately the business world traditionally has been optimized within the four walls of the enterprise. Companies have invested billions over the past 20 to 30 years in re-engineering their processes and investing in systems to really automate those internal processes and information flows.

They have created what have become islands of efficiency that work very well, and continue to work well, for those that are highly vertically integrated, but very few are, as we talked about earlier.

At SAP, we believe that solving this inter-enterprise collaboration challenge is one of the biggest opportunities of our era. We feel that we're well positioned to do that and have been assembling some of these business networks. We've had the acquisition of Ariba and Fieldglass in the area of contingent workforce and, with Concur, now in the area of travel and expense.

Minahan
We're complementing that with network extensions of our own, both through the addition of things like the product sustainability network, which leverages the existing connections within the network to help companies better perform tracing and tracking of their products, and the financial services network, which really facilitates and aids payment.

What we're looking at is an opportunity to extend existing IT infrastructure and business process outside the four walls of the enterprise in the most scalable and efficient way possible, no matter what systems a particular company or their trading partners use, all through a single integration point.

Integration adapters

Think about Amazon in your personal lives. You don’t worry about integrating tier trading partners or how you are going to sell that. Amazon takes care of that for you. That’s the same metaphor that we're attempting to carry through into the business world by providing single standard integration adapters or on-ramps to the network that allow you to manage this virtual enterprise in a highly transparent and highly efficient manner.

Gardner: Professor Van Alstyne, we've seen a great deal of network effects in business over the past decades. Yet nowadays, the confluence of cloud, mobile, and social and an emphasis on data-driven business processes seems to be accelerating and empowering these shifts. Some organizations call this the Third Platform. How does your research define business platforms, and how are the impacts from these Third Platform technology advancements newly impacting businesses?

Van Alstyne: I emphasize the network effect as one of the driving forces. Indeed, if we can create a positive feedback loop throughout the network effects, that’s where you see the efficiency in the scale happening so quickly.

In terms of a definition, we focus on two elements of the platform. The first is an open architecture that third parties can build upon.

The second is the governance rules. How is it that people can participate? Why would they participate? How do you share the profits? How do you resolve conflict? You think about it as a nexus of rules and architecture. If you can put those two things together, you can probably grow an ecosystem that helps to foster and stimulate some of those network effects.

Gardner: Tim Minahan, SAP has been a pioneer inside the four walls of the enterprise over the years with enterprise resource planning (ERP) and other business applications. Now, it seems as if you're recognizing what Professor Van Alstyne has been describing with these network effects and extending your value and business insight and processes across multiple boundaries, outside the four walls of any given enterprise into entire ecosystems.

Next productivity wave

Minahan: We truly believe that the next wave of business productivity is not going to come just within enterprises, but between them. Forty years ago, when SAP arguably invented the whole concept of ERP, businesses were operating much, much differently.

We showed them a new way to automate their internal information and process flows, but they were organized in a much more vertically oriented fashion. The employees would graduate from college, spend 40 years with the company, get the gold watch, and retire.

Companies owned most of their infrastructure, their manufacturing facilities, their inventory, their shipping fleets, but certainly this is not your father's business environment anymore. In part, this was accelerated by the recession that we're still emerging from. Companies are less vertically integrated than they were in the past.

They've adopted more variable operating models. They've outsourced everything from manufacturing to customer service, and they need to reach and compete with companies across the street and on the other side of the world. And this is creating new opportunities, as well as new challenges, for businesses today, and it’s increasing demands and expectations on individual functions of their teams.

You're seeing it everywhere. If you have an iPhone, look on the back. It’s designed in California by Apple, but it's built, shipped, and serviced by someone else entirely. Even beyond the physical device, Apple makes most of its revenue from network-based services. iTunes relies heavily on an ecosystem of mobile carriers and artists and studios.

Now, we're seeing this move into the business world, in which companies need to rapidly organize this virtual enterprise, all these resources of employees, manufacturing capacity, logistics, delivery capacity, and customer service to take advantage of certain market opportunity. Or, they need to adapt very quickly to certain market changes, and the only real way to do that is through a digitally connected network of partners, customers, and supply chain.

Gardner: As the very nature of corporations change, it's really about relationships, data, and feedback loops. The data-driven organization, is it really about that. Are we losing something, are we gaining something, or both, Tim, as we seek this new definition of a corporation?

Minahan: We're entering an age where the borders between enterprises are being taken down. Companies are moving toward a model where they're managing pools of resources, whether that’s pools of talent around expertise, as you just indicated Dana.

A third of a typical workforce is no longer on the company payroll. It's contingent, statement of work (SOW) workers. In some industries, it’s already more than half. This is fastest growing part of the workforce. HR executives, and I talk with many of them, are beginning to rethink what constitutes the workforce and are looking at pools of talent.
A third of a typical workforce is no longer on the company payroll. It's contingent, statement of work (SOW) workers.

They need to understand where the skill sets lie, not necessarily what roles someone plays today, what skills they have had in the past and be able to, when a particular opportunity or project arises, assemble that expertise very quickly to address that particular project, and disassemble them just as fast, but retain the knowledge within the enterprise for the next time that comes up.

The same thing is true if you're organizing a supply chain and need to be able to serve a new market like China. Where do you put your manufacturing? How do you address distribution, value-added taxes, and customer support. Traditionally, the model would have been to go and establish your own manufacturing facilities, build your own local agents, but no longer.

Now you can quickly assemble and address, or test, a particular market or test a particular product in any given market. Should it work, scale it up. Should it not, scale it down and move on. Networks allow you to achieve this.

I wanted to go back to something that Professor Van Alstyne said that's critically important. I fully agree that the networks go through phases. The first phase is to connect all the various parties, whether they be people, businesses, merchants, banks or all of the above.

The second part is to automate their existing processes. What gets really exciting, once you've automated these processes, once you have these parties collaborating or transacting its scale, are the new insights and entirely new services you could enable.

Transactional information

Once you have these millions of companies or people transacting at scale, you can see the transactional or relationship information. It could be the generated content that helps all members of the community make more informed decisions whether it's about buying or whether it’s about, should I bid on a particular bit of business as a seller or as a bank, mitigating risk in lending to allow them to understated who the buyer is, who the seller is and what their traditional history is.

That is the ultimate big data opportunity, when you have these networks operating at scale. We're beginning to deliver this networked intelligence in the form of insight services to help our members of the communities make important buying, selling, and financing decisions in ways that they couldn’t before.

Van Alstyne: Dana, let me jump in for a second. One of the things that Tim just said is quite important. One of the most interesting elements of the platform is the extent for new business services and new products to emerge. One of the Silicon Valley descriptions of the platform is that you know you have one when your community takes it in a direction you didn't expect.
One of the most interesting elements of the platform is the extent for new business services and new products to emerge.

You need to have made it possible for that. The underlying architecture needs the support the ability to develop something new that wasn't expected, but that’s one of the ways the platform adapts to create new value.

The communities start to add new value and new services in ways that the platform meets the needs of the ecosystem, so it’s this ability to turn out new sources of value based on the underlying architecture. This is one of the key distinctions of platforms that really do add value.

Minahan: I totally agree with that. We've only just entered it into this networked economy or networked era. One of the most exciting things is that it allows you to begin to entirely rethink traditional business models that were organized in an era where, to use an economic term, transaction costs were extremely high.

Look at Uber, what Uber has done, and the challenges we're now seeing around challenging the traditional medallion livery service. That was organized out of a very real concern around safety and issues, but over time, that model matured and unfortunately got very costly.

What you saw were the medallions being aggregated in the hands of a small few who could afford them. That obviously had some implications on the level of service and cost of service to employers. Now we've removed all of the transaction costs and could add up efficiently match demand -- i.e. you as the traveler -- and supply literally anyone that is a card-carrying member of the Uber service.

That’s an entirely new business model that is fundamentally challenging hundreds of old rules and thoughts about what it means to hail a cab. So let me toss in one additional principle that’s often used for design. I'm thinking exactly of the Uber example.

One of the best ways to view a platform is that you have the best platform and the transaction cost are the lowest. If you can get those lowest transactions, you're going to get more business taking place on that platform. So do whatever you can to see if you can lower those transaction costs to get the business going.

Looking for signs

Gardner: So we've taken a look at the inevitability of these networks. We've seen them already very prominent in the business to consumer (B2C) space, consumer activities, and commerce. We’ve recognized that openness is important. So we have innovation. We also recognized the importance of governance and management.

So how do we know when we've done this correctly? Is there a sign? Professor Alstyne, you've mentioned a few that describe powerful and successful networks. Do enterprises have to view themselves differently? Do they need to look at participants in their network as a metric rather than just margin and net in gross revenues and incomes? Is there a way to be successful?

Van Alstyne: Platform businesses behave differently than traditional businesses. Silicon Valley had been using lot of these metrics for engagement. How many new users do you get, and how engaged are they with the platform? It’s a wonderful place to start. Let me give you three rules that we like to use for platform design that actually help get the system running smoothly.

One of them is "frictionless entry." You would like to make it as easy as possible for people to get onboard your platform. It doesn’t matter if that user is on the developer side. You want folks to be able to enter the platform as easily as possible.
If you're bringing in apps in your ecosystem, your users are going to get a bad experience if they are low-quality apps.

The next one is that you need to manage "riskless quality." If anyone can participate, there's a danger that folks who actually get onto the platform don't necessarily add value or they may try to siphon off value. You may worry about lower quality. Atari fell apart as a platform when it got low-quality games on it. Uber has to worry about low-quality drivers. If you're bringing in apps in your ecosystem, your users are going to get a bad experience if they are low-quality apps. So you still need to have riskless quality.

The first principle is frictionless entry, and you need to manage riskless quality from the users on that side.

The third one is "permissionless innovation." You don't want your developers to necessarily have to come to you to get permission. There is always this danger because you own the platform. You have enormous power over them and you could simply take that idea and run with it. You need the ecosystem partners to be able to run with an idea and create something novel on their own and let them have that value. They don’t need to get permission first.

These are three rules that we use for design -- frictionless entry, riskless quality, and permissionless innovation. Those are really good guidelines and are helping to get these ecosystems to grow quickly, get more users onboard, and get your value add from third party participation.

Gardner: Tim Minahan at SAP Cloud, tell us a bit about what you're doing at SAP, some of your acquisitions, besides your cloud, this ability to be frictionless and help people come on the network easily. You recently finished up the Concur acquisition, one of your largest ever. Explain how you're growing the size of your network?

Application agnostic

Minahan: What Professor Van Alstyne just talked about are principles that we subscribe to. In a business network sense, it also requires you to be open and application agnostic and largely agnostic to the on-ramps. That’s part of the frictionless entry.

So regardless of what system you are using, whether it’s SAP, Ariba, Concur, Oracle, PeopleSoft Info, etc., you need to be able to attach the systems to the network, those demand systems that allow you to connect and collaborate through the network to extend that business process and engage with your customers, suppliers, and other partners.

Think about our personal lives, whether it’s Uber or Amazon, those networks that are most powerful and most impactful on our personal lives allow a seamless process. You don’t even think about the process, but it is end to end.

In the case of Amazon you don’t think about the buying process -- how am I going to connect to those individual merchants? They're already connected for you. Ultimately, you believe you're buying from Amazon, but you might be buying from an independent provider and they are still delivering to you.
Those networks that are most powerful and most impactful on our personal lives allow a seamless process.

Likewise, you don't think about, gee, now that I have placed the order, do I have to call my bank to settle out? No, that’s handled for you, SAP has been using these guiding principles to go out and make sure that we're building the network appropriately, both in our organic means through innovation and the introduction of new services, like payments, financing, and dynamic discounting, both independently with other members and financial institutions of the network, as well as inorganically through acquisitions.

Gardner: As we close out, we've determined that the number of participants and the value of the commerce is super important in these networks. Several times we've also touched on this feedback loop in the data. So as we look to the future, we might have  competing networks. If we assume that those networks are going to have some frictionless ability to move on and off of them, then the best network is where people will go.

Is the best network the one that provides the best insights in data? Can we close out our discussion by looking at the importance of shared data and analysis and the ability to counter that analysis up from these transactions as a differentiator going forward that will pick winners and losers in open commerce network environment, if you will.

Let’s go to Professor Van Alstyne first. Who is going to win in this network environment and is the data and openness and availability of analytics going to be a major determinant of that?

Van Alstyne: I am going to argue the best platform is the one that creates the most value over time and that probably means that the data analytics, those that can use the data to create these data-driven feedback loops, will be the winners.

One of the things that I want to emphasize is that frictionless entry and the ability of the movement of data doesn’t necessarily mean that switching costs are going to be low or that it’s going to be easy to necessarily change networks. Network effects do create winner-take-all markets, they do create these behemoths. Google Search has 67 percent market share in the US and 90 percent in Europe. Facebook has 1.3 billion users. I think Amazon web services has a huge proportion of the cloud services.

We need to be careful if we think we're going to be able to switch networks easily. There are going to be some very substantial winner-take-all networks and some concentration at the top. Cloud and data is going to be an integral part of that, as the data creates these data-driven feedback loops that support these network effects.

Data and analytics

Minahan: I agree with the professor that the key litmus test of who wins is the platform or the network that creates the most value, and I think value comes in a few flavors.

Number one is relevancy. Are my trading partners there? At SAP, typically about half of any given company's trading partners are already connected in transacting. That makes the frictionless entry that much easier. Think about Facebook. Why would you join any other personal network when most of your friends and family are already there.

The second is the aspect of value. Can I manage most of my collaborations in a single environment or do I need to join multiple networks in order to complete a transactional process? The more capabilities you can layer in to make it more convenient for all members of the network to collaborate, the more value add.
The more capabilities you can layer in to make it more convenient for all members of the network to collaborate, the more value add.

And third, I believe that we've only scratched the surface on these insights. I wouldn’t even say that it’s a two-sided model. It’s a multi-sided model, where once you get these parties collaborating at scale, the transactional relationship and community-generated content can deliver new insights to help folks make more informed decisions, whether it's, which trading partners to do business with or which areas of your existing supply chain might be presented with risk in the future and you need to adapt quickly or which financial settlement options you have to settle out to help you optimize cash flow.

These are new insights that were previously impossible with traditional on-premise and point-to-point integration models and it can only be accomplished in a network model.

Gardner: I'd like to thank out panel, Marshall Van Alstyne, Professor at Boston University School of Management and Research Scientist at the MIT Center for Digital Business. And I'll alert our readers that there will soon be a new book called "Platform Strategies" out in 2015 from Professor Alstyne and co-authors. Also a big thank you to Tim Minahan, Chief Marketing Officer, SAP Cloud and Line of Business.

Listen to the podcast. Find it on iTunes. Read a full transcript or download a copy. Sponsor: SAP.

You may also be interested in:

Thursday, February 5, 2015

Kony gives enterprises the means to make mobile development a force multiplier for business productivity

Orlando, Fla. -- Kony, Inc. burnished its mobile development credentials this week at the Kony World conference here, detailing new updates to its visual tools and platform, expanding its partner ecosystem, and launching a new enterprise mobile app marketplace with the debut of CRM app Kony Sales.

The combined efforts are designed to help businesses gain enterprise-grade mobile productivity fast, leveraging central services and automation, embracing all end-points from a common code base, and encouraging users themselves to tweak their apps best.

"We are going to do to mobile what Salesforce did to web apps with Force,” said Kony CEO Tom Hogan at the Orlando conference, one of three Kony user gatherings set for 2015, with the others soon in Frankfurt and Dubai.
We are going to do to mobile what Salesforce did to web apps with Force

Hogan encouraged enterprise IT leaders to not force their users to make compromises as they seek mobile apps for extending and improving their business processes. Enterprise business users want to have their native interface usability benefits, but developers need to enjoy cross-platform benefits to deliver their apps with speed and security. They can both get their way, says Hogan. [Disclosure: Kony is a sponsor of BriefingsDirect podcasts.]

 "Consumers won’t tolerate the pace of enterprise IT,” said Hogan, pointing out that demand for mobility has led IDC to predict that 25 percent of IT budgets by 2017 will go to supporting the mobile enterprise.

Trouble in mobile pursuits

At the same time, says IDC, 50 percent of enterprises are having trouble linking mobile front ends to the rest of IT. This is where Kony is focusing its efforts, to bridge the divide between what users demand and enterprises can responsibly deliver in enterprise mobility.

Competitive pressures are trumping IT efficiency, forcing a higher pace and larger budgets to attain effective mobility, says Hogan. A leading mobility analyst agrees.

"We are at the end of the golden age of the standalone app," Forrester Principal Analyst Jeffrey Hammond told the Kony user crowd. “Instead, we’re now in a mobile mind shift, with the vast majority of users already on mobile devices,” he said.

Forrester surveys show that "improving customer experience” in using mobile apps is now much higher among the very top of planned business initiatives, says Hammond.

Factoring "effectiveness, ease, and emotion" are keys to designing good mobile apps, he continued, adding that business should "own an equal share of determining a mobile strategy. … By doing this, you actually help IT get the job done better,” says Hammond.

A big hold-up for mobile apps velocity, however, is the need to code each of multiple end-point platforms, says Hammond. Continuous delivery and fast feedback via analytics is only just beginning but is essential for mobile apps development in-house at enterprises.

To do rapid test and release mobile app dev -- and to gain that feedback loop -- enterprises need force multipliers like stronger tools and platforms with automation, says Hammond. They also need to gain more of the skills needed for a mobile-first capability.

"Kony MobileFabric is a good example of the kind or architecture enterprises need to do proper mobile development," says Hammond.

That's behind the Kony drive to expand its role in a lifecycle approach to enterprise mobile attainment, as the company announced a growing ecosystem of partners that are offering new “ready to run” applications via Kony’s cloud-based business mobile app marketplace.

The Kony Marketplace offers a collection of ready to run apps, reusable components, and design templates. These allow the growing list of partners to speed the process of adopting and delivering mobile apps to meet business demand.

The new partners, who will offer their solutions throught the marketplace include: Broadstrokes, Factual, InfoStretch, Knack, PopcornApps, Quinscape, Redora, Softechnologies, Splyt, Stefinini, UST Global, VeraSynth, and ZineOne.

“Industry experts are predicting that the demand for mobile apps will dramatically increase for enterprise organizations in the next few years,” said Burley Kawasaki, Kony senior vice president of products. “To meet this demand, enterprises are looking for ways to empower their businesses to rapidly deliver secure, enterprise-level mobile apps with great user experiences. Our goal is to provide a rich collection of pre-built apps and app models through the Kony Marketplace, which they can use to quickly build their mobile apps."

Mobile apps are way different

And these new mobile apps need to be designed differently, because they are different. They are typically situational, with dynamic requirements, in high demand, possibly throw-away, and often like consumer apps, said Van Baker, Gartner vice president and leading mobility analyst, to the Kony World crowd on Thursday.

User experience is the key, echoed Baker for other speakers at the conference. "User centricity is the only option. It must bring the relevant information to the user in a relevant fashion,” he said. And so mobile technology needs to adapt to people, not the other way around, he says.

And today’s mobile apps are just a stepping stone. By 2017, 50 percent of today’s deployed mobile apps will be rewritten or replaced, said Baker.

Traditional IT is being shunted aside by those who will get their mobile apps one way or another. Indeed, shadow IT spending is going to 50 percent, and so will be the third largest IT budget item, said Baker.
By 2017, 50 percent of today’s deployed mobile apps will be rewritten or replaced

So IT needs to deliver tools to the enterprise that business analysts can use to make mobile apps, IT will not keep up using waterfall-style code-based development, says Baker. So IT will end up surrendering the client development to business analysts using visual tools, concludes Gartner’s Baker

Other predictions from Baker: By 2018, more than half of all business to employee mobile apps will be created by business analysts with codeless tools like Kony’s. And by 2020, web- and mobile-style app integration will have fully displaced traditional approaches, he said.

That jibes well with what researcher IDC has predicted, that the number of apps optimized for mobility will quadruple by 2016.

Given this sea-change in the enterprise, Kony has moved quickly to help businesses provide mobile-first apps for their sales teams. Kony this week released its first ready to run Kony Sales app suite, featured in the new Kony Marketplace. The mobile productivity extension app for SAP and Salesforce allows sales representatives to:
  • Increase sales rep productivity
  • Manage tasks and follow-ups
  • Accelerate pipeline activity
  • Manage leads, accounts, opportunities and contacts, and
  • Work offline to capture information while traveling, and then sync it to the back-end once they return to the office. 
Built on top of Kony’s Mobility Platform and composed with Kony Modeler, the Kony Sales app can be easily extended, configured and customized by business analysts and sales operations personnel. Kony Sales is optimized for iOS and Android phones and tablets, and has the ability to receive upgrades while preserving customizations.

Expect more business-centric apps like Kony Sales soon, targetng such arenas as finance and healthcare. Kony's ISV partners will help drive the creation of these market-driven apps, said Kony officials.

Composition tool set

Also available this week is Kony Modeler, a powerful visual, composition toolset for business users to assemble and configure mobile-first apps from reusable, lightweight app models available in Kony’s app marketplace. With Kony Modeler business users can rapidly customize their apps for unique industry requirements, business units and processes, and then immediately deploy the changes to end-users on iOS or Android phones and tablets.

Powered by Kony MobileFabric, the enterprise mobile back-end services platform, has also been extended with the addition of a brand new App Services layer that enables IT to power these model-driven applications and allows them to be configured and deployed to the cloud. It enables rapid customization, automatic upgrades and versioning, and significantly lower total cost of ownership (TCO) for ongoing app maintenance.
Enterprises are looking for ways to empower their businesses to rapidly deliver secure, enterprise-level mobile apps with great user experiences.

"We are really excited about our partnership with Kony and our presence in the Kony Marketplace," said Debjani Deb, CEO and co-founder of ZineOne, a real-time mobile messaging platform. "Our solution helps businesses increase conversions on mobile by instrumenting their app with our light-weight, easy-to-use SDK. This enables them to actually have real-time conversations with their customers within the app itself to enhance experience and increase engagement."

“Knack Systems is happy to partner with Kony to bring enterprise mobility solution to its customers. Organizations currently using SAP solutions will be able to quickly empower their mobile workforce by leveraging Kony’s flexible mobile platform and solutions fully integrated with their SAP ERP and CRM solutions,” said George Kaadi, Managing Director Client Services and CIO Advisory, Knack Systems.  “Knack Systems is a niche consulting firm with experience in SAP and Kony technologies that helps customers to enable their mobile workforce to be more efficient and provide better customer experience.”

As enterprises adopt more of a strategic approach to mobility, they change the way they do business, not just attach new front ends to business services, says Forrester's Hammond.

Developers that bring the most context to the mobile app and associated processes wins, said Hammond at Kony World. Think mobile-first, but make sure it’s part of a true enterprises mobility strategy, including the inout from both IT and business, he said.

Looking to the future, Kony expects even more end-points to enter the picture -- from wearables and the Internet of Things -- and need to be addressed with a rapid app development capability. Forrester agrees.

"Expect with wearables a shift from mobile moments to micro moments to hold a user’s attention," says Hammond.

Yet even as the complexity around mobility increases, enterprises are still confronted with the need to get their essential mobile apps to market faster, to modernize their mobile apps lifecycle, and to gain and embed the ability to constantly revise and adjust mobile apps amid myriad back-end services and APIs.

It's into this opportunity that Kony is focused and building global momentum, said Hogan in summing up the conference.

You may also be interested in: