Author: Hyoun Park

When we started Amalgam Insights, we oh-so-cleverly chose the AI initials with the understanding that artificial intelligence (the other AI…), data science, machine learning, programmatic automation, augmented analytics, and neural inputs would lead to the greatest advances in technology. At the same time, we sought to provide practical guidance for companies seeking to bridge the gaps between their current data and analytics environments and the future of AI. With that in mind, here are 8 predictions we’re providing for 2020 for Analytics Centers of Excellence and Chief Data Officers to keep in mind to stay ahead while remaining practical.

1. In 2020, AI becomes a $50 billion market, creating a digital divide between the haves and have nots prepared to algorithmically assess their work in real time. Retail, Financial Services, and Manufacturing will be over half of this market.

2. The data warehouse becomes less important as a single source of truth. Today’s single source replaces data aggregation and duplication with data linkages and late-binding of data sources to bring together the single source of truth on a real-time basis. This doesn’t mean that data warehouses aren’t still useful; it just means that the single source of truth can change on a real-time basis and corporate data structures need to support that reality. And it becomes increasingly important to conduct analytics on data, wherever the data may be, rather than be dependent on the need to replicate and transfer data back to a single warehouse.

3. Asking “What were our 2020 revenues?” will be an available option in every major BI solution by the end of 2020, with the biggest challenge then being how companies will need to upgrade and configure their solutions to support these searches. We have maxed out our ability to spread analytics through IT. To get beyond 25% analytics adoption in 2020, businesses will need to take advantage of natural language queries and searches are becoming a general capability for analytics, either as a native or partner-enabled capability.

4. 2020 will see an increased focus on integrating analytics with automation, process mapping, and direct collaboration. Robotic Process Automation is a sexy technology, but what makes the robots intelligent? Prioritized data, good business rules, and algorithmic feedback for constant improvement. When we talk about “augmented analytics” at Amalgam Insights, we think this means augmenting business processes with analytic and algorithmic logic, not just augmenting data management and analytic tasks.

5. By 2025, analytic model testing and Python will become standard data analyst and business analyst capabilities to handle models rather than specific data. Get started now in learning Python, statistics, an Auto Machine Learning method, and model testing. IT needs to level up from admins to architects. All aspects of IT are becoming more abstracted through cloud computing, process automation, and machine learning. Data and analytics are no exception. Specifically, Data analysts will start conducting the majority of “data science” tasks conducted in the enterprise, either as standalone or machine-guided tasks. If a business is dependent on a “unicorn” or a singular talent to conduct a business process, that process is not scalable and repeatable. As data science and machine learning projects start becoming part of the general IT portfolio, businesses will push down more data management, cleansing, and even modeling and testing tasks to the most dependable talent of the data ecosystem, the data analyst.

6. Amalgam Insights predicts that the biggest difference between high ROI and low ROI analytics in 2020 will come from data polishing, not data hoarding. – The days of data hoarding for value creation are over. True data champions will focus on cleansing, defining, prioritizing, and separating the 1% of data that truly matters from the 99% more suited to mandatory and compliance-based storage.

7. On a related note, Amalgam Insights believes the practice of data deletion will be greatly formalized by Chief Data Protection Officers in 2020. With the emergence of CCPA along with the continuance of GDPR, data ownership is now potentially risky for organizations holding the wrong data.

8. The accounting world will make progress on defining data as a tangible asset. My expectations: changes to the timeframes of depreciation and guidance on how to value specific contextually-specific data such as customer lists and business transactions. Currently, data cannot be formally capitalized, meaning asset. Now that companies are generally starting to realize that data may be their greatest assets outside of their talent, accountants will bring up more concerns for FASB Statements 141 and 142.

In this blog post series, Amalgam Insights is providing a practical model for businesses to plan the ethical governance of their AI projects.

To read the introduction, click here.

To read about Stage 1: Executive Design, click here

This blog focuses on Technical Development, the second of the Three Keys to Ethical AI described in the introduction.

Figure 1: The Three Keys to Ethical AI

Stage 2: Technical Development

