All Posts By

IDS

EMC Takes Control of VCE

By | Cloud Computing, EMC, Strategy, VMware | No Comments

EMC recently announced that they were buying out most of Cisco’s interest in VCE with Cisco only retaining a 10 percent stake in the company. VCE published that they would keep their mission intact, and continue to create new solutions using their industry-leading VBlock Systems. EMC has also made headlines lately for being nominated as one of the “World’s Best Multinational Workplaces,” and for some speculation that they may be planning a reorg, which may include the formation of a new cloud business unit.

What Does The EMC Transition Mean for VCE?

While there are always different rumblings of opinions throughout an industry, many analysts maintain that the VCE transition towards becoming an EMC business is an entirely natural one, and will probably help to skyrocket their growth. In the cio-today.com article “EMC Buys Cisco’s Stake in VCE, Eyeing Hybrid Cloud Potential” analyst Zeus Kerravala from ZK Research explained that joint ventures are only meant to last for certain period of time.

Kerravala said “If VCE Is going to earn billions more, they are obviously going to have to find a way of growing beyond organic growth. That will probably be through mergers and acquisitions or a change of channel strategy, and it’s going to require making faster decisions.” He went on to say that since there will now be streamlined decision making under EMC, he believes it’s a good move for VCE.

Our Take on the VCE Transition to EMC

With a big industry move like this one, we wanted to talk to IDS Chief Technology Officer, Justin Mescher, and get his take on the VCE transition. Mescher explained that the move might help solidify previous marketplace suspicions.

He said,“Ever since VMware acquired Nicira in 2012 and created their own software-defined networking stack, speculation has been swirling that EMC, VMware, and Cisco would start to grow further apart. While this move seems to confirm the rumors, I think it will be a positive move overall.”

Mescher went on to explain that VCE’s biggest value has been bringing fully validated and pre-integrated systems to customers to accelerate time to value, reduce risk and increase efficiency, and that mantra of the offerings shouldn’t change.

He explained that it will be interesting to see is how the recent EMC re-structuring to create a Cloud Management and Orchestration group will impact this acquisition. EMC has proclaimed that this new business unit will focus on helping customers work in both the private and public cloud independently of the technology running underneath it. This will include EMC’s “software-defined” portfolio as well as some of their new acquisitions targeted at cloud enablement and migration.

Concluding his thoughts, Mescher said,“Could EMC take the framework and concept that VCE made successful and start to loosen some of the vendor-specific requirements? While this would certainly not be typical of EMC, if they are serious about shifting from a hardware company to focusing on the software-defined Data Center, what more impactful place to start?”

About VCE

VCE was started in 2009 as a joint venture between three of the top IT industry companies, EMC, Cisco and WMware as an effort to provide customers integrated products solutions through a single entity. In 2010 VCE introduced their Vblock Systems which provided a new approach to optimizing technology solutions for cloud computing. Since then they have continued to grow their customer portfolio and improve their solutions and be a leader in the industry. See the complete VCE history.

4 Mistakes Technology Departments are Making

4 Scary Mistakes Technology Departments are Making

By | How To, Project Management | No Comments

Halloween is a great reminder for everyone to take some time and enjoy their favorite spooky activities, but what about the really scary stuff? In honor of Halloween we are breaking down the top four truly scary mistakes that technology departments are making today. If you see a frightening mistake that sounds familiar, take a look at our tips for getting back on track.

1. Allowing Miscommunication Between Business and IT

Business and IT units understand projects in inherently different ways. Business and IT professionals are trained differently, understand processes with contrasting views and ultimately communicate in a way that best suits their own team. Lack of communication and understanding between the two units can lead to problems like unrealistic deadlines, confusion on project scope and general lack of clarity. These types of issues can delay or halt projects altogether, creating an inefficient work environment for both types of business units.

How to Improve Communication Between Business and IT Units

  • Get both sides involved in development.
  • Be realistic about workload management.
  • Strategize reworks and changes together.

2. Ignoring Infrastructure and Storage Resources

Too many technology departments are putting focus on building out internal solutions and infrastructure when there are readily-available resources they can take advantage of that are much more cost and time efficient. By using existing commercial options, IT teams can spend less time focused on infrastructure and maintenance, and more time focusing on other projects. Choosing to partner with a Data Center Technology Integrator and Cloud Service Provider, such as IDS, allows IT teams to access best-of-breed infrastructure and offload some of the day-to-day management so they can spend time focusing in more strategic areas.

How to Use Commercial Infrastructure and Storage Resources

  • Realize department limits and prioritize time.
  • Research cost effective commercial solutions.
  • Contact IDS for a custom assessment.

3. Always Saying “Yes”

Technology departments need to have realistic expectations about bandwidth. Agreeing to take on every project and meet every deadline will undoubtedly create a lot of stress and less than impressive outcomes. Maryfran Johnson who wrote “A CIO Survival Guide to Saying No” for CIO.com suggested that it’s getting even harder for IT departments to say no because of their increased involvement in business activities that can directly impact revenue. Johnson suggests leaving emotions behind and discussing the matter at hand using fact-based reasoning as often as possible.

How to Strategically Say “No”

  • Leave emotions off the table.
  • Explain project scopes in a universal way.
  • Use fact-based reasoning.

4. Forgetting About the Users

Technology teams should always have the end user in mind. No matter what the project or end deliverable, the user needs to be successful at whatever it is they are doing. Often times IT departments are so overloaded with completing projects, they don’t have time to collect and implement user feedback in the development process. Taking the extra time to strategically analyze feedback from the users can drastically change the success of technology outcomes.

How to Keep Users on the Radar

  • Schedule regular user feedback collections.
  • Create action plans from reliable feedback.
  • Test products and updates aggressively.

Have other mistakes you think technology departments should avoid? Comment below and tell us about them!

float(2)