Donald Carroll asked:




My name is Donald Carroll. I am the President and Webmaster of Green Planet Fantasy Theater. How did I get here? I have over ten years of work experience in the field of Information Technology (IT). I also have five years of teaching experience as an instructor in both Microsoft and Cisco technologies as well as other networking technologies such as Novell Netware, Unix, and Linux. I am twice certified by Microsoft as a Microsoft Certified Systems Engineer (MCSE), and twice certified by Cisco Systems as a Cisco Certified Network Associate, or CCNA?

The field of Information Technology has been very good to me and is an excellent trade to get into for those of you looking at entering a career or changing careers. As a former instructor, I can tell you that as a prerequisite you must be at least comfortable with using computers; better if you have a knack for fixing them when they break! Those of you who are very familiar with using, repairing, and even building computers are perfectly cut out for the lucrative field of Information Technology.

The purpose of this article is to help you in getting started on the path towards earning your industry standard certifications in the field of Information Technology while also gaining hands on practical experience with computer networks. I will tell you on the next page exactly what to do if you are interested in entering the field of Information Technology, even if you have no experience whatsoever. In the field of Information Technology, it is often not enough to just earn your certifications as employers generally favor IT professionals with work experience.

I will also share with you more about my own background and how it helped me to enter the field of Information Technology.

In the early 1990’s I was working as an administrative assistant, and as part of my duties I learned how to use a number of different computer programs; common business applications including word editors, spreadsheet programs, and databases. After my stay as an administrative assistant, and while I was seeking new and interesting employment opportunities, I sent away for a PC (Personal Computer) home study course, mostly because it came with a PC! I learned computer hardware, and computer software, including operating systems such as Microsoft DOS and Windows version 3.1. (Learning computer hardware and computer software, including operating systems such as Microsoft Windows XP and Microsoft Windows Vista is the first step in training for a career in Information Technology. I will explain more about this on the next page.)

I was also able to connect to the Internet using a modem; at that time, the only real Internet choices there were was “GopherNet”, and the America Online Network. (“GopherNet”, which is still in existence today, allows you to view folders and files on a remote computer, not web pages. The America Online Network has merely changed over the years.) Besides then connecting to a rather bleak Internet, in comparison with today’s Internet, you could connect to what were called “BBS’s”, or electronic bulletin boards. These “sites” allowed you to chat, play online games, and both upload and download content. ( I would have to check to see if any “BBS’s” are still in existence today!)

In 1997 I relocated to the Silicon Valley (San Jose, California), and I began applying around for administrative assistant positions. One recruiter pointed out that I “had a list of computer skills a mile long” between having learned a number of business applications, and having also completed a two year home study course as a PC Specialist. I was offered a high paying short term contract to provide computer support for employees at NEC Computers. I was basically an apprentice to what I would call a “guru” in terms of computer and computer networking skills.

I also entered college again to earn an Associate of Science/Information Systems Degree. After my contract at NEC Computers ended I applied at Honeywell Automated and Industrial Controls, and I accepted a position as a hardware technician. At this point now in my life I was pursuing a second degree in Information Technology, and working in the field of Information Technology, developing on the job skills critical to become a real expert. (At that time, the field of Information Technology was called Management Information Systems (MIS). Later it was changed to Information Specialist (IS), and today it is known as Information Technology (IT)).

That was the beginning for me. I soon continued on to teach networking technologies, and I accepted senior engineering positions with a number of different companies and corporations. I WAS EARNING WAGES and BENEFITS PACKAGES I HAD NEVER DREAMED OF!!! I essentially climbed the ladder from working as a computer hardware technician to working as an instructor, a network engineer, a senior network engineer, and finally as a consultant! Today I work as a contractor and as a webmaster.

If you would like to enter the field of Information Technology yourself PLEASE CONTINUE READING!!! I have myself graduated over four hundred computer networking students, and I can teach you how to learn computer hardware and software, and computer networking. I will tell you what course books to study and how and what certification tests to prepare for.

The field of Information Technology is not about computer programming, or application development; this field is all about the designing, building, maintaining, troubleshooting and repairing both the computers and the computer networks that companies use to store and use their data. In considering computers, there is the computer hardware; the disk drives, cd-rom drives, memory, motherboard, processors, power supplies, mice, keyboards, and other parts and peripherals. There is also the computer software; namely, the operating system, like Microsoft Windows XP or Microsoft Windows Vista, and computer applications or programs, such as Microsoft Office or Adobe Acrobat Reader.

