1、Designation: F 2017 00 (Reapproved 2006)An American National StandardStandard Guide forDatabase Structure of Electronic Data Interchange BetweenShip Owner and Shipyard for Contract Administration1This standard is issued under the fixed designation F 2017; the number immediately following the designa
2、tion indicates the year oforiginal adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. Asuperscript epsilon (e) indicates an editorial change since the last revision or reapproval.1. Scope1.1 This guide provides the database
3、 structure of electronicdata interchange (EDI) information between ship owner and ashipyard for contract administration. Ship owners (hereinafterreferred to as owners) and shipyards may each have uniquesoftware programs to manage their respective portions of a shiprepair period. There is information
4、 that must be exchangedbetween the parties during the contract period. This standardhas been developed to establish common field lengths, names,and types such that the exchanged information can be useddirectly by the respective software programs without scanning,typing, or redundant keying of inform
5、ation.2. Terminology2.1 Definitions of Terms Specific to This Standard:2.1.1 BLOBshort for binary large object, a collection ofbinary data stored as a single entity in a database managementsystems (DBMS). BLOBs are used primarily to hold multime-dia objects such as images, videos, and sound, though
6、they canalso be used to store programs or even fragments of code. Notall DBMSs support BLOBs.2.1.2 CHAR(XX)character data, alphanumeric where XXrepresents the maximum number of characters permitted andSQL fills the remaining spaces with blanks if fewer than themaximum are entered.2.1.3 Condition Fou
7、nd Report (CFR)a report generatedby the shipyard to inform the owner of conditions found,deficiencies with the specification, or any other pertinentinformation regarding a particular work item.2.1.4 Condition Found Report Responsethe owners re-sponse back to the shipyards Condition Found Report. It
8、maybe a simple acknowledgement of receipt or a lengthy responseand reference to a Request for Proposal.2.1.5 DATEstores the year, month, and day values of adate. The length of a DATE is ten positions, as in 01/31/2000(for 31 Jan 2000).2.1.6 INTEGERa number that has no fractional part andits precisio
9、n (maximum number of digits) depends on thespecific SQL implementation.2.1.7 ownerin this case, the recognized authority forcontracting ship repair work.2.1.8 Request for Proposalan owner-generated documentasking the shipyard to add, modify, or delete work to theexisting package. It may or may not b
10、e related to a shipyardinitiated CFR.2.1.9 shipyardin this case, the principal party to a contractwith a ship owner.2.1.10 SQL compliantan industry standard data sublan-guage, specifically designed to create, manipulate, and controlrelational databases. SQL-92 is the latest version of thestandard.2.
11、1.11 tests and trial agendathe agenda provided by theshipyard, which details the planning schedule for all testingevents to be conducted during a dock or sea trial.3. Significance and Use3.1 Intended UseCompliance with this guide will allowthe sharing of electronic data between contracting parties t
12、hatis normally done by hard copy. This can only be used whenboth parties use a database-derived software package to man-age their contracts. Specifically, it will:3.1.1 Eliminate the duplication of manual entry of data intoeach partys contract administration software package and3.1.2 Allow for wide
13、access of the data to all authorizedparties.4. Database Structure4.1 A shipyard contract management database, or an ownercontract management database, may contain hundreds of tablesand fields and thousands of records. Much of the data isbusiness-sensitive and must remain under the control of thepart
14、y. However, there is data that is shared and common to bothparties in a ship repair contract.4.2 Condition Found ReportA Condition Found Report,generated by the shipyard and forwarded to the owner, will bestructured as follows:Name Re-quiredFieldType Size DataElementOwner1This guide is under the jur
15、isdiction of ASTM Committee F25 on Ships andMarine Technology and is the direct responsibility of Subcommittee F25.05 onComputer Applications.Current edition approved May 1, 2006. Published May 2006. Originallyapproved in 2000. Last previous edition approved in 2000 as F 2017 00.1Copyright ASTM Inte
16、rnational, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.Condition Found Report ID Y CHAR 10 shipyardContract number Y CHAR 16 ownerWork item number Y CHAR 7 ownerEquipment ID number N Integer 12 ownerShip name N CHAR 30 ownerDate Condition Found ReportGenerated
17、YDATEMM/DD/YYYY10 shipyardShipyard POC Y CHAR 30 shipyardCondition Y memo BLOB shipyardRecommendation N Memo BLOB shipyard4.3 Condition Found Report ResponseACondition FoundReport Response, generated by the owner and forwarded to theshipyard, will be structured as follows:Name RequiredFieldType Size
18、 DataElementOwnerCondition Found Report ID Y CHAR 10 shipyardContract number Y CHAR 16 shipyardShip name N CHAR 30 ownerResponse date Y DATEMM/DD/YYYY10 ownerOwner POC Y CHAR 30 ownerResponse N memo BLOB owner4.4 Request for ProposalA Request for Proposal, gener-ated by the owner and forwarded to th
19、e shipyard, will bestructured as follows:Name RequiredFieldType Size DataElementOwnerRFP ID Y INTEGER 4 ownerCondition Found Report ID Y CHAR 10 shipyardOwner contract number Y CHAR 16 ownerShipyard contract number Y CHAR 16 shipyardShip name N CHAR 30 ownerRFP date Y DATE(MM/DD/YYYY)10 ownerOwner P
20、OC Y CHAR 30 ownerStatement of work Y memo BLOB owner4.5 ProposalA Proposal, in response to an RFP andgenerated by the shipyard and forwarded to the owner, will bestructured as follows:Name RequiredFieldType Size DataElementOwnerProposal ID Y CHAR 10 shipyardOwner contract number Y CHAR 16 ownerShip
21、yard contract number Y CHAR 16 shipyardShip name N CHAR 30 ownerRFP ID N INTEGER 4 ownerProposal date Y DATE(MM/DD/YYYY)8 shipyardShipyard POC Y CHAR 30 shipyardSOW comments N memo BLOB shipyardShipyard proposal N Currency($#,#,#.#)$M shipyard4.6 Test and Trial AgendaA TTA, generated by theshipyard
22、and forwarded to the owner, will be structured asfollows:Name RequiredFieldType Size DataElementOwnerTTA ID Number (Long) 4Owner contract number Y CHAR 16 ownerShipyard contract number Y CHAR 16 shipyardShip name N CHAR 30 ownerAgenda date Y DATE(MM/DD/YYYY)8 shipyardShipyard POC Y CHAR 30 shipyardE
23、vent tableAY memo BLOB shipyard_AThe event table will include the test name, equipment name, start time, andrequired attendees (witnesses).5. Keywords5.1 contract administration; database; electronic; owner;shipyardASTM International takes no position respecting the validity of any patent rights ass
24、erted in connection with any item mentionedin this standard. Users of this standard are expressly advised that determination of the validity of any such patent rights, and the riskof infringement of such rights, are entirely their own responsibility.This standard is subject to revision at any time b
25、y the responsible technical committee and must be reviewed every five years andif not revised, either reapproved or withdrawn. Your comments are invited either for revision of this standard or for additional standardsand should be addressed to ASTM International Headquarters. Your comments will rece
26、ive careful consideration at a meeting of theresponsible technical committee, which you may attend. If you feel that your comments have not received a fair hearing you shouldmake your views known to the ASTM Committee on Standards, at the address shown below.This standard is copyrighted by ASTM Inte
27、rnational, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959,United States. Individual reprints (single or multiple copies) of this standard may be obtained by contacting ASTM at the aboveaddress or at 610-832-9585 (phone), 610-832-9555 (fax), or serviceastm.org (e-mail); or through the ASTM website(www.astm.org).F 2017 00 (2006)2
