Back to JKI Main Page
JK-Labs.com Site Map
Conracting: Ordering, Terms and Conditions
Contact JKI

©Copyright 1997-2010 
Johnson Kinetics, Inc.
All Rights Reserved
 

Pages best printed
in Landscape

 


 

 

Frequently Asked Questions ( FAQ's )

Below are common Q/A's, if there is a topic or question you may have, please contact us. 

Q1:  How do I specify a non-standard product or service in which I am interested ?
Q2:  Can I apply JKI technology or know-how to my product or application?
Q3:  Is it expensive to perform an R+D Effort?
Q4:  How "custom" are your custom products, does that mean it will take a long time?
Q5:  How can I import data or interface new products to my existing Hardware / Software?
Q6:  How can I get done a block of work without getting into extended developments or contracts?
Q7:  What versatility to I have in enclosure type and characteristics?
Q8:  Does JKI stock its products?




A1:  How do I specify a non-standard product or service in which I am interested?  The majority of our work comes from built-to-order items, typically with client-specified features and configurations.  Our engineers will work with you to help define and specify exactly what you want, we look forward to discussing your applications, environments, and goals.  Contact us today.

A2:  Can I apply JKI technology or know-how to my product or application?   In most cases, our Engineering Services clients will benefit from general know-how.  If, however, a specific need or desire would best be served by incorporation of a JKI priorative technology, we would work through these advantages with you.  If you would like to license all, part, or any combination of JKI know-how, software, technologies, inventions, we regularly review such applications for partial, limited, unlimited, and exclusive agreements. 

A3:  Is it expensive to perform an R+D Effort?   The scope and goals of any project typically defines what kind of effort ( i.e. how much ) is required.  JKI bids on jobs from very small to large, simple to complex.  A tight and detailed description of expectations, goals, and scope are agreed upon before R+D or other engineering services work begins, excluding any preliminary or feasibility reviews.  Periodic communication with the client are key to maintaining course and direction.

A4:  How "custom" are your custom products, does that mean it will take a long time?  Many custom projects can be built from existing platforms and modules, others require fresh designs and fabrications.  JKI has produced products and functional modules from design to demonstration in 4-6 weeks, others in 3-4 months. 

A5:  How can I get data to interface to my existing Hardware / Software?   As part of the specification for your system or device, communications and data path will be determined.  Analog, digital, serial, formatted, custom protocols can all be converted to suit exiting input syntaxes.  We will convert any controls or data paths to be compatible to your existing systems.

A6:  How can I get done a block of work without getting into extended developments or contracts?   JKI has offered Engineering Service Blocks as a way of limiting contract scope and term.  This is a great option for pre-investment review, feasibility analysis, and similar short term options. 

A7:  What versatility to I have in enclosure type and characteristics?  Most clients will use a standard metal or plastic enclosure for even customized products.  In the case where your applications demand special features, such as weight/size limits, high temperature exposure, waterproof, shock-proof, connector-less operation, or other requirements, JKI will happily present and discuss the possibilities with you.

A8:  Does JKI Stock its products?   JKI stocks only some of its standard products, but does stock all major systems components and sub-systems.  Most of our products are built to order because most systems and devices have at least one variation and custom selection.  JKI does stock some accessories, support items, components, and modules to decrease delivery latency. 
 
//