Click here to close now.

Welcome!

@MicroservicesE Blog Authors: Elizabeth White, Pat Romanski, Cloud Best Practices Network, Lori MacVittie, Liz McMillan

Related Topics: @MicroservicesE Blog, Industrial IoT, Mobile IoT, @ContainersExpo, @CloudExpo Blog

@MicroservicesE Blog: Article

Telecommuting – The Invisible Employee

The biggest advantages to having remote workers & virtual offices are in-house facility costs, expansion, & talent acquisition

One of the truisms in information technology is that everything old is new again - well, except maybe for punched cards. We went from big corporate data centers to regional/division corporate data centers back to big corporate data centers and now to even bigger cloud data centers. We have gone from dumb terminals were everything was done on the mainframe, to PCs, and now to virtualized desktops - where everything is run on the central servers. And now, we are back to talking about the IT advantages of telecommuting.

Telecommuting is certainly nothing new. But what is changing is how people are telecommuting and the IT processes and procedures that support them. Gone are the days of modem banks and analog days. Gone are the days when IT departments handed out PCs so people could work from home. And gone are the days when connecting remote employees meant connecting them directly into the corporate network.

When most people think of telecommuting, we hark back to the model that JetBlue made famous: the company supplied the personal computer, monitor, keyboard, mouse, and Internet connection (there is no need to go back to the caveman days with terminals and modems or acoustic couplers!). The PC was company property so that the policies, anti-virus, patches, etc., could all be controlled and managed by the corporate IT department. After all, a lot of employees still didn't even own their own computer.

These PCs had the necessary software pre-loaded on them, be it a thick client or a terminal emulator. When the remote staff connected in - their computers were placed onto the corporate network and became part of the companies extended network. When the PCs needed to be updated, patched, or upgraded - the employee had to bring everything back to the in-house IT department.

What changed? Well... EVERYTHING! There were four basic changes made for teleworking - and each of these changes required the IT department to adapt in different ways. As the ability to provide a realistic work environment kept increasing, we have gone from teleworkers to virtual offices.

One of the first big changes was that users no longer wanted to take a company PC home with them. They had their own perfectly good computer, and wanted to be able to connect using their machines. These machines/users wanted to connect to the company over the Internet instead of through dial-up modems. So IT departments started to increase their network connectivity, add Virtual Private Network (VPN) devices, and put in place intrusion detection/prevention appliances. Many a sleepless night was had by the IT administrator waiting for some remote user to spread a worm or Trojan through the entire organization.

The next big change was also Internet related - the death of thick clients. As browser technologies involved we were finally able to produce thick-client like look-and-feel inside a browser window. Most companies ported their internal applications to use browser-based web interfaces. These browser-based applications were exactly what were needed to allow better remote workers.

Ironically the Internet contributed the necessary technology to the next big change in our march to the virtual office: the move from IPSec-based VPN connections to browser-based SSL connections. IPSec, while a good protocol, proved problematic. Many travelers found out that their VPN connections were either blocked, or that the ISP or hotel lacked the technology to allow IPSec to pass through their networks. Just about every company's helpdesk received a call from some executive complaining about being unable to connect, and the helpdesk would have to try to work with the hotel or ISP to resolve the problem (and usual not be able to).

