電子コラボレーションビジネスに向けて

Size: px

Start display at page:

Download "電子コラボレーションビジネスに向けて"

さみかやぬま
5 years ago
Views:

1 ebxml

3 Electronic Data Interchange: Val ue Added Network: extensible Markup Language:

4 XML/E DI (H12) XML/EDI 1213 XML/EDI No XML B2B 2 XML/EDI XML/EDI ( )EDI XML/EDI WG 14 3

5 i

6 ii

7 iii

8 1 XML/EDI

9 2 TCP/IP TCP/IP

10 3 < > XML < > XML XML XML XML XML

11 AnytoAny 4

12 DO BUSINESS! ebxml ebxml Build System & 4 9 CPA 7 8 CPA 6 X7 10 ebxml BO Library 2 5 X X X X 11 ebxml BP Model 5

13 ebxml eb

14 2 ebxml

15 ebxml Requirement Specification Single Global Electronic Market 8

16 deliverables 9

17 Common Business Process Common Semantics 10

18 11

19 12

20 2-2 (1) (2) (3) 08 13

21 2-2 14

22 3 Open edi Reference Model ISO 14662, JIS X 7001 Business Operational View) Functional Service View) Business Process Unified Modeling Language 15

23 Actor 3-2 Business Transaction Commercial Transaction with Responding Business Document Query/Response Request/Response(Confirm) (Notification) 16

24 Information Distribution 3-2 Service-Service Agent-Service-Service Service-Service-Agent Service-Agent-Service Agent-Service-Agent 3-3 (Service-Service) OriginatingService RespondingService 1. request(businessaction) 1.1. signal(receiptacknow ledgement) 1.2. signal(acceptanceacknowledgement) 1.3. response(businessaction) signal(receiptacknow ledgement)

25 Core Component) context (Party) (Address) (Contact) (Charge) (Tax) (Classification Goods/Service) (Quantity) (Shipment Information) (Packaging) 18

26 19 Trading Partner Agreement Collaboration-ProtocolAgreement 3-4 Collaboration-Protocol Profile) Version No. Version No.

27 (Document) (Exe. Code) (Document) (Exe. Code) (Document) (Exe. Code) (Document) (Exe. Code)

28 21 From/To,TPA (Multipurpose Internet Mail Extensions) Repository

29 22 Collaboration-Protocol Profile) Registry Classification) ( )

30 23

32 UN/CEFACT ISV UN/CEFACT ISV

33 4-1 UMM. : 1) 2) :1), 2) EDIFACT /OO-EDI XML DTD/ ISV :1), 2) ISV :

34 4-3 Business Domain Expe rt (from Actors) Capture the Business Operations Maps Business Process Analyst (from Actors) Document the Requirements Message De signer (from Actors) Analyze the Requirements Design the Services and Information Models Technical Modeler (from Actors) Software De veloper (from Actors) Implement the Design including Designed Messages

35 4-4 Buyer Business Process and Information Models Request Catalog Register OrderProduct Ge t Pric e Quote Ge t Order Status Seller Re gu l ato ry Authority :Reque sti ngro le Document Reques t :Respo nd in grole <<Stereotype>> RespondingBusiness Activity START <<Stereotype>> Re questingbusiness Activity [SUCCESS] [CONTROLFAIL] END CONTROL FAILED : Ori g in at in g Service 1. request(bus in ess Act io n) 1.1. signal(receiptacknowledgement) ed gem ent 1.2. signal(acc ep t anc e Ack no wl ed gem ent ) 1.3. response(businessaction) s i gn al ( Rece i pt Acknowledgement) : Re sp on di ng Se rvice 28

37 Business Transaction Commercial Transaction with Responding Business Document Query/Response Request/Response(Confirm) (Notification) Information Distribution OriginatingService Re spondingservice 1. request( BusinessAction) 1.1. signal(receiptacknowledgement) 1.2. signal(acceptanceacknow ledgement) 1.3. response( BusinessAction) signal(receiptacknowledgement) 4-6 Service-Service Agent-Service-Service Service-Service-Agent Service-Agent-Service Agent-Service-Agent 4-6 (Service-Service) 30

