These development terms explain what’s expected during a custom software development project with Domini Technologies.
They complement our main Terms of Use & Conditions page and outline how projects are quoted, built, and refined.
1. Information & Documentation
Before a project can begin, the customer must provide:
- The test documentation to be followed (e.g., service manuals, GIDEP procedures, or internal performance verification procedures).
- The make and model of the device under test (DUT) and all supporting test equipment.
- Any special testing requirements, configuration details, or setup notes.
Incomplete or missing documentation may delay project start or affect quoted timelines.
2. Quotation & Scope
Each project is quoted based on:
- The estimated time to develop all specified test routines and any required instrument drivers.
- The complexity of the test documentation.
- Equipment availability and required access.
Important: The quoted price covers only the scope described in the submitted documentation and approved quotation.
Major changes—such as using different test equipment, adding new tests, supporting special options, or requesting new features not listed in the quote—will require a separate quotation and may extend delivery time.
3. Equipment Access & Driver Development
If new drivers (code to control instruments) are required, Domini Technologies may rent out or loan a remotely accessible development laptop to the customer’s facility (loans for qualified accounts only).
This allows driver development to proceed without shipping equipment or interrupting customer operations.
4. Testing & Refinement
Once the first version (v0.x) is delivered:
- Bugs and issues are expected — this is the refinement stage where the program is polished.
- Customers should allow the software to complete all test runs, even if some tests fail, so all errors are logged and sent for review.
- Feedback during this stage is essential and may include improving test flow, adjusting instructional clarity, and refining ease of use — within the original project scope.
- Major functional or scope changes after this point require re-quotation.
5. Review & Approval Period
After the initial delivery:
- Customers are encouraged to review and provide feedback within 30 days, or up to 60 days for larger projects.
- The invoice is issued under NET30 terms unless otherwise agreed.
- Minor revisions within the approved scope are supported for up to 6 months after project acceptance.
Ongoing communication ensures timely adjustments and a smooth approval process. If testing or feedback stops for several weeks without notice, the project may be considered inactive, and a reactivation fee may apply.
6. Pay-Per-Cal Projects
For Pay-Per-Cal programs:
- Initial development costs are lower, but approval depends on the commonality of the instrument and customer qualification.
- Fringe or uncommon models may be limited to full project-based pricing.
7. Collaboration & Communication
Successful development relies on communication.
Customers are encouraged to provide clear feedback, test data, and screenshots where possible.
Regular updates help ensure the final product meets expectations within the quoted scope.
8. Final Delivery & Ongoing Support
Once a working version of the software has been delivered, the client is expected to remit payment according to the issued invoice, regardless of the current revision number.
Validation feedback and refinements may continue as part of the normal review process, but payment remains due for the delivered, functional version.
After final approval:
- The program is rebuilt as Rev 1.0, replacing earlier beta versions (e.g., v0.1, v0.2).
- Final files are delivered and licensed to the test equipment serial numbers provided during development.
- Licensing applies only to equipment owned and registered at the time of development. New or replacement equipment may require a separate license or quotation.
- Unless otherwise stated in writing, up to two licenses are included per project for qualified accounts.
9. Project Abandonment
If a project is inactive for more than two consecutive months without communication:
- It may be considered abandoned.
- Deposits may be forfeited, and additional review time may be billed if the project is later reactivated.