General Specifications

Transcription

1 General Specifications STARDOM Portfolio (InfoWell) GENERAL Portfolio (InfoWell) is a software package that runs in an autonomous controller and that is designed to log process. An autonomous controller is a controller that is equipped with both a control function equivalent to that of a programmable logic controller (PLC) and an information processing and transmission function equivalent to that of a. InfoWell is a group of packages that is designed to perform these information processing and transmission functions through a simple setup procedure. Portfolio provides a logging function that is indispensable for managing the utilities and equipment. It collects from the control application in an autonomous controller in various forms ideal for use by the system, and saves it in a logging (in CSV format). This logging can be viewed in various forms (trend view, table format view, etc.) from the Web browser via a network. The logging can also be sent by . Use of software for a that is included in the package allows for the acquisition of logging s periodically from the via a network for further use. Viewer View (Offline) View (Online) Collect Collector FEATURES Simple Configuration without A highly reliable logging function can be implemented at low cost without using a. There is no need to maintain a dedicated running 24 hours a day. Moreover, there is no need of communication between and, although a large amount of can be logged at a high speed. Simple Configuration A simple setup makes it possible to log the of the control application. Rich Functions In addition to a basic function to periodically log and save in a logging, there are various functions such as a batch logging for recipe management, snapshot logging for reducing total amount of, SOE ( Sequence of Events) logging for collecting before and after an event such as event is detected, or message logging function for recording failures and recovery of devices and controllers. The most suitable recording method can be selected according to the purpose. Rich View Functions and Transmission Logged can be viewed on a Web browser in a variety of forms such as trend view and table format view. Logged () can also be transmitted by . Advanced Use of A logging collector running on a allows for periodically collecting logging s (in CSV format) on a. This makes it simple to analyze using MS Excel, for example. FCN FCJ Control application Collect function Figure Function Save F01E.ai #APPNAME SD-DLG #FILEREV 0 #LOGTYPE DATA_HC #TIMEZONE GMT+9 #TITLE Log File Title #DATE :00 #DATA Main.PI100_HI Pressure HI Limit KPa #DATA Main.LI100 Initial Level mm #VAR Main.PI100 Main.PI200 Main.FI100 Main.FI200 #LABEL Vessel Pressure Outlet Pressure Inlet Flow Outlet Flow #UNITS KPa KPa m3/min m3/min #TYPE REAL REAL REAL REAL :00: :00: *** :00: *** #MINIMUM #MAXIMUM #AVERAGE #TOTAL F02E.ai Figure Example of File Yokogawa Electric Corporation , Nakacho, Musashino-shi, Tokyo, Japan Tel.: URL: Copyright Apr. 2008(YK) 13th Edition Feb. 26, 2014(YK)

2 FUNCTION OVERVIEW Portfolio (InfoWell) provides the following functions. function File View function File Collection function File () Transmission ( ) function Configuration function LOGGING FUNCTION The logging function has the following functions. SOE ( Sequence of Events) Message Control application function Collect Block 40 items Block Block items Save Figure Function Note: The logging type can be set on a block basis. Note: s are created on a block basis. Note: One logging is created on each closing process. F03E.ai There are the following types of logging. type Hourly logging Table Periodic High speed (*5) 1 to 60 seconds (*1) (*3) Daily logging - Batch logging Snapshot logging Continuous Triggered 1 to 60 seconds (*1) (*3) Low speed 1 to 60 minutes (*2) 1 to 60 minutes (*2) 1 to 60 minutes (*2) - Trigger Closing timing Every hour Every day Batch start/ stop switch Every hour or every day Closing trigger 2 Simple report (*4) Daily, monthly, yearly report Monthly, yearly report - Daily, monthly, yearly report *1: Any of the fixed values (1, 2, 5, 10, 15, 30, and 60 seconds) can be set. *2: Any of the fixed values (1, 2, 5, 10, 15, 30, and 60 minutes) can be set. *3: To collect, a program organization unit (POU) for logging is required when programming a control application. Periodic depends on the scan period of the task. *4: A simple report, including daily, monthly and yearly report, is a CSV format consisting of closing values (maximum, minimum, average and total). *5: Not supported by FCN-RTU (NFCP050) style S1. - Aug. 9,

