Hello all,
We are planning to pick our next development project. The idea is to come up with a plug and play component written under .Net Framework/Compact .Net Framework, similar to NetPro Modbus Master [see www.controltoolbox.com].

We like to share some ideas with you guys and get your feedback. If you may, please try to include the following points in your feedback:

* Existing competition if any
* Industry and the applications it can be used
* Country and the industry you are working in
* How you like to see the licensing for each particular case (for example per RTU, per point, per number of communication bytes etc)
* Any feature you like to see with the solution
* How much would you think the solution worths to you.

Now here are the ideas:

[1] Data communication protocol module: Examples: Modbus client, OPC server/client, DNP3 master/slave, etc. The module can be accessed via network APIs [including a wide area network and M2M] to read/write and receive events.

[2] Independent Alarm Module: Be able to define an alarm module independent of SCADA, as an OPC client and be able to communicate via network APIs such as Remoting, Web Services or other WCF [Windows Communication Framework] mechanisms. Be able to define object hierarchy, different alarm zones and classes and script the alarm conditions rather just H, HH, L and LL conditions. Be able to delete, add, inhibit and un-inhibit online. Be able to acknowledge an entire parent area. Be able to view reports and alarm history based on filters such as zone, class, area, time etc.

[3] Independent Historian Module: Be able to define a historian module independent of SCADA, as an OPC client and be able to communicate via network APIs such as Remoting, Web Services or other WCF mechanisms. Be able to view reports in online and batch mode based on filters such as zone, class, area, time etc.

Please let us know if there is any other solution that you wish somebody develop it for you.

Thanks in advance for sharing your ideas.

If you like, please email us directly at [email protected]

 

I've got a really good idea for you. Why don't you hire a consultant who specializes in this kind of research to develop it for you? Otherwise, you will probably develop a gee-whiz product nobody really wants, and won't make a lot of money for yourselves.

Cheaping out on market research isn't ever a good idea.

Walt Boyes (who used to be one of those consultants)
Editor in Chief
Control and Controlglobal.com
www.controlglobal.com
Mailto:[email protected]
Read my blog SoundOFF!! At www.controlglobal.com/soundoff

 

Well, thanks for your response. But how about if we let the real users (engineers, system integrators, etc) tell us what they want instead and market research consultants that probably do not know the subject matter that well?

Best Regards,
Rod

 

I would have to agree with Walt Boyes. The questions you are asking aren't technical ones, they're market research questions. You can ask people on the Internet for opinions, but opinions are cheap and you won't know which if any of the opinion givers fit the profile of your potential customers. You're selling software licenses, and there is a big difference between "being interested in something" and "being willing to part with money for it".

If you don't like that avenue, then try talking to some of your existing customers yourself, if you know who they are. That will probably mean dropping in to see them and taking them out for lunch, so that approach won't be free either. You'll also have to know which ones are worth talking to, which isn't always easy.

The other alternative is to just use your own judgment, write it, and see if anyone wants it. DNP3 might be a lot of work, but the rest of the stuff you have listed doesn't sound particularly difficult.