- Historical data recording
- Linking capabilities
What is most valuable?
How has it helped my organization?
The ability to auto-linking multiple records/sources to one common Enterprise ID (EID).
What needs improvement?
The use of an EID as unique identifier.
For how long have I used the solution?
I've been using it for six years.
What was my experience with deployment of the solution?
No issues encountered.
What do I think about the stability of the solution?
No issues encountered.
What do I think about the scalability of the solution?
No issues encountered.
How are customer service and technical support?
Customer Service:
It's acceptable.
Technical Support:It's acceptable.
Which solution did I use previously and why did I switch?
It was done in-house and needed a lot of manual intervention.
How was the initial setup?
Prior to IBM coming in a helping, the initial setup was a bit of a challenge.
What about the implementation team?
We used a mix and the level of expertise was acceptable.
Which other solutions did I evaluate?
Yes, we did.
What other advice do I have?
The EID is an internally-generated and managed identifier that will change based upon various system & business rules, and its function. It's not recommended that Initiate EIDs be used as unique identifiers within your downstream system(s) due to possible frequent change, which could therefore create issues if downstream systems are dependent upon them not changing.
![IBM Initiate [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_100/vrgt1zpi8gqi3wy9lt9smu963yx9.jpg?_a=BACAGSGT)