462 replies
I just wanted to take a moment to introduce myself to those of you that
are not familiar with me through my writings as the author of the
Government Technology Newsletters. I am a 17 year technology
veteran (more than that if you count my tinkering before I was actually
employed as an IT professional) who started as a programmmer analyst
and worked my way up to CIO and now as a consultant. I spent 16
of those years in government IT, 5 at the executive level, so I feel
that I have a little knowledge and experience that I can draw upon as I
add to this blog and the newsletters.
My passion has been and still remains the intelligent application of
technology to solve problems. While I have always had an interest
in the technology just for technology's sake, I get a real kick out of
making technology really work
for an organization. So while you might find a strictly technical
article from me on occasion, most of what I concentrate on are the hows
and whys of technology and how best to manage it in the
organization. After all, if it isnt being managed properly,
technology is probably not doing the organization all that much good.
So if you find yourself reading this and are new to my writings,
welcome aboard. If you are an old friend, thanks for the
continued readership. In either case, I hope to continue to make
you think, inspire you to act, or in some way possible aid you as you
go about your duties in your organization.
Thanks for reading!
Ramon
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
by fatfreddy
After what seems to be an eternity, Microsoft is about to
put its next operating system out for beta.
Perhaps I am becoming jaded but the operating system releases from
Microsoft over the years have been more of a relieving of pain from the last
one, rather than excitement over new features.
In this preview: http://www.pcmag.com/article2/0,1895,1840730,00.asp you will see that Microsoft has gotten a
clue from Unix/Linux and users will no longer run under accounts with
administrator privileges. Additionally,
they are introducing tabbed browsing in IE 7, another take from an existing product
(Firefox for one). Obviously there are more
changes than these so you need to take a look.
Why do I say need?
Well despite statements like this from the article linked above,
?It's too
early to see how Vista measures up against competitive operating systems, but a
lot of the more visible features are familiar. Apple's Mac OS X
"Tiger" already has many 3D visual effects and a search interface,
Spotlight. Unix has had usable limited-rights accounts for years. But Vista's
biggest competitor probably isn't any of these?it's previous versions of
Windows. Microsoft needs to make these features more mainstream and make them
attractive to developers, while still retaining compatibility with previous
versions.?
- we all know that
there is really no competition for the OS and your ?enterprise licensing
agreement? will help make sure you make the transition to the OS when it comes
out.
Actually, there is competition, but it takes a lot of courage to switch an organization to a
new OS. I believe it can be done and
I?ll share my thoughts on how in the near future.
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
I came across this blog the other day and it made me want to
scream. http://www.mindsay.com/comments/gamecoder/37
Yes, I realize it is about game programming, but there is an important lesson in
there and I promise I will tie it back to government technology shortly. In
order to understand why I wanted to scream I have to set some context for this
blog post. Gunship was a simulation/game of the Apache helicopter that was created
by Microprose circa 1986. Two subsequent releases were done between 1986 and
1999.
The blog's author does not state which version he was working on, but in
any of the versions, the battlebuilder he created was groundbreaking for the genre at the time. Having played those
games, I would have loved the feature he created. It would have added
tremendously to the game's fun and replayability and surely would have resulted
in even better reviews and sales - thus the reason for my first scream.
The reason for my second scream was the fact that Quality
Assurance (QA) was allowed to nix such a major feature (with a pretty lame
excuse) and that the lead programmer allowed it to happen. These two things get
my gander up pretty quickly as I have worked with large government
organizations that have their QA departments wield considerably too much power
? costing the organizations time and money in the realm of application
development.
Whenever I see a QA department that has an adversarial
relationship with development, one that derives some sort of sick pleasure in
kicking work back or halting production, I know I am looking at a unit whose
management has lost sight of the purpose of QA.
The purpose of a quality assurance system is to ensure that
all products developed/manufactured and supplied meet the organization?s
specifications in full. In the world of software development it means a unit
who is working to make sure that any application developed meets the
organization?s application standards and that the subsequent code is as error
free as possible.
Additionally, QA should work to help the software development
team to identify problems as early as possible in the development process. (See
ISO 9126 for a full listing of software quality standards: http://en.wikipedia.org/wiki/ISO_9126
) It is no secret that catching problems earlier in the process is much more
cost effective than catching them late in production.
What QA is not supposed to be about is hindrance and
suppression of innovation and creativeness. QA is not about design nor are they
the design experts. While they can offer valuable feedback regarding
functionality and ease of use, that is not their primary role nor should they
have the power to "fail" a product because they don't
"like" a particular feature. You laugh, yet I have had software fail
QA because the head of QA did not like the screen design - yet the customer not
only approved the design, they suggested it.
Besides losing sight of what QA is about, management that
lets the above situations happen is grossly negligent. Software development by
its nature is a process that starts behind schedule and over budget. Most
software development is in response to a need ? one that is usually causing the
organization some level of "pain". Therefore, the desire for the
software solution is high and the time for it to be delivered was
"yesterday". In addition, whatever amount of money is budgeted for
the solution, it always seems "too much" to the client, yet not
enough for the developer. Allowing the QA unit to wield such power as to add
considerable delay and expense to a project for subjective reasons is not only bad management but poor customer
service.
In the blog that inspired me to write this piece, the QA
department's response should have been, "We haven?t encountered something
like this. Help us devise some tests that we can use to make sure this piece is
operating as intended." Similarly, the lead programmer should have had the
backbone to say, "This is an important feature that clearly adds value to
our product. Let?s work together to find a way to test it."
Please don?t mistake my ranting as a knock on QA. It is
extremely important and, if applied correctly, is a critical part of the software
development process. However, like anything else, if not performed and managed
properly, it can prove detrimental to the organization. Have you examined the
role of QA in your software development process lately? What kind of
relationship does QA have with your application developers? Are you aware of
how much time and effort you might be losing due to the relationship? Now might
be the time to check things out.
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
by nostaff
by damunzy
Regarding "What does this have to do with government?" If I had
said it was politically motivated would that have made it more
government? Politics happens in both the public and private
sector. What I mentioned but perhaps not directly enough, is that
I have seen this behavior (mismanaged QA) frequently in the government
sector. Why? I suppose part of the reason is that often
times people get placed into positions of authority (such as head of
QA) based on longevity or as a political favor in government more often
than they do in the private sector. I'm sure there are many more
reasons. Regardless, the point is that it is a bad practice no
matter what sector you are referring to. QA shouldn't be run
differently based on sector - best practices apply equally to both.
by jnatteford
by john
Both the QA department & the programmers gave up too easily.
There is a pretty good solution for this that isn't difficult to figure out. Why couldn't they store the randomly generated scenario into a file which is automatically deleted after a certain amount of time?
Then if there was a problem; support could request the scenario file, load the file, and repeat the problem.
IMO-They gave up and lost a major benefit.
A colleague of mine and me often use the term M&Ms when
describing an IT organization or a component of one ? as in ?They are just a
bunch of M&Ms?. When doing so, we aren?t referring to chocolaty goodness but
the fact that they are mired in methodology.
You know what this is.
This is when a group has decided for whatever reasons that process is an
end unto itself. When methods are what
drives the work and not the product.
I see this quite a bit in government, particularly regarding
project management. Often, project
management is looked upon as a panacea and that it can cure all ills regarding IT
projects. So the organization adopts a
project management framework designed to launch the space shuttle and then
requires all its projects to fit this framework, both large and small - failing
to realize that your project management methodology needs to scale with the
size of your project. The result?
Projects that may or may not be successful but take forever to be
completed.
Want to know how to suck the enthusiasm out of both your
staff AND the clients of your services?
Burden them with unnecessary and/or over complicated processes and procedures
in order to get anything done. Soon you
will have nothing but a bunch of automatons going through the steps and clients
who refuse to deal with you. On top of
that you will develop a clientele that wrongfully hate all project management
and any other processes and procedures because they equate it with your inefficiency
and ineffectiveness.
Are you an M&M?
If so, it might be worth taking a hard look at your processes and
methodologies and see where they can be streamlined and improved. Make sure project management is not being
done for the sake of itself, and by all means ? ask your customers how they
feel about it. If you dare!
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
by wayne m.
I believe a major subcategory of M&M is CMMI. The whole rationale of work in a CMMI environment is to create "artifacts" based on the off-chance that some CMMI auditor will choose your project for evaluation. Luckily, most project managers are aware that the project really ought to accomplish something. They take there hits when an auditor's evaluation comes back, make the appropriate gestures, and continue with the project.
I was going to begin this post with "in these tough
economic times" in regards to funding for technology, but when do you ever
have enough money to fund all the worthwhile projects that need to be done? It
is rare to have more than enough money to get the job done.
That being the case, we should always be on the lookout for
ways to add to our existing funding streams. Grant funding is one way to do
that. Oh, don?t roll your eyes. I know that while some departments live and
breathe because of grant funding, technology departments don?t often seek them
out because of the work involved ? and they are work!
However they are certainly worth the effort and can provide
a significant boost in your funding stream ? often for years.
So what kinds of
grants are available?
There are numerous kinds of grants and sources of grants. Some
of these are:
Higher Education, Grants for Non Profit Organizations,
University Grants, Non Profit Funding, K-12 Grants, School Grants, Education
Grants, Science Education Grants, Vocational Education Grants, Federal Grants, Government
Grants, Corporate Grants, Technology Grants, Technology Funding Grants, and the
list goes on.
What specific grants
within the categories listed above can be had?
This is where research comes into play. My first visit would
be to your organization?s grant coordinator (if you have one available). If you
do, make them your friend! They can be invaluable in navigating the myriad of
possibilities out there. If you do not have a resource such as this, you can
make use of the thousands of resources, paid and free available on the Web.
http://www.fedgrants.gov/Applicants/
http://www.ntia.doc.gov/top/grants/grants.htm
Before you start looking or making an appointment with your
grant coordinator, make sure you have your list of needs/projects in hand. In
fact, one of the questions I always ask when evaluating a potential project is:
"Is there any grant funding available?" That way, if the request is
from a department, they will have done some of the research and perhaps used
their inside information to determine grant-funding availability.
Also be prepared to answer whether you have "matching
funds" available. Some grants require you to put up half the funds in
order to get the grant. So don?t go looking for a $5 million matching grant if
you don?t have millions to put up as a match. However, be aware that your match
does not always have to be in the form of dollars. In-kind contributions, such
as value for work performed, employee?s salaries, hardware and software, can
sometimes be used as all or part of your match.
Things to know.
Once you begin searching, keep an open mind. Acquiring grant
funding is as much an art as a science. Know that while being super analytical
can help you as a technologist, it is a drawback when evaluating possible
grants. Know that grantors often give grants to programs/projects that in your
mind are "loosely" connected to the purpose of the grant. That?s
where the art of grant writing comes in. I am still boggled by some of the
grant awards I have seen over the years and those were a testament to the "creativeness"
of the grant writers.
Also know that partnerships are highly valued when awarding
grants. Grantors look kindly upon partnerships, especially public/private
partnerships. So it is worth your while to foster good relations with other government
organizations - local/state/federal as well as not-for-profits and even for-profit
organizations.
Understand the strings attached. Many people assume that
grant money can only be spent for the express purposes of the grantee and that
no one else can take advantage. This is expressly false. I have had grants that
were for a specific department but purchased enterprise-level hardware because
by doing so, I was able to provide the specific services to the department
required by the grant. The fact that the rest of the organization benefited
from the purchase was just a plus.
The point is you will need to understand the caveats of the
grant. Some grants assume you never actually own what you purchase with the funds and they expect that you return goods back to them when you take
them out of service. Others offer much greater flexibility. Understand the
grant to maximize your flexibility! Gray areas can be your friend.
Make sure you are prepared to be a diligent record keeper
and can show exactly where, when, and how grant funds were expended. You will
be required to do so.
Lastly, under the category of things to know, be prepared to
spend the money! You will drive your finance department and the grantor crazy
if you get funds allocated to you and then do not move forward with spending the
funds at hand. So if you get a grant, make whatever projects associated with
them a HIGH priority. Trust me, I speak from experience on this and being
cautious and frugal is not what the grantor is looking for. In their minds, if
you are not using the dollars in the time allotted, they may as well have given
the funds to someone else.
When you finally choose one or more grants to go after, it
is then time to put on your writing hat. If you haven?t written one before (and
even if you have), it often pays to get a model of a grant submission that was
awarded funding in previous years. It can also be worth your while to take a grant writing course to learn some of
the ins and outs. Additionally, if you made friends with your grant coordinator
you might get lucky enough to be able to work with a grant writer who can write
the majority of the grant and let you fill in the technical parts.
In any case, being able to bolster your funding via
grants can go a long way in giving you the ability to meet the technology needs
of your organization. Like anything worthwhile, there is an investment to make
in order to get started, so forget about easy money. But know that your hard
work can provide dividends for years to come.
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
I don?t read a lot about Oracle HTML DB in trade magazines,
nor do many of my colleagues know about it.
But the ones that are using it think it?s the next best thing since
sliced bread and are happily singing its praises.
What
is it? ?Oracle
HTML DB is a web-based application development and deployment tool integrated with Oracle Database 10g. Oracle
HTML DB enables anyone with only a web browser and limited programming
experience to quickly create secure and scalable web applications that can be
instantly deployed to tens, hundreds, or thousands of users. Oracle HTML DB is
a standard feature of Oracle Database 10g, available in Standard One, Standard
and Enterprise Editions at no additional charge.?
Essentially it is a web based application
development tool geared to those users who are creating the dozens of
spreadsheet and small desktop database applications that one finds among end
using departments. The colleagues that I
speak to tell me that it is a fabulous tool that has enabled them to get rid of
dozens of problematic spreadsheets and MS Access databases that have grown too
large and complicated for the desktop.
I haven?t had an opportunity to try it out myself yet,
but they insist that this feature alone is enough to drive the upgrade to 10G
from Oracle 8i or 9i. You might want to
check it out yourself and see if you feel the same way. Just don?t tell them I told you their secret.
Oracle HTML Product data sheet: http://www.oracle.com/technology/products/database/htmldb/pdf/Oracle_HTML_DB_2.0_Data_Sheet.pdf
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
A couple of months ago I wrote on the difference between Blogs and
Wikis. (Blogs Vs Wikis)
In the article I spoke of Wiki use by government primarily for internal use, in conjunction with an organization's intranet.
This article; (Wiki advocate sees government uses)
discusses the use of external facing wikis for government use.
I think it does a good job of showing how wikis can be used by government to carry on a conversation with the public.
And for those of you that might be interested in trying out a wiki for
either internal or external use and are committed to products that will
run in a Microsoft environment, check out OPENWIKI.
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
Every IT department usually has a mission statement. It is
usually more verbose than necessary and drones on about how the IT department
will support the mission and objectives of the organization. They (mission
statements) are usually created because of the need to document the fact that
you have one.
Values are something different. The dictionary defines
values as: beliefs of a person or
social group in which they have an emotional
investment. Your IT department is a social group. What does it believe
as a group? Are these values expressed or are they just intrinsic to the group?
Does your IT department even have shared values? Or is it just an amalgamation
of people doing prescribed work from 8 to 5?
I personally believe that values are hugely important in an
organization. I think they are the heart and soul of the work group and are
what drives us to excel. I believe they play a huge part in creating an
environment where people like to come to work and a significant role in job
satisfaction.
Values/beliefs of a workgroup come from management. Not just
in the form of words, but more importantly, through actions. Everyone can tell
when beliefs are only hollow words, just as they can tell when they are full of
conviction.
I think it is an important and worthwhile exercise to put
down the values of your unit on paper. Are they what you want them to be? Will
these values guide your unit/workgroup towards excellence? Do they conflict
with your organization's mission? If you are not satisfied with the values,
then you must work to change them. Discuss them with your staff. Talk about why
they are important and how they are guidelines for how work is performed. Most
importantly, manage in a way that is consistent with them and that showcases
them.
I recently came across a brochure from my old Government IT department
that I directed. On it, we had listed our values for our customers to see and
to judge us by. As I read these values again, several years after I had written
them, I realize that they are just as relevant now as they were then. More
importantly, I still believe them and
am confident of the fact that my staff shared in them as well. We all had an
emotional investment in them that drove us to excel.
I thought I might share them with you in the hopes that they
can help you as you develop the values for your own IT organization. Here is a
section from our brochure:
"We believe that we are different from your garden
variety technology organization because of our values. Our values set the tone
for everything we do and how we approach our work. These values are:
- We are
a customer-focused, quality driven-organization. - Flexibility,
creativity, and initiative help set us apart from the ordinary. - Teamwork:
We value individuals ability to work together to achieve a common goal. We
are able to compromise and learn from others. We promote cooperation and
building consensus when working with others. - Ethical
behavior: We maintain a personal commitment to professionalism and
integrity. We will bend over backwards to keep our promises. - Leadership:
We value those that lead by example. We encourage everyone to be a leader
in his or her job. - "Just
do it:" We refuse to be mired in bureaucracy. We will seek to change
established processes if they are ineffective or inefficient. We seek to
avoid blaming processes and personnel as an excuse for delays or lack of
progress. - We
take pride in our work and strive to raise the standards by which we are
judged. - We see
change as an opportunity."
As you can tell, these are common themes that you have
probably seen before. Individually they are ordinary statements of commitment.
Taken as a group however, they form a strong foundation for providing excellent
services to customers and the organization.
These values were quite successful for us as a group and
went a long way towards helping to create a unit that performed far greater
than one would have expected given our numbers and our budget.
The point of this essay is not to force my values on anyone,
as they may not apply to your group or situation. Its purpose is to make you
think about values for your organization. It is worthwhile to document them,
not only because it makes you examine them in the context of your situation,
but it helps to establish a road map towards goals you wish to obtain. Additionally, you might find that the beliefs
of the group, while perfect for the organization, don?t fit your personal
beliefs. That then becomes the subject for a lot of soul searching?and another
essay.
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
I had my first hands on with Linspire 5.0 over the weekend and I will
have to say I am lukewarm over the product. Linspire (formerly
known as Lindows) is a Linux distribution by Linspire Inc. that is
touted as the "Worlds Easiest Desktop Linux".
Based on that description, I had my expectations set. I was
prepared to have an install that went smooth and painless and which
recognized all my hardware. So I pulled out my test machine that
I put all my linux distributions on and started fresh by wiping the
drive as part of the install. My test machine is a Pentium
II 450mhz with 384 megs of RAM, a Nvidia Geforce II MX, an HP CD/RW, a
floppy drive, an internal ZIP drive, a generic NIC, and a Sound Blaster
sound card. Yes the platform is old, but it is a good test bed
for linux and those distributions that are well done run like a champ
on it.
The install was smooth and required less input and hid more of the
technical stuff that was going on than most other linux distros that I am
familiar with. Once it was done however, I was disappointed to
find that my sound card and my Zip drive were ignored during the
setup. This was disconcerting since both Suse Linux, Red Hat, and
Mandrake love this machine.
Ignoring the hardware that didn't work, I proceeded to use the OS to
see how functional it was. The desktop is KDE, (Gnome is not a
choice during setup) and is attractive. It is designed to mimic
Windows as much as possible. It has just about everything you
need to get going with Linux as your desktop. I have no issues
with the installed base of software you get or the environment's ease
of use. My biggest gripe is its speed. Having had previous
versions of linux on this same machine, I have come to expect a certain
level of performance and this install just seemed sluggish.
Bringing up the browser, switching applications, etc. just seemed to
take longer. In fact, Windows XP on this same machine runs faster.
My second gripe is the service that comes with Linspire 5.0 called CNR
which is short for Click and Run. It is billed as "A software
delivery service designed for Linspire users that makes it easy to
install Linux software." And in fact it does - however it is a
subscription service for which you get charged for the convenience of
having 1 click access to already free software. The CNR interface
was just too out right "comercial" for me and just screamed "BUY BUY
BUY" to me. A definite turn off for what could be a powerful tool.
All in all, for home use Linspire 5.0 is ok. But if I was going to
choose a linux desktop for the enterprise I would rather have Red Hat
or Novell/SUSE. Obviously this wasn't a scientific evaluation of
the product but more of a gut reation based on experience - and as
always, it is my personal opinion. I normally would suggest you try
before you buy, but Linspire does not have an evaluation version as far
as I can tell. And unless you have $50.00 to spend for the sake
of curiosity, I would stay with one of the free linux distributions
which you can obtain here.
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
by mdevere
I also tried Linspire and was disappoited at the lack of intuitivity: To add a language or change screen settings is not an easy thing at all. I had to drill down the different menus.
Am I so locked on to Redmont? I did expect the imitator to do it better not harder!
The Help is not helpful enough though the introductory filmstrips are nice but I don't have patience to wait for it to get to the point I am looking for.
by ctos
I live in Canada and went to buy a machine installed with Linspire 5.0 from Toronto. I brought it home, turned it on and that was it. To be truthful, I have no knowledge of Linspire or RedHat or the others. I was hoping to be able to learn from use, since i am fairly good at DOS.
It did not take me long to find that I could not connect to the CNR site as my internet would not function on this machine...it was designed for Windows 98 at the time. I tried to instal 98SE on here to remove the 5.0 but that would not work either. I tried to get answers for all the different issues from the person who sold it to me, but that was a total bust as well. As a last resort, I managed to contact a software geek I know in a nearby town and explained the situation. He was totally lost on Linspire, (every one that I asked had never even heard of it!) I would have to explain to them what it is! But he believed that if I was to put in the CD of XP upgrade and when it wants the disk for the previous system, stick in my 98 it should work. He was right, it did.
I could not USE the Linspire, I could not get rid of it, I could not get any basic questions answered to continue my explorations, I could not download from CNR and I could not get out on my Internet. This machine is now an XP and it will remain so. I was very, very dissappointed in my purchase and Linspire. I too had my hopes up with the new 5.0, they make it sound easy enough for a Window/GUI user to just use!
I
don't think Linspire is really trying to compete with Red Hat or Novell/SUSE in
the enterprise.
AFAIK,
the home user is the intended market, and here is a posting from the
Philadelphia Area Network Technology User Group, which demonstrates an ideal
solution and a pleasant surprise. This probably wouldn't have happened with Red
Hat or SUSE.
-----Original
Message-----
From:
Troy Sorzano
Sent:
Saturday, July 02, 2005 1:46 PM
To:
'PANTUGGeneral@pantug.org'
Subject:
Linspire Experiment / The cheapest computer in the world
My
mother's Win98 box died a little while ago. I needed to find a replacement for
her as a birthday gift. I took a look at Dell and all the sales flyers in the
Sunday paper. I could not really justify a $400 - $500 computer because she
only uses it for Internet access. If the computer could work with hotmail,
ebay, half.com, e-cards and open images of her grand-dogs she would be happy.
Micro
Center had an ad for a $99 Linspire box after rebate. The price was $249 and
came with a $50 mail in rebate. Then if you signed up for a Micro Center credit
card you could get another $100 rebate on any pc. So after all the hassle of
signing up for a credit card and getting approved and mailing in two rebate forms
the price of the pc is $99. Ok it's a powerspec (1405) piece of crap but for
$99 what do you expect? It comes with a scroll mouse, keyboard, CD-Rom drive,
128meg ram, 40 gig HD and AMD Sempron 2200+ processor. The case is actually
very nice and the interior was tidy. The motherboard is a BIOSTAR M7VIG 400Pro
V.1 which costs about $45 online.
I did
a few upgrades to the box. I added 512meg PC2700 ram and then pulled the CD-RW
and hard drive out of the old Win98box. I was surprised to see Win98 was automatically
added to the Boot Menu. The only problem was Win98 would not boot, not that I
really cared, because all the Win98 partitions and files were available from
within Linspire. The CD-RW drive icon was added to the desktop like a Mac
desktop.
The
real story here is not the hardware it is the software. Can Linspire replace
the functionality of Win98 for a computer novice? It seemed to do very well
with hardware detection finding the second hard drive and the second CD-RW
drive. When Linspire starts for the first time it brings up some very well done
training videos. The videos are all done in Flash 6 so we know we are ready to
surf the web and have the full multimedia experience.
I
tested the Modzilla browser with hotmail, I had been a little concerned that
Microsoft may have blocked non IE browsers. I was glad to see that everything
appeared to work fine on hotmail. The pages opened fast even after I opened several
browser windows with several tabs each. With the stock 128megs of RAM there
were serious performance problems. The biggest problem was the Linspire CNR
(click and run) agent. It was getting loaded during startup and taking about
40megs of RAM. The CNR agent is the package manager for Linspire. It allows
easy installation of software from a web interface. CNR is how Linspire plans
to make money. They charge a yearly fee for a CNR subscription but they do
allow a 15 day trial.
This
weekend will be the moment of truth. I delivered the computer on Monday and I
will be visiting this weekend. I have not heard anything from my mother about
the computer. I don't know if that is a good or bad thing. <g>
Later,
P.S.
(a week later)
I saw
my parents this weekend. I asked my
mother if she had a chance to use the computer? She replied "I've been
using it all week, why?" Well I guess no news was good news. She did ask
my sister to help setup her Epson Stylus 400 printer. The cool thing was my
sister got the printer installed and working. She has never even heard of Linux
and was able to get it working. I think Linspire is a great option for the user
with limited computer experience that only needs to surf and print.
Troy
August 11th, 2005 was the debut of NVD (The National Vulnerablility
Database) by the National Institution of Standards and Technology
(NIST). Quoting directly from the NVD website "NVD is a
comprehensive cyber security vulnerability database that integrates all
publicly available U.S. Government vulnerability resources
and provides references to industry resources. It is based on and
synchronized with
the CVE vulnerability naming standard." The database is funded by the Department of Homeland Security's National Cyber Security Division.
So what NIST has provided us in the form of NVD is a comprehensive one
stop shop for locating information about vulnerabilities in products
presented in an easy to use format. I spent a few minutes with
the database, popping in the names of software vendors and you
certainly will find tons of info, even on software packages that don't
pop into your mind when thinking about vulnerabilities - such as your
back up software.
This is certainly a site you want to bookmark and make visiting it a
regular part of your security protocols. You can get to it by
clicking here.
The recent news reports
that I have read regarding organizations, both public and private, who were
impacted by the Zotob and Rbot worms is disconcerting. To the uninitiated,
those who were affected did not practice good patch management.
However, those in the
trenches know that keeping up with patches, especially at the desktop level, is
a daunting task. On top of that, patch management is just a small part of total
desktop management. Application installation, software updates, hardware
maintenance, training, security, and more are all part of desktop management.
In 1996, Gartner Research announced
the average Windows 95 desktop cost $10,000 a year to own. This includes,
besides the activities mentioned above, the direct costs of user support, lost
productivity, downtime, and administrative costs including depreciation, and
finance charges.
Some would argue even then
that the total cost of ownership (TCO) computed by Gartner was either
overinflated or underrepresented. Whatever the cost is today, (based on your
own TCO) there is no arguing that managing the desktop takes up a significant
amount of an IT department's total resources.
The workload to manage
desktops is such that a whole market of desktop management tools have sprung up
to help us "control" them. Novell Zenworks, Intel Landesk, Hewlett-
Packard OpenView, IBM's Tivoli TME10, or Microsoft's Zero Administration Kit
are just a few examples. And even with these tools, the TCO for a PC just seems
to stay the same or is even increasing.
So given all this, don't
you have to wonder if it's worth it?
I know I did a few years
ago. I looked at my organization's IT budget and the amount that was being used
to purchase and support PCs and said "there has to be a better way".
That better way, after
some significant research and testing was a hybrid solution consisting of thin
client technology, Citrix, and Linux that would be phased in over time.
In a nutshell, the plan
was to provide a "desktop" to the end user via their browser and run
all their applications either directly from a Web server or from a Citrix
server. Their individual machines would have their OS replaced by a very thin
build of Linux and all machines purchased (new or as replacements) would be
Linux-based thin client machines.
This desktop solution, in
my opinion, was more secure and less susceptible to end user
"intervention", virus breakouts, and emergency patches; thin clients
were easier to install and trouble shoot, and workers were no longer
"tied" to their workstation since they could get their own tailored
desktop from any machine in the organization.
In order to succeed, we
had to do two critical things. Get buy-in from the organization and
make sure we had a solid network infrastructure that had a very low
latency.
The buy-in began with the IT
governance committee. Fortunately, we had a very astute committee that, after
seeing the research and the solution in action, quickly bought in to the idea. The
next step was to eat our own dog food. The IT department made the move to this
solution. From there, it was time to woo top management. We knew that if they didn't
understand what was going on, the plan would eventually fail. Again, at the
time I attempted this plan (and probably why I was comfortable in doing it) we
had an incredibly sharp and IT-friendly administration. From the CEO to the
CFO, they were on board and active supporters.
Meanwhile the
infrastructure work was going on, and we were revamping and expanding what was a
tired network to start with. So we began putting the solution into place,
department by department, and you know what? It worked great! Yes, we initially
had some kinks, but once they were worked out the network was greatly improved.
Unfortunately, this story
has an incomplete ending. While doing the project, our community voted to merge
local governments. So when the time came for the merger, we were not quite
finished. Overnight, the whole environment that had been primed and ready
literally disappeared. That ended the solution.
The point of this story
though is that I know the solution works and you can be rid of a great deal of
desktop headaches by ridding yourself of a fat client machine. I have seen the
beginnings of it, I know what the TCO was turning out to be, and if I ever get
the opportunity again I will seek to implement a similar solution.
And yes I realize that
this solution doesn't fit 100% of the users but it works for the vast majority.
And I would rather be managing a very small subset of needy fat client machines
than an entire organization's.
It?s a bold move, switching from fat client
machines to thin client and delivering an organization's desktop through a Web
browser. But with the proper planning and execution it can be done. Just make
sure you start at the beginning of
your CEO's next term in office.
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
by emil.vincent
Sounds very interesting, we have the same issue with desktop management. What was your plans for mobile notebook users under this setup, who also need to work off line at times?
by ktharbi.c
I am not fully agree with you!!! , I think that idea depend on your environment , and if the organization use the full facility of his operating system (like Windows), he can reduce his costs in managing the clients , and also if I go to your idea I think I must do a big investment on servers , networks and software (like CITRIX), and also I have the single fall point problem if that servers have any problem , and also I lose the power of the clients , this is what i think!!!
Can you help me with more information.
by wayne m.
Return of the Mainframe! Having grown up in the days prior to networking where there were dumb terminals connected to a central computer, I can assure you there is a need for distributed processing that drove the migration away from the mainframe.
As noted above, one of the prerequisites for a complete thin client approach is a large amount of network bandwidth. Two more that are equally important are low latency and high availability. Finally, the "network" needs to take on the responsibility for storage and processing power.
Due to the combiniation of processing power and low latency available at a desktop, the computer user interface has grown up to be much more supportive of the user. For example, most word processing packages now provide keystroke-by-keystroke spelling checks. Some user interfaces are context sensitive, with areas of the screen enabled or disabled based on user data entry. These types of functions are feasible because we can throw excess processing power at the problem without affecting user response times.
For a reminder of the user cost of thin client technology and centralized processing, pay attention to the response times the next time you are at a gas station. I am continually amazed at how long it takes the pump to realize that I have stopped pumping gas and returned the nozzle to the recepticle. This is the same reaction users often feel when migrated to a Citrix or Web-based version of a familiar desktop application.
Regarding support cost, the transition back to centralized processing and storage has lead a return to 24x7 support. Even routine maintanence needs to be scheduled at off-hours. Any sort of outage during standard working hours is a crisis affecting the entire company.
I have touched on mostly the technical issues and I feel that true distributed processing is still in its infancy. Current web browser software does not provide near the level of user interface support that people desire and need. There is also the problem of inadequate funding and staffing for the underlying support professionals, but that is another topic.
Regarding Emil and Harbiks questions and Wayne's comments. Emil, we put Windows and
Office on their mobile PCs with the eventual plan that they would
switch to Linux and StarOffice. However they were encouraged (and
most did) to find a network connection in order to use a Citrix
session. We employed the Citrix secure gateway as well as RSA
SecureID Authenticators for anyone connecting outside our network.
Harbik, I have to laugh because you bring up some of the same points
people used to scoff at the idea when they first heard it. Yes
you have to invest in servers, but that is offset by the cheaper
desktops/thin clients and keeping them in service longer. As for
single fail point, Citrix provides fail over and we also built
redundancy in for those users that HAVE to be able to get on no matter
what. Also, in 99% of network environments, if the power goes off
- PEOPLE DONT WORK. Why? Because their files are on the
network servers and they print via the network. Same as if the
network goes down (which should not happen that often). So that
is a false arguement. In fact, that exact thing happened in the
environment that I work in yesterday. Power was lost to the
building but generators brought enough power back on to run the lights
at low level and power a PC. However, the switches in the closets
on each floor had very small back up power supplies which did not last
long and then guess what - everyone sat around looking at each other
because of a lack of network connectivity - NO MATTER that
everyone was using a fat client.
Lastly, of course this solution depends on your environment - as do ALL
IT solutions. If it fits use it, if it doesn't don't or tailor it
for your environment. I think though that this solution is
appropriate to more environments than people think. They just are
too comfortable with the status quo.
Wayne - Gonna have to disagree with your there. Response time was
so good that most people did not realize they were in a Citrix
session. My demonstration of the environment was to play PINBALL
that comes with Windows with full color and sound. That always
made a believer out of folks. If you are going to compare a gas
station to your network, go ahead, but that was no comparison to
ours. Fact was, response times were extraordinary. The
whole thin client/Citrix solution is FAR from infancy.
Thanks for reading!
Ramon
by bobbypr
Hi folks!
Once I had to give advice to a client about the same matter. Unfourtunately the advice was against the thins clients. Maybe this could apply for you. Check the problems that I found with the thin clients at this site:
- Very slow connection to applications like: Word, Excel, and a Data Entry Windows App.
- Sometimes Windows freezes
- Data Entry App. sometimes took from 10 seconds to 3 mins (with timeout feature turned off) to bring a single record. So basically they were getting a timeout screen often.
- Poor screen resolution. Some Windows colors look sandy.
- Option that you set on Word (like dictionaries, language, auto correct) are lost on each reboot. This options vary between users, and offices.
- Can't bring work made at home in a floppy because theres wasn't one drive on the thins. (lots of lawyers depend on this)
- If network is down nobody can keep working offline. (with desktops they can keep working and even print because theres always a printer that is connected directly to a PC to prevent this events)
- The thins generated more network traffic.
- It created an unexpected task for the networking department. Users started to flow to their offices to upload documents to the server.
- On the maintenance side, there where not many vendor that could give hardware support to this equipment. So they were under the mercyless hand ($$$) of only one vendor. Desktops hardware is easier to find and troubleshoot. More vendors = competions = low prices.
Of course, the thins needed less maintenance, administration comes down to zero, security is a plus, the possibility of getting a virus via floppys or any other media is reduced, but with so many disadvantages...
Roberto D?az
by mr l
Ramon,
Some details please (we can deep-dive offline if you prefer)...how many seats, application environment, how many customized/home grown apps, etc. Not to minimize, at all, the project you undertook, but without knowing the scope it's hard to judge. I have better than 10,000 seats to worry about...3,000 of them at a corporate campus with a wide variety of apps, both shrink-wrap and home grown...and I'm uncomfortable at first pass even thnking about expecting Citrix to support them all.
I'm all for dumb terminals, I grew up with them, but my users have got to come first
Mr. L,
We were at around 300 seats when we had to
stop. Putting 50 clients per server. Saw no reason not to
keep going - bandwith was looking good and we had built our
infrastructure to handle the full amount of desktops in the
organization - about 3500-4000. Had a good mix of applications -
Of course Office (which by the way did not display any of the negative
tendencies that were mentioned above by Mr. Diaz. We then had
multiple home grown applications, some were delivered via a terminal
emulator back to a mini computer (very old apps) some were in VB that
ran against SQL Server, some were comercial (a large inmate tracking
system) fat client against Oracle database, and web apps that had to be
run via IE which we served up as well. In short, we had a large
variety of apps that covered the gamut. Like any roll out, we had
some niggling issues we worked through, but we made all the apps
work. Biggest problem was an app that assigned an ID based on the
machine it was running on. Can't remember the exact problem, but
the solution was to get the vendor to give us a fix where it derived
the ID from the mac address of the NIC in the machine.
Obviously in your situation you are talking about a much larger role
out - but I am a believer that this solution scales so long as you have
built your infrastructure out correctly. The nice thing about it
is that you can run both environments in parallel and they co exist
nicely. You can add more as you are able to - its not like you
turn out the lights one night and bingo everyone is on a thin client
running Citrix.
As I said in the article, it is a bold move that takes alot of careful
planning. But it is a strategy. It doesn't have to be
accomplished over night and can be done over a period of time.
There are many people who like to nay say about it without putting a
lot of thought into it. I spent a considerable amount of time
looking into it before making the decision to go forward and never
regretted it. Unfortunately I ran out of time, otherwise I would
be sitting here writing this with a much larger installed base than
what we got to. However, as I said before, given the opportunity
I would do it again in a heart beat. The rewards we were reaping
were too nice to be ignored. Supporting the Citrix clients was
much easier than a traditional desktop and troubleshooting was a
breeze. Virus protection/security was easier and more centralized
and I could go on and on. But this whole concept leads to debates
not unlike Linux vs Windows - it is religious and personal to
some. I personally look for soultions that work and can give me
as much freedom to provide solutions to my organization that I can for
the least cost. I feel/felt that this is one of them.
But don't just take my word for it (not that you would). If I
picqued your interest just a little, try some more research. Thin Planet is a good place to start as well as Brian Madden's home page.
Hope this proved informative to you.
by mr l
Ramon,
Thanks, that's exactly what I was looking for, and I'll be digging deeper. I'll keep you posted as I dive into this.
IT Makes Sense,
I'm afraid I no longer have access to my
business case. :-( However, business cases are always
organization specific and usually don't apply across companies.
Just as Gartner numbers do not necessarily equate to numbers in your
own org. I certainly would enjoy doing one again though as both
the hardware and software has changed (both in price and capability) in
the 3.5 years since I wrote the last one. Now to find an
organization in Florida that is in search of a CIO/Director with a bold
vision that will let me do one for them ;-)
Sorry I couldn't be more help,
Ramon
Hi Ramon,
As The Fates would have it, the discussion you prompted with "Why have a PC at all?" was a very timely arrival as our local government IT governance committee is deliberating a change to our desktop deployment strategy from fat clients to thin clients. The Citrix thin client model has worked exceedingly well for us in the areas of remote access, for smaller departments without the resources for replacing PCs, and to distribute our PeopleSoft applications enterprise-wide.
I forwarded a copy of "Why have a PC at All?" to our governece committee leader and she asked 2 questions perhaps you can help me with.
1.
Hi Ramon,
As The Fates would have it, the discussion you prompted with "Why have a PC at all?" was a very timely arrival as our local government IT governance committee is deliberating a change to our desktop deployment strategy from fat clients to thin clients. The Citrix thin client model has worked exceedingly well for us in the areas of remote access, for smaller departments without the resources for replacing PCs, and to distribute our PeopleSoft applications enterprise-wide.
I forwarded a copy of "Why have a PC at All?" to our governece committee leader and she asked 2 questions perhaps you can help me with.
1.
WhoHi Ramon,
As The Fates would have it, the discussion you prompted with "Why have a PC at all?" was a very timely arrival as our local government IT governance committee is deliberating a change to our desktop deployment strategy from fat clients to thin clients. The Citrix thin client model has worked exceedingly well for us in the areas of remote access, for smaller departments without the resources for replacing PCs, and to distribute our PeopleSoft applications enterprise-wide.
I forwarded a copy of "Why have a PC at All?" to our governece committee leader and she asked 2 questions perhaps you can help me with.
1.
WhoisHi Ramon,
As The Fates would have it, the discussion you prompted with "Why have a PC at all?" was a very timely arrival as our local government IT governance committee is deliberating a change to our desktop deployment strategy from fat clients to thin clients. The Citrix thin client model has worked exceedingly well for us in the areas of remote access, for smaller departments without the resources for replacing PCs, and to distribute our PeopleSoft applications enterprise-wide.
I forwarded a copy of "Why have a PC at All?" to our governece committee leader and she asked 2 questions perhaps you can help me with.
1.
WhoisRamonHi Ramon,
As The Fates would have it, the discussion you prompted with "Why have a PC at all?" was a very timely arrival as our local government IT governance committee is deliberating a change to our desktop deployment strategy from fat clients to thin clients. The Citrix thin client model has worked exceedingly well for us in the areas of remote access, for smaller departments without the resources for replacing PCs, and to distribute our PeopleSoft applications enterprise-wide.
I forwarded a copy of "Why have a PC at All?" to our governece committee leader and she asked 2 questions perhaps you can help me with.
1.
WhoisRamonPadillaby lamparth
Affordable desktop recipe
Ingredients
- Cheap Dell PC
- Norton Ghost Corp Edition
- Universal Image Utility
- SUS or WUS
- NAV
- Books on Group Policy and Ghost
First take a blank PC put all the software on it which 80% of your company uses, than make an image of it using Ghost and UIU/Sysprep. (UIU is a standard driver db, that allows you to use images on different PC Hardware). Push out the image whatever way you want PXE, Client Install, CD etc? Use Sysprep to have the system add itself to the domain.
Push out NAV and other needed applications using MSI or Automated Installation Files. Use SUS and NAV to keep the machine patched and roaming profile to synchronize the local user data with the server for backup purposes.
Done?
by dpenrod
In the last year I have implemented a Citrix environment at our company, and it is working well.
I am the sole system administrator managing 100 desktops in 3 locations. About 75 desktops at our corporate office.
My cost justification was to free up more of my time from help desk support to doing more systems admin and planning. Also to eliminate the need for PC upgrades.
I proposed the Citrix implementation when we decided to purchase a CRM package, that would have required the installation of a DB server at each of our 3 locations, and the Syncing of Databases between them. Citrix allowed all desktops to be run on Citrix servers here, using a single DB server for the CRM, eliminating the need for DB servers at our other 2 locations.
I purchased 3 dual processor servers to host the apps. THeye are set up identically. if any server fails, the others keep running providing very high availability. I ended up dedicating one server for testing, as 2 servers seem to handle our needs fine.
We run the entire MS office suite, CRM, ERP, Outlook, and a handful of other apps on the Citrix desktop. Users run all their apps except autocad on the Citrix desktop, we have removed the apps from their PC's, reducing desktop complexity and admin costs.
Users love the fact that ALL of our apps are now web enabled via Citrix secure gateway. They can access their apps from any web browser, at home or on the road.
My users on slower desktops (P-350s) indicated their apps run MUCH faster on the server desktop.
I can now roll out an application to all users in an hour by installing it on 2 servers instead of 100 desktops.
Our fat client apps (CRM, ERP) required desktop hardware upgrades with each major update. Now we dont have to upgrade PC's any longer. And our network traffic has been greatly reduced, since all those desktops now only need about 24Kb bandwith to run the Citrix application, instead of several hundred kb to query the DB servers. Most of the network traffic is now between the citrix servers and the DB servers, which in network terms are close and fast to each other.
We had some intial latency issues with our remote offices over the WAN, this was due to some Citrix version and config issues, which once worked out seemed to disappear. Our remote office users have had to adjust to slower print times, print jobs taking a minute or two to print instead of being nearly instantaneous. (as all printing is generate from the Corporate office citrix servers, instead of their local desktops) In server based computing implementation, pay special attention to planning for your printing needs.
My users have trouble telling whether the app is running locally or via citrix, they are identical. This has caused problems on a few occasions.
I have used Ghost images before, and it didnt work out as well for me as we have purchased PC's piecemeal over the years (weve never had the budget for wholesale standardization of desktops), and I never had enough desktops with the same software configuration to allow me to scale up the number of desktops per ghost image. Now I have only a couple ghost images I can use for all Citrix client PCs, as there is is only the OS and Citrix client on most desktops now.
The majority of my help desk calls were software issue related, and those have all but disappeared on the desktops since Citrix.
I have only 6-7 laptop users. They use both Citrix and local applications when they are traveling. Once internet data access becomes Ubiquitous, (like cell phones are today), I hope to move my laptop users to Citrix only.
In reading the posts here, ive found many of the cons to be wrong or mis-stated.
Its probbably unusual for a company our size to move to Server based computing, most of the time it seems to be large companies who use it, their economies of scale provide greater benefits for the hugh number of desktops that are affected. Many of the Fortune 500 are using Citrix. I know locally that Nationwide insurance is using Citrix on about 450 servers to service 50,000 client machines all over the world.
We were a long time Terminal service user for only 1 app. Our ERP fat client app for remote offices. I used to think of Citrix as Terminal services on Steroids, just lots of extra bells and whistels that were nice, but not necessary.
In the past few years Citrix has changed into a complete Solution that goes way beyond simple terminal services.
To summarize my experience, server based computing, especially the Citrix suite, provides robust, reliable, secure, and manageable application access, to anyone, anywhere, anytime. And it does so with Lower TCO.
Gov. Kathleen Blanco has stated that ?everyone needs to
leave New Orleans
due to flooding from Hurricane Katrina.?
What an overwhelming statement that is.
Even with all the coverage that we have had regarding the hurricane, it
is still hard to grasp the enormity of this disaster.
During times such as these, we often talk about business
continuity and disaster recovery planning.
However few if any local governments are fully prepared for catastrophe
of this magnitude. While I am certain
that some of the City of New Orleans
plans are still viable and are being put into action (particularly regarding
emergency services) many of their plans for continuity and recovery have been
negated due to the sheer size of the event.
There is no doubt that in many areas the government as well as individual
citizens will be starting over.
It is times like these where State and Federal resources as
well as non-profits come into play to help the citizens and the local government
get back on its feet. We are fortunate
to live in a nation whose government and citizens are quick to respond and are
technically and financially able to help out.
On that note, rather than talk about the myriad of IT issues
that are brought about due to disaster, (there will be plenty of time for that)
I will just end with a couple of web links of significance:
The American Red Cross
Disaster Center - Comprehensive list of relief organizations.
Over the years I have had the opportunity to experience IT
in the organization as it has transformed itself from the "glass
house" through the PC "revolution;" client servers; web-centric
computing; and now the amalgamation of all of these evolutions as IT strives to
be a true "business partner".
Interestingly, I find that for those in several of the
government organizations that I have come into contact with in the last couple
of years, the concept of IT as a "business partner" is more of a
figment of the imagination than a reality.
If you asked people in the departments that IT was serving
what the relationship between them and IT was like, they would say that their
IT was a business partner in the same vein that the Soviet Union was a business
partner to Poland, East Germany, or Czechoslovakia during the Cold War.
One characteristic view that users in these organizations
have about their IT department is that IT operations of any kind can not exist
outside the IT department's control. And should such "rogue"
activities arise, they are to be squashed or consumed.
Another common view of users was that IT departments were
monolithic and unresponsive - filled to capacity with bureaucratic "goodness"
to insure that each project progressed at glacial speeds.
Of course, these two views led to a lot of user frustration.
From their perspective, if the IT organization were nimble and responsive to
customer needs, they wouldn't need to engage in rogue activities; and to make
matters worse, they felt that taking matters into their own hands was the only
way to get around the bureaucratic bottleneck blocking progress on their
various projects.
The end result of these competing views is an angry customer
base that is frustrated by IT's lack of response and its attempts at squashing
the users' attempts at helping themselves.
Why does this happen? I speculate that the above situation
arises when IT remains stuck in its legacy as a "glass house"
mainframe shop, or from IT's reaction to a decentralized computing environment
that seems to have gotten out of control.
In either case, the end result is a heavy-handed,
centralized IT shop that rules with an iron fist. This kind of IT department is
likely to struggle in building a true partner relationship with its end-user
departments.
We all know the benefits of centralized IT units:
Procurement of hardware and software is possible on the broadest scale within
the organization and centralized operations generally produce substantial
economies of scale. Additionally, a centralized staff eliminates redundant
functions, and there is a greater adherence to standards and a unified vision.
Conversely, in a highly centralized IT department, there are
problems like the ones mentioned above. Some of these are: tendencies towards
bureaucracy, lack of responsiveness, and decision-making in a vacuum.
The alternative to this is a completely decentralized IT unit--agile and responsive, in tune with the needs
of the business, and more tightly integrated with business goals and
objectives.
Yet purely decentralized IT structures also have drawbacks,
such as duplication of effort, lack of standards across the organization,
islands of excellence at the expense of other departments, higher total
procurement and operational costs, lack of integration, etc.
I have always been a big believer that a balance can be
struck between completely centralized IT and completely decentralized
IT--hopefully deriving the benefits of both.
In my opinion this balanced IT structure has
"enterprise" functions being performed by central IT such as: data
center, network and infrastructure operations, e-mail, procurement, standards
architecture, and cross-departmental application development.
While department-level functions include help desk
operations, departmental application development (up to a certain size), and IT
strategy and planning for the department. All of these activities coinciding
with standards which they help develop along with central IT and a strong governance
committee.
In order for this hybrid approach to work though, there has
to be a strong sense of cooperative and collaborative management at the level
of the CIO and with the departmental IT management. I like to view this
approach as a representative government model where the departments actually
have a say-so in their IT operations.
Ultimately, there is no "right" answer to how IT
should be structured in every organization. There are success stories for each
model (which I am sure many readers of this blog will point out). And we have
to take into consideration the influence of the culture and structure of the
organization as a whole when determining the optimal IT configuration.
Yet I am willing to bet that at the end of the day, those
organizations which choose a model which is more democratic in its structure
and processes are more likely to end up as true business partners to the
organization.
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
by rexworld
Interestingly, here at CNET we are going thru a transition from a strongly centralized IT function to the kind of hybrid you talk about. I don't think TPTB have fully fleshed out the plan but it's looking like things such as the data center (co-location facilities, etc.) will be a centralized IT function whereas application development (i.e., News.com and TechRepublic.com) will be dispersed into the respectice business units.
We've swung the pendulum wildly here at CNET, going from highly dispersed to highly centralized and now to this hybrid model. I think it remains to be seen whether this hybrid approach works any better.
by kirk webber
I have been a Gov IT worker for about 11 years, and I have also seen and heard about problems with both centralized and de-centralized IT organizations. It seems like in many organizations, the pendulum swings from one extreme to the other (centralized to de-centralized), with re-organizations every couple of years. I believe a balanced approach is often the best (depending on a lot of organizational factors), but I admit, I haven't been involved with one of these yet.
I think one of the (if not THE) key to a successful organization is communication. There must be free, open, bi-directional communication on a regular basis, no matter whether the IT organization is centralized or de-centralized. If you have IT assigned to the business line departments, they must communicate both with their own department as well as central IT. If you have centralized IT, they must be sure to have that close customer communication. In order for IT to properly service the needs of the Agency, they must understand the needs of the Agency. And they cannot get that understanding by hiding behind the walls of the IT Department.
by wayne m.
I would think the balance point will be closer to the fully decentralized model and certainly not at a "mid-point" especially in geographically disperse environments.
I have noticed that the further one sits from the IT department, the worse the service gets. Sit next to the IT department and things are great. Sit on another floor in the same building and things are okay. Sit in another building and you better practice your Solitaire skills. Sit in another city or state and you will likely be doing your own "rogue" IT and hoping not to get caught.
I would also question how well economy of scale holds up once you get outside of a single building or campus. For hardware, I am not sure centralized purchasing saves money, if you add in the difficulties of issuing a purchase req, shipping between headquarters and the site, and potential travel time to configure systems. Memory upgrades are very expensive when you have someone trying to explain to a user over the telephone how to open up the computer to see what memory is installed and the misorders as offices get the quantities and types wrong.
I find the costs of centralized IT far hgher than that of decentralized and would prefer to err on the side of decentralized.
In a statement on Monday, Peter Quinn, chief information
officer for Massachusetts, said that the state will support the newly
ratified Open Document Format for Office Applications, or OpenDocument,
as the standard for its office documents and not proprietary formats
such as Microsoft Office. Whoa! That is a gutsy statement
indeed. You can read more about it here.
Since MS Office is such a large part of the MS Enterprise licensing
agreement, I have a strong feeling that there will be more changing in
the State of Massachusetts IT environment than MS Office. If
Novell isn't camped out on the CIO's doorstop, they should be.
Personally I applaud this bold move. What do you think?
by ironfist03
Not knowing all of the details I would say it just does'nt make sense. I am sure taxpayers who are to foot the bill would agree as well as the multitudes of state workers who now are going to be using applications that are new and uncomfortable to them. I'm not bashing state workers but anything I.T. does to slow them down more is downright bone headed. Peter may end up with a new applications platform however, the cost in lost productivity due to resistant and disgruntled end users over i'm sure is a vast network needs a second look, or a 3'd or 4th.. I'd roughly guess millions in multiples of ten. And thats just the human side. Heres a quick ballpark guesstimate; take 1 hour of every users productivity every day for say 6 months (conservativily) and multiply it by their salaries, now take that and cascade it into what would that have held up for an hour and the other things that would have held up for an hour. It grows exponentially to insane purportions in a very quick time frame. Not to mention that new hardware infrastructure and applications costs.(open source is often the gift horse you "should" have looked in the mouth) In other words it is barely competetive, especially if your purchasing department is doing their job and getting the volume deals they should be getting from the redmond boys. I did'nt even mention compatibility with other states documents, every moment you have to translate coming or going your're burning time for someone that is cascading to someone else, etc.. Add up daily traffic and that alone is a significant block of time. If Peter does not know time is money he's in the wrong occupation. I myself have issues with the redmond boys, by paying attention to the looks of shock and horror and vocal protestations of the end users when I mentioned moving away from microsoft applications it became immediatly apparent that the human cost needed to be a major contributor in the decision. I.T. has to be the enabler not the stumbling block. A personal issue with the redmond boys which on the surface is what this decision appears to be should never be the overriding factor when making a sweeping change such as this.
by johnnysacks
Ouch! I'm assuming the state has some pretty tight software license compliance controls so truckloads full of cold hard taxpayer cash have already been carted out to Redmond and poured into the Microsoft coffers.
The cost benefit of performing this switch at this point in time based upon expected future software licensing expenditures needs to be considered. Re-training of users is an issue that should not be ignored but I guess it's hard to imagine that there are really people out there who are that untrainable vs. those who's sole purpose is to perpetually whine about every change imposed upon them.
by debuggist
Wasn't the Massachusetts' AG (at the time) one of the strongest
proponents in the Microsoft antitrust litigation a few years ago? If
so, then this is not so surprising. However, it is bold. I wouldn't be
surprised though if this is a negotiation tactic to lower the state's
licensing costs. This only affects state offices. What about the local
government offices? Will they switch, too? Or are they already part of
the deal?
by ergodic
I have been using Word Perfect Office since since the days of DOS and
still use it sporadically since we are mostly using Linux and of
course OpenOffice.org Writer which is uses the odt format (Open
Document Format).
We join you in applauding Massachusetts move. Very interesting.
by andré2
Anyone familiar with Microsoft office, the Wordperfect office suite,
and Sun's Openoffice.org and Staroffice, should be asking why did they
stick with Microsoft for so long?
First of all, word processing and spreadsheets, the core of any
office suite, have be around for a long time, and are all that most
users need, and that at fairly basic levels. Most users would do
better to disable the more advanced features of most office
suites. At basic levels, word processors and spreadsheets are
very similar to work with - learning to use one is learning them all.
For the vast majority of users any advantage of Microsoft office is
marginal at best. Sure, they claim to provide better
support. But Massechusetts is big enough to provide the little
support needed, very economically. The Wordperfect suite
provides a much better word processor, and is less
expensive. Openoffice is free and for the vast majority of
users is more than adequate. Openoffice and a number of other
office suites are at least in beta with versions that already support
the new standard. Given the (reasonable) attitude of Massacusetts
in the past toward the monopolistic behavior of Microsoft, it would be
very surprising if Massachusetts DID NOT fully support this new
standard. I would expect Wordperfect to support this new
standard, giving a full range of excellent software to choose from.
This gives Microsoft the opportunity, perhaps, to target the softwood
industry to continue their appetite for monopolistic practices.
(They're in the right state, why not? It'll take a while before
consumers wake up and challange that protectionism.)
In sum, an excellent move by Massachusetts.
by dosmaster
I too applaude this move. It is a gutsy thing to walk outside the safety zone and try something new. That's probably why there are already a few "oh gosh, what if it doesn't work?" posts already made. I won't worry about whether the sky will fall on Massachusetts IT for trying this. Rather, I thank them for taking the risk (however big anyone else thinks it is) and initiative to try something new that could honestly be of menetary benefit to the sate taxpayers. The success of this change will be a determining factor in how seriously I consider such a move. And believe me, I AM considering such a move...
I can't believe I failed to mention this web site when I wrote about grant writing a few weeks ago. Grants.gov
is an excellent place to begin your search for grant
opportunities. Not only can you search for grant opportunities,
you can download grant application packages and even apply for grants
through Grants.gov. Add this site to your list of important
bookmarks and begin to expand your budget with the help of some grant
dollars today.
Let?s open a can of worms and make this week interesting,
shall we? Is e-mail and Web use monitoring good or bad in a government work
place? I bring this topic up because I just read an article that quoted a recent
survey in CSO magazine that said that 61% of survey respondents allow e-mail
content monitoring while 75% allowed monitoring of Web use.
This made me wonder about government use of employee
monitoring. My guess is the percentages would vary depending on the
organization's mission and amount of regulation that they must work under. For
instance, the Department of Defense and the CIA probably do more monitoring
than a local government, for instance. But before we get into who is monitoring
and why, let?s talk about the basics of monitoring.
Monitoring can be defined as storage and review of employee e-mail, files, and computer
activity. By default we engage in the first part of the definition through our
normal IT activities. E-mail and files are regularly backed up for recovery
purposes and network activities, such as login and logout times, are often part
of log files kept by the network operating system. Our Web activity record is
kept by default in the form of history files, cookies, cache, and logs on
servers, as well as on the clients themselves.
The key then to "do we monitor" is review. Do we allow the review of e-mail, files or Web
use in our organization? I am willing to bet that most of you reading this will
say yes to that question. In fact, I am pretty sure that there are extremely
few government organizations that would disallow the examination of computer
records and e-mail as part of an investigation into harassment, theft, or other
conduct not permitted by the organization. Therefore, the majority of us
participate in monitoring at the lowest level.
But when most of us hear the term monitoring, we aren?t thinking about the passive, low-level
monitoring described above. Most of us think about active monitoring tools and
active/purposeful review of information collected by those tools.
From keystroke loggers to e-mail and Web filtering/blocking,
there is a tool made that we can employ to record/stop the activity. The
question then becomes ? should we?
Proponents of active monitoring usually give the following
arguments for doing so:
- Increases
employee productivity. - Security
? protects confidential information. - Increases
in network performance. - Aids
in regulatory compliance. - Aids
in network/capacity planning.
Detractors of the practice usually give the following
arguments:
- Breeds
contempt amongst the workforce. - Lowers
productivity. - Opens
the organization up to litigation. - Can
create storage and retention issues. - Can
decrease network/computer performance.
First and foremost, the answer to "should we?" should
not come from IT. This is strictly a management and HR decision and the
decision to monitor or not and to what degree has to come from them. That?s not
to say that IT should not play a leadership role in bringing the issue to
management's attention ? after all, the tools and capabilities do reside with
IT.
In fact, IT must play a strong role in making sure that
those who will be making the decisions understand not only the capabilities
regarding employee monitoring but also understand the drawbacks. It is with
this information that management can weigh all the pros and cons associated
with the issue and choose the course that is best for the organization.
No matter what level of monitoring is used, (remember I
argued earlier that we all participate in monitoring) the policy should be
disclosed very clearly. Make sure your acceptable use policy defines what a
violation is and what the consequences are of violating the policy.
Personally, I have always been a big believer of blocking certain
types of activities. I think it is in the best interest of the organization and
its employees to protect the workers from themselves (to a certain degree.) For
example, I would rather proactively block pornography and hate material rather
than check up on people, or deal with the results of complaints that might
arise from inappropriate use.
Secondly, given open records laws, the more you retain
regarding employee behavior, the more fodder there is for unwarranted ill will.
For example; if you log Web site activity for the organization and you allow
"casual surfing of the internet during lunch and breaks," you will
likely find that non-work related Internet activity comprises a large
percentage of total Web activity. It won?t matter when and how the activity
occurred to the citizenry when they read a headline screaming "Government
Employees spend majority of time on eBay!" Think about that when factoring
in the pros and cons of monitoring.
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
by zlitocook
I have been a contractor for three years and a employee of two companys. They all had an email policy and internet usage policy which was enforced buy three strikes your out. Or if you do one of the big nono's like sending porn or ethnic email you were let go that day. People forget that you work for the company and you use thier equipment and network bandwith. Most companies state that any work, ideas or other things done on company time is the company property .
I dont like the governmemt spying on me at home but that is not the same thing. I am paying for a service and with paying for it the service provider works for me. So I should be able to say what should be done and who should see what I am doing.
The company I am now contracted to has a free wireless conection in the lunch room, but it has it's own useage policy. You sign a contract/waver stating that you know it is an open connection and the company provides no protection.
I do not care if any one looks at what I do on company time! I have enough problems to worry about with in the company and do not have time to play around. Think about what you do at work and the amount of time others waste just playing around. Would you want the person who is suppost to give you the big report so you can give it to your boss to be surfing for a new pair of shoes? And now your report is late and the boss is looking for a new person!
I was a slacker once, now I more interested in getting the job done and done right so I can get on to other things. Playing around at work is fun until you get caught. Or get some one else in trouble, you start looking like the bad guy.
Yes, a work computer should be monitored and you should know this, a useage policy should be in place. And employees should know that they are Responsible for what they do on the companys computer. I expect to be hit hard for saying this but there has been too many things that have happened because of people not thinking before doing.
Companies often talk about how they want their Intranet to
reflect the heartbeat of their organization, but if the Intranets I have seen
in the last few years are any indication, then many of them are dead.
Why is that? I think
the main reason is that any web site is a living document and organizations
often forget about the care and feeding that goes along with that living
document. You have seen this before and
you know the drill. A great big noise is
made about the Intranet for its launch, and then over time it goes quiet. Not much of an investment is made in it
because it is ?DONE?. The people
assigned to update its contents have ?real? jobs that keep them busy, and
Department Execs are busy shepherding their units, concerned about budgets and
priorities, not whether their department?s info is up to date.
Go ahead; take a look at your Intranet or even your
organization?s Internet presence. How
much of that material is material from the launch? How much of it is more than a year old, 3
months old, a month old?
I have always felt that the Intranet needs to have people
dedicated to it full time whose responsibility it is to keep the content fresh
and relevant to the employees. Where
these people come from and where they exist in the organization is entirely
flexible, but they need to exist.
What do you think?
Has your Intranet straight-lined?
If so, what do you think is wrong
and how would you improve it? If not,
tell us how and why you manage to keep yours fresh. Your peers I am sure would be eager to know!
Need a State Statute or Legislation but just don?t know
where to go to get it? Then I have just
the place for you. Just click here for a
page full of hot links to the information you are looking for. State Constitutions, codes and even some
municipal laws and regulations can be found.
And if you are wondering where I found this link ? The Library of
Congress. Check it out here.
by marya123
The current Alaska legislative link is:
http://w3.legis.state.ak.us/home.htm, last update 3/10/2005. Wonder who
keeps track of the Library of Congress links?
by psu-curt
To research Federal laws & Statutes, including those currently under discussion, see: http://thomas.loc.gov/.
Another good resource for information at the Federal level is: http://www.firstgov.gov/
I have recently been involved with a community of users who
experienced a drastic change in one of their applications overnight. Even
though they had been warned of the impending changes, and some of the users
actually had input into the process, the change has been overwhelming to many
of them.
As to be expected, there has been much wailing and gnashing
of teeth and cries for things to go back to the way they were. While some have resigned
themselves to learning the new system (grudgingly), others swear they will never
use it and some have embraced it for all the reasons that initiated the changes
in the first place. So, was this a good roll out, a failed roll out, or
something in between?
Before we answer that question, let's talk about change in
general. Everyone tends to believe that people hate change. And while hate may
be a strong word, people often tend to look upon change with a less than
favorable attitude.
Why is that? There are dozens of reasons, but here are some
of the leading candidates:
Fear of the unknown, loss of control, fear of being made to
look "stupid", loss of knowledge/feeling worthless because what you
knew is no longer relevant, change in your routine, forced learning, bad past
experiences with change, rigid thinking/lack of flexibility.
Given the reasons above, you have to wonder why we attempt
change at all. With all the negativity surrounding change, isn't any major
change destined to fail? The answer to that is not necessarily. The better way to phrase the question is "isn't
any major change subject to failure?" And that answer is a resounding yes!
As IT professionals, we must always be cognizant of the fact
that no matter what you are doing, change is a risk factor that must be
accounted for and managed. Even if the changes are completely and positively
for the better, they will be resisted, often quite vocally. And even the
smallest modification can cause a maelstrom of discontent far exceeding the
magnitude of the change, if it isn't handled right.
So how do we manage this change? To answer this, we must
look back at our reasons why people dislike change. One theme is fear of the
unknown and a loss of knowledge. You combat this with information. Unless you
have a VERY strong reason for surprising people with change (those situations
do exist) you should precede change with lots of information.
Inform those to be affected why changes are being made, what
they are, and how things will work differently. Don't be stingy with your
information either. While there should always be executive summaries available of
what you are planning to communicate, you should be ready with more verbose
explanations of the change. One behavior that people engage in to calm their
fears is to garner as much information as possible about it. Don't let people
starve for this kind of information. The more you can provide, the better the
outcome.
Besides providing information, you need to control your
change schedule. Even people who are more accepting of change often dislike sudden change. If at all possible, make people
aware of the schedule, and make it as gradual as possible. Shock and awe might
work in a military campaign, but it is usually bad for change management.
Include change-affected users as much as possible in the
planning stages. Not all change fits this category, but if you can get active
participation in the development, you will have allies in the audience that can
share their knowledge with their coworkers and thus buffer the response to
change.
Lastly, communicate during the change process. Listen to and
respond to comments, both good and bad. Even if you provided tons of
information prior to the changes, keep information flowing and show that you
are listening--even if it is just to say that you understand their concerns and
you will try to help them through any issues the best way you can.
As a government IT professional, you must be prepared to
deal with an enormous amount of change. From your role as a change agent in the
organization, to the fact that wholesale changes are often thrust upon you due
to politics and differences in administrations, you have to be prepared to
manage change to achieve successful outcomes.
As far as the example given to start this article, the
jury is still out. It sometimes takes a while to judge the results of changes,
but my gut tells me this is going to be one of those in-between roll outs.
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
by dmiller
by leoofmars
I work for a public sanitation agency and we are experiencing some of the symptoms of change resistance mentioned by Ramon, and we're just in the "gather the specifications for the new system" stage. "Loss of Control" and "loss of knowledge" fears have already surfaced. I discussed this with the application development/support team that I lead. I asked them to be tolerant of users who appear to be resistant and understand what may be bothering them. As for me and the team, we like to learn new things...really, we don't care that the 15 years of knowledge we gathered about the old system is out the door. Really.
You might want to check out the blog I'm doing on this process, A New ERP.
As I sit here and write this column, I have been using the
new OpenOffice beta 2.0 (Windows Version) for about a week now. I downloaded
it, ran the install, and began using it immediately. I did not peruse the help
files, check out the read me, or anything of the sort. I just started working. Since
then, I haven't had one difficulty arise that prevented me from composing or
editing a document in OpenOffice Writer or creating a spreadsheet.
I call this success. Not just on the part of OpenOffice.org
but also for the whole concept of the Windows GUI. I am old enough to remember
the splash Apple made with the Mac and all the convincing Microsoft had to do
to make people switch from DOS and our command-line comfort to Windows.
One of the compelling arguments of the day was that because
of the consistency of the Windows GUI interface, particularly in the area of
the menu system, we would become better computer users because we could go from
program to program with familiarity, thus reducing the learning curve.
And you know what? They were right. Fast forward to 2005,
and the majority of our users have been using Windows for at least five years. They
also have been using an office suite for that same amount of time and are
pretty familiar with what a word processor does, and to a lesser degree, a
spreadsheet and a presentation package such as Power Point.
So I am a little alarmed when I see articles or remarks
espousing how costly and difficult it would be to switch to an open source
office suite such as OpenOffice or a commercial package such as StarOffice, or
even Corel Word Perfect Office, or Lotus SmartSuite.
I will be the first to admit that there will be some costs
involved, particularly for the power users who actually use the more detailed
features of Microsoft Office. And there will be some conversion headaches with
some documents for sure, but as far as word processors and spreadsheets go, for
the majority of users, the transition would be far less traumatic than many
make it out to be. Those spouting off about how difficult it will be do not
give the general user base credit for the basic windows skills I mentioned
above.
And if your argument against it is that people would grumble
because you switched out their office suite, just remember that these are the
same folks that grumble over a switch between versions of the same software. So grumbling is a poor
indicator of satisfaction/dissatisfaction.
The reason I mention all this is partly because of the
polarizing comments I have been reading in the trade press over the State of
Massachusetts' decision to switch workers away from Word and Excel (http://news.com.com/2100-1012_3-5845451.html).
If this were biblical times, I believe someone would have stoned CIO Peter
Quinn for his decision. Others, on the other hand, have praised the decision as
if it came down chiseled on a stone tablet.
I personally believe that many of those that have vilified
Mr. Quinn have never tried OpenOffice for fear that they would find that they
can function just fine in its environment.
To those who have never tried OpenOffice, I encourage you to
download it and give it a whirl for a week. I think you will find that as a
package it does some things better than MS Office and some things worse than MS
Office and some things different than MS Office. But as a whole, does a
more-than-adequate job--particularly when you compare the price.
As technology professionals, we are supposed to be able to
weigh the pros and cons of technology, independent of emotion or allegiance to
a particular vendor or manufacturer. Zealotry is not in your job description (https://www.techrepublic.com.com/5100-10878_11-5706440.html).
A decision such as switching office suites can only be made after careful
consideration in your own particular environment and based on fact not on hype
or hysteria.
I am willing to bet that Mr. Quinn's decision to make this
switch was not a knee-jerk reaction and that he spent a considerable amount of
time considering it. It will be interesting to see how it turns out in his
environment. However it does, it will not be an indication that it can or can't
work for you in your own environment. Only that it succeeded or failed in his.
In the meantime, his decision has given some attention to a
product that normally would not cross people's mind during their day to day
activities. This, I applaud him for. We too often create a standard and stick
with it mindlessly from year to year just because it was the right decision at
that time. When was the last time you actually re-evaluated your standards? I
bet that for many, the last time any consideration was made over which office
suite to use was when there was some real competition between the vendors. Since
then, most places have been on auto-pilot, switching versions only when told
to.
OpenOffice has matured considerably since its inception and
now just might be the right time to take a look at the state of things in the
office suite world. You have nothing to lose by trying it and might be
surprised at what you find.
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
While the USPS gets its share of grief from consumers regarding in
person customer service, someone is getting things right in regards to
its web presence. The USPS is the 2005 winner of WebAwards
Best Government Website Annual competition. While the WebAwards
judges specifically singled out the USPS postage rate calculator, the
entire USPS web site is
extremely well done. Attractive, informative, and easy to
navigate with plenty of handy tools, you could do worse than using it
as a model for your own site.
With most states and local governments now 2 months into their new
fiscal years, and the federal fiscal year about to begin, I would like
to know how your IT budget fared this year? Did you get an
increase, decrease or continuation? Did your budget remain
constant but you have a bunch of money set aside for capital
projects? If so, what kind? ERP, infrastructure, security
or maybe something else? You don't have to give your name or even
what organization you are with. Just say local, state, or federal
or non profit and give a sense of size of your organization - small,
medium or big. This is not a scientific query, but just something
to give everyone else reading a sense of how things are with their
government kin. So don't be shy - go ahead and post a comment and
let us know how you are doing.
I just read the following story regarding IT security:
"The weakest security link: Users."
INS
issued the results of a survey that found--you guessed it-end-users,
and "their unwillingness to follow good security practices is the
primary barrier to improving protection against malicious code."
(http://weblog.infoworld.com/techwatch/archives/004141.html)
Clearly this news comes as no surprise to most of
you that are practicing IT professionals. The biggest question
surrounding this issue is not that users are the weakest link, but how
to deal with it. Definitely a tough issue to deal with or we would have
solved it already right?
Like many complex problems, the solution is
multifaceted and includes technological and nontechnological
components. Our first steps in combating user unwillingness to follow
security practices fall in the nontech side and involve
changing/shaping behavior.
I. Rules and Regulations:
In order to move noncompliance from just an organizational social
phenomenon to one of actual consequence, we have to have our security
practices codified in the form of "official policy and
procedure"--preferably in the organizational policies and procedure,
not just departmental rules and regulations.
By doing so, we hopefully are conveying to the
organization that we are serious about security and that violations do
have consequences. However, this is easier said than done. It involves
convincing senior management that information systems security is
important enough to discipline employees over and more importantly,
that the rules are important enough to enforce. It's possible to write
volumes on just this aspect, but let it suffice to say that this step
is not the place to skimp on research and details and the more well
thought out and articulated the policies the better. Also, your
governance body can play a huge role in the formulation of policy.
II. Training: It is not enough to get the rules on paper; they must be articulated in such a fashion as to let employees know why security
practices are important as well as the consequences to both them AND
the organization of not following them. A great place to start is by
catching the employee as they enter the organization. They have yet to
be indoctrinated into bad habits by coworkers and tend to be more open
to organizational messages than they are later on. So have someone from
IT be part of new employee orientation or make sure that whoever is
charged with the orientation can deliver your message in an effective
way.
We can?t forget current employees in our training.
We need to find ways to train existing users on the importance of good
security practices. Whether this is through HR-sponsored internal
training, brown bag lunch and learns, or some other method, the
training needs to be made available frequently and the content kept
fresh.
III. Communication:
This is your propaganda campaign. You are running one aren't you? Just
like in WWII with "Loose Lips, Sink Ships," you need to get the message
out in a variety of ways. Come up with a slogan and plaster it wherever
and whenever you can. Start up messages, e-mails, on the company
intranet, e-mail signature lines, posters, mouse pads, contests, the
limit is your imagination. Keep the messages regarding good security
practices in front of employees as much as possible. It will begin to
sink in and soon peer pressure among employees will aid in policing
your policies.
One idea is to publicize compliance by having a
very visible scorecard on the intranet that shows violations by
department or by showing how many days have passed since a violation in
a particular area ? such as: "HR has been 128 days without a security
violation." Of course this has to be coupled with random audits by
staff who can use minor infractions as learning episodes by issuing
"warnings" and of course, keeping records. This can be done in a way
that you are taken seriously without getting the reputation of the
Gestapo.
IV. Enforcement:
Assuming you have clear rules, regulations and consequences created as
part of step I, you must be proactive and consistent with enforcement.
In many organizations this means having those difficult battles with
other managers that get escalated to senior management because they
(the other manager/s) have a "star" performer who feels they can ignore
rules and regs that inconvenience them. You must be prepared to invest
the time in these seemingly "minor" infractions because of the
precedent they set, and the message they convey. Major violations are
usually a breeze and few managers will protest the enforcement of those
rules and regulations on any employee. For example, it's hard to defend
anyone for viewing porn in the office, and it's usually a one-way
ticket out of the organization.
As mentioned above, there is an ever increasing
array of technology-based tools that aid in enforcing--or better
yet--taking most of the security practices out of the users' hands.
From firewalls, antivirus software, Web filtering and tracking, to
keystroke logging, spam filters, and routing rules, there are seemingly
dozens of new tools being created everyday. I have written about some
of these in previous blogs and articles, and you will find that, in
general, I prefer tools that prevent infractions rather than just
report infractions.
None of the components listed above can work alone
to solve the problem of users who are unwilling to follow security
practices. Together though, they can go a long way in reducing security
vulnerability due to our users.
Keep up with the issues and challenges that
uniquely affect public-sector IT with TechRepublic's free Government IT
newsletter, delivered each Tuesday. Automatically sign up today!
One of the challenges faced by governments is to create web sites that
have the same appeal as the flashy feature rich web sites of commercial
enterprises while at the same time keeping their sites accessible to
the disabled. This is no small task, yet one that must be
undertaken, particulary for those government web sites that are in some
part funded by the federal government.
The Web Accessibility Initiative of the W3C is an excellent place to
start when looking for resources to help make sure your web site/s is
up to snuff regarding accessibility. You can reach their site by
clicking here.
I love it when magazines take best in class solutions and put them
through the wringer, don't you? Infoworld did just that with
Identity Management Solutions and you can find the interesting results
of their showdown right here.
I sat down to begin this blog feeling pretty good about myself. Humph, I thought, I?ll write about podcasting and RSS feeds ? I bet many governments haven?t even thought about utilizing them yet. Then, to test my theory, I surfed on over to www.firstgov.gov and lo and behold, the Federal Government is already doing it! Whoa! Perhaps I underestimated government.
So I started looking for some state and local government sites that might be using them and found none. Please note, my search was not intensive, so there may be some out there, but I hit about ten random sites and came up empty. So perhaps the topic hasn?t caught on at the state and local government level yet.
Just in case you might be scratching your head right now regarding Podcasting and RSS, let me shed some light on these terms for you.
I found the following definition of Podcasting on Wikipedia which gives a pretty good explanation of what it is:
"Podcasting is a method of publishing audio programs via the Internet, allowing users to subscribe to a feed of new files (usually MP3s). It became popular in late 2004, largely due to automatic downloading of audio onto portable players or personal computers.
Podcasting is distinct from other types of online media delivery because of its subscription model, which uses a feed (such as RSS or Atom) to deliver an enclosed file. Podcasting enables independent producers to create self-published, syndicated "radio shows," and gives broadcast radio programs a new distribution method. Listeners may subscribe to feeds using "podcatching" software (a type of aggregator), which periodically checks for and downloads new content automatically.
Most podcatching software enables the user to copy podcasts to portable music players. Any digital audio player or computer with audio-playing software can play podcasts. From the earliest RSS-enclosure tests, feeds have been used to deliver video files as well as audio. By 2005 some aggregators and mobile devices could receive and play video, but the "podcast" name remained most associated with audio."
For RSS, I will again turn to Wikipedia for a clear and concise description:
"RSS is a family of XML file formats for web syndication used by (amongst other things) news websites and weblogs. The abbreviation is used to refer to the following standards:
- Rich Site Summary (RSS 0.91)
- RDF Site Summary (RSS 0.9 and 1.0)
- Really Simple Syndication (RSS 2.0)
The technology behind RSS allows internet users to subscribe to websites that have provided RSS feeds; these are typically sites that change or add content regularly. To use this technology, users are required to download an aggregation service, which presents new articles in a list, giving a line or two of each article and a link to the full article or post. Unlike subscriptions to pulp-based newspapers and magazines, RSS subscriptions are free."
Now that we know what they are, let?s talk about how they can be used and whether it is worthwhile to make the effort. First, podcasting. We can assume that the target audience for podcasting is below 30 correct? Well, maybe not. In fact, while many of the early adopters were indeed quite young, the demographic for portable music players is increasingly getting older. So I think it is safe to say that a growing number of government constituents are using or will be using a device that can listen to a podcast as time passes ? thus making podcasting even more worthwhile than it is today.
Given that you indeed have an audience, what kind of material do you have that can be made available? The answer ? basically anything that you have as recorded audio. This can be meetings, addresses, public service announcements, press releases, instructional audio, the weather, radio programs and more. The more you have available, the richer your service can be.
As for the question already on your lips ? how much is this going to cost me to be able to provide this service? Not that much. Other than coordinating the creation of MP3 files from your audio sources, creating an RSS feed, and the organization of the whole process by your web admin/s, this is something you can take on without great expense.
RSS is basically the process of providing your web content in the form of an XML file format. As noted above, it is best used for portions of your website that have actively changing content. The federal government uses it for transmitting information on recalls and public safety, data and statistics, changes in rules and regulations, press releases, and science and technology to name a few.
I can also imagine the use of RSS to transmit street closures, traffic updates, "Amber alerts" public service announcements, event reminders, findings, legislative changes, proceedings ? the list could go on and on.
As with podcasting, the effort it would take to implement this technology is negligible and easily can fall into the realm of normal web site maintenance and enhancement.
In short, both of these tools provide a way for government agencies of any size to extend their web services to reach an even greater number of constituents for little cost while at the same time doing something that is deemed "cutting edge". By doing so, you increase the ability for government to communicate with its customer and at the same time possibly building a little "credibility" with the younger crowd. Neither is a bad thing.
by mike.reys
The prime minister of Belgium has his own podcast...
by chrisd
No, I missed that site and what a good one it is. Thanks for bringing it to my attention!
Ramon
I work for the State of Oregon and while the group I work for does not
publish any RSS feeds, we have talked about using them with some
internal data. So we are talking about ways we could use it and I
would expect us to provide some rss feeds in the future.
I?m on a bit of a rant today, so forgive me if I come off a bit angry. Everywhere
you turn these days it seems that we are being bombarded with messages
regarding the product or service or process that will take our business
to the next level or into the future.
Forget the next level; I just want people to do their job today! To do what is required. No more, no less. I
am not asking for superhuman feats or for someone to employ space age
technology ? just deliver on whatever product or service you are to
provide me. That?s all.
I?m tired of
having to check, double check and check again because if I don?t follow
up, nothing gets done or it isn?t done correctly. Whether it is in the
drive through and finding out once again that my order is incorrect or
partially missing, or having a government organization lose an
important original document, or finding out four days later that my
computer order made online was lost due to a server crash, it seems
that everywhere I turn no one is capable of performing the basic
service they are there to provide.
In fact,
this malady is getting to be so ubiquitous that any more I am shocked
and awed when people actually do what they are supposed to. What has happened? Why is every transaction with another person for a good or service such a SNAFU?
Perhaps it?s me and my perspective is all wrong. It might be possible that my expectations are too high. Then again, maybe not. My personal theory ? I blame management, or the lack of it for most of these problems.
Whenever I
look at a person or unit or organization that is not performing, I
usually spy management not doing one or more of the following:
Holding people accountable. ? Whose accountable anymore? Missed meetings, deadlines missed, products not delivered, promises not kept. Plenty of blame gets spread around, but so what? No one ever does anything about it. Without accountability, where is the incentive to perform? Insuring that people are doing their jobs is what management is about, yet one of the most avoided tasks of a manager. Why?
Because if people aren?t performing, dealing with them can be an
unpleasant and time consuming task. However not dealing with it and
showing that there are no consequences to poor performance sets a very
bad example that is very contagious. People learn quickly what they can get away with.
Planning. Is it me or are many organizations seemingly flying by the seat of their pants? Often
when I go into meetings I ask questions regarding projects or efforts
such as ?What is the goal or objective of this effort? Who is responsible for the deliverables? When will it be finished and what processes have been put into place to insure it will get done?
I often just get blank stares as a response. Apparently proactive management is alien to many of today?s managers?
Being realistic rather than asking the impossible. In
this day and age of doing more with less there are individuals or units
who simply cannot do anymore than they are doing because there are
limits to how much they can perform. Yet management continues to pile
on without the realization that something has to give ? and that
something is usually quality of product or service.
Being Active Managers. I remember having management defined for me as Planning, Organizing, Commanding, Controlling, and Coordinating. The last time I checked, these were action verbs. Too
many managers these days manage from behind a desk and their only form
of communication is email. And/or they are so wrapped up in meetings
that they have no time or energy for dealing with day to day activities. Management has to make time to be visible and to see what is going on first hand. No one likes to be managed by the ghost that is rarely seen and communicates infrequently. If you want employees to work hard, you need to build a rapport and earn respect. Hard to do when you never enter the trenches yourself.
Remembering that the customer is what it is all about. Well at least that?s what I think it should be. Others might think it is profits or return on investments or such. Apparently I am in the minority on this subject because if I wasn?t I wouldn?t be getting such poor quality service.
Being
that IT is first and foremost a service provider we need to insure that
we are providing the best possible service we can for the level of
technology that we have/can afford. Your IT shop doesn?t have to resemble a space station to provide excellent service. It comes from proper processes and management involvement. While my examples earlier were not IT related it is easy to come up with those as well.
Have
you experienced any projects going nowhere because you are waiting for
a sign off from an authority that never seems to have the time to give
it? How long does it take for a problem to be resolved by your unit once it is discovered? How many reams of paper does it take to fill out a request to fix something that will take under an hour to fix? How
often does nothing get done on an issue because the ONLY person who can
do something about it is sick or on vacation or too busy?
If any of
these sound familiar with your unit, perhaps it might be worth stepping
back and seeing if you are practicing all of the above. If not, it might be worthwhile to think about them. In
the meantime, I?m going to ponder how to fill out a web based help
ticket from a PC without a network connection because no one will
answer the phone at the help desk.
by wayne m.
Hold Management / Company Accountable - Not the People! - I have rarely seen problems that are due to the people doing the work. Often the people at the bottom are the ones doing their very best to get things right, but they have been given an impossible task to complete accurately and reliably. As I read the remainder of the items in this blog, I note they are all management tasks, but the only item that assigns responsibility points the finger at the staff.
If there is no planning, is the person trying to do the work responsible for the poor outcomes? If requests are unrealistic, is the person trying to meet them responsible? If the person directing the work is no where to be seen, is the undirected worker responsible for the results of his ad hoc attempts? Is it the person who is face-to-face with the customer the one who is more concerned about profit or return on investment? In general, it is the staff level are doing there best. In my experience, staff members who are screw ups are far and few between. If the people you are dealing with directly continually fall in this category, then management has sever problems in its hiring policy. If, instead, the people are doing their best and continue to fail, then management has created a situation that breeds unreliability and has failed to take action to correct the issue.
It is easy for a manager to point at someone and say "If only he had done his job better ..." Unless this is an isolated occurrence, the manager would do better to point at himself and ask, "What should I do to ensure that dedicated people can do their jobs better?"
Wayne,
Perhaps I wasn't clear but the whole piece was
about management taking responsibility for these problems. In
fact, I quote from one of the above paragraphs "I blame management, or
the lack of it for most of these problems." Sorry if that didn't
come across to you.
Ramon
If you do a
quick search on IT best practice frameworks, you will find no shortage of
foundations/architectures on which to build your IT organization. COBIT
(Control Objectives for Information and Related Technology), ISO9000 (International
Standards Organization set of quality standards), CMM (The Capability Maturity
Model), and Six Sigma are just a few. Another framework which is gaining
interest in the United States is ITIL.
ITIL
stands for IT Information Library and it is a framework developed in Britain in
the 1980s that addresses service delivery and support of IT services. Widely
accepted internationally, it is just beginning to make significant inroads in
the US. Privately, IBM, EDS, HP, Mead, and GM have adopted the framework. In
the public sector, the states of Virginia and Wisconsin and Oklahoma City,
among others have embraced the framework.
Why ITIL?
So
what makes ITIL so special? Combing the literature, it appears that the
consensus opinion on ITIL is that it is unique because of its strict focus on
service delivery and IT operations as opposed to general techniques involving
quality management or the implementation of standards. To many that have become
involved with ITIL they see it becoming the de facto standard for all IT shops
in the US as it has become so internationally. I have read in one source that
the US and Canadian Governments will soon require IT contractors to use ITIL,
but I have not been able to confirm that through any other sources at this
time.
Specifically what is ITIL
and how do I access the library?
ITIL
as mentioned above is a collection of best practices that has been developed
into a series of 8 books that run about $114 dollars each. They are:
Service Support: Covers the basic processes
involved with support to the enterprise such as Service Desk, Incident
Management, Problem Management, Configuration Management, Change Management and
Release Management.
Service Delivery: This book focuses on the
planning and delivery of services and includes topics such as Capacity
Management, Financial Management for IT Services, Availability Management,
Service Level Management, and IT Service Continuity Management.
Planning to Implement
Service Management: "This book answers the question ?Where do I start with ITIL?'. It
explains the steps necessary to identify how an organization might expect to
benefit from ITIL and how to set about reaping those benefits."
Infrastructure Management: As the title infers, this
book covers everything about managing your telecommunications infrastructure
including Design and Planning, Deployment, Operations, and Technical Support.
Application Management: Covers the management of
applications from inception to retirement and everything in between.
Software Asset Management: Seeks to explain what
software asset management is, why it is important and how to manage them.
Security Management: ?This guide focuses on
the process of implementing security requirements identified in the IT Service
Level Agreement, rather than considering business issues of security policy.?
The Business Perspective: "This book is
concerned with helping business managers to understand IT service provision. Issues
covered include Business Relationship Management, Partnerships and Outsourcing,
and continuous improvement and exploitation of Information, Communication and
Technology (ICT) for business advantage."
You
can obtain these books here: http://www.itil.co.uk/publications.htm
or via www.amazon.com
Do you need another
framework?
I have to be
honest with you, every time I read about another framework my first reaction is
to roll my eyes. I have been around long enough to experience many "better
than sliced bread" phenomenon that--if only implemented--will make my
organization a superstar. And, of course, there are always an army of
consultants to be hired and classes that need to be taken and certifications to
achieve in order to "realize the potential" of the framework.
And
in that sense ITIL is no different. You can invest the time and resources in
understanding the framework to build up expertise in order to implement it
(which several organizations have) or you can hire someone to help you along.
Additionally,
like many of the frameworks that have come into vogue before it, integrating
the processes involved with ITIL takes time--usually measured in years.
However,
with all that said, frameworks can prove beneficial. I think there are very few
if any IT organizations in existence that can claim to be perfect and have no
need for improvement. Most can stand some enhancements to their operations. The
tough questions are: where can we improve and how do we go about doing it?
That's where frameworks are beneficial.
Personally,
this framework intrigues me--partly, I guess, because it was originally written
by government workers, and I intend to research it further. If you are
similarly intrigued, here are some places, besides the books, that you can get
information to see if ITIL is right for you and your organization:
ITLPEOPLE.com
www.itilpeople.com
The
ITL Community Forum http://www.itilcommunity.com/index.php
The
IT Service Management Forum http://www.itsmf.com/index.asp
Hi Ram?n,
I find the article very intersting. I would like to comment on this:
You can invest the time and resources in
understanding the framework to build up expertise in order to implement it
(which several organizations have) or you can hire someone to help you along.
I believe ITIL can be implemented by a company on
its own successfully at a reasonable effort. They must have a realistic
scope and implement it incrementally. A valuable resource for companies
embracing this approach is the FITS (Framework for ICT Technical Support), an ITSM methodology based on ITIL developed by the BECTA.
Lucas Rodriguez Cervera
Nevant
by teldata
First of all, remark that ITIL stands for IT Infrastructure Library (otherwise we would have the word Information twice), but that's a little detail (although with 16 years of experience one should know better).
I want to notify that the way you describe it, it souds as a method for large companies only. But because it's a set of best practices every company, large or small can benefit from using parts of the ITIL framework.
DOH! Good catch. <sigh> Unfortunately all the amount of experience doesn't always catch typos :-(
Ramon
If you happen to overhear conversations regarding the need to develop
applications that are network efficient and offer a zero footprint
deployment in conjunction with the phrase AJAX, don't look too
perplexed. Asynchronous JavaScript and XML, or Ajax, is a web development architecture using:"
- HTML (or XHTML) and CSS for presenting information
- The Document Object Model manipulated through JavaScript to dynamically display and interact with the information presented
- The XMLHttpRequest object to exchange data asynchronously with the web server. (XML is commonly used, although any format will work, including preformatted HTML, plain text, JSON and even EBML)
Like DHTML, LAMP, or SPA,
Ajax is not a technology in itself, but a term that refers to the use
of a group of technologies together. In fact, derivative/composite
technologies based substantially upon Ajax, such as AFLAX, are already appearing."
While somewhat complicated, AJAX is being used more and more by
organizations to create web applications that operate and feel like fat
client apps.
If this intrigues you and you want to learn more about AJAX, here are some resources to get started:
Here is another link to an AJAX-related resource:
SWF (Simple Web Framework) https://swf.dev.java.net/
has just been released in its initial version. From their press
release, "The Simple Web Framework (SWF) is an event based framework
... The SWF event model supports XmlHttpRequest (as well as
form/submit) based event posting, similar to VB.NET or JSF, with In
place Page Updating (IPU) rather than page reloading." See the
overview here.
This week's hot site ranks intermediate in the geek factor. If
you consider yourself a budding web programmer than you should take a
gander at this site. Besides being well written, the article includes source code as well. What are you waiting for!
I took a trip this weekend which involved air travel. As I stood in line to wait my turn at the "mandatory" self service kiosk to check in, I observed an elderly couple struggling with the process. I say "mandatory" because the two employees behind the kiosks (who were not employees of the airline we were trying to check in to) offered no other help to anyone other than suggesting what they might be doing wrong regarding the self service terminal.
Meanwhile, the elderly couple worked unsuccessfully at trying to check in. Before I had a chance to do so, another passenger stepped forward and worked the display terminal for them so that they could finally get checked in. The couple was clearly distraught at the whole process and was grateful for having had a person finally help them out of their torture of dealing with this particular technology.
As I stood there, I wondered if the airline really intended (or cared) for the process to work the way it does. Do they really intend for the process to be as difficult as it is for the elderly, or sight-impaired, or reading-challenged? I am sure that the self-service kiosks were meant to reduce personnel needed at the ticket counter, therefore saving the airline money, but I hope they had better intentions for the usability of the technology.
This got me to thinking about technology in government use and how we need to ensure that the solutions we put into place are not exclusionary to a portion of our customer base.
Some would say that the increased use of technology for self-service types of transactions is exclusionary by nature. I disagree. I believe it is how the technology is employed that determines its inclusiveness/exclusiveness. Let?s take Web-based services for example. For every function that we can offer as self-service via the Web, we will have two groups of people ? those that will make use of the opportunity for self service and those who can't or won't. Unlike the airlines, who see the incorporation of self-service technology as a way to reduce personnel costs, government should first see that the time gains for personnel is a way to provide better/more personal service to those who do not take advantage of the technology. In this light, the use of technology for self-service is a win-win for both sets of consumers.
While it is important for all businesses and industry to think about their customer when employing technology to service them, it is crucial for government to do so. This consideration should be integral to every decision that is made where there is a possibility of customer interaction. Consider the decision to "only support IE version 6 or higher" for your Web site. I know more than one organization that has made this its policy regarding Web content. While a seemingly innocent business decision at first blush, this is a prime example of employing an exclusionary technology. Don?t think this is a big deal? Ask FEMA what they think!
According to the Washington Watch section in the October 15th, 2005 CIO magazine, FEMA had adopted this policy in regards to the ability to complete/access digital forms for applying for assistance if you were a victim of hurricane Katrina. Because its phone lines were swamped, it was extremely difficult to access FEMA with anything other than a computer. However, much to their dismay, Mac and Linux users found themselves unable to complete the forms online. While this may be a small percentage of computer users, the point is that by choosing the exclusionary technology not only did FEMA frustrate some of its customers during a time of crisis, but it gave itself a public black eye at a time when it could least afford it.
The same precautions apply regarding our own agencies' Web sites and their accessibility to the disabled. While we want our Web sites to have the same flashiness and sex appeal as commercial Web sites, we do need to keep in mind that we should (or in some cases must) be accessible to the disabled. This can be an extreme challenge at times and should always be a point in any Web design specification. The decisions involving accessibility can be numerous and can involve creating alternate content or deciding not to use particular Web technologies. Although I have mentioned it before, a good starting place for Web site accessibility decisions is the Web Accessibility Initiative of the W3C whose Web site you can reach at http://www.w3.org/WAI/Resources.
In summary, while it is important for government to employ technology to make interaction with it faster and easier, every technology introduction must take into consideration those who are unwilling or unable to take advantage of it. For those customers, alternate equitable means need to be part of the plan in order to accommodate their needs.
Keep up with the issues and challenges that uniquely affect public-sector IT with TechRepublic's free Government IT newsletter, delivered each Tuesday. Automatically sign up today!
by j alley
It is all about the business case
While I couldn't agree more with Ramon's position that we need to remember who we serve, this is a complex issue and there are a couple of other considerations.
First, adding a web channel for service rarely means that we can remove the existing channels. While it can reduce the effort to support traditional channels, by adding a web channel we almost always increase cost. Attempting to generate a payback on a web-based initiative is difficult and in many cases should not be part of the business case. The argument for web channels is to provide enhanced access to service.
Second, if there are savings by adding a web channel, it is important to consider where those savings should be applied. They could be applied to reduce taxes, to improve this service, or even to add new services. Again, this is a decision that is made through the business case for any initiative.
I have a friend who is dealing with an issue that I had to deal with a
few years back. Seems that a salesperson has convinced influental
members of a legislative body that their organization is backwards
because they are not using VOIP instead of paying the local telephone
company for dial tone. So a "study" is being commissioned to
investigate why the organization is so backwards.
I feel for my
friend because it was not long ago that I faced the same issue.
It's not that we have anything against VOIP, it's that the majority of
buildings that house/d our organizations are OLD - as in
historic. And while they have so much of the old quad wiring in
them that you can put a standard telephone in almost every square inch,
there is not enough CAT 5 or 6 wire to accomodate the needed PC
connections.
Needless to say, wiring the old buildings isn't cheap
but no one ever wants to pony up the dollars for infrastructure.
So countless hours will be spent and meetings will be held to once
again prove that just because a fortune 500 company can put technology
to use, it is not always economical to do so in a government
environment.
by lesko
you can always look at wireless voice ... there are some cool products
out there some of which can work with both 802.11 and CDMA or GSM all
in one device.
I have been researching enterprise portals this week and came across
the following web site that contains some useful information when
considering portal technology. While many of the articles are
authored by portal vendors, there are some gold nuggets to be found. Check it out here:
by welshbilly
This is a really good web site. We are currently looking into portals and this gives alot of help in what to consider.
Thank you
I just read an article reporting that the GAO finds that the
responsibilities of government CIOs largely resemble those of their non
government counterparts. (http://www.eweek.com/article2/0,1895,1869922,00.asp)
The article says that the major difference between the two is in the challenges
that they face: private sector CIOs struggle to align themselves with business
goals, while public sector CIOs must overcome organizational obstacles and find
enough money to keep the lights on.
We needed a GAO study to tell us this? It is no great secret
that government faces the same IT hurdles as the private sector, plus the
additional challenges of: more regulation, fewer funds, constantly changing
executive leadership, frequent changes in mission and priorities, conflicting
missions and priorities due to having to be responsible to multiple masters
(administrations, legislatures, and the public), less flexibility, and greater
exposure/public oversight.
Given all that, you have to wonder sometimes how IT in
government functions at all? But despite these hardships/obstacles, government
IT shops perform -- and some of them quite
well. To all of you working in the government IT realm, my hat is off to you.
However, even those that feel they are performing well know
deep down that they are lacking substantially in some areas and are doing the
best they can. Why? Generally, because of a lack of resources. And why the lack
of resources? Three main reasons: (a) a limited pool of funds, (b) competition
for those funds, (c) the reactionary nature of government.
The limited pool of funds refers to the fact that government's
primary source of income are taxes. Besides the fact that no one likes to pay
large amounts of taxes and thus the flow of incoming funds is regulated by how
little one can tax and still provide all the necessary services, the pool is
also regulated by how well the economy is doing. Economy is depressed = tax
revenues depressed = fewer funds to cover all the services the public expects
to receive.
The competition for funds refers to the intense battle over that limited pool of funds by all the
departments/agencies that provide services ? either to the public or to keep
government running. It is in this area that IT tends to get short shrift as
they do not provide direct services to the public. It is those public-facing
units that tend to get the lions' share of funding. While IT in budget hearings
can generally talk about how decreases in funding will affect performance of
systems, etc., it usually isn't as jaw dropping as a Police Chief claiming that
without proper funding the streets will be rife with criminals. In fact, I once
knew a Chief of EMS who would answer requests for budget decreases with the
statement, "No problem commissioner, which district should I let people
start to die in?" That was usually pretty effective in stopping that line
of conversation.
The reactionary nature of government refers to the fact that
government -- as reflected by elected officials -- tends to mirror what is hot at
the moment with the public. This being the case, government tends to be
reactive rather than proactive.
All of the above combine to create a situation in which it
is almost impossible for IT to get the necessary funding to excel in all areas,
or in some cases -- operate adequately.
Two of the major areas where government IT shops are often severely
lacking because of the above are security and disaster prevention/recovery.
Why? Because they are expensive, they are insurance, and they are behind the
scenes. Face it, systems will run
without proper security, backup, and recovery capabilities. And for some of
those that provide IT funding, that is enough. We all know it is not wise to
operate that way, but for many it is a calculated gamble: Will it blow up on my
watch? And even if it does, the funders are never usually the scapegoat.
Thus, it is up to government IT shops to do the best that
they can with the limited funds provided. It's a pity the GAO didn't provide
any answers on how to solve this dilemma -- because their survey only proved
what we knew all along.
However, the GAO did point something out that we should take
note of. Public sector CIO's generally are charged with more operational
responsibility than private sector CIOs, such as architecture and strategic
planning. Thus, they (public sector CIOs) tend to spend more time tending to
the machinery rather than greasing the wheels. Find a way to reverse that
balance. Greasing the wheels will get you more in the long run.
Keep up with the issues and challenges that
uniquely affect public-sector IT with TechRepublic's free Government IT
newsletter, delivered each Tuesday. Automatically sign up today!
by nostaff
So true, but Public Sector CIOs are also far more likely to have to deal with taking on the responsibilities of other Departments. Haven't you all had to deal with the computerization of a function and then the expectation that IT is responsible for monitor effective use of resources! After all, the staff are not all computer gurus!
Battling this from happening is then viewed as IT being obstructionist or not customer service oriented.
I do believe that Goverment CIOs/Execs need to foster regional/collaborative services, perhaps hosted service from another government entity. That's a long shot though.
by pmoleski
I work as a CIO in the public sector. In general I agree with your comment about greasing the wheels but will make the observation that it has to be backed up by process to generate the required budgets. To overcome the budget issues talked about we have gone through two iterations of planning for IT since I have been in my current position.
In the first iteration we became visible (greasing the wheels) and developed an IT plan based on input gained from conversations between the CIO and the leaders of the business areas. This successfully identified what needed to be done. It was not successful in addressing the budget issue as IT still requested a block of money each year and projects had to be done within that.
In the second iteration, which we are using now and works quite successfully to address both content and budget, we did things a bit differently.
We separated the base budget, which includes the money to keep the lights on and enough to maintain (with small enhancements) the current applications, from the large IT projects. The large IT projects are brought forward by the business areas they will support, as business cases, when the yearly budget is first proposed. The business cases include the dollars that will be needed in both the business area and the IT area budgets. If the business case survives the budget process then the initiative proceeds. If it does not then the unit can try again the next year. As for infrastructure issues they are self funding. The cost of infrastructure seems to be going down as quickly as demands for infrastructure go up so a flat budget base is meeting our year to year needs. If a large one time project was needed for infrastructure beyond the base I would have to bring it forward in the budget process, representing my own branch.
The key thing we have done is integrated the IT budget planning into the overall budget planning for the organization. It all starts with the key relationships and conversations with the branches in the organization buts ends with a single business/budget planning exercise for the organization into which IT is fully integrated.
The above produces a yearly base and project budget that is automatically aligned with the key initiatives of the business and funded with the same priority as the key initiatives as it is integrated into the rest of the planning and budgeting.
At this point I am repeating, but the key is there is not a separate process for IT. It is fully integrated into the rest of the business planning and budgeting process.
It is working very well since we made the switch. The fact I can make this claim when I work for the Health Department in a province in Canada where health is publicly funded and I complete against nurses and doctors salaries for priority speaks to the robustness of the approach.
Phil
I just wanted to let everyone know that while I may not be able to
respond to every comment that is made regarding a blog posting, I read
every single one of them. Not only do I enjoy your feedback but
it allows me to be in better touch with what is important to you.
So please, don't be shy. Let me know what's on your mind, what
you want to hear about, and whether or not you agree or disagree.
Thanks again for reading, especially those that take time out to comment!
Ramon
The FCC has stirred up a hornet's nest with its latest decision
to decree that any VOIP provider must insure that their network is
wiretap ready. Besides the obvious providers, they are
insinuating that colleges and universities must do the same. Talk
about an unfunded mandate! There are tons of details to this and
certainly more reserach to be done on my part before I write at length
about it. In the mean time, check out CNETs coverage here.
Let's say, for the sake of discussion, that I know of two fictional
IT project managers. Both have many years of experience. The first is a certified
Project Manager (PM) who is absolutely dynamite when it comes to PMBOK
knowledge. He knows project management processes and procedures up, down, left,
right, and backwards.
On top of that, he is brilliant with Microsoft Project. He
keeps up with the trade, stays on top of his game and on paper looks to be the
ultimate PM. You know what's coming next right? I wouldn't choose him to manage
his way out of a paper bag.
How can someone so knowledgeable--and certified to boot--be
so bad at actually taking a project to completion? The answer is: attitude and
people skills. This person unfortunately does not exude confidence to anyone he
comes into contact with. His personality is as dry as the Sahara and his ability
to get people to follow him is virtually non-existent.
Worse, he believes that he doesn't need to understand the
client's business nor the particular subject matter of the project other than
at a cursory level. To him, project management is the act of strictly following
a defined methodology and making sure that all Ts are crossed and i's are
dotted. If that is done, then the project should succeed.
If the project doesn't
succeed, he believes that he has been successful for not allowing the client to
waste any more resources on an effort that never had a chance in the first
place. Needless to say, he doesn't have a long list of projects completed on
time, within budget, and with a happy customer.
Conversely, I know of an individual PM that is not
certified, uses PMBOK and other methodologies loosely, is logical, quick on the
uptake, and has a laser-like ability to get to the root cause of an issue and
then determine how to fix it.
More importantly, she is an active listener, a participatory
manager, and always takes the time to understand the client's business ? even
if this means adding time up front on a project in order to do so. Ultimately
because of her style, the client comes to know and trust this PM. This trust
allows the client and the PM to travel the project road together and encounter
whatever slips and slides await them. But if they do encounter the inevitable
problem, there is no finger pointing or wringing of hands, just a quick
reaction on how the "team" (client and PM) can deal with the issue.
This trust also allows the PM greater flexibility in her
project management because the client trusts that the PM is working in their
best interest. This PM truly becomes a leader in the project, rather than a
dictator of processes and procedures.
Needless to say, this PM has a very good record of
delivering projects and satisfying the customer.
Now some will say that both PMs are very good and that the
first PM just happened to end up in the wrong environment. The environment he
is best suited for is one where clients are exceptionally skilled at what they
do; they just need some organization wrapped around their work.
Conversely, one could argue that the second PM just happened
to end up in environments where the clients know they want something done, may
even know what the solution to their ailments are, but they just don't know how
to get there. In this environment, the second PM really shines.
I happen to think there is something to be said for both the
above arguments, and there really is a best match of client to PM. However,
when hiring a PM based on a resume and an interview and a few references, it is
still hard to determine which one you are going to get, PM #1 or PM #2 or maybe
a mix of both.
Personally, I always hope for #2. I think their style
is more adaptable to either environment and they can adjust to whatever
methodologies are required and the degree of rigorousness that must be
followed. What do you think?
by lfhowell1
Schizophrenia of Organizations Today: To PMP or Not
This is a terrific discussion and timely. It underscores an
important and growing
dilemma about what a client (for consultants) or enterprise (for
internals) really want versus what they need regarding the successful
execution of a project. As many of the readers know, there is a
growing debate for PMP certification in job requirements or the
infamous "preferred" catch-phrase that follows this expectation.
A nice analysis of this is at the link:
https://www.gantthead.com/article.cfm?ID=226852
Unfortunately, however, the #2 person described in your post exposes
the weakness of the hiring and interview process for many client
organizations. Behavioral interviewing techniques and situational
discussions can uncover the tendencies to ascertain the traits an
organization desires that would identify person #2. The challenge:
who has time for this? The irony, however, is that hiring right
the first time, creates tremendous value for the enterprise--at least
that is what common sense tells us. Sadly, many organizations
believe that the PMP certification requirements will help in the
decision-making process to validate the "final call." To be sure,
I am a fan of PMBOK--know it well, and apply some of it and
begrudingly on the road to certification. But, "right-brain"
skills and competencies--those creative tendencies, the ability to
think and collaborative when unusual circumstances occur or the
political heat is turned up a notch, often begs for non-PMP skills and traits.
The schizophrenia of enterprises today highlights the dichotomy between
person #1 and person #2; a company or government agency would love to
hire person #2, but feel it is "safer" to hire person #1--depending on
the culture or the project and sponsorship. From participating on
both ends of hiring and delivering PM services, the back and forth that
takes place during the hiring process usually protracts making a
decision. What's more, it makes you wonder if the project is
really that important to begin or how does an organization truly define
success? Is it the process or the outcome?
Excellent comment, Could not have said it better myself.
Ramon
by catfish182
Network admins, perhaps you may not know thine enemies, but you should
be aware of some of their tools. Check out
http://www.insecure.org/ to get the scoop on some of their tools and the thoughts from a self professed "good guy" hacker.
Trending After Hours posts
Sort by Trending