SSL VPNs resolve that issue because they work through the browser - an application that every PC already had loaded and that every user was already familiar with using. No longer would users have to be given CDs of the VPN software along with installation instructions (and the sure to follow helpdesk call). Most SSL VPN systems function as a proxy to allow dynamic access rights to the user. Instead of connecting them to the network (along with every virus, Trojan, and worm and the person's computer), we can now limit them to accessing the company's Intranet server, or to allow only access to specific company web pages.

Now that we have people using their own computers, over their own Internet connection, to securely access browser based applications - we must be done, right? What could be left? What is left is giving the user the necessary tools to have a virtual office instead of a remote connection.

Remote phone are required. The person needs to have a phone at his desk - even if that desk is 1000 miles away (or more). Here again new technology was required. We needed the new modern voice systems that allow Voice over IP (VoIP) so that we could have corporate phones remotely become part of the corporate telephone system. Even here, this is starting to give way to soft phones - software running on somebody's computer that provides that phone interface.

The remote person needs to know if his/her co-worker is available. After all, she can't simply look over the cubicle wall anymore to see if the coworker is there or not - and she can't see/hear if the co-worker is on the phone. But presence software, tied into the phone and using software on the person's computer, can tell the remote person if that co-worker is on the phone, in a meeting, or even at their desk working on their computer. Such presence software is normally built into an instant messaging client. These clients provide an easy way to communicate with somebody. Instant messaging is the new way to ask: Do you have a second?

The final piece of the puzzle to finally become feasible is video conferencing. IT departments no longer have to purchase expensive cameras, video conferencing servers, and large data connections everywhere. Point-to-point ad-hoc video conferences are easily done today with commercial "webcams" sitting on people's monitors and attached to their computers. In fact, most modern laptops have webcams built into them. Video conferencing allows the visual interfacing that is critical in modern communications. If you think that video is not important, remember that 70% of all our communication information comes from visual "clues". Without providing video conferencing, you are removing 70% of the person's comprehension.

Now that we know how to create a modern telecommuter environment, the question becomes whether we should allow telecommuting. Why are companies, both big and small, investing in this technology? Is this a technology that you should to be implementing?

The biggest advantages to having remote workers and virtual offices are in-house facility costs, expansion, and talent acquisition. Companies that have increased their use of remote workers have benefited from reduced building overhead expenses. One company that I frequently visit has been so successful with their remote worker program that they had to close the on-site cafeteria because there simply wasn't enough staff present to make use of it.

JetBlue used remote employees to staff their reservation lines. These were primarily part-time college educated women who only wanted to work 3-4 hours while their kids were in school. Using remote employees allowed JetBlue to staff across the country - thereby moving calls across the country as people's shifts changed. This is something that could not have been done with a traditional on-site call center.

Sometimes the perfect employee that you need to succeed isn't willing to relocate to where your office is. This leaves employers with the choice of either doing without a key resource, or figuring out how to allow that employee to work from home. Remote employees and virtual offices empower an employer to find the employee that will best contribute to the company - even if that person lives in a mountain cabin.

Those people who wonder if I really mean what I say about the advantages of virtual offices should know that it is what I use. I have a company phone that connects directly over the Internet to the company's phone system. I have an SSL VPN connection to gain access to the internal system. I use Cisco's Jabber service to provide presence information and instant messaging capabilities. And I use Cisco's WebEx Telepresence video conferencing service for when I need "face-to-face" time. The most important lesson I have learned about using a virtual office is to treat it like it is your real office - because the day you decide to wear your fuzzy slippers to the office is the day your boss will have a surprise video conference call with you.

More Stories By Dean Nedelman

Dean Nedelman is Director of Professional Services at ASi Networks, a network and voice services firm in City of Industry, Calif. In this role, he supports our major accounts, and oversees the implementation of advanced Cisco solutions and services. He has over 25 years of experience in technical and executive level technology roles, primarily in secure high performance computer environments across multiple industries and sectors. Dean's background includes security, high availability, telephony, advanced network, wide area application services, and storage area networks.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
DevOps tends to focus on the relationship between Dev and Ops, putting an emphasis on the ops and application infrastructure. But that’s changing with microservices architectures. In her session at DevOps Summit, Lori MacVittie, Evangelist for F5 Networks, will focus on how microservices are changing the underlying architectures needed to scale, secure and deliver applications based on highly distributed (micro) services and why that means an expansion into “the network” for DevOps.
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
Discussions about cloud computing are evolving into discussions about enterprise IT in general. As enterprises increasingly migrate toward their own unique clouds, new issues such as the use of containers and microservices emerge to keep things interesting. In this Power Panel at 16th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the state of cloud computing today, and what enterprise IT professionals need to know about how the latest topics and trends affect t...
Data center models are changing. A variety of technical trends and business demands are forcing that change, most of them centered on the explosive growth of applications. That means, in turn, that the requirements for application delivery are changing. Certainly application delivery needs to be agile, not waterfall. It needs to deliver services in hours, not weeks or months. It needs to be more cost efficient. And more than anything else, it needs to be really, dc infra axisreally, super focus...
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
Many people recognize DevOps as an enormous benefit – faster application deployment, automated toolchains, support of more granular updates, better cooperation across groups. However, less appreciated is the journey enterprise IT groups need to make to achieve this outcome. The plain fact is that established IT processes reflect a very different set of goals: stability, infrequent change, hands-on administration, and alignment with ITIL. So how does an enterprise IT organization implement change...
Conferences agendas. Event navigation. Specific tasks, like buying a house or getting a car loan. If you've installed an app for any of these things you've installed what's known as a "disposable mobile app" or DMA. Apps designed for a single use-case and with the expectation they'll be "thrown away" like brochures. Deleted until needed again. These apps are necessarily small, agile and highly volatile. Sometimes existing only for a short time - say to support an event like an election, the Wor...
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of...
The cloud has transformed how we think about software quality. Instead of preventing failures, we must focus on automatic recovery from failure. In other words, resilience trumps traditional quality measures. Continuous delivery models further squeeze traditional notions of quality. Remember the venerable project management Iron Triangle? Among time, scope, and cost, you can only fix two or quality will suffer. Only in today's DevOps world, continuous testing, integration, and deployment upend...
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations migh...
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Mashape is bringing real-time analytics to microservices with the release of Mashape Analytics. First built internally to analyze the performance of more than 13,000 APIs served by the mashape.com marketplace, this new tool provides developers with robust visibility into their APIs and how they function within microservices. A purpose-built, open analytics platform designed specifically for APIs and microservices architectures, Mashape Analytics also lets developers and DevOps teams understand w...
Buzzword alert: Microservices and IoT at a DevOps conference? What could possibly go wrong? In this Power Panel at DevOps Summit, moderated by Jason Bloomberg, the leading expert on architecting agility for the enterprise and president of Intellyx, panelists peeled away the buzz and discuss the important architectural principles behind implementing IoT solutions for the enterprise. As remote IoT devices and sensors become increasingly intelligent, they become part of our distributed cloud envir...
Sumo Logic has announced comprehensive analytics capabilities for organizations embracing DevOps practices, microservices architectures and containers to build applications. As application architectures evolve toward microservices, containers continue to gain traction for providing the ideal environment to build, deploy and operate these applications across distributed systems. The volume and complexity of data generated by these environments make monitoring and troubleshooting an enormous chall...
Containers and Docker are all the rage these days. In fact, containers — with Docker as the leading container implementation — have changed how we deploy systems, especially those comprised of microservices. Despite all the buzz, however, Docker and other containers are still relatively new and not yet mainstream. That being said, even early Docker adopters need a good monitoring tool, so last month we added Docker monitoring to SPM. We built it on top of spm-agent – the extensible framework f...
There's a lot of things we do to improve the performance of web and mobile applications. We use caching. We use compression. We offload security (SSL and TLS) to a proxy with greater compute capacity. We apply image optimization and minification to content. We do all that because performance is king. Failure to perform can be, for many businesses, equivalent to an outage with increased abandonment rates and angry customers taking to the Internet to express their extreme displeasure.
There's a lot of things we do to improve the performance of web and mobile applications. We use caching. We use compression. We offload security (SSL and TLS) to a proxy with greater compute capacity. We apply image optimization and minification to content. We do all that because performance is king. Failure to perform can be, for many businesses, equivalent to an outage with increased abandonment rates and angry customers taking to the Internet to express their extreme displeasure.
SYS-CON Events announced today that the "Second Containers & Microservices Conference" will take place November 3-5, 2015, at the Santa Clara Convention Center, Santa Clara, CA, and the “Third Containers & Microservices Conference” will take place June 7-9, 2016, at Javits Center in New York City. Containers and microservices have become topics of intense interest throughout the cloud developer and enterprise IT communities.
The causality question behind Conway’s Law is less about how changing software organizations can lead to better software, but rather how companies can best leverage changing technology in order to transform their organizations. Hints at how to answer this question surprisingly come from the world of devops – surprising because the focus of devops is ostensibly on building and deploying better software more quickly. Be that as it may, there’s no question that technology change is a primary fac...