NEXYTE Product Description Page 11 + Entity display. Each entity can appear in different places within the user workstation and in different contexts. The display is determined in the DDM. Different models are defined for each data source. Person Entity with Relations Principles of NEXYTE’s data modeling solution: + Independent customer-defined modeling. The local IT partner, third party integrator or Cognyte services define the entity model based on customer inputs regarding what constitutes an entity, its characteristics, and relations, relevant sources and intelligence needs. The entity model is designed according to the customer’s guidelines and priorities, and determines what appears in the workstation investigation interface, timeline, analytics and Link Analysis. The party defining and tailoring the data model will work on the customer’s behalf to ensure a smooth intelligence-driven conversion of all system data, aligned with the customer. + Independent Customer additions. The customer, or his IT partner, is fully independent to add new sources and entities according to its needs and resources. The customer can also edit data fields to its created entities at any time throughout the system lifetime, with minimal resources and effort. + Promoting intelligence insights. The customer together with his IT partner provide intelligence-oriented entity modeling guidelines for each data type. The resulting entities and entity relations can promote intelligence insights, by prioritizing and visualizing information items that contribute the most value and can be adjusted as necessary based on new understanding as it evolves. + Source-specific modeling. Different flows are applied to different types of data and content, assuring the data is processed to gain the most relevant intelligence-worthy information from each source. − Textual data modeling applies to modeling of textual content, which includes multiple processing stages, such as basic language and content classification,