ASTM F2017-15
(Guide)Standard Guide for Database Structure of Electronic Data Interchange Between Ship Owner and Shipyard for Contract Administration
Standard Guide for Database Structure of Electronic Data Interchange Between Ship Owner and Shipyard for Contract Administration
SIGNIFICANCE AND USE
3.1 Intended Use—Compliance with this guide will allow the sharing of electronic data between contracting parties that is normally done by hard copy. This can only be used when both parties use a database-derived software package to manage their contracts. Specifically, it will:
3.1.1 Eliminate the duplication of manual entry of data into each party’s contract administration software package and
3.1.2 Allow for wide access of the data to all authorized parties.
SCOPE
1.1 This guide provides the database structure of electronic data interchange (EDI) information between ship owner and a shipyard for contract administration. Ship owners (hereinafter referred to as owners) and shipyards may each have unique software programs to manage their respective portions of a ship repair period. There is information that must be exchanged between the parties during the contract period. This guide has been developed to establish common field lengths, names, and types such that the exchanged information can be used directly by the respective software programs without scanning, typing, or redundant keying of information.
General Information
Standards Content (Sample)
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
Designation: F2017 − 15 An American National Standard
Standard Guide for
Database Structure of Electronic Data Interchange Between
1
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.5 DATE—stores the year, month, and day values of a
date. The length of a DATE is ten positions, as in 01/31/2000
1.1 This guide provides the database structure of electronic
(for 31 Jan 2000).
data interchange (EDI) information between ship owner and a
shipyard for contract administration. Ship owners (hereinafter 2.1.6 INTEGER—a number that has no fractional part and
referred to as owners) and shipyards may each have unique its precision (maximum number of digits) depends on the
softwareprogramstomanagetheirrespectiveportionsofaship specific SQL implementation.
repair period. There is information that must be exchanged
2.1.7 owner—in this case, the recognized authority for
between the parties during the contract period. This guide has
contracting ship repair work.
been developed to establish common field lengths, names, and
2.1.8 Request for Proposal—an owner-generated document
types such that the exchanged information can be used directly
asking the shipyard to add, modify, or delete work to the
by the respective software programs without scanning, typing,
existing package. It may or may not be related to a shipyard
or redundant keying of information.
initiated CFR.
2. Terminology
2.1.9 shipyard—in this case, the principal party to a contract
with a ship owner.
2.1 Definitions of Terms Specific to This Standard:
2.1.1 BLOB—short for binary large object, a collection of
2.1.10 SQL compliant—an industry standard data
binary data stored as a single entity in a database management
sublanguage, specifically designed to create, manipulate, and
systems (DBMS). BLOBs are used primarily to hold multime-
control relational databases.
dia objects such as images, videos, and sound, though they can
2.1.11 tests and trial agenda—the agenda provided by the
also be used to store programs or even fragments of code. Not
shipyard, which details the planning schedule for all testing
all DBMSs support BLOBs.
events to be conducted during a dock or sea trial.
2.1.2 CHAR(XX)—character data, alphanumeric where XX
represents the maximum number of characters permitted and
3. Significance and Use
SQL fills the remaining spaces with blanks if fewer than the
3.1 Intended Use—Compliance with this guide will allow
maximum are entered.
the sharing of electronic data between contracting parties that
2.1.3 Condition Found Report (CFR)—a report generated
is normally done by hard copy. This can only be used when
by the shipyard to inform the owner of conditions found,
both parties use a database-derived software package to man-
deficiencies with the specification, or any other pertinent
age their contracts. Specifically, it will:
information regarding a particular work item.
3.1.1 Eliminate the duplication of manual entry of data into
2.1.4 Condition Found Report Response—the owner’s re-
each party’s contract administration software package and
sponse back to the shipyard’s Condition Found Report. It may
3.1.2 Allow for wide access of the data to all authorized
be a simple acknowledgement of receipt or a lengthy response
parties.
and reference to a Request for Proposal.
4. Database Structure
4.1 A shipyard contract management database, or an owner
1
This guide is under the jurisdiction of ASTM Committee F25 on Ships and
contract management database, may contain hundreds of tables
Marine Technology and is the direct responsibility of Subcommittee F25.05 on
Computer Applications.
and fields and thousands of records. Much of the data is
Current edition approved May 1, 2015. Published May 2015. Originally
business-sensitive and must remain under the control of the
approved in 2000. Last previous edition approved in 2006 as F2017 – 00 (2006)
party. However, there is data that is shared and common to both
which was withdrawn January 2015 and reinstated in May 2015. DOI: 10.1520/
F2017-15. parties in a ship repair contract.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States
1
---------------------- Page: 1 ----------------------
F2017 − 15
4.2 Condition Found Report—A Condition Found Report, 4.5 Proposal—A Proposal, in response to an RFP and
generated by the shipyard and forwarded to the owner, will be generated by the shipyard and forwarded to the owner, will be
structured as follo
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.