ANSI ASTM F2017-2015 Standard Guide for Database Structure of Electronic Data Interchange Between Ship Owner and Shipyard for Contract Administration.pdf

《ANSI ASTM F2017-2015 Standard Guide for Database Structure of Electronic Data Interchange Between Ship Owner and Shipyard for Contract Administration.pdf》由会员分享，可在线阅读，更多相关《ANSI ASTM F2017-2015 Standard Guide for Database Structure of Electronic Data Interchange Between Ship Owner and Shipyard for Contract Administration.pdf（2页珍藏版）》请在麦多课文档分享上搜索。

1、Designation: F2017 15 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 F2017; the number immediately following the designation indicates the

2、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 () indicates an editorial change since the last revision or reapproval.1. Scope1.1 This guide provides the database structure of electr

3、onicdata 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 that must be exchan

4、gedbetween the parties during the contract period. This guide hasbeen developed to establish common field lengths, names, andtypes such that the exchanged information can be used directlyby the respective software programs without scanning, typing,or redundant keying of information.2. Terminology2.1

5、 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 they canalso be used to

6、 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 Found Report (CFR)a report

7、 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 maybe a simple acknowle

8、dgement 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 precision (maximum number of di

9、gits) 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 be related to a shipyard

10、initiated CFR.2.1.9 shipyardin this case, the principal party to a contractwith a ship owner.2.1.10 SQL compliantan industry standard datasublanguage, specifically designed to create, manipulate, andcontrol relational databases.2.1.11 tests and trial agendathe agenda provided by theshipyard, which d

11、etails 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 thatis normally done by hard copy. This can only be used whenboth parti

12、es 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 access of the data to all authorizedparties.4. Database Structure4.1 A

13、 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 theparty. However, there is data that is shared and common to bothparties in

14、a ship repair contract.1This guide is under the jurisdiction of ASTM Committee F25 on Ships andMarine Technology and is the direct responsibility of Subcommittee F25.05 onComputer Applications.Current edition approved May 1, 2015. Published May 2015. Originallyapproved in 2000. Last previous edition

15、 approved in 2006 as F2017 00 (2006)which was withdrawn January 2015 and reinstated in May 2015. DOI: 10.1520/F2017-15.Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States14.2 Condition Found ReportA Condition Found Report,generated by the

16、 shipyard and forwarded to the owner, will bestructured as follows:NameRequiredFieldType SizeDataElementOwnerCondition 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 R

17、eportGeneratedYDATEMM/DD/YYYY10 shipyardShipyard POC Y CHAR 30 shipyardCondition Y memo BLOB shipyardRecommendation N Memo BLOB shipyard4.3 Condition Found Report ResponseA Condition FoundReport Response, generated by the owner and forwarded to theshipyard, will be structured as follows:NameRequired

18、FieldType SizeDataElementOwnerCondition 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 fo

19、rwarded to the shipyard, will bestructured as follows:NameRequiredFieldType SizeDataElementOwnerRFP 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 o

20、wnerOwner POC 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:NameRequiredFieldType SizeDataElementOwnerProposal ID Y CHAR 10 shipyardOwner contract number Y CHAR 16

21、ownerShipyard 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 the

22、 ship-yard and forwarded to the owner, will be structured as follows:NameRequiredFieldType SizeDataElementOwnerTTA 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

23、 shipyardEvent tableAY memo BLOB shipyardAThe 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 r

24、ights asserted 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 a

25、ny time by 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

26、will receive 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

27、ASTM International, 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). Permission rights to photocopy the standard may also be secured from the Copyright Clearance Center, 222Rosewood Drive, Danvers, MA 01923, Tel: (978) 646-2600; http:/ 152