38 31 5 ebxml (1) (2) (3) (4)

39 Specification Technical Report Reference White Paper Proof Of Concept BEA Systems Bind S ystems btrade.com Bowstreet CareData Commerce One Contivo Cyclone Commerce Data Access Tech. NTT communications Sun Microsystems Fujitsu NTT Data Sybase GE Mega Vi qui ty Covisint Sumsung SDS TIBCO IBM Savvion webmethods Intalio Schemantix XML Global IONA Seeburger XML S olutions IPNet Sterling Commerce 32

40 Business Process Core Component Collaboration-Protocol Agreement Registry and Repository Transport, Routing, and Packaging Business Process Specification Schema (1) (2) 33

41 Geography Industry Asia Europe N.America Retail Financial Health Care Japan Germany US A Buyer Seller cj1 cr1 cr2 Cpp-a(Fujitsu) Cpp-b(IONA) Seller Buyer Registry 2A Form CPA Contivo 1 Discover CPP 2 Receive CPP Sterling IONA IONA 3 Propose CPA BEA BEA

42 (1) (2) 5-3 Seller NetMarket Buyer Payment Authori ty Seller Bank Buyer Bank Clearing Bank Sumsung IONA IPNet C1 Covisint GE Fujitsu Seeburger IBM Sun XML Global Bow street Tibco 18 Seller NetMarket Buyer Payment Authori ty Seller Bank Buyer Bank Clearing Bank Sumsung IONA IPNet C1 Covisint GE Fujitsu Seeburger IBM Sun XML Global Bow street Tibco 18

43 5-3 (7) Sales Product Notification RosettaNet PIP2A1 (8) Product Catalog OAG BOD128 (9) Place Order OAG POBOD#3(Reliable Messaging) (10) Purchase Order ANSI vxxxx 850 (11) Purchase Order Ack ANSI vxxxx 855 (12) Place Order Ack OAG POA BOD #4 (13, 14) Advance Shipment Notice AIAG (15) Payment Authorization ebxmlcore Component (16, 17) Invoice & ACK ebxml Core Component (18) Settlement Authorization ebxmlcore Component (19) Payment Request SWIFT (20) Funds Transfer SWIFT (21, 22) Funds Transfer & ACK O FX (23) Statement OFX (1) (2) 36

44 (3) (1) (2) IONAMegaBind Systems (3) (1) (2) Enterprise Collaboration Architecture Data Access Tech. (3) (1) (2) 37

45 <SimpleCC UID="100001" Type="Text"> <Name>AbsoluteDate</Name> </SimpleCC> <SimpleCC UID="100002" Type="Text"> <Name>PaymentDate</Name> </SimpleCC> <SimpleCC UID="100003" Type="Text"> <Name>TaxValue</Name> </SimpleCC> <ComplexCC UID="100004"> <Name>PaymentTerms</Name> <EmbeddedCList> <EmbeddedC UID="100032"> <Name>PaymentTermType</Name> <Occurs Min="1"Max="1"></Occurs> </EmbeddedC> <EmbeddedC UID="100001"> <Name >Absolute Date</Name > <?xml version="1.0" encoding="utf-8"?> <!ELEMENT Invoice (InvoiceHeader,InvoiceDetails+,InvoiceSummary)> <!ATTLIST Invoice sectorusageversion CDATA #IMPLIED> <!ELEMENT InvoiceHeader (Invoi ce Type,Invoi cestatus,taxtreatment,discounttre atment?,invoi ce Tre atment,invoicenumber,invoicedate,taxpointdate?,currency,party*,paym ent?,ponum?,deliverynote Num?,Ref*,Date*,GenTe xt*)> <!ELEMENT InvoiceType (#PCDATA)> <!ATTLIST InvoiceType stdvalue ( ) '380' stdname (UNTDID:1001) 'UNTDID:1001'> <!ELEMEN T In voicestatus (#PC DATA)> <!ATTLIST InvoiceStatus stdvalue ( ) '9' stdname (UNTDID:1225) 'UNTDID:1225'> <!ELEMENT TaxTreatment (#PCDATA)> <!ATTLIST TaxTreatment stdvalue (NIL GIL NLL GLL NON) 'NLL' stdname (VISA:TAXT) 'VISA:TAXT'> <!ELEMENT DiscountTreatment (#PCDATA)>. (3) ebxml 38

