HsinTa SOA Training

1. INTRODUCTION..........................................................................................................................................2

2. SYSTEM ARCHITECTURE........................................................................................................................2

3. SYSTEM DESCRIPTION.............................................................................................................................3

4. SOOTBLOWING STRATEGY....................................................................................................................3

4.1 EXPERT SYSTEM’S RULE BASE.................................................................................................................34.2 RESCUE RULES.........................................................................................................................................34.3 IDLE TIME RULES AND ACTIONS...............................................................................................................34.4 CLEANLINESS RULES AND ACTIONS.........................................................................................................34.5 BLOWING RULES AND ACTIONS DESCRIPTION..........................................................................................3

4.5.1 Economizer blowing approach...........................................................................................................34.5.2 Water Walls blowing approach...........................................................................................................34.5.3 Primary Superheater blowing approach.............................................................................................34.5.4 Platen Superheater blowing approach................................................................................................34.5.5 Secondary Superheater blowing approach.........................................................................................34.5.6 Reheater blowing approach................................................................................................................34.5.7 Air Heaters blowing approach............................................................................................................34.5.8 Special actions....................................................................................................................................3

5. SOA SYSTEM CONFIGURATION AND TUNING..................................................................................3

5.1 SOA SYSTEM GUI...................................................................................................................................35.2 TUNABLE: RESCUE RULES PARAMETERS..................................................................................................35.3 TUNABLE: SECTIONS MAX IDLE TIMES.....................................................................................................35.4 TUNABLE: SECTIONS MIN IDLE TIMES......................................................................................................35.5 TUNABLE: SECTION DESIRED CLEANLINESS.............................................................................................3

6. TROUBLESHOOTING.................................................................................................................................3

6.1 SOA APPLICATION NOT READY...............................................................................................................36.2 CALCULATION MODULE NOT READY........................................................................................................36.3 SOA APPLICATION AND CALCULATION MODULE NOT READY................................................................36.4 ALL SOA MODULES RESTART..................................................................................................................36.5 SOA SYSTEM FAILURE.............................................................................................................................36.6 BOILER NOT READY.................................................................................................................................36.7 REBOOTING DROP 202.............................................................................................................................36.8 REBOOTING SOA WINDOWS MACHINE...................................................................................................36.9 SOA LOGS................................................................................................................................................3

1. Introduction

Sootblowing is an important technique for cleaning boiler heat absorption surfaces and improving heat transfer efficiency. This document describes the methodology of scheduling sootblower sequences based on individual boiler section fouling status for TPC Hsinta Power Plant, unit 4. This document also includes software startup procedures and the user’s guide for the Sootblower Operation Advisory (SOA) software.

The SOA application program runs on a Windows operating system computer and the OVATION Drop 202.

The web-based Graphic User Interface for editing the SOA configuration is provided, and is accessible from the Windows SOA machine through the web browser.

The SOA software starts automatically upon rebooting Drop 202. Restarting SOA software on Windows SOA machine is more complicated. The procedures on restarting SOA software on Windows SOA machine are described in Troubleshooting section.

2. System Architecture

Figure 1. SOA system architecture

Drops functions are described below.

1. SOA MACHINE

Runs SOA application Runs MySQL database

2. DROP 202

Runs SOA modules:a. Data IOb. Calculation module

Originates SOA points – interface between SOA and DCS

3. DROP 7 Runs SOA logics:

a. SOA Control logic (sh210)b. Heat absorption calculations (sh200 – sh205)c. Blowers idle times counters (sh213 – sh222)d. Sequences idle times counters (sh250 – sh254)


4. DROP 22 Runs base sootblowing logics:

a. Blowing permissions b. Blowers control logicsc. Sequences control logics

Runs SOA logics:a. Recommendations alarm logic (sh285)


3. System Description

Given the existing instrumentation including temperature and pressure measurements, the Unit 4 boiler is divided into six different heat absorption areas for analysis purposes. These are:

Economizer

Water Walls

Primary Superheater

Platen Superheater

Secondary Superheater

Reheater

The SOA system also schedules blowing of Air Heaters.

There are wall blowers (IR), retractable blowers (IK) and air heaters blowers (AH) installed on Unit 4. Based on the heat absorption section classification, a set of new sootblower sequences was defined and appear in the following table. These sequences were designed to service all individual Boiler Sections defined.

Name Section No. of steps

Duration [min] Blowers

