Results

Event Report: Dell's Annual Analyst Conference INDIA #DAACIndia 2013

Event Report: Dell's Annual Analyst Conference INDIA #DAACIndia 2013

This post comes from Sachin Gosavi, our Vice President for South Asia

A First Peek Into Dell’s Private Affair

Constellation Research attended the DAACIndia 2013 on 26 and 27 Sept 2013 in Bangalore. Having won the go-private mandate barely a fortnight ago, ‘The World’s Largest Start-up’ message  dominated the conference theme.  Alok Ohrie, President and Managing Director, Dell India, dedicated a sizable chunk of his keynote to sharing Dell’s focus and priorities post mandate (see Figure 1).  Moreover, Dell's India customers speaking on the panel expressed a sense of relief that the uncertainty had passed.

Figure 1. Dell Unveils It's World's Largest Startup Messaging to India

Source: Dell India

Dell’s Future Is “Transform, Connect, Inform, Protect”
Dell continues to weave together it’s global theme of “Transform-Connect-Inform-Protect” for its customers in India, and is making investments in areas such as delivering new services/solutions, footprint expansion and widening the sales coverage beyond tier-II cities, superior customer experience, and support. Clients in India will closely watch execution of these investments and strategy, as Dell India witnessed a leadership change earlier this year. The Dell India leadership and many of it’s BU leaders attempted a two-front pitch:

  1. Dell’s current India business and its roadmap, and
  2. Dell’s global play as an end-to-end player

Constellation’s Point Of View (India): In a market like India, strong relationships and footprint spanning major industrial/IT hubs play an important role in the enterprise tech space.  Dell has been a key player in the Indian enterprise market, especially in the server and storage space, and Constellation expects them to build further on that position.  Beyond the hardware play, Constellation sees Dell’s Services unit gaining traction with a segment of Indian buyers – both existing and net new – with its Business Applications and BPO services. That said, in  Services, Dell needs to focus more on it’s Business Innovation Services portfolio addressing disruptive technology trends such as Cloud, Mobility, Social, BigData-Analytics and UC.  For, as with every market, there exists a Market-leader and Fast-follower section of Indian CXOs that are willing to bet on these emerging technologies and newer engagement models.  Dell can benefit by finding organizations looking for innovation partners in their quest.

Constellation’s Point Of View (Global): DAACIndia was a reflection of Dell’s global plans to shape up into an ‘End-to-end’ technology player. The economic recession has forced business model shifts at the major technology companies, and Dell is no exception.  Be it hardware vendors, service providers, and software players,  all are vying for the largest share of the business and IT technology budget today. It was this market reality that prompted Dell to explore ways to reinvent itself, which demands taking risks and faster decision making. The Go-private mandate will not only bring in freedom and speed in decision making, it will also help Dell re-deploy the resources, the management bandwidth and focus needed to re-shape its business model.

The Bottom Line: Dell’s Privatization Efforts Open Up Opportunities For Buyers
Dell provided many proof points to validate its vision. More importantly, the Indian market can take advantage of the integrated approach Dell is providing across the stack.  Consequently, Constellation’s preliminary assessment includes the following advice to prospects and existing customers:

  1. Seek clarity on product road maps. As Dell enters privatization, Constellation expects Dell to re-organise a few of its businesses globally in the near term.  Buyers should seek clarity on key product road maps and investment priorities from Dell so they can adjust spending portfolios as needed.
  2. Explore how “Transform, Connect, Inform, and Protect” can apply to existing budgets. Determine what role Dell plays in the overall technology strategy.  With an end-to-end play in mind, Dell is aggressively pushing for cross-sell opportunities in existing accounts with new products and services. Clients exploring these new products and services of Dell must ask for vertical/domain specific use cases, rather than relying on mere features/benefits.
  3. Remain cautious. While market leaders and fast followers will most likely jump in to co-innovate with Dell, most customers and prospects will take a wait and see approach.  Why? Dell is at the beginning of its journey towards privatization.  Buyers should start with bite-sized entry points and work on expansion as Dell proves out its strategy and capabilities.

Your POV.

What’s your plan to invest with Dell?  Will Dell succeed as a private company in shoring up it's offerings? Add your comments to the blog or reach me via email: R (at) ConstellationR (dot) com or R (at) SoftwareInsider (dot) com.

Reprints

Reprints can be purchased through Constellation Research, Inc. To request official reprints in PDF format, please contact Sales .

Disclosure

Although we work closely with many mega software vendors, we want you to trust us. For the full disclosure policy, stay tuned for the full client list on the Constellation Research website.

* Not responsible for any factual errors or omissions.  However, happy to correct any errors upon email receipt.

Copyright © 2001 – 2013 R Wang and Insider Associates, LLC All rights reserved.
Contact the Sales team to purchase this report on a a la carte basis or join the Constellation Customer Experience!