3 Hourly Hourly logging collects in a specified period, closes processing once every hour, and creates an hourly logging. Periodic options are high speed (1 to 60-second period) or low speed (1 to 60-minute period). The closing processing of hourly logging calculates the maximum, minimum, average, and total values and saves them along with the collected in the logging. The saved logging is compressed in Zip format. s (daily report, monthly report, or yearly report) can also be created based on the collected. Daily Daily logging collects in a specified period (1- to 60-minute period), closes processing once every day and creates a daily logging. The closing processing of daily logging calculates the maximum, minimum, average, and total values and saves them along with the collected in a logging. The saved logging is compressed in Zip format. s (monthly report and yearly report) can also be created based on the collected. Collect at a specified interval Collect at a specified interval 3 Collect at a specified interval Collect at a specified interval Daily logging Daily logging Create simple report Hourly logging Hourly logging Daily report Monthly report Create simple report Monthly report Yearly Report Figure Operation Example of Daily (with a Simple Report) F05E.ai Yearly Report F04E.ai Figure Operation Example of Hourly (with a Simple Report) #APPNAME SD-DLG #FILEREV 0 #LOGTYPE DATA_HC Start time to collect #TIMEZONE GMT+9 #TITLE Log File Title #DATE :00 time #DATA Main.PI100 Vessel Pressure KPa #DATA Main.LI100 Initial Level mm #VAR Main.PI100 Main.PI200 Main.FI100 Main.FI200 Main.PUMP1 Main.TI100 #LABEL Vessel Pressure Outlet Pressure Inlet Flow Outlet Flow Inlet pump Vessel Temp #UNITS KPa KPa m3/min m3/min DegC #TYPE REAL REAL REAL REAL BOOL REAL #ON_LABEL RUN #OFF_LABEL STOP :00: RUN *** :00: *** RUN (up to 40 items) :00: *** STOP #MINIMUM #MAXIMUM #AVERAGE #TOTAL Header information ( attributes) Header information (parameters) Header information (labels) Collected Footer information (closed logging ) F06E.ai Figure File Example of Hourly Nov. 11,

4 4 #VAR Main.PI100 Main.PI200 Main.FI100 #VAR Main.PI100 Main.PI200 Main.FI100 #VAR Main.PI100 Main.PI200 Main.FI100 #LABEL Vessel Pressure Outlet Pressure Inlet Flow #LABEL Vessel Pressure Outlet Pressure Inlet Flow #LABEL Vessel Pressure Outlet Pressure Inlet Flow Hourly logging Simple daily report Simple monthly report #UNITS KPa KPa m3/min #UNITS KPa KPa m3/min #UNITS KPa KPa m3/min #TYPE REAL REAL REAL #TYPE REAL REAL REAL #TYPE REAL REAL REAL :00: :00: :00: :00: :00: :00: Close the hourly logging, compile the collected, Close and compile the simple daily reports and record the results in a simple daily report and record the results in a simple monthly report :00: :00: :00: :00: :00: :00: #MINIMUM #MINIMUM #MINIMUM #MAXIMUM #MAXIMUM #MAXIMUM #AVERAGE #AVERAGE #AVERAGE #TOTAL #TOTAL #TOTAL Figure Example of Generating Simple Daily and Monthly Report Batch This function collects in a specified period and saves it in the while the batch start/stop switch (*1) is true. The periodic options are either high speed (1- to 60-second period) or low speed (1- to 60-minute period). A simple report is not created. Note: Whenever the batch start/stop switch is true, a new is created. *1: Batch start/stop switch This is a Boolean type variable of control application to specify the period to collect. At the timing when the batch start/stop switch is changed from false to true (when starting ) or oppositely changed from true to false (when stopping ), will also be executed. The interval between True and False of Batch start/stop switch must be one minute or longer. F07E.ai Batch start/stop switch Collect at a specified interval :True :False Batch logging Figure Operation Example of Batch F08E.ai Nov. 11,

