Possible Strategies for Data Exchange
This presentation is the property of its rightful owner.
Sponsored Links
1 / 43

Emergency Response & Salvage operations ERS-Data Sheets (technical data) PowerPoint PPT Presentation


  • 112 Views
  • Uploaded on
  • Presentation posted in: General

Possible Strategies for Data Exchange in MARVIN David Jaramillo TC Meeting #2 June 17th - 18th, Oslo - Norway. Data Requirements in T1.2. Emergency Response & Salvage operations ERS-Data Sheets (technical data) Additional ship documents, drawings, etc. (technical data) Repair Negotiation

Download Presentation

Emergency Response & Salvage operations ERS-Data Sheets (technical data)

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Emergency response salvage operations ers data sheets technical data

Possible Strategies for Data Exchange in MARVINDavid JaramilloTC Meeting #2 June 17th - 18th, Oslo - Norway


Emergency response salvage operations ers data sheets technical data

Data Requirements in T1.2

  • Emergency Response & Salvage operations

    • ERS-Data Sheets (technical data)

    • Additional ship documents, drawings, etc. (technical data)

  • Repair Negotiation

    • Preliminary work specifications (technical data)

    • Tenders, Quotations (business data)

  • Repair

    • Final work specifications (technical data)

    • Ship specific data and data for class renewal (technical data)

    • Other internal yard processes like purchasing, contracting etc. (business data)


Emergency response salvage operations ers data sheets technical data

Product Data & Business Data

  • Existing solutions for exchanging both kind of data

    UN/EDIFACT (ISO 9735)

    ODETTE (VDA)

    STEP (ISO 10303)

    IGES, SET, VDA-FS

  • Sub-Standards in maritime/shipbuilding industry

    STEP shipbuilding AP’s (ship product data description)

    IMPA/ETS (purchasing, trading)

    EDIMAR EDIFACT-subset (not available yet)

  • Harmonization of product and business data


Un edifact

UN/EDIFACT


Emergency response salvage operations ers data sheets technical data

UN/EDIFACT

  • United Nations Electronic Data Interchange for Administration Commerce and Transport

  • Set of internationally agreed syntax standards, directories and guideline for the structuring and exchange between independent computer systems of data that can be generated in character format.

  • UN/EDIFACT rules are published in the United Nations Trade Data Interchange Directory (UNTDID).


Emergency response salvage operations ers data sheets technical data

UN/EDIFACT (2)

  • UN/EDIFACT syntax rules (ISO 9735) for structuring data messages ratified as a European Standard (EN 29735).

  • EDIFACT Message Directory (EDMD): Lists all the messages that have been approved for international use, known as United Nations Standard Messages (UNSMs).

  • Over 200 internationally agreed messages available


Emergency response salvage operations ers data sheets technical data

EDIFACT based data exchange

Source: Rabe et al, 1998


Emergency response salvage operations ers data sheets technical data

Structure of an EDIFACT file


Emergency response salvage operations ers data sheets technical data

  • UN/EDIFACT - Purchase Order Message Structure

  • (Simplified)

  • UNH

  • BGM

  • DTM

  • NAD

  • LIN

  • UNS

  • UNT

  • IMD

  • QTY

  • Example of Call - Up Order

  • UNH + 1+ ORDERS: 93A : UN : CE 941 ‘

  • BGM + 226 + 0103109601 ‘

  • DTM + 137 : 19941212 : 102 ‘

  • DTM + 2: 19941215 : 102 ‘

  • NAD + BY + 5467895056010 . : 9 ‘

  • NAD + SE + 4012345500000 : : 9 ‘

  • LIN + 1 + + 4000862141404 : EN ‘

  • IMD + F + + : : : SULPHURIC ACID 96% ‘

  • QTY + 21 : 4000 : LTR ‘

  • UNS + S ‘

  • UNT + 32 + 1 ‘


