Joris Ide filename convention

⚠️ Every product document must follow strict naming convention.

⚠️ Do not create a variation of that convention without refering to a PIM Manager.

⚠️ Special characters (ex : "à", "ï", "é", "è", "@", "(", ")") are not allowed. German characters are not allowed either. Only lowercase letters, hyphens and numbers are allowed.

⚠️ Every PIM document should start with "jri_".

Naming convention template:

Master files:

jri_productname_master_catalog_nolang_productid.ext

Catalog/Language specific files:

jri_productname_doctype_catalog_language_productid.ext

How to find a PIM ID number ?

Doctypes available in PIM environment:

• Asset (not used)

• Brochure (mkt)

• Certificate (tech)

• Coating_Sheet (mkt)

• Color_Flow (mkt)

• Fire_Resistance_Certificate (tech)

• Installation_Guide (mkt)

• Manual (not used - mkt)

• Other

• Packing_Details (mkt)

• Product_Sheet (mkt)

• Span_Table (tech)

• Technical_Drawing (compliance)

• Waranty (tech)

Used images in PIM

• Thematic Image field -> Hero Image used for the HIO = Hero image online: (ex:jri_ji-vulcasteel-roof-37-500_hio_017.jpg), extra info: resolution 3840 x 2160 @ 72dpi

• Gallery Images field (use always as first item in the gallery) -> PIO = Product image online: (ex:jri_ji-vulcasteel-roof-37-500_pio_017.jpg), extra info: resolution 1500 x 1500 @ 72dpi

• 3D Image -> FBX = 3D FBX file: (ex:jri_ji-vulcasteel-roof-37-500_fbx_017.fbx)

  Please click here for more info

• Main Image -> When a PIO image is uploaded to the Azure Hotfolder, the system will automatically generate an image with dimensions of 300 px in width and 300 px in height. The new image will keep the original filename, but will have "_300Wx300H" appended to it. For instance, 'jri_ji-vulcasteel-roof-37-500_pio_017.jpg' would become 'jri_ji-vulcasteel-roof-37-500_pio_017_300Wx300H.jpg'. This main image serves only as a thumbnail within the PIM.

Used doctypes in product tree structure

• tds = technical data sheet

(ex: jri_aquadrain-1500_tds_b2bfr_fr-fr_000000000000000003_04.pdf)

• tet = technical tables

  • tet-acoustic = Acoustic properties (ex: jri_ji-vulcasteel-wall-liner-profile_tet-acoustic_b2bbe-nl-be_020.xlsx)

  • tet-st-pressure = Span at wind pressure (ex:jri_ji-vulcasteel-wall-liner-profile_tet-st-pressure_b2bbe_fr-be_020.xlsx)

  • tet-st-suction = Span at wind suction (ex: jri_ji-vulcasteel-wall-liner-profile_tet-st-suction_b2bbe_fr-be_020.xlsx)

  • tet-td# = Technical Data (ex: jri_ji-z400_tet-td1-b2bbe_nl-be_073.xlsx)

  • tet-st-pouring = Maximum span during pouring phase (ex: jri_ji-60-160-800-pre-drilled_tet-st-pouring_b2bbe_nl-be_000000000000000370.xlsx)

  • tet-st-used-load# = Allowed load during use (ex: jri_ji-60-160-800-pre-drilled_tet-st-used-load1_b2bbe_nl-be_000000000000000370.xlsx)

  • tet-load-up = Safe upward load (ex: jri_ji-106-250-750-perfo_tet-load-up_b2bbe_nl-be_000000000000000024_02.xlsx)

  • tet-load-down = Safe downward load (ex: jri_ji-106-250-750-perfo_tet-load-down_b2bbe_nl-be_000000000000000024_02.xlsx)

  • st-static = Static properties (ex: jri_ji-106-250-750-perfo_tet-st-static_b2bbe_nl-be_000000000000000024_02.xlsx)

  • st-up= Safe span under upward load (ex: jri_ji-vulcasteel-roof-37-500_tet-st-up_b2bbe_nl-be_017.xlsx)

  • st-down = Safe span under downward load (ex: jri_ji-vulcasteel-roof-37-500_tet-st-down_b2bbe_nl-be_017.xlsx)

  • 2-supports = Placed on 2 supports (ex: jri_ji_boreas_xls_tet_2-supports_b2bfr_fr-fr_055.xlsx)

  • 3-supports = Placed on 3 supports (ex: jri_ji_boreas_xls_tet_2-supports_b2bfr_fr-fr_055.xlsx)