Tech Optimization Data to Decisions Future of Work Innovation & Product-led Growth New C-Suite Event Report dell SoftwareInsider ML Machine Learning LLMs Agentic AI Generative AI Robotics AI Analytics Automation B2B B2C CX EX Employee Experience HR HCM business Marketing Metaverse developer SaaS PaaS IaaS Supply Chain Quantum Computing Growth Cloud Digital Transformation Disruptive Technology eCommerce Enterprise IT Enterprise Acceleration Enterprise Software Next Gen Apps IoT Blockchain CRM ERP Leadership finance Social Healthcare VR CCaaS UCaaS Customer Service Content Management Collaboration M&A Enterprise Service Executive Events Chief Information Officer Chief Procurement Officer Chief Supply Chain Officer Chief Executive Officer Chief Technology Officer Chief Data Officer Chief Digital Officer Chief Analytics Officer Chief Financial Officer Chief Operating Officer Chief Marketing Officer Chief Revenue Officer Chief Information Security Officer Chief Experience Officer

Exit Sandman – microcosm of supply chain failures in the Bronx

Exit Sandman – microcosm of supply chain failures in the Bronx

Those of you who are baseball fans know that the greatest closer in baseball – Mariano Rivera – retired from the game this season (mind you I am a diehard Red Sox fan so that was hard for me to write). Rivera was a model of consistency in excellence – since 1995 the pitcher known as the Sandman accumulated some gaudy statistics:

  • 652 saves
  •  2.21 ERA
  • 82 wins
  • 1173 strikeouts
  • 1.00 WHIP
  • Oh and 5 World Series rings

His post season statistics are at an even greater plateau of excellence:  0.70 ERA, 8 wins and 42 saves…and those 5 World Series titles. To honour his retirement the Yankees decided to give away bobble heads during one of his last home games. Unfortunately the management of the supply chain was

The holy grail for Yankee fans

The holy grail for Yankee fans

opposite of how Mariano pitched. It was an unmitigated disaster.

Supposedly there was a break down in the logistics; the truck delivering the inventory broke down on the New Jersey turnpike. Fans arriving at Yankee stadium were met with no available bobble heads, were given vouchers and asked to come back later during the game to collect their tchotchkes. Of course this being the Bronx, there were fights amongst the fans, long lines and people missing the game as they waited for their bobble head. All this caused by a simple truck breaking down on the highway…not an uncommon disruption in supply chain.

So what lessons can we learn from this?

·         Do better planning! The night of the give-away was known for months if not a year, everyone know that Mariano was retiring this season. The Yankees had plenty of time to plan the manufacturing and delivery of the items. But clearly their plan did not leave much buffer for any potential pitfalls – like a broken down truck.

·         Weigh the costs of not being able to have inventory on time with the cost of warehousing the inventory. Would it really have been that difficult for the Yankee to have the shipments arrive a week early? Would their “warehousing” costs have been that great? I highly doubt it. Maybe they were afraid that the stock would suffer from shrinkage prior to the give-away.

·         Have a plan in place to respond to potential supply chain outages. Trucks break down, factory manufacturing suffers unforeseen down time, points of entry suffer from labour strikes, and natural disasters cause interruptions. The Yankees had a plan, but it did not seem very well thought out – forcing the paying audience to leave their seats to wait in line for something they should have received upon entering the ball park not a good plan. Why not let people get their bobble head dolls on the way out of the park? Plus that would have guaranteed everyone stayed until the end of the game!

What is fascinating about what happened with the Yankees is that it was a microcosm of problems that can strike your supply chains. The problems with inventory management, transportation, and the desire for just in time all blew up under the weight of one truck, broken down on the Jersey turnpike.

Unlike Mariano, the Yankees did not demonstrate superior execution when it came to the bobble head give away. The Yankee closer was relentless in his ability to come into a game with a plan – throw that cutter and get people out. His ability to execute to that plan led to his gaudy statistics.

Unfortunately the Yankees supply chain for bobble head dolls looked more like Byung-Hyun Kim from the 2001 World Series – all over the place, not executing properly and leading to a minor disaster.


Tech Optimization Matrix Commerce Data to Decisions Innovation & Product-led Growth Supply Chain Automation Cloud Digital Transformation Disruptive Technology Enterprise IT Enterprise Acceleration Enterprise Software IoT Blockchain ERP Leadership Collaboration M&A Chief Supply Chain Officer

Constellation Research Appoints Steve Wilson as VP and Principal Analyst Covering Digital Identity

Constellation Research Appoints Steve Wilson as VP and Principal Analyst Covering Digital Identity

Steve WilsonAppointment expands Constellation’s coverage area into the data privacy and digital identity space