Emergency response salvage operations ers data sheets technical data

  • Business Transaction

  • CONNIT

  • Invitation to tender

  • CONEST

  • Establishment of contract

  • CONTEN

  • Tender

  • Materials Management

  • PRICAT

  • Price/sales catalogue

  • REQUOTE

  • Request for quote

  • PARTIN

  • Party information

  • QUOTE

  • Quote

  • PRODAT

  • Product data

  • ORDERS

  • Purchase order

  • QUALITY

  • Quality data

  • ORDRSP

  • Purchase order response

  • ORDCHG

  • Purchase order change

  • DESADV

  • Dispatch advice

  • DELFOR

  • Delivery schedule

  • RECADV

  • Receiving advice

  • DELJIT

  • Delivery Just In Time

  • INVOICE

  • Invoice

  • Finance/Accountancy

  • CREADV

  • Credit advice

  • FINCAN

  • Financial cancellation

  • PAYORD

  • Payment order

  • FINSTA

  • Financial statement

  • DEBADV

  • Debit advice

  • Other fields

  • PROTAP

  • Project tasks planning

  • CONDRO

  • Drawing organization

  • CONAPW

  • Advice on pending works

  • CONDRA

  • Drawing administration

Example of existing EDIFACT messages

Source: UNTDID (1997)


Emergency response salvage operations ers data sheets technical data

EDIFACT and Product Data Exchange

  • ENGDAT (ODETTE WG)

  • UN/ECE CONDRA (EDIFACT)

  • Referencing of product data files in EDIFACT messages in both ENGDAT and CONDRA messages

  • Other approaches, e.g EDIFACT Transfer Protocol ETP of C-lab (Germany)

  • Description of EDIFACT messages in EXPRESS


Impa ets

IMPA/ETS


Emergency response salvage operations ers data sheets technical data

IMPA/ETS

  • IMPA: International Marine Purchasing Association (ship owners, managing and operating companies, suppliers and manufacturers).

  • Working group established 1997 to improve communication between purchaser and supplier within the maritime industry.

  • Communication standard for trading in the shipping industry created - ETSF (Electronic Trading Standard Format)

  • Based on internet technology and the EDIFACT standard.

  • Freely accessible to all companies wishing to use it.

  • Definitions available to companies wishing to adapt software to work with the standard (registration required).


Emergency response salvage operations ers data sheets technical data

IMPA/ETS

Purchasing Cycle

  • Ships Requisition

  • Requisition forwarded to office

  • Office requests quotes

  • Quotes received and compared

  • Order placed

  • Order Acknowledged

  • Delivery advice

  • Goods delivered to ship or central store

  • Office advised delivery

  • Invoice

Items in red are covered by the standard


Emergency response salvage operations ers data sheets technical data

IMPA/ETS

Some Message Definitions


Step express

STEP & EXPRESS


Emergency response salvage operations ers data sheets technical data

STEP Technology (1)

  • STandard for the Exchange of Product Model Data

  • Informal name for ISO 10303 “Product Data Representation and Exchange”

  • Undertaken by the ISO in the TC184 SC4

  • Provide a complete, unambiguous, computer interpretable definition of the physical functional characteristics of each unit of a product throughout its lifecycle.

  • Uses methodologies to develop and define the standard to avoid ambiguities found in other standards such as IGES


Emergency response salvage operations ers data sheets technical data

STEP Technology (2)

  • STEP supports the exchange of product data

  • STEP has been designed with computer aided implementation in mind.

  • The enabling technology for the computer aided implementation of STEP (the STEP technology) is part of the STEP standard.

  • STEP Technology is totally independent of the STEP content


Express

ENTITY cartesian_point;

SUBTYPE OF (point);

coordinates : LIST [1:3] OF length_measure;

END_ENTITY;

EXPRESS

  • ISO 10303-11 – EXPRESS Language Reference Manual

  • machine compilable

  • object oriented baseline

  • several incarnations

  • also in use outside of STEP


Express g

EXPRESS-G

  • A formal graphical notation of a subset of EXPRESS

  • For human communication

  • A normative Annex to ISO 10303 - Part 11


Use of express models

