Relationship Dependent Data _RDD

Document Sample
Relationship Dependent Data _RDD Powered By Docstoc
					          Breakout 4:
 Relationship Dependent Data
(RDD): What’s Happening with
Price/Promotion Synchronization

       4:00 PM - 4:45 PM
          April 3, 2006

          Carolyn Kroll
            1SYNC
               Agenda
• History of the GSMP Price Standard
• Current Status of the GSMP Price
  Standard
• Timeline for Syncing Price in the GDSN
• Getting Started
• Appendix: Details of the GDSN Pricing
  Model
History
Many Are Already Exchanging Price
 EDI          XML           Proprietary          Industry Pain
                                           • Multiple one off solutions
                                              – Custom build per
 Trading      Trading          Trading           implementation:
 Partner 1    Partner 2        Partner 3         expensive and resource
                                                 intensive
                                              – All requirements are not
                                                 addressed
                                              – No significant adoption
                                                 of one standard




                                                    Solution
                                           • Harmonize the requirements
                                             in all the message types and
                                             provide one standard based
 2-Tier DSD    3-Tier DSD     Warehouses     solution
    Benefits of Harmonizing on 1
        Standard for Price
•   Reduce invoice discrepancies
•   Improve order accuracy and process
•   Streamline check-in process
•   Execute against promotional events
•   New item setup and execution
  How Does Price Sync Fit Into the
       GDSN Landscape?
1. Party Sync = Who
  •   No current activity, but trying to regroup
2. Item Sync = What
  •   Implemented within GDSN
3. Item Authorization = Where
  •   GDSN pilot in progress, with certification in
      Q2’06
4. Price Sync = How Much
  •   GDSN pilot in Q4’06, with certification in Q1’07 or
      Q2’07
          The Path to the Standard
Approved Standards                   Approved Standards
•  Price                             •  Business
                                        Requirements
•  Price Bracket
                                        approved

   2002                                  2004
                     2003                                       2005 - 2006
               CR# 03-000045                              Develop Standards
               •  Component Based                         •  Message Choreography
                  Pricing                                 •  Sync List Requirements
               •  Price Sync (inside &                    •  Validations
                  outside GDSN)                           •  Move to 1 Message Doc
          Why the Long Timeline?
• The standard incorporates global requirements
  from all verticals and business models
  •   Sync transaction price or components
  •   Sync my catalog of bracket prices
  •   Sync targeted promotion and allowance activity
  •   Sync line item & invoice-level components
  •   Sync at corporate level, at division level, at store
  •   Sync rate, percent, or amount, along with the
      calculation sequence
• Success includes establishing a comfort level
  with security, auditing, and trace-ability
3 Elements of the Prior Model
   Condition Document & Monetary Document
      Business Requirements Document




Conditions      Partner Profiles   Amounts & Values




            Trading Partner Profile
       Business Requirements Document
     GDSN Analysis Feedback
• Difficulty finding pilot partners for the 3
  message model
• Architectural analysis suggested that a 1
  message model might reduce the complexity
  of the 3 message model
• GS1 Australia, GS1 Canada and GS1
  Columbia have experience with price
  synchronization using 1 message
• Adoption of the crawl phase would provide
  less functionality then currently exists and
  would be viewed as a step backwards.
   1 Message Proposed - Why?
• Experience could be demonstrated
• The bar for CRAWL could be raised
• Better integration: Easier to compose, transmit, interpret and
  store than to receive multiple documents to re-assemble
• Compatible with existing price activity
    • 1) GS1 Australia, Canada and Colombia have implemented a
      single message price sync
    • 2) American c-stores have implemented PCATS single message
      price sync. Work is underway to harmonize PCATS with GDSN
      standards.
• Easier for EDI users to understand
Current Status
 Revised Phase 1 “Crawl” Has
       Broader Scope
Price synchronization in the crawl phase will include the
following pricing components:

              •   Simple transactional pricing
              •   Bracket pricing
              •   Allowances & Charges
              •   Promotions
      Overview of Pricing Model
                         • Defines unique pricing document identifier
Price Synchronization
                         • Describes a specific trading partner relationship
       Header



Relationship Segment      • Provides specific information about the trading partner relationship


                          • Communicates a price related component
  Condition Segment       • Can define a summary level condition, example: swell allowance
                          • Can define a line item depiction for a bracket component



Item Depiction Segment    • Communicate the Catalog Item pertaining to the price component


                          • Communicates a price related component
   Item Price Type
                          • Used to define line item depictions
      Segment
                          • Defines allowances or charges
      Consolidate to 1 Message:
         Accomplishments