Technical Development is the area of AI that gets the most attention as machine learning and data science start to mature. Understandably, the current focus in this Early Adopter era (which is just starting to move into Early Majority status in 2020) is simply on how to conduct machine learning, data science efforts, and potentially deep learning projects in a rapid, accurate, and potentially repeatable manner. However, as companies conduct their initial proofs of concepts and build out AI services and portfolios, the following four questions are important to take into account.

• Where does the data come from?
• Who is conducting the analysis?
• What aspects of bias are being taken into account?
• What algorithms and toolkits are being used to analyze and optimize?

Figure 2: Technical Development

Where does the data come from?

Garbage In, Garbage Out has been a truism for IT and data projects for many decades. However, the irony is that much of the data that is used for AI projects used to literally be considered “garbage” and archival exhaust up until the practical emergence of the “Big Data” era at the beginning of this decade. As companies use these massive new data sources as a starting point for AI, they must check on the quality, availability, timeliness, and context of the data. It is no longer good enough to just pour all data into a “data lake” and hope that this creates a quality training data sample.

The quality of the data is determined by the completeness, accuracy, and consistency of the data. If the data have a lot of gaps, errors, or significant formatting issues, the AI will need to account for these issues in a way that maintains trust. For instance, a long-standing historical database may be full of null values as the data source has been augmented over time and data collection practices have improved. If those null values are incorrectly accounted for, AI can end up defining or ignoring a “best practice” or recommendation.

From a practical perspective, consider as an example how Western culture has recently started to formalize non-binary gender or transgendered identity. Just because data may not show these identities prior to this decade does not mean that these identities didn’t exist. Amalgam Insights would consider a gap like this to be a systemic data gap that needs to be taken into account to avoid unexpected bias, perhaps through the use of adversarial de-biasing that actively takes the bias into account.

The Availability and Timeliness of the data refers to the accessibility, uptime, and update frequency of the data source. Data sources that may be transient or migratory may serve as a risk for making consistent assumptions from an AI perspective. If an AI project is depending on a data source that may be hand-curated, bespoke in nature, or inconsistently hosted and updated, this variability needs to be taken into account in determining the relative accuracy of the AI project and its ability to consistently meet ethical and compliance standards.

Data context refers to the relevance of the data both for solving the problem and for providing guidance to downstream users. Correlation is not causation, as the hilarious website “Spurious Correlations” run by Tyler Vigen shows us. One of my favorite examples shows how famed actor Nicolas Cage’s movies are “obviously” tied to the number of people who drown in swimming pools.

Figure 3: Drownings as a Function of Nicolas Cage Movies

(Thanks to Spurious Correlations! Buy the book!)

But beyond the humor is a serious issue: what happens if AI assumptions are built on faulty and irrelevant data? And who is checking the hyperparameter settings and the contributors to parameter definitions? Data assumptions need go through some level of line of business review. This isn’t to say that every business manager is going to suddenly have a Ph.D. level of data science understanding, but business managers will be able to either provide confirmation that data is relevant or provide relevant feedback on why a data source may or may not be relevant.

Who is conducting the analysis?

In this related question, the deification of the unicorn data scientist has been well-documented over the last few years. But just as business intelligence and analytics evolved from the realm of the database master and report builder to a combination of IT management and self-service conducted by data-savvy analysts, data science and AI must also be conducted by a team of roles that include the data analyst, data scientist, business analyst, and business manager. In small companies, an individual may end up holding multiple roles on this team.

But if AI is being developed by a single “unicorn” focused on the technical and mathematical aspects of AI development, companies need to make sure that the data scientist or AI developer is taking sufficient business context into account and fully considering the fundamental biases and assumptions that were made during the Executive Design phase.

What aspects of bias are being taken into account?

Any data scientist with basic statistical training will be familiar with Type I (false positive) and Type II (false negative) errors as a starting point for identifying bias. However, this statistical bias should not be considered the end-all and be-all of defining AI bias.

As parameters and outputs become defined, data scientists must also consider organizational bias, cultural bias, and contextual bias. Simply stating that “the data will speak for itself” does not mean that the AI lacks bias; this only means that the AI project is actively ignoring any bias that may be in place. As I said before, the most honest approach to AI is to acknowledge and document bias rather than to simply try to “eliminate” bias. Bias documentation is a sign of understanding both the problem and the methods, not a weakness.

