When baking a cake, or building a VA, you need to make sure you have all the right ingredients and that you apply the right recipes.
In the VA context, the ingredients are relevant data records, factors, content, entities and users that will impact the resulting decision or action. The recipes are the logic that needs to be applied to each ingredient or component to derive the specific outcome.
This section covers the specific components that can be used within any VA (to see more on the logic types, click here).
IMPORT REQUIRED DATA
The organisation’s existing master data can easily be formatted and imported into CLEVVA. This makes the imported data records, as well as the data columns or fields available in the component library (which are referred to as factors in CLEVVA), to be easily added to the VA. Images linked to any data record can also be uploaded and automatically linked.
INTEGRATE REQUIRED DATA
Data that already exists in other systems can also be integrated with CLEVVA using our API’s to ensure that the data in CLEVVA is automatically kept up to date.
STRUCTURE YOUR DATA
Data can be structured in hierarchical folders that can easily be moved around. This allows for data records to inherit factors and other linked objects of the data folder which makes it simple to apply changes to large data sets.
Factors are used to represent the unique considerations, options, benefits, conditions, features or attributes when making a choice or decision. Factors can either relate to data records, or act in isolation. Factors are a key mechanism used within CLEVVA to identify relevant solutions (usually data records) or automate various responses.
THE TYPES OF FACTORS THAT CLEVVA SUPPORTS
HOW FACTORS ARE MAINTAINED
Factors can be grouped and maintained in folders to make them easy to find as well as to avoid duplication. Factors can also be applied to Users and Entities to auto answer or suggest specific decisions to be made for a specific User or for a selected Entity.
|Filtered||Use factors to narrow down data to find matching records based on a series of conditions (factor combinations).|
|Triggered||Use factors to specify conditional rules that need to be met in order to trigger a prescribed action.|
|Calculated||Use numeric factors to set up calculations and ranges to provide answers when there are too many possibilities to consider.|
|Inferred||Apply factors to hierarchical data folders to be inherited by records that can be used for inferring answers|
|Sequential||Use factors to represent decisions in sequential processes that can be tracked for reporting purposed as well as used to answer decisions in the process that have already been answered.|
Content includes any reference information that the user may find valuable to reference at any time within any VA. Content can either be uploaded into CLEVVA for easy reference, or referenced in another system e.g. your knowledge system.
UPLOAD HYPERLINKS TO REFERRED SYSTEMS
– Content Management Systems (CMS)
– Knowledge Base (KB)
Upload any of the following white listed file types into CLEVVA:
|FILE TYPE||FILE EXTENSION|
|Comme Separated Values||.csv|
|Graphical Interchange File Format||.gif|
|JPEG Image||.jpeg, .jpg|
|Outline Mail Message||.msg|
|OpenDocument Text Document||.odt|
|Portable Document Format|
|Portable Network Graphic||.png|
|Microsoft PowerPoint 2007||.ppt, .pps|
|Microsoft PowerPoint 2010+||.pptx, .ppsx|
|Microsoft Word 2007||.doc|
|Microsoft Word 2010+||.docx|
|Microsoft Excel 2007||.xls|
|Microsoft Excel 2010+||.xlsx|
Entities are records that a given session or interaction applies to. A good example of an entity is a customer. So if any advice is being sought that relates to a specific customer, CLEVVA is able to track the engagement to that customer record, as well as leverage any customer-related factors saved against that record. And at the end of any interaction, the customer record can also be updated based on any relevant factor selections made.
By supporting entity records, CLEVVA makes it possible to effectively integrate VA logic into CRM and other similar systems, where the assigned activity must be relevant to a specific entity record.
Users of the CLEVVA system are mapped to departments and roles. Access to specific VAs are then managed based on these mappings. User records can also contain a number of relevant factors that can influence the advice offered by any VA. For example, a staff member who works from Nigeria may need to have Nigeria-specific advice offered. Using user-mapped factors, any VA that the user accesses where this is so will automatically guide them to teh Nigeria-relevant questions and outcomes. The same applies to authors who can be mapped to different folders of VAs, so that they are only given access to the VAs you require (and not VAs they have not been approved to work on).