•   Developed Message Choreography
•   Defined Data Pool Sync Lists
•   Determined Validation Requirements
•   Applied Sequencing Rules to Business
    Use Cases
      Consolidate to 1 Message:
       Remaining Deliverables
•   Change Tracking Requirements
•   Pilot Test Specifications
•   Implementation Guide & Best Practices
•   Security Requirements
Timeline
                           GDSN Price Schedule
                                                                                        May 8
                Optional Certification:                                             Draft Standards
                                                                                     Available For
                Price Sync:                   Jan 2007                           Development & Piloting


 2006                                                                    2007
 Apr    May   Jun    Jul    Aug       Sep   Oct      Nov       Dec       Jan    Feb   Mar   Apr May



               Development of Pilot
                Specifications and
              Implementation Guide




                                                                         Cert
Price Sync          Data Pool                          Pilot
 Standard         Development /
                                                               eBallot
Delivered                                           Pilot
               Minimum Four Months                Feedback
                           GDSN Price Schedule
                      Optional Certification:
                      Price Sync:                   April 2007
                                                                                May 8
                                                                            Draft Standards
                                                                             Available For
                Gates                                                    Development & Piloting


 2006                                                          2007
 Apr    May   Jun    Jul    Aug       Sep    Oct   Nov   Dec   Jan     Feb      Mar         Apr May




                                                                                             Cert
Price Sync     Development of Pilot              Data Pool               Pilot
 Standard       Specifications and             Development /




                                                                                  eBallot
Delivered                                                              Pilot
              Implementation Guide          Minimum Four Months      Feedback
Getting Started
                    Getting Started
• Begin building your company’s ROI
   • Utilize available tools
       • GMA, “Invoice Accuracy: 2002 Industry Survey & Benchmarks”
       • GDS Launch Pad provides a business calculator and a business case
         development tool (www.gdslaunchpad.com)
       • GCI “Global Data Synchronisation at Work in the Real World Illustrating
         the Business Benefits” provides sample KPIs and critical success
         factors
   • Include KPIs that will be used to track your progress
• Obtain senior-level sponsorship
   • Address security and transparency issues
   • Obtain buy-in from both business and technology
   • Incorporate KPIs into performance reviews
      Getting Started (continued)
• Mobilize your organization
   • Designate project champion and create charter
   • Provide strong project management/project manager
   • Manage Change
       •   Project structure: Phased implementation plan
       •   Business process change: Involve users
       •   People: Find and reward those who will make a positive contribution
       •   Team Structure: Qualified people who can dedicate time
       •   Communications: Lots of them
• Success Factors
   • Choose a data sync partner who has built and maintains the
     highest level of security
   • Ensure that you have a solid business plan, senior level support,
     and qualified, dedicated resources to make it happen
   • Monitor progress and reward success
      Getting Started (continued)
• Other
  •   Consider Participating in the GDSN pilot
  •   Understand the data model and the attributes
  •   Begin locating and cleaning your data
  •   Talk to your data pool
      • Data Pool implementation plans
      • Timing
      • Structure of “out-of-network” supplier and retailer connections
Overcoming Barriers to Adoption
• Waiting for an ideal standards-based
  solution
• Security
  • “Someone is going to access my data who
    shouldn’t”
  • “A 3rd party will send my data to wrong
    place”
  • “Price & Promotion sync will shift the
    balance of trading power”
                Questions?

Further Information:
•http://eroom.uc-council.org/eRoom/facility/GSMPRDD-
 GDSNIndustryRequirementsTeam

Contact Information:
•Ckroll@1sync.org
Appendix: The GDSN
  Price Sync Model
        Overview of Pricing Model
                         • Defines unique pricing document identifier
Price Synchronization
                         • Describes a specific trading partner relationship
       Header



Relationship Segment      • Provides specific information about the trading partner relationship


                          • Communicates a price related component
  Condition Segment       • Can define a summary level condition, example: swell allowance
                          • Can define a line item depiction for a bracket component



Item Depiction Segment    • Communicate the Catalog Item pertaining to the price component


                          • Communicates a price related component
   Item Price Type
                          • Used to define line item depictions
      Segment
                          • Defines allowances or charges
 Overview of Pricing Model
                  Price Synchronization Header




        Document Header - [1] Mandatory for each Price    Key
M/O/C
        Document                                         Field
 M      Price Document ID                                 No
 M      Relationship ID                                   No
 M      Information Provider                              No
 M      Party Receiving Private Data                      No
 O      Price Document Type                               No
         Overview of Pricing Model
                          Relationship Segment


        Optional Segment – Must be sent once to     Key