When one or more computers are connected together to form a computer network they are connected using network devices such as hubs, switches, routers, and other network devices. In the field of Information Technology some IT Specialists prefer to work on computer hardware and computer software, and special computers used in a computer network called network servers. Other IT Specialists prefer to work more with network switches, network routers, and other telephone and telecommunications equipment.

If you would prefer to work with networking devices more than with computer hardware, computer software, and servers, you might want to pursue getting certified as a Cisco Certified Network Associate, or CCNA. (The CCNA certification is either one or two exams; you have a choice of taking it as either one or two exams depending upon your preference.) Your duties as a CCNA would revolve more around configuring and troubleshooting network routers and switches, and working with leased line providers and telecommunications equipment. Cisco Systems also offers other more advanced routing certifications beyond the CCNA, namely the Cisco Certified Network Professional, or CCNP, and the Cisco Certified Internetwork Expert, or CCIE.

If you would prefer to work on computers; installing and fixing computer hardware and computer software, and administering network servers and network databases and applications, you might be interested in pursuing first the A+ certification followed by the Microsoft Certified Systems Engineer, or MCSE certification. (The A+ certification exam is given as either one or two exams; one exam is based on computer hardware and the other exam covers special software known to IT Specialists as operating systems. The Microsoft Certified Systems Engineer, or MCSE, is awarded upon the successful completion of seven individual exams.)

Many IT professionals maintain proficiency in computer hardware, software, network servers, and computer networking devices such as routers and switches. Many employers demand that their IT staff be able to help employees with simple computer problems while also being able to solve complex network problems on network routers, switches, and even firewall systems. Many positions in the field of Information Technology require an A+ certification, an MCSE, and a CCNA. Other positions require only one of these certifications, plus or many any of a number of other industry standard certifications.



Unless you decide to pursue the Cisco Certified Network Associate, or CCNA certification, you will probably want to begin learning the ins and outs of a single computer before studying computer networking technologies. You can purchase the textbooks for the A+ certification, the MCSE certification, and the CCNA certification at almost any book retailer.

Focus first on the A+ exam material before proceeding to the MCSE exam material and/or the CCNA exam material – this is best if you are an absolute novice. It is also a good idea to set up a small computer network at home to practice with – hands on experience with these technologies is essential to success! It is also a good idea to attend a technical school to learn the basics of networking technologies, but you can study and become proficient with these technologies on your own just as well.

With your A+ certification behind you, you can work as a PC technician, or even as a Help Desk Specialist (helping employees with their hardware, software, and basic network problems.) While pursuing your MCSE and or CCNA, you can apply for positions as a junior systems administrator, network administrator, and even a junior network engineer.

Study your exam materials, setup your own home network that you can use to practice on, and by all means try to meet people who work as IT Specialists so that you can learn more about working in the field of Information Technology. Maybe you can spend a day at work with them working for free as an apprentice? (Companies usually do not mind extra help for free!)

Create a sharp resume’ listing your certifications and/or technical school degrees, and your work experience…if you do not have any work experience, try to get some working with an IT Specialist. Though certifications are important, most employers prefer work experience. Some job interviews have a required technical interview where you are tested on your fundamental knowledge and your ability to troubleshoot and resolve computer and computer network problems.

Once you have passed you A+ certification exams you can begin applying to work as a computer technician (hardware and/or software technician.) From there you can continue your studies in networking, earn your MCSE and/or CCNA, CCNP, or CCIE, and become a network engineer, a senior network engineer, a contractor, or even work as a consultant.

Good luck to you…if you have any questions about the field of Information Technology please feel free to contact Donald Carroll at Green Planet Fantasy Theater.

(For more great “how to” articles, plus DVD Movies, Music Collections, PC, XBox, Wii, Sony Playstation and Nintendo Games, Software, E-Books, Audio Books, and Adult *** Material FREE, visit Green Planet Fantasy Theater online at ww.myplanetfantasy.com.)



Caffeinated Content – Members-Only Content for WordPress

Julie Lavallee asked:


Shrinking product development cycles coupled with demanding product requirements and increasingly complex design implementations can overwhelm a design team. The technical risk of employing new, complex, high-speed processor technology can often deter a design group from incorporating new technology in their product designs.

Intel Corporation’s ATOM processor and low power chipset solution is a technology choice which cannot be overlooked. With the potential for wide application in deeply embedded, low power, fanless industrial, medical, communications, automotive and consumer applications this technology demands attention.

Orchid Technologies, a developer of custom electronics product solutions, can help. With their new ATOM processor technology core design, that combines your custom electronic hardware with an ATOM processor core. The result is a highly integrated circuit board solution customized for your applications needs.

