Honeywell Benefits Guardianship Newsletter

Welcome

Welcome to the quarterly Benefits Guardianship e-Newsletter. Here you will find the latest product updates, new release information, industry news, and Honeywell Connected Industrials solution articles.

This issue includes information on:

• Enterprise Data Management - Knowledge Article Quarter: Summary of Articles - 2025
• Honeywell Inspection Rounds: Configuring Round suspension in the Planning board
• Honeywell Blending & Movement - KA for Creating an Order for a Movement
• Honeywell Workforce Competency - SMTP Support Added Alongside SendGrid
• UniSim Design Suite Electrolyzer Capability
• Honeywell Alarm Management: Alarm Configuration Manager (ACM) End of Life Extension
• Honeywell Operations Management R246.3 (On-Prem offering)
• Honeywell Production Management - Upcoming release of PAR R3.1.0 in Q3 2025
• List of Knowledge Articles published to Process.Honeywell.com

If you have any questions or comments, please contact us at: GlobalBGPDeliveryCentre@honeywell.com

Enterprise Data Management

Knowledge Article: Summary of Articles - 2025

READ ENTERPRISE DATA MANAGEMENT ARTICLES

Uniformance Products (PHD/UI/CHC/UPS/AFM)

Honeywell Inspection Rounds (HIR)

The Rounds Suspension feature in Honeywell Inspection Rounds is designed to maintain operational integrity and regulatory compliance during periods when inspection activities cannot be performed. Here's a breakdown of its key uses:

Primary Use of Rounds Suspension

1. Operational Flexibility
   It allows plant managers or system administrators to temporarily pause inspection schedules without deleting or modifying them. This is especially useful during:
   • Plant Turnaround
   • Equipment Overhauls
   • Emergency shutdowns
   • Environmental or safety hazards
2. Audit and Traceability
   Suspension events are logged with metadata such as:
   • Timestamp of suspension and reactivation
   • Reason for suspension
   • User who initiated the action
   • Affected assets or areas

In scenarios where field operations across the plant or enterprise are temporarily halted due to scheduled or unscheduled maintenance, and operators are unable to execute their assigned rounds, the 'Rounds Suspension' functionality within Honeywell Inspection Rounds can be enabled to prevent compliance issues.

This Newsletter provides step-by-step instructions about how to suspend Rounds in the Honeywell Inspection Rounds portal.

Configuring Suspension in Planning Board

You need explicit permission to perform these actions (Planning Board Admin). Contact the Honeywell support engineer to obtain the required user role.

There are two options to Suspend Rounds:

• Suspend all Rounds that are scheduled for a specific level
• Suspend only those Rounds that are based on a particular round template

Suspend all rounds for a level

Perform the following steps to suspend all Rounds that are scheduled for a level:

1. Navigate to the Planning Board.
2. Choose [icon: toolbar] in the toolbar below the navigation bar. The Scheduled suspensions dialog opens.
3. Select the level for which you want to suspend all Rounds from the tree on the left.
4. If you want to suspend all Rounds for a specific level, select the relevant level from the tree on the left.
5. Choose [+] in the upper right corner of the Suspensions on hierarchy level section.
6. Enter the type of the round suspension in the Type field.
7. Enter a description for the round suspension in the Description field.
8. Enter a start time and start date for the round suspension in the Start from fields.
9. Enter an end time and end date for the round suspension in the End on fields. When the end time and end date is reached, the rounds are not suspended anymore.
10. Choose Save.

A notification indicates whether the round suspension is successfully saved.

11. Close the notification by clicking outside the notification. You see the new round suspension in the Suspensions on hierarchy level section.
12. Close the Scheduled suspensions dialog.
13. Refresh your browser window to display your changes.

Now, the suspended Rounds are displayed with the Suspended status tag in the Round Status column of the rounds table. The suspended Rounds are grayed out on the Schedule table.

Suspend all Rounds based on a particular Round template

Perform the following steps to suspend all Rounds that are based on a particular Round template:

1. Navigate to Planning Board. You can see the round templates on the rounds table. The Round templates are displayed with the Template status tag in the Round Status column.
2. Right-click the relevant round template and choose the schedule from the context menu. The Scheduling dialog opens.
3. Choose [icon: plus] in the upper right corner of the Scheduled suspensions section. The Configure suspension dialog opens
4. Enter the type of the round suspension in the Type field.
5. Enter a description for the round suspension in the Description field.
6. Enter a start time and start date for the round suspension in the Start from fields.
7. Enter an end time and end date for the round suspension in the End on fields. When the end time and end date is reached, the rounds are not suspended anymore.
8. Choose Save. A notification indicates whether the round suspension is successfully saved.
9. Close the notification by clicking outside the notification. You see the new round suspension in the Scheduled suspensions section.
10. Close the Scheduling dialog.
11. Refresh your browser window to display your changes.

Now, the suspended Rounds are displayed with the Suspended status tag in the Round Status column of the rounds table. The suspended Rounds are grayed out on the Schedule table.

Once a round is suspended, it becomes inaccessible to workers until the suspension period expires. You can continue with the following actions:

• Suspend other Rounds
• Edit this Round suspension or other already active round suspensions
• Delete already active round suspensions.

HIR SaaS Updates Details

The most recent version update is Honeywell Inspection Round R8.4.6. Below are the details of the update.

Honeywell Inspection Rounds R8.4.6 update