IR sequence 01 Water Walls 5 70 1, 7, 3, 9, 5

IR sequence 02 Water Walls 5 70 11, 13, 15, 17, 19

IR sequence 03 Water Walls 2 9 22, 24

IR sequence 04 Water Walls 3 13 26, 28, 30



IR sequence 07 Water Walls 20 90 1 – 40





IR sequence 12 Water Walls 10 45 41 – 59

IK sequence 01 Economizer 6 75 101, 102, 103, 104, 105, 106

IK sequence 02 Primary SH 6 75 77, 78, 79, 80, 81, 82

IK sequence 03 Primary SH 6 75 83, 84, 85, 86, 87, 88

IK sequence 04 Secondary SH 4 50 21, 22, 41, 42

IK sequence 05 Secondary SH 6 75 33, 34, 25, 26, 45, 46

IK sequence 05 Secondary SH 6 75 37, 38, 29, 30, 49, 50

IK sequence 07 Secondary SH 16 20021, 22, 41, 42, 33, 34, 25, 26, 45, 46, 37, 38, 29, 30, 49, 50

IK sequence 08 Reheater 6 75 69, 70, 63, 64, 67, 68

IK sequence 09 Reheater 8 100 63, 64, 57, 58, 73, 74, 59, 60

IK sequence 10 Reheater 8 100 67, 68, 95, 96, 97, 98, 99, 100

IK sequence 11 Reheater 18 22069, 70, 63, 64, 73, 74, 57, 58, 67, 68, 59, 60, 95, 96, 97, 98, 99, 100

AH sequence 01 Air heaters 2 40 1, 2

One IR sequence and one IK sequence can run simultanously. One IR sequence and one AH sequence can run simultaneously.

There are two main strategies implemented for this application: Cleanliness Factors and Idle Times. However the main goal of SOA application is to maximize reheat steam temperature level and maintain this level below the DCS setpoint.

4. Sootblowing Strategy

4.1 Expert System’s rule base

The Expert System’s rule base is analyzed every execution of SOA main loop.

The SOA Expert System allows setting priorities to all defined rules. This is a very important tool for creating the desired behavior of the intelligent sootblower software. The valid value of a rule’s priority is from -9999 to 9999. The entire range of priority are divided into groups of five hundreds (e.g. from 0 to 499 or 9500 to 9999). When any rule fires during the Expert System’s evaluation, the rules in groups having priorities lower than the minimum priority of the fired rule’s group are skipped. For example, when a rule with priority equal to 467 fires, the Expert System continues evaluation of rules with priorities higher than 0 and all the lower priority rules are skipped.

The SOA system allows defining modes of operation that can use different priority numbers for the same rule. Some rules can have higher priority in one mode and lower priority in other modes.

For more information refer to Ovation manual SP_0035, “SmartProcess Intelligent SootBlower User Guide”.

The rule base at Hsinta, Unit 4 consists of following groups of rules.

Inhibiting rule

Rescue rules

Idle times rules

Cleanliness rules

No recommendations rule

The Inhibiting rule has constantly the highest priority and they are evaluated first. If the unit load is lower than 400 MW other rules evaluation is skipped.

The Rescue rules priority is always lower than Inhibiting rule and always higher than other rules defined in SOA system.

The No recommendations rule has constantly the lowest priority and are evaluated as the last rules if no rules from higher priority group fires.

The priorities of idle times rules and cleanliness rules depend on a value of SOA strategy point (mode of operation indicator). There are two modes defined at Hsinta, Unit 4:

Idle times mode

Cleanliness mode

When SOA works in Idle times mode, the idle times rules have higher priority than cleanliness rules. In Cleanliness mode, cleanliness rules have higher priority than idle times rules rules.

Switching between the operating modes can be done using operator’s graphic in DCS or SOA GUI.

4.2 Rescue Rules

The rescue rules are provided for maintaining the reheat steam temperature below the DCS setpoint and help other rules to maximize this temperature.

Also, there are rues provided for maintaining Air Heaters outlet gas temperature below the setopint.

The parameters used to configure the rescue rules are available through the web-based GUI.

4.3 Idle time rules and actions

The SOA system compares the maximum allowed idle time for a heat exchange section with the actual elapsed idle time for each sequence. If the maximum allowed idle time of a particular section is exceeded, one of the corresponding sequences is recommended for initiation.

For Hsinta, Unit 4 idle time rules are used to schedule the blowing of six heat exchange sections:

