Symptom in multiple incidents

["Isaiadis, Stavros" <stavros.isaiadis@baml.com>]

Hi Alvin, all,

 

We were trying to clarify the incident id field yesterday and specifically find strong cases where a symptom could be part of multiple incidents. You have previously said:

 

The “symptom participating in multiple incidents” seems like it would come up very often.  The most obvious scenario to me is for any  broad symptom that could have multiple possible causes (which may actually be completely separate incidents).

 

For example:

A “Service not available” symptom could belong to a symptom chain for multiple causes:

A)      “Virus detected” symptom

B)      “Network unavailable” symptom

C)      “Server on fire” symptom

 

Or, if we want to use a more abstract example:

“I have a headache” symptom:

A)     “Did not get any sleep last night” symptom

B)      “Axe buried in my head” symptom

C)      “I just read another one of Alvin’s emails” symptom

 

I can see the value in the above; do we assume the emitter will know and supply all these incident Ids? Cause then it will have to be a bit smarter than we have thought.

 

Is this a matter of merely having a collection of incident Ids? I assume it is, and I think right now that’s how it is in the spec.

 

Any more thoughts or comments on this one so that we can put it to rest?

 

Cheers,

Stavros

 

---

This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. 
Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. 
The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. 

References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: 
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.