5 5 Snapshot This function collects and saves it in a at the timing when a trigger becomes True. There are two types, Continuous and Trigger, in accordance with the logging closing method. Snapshot (Continuous) This function performs the closing processing at a specified time and creates a logging. A simple report (daily report, monthly report, or yearly report) can also be created. trigger Collect Create simple report Snapshot logging Collect Daily report :True :False Snapshot logging Snapshot (Trigger) This function generates a when the first trigger becomes True, and then ends the logging and saves the in the when a closing trigger becomes True. A simple report cannot be created. Note: After the closing processing is performed, the next trigger creates a new and starts logging. Close trigger trigger Collect :True :False :True :False Monthly report Yearly Report F09E.ai Figure Example of Snapshot (Continuous) First trigger generates Snapshot logging Figure Operation Example of Snapshot (Trigger) F10E.ai Note: Both the trigger and closing trigger are Boolean type variables of control application. SOE (Sequence of Events) SOE (Sequence of Events) logging collects at high speed before and after the detection of event such as failure and saves in a. A simple report is not created. function Blodk Blodk Blodk Collect items items 32items 32items 40 items Save Event detection before event after event Event detection Y X High speed before and after Event Detection t Figure SOE Function SOE File F18E.ai Event (600 ) :True :False SOE logging Figure Operation Example of SOE F19E.ai Nov. 11,

6 6 Message This function saves messages in a continuous (one-minute) period in the. The messages can also be filtered by the message number. #APPNAME SD-DLG #FILEREV 0 #LOGTYPE MSG #TIMEZONE GMT+9 #TITLE Log File Title #DATE :23 #TIME ID CATEGORY TYPE :37: APPLICATION EVENT :37: APPLICATION EVENT :37: APPLICATION EVENT :37: APPLICATION EVENT :37: APPLICATION ALARM :37: APPLICATION ALARM :37: APPLICATION ALARM :37: APPLICATION ALARM :55: APPLICATION EVENT :55: APPLICATION EVENT SOURCE MSG100.MSG_BLOCK_01.USRALM MSG100.MSG_BLOCK_01.USREVT MSG.MSG_BLOCK_01.USRALM MSG.MSG_BLOCK_01.USREVT TRIGGER.BATCH_MSG1 TRIGGER.BATCH_MSG2 TRIGGER.SNAP_MSG1 TRIGGER.SNAP_MSG2 MSG100.MSG_BLOCK_01.USRALM MSG100.MSG_BLOCK_01.USREVT MESSAGE MSG100.MSG_BLOCK_01.USR... MSG100.MSG_BLOCK_01.USR... MSG.MSG_BLOCK_01.USRALM... MSG.MSG_BLOCK_01.USREVT... TRIGGER.BATCH_MSG1 Batch... TRIGGER.BATCH_MSG2 Batch... TRIGGER.SNAP_MSG1 Writing... TRIGGER.SNAP_MSG2 Closing... MSG100.MSG_BLOCK_01.USR... MSG100.MSG_BLOCK_01.USR... Header information ( attributes) Header information (labels) Messages F11E.ai Figure Example of Message File LOGGING FILE COLLECTION FUNCTION s on are periodically collected on using logging function. Collection can also be performed manually whenever necessary. The following methods are prepared for the logging function. Select one of them for the intended purpose. File Collector It runs in the task tray while is logged on. File Collection Service It runs as a service even if is not logged on. File Collection Collect Collect LOGGING FILE VIEW FUNCTION File View Function collected by the logging function can be viewed in Viewer on the Web browser (online view). s not only in the but also those collected on the can be simply viewed using Viewer (offline view). Trend View and Table Format View are available in Viewer. Message View Function message logs that were collected can also be viewed in Viewer in the same manner as viewing. Viewer View (Offline) Collector FCJ FCN F13E.ai View (Online) Collect Figure File Collection Function F12E.ai Figure Viewing File by Viewer Feb. 2,

