Intake 4-12-2015 + Kick-off 15-1-2016

Maak een Begin. Het is Gratis
of registreren met je e-mailadres
Rocket clouds
Intake 4-12-2015 + Kick-off 15-1-2016 Door Mind Map: Intake 4-12-2015 + Kick-off 15-1-2016

1. Present

1.1. Leendert van der Waal (Wienerberger)

1.2. Paul Oudenhooven (Acterus)

2. Why the request for [email protected] in de Bouw export format?

2.1. HIBIN requests

2.2. A direct connections with 4some of these customers is requested

2.2.1. Why?

2.2.1.1. Wienerberger strongly beliefs that more, fast and correct product information will become a requirement to maintain and grow their market position.

2.2.1.1.1. Consequence: expected loss of market share

2.2.1.1.2. Wienerberger customers do not have correct and up to date information

2.2.1.1.3. Branch organisations (like HIBIN) advise to communicate with one standard.

2.2.1.1.4. Is not YET a requirement in order to purchase products at Wienerberger

2.2.1.1.5. Wienerberger expects that this standard will become the leading communication standard in their branch

2.2.2. What for?

2.2.2.1. This is to be the first stap towards automatic ordering

2.2.2.1.1. First one format, then automatic ordering of products

2.2.2.2. To be used for these customers in their ERP systems.

2.2.3. How?

2.2.3.1. Wienerberger landscape

2.2.3.2. Not yet defined how Wienerberger customers need this information

2.2.3.2.1. Push

2.2.3.2.2. Pull

2.2.3.2.3. Automatic

2.2.3.2.4. Manual

3. For who [email protected] in de bouw?

3.1. Market:

3.1.1. Netherlands

3.2. Target group:

3.2.1. Independent. The [email protected] in de bouw standard should be used to communicate different product portfolio's (depending on user groups)

4. To-Do

4.1. Wienerberger (deadline: week 50)

4.1.1. Describe the (max 3) user scenario's for communicating product information with the [email protected] in de bouw standard (se 'how')

4.1.1.1. Who

4.1.1.2. Uses what information

4.1.1.3. For what

4.1.1.4. What information is used

4.1.1.5. What are the variables

4.2. Acterus (deadline: week 50)

4.2.1. Research [email protected] in de bouw format

4.2.1.1. The different files

4.2.1.1.1. 1. Product bestand

4.2.1.1.2. 2. Artikel bestand

4.2.1.1.3. 3. Conditiebericht

4.2.1.2. Format of the xml message

5. Which information to communicate?

5.1. 1. Product bestand

5.1.1. Bijv, pindakaas

5.2. 2. Artikel bestand

5.2.1. Bijv. pot pindakaas 250 gram

5.2.1.1. GLN, GTIN, SKU's, prijzen

5.2.1.1.1. LW stuurt info van [email protected] in de Bouw toe

5.3. 3. Conditiebericht

5.3.1. LW: deze niet

6. Next meeting

6.1. 18-12-2015

7. Huidige situatie

7.1. Voor 1 klant

7.1.1. Veris

7.1.1.1. Hebben zijn nog voor ons lijstprijzwn = bruto adviesprijs

7.1.1.1.1. Assortiment prijslijst/IB = exact hetzelfde assortiment

7.1.1.2. Veris gebruikt gegevens voor in hun eigen ERP-systeem. Willen ze graag op deze manier, want klant moet inhoud zelf nog aanpassen (doet 1 mannetje: Michiel Blans - Hoofd artikelbeheer)

7.2. Verwachting is dat meer klanten deze wens zullen gaan krijgen

7.3. Wij sturen hen

7.4. Zij gebruiken EZ Base, maar niet voor publieke doeleinden