Wednesday Mar 04, 2015

All Data as a Service (DaaS/BDaaS) - Who's Your D-a-a-S Enabler?

There are three primary and distinct roles to consider, whether you're building or buying DaaS - regardless of the type or characteristics of data that's being exchanged; big data, open data, fast data, IoT/IoE data, metadata, microdata, multimedia content, structured, non-structured, semi-structured...ALL DATA.

The DaaS Consumer - who needs not only to acquire data from somewhere (in a way that shields them from the underlying technology concerns), but also then may use it to develop information apps and services, or repackage the data to share further with others.  The consumer assigns and realizes value from the service.

The DaaS Provider - who actually builds, markets and operates the business service and categorized storefront (or catalog), and brokers or stewards the data quality & availability, data rights, licenses and usage agreements between the consumers and the original data owners.  The provider creates, shapes and deploys the opportunities for value-enablement of specific data assets.

IT Services Management  - who design, implement and operate the information and data management infrastructure the DaaS Provider relies upon - and manage the IT component and services portfolio this infrastructure includes. For example the databases, virtualization technologies, data access services, storage and middleware capabilities. (Note that "IT Services Management" may be a wholly 3rd-party role, as well as a role within the DaaS Consumer or Provider organizations - there may be 3 or more IT Services Management domains).

There's also a less distinct, more broadly relevant role - the DaaS Enabler. a.k.a. the "Enterprise Architect", which can be a person, a role, or an organizational capability. The EA scope includes a heavy focus on enterprise "universal" information management and governance, infused (particularly in the Public Sector) with the currently vogue philosophies of SOA, Open Data, Mobility, Privacy-by-Design (PbD) and Cloud Computing. (Note that DaaS does not have to be delivered via a "cloud" deployment model - it's equally-applicable delivered as a private data services virtualization platform, for example).

[Read More]

Tuesday Mar 25, 2014

Public Sector Open Data via Information Sharing and Enterprise Architecture

Recent government policies and public demand for open data is rapidly exposing both opportunities and challenges within government information-sharing environments, behind the firewall - in turn a fantastic opportunity and challenge for the Enterprise Architects and Data Management organizations.


[Read More]

Wednesday Jul 24, 2013

The Chief Marketing Technology Officer - CMTO - and the EA

The Chief Marketing Technology Officer (CMTO) is recently an often-proposed role, that combines the interactive marketing savvy and experience of a Chief Marketing Officer (CMO) and the traditional information technology operations, management and investment knowledge of a CIO or CTO. More and more often, digital marketing requirements of an organization need a healthy integration of both marketing and IT skills. A good deal of the CMTO/CMO's "enterprise" scope to address is actually outside of their organization, i.e. dealing with Internet-based services, tools or 3rd-party sourced data and information.  This expanded, external scope can effectively, and should be addressed by the Enterprise Architect.[Read More]
About

This blog is written and maintained by the Oracle Public Sector Enterprise Architecture & Strategy Community. We are senior Enterprise Architects across Canada and the United States dedicated to helping public sector customers use the discipline of enterprise architecture to turn strategy into successful execution.

Search

Archives
« May 2015
SunMonTueWedThuFriSat
     
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
      
Today