This document provides a comprehensive step-by-step process to understand the detailed specifications of the Corolla Cross models using the Indigo PIM system. The guide is designed to assist you in comparing different models, analyzing their attributes, and utilizing the PIM system effectively for planning and decision-making.
To address your question about the Corolla Cross specifications, this video provides background information on the additional Excel file you've shared.

This video focuses on the specifications and critical components required for planning. All information should be integrated into the PIM system for accessibility.

Each vehicle model may have different statuses, but all information should reside in the PIM system. Here's a demonstration of how this looks in the system, facilitating side-by-side comparisons.

The Indigo PIM system reflects the data from the Excel spreadsheet you provided. This system is recommended for efficient data management.

This is the worksheet you shared, containing detailed specifications for different Corolla Cross models, including various suffixes.

Some model codes differ partially. We have partially different TMC and TNZ model codes.

The suffix code varies depending on the model code, resulting in slight differences among the models.

Columns F and G show an option for two-tone paint, unavailable for one of the models.

The suffix code changes due to the two-tone paint option. Different TMC and TNZ model codes affect the suffix, grade level, and drive type.

There is a two-tone paint option compared to a single-tone option. One is front-wheel drive, the other all-wheel drive.

Overall, there are five models with varying specifications.

Here's how these specifications are reflected in Indigo.

Entering the system, you see the list view in Indigo with various models. You can rearrange the order by clicking on the headline, from B0 to D1.

The view matches what you've shown in Excel, from B1 to C0, C1, D0, and so on.

This view can be customized. There are multiple views available.

For detailed specifications, users with appropriate permissions can create or modify views by adding desired elements.

To add drive type, simply include it in the view and save.

The system will then reflect the drive type. These are the customization options available.

Here you can see the different models. You may wish to compare them side by side to identify differences.

Access the Actions menu and select Compare View. The setup will allow you to see different models side by side, highlighting your primary choice.

You can adjust the primary model, and differences and similarities will be displayed.

Additionally, you can filter for identical values to see commonalities across models.

Notable similarities include the engine block, which is consistent across models.

All models share the same engine block, but fuel consumption varies.

Fuel consumption differences stem from testing regimes, influenced by model specifications.

Differences in fuel consumption may relate to options like all-wheel drive.

Some models feature all-wheel drive, others do not, resulting in varying specifications. To compare two models, such as C1 and D0, examine the differences.

Return to the Excel file to compare C1 and D0, observing their differences in the comparison view.

Differences include the name, model code, suffix, production date, grade level, and drive options.

Also notable are differences in consumption and power mode availability, which is a Boolean attribute.

The all-wheel drive variant has unique features, including color variations.

You can explore unique relationships and views tailored for detailed specifications.

I've included all available information, totaling 88 attributes, in this Excel document.

Proceed with the download.

The download is complete, and you can open it to review...

Within the Excel file, different entities are organized in worksheets, displaying basic attributes...

and all other attribute groups for various models. Attributes can be organized in columns...

or in rows, with models in columns.

That's everything regarding question three and the detailed specification.
