[foxboro] AW: Tool development (was Spare I/O points)

Andreas,

you wrote:
> Why isn't Invensys Foxboro able to recognize this gap...=20

Invensys DOES recognize this. Unfortunately we from Invensys have to =
work
with our own software, so we suffer at least as you customer guys do. =
;-)=20

> ...and offer a solution?

I can tell you that Invensys is working on that, but up to now I can't =
tell
you when and what you'll get, maybe I can later.

Best regards -

Marcel Sieling
Systems Technologies

Invensys Systems GmbH
Emanuel-Leutze-Str. 11
40547 Duesseldorf
Germany
T: +49-211-5966-302
F: +49-163-99-5966302=20
M: +49-163-5966302
Skype:  marcel.sieling
mailto:marcel.sieling@xxxxxxxxxxxxxxxx
http://www.foxboro-deutschland.de

Invensys Anwender Symposium
F=FCr Prozess- und Kraftwerksindustrie
21.- 22. September 2005
MARITIM Hotel K=F6ln=20
Informationen und Registrierung
www.foxboro-deutschland.de/as2005/


> -----Urspr=FCngliche Nachricht-----
> Von: foxboro-bounce@xxxxxxxxxxxxx=20
> [mailto:foxboro-bounce@xxxxxxxxxxxxx] Im Auftrag von Weiss, Andreas
> Gesendet: Mittwoch, 24. August 2005 09:08
> An: foxboro@xxxxxxxxxxxxx
> Betreff: [foxboro] Tool development (was Spare I/O points)
>=20
>=20
> Hi,
>=20
> everyone is developing his own tool or toolkit to extract=20
> data out of the I/A system.
>=20
> Why is that?
> I vote that a lot of users are not happy with FoxCAE.
>=20
> Why isn't Invensys Foxboro able to recognize this gap and=20
> offer a solution? I don't know.
>=20
> But it would help developers like you and me if we had a way=20
> to exchange our code. Why not working more together? I think=20
> that we had a call for action like this sometime ago and I'm=20
> interested again. That would require that all developers in a=20
> project accept the code formatting rules and a lot of other=20
> stuff ...=3D20
>=20
> more concrete
>=20
> I'm working on a standardized way of extracting all Control=20
> Station Database data into other file formats. I develop my=20
> own thing (at this
> time) because I'm not happy with existing tools, they are not=20
> failsafe enough and not able to run 24x7x365. The project is=20
> splitted into different parts: 1. detecting changes in the=20
> Control Station database 2. extracting the Control Station=20
> database information=3D20 3. converting the information into=20
> different file formats (xml, txt, sql database)=3D20 4.=20
> creating subsets of these information for specific tasks=20
> (data file for visualizing the used I/O points, ...) because=20
> the amount of data (file sizes) takes a lot of machine=20
> ressources 5. offer the data for clients or client programs=20
> on other machines
>=20
> Part 1 and 2 are nearly finished. Part 3 is finished for one=20
> xml-file-format.=3D20 I'm using kornshell scripts at this time.
>=20
> Let's see how far this project grows.
>=20
> Regards,
> Andreas Weiss
>=20
> =20
> =20
> ______________________________________________________________
> _________
> This mailing list is neither sponsored nor endorsed by=20
> Invensys Process Systems (formerly The Foxboro Company). Use=20
> the info you obtain here at your own risks. Read=20
> http://www.thecassandraproject.org/disclaimer.html
> =20
> foxboro=20
> mailing list:             http://www.freelists.org/list/foxboro
> to subscribe:        =20
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to=20
> unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
>=20

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: