Runtime Options - Intergraph Smart Materials - Version 10.1 - Administration & Configuration - Hexagon

Intergraph Smart Materials Integration (10.1)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Administration & Configuration
Smart Construction Version
8
Smart Materials/Smart Reference Data Version
10.1

Issue Status

This attribute is used in conjunction with List Status. Typically Issue Status refers to the PHASE of a project (e.g. Preliminary, For Design, For Construction, As Built). It may also be used to show the revision level depending on the company’s philosophy.

A simple example may be Issue Status:

A, B, C, D = Preliminary

0, 1, 2, 3, 4 = For construction

0a, 0b, 1a, 1b, 1c, etc = Internal revision once at the information has reached As Built Status

The coding in Smart Materials may be modified to reflect the phase as well as the status:

Preliminary PRE_x (where X is the revision letter/number)

Approved For Design AFD_x

Approved For Construction AFC_x

As Built ASB_x

List Status

This status is used in conjunction with the Issue Status. Typically the List status is used to monitor the completeness of each revision if desired.

0 Working

A Design Service conditions complete

B Operating Service Conditions complete

C Insulation requirements complete

D …………

E Checked for Issue

Z Issued

Transfer

If checked, the import job will update the records in Smart Materials. If not checked, it will perform a simulation only. This allows some testing to be done without modification to the database.

Find Ident

When importing material using the commodity code, you can request Smart Materials to find the associated ident. The prerequisites are that there must be sufficient information for Smart Materials to determine the ident that is tabulated in the "Idents or Commodity Codes" section. If this option is not checked then it will be necessary to run a separate verification job in B20.01.

Recognize Rev +1

In earlier versions of Smart Materials, Material in the BOM could be locked as a form of revision control. This is no longer recommended and as such the Rev+1 option should not be checked. (Basically it used to allow the import to continue even when a BOM had been locked for issue).

Job Execution Statistics

General information about the job.

Job Control - Buttons

Start - Click this once all parameters have been set and saved.

Delete Job - Good to clear unwanted test loads (production loads should perhaps be kept live for some time).

View SQL*Loader Log File - Shows Oracle log file – useful if import fails.

View Import Protocol - Shows step-by-step import of material, gives warnings where material has imported but there is some potential problem with it (for example, idents were not found for the imported commodity code).

Restart Job - Available under special circumstances – see online help.

Clear Import Data -- Import data is stored in a temporary interface table, this clears the table and removes some log information from the Import Protocol.

Clear Info Panel -- Just clears the info panel at the bottom of screen.

Execute and Import

The import file must have a .dat extension for OMI import. Importing material for a specific node (module in this example) at the same issue status has the effect of deleting the existing and overwriting it with the new data. No revision history is kept. This is true EXCEPT when using the "Import Fab Spools" Option as in Example 2.

Check Error Logs

  1. Check the info screen at the bottom of B.40.01. See if there are any failure messages.

  2. Check the SQL Loader Log file. See the number of read lines matches the import file (e.g. total logical records read: 67)

  3. View Job Log file. Check the Section entitled "Import Data Error Summary"

  4. View the import protocol. Look for Errors and Warnings. In the top right corner you can set Smart Materials to only show errors. This is a quick way to find problems.