• [MOVOR-19530] – Native Dashboard (ND) : Bug fixes
• [MOVOR-19328] - Movelets : Map view is not working in ART
• [MOVOR-19361] - Recommendations tile should be aligned correctly to see the priority & type correctly at the bottom
• [MOVOR-19374] - Dashboard : Filter not working as expected when navigating to third page from incidents pie chart
• [MOVOR-19671] - Easyconfig - User should be taken to page number 1 by default in Round Results page
• [MOVOR-19585] - EasyConfig Bug Fixes
• [MOVOR-19590] - Started rounds in Edit rounds screen issues
• [MOVOR-19554] - Issue page missed entry to be deleted when the round started in online mode and completed in offline mode, later synced
• [MOVOR-19704] - Mobile - Readings, Comments, Observation are vanished when user Redoes the round
• [MOVOR-19602] - 500 Internal server error when navigating to second depth ND page
• [MOVOR-19574] - ND api: Missing security header in https response
• [MOVOR-19573] - Missing security headers in https response
• [MOVOR-19702] - Easyconfig - Round Result Page keeps on loading even though round results are existing
• [MOVOR-19691] - Easyconfig - Page Keeps on loading when user clicks on Load Attributes button in the Assets page
• [MOVOR-19690] - Easyconfig - Export level is failing with error SEVERE: (TypeError) : Cannot read properties of undefined (reading 'map_0')
• [MOVOR-19689] - Easyconfig - Type and Value fields are optional during extending the task but currently shows as mandatory
• [MOVOR-19715] - Missing Secure and HTTPOnly Flags for Cookies for cookies
• [MOVOR-19692] - Mobile : Issue with asset has no task
• [MOVOR-19708] - Easyconfig - User is not able to edit and submit this Asset
• [MOVOR-17719] - Security Risk: Twistlock - Third party container image for gridgain contains issues
• [MOVOR-17699] - Security Risk: BDH - Spring Framework
• [MOVOR-19147] - Security Risk: PSIRT - Envoy Proxy - HTTP/2 Continuation frames can be utilized for DoS attacks
• [MOVOR-19312] - EasyConfig (Acelen/Inovyn) : Filters are getting reset after approval of rounds in Round Approval Page
• [MOVOR-19455] - Fix Twistlock and BDH issues in ND API, ND Common and Write API
• [MOVOR-19454] - Upgrade latest GridGain and deploy in OR
• [MOVOR-19610] - Upgrade GridGain R8.9.9, check security reports and validate ND
• [MOVOR-19519] - adjust get userInfo for ADFS non-standard behaviour
• [MOVOR-19521] - EasyConfig : Download Errors button needs to be enabled for errors <=5
• [MOVOR-19510] - EasyConfig: Add limit type and deviated limit value to the Task table in the Asset details page of Round result (show in red)
• [MOVOR-19314] - security remediation for media, hfir-rest, service-event components
• [MOVOR-19408] - MAF : Adjust the deletion DCs based on index
• [MOVOR-19551] - MAF : Add an index based on scheduled start time for both round result and missed
• [MOVOR-19513] - MAF : Delete MAF index after MD deletion
• [MOVOR-19540] - Round when started in offline mode and later synced in online mode shows the status as Inprogress in Round Result section
• [MOVOR-19619] - MAF: Use the new index of scheduled start time for fetching the issues during cleanup job
• [MOVOR-19577] - Movelets : Add reExecuted flag inside attached properties
• [MOVOR-19608] - MAF: Resolve compatibility issues due to changes of MAF Server Framework
• [MOVOR-19647] - MAF : Adjust missed scheduler not to set missed for re-executed rounds
• [MOVOR-19488] - MAF: Script to trigger Task Deviations for R7 & R8
• [MOVOR-19642] - Create consolidated Connector build (binaries, reports) from R8.4.1 to R8.4.6.
• [MOVOR-19643] - Create consolidated SQL scripts from R8 to R8.4.6
• [MOVOR-19649] - Check and include exception handling for SQL Script execution in Connector installer
• [MOVOR-19458] - ND API: API to get all tasks deviation details irrespective of limit criticality, limit type or the drill down filters
• [MOVOR-19611] - Connector: Include issue id for rounds to have hyperlink to Approval workflow
• [MOVOR-19612] - ND API: Make query changes to get issue id for rounds and validate
• [MOVOR-19552] - HFIR-REST: Adjust Issue listBy category API
• [MOVOR-19578] - HFIR-REST: Update the APIs error message header and handle the duplicate Users error message
• [MOVOR-19451] - Dashboard : PART-4 - Field operation should be able to view the all tasks deviation details at one go irrespective limit Criticality and Type
• [MOVOR-19453] - Dashboard : Navigation Label name on the top of the page to be changed from "Asset -> Deviation" to "Assets with "Critical/Medium/Low" Task Deviation"
• [MOVOR-19452] - Dashboard : Top 10 count by rank KPI && DATA With level separate by category KPIs placement to be swapped to accommodate more details.
• [MOVOR-19339] - ND : Display the bar chart for re-executed rounds when qty is 0
• [MOVOR-19587] - EasyConfig : Consume the new listBy api to display the list of issues based on issue category
• [MOVOR-19525] - EasyConfig : Enhancements in round result
• [MOVOR-19485] - Create ND installer
• [MOVOR-19486] - Validate ND installer
• [MOVOR-19462] - Generate R8.4.6 consolidated build and validate
• [MOVOR-19614] - Create R8.4.6 Connector installer and validate the migration scenario
• [MOVOR-19615] - Create R8.4.6 ND installer and validate
• [MOVOR-19405] - create MAF index to prevent unnecessary DC generation when cleanup issues
• [MOVOR-19509] - EasyConfig : Deviation comment to be made visible in deviation tab (currently only in asset details page visible)
• [MOVOR-19365] - Dashboard : PART-1 - Field operation should be able to view the all tasks deviation details at one go irrespective limit Criticality and Type
• [MOVOR-19449] - Dashboard : PART-2 - Field operation should be able to view the all tasks deviation details at one go irrespective limit Criticality and Type
• [MOVOR-19450] - Dashboard : PART-3 - Field operation should be able to view the all tasks deviation details at one go irrespective limit Criticality and Type
• [MOVOR-19586] - EasyConfig/ND : Regenerate security scan reports (BDH, Twistlock, Coverity)
• [MOVOR-19533] - Security vulnerability fixes for oidc-auth, logout and tokenx
• [MOVOR-19621] - HFIR-REST: Migrate Issues entity to create new indices
• [MOVOR-19638] - QA Testing Tasks + Any Bug Fixes
• [MOVOR-19504] - EasyConfig/ND : Security Scan fixes and reports (BDH, Twistlock, Coverity)
• [MOVOR-19499] - Security vulnerability fixes for auth service
• [MOVOR-19404] - security remediation for portal/portal-sdk
• [MOVOR-19403] - security remediation minio/nginx-unprivileged/redis
• [MOVOR-19402] - Security remediation for event consumer dispatcher

Article submitted by – Abirami Chidambaram, HCI Technical Support – Honeywell Inspection Rounds.

Honeywell Blending and Movement

Supported Releases

Releases Approaching Phased Out Date

PBM R510.x will be phased out in September 2025.

Phased-Out: For Standalone Software Product releases which have been Phased-Out, HPS intends to make commercially reasonable efforts to provide support as, and if, available consisting of technical assistance for product use, lost/damaged software media replacement and reference materials download. "Phased-out" Support applies to releases older than R-2.

1. Limited TAC support will be available.
2. Honeywell may not always be able to enter into a contract for Phased-out releases due to technology or resource considerations. Any contract would exclude PAR fixes.
3. For all PARs, "commercially reasonable effort support" will be provided, typically including answering questions and offering advice, but problem fixes will require upgrading to a release in the "Current" support phase.
4. Fixes developed for later releases generally will not be ported back to Phased-out releases.
5. Product documentation updates will not be provided.