Use of EXPRESS models

  • as data dictionary for a DBMS

  • as specification of an exchange format

    • ISO 10303-21: Clear Text Encoding of the Exchange Structure

  • as specification of a data access interface

    • ISO 10303-22: Standard Data Access Interface

    • ISO 10303-23: C++ binding

    • ISO 10303-24: C binding

    • ISO 10303-26: IDL binding


Express data on file

Classification

Society

Yard

DB

DB

EXPRESS data on file

EXPRESS

schema

STEP-physical file


What is part 21

What is Part 21?

  • specification of an ASCII file format

    • character set

    • tokens

  • a mapping of EXPRESS defined models to and instance exchange format

    • What does an instance look like that is conformant to an EXPRESS definition on an exchange file?

EXPRESS definition

Part 21

Instance on file

Data


Step file example

STEP file example

ISO-10303-21;

HEADER;

FILE_DESCRIPTION(('Transfer from NAPA to AP216L'), '2;1');

. . .

ENDSEC;

DATA;

. . .

#3080 = GLOBAL_ID('NAPA', ’SHIP111/A/DECK1-IDSHIP:moulded_form_design_definition ');

#3090 = SURFACE_SHAPE_REPRESENTATION('DECK1-MIDSHIP', (#3110), #3100, $ , $);

#3100 = REPRESENTATION_CONTEXT('DECK1-MIDSHIP', 'surface');

#3110 = FACE_BASED_SURFACE_MODEL('DECK1-MIDSHIP', (#3120));

#3120 = CONNECTED_FACE_SET('DECK1-MIDSHIP', (#3300));

#3130 = (BOUNDED_SURFACE() B_SPLINE_SURFACE(3, 3, ((#3140, #3150, #3160

, #3170), (#3180, #3190, #3200, #3210), (#3220, #3230, #3240, #3250)

, (#3260, #3270, #3280, #3290)), .UNSPECIFIED., .F., .F., .F.)

B_SPLINE_SURFACE_WITH_KNOTS((1, 1, 1, 1, 1, 1, 1, 1), (1, 1, 1, 1, 1

, 1, 1, 1), (0.0, 0.0, 0.0, 0.0, 1.0, 1.0, 1.0, 1.0), (0.0, 0.0, 0.0

, 0.0, 1.0, 1.0, 1.0, 1.0), .UNSPECIFIED.)

GEOMETRIC_REPRESENTATION_ITEM() RATIONAL_B_SPLINE_SURFACE(((1.0, 1.0

, 1.0, 1.0), (1.0, 1.0, 1.0, 1.0), (1.0, 1.0, 1.0, 1.0), (1.0, 1.0,

1.0, 1.0))) REPRESENTATION_ITEM('DECK1-MIDSHIP_1') SURFACE());

#3140 = CARTESIAN_POINT('DECK1-MIDSHIP_1_11', (47.5, -0.1, 2.0));

#3150 = CARTESIAN_POINT('DECK1-MIDSHIP_1_12', (55.447, -0.1, 2.0));

#3160 = CARTESIAN_POINT('DECK1-MIDSHIP_1_13', (63.393, -0.1, 2.0));

#3170 = CARTESIAN_POINT('DECK1-MIDSHIP_1_14', (71.34, -0.1, 2.0));

#3180 = CARTESIAN_POINT('DECK1-MIDSHIP_1_21', (47.5, 5.198, 2.0));

#3190 = CARTESIAN_POINT('DECK1-MIDSHIP_1_22', (55.447, 5.198, 2.0));

. . .


Express and part 21

EXPRESS and Part 21

In common:

  • ISO standards

  • application independent

  • same character set

  • defined using Wirth Syntax Notation

Differences:

ExpressPart 21

data typesinstances

stablechanging


Express data in database

appl.

1

appl.

2

DB

appl.

3

EXPRESS data in database

EXPRESS

schema

S

D

A

I

S

D

A

I

calls

code


Step translator architecture

EXPRESS

schema 3

EXPRESS

schema 2

EXPRESS

schema 1

late binding

late binding

S

D

A

I

S

D

A

I

S

D

A