An extreme example is Microsoft’s “Tay” chatbot released in 2016. This bot was released “without bias” to support conversational understanding. The practical aspect of this lack of bias was that the bot lacked the context to filter racist messages and to differentiate between strongly emotional terms and culturally appropriate conversation. In this case, the lack of bias led to the AI’s inability to be practically useful. In a vacuum, the most prevalent signals and inputs will take precedence over the most relevant or appropriate signals.

Unless the goal of the AI is to reflect the data that is most commonly entered, an “unbiased” AI approach is generally going to reflect the “GIGO” aspect of programming that has been understood for decades. This challenge reflects the foundational need to understand the training and distribution of data associated with building of AI.

What algorithms and toolkits are being used to analyze and optimize?

The good news about AI is that it is easier to access than ever before. Python resources and a plethora of machine learning libraries including PyTorch, Scikit, Keras, and, of course, Tensorflow, make machine learning relatively easy to access for developers and quantitatively trained analysts.

The bad news is that it becomes easy for someone to implement an algorithm without fully understanding the consequences. For instance, a current darling in the data science world is XGBoost (Extreme Gradient Boosting) which has been a winning algorithmic approach for recent data science contests because it reduces data to an efficient minima more quickly than standard gradient boosting. But it also requires expertise in starting with appropriate features, stopping the model training before the algorithm overtunes, and appropriately fine tuning the model for production.

So, it is not enough to simply use the right tools or the most “efficient” algorithms, but to effectively fit, stop, and tune models based on the tools being used to create models that are most appropriate for the real world and to avoid AI bias from propagating and gaining overweight influence.

In our next blog, we will explore Operational Deployment with a focus on the line of business concerns that business analysts and managers consider as they actually use the AI application or service and the challenges that occur as the AI logic becomes obsolete or flawed over time.

In this blog post series, Amalgam Insights is providing a practical model for businesses to plan the ethical governance of their AI projects. To read the introduction, click here.

This blog focuses on Executive Design, the first of the Three Keys to Ethical AI introduced in the last blog.

Stage I: Executive Design

As a starting point, any AI project needs to be analyzed in context of five major questions that are important both from a project management and scoping perspective. Amalgam Insights cannot control the ethical governance of every company, but we can provide a starting point to let AI-focused companies know what potential problems they face. As a starting point, businesses seeking to pursue ethical AI must consider the following questions:

• What is the goal of the project?
• What are the key ethical assumptions and biases?
• Who are the stakeholders?
• How will AI oversight be performed in an organization?
• Where is the money coming from?

What is the project goal?

In thinking about the goal of the project, the project champion needs to make sure that the goal, itself, is not unethical. For instance, the high-level idea of understanding your customers is laudable at its surface. But if the goal of the project is effectively to stalk customers or to open up customer data without their direct consent, this project quickly becomes unethical. Likewise, if an AI project to improve productivity and efficiency is practically designed to circumvent legal governance of a process, there are likely ethical issues as well.

Although this analysis seems obvious, the potential opacity, complexity, and velocity of AI deployments mean that these topics have to be considered prior to project deployment. These tradeoffs need to be analyzed based on the risk profile and ethical policies of the company and need to be determined at a high level prior to pursuing an AI project.

What are the key ethical assumptions and biases?

Every AI project has ethical assumptions, compromises, and biases.

Let me repeat that.

Every AI project has ethical assumptions, compromises, and biases.

This is just a basic premise that every project faces. But because of the complexities of AI projects, the assumptions made during scoping can be ignored or minimized during the analysis or deployment if companies do not make a concerted effort to hold onto basic project tenants.