SYDNEY, AUSTRALIA  – Constellation Research, Inc., the award-winning research and advisory firm focused on how disruptive technologies transform business models announced today the addition of digital privacy specialist, Steve Wilson, to the research team as VP and Principal Analyst. Wilson, whose research focuses on digital identity, privacy and cyber security, expands Constellation’s ability to provide online risk management research/solutions to its early adopter clients worldwide. 

The addition of Wilson and consequential expansion into the digital identity space signals Constellation’s commitment to push its coverage area to the frontier of disruptive technology, and provide its early adopter clients with the most comprehensive coverage of emerging and disruptive technologies.

Wilson, a leading authority on digital identity, authentication technology, online risk management and privacy has been a thought leader in emerging authentication frameworks around the Asia Pacific since 1998. He lays claim to several authentication inventions. Wilson’s research focuses on identity federation, identity innovation, privacy management, and authentication technology optimization.

On joining Constellation Research
“We are witnessing tremendous flux as the digital revolution blends our work and personal spaces. As a society we are only beginning to understand the impact on private and public identities and how we conduct ourselves in the digital economy. Constellation Research is a red hot melting pot of business and technology, and an amazing channel in which to join disruptive ideas to diverse businesses.” - Steve Wilson, Vice President and Principal Analyst, Constellation Research

Steve Wilson’s Research Manifesto
“I work in disruptive authentication technologies and I’m committed to reforming identity management orthodoxies. Novel technology driven IDM ‘ecosystem’ provokes a sort of immune response from the business establishment; despite the desperate problems of trust and insecurity online.  Promising IDM frameworks repeatedly fail. My work tries to explain this paradox.  The answers lie in re-imagining identity management, with a promise of more elegant identity solutions that fit more smoothly into the ways real business is done.” - Steve Wilson, Vice President and Principal Analyst, Constellation Research

R “Ray” Wang comments on the significance of Digital Identity
"The recent NSA leaks, a battle for identity among social logins and financial services firms, and a growing awareness for a balance between privacy and convenience have our clients asking for Steve's expertise", noted R "Ray" Wang, Founder and Chairman of Constellation Research, "We're very lucky to have Steve on the team as his research agenda is core across our business themes.  For those who are attending our innovation summit, you can catch him live as he leads one of our tracks in our Big Ideas Forum on October 31, 2013" - R "Ray" Wang, Chairman and Principal Analyst, Constellation Research

COORDINATES

Twitter: @Steve_Lockstep
Profile: https://www.constellationr.com/users/swilson
Linkedin:  http://www.linkedin.com/in/lockstep
Geo: Sydney, Australia

Steve Wilson Biographical Information

Steve is a leading authority on digital identity, authentication, PKI, smart technologies and privacy.  As an independent analyst and strategic adviser for 18 years, Stephen has helped clients throughout the Asia Pacific navigate the multi-facetted identity management landscape.  He bridges and brings together expertise in technology, business and governance, with sophisticated but practical consulting. 

Steve has been a key player in numerous emerging authentication, PKI and smartcard frameworks.  Over 1998-2001 he served as a Ministerial appointee to Australia’s National Electronic Authentication Council (NEAC).  In 2006 he created the first National Smartcard Framework.  He led the reform of the Gatekeeper PKI framework, and was responsible for innovations including Relationship Certificates and Known Customer registration which are now central to contemporary Australian PKI.  Since 1998 Steve has provided strategic IDM framework advice to the governments of New Zealand, the US, Singapore, Hong Kong, Indonesia, Macau, Malaysia and Kazakhstan.  He was a long term member of the APEC eAuthentication Task Group, and of the American Bar Association PKI Working Group.

From 1995 to 2004,Steve held Principal Consultant and R&D leadership roles with PwC, KPMG, Securenet Ltd and Security Domain (later Baltimore Technologies).  Before that, he worked for nine years in government R&D and the biomedical industry in Australia and the USA.  in 2004 he founded the independent Lockstep Consulting and Lockstep Technologies. 

He holds an honors degree in Electrical Engineering, and a Bachelor of Science. 

Steve Wilson Research Agenda

Research will focus on:

  • The Consumerization of Identity
  • The Business of Social Logon
  • Big Data and the Collection Limitation Principle
  • The future of privacy in blended personal and work spaces
  • Is privacy really "good for business"?
  • Internet Life Verification
  • The ecology of identity

Press Contacts:

Contact the Media and Influencers relations team at [email protected] for interviews with analysts.

Sales Contacts:

Contact our sales team at [email protected].

Media Name: stevewilson website.png
Marketing Transformation Matrix Commerce New C-Suite Next-Generation Customer Experience Innovation & Product-led Growth Digital Safety, Privacy & Cybersecurity Security Zero Trust Chief Customer Officer Chief Executive Officer Chief Information Officer Chief Marketing Officer Chief Information Security Officer Chief Privacy Officer

Is it all coming together for Oracle in 2014? Or not?