7 LOGGING FILE TRANSMISSION (E- MAIL) FUNCTION (*1) This function allows for transmitting logging s as attachments by . server Transmit Mobile phone LOGGING CONFIGURATION FUNCTION A Configurator allows for configuring how to collect. This tool has an online mode that allows for directly changing the configuration information in the and an offline mode that allows for downloading the configuration information to the after it is changed on the. 7 transmission function Web browser configurator Collected *1: Not supported by FCN-RTU (NFCP050) style S1. F14E.ai Figure File Transmission ( ) Function Note: An server is required on the intranet to transmit . Use Application Portfolio (InfoWell) to transmit messages and alarms by . The File Transmission ( ) Function and Application Portfolio (InfoWell) can be applied simultaneously. The logging s that can be transmitted are simple reports (daily report, monthly report, and yearly report). configuration F15E.ai Figure Configurator (Online) configurator configuration Download configuration Figure Configurator (Offline) F16E.ai Note: When using the logging configurator offline, the tool is required to be installed in the. Feb. 2,

8 8 DATA LOGGING FUNCTION SPECIFICATIONS Table Function Specifications / SOE Specifications Message to be collected control application variables message Number of items 40 items/block - Number of blocks FCN, FCJ 25 blocks (*2) (10 blocks in case of high-speed ) (*8) FCN-RTU 16 blocks (*11) (*12) block start/stop trigger BOOL-type control application variable (*1) (*9) 2 blocks Amount of to be saved FCN, FCJ 60,000 items/min. (*3) FCN-RTU 30,000 items/min. (*13) File format CSV form (*4) Total logging size block size Number of s 400 s per logging (*7) Limited by the free space on the system card (500 MB max) or flash memory on FCN-RTU (80 MB max) (*10) Specify the maximum size on logging block basis. The specified values must be such that the sum of all logging block sizes does not exceed the total logging size. (*5)(*6) Note: When there is possibility of power interruption in the electric supply to, please connect an uninterruptible power supply system (UPS). For more information, refer to the STARDOM UPS Guide () (TI 4P02Q45-01E) *1: for a logging block can be started or stopped from a control application by specifying a variable as a block start/ stop trigger. If no trigger is specified, the logging block is always activated (in RUN status). *2: This represents the total number of blocks for the logging function and SOE logging function. *3: Collecting this amount of is equivalent to increase in CPU load by 25 % to 30 %. CPU load is increased when s are sent, simple reports are created and messages are logged. *4: When closing processing is performed, the logging is compressed into Zip format, normally to between 10% and 50% of the original size. *5: The oldest is removed when collected for a logging block exceeds the specified logging block size, even if the number of s accumulated in a logging block does not exceed 400. *6: In case of hourly logging (for up to 40 items and in a period of 1 second), the maximum size of one is approximately 1.7 MB. The is compressed to the one-third compared to the size of the original in Zip format, except for a logging for which is currently being collected. When a 100 MB area is allocated, approximately 170 s (for one week) can be logged. *7: Files are deleted from the oldest when the number of s accumulated in a logging block exceeds 400, even if collected for a logging block does not exceeds the specified logging block size. *8: This represents the total number of blocks for the high-speed, namely hourly logging(high-speed), batch logging(high-speed) and SOE logging. *9: The interval between True and False of start/stop trigger of logging block must be one minute or longer. *10: 16 MB max in case of FCN-RTU (NFCP050) style S1 *11: Maximum of the total number of blocks for high-speed, low-speed, and SOE logging is 16. Maximum of the total number of blocks for high-speed and SOE logging is 5. *12: FCN-RTU (NFCP050) style S1 can be used only with low-speed function. High-speed and SOE logging function are not supported. *13: 8,000 items/min. in case of FCN-RTU (NFCP050) style S1 Feb. 26,