For instance, it’s easy to say that a company should not stalk its customers. And in the scoping process, this may mean masking personal information such as names and addresses from any aggregate data. But what happens if the analysis ends up tracking latitude and longitude to within 1 meter, tracking interactions every 10 minutes, and taking ethnic, gender, sexuality, or other potentially identifying or biasing data along with a phone IMEI identification into account as part of an analysis of the propensity to buy? And these characteristics are not taken into account because they weren’t included as part of the initial scoping process and there was no overarching reminder to not stalk or overly track customers? In this case, even without traditional personally identifiable information, the net result is potentially even more invasive. And with the broad scope of analysis conducted by machine learning algorithms, it can be hard to fully control the potential parameters involved, especially in the early and experimental stages of model building and recursive or neurally designed optimization.

So, from a practical perspective, companies need to create an initial set of business tenets that need to be followed throughout the design, development, and deployment of AI. Although each set of stakeholders across the AI development process will have different means of interpreting and managing these tenets, these business guidelines provide an important set of goalposts and boundaries for defining the scope of the AI project. For instance, a company might set as a set of characteristics for a project:

• This project will not discriminate based on gender
• This project will not discriminate based on race
• This project will not discriminate based on income
• This project will not take personally identifiable information without first describing this to the user in plain English (or language of development)

These tenets and parameters should each be listed separately, meaning there shouldn’t be a legalese laundry list saying “this project respects race, class, gender, sexuality, income, geography, culture, religion, legal status, physical disability, dietary restrictions, etc.” This allows each key tenet to be clearly defined based on its own merit.

These tenets should be a part of every meeting and formal documentation so that stakeholders across executive, technical, and operational responsibilities all see this list and consider this list in their own activities. This is important because each set of stakeholders will execute differently on these tenets based on their practical responsibilities. Executives will place corporate governance and resources in place while technical stakeholders will focus on the potential bias and issues within the data and algorithmic logic and operational stakeholders will focus on delivery, access, lineage, and other line-of-business concerns associated with front-line usage.

And this list of tenets needs to be short enough to be actionable. This is not the place to write a 3,000 word legal document on every potential risk and problem, but a place to describe specific high-level concerns around bias.

Who are the stakeholders?

The makeup of the executive business stakeholders is an important starting point for determining the biases of the AI project. It is important for any AI project with significant potential organizational impact to have true executive sponsorship from someone who has responsibility for the health of the company. Otherwise, it is too easy for an algorithm to “go rogue” or become an implicit and accepted business enabler without sufficient due diligence.

How will AI oversight be performed in an organization?

AI projects need to be treated with the same types of oversight as hiring employees or any significant change management process. Ideally, AI will be either providing a new and previously unknown insight or supporting productivity that will replace or augment millions of dollars in labor. Companies putting AI into place need to hold AI logic to the same standards as they would hold human labor.

Where is the money coming from?

No matter what the end goal of the AI project is, it will always be judged in context of the money used to fund the AI. If an organization is fully funding an AI project, it will be held accountable for the outcomes of the AI. If an AI project is funded by a consortium of funders, the ethical background of each funder or purchaser will eventually be considered in determining the ethical nature of the AI. Because of this, it is not enough for an organization to be pursuing an AI initiative that is potentially helpful. Organizations must also partner with or work with partners that align with the organization’s policy and culture. When an AI project becomes public, compliance officers and critics will always follow the money and use this as a starting point to determine how ethical the AI effort is.

In our next blog, we will explore Technical Development with a focus on the key questions that technical users such as data analysts and data scientists must consider as they build out the architecture and models that will make up the actual AI application or service.

As we head into 2020, the concept of “AI (Artificial Intelligence) for Good” is becoming an increasingly common phrase. Individuals and organizations with AI skillsets (including data management, data integration, statistical analysis, machine learning, algorithmic model development, and application deployment skills) have effort into pursuing ethical AI efforts.

Amalgam Insights believes that these efforts have largely been piecemeal and inadequate to meet common-sense definitions for companies to effectively state that they are pursuing, documenting, and practicing true ethical AI because of the breadth and potential repercussions of AI on business outcomes. This is not due to a lack of interest, but based on a couple of key considerations. First, AI is a relatively new capability in the enterprise IT portfolio that often lacks formal practices and guidelines and has been managed as a “skunkworks” or experimental project. Second, businesses have not seen AI as a business practice, but as a purely technical practice and made a number of assumptions in skipping to the technical development that would typically not have been made for more mature technical capabilities and projects.

In the past, Amalgam Insights has provided frameworks to help organizations take the next step to AI through our BI to AI progression.

Figure 1: Amalgam’s Framework from BI to AI

 

 

 

To pursue a more ethical model of AI, Amalgam Insights believes that AI efforts need to be analyzed through three key lenses:

• Executive Design
• Technical Development
• Operational Deployment

Figure 2: Amalgam’s Three Key Areas for Ethical AI

In each of these areas, businesses must ask the right questions and adequately prepare for the deployment of ethical AI. In this framework, AI is not just a set of machine learning algorithms to be utilized, but an enabler to effectively augment problem-solving for appropriate challenges.

Over the next week, Amalgam Insights will explore 12 areas of bias across these three categories with the goal of developing a straightforward framework that companies can use to guide their AI initiatives and take a structured approach to enforcing a consistent set of ethical guidelines to support governance across the executive, technical, and operational aspects of initiating, developing, and deploying AI.

In our next blog, we will explore Executive Design with a focus on the five key questions that an executive must consider as they start considering the use of AI within their enterprise.

Key Stakeholders: Chief Information Officer, Chief Financial Officer, Chief Accounting Officer, Controllers, IT Directors and Managers, Enterprise Mobility Directors and Managers, Networking Directors and Managers, Software Asset Directors and Managers, Cloud Service Directors and Managers, and other technology budget holders responsible for telecom, network, mobility, SaaS, IaaS, and IT asset and service expenses.

Why It Matters: The race for IT spend management consolidation continues. The financial management of IT is increasingly seen as a strategic advantage for managing the digital supply chain across network, telecom, wireless, cloud, software, and service portfolios.

Top Takeaway: The new combined business with over 800 employees, 3,500 customers, and an estimated 2 million devices and $20 billion under management both serves as legitimate competition for market leader Tangoe and an attractive potential acquisition for larger IT management vendors.

[Disclaimer: Amalgam Insights has worked with Calero and MDSL. Amalgam Insights has provided end-user inquiries to both Calero and MDSL customers. Amalgam Insights has provided consulting services to investors and advisors involved in this acquisition.]
Continue reading TEM Market Leaders Calero and MDSL Merge as Global IT Spend Management Consolidation Continues

(Note: This blog was co-written by Hyoun Park and Larry Foster, an Enterprise Technology Management Association Hall of Famer and an executive who has shaped the Technology Expense Management industry. Please welcome Larry’s first contribution to Amalgam Insights!)

On August 22, 2019, Upland Software announced the acquisition of Cimpl (f.k.a. Etelesolv), a Montreal-based telecom expense management platform that was the market leader in the Canadian market and had expanded into the United States market. With this acquisition, Cimpl will become a part of Upland’s Project & Financial Management Solution Suite and add approximately $8 million in annual revenue.

Context for the Acquisition

The TEM (Technology Expense Management) industry has experienced a continual series of ebb-and-flow acquisitions/mergers over the past twelve years. The typical TEM acquisition/merger encompasses two or more independent entities within the realm of TEM, WEM (Wireless Expense Management) or MMS (Managed Mobility Services) merging to create a more comprehensive expense management solution portfolio with superior global delivery capabilities.

The reality is that many of these mergers are driven by economic reasons where one or both entities can reduce overhead by eliminating duplicate services. Overhead is eliminated by unifying back-office operations and amalgamating technology platforms. These types of consolidation mergers are typical in a maturing industry that is eventually dominated by a few leading solution providers representing the majority of market share. All of the leading TEM solution providers including Tangoe, MDSL and Calero encompass a long history of multiple “like-minded mergers”.

Cimpl as an outlier in the TEM market

Until this recent acquisition, Cimpl has maintained the persona of the independent dark horse of the TEM industry quietly residing in Quebec, Canada refining its multi-tenant cloud platform and progressively building its market share.

Unlike most TEM managed service solution providers, Cimpl has decided to focus on being mainly a pure software company and providing a white-label technology platform for its delivery partners. In early 2018 CIMPL stealthily started to expand its physical presence into the United States. Since its inception, Cimpl has continued to progressively achieve conservative incremental success and stay profitable in contrast to a number of TEM vendors that have gone through boom-or-bust cycles driven by external funding (or the lack thereof).

