How do I move data from Model A to Model B without reinputting the data? Model A works better for planning studies. Model B is better for survival studies. I need to get information from my model and publish it on the company intranet, for others to see. How can I efficiently do this? It is to answer the questions given above that the Data Standards Committee was initially formed. This small group of volunteers has worked very hard to get the standards written and available for review. We have posted two sections of the XPSL (extensible pipeline simulation language) on the PSIG website for review. These are:

  • PSIG 001/2004 XPSL: Configuration Objects: Recommendation Document

  • PSIG 002/2004 XPSL: Output Snapshots: Recommendation Document The paper gives an overview on where the committee is and includes the two sections that must be reviewed.


The data standards committee was initially formed in 1998 by the PSIG Board. The committee has published two standards:

  • PSIG 001/2000 - Common Language Standard

  • PSIG 002/2000 - Recommend Practice for Software Acquisition After the 2000, meeting the committee reformed to work on the Data Model Standards. In 2002, the XPLS Plan was presented and accepted by the PSIG membership. The plan gives the philosophy of the XPSL language and set up the approval process for the XPSL standards. Also, we registered the XPSL language type. Presently, the committee has the following members, Mary Goodreau, Susan Bachman, Ed Nicholas, Chuck O'Leary, Vern Mallu, Jason Modisett, Ulli Pietsch, Bill Chmilar, and Terry Hughes.


The basic philosophy of the Standards Committee has been to create a Data Model Standard that is independent of Software Vendor and as independent as possible of the type of modeling being done (steady state, transient or online - liquid or gas). The proposed XPSL is extensible and can be enhanced by vendors to include their specific input. The other basic philosophy was to document the 20% of the devices and features which make up 80% of the PSIG user community models. This sets limits on the extent of the data model. The basic concept is to have a vendor independent XML file which can be translated by the vendor or the user into the appropriate format for which ever simulation package is currently being used. This would leave one central data model which can be maintained and then translated into the appropriate input structure. The goal is that once the standards have been accepted by the membership that the vendors will implement the necessary translations and provide means of writing and reading the PSIG Data Model.


The Configuration Objects Recommendation has definitions for devices which physically make up the piping system, pipes, valves, regulators, compressors and pumps. See Appendix A. It also has definitions for non-physical modeling devices such as nodes (connection points - possibly where flow enters or leaves the system) and externals (points where flows enters or leaves the system).

This content is only available via PDF.
You can access this article if you purchase or spend a download.