Water Walls (ten sequences used alternatively: IR SEQ01, IR SEQ02, IR SEQ03, IR SEQ04, IR SEQ05, IR SEQ06, IR SEQ08, IR SEQ09, IR SEQ10, IR SEQ11; the idle time between executing Water Walls sequences depends on current level of reheat steam temperature)

Economizer (one sequence: IK SEQ01)

Primary Superheater (two sequences used alternatively: IK SEQ02 and IK SEQ03)

Secondary Superheater (three sequences used only in ADVISORY mode: IK SEQ04, IK SEQ05 and IK SEQ06; in CONTROL mode individual blowers from the Secondary Superheater section are triggered and the idle time between Secondary Superheater blowers depends on current level of reheat steam temperature)

Reheater (three sequences used alternatively: IK SEQ08, IK SEQ09, IK SEQ10; frequency of execution of IK SEQ08 is two times higher than other Reheater sequences)

Air Heaters (one sequence: AH SEQ01)

The idle times configuration for all sections are accessible through the web-based GUI.

4.4 Cleanliness rules and actions

The SOA system analyzes the cleanliness factors of the following heat exchange sections:

Water Walls

Economizer

Primary Superheater

Secondary Superheater (cleanliness rules are active only in ADVISORY mode; in CONTROL mode Secondary Superheater is blown basing on the current level of reheat stem temperature)

Reheater

The current cleanliness factor is compared with desired cleanliness factor for each section. If the current cleanliness is lower than the desired, the section is designated for cleaning.

The minimum idle time of a section blowing must be exceeded in order to execute blowing caused by low cleanliness. This feature was developed to prevent over blowing.

The desired cleanliness values for all sections, as well as minimum idle times are configurable through the web-based GUI.

4.5 Blowing rules and actions description

4.5.1 Economizer blowing approachThe Economizer is blown based on the cleanliness factor and the idle time criteria. One sequences is designated as Economizer sequence: IK SEQ01. The sequence contain all blowers affecting the Economizer heat absorption.

The following flow chart diagrams the blowing approach for the Economizer section.

Figure 2. Economizer blowing

4.5.2 Water Walls blowing approachThe Water Walls section is blown based on the cleanliness factor and the idle time criteria. Ten sequences are used alternatively to blow Water Walls section: IR SEQ01, IR SEQ02, IR SEQ03, IR SEQ04, IR SEQ05, IR SEQ06, IR SEQ08, IR SEQ09, IR SEQ10, IR SEQ11. The idle time between executing Water Walls sequences depends on current level of reheat steam temperature.

The following flow chart diagrams the blowing approach for the Water Walls section.

Figure 3. Water Walls blowing

4.5.3 Primary Superheater blowing approachThe Primary Superheater section is blown based on the cleanliness factor and the idle time criteria. Two sequences are used alternatively to blow Primary Superheater section: IK SEQ02 and IK SEQ03.

The following flow chart diagrams the blowing approach for the Primary Superheater section.

Figure 4. Primary Superheater blowing

4.5.4 Platen Superheater blowing approachPlaten Superheater is not equipped with dedicated soot blowers, however some of the Secondary Superheater blowers are influencing the Platen Superheater heat absorption. Therefore Platen Superheater is cleaned together with Secondary Superheater by using actions and rules provided for blowing Secondary Superheater.

4.5.5 Secondary Superheater blowing approachThe Secondary Superheater blowing depends on SOA working mode.

In ADVISORY mode section blowing recommendations are based on the cleanliness factor and the idle time criteria. Three sequences are used alternatively to blow Secondary Superheater section: IK SEQ04, IK SEQ05 and IK SEQ06.

In CONTROL mode Secondary Superheater blowers are blown individually basing on the blowers idle times. The allowable blowers idle time depends on current level of reheat steam temperature.

The following flow charts diagram the blowing approach for the Secondary Superheater section.

Figure 5. Secondary Superheater blowing – Advisory mode

Figure 6. Secondary Superheater blowing – Control mode

4.5.6 Reheater blowing approachThe Reheater section is blown based on the cleanliness factor and the idle time criteria. Three sequences are used alternatively to blow Reheater section: IK SEQ08, IK SEQ09 and IK SEQ10.

Beside of idle times and cleanliness rules, high priority rescue rules were provided to maximize reheat steam temperature and maintain it below the DCS setpoint.

The following flow charts diagram the blowing approach for the Reheater section.

Figure 7. Reheater blowing