The Challenge for TEM

The traditional acquisition playbook is preventing the TEM industry from being recognized as a strategic asset by organizations. Nonetheless, the TEM industry is experiencing a dramatic paradigm shift as organizations continue to replace legacy communication services with the ever-growing spectrum of cloud-based services. Traditionally, TEM solutions have focused on validating the integrity of invoice charges across multiple vendors prior to payment and allocating expenses to the respective cost centers leveraging the leased service. Enterprises derive value from TEM solutions by enabling a centralized ICT (Information and Communications Technology) shared service to automate the lifecycle from provisioning through payment and managing the resolution of disputed invoice charges for essentially static services.

However, as organizations adopt more ephemeral cloud services that encompass multi-vendor private, public and hybrid leased environments for compute, storage, API-enabled integrations, connectivity, input/output, and telecommunications, the purpose of the centralized ICT business operation is being transformed from managing daily operations to a fiduciary broker focused on optimizing technology investments. Unlike the recurring charges that represent the majority of traditional telecom charges, cloud services are consumption-based, meaning that it’s the responsibility of the client user to deactivate and manage the appropriate configuration of contracted services based on statistical analysis and forecast of the actual usage.

In the world of cloud, the provisioning activities such as activations, changes, and deactivations are done “on-demand,” completely independent from the ICT operation. The primary focus of ITEM solutions is to manage recurring and non-recurring invoice charges in arrears. As ICT operations evolve into technology brokers, they need real-time insight underpinned by ML and AI algorithms that make cost optimization recommendations to add, consolidate, change or deactivate services based on usage trends.

Why the CIMPL acquisition will help Upland

This context brings us to the real ingenuousness of the Cimpl acquisition. In the typical quiet financial days of August when everyone is away on vacation, Upland Software announced an accretive acquisition of Cimpl with a purchase price of $23.1M in cash and a $2.6M cash holdback payable in 12 months. Upland expects the acquisition to generate annual revenue of approximately $8M, of which $7.4M is recurring. The keyword buried within all of those financial statistics is “accretive” which means their strategy is to help increase natural growth.

Upland already has an impressive complementary portfolio of profitable software solutions. A closer look at the acquisition of Cimpl shows how Upland is formulating a solution strategy to manage all aspects of the Information and Communication Technology business operations.

The strategic value of the Cimpl acquisition becomes very clear when you recognize that Upland is the first company to combine an IT Financial Management platform (ITFM), ComSci, with an IT Expense Management-based solution (ITEM), Cimpl. Upland already owns additional complementary solutions such as a document and workflow automation, a BI platform, customer engagement platform, and a knowledge-based platform. With these components, Upland is working to create an industry-leading ERP-type solution framework to automate, manage, & rationalize all aspects of ICT business operations.

Although both ITFM and ITEM support the ICT business operations, they focus on different aspects. ITFM is predominately used on the front end to manage budgets and on a monthly basis to support internal billing/chargeback activities and leveraged by the IT CFO office whereas ITEM solutions like Cimpl are used by analysts and operational managers because they focus on managing the high volumes of transactional operations and data throughout the month, including provisioning and payment of leased services such as both landline and mobile communication services and now the ever-expanding array of cloud services.

Looking Forward: Our Recommendations

In this context, take the following recommendations into account based on this acquisition.

Expect other leading TEM, ITFM, CEM/CMP (Cloud Expense Management and Cloud Management Platform) solution providers to develop competitive solution frameworks that bring multiple IT categories together from a finance and expense management perspective.

ICT managers need to evolve and transform their solution to due diligence approach beyond pursuing and leveraging independent ITFM, ITEM, CEM/CMP solutions to choosing solutions with comprehensive IT management frameworks. As IT continues to become increasingly based on subscriptions, project-based spend, and on-demand peak usage across a variety of categories, ICT managers should aim towards having a single management control plane for finance and expenses rather than depend on a variety of management solutions