9 9 Table Detailed Specifications of Hourly and Daily Functions Periodic to be collected Closing timing Closing processing period Hourly logging Daily logging High speed Low speed 1, 2, 5, 10, 15, 30, 60 second(s) POU for logging (*1) Fixed period 1, 2, 5, 15, 30, 60 minute(s) control application variables (*2) 1 hour 1 day Closing time Specify in minutes Specify in hours s to be generated at closing time (*3) Minimum, maximum, average, Minimum, maximum, average, total. Daily report, Daily and monthly report, Daily, monthly, and yearly report. Monthly report, Monthly and yearly report. *1: The types that can be connected to the POU for logging are C_REAL, REAL, C_INT, INT, and BOOL. *2: control application variables with an O check. The types of variables that can be collected are C_REAL, C_INT, REAL, LREAL, INT, SINT, UNIT, USINT, DINT, UDINT, BOOL, and STRING. *3: s can be transmitted by . ( function is not supported by FCN-RTU (NFCP050) style S1.) Periodic to be collected Closing processing s to be generated at closing time Table Detailed Specifications of Batch Function High speed 1, 2, 5, 10, 15, 30, 60 second(s) POU for logging (*1) Batch logging Low speed 1, 2, 5, 10, 15, 30, 60 minute(s) control application variables (*2) When is finished Minimum, maximum, average, Minimum, maximum, average, total Unavailable Periodic to be collected Close timing Closing processing period Closing time (*2) Closing processing s to be generated at closing time Table Detailed Specifications of Snapshot Function Snapshot logging Continuous Trigger More than 1 minute for the trigger (*3) interval control application variables (*1) Fixed period Closing trigger (*3) (*4) 1 hour 1 day - Specify in minutes Daily report, Daily and monthly report, and Daily, monthly, and yearly report. Specify in hours Monthly report, and Monthly and yearly report. When is finished - Unavailable Minimum, maximum, average, and Minimum, maximum, average, total. *1: control application variables with an O check. The types of variables that can be collected are C_REAL, C_INT, REAL, LREAL, INT, SINT, UNIT, USINT, DINT, UDINT, BOOL, and STRING. *2: can be transmitted by . ( function is not supported by FCN-RTU (NFCP050) style S1.) *3: Trigger is a Boolean type variable of control application. *4: The interval between the closing triggers of logging block must be one minute or longer. *1: The types that can be connected to the POU for logging are C_REAL, REAL, C_INT, INT, and BOOL. *2: control application variables with an O check. The types of variables that can be collected are C_REAL, C_INT, REAL, LREAL, INT, SINT, UNIT, USINT, DINT, UDINT, BOOL, and STRING. Feb. 2,

