Development


Since our start in 1988, V-Teknik has done around 50 projects with varying success. The finished products almost always contains programmable components (microprocessors) and a user interface, often consisting of a text-based monitor and custom-made actuators, i.e. joystick. The scope of the project from first contact to tested prototypes is within 2-12 months most of the time.


Below is a short example describing a typical project for V-Teknik.

Defining the problem and requirements
What most of our clients have in common is that they lack detailed knowledge about electronics. More often than not the client has recognised that they need a control system, but they havent thought about any specific details. In other words, defining the problem is rarely done with a list of requirements so our first mission is to get familiar with the task. Often this involves a newly constructed machine in need of an electronic system. This is often done with the client. A typical case involves 5-50 to/from outputs (i.e. valves) and 1-10 analog outputs for motorcontrol or flows. In-signals are generated by the system itself (i.e. RPM-sensor), or by an operator with a joystick and such. Some form of text-based operatorconsole is almost always neccessary so that the operator can get and set numerical values (in the form of text). On top of all this variables have to be saved even when power is cut, in some sort of memory. The list of requirements is often written by us in collaboration with the client and is improved upon during all of the development cycle.


Solutions
The next step is that we (V-Teknik) presents a solution to the specified problem. Practically all of our solutions involve custom software, and sometimes newly designed hardware. Discussions are reguraly held with the client about different options, particulary cost. After this, the decision is made to either continue with the project or abandon it. Price and delivery-options are also discussed.

Prototypes and testing
Sometimes existing hardware can be used for all of the project, and sometimes only partly re-used. In the latter case, un-optimized modules can be used for construction of the prototype, so testing can start as soon as possible.


Productizing and delivery
After the tests are done, we (V-Teknik) and the client discuss possible modifications needed for serial-production, how the product is to be delivered, what cables, instructions and such are included, and if any special actions need to be take to make assembly as easy as possible (i.e. pre-programming of various variables). Delivery, reparation and storage of spare parts is agreed upon.

Production
Normally we produce both the hardware and software. Mechanical parts, cables and sensors are sometimes produced by a third party, or the client if it is deemed profitable.


Maintenance and modifications
More often than not the right for the client to modify the product within the specification exists. From experience, we know that modificaions beyond this is often desired. These can be done with either perpetual payment or with a fixed price.

Manuals and documentation
V-Teknik delivers documentation, assembly-instructions and a troubleshooting-guide with the system, depending on what the client needs. Because the system being intergrated in another machine most of the time, the client uses these provided documents to use in the final documentationm which will cover more than just the control system.


Ownership and copyright
For the purpose of explaining we can think of the product consisting of the following:
1. Decals and other exterior design.
2. Custom software (i.e. menus, menutexts, graphical symbols)
3. Design of base hardware (i.e. PCB, regulators, keypads)
4. Base software (i.e. Operating System, rules, drivers).

Parts 1 and 2 can be the property of the client, but parts 3 and 4 normally remains in the hands of V-Teknik. The client can use 3 and 4 in the delivered product free of charge. If the client wants to produce hard- and/or software some other place, this can be negotiated.