Is it all coming together for Oracle in 2014? Or not?

Oracle Openworld just finished in San Francisco - and it was the event it promised to be - not big, but mega - in all aspects - size, attendees, number of sessions, steps walked between meetings (I even walked myself some blisters...), number of press releases etc. But let's look at the good and the bad.
 


Oracle's vision has been formulated and commented on many times - it is to create an integrated stack from low level storage services - even tape - all the way up to complex advanced analytical applications. In between the company already offers everything an enterprise may desire for any automation need.

It is Oracle's believe that by designing and building all these software layers in combination with its own hardware - it will be able to achieve better price performance than any of the (less well integrated) competitors. And this is very well compatible with the core corporate DNA of Oracle - of reducing total cost of ownership (TCO) through its products and services.
 

Top 3 Positive Signs

The unveiling of Oracle's in  memory plans is a key stepping stone to get Oracle's strategy going. And it's less the features and capabilities of in memory - that by itself are nice and compelling - but the nature of the delivery - that is non invasive, I called it organic in my first take here. For Oracle's vision to materialize both on the drawing boards of its engineers, its production code and the customer adoption - it matters greatly, that the upgrade to the latest version of key products like the database are not invasive, do not require additional coding beyond the task of upgrading. This will accelerate adoption.

The next one is, that Oracle seems to have understood that it needs to maintain its technology provider role - even in the cloud age. And while that self understanding peeked through e.g. with the Microsoft and Salesforce.com partnership agreements and announcements from June of this year - it was visible also in the keynotes of Thomas Kurian and Larry Ellison (the one that Kurian held for him). If Oracle manages to get a relevant piece of the license revenue from the cloud infrastructure providers trough any of the dozen or so XX as a service products - it will be positioned well for the future where it can play in the public cloud, it's own public cloud and on premise.

Finally we also had the chance to speak to a number of Fusion HCM Cloud customers - either implementing or being live running on Fusion. The sheer number, their experience and commitment were  more positive than what we had expected based on the previously general available information and sentiment in the marketplace. It's important for Oracle to see traction of its top of the stack products, the Fusion applications, especially in an embattled marketplace like HCM.
 

Top 3 remaining concerns

We have blogged before on how the BigData trend has the potential to disrupt Oracle. If the growing number of BigData players manage to move close enough to real time and support of transactional processes, they form a threat to Oracle's core and bread and butter - the database. And while Oracle has made a lot of progress with its BigData appliance - the BigData threat is potentially less of a technological threat but a commercial threat, being mostly open source based.

Which leads us to the second concern, centered around open source. Oracle is setup to extract significant amounts of payments from its customers. Needless to state the company provides value to its customers, but Oracle has mastered the art of price differentiation - never (or seldom) charging too match to stymie the uptake of new technology but equally avoiding any association with being a cheap offering. And while that is a fair strategy and probably the core to it fueling a massive R&D budget - it  makes Oracle vulnerable to low cost or even free open source competitors.

And lastly - Oracle is building a massive technology stack - probably the most extensive one ever build. We know IBM did the same, but we dare to say in a less complex and dynamic age. The sheer magnitude of engineers involved, interfaces, testing, documentation, training etc could make an endeavor like Fusion fail. Providing non disruptive path to get to Fusion is a key aspect - but that's not always possible for technical reasons or for decisions taken in the past. Ironically the sheer magnitude of the effort both labor wise and financially, is also a barrier to entry for most competitors and specifically for open source based products and their communities, that simply do not have the resources.
 

MyPOV

It is difficult to distill an event like OpenWorld into a short blog post (but writing double the amunt would not have made it easier). Clearly Oracle is on a roll and at this point the positive signs prevail over the warning signs... but given the complex and dynamic environment Oracle competes in - that can change any day.

In the  next quarters the company will have to sort out its hardware business and create customer success around its Fusion Applications. Nothing validates a technology stack  more than the products sitting on the very top of it.
 

Future of Work Tech Optimization Innovation & Product-led Growth Next-Generation Customer Experience Openworld Oracle Chief People Officer Chief Information Officer

News from one of the oldest software companies - and it's getting exciting

News from one of the oldest software companies - and it's getting exciting

One of the oldest software companies in Europe - if not in the word - purely founded for the purpose of software as a business, is Software AG in Germany. Unlike some older companies, Software AG never dabbled into anything hardware - but only focused on software for its 40+ years in existence.





Software AG was founded in Darmstadt, Germany by 6 members of a local consulting firm, not even 30 miles north of the more prominent other German software company's location, Walldorf (SAP (AG)). But it was too early for business software, so the Software AG founders focused on building the tools that were needed at the time, zeroing in on a database, that was supposed to be adaptable, so in 1971 the company launched adabas (you guess it - adaptable database system). It prove to be quite successful in the banking and insurance areas and along came the need to establish a programming language, that the founders wanted to make more easy to use and learn than the other programming languages on the market. In 1979 the company delivered natural as a 4GL application development environment - an easy to learn programming language that supported both procedural and event driving programming. 