Figure 8. Reheater blowing – High reheat steam temperature

Figure 9. Reheater blowing – Low reheat steam temperature

4.5.7 Air Heaters blowing approachThe Air Heaters are blown based on the idle time criteria and the Air Heaters outlet gas temperature level. There is one Air Heaters sequence defined in the SOA system. The sequence contains both AH blowers.

The following flow chart diagrams the blowing approach for the Air Heaters section.

Figure 10. Air Heaters blowing

4.5.8 Special actionsBesides the rules and actions described above, the following special actions have been implemented:

lowLoadAction – informs that unit load is too low for SOA operation and all rules evaluation is inhibited.

noRecommendationAction – informs that no additional recommendations were generated by the SOA application after evaluating the expert system rule base.

mustRunAction – this action is executed every execution of SOA main loop regardless of Expert system’s rules evaluation. At Hsinta, Unit 4 mustRunAction is responsible for tracking the progress of other actions, calculating constrains for other actions and managing the advisory recommendations.

entryAction – responsible for preparing the sootblowing system for working in CONTROL MODE of an SOA system. The entryAction is executed only once, when the system enters the CONTROL MODE (transition from ADVISORY to CONTROL).

exitAction – responsible for preparing the sootblowing system for exiting CONTROL MODE of SOA system. The exitAction is executed only once, when system exits the CONTROL MODE (transition from CONTROL to ADVISORY).

safeStateAction – triggered when the SOA system encounters an error during executing any action. This error could be caused by

o problems communicating with the DCS

o problems with the syntax of a rule or action

o problems with communicating between SOA system modules

When the safeStateAction is executed during CONTROL MODE operations of the SOA application, the SOA rejects to ADVISORY and performs exitAction.

5. SOA System configuration and tuning

The SOA system allows fine tuning of the advanced sootblowing algorithms by using a number of parameters available on the SOA GUI, “Categorized parameters” page. These parameters can be accessed by the Engineer or Administrator GUI users.

5.1 SOA System GUI

The SOA GUI can be accessed from the SOA Windows Machine or any other machine equipped with Internet Explorer web browser and connected to the Ovation network.

To access the SOA GUI type in following web address:

http://192.168.2.120/

For detailed description on SOA GUI please refer to Ovation manual SP_0035, “SmartProcess Intelligent SootBlower User Guide”.

The modification of tuning parameters can be done by GUI user with the Engineer’s privileges. The other, more complex modifications (e.g. rules or actions modifications) can be done by the Administrator user only.

The following chapter summarizes all tunable parameters available in SOA point categories.

The parameters that belong to the other point categories or are not listed below should never be modified.

5.2 Tunable: Rescue rules parameters

The category “Tunable: Rescure rules parameters” contains the configuration of parameters listed in following table:

Name Alias Description Value

AH_TEMP_SP AH_TEMP_SPAir Heaters outlet gas temperature setpoint 140

RH_TEMP_MAX RH_TEMP_MAX Reheat steam temperature - maximum 539RH_TEMP_SP RH_TEMP_SP Reheat steam temperature - setpoint 537RH_TEMP_MIN RH_TEMP_MIN Reheat steam temperature - minimum 525

5.3 Tunable: Sections max idle times

The category “Tunable: Sections max idle times” contains the configuration of parameters listed in following table:

Name Alias Description ValueECON_max_it ECON_max_it Economizer max idle time [min] 645PRSH_max_it PRSH_max_it Primary SH max idle time [min] 285AH_max_it AH_max_it Air Heaters max idle time [min] 440

http://192.168.2.120/

RH_max_it RH_max_it Reheater max idle time [min] 66

WW_max_it_short WW_max_it_shortWater Walls max idle time – short [min] 50

WW_max_it_long WW_max_it_longWater Walls max idle time – long [min] 100

SSH_max_it SSH_max_it Secondary SH max idle time [min] 220

SSH_blowers_max_it_short SSH_blowers_max_it_shortSecondary SH max idle time – short [min] 45

SSH_blowers_max_it_long SSH_blowers_max_it_longSecondary SH max idle time – short [min] 120

5.4 Tunable: Sections min idle times

The category “Tunable: Sections min idle times” contains the configuration of parameters listed in following table:

