1 / 6

Z-SPIRE Locks 101

Application Support Center Tips: Information Regarding the Top Three Z-SPIRE Inquiries: Blue Locks, Red Locks & Password Resets. Z-SPIRE Locks 101. 2. How do I recognize a blue lock versus a red lock? Locks are displayed by colored font in the “Process Status field.”

ivor-cochran
Download Presentation

Z-SPIRE Locks 101

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Application Support Center Tips:Information Regarding the Top Three Z-SPIRE Inquiries: Blue Locks, Red Locks & Password Resets

  2. Z-SPIRE Locks 101 2 • How do I recognize a blue lock versus a red lock? • Locks are displayed by colored font in the “Process Status field.” • What’s the difference between a blue lock and a red lock? • Red locks indicate a serious problem and they all need to be investigated by the ASC (e.g., a process failed, the entry causes an error in an algorithm, there are characters the system does not recognize, an edit or validation failed). • Blue locks are not an indication of any system problem and occur when the SAN (System Assignment Number – a unique identifier for each transaction) is in use. • Why do blue locks happen? • Blue locks happen because the SAN is either in use by the system or another user. To avoid a conflict caused by users accessing policies while the data is in use by the system or another user, Z-SPIRE locks the transaction until the person or process has stopped using the policy data.

  3. Z-SPIRE Locks 101, continued 3 3 • Can you give me some examples of when a blue lock will occur? • A Rater is in a SAN, and a UA is trying to access the same SAN at the same time. It will display as a blue lock-external message for the UA. • You are using the Remote Rating Option, and then close out of the system. If you log back in immediately and rating has not yet completed, it will display as a blue lock. • During the issuance of a transaction, the system will go through the process of formatting the transaction. Below are a few process status blue lock formatting messages that users generally mistaken for being a system issue: Locked - Download Locked - Download - In Process (Reporting Status) Begin Distributed Transaction Locked - Issuer - In Process (Reporting Status) Starting Detailed/Output Locked - Issuer - In Process (Reporting Status) Calculating Cash Premiums Locked - Issuer - In Process (Reporting Status) Format Output ended in error (this could possibly relate to a server or network issue) NOTE: Depending on the size of the account, such as large location, vehicle, class code schedules, the number of endorsements processed on a policy and network traffic, this can result in longer processing times.

  4. Z-SPIRE Locks 101, continued • Why does the system occasionally bring me to the home screen and when I try to access my transaction it displays “Locked –Rating”? • If a transaction takes longer than 10 minutes to rate, the system will automatically move the transaction to Remote Rating and bring the user to the home page. This is normal system behavior and allows the system to be used for other transactions while the rating completes. • Why do some blue locks disappear on their own and others have to be unlocked? • Most blue locks will resolve on their own when the user or system process has finished using the SAN. For example, when the remote rating is completed or the Rater moves on to a different SAN. • Occasionally, the system will ‘hang’ and not recognize that person or process is no longer using the SAN and requires an unlock. This could be caused by network or system environment issues, logging out of Z-SPIRE incorrectly, or a PC issue.

  5. Z-SPIRE Locks 101, continued 5 • How can I avoid a blue lock? • Always sign off using the Signoff button. Many blue locks are caused by exiting the system incorrectly. • Are there any blue locks I can unlock myself? • Yes. If you mistakenly caused a blue lock by signing out of the system incorrectly, you can unlock the transaction by selecting the locked SAN and clicking the Home button. (Note: this only works if your ID is the ID that has the SAN locked. It will not unlock all blue locks.) • If I request an unlock of a blue lock, is there any risk? • Yes, there are some risks to performing unlocks: • If another user is in the SAN at the time of the unlock it will kick them out of the system and they may lose work. • If you unlock a SAN that has an active System Process (like Rating) it will stop the process and it will need to be done again. • It is recommended that all Blue Locks are given at least 20 minutes* of time to clear before calling for them to be cleared. *20 minutes is a guideline, actual time may vary due to size of policy and network traffic

  6. Z-SPIRE Password Resets 6 • Password resets are the 3rd most common Z-SPIRE Inquiry. Z-SPIRE Passwords expire every 90 days. Fortunately, you can change your password prior to being locked out of the system. Here are some suggestions to avoid being locked out of the system. • After changing your password, set a reminder on your calendar to change it again in 85 days. • Change your Z-SPIRE password when you P-Synch (applies to Zurich employees only). • You are given “grace logins” after your password expires. Change your password immediately upon seeing this message.

More Related