Mitch and I will deliver the core of this presentation as if you were the customer. At the end Mitch will talk a little more about how to leverage this PPT as a tool with your customers.
これで4つのディメンションを見てきました...
分析プラットフォームの要件を見てみましょう。
横軸は、小規模から大規模のアナリティクスデプロイメントのサイズを示しています。
縦軸は、ビジネス主導のセルフサービスをITマネージドサービスとして分析した結果を示しています。 ITは他の部門のパートナーであり、ITの内部顧客です。規模を上げるにつれて、分析機能はより洗練され、ITによる管理が必要になります。そのため、ITは分析機能をビジネスパートナーにサービスとして提供する必要があります。だからこそ、ビジネスはセルフサービスを主導し、トップはビジネスの洗練された分析でしたが、ITによって管理されていました。
小規模な導入では、ITの介入はほとんど必要なく、ビジネスユーザーはセルフサービスの発見が不可欠です。
次のセクションは、展開が進むにつれて、より洗練された統制された分析を意味します。各セクションには、前のセクションの機能が含まれています。
最後に、大規模な展開では、プロアクティブな分析とシナリオのモデリングが追加されます。
============================================ ==============
X軸は、ユーザー数の観点から展開のサイズを定義します。
Y軸は、ビジネス主導のセルフサービス分析とIT提供のサービスとしての分析の間の連続性を定義します。 IT関連については以下を参照してください。
DVCSは小規模な展開のためのもので、チームや部門がITに依存することなく分析自体を所有していることがよく見られます。 Oracleは環境を管理します。
BICSは、より高度な分析ソリューションを必要とする中規模の導入向けです。このような意味で、ビジネスはそれ自体では完全には機能せず、セマンティック層のようなものを管理するためにITを必要とします。 Oracleは環境を管理します。
OACは、ITがお客様の管理下にある展開を所有する大規模な展開用です。顧客管理により、IT部門が分析を展開/管理/管理する方法の柔軟性が向上します。 IT部門がOACプラットフォームを管理することで、アナリティクスを他の組織のサービスとして提供することができます。
大きなサークルのそれぞれは、小さなサークルによって導入されたすべての機能を提供します。各ソリューションは以前のソリューションをベースに構築されています。それぞれは、データ視覚化から統制されたメトリックとダッシュボード、高度な分析、シナリオのモデリングに至るまで、OACで終わる別のレベルの分析を導入します。
IT自体は2つのモードで動作します(バイモーダルITではありません)。
財務やマーケティングと異なり、分析を消費する部門ではなく、分析自体を必要とする部門です。
IT部門は、ハードウェアまたはネットワーク機能のサービスを提供するのとは異なり、他の部門にも分析機能を提供します。ここでIT部門は、他の部門にサービスとしての分析を提供します。
Now that we’ve seen the 4 dimensions…
Lets take a look at the requirements of an analytic platform.
The horizontal axis shows the size of your analytics deployment small to large.
The vertical axis shows the business led self-service through to IT managed analytics-as-a-service. IT is a partner to the other departments, they are IT’s internal customer. As we move up the scale the analytics capabilities become more sophisticated and require more management by IT, hence IT is required to provide those analytic capabilities as a service to their business partners. So at the bottom, its business led self-service, and at the top its sophisticated analytics for the business but managed by IT.
With a small deployment, little IT intervention is required and business users are primary need is self-service discovery.
The next section as we grow, means a larger deployment and more sophisticated and governed analytics. Each section of course includes the capabilities of the prior sections.
Finally, larger deployments add proactive analytics and scenario modeling.
================================================================
The X-Axis, defines the size of the deployment in terms of number of users.
The Y-Axis defines the continuum between business led self-service analytics and IT provided analytics-as-a-service. See below for IT context.
DVCS is for smaller deployments that most often see teams or departments owning the analytics themselves without reliance on IT. Oracle manages the environment.
BICS is for medium deployments that require a more sophisticated analytics solution. As such the business cannot operate entirely on its own requiring IT to manage things like the semantic layer. Oracle manages the environment.
OAC is for larger deployments where IT will own the deployment as it is customer managed. Customer managed introduces more flexibility to how IT can deploy/manage/administrate their analytics. With IT managing their OAC platform they can provide analytics as a service to the rest of the organization.
Each of the larger circles provides all of the capabilities introduced by the smaller circles. Like Russian dolls each solution builds on the previous solution(s). Each introducing another level of analytics ending with OAC that provides everything from data visualization, through to governed metrics and dashboards to advanced analytics and scenario modeling.
IT itself acts in 2 modes (not bi-modal IT!);
a department that requires analytics itself, not unlike finance or marketing where it consumes the analytics.
IT also provides the capability of analytics to other departments not unlike providing the service of hardware or network capabilities. Here IT provides analytics-as-a-service to the other departments.
Oracle provides a solution everyone. Whichever quarter circle you fit into you have the capabilities and deployment choices you need. As you grow you can easily expand into the next level without any loss of work or content.
We have the DVCS for business led groups wanting visualization on any of their data sources.
We have BICS, which includes DV, but adds a semantic layer that adds that level of governance and control.
Finally we have the OAC, which provides all capabilities from the previous 2, and adds mobility with Day-by-day and scenario modelling with Essbase.
================================================
The X-Axis, defines the size of the deployment in terms of number of users.
The Y-Axis defines the continuum between business led self-service analytics and IT provided analytics-as-a-service. See below for IT context.
DVCS is for smaller deployments that most often see teams or departments owning the analytics themselves without reliance on IT. Oracle manages the environment.
BICS is for medium deployments that require a more sophisticated analytics solution. As such the business cannot operate entirely on its own requiring IT to manage things like the semantic layer. Oracle manages the environment.
OAC is for larger deployments where IT will own the deployment as it is customer managed. Customer managed introduces more flexibility to how IT can deploy/manage/administrate their analytics. With IT managing their OAC platform they can provide analytics as a service to the rest of the organization.
Each of the larger circles provides all of the capabilities introduced by the smaller circles. Like Russian dolls each solution builds on the previous solution(s). Each introducing another level of analytics ending with OAC that provides everything from data visualization, through to governed metrics and dashboards to advanced analytics and scenario modeling.
IT itself acts in 2 modes (not bi-modal IT!);
a department that requires analytics itself, not unlike finance or marketing where it consumes the analytics.
IT also provides the capability of analytics to other departments not unlike providing the service of hardware or network capabilities. Here IT provides analytics-as-a-service to the other departments.
Lets now look at a company that has truly leveraged exploration with Oracle: Valdosta State University.
Voldosta Implemented Oracle Business Intelligence Enterprise Edition to provide more than 600 faculty and staff members with rich insight into student academic performance
They now use BI Cloud service and Provided instant, on-demand access to student class loads and grades to enable faculty to make important timely decisions on how to facilitate student success.
They use Interactive dashboards to improve administrative productivity by more than 500% by enabling administrative staff to fulfill 90% of all data requests from faculty, department heads, deans, and others.
Oracle has Enabled the university to examine granular data to draw previously unknown correlations to make more informed decisions—for example, determining that students who eat breakfast on campus have a 10% higher retention rate!
They Streamlined IT responsibilities and cut database administration time in half, enabling database administrators and programmers to focus on core tasks, such as implementing new web applications, exploring new technologies, and building new Innovative analytic reports
Recently purchased BICS
{INFO BELOW FROM Http://www.oracle.com/us/corporate/customers/customersearch/vsu-1-endeca-ss-2156270.html}
Oracle BI SE one
http://docs.oracle.com/cd/E55108_01/doc.62016/e56762/GUID-46C06986-CCBC-4153-B261-01F6D60CC929.htm#FMWLC-GUID-9CBC1192-88FC-47B9-A65C-FECA40F59A41
初年度費用 初年度5人 次年度費用 次年度5人
Oracle Business Intelligence Standard Edition One Named User Plus ¥175,680 ¥878,400 ¥31,680 ¥158,400
Data Visualization Cloud Service Named User Plus ¥108,000 ¥540,000 ¥108,000 ¥540,000
初年度5人 次年度5人
合計 ¥1,418,400 ¥698,400
Mitch: Thanks Barry, now that concludes the positioning for OAC. Lets review it to go over some important points about the sections. If you take a look at the slide sorter and view the total slide deck, you will see a large appendix of additional content. Again that is so you can tailor your presentation in the way it makes sense for your situation.
There are 3 or more options for delivery of this deck.
Introduction – seminar, or a customer’s first intro to OAC.
Overview – more detailed, with the detailed section slides we presented today and…
Product need specific overview – adding or removing slides to meet the focus of the customer – need more Essbase focus? You delete some of the standard Viz slides and add additional Essbase centric slides from the appendix to each section. Most of the marketing and challenge statement slides would be removed for a more specific meeting. This can easily be the positioning overview before diving into features and details specifically for Essbase, or DV, or BICS, or Cloud in general.
So having said that, we will now turn it over to Vasu to discuss competitive positioning with OAC, specifically when competing with Microsoft.