Name Alias Description ValueECON_min_it ECON_min_it Economizer min idle time [min] 600PRSH_min_it PRSH_min_it Primary SH min idle time [min] 270AH_min_it AH_min_it Air Heaters min idle time [min] 420RH_min_it RH_min_it Reheater min idle time [min] 50WW_min_it WW_min_it Water Walls min idle time [min] 23SSH_min_it SSH_min_it Secondary SH min idle time [min] 180

5.5 Tunable: Section desired cleanliness

The category “Tunable: Section desired cleanliness” contains the configuration of parameters listed in following table:

Name Alias Description ValueECON_desired_cf ECON_desired_cf Economizer desired CF 0.7WW_desired_cf WW_desired_cf Water Walls desired CF 0.7PRSH_desired_cf PRSH_desired_cf Primary SH desired CF 0.7SSH_desired_cf SSH_desired_cf Secondary SH desired CF 0.7RH_desired_cf RH_desired_cf Reheater desired CF 0.7

6. Troubleshooting

6.1 SOA Application not ready

The following figure depicts a fault condition on the main SOA graphic provided in the Ovation system.

Figure 11. SOA Application not readyIf the SOA application’s status is reported as “NOT READY”, one or more SOA services are not running correctly.

Operator’s reaction: Inform the engineer trained in SOA system maintenance

Engineer’s reaction:On SOA Windows Machine:

Verify if following services are running:

o TransactionKernel

o ConsequenceModule

o ExpertSystem

o IntelligentSootblower

by using the Control Panel\Administrative Tool\Services tool.

If any of these modules is not working, STOP all of them and restart in following order:

o TransactionKernel

o ConsequenceModule

o ExpertSystem

o IntelligentSootblower

On Solaris machine Drop 202 (logged in as wdpf): Verify if DataIO module is running by using the ps command from the Solaris

console:

drop202:/usr/wdpf/init:7 ps -ef |grep PWS root 12391 12387 0 14:20:42 pts/4 0:00 grep PWS root 12344 1 0 12:10:03 ? 7:14 /usr/bin/EmersonPWS/SmartProcessFramework/DataIO/DataIO /usr/bin/EmersonPWS/Smadrop202:/usr/wdpf/init:8

If the DataIO is not running please start by executing script:

/usr/bin/isbstart

drop202:/usr/wdpf/init:9 /usr/bin/isbstart 12406 ? 0:00 DataIODataIO loaded

drop202:/usr/wdpf/init:10

After restarting SOA modules log in to the SOA GUI and check the Dispatcher/Requests history page. The new requests should appear after approximately 5 minutes from SOA modules restart

Figure 12. Request history

6.2 Calculation module not ready


Figure 13. Calculation module not readyIf the Calculation module’s status is reported as “NOT READY”, the Calculation module is not running.

Operator’s reaction: Inform the engineer trained in SOA system maintenance

Engineer’s reaction:On Solaris machine Drop 202 (logged in as wdpf):

Verify if the SOA_calculation_module is running by using the ps command from the Solaris console:

drop202:/usr/wdpf/init:7 ps -ef | grep SOA_calc wdpf 12443 1 0 14:38:32 pts/4 0:00 /usr/wdpf/SOA/SOA_calc/SOA_calculation_module wdpf 12445 12378 0 14:39:32 pts/4 0:00 grep SOA_calcdrop202:/usr/wdpf/init:8

If the SOA_calculation_module is not running please start by executing script:

/usr/wdpf/SOA/SOA_calc/isbstartcalc

drop202:/usr/wdpf/init:6 /usr/wdpf/SOA/SOA_calc/isbstartcalcSOA Calculation Module started

drop202:/usr/wdpf/init:7

6.3 SOA Application and Calculation module not ready


Figure 14. SOA Application and Calculation module not readyBoth the SOA Application and Calculation modules report “NOT READY”, there is a:

Problem with both applications.

Problem with the Ovation software installed on the MMI station.

A network failure.

Verify proper functionality of the Ovation applications (Point Info, Trends, Graphics) on the MMI where the SOA software is installed.

Verify the status of the network connection between the SOA Windows Machine and Ovation MMI (Drop 202). Access a command prompt and type the ping command to check for a valid connection. If there is a problem with the Ovation system or the network connection, review the MMI configuration.

Restart all SOA applications (see previous paragraphs) if the problem is not network related.

6.4 All SOA modules restart

If for any reason all SOA modules must be restarted there should be a following order of tasks maintained:

1. Switch the Intelligent Sootblower from CONTROL to ADVISORY if it’s running in CONTROL mode.