Real-time management is the future of IT expense management. The next levels of operational efficacy will be underpinned by more comprehensive real-time insight that helps organizations understand the most optimal way to acquire, configure and consume inter-related cloud services and pay their invoices. This will require insights on usage, project management, service management and real-time status updates associated with expense and finance. By combining financial and operational data, ICT managers will have greater insights into the current and ongoing ROI of technology under management.

(Editor’s Note: This week, Tom Petrocelli and Hyoun Park will be blogging and tweeting on key topics at VMworld at a time when multi-cloud management is a key issue for IT departments and Dell is spending billions of dollars. Please follow our blog and our twitter accounts TomPetrocelli, Hyounpark, and AmalgamInsights for more details this week as we cover VMworld!)

As Amalgam Insights prepares to attend VMworld, it is an especially interesting time from both an M&A and a strategic perspective as VMware completes acquisitions of its sibling company Pivotal and end-user security startup Carbon Black. As these acquisitions are in progress and Amalgam Insights has the opportunity to question executives at the top of Dell Technologies, including Pat Gelsinger and Michael Dell, Amalgam Insights will be looking forward to answers to the following questions:

1. How will VMware accelerate Pivotal’s growth post-acquisition? Back in 2013 when Pivotal was first founded, I stated in an interview that

“Pivotal is the first application platform that combines cloud, Big Data, and rapid application development and it represents a fundamental shift in enterprise IT. By creating an enterprise-grade Big Data application platform, Pivotal has the opportunity to quickly unlock value from transactional data that has traditionally been archived and ignored without requiring a long period of up training, integration, and upfront development time.”

 

The potential for Pivotal was immense. Even in light of The Death of Big Data, Pivotal still has both the toolkits and methodology to support intelligent analytic and algorithm-based application architectures at a time when VMware needs to increase its support there in light of the capabilities of IBM-Red Hat, Oracle, and other competitors. We’re looking forward to getting some answers!

2. How will the Carbon Black acquisition be integrated into VMware’s security and end-user computing offerings? Carbon Black is a Boston-area security startup focused on discovering malicious activity on endpoints and will be a strong contributor to WorkspaceONE as VMware seeks to manage and secure the mobile-cloud ecosystem. And along with NSX Cloud for networking and CloudHealth Technologies for multi-cloud management, Carbon Black will help VMware to tell a stronger end-to-end cloud story. But the potential and timeline for integration will end up defining the success of this 2 billion+ dollar acquisition.

3. Where does CloudHealth Technologies fit into VMware’s multi-cloud management story? Although this 500 million dollar acquisition looked promising when it occurred last year, the Dell family previously invested in Enstratius to manage multi-cloud environments and that acquisition ended up going nowhere. What did VMware learn from the last time around and how will CloudHealth Technologies stay top of mind with all these other acquisitions going on?

4. Where is VMware going with its machine learning and AI capabilities for data center management? I can’t take credit for this one, as the great Maribel Lopez brought this up (go ahead and follow her on LinkedIn!). But VMware needs to continue advancing the Software-Defined Data Center and to ease client challenges in supporting hybrid cloud environments.

5. How is VMware bringing virtualization and Kubernetes together? With VMware’s acquisitions of Heptio and Bitnami, VMware has put itself right in the middle of the Kubernetes universe. But virtualization and Kubernetes are the application support equivalent of data center and cloud, two axes on the spectrum of what is possible. How will VMware simplify this componentization for clients who are seeking hybrid cloud help?

We’ll be looking for answers to these questions and more as we roam the halls of Moscone and put VMware and Dell executives to the test! Stay tuned for more!

On August 15, 2019, Incorta announced the closing of a $30 million Series C round led by Sorenson Capital and including participation from existing investors GV, Kleiner Perkins, M12 (formerly known as Microsoft Ventures), Telstra Ventures, & Ron Wohl. Incorta has raised $75 million in funding since its founding.

Incorta is an innovator in the enterprise analytics space because of its Direct Data  Mapping capabilities that allow organizations to build data warehouse-like organizational capabilities without having to create ETL jobs or data models. This allows organizations to massively accelerate their time to incorporate new data into analytic environments and represents one of the new paradigms in data and analytics that is getting organizations closer to the Holy Grail of supporting ubiquitous analytics. This approach also provides performance benefits associated with analytic queries compared to traditional database approaches to organizing large stores of data for analytic usage, such as columnar data queries.