Creating an Order for a Movement that has Already Started (Log Started)

The following workflow is used to create an order for a movement operation that is already started and is currently "active" or flowing. This technique will create the Open Logs for the movement, with the appropriate start time. MM's historian is used to capture the available log data at the time the start event occurred.

1. Create an order as usual.
2. In the Order Detail - Task Definition tab, set the Log Time for Task Start in the Work Item Conditions to the time (in the past) that the movement started.
3. Update the order. Correct any errors found if needed. (Note: Order update validation will ensure that the Log Time for Task Start is earlier than the current date and time.) In the Work Item Conditions, the Task Start Condition is set to Date_Time.
4. Release the work item to the task handling processes.
5. The task and sequences are created as usual. The task start condition is set to the specified Log Time for Task Start (in the past). The Already Flowing option is automatically selected for each sequence in the task.
6. Once path selection, path approval and sequence lineup has been performed, the sequences are started automatically. Note that because the sequences are marked as already flowing, the path selection process is simplified. (A subset of the normal path selection checks is performed.)
7. A Task Open Log is created for the task and a Component Open Log is created for each sequence.

The data available from the historian at the configured Log Time for Task Start time is used as the source of the log data. For the data collected from the real-time system (i.e. from RTDR), the values displayed will be those at the time that the snapshot is taken (not the log started time). For the Component Open Logs, the AlreadyFlowing event attribute will show True, to indicate that this is a delayed log for an already flowing movement.

Order History Notes:

In the Order History display, the TaskOpenLog and ComponentOpenLog timestamps that appear in the Logged Information column header show the date and time that the log was generated. They are not the start time for the movement (that occurred in the past). The start time that was configured as the Log Time for Task Start for the work item, appears as the StartTime and EndTime entries for the Open Logs instead.

The Scheduled Start dates and times for the order, work item and end points in the Planning Information table are set to the configured Log Time for Task Start date and time (in the past). If a Task Stop condition has not been configured for the work item in the Order Detail, then the Scheduled End date and times are set to the date and time that the order was created. (This Scheduled End behavior is normal. It has not been changed.).

8. Control the movement operation using the task handling displays as usual. The remaining event logging operations will occur as usual.
9. If a new end point is added after the work item was released, the new end point is treated as a normal end point/sequence addition. The new sequence is not assigned the Log Time for Task Start. (This makes it possible to add new sequences in the normal way. However, if you set up the work item incorrectly (prior to releasing it for the first time), then you cannot go back and correct the logs by adding or removing end points.)
10. When the movement is finished, complete the task and close the order as usual.

ATTENTION: If you need to create multiple orders that started in the past, they must be entered in chronological order (with the order that started earliest entered first, and so on). This is necessary to ensure that end point sharing and volume information is determined correctly.

Creating an Order for a Movement that Started and Stopped in the Past (Log Completed)

The following workflow is used to create an order for a movement operation that started and stopped in the past. This technique will create the Open and Complete Logs for the movement with the appropriate start and stop times. MM's historian is used to capture the available log data at the time the start and stop events occurred.

1. Create an order as usual.
2. In the Order Detail - Task Definition tab, set the Log Time for Task Start and the Log Time for Task Stop in the Work Item Conditions, to the times that the movement started and stopped.
3. Update the order. Correct any errors found if needed. Order update validation will check the following:
   • The Log Time for Task Start and for Task Stop must be earlier than the current date and time.
   • If a Log Time for Task Stop has been entered, then a Log Time for Task Start must also be entered.
   • The Log Time for Task Start must be earlier that the Log Time for Task Stop.
4. In the Work Item Conditions, the Task Start Condition is set to Date_Time and the Task Stop Condition remains unchanged.
5. Release the work item.
6. An Open Log and a Complete Log are created for the movement. Component Open Logs and Component Complete Logs are created for each end point. The Log Times for Task Start and Task Stop set in the Order Detail are used as the Start and End Times for the logs.

The data available from the historian at the configured Log Time for Task Start and Task Stop times is used as the source of the log data. The status of the order, work item and end points is set to InReconciliation.

Notes:

A task and sequences are not created when the work item is released. The work item is never handed over to the task handling processes.

Only data that can be collected from the historian is added to the logs. (Data that would normally be collected from the real-time system (i.e. from RTDR) will not be added to the Open or Completed Logs.) Real-time data cannot be displayed in this case. If this data is needed, then it must be historized.

As Log Started orders, the Open or Completed Log timestamps that appear in the Logged Information column header in the Order History display, show the date and time that the log was generated. They are not the start or stop time for the movement (that occurred in the past).

The Scheduled Start and Scheduled End dates and times for the order, work item and end points in the Planning Information table are set to the configured Log Time, Task Start and Task Stop dates and times (in the past). The only exception is the Scheduled End date and time for the order. As always this shows the date and time that the order was created.

6. Close the order as usual.

ATTENTION: If you need to create multiple orders that started and stopped in the past, they must be entered in chronological order (with the order that started earliest entered first, and so on). This is necessary to ensure that end point sharing and volume information is determined correctly.

Honeywell Workforce Competency

SMTP Support Added Alongside SendGrid

Honeywell Connected Workforce Competency is a cloud-deployed, simulation-based, and scalable solution designed to deliver comprehensive process training for operations personnel. It enables trainees to gain both knowledge and hands-on experience in executing, analyzing, and making decisions--anytime, anywhere, with expert mentoring.

With the release of version R1.0.3, a key enhancement has been introduced to improve email communication flexibility within the platform.

What's New in Release R1.0.3?

The application now supports SMTP (Simple Mail Transfer Protocol) in addition to SendGrid for email transmission. This update gives customers the flexibility to choose their preferred email service provider or even configure their own SMTP server.

Understanding SMTP and SendGrid:

• SMTP is the core protocol used for sending emails across the internet. It defines how messages are transmitted between mail servers.
• SendGrid is a cloud-based email delivery service that uses SMTP under the hood but also provides advanced features such as analytics, templates, and delivery optimization.

Why Add SMTP Support?

Supporting SMTP alongside SendGrid offers several benefits:

• Cost Efficiency: Customers can deploy their own SMTP Exchange servers, avoiding licensing fees from third-party providers.
• Greater Control: Self-hosted SMTP servers allow for more granular control over email delivery, security, and compliance.
• Flexibility: Customers are no longer tied to a single provider.

Configuration Requirements

To enable SMTP support, customers must:

1. Deploy an SMTP Exchange Server.
2. Configure the SMTP server's IP address in the application settings.
3. Ensure the SMTP port is open on the firewall to allow email traffic.
4. Set the feature flag in the environment variables during deployment to activate SMTP support.

Note: SMTP configuration is handled during tenant creation by Honeywell. Users will not see an option to select SMTP within the application UI.

Is there any impact on the existing Cloud System?

There is no change to the default configuration. SendGrid remains the default email service provider in the application. This update simply introduces SMTP as an additional option, giving customers who which to install on their own private cloud the freedom to configure their own email infrastructure if desired.

Conclusion

This enhancement in R1.0.3 empowers customers with more flexibility and control over their email delivery systems. Whether continuing with SendGrid or transitioning to a custom SMTP setup, the application now supports both options seamlessly ensuring reliable communication tailored to each organization's needs.

Honeywell Workforce Competency Updates

Honeywell Workforce Competency R530 update

The latest update for Workforce Competency R530 is 530.2.1.0 (released on March 11th, 2025)

• 2/27/2025 HCPP-29478: Fix for TPS LOGIC block LOENBL with FL1 stuck.
• 2/27/2025 HCPP-29309: Fixed error in CL toolkit translation by adding logic for "when error" clauses in CL wait statements
• 2/27/2025 HCPP-27160: If R521.3 installed on PTS and the Yokogawa machines, It throws unwanted alarms and trips (Rebuilt)
• 2/27/2025 HCPP-29602: Implementation of PRD mode for Yokogawa PID controllers in Master-Slave configuration in OTS
• 10/2/2025 HCPP-29611: CS3000: IOP is not getting triggered in PID controller
• 10/2/2025 HCPP-29316: DSMDLL compilation of CS3000 DCS translated output throws errors for CALCU and LC64 blocks
• 10/2/2025 HCPP-29572: CS3000 translation failed by toolkit in PTS R530
• 3/02/2025 HCPP-29567: The PTS is creating SNST snapshot and exercise goes freeze though the auto save session state option is disabled in Workforce Competency.
• 3/02/2025 HCPP-27379: PTS Snapshot does not retain controller modes in CS3000 emulated layer
• 3/02/2025 HCPP-27338: FUNC-VAR block is not working as intended, Calculated PV (CPV) is not correct
• 3/02/2025 HCPP-29391: SIO-11 block logic is not working as intended
• 3/02/2025 HCPP-29362: SM Emulation: The Safety Manager First Out Alarm logic using ANN Type blocks not working in PTS
• 3/02/2025 HCPP-29390: SIM-SM Adapter and SCADA Adapter availability with ProSim bridge Solution
• 3/02/2025 HCPP-28944: GE Mark Vie controller version i.e., 06.08.00C Qualification
• 3/02/2025 HCPP-29388: Enable alarm parameters R/W for FBControlOp
• 3/02/2025 HCPP-29389: PTS App option to avoid dialog on model close
• 3/02/2025 HCPP-29226: IFS muti-OTS
• 1/16/2025 HCPP-29273: Fix for TPS Ratio block to include overall bias in output calculation
• 1/16/2025 HCPP-29272: Fix for TPS OrSel block CVEUHI/LO parameter should track XEUHI/LO and not downstream SPEUHI/LO.
• 1/16/2025 HCPP-26222: Save Location for Saving Event is not kept in the specified path when event is modified
• 1/16/2025 HCPP-29330: Unable to change the role of another domain user in user manager
• 1/16/2025 HCPP-28899: CEE Adapter: Communication fails from CeeAdapter to EPKS Input blocks with "CDA Error Message: %s: Change Not Permitted
• 1/16/2025 HCPP-28838: The Cee Adapter Model communication fails with an Error "Problem with SyncWrite of AI's to EPKS server
• 1/16/2025 HCPP-29400: The SIM SM Adapter snapshot files should be included in the Export Snapshot feature in PTS.
• 1/16/2025 HCPP-29146: The Cee Adapter Model communication fails with an Error "Problem with SyncWrite of AI's to EPKS server"
• 1/16/2025 HCPP-28923: BCAS mode related to SIM2 gcb, Shape(s) and Faceplate(s) in WFC R521.4
• 1/16/2025 HCPP-28736: Generic framework adapter does not read the DCS values after loading snapshot
• 1/16/2025 HCPP-28645: RQUP-04554271 CS3000 Toolkit: network card I/O to be supported
• 1/16/2025 HCPP-27763: CPV tracking downstream Value disabled when OTRK=low
• 1/16/2025 HCPP-27419: Rockwell API thread startup logic that can result in thread hangs which freezes the RSLogixSimServer
• 1/16/2025 HCPP-27378: TRB: DeltaV Toolkit is not processing double quotations correctly; therefore, it continues to read in the entire file causing an out of memory error.
• 1/16/2025 HCPP-27351: PIDALL_CCS block is ramping its PV to SH value when it is changed from MAN to AUT mode
• 1/16/2025 HCPP-26679: Exatif synchronization message when a snapshot takes long to load.
• 1/16/2025 HCPP-29305: SM Emulation: The Safety Manager First Out Alarm logic using ANN Type blocks not working in PTS
• 1/16/2025 HCPP-27758: TRB: CCC adapter is not writing the StepSize parameter on the CCC Emulator
• 1/16/2025 HCPP-27372: TRB: DeltaV Step timing out too soon.

Honeywell Workforce Competency R521 update

The latest update for Workforce Competency R521 is R521.5.1.0 (released on September 9th, 2024)

• 02/08/24 HCPP-28645: DE: CS3000 Toolkit: network card I/O to be supported
• 05/08/24 HCPP-28381: PTS speed reported is less than minimum speed in this case of SIMIT Adapter (refer 2x Speed)
• 05/08/24 HCPP-28382: When launched the Model without Starting the SIMIT OPC didn't notice any Error reporting Time Out of the SIMIT OPC
• 05/08/28 HCPP-28590: Reset tag which is set to HIGH before saving the snapshot is coming back to LOW after reloading the snapshot
• 06/08/24 HCPP-28923: BCAS mode related to SIM2 gcb, Shape(s) and Faceplate(s) in WFC R521.4
• 09/08/24 HCPP-27963: TRB: BW-63870: R521.3.0 Yokogawa Server Connection Failing Between PTS for R521.3.0 Yokogawa Server
• 19/08/24 HCPP-28736: Generic framework adapter does not read the DCS values after loading snapshot
• 19/08/24 HCPP-28899: CEE Adapter: Communication fails from CeeAdapter to EPKS Input blocks with "CDA Error Message: %s: Change Not Permitted"
• 04/09/24 HCPP-28838: PTS: The Cee Adapter Model communication fails with an Error "Problem with SyncWrite of AI's to EPKS server"

Honeywell Workforce Competency R520 update

The latest update for Workforce Competency R520 is 520.3.3.0 (released on February 7th, 2025)

• 01/09/25 HCPP-29330: Unable to change the role of another domain user in user manager
• 09/20/24 HCPP-28838: The Cee Adapter Model communication fails with an Error "Problem with SyncWrite of AI's to EPKS server"
• 09/20/24 HCPP-28899: CEE Adapter: Communication fails from CeeAdapter to EPKS Input blocks with "CDA Error Message: %s: Change Not Permitted
• 09/20/24 HCPP-26875: SM CDA points in alarm do not show in the Station's alarm display.

Article submitted by – Anne Colençon, HCI Technical Support – Workforce Competency.

UniSim® Design Suite

UniSim Design – Electrolyzer Capability

This article describes electrolyzer module features and its usability in UniSim Design.

The electrolyzer is an apparatus that produces hydrogen through a chemical process (electrolysis) capable of separating the hydrogen and oxygen molecules of which water is composed using electricity.

In contrast to all other methods of hydrogen production, the electrolyzer is the only commercially available technology that can produce high-purity hydrogen without the involvement of hydrocarbon feed or carbon emissions.

Typically, an electrolysis system consists of a water container containing an electrolyte and two electrodes: a cathode (negative pole) and an anode (positive pole). A chemical reaction occurs on both sides of the electrolyte by directing an electric current to both electrodes. Hydrogen is released on the cathode side and oxygen on the anode side.

[Diagram: Electrolysis of water showing H2 output from cathode and O2 output from anode, with DC supply in between.]

Types of Electrolyzers

UniSim Design supports modeling of the two best-known electrolyzers for hydrogen, the Alkaline Electrolyzer (AEL) and the Proton Exchange Membrane (PEM) Electrolyzer

The Alkaline Electrolyzer (AEL)

A alkaline electrolyzer uses liquid electrolyte solution and water. The water in this electrolyte is split into hydrogen and hydroxide ions at the cathode. These ions are then brought into contact with a membrane, after which they are oxidized to water and oxygen at the anode.

Chemical Reactions:

Cathode: 2 H₂O + 2e^- → H₂ + 2 OH^-
Anode: 2 OH^- → ½ O₂ + 2e^- + H₂O
Total reaction: H₂O → H₂ + ½ O₂

UniSim Design supports only NaOH and KOH as electrolytes for AEL.

The Proton Exchange Membrane Electrolyzer (PEM)

A PEM electrolyzer uses a polymer membrane that allows only hydrogen ions to pass through. The water is split into oxygen, hydrogen ions and two electrons at the anode. The hydrogen ions and the two electrons then pass through the membrane and are converted to hydrogen at the cathode.

Chemical Reactions:

Anode: H₂O → H₂ + ½ O₂ + 2e^-
Cathode: 2H⁺ + 2e^- → H₂

PEM electrolyzers are the most popular because they produce high-purity hydrogen. They are best suited to match the variability of renewable energies and are compact. On the other hand, they are somewhat more expensive because they use precious metals as catalysts.

How to configure an Electrolyzer in UniSim Design?

UniSim Design supports modeling of AEL and PEM Electrolyzers in both steady state and dynamics.

To add an electrolyzer, open the Object Palette and select the Electrochemical Reactors sub-palette:

[Screenshot of UniSim Design Suite Object Palette showing 'Electrochemical Reactors' sub-palette selected.]

The required inputs are similar for both types of electrolyzer.

Design tab

The Connections page is used to configure the anode and cathode side input and output streams along with energy streams:

[Screenshot of UniSim Design Suite 'Alkaline Electrolyzer' - Design tab, Connections page, showing Anode Inlet, Anode Outlet, Cathode Inlet, Cathode Outlet, and Energy inputs.]

PEM:

[Screenshot of UniSim Design Suite 'PEM ELX. (TRAIN-A)' - Design tab, Connections page, showing Anode Inlet, Anode Outlet, Cathode Inlet, Cathode Outlet, and Energy inputs.]

The Parameters page is used to specify the pressures at the anode and cathode.

Specifying the AEL Electrolyzer

For AEL electrolyzer, users can specify either current or anode / cathode current density or stack power. UniSim Design back calculates the other parameters based on user input.

1. Specify input current - UniSim Design calculates anode and cathode current densities, stack temperature, operating voltage per cell, stack power and stack voltage.
2. Specify either anode or cathode electrode current density - UniSim Design calculates current, another electrode current density which is not specified, stack temperature, operating voltage per cell, stack voltage and stack power.

[Screenshot of UniSim Design Suite 'Alkaline Electrolyzer' - Parameters tab, showing Pressure, Current, Stack Power, Number of Cells, and Stack Temperature inputs/outputs.]

Specifying the PEM Electrolyzer

For the PEM Electroyzer, the user must specify Faraday Efficiency and the Number of Cells present in the electrolyzer stack.

1. Specify input current / current density and efficiency - UniSim Design calculates cell temperature, stack power and stack voltage.
2. Specify stack power and efficiency - UniSim Design calculates input current / current density, stack voltage and cell temperature.

[Screenshot of UniSim Design Suite 'PEM ELX. (TRAIN-A)' - Parameters tab, showing Pressure, Number of Stacks, Current, Power, Number of Cells, and Temperature inputs/outputs.]

Rating tab

The Sizing page is used to specify electrode, membrane, current densities and tuning factors. The Electrode Data section is used to specify electrode and membrane geometry and properties respectively. The Water And Electrolyte Data section consists of the Water Activity, which is a calculated and the Electrolyte Resistivity which is a user specification. Limiting Current Density must be specified by the user whilst current densities and charge transfer coefficients are calculated. Electrode data, membrane data, electrolyte resistivity and limiting current density are given default values, but these can be changed by the user as required.

AEL:

[Screenshot of UniSim Design Suite 'AEL-101' - Rating tab, Electrode Data section, showing Anode Surface Area, Cathode Surface Area, Anode Membrane Gap, Cathode Membrane Gap, Anode Thickness, Cathode Thickness, Water Activity, Electrolyte Resistivity, Limiting Current Density, Tuning Factors, and Solver Option.]

[Screenshot of UniSim Design Suite 'AEL-101' - Rating tab, Membrane section, showing Thickness, Surface Area, Porosity, Tortuosity, Wettability Factor, Hydrogen Crossover, Membrane Permeability, and Gas Diffusion Coefficient.]