In the 90ies the company extended it product range and most notably had partnerships with SAP (yes - a cheaper database option was even then a topic of interest) and Microsoft (porting of DCOM to other platforms than Windows). 

Later the company established a fondness of all things XML, which despite very high marks on the usability and lowered cost of ownership aspects of its products, never really took off and put the company in the doldrums to a certain extent.




Reshaping Strategy

In 2007 Software AG acquired webmethods - and with that focusing more on the integration aspects of software than it's creation, which in hindsight - and the 2013 perspective - provided to be pretty pivotal. Equally the acquisition of IDS Scheer AG with its Aris modelling tool was a key addition to is products and services portfolio. When Software AG was looking at a way to accelerate slow running business processes it acquired Terracotta - a leader of in memory caching technology. All that formed a very good base for growth at Software AG.




The latest 

While the company still provides adabas and natural, the main focus has been on integration and creation of high value, real-time and highly complex processes. Software AG picked more acquisitions in 2013 to complement this strategy, acquiring the CEP platform Apama from Progress, realizing the need for better visualization acquiring Jackbe and improving the agility of integration to webmethods with Longjump. And finally there is ambition to play in the IT transformation market with the acquisition of alphabet AG. It will be interesting what the company will unveil at their upcoming user conference in early October in San Francisco.




MyPOV

It's remarkable to have a 40+ year run in the software industry. Inevitably there will be success and failure, but with the right degree of innovation and re-inventing itself, Software AG has become one of the key players in the upcoming cloud integration game.

But the game has not changed - and we do not see it changing with the cloud - that integration vendors have to create value and not simply be a point to point connection protocol. Here the cloud is an opportunity for all of them -  not just Software AG - to more easily create value added services on top of the pure integration data streams. 

Tech Optimization Data to Decisions Digital Safety, Privacy & Cybersecurity Innovation & Product-led Growth Future of Work Google salesforce IBM SAP Oracle SaaS PaaS IaaS Cloud Digital Transformation Disruptive Technology Enterprise IT Enterprise Acceleration Enterprise Software Next Gen Apps IoT Blockchain CRM ERP CCaaS UCaaS Collaboration Enterprise Service Chief Information Officer Chief Technology Officer Chief Information Security Officer Chief Data Officer Chief Executive Officer

Is it Personal Information or not ? Embrace the uncertainty.

Is it Personal Information or not ? Embrace the uncertainty.

The US General Services Administration defines Personally Identifiable Information as information that can be used to distinguish or trace an individual’s identity, either alone or when combined with other personal or identifying information that is linked or linkable to a specific individual (underline added). This means that items of data can constitute PII if other data can be combined to identify the person concerned. The fragments are regarded as PII even if it is the whole that does the identifying. And the definition means that a piece of data may be classed as PII before it is identified, rather than after.  This is only prudent. 

I am frequently asked - semi-rhetorically - by IT and security professionals if the definition means that even an IP or MAC address nowadays could count as PII? And I've said that in short, yes, it appears so!

Some security people are uncomfortable with this, but why? When it comes down to it, what is so worrying about having to take care of Personal Information? In Australia and in 100-odd other jurisdictions with OECD based data protection laws, it means that data custodians are required to handle their information assets in accordance with certain sets of Privacy Principles. This is not trivial but neither is it necessarily onerous. If the obligations in the Privacy Principles are examined in a timely manner, alongside compliance, security and information management, then they can be accommodated as just another facet of organisational hygiene.

So for instance, consider a large data base of 'anonymous' records indexed by MAC address. This is just the sort of data that's being collected by retailers with in-store cell phone tracking systems, and used to study how customers move through the facility and interact with stores and merchandise. Strictly speaking, if the records are not identifiable then they are not PII and data protection laws do not apply. But the new definition of Personal Information in Australia means IT designers need to consider the prospect of the records becoming identifiable in the event that another data set comes into play. And why not? If anonymous data becomes identified then the data custodian will suddenly find themselves in scope for privacy laws, so it's prudent to plan for that scenario now. Depending on the custodian's risk appetite, any large potentially identifiable data set should be managed with regard to Privacy Principles. These would dictate that the collection of records should be limited to what's required for clear business purposes; that records collected for one purpose not be casually used for other unrelated purposes; and that the organisation be open about what data it collects and why. These sorts of measures are really pretty sensible.

Security practitioners I've spoken with about PII and identifiability are also upset about the ambiguity in the definition of Personally Identifiable Information. They complain that the identifiability of a piece of data is relative and fluid, and they don't want to have to interpret the legal definition. But I'm struck here by an inconsistency, because security management is all about uncertainty.

