ISV Customer Story · Semiconductor Manufacturer
Incorporate independent licensing guidance into your software offering.
Your customers buy your software to improve their operations. They may also depend on you to understand how its implementation affects their existing technology environment—including licensing requirements they may never think to ask about.
For applications running on Oracle, a database design or configuration choice can introduce a separately licensed feature. The application may perform exactly as intended while creating a compliance gap for the customer.
Two incidents at a semiconductor manufacturer demonstrate why licensing guidance deserves a place in the software offering.
The manufacturer relied on third-party applications to support factory automation and manufacturing operations.
Software connecting production systems with automated transport and storage equipment. LicenseFortress identified nine application tables that appeared to have been created with Oracle Partitioning enabled. The manufacturer did not hold the required Partitioning licenses.
$336,720 recorded contractual exposure
Unlicensed Partitioning across three database instances in an environment associated with software that organizes production and equipment data to help manufacturers understand factory conditions and improve production flow.
$336,720 recorded contractual exposure
The two assessments should be considered individually; the records do not establish that the amounts are additive.
The licensing consequences of an application can extend beyond the application license itself.
A customer may have licensed Oracle Database without licensing every optional feature an application can use. An implementation, upgrade or configuration change can introduce usage outside those entitlements.
The end customer holds the Oracle agreement and remains responsible for its compliance. An application’s role in introducing the usage does not automatically transfer that responsibility to the application provider.
For an ISV, this creates a customer relationship issue as well as a technical consideration. An unexpected licensing requirement can complicate deployment decisions, prompt redesign work and undermine confidence in the overall cost of the solution.
LicenseFortress’ ISV program gives software providers a way to incorporate independent licensing expertise into their offering. Together, we can define a review that examines:
How the application will operate within the customer’s Oracle environment and which entitlements it assumes.
Whether proposed changes introduce additional database features or licensing requirements.
Whether application settings and database structures align with the customer’s licensed capabilities.
Depending on the engagement, that guidance can support implementation planning, customer discussions and decisions about alternative configurations. The objective is to identify licensing dependencies while the vendor and customer still have time to make informed choices.
Your team understands the application. Your customer understands its operational needs. LicenseFortress brings an independent licensing perspective to the decisions connecting the two.
Incorporating that expertise into your software offering helps customers understand the licensing implications of deployment—and helps your team address those questions before they become unexpected exposure.
Explore the ISV Program