PEM:

[Screenshot of UniSim Design Suite 'PEM ELX. (TRAIN-A)' - Rating tab, Membrane section, showing Membrane Dry Mass, Membrane Thickness, Membrane Equivalent Area, Membrane Density, Water Transport details, Electrode details (Anode Charge Transfer Coeff, Cathode Charge Transfer Coeff, Anode Exchange Current Density, Cathode Exchange Current Density, Electrode Resistance, Current Density, Limiting Current Density), and Solver Options.]

The Degradation page allows users to estimate degradation of electrolyzer over a required period of operation. Rated Power, Rated Current and Degradation Percent Per Year are user specified variables. In Steady State, the user must also specify the Run Length (total number of hours the electrolyzer is in operation). Once the Enable Degradation check box is active, the degradation resistance is calculated based on the specified inputs. In Dynamics, the Run Length is taken directly from the simulation run time and cannot be specified by the user.

[Screenshot of UniSim Design Suite 'PEM ELX. (TRAIN-A)' - Degradation tab, showing Enable Degradation checkbox, Rated Power, Rated Current, Degradation [%/yr], Run Length Completed [Hours], and Degradation Results.]

The Performance page provides information on the calculated parameters, including overpotentials, cell Temperature and Heat Loss. Also, it gives Total Power, Total Hydrogen Produced and Total Heat Loss.

PEM:

[Screenshot of UniSim Design Suite 'PEM ELX. (TRAIN-A)' - Performance tab, showing Cell details (Open Circuit Potential, Activation Overpotential, Ohmic Overpotential, Concentration Overpotential, Total Voltage Per Cell, Anode Activation Overpotential, Cathode Activation Overpotential) and Plant details (Total Power, Total Heat Loss, Total Hydrogen Produced).]

In addition, for the AEL electrolyzer, Effective H2 Diffusion, Hydrogen Cross Glow and Hydrogen to Oxygen % by moles will be shown.

AEL:

[Screenshot of UniSim Design Suite 'AEL-101' - Performance tab, showing Cell details (Temperature, Heat Loss) and Plant Data (Total Power, Total Heat Loss, Total H2 Produced).]

Dynamics Tab

The Specs page is used to configure the dynamic specifications and parameters. The user can set the Dynamic Operating Mode as either Current Spec or Power Spec. Current spec means the current is the specified variable, whilst Power spec means heat flow is specified in the electrolyzer energy stream.

The resistance to the flow is based on the cell geometry parameters (anode surface area and cathode surface area) specified by the user on the Rating tab. Pressure-Flow resistances k1 and k2 are calculated from the specified pressure-flow tuning factors according to:

k1
k2 = PF Tuning Factor * Anode (or) Cathode surface area

Anode and Cathode cell volumes indicate the volume occupied by the fluid on the respective sides:

[Screenshot of UniSim Design Suite 'AEL-101' - Dynamics tab, showing Parameters (Dynamic Operating Mode, Pressure Flow Tuning Factors), Cell Volume (Anode Segment, Cathode Segment).]

Article submitted by Irina Florea, UniSim Design Suite Global Support Team

Honeywell Forge Alarm Management

Alarm Configuration Manager (ACM) End of Life Extension

After careful analysis, we have decided to extend support for ACM by 12 months. With this extension, ACM Phased-Out Support will begin December 31, 2026. All support ends December 31, 2027.

This decision is aimed at helping customers successfully migrate from ACM to APO by December 31, 2027.

Important Dates:

• December 31, 2025: End of Sale
• December 31, 2026: Beginning of Phased-Out Support
• December 31, 2027: End of Support

Key Terms:

• End of Sale: No new ACM sales will be made from this point
• Phased-Out Support: Limited TAC Support, commercially reasonable effort support, No new enhancements will be made to the product
• End of Support: No TAC Support, No defect fixes, No development

If you have any questions, please contact your Honeywell Aftermarket Services Manager.

Honeywell Alarm Management | Alarm Performance Optimizer R3.0.0

Due in August 2025, Honeywell Alarm Management | Alarm Performance Optimizer R3.0.0 will be released. This release includes the option to migrate from the legacy Alarm Configuration Manager R321.

[Image: Screenshot of Honeywell Alarm Management | Alarm Performance Optimizer dashboard showing various metrics like Tag Status, Priority Distribution, Recommendation Status, Alarm Documentation Completion, Ignored Enforcements, etc.]

New features include:

• ACM – APO Migration:
  • Seamless migration from ACM to APO with built-in validation and flexibility
  • Three-phase migration: Pre-migration, Migration, Post-migration
  • Pre-migration: Configure essential components and secure the site environment
  • Migration: Validate, map, and migrate data with utility tools
  • Post-migration: Conduct reviews and ensure data integrity with validation tools
• Constraints:
  • APO allows users to create constraints and associate them with variables
  • Alarm limits are validated against constraint values during proposed changes
  • Error triggered if proposed alarm limit exceeds the constraint, preventing the change
• Offline Rationalization:
  • Allows updates to multiple alarm-related variables outside APO Web UI using Excel.
  • Export data with filters, edit or add entries in Excel, then import back.
  • System processes changes, updates valid records, unlocks modified alarms, flags invalid entries.
  • Detailed import/export status and error logs provided.
• Tag Suspend/Resume:
  • Allows temporary suspension of tag enforcement from APO to DCS during planned maintenance.
  • Prevents unwanted overwrites during known data changes.
  • Enforcement can be paused for a defined time window.
  • Enforcement is automatically or manually resumed after the activity or the scheduled period.

DeltaV DCS:

• APO now supports DeltaV Control System integration.
• Enables import and synchronization of tags and alarm properties from DeltaV systems into APO.
• Modification and rationalization of tag and alarm properties within APO.
• Management of the MOC process for tag approval and release.
• Generation of exception reports to track differences between the DCS and the master alarm database.

Mode-Based Enforcement - AMS_Proxy

• Mode-Based Enforcement using AMS_Proxy allows automatic mode changes without manual action.
• It is triggered from the DCS Server using command-line parameters.
• AMS_Proxy must be installed on a server within the same domain as the APO Site with .NET Framework 4.8.
• Once configured, it connects to the APO Site and enforces the defined mode on specified assets and consoles.

Honeywell Alarm Management (HAM) Product Family Consolidation

Overview

We have now completed the consolidation of legacy Alarm Management product families and their respective products into the current product family name, Honeywell Alarm Mgmt. This change affects the following supported products:

Knowledge Article Search Impact

