1、Designation:F201715An 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 year
2、 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 electronicdata in
3、terchange(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 exchangedbetween the pa
4、rties 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 Definitions of Terms
5、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 store programs or even frag
6、ments 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 generatedby the shipyard to in
7、form 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 acknowledgement of receipt or a lengthy r
8、esponseand 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 digits)depends on thespecific SQL implem
9、entation.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 shipyardinitiated CFR.2.1.9 shipyardin this case,th
10、e principal party to a contractwith a ship owner.2.1.10 SQLcompliantanindustrystandarddatasublanguage,specifically designed to create,manipulate,andcontrol relational databases.2.1.11 tests and trial agendathe agenda provided by theshipyard,which details the planning schedule for all testingevents t
11、o 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 parties use a database-derived software package to man-age
12、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 shipyard contract management database,or an ownercontrac
13、t 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 a ship repair contract.1This guide is under the jurisdiction o
14、f 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 approved in 2006 as F2017 00(2006)which was withdrawn January 201
15、5 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 States1 4.2 Condition Found ReportA Condition Found Report,generated by the shipyard and forwarded to the owner,will bestructured as follows:NameReq
16、uiredFieldTypeSizeDataElementOwnerCondition Found Report IDYCHAR10shipyardContract numberYCHAR16ownerWork item numberYCHAR7ownerEquipment ID numberNInteger12ownerShip nameNCHAR30ownerDate Condition Found ReportGeneratedYDATEMM/DD/YYYY10shipyardShipyard POCYCHAR30shipyardConditionYmemoBLOBshipyardRecommendationNMemoBLOBshipyard4.3 Condition Found Report ResponseA Condition FoundReport Response,generated by the owner and forwarded to theshipyard,will be structured as follows:NameRequiredFieldTypeS
