Вы находитесь на странице: 1из 15

SmartPlant Instrumentation

Release Bulletin

Version 2013

March 2013

DSPI2-PE-200012B
Copyright
Copyright © 1995-2013 Intergraph® Corporation. All Rights Reserved. Intergraph is part of Hexagon.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement;
contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade
secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from
Intergraph Corporation.
U.S. Government Restricted Rights Legend
Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was
developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with
subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal
Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of
the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS
252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.
Unpublished - rights reserved under the copyright laws of the United States.
Intergraph Corporation
P.O. Box 240000
Huntsville, AL 35813
Terms of Use
Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless
the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed
license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use
of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives
licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement
and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for
resale or redistribution.
Warranties and Liabilities
All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software
or applicable license for the software product signed by Intergraph Corporation, and nothing stated in, or implied by, this
document or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes
the information in this publication is accurate as of its publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable
technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.
The software discussed in this document is furnished under a license and may be used or copied only in accordance with the
terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not
supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL
EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.
Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data.
Users should verify for themselves that the data is accurate and suitable for their project work.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, SmartMarine, FrameWorks, I-Convert, I-Export, I-Sketch, IntelliShip, INtools,
ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks
of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered
trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. Other brands and product
names are trademarks of their respective owners.
Contents
New Features in SmartPlant Instrumentation........................................................................................... 5
SmartPlant Instrumentation 2013 ........................................................................................................... 5
General ............................................................................................................................................. 5
Administration ................................................................................................................................... 5
Calculation ........................................................................................................................................ 5
Calibration ........................................................................................................................................ 6
Instrument Index ............................................................................................................................... 6
Integration ......................................................................................................................................... 7
Interfaces .......................................................................................................................................... 7
Preferences ...................................................................................................................................... 7
Process Data .................................................................................................................................... 7
Wiring................................................................................................................................................ 8

General Notes ............................................................................................................................................ 11


Retrieving DCS Catalogs................................................................................................................ 11

Internationalization .................................................................................................................................... 13
Configuring Enhanced Reports for Internationalization ........................................................................ 15
Set Preferences for Internationalization of Enhanced Reports ............................................................. 15
Configure Enhanced Reports for Internationalization ........................................................................... 15
Configure Enhanced Report Symbols for Internationalization .............................................................. 15

SmartPlant Instrumentation Release Bulletin 3


Contents

4 SmartPlant Instrumentation Release Bulletin


SECTION 1

New Features in SmartPlant


Instrumentation
This section provides short descriptions of the new features in SmartPlant Instrumentation 2013.
For details of features added in previous versions of SmartPlant Instrumentation, see the
Release Bulletin document supplied with the specific version.

SmartPlant Instrumentation 2013


General
 The software now supports Oracle 11. Previous versions of Oracle are no longer supported.
 The software now supports InfoMaker 12.5. Previous versions of InfoMaker are no longer
supported.
 Functionality was added to support definition of custom units of measure and custom unit of
measure types.

Administration
 Access Rights for Instrument Index supporting tables can now be controlled on an individual
basis.
 If you are using SmartPlant License Manager 2010 or 2012 and you have administrative
rights, you can create environment variables to customize license tracking. The
environment variables can be defined at the system level, user level, or by using a script that
automatically starts your products. Any of the following three variables can be defined as
required:
 ProjectName
 NodeName
 UserNameEX
For more information contact SmartPlant Instrumentation Support.

Calculation
 SmartPlant Instrumentation now supports the ISO-5167-2003 standard for calculations for
flowmeters. This includes addition of the following:
 Square-edge orifices
 Flange tappings
 Corner tappings
 Radius tappings
 Nozzles — calculation for ISO Long Radius Nozzles and ISA 1932 Nozzle now includes
the option to select either the 1991 or 2003 standard.
 SmartPlant Instrumentation now supports calculation for the ASME PTC 19.3 TW-2010
standard for thermowells. This includes calculations for tapered, stepped, and straight
thermowells. The following values are calculated:

SmartPlant Instrumentation Release Bulletin 5


New Features in SmartPlant Instrumentation

 Frequency
 Static stress
 dynamic stress
 hydrostatic pressure

Calibration
 SmartPlant Instrumentation now supports the 75x series of Fluke calibrators.

Instrument Index
 Duplicating a tag no longer requires reselecting the instrument type.
 Renaming a tag no longer requires reselecting the instrument type.
 The Cable Instrument Index Browser has been improved and is now available