(ex: xxx)

• tvi = technical vector image (Easy Catalog specific)

(ex: jri_aquadrain-1500_tvi_000000000000000003_04.ai)

• tbi = technical bitmap image

(ex: jri_aquadrain-1500_tbi_000000000000000003_04.jpg)

• pip = product image used in print (Easy Catalog specific)

(ex: jri_aquadrain-1500_pip_000000000000000003_04.png)

• bro = brochure

(ex: jri_mr029_panneaux_sandwiches_couvertures_bro_b2bfr_fr-fr.pdf)

• dvi = detail vector image (Easy Catalog specific)

(ex: jri_aquadrain-1500_dvi_000000000000000003_04.ai)

• dbi = detail bitmap image

(ex: jri_aquadrain-1500_dbi_000000000000000003_04.dbi)

• NB1: In case of a conflict between two files (ex: if a product has different TVI in a specific market), add a catalog (and language information if necessary) in the filename, ex:

  [...]tvi_xx_catalog_xx_xx_

(ex: jri_aquadrain-1500_tvi_b2bfr_fr-fr_000000000000000003_04.ai)

• NB2: In case you need multiple time the same doctype for the same product, add a number after the doctype, ex:

(ex: jri_aquadrain-1500_dbi1_000000000000000003_04.dbi,

jri_aquadrain-1500_dbi2_000000000000000003_04.dbi,

jri_aquadrain-1500_dbi3_000000000000000003_04.dbi)

• ctd = compliant technical drawing

(ex: jri_aquadrain_1500_ctd-dxf_b2bfr_fr-fr_000000000000000003_04.dxf

jri_aquadrain-1500_ctd-dwg_b2bfr_fr-fr_000000000000000003_04.dwg

jri_aquadrain-1500_ctd-pdf_b2bfr_fr-fr_000000000000000003_04.pdf

jri_aquadrain-1500_ctd-rvt_b2bfr_fr-fr_000000000000000003_04.rvt

...)

• tcf = technical certificate

(ex: jri_aquadrain_1500_tcf_certificatename_b2bfr_fr-fr_000000000000000003_04.pdf

Where to save doctypes in ProductData folder ?

• tds = ... > Product Name > Technical Data Sheet

• tet = ... > Product Name >Technical Tables

• tvi = ... > Product Name > Technical Drawings - Vector

• pip = ... > Product Name > Images

• bro = (to be defined) Brochure

CTD Drawings

• DXF : jri_aquadrain_1500_ctd-dxf_b2bfr_fr-fr_000000000000000003_04.dxf

• DWG : jri_aquadrain-1500_ctd-dwg_b2bfr_fr-fr_000000000000000003_04.dwg

• PDF : jri_aquadrain-1500_ctd-pdf_b2bfr_fr-fr_000000000000000003_04.pdf

• RVT : jri_aquadrain-1500_ctd-rvt_b2bfr_fr-fr_000000000000000003_04.rvt

Catalogs available in PIM:

• b2bbe (Belgium)

• b2bch (Switzerland)

• b2bde (Germany)

• b2bdk (Denmark)

• b2bfr (France)

• b2bhu (Hungary)

• b2bis (Iceland)

• b2bnl (The Netherlands)

• b2bno (Norway)

• b2bro (Romania)

• b2bse (Sweden)

• b2buk (United Kingdom)

Languages available:

• en-gb (English)

• nl-be (Dutch Belgium)

• fr-be (French Belgium)

• de-be (German Belgium)

• nl-nl (Dutch)

• de-de (German)

• fr-fr (French)

• da-dk (Danish)

• sv-se (Swedish)

The product doesn't exist in the PIM yet:

In case the product haven't been created in the PIM yet, you won't be able to find a PIMID number. If that is the case, place the product document in a temporary folder in the product document type folder, ex:

"Assets\products\roof\roofProfiles\Aquadrain 1500\Technical Data Sheet\Temp\jri_aquadrain_1500_tds_b2bfr_fr-fr.pdf"