Sunday, February 18, 2007

Session 7

Ed Norman Syndrome

Standardization is normally a great thing for efficiency. This was one of the reasons to outsource the operation and maintenance of our network, hardware and software to a civilian company. The standardization was supposed to level the field for every one and be able to bring up to par the technology available throughout the Marine Corps. However, reality happened. Every unit does not work the same. The implementation of the contract was put in place and units began changing to the new network, but now they did not have all the software programs they need to do their job. The process to run newly identified software in the new network was a lengthy one. The unit had to submit a request for service (RFS) and give a copy of the software and licensing proof to be tested as well as a military side Subject Matter Expert (SME) to participate in the testing. Test of the software had to be done in a lab to make sure that a particular software combination would not harm the already running network. This process took more than six months. This issue became very problematic. The old network, now called “legacy” network, was kept to run parallel to the new network to ensure those units could function.

When the outsourcing contract was signed, a software survey was done. Unfortunately, not everything was identified. Now we had to deal with the transition and run double networks until the transition was complete. At that time, I was in charge of the transition for one of our bases. The civilian representative for the company on my base and I, got together to figure what to do about the software applications coming up now. We worked out a one time deal. The military was going to collect all the applications not previously identified and put a deadline to have this done by. On their part, the civilian company would put a testing lab on our base and streamline all the applications identified by the deadline. This process would be done in approximately 30 days after the deadline.

Weekly Log
- Download and listen to Session 7 mp3
- Post response items
- Continue Working on Projects
- Read classmates blog postings
- Post comments on classmates blogs

7 comments:

Anonymous said...

Standardization can be a good thing, I agree but many times the standard part is usually the starting point. For instance, the standard could be that every computer has installed on it Internet Explorer, Firefox, Microsoft Office and Publisher; whereas beyond that standardization teachers can install personally needed programs like Photoshop for Photography or design software for yearbook, etc.

Linda Faulk said...

I think that you've identified the problem with standardization. It works great when we are all the same, but we are not. We all require different things to be successful, just as students do.

RFLORES said...

Hello Rosa,

Standarization is a good thing. Standarization helps to mainstream a more homogeneous technology environment. Standarization also makes things more manageable. As I stated in my blog page, too much or too little of something, in this instance standarization, is the key to things running the most efficient.

The trouble is that since we are discussing standarization as it applies to human beings, it only goes so far. Teachers also need a degree of flexibility to be able to implement and incorporate certain pieces of technology that may apply to their specific subjects. In such situations then, standarization no longer works efficiently as intended. Therefore, some flexibility needs to be in place to allow for those exceptions to the rule.

Davena Peters said...

Rosa,
You are always so articulate in your responses. Sounds like your Ed Norman is a real beuracracy and red tape nightmare, seems so odd when the intention is not ill willed though. You make a good point, as well as Jon. Maybe standards are about a starting point with customization occuring at the real end user side of things. A thing we like to call balance right?
Davena

Jennie O'Kelley said...

Hi Rosa,
I think keeping things organized and structured is good, but being as strict as Ed was, is crazy. I like your theory on the strandaization. We need something like that at my school. So many teachers have weird things downloaded onto theor computers, its funny :) Great post.

Michele said...

Standardization is a good starting point, however we are all so unique in our very own way, that in order for us to be successful, we all need different things.

Brian Newberry said...

Thanks for the real-world example of how things are run in other situations. It is true that standardization is helpful. In fact I like to see a standardized computing setup in schools. That standard is what is supported. I do like to allow teachers to install software (especially open source and free) because there are things that might need to be done that are outside of the standards.

Then, when the computer no longer works the IT department should be able to wheel it out and place a fresh system with the standard setup on it. The now-polluted system goes back to the workshop to have it's hard drive wiped and a fresh install of the standard setup placed back on it so that this computer can then be placed into another classroom as a replacement.

Key to this is centralized data storage. I'm curious, does the Marine Corps have server-based data storage or is each computer expected to be a data storage device?