sample work
Steve McCoy has always been a strong believer
that effective management and leadership in highly technical
disciplines requires continuous involvement with detailed
understanding of the technologies. For him, that has included
maintaining competencies in programming languages and techniques as
well as networking protocols and configurations. In typical
work situations, he has worked closely with his team members to
"lead by example", mixing the providing of guidance to others as
well as providing low-level engineering tasks himself. He
remains very comfortable delivering both types of technical work.
In addition, his extensive background in understanding the
relationship between the technology and the business have resulted
in him providing a majority of the data reduction and analysis of
financial models in lines of business that he has worked in.
He is a strong believer that understanding discrete "units of work"
and their costs is critical to managing any business.
|
|
|
The following items represent a few samples of
McCoy's more "engineering" oriented activities. While
much of this type of work product was and is "owned" by his previous
employers, he often has created tools and utility resources for use
across organizations (including for clients) that are non-specific
to the businesses but demonstrate some of the skills required to
perform necessary technical tasks. Below are a very few
examples that may be useful to readers as well. Click
on any of the document titles to access them. ("open" or "save as")
Simple VoIP Bandwidth Calculator - This
"Voice over IP bandwidth calculator" allows you to enter a number
representing a required number of simultaneous calls (the key factor
in calculating VoIP) and provides the
required network bandwidth required for that solution. The
spreadsheet then works with sample tables from a couple network
providers (in this case, AT&T and Sprint) and provides an estimate
of what the costs would be to implement such a configuration.
These tables are purely samples and could be easily be replaced by
the information that would be specific to any particular business.
This tool accomplishes several common telecommunications engineering
functions in one simple tool.
These examples are not necessarily representative of what costs
would be in your particular environment.
This example is a Microsoft Excel file using VBA. If you need
a non-Microsoft version please drop me an email and I will be glad
to send you another version of the information.
TDM versus VoIP Modeling -
Contrary to what much media hype might have folks believe, Voice
over IP is not always more cost
effective in delivering phone calls than classical TDM (time
division multiplex) circuit configurations. As part of an
overall network strategy VoIP may have other advantages in your
network than just unique line costs, but it's important to
understand discrete components. This particular model combines
some more simple "per minute" charges of TDM and the "bandwidth"
cost of VoIP to draw a comparison in how an interactive environment
or call center might be affected by differences in Call Volume, Peak
Call Rates, Average Call Rates, and Average Call Length to create
estimates of how much TDM and two different VoIP compression models
might affect a business cost. These underlying data is purely
sample and could be easily be replaced by the information that would
be specific to any particular business. This tool accomplishes
several common telecommunications engineering functions in one
simple tool. These examples are not
necessarily representative of what costs would be in your particular
environment. This example is a Microsoft
Excel file using VBA. If you need a non-Microsoft version
please drop me an email and I will be glad to send you another
version of the information.
Provider1 to CustomerX Functional Business Requirements -
This document was authored by McCoy as
a "Functional Business Requirements" assesment of a complex set of
implementation challenges for a major client. The company
names have been expunged, but the document contains network
drawings, narrative design response, SIP signaling sequence
diagrams, and other analysis material that is representative of
McCoy's ability to provide both technical and business saavy
information when required. It represents a complex
configuration of interactive voice response systems, multiple
contact centers, and data communications access. A primary
objective was to convert the contact centers to VoIP operations but
maintain interface capabilities with Cisco's Intelligent Call
Management(ICM) service product. Most call centers operated
Avaya ACD systems, but others were also in play at 3rd party contact
centers. Because of the client's technology plans, this
solution also included creating an ability to combine standard
VoIP/SIP signaling with more classic Cisco proprietary solutions.
McCoy has spent many years helping clients implement new standards,
but also migration strategies that allow the coexistence of
standards-based and custom solutions together.
|