When searching knowledge articles please filter on Honeywell Alarm Mgmt Product Family to limit the results to all alarm management products:

[Image: Screenshot of Honeywell website search interface showing filtering by 'Honeywell Alarm Mgmt'.]

Submit Technical Support Request Impact

When raising a Technical Support Request (SR) please use the Product Family Honeywell Alarm Mgmt so that all alarm management products will be listed under the Product field:

Alarm Management Product Support Update

• DynaMo Metrics & Reporting R210.x support status changes to Phased-Out in May 2025
• Process Safety Analyzer R20x support status changes to Phased-Out in January 2025
• Alarm Configuration Manager R321 support status changes to Phased-Out in December 2026

REMINDER! Experion upgrade to R520/530 causes HAM-Reporting (DynAMo M&R) Collector Data Corruption

If the Experion DCS is upgraded to R520+ from an earlier version, it may lead to data corruption problems with DynAMo Metrics & Reporting (M&R) or HAM Reporting (HAM-R) installations. This migration can introduce extra (and invalid) Tagnames, potentially affecting the licensed tag-count limit. Additionally, it may result in the creation of extra Assets, which could negatively impact report performance.

For more details refer to knowledge article KSM2022-DYN003x.

Also refer to Knowledge Article 000189115 – ‘EAS ODBC R530 Client Hotfix Matrix' which lists the ODBC version required against the Windows Operating System installed on the collector, and the minimum version of Experion required to communicate with the ODBC driver.

If you have any doubt please contact the Honeywell Alarm Management Technical Support (GTAC) team if you are planning to migrate to Experion R520+, they will review your system and inform you of what steps are needed to avoid system downtime.

Upgrading Experion to R520/530 prevents HAM-Documentation/ACM Clients from connecting to the application server

Experion 520+ recommends encryption types AES256_HMAC_SHA1, AES128_HMAC_SHA1, and future encryption types as default for Kerberos authentication to ensure secure communication and data integrity. Below is an extract from Experion documents:

When these policy settings are implemented on the Experion server, the related client-server applications, like ACM, must be updated as well. Specifically, all client and server machines, along with service users, must be compatible with the new encryption types. If this compatibility is not achieved, it could lead to authentication problems during DCOM communication between the application client and server.

A knowledge article how to address this problem will be published soon. If you are facing problems with ACM clients not connecting to the ACM application server then please contact the Honeywell Alarm Management Technical Support (GTAC) team.

Knowledge Articles: Summary of Articles – 2025

Below is a list of knowledge articles published to Process.Honeywell.com for the following supported products:

• DynAMo Metrics & Reporting R202.1 - R210.1
• Honeywell Alarm Management | Reporting R2.2.0 – R2.3.0
• Honeywell Alarm Management | Documentation / DynAMo Documentation & Enforcement (ACM R321.12)
• Honeywell Alarm Management | Alarm Performance Optimizer R1.0.0 – R2.0.0
• Honeywell Alarm Management | Process Safety Analyzer R201.x – R2.2.0

Honeywell Operations Management

Honeywell Operations Management R246.3 (On-Prem offering)

We are pleased to announce that the Honeywell Operations Management R246.3 has been released in June 2025. This release provides new functionality as well as addressing prior release issues.

New features include:

• A user-friendly mobile experience for accessing Logbook Shift reports. Users can effortlessly create, update, and submit their reports. Supervisors, in addition, will have the capability to view and approve reports, as well as navigate through various timelines and assets to review all relevant reports.
• New DAS plugins to expand data connectivity options for both Logbook and Monitoring applications. These plugins enable seamless integration with systems supporting OPC UA and facilitate connectivity to PI systems through the PI Asset Framework (AF), enhancing data management and operational efficiency.
• Two new applications as part of our Logbook suite, specifically designed to enhance safety management: Permit to Work and Incident Management. These applications provide robust tools to streamline safety processes, ensuring compliance and promoting a safer work environment
  • The Permit to Work (PTW) application streamlines the creation and management of work permits and their workflows, ensuring adherence to safety protocols through defined stages including request, validation, approval, and completion. By assigning multiple roles within the workflow, it enhances operational safety and transparency, fulfilling regulatory documentation requirements.
  • The Incident Management (IM) module supports workplace safety by providing a structured process for documenting and addressing incidents that occur during authorized tasks. It ensures that incidents are reported, reviewed, and resolved, fostering a culture of safety and continuous improvement. This module helps organizations track, resolve, and learn from incidents, thereby enhancing proactive risk management and minimizing the potential for future occurrences.
• Enhanced Logbook Report Templates: Introduction of multi-select dropdowns and external source dropdowns in Data Entry Table (DET) and Matrix snippets, along with support for basic calculations using cell references in Matrix snippets.
• Improved Standing Order Notifications: Enhanced email notifications now include Plan notes and improved readability for better communication.
• Shift Handover Workflow Upgrade: Added functionality to capture and record user signatures directly in shift handover reports for enhanced verification.
• Monitoring Target Deviation Update: Ability to recalculate the financial impact of Monitoring Target deviations when factors are modified.

The Software Change Notice (SCN) will be published to Process.Honeywell.com for more information.

Knowledge Article: Summary of Articles – 2025

Below is a list of knowledge articles published to Process.Honeywell.com for the following supported products:

• Uniformance Executive R301-330.1
• Uniformance KPI R121 – R140.1
• Honeywell Forge Operations Logbook R240.1 – R246.3
• Honeywell Forge Operations Monitoring R240.1 – R246.3

Honeywell Production Management

Upcoming release Production Accounting & Reconciliation R3.1.0 in Q3 2025 (September)

We are pleased to announce that the Production Accounting & Reconciliation R3.1.0 has been slated to be released by September 2025. This release would include a completely new module, as well as address prior release issues. Detailed information to be provided in Q3 newsletter.

Key outcomes of R3.1.0 to include

• Co-existence of PAR & Solution builder, which is the evolution journey of PAR
• The introduction of Solution builder enables extension of product life for MPM customers and shoulder space to retain higher level of maturity using PAR capability.
• API integration using inventory calculations to perform level-to-volume conversions (as part of Exxon MDF), to prevent inventory loss resulting in savings for any end user.
• Implementing Adhoc movements to allow more flexibility in the reconciliation

An overview of the PAR to PAR ++ journey - EVOLUTION OF PAR ++

[Diagram: A timeline showing PAR releases R212.3, R300, R310, R311, R312, with descriptions of migration, tools, and functionality. It also includes benefits of Solution Builder integration.]

Honeywell Production Management updated support policy

The applications contained within this suite is as follows.

