Learn how we create and refine custom automation programs from gathering your requirements to testing and final delivery. This overview explains what to expect at each step of the development process.
1. Discovery & Requirements
Every project begins with understanding your needs.
Customers typically reach out with a specific instrument or group of models they want to automate. To get started, we’ll request:
- Documentation such as service manuals, GIDEP procedures, or internal test procedures.
- Information about the standards and test equipment used.
- Serial numbers for standards like a Fluke 5522A(for software licensing).
Once we have these details, we can prepare an accurate project quote.
2. Quoting & Planning
Quotes are based on:
- Estimated programming and driver development time. *A driver is code used to control each test equipment like a 34401A DMM or 53132A frequency counter.
- Availability of test equipment for development.
- Complexity of tests and documentation.
When new drivers are needed, we can supply a remotely accessible development laptop to support driver creation.
Most projects are quoted as fixed-price; however, very complex or highly specialized requests may be hourly.
For larger projects or newer customers, deposits may be required.
3. Development Phase
After approval, development begins.
- We typically start with developing drivers for the required instruments if needed.
- We begin developing all the required tests, instructional images, test points and tolerances into the program.
- Internal simulation testing is performed to catch typos, verify calculations, and ensure test results are produced correctly.
If the customer’s hardware isn’t immediately available, we proceed with simulation until live testing can be performed.
4. Testing & Refinement
Once a working version is ready:
- Once a working version is ready, an initial executable (v0.x) is delivered for live production testing.
- This stage marks the beginning of the refinement phase which is a normal part of the development process where we polish the program for everyday use.
- At this stage, bugs and minor issues are expected. They’re part of improving the software’s reliability and usability. During this phase, customers provide feedback on things like the order of tests, clarity of instructional images, and overall ease of use; all within the original scope of the project.
- The program is built to continue running even if some tests encounter errors, allowing all issues to be automatically logged for review and correction. This approach helps us identify and resolve multiple issues efficiently rather than one at a time.
- Because this is a collaborative stage, there will often be back-and-forth communication as feedback is reviewed and updates are provided.
- Major changes such as using different test equipment or adding new tests not included in the original scope, documentation or quote will require a separate quotation.
Typically, we iterate quickly during this stage as several revisions may be exchanged during the first week.
5. Final Delivery & Support
When the customer confirms functionality:
- The first production version of the program is released as version 1.0.
- Any special instructions and equipment requirements are produced inside the read-me file inside the programs main directory.
- Minor updates (e.g., adding/removing test points or supporting compatible models) are provided for up to 6 months.
- Regular customers receive extended flexibility.
If a project becomes inactive for several weeks without feedback, it may be paused and require a review fee before resuming.
6. PayPerCal Projects
For PayPerCal customers, project approval depends on how common the instrument is and customer qualification.
These projects have lower upfront costs but are limited to supported instruments and standardized frameworks.
Highly specialized models may require a full project quote instead.
For detailed information on client expectations (including beta review, payment terms, and timelines), please see our Development Terms page.