Yes, identifiability changes over time and in response to organisational developments. But security professionals and ICT architects should treat the future identification of a piece of unnamed data as just another sort of threat. The probability that data becomes identifiable depends on a range of variables that are a lot like other factors (like the emergence of other data, changes of circumstance, or developments in data analysis) that are routinely evaluated during risk assessment.

To deal with identifiability and the classification of data as PII or not, you should look at the following:

  • consider the broad context of your data assets, how they are used, and how they are linked to other data sets
  • think about how your data assets might grow and evolve over time
  • look at business pressures and plans to expand the detail and value of data, and the resulting potential for new linkages
  • make assumptions, and document them, as you do with any business analysis, and
  • plan to review periodically.

Many organisations maintain a formal Information Assets Inventory and/or an Information Classification regime, and these happen to be ideal management mechanisms in which to classify data as PII or not PII. That decision should be made against the backdrop of the organisation's risk appetite. How conservative or adventurous are in you respect of other risks? If you happen to mis-classify Personal Information, what could be the consequences, and how would the organisation respond? Do some scenario planning, and involve legal, risk and compliance. While you're at it, take the chance to raise awareness outside IT of how information is managed. Be prepared to review and change your classifications from non-PII to PII over time. Remember that security managers should always be prepared for change. Embrace the uncertainty in Personal Information!

Truly, privacy can be tackled by IT professionals in much the same way as security. There are no certainties in security and it's the same in privacy. We will never have perfect privacy; rather, privacy management is really about putting reasonable arrangements in place for controlling the flow of Personal Information.

So, if something that's anonymous today, might be identified later, you're going have to deal with that eventually. Why not start the planning now, treat identifiability as just another threat, and roll your privacy and security management together?

 

See also the excellent survey of identifiability by William B. Baker and Anthony Matyjaszewski The changing meaning of 'personal data' (2010). The essay looks specifically at the question of whether IP addresses can be PII, and highlights a trend in the US towards conceding that IP addresses combined with other data can identify, and may therefore count as PII:

Privacy regulators in the European Union regard dynamic IP addresses as personal information. Even though dynamic IP addresses change over time, and cannot be directly used to identify an individual, the EU Article 29 Working Party believes that a copyright holder using "reasonable means" can obtain a user's identity from an IP address when pursuing abusers of intellectual property rights. More recently, other European privacy regulators have voiced similar views regarding permanent IP addresses, noting that they can be used to track and, eventually, identify individuals.
This contrasts sharply to the approach taken in the United States under laws such as COPPA where, a decade ago, the FTC considered whether to classify even static IP addresses as personal information but ultimately rejected the idea out of concern that it would unnecessarily increase the scope of the law. In the past few years, however, the FTC has begun to suggest that IP addresses should be considered PII for much the same reasons as their European counterparts. Indeed, in a recent consent decree, the FTC included within the definition of "nonpublic, individually-identifiable information" an “IP address (or other "persistent identifier")." And the HIPAA Privacy Rule treats IP addresses as a form of "protected health information" by listing them as a type of data that must be removed from PHI for deidentification purposes.

New C-Suite Digital Safety, Privacy & Cybersecurity Infosec Security Zero Trust Chief Customer Officer Chief Executive Officer Chief Information Security Officer Chief Privacy Officer

Richard Napier Creates Siebel 20 Year Anniversary Quiz

Richard Napier Creates Siebel 20 Year Anniversary Quiz

CelebrationLogo-150x150Leading Siebel blogger Richard Napier has created a quiz to celebrate the 20th Anniversary of the product. His On Demand Education blog is one of the most popular dedicated to Oracle Siebel technology.

The free quiz has some technical questions, some functional questions, and some Siebel trivia. The quiz is free, and even has a leaderboard to capture and share results through Twitter, Facebook and other social networks.

Richard challenges his readers to "see who is the Siebel Quiz Master". The quiz can be found here at http://ondemand-education.com/corp/index.php/quizzes/siebel-20-year-anniversary-quiz/

Tech Optimization Chief Information Officer

The end of an era – Blackberry goes private

The end of an era – Blackberry goes private

Okay okay, Blackberry will not disappear from the face of consumer electronics, but it is facing its Waterloo and being sent to Saint Helena (for you Napoleon history buffs). Blackberry has to hope that going private and being tucked away on a symbolic island away from prying eyes will allow the once mighty company to rediscover itself.

But can this move help the smart phone manufacturer? Blackberry’s story is well documented. The pioneer of mobile email, it got caught flat footed with the rise of the iPhone and then Android devices. As smart phones moves away from simple email into the world of apps, texting and web browsing, just having a secure email service was not longer the “killer app.” The iPhone and more importantly the App Store open up a world of mobile tools that was ignored by Blackberry. As a former Blackberry user I remember trying to download apps on my device and being frustrated by the lack of choice, the amount of memory it ate up on my phone and the overall lack of user friendliness. Meanwhile some of my colleagues were zipping around on their user friendly touch screen iPhones.