10 SOE LOGGING FUNCTION SPECIFICATIONS Table SOE Function Specifications SOE (*3) Periodic 100 milli seconds or longer (*1) to be collected POU for SOE logging (*2) Number of sample 600 Number of pretrigger sample 0 to 599 Closing processing When is finished s to be generated at closing time Unavailable Unavailable *1: Periodic depends on the scan period of the task. *2: The types that can be connected to the POU for SOE logging are REAL, INT, and BOOL. *3: Not supported by FCN-RTU (NFCP050) style S1. MESSAGE LOGGING Table Message Message logging Periodic 1 minute to be collected message Number of blocks 2 blocks (*1) Filter ID of messages to be collected can be specified on a block basis Closing processing period 1 day Closing time 0 A.M. File format CSV format (*2) size 1 : Less than 1 MB (by default) Total: 1 to 500 MB (*3) *1: Total number of blocks for the message logging function. *2: When the closing processing is performed, the logging is compressed in ZIP format. This logging is compressed to 10% to 50% compared to the size of the original. *3: Specify the maximum size on a block basis. When the collected is larger than the specified size, the oldest is deleted. TIME STAMP Time stamp in logging, SOE logging and message logging is recorded based on clock and time zone of setting. Daylight saving time is not applied. POUs FOR LOGGING A POU for logging is used to collect at high speed. Control application Collect POU for logging function Block Block Save Figure POU for Block items 40 items POUs for High-speed There are high-speed synchronous POU and highspeed POU ( types: REAL, INT, BOOL, C_REAL, C_INT). 10 F17E.ai POUs for SOE There are SOE trigger POU and SOE POU ( types: REAL, INT, BOOL). LOGGING VIEWER Table Viewer Function Specifications Specifications Online: Specify URL with the Web browser Tool Offline: Start the tool on a generalpurpose View method Trend, table format (*1) Number of items to be viewed Table format view: up to 40 items Trend view: up to 10 items *1: Message logging can be viewed only in table format. LOGGING FILE COLLECTION FUNCTION SPECIFICATIONS Table File Collection Function Specifications Specifications Applicable device : up to 32 units File transfer mode HTTP, FTP passive or FTP active Periodic Every 1, 2, 3, 4, 6, 8, 12, and 24 hours (*1) Applicable All logging s Amount of to be saved Depends on the disk space of the (*2) *1: s can also be collected manually whenever necessary. *2: As for logging collected in, you can select automatic decompress or not automatic decompress. Prepare a hard disk in which all s can be saved, or remove unnecessary logging s on a timely basis. Feb. 2,

11 LOGGING FILE TRANSMISSION (E- MAIL) FUNCTION SPECIFICATIONS Table File Transmission ( ) Function Specifications transmission protocol (*1) address group transmission destination Specifications SMTP (Specify the server type from the following options) SMTP (Standard) AUTH (User login is required) PBS (POP before SMTP) 5 addresses per group can be specified 32 groups can be registered Specify it in the group Transmit a logging (*2) as an attached (*3) Note: Use Application Portfolio (InfoWell) to transmit messages and alerts by e- mail. The logging transmission ( ) function and Application Portfolio (InfoWell) can be used simultaneously. transmission ( ) function is not supported by FCN-RTU (NFCP050) style S1. *1: For sending s, an server is needed. Not only servers in the intranet but also external servers, such as internet providers can be used. When external servers are used, the firewall needs to be configured that s can be sent to external servers. *2: The logging s that can be transmitted are described in the table below Files for Transmission. *3: A compressed in Zip format is attached. File attachement is done by uuencode, so client needs to support uuencode function. Table Files for Transmission File Transmission Hourly logging Hourly logging - X Daily logging Daily logging - X Batch logging Batch logging - Snapshot logging Continuous Snapshot logging - X Triggered Snapshot logging - SOE logging SOE logging - Message logging Message logging - OPERATING ENVIRONMENT Autonomous Controller (Except FCN-RTU) Table Hardware Hardware Description Model (CPU) NFCP100 (FCN) or NFJT100 (FCJ) (*1) Style (CPU) S2 or later System card More than 128 MB Note: When there is possibility of power interruption in the electric supply to, please connect an uninterruptible power supply system (UPS). *1: Only single CPU can be used. Software Operating software Revision Table Software Remarks basic software (with Java function) R or later Low Power Autonomous Controller FCN- RTU Hardware Model (CPU) Style (CPU) Software Basic Software Revision License NFCP050 S1 or later Table Hardware Description Table Software Description Basic Software R or later 11 For FCN-RTU, licenses are bundled with CPU module (Model: NFCP050). Select CPU modules with the portfolio licenses required. Feb. 26,

