Seeking advice on organization of variables

[HiyaKath]

Hi,

I have one project that creates documents for about 25 similar products. Each product has between 5 and 12 distinct models.

I'm using variables to define model attributes within each product. I have a MODEL variable set with twelve generic models named A through L. I also have a MODEL conditional set (A through L). There are approximately 50 attributes for each model defined in the variable set and each model can have two variants (mono and/or color).

I have a number of tables that list the models with attributes as defined by variables. These are used in different TOCs for different outputs.

However, I also have some tables with fixed attributes for a given model.

In our master table of models, we sequence them by one attribute (size). It is not uncommon for the product team to add new models that fit in the middle of the current set. When this happens, I reorder the variables in my target file. For example, C becomes D, B becomes C to make room for a new B.

It is also not uncommon for the product team to change the model number over the course of development. This is not an issue for changing the variable, but is an issue for anywhere I may not have used it. Currently, I don't use the Model number variable in the tables with fixed attributes, because if the variable changes, the fixed attributes will no longer be correct.

I can't see creating variables for all the fixed attributes because not only are there a lot of them, they are not always the same across products.

Has anyone got some advice for how to set up a structure like this? It made sense when we only had about 5 models per product and only 10 attributes a piece, but it's becoming...messy.

Thoughts?

I'm using Flare 9.1 - Windows 7. Let me know if I can clarify anything.

Thanks,
Kath

[CATERAF]

Hi Kath,

I'm not sure if you're still experiencing this problem but, if you are, would you mind giving some examples for me please?
I'm not quite clear on what you're asking with different models and such.
Our company has multiple products with lots of variations between them all so I wonder if I may be able to help but I'm not quite clear on your current system...

Thanks,
Avril

[HiyaKath]

Thanks Avril.

It is a bit complicated and reading over my post I'm not sure I explained it well.

I have ~25 products (cameras). I have a target file for each product. Each product has between 8 to 20 models (based on camera sensor). Each model has two variants (mono/color). I don't know the full suite of models when we first put the product out. New models are defined over time.

There is a set of ~50 attributes for each model (size, frame rate, resolution, shutter, etc.). There are also a myriad of additional attributes that vary from model to model - I do not use variables for these but rather fixed text conditionally tagged.

The most common use for these in my documents are in tables of specifications for the product.

I have defined variable sets to accommodate up to 20 models conditionally tagged. Example: 01.Color.ShutterSpeed (Model.Variant.Attribute)

The system is working for now, but it seems messy to me. My question was seeking ideas for organization that might make it cleaner.

I hope that makes it a little clearer.

Thanks,
Kath