This round of funding was validated by Incorta’s rapid recent growth, including 284% growth in revenue year-over year (including key deals in verticals such as financial services, retail, and manufacturing), 200 new employees added over the last six months with new offices in Chicago, Dubai, and Bangalore, and a strengthened marketing and sales partnership with Microsoft

Incorta is expected to use this funding to acquire top technical, sales, marketing, and operational talent, continue investing in current technologies, and work with  public cloud providers on supporting effective and efficient deployments.

Why It Matters

Enterprise analytics have gone through several generations of evolution, starting with the initial development of reporting on structured databases and ETL with the likes of Business Objects, Cognos, and Microstrategy , then continuing with the growth of self-service and data discovery driven by Qlik and Tableau, and then a variety of Big Data solutions including Hadoop, MongoDB, Oracle Exadata, and SAP HANA. We also saw a set of cloud BI solutions that accelerated the ability to create data models and star schemas, such as Birst, Power BI, and Oracle Analytics Cloud.

Although many of these technologies continue to be valid and effective ways to manage analytic access, we are entering a new era of analytics solutions seeking to accelerate analytic access and ubiquity not by simply improving current paradigms of data querying, modeling, and integration, but by fundamentally changing the way we access and structure analytic data by taking advantage of the cloud and modern methods of supporting complex data. Amalgam Insights believes that Incorta is an emerging game changer in the current era of analytics in its approach that actively avoids traditional data modeling and ETL in favor of a more direct approach of bringing data sources together and conducting analytics on the data. This approach is fundamentally important because it practically allows businesses to bring in new data sources as trusted analytic data without having to figure out the complexities of Kimball-esque data warehouse mapping.

With this round of funding, Amalgam Insights believes that Incorta is equipped to sell its unique approach to analytics to a larger audience. However, if the recent funding rounds of Looker, Thoughtspot, and Sisense are any indication, Incorta will likely look for at least one more round of funding either to support global marketing and selling efforts or to prepare for IPO. Either way, Amalgam Insights expects Incorta to continue its success as enterprise IT organizations seek a faster and more efficient way to continue bringing more data sources into their analytic environments. Amalgam Insights highly recommends Incorta as a solution for enterprise analytics departments struggling to keep up with the pace of readying new data sources for analytics. In addition, we recommend Incorta as a solution that is worth an initial free trial and sandbox installation even in mature and stable analytic environments to ensure that analytics teams are up to date with the Art of the Possible with modern analytic tools.

(Note: Amalgam Insights currently recommends Incorta, Looker, Microstrategy, Sisense, and Thoughtspot as analytic vendors with novel approaches for developing ubiquitous analytics.)

[Edited July 25th to reflect Mobile Solutions’ current public-facing offerings]

Key Takeaway: Mobile Solutions is providing Robotic Process Automation for Managed Mobility Services with a focus on mid-market enterprises and organizations. This capability provides Mobile Solutions with a starting point for handling basic service orders.

On July 10th, Mobile Solutions announced the launch of two Robotic Process Automation  (RPA) assistants named Maxine and Maximus Brain that are assisting with service orders entered into Mobile Solutions’ mobility management platform, MAX.

Maxine serves as Continue reading Mobile Solutions Launches New Robotic Process Automation Capabilities

On July 22, Microsoft announced a $1 billion investment in OpenAI, a lab focused on “artificial general intelligence,” or the goal of creating artificial intelligence with human-like observation and learning capabilities. With this announcement,  Microsoft becomes the “exclusive” cloud computing provider for OpenAI and will have access to productizing OpenAI capabilities as they come to market.

Key Takeaways: Microsoft makes a long-term investment in “general intelligence” to start on the next generation of AIs that will be coming to market in five-to-ten years and will be able to recoup some costs back as OpenAI’s cloud provider and monetizer of OpenAI technologies.

Continue reading Understanding Microsoft’s Investment in OpenAI