How does working with DatumProof start, and how is contact made?
The early-adoption program
| Item | Term |
|---|---|
| Target | One machine. One being designed now fits best. |
| Scope | Fixed in writing before work starts. |
| What the customer brings | The drawings and parts list of that machine, as far as they exist. |
| Confidentiality | Under NDA. Design data is treated as confidential. |
| Hardware | Not required. The platform works on the design. |
| Fee | Paid, quoted for the agreed scope; early programs are priced as reference work. After the program, the platform is licensed by subscription. |
How it runs: choose the machine and the outputs → build the first equipment model together with the customer’s designers → use the outputs on the real project → if it fits, the customer’s designers run the platform themselves from the next machine.
What is handed over: the equipment model, the I/O list and BOM, the safety interlock tables, the start-up procedure documents, and an issue log of what the model brought to light and what it could not decide. A program can also show that the platform does not fit a machine yet; if so, that is reported, with the reason.
Making contact
- Enquiry form: /contact/ (English) · /ja/contact/ (Japanese)
- Email: [email protected]
- Languages: English, Japanese, Korean
Not having decided what to ask for is a normal starting point. “Would this fit our machines?” and “Which machine should we start with?” are the most common enquiries.
At first contact
- An outline is enough: what kind of equipment, what takes longest in its design, preferred timing. None of it is required.
- Drawings, specifications, model numbers, source code and internal identifiers are not for this stage. They are discussed once an NDA is in place.
- Sending an enquiry does not create a contract, and a response time is not promised.
Human-readable versions: getting started · contact
Back to the question list.