Government Technology
This is page 3 of the discussion. Read the opening post
After Hours
This is page 3 of the discussion. Read the opening post
Good programmers hate to reinvent the wheel every time they
are working on a project, therefore wouldn't a search engine designed specifically
for programmers to find code be a neat idea?
If your answer to this question is yes, you have a treat coming soon:
KRUGLE. Go join the beta now or wait for it to go live in March!
Yes. I need to repost about this, and add prominent link to it on my blogs sidebar, up high, near my intro text.
It also is supposed to be answers, definitions, syntax, etc., not just code.
this is a revolutionary new tool for developers, bloggers, webmasters, content managers, IT departments, and others who need code, definitions, templates, and other building blocks of web objects. it is important to know that it is not a simple code generator, but an actual full-blown programmer's search engine that strives to be so astonishingly relevant in search results, the web dev community will wonder how they clunked and chunked along without it.
DISCLAIMER: I am a friend and colleague of RB who is doing something clever I'm sure with Krugle marketing storms.
by btljooz
Drivers Licenses already have magnetic strips on them. Remember back in the 80s when it was the LAW you HAD to have your SS# on your DL especially if it was a CDL (Commercial Driver's License)???? THAT is when the National Database was formed. All this hoopla about Driver's Licenses is only to divert attention away from the REAL threat: IMPLANTED RFID chips into humans. They've already been doing this to pets for over 15 years. Now it's been done to the dead of Katrina. Inmates are next...THEN guess who??? ;)
The whole story surrounding Massachusetts former CIO Peter Quinn and
his decision to step down as CIO after his controversial decision to
adopt the Open Document Standard (ODF) for the state government really
bothers me. Not because I am surprised by the outcome, but because of
the precedent it sets and the chilling effect it will probably have on
decision-makers who might think about an alternative to Microsoft.
While I will freely admit I do not know all the grisly details involved
in the decision regarding the choice of ODF for the state, my research
tells me that some people felt the decision was made without enough
input from others, which resulted in a lack of buy-in among the
relevant parties.
Whether this is true or not, it will be hard to ever know the complete
truth. Personally, I'm not sure you can get 100-percent buy-in on
anything, particularly in an organization as complicated as state
government. And I'm not sure that 100-percent buy-in would have solved
Quinn's problems, because the decision he made was going to cost a
certain company a lot of money or was going have to change its software
to support a standard it didn't create or want to support.
Anytime you make public decisions that are not only costly for a major
statewide vendor, but also can be viewed as an act of defiance, you are
looking for trouble. No company, (monopoly or not) is going to take
that one sitting down, and they are going to go down fighting or take
you down first.
While I thought that Mr. Quinn's decision was bold and inspiring to
many open source proponents, it was in fact a declaration of war. Quinn
is a casualty of that war and it's quite possible that Massachusetts'
ODF standard will become another casualty, even though the state says
it will implement it as planned.
So what is the lesson from this saga? That any attempt to implement
open standards in government is political suicide? The answer is maybe;
but it depends on how you go about it.
My personal philosophy on this one is that if you are going to go up
against such a powerful force, you either need bring an equally
powerful force with you, or you prepare to fight a guerrilla war.
For instance, had Mr. Quinn said that the state is going to become an
all-Oracle state, from backend to desktop; the tale might have ended
differently because you would have money fighting money.
On the other hand, if you aren't about to swap out one huge major
software vendor for another, then in my opinion, you need to take a far
subtler approach. The first thing you do not do is blow your own horn
with a huge announcement. You need to keep quiet about it, and win the
hearts and minds of the populace without them even realizing you have
done it. The way to do it is not from the desktop, but from the back
office. Start with things the end user doesn't see or care about: DNS
servers, Web servers, and the e-mail servers. They (the end users)
continue to use the same front ends--desktop and e-mail clients that
they are used to--while you start to exchange the plumbing out from
under them. Done correctly, this can happen without anyone noticing.
And if you do it during a period in which you have paid for a volume
license of the back end stuff, no one is the wiser (particularly the
software vendor whose tools you are replacing); you will reap your
savings later when you choose not to renew.
Later, you can turn your attention to replacing the file systems and
the database servers (if you choose to go whole hog). This is a bit
trickier because applications can depend on them, but it can be done.
Mind you, this process doesn't happen overnight, but takes time and
careful planning.
Once you have liberated the back office, then the desktop is ripe for
the taking. By then you can document successful implementation and
usage over a period of time and also show the cost savings. Now, you
have ammunition and probably some fellow believers because you have
been working the steering committee all along--haven't you?
As open source continues to make headway and increase awareness through
its adoption in private sector companies, it will become easier to
stick one's neck out and make those far-reaching decisions. In the
meantime, it will take death by a thousand cuts rather than a frontal
assault should you wish to avoid political suicide and actually stick
around to see your plans come to fruition.
by bishaw
Your process is sound up to a point. Training for the staff from the IT Support to the end users is not covered which could make or break the deal too. If the products are easy to use then the transition can run smooth but if the products are difficult to do the same functions that staff use on a constant bases then it is an up hill battle. Also on the desktop end, can the new software support archived documents saved in prior versions of MS since that is what they used in the past? I work for a state agency and the agency I came from loves to challenge vendors to try to open existing documents created by MS products. So far, all challengers have failed but they would like to find one that can provide the same functions that they are use to using with MS. I tried some evaluations from a number of vendors for desktop software and none could compare to what we used with MS. In addition, people forget what happen in Huston, Texas
when they tried going down this road and Microsoft did an audit for licensing violations or stay with their products.by apotheon
1. The Consipracy. It looks like the "conspiracy theory" was true: the "conspiracy" actually existed. The state just lucked out in that Quinn was savvy enough to outmaneuver it, in part by being essentially forced to step down to remove himself as an easy target for Microsoft FUD and mudslinging.
2. Guerilla Migration. There's a relatively easy way to greatly reduce the bogieman of "training costs" and avoid angering the 900 pound gorilla when switching out desktop software: start out by making it voluntary. Once you've swapped out the back-end software (like trading in MS Exchange Server for Open-Xchange Server), you are now no longer dependent on the Microsoft applications that require that back-end functionality (like Outlook). Rather than making a company-wide migration mandate from Outlook (for instance) to something else, though, you can now just say that everyone in the company is free to use one of a set of other alternatives as well. Microsoft will find it difficult to target you for saying "I don't care whether you use a free alternative to a Microsoft appliction," even though it would be easy for Microsoft to target you for mandating a migration to non-Microsoft applications. As time goes on, you can encourage alternatives more and more, until finally you get to a thorough enough saturation by alternative applications that you can just fail to renew licenses for MS products. What'll they do then, attack you for ceasing to be a customer? Another approach is to mandate the use of alternative technologies alongside the Microsoft technologies, rather than as a replacement to the Microsoft applications. This option is a bit more difficult to employ universally, though it might be useful in a couple of individual cases of specific applications.
by juleslt
It depends if your aim is 'open source' or 'open standards'.
I don't think the aim here was an end game of 'Linux on the desktop'. After
all, you could switch to Open Source and keep using Word document format.
However, while companies are free to support what they like,
I can wholly understand the argument that governments should NOT lend support
to a particular vendor?s format (particularly where that format is closed). It?s
a completely different issue from using a particular vendor?s software, which
is acceptable. Unfortunately, the dominance of the MS ecosystem means that many
people can?t even see the difference between software and data format.
European countries have slowly got more hardline on this
(after all, they have more to gain by hurting a US business), passing laws on
accessibility standards that mandate data to be available in open standard
formats - W3C compliant HTML and plain
text primarily, although PDF is also widely acceptable due to the fact that it
is a documented standard that can be freely implemented (i.e. you can easily
write a PDF Braille reader).
It?s acceptable for a company to decide to make it?s website
IE only because it doesn?t want to cater to the tiny percentage of Firefox, Mac
and Linux users, because that?s a commercial decision. It?s not acceptable for government
to do the same. You might say ?come on, it?s a waste of tax dollars spending
money making cross-platform sites for losers than get what they deserve for
buying a minority machine? but you?re still missing the point. The question is
whether governments should be supporting commercially determined ?standards?
aka winners, or properly defined standards (in the sense of ISO, ECMA, etc).
I think the issue, perhaps, WAS in promoting a standard that
is equally associated with a product (OpenOffice). Maybe a better strategy
would have been in promoting that State documents should be saved in ?The
simplest possible format?. I can never understand why people send plain
unformatted text in Word files. RTF would also suffice in 80% of cases. For
Read-Only documents, PDF is almost certainly a better choice. Word is only
really useful if you want to send a document for someone else to modify and
return.
If you really HAD to pick a single format, I?d go for
PDF as it allows maximum choice of tools to produce documents (even including
MS tools that don?t write out in Word format like Publisher). I can?t think of
many situations where agencies want to send editable documents. (Of course that still leaves the issue of what format your INTERNAL documents are kept in).
by apotheon
The Open Document Standard isn't an Open Office format. It's a document format that was developed separately and has been implemented by a number of word processor developers. The problem Microsoft has with it being adopted as a state governmental standard isn't that OpenOffice.org implements it (nor that any other particular word processor implements it), but that it's something Microsoft doesn't control and for which MS Word doesn't have any support (due to Microsoft decision-makers making a conscious choice to ignore open standards in favor of its own closed formats).
In other words, it's not that the Open Document Standard is associated with any particular product (it's not, except in the minds of some underinformed people who don't know better) — it's that it is not associated with a particular product, namely Microsoft Word.
I just finished sitting in on a conference call of a board meeting of
about 25 members where the main topic was regarding a politically
contentious document and how the members were going to form a strategy
to deal with the document. While the discussion proved interesting,
what was most fascinating to me was the style in which the chairperson
(who called the meeting) managed the process. Smooth, articulate and
consensus building, the chair had the meeting wrapped up in 30 minutes
with a general agreement from the group to act as one as the process
was worked out and assignments were made--pretty slick in a politically
charged environment.
This got me to thinking, where do most managers get taught this stuff?
And the answer for most is nowhere. For the most part, most of us have
had to pick it up on the fly, by observing others and by being thrust
into a position to run a meeting. As I am sure you will agree, based on
some of the awful meetings I have attended (hopefully not the ones I
ran!) some people learn the art better than others.
I say art as opposed to science because, although there is a method
involved, you can follow all the rules and still run a lousy meeting.
Running successful meetings comes from feeling comfortable with public
speaking and being able to think on your feet. These are skills that
many IT people struggle with.
Another part of the art is being politically savvy. You must understand
the power equations--who has it, who doesn?t, how to wield it, and how
to be sensitive to it. This is another one of those things that isn't
taught in school.
So if our process of learning how to run meetings is by observation or
being thrown in the deep end and asked to swim, is it any wonder that
so many do it so poorly?
Interestingly enough, while the art of running a good meeting is a
difficult skill to acquire, it is more easily acquired if you know the
science behind meetings. By this I mean that if you are less worried
about knowing the "mechanics" of how to run a meeting, you can
concentrate on developing more of the "art."
Fortunately, there are plenty of guides on how to run a meeting, both
public and private, formal and informal. Here are just a few:
There are dozens if not hundreds more from where these came from, and
they all say pretty much the same thing. I recommend reading a few to
make sure you understand the ground rules.
The next step is to put them into practice. Practice does indeed help
you get to the next level. The more you lead or participate (not sleep
through) meetings, the more comfortable you get with the procedure. Be
critical of meetings (in your mind) and evaluate those you attend,
based on what you know (in regards to process), and also the style in
which they are run. You shouldn?t have too much trouble identifying
good meetings from bad ? it's usually pretty self evident.
Now for the "art" part: Some people are naturally better communicators
than others. For reasons too many to enumerate, some people have a
built-in command of language, are sharp observers of their environment,
and are attuned to the feelings and emotions of their listeners.
However, even if you are not a natural communicator, there are
resources to help you hone your talents just a Google search away or in
the self-help section of your local book store. My suggestion, besides
reading, is to get a mentor to gently critique you. It?s easy to be too
hard on yourself, but videotaping can be extremely helpful, along with
coaching from a pro.
As for power and politics, here are a couple of good reads:
Managing with Power:
While reading on the subject is good, I certainly recommend paying
attention to the power and politics in your own organization. Ask
questions and learn more about who wields power, how they do it, and
why.
Finally, "style" is hard to quantify or learn from a book. My
suggestion is to find someone that you admire and try to incorporate
some of the things that they do best into your own style.
With the right attitude, you can improve your ability to manage a
meeting. This is hugely important, since your effectiveness in meetings
determines a great deal of things in the workplace ? from funding to
project management success. So for those of you who are "old" pros at
managing meetings, you might want to take a step back and make sure you
are as good as you think ? there is always room for improvement. And
for those who haven?t had much experience yet, I hope I have provided
something for you to work with. Call it a life preserver ? its probably
more than most of us got to start with ;-)
by raelayne
I'm busy. So busy I can barely see straight. Busy enough to
appreciate -- more than I can express -- a well-run meeting. I
think most people feel the same way, because we are all busy.
Here are a few things I appreciate:
1. An objective -- terse, specific, and important. An agenda is optional, but an objective is essential.
2. The right people - the subject matter experts and the decision makers, and no one else
3. A structured statement of the issues and elicitation of points of view
4. Terse summary by the leader of what he has heard (assumes he's listening, not just talking) - all points of view
5. Preparation (stop and re-schedule the meeting if critical participants aren't ready)
6. On-time start and finish
7. Determination to stick dispassionately to the issues or questions at hand
8. Follow-up: skip the minutes; what you've done is make
decisions, identify action items (with responsibility and timeframe),
and new issues. Make sure they're all recorded wherever you
record such things and that those action items really are completed.
Recently, I attended the kick-off
meeting of a local interest group (LIG) of the ITSMFUSA. The acronym
stands for IT Service Management Forum USA and it is a group
dedicated to fostering the delivery of IT services via ITIL. ITIL,
which I covered in an earlier post, stands for IT Information
Library, and it is a methodology developed by the British Government
for best practices in the delivery of IT services. It is popular
internationally and is just catching on in the USA. It is another
management methodology such as CobiT, ISO, Six Sigma, etc., except it
tells you what to do in the ways of best practices, not how to do
them.
In any case, I was talking to a
colleague of mine before the meeting about why companies need (and
will pay for) what are essentially common-sense guidelines for
managing. We were discussing this as I was flipping through a book on
IT alignment with business strategy when I came across a paragraph
(and I wish I could remember it to quote it) but it read something
like: Regarding database backups, they should occur on a regularly
recurring schedule, which is made known to the customer and any
deviation from said schedule should be made known right away.
No kidding! What a brilliant bit of
insight! Another concept in the same vein (but not part of ITIL) is
Root Cause Analysis. Root Cause Analysis refers to finding the
real cause of the problem and dealing with it rather than simply
continuing to deal with the symptoms. Okay, when was the last
time you set out to just remedy the symptoms of your problems?
See my point? Most of this stuff,
especially to those who have been in the field for a long time, is
pure common sense. Yet, I am going to argue that, in fact, these
methodologies are very important.
I concluded that the reason we pay for
common sense is because of size. When organizations are small, they
tend to communicate well. There are less people involved in all
processes; each person is usually responsible for multiple processes
and the atmosphere is usually very collegial. Thus, there is little
need for lots of communication and the communication that does occur
is direct and usually unhindered by multiple layers of management.
When organizations get larger they
start to lose the ability to communicate effectively (for a variety
of reasons). Additionally, as the organization grows, the work
typically gets more complex because you have more to do, even if it
is the same stuff you've been doing for years. It?s like growing
from a two-person IT shop that supports 50 users to a 50 person shop
that supports 5000 users.
So you put these things together and
suddenly, all the things that we used to do that made sense get lost
in the magnitude of the work and the breakdown in communication. As
the organization grows larger, there is a tendency to over
communicate, which increases the chances that the important messages
get lost in the deluge of e-mail, memos, forms, phone calls, etc.
Thus, we turn to methodologies to help
us return to the times when we did a better job of managing by
formalizing the structure. This helps us ensure that the basics get
taken care of as they should.
ITIL, and the other methods mentioned
above are excellent examples of how best practices and their skillful
implementation can lead to outstanding results for your organization.
I do suggest you check them out ? particularly ITIL as it is being
touted as the coming wave of IT service delivery management.
You might be thinking, "Oh, so
ITIL and other frameworks are just for the big guys". And my
answer to that my Padawan (Jedi learner) is no, it is for the little
guys too. In fact, it can be just as important for the small- and
medium-size organizations as the big ones. Whoa! How can this be?
Simply because good habits and processes learned early and practiced
regularly will stay with the organization as it gets bigger, if it is
part of the culture. Even as personnel turn over, if the processes
are firmly in place, they have a tendency to stick around. So
starting out early with one of these frameworks can pay huge benefits
down the road when your organization is MEGA-GOV.
So my suggestion is to get familiar
with one or more of these methodologies and decide which you might
want to try on for size depending on the culture of your
organization. Keep in mind though, that the implementation of any
kind of framework is a BIG DEAL and requires work, work, and then
more work. Also, it needs to start from the top. If management
doesn?t buy in, it will be doubly hard to implement and succeed.
Start slow, research, and join groups
such as ITSMFUSA
in order to have a support system around you as you begin to plan
your journey into an IT management framework. And remember, this
stuff doesn?t happen over night. But by joining a group, you will
have folks to lean on and be able to pick their brains and learn from
their mistakes ? and besides, the cookies were really good at the
meeting Best of luck in your
endeavors!
Ramon,
That's sounds great if you are a new organization with a clean slate to develop policies and procedures. What about if, as in 90% of the cases, you have well-entrenched people and ways of doing things (or not doing things)? It seems like you really need both a GREAT tasting carrot and a BIG stick to bring about the behavior modification that will be required, especially in the beginning when all the naysayers, BTDT (been there done that), and WEBE's (we be here when you came and we will be here when you leave) mumble, grumble and drag their feet. :) That's where it seems like that critical element of Leadership becomes really essential. The road is littered with managers who got bogged down in otherwise worthy re-engineering campaigns because they went about it the wrong way with their staff.:(
Bubba
by madtechgirl
For the past ten years I've been telling clients, in-house and conference attendees alike: It doesn't matter which framework you choose, just pick one and implement it. Just do it. It doesn't matter if you are a new company and can start from scratch or if you are a solid corporation that's been around for years. It doesn't matter if you're private sector or public. If you're in a large organization that has continually flown by the seat of their pants learn how to become a change agent. Document how much time is lost due to reinventing the wheel over and over, how much time is lost testing on the backend because requirements weren't clear in the first place, documentation was never written, misunderstandings continual arose, etc. then equate that to $$$$. Management will listen. It never ceases to amaze me how many companies, including solid corporations are not using any kind of standards, methodologies or quality framework of any kind.
Although it is not a saying you hear much anymore, success
in school used to be qualified by making sure you understood and were
proficient at the three R?s -- "readin', ritin', and rithmatic." And
while it isn?t politically correct to reference them in that way today, the
individuals who spouted that phrase were actually on to something --
particularly when it comes to IT management.
You are probably going "huh?" about now, so let me
explain. The first 2 R?s when it comes to IT management are about
communication. I have written often on the importance of communicating well and
often with all those that are consumers of your services. So I won?t beat a
dead horse on this issue (although I am sure I will come back to it again in
the future -- it?s that critical).
However, neglecting the third R is what can get you into
real trouble. In terms of IT management, that third R means budgeting and
knowing the numbers for your operations inside and out. This can make or break
you as an IT management professional.
Once upon a time, IT was mysterious and magical -- the
proverbial black box. Flawlessly running operations with little or no downtime
was both an art and a science. And as long as you did just that, most people
were pretty satisfied with your performance.
Times have changed, however, and people (your customers and
management) have come to expect IT services to be just like a utility -- always on. Of course, the difference
between your IT department and a utility is that you are not a monopoly; there are not a million suppliers of
electricity and water out there knocking on doors and offering to sell them
cheaper and with the same level of service ? but there are for IT services.
There is always someone telling your management that they can provide the same
services as you better AND cheaper.
To make matters worse, your customer?s budgets are getting
squeezed ever so tightly and, guess what, you are just an expense, my friend.
No matter that you provide the best service possible -- it?s just business, and
Frank here says he can do better than you.
So?with that set of expectations, you had better be good at
"rithmatic." What does that mean? Management expects three things
from your numbers concerning your operations: Transparency, Clarity, and
Consistency. They want to be able to see how you arrive at your numbers, they
want to understand the methodology you used to arrive at those figures, and
they want your numbers to be consistent over time -- meaning that you are not constantly
changing your methodology and accounting practices.
Management may not always agree on how you arrive at your
numbers, nor your methodology for calculating costs -- but those are things
that can be argued and defended.
What gets you into hot water is when your numbers don?t meet
the TCC test (transparency, clarity and consistency). Failing the TCC test
creates doubt -- doubt in your ability to manage the operations, in what you
are charging them, and doubt regarding whether there is any dishonesty
involved. If people think your figures are fishy, you have a problem.
So what does all this mean to a typical IT organization?
That bookkeeping and performance metrics are critical to your operation -- not
from the stand point of how well your operation performs (although they play a
part), but in how your operation is funded and, just as importantly, how your
own performance is judged.
So as a manager, what does this mean for you? If this is a
weakness of yours, you need to get up to speed or find people to help you who
are well-versed in budgeting and accountability -- preferably both.
What you should not do is bury your head in the sand or be
too "busy" running the operation to take care of these things
because, buddy, not knowing your third R will come back to bite you and HARD.
Here are a few resources to give you a start while you scour
the Internet, your peers, and mentors for help.
I have written on occasion that obtaining grants can be a
way to augment your operations should you need additional funding in some
areas. But if you just go out looking for grants because you are short on money
and need to fix problems internal budgeting problems, you are going to come up
short. There are not many organizations willing to hand out money to fix your basic
problems.
However, you can kill two birds with one stone, so to speak,
by partnering with one of your business units in trying to help them solve a techncial
problem that is likely to get grant
funding. This, in turn, could free up your budget dollars if your business-unit
partner can get grant funding for their issue.
As an example, let's say your social service agency wants to
help reduce homelessness, and the homeless shelters in your area lack computing
resources to perform administrative functions. Together, all three groups form
a partnership to create a data collection system for the shelters where the
information regarding their homeless population gets entered into a centralized
system managed by the social service agency for statistical purposes. Once this
concept is agreed upon, you can then look for grants that might pay for such a
thing.
So, if you are looking to fund the above project ? where do
you start? First, you need to decide if you want to go for government money or
foundation money. The rules of the game are a bit different for the two. While
governments have to be fair and equitable and treat everyone the same, foundations
play by their own rules. This may or may not work in your favor. Foundation
grants often require less paperwork than government grants, and they can grant
funds at any time. Government grants are usually fixed to a fiscal year and have
definite application periods. But foundations can be fickle, and they can have
criteria that you may not be able to accommodate as a government entity.
Government grants are more structured and methodical and
have strict rules regarding the process and, of course, the administration of
the grant. However, the playing field for obtaining these grants is relatively level.
Besides thinking about what type of granting organization
you are going to go looking for, you need to know if you are in the position to
do any matching. Matching grants often require a 1-1 match dollar per dollar,
or in-kind contribution. So there is no point in looking at that 10 million
dollar matching grant if you or your partners (always best to partner and
collaborate) can?t come up with the match.
Once you have made those kinds of preliminary decisions ?
you need to carefully study the requirements and deadlines for potential
grants. Your modus operandi in this case is to determine if you can do the
amount of work that is required to prepare the grant (and run it, if awarded)
by the deadline given. Sometimes your answer will be no. It might be a great
grant opportunity, but you just can?t make the time investment to produce a
quality proposal.
Also, make sure that, as part of your reading of the
requirements, you look closely at eligibility requirements. They can change
from year to year, and often federal grants have additional requirements added
to them if the money is funneled through a state agency. Also look for
geographic restrictions.
The two types of granting bodies also advertise
opportunities differently. Governments usually announce their grants through a
Request for Proposal (RFP). Foundations have a variety of ways for publicizing
grant requests. In fact, foundations may not call for a full-blown proposal at
all, but instead may request a letter of inquiry. A letter of inquiry is often
harder to do than a full blown proposal because it has to be brief (usually no
more than three pages). That means you have to communicate your need, your
proposed solution, and your qualifications for implementing the solution very
concisely.
If you haven?t gotten the hint by now, obtaining a grant is
hard work and like most projects, the 80/20 rule applies. In this case,
obtaining a grant is 80% planning and 20% writing. If at all possible, work
with an experienced grant writer if you haven?t written one before. It will
greatly increase your chances of creating a good proposal.
However, if you do not have the luxury of working with someone
with experience, there are ways of getting up to speed. Most large
organizations offer in-house grant writing training. If you are part of a
smaller organization, many colleges and universities offer these courses as part
of their continuing education programs. And of course there are books and the
Internet. Grant Writing for Dummies
is an excellent book to get you started:
The Internet has a plethora of resources on grant proposal
writing including this short course on proposal writing from the Foundation
Center at http://fdncenter.org/learn/shortcourse/prop1.html
and a short course on budgeting from the same organization at http://fdncenter.org/learn/classroom/prop_budgt/index.html
Participating in grant writing can strengthen your
relationship with your business units and help extend your already limited
funds. I personally believe that every government IT staff should have a
dedicated grant writer, whether in house or assigned to them from another department.
Doing so can be the difference between being able to service only some of your
client?s needs or going much further in helping them to do their business.
IT staff often do not think that grant writing is in their
realm of possibilities, but smart government IT management knows that effective
grant writing can add immensely to their capabilities. And anyone can write a
grant; you don?t have to be an English major ? you just have to have a problem
to solve, a solution to propose, and the willingness to do the work to prepare
that proposal.
by bbelon
I've served as both a grant writer/concept developer and grant reviewer for a government agency, and can tell you that you not only need a grant writer (who makes the text sound like it should be in the running for a Pulitzer), but you need someone who 1.) knows the topic inside and out, 2.) has a thorough understanding of the solicitation/requirements, and 3.) can analyze all the potential holes. For those grants that are "peer-reviewed", you may have up to five subject matter experts (SMEs) reviewing your grant and digging into every aspect, from the plan to the budget to the CVs of those who will be taking responsibility for moving the grant's plan into practice. Don't think for one minute that you'll be able to slip anything by these SMEs! Additionally, reviewers are looking for elements that are novel and/or innovative. Submitting a well-written grant that looks the same as most of the other submissions will not get you the funds.
So, I'd seriously recommend that, even if you use/hire a professional grants writer, find someone else who is familiar with the review process, and have them do a pre-submission review to spot the holes and those weak places that just won't fly. Because of the ever-shrinking pot of grant funds, maybe as few as 2-5% of the submissions will be funded. If your grant idea is solid and worthy of funding, then don't rely on an inexperienced writing team or your efforts may not be rewarded.
Dr. Barbara Belon
Belon Research & Practice
Today, I am
going to do something a little different with my blog and share with you a
problem I am struggling with that I don?t have a complete answer for. The
problem is information overload ? not just personally, but also for my
organization; maybe you're having the same problem.
We as
business professionals have more tools than ever before to help us send and
receive information. On the receiving end, we get e-mail, instant messages,
telephone calls, pointers to the Web, applications, podcasts, blackberry
messages, text messages, paper documents, CDs, DVDs, books, magazines, and so on
and so on.
Multiply
the above by the number of individuals in your organization who might be
sending you any of these communications, and the sheer volume of material is
astounding. How do we deal with it, make sense of it, and most importantly,
manage it?
A quick
look on the Web and you will find dozens upon dozens of "solutions"
to this problem in the form of collaboration tools, knowledge management tools,
whiteboards, Sharepoint, groupware, Web conferencing, change management,
document management, and more.
In and of
themselves, each of these tools can be as much a contributor to the problem as
they are a solution. There is no magic bullet. The reason there is no magic
bullet is that each organization is unique, as well as each individual, in the
way they work or prefer to work.
Because of
this uniqueness, what works for one organization or even a set of individuals
within an organization, may not work for others. On top of that, even when
people are clearly drowning in information, they are often reluctant to change
to a "new way of doing things."
Therefore, we
end up with a difficult problem about which everyone has an opinion. The
problem begs for multiple approaches, is not necessarily cheap to solve, and
the solution probably will not satisfy everyone.
So where do
we start? I think the most important place to start is the same place that
therapists tell their patients to start ? by admitting you have a problem in
the first place.
This isn?t
as easy as it sounds. Management may not be too keen on admitting that a
problem exists despite the fact that you can go into most organizations and
document hundreds if not thousands of hours of lost productivity due to
information overload.
I often
cite that organizations have difficulty in communicating, and in fact, by
making that statement, I am not communicating well myself. As you know,
organizations generate a great deal of information that gets disseminated among
individuals ? but is it truly effective communication?
If so, why does it seem
that important information always seems to fail to reach the necessary
individuals, or if it does get to them, it gets lost among all the other noise?"
Is it
possible to communicate too much? Can you have too much information?
The answers
you just gave yourself to those questions may very well be different than mine,
but I think the answers are yes and yes.
I believe
that all the tools we have allow us - or delude us - into thinking that the volume of communication is what is
important and not the quality. And
perhaps if we spent more time thinking about what we are communicating and to
whom, we might become better at it and communicate more efficiently.
But even
coming to that understanding is not enough. The sheer volume of
"good" communication is still vast and overwhelming. There has to be
a plan to manage information in order to make more effective and efficient use
of our precious time.
The plan is
the tough part. Most people are too "busy" doing their jobs to take
time to think about how they work and communicate. But without buy-in and
participation, any solution you can provide is not going to be well received
.
Yet, I know
I have to do something, because I can envision the untapped potential of
workers who are less encumbered by a crushing volume of information and are
free mentally to concentrate on what is important.
I also know that the solution tools I mentioned above are
potentially part of the problem. And that is the crux of the issue. Merely
implementing more tools will not solve anything. I need to create a paradigm
shift in my organization. The American
Heritage Dictionary defines paradigm as: ?A set of assumptions, concepts,
values, and practices that constitutes a way of viewing reality for the
community that shares them, especially in an intellectual discipline.?
Therefore I
need not only to establish acknowledgement of the problem, but I also need to effect
a shift in thinking about how we manage our information and communication. I
have started down the road regarding the first part ? acknowledgement of the
problem.
Tackling the second part is going to be an interesting challenge. I?ll
bring you along for the ride and share my insights with you. But I know it is
going to be a long and slow one given my circumstances. But then again, you
never know ? life has a way of handing you unexpected opportunities. So stay
tuned and share your thoughts and experiences with me too!
by amberhaze
You raise an excellent point. As a consultant, I am often called in when the problem has reached way beyond the breaking point.
As you say, every situation is unique, and what works for one situation often doesn't for another. Since the entities I deal with tend to be smaller private companies, I have found an approach to finding the solution which seems to work for me.
I start by holding a series of round tables with all involved. At these initial meeting, there are a couple of basic ground rules. Leave all technology outside the room. (cell phones, PDA's, laptops, etc)
We start by identifying what informatin each person actually needs to fulfill thier job. We then build a logical framework of how that information should best flow, and finally as consultants, we come up with hopfully the best tool or tools to make this happen. Since people are part of the solution from the beginning, we find they are a lot more open to change than having a solution "imposed" on them.
When all is said and done, we usually find that on average, 80% of the info that was being handled can be eliminated as either duplicated unnecessarily, or else completely irrelevant only being recieved because somewhere, somehow, it has "always been done that way." The side benefit of cutting all this wasted effort on information is a much more streamlined organization where it is much easier to see net performance.
Now if only I could get our own company to apply some of this knowledge... oops did I write that out loud?
by goodwisj
by c.walters
I think that we need to split the problem into
1) Workflow, storage and retrieval of information for the company and
2) Personal information overflow and how to handle this
Both have a different solution.
One of the comments gives an excelent example how to deal with information flow in a company.
Further looking at part 2.
We are interrupted by others while we try to perform. How can we maximize our performance? How can we mitigate interruptions and distractions?
I'm still struggling with part 2.
The following keywords might work:
- discipline
- time management (structure your time to what is important to you)
- set your communication rules to others (like the cc-rule in one of the comments)
- when to attend phone calls and e-mails (they distract you when working).
- don't sit behind your office desk (go to the library or empty office) when you need to concentrate
Cai Walters
Curacao, Dutch West-Indies
by pmoleski
I break this down into two areas, information coming in and information going out. My perspective is also biased by the role that I play in our organization.
As for information coming in I tend to do a lot of skimming to pay attention to trends across a wide range of IT issues. The key technical details I expect to be followed by the staff member responsible for those technologies. At a general level I just need enough to know was is coming and the business value of it so I can plan strategically at a budget and resources allocation level. It also allows me to stay ahead of the user community. By the time they are asking for things we should at the very least know what is possible if not already have the service in place. An hour a day is a reasonable amount of time for this activity. More time is spent on specific items of interest as required. A CIO?s job is to lead so time spent to have a credible vision is well spent. So for incoming I recommend a layered approach of skimming, prioritizing, and then focusing on the really important. I consider this activity to fall into the important but not urgent category, which therefore must be scheduled as a regular part of the day to make sure it gets done.
All of the above forms a base for the more interesting and critical part of communications, which is the outgoing. Things like email are great for timely distribution of routine communications. It is not appropriate for any conversation that is important. These must be done face to face. Email and written communication can lay the groundwork for a conversation. They are also great for documenting the results of a conversation. The truly important conversations are when two or more people work together to discuss an issue and find a solution that this inclusive of all the needs at the table. I just had the privilege of attending a session called ?Crucial Conversations?. It lays out a step-by-step process for having these key conversations. It clearly and correctly makes that case that quality of communications is what counts for anything of importance. Their web site is www.crucialconversations.com.
Personally I have always preferred to talk to someone rather than send an email if possible. The above course confirmed for me the importance of doing so. Because of this I often spend a lot of time composing even a short email because written communications is hard. Without the 94% of communications that is comprised of tone and body language in a verbal conversation it leaves very little left to express using words. For this reason I treat email the same way as my incoming communications. I focus the message and send it only to those who need to see it. When the issue and or I am hot I may compose something as a vent but then discard it and use the mail just to flag that a verbal conversation is needed.
At a senior level these tips are vital as the results of every bad decision or conversation have a broader impact. However, I believe that they apply equally at all levels and in our homes. Quality dialog leading to shared goals and strong relationships is what makes things work. All the rest of the information that flows is fluff. Like many of us I don?t get the communications right all the time and suffer the consequences. However, I am increasingly watching and learning from those who are good at this and not coincidently are without exception very successful.
Phil
by blueknight
Excellent points for sure. Part of my problem over the years, certainly the past 25 years, is that I am an information junkie. Yes, I admit it. For some reason the organizations I have worked for were unwilling to send me for any training unless it was free. This presented me with a problem -- how do I keep up on today's technology in order to do my job. My job of course was to wear many hats including all aspects of the local and wide-area networks, servers etc as well as being a mainframe systems programmer, DBA, systems analyst and programmer. I was reading as many as 32 trade publications to soak in as much information as I could. Then I'd search out other information I needed, or wanted to know, on the web. At one point I thought I'd need a 12 step program to cut down on all the information. I've been an informationholic for nearly 40 years and it's hard to change.
When I began working in my current position I made a decision. I paid a lot of attention to what I read and what the content was and compared it to other similar sources. I then discontinued those sources that were redundant or that didn't do as good a job as others covering the same topics. I'm down to about 10 trade publications now.
I also have changed my reading habits with regard to information that comes in e-mail form. I scan what comes in rather than reading everything. If I don't see anything interesting in my scan, I delete the item. I've also come to the realization that as much as I like to know everything and learn all kinds of stuff, I simply don't have time to do that and do my job.
Your time is precious, so use it as wisely as you can. Don't waste time reading things that are redundant or that don't contain information you NEED.
You said "...why does it seem that important information always seems to fail to reach the necessary individuals, or if it does get to them, it gets lost among all the other noise?"
I think that part of this problem is that often times those who receive the information are the wrong target. Either that, or they are so overloaded with incoming information that they can't deal with it, thus it gets lost.
Before I send something, I consider who my target is... just like writing. Before you write, whether it's an article, or instructions on how to do something, you need to consider who your target (audience) is. That way you can write directly to them. Your communication is therefore much more direct and meaningful for the recipients. Do the same when sending corporate information. Send it to those who really need it. If you're told that someone should be cc'd, find out why if you can. If it's basically just for the heck of it (because we always send this stuff to so and so), call that target and ask them if they need the information you're about to send. If not, don't send it to them.
If I get stuff I didn't request and has no relevance to what I'm working on , it goes in the "trash" without a second thought. I don't have time to read everything just because it shows up in my inbox.
You can make a difference in the information you send out and how you handle what comes in. For information you send to others that seems to get lost within their information universe, there's nothing that you can really do. They need to figure their way out of their problem just as you have, or are in the process of working on.
I am thankful that we don't use IM much here at all. We started out with a complete ban on it in the beginning because of the security risks that come with it. Since then we have installed GroupWise Messenger (yes, we're a Novell LAN shop). I don't get IM's from outside the organization, but on occasion I do get one or two from coworkers who really need info fast. IM works well like this and I appreciate not being overwhelmed with non-essential messages. And, fortunately, I have found no compelling reason to get a PDA (with or without phone). If I want to check e-mail, I do it from my desk. If someone truly has an emergency situation, they can reach me by pager.
It sounds like my life is a bit less complicated than yours, but I had to work at it to get it this way, and I have no intention of changing.
by danhouse
We have a short, informal test of "solutions" before allowing them in.....
First, what does it cost. In money, manhours or training. Second does it directly and mmediately contribute to the bottom line, to productivity or some other criteria.
If it fails either one, we dont do it. Or we allow the "solution" to be introduced in small numbers but refuse to support it. By making this known as our standards for new stuff, we have cut down on folks wanting to implement stuff willy-nilly.
by stan k.
I look at the concern for
"information overload" philosophically, that is by employing
discipline, logic, skepticism, and a high regard for the qualities of speech
and expression.
What does all this have to do with information overload?
Becoming more rigorous in your thought process can help you to detect
what constitutes information and what is likely to be communication noise.
This helps reduce both the amount of time you give to nonsense and the
amount of anxiety you might feel for ignoring it.
by goodwisj
by dc guy
This thread on "information overload" contains a couple of 2 1/2 page postings. Did you all read them? ^_^
You made a good comment and also how to find the solution:
The solution starts with " a shift in thinking about how we manage our information and communication" or Change management
1-Make a company campaign: How would you solve your own Inbox problem? Starting with the Inbox brings each person to their own problem creating a collaborative company to propose a solution. Work together with the company management on a program tying the HR team together
2-You must understand why people send messages and how they respond them. What kind of emotion is embedded in each message?
Every communication brings the writer?s emotion like anxiety,passion, love, fear, power or worried about something embedded in the message. The emotions and related e-mail behavior are explained in the Surfing the email high tide chapter in the Managing Your Business with Outlook 2003 For Dummies book The beavior chapter applies to any other e-mail software.
2-Understanding the emotions and making presentations to the whole team shows where the problem is hiddden and starts the solution?s road.A smile to brake up the day is welcome but ten jokes a day? Call Batman to fight your Joker enemy or eliminate his messages using e-mail rules, Mary Slicer is an anxious human being, and she sends an update message at every step of a job, when the job is complete the requester received 25 messages. Showing the behaviour and asking her when she expects to finish the job? If the answer is Two days great! Ask her to send the job done message as schedule. 24 messages per job will not be written anymore.
3- The Zen of Inbox Management training.
Marcelo Thalenberg
marcelo@myboutlook.com
It seems to me the only way to a solution is to actually teach every one in your organization when to write, when not to write, and how to write. Perhaps the most important thing is when it is "not" necessary to reply to an email.
People must be educated on what information to keep and what information to toss in the trash. When people don't know, they tend to keep everything, but can't find anything in their mountain of unimportant stuff.
I think it will take an aggressive approach to get these things in people's heads, and as much as I feel opposed to using a heavy hand, I don't see things changing without clearly spelled out communication rules ... and some type of enforcement. Think of it as just another application of business rules like we all must follow in other areas of our business organizations. People will learn if we take the time to teach them.*
If we fail to do this ... and as management comes to understand the incredible amount of time employees waste on digital communications -- and the lost business and irritated customers caused by lousy writing skills -- and on information mismanagement ... they will insist on fixing the problem. And it won't be a pleasant fix.
-------
*I personally would not mention the American Heritage Dictionary definition of "paradigm shift" or other such intellectual blaberisms in training because the average person is not
interested figuring out sentences of that length and complexity. I might go so far as to suggest that even "thinking" in those terms hinders
rather than helps us find solutions to problems. (so shoot me ;-)
The following few paragraphs are excerpted from the 2005 UK Influenza Pandemic Contingency Plan:
?Most experts believe that it is not a question of whether there will be another severe influenza pandemic, but when.?
(The Government?s Chief Medical Officer, 2002)
The widespread occurrence ? and continued spread ? of a highly pathogenic avian (bird) influenza virus (H5N1) in poultry in SE Asia since 2003 has increased concern that this could provide the seedbed for the emergence of a new human influenza virus with pandemic potential.
While international efforts are being directed at preventing such an event, or aborting it early in its tracks, the opportunities to do this are limited and once established, the virus will spread rapidly. The tools to reduce its spread and impact are also limited, and will have to be used to best effect. The UK Government gives high priority to improving our preparedness to manage an influenza pandemic. This document which updates the March 2005 Contingency Plan, sets out the overall UK response. It concentrates on the central Government and health responses, but provides the information and framework for the planning which must take place across all sectors of society.
A pandemic is the worldwide spread of a disease, with outbreaks or epidemics occurring in many countries and in most regions of the world.
Influenza (flu) pandemics have swept the globe from time to time throughout history with devastating effect, far in excess of that resulting from the ?seasonal? influenza which (in the UK) occurs most winters.
Three pandemics occurred in the last century ? in 1918/19 (?Spanish? flu), 1957/58 (?Asian? flu) and 1968/69 (?Hong Kong? flu). Up to a quarter of the UK population developed illness in each of these pandemics, many thousands of people died and the associated economic and social disruption was huge. The most severe ? that of 1918/19 ? is estimated to have killed around 250,000 people in the UK and between 20 and 40 million people worldwide, a greater toll than the whole of the First World War.
A pandemic of influenza results when a new influenza virus emerges which is markedly different from recently circulating strains and is able to:
? infect people (rather than, or in addition to, other mammals or birds)
? spread readily from person to person
? cause illness in a high proportion of the people infected, and
? spread widely, because most people will have little or no immunity to the new virus and will be susceptible to infection (they will not previously have been exposed to it or a similar strain of virus, and any previous vaccinations will not have covered the strain).?
Scary stuff isn?t it? This is the kind of thing we read in science fiction novels or history books but it isn?t supposed to be a reality for us now ? right? Unfortunately it is, and most of our disaster recovery/business continuity plans are inadequate to deal with this sort of event. Why? ? Time frame and affected area. Confused? Let me explain.
Most of our continuity of operations plans (COOP) and disaster recovery plans assume a catastrophic event that destroys infrastructure and personnel in a localized area but the "event" is over in a relatively short period of time ? days, or at the most, a few weeks. Hurricanes, earthquakes, floods, even bombings and other acts of terror are assumed to be relatively short lived. Then the rebuilding starts. You assess the damage, put your plan into action, and begin anew.
An epidemic or a pandemic is different. The onset is not as dramatic as a natural disaster, the impacts are wider spread, physical damage to infrastructure is not a key characteristic, and they occur over a much longer period of time. Quite different than what our "normal" COOP plans address.
For example, many IT COOP plans have as part of their plans "hot" sites to which operations can be switched. But what if your "hot" site is in an area just as infected as your main site? See the disconnect? Our plans assume physical disaster that prevents work, not the wide-scale loss of personnel to do the work over a long period of time.
It is time to begin to think differently about continuity of operations.
The U.S. Congressional Budget Office issued a report in 2005 in which it considered two possible scenarios for pandemic ? mild and severe. The severe scenario projects 90 million cases of infection, 2 million deaths, and a 5% drop in GDP.
Let?s imagine this scenario for a moment. You have large areas of the country possibly under infection with workers sick, dying, or unable or unwilling to come to work because they are at home caring for loved ones who are infected or are afraid to come into contact with another human being. Particularly heavily affected areas might have to be quarantined (this could be your place of business) or a large section of town in which your workforce resides.
This, my friends, is a completely different problem than what is assumed in our typical disaster planning.
So how do we go about tackling this one?
A.
Remote access of systems from outside your organization by large numbers of users would probably be the norm; i.e., people working from home or even other cities.
B. Key personnel will become temporarily or permanently disabled, leaving gaps in knowledge and leadership if appropriate measures are not taken.
C.
Infrastructure that we currently depend on to provide access may become overtaxed, and therefore unavailable if much of the world is working remotely.
D.
Collaboration tools become even more important if people cannot physically be together.
E.
Your key partners in business may not have a plan to deal with the crisis and therefore may become non-existent or useless.
I could go on, but that?s what your planning effort is supposed to be about ? determining what our needs will be during such a prolonged crisis.
My purpose in writing about this is not to be a ?Chicken Little? and run about screaming that the sky is falling down ? we had enough of that with Y2K; but similar to Y2K, start a thought process and a discussion that will lead to planning, as it did leading up to the year 2000, that ends up with most organizations having crafted plans that will have IT be a non-issue in such a crisis. There are a lot of "ifs" concerning avian flu that could make it a non issue in the future (and I really hope that is the case) ? however, is your organization willing to gamble on planning only when the crisis appears imminent?
Implementing the
LAMP Stack
The LAMP Stack (for
Linux/Apache/MySQL/PHP-Perl-Python) represents a major reconsideration of how to
design and implement a high-availability, Enterprise-grade Web infrastructure.
Using best-of breed open source technology, companies and organizations are able
to design, implement and administer cost-effective, robust environments which
meet and exceed more proprietary solutions. Attend this webinar if you
are considering any of the following:
In this webinar you
will get an in-depth look at:
To register, go to:
http://www.mysql.com/news-and-events/web-seminars/lamp.php
by wtr
In 2004 - 2005 I instigated this type of configuration into a company using the Microsoft Terminal Server technology without a Citrix server, the results have been very positive and decreased the TCO extensively. The configuration has been in place now for almost 2 years and has been stable and secure.
It also has allowed users to remote access with ease (where granted), it has also decreased the administrative time needed to manage the network and brought desktop management to a central location thus easing the burden of managing desktops over a large geographical area.
Due to the success of this thin client architechure I am very much a supporter of this form of configuration, the only downside to this form of networking is the loneliness expierence due to the deacrease in administrative staff.
Through effective policies and frontline security measures the network has not to date been effected by an external threat either viruses or spyware .
Also with a storeroom full of once obsolete PC's we can now re-commission these units to become active nodes on the network. (dumb terminals)
I was in a strategic planning meeting the other day and as
part of the discussion, a decision was made to pursue the creation of one or
more positions. That?s a good thing, as opposed to talks about layoffs, and it
made me think about how job opportunities often spring out of the blue. The
question then becomes, does the job interest you and are you prepared to take
immediate action on the opportunity - because, as the saying goes, if you
snooze, you lose.
In this case, and another recently, the positions were nice
enough that for a brief moment my interest was piqued. But only briefly,
because I just started a new position and am enjoying it immensely. However, if
that had not been the case, would I have been ready to make the most of the
opportunity? The answer is, probably not as ready as I could be. Why? Because I
have not been keeping my job journal up to date. Please note that this is not
the same as keeping your resume up to date. The difference? Let me answer by
explaining what I call a job journal, how you go about keeping one, and what
goes in it.
What I call a job journal is a diary of sorts in which you
make note of your accomplishments; keep track of boards, committees, and
workgroups you participate in or chair; track hours spent doing project
management; document products you have created or were involved in creating;
and provide enough detail about each of these entries to jog your memory should
you need to talk or write about it later. This is the information that will
fuel your resume and cover letters and provide you with material to speak about
during an interview. It also gives you information for preparing applications.
For
example, if you want to become a certified project management professional
(PMP) you will have to document the number of project management hours you have
under your belt for a certain number of years and also what category of project
management those hours fall into, such as project inception, planning, etc. This
is another good place to keep track of all the training you take - the course
title, when, where, who offered it, and so on.
Basically, the job journal consists of the small details of your
daily work life that you think you
will be able to remember, but by the time you need to accumulate that
information, you've either forgotten the details of your accomplishments, or
misplaced the documents or e-mails that would have provided it to you.
I am a strong believer of keeping your job journal in a real
paper journal pad. You can transfer the information to some form of electronic
media if you wish, but I believe that it is the handiness of having it in your
desk to make quick notations that makes it special. It also can?t get locked
away from you should you be told to clear out your desk and you suddenly find
yourself unable to log into your corporate network.
However you keep it, you should keep one, and keep it
updated while the information is fresh in your mind. It is up to you how
verbose you want to be with your entries, but they should be detailed enough
that they don?t leave you wondering what you meant if you pick up your journal two
years from now.
Besides getting you ready for your next job opportunity, journals
are also very useful in preparing your own performance evaluations as well as
creating lists of accomplishments for a particular time period. So make sure
you time stamp every entry and indicate the beginning and end dates of
everything.
If you are a manager or supervisor, you might consider
having your employees keep a journal as part of their "growth or
professional development plan". It is a useful tool for everyone up and
down the corporate ladder - and if you do a good job with it, you just might
find that you will be the person who is best prepared to respond to
opportunities when they appear out of the blue. So what are you waiting for? Head
out to your office supply store and pick out the journal that is going to
document your work history from this point on. You won?t regret it. In the mean
time, I?m going to go bring mine up to date. Good Luck!
by putchavn1
Sound and Simple
Yes, it is easy to launch and it works. Set back, if any, would be treacable to not updating the journal. This is true for the professional and those who report to him. Well, this does not have much to do with Government!
Now let me update my journal.
by karen mac
Sounds like a great idea. I'm going to start one immediately. The challenge will be to keep it up to date in the midst of the daily flurry of activity.
By the way, don't let people tell you that government workers don't work hard. Most of them that I've met have been very dedicated to their work and put in looooong hours to make sure things get done right. At least that's the case in Canada.
I've been doing something similar for over 20 years now. First, as an engineer for a defense contractor, I had to keep track which project and phase I was working, even admin time, all to keep the auditors happy becasue we didn't want to fudge on reported costs. Then I became one of the auditors, and still had to keep track of how much time I was spending on a given project. Even in the private sector, this was the case. We needed to be able to track our time to make reasonable estimates for the next job. Now that I'm in a government position, I'm still doing the same things. but you're right about it being a good tool for interview prep. I've never been at a loss for describing what I've done or for one of those "tell me about a time when you..." questions.
by blueknight
Great idea Ramon. I'd never thought about a job journal, but I have kept track of major projects etc. for updating my resume. I have to agree with Karen Mac from Canada, most of us in public service work our tails off; the past 2 years have been particularly busy for me with barely a minute to catch my breath before the next item demands attention. Of course that isn't very conducive to maintaining a job journal, but I'll plan to make that part of my project management tasks... update project status, update journal -- should work. I have just the perfect sized notebook for a journal... now to get started.
Thanks,
Jimby rayjeff
by pmp 1995
Tip & Technique: I use a spiral notebooks, graph paper pages to help create columns and diagrams, with pre-numbered pages. The page numbers help to make cross references to other pages to LINK notes together. My notebooks have a few pages in the front for manual indexing. So if I need to skim the notebook for everything related to one employee or one project, I can easily create my own index with page numbers and then read all the references. I don't index frequently, but if I need to build to case for one reason or another I take the time and do the research in my own notebook. I mark the covers with start and end dates on my assignment on my current business card and tape it to the front of the journal for that assignment. (I started this technique years ago when I worked in laboratory that supplied these notebooks for recording patent development activities. Now, I have to buy my own but I am addicted to the process. I have a separate series of notebooks for my volunteer work.)
TACTICAL USE: I take the spiral notebook with me everywhere on the job. I keep it in my briefcase ALL times. I take ALL my notes in the spiral notebooks. I enter a date line every day. Then each time I start a meeting or drafting some thoughts I enter the time of day and then the notes. If it is a meeting I try to jot down place and participants as they are are introduced. Then I take notes. Sometimes I have very little to write and sometimes 3 pages from a single meeting. If I am trying to plan something, I put my initial thoughts in the notebook. Keep the entries of who, what, why, when and where. When I was doing design work, I kept my ideas in the book potentially for patent purposes. When i became a manager my notes sometimes were about employee discussions. When I get a phone call i could the enter the who-what-why and contact information notes. Just about every week I am looking back at the notes and finding to-do's that I forgot I commited to do, phone numbers that I took while talking on the phone and thought I would never need again, notes about when I placed a complaint (personal or business) about something and now this is the third time i am calling and I can go back through the notebook and recreate the chronology. You would be amazed how powerful it is to write a letter to the Pres. of company documenting three phone calls over a one month period with who, what, and when included and the promises made.
STRATEGIC: If you are looking for a new job and you need to create a series of resumes for different target opportunities, the notebooks become your resource material. If you have only one resume, you will re-think that as your career develops. Different aspects of what you have accomplished need to be emphasized for different target opportunities. Since my notebooks are chronological, I can start skimming them and memories come back about what problems i worked on, what actions i took, and what results i achieved.
SUMMARY: Long and short of it. Keep a "job/life journal". You will be amazed how many times you go back and use the history. I started a new assignment 15 months ago. I am on my third spiral notebook. The notebooks are about 100 numbered pages each. I keep the first two volumes in my desk next to me. I refer back to them couple of times per month for many different reasons as different issues come up that I know we talked about before. I find the notes have the highest value during the first six months of any new assignment when I meeting all new people, processes, and challenges for the first time.
After 20 years of doing this, I can tell you that no matter what you are doing in your career or life this will be a blessing some time. Integrate "the notebook concept" into your life. Life is full of surprises. Be prepared.
Many of you are heads-down in your budget process now and
some of you are perhaps at a juncture where you are choosing a new product to
upgrade or replace an existing hardware or software system.
When choosing to upgrade or replace, there are many things
to consider: price, functionality, how it fits in your current environment,
warranty, service, etc. But over the years a new dynamic has been added to the
mix ? vulnerability due to popularity. By this, I mean the hardware's or
software's propensity for being a target of "security attacks"
because of its notoriety.
Obviously the king in this arena is Microsoft. Whether you
believe Microsoft is doing enough regarding security is up for debate, but
there is no arguing that a large number of people love to hate Microsoft. Because
of this, Microsoft products are the targets of innumerable attacks and exploits
? the result being a new Microsoft vulnerability seemingly in the headlines on
a daily basis.
To be fair, Microsoft is not alone and Oracle and Cisco have
had their share of headaches as well, being the targets of malicious software. Not
surprisingly, one might assume that most of the "leading" software
packages in all the different software categories garner a greater share of
attention from hackers and other malcontents. So the question becomes, at what
point, if ever, does a product's propensity for attracting attacks figure into
your decision-making?
Does the constant need to keep updated regarding security on
a particular product reach a level where it is not worth the trouble and a
decision is made to go with the closest competitor who can give the same or
nearly the same functionality?
Let's take as an example, Microsoft's Exchange Server. One
could argue that Exchange requires a greater amount of support than competitors
such as Scalix 10 and Zimbra Collaboration Suite because it resides on a
Microsoft operating system and is immensely more popular and thus is a magnet for
attacks.
Assuming you are a Microsoft shop and have no Linux
expertise in house, do you ever reach a point where you will make the
investment in new knowledge such as Linux in order to implement one of the two
aforementioned products that give the same or similar functionality as
Exchange? Or does sheer inertia keep us doing the same thing from year to year?
What about file and print services? Novell certainly knows
what it is doing in this arena (technically speaking, they are still horrible
at marketing in my opinion). When the decision to switch to a new Microsoft
server operating system is being presented to you, will Novell ever be
considered?
It is my belief that the security risks and costs associated
with using a particular product have to be greater than the personal risk the
decision maker is taking when deciding to switch products before he or she will
ever do so. Inertia is that powerful.
It is also my belief that the type of risk associated with a
"popular" product should be part of the decision-making process.
So how does one ever place themselves or their organization
in a position to truly assess the merits of a "legacy" product vs. a
competitor's when they already have a product in place?
Don't make the decision on your own or in a vacuum. That's
what governance committees are for and that is where good executive management
comes into play. Both are required in order to make the best decision for the
organization.
Lastly, there will be some who will argue that you
cannot create a totally secure piece of software or hardware, and that exploits
are going to happen ? so don't even consider this in your decision-making. I
can understand this point of view and to some extent it may be true. But I have
to believe that there are IT professionals sitting out there in the wings,
using "non-mainstream" software and hardware, providing equivalent
services for their users, and they are grinning and stress-free as they read
this article!
by dawgit
Fired? That could be one way to put it, Freed would be another. He did open the door to something different, and to discussion. He could be said to expose entrenched closed mindedness, and hyprocy, that is always present in goverment circles, at all levels. It is the nature of the beast, and he got bit. But in time they will be proven wrong (as always) and 'Open' will be the prevailing way.
Pardon me if I seem a little cynical this week; it?s been
one of those weeks where I have borne witness to a lot of decision-making that
seems to be decoupled from logic. Actually, that?s not the best way to phrase
it, because there is logic behind this decision-making, just not common sense.
The logic I am speaking of is the old "sacrifice the
future for short term profits/gains". I guess by now I should be used to
it, but it still aggravates me to no end. This week, I participated in vendor
negotiations in which the vendor suddenly changed the deal in order to try to
hit quarterly profit/revenue targets, knowing full well that the changes would
be a show stopper. I have watched as legislatures around the country continue
to make decisions based on short-term political goals, rather than long term
strategies, and I have read articles such as this one from ZDNet that heralds
that "outsourcing
saves less than claims". It's yet another example of short-sightedness
as a result of trying to maximize short term savings.
I wonder if this will ever end and people will think about
the long-term implications of their decision making as a matter of habit? I
kinda doubt it, but I know that the exception for the most part will be my
Government IT fellows. For the most part, unless forced to because of lack of
funds or political pressure, I find government IT professionals to be forward
looking. Why? I think it's mostly because they have every intention of being
there when plan x or plan y concludes, even if the plans span administrations. Hail
to those in it for the long haul!
That being said, it seems anymore that we are faced with
having to think short term because of such a lack in funding or political will.
When you are forced to try and get blood out of a turnip, it?s hard to think
much past keeping things running and not worrying about tomorrow. Yet that is
exactly what we must do in order to do the best job we can for our organization
(while we watch everyone else cut their noses off to spite their faces).
So how do we face this conundrum? How do you do what is best
for the organization in the long run, knowing that long-term solutions often are
costlier up front or require more work than the quick fix?
I have a few strategies that seem to work for me. The first
one is to break up the planning for a project into many short phases that over
time add up to a long term solution. Each phase encompasses what you CAN do with the resources you have
during that time period. For example, your goal is to create a data warehouse
for your organization, but you only have enough funding to create a data
porta-pottie, instead. Start breaking it down into chunks. Begin with the planning,
and go for the whole enchilada, but phase it such a way that you are directing
much of your work within the framework ot the more affordable data
"cottage." Yes, you know there are going to be scaling issues that you
need to deal with, but work with the tiny increments and invest what you have
in good design and planning. Do "proof of concepts" that can grow
rapidly with enough funding and attention once it is garnered. Always be
prepared to be able to expand your plan into the next phase should funding
become available.
Another method is to strategically over-buy just a little
when you get the opportunity. Kind of like buying four cans of tuna instead of
the three you need and putting one away for a rainy day. You have to be careful
with this strategy, but if done right, over a relatively short period of time
you might be able to assemble the thing you wanted to do in the first place,
but didn?t have the money for all at once.
The third strategy is to be flexible and do some hard work
in the short run in order to save dollars and work smarter in the long run. Yes,
it is harder to find staff that are experienced with open source solutions than
it is to get your current expert in Oracle or Microsoft. However, if you can
place an open-source gem or two in your organization and don?t get caught up in
staying homogenous, you might be surprised at how well you can do.
Fourth, hire the old guys! Over the years, I have hired many
retired military or government workers who want to come back because they need
some extra money or just want to be productive. They don?t ask for huge
salaries (meaning they can work for the pittance you can pay them); they have
strong work ethics; and they usually have a desire to learn. For example: Do
you need a start with Linux in your organization, but you can?t find someone
suitable? Did you advertise for UNIX knowledge as well? It is a short leap from
UNIX to Linux, and you might find the grizzled UNIX admin who was phased out to
make way for an influx of Microsoft techies. Guess what? That old hand probably
brings a ton of transferable experience that you couldn?t afford if he or she
was a veteran MCSE. Give that person a little training, and you have rock-solid
foundation to build your Linux systems on. I use Linux as an example, but you
can replace that with any older technology that is similar to something
employed today.
Lastly, continue to be the flexible, do-the-impossible
entrepreneurs that you always have been, because without you many government IT
shops wouldn?t function at all. My hat?s off to you. Carry on!
by gentlerf
by shane.beard
The best way to fix outsourcing is to outsource goverment from the
Senate to the President, then they might look at it a different way.
by mida235
Outsourcing or offshore? Should government be sending tax moneys offshore?
This is the real question. Most IS professionals who have spent time in both public and private sectors understand the concept of outsource. In old school terms, outsource would equate to hardware maintenance contracts with the manufacturer or having your internal IS staff self maintain. Under the new world of outsourcing, outsource equates to some or all of a service being performed outside the US. In countries that do not have child labor laws, minimum wage, large labor unions, corporate funded retirement plans, social security benefits, or unemployment benefits to be paid. This is the quandary we are faced with. It is this persons opinion that tax moneys paid by persons and businesses within the US should stay in the US, even if it means we pay a little more for the service. At the very least it will serve to slow the rapid decline of the American way of life, and maybe, just maybe, long enough for the offshore standards of living to improve to a point where our internal labor force can compete on a global scale, on level ground, including the costs of social infrastructure necessary to support large growing economies.
by mida235
Outsourcing or offshore? Should government be sending tax moneys offshore?
This is the real question. Most IS professionals who have spent time in both public and private sectors understand the concept of outsource. In old school terms, outsource would equate to hardware maintenance contracts with the manufacturer or having your internal IS staff self maintain. Under the new world of outsourcing, outsource equates to some or all of a service being performed outside the US. In countries that do not have child labor laws, minimum wage, large labor unions, corporate funded retirement plans, social security benefits, or unemployment benefits to be paid. This is the quandary we are faced with. It is this persons opinion that tax moneys paid by persons and businesses within the US should stay in the US, even if it means we pay a little more for the service. At the very least it will serve to slow the rapid decline of the American way of life, and maybe, just maybe, long enough for the offshore standards of living to improve to a point where our internal labor force can compete on a global scale, on level ground, including the costs of social infrastructure necessary to support large growing economies.
You wrote:
"I wonder if this will ever end and people will think about the long-term implications of their decision making...?"
Not until the constituency that the powers in place pander to stop demanding short term gratification.
by gmorgan14
Well said. I have found that private companies vs. public ones look for the "best" solution because their goals are the long term health of the organization instead of a bonus, tied to profit, this quarter. There will always be individuals who are more interested in their personal agenda and they tend to thrive in large public companies. You sound like you have managed ,quite successfully, to circumvent short sighted executives to deliver value to your company. Thanks for the note to confirm that there are still some of us who intend to deliver the right solution for our companies in spite of the hurdles placed in front of us by the persons who should be smoothing the way.
I'm trying to remember the industry where a Japanese company spent 22 years trying to get into the US market, losing money every year. Now they dominate it completely. I don't think any US company thinks even one year ahead, or even one quarter.
Great suggestions!
by tony.maine
I think this is a universal human attribute, and it's built into us at
a very basic level. It has arisen because in the distant past neither
we - nor any other living thing - had much if any conscious control of
our environment, and in such a case long term planning was futile. The
best strategy was just to stay alive, which is a short term gain,
measured over a timescale of days. Now we have set in train systems
which demand much longer term planning than a few days of weeks - and
look at the resistance to change you get! Look at the excitement when
the stock market jumps a few points in a few minutes, even though you
know it could plummet next week (or even this afternoon). The
only system oriented solution I can think of is to weight short term
gains low against long term gains when doing the calculations. This
might help re-align decision making based on common sense with that
derived from logical conclusions. Getting such a strategy accepted
however is not going to be easy.
by knemow
I don't know that it is a "common human attribute" to be short-sighted.
There are quite a few people who are so far-sighted that they cannot
break projects into smaller steps and goals. The problem that I see is
that if you are a short-term person, you are more easily able to
demonstrate the immediate benefits and results, but the long-range
plans face a lot of uncertainty. What if the economy tanks? What if the
market goes away? What if a newer, better technology comes out
tommorrow?
Long-range plans also tend to require careful consideration of a wide
range of information, which we often are not given the time to present.
It is not realistic to expect people who's expertise is in another area
to easily grasp what we are being paid to know. They are being paid to
know something else, regardless of how well they know it. Short-term
presenting plays well in this scenario because it is simple. It is
simple to show how the upfront costs of outsourcing are lower than
hiring quality people in-house. It is difficult to quantify the value
of experience, loyalty, and work ethic.
This is especially powerful in a culture that is so directed by
scientific thought. Science requires hard numbers, quantitative
measurements, and calculations. Most Americans have been reared under a
culture that promotes science as the appropriate method of solving
problems. Unfortunately not all of us have not taken the time to fully
commit to scientific principles, but most people do seem to understand
making decisions based on solid, quantitative data. Nevermind that they
are often just looking for numbers to support an opinion that they
already hold, those short-term numbers are very compelling.
"MobiKey is the
world's first USB thin-client for instant, secure remote computing. The latest
edition to Route1's Mobi Solution family, MobiKEY simply plugs into a USB port
to turn any internet-connected Microsoft Windows computer into an instant,
secure Virtual Private Office, with computing, applications and data located
elsewhere behind a firewall."
I had one demonstrated to me yesterday in my office and I
have to say that my interest has been piqued. The response was similar to a
Citrix session (meaning it is as good as your network and the latency between
client and host) and was easy to install and use.
The basic idea behind MobiKey is that a host (the PC to be
remote controlled) is set up and registered with Route1 as a device that can be
controlled by a particular MobiKey. The PC is left on (and hopefully locked by
the user) and can be accessed by the authorized user by inserting the MobiKey
into any USB port of any machine running MS Windows
2000 or later. The MobiKey then contacts MobiNET and the user is prompted for a
password. This password is validated using the MobiKEY's SIM Chip granting
access to the MobiKEY. Then, further security credentials are authenticated and
MobiNET presents a list of available Hosts to the MobiKEY user. Once the user
chooses a host, MobiNET goes through a process of establishing an SSL session
with the host, which allows the user to control the host securely ? as in most
thin client applications. The pricing given to me for the above was approximately
$400 per device and a $40/month fee.
So what is this device really? A
poor man's VPN? A way to deploy thin clients in the field? Or a way to quickly
provide a secure connection to a machine in your network on the fly? Or maybe
all the above?
My first thought when presented
with the device was "cool, a VPN replacement." But that's not the
case. In an emergency or disaster that destroys the physical infrastructure,
knocks out power, etc.?if you have things set up correctly?you probably have
back-up power for your server room and major network components. Therefore,
even if all the power is off to your main offices, or your site no longer
exists, a traditional VPN or Citrix-style solution allows you connectivity with
the network and its resources. However, with MobiKey, the host PC has to be
powered up and have an Internet connection.
That being said, smaller offices
or organizations that do not have this standby capability could use it as a VPN,
realizing that if physical disaster strikes, they may be out of luck.
Notice I say physical disaster,
because Route 1 is positioning the device to be used during health/ecological
disasters in which your infrastructure is fine, but the people may be required
to leave the office. For example; an envelope containing a white powder is
discovered in the mailroom. The order to evacuate the building is given. Key
users who have already registered their machines with MobiNET grab their stuff
? (leave their PC ON and locked) and go home. Once home, they plug the MobiKey
into their PC and?ta da!?they are working securely from home as if they had not
left the office.
Not a bad idea if your number of
"key" individuals is fairly low, and you do not have a VPN or Citrix
style solution already in place for those individuals. This could be very
important in your pandemic flu planning. My guess is that once your numbers
start to grow greater than 50, deploying a Citrix server may be more cost
effective. However, giving Route 1 the benefit of the doubt, I have not asked
them about volume discounts, so I am not sure where the break point occurs and
when it would be more cost effective to deploy a larger-scale thin client
solution.
I can also see keeping a few of
these around for individuals that suddenly need to work from home because of
illness or injury. This way, you can assist HR in making special accommodations
without having to have a corporate laptop or desktop to give to each person
that needs to work from home.
There are more creative ways to employ
the device for sure, and I am going to acquire a couple just because of their
flexibility. But it certainly is a device/service that can be a valuable
addition to your tool kit.
by jpollard
Mr Padilla: Virtualization is a form of computing that addresses the above concerns re physical disasters. And this is where MobiKEY shines since you can put your infrastructure anywhere in the country .. like away from Hurricane areas, and access the virtual workspace reliabily and securely. It IS a thin client
Also I would suggest that implementing a 100 user Citrix solution vs a 100 user MobiKEY/virtuaization solution including system support etc, will be significantly lower than Citrix. Many reasons for this..
Costing .. fear not .. I would suggest that pricing depends on your application .. and there are big tax advantages as well .. doesnt have to be CapEx..
Its the 2 factor authenticaton mate - along with a bunch of other stuff.. I dont work for the company and have reviewed the product and technology for 2 different manufacturing automation magazines..
Keeping an eye on this one!! Cheers mate
Jeremy Pollard
by tami
Mr. Padilla: As a trusted reseller of the MobiKEY, I would like to take the opportunity to clarify some of the points you bring up.
Firstly, The MobiKEY is about high security, simple-to-use remote access, without exposing an organization to the risks typically associated with browser-based remote access solutions. There is no risk of the Guest Computer infecting the Host Computer, and the MobiKEY?s unique two-factor authentication ensures individual access is not compromised due to loss or theft.
At $399 including the first year of service, it is one of the most cost-effective, remote-access solutions in the market today. It extends control of the desktop environment while reducing the associated costs required to support and secure the mobile workforce. I have seen the TCO models and the financial impact is truly remarkable. IT managers appreciate its ease of deployment and users appreciate that, although remote, they can work in the comfort of their own workspace, with the same administrative rights as if they were physically on-site.
I encourage anyone who is looking for a simple, secure remote access solution to check out the MobiKEY
Well get ready for the hype: Here is a press release for a made for TV movie that should stir the pot a bit and below that is a press release regarding a show that came on this weekend:
*****************************************************************************************************************************************
April
17, 2006
ORIGINAL MOVIE ?FATAL
CONTACT: BIRD FLU IN AMERICA?
TO AIR TUESDAY, MAY
9 ON ABC
Joely Richardson,
Stacy Keach, Ann Cusack, Justina Machado,
Scott Cohen and David
Ramsey Star
There are times that test
humanity and challenge the soul of a community or a nation. News images and
headlines tell stories of rising waters, quaking ground and tragic acts by man
himself. But the real story, the human story, is found in the lives changed
forever, in the strength of the survivors, and the resilient hope that gives
them the courage to recover.
On TUESDAY, MAY 9 (8:00-10:00 p.m., ET), ABC
will bring such a story to television in a two-hour original movie. ?Fatal
Contact: Bird Flu in America? follows an outbreak of an Avian Flu from its
origins in a Hong Kong market through its mutation into a virus transmittable
from human to human around the world. The meticulously researched film stars Joely
Richardson (?Nip/Tuck?), Stacy Keach (?Prison Break,? ?Blackbeard?), Ann Cusack
(?Grey?s Anatomy,? ?Ghost Whisperer?), Justina Machado (?Six Feet Under?), Scott
Cohen (?Street Time,? ?Law & Order: Trial by Jury?) and David Ramsey (?All
of Us?).
John M. Barry, Distinguished
Visiting Scholar at Tulane University and writer of the New York Times
bestseller, ?The Great Influenza: The Story of the Deadliest Pandemic in
History,? served as a consultant on the project. Barry?s book, which includes a
new afterword on today?s Avian Flu, focuses on the 1918 Spanish Flu which
killed between 50-100 million people.
[Editors Note: The film deals with
the current threat of the Avian Flu virus (H5N1). Scientists continue to debate
the degree to which the virus can mutate and be easily passed among human
beings.]
The movie opens with an
American businessman flying to Hong Kong to
meet with his Asian manufacturers. After 11 meetings in three countries in six
days, he starts his return to Virginia.
But before he returns home, the Chinese government has informed the World
Health Organization that a new strain of the Avian Flu virus was discovered in
a local marketplace. Over 1.2 million infected birds were killed in an attempt
to eradicate this strain. Dr. Iris Varnack (Richardson) of the Epidemic Intelligence
Service receives an emergency summons to China, where she discovers these
efforts may have come too late. Despite the early warning, the H5N1 virus has mutated
into a version that can spread from human to human -- shown in eye-opening
detail whenever the microbes start to permeate the atmosphere ? across races,
nationalities, genders and ages.
The story is seen through the
eyes of other key characters, including Collin Reed (Keach), Secretary of
Health and Human Services, who is the primary go-between for Dr. Varnack with
the state and local leaders back in America; Denise Connolly (Cusack),
wife of the American businessman, as she deals with his illness and then helps
to support other infected people;
Governor Mike Newsome (Cohen)
of Virginia, who, upon learning of this deadly virus, puts his city in
quarantine and then breaks down the state into communities that can nurture
each other; Alma Ansen (Machado), a hospital nurse in New York City who
suddenly finds herself in the midst of escalating chaos working at a new and
hastily constructed flu facility; and Curtis Ansen (Ramsey), Alma?s husband in
the National Guard who was brought back to New York.
?Fatal Contact: Bird Flu in
America? is executive-produced by Diana Kerew (?Surrender Dorothy?) and Judith
Verno (?The Hunt for the BTK Killer?) for Sony Pictures Television. The movie was
written by Ron McGee (?Atomic Twister?) and directed by Richard Pearce (Academy
Award winner for ?Hearts and Minds,? Peabody Award winner for ?Nothing Sacred?).
ABC Media Relations: (West
Coast) Jonathan Hogan (818) 460-7016
(East Coast) Patrick Preblick (212) 456-7819
Sony Media Relations: Karen Barragan (310) 244-6467
-- ABC --
***************************************************************************************************************************************
Bird Flu: Facts and FearsThe cross-platform networks of NBC News examine Avian flu in special report on April 21-23NBC NewsUpdated: 9:26 a.m. ET April 20, 2006NBC News will take an unprecedented look at the Avian flu: its myths, its realities, and its potential threat to the country and the world? in a division wide series, kicking off with the "Today" show on Friday, April 21 and culminating in an hour-long look on "Dateline" on Sunday, April 23.
Beginning on "Today," on Friday, April 21, Katie Couric and Matt Lauer will have an in-depth look at what the government's response plan will be if bird flu indeed hits, how will it affect building closures, airports and major city centers. That evening, on "NBC Nightly News with Brian Williams," correspondent Tom Costello reports from Seattle, the city experts say could be one of the first places in the continental U.S. to see positive tests in birds. Coverage will include how Seattle is preparing for a possible outbreak, and what concerns, if any, it has about the Federal government's level of preparedness. Additional interviews will include Health and Human Services Secretary Michael Leavitt, who will discuss the Federal government's plan, and a conversation with Jeff Levi, who is with Trust for America's Health, and a critic of U.S. bird flu preparedness. Ann Curry will also appear on "Nightly News" to discuss her extensive reporting in Southeast Asia on the effects of bird flu. Weekend editions of both programs will take a look at bird flu as well.
On "Saturday Today," Dr. Anthony Fauci, the National Institute of Health's infectious disease expert, will walk through the steps every family should take in anticipation of, and in the event of a bird flu pandemic. He will lay out a preparedness plan for medications, food and family communication. On the weekend edition of "NBC Nightly News with John Seigenthaler," reports will focus on the business impact of bird flu, including how poultry producers and other companies will address and manage public concern about the safety of the food supply. Another report will focus on chicken farming in the United States. NBC NEWS SPECIAL REPORT ? Why worry? Experts explain? Skeptics warn against hype? Is your town ready?? Robert Bazell: Preparations long overdue? Ann Curry: Bird flu?s fear factor ? Interactive map: Track bird flu's spread? Migratory routes: Follow the birds? MSNBC.com: Bird Flu|What you need to know? On TV: Today, Nightly News, Dateline, MSNBC In an hour-long broadcast of "Dateline" to air on Sunday, April 23 (7:00 PM/ET), co-anchor Ann Curry takes an in-depth look at what would happen if a virus like the avian flu caused a pandemic.
For the special report, "Dateline" consults experts on the front lines from the Center for Biosecurity at the University of Pittsburgh, the Centers for Disease Control, the United Nations, the U.S. Department of Health and Human Services and the World Health Organization. In an effort to offer viewers an understanding of how a flu pandemic would affect their lives, the report illustrates how the virus could potentially enter and spread throughout cities in America and around the world, visualizing possible scenarios resulting from human contact.
On Friday, MSNBC will cover the issue with a variety of reports and with special guest Dr. Sue Bailey, MSNBC analyst and former Assistant Secretary of Defense for Health Affairs. The network will take a look at how a possible outbreak of bird flu would affect the U.S. poultry industry should it reach our shores and will also examine preparations underway throughout the U.S. and especially in Alaska, which is expected to be the first U.S. state to spot the disease. Dr. Bailey will appear on MSNBC throughout the day and will answer viewer questions submitted through MSNBC.com. She will also appear on "Hardball with Chris Matthews" (5 and 7 p.m. ET) to discuss the politics of the bird flu. MSNBC will continue to cover the issue over the weekend with additional reports and guests.
by dawgit
America is finally waking up to a problem that is at least three years in the making. And the first exposure for most Americans is from Hollywood, and psudoscience hype. Sad, Very Sad.
The Content Object Repository Discoveryand Registration/Resolution
Architecture is a mouthful, but it should be. It is a monumental
attempt to become the main DNS (so to speak) for digital learning
content. But don't let learning content turn you off, this
methodology is applicable to digital content of all kinds. Learn
more about it here.
Though it sounds like a villain from a comic book, SCORM: Shareable
Content Object Reference Model is "SCORM is a collection of standards
and specifications adapted from
multiple sources to provide a comprehensive suite of e-learning
capabilities that enable interoperability, accessibility and
reusability of Web-based learning content." Why is this important
to you? Government is one of the heaviest producers/users of
training/information material. Read more here on why your training material should be SCORM compliant.
Is it just me, or do you also think that we won't get decent technology
legislation until our government representatives average younger than
60 years old? Or will politics remain the same? Who
knows. In the mean time, read about how the net neutrality bill failed to gain any critical mass.
I just spent three days at a conference in which 70 people
spent time listening, learning and talking about digital object repositories,
methods for naming and identifying these digital objects amongst shared
repositories, and methodologies for insuring quality of these digital objects.
The information and discussion was interesting, thought-provoking
and inspiring. The technologies we talked about, and the uses for those
technologies, were truly fraught with potential. However, at the end of the
three days, the discussion ended not with detailed hardware or software
requirements, the endorsement of one or more software packages, or even plans
for implementation. The end discussion focused (and rightly so) on how to sell
the idea and whether or not the idea was a good fit for your organization. For
this group realized that despite all the potential (and indeed there was much
potential in what we discussed) everyone knew that "if you build it, they
will come" is truly a misnomer.
In fact, too many times, people fail to realize that even
when you build something technologically fantastic, rarely will it be embraced with
the same level of enthusiasm as its builders.
I do not know of a single IT professional who has not at
some point in his or her career stood proudly by a technology achievement and
watch it get ignored by the user base it was intended for. This applies to all
aspects of IT, from infrastructure, to support, to development.
What happened? There are a hundred other reasons that new
implementations go wrong, including a lack of buy in at the proper level,
improper change management, failure to meet the intended need, the product too
late to satisfy the need, or the product was ahead of its time.
Like it or not, as cool as we think technology is (and we do
think it is cool, or we wouldn?t be in this field)--unless you are in the
business of research and design (which few of us are)--the key to the
successful use of technology is in how it is presented and sold to the end
user. Technology is simply a tool, and even though you and I know that using a
screwdriver to drive in a screw works better than a hammer, as long as the end
user of the tool is satisfied with the hammer, your technologically brilliant
screwdriver doesn?t stand a chance.
This can really frustrate us to no end, because it is
absolutely clear to us that what we created is exactly what "they"
need, and they are just too dumb to see it ? right? I mean, come on, you have
to be braindead not to appreciate our magnificent contribution. Sheesh!
In many cases, you DO know better than the end user what is
needed, but then again, sometimes you don?t. What matters is that for any
technology solution, someone in the organization has got to feel strongly
enough about the solution to want it and want others to share it with. If you
do not get the buy-in, forget about it.
This buy-in usually has to come at multiple levels, from
those that can command change, to those that control change (not often the same
people) to those who are affected by the change.
That is why your best IT managers and analysts are often
good sales people and more often than not, they did not start out in IT, but
from within the business. For while our dedicated and hard-working IT staff work
behind the scenes to make the "IT miracles" happen, it is those who
understand the business and--perhaps more importantly--the politics of the
business, that can make things happen in the organization.
To make significant contributions in the organization, you
need to pair great IT ideas with the right people to sell those ideas to the
other users. Without this pairing, you are depending on pure luck.
Mind you, this is to some degree an oversimplification of
the successful technology adoption/implementation process, because we know
there is a huge amount of work that goes into it. But, at the end of the day,
lack of buy-in can kill you.
So what does this mean for you? It means that buy in is so
important to the process that it must be worked on before, during, and after a
technology project, and that giving it short shrift can get you in a TON of
trouble. If you don?t have a marketing plan for your project (often tied in
with your change management plan), you had better get one. Don?t assume that
just because you have top management?s approval and/or funding that it is
smooth sailing from that point on--your marketing effort to users has just
begun.
For those of you who are the designers, developers, and
architects out there, know that much of your success or failure for your work
hinges not only on the quality of your work but how it is being presented to
your user base. IT managers should understand that just having your staff
produce technically competent work is not the extent of IT management. It?s a
partnership, guys and gals, and the more often we remind ourselves of that
fact, the more successful we will be.
by justin james
The day I can convince the people in my organization to give their files names more meaningful than "temp file 3.doc" is the day that users will start using anything that is not 99.99% automated for them. Heck, I have users that are still dropping files all over C:\ despite the fact that their apps default to My Documents just because that is what they are used to! This is why I am so down on so many "cool" projects. Anything that is not so intuitive that it requires zero training, zero selling, and zero effort simply will not get used. It is really sad, but really true.
J.Ja
by gcostigan
I have found that my best success in getting buy-in is by having my technology people involved at the beginning of any project or program. They start out at the same time with the other people and resources I bring together. The projects that I have worked on where technical resources weren't brought in at the start, or consulted late in the process, is where I have had buy-in problems.
I also work very hard to get people in IT who are problem solvers first. I or the rest of my staff can teach them the technology to help solve our customers' problems.
I am a new project manager. I have been successful in promoting the development of communication plans during project initiation. I've gotten buy-in to the idea that there needs to be as much attention put into the planning of informing the end-users about the new and cool tool (integration) as there is in rolling it out (implementation). I've been mildly successful at getting the project teams to document their communication plan but, we still have a long way to go when it comes to actually executing the plan ("Com'on, people, writing it down isn't the same as doing it." -sigh-. But, they are WRITING IT DOWN (sometimes)....so I have hope. There's hope.
If you Google the term data
dictionary, you will get nearly a hundred or more results of definitions
that generally mean the same thing. A data dictionary is data about data. It is
what defines the items in your database/s and can be looked to for definitions,
structures, use, allowable content, and sometimes business rules associated
with the data. It is THE roadmap to data in your database.
I was recently asked the question: Does the ROI on the data
dictionary that my organization religiously maintains justify its cost? I
answered with a resounding yes! Then I thought, why would anyone ask that
question? After all, aren?t the inherent benefits of a well-thought out and
maintained data dictionary obvious to all? Perhaps not if the question is being
raised.
Having spent a number of years of my career on the
database/applications development side of the house, a data dictionary has
significant meaning to me. Not only do I know what it is, but I know how
important it is to an organization and how difficult life can be without one
when you need to combine data from multiple sources.
Based on the above, you might conclude that a data
dictionary:
Is common sense
Is important
Is worth the effort to create and maintain
Is part of every organization
Based on these assumptions, you might be surprised at how
many organizations do not have data dictionaries, do not staff a dedicated data
administration/metadata management team, do not update existing ones (they were
created at the time an application was built), or depend on the knowledge of
one or more individuals to maintain this information about the data in their
heads as institutional knowledge.
So what?s the big deal with data dictionaries if so many
organizations forgo them?
The big deal is the value that they bring when you have to
share data, whether internally or across organizations. Having one makes life
so much easier, while not having one can result in chaos and misinformation.
Imagine this situation: Organization O has three
departments. The role of organization O is to collect information about Air
Quality so that it can make rulings, set standards, and influence legislation
concerning the quality of air in the environment. Department A in the
organization is responsible for monitoring outdoor air quality. Department B is
responsible for monitoring air quality in indoor environments, while Department
C is responsible for monitoring air quality underground, such as in mines and
sewers.
Each department is made up of brilliant scientists who are
extremely familiar with the chemistry of air. All the scientists are not
necessarily from the same disciplines, but all KNOW air. Now these scientists
begin to construct spreadsheets and databases to capture and manipulate data
about air quality. What do you think the odds are that in each and every
spreadsheet and database that is created, the terminology used to name the
fields is the same? Probably moderately high. Now what are the odds that these fields
with the same names across databases are defined the same and capture data in
the same way? That?s right ? pretty low. Now, try to combine the data from the
disparate databases in the three departments into a data warehouse or central
repository so that you can do statistics using a larger data set, and boy, do
you have trouble (and a lot of work on your hands).
Unfortunately, many of us are not fortunate enough to be in
an organization at the time that these databases are first developed, and so we
can't step in with good data administration practices in time to prevent such messes
from happening. In fact, many of us get brought in to deal with the train wreck
of disparate data sources under the guise of creating a data warehouse or
having to define the data to be used in a service as part of a SOA effort.
The good news is that it is never too late to create AND
MAINTAIN data dictionaries--with standards, administrative policies, and
procedures governing data. The bad news is that it takes a considerable amount
of time and effort to create them "after the fact," particularly when
it is long after the fact and the people who actually know what the data was
intended to mean have left the organization. However, the effort always pays
for itself OVER TIME. Creating data dictionaries will not boost profits overnight,
nor will they suddenly allow you to do more with less or make your company 100
percent more efficient. But by working steadily on the project, you will aid in
decision-making in your organization by improving the quality of the data and
exposing the data to its users (because they now know where it is and what it
means), thus putting your organization in the position to build top quality data
warehouses or SOA services.
All of these goals are worthwhile and can add to
the bottom line by helping you work smarter and faster. But how do you measure
this as ROI? That?s difficult, because many of the benefits are either hard to
measure, are intangible, or have to be measured over very long period of time.
Yet despite all this, it just makes good sense strategically for an
organization, and strategic ROI is measured over a period of many years.
So going back to the question that started this article ?
yes, by golly, it is worth it! Can I measure it in terms of ROI well enough to
convince someone stuck on pure numbers that they should give the project a go? Maybe
not (lots of intangibles there), but I feel confident that I can argue the
point that every penny spent on building and maintaining an accurate data
dictionary is well spent. Don?t believe me? Ask the poor guy working on the
"new" data warehouse for a company that doesn?t have one. He will
tell you how much not having one is costing you.
by justin james
Sadly, if I were to spend time writing documentation in many of the organizations that I have been in, the response would have been "we pay you to program (or admin or network), not to write stuff." Most IT workers do not have nearly enough hours in our day. I know I don't. My to-do list (some of it rather important) contains items back to January. I just hope I get a chance to configure M.O.M. (I installed it three months ago) before a server goes down. If I do not have the time to even do my job, where is the time to document going to come from?
J.Ja
by putchavn1
Insert comment text here
The Need is Acute---ROI is Real.
The phrase "Data Dictionary" is too specific to Structured Systems Analysis and Design Methodology but the sense in which it is used in the article is "Repository of Terms" "Knowledge Base", "Knowledge Repository", "Corporate Memory" etc. The need for it is in deed acute. Organizations pay for it by wasting time and resources, redoing or making do with incorrect / incomplete information. If all that is properly accounted for, ROI can be calculated and seen to be significant.
.
by whistl3r
"After all, aren?t the inherent benefits of a well-thought out and
maintained data dictionary obvious to all? Perhaps not if the question is being
raised."
The question could go in both directions. Some Professionals prob for alternate methods or better yet inquire about your Professional influences.
Either way, I found this a good read.
Maybe the more meaningful way to look at the financial value of a data warehouse is to try and calculate the "cost avoidance" of the exta staff time necessary to operatate without this resource.
Bubba
by kmurray
Not only the extra cost of lost user productivity, but also the high cost of doing this work *over* when the application needs to be re-developed! How many upgrade projects have I worked on that have no documentation at all, let alone a data dictionary! If the proper documentation were in place, when changes and re-development need to occur (as they inevitably do), programmer and analyst cost would be cut in half because they could focus on the re-work instead of the "old-work"!
by wayne m.
You can pay me now, or not pay me later.
I have come to believe the opposite. The time and effort in creating data dictionaries (and other documentation) does not provide ROI. The problem is creating a maintaining a data dictionary is a predictive effort. One ends up trageting as wide a range as possible to cover the part that may be needed in the future. Does the wide scope of documenting and maintaining everything really offset the cost of the narrow scope of reverse engineering a specific detail?
For an initial development, the cost of creating an enterprise wide data dictionary prior to creating the first database is simply overwhelming. The scope of the effort needs to be restricted to the task at hand. Will items have to be modified in the future to interoperate with other systems? Yes, but these interactions cannot be predicted, they must be discovered.
For existing systems, development tool sets often supercede the need for written documentation. Maintenance workers do not go back to the master documents, they look at the existing system. When changes are to be applied, the changes can only be evaluated on the current implementation; the details that are critical are typically lost when generalized to create documentation. This creates a duplicate effort situation. The change must be applied to the system and also applied to the documentation. Despite best efforts by the staff, entering the same information in two different formats will create discrepencies and the system is always correct.
Re-implementing an existing system is always a risky task. The risk is only increased by a team that relies on documentation rather than an understanding of the system to be replaced. The problems with the replacement system are rarely due to the definitions of the database, rather they are due to differing operational characteristics.
Data dictionaries and other forms of documentation are time consuming to create and do not alleviate the need to reverse engineer a problem nor a replacement system. The key information is readily available from development tools and this is the primary source of information used by developers. The documentation merely creates an aura of understanding for those not directly involved with the development effort and documentation is an innefficient means to create that aura.
by bfilmfan
Encourage your employees not to document, as the high paid consultants earn big bucks from doing it.
Keep a consultant employed!
Sort by Trending