2. Stop DataIO on Drop 202 by using /usr/bin/isbstop script

3. Stop Calculation Module on Drop 202 by using script /usr/wdpf/SOA/SOA_calc/isbstopcalc

4. Stop SOA modules on SOA Windows Machine in following order:

IntelligentSootblower

ExpertSystem

ConsequenceModule

TransactionKernel

5. Wait approximately 2-3 minutes.

6. Start DataIO on Drop 202 by using /usr/bin/isbstart script

7. Start Calculation Module on Drop 202 by using script /usr/wdpf/SOA/SOA_calc/isbstartcalc

8. Start SOA modules on SOA Windows Machine in following order:

TransactionKernel

ConsequenceModule

ExpertSystem

IntelligentSootblower

6.5 SOA System failure


Figure 15. SOA System failedThe indication of SOA system’s status - “NOT READY” when software status is reported as “READY” may happen when SOA system encounters an error while executing any task.

Figure 16. SOA system errorWhen the SOA system encounters any error during the execution of main loop tasks (reading and writing points to DCS, neural networks evaluation, rule base evaluation or consequences actions execution) it switches from CONTROL mode to ADVISORY mode and presents a visible alarm on the main SOA graphic.

This situation indicates two possible problems:

There was a short time communication error during the SOA application’s main loop tasks.

There is a serious configuration problem.

Operator’s reaction:

The operator can verify if the problem is serious by using the “RESET” button on the main SOA graphic. This should be done not earlier than approximately 2 minutes after the failure was reported. If the problem reappears after resetting alarm, this should be reported to the engineer trained in SOA system maintenance

Engineer’s reaction:Engineer should log in to SOA GUI and check the content of “Dispatcher/Request history” GUI page. The page should contain the information on which module has generated a problem and what is the reason of the alarm. Fixing the problem may require:

Restarting some or all SOA modules (please refer to previous paragraphs for instructions)

Changing the system’s configuration – this should be done after consultation with TT project engineer.

6.6 Boiler not ready


Figure 17. Boiler not readyBoiler status is reported as “NOT READY” when one of following conditions happen:

unit’s load is lower than 400 MW

the sootblowing system is switched to LOCAL mode

any blower is in alarm

Switch sootblowing system to REMOTE mode, clear all lower alarms or wait until unit’s load increases above 400 MW.

6.7 Rebooting Drop 202

If for any reason Drop 202 needs to be rebooted, following tasks should be performed in the correct order:


2. Reboot Drop 202.

3. Verify that SOA system is ready after approximately 5 minutes from restarting Drop 202. If any of situations described in previous paragraphs happens, proceed according to the provided instructions.

6.8 Rebooting SOA Windows Machine

If for any reason SOA Windows Machine needs to be rebooted, following tasks should be performed in the correct order:


2. Stop DataIO on Drop 202

3. Reboot SOA Windows Machine

4. Stop SOA modules on SOA Windows Machine in following order:

a. IntelligentSootblower

b. ExpertSystem

c. ConsequenceModule

d. TransactionKernel

5. Wait approximately 2-3 minutes.

6. Start DataIO on Drop 202.

7. Start SOA modules on SOA Windows Machine in following order:

a. TransactionKernel

b. ConsequenceModule

c. ExpertSystem

d. IntelligentSootblower

8. Verify that SOA system is ready after approximately 5 minutes from restarting Drop 202. If any of situations described in previous paragraphs happens, proceed according to the provided instructions.

6.9 SOA logs

Every SOA module generates one or more log files containing information about all fault conditions. Following list summarizes the locations of SOA log files:

1) DataIO:

Drop 202: /usr/bin/EmersonPWS/SmartProcessFramework/DataIO/*.log

2) IntelligentSootblower:

SOA Machine: C:\Program Files\Emerson Process Management PWS\Intelligent Sootblower\IntSootblower\*.log

SOA Machine: C:\Program Files\Emerson Process Management PWS\Intelligent Sootblower\IntSootblower\Logs\*.log

3) ExpertSystem:

SOA Machine: C:\Program Files\Emerson Process Management PWS\SPFramework\ExpertSystem\*.log

4) ConsequenceModule:

SOA Machine: C:\Program Files\Emerson Process Management PWS\SPFramework\ConsequenceModule\*.log

5) TransactionKernel:

SOA Machine: C:\Program Files\Emerson Process Management PWS\SPFramework\TransactionKernel\*.log

Documents

HsinTa SOA Training