• Honeywell Production Accounting and Reconciliation | Mass balance: Sophisticated Statistical Data Reconciliation Algorithms ensures faster time to compute and reconcile Mass Balances - provides easier and faster identification of Key errors and fugitive losses and their root causes.
• Honeywell Production Accounting and Reconciliation | Inventory Accounting (previously Production Logger): Maintains Accurate Inventory Balances for informed decision making. Improves planning cycle based on precise Inventory levels, owing to reconciled inventory.
• Honeywell Production Accounting and Reconciliation | Composition tracking: Composition Tracking helps in better yield prediction and accurate apportioning of secondary

For organizations looking to drive supply chain optimization, visibility and profitability; for operations managers looking to manage costs, feedstock and product blending, and for planners and production accountants looking to improve agility with tighter plan versus actual alignment

Support Phases Definition

Overall support phases are “Current”, “Supported” and “Phased-out" respectively. These are described below:

Current (Full Support):

Standalone Software Product releases, represented by the 'Current' software releases, are eligible for all applicable support programs made available by HPS, subject to business conditions including, but not limited to, availability of software and support from third party software suppliers. "Current" Support applies to the most recent or current release (R). The entitlements for Current phase are:

• Full TAC support is available.
• Category 1 (product not useable) and 2 (major function not useable) PARs are processed and resolved; maintenance and point releases are generated when needed.
• Product documentation is regularly updated to reflect changes in product features and correct errors found in existing documentation.
• Relevant security updates for qualified third-party Software (for example, OS software) are qualified.
• Relevant security updates for certified third-party Software (for example, Microsoft Excel) are certified.
• At least one anti-virus software product and its updates are qualified or certified.

Supported:

Standalone Software Product releases, represented by selected “Current-n" software releases, are eligible for selected support programs made available by HPS/HCI for such releases, subject to business conditions including, but not limited to, availability of software and support from third party software suppliers. “Supported" applies to the releases prior to the current release.

The Entitlements for Supported phase are:

• Full TAC support is available.
• Category 1 (product not useable) PARs are processed and resolved; maintenance and point releases are generated when needed. Selected Category 2 PARs will be evaluated & resolved based on criticality.
• For PARs other than Category 1&2, "commercially reasonable effort support" will be provided, typically including answering questions and offering advice, but problem fixes may require upgrading to a release in the "Current" support phase.
• Fixes developed against later releases generally will not be ported back to releases in the supported phase.
• Product documentation updates generally will not be provided.

Phased-Out:

For Standalone Software Product releases which have been Phased-Out, HPS intends to make commercially reasonable efforts to provide support as, and if, available consisting of technical assistance for product use, lost/damaged software media replacement and reference materials download. "Phased-out" Support applies to releases older than R-2.

• Limited TAC support will be available.
• Honeywell may not always be able to enter into a contract for Phased-out releases due to technology or resource considerations. Any contract would exclude PAR fixes.
• For all PARs, "commercially reasonable effort support" will be provided, typically including answering questions and offering advice, but problem fixes will require upgrading to a release in the "Current" support phase.
• Fixes developed for later releases generally will not be ported back to Phased-out releases.
• Product documentation updates will not be provided.

Special Arrangements (Contract Support) can be negotiated for individual customers and may provide additional benefits not otherwise available, as mutually agreed. Special arrangement may provide problem fixes for Retired or Obsolete releases, security or anti-virus qualification or certification after the normal period, or other benefits. Special arrangement agreements are negotiated with Honeywell's Application Technology Services groups and generally have an additional cost. Please note that Honeywell may not always be able to enter into a contract due to technology or resource considerations.

Active Products Support Status

Support Status for Honeywell | Production Accounting and Reconciliation

*Planned. Information about future releases is subject to change without notice

Current Product Releases

Advanced Applications:

Honeywell Alarm Management

• Reporting R2.2.1
• Alarm Performance Optimizer R2.0.0
• Documentation (ACM R321.12.7)
• Notifications (UA R321.2)
• Process Safety Analyzer R2.1.1

Honeywell Operations Management R246.2

• Operations Logbook
• Operations Monitoring
• Operations Instructions
• Operations Limit Repository

UniSim Design Suite

• UniSim Design R500

Honeywell Workforce Competency R530.1

• Process Training Simulator
• Tutor
• Curriculum
• ProSim

Honeywell Production Management

• Production Accounting and Reconciliation R212.3

Honeywell APC (Profit Suite)

• Release R513.1

Uniformance

• Uniformance PHD R430
• Uniformance Process Studio R323
• Uniformance Asset Sentinel R532
• Uniformance Insight R240
• Uniformance Cloud Historian R100
• Uniformance Executive R331
• Uniformance KPI R140.1

Control Performance Monitor

• Control Performance Analytics-Unified (CPA-Unified) R610.1
• TaiJi PID R320.2

Honeywell Blending and Movement (HBM) Suite

• Blending and Movement (PBM) R530.2
• Blend Performance Monitor (BPM)
• Experion Blend Controller (EBC)
• Experion Tank Monitor (ETM)
• Profit Inventory Monitor (PIM)
• Profit Blend Controller (PBC)
• Profit Blend Optimizer (PBO)
• LIMS Viewer (LV)
• Profit Movement Management:
  • Movement Monitor (MM)
  • Movement Control (MC)

Contact Information

All GTAC support should be directed through https://www.process.honeywell.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx Portal.

Americas Support Centre Contact Information

Asia Pacific (AP) Technical Assistance Centre (TAC) for Honeywell Connected Industrial contacts

Honeywell Asia Pacific regional GCCC hotlines:

• Australia: 1 300 301 135
• China: 400-820-0386
• India: 1-800 2335051
• Indonesia: 0018-03-440-212
• Malaysia: 1 800-812-674
• New Zealand: 0800 855 663
• Pacific (outside Australia and New Zealand): +65 6787 1788
• Philippines: 1-800-1441-0223
• Singapore: 6823-2215
• Taiwan: 0800-666-051
• Thailand: 0018-004-415-283

Europe and Middle East and Africa, (EMEA) Technical Assistance Centre (TAC) for Honeywell Connected Industrial contacts

For questions, comments, or archived copies of the Guardian newsletter, please contact Gunjeet Chaudhari at Gunjeet.Chaudhari@Honeywell.com.

Honeywell Process Solutions
1250 West Sam Houston Parkway South
Houston, TX 77042

Honeywell Control Systems Ltd, Honeywell House Skimped Hill Lane Bracknell RG12 1EB
555 Huanke Road, Zhangjiang Hi-Tech Park, Shanghai, China 201203

www.honeywell.com/ps