12 The tables below show the operating environment for the following tools. Viewer File Collector Configurator Hardware Model CPU Memory Hard disk Network Media OS Software Web browser (*1).NET Framework Table Hardware Remarks IBM /AT compatible machine Windows 7 (32-bit) Windows Server 2008 SP2 (32-bit) 1 GHz or higher 32-bit (x86) or 64-bit (x64) processor 1 GHz or higher 64-bit (x64) Windows 7 (64-bit) processor 2 GB or larger recommended Free space 20 GB or larger DVD-ROM Table Software Remarks Windows 7 Professional SP1 (32-bit/64-bit) Windows Server 2008 SP2 (32-bit) (*6) Internet Explorer Java Windows 7 Plug-in 7.0 Update 25 (*2) (*3).NET Framework 3.5 SP1 (*4) Windows 7 (*5) Windows.NET Framework 3.0 (*4) (*5) Server *1: Only 32-bit version *2: It is bundled with Application Portfolio Software Media. *3: When it operates on the same with a VDS HMI client, version of Java Runtime Environment including Java Plug-in for both of them have to be the same. *4: This is required for a that uses the logging function, but is not required for a for the configuration function and viewing logging s. *5:.NET Framework is pre-installed in Windows 7 and Windows Server *6: Only logging function is supported. 12 PERFORMANCE The table below describes a rough guide of the CPU load of control application and the collecting capacity of logging function. Autonomous Controller (Except FCN-RTU) Table The collecting capacity of logging function for FCN, FCJ (Guide) CPU load of Control AP Number of logging block High speed Low speed SOE Simple report transmission 40% % X (*1) 25% % X (*1) 25% % X (*1) Note: The capacity described in the table above is a rough guide of the performance. In case other functions such as Java function or transmission function are running simultaneously on FCN/ FCJ, the CPU load should be considered to be higher. Configure the system secured enough to avoid any overloaded operation. *1: When all Simple Reports are sent by . Low Power Autonomous Controller FCN- RTU Table The collecting capacity of logging function for FCN-RTU (Guide) CPU load of Control AP Number of logging block High speed Low speed (*2) SOE Simple report transmission 40% % X (*1) 25% % X (*1) 25% % X (*1) Note: The capacity described in the table above is a rough guide of the performance. In case other functions such as Java function or transmission function are running simultaneously on FCN- RTU, the CPU load should be considered to be higher. Configure the system secured enough to avoid any overloaded operation. *1: When all Simple Reports are sent by . *2: FCN-RTU (NFCP050) style S1 only supports Low Speed type. (5 blocks for 40 %, 10 blocks for 25 %, 16 blocks for 10 %) Feb 26,

13 SOFTWARE DISTRIBUTION Software Distribution Media Portfolio in the information transmission package (InfoWell) is provided in the Application Portfolio media (model number: NT205A). Portfolio License Note: Use of the following tools running on a does not require dedicated licenses. Setup Tool for Portfolio (InfoWell) Offline Configurator and Viewer Applet File Collector Autonomous Controller (Except FCN- RTU) Portfolio License includes an order sheet with an order ID and password on it. After purchasing the product, access Yokogawa s Web site and enter your order ID and password to obtain your license ID. Register the issued license ID in the system card to enable you to use Portfolio. ORDERING INFORMATION Specify the model and suffix codes. 13 TRADEMARKS STARDOM is a trademark of Yokogawa Electric Corporation. InfoWell is a registered trademark of Yokogawa Electric Corporation. Microsoft and Windows are registered trademark of Microsoft Corporation in the United States and/or other countries. is a registered trademark of Xerox Corporation, the United States.v Java is registered trademark of Oracle and/or its affiliates. Other company and product names appearing in this document are trademarks or registered trademarks of their respective holders. Low Power Autonomous Controller FCN-RTU For FCN-RTU, licenses are bundled with CPU module (Model: NFCP050). Select CPU modules with the Portfolio License required. MODEL AND SUFFIX CODES (EXCEPT FCN-RTU) Portfolio License Table Software Model number Suffix code Remarks NT8016J Portfolio license (InfoWell) NT8017J InfoWell License Pack (*1) -L License W Order ID sheet delivery 1 Always 1 1 Always 1 A Standard *1: This license pack includes the following four licenses. - NT8012J: Web Application Portfolio license - NT8013J: Application Portfolio license - NT8014J: Graphics Portfolio license - NT8016J: Portfolio license Subject to change without notice. Feb. 2,