1. Solution 2
1.1. Workflow
1.1.1. Login
1.1.1.1. Steps
1.1.1.1.1. Load Configuration to see Master HICon port
1.1.1.1.2. Connect to Master HICon
1.1.1.1.3. Send ICNSLoginRqst
1.1.1.1.4. Wait for ICNSLoginRply
1.1.1.1.5. After receiving ICNSLoginRply (successful), terminate the connections.
1.1.1.1.6. If ICNSLoginRply failed, the connections shall be kept open.
1.1.1.2. If Login failed
1.1.1.2.1. HICon shall display failure message
1.1.1.2.2. Re-try for some (?) time
1.1.1.2.3. Return the ICNSLoginRply as failed
1.1.1.2.4. When everytime user clicks for HICon int he HMI, the same login shall be initiated
1.1.2. Validation/Execution
1.1.2.1. If the login failed
1.1.2.1.1. No Safety Validation messages shall be sent
1.1.2.1.2. No Safety Execution messages shall be sent
1.1.2.1.3. Once the login success, all the pending Safety Validation/Execution requests shall be processed and send to HICon.
1.2. assumptions
1.2.1. Each HICon shall be able to communicate with other HICon on the same Workstation
1.2.1.1. Shall exchange current login information
1.2.1.2. Shall exchange current View information
1.2.1.3. Shall exchange current logout details
1.2.1.4. Shall work like Master-Slave where the first one logged in will be Master and there after all slaves
1.2.1.5. The Master HICon shall transfer the login information to Slave HICons.
1.2.1.6. The Master HICon shall transfer the Validation/Execution to corresponding HICon.
1.2.1.7. Master HICon will be launched automatically when the HMI launches and hidden. Once the user wants to show in any of the monitor then it will be visible.
2. Assumptions
2.1. HICon shall be launched only by Signal Operator and Shift Leader
2.2. Single HICon shall be contained in only one monitor
2.3. Single HICon shall show only one view at any time
2.4. The first HICon launched with particular view shall have write access and subsequent HICon with same view shall have read access. Once the first one with write gets closed, the second one shall get the write access.
2.5. At any time, 8 possible HICon shall be launched (can be configured based on the number monitor available)
3. Solution 1
3.1. Workflow
3.1.1. Login
3.1.1.1. Steps
3.1.1.1.1. User login to Client Builder
3.1.1.1.2. In client Builder, user selects HICON and select Select Areas
3.1.1.1.3. Client builder launches HICon with selected Areas
3.1.1.1.4. Client Builder updates S2K Nodes about which HICON Which Area (which is exposed in MDM)
3.1.1.1.5. ICONIS -HI Interfaces fetches this information and initiate the login request based on user name/areas to that particular HICON Instances
3.1.2. Validation/Execution
3.1.2.1. Based on the action, finds about the Area it belongs to.
3.1.2.2. Locate the concerned HICon based on the S2K node with the help of Area id(s).
3.1.2.3. Send the validation /execution requests to that particular HICon
3.1.2.4. If the login failed
3.1.2.4.1. Interface will wail it gets the entry updated in the S2K node
3.1.2.4.2. Once node updated, interface will push this request to that HICon.