How to Submit a Change Request

POSC Request Tracker Information

Introduction

The POSC Request Tracker ("Tracker") is used by POSC to accept, track, and respond to various types of requests related to POSC offerings. Users may submit requests to the Tracker to report defects, to request enhancements, to ask questions, to make recommendations, to ask for clarification, or to get general help.

The Tracker provides e-mail notification to the individual submitter of the progress of the request in the system. Each request and the POSC response to each request are posted in the appropriate POSC news groups on UUNET. Please contact the POSC Help Desk (help@posc.org) if you need additional information on subscribing to these news groups.

E-mail Submittal Instructions

The Tracker accepts requests submitted by e-mail using the Request Submittal Form. The form is also available on the POSC anonymous ftp server:

       ~/pub/request_form.txt

The format must be followed explicitly in order to have a request registered correctly in the system.

After completing the request form, send it by e-mail to:

         problem@posc.org

To be processed electronically into the Request Tracker, the request form must be in the body of the message, not as an include or enclosure file. Additional comments or other information included in the e-mail will not be read by the Help Desk staff. If you have comments or questions on submitting a request, e-mail them to help@posc.org. This mail box is read directly by the Help Desk staff.

When your request is processed into the Tracker, the Tracker generates an e-mail notification confirming its receipt. If you not receive this confirmation message within two business days after submittal, contact the POSC Help Desk by e-mail at help@posc.org, or by telephone at 713 784 1880.

The form is self-explanatory in most areas; however, the product definitions require some additional detail to ensure the correct classification is made. Included after the product definitions are some guidelines for preparing the problem description.

Submitting a Change Request by means other than email

To submit a change request by fax, please send it to the attention of the Help Desk at:

POSC Houston office: +1 713 784 9219 (fax)

POSC London office: +44 17 3281 7248 (fax)

For instructions on how to submit a problem report by means other than email or fax, please contact:

POSC (Houston): +1 713 784 1880 (voice)

POSC (London): +44 17 3246 6157 (voice)

Product Definitions

The following is a list of the various product types currently used by POSC; the types generally follow the deliverables available from POSC or other sources. There are some subtle variations which you should follow, so please review this list prior to submitting a request.

Epicentre DM: Applies to Entity Definitions or other definitions within the Data Model description itself.
Epicentre Spec: Applies to the written specification for areas other than Entity Definitions, generally the discussion portions of the documentation.
Epicentre EXPRESS: Applies to requests specific to the EXPRESS file. These requests should be very specific to the EXPRESS file, such as "file will not load." For requests related to a definition, specify the product as Epicentre DM rather than Epicentre EXPRESS.
Relational DDL: Applies to the DDL file specifically, and can include questions about definitions in Tables, etc., which in turn will be generated by creating a new projection from Epicentre.
DAE Spec: Applies to the specification for Data Access and Exchange.
Sample Implent'n: Applies to any request related to the various Sample Implementations for Data Access and Exchange. In general,this product designation is for questions associated with the source code, make files, etc.
Relational Implent'n: Applies to the computer programs associated with access to the spatial data types using the supplemental libraries. Care should be taken to differentiate questions related to DDL from questions about the actual routines.
DAE Doc: Applies to any written documentation for the Data Access and Exchange products other than the published specifications. This applies to Release Notes, User Information or other written materials delivered as part of the implementations.
PEF Spec: Applies to the Exchange Format specification.
PEF R/W: Applies to the PEF read/write routines included in the Sample Implementation.
Epigramme Toolkit: Applies to Epigramme Toolkit documentation and to the routines included in the specification.
Ref_Entity: Applies to any question regarding Reference Entities and their values or usage. For questions related to definitions of entities, specify the product as Epicentre DM rather than Ref_Entity.
Style Guide Spec: Applies to the Prentice Hall published specification.
CGM*PIP Spec: Applies to the CGM*PIP document published by POSC. The specifications for both PIP/I and PIP/II are included in the same document. Submissions should indicate the PIP level in the "product_version" attribute.
BCS Spec: Applies to the Base Computer Standards specification.
Browser: Applies to the operation of the Epicentre Data Model Browser product, including errors in the computer program or failure to operate correctly. For questions related to definitions in the Epicentre Data Model, which are viewed in the Browser, specify product Epicentre DM rather than Browser.
Issue: Applies to topics that are not related to a specific deliverable.
Help: Applies to requests for assistance of a general nature, for example "Need copy of Maintenance Agreement."

Problem description field

The problem description field should include as much detail as necessary to thoroughly describe the request. For requests which are classified as enhancements or recommendations, the problem description should include the business justification.

POSC Home Page

Updated: February 21, 2001. Send questions and comments to webmaster@posc.org