So now Blackberry should have the ability to make some difficult strategic decisions away from the pressures of the public market. What should they do? I still think what I published a few posts ago is the direction they should head in, click here. Being private should make this process smoother.

It is always a little sad to see a once mighty company wither away, much like watching other tech giants like Digital, Wang, Compaq fall away. However it is a good lesson for the likes of Google, Apple, Facebook to realize that the top of the mountain is not a right but something that was earned and has to be constantly worked on to maintain (Apple probably knows this better than the others).

Good luck Blackberry…it was a great ride.

New C-Suite Next-Generation Customer Experience Innovation & Product-led Growth Chief Executive Officer Chief Financial Officer

ADMA Young Marketer of the Year Finalists Announced

ADMA Young Marketer of the Year Finalists Announced

1
 

The finalists for the ADMA Young Marketer and Young Creative of the Year have been announced, celebrating and showcasing the work of the Australians under the age of 30. It’s hotly contested, with winners flying to New York City in 2014 on an all-expenses paid trip to meet with leading marketers, creatives and agencies including Google Creative lab, OgilvyOne Worldwide and Anomaly.

In the running for Young Marketer of the Year are:

  • Leigh Allen, Marketing and International Marketing Solutions Manager, ESPN Australia/NZ
  • Anna Guerchenzon, Marketing Team Manager, Telstra
  • Jasmine Hildebrand, BTL Manager-Marketing, AAMI Insurance
  • Chris Howatson, Managing Director, CHE Proximity, Melbourne

Young Creatives have entered their work for judging – and you can check it out yourself at the ADMA site.

  • Jardin Anderson, art director, Rapp DBB, for Get ahead of yourself.com.au which calls on young creatives and marketers to ditch an old award in favour of one from ADMA.
  • Michael Gagliardi, creative/art director For KWP! Advertising, for #YoungPeopleGetIt – getting young marketers and creatives to enter YMYC by speaking to them in the language only they understand.
  • James Nguyen, art director at OBM, for Follow the Follower –  for a fresh twist in getting the leading lights in the marketing and advertising industries to follow the young person on Twitter.
  • Tony Simmons, art director at The Brand Agency –  for See Where It Can Take You – for showing junior marketers and creatives where their career can take them with YMYC using their own Facebook timeline as the narrative.

The overall winners will be announced on Friday 1 November at the ADMA Awards at The Star, Pyrmont.

Is there something you see that you love? Leave me a comment below.

Best Practices for SaaS Upgrades as Seen in Workday's Approach

Best Practices for SaaS Upgrades as Seen in Workday's Approach

If you're involved with enterprise software, you need to pay attention to what Workday is doing--even if you're not interested in HR or financial systems. Because Workday is one of the best examples of how enterprise applications can and should be delivered in the cloud.

This was one point I took away from Workday's annual user conference in San Francisco and from a day-long series of briefings for industry analysts earlier this month. 

The differences between Workday's practices and the approach of traditional enterprise software vendors are striking. There are several points of contrast, but in this post I'd like to focus on how Workday delivers software upgrades and some new twists in how it does this.

Traditional Approach to Software Upgrades

In the traditional enterprise software model, vendors develop new versions and provide them to their customers that are under maintenance agreements. The customer takes delivery of the new version, installs it on a test copy of the system, migrates data from the existing production version, retrofits any customizations or interfaces with other systems, revises its user procedures, performs system testing,  and migrates all of its users to the new version. In the process, if there is any time left in the schedule, the customer also may investigate how it would like to use any new functionality offered in the new version.

The bottom line is that in the traditional model, software upgrades are both a technical exercise as well as a business exercise. The technical challenges of data migration, retrofitting of customizations, and reworking system interfaces can be significant and can encourage customers to stay on older versions of a vendor's system for many years. When such a customer finally wants to get current on the latest version, the upgrade process can rival the time and expense of the original implementation. The technical aspect can be so much work that companies often retain outside service providers to manage or assist in the effort. The business aspects--accommodating changes to business processes or embracing new functionality--are often jettisoned for the sake of simply getting the new version installed from a technical perspective. As a result, customers often do not realize the benefits of the new functionality that the vendor offers.

The Workday Approach

Workday's approach to upgrades, from the beginning, is simple: it takes responsibility for all technical aspects of the software upgrade, allowing the customer to focus solely on the business aspects. There are at least three reasons that Workday can do this:

  • Workday's object model allows most customizations to be brought forward to new versions of the system with little or no retrofitting.
  • Likewise, Workday's Integration Cloud, based on technology it obtained through its acquisition of Cape Clear,  allow most custom integrations to continue to work with new versions of its system.
  • Since Workday operates the system on behalf of the customer, Workday takes all responsibility for migrating the customer's data to the new version. 