46 6 ebxml BPM CCL EDIFAC T XML edocs 39

47 6-2 40

49 6-3 EDI EDI XML VPN

50 EDI B A

51 6-1 1ebXML TCA ROCBA ebxml MSG AFACT XML WG ebxml KIEC POC AFACT ebxml Web ECOM ebxml IT ebxml KIEC TCA MSG V2.0 ECOM UMM CC/BIE BIM 44

52 45

53 46 7 ebxml (TCP/IP) (TCP/IP)

54 47

56 7-1 AS P Web-EDI for JEITA Web-EDI for JEITA BtoB BtoB JEITA BP JEITA BP MSG ebxml MSH ebxml MSH SOAP ebxml SOAP BtoB BtoB JEITA JEITA BPMSG ebxml MSH ebxml MSH ebxml MSG SOAP SOAP 49

57 Reg/Rep BP BP Company A Company (Seller) A (Seller) Company B Company (Buyer) B (Buyer) BP Creation BP Registration BP Search Application & CPP Creation CPP Registration CPP Search CPA Creation CPA Sending CPA Acceptance BP Search Application Creation Business 50

58 Trading Partner A Trading Partner B Trading Partner C ebxml Service Provider Hub-to-HubH2H ebxml Service Provider Trading Partner P Trading Partner Q Trading Partner R Any Traditional Method ebxml Any Traditional Method Security CC BP Re gistry CPPA Future (BP, CC) Scope of PAA (MSG, CPPA, Registry) MSG 51

59 52

60 53

61 Swim Diagrams DTDs Processes Data Dictionary Data Vocabulary Dictionaries Implementation Framework Envelope & Security 54

62 8 CPP/CPA 8.1 (1) 8-1 (2) ebxml Process-Specification Document ebxml CPP/CPA (3) CPP/CPA 55

63 Buyer Service Seller Service 1. Request (PurchaseOrderRequestAction) 1.1. signal(receiptacknow ledgement) 1.2. response(purchaseorderconfirmationaction) signal(receiptacknow ledgement) 56

64 # Na me Time to Acknowledge Receipt Signal Time to Acknowledge A cceptance Signal Time to Respond to Action Included in Time to Perform Is Authorization Required? Is Non- Repudiation Required? Is Secure Transport Required? 1. Purchase Order Request Action 2 hrs N/A 24 hrs Y Y Y Y 1.1. Receipt Acknowledgment N/A N/A N/A Y Y Y Y 1.2. Purchase Order Confirmation Action 2 hrs N/A N/A Y Y Y Y Receipt Acknowledgment N/A N/A N/A N Y Y Y (1) Business Document Business Transaction 2 57

65 <ProcessSpecification xmlns= name="pip3a4requestpurchaseo rder"> <BusinessDocument name="p uchase O rder Request na mei D="Pip3A4PurchaseOrderRequest specif icationlocation="purchaseorderrequest.xsd"> </BusinessDocument> <B usine ssdocument name="puchase Order Confirmation" nameid="pip3a4purchaseo rderconfirmation specificationlocation="purchaseo rderconfirmation.xsd"> </BusinessDocument> <BusinessTransaction name="request Purchase Order" nameid="requestpurchaseorder_bt"> <RequestingBusinessActivity name="p urchase Order Request Action" nameid="purchaseo rderrequestaction isauthorizationrequired="true" isnonrepudiationrequired="true" timetoacknowledgereceipt="p0y0m0dt2h0m0s"> < DocumentEnvelope businessdocument="puchase OrderRequest businessdocumentidref="pip3a4p urchaseo rderrequest " /> </RequestingB usine ssa ctivity> <RespondingBusinessActivity name="p urchase Order Confirmation Action nameid="p urchaseorderconfirmationaction" isauthorizationrequired="true" isnonrepudiationrequired="true timetoacknowledgereceipt="p0y0m0dt2h0m0s"> <DocumentEnvelope businessdocument="purchase O rder Confirmation businessdocumentidref="pip3a4purchaseorderconfirmation" /> </RespondingBusinessA ctivity> </BusinessTransaction> <BinaryCollaboration name="request Purchase Order" nameid="requestpurchaseo rder_bc"> <InitiatingRole name="buyer" nameid="buyerid" /> <RespondingRole name="seller" nameid="sellerid" /> < Start tobusinessstate="request Purchase Order" /> <BusinessTransactionActivity name="request Purchase Order" nameid="requestpurchaseorder_bta businesstransaction="request Purchase O rder"businesstransactionidref="requestpurchaseorder_bt fromauthorizedrole="buyer" f romauthorizedrolei DRef ="BuyerId" toauthorizedrole="se lle r" toauthorizedroleidref="selle ri d" timetoperform="p0y0m0dt24h0m0s"/> </BinaryCollaboration> </ProcessSpecif ication>

