OASIS Universal Business Language (UBL) TC

 View Only
  • 1.  Swim lane diagrams in the hub document

    Posted 01-25-2013 22:32
    I am working more on the hub document today and I'm looking at the diagrams ... please see the November version of the hub document here: https://www.oasis-open.org/committees/download.php/47370 (1) Missing document types In the collaborative planning, forecasting, and replenishment swim-lane diagrams, there is no flow that illustrates the use of either the ItemInformationRequest document or the PerformanceHistory document. I think these are the only documents (except for the general DocumentStatusRequest, DocumentStatus and AttachedDocument documents) not included in any of the swim-lane diagrams in the hub document. Is it important to update the diagrams with their inclusion? I think so. (2) Figure 57 in section 2.14.3.3 There is a document type box labelled "Change Order Response" and we don't have such a document type in the package. I'm progressing with producing the draft package for sanity review, but I would like this issue addressed before we create the package for voting, please. Thank you! . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal


  • 2.  Re: [ubl] Swim lane diagrams in the hub document

    Posted 01-26-2013 03:43
      |   view attached
    well spotted. I have put suggestions below. If we dont here to the contrary by early next week lets go with this. On 26/01/13 6:32 AM, G. Ken Holman wrote: I am working more on the hub document today and I'm looking at the diagrams ... please see the November version of the hub document here: https://www.oasis-open.org/committees/download.php/47370 (1) Missing document types In the collaborative planning, forecasting, and replenishment swim-lane diagrams, there is no flow that illustrates the use of either the ItemInformationRequest document or the PerformanceHistory document. I think these are the only documents (except for the general DocumentStatusRequest, DocumentStatus and AttachedDocument documents) not included in any of the swim-lane diagrams in the hub document. Is it important to update the diagrams with their inclusion? I think so. I would suggest ItemInformationRequest should be shown as the trigger for 'Create Sales Forecast' (go on the top of Figure 33). It would be sent by the Seller to the Buyer. So the diagram needs updating. As for PerformanceHistory it was original part of the VMI model (not CPFR) but I cannot see how this differs from ProductActvity and suspect it is now redundant (been replaced by Product Activity when the processes were harmonized). So we should drop PerformanceHistory document type from the package and not update any diagrams. (2) Figure 57 in section 2.14.3.3 There is a document type box labelled "Change Order Response" and we don't have such a document type in the package. I think it should just say "Order Response". Diagram needs updating. I'm progressing with producing the draft package for sanity review, but I would like this issue addressed before we create the package for voting, please. Thank you! . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php begin:vcard fn:Tim McGrath n:McGrath;Tim org:Document Engineering Services email;internet:tim.mcgrath@documentengineeringservices.com title:Managing Director tel;work:+61893352228 tel;home:+61438352228 tel;cell:+61438352228 url:www.documentengineeringservices.com version:2.1 end:vcard

    Attachment(s)

    vcf
    tim_mcgrath.vcf   287 B 1 version


  • 3.  Re: [ubl] Swim lane diagrams in the hub document

    Posted 01-26-2013 16:12
    At 2013-01-26 11:42 +0800, Tim McGrath wrote: well spotted. I have put suggestions below. If we dont here to the contrary by early next week lets go with this. I'm trying to prepare the "sanity version" this weekend. I don't want to delay the process any further by putting off this important preview of the review version. On 26/01/13 6:32 AM, G. Ken Holman wrote: In the collaborative planning, forecasting, and replenishment swim-lane diagrams, there is no flow that illustrates the use of either the ItemInformationRequest document or the PerformanceHistory document. I would suggest ItemInformationRequest should be shown as the trigger for 'Create Sales Forecast' (go on the top of Figure 33). It would be sent by the Seller to the Buyer. So the diagram needs updating. Who is responsible for this diagram and when can they get a revision to me? I will put the existing diagram in the "sanity version". As for PerformanceHistory it was original part of the VMI model (not CPFR) The hub document says it is involved in the process "Cyclic Replenishment Program" which led me to that incorrect conclusion. but I cannot see how this differs from ProductActvity and suspect it is now redundant (been replaced by Product Activity when the processes were harmonized). So we should drop PerformanceHistory document type from the package and not update any diagrams. I am removing it from the "sanity version" today. There is a document type box labelled "Change Order Response" and we don't have such a document type in the package. I think it should just say "Order Response". Diagram needs updating. I should be able to patch that diagram seamlessly. I will let it be know if I need to have it redrawn. If my conclusions are unacceptable, I'll produce a second preview version, but I'm going ahead with what I can today and await the artist of the drawing to get me the version to use for the actual review. . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal


  • 4.  Re: [ubl] Swim lane diagrams in the hub document

    Posted 01-27-2013 03:31
      |   view attached
    i agree these are things we can fix in the disposition of PRD3. On 27/01/13 12:10 AM, G. Ken Holman wrote: At 2013-01-26 11:42 +0800, Tim McGrath wrote: well spotted. I have put suggestions below. If we dont here to the contrary by early next week lets go with this. I'm trying to prepare the "sanity version" this weekend. I don't want to delay the process any further by putting off this important preview of the review version. On 26/01/13 6:32 AM, G. Ken Holman wrote: In the collaborative planning, forecasting, and replenishment swim-lane diagrams, there is no flow that illustrates the use of either the ItemInformationRequest document or the PerformanceHistory document. I would suggest ItemInformationRequest should be shown as the trigger for 'Create Sales Forecast' (go on the top of Figure 33). It would be sent by the Seller to the Buyer. So the diagram needs updating. Who is responsible for this diagram and when can they get a revision to me? I will put the existing diagram in the "sanity version". As for PerformanceHistory it was original part of the VMI model (not CPFR) The hub document says it is involved in the process "Cyclic Replenishment Program" which led me to that incorrect conclusion. but I cannot see how this differs from ProductActvity and suspect it is now redundant (been replaced by Product Activity when the processes were harmonized). So we should drop PerformanceHistory document type from the package and not update any diagrams. I am removing it from the "sanity version" today. There is a document type box labelled "Change Order Response" and we don't have such a document type in the package. I think it should just say "Order Response". Diagram needs updating. I should be able to patch that diagram seamlessly. I will let it be know if I need to have it redrawn. If my conclusions are unacceptable, I'll produce a second preview version, but I'm going ahead with what I can today and await the artist of the drawing to get me the version to use for the actual review. . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php begin:vcard fn:Tim McGrath n:McGrath;Tim org:Document Engineering Services email;internet:tim.mcgrath@documentengineeringservices.com title:Managing Director tel;work:+61893352228 tel;home:+61438352228 tel;cell:+61438352228 url:www.documentengineeringservices.com version:2.1 end:vcard

    Attachment(s)

    vcf
    tim_mcgrath.vcf   287 B 1 version