I

S

D

A

I

E

x

p

o

r

t

I

m

p

o

r

t

DB

DB

calls

STEP-physical file

calls

code

code

STEP translator architecture


Data harmonization

DATA HARMONIZATION


Emergency response salvage operations ers data sheets technical data

Harmonization of Standards for Data Exchange

  • Harmonization provides a mechanism to improve the interoperability of standards.

  • Harmonization collects semantic data which may support the convergence of standards for the exchange of data

  • Harmonization efforts initiated in the early 90’s.

  • Basic Semantics Register (BSR) of the ISO setup in 1995.

  • Product and Business Data Harmonization (PBDH) project of CEN/ISSS to promote harmonization of STEP and EDIFACT standards


Emergency response salvage operations ers data sheets technical data

Some goals of the PBDH project (1)

  • Build a repository in a human processable format termed the Common Object Repository -whereby the format is not important, only the content.

  • Objects should be above code level and below message level.

  • Focus on industry implemented standards, which are actually used to make a first population of the repository- EDIFACT & STEP.

  • Focus on objects, which are likely to be reusable in the same or other environments.


Emergency response salvage operations ers data sheets technical data

Some goals of the PBDH project (2)

  • Work on a step by step basis at a technical level to alleviate any political obstacles and the tasks.

  • Utilise existing implemented standards as the basis for deriving the repository content. These can be placed in the repository for reuse in different environments (e.g. different syntaxes, applications)

  • If needed, the repository entities can be mapped to the appropriate representation (e.g. EDIFACT, STEP, SGML, etc, and these relationships / bridges should be recorded. Guidelines for the bridging have to be established.


Emergency response salvage operations ers data sheets technical data

STEP

UN/EDIFACT

PBDH-Harmonization Area

S.W.I.F.T.

Others

XML-EDI

Overlap between STEP and UN/EDIFACT

ANSI ASC X12

ISO Central Register BSR

Harmonization of Standards for Data Exchange


Emergency response salvage operations ers data sheets technical data

XML


Emergency response salvage operations ers data sheets technical data

Newest web technology: XML

  • XML: eXtensible Markup Language.

  • Markup language for documents containing structured information. It is based on SGML (Standard Generalized Markup Language, ISO 8879).

  • Developed under the auspices of the W3C (World Wide Web Consortium).

  • Designed to make it easy to interchange structured documents and data over the Internet.

  • Structure of XML files can be defined using Document Type Definitions (DTDs)

  • Layout is defined using Style Sheets: Cascading Style Sheets (CSS) and eXtensible Style Sheet Language (XSL)


Emergency response salvage operations ers data sheets technical data

XML/EDI

  • XML/EDI is a fusion of five technologies:

    • XML

    • EDI

    • Templates

    • Web agents

    • Repository.


Emergency response salvage operations ers data sheets technical data

XML/EDI concepts (1)

  • is built on open standards

  • provides for self-describing transactions products

  • allows tool vendors to build on existing products

  • can be integrated with traditional EDI methods

  • can be used with all standard internet transport mechanisms (IP routing, HTTP, FTP and SMTP)

  • Uses modern programming tools such as Java and ActiveX to allow data to be shared between programs

  • framework uses evolving best of breed philosophy - i.e. dynamic shared dictionaries


Emergency response salvage operations ers data sheets technical data

XML/EDI concepts (2)

  • will allow for object-based documents - data & rules reside together

  • provides the organization path to move down to a document-centric environment

  • enables more flexible business models (Rules/Agents)

  • cheaper and easier to implement than traditional EDI

  • access to a fair wider number of trading partners

  • Security, reliability and robustness

  • interactive transactions enabled by the web, not just “system” or “batch” transactions.

  • Will be the native language for the next generation of most of the popular web browsers.


Emergency response salvage operations ers data sheets technical data

XML and STEP

  • Need for linking together product documentation and product data (i.e. documentation references product data and is dynamically modified as the data changes over time; documentation itself as part of the product)

  • Ongoing STEP/SGML harmonization under ISO TC184/SC4

  • Work Item: “Preliminary Work Item on SGML and Industrial Data”

  • New Work Item: “An XML representation of EXPRESS-driven data”

  • Use of XML for encoding both EXPRESS schema definition and the instance data that conforms to that schema (Part 21).

  • STEP to become “Web-enabled” through XML


Emergency response salvage operations ers data sheets technical data

XML to EXPRESS mapping

  • Definition of XML constructs which represent the semantic of EXPRESS

  • First demonstrations presented during the STEP meeting in June 1998

    Some mapping examples:

SCHEMA geometry;

...

END_SCHEMA

SCHEMA map;

USE FROM geometry (point AS map_reference);

...

END_SCHEMA;

ENTITY point;

x_coord: REAL

y_coord : REAL

END_ENTITY

EXPRESS

<schema name="geometry">

...

</schema>

<schema name="map">

<usefrom href="#geometry" entity="point"

alias="map_reference"/>

...

</schema>

<entity name="point">

<attribute name="x_coord">

<REAL/>

</attribute>

<attribute name="y_coord">

<REAL/>

</attribute>

</entity>

XML


Emergency response salvage operations ers data sheets technical data

Conclusions

  • MARVIN processes require both Business and Product Data to be exchanged between partners

  • EDIFACT standard was designed for the exchange of business data and is today the most used technology for doing e-commerce in the world.

  • STEP standard was developed for the exchange of Product Data.

  • Harmonization efforts for both type of data have been done on basis of data repositories (BSR, PBDH)

  • Existing specialized sub-standards for both STEP and EDIFACT in the maritime/shipbuilding industry

  • Existing approaches for using both standards simultaneously (CONDRA, ENGDAT, ETP)

  • New Web XML technology can be combined with both standards to make them “web-enabled”.


Emergency response salvage operations ers data sheets technical data

Sources of Information (1)

  • UN/EDIFACT & STEP: Electronic Data Interchange for Business and Product Data. http://www.c-lab.de/~wolfgang/edi/index.html

  • UN/EDIFACT Standardshttp://www.harbinger.com/resource/edifact/

  • Henry's Yellow UN/EDIFACT Book: Introduction to UN/EDIFACT Messageshttp://www.harbinger.com/resource/henry/

  • UN/EDIFACT D.97A Download directoryhttp://www.unicc.org/unece/trade/untdid/d97a/Welcome.html

  • Use of the UN Electronic Data Interchange for Administration, Commerce and Transport Standard (UN/EDIFACT)http://www.unece.org/trade/rec/rec25en.htm


Emergency response salvage operations ers data sheets technical data

Sources of Information (2)

  • STEP documents and information http://www.nist.gov/sc4/www/stepdocs.htm

  • European Maritime STEP Association:http://www.oss.dk/emsa/

  • Information on STEP and EXPRESS: http://www.epmtech.jotne.com/learn/index.html

  • PBDH Project:http://pbdh.ecworkshop.org/

  • Data Standards Integration Comitee:http://cals.emsi.com/ISG/DSIC/DSIC.HTM/

  • Product DataTechnology Advisory Group:http://www.cadlab.tu-berlin.de/~PDTAG/

  • EDIMAR project:http://www.biba.uni-bremen.de/projects/edimar/


Emergency response salvage operations ers data sheets technical data

Sources of Information (3)

  • The XML resource guide: http://www.xml.com/xml/pub/listrescat

  • W3C XML 1.0 recommendation: http://www.w3.org/TR/REC-xml

  • The SGML/XML Web page: http://www.oasis-open.org/cover/xmlIntro.html.

  • Introducing XML/EDI: http://www.geocities.com/WallStreet/Floor/5815/start.htm

  • Guidelines for using XML for Electronic Data Interchange:http://www.geocities.com/WallStreet/Floor/5815/guide.htm

  • The european XML/EDI pilot project:http://www.cenorm.be/isss/Workshop/ec/xmledi/isss-xml.html

  • STEP/XML Knowledge Base: http://www.rivcom.com/k06.htm


  • Login