66 <tp:collaborationprotocolp rofile xmlns:tp=" <tp:partyinfo tp:partyname="companya " tp:defaultmshchannelid="asy nccha nnela 1"> <tp:partyid tp:type="urn:oasis:names:tc:ebxml-cppa:partyid-type:duns"> </tp:partyid> <tp:partyref xlink:href=" nya.com/about.html" /> <tp:collaborationrole tp:id="buyerid"> <tp:processspecification tp:version="2.0" tp:name="pip 3A4RequestPurchaseO rder"xlink:type="simple xlink: href =" /> <tp:role tp:name="buyer" xlink: href =" /> <tp:servicebinding><tp:service> bpi d:icann:roset tanet.org: 3A 4$2.0</tp:Service> <tp:cansend> <tp:thispartyactionbinding tp:id="companya_abid1" tp:action="purcha se O rde r Reque st A ct ion tp:packageid="companya_requestpackage"><tp:channelid>asyncchannela1</tp:channelid> </tp:thispartyactionbinding> </tp:cansend> </tp:servicebinding> </tp:collaborationrole> <tp:deliverychannel tp:channelid="asyncchannela1" tp:transportid="transporta2 tp:docexchangeid="docexchangea1"> <tp:businesstransactioncharacteristics tp:isnonrepudiationrequired="true" tp:issecuretransportrequired="true tp:isauthorizationrequired="true" tp:timetoacknowledgereceipt="pt2h" tp:timetoperform="p1d" /> </tp:deliv ery Channel> <tp:transport tp:transportid="transporta2"> <t p:transport Sende r> <tp:transportprotocol tp:version="1.1">http</tp:transportprotocol> <tp:transportclie nt Se curity> <tp:transportsecurityprotocol tp:version="3.0">ssl</tp:transportsecurityprotocol> </t p:tra nsportclie nt Se curity> </tp:tra nsportse nder> </t p:tra nsport > <tp:docexchange tp:docexchangeid="docexcha ngea 1"> <tp:ebxmlsenderbinding tp:version="2.0"> <tp:reliablemessaging> <tp:retries>3</tp:retries> <t p:ret ryinterval>pt2h</t p:ret ryi nterva l> <tp:messageordersemantics>guaranteed</tp: Me ssa geo rde rse mantics> </tp:reliablemessaging> <tp: Sende rnonre pudiation> <tp:nonrepudiationprotocol> <tp:hashfunction> <t p: SignatureA lgorithm> </tp:sende rnonrepudiation> <tp:senderdigitalenvelope> <tp:digitalenvelopep rotocol tp:version="2.0">s/mime</tp:digitalenvelopep rotocol> <tp:encryptionalgorithm> DES-CB C</tp:Encry ptionalgorithm> </tp:sende rdigitalenvelope> </tp:ebxmlsenderbinding> </tp:docexchange> </tp:partyinfo> </tp:collaborationp rotocolprofile> 59

67 8.5 CPAA,B) Role element CPAId element Action element Ti metoli ve CPAElement /At tri bu te PartyId element ConversationId element Serviceelement MesageId PartyId element Role element Cpaid attribute in CollaborationProtocolAgreement element No equivalent; should be generate d above the MSI Serviceelement Action attribute in ActionBinding element Computed as the sum of Timestamp (in message header)+persistduration (under DocExchange element) No equivalent; generated by the MSH (Message Service Handler) per message

