ASTM F2017-00

NOTICE: This standard has either been superseded and replaced by a new version or withdrawn.
Contact ASTM International (www.astm.org) for the latest information
An American National Standard
Designation:F2017–00
Standard Guide for
Database Structure of Electronic Data Interchange Between
Ship Owner and Shipyard for Contract Administration
This standard is issued under the fixed designation F 2017; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (e) indicates an editorial change since the last revision or reapproval.
1. Scope 2.1.6 INTEGER—a number that has no fractional part and
its precision (maximum number of digits) depends on the
1.1 This standard provides the database structure of elec-
specific SQL implementation.
tronic data interchange (EDI) information between ship owner
2.1.7 owner—in this case, the recognized authority for
and a shipyard for contract administration. Ship owners (here-
contracting ship repair work.
inafter referred to as owners) and shipyards may each have
2.1.8 Request for Proposal—an owner-generated document
unique software programs to manage their respective portions
asking the shipyard to add, modify, or delete work to the
of a ship repair period. There is information that must be
existing package. It may or may not be related to a shipyard
exchanged between the parties during the contract period. This
initiated CFR.
standardhasbeendevelopedtoestablishcommonfieldlengths,
2.1.9 shipyard—inthiscase,theprincipalparty to a contract
names, and types such that the exchanged information can be
with a ship owner.
used directly by the respective software programs without
2.1.10 SQL compliant—an industry standard data sublan-
scanning, typing, or redundant keying of information.
guage, specifically designed to create, manipulate, and control
2. Terminology relational databases. SQL-92 is the latest version of the
standard.
2.1 Definitions of Terms Specific to This Standard:
2.1.11 tests and trial agenda—the agenda provided by the
2.1.1 BLOB—short for binary large object, a collection of
shipyard, which details the planning schedule for all testing
binary data stored as a single entity in a database management
events to be conducted during a dock or sea trial.
systems (DBMS). BLOBs are used primarily to hold multime-
dia objects such as images, videos, and sound, though they can
3. Significance and Use
also be used to store programs or even fragments of code. Not
3.1 Intended Use—Compliance with this practice will allow
all DBMSs support BLOBs.
the sharing of electronic data between contracting parties that
2.1.2 CHAR(XX)—character data, alphanumeric where XX
is normally done by hard copy. This can only be used when
represents the maximum number of characters permitted and
both parties use a database-derived software package to man-
SQL fills the remaining spaces with blanks if fewer than the
age their contracts. Specifically, it will:
maximum are entered.
3.1.1 Eliminate the duplication of manual entry of data into
2.1.3 Condition Found Report (CFR)—a report generated
each party’s contract administration software package and
by the shipyard to inform the owner of conditions found,
3.1.2 Allow for wide access of the data to all authorized
deficiencies with the specification, or any other pertinent
parties.
information regarding a particular work item.
2.1.4 Condition Found Report Response—the owner’s re-
4. Database Structure
sponse back to the shipyard’s Condition Found Report. It may
4.1 A shipyard contract management database, or an owner
be a simple acknowledgement of receipt or a lengthy response
contract management database, may contain hundreds of tables
and reference to a Request for Proposal.
and fields and thousands of records. Much of the data is
2.1.5 DATE—stores the year, month, and day values of a
business-sensitive and must remain under the control of the
date. The length of a DATE is ten positions, as in 01/31/2000
party.However,thereisdatathatissharedandcommontoboth
(for 31 Jan 2000).
parties in a ship repair contract.
4.2 Condition Found Report—A Condition Found Report,
Th
...