ASTM F2017-15(2022)

This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the
Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.
Designation: F2017 − 15 (Reapproved 2022) An American National Standard
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 F2017; 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 (´) indicates an editorial change since the last revision or reapproval.
1. Scope 2.1.4 Condition Found Report Response—the owner’s re-
sponse back to the shipyard’s Condition Found Report. It may
1.1 This guide provides the database structure of electronic
be a simple acknowledgement of receipt or a lengthy response
data interchange (EDI) information between ship owner and a
and reference to a Request for Proposal.
shipyard for contract administration. Ship owners (hereinafter
2.1.5 DATE—stores the year, month, and day values of a
referred to as owners) and shipyards may each have unique
date. The length of a DATE is ten positions, as in 01/31/2000
softwareprogramstomanagetheirrespectiveportionsofaship
(for 31 Jan 2000).
repair period. There is information that must be exchanged
between the parties during the contract period. This guide has
2.1.6 INTEGER—a number that has no fractional part and
been developed to establish common field lengths, names, and
its precision (maximum number of digits) depends on the
types such that the exchanged information can be used directly
specific SQL implementation.
by the respective software programs without scanning, typing,
2.1.7 owner—in this case, the recognized authority for
or redundant keying of information.
contracting ship repair work.
1.2 This international standard was developed in accor-
2.1.8 Request for Proposal—an owner-generated document
dance with internationally recognized principles on standard-
asking the shipyard to add, modify, or delete work to the
ization established in the Decision on Principles for the
existing package. It may or may not be related to a shipyard
Development of International Standards, Guides and Recom-
initiated CFR.
mendations issued by the World Trade Organization Technical
2.1.9 shipyard—in this case, the principal party to a contract
Barriers to Trade (TBT) Committee.
with a ship owner.
2. Terminology
2.1.10 SQL compliant—an industry standard data
sublanguage, specifically designed to create, manipulate, and
2.1 Definitions of Terms Specific to This Standard:
control relational databases.
2.1.1 BLOB—short for binary large object, a collection of
binary data stored as a single entity in a database management 2.1.11 tests and trial agenda—the agenda provided by the
systems (DBMS). BLOBs are used primarily to hold multime- shipyard, which details the planning schedule for all testing
dia objects such as images, videos, and sound, though they can
events to be conducted during a dock or sea trial.
also be used to store programs or even fragments of code. Not
3. Significance and Use
all DBMSs support BLOBs.
3.1 Intended Use—Compliance with this guide will allow
2.1.2 CHAR(XX)—character data, alphanumeric where XX
the sharing of electronic data between contracting parties that
represents the maximum number of characters permitted and
is normally done by hard copy. This can only be used when
SQL fills the remaining spaces with blanks if fewer than the
both parties use a database-derived software package to man-
maximum are entered.
age their contracts. Specifically, it will:
2.1.3 Condition Found Report (CFR)—a report generated
3.1.1 Eliminate the duplication of manual entry of data into
by the shipyard to inform the owner of conditions found,
each party’s contract administration software package and
deficiencies with the specification, or any other pertinent
3.1.2 Allow for wide access of the data to all authorized
information regarding a particular work item.
parties.
4. Database Structure
This guide is under the jurisdiction of ASTM Committee F25 on Ships and
Marine Technology and is the direct responsibility of Subcommittee F25.05 on
4.1 A shipyard contract management database, or an owner
Computer Applications.
contract management database, may contain hundreds of tables
Current ed
...