M/O/C
        establish a trading partner relationship   Field
 M      Relationship ID                            YES
 M      Relationship Action Code                    No
 M      Relationship Effective Start Date           No
 O      Relationship Effective End Date             No
 M      Information Provider                        No
 M      Party Receiving Private Data                No
 M      Business Location                          Yes
 M      Target Market Country Code                 Yes
 M      Trade Channel                              Yes
 M      Currency                                   Yes
Overview of Pricing Model
                        Relationship Segment




M/O/   Optional Segment – Must be sent once to            Key
 C     establish a trading partner relationship          Field
 O     Price Synchronizaiton Relationship Name            No
 O     Additional Party Identification (sender)           No
 C     Additional Party Identification Type (sender)      No
 O     Additional Party Identification (recipient)        No
 C     Additional Party Identification Type (recipient    No
 O     Incoterm Code                                      No
 C     Incoterm Code Location                             No
        Overview of Pricing Model
                          Condition Segment


        Optional Segment – Repeatable within a price    Key
M/O/C
        document                                       Field
 M      Condition ID                                   YES
 M      Condition Action Code                           No
 M      Condition Effective Start Date                  No
 C      Condition Effective Start Date Context          No
 O      Condition Effective End Date                    No
 C      Condition Effective End Date Context            No
 M      Condition Type                                  No
 M      Condition Name                                  No
 C      Condition Value Type                            No
 O      Condition Value                                 No
        Overview of Pricing Model
                            Condition Segment


        Optional Segment – Repeatable within a price            Key
M/O/C
        document                                               Field
 C      Condition Value Qualifier                               No
 O      Condition Value Cap                                     No
 O      Condition Value Basis Quantity                          No
 C      Condition Value Basis Quantity UOM                      No
 C      Condition Application Sequence                          No
 C      Information Provider                Can provide list    No
                                            Of Catalog Items
 O      Global Trade Item Number                                No
 C      Target Market Country Code                              No
 O      Target Market Subdivision Code                          No
 O      Classification Category Code                            No
           Provide either
           Catalog Item
           or Class Code
 Overview of Pricing Model
                        Condition Segment




        Bracket Qualifier Subclass: Optional and    Key
M/O/C
        Repeatable within each condition segment   Field
 C      Bracket Tier Minimum                        No
 O      Bracket Tier Maximum                        No
 C      Bracket Range Qualifier                     No
 O      Bracket Operator                            No
 Overview of Pricing Model
                      Item Depiction Segment




        Optional Segment – Repeatable within a price    Key
M/O/C
        document                                       Field
 M      Information Provider                            No
 M      Global Trade Item Number                        No
 M      Target Market Country Code                      No
 O      Target Market Subdivision Code                  No
        Overview of Pricing Model
                        Item Price Type Segment


        Mandatory Segment – Repeatable within each    Key
M/O/C
        item depiction segment                       Field
 M      Price Type ID                                YES
 M      Price Action Code                             No
 O      Reason for Price Action                       No
 O      Parent Catalogue Item                        Yes
 M      Price Type                                    No
 O      Price Type Name                               No
 M      Price Type Effective Start Date               No
 C      Price Type Effective Start Date Context       No
 O      Price Type Effective End Date                 No
 C      Price Type Effective End Date Context         No
        Overview of Pricing Model
                      Item Price Type Segment


        Mandatory Segment – Repeatable within each    Key
M/O/C
        item depiction segment                       Field
 M      Distribution Method                          Yes
 O      Target Market Subdivision                    Yes
 O      Business Location (Ship To)                   No
 O      Business Location (Ship From)                 No
 O      Alternate Location Grouping                   No
 O      Target Condition ID                           No
 O      Target Price Type ID                          No
 M      Price Value                                   No
 O      Price Value Cap                               No
 M      Price Value Type                              No
        Overview of Pricing Model
                      Item Price Type Segment


        Mandatory Segment – Repeatable within each    Key
M/O/C
        item depiction segment                       Field
 C      Price Value Qualifier                         No
 M      Price Basis Quantity                          No
 M      Price Basis Quantity UOM                      No
 O      Suggested Unit Retail Price                   No
 C      Suggested Unit Retail Price UOM               No
 M      Price Type Application Séquence               No
 O      Reference Document Identifier                 No
 O      Reference Document Description                No
 C      Reference Document Language                   No
 O      Performance Requirement Option                No
 Overview of Pricing Model
                     Item Price Type Segment


        Mandatory Segment – Repeatable within each      Key
M/O/C
        item depiction segment                         Field
 O      Performance Requirement Description             No
 C      Performance Requirement Description Language    No
 C      Performance Start Date                          No
 C      Performance End Date                            No

 O      Bracket Tier Minimum                            No
 O      Bracket Tier Maximum                            No
 O      Bracket Range Qualifier                         No
 O      Bracket Operator                                No

				
DOCUMENT INFO