Continued from CYA: Using Contracts to Protect Your Company.

Escrow: When purchasing software (especially from small vendors), make sure the source code is placed into escrow with a third party. This means that if the vendor goes bankrupt or out of business, you have the source code of the software to help support […]

CYA: Using Contracts to Protect Your Company

Software licensing and hardware contracts are a primary tool in protecting your company from vendors that you have purchased product from and do business with. In an ideal world, vendors work well with your companies representatives and when issues arise they are handled to meet both parties’ […]

This article is aimed at relating my experience in trying to reduce Oracle licensing costs, how they view contracts, and how to put yourself in the best position in relation to your licensing arrangement. I plan to explain more about the Oracle licensing model in future articles. In this article I will use […]

Continued from How Oracle Licensing Differs.

To help alleviate and prevent this situation, managers responsible for Oracle licensing should have a game plan on how to ensure their software compliance. They should get ahead of the game and make sure licensing issues are caught early before the company is already dependant on a platform build […]

As an IT manager, one of the activities you are most likely involved in is procuring software or hardware and maintaining the purchased hardware or software. A very important part of the procurement process is constructing, modifying, and negotiating the initial contract. The initial contract is vitally important as it defines the relationship […]

The Oracle licensing model differs from most other commercial (not open source) software vendors in one main regard. There is no activation key or other instrument for making sure that a license has been purchased before the software can be put into use. Other software products require a product key, activation code, etc […]