“The development time and risk are low, because Orchid has done much of these designs before,” says Paul Nickelsberg, President and Senior Engineer of Orchid. “Your custom design builds on our firm foundation of design success.” “Orchid has designed many highly customized Intel-processor-based (IA32) circuit boards.”

A typical Orchid Technologies’ client in the fanless industrial space may require customized GPIO; perhaps special data logging features: possibly specialized precision analog electronics; or maybe the integration of a specialized DSP front end. Orchid Technologies can skillfully combine clients’ specialized electronic circuitry with our existing ATOM core design to create a cost-effective, highly integrated, design solution. Add Orchid’s ability to customize BIOS to the mix and the result is an optimized IA32 solution tuned specifically to client needs.

Orchid Technologies has had a highly successful IA32 design track record. Among the many highly embedded IA32 circuit board designs we have performed include:

Comverse’s Series IV Telecommunications Processor.

This Pentium-based product built on Orchid’s IA32 Processor Core Design, interfaces to sixteen Texas Instruments DSP devices, a dual port memory interface, and T1/E1 WAN networks.

Dialogic Corporation’s Private Branch Exchange Processor.

This Pentium-based product built on Orchid’s IA32 Processor Core Design, is coupled to a Texas Instruments based DSP Soft Modem, Solid State Disk Drive, and Telephony Line interfaces.

Chemical Controls Interface Processor.

This Pentium-based product built on Orchid’s IA32 Processor Core Design, mixed our client’s old grandfathered controls-technology with today’s modern laser communications solutions. In this design, we preserved the best elements of our client’s obsolete existing design while modernizing its features and extending product life another ten years.

As electronics technology, continues to evolve the requirements for high-speed devices, tighter integration, enhanced functionality, and low power pose design challenges for any product development team. Visit Orchid Technologies website www.orchid-tech.com and discover for yourself why design teams rely on Orchid for their product development needs.

In this article OTEC, Orchid, and Orchid Technologies refers to Orchid Engineering and Consulting, Inc. The Orchid Technologies logo is a trademark of Orchid Technologies Engineering and Consulting, Inc. All other trademarks are the property of their respective owners. Copyright 2008 Orchid Technologies Engineering and Consulting, Inc. All rights reserved.



Caffeinated Content

Timothy Nuckles asked:


Commercial buyers of information technology products and services are locked into a self-defeating pattern of behavior when it comes to negotiating contract terms and conditions with technology vendors, and it is time to move on to a better approach. Better technology vendor negotiations produce better contracts for a technology project, and better contracts produce better project outcomes. So, break the mold and move on to a better way of negotiating contract terms and conditions for your next technology project.

Vendor Contracts – Timing Is Everything

Let us assume that by now you have done a lot of planning and information gathering for your proposed technology project, you have completed a vendor selection process, and now it is time to document your deal with your chosen vendor.

At this stage in the technology procurement process, the most common practice—indeed the almost-universal practice—is to distribute the vendor’s proposed contracts to your project team for review and comment. Then, as if by instinct, everyone starts looking for vendor bias in the contracts. No one has been given this specific directive. You simply assume and expect that everyone knows the drill. Folks on your project team begin striking certain biased provisions and scribbling notes about amending others. For sure, removing or limiting vendor bias in the contracts is a worthwhile exercise, but now is not the time to perform this exercise.

Light bulb on

I had to get several technology deals under my belt before I realized this, but at this early stage of the contracting process, you really need to focus first on terms and conditions that are important to you, not the terms and conditions that are important to your vendor. We know your vendor has included in its specimen contracts (as modified prior to presentation to you) all the terms and conditions of your deal that are important to your vendor. In fact, they are very easy to identify. They are all the contract terms with vendor bias. These provisions are so important to your vendor that it has purposely added bias to them, often with obvious exaggeration and redundancy. Even if your vendor has to bargain down somewhat from these provisions, your vendor is still in a safe position because the starting point was so extreme.

What you should do instead

At this initial stage of contracting, you should ignore your vendor’s proposed contracts. Simply set them aside for the time being, and do this for two reasons.

First, in order to express in writing the terms and conditions that are most important to you, you must actually think of what those terms and conditions might be. Likeable as your vendor may be, your vendor will not have already added to its proposed contracts the terms and conditions most important to you for your particular project. You will have to come up with this stuff on your own.

Second, until you know what terms and conditions are most important to you

for your particular project, you are in no position to challenge your vendor’s biased provisions except in attempt to remove or limit the bias. “I don’t know exactly what impact this provision has on our project, but I know it’s not a provision that helps our cause.” Challenging these provisions in a vacuum does not really help you.

The big picture