“out-of-the-box” when you install SmartPlant Instrumentation. It has been improved to work
in an integrated environment, publishing all types of cables that are connected to any type of
panel and showing the connections of both ends. This makes it easier to publish form
SmartPlant Instrumentation to SmartPlant 3d.
 A new field, Revision description, has been added to the following reports:
 All Tag Numbers
 Loop Summary
 Telecom Devices
 Index Browse

6 SmartPlant Instrumentation Release Bulletin


New Features in SmartPlant Instrumentation

Integration
 New task types have been added to the To Do List:
 Marked for Deletion — This task type highlights those items the software has decided
need to be deleted from the database. You have to check that these highlighted items
are in fact for deletion and then manually change their status to delete where required.
 You must activate the Marked for Deletion option found under File >
Preferences > SmartPlant Integration > General.
 Overwrite — Similar to the Update task type that is displayed when changes have been
made to the source properties, the Overwrite task is displayed when changes have
been made to the source object other than its properties. For example, if an object is
deleted from one drawing and the same object name is used in a different drawing that
is published to SmartPlant Instrumentation.
 New functions have been added to the To Do List:
 Regenerate the To Do List — Allows the software to regenerate the status of the To
Do List items, without having to retrieve the documents from SmartPlantFoundation.
You cannot regenerate items in the To Do List that were upgraded from versions
prior to SmartPlant Instrumentation 2013. Before upgrading to SmartPlant Instrumentation
2013 you must complete all tasks in the To Do List, or after upgrading delete the To Do List
and then create a new one.
 A new command has been added to the To do List toolbar, Related Tasks . This
new command combines the Select Parent Task and Select Sub-Tasks commands
into one command that allows you to select a task from the To Do List and view all its
related tasks in the To Do List.
 Changes have been made to the underlying software of the To Do List to improve
performance and reduce the number of tasks displayed. For example, in previous versions a
Create task for a new instrument would also involve the creation of a Create Relationship
task between the instrument and the loop, 2 tasks for one action. With the improvements in
the software just the Create instrument task is displayed in the To Do List, while the
relationship to the loop is now a property of the instrument. This makes the To Do List less
cluttered, easier to use, and faster.

Interfaces
 A license for the Yokogawa DCS interface is no longer required for SmartPlant
Instrumentation.

Preferences
 The option was added to save user preference customizations on a per-domain/project
basis. This includes the option to retain domain-specific user preferences when resetting the
preferences to default values.

Process Data
 Printing is now enabled for process data reports on process data that is locked

SmartPlant Instrumentation Release Bulletin 7


New Features in SmartPlant Instrumentation

Wiring
 Changes have been made to the way Multi-Strip Panel Report drawings store data for use
when regenerating an existing drawing. Previously retrieval of the drawing data was based
on the filter saved with the drawing, when first creating the report drawing, for example a
filter based on manufacturer X would retrieve and display all the strips that were associated
to manufacturer X. As the filter criterion, in this case manufacturer X, is saved along with the
drawing, subsequent generation of the drawing, results in all of manufacturer X strips being
displayed even if they were added after the original drawing was created. In the same way,
strips that have been deleted after the original drawing was generated would be removed.
Now the filter is no longer saved with the drawing. Even if new strips were added to the filter
after generation, regenerating the drawing results in the original drawing being displayed
without the new strips. For example, after using the filter Manufacturer = X the generated
Multi-Strip report contains 3 panel strips PS1; PS2; and PS3. Now if you add 2 more panel
strips to manufacturer X, PS4 and PS5 and then regenerate the original drawing these new
panel strips do not appear on the drawing as the drawing is now based on the selected
terminal strip and not the filter. If you want them to appear in the same drawing you can
select to add them to the drawing by selecting the drawing from the Document and
revision number list, and then from the search results using the Select check box next to
the strips you want to add. You can also remove strips by clearing the check box from the
search results.
 The Wiring Equipment Connection report has been enhanced by adding an option, Show
signals separately, to the Wiring Equipment Connections dialog box. This publishes the
report showing individual signals as separate paths.
This replaces the custom preference ShowIndividualSignals that was supplied with
SmartPlant Instrumentation 2007 SP6 HF41.
This is not to be confused, in the Wiring Equipment Connections dialog box, with
the Generate Report by group > Signal option. This option just signals the application to
retrieve all the terminals that signals flow through them.
The following changes were applied to the option Generate reports by > Signal:
 Power supplies are displayed as general signals on the report drawing.
 The same general signal may appear multiple times.
 The signals will be ordered by channel sequence.
 If at least one of the terminals of a channel has a signal running into it, then all the
terminals of this channel will be drawn, including those terminals that no signals run into
them.
 If a channel is drawn and a cable is connected to those terminals that no signal runs into
