SYSTEM / 06
Software development & technology licensing
Define how the control software, equipment interfaces and technical documentation fit together.
Build for use. Document for handover.
Software and licensing projects need a clear description of both functionality and deliverables. For equipment control, data processing, utility software and technical implementation, BJLC scopes the functions, environment, interfaces and usage rights together.
What to clarify in the brief
| Functions and workflow | Users, workflow, inputs and outputs, error handling and required operational records. |
|---|---|
| Environment and interfaces | Operating system, equipment interface, protocol, deployment and dependencies. |
| Files and versions | Installer, interface documentation, configuration, source-code scope and version handover. |
| Rights and support | Licensee, usage scope, modification or redistribution conditions, maintenance and later changes. |
Define the deliverables
Software and deployment files
Deliver executable software, configuration and user documentation as agreed. Source-code delivery is defined separately within the scope.
Licensing and technical handover
Record the deliverables, usage rights, version and support scope, with a clear distinction between a demonstration and the contracted release.
Before you start
Can we discuss licensing without a development project?
Yes. Outline the technology, intended product, licensee and preferred licensing arrangement. The available scope and terms can then be reviewed.
Let’s define your next project.
Start with the application, existing equipment and critical interfaces.