Wednesday, June 10, 2009

WaveRoute Enterprise unveiled at Sensors Expo.

Machine to Machine (M2M) communications is increasingly important to the success and viability of businesses today. Our WaveRoute products allow for devices and sensors to be connected and available for data communications. WaveRoute Enterprise is a hosted, web-based M2M application for managing, monitoring, and controlling these devices and sensors remotely. Easily add devices and receive data in under a few minutes, create powerful rules and alerts, and visually know what is happening anytime, anywhere.

If you are looking for a solution to bridge the gap between your sensors, devices, and existing data to your end users, WaveRoute Enterprise can bring it all together.

Come Visit Us at Sensors Expo Booth 603! Speak one-on-one with Digitec engineers, grab some mints, and learn more about WaveRoute Enterprise first hand. You can also visit our website, , to request a live demonstration.

WaveRoute is a division of Digitec, Inc. The WaveRoute product line offers drop-in M2M network hotspots. WaveRoute Enterprise is a hosted, web-based M2M application for remote monitoring and control. Established in 1982, Digitec is an electronics research, development, and manufacturing company in Milford, Nebraska.

Tuesday, April 14, 2009

M2M Expo

We are getting things ready for our booth at the M2M Expo. If you have done trade shows and have some tips, I would be thankful for the advice!

Update: We are no longer going to the M2M Expo in favor of going to Sensors Expo. Look for details soon!

Trying to Make EAV Work

I heart PostgreSQL. I heart data. I heart challenges. So when my friend David Fetter challenged me recently on a db design that stored data using the EAV model, I felt a bit cornered and not sure how to tackle the downsides of EAV.

There seems to be a lot of interesting discussions out there for and against EAV. The project I am currently working on requires flexibility as we, the developers, don't know what we need to add to the system. We have a fairly rigid set of requirements about the data and have metadata tables to help in the process.

Our application will be responsible for making sure that the data is stored properly. Secondly, all data is stored as NUMERIC, not as VARCHAR/TEXT as what most EAV systems seem to use. Thirdly, we assign what kind of data is being stored and use a lookup table for finite textual data.

So, now the question is, are we setting ourselves up for disaster going with EAV? I hope not.