them, then the cable will not be drawn.
 If none of the terminals of a channel has a signal running into it, then the channel will
not be drawn.
 All internal IO card jumpers are shown.
 The wiring report shall show relevant Jumpers, plus 1st and last terminal. This is similar
to the way jumpers and terminals are drawn on present drawings, i.e. only the first
terminal and last terminal, but with the following exceptions:
 Channels that are not associated with this signal may appear in the signal path of
the signal.
 The same channel may appear multiple times: once for the signal it is associated
with, and the other times for each channel that is wired through this channel via
jumpers.

8 SmartPlant Instrumentation Release Bulletin


New Features in SmartPlant Instrumentation

 Only wired terminals will be shown


Wiring Equipment Report Example Diagram

1. A signal enters terminal 14 all terminals that are under this channel (or apparatus) are
drawn, including terminal 0V.
2. Terminal 0V is wired, through a jumper, to terminals in apparatus pos: 0, therefore all the
channels of apparatus 0 are drawn.
3. If the jumper is wired to other channels before reaching apparatus 0, then these channels
are not shown. This explains the gap above apparatus 3.

SmartPlant Instrumentation Release Bulletin 9


New Features in SmartPlant Instrumentation

4. Only the starting terminal and ending terminal of the jumpers are drawn, with all other
terminals that belong to the channels of these two terminals.
 Twelve new wiring colors have been added to the available wiring colors. The new colors
are:
 Tan
 Dark Blue
 Nickel Gray
 White/Black/Blue
 White/Black/Brown
 White/Black/Gray
 White/Black/Green
 White/Black/Orange
 White/Black/Red
 White/Black/Violet
 White/Black/Yellow
 Green/Yellow (30%)

10 SmartPlant Instrumentation Release Bulletin


SECTION 2

General Notes

Retrieving DCS Catalogs


 In an integrated environment, retrieving DCS Catalogs no longer requires that the
SmartPlant Schema Component and SmartPlant Client are installed on your local machine.

 Publishing DCS Catalogs still requires that the SmartPlant Schema Component and
SmartPlant Client be installed.
 If you are working with the SmartPlant Instrumentation - SmartPlant Electrical
point-to-point interface, you should install the SmartPlant Schema Component and
SmartPlant Client from the SmartPlant Instrumentation installation DVD. If you are
working in a fully integrated environment then, you must install these items from the
SmartPlant Foundation installation DVD.

SmartPlant Instrumentation Release Bulletin 11


General Notes

12 SmartPlant Instrumentation Release Bulletin


SECTION 3

Internationalization
Supporting internationalization in a homogeneous environment is one of the enhancements
available in SmartPlant Enterprise. A homogeneous environment uses elements from only a
single locale. For example, a German customer running on a German operating system using
only German characters and German cultural conventions is a fully supported homogeneous
environment configuration.

Homogeneous Environments
When starting a new project, use extra care during installation and configuration to ensure the
proper creation and maintenance of homogeneous environments:
 All the computers (servers and clients) within an integrated SmartPlant Enterprise
implementation must have the same regional settings, and no one should change the
regional settings after the project has started.
 Do not cross the decimal locale boundary. This is the most common cause of numeric data
corruption and calculation errors. Having users with different regional settings (like with a
period versus a comma for the decimal point) causes the software to interpret values
unpredictably. For example, a pipe run with a pressure of 35.3 psi can be read by the
software as 353 psi to the user with different regional settings. A cable length defined as 39
ft 11,21 inches has been interpreted as 121718910971323 meters when published to an
XML file. These incorrect interpretations may be used in internal software calculations and
can be impossible to backtrack or correct. Do not change the decimal point character to try
to solve an issue. Doing so will only corrupt values in the database or in text files.
 Do not cross the character-set locale boundary. For example, the character set boundary
between Western (Latin-based) and Eastern Europe (Cyrillic-based), or between Eastern
Europe and Japan.
 Create Oracle databases using AL32UTF8 for the database character set and AL16UTF16
for the NLS character set.
 Never modify the NLS_LANG registry entry on an Oracle client. Doing so causes the
character data not to convert to Unicode.
 Create Microsoft SQL Server databases with locale-specific collation settings and ensure
that all databases have the same setting.

Heterogeneous Environments
In contrast, a heterogeneous environment using elements from different, or even multiple
locales, is not supported. Many customers are currently operating in unsupported
heterogeneous environments and are often not aware of that fact. Examples of heterogeneous
environments:
 Entering or viewing Japanese data on an US/English operating system
 Using German Regional Settings (where the decimal point is a comma) on a US/English