Now is the time to start with a fresh, big-picture perspective, and then fill in lots of detail. Circle back to earlier stages of your procurement process and revisit your decisions, your assumptions, and the various things you have learned. As a result of your many meetings and discussions, there may be things that you are now taking for granted: special vendor qualifications, how a particular piece of your project will be orchestrated, acutely risky aspects of your project, and so on. Bring to mind other similar projects within your organization and apply what you learned from those experiences.

Re-acquainting yourself with prior thought processes, discoveries, assumptions, and experiences will help you remember aspects of your project that you previously deemed important—whether because they are critical to project success, they pose a substantial risk within your project, or perhaps both—and it will force you to consider the importance of other elements for the first time. This process will help you build out the terms and conditions for your deal that benefit and protect you, terms and conditions that maximize the probability of project success and minimize project risk.

As part of this process, make a detailed list of list of terms and conditions that are important for your particular project, and:

1) Categorize them by subject matter.

For example, requirements development and prioritization, data mapping, business process issues, software development, application integration, database integration, system integration, testing, implementation, buyer protections, vendor management tools, warranties, etc. When you get around to negotiating the items on your list with your vendor, your project team will have important reference points. “Does this contract item touch implementation? If so, let’s look at our implementation items.”

2) Add qualifiers for each item.

Among other things, qualifiers can include a ranking of particular item’s relative importance within your project (critical to project success, represents substantial risk, wish list, etc.). When you get around to negotiating the items on your list with your vendor, your project team will be less inclined to treat all items on your list as equally important. Almost certainly, not all will be equally important. Your team will have a sense of how hard to push on a particular item, and in terms of the give and take that occurs in any negotiation process, they will have sense of what items to compromise (and by how much) or concede outright if met by strong resistance from your vendor.

3) Add relevant notes and comments for each item.

Among other things, relevant notes to attach to your list items include comments about accountability. Who within your project will be accountable for accomplishing the particular item: your vendor, your internal staff, or some combination? And what should happen if the party with accountability drops the ball?

With this kind of list in hand, you are in a much better position to review your vendor’s proposed contracts. Perhaps most important, you are no longer reviewing the contracts in a vacuum. You are equipped to conduct a truly meaningful review of your vendor’s proposed contracts.

Is there a gap in the vendor’s proposed contracts; that is, an item from your list has not been addressed at all? Is there an inaccuracy in the vendor’s proposed contracts; that is, an item is addressed, but its present treatment does not match your understanding, preference or requirement? Are topics within the contracts miscategorized? Are interrelated items not treated as such? Are accountabilities not clearly established?

An even better approach

Although breaking the mold and adopting the above approach to technology vendor contracting will certainly help you produce better contracts for your next technology project, which contracts should facilitate a better project outcome, there is a way to help yourself even further.

Instead of starting with and working from your vendors’ proposed contracts for your next project, think about developing your own standard agreements to include within your technology procurement process (usually at the RFP stage).

First, develop a neutral or somewhat buyer-favorable Software License Agreement. Find a standard Software License Agreement and neutralize or remove the elements of vendor bias. Then add the buyer-side content that you would normally find yourself negotiating with a typical vendor (were you working from the vendor’s standard Software License Agreement). Next, find a standard Consulting Services Agreement and do the same thing.

You can add your newly-developed standard agreements to your next technology RFP and request that responding vendors either approve your standard agreements as-is, or cite alternative language for provisions they do not find acceptable.

By incorporating your standard agreements into your technology procurement process, you will achieve two important things. First, you will be able—probably for the first time—to evaluate vendor candidates based on one of the most important factors for project success, terms and conditions. You can guage a prospective vendors appetite for terms and conditions that are important to your for your particular project BEFORE you have selected a vendor. It is much harder to win favorable terms and conditions AFTER you have selected the vendor for your project. And second, you will greatly reduce negotiation cycle times.

More and more commercial information technology buyers—of all sizes—are using this approach. It may surprise you to learn that many reputable technology vendors will not only entertain the possibility of working from your standard agreements instead of theirs, they may even welcome the prospect because it saves them time and expense as well.

A word of caution

When you develop your own standard agreements, exercise some discipline. Do not convert a terribly vendor-biased agreement into a terribly buyer-biased agreement. This will not help your cause. Instead, shoot for balance. Software developers, for example, have to protect their rights in their intellectual property, and there a certain limits beyond which they will not venture; for example, an excessively broad license grant. Understand vendor limitations and be fair. Add buyer bias judiciously and only if it is truly important to your organization.

Meet Nuckles at www.NucklesLaw.com or visit the firm’s sister site at

Share and Enjoy:

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
•