The impact of this last point should not be underestimated. Last year, Workday's CTO, Stan Swete, wrote about how important it is for the SaaS provider to take full responsibility for migrating customer data to new versions: 

[The] Software-as-a-Service (SaaS) model improves service delivery quality by letting the provider own the end-to-end process of development, conversion, and deployment. In the on-premise software world the vendor controls development (and associated QA), but there is a hand off for conversion and deployment. At Workday, the update process is not done until every customer is on the new version. The same team that project manages our development also project manages conversion and deployment.

When it comes to version upgrades, not all SaaS providers are created equal. Some are little more than single tenant hosting providers. Others are multi-tenant SaaS providers, but they deploy new versions as separate instances of the system and allow customers to stay on older versions for long periods of time. This makes version upgrades considerably more difficult if and when customers do decide to upgrade. Workday, as discussed, is at the other end of the spectrum, keeping all customers current on the latest version. Salesforce.com, NetSuite, and Plex, are similar to Workday in this regard, though they may differ in the details of how they do it.

    Further Improvements in Workday's Approach

    This year, Workday has further refined its approach to version upgrades in three ways:

    1. Single production instance for all versions. Previously, Workday would deploy a new version of Workday as a system instance that was separate from the previous version, and Workday would migrate customers in waves from the old version to the new version over a three week period. Workday's new approach is for the current version and the new version to exist simultaneously on the same system instance. Workday will now move customers to the new version by means of a set of "switches" that dictate which features of the system the customer will see. This new approach is possible because of Workday's object orientation discussed earlier.
    2. Continuous development and deployment of new functionality. Instead of holding all functionality enhancements for its periodic version upgrade, Workday is now introducing smaller changes on a weekly basis. This is especially important for small but high-priority changes or for tax and regulatory updates. Contrast this to the traditional vendors, who required many months or years between the time customers request changes and the time they actually see them in updated versions.
    3. Continuous conversion of customer data. As Workday develops new features that require changes to its data model, the single production instance now allows Workday to convert customer data in the background in advance of actually migrating customers to the new version. This reduces the amount of downtime required during the when the customer is moved to the new version. 
    4. Preview instance. Now that there is a single production instance and continuous conversion of customer data, Workday is now able to offer customers a preview instance of the new version, giving customers a longer time-frame in which to evaluate and plan for the new version. Under the traditional model, customers only get a hands-on look at the new version when they take delivery of the upgrade, install it, and convert their data to it in a prototype environment. Workday's approach gives customers much more time and encourages them to make use of the new functionality.

     Swete summarized these changes in a blog post during the user conference:

    Probably the best example of embracing continuous change is happening on the service delivery side of our business. Workday has moved to continuous deployment of new features to a single code line. This move, along with the continuous background conversion of data for new features, enables us to complete updates for our production customers with less scheduled downtime. Application of changes to a single code line reduces the expense of maintaining multiple code lines around each update we do. Moving to continuous deployment also gives us the flexibility to continue to respond to our customers’ requirements when it comes to the number of updates we do each year.

    As Swete indicates, the single production instance, continual development approach, and continuous conversion of customer data allow Workday to scale back from three new major versions a year to just two. The conference audience applauded when co-CEO Aneel Bhusri made this announcement, perhaps indicating that many companies have difficulty absorbing three major upgrades a year. At first blush, the reduction in the number of new versions a year would imply that Workday is slowing down the number of new features per year. But in an sidebar conversations with Workday executives the next day, it became clear that these most recent improvements actually mean that Workday will be introducing more new features each year. The difference is that the smaller changes will be trickled-in on a weekly basis, while major new features will be held for the twice-yearly updates.  As indicated earlier, this approach also allows Workday to accommodate regulatory or tax-law changes on short notice, which have become more common in recent years.

    Workday's core strategy of reducing or even eliminating the technical burden of version upgrades is a best practice for SaaS providers, allowing customers to focus exclusively on business improvement and maximizing the value of their system investment. More SaaS providers should follow this example.

    Postscript: Over at Diginomica, Phil Wainwright has two good posts covering some of these same points:

    Note: Workday covered my travel expenses for attending its user conference.


    Related Posts

    The Simplicity and Agility of Zero-Upgrades in Cloud ERP
     

    New C-Suite Future of Work Tech Optimization Innovation & Product-led Growth workday SaaS PaaS IaaS Cloud Digital Transformation Disruptive Technology Enterprise IT Enterprise Acceleration Enterprise Software Next Gen Apps IoT Blockchain CRM ERP CCaaS UCaaS Collaboration Enterprise Service Chief Information Officer Chief Technology Officer Chief Digital Officer Chief Data Officer Chief Analytics Officer Chief Information Security Officer Chief Executive Officer Chief Operating Officer