operating system
 Using databases with different character encodings such as CL8MSWIN1251 or JA16SJIS
 Using multiple languages in a project, especially when crossing language-group boundaries
 Using an English server with different local language clients

SmartPlant Instrumentation Release Bulletin 13


Internationalization

International / Bi-lingual Projects


International bi-lingual projects are possible; however, great care must be used when
configuring these environments. Limitations exist and must be properly understood:
 Oracle and MS SQL Server databases can reside on any language operating system, as
long as the databases have been created and configured with proper Unicode and collation
settings.
 All SQL Server databases must have the same collation setting and reflect the “master”
language. Text is stored, sorted, indexed, and presented based on the collation setting. You
must determine which language will be used primarily to generate output (P&IDs, SLDs,
reports, approval documents, and so forth.) If Russian and English text is entered, and
Russian is the target locale, the chosen collation should be based on the Cyrillic character
set.
 All Microsoft operating systems (Japanese, Russian, German, and so forth) can enter
English characters. The reverse, however, is not true in most cases.
 Keyboard-locale can be changed as long as a character-set and code-page boundary is not
crossed. For example, English, German, French, and Spanish characters can all be used in
®
the same project because the same Windows code-page (1252) is used. However, Russian
characters (code-page 1251) cannot be used in a US/English environment.
 You must decide which language operating system will be the master for bi- lingual projects.
The following is an example of a Russian-based project:
Companies in the United States and the United Kingdom are working a project with a Russian
company and the deliverables (drawings, reports, and so forth) must ultimately be provided in
Russian. The companies in the U.S. and the U.K. are working the project using the "master"
Russian operating systems (possibly using virtual Russian operating systems running on
VMware Workstation). The U.S. and U.K. companies can install and use English Microsoft
Office products on the Russian operating system because Office products are globally enabled.
If a Russian interface exists for the SmartPlant Enterprise application, then Russian users can
use the Russian interface while the English-speaking users would continue to use the
US/English interface. English-speaking engineers can enter English characters.
Russian-speaking engineers can enter Russian characters.
However, because the Russian locale uses different decimal and character-set locales,
everyone (English and Russian engineers) must use the Russian decimal symbol which is a
comma. For customization purposes, databases can be modified to accommodate new
Russian-specific requirements (fields, properties, and so forth.) Using filters, display sets, and
other software features, bi-lingual projects can be further customized. Graphic data, reports, and
so forth can be created in either or both languages.
Do not change regional settings to reflect a U.S. environment in order to resolve
problems in a non-US/English homogeneous configuration. Doing this creates a heterogeneous
configuration that will cause other possibly hidden problems that cannot be corrected. Everyone
working on a project must use the same regional settings and character set throughout the life of
the project.

Questions and Assistance


Please contact your support representative for assistance and answers to your questions:
Intergraph Customer Support (http://support.intergraph.com).

14 SmartPlant Instrumentation Release Bulletin


Internationalization

Configuring Enhanced Reports for


Internationalization
When working in a language that uses double-byte characters (for example, Chinese, Japanese,
or Russian), you must localize delivered symbols containing text boxes that are used as labels.
Symbols that do not use text boxes as labels do not need to be modified.

Set Preferences for Internationalization of Enhanced


Reports
1. In SmartPlant Instrumentation, click File > Preferences.
2. On the Enhanced Reports > Enhanced Smart Loop > Fonts page, select your
locale-specific font.
3. Repeat the previous step for each enhanced report type font that affects graphical text
display.

Configure Enhanced Reports for Internationalization


You can perform this procedure on any .sma file.
1. Double-click the .sma file to open it in the Enhanced Report Utility.
2. Click Format > Text Box.
3. On the Format Text Box dialog box, click the Paragraph tab.
4. From the Font list, select your locale-specific font.
The value in the Language field will change automatically to the language for the font
that you selected.
5. Click OK to close the Format Text Box Style dialog box.

Configure Enhanced Report Symbols for


Internationalization
1. In the Symbol Editor, open the desired symbol.
2. Click Format > Style.
3. On the Style dialog box, from the Style type list, select Text.
4. From the Styles list, select a style and then click Modify.
5. On the Modify Text Box Style dialog box, click the Paragraph tab.
6. From the Font list, select your locale-specific font.
The value in the Language field will change automatically to the language for the font
that you selected.
7. Click OK to close the Modify Text Box Style dialog box.
8. On the Style dialog box, click Apply.
9. Repeat steps 4-8 for each style in the Styles list.
10. On the Style dialog box, click Close.

SmartPlant Instrumentation Release Bulletin 15

Вам также может понравиться