68 8-3 <SOAP:Envelope xmlns:soap= /> <SOAP:Header xmlns:eb= http// > <eb:messageheader id=" " eb:version="2.0" SOA P:mustUnderstand="1"> <eb:from><eb:partyid> </eb:PartyId></eb:From> <eb:to> <eb:partyid eb:type="some Type "> </eb:PartyId> <eb:role> </eb:to> <eb:cpaid> uri:companya-and-companyb-cpa</eb: CPAId> <eb:conversationid> </eb:ConversationId> <eb:service eb:type= any URI">bpid:icann:rosettanet.org:3A4$2.0</eb:Service> <eb:action>purchase Order Request Action</eb:Action> <eb:messagedata> <eb:messageid> UUI D-2</eb:MessageId> <eb:timestamp> t12:19:05</eb:timestamp> <eb:ref ToMessageId> UUID-1</eb:RefToMessageId> </eb: MessageData> <eb:duplicateelimination/> </eb: Me ssage Hea der> </SOA P:Hea de r> <SOAP:Body xmlns:eb= http// <eb:manifest eb:version= 2.0 > ---- </eb: Manif ast> </SOA P:Body> </SOA P:Envel ope > 61

69 62

70 1 _ 63

71 64

72 65

73 66

74 67

75 68

76 69

77 70

78 71

79 72

80 73

81 74

82 75

83 76

84 77

85 78

86 79

87 80

88 81

89 82

90 83

91 84

92 85 2XML/EDI (1) XML/EDI XML/EDI

93 86

94 (2) XML/EDI XML/EDI

95 3 4 5 (1) 1/281/30 OASIS ebxml CPPA TC (2) 2/48 UN/CEFACT ebtwg ebtwg UN/CEFACT TMWG (3) H13 H14 (4) H13 EDI 1 88

96 2 3 89

99 92

100 3XML/EDI (1) XML/EDI XML/EDI 93

101 94 EDI

102 95 (2) XML/EDI XML/EDI 1 1 XML/EDI EDI XML/EDI EDI XML/EDI (ebxml) ebxml

103 2 3 4 XML/EDI WG EDI SWG SWG 2 JEDIC EDI 1 XML/EDI 3 ebxml ebxml Proof-of-Concept 1 TMWG (7/1620) TMWG UN/CEFACT 6 1 TMWG EDI UML( ) edi UN/CEFACT UML edi (UN/CEFACT Modeling Methodology) TMWG 2 EDI SWG EDI CII EDI EDI 3 SWG ebxml 4 3 ebxml 5 EDI 1 UN/CEFACT EWG UN/CEFACT ebxml 22 ( )EDI SWG 32 SWG 4XML/EDI Business 5AFACT ebxml 6 XML/EDI < > XML/EDI ()< >( 150 ) XML/EDI 1 ( ) ( 300 ) XML/EDI 2 8 ()< >( 150 ) (1) (11) 5 9 TMWG(Technology & Methodology WG) UN/CEFACT Modeling 96

104 5 Methodology(UMM) (H13) (2)3 EDI SWG EDI EDI (3)3 SWG Open Travel Alliance ebxml (4) ebxml ebxml (5) XML/EDI (1) 1/281/30 OASIS ebxml CPPA TC (2) 2/48 UN/CEFACT ebtwg ebtwg UN/CEFACT TMWG (3) (H13)12 (H14)2 (2 ) XML/EDI IT (4)WG H13 XML/EDI EDI

105

106

107 5 (1) NTT EDI Web 10 (2) TEDI TEDI (3) SWG () 100

108 TEL F TEL

ebXML相互接続テスト

ebXML相互接続テスト XML Week ebxml 2003530 ECOM( ) ebxml SWG ()NTT Copyright 2003 ECOM, NTT DATA CORPORATION Agenda ebxml ebxml ebxml SWG ebxml 1 Copyright 2003 ECOM, NTT DATA CORPORATION ebxml UN/EDIFACT XML/EDI Create a