CREALIS® — functions

The most important features at a glance

Everything you need: The power functions of CREALIS® CPQ

The basic tasks of a CPQ sys­tem are to con­fi­gu­re pro­ducts, cal­cu­la­te pri­ces and gene­ra­te quo­ta­ti­on docu­ments. In addi­ti­on, the­re are many sub­or­di­na­te tasks that a CPQ sys­tem must ful­fil. New func­tions often ari­se from indi­vi­du­al cus­to­mer requi­re­ments. During con­ti­nuous deve­lo­p­ment, the ORISA team has always endea­vou­red to estab­lish indi­vi­du­al wis­hes and func­tions through gene­ral­ly valid and gene­ric imple­men­ta­ti­ons. The deve­lo­p­ment of CREALIS® is the­r­e­fo­re based on deca­des of expe­ri­ence in the con­fi­gu­ra­ti­on envi­ron­ment. Today, CREALIS® is one of the lea­ding CPQ sys­tems on the mar­ket with advan­ced tech­no­lo­gies, sophisti­ca­ted func­tions and well thought-out usa­bi­li­ty.

Product data management — data sovereignty and single source of truth

A con­fi­gu­ra­ti­on solu­ti­on depends on a struc­tu­red data pool. The­se data are usual­ly pro­duct parts, artic­les, assem­blies and their parts or com­pon­ents. They can be ful­ly main­tai­ned in CREALIS® PDM. All the infor­ma­ti­on that a data record requi­res is stored in CREALIS® PDM. This includes texts and descrip­ti­ons as well as pro­per­ties and pri­ces. Of cour­se, the data can also be impor­ted from other sys­tems, typi­cal­ly ERP. The­se import pro­ces­ses defi­ne the data sove­reig­n­ty or which sys­tem is regard­ed as the sin­gle source of truth (sin­gle source of data). Mas­ter data from an ERP sys­tem is often incom­ple­te if it is to be used in a con­fi­gu­ra­tor. In CREALIS® PDM, impor­ted data can be easi­ly sup­ple­men­ted. Strict atten­ti­on is paid to the sepa­ra­ti­on bet­ween impor­ted infor­ma­ti­on and infor­ma­ti­on stored in the PDM.

Maintenance of information on parts lists

A com­mon approach to pro­duct data is to struc­tu­re artic­les and assem­blies in maxi­mum BOMs. CREALIS® uses struc­tu­re levels and their assign­ment to artic­le cha­rac­te­ristics for this pur­po­se. This approach offers maxi­mum fle­xi­bi­li­ty for use in con­fi­gu­ra­ti­on models. CREALIS® atta­ches gre­at importance to avo­i­ding red­un­dan­cy and the reusa­bi­li­ty of exis­ting data. Items can be con­ve­ni­ent­ly assi­gned to dif­fe­rent struc­tu­ral levels so that when item data is updated, it remains syn­chro­nis­ed in all affec­ted parts lists. Which data is main­tai­ned and sup­ple­men­ted in the PDM’s modu­lar sys­tem natu­ral­ly depends on a company’s indi­vi­du­al pro­ces­ses and exis­ting data struc­tures. A simp­le exam­p­le of the cus­to­mi­sa­ti­on of impor­ted data is the mar­ket-spe­ci­fic texts on artic­les. If the impor­ted texts are not sui­ta­ble for use in the con­fi­gu­ra­tor due to ina­de­quaci­es such as data fields being too short in the lea­ding ERP sys­tem, they can be over­writ­ten with mar­ket-spe­ci­fic texts. The ori­gi­nal texts are of cour­se still available in the PDM to ensu­re maxi­mum trans­pa­ren­cy. The­se struc­tures can also be easi­ly appli­ed to other are­as in CREALIS® PDM, such as pri­ce struc­tures.

Ano­ther typi­cal exam­p­le is the par­al­lel crea­ti­on of rou­tings and the sto­rage of work steps. By model­ling and lin­king, the neces­sa­ry work steps and rou­tings can be gene­ra­ted simul­ta­neous­ly when gene­ra­ting the spe­ci­fic parts list for an indi­vi­du­al vari­ant.

Modelling the configuration logic

The cen­tral task of CREALIS® PDM is to main­tain the con­fi­gu­ra­ti­on logic. The focus here is on describ­ing the depen­den­ci­es that are ulti­m­ate­ly neces­sa­ry for the builda­b­ili­ty of an indi­vi­du­al­ly con­fi­gu­red pro­duct vari­ant. The­se depen­den­ci­es can be crea­ted intui­tively via the pro­per­ties of the artic­les and com­pon­ents wit­hout requi­ring a gre­at deal of main­ten­an­ce. In addi­ti­on, fur­ther means are available for model­ling topics rela­ted to builda­b­ili­ty that sup­port inter­nal and exter­nal busi­ness pro­ces­ses, for exam­p­le. The model­ling of dif­fe­rent views of the model, such as the use of sales fea­tures or the sup­port of pro­duct con­fi­gu­ra­ti­on through a gui­ded sel­ling pro­cess, is easi­ly pos­si­ble. The con­s­tructs used in CREALIS® PDM help to avo­id red­un­dan­cy and main­tain an over­view of the indi­vi­du­al aspects of a com­plex model.

Enrichment of data with documents and visualisations

In order to make a con­fi­gu­ra­ti­on pro­cess in the appli­ca­ti­on clear and rich in con­tent, it is neces­sa­ry to work with sup­ple­men­ta­ry docu­ments and use visua­li­sa­ti­ons. CREALIS® offers all the neces­sa­ry func­tions for this. Artic­les and com­pon­ents can be enri­ched with artic­le- and lan­guage-spe­ci­fic docu­ments in a wide varie­ty of for­mats, which are made available in the con­fi­gu­ra­ti­on. Images can be embedded direct­ly into the con­fi­gu­ra­ti­on using modern tem­pla­tes. Dyna­mic visua­li­sa­ti­ons, in which the pro­duct image imme­dia­te­ly adapts to indi­vi­du­al requi­re­ments, are pos­si­ble with 2D and 3D. The 3D tech­no­lo­gy is brow­ser-com­pa­ti­ble, plug­in-free and, of cour­se, sui­ta­ble for VR (vir­tu­al rea­li­ty) and AR (aug­men­ted rea­li­ty) appli­ca­ti­ons. CREALIS® PDM offers suf­fi­ci­ent main­ten­an­ce opti­ons to mana­ge all the neces­sa­ry infor­ma­ti­on cen­tral­ly. Of cour­se, it is also pos­si­ble to inte­gra­te data from exter­nal sys­tems.

Ready for international deployment

CREALIS® is ful­ly desi­gned for inter­na­tio­nal use. All texts can be map­ped in all lan­guages available in Uni­code. Pri­ce struc­tures can be stored with the requi­red cur­ren­ci­es. Docu­ments and images can be stored in spe­ci­fic lan­guages. In addi­ti­on, all objects can be used for spe­ci­fic mar­kets. A good exam­p­le is the coun­try-spe­ci­fic fire extin­gu­is­her in vehic­les, which is some­ti­mes requi­red by law. Mar­ket-spe­ci­fic depen­den­ci­es force the sel­ec­tion of the fire extin­gu­is­her only in tho­se count­ries whe­re it is requi­red by law. In other count­ries, it may be offe­red as an opti­on or may not be available at all. A lan­guage- and mar­ket-spe­ci­fic docu­ment shows the vari­ant of the built-in fire extin­gu­is­her in exact­ly the right form. Such defi­ni­ti­ons can be appli­ed to any assem­blies and pro­duct are­as.

Configuration of complex products

The com­ple­xi­ty of a pro­duct or its varie­ty of vari­ants increa­ses with the num­ber of opti­ons it offers. A com­pact pro­duct such as a car, for exam­p­le, typi­cal­ly has all sel­ec­tion opti­ons sum­ma­ri­sed in dif­fe­rent cate­go­ries, which can all be offe­red on one level. Sel­ec­tion opti­ons are usual­ly pro­duct opti­ons that are alre­a­dy sum­ma­ri­sed in modu­les for the sales per­spec­ti­ve. For exam­p­le, it is pos­si­ble to sel­ect a spe­ci­fic sound sys­tem from a ran­ge of dif­fe­rent sound sys­tems. Howe­ver, spea­k­ers can rare­ly be sel­ec­ted indi­vi­du­al­ly and inde­pendent­ly of the radio. From a tech­ni­cal point of view, the­re are many more indi­vi­du­al parts behind the sel­ec­tion of the sound sys­tem, right down to the indi­vi­du­al cable con­nec­tors and their plug-in sys­tems. For the user who con­fi­gu­res the car on the Inter­net, this data is irrele­vant, but it is very important when it comes to brea­king down the parts list for pro­duc­tion. Whe­ther this reso­lu­ti­on takes place in the con­nec­ted ERP sys­tem or the con­fi­gu­ra­tor alre­a­dy pro­vi­des the infor­ma­ti­on depends on the busi­ness pro­ces­ses estab­lished in the com­pa­ny and the available data.

The need for mul­ti-level con­fi­gu­ra­ti­on quick­ly ari­ses with more com­plex pro­ducts such as hea­ting sys­tems, heat pumps for apart­ment blocks, pro­duc­tion lines or other sys­tems made up of various con­fi­gura­ble modu­les. A cor­rect, mul­ti-level con­fi­gu­ra­ti­on can deal with sub-ins­tances, map depen­den­ci­es across the indi­vi­du­al levels of the mul­ti-level con­fi­gu­ra­ti­on and form a pri­ce for the enti­re con­fi­gu­red sys­tem. Mul­ti-level con­fi­gu­ra­ti­ons also offer advan­ta­ges at the model­ling stage. Red­un­dan­ci­es can be avo­ided through reusa­bi­li­ty and inhe­ri­tance. In CREALIS® PDM, mul­ti-level con­fi­gu­ra­ti­on models can be easi­ly crea­ted by lin­king the indi­vi­du­al sub-models. CREALIS® CPQ is able to pro­cess the­se com­plex con­fi­gu­ra­ti­ons effi­ci­ent­ly in all direc­tions. During con­fi­gu­ra­ti­on, chan­ges can be made at any point and depth of the mul­ti-level con­fi­gu­ra­ti­on wit­hout jeo­par­di­sing the con­sis­ten­cy of the con­fi­gu­ra­ti­on or the builda­b­ili­ty of the sys­tem. Sophisti­ca­ted con­flict hand­ling gui­des users through the con­fi­gu­ra­ti­on pro­cess and, based on sophisti­ca­ted model­ling stra­te­gies, users retain an over­view of their indi­vi­du­al con­fi­gu­ra­ti­on.

Configuration and guided selling with different views and roles

Crea­ting a con­fi­gu­ra­ti­on model often requi­res some effort. It is the­r­e­fo­re an advan­ta­ge if a con­fi­gu­ra­ti­on model can ful­fil various requi­re­ments. This includes pre­sen­ting the model on the Inter­net in a way that is just as easy to under­stand for the inte­res­ted lay­per­son as it is for the expe­ri­en­ced sales employee. The same model can also be used in pro­ces­sing, whe­re other views of the con­fi­gu­ra­ti­on data play a role. To avo­id having to crea­te dif­fe­rent con­fi­gu­ra­ti­on models for the various chan­nels, dif­fe­rent views can be crea­ted around the model in CREALIS®. The­se views are in turn made available to the various users with their dif­fe­rent roles and requi­re­ments. In this way, the inte­res­ted Inter­net user can use sophisti­ca­ted gui­ded sel­ling to find their desi­red vari­ant wit­hout having to under­stand the tech­ni­cal details. And the expe­ri­en­ced expert can put tog­e­ther the con­fi­gu­ra­ti­on with a dif­fe­rent view from a more tech­ni­cal per­spec­ti­ve and may have signi­fi­cant­ly more opti­ons available, which would cle­ar­ly over­whelm the Inter­net user. In the back­ground, CREALIS® ensu­res that a buildable vari­ant is always crea­ted and that the con­sis­ten­cy of the con­fi­gu­ra­ti­on is gua­ran­teed.

Type code generation — Digital type plate

With the gene­ric model­ling approach, addi­tio­nal infor­ma­ti­on can be gene­ra­ted with CREALIS® in par­al­lel to the pro­duct con­fi­gu­ra­ti­on. A com­mon exam­p­le of this is the crea­ti­on of the type code or pro­duct code. This often has the task of uni­que­ly iden­ti­fy­ing an indi­vi­du­al­ly con­fi­gu­red vari­ant. If an iden­ti­cal vari­ant is con­fi­gu­red at a later date, the iden­ti­cal type code is crea­ted and a down­stream ERP sys­tem can access the exis­ting vari­ant. Ano­ther pie­ce of infor­ma­ti­on that is beco­ming incre­asing­ly important nowa­days for iden­ti­fy­ing a pro­duct vari­ant is the digi­tal type pla­te. With cor­rect model­ling, all data for the digi­tal type pla­te can be auto­ma­ti­cal­ly coll­ec­ted by the con­fi­gu­ra­ti­on and pro­vi­ded accor­din­gly. Such algo­rith­ms for data gene­ra­ti­on usual­ly do not requi­re any spe­cial imple­men­ta­ti­on, but can sim­ply be map­ped with the model­ling.

Document generation and integration of configuration-relevant documents

At the end of a con­fi­gu­ra­ti­on, the­re is often the task of crea­ting docu­ments such as quo­ta­ti­ons, descrip­ti­ve docu­men­ta­ti­on and visua­li­sa­ti­ons. CREALIS® acces­ses all the infor­ma­ti­on crea­ted during con­fi­gu­ra­ti­on from docu­ment tem­pla­tes with gene­ric syn­tax fields. Users are offe­red a list of pos­si­ble docu­ments via a role-spe­ci­fic dia­lo­gue, which also con­ta­ins vari­ant-spe­ci­fic files. In this way, all docu­ments requi­red for the spe­ci­fic use case can be crea­ted by sel­ec­tion and cus­to­mi­sed sort­ing and then used.

Central control centre for offer management

The digi­ta­li­sa­ti­on of sales pro­ces­ses requi­res more than just pro­duct sel­ec­tion. In addi­ti­on to cus­to­mer data manage­ment, func­tions for com­pi­ling shop­ping bas­kets and gene­ra­ting docu­ments are also requi­red. This is whe­re the CREALIS® Dash­board plays a cen­tral role. It pro­vi­des an over­view of sales and admi­nis­tra­ti­on pro­ces­ses and allows users to save and share their own con­fi­gu­ra­ti­ons as favou­ri­tes.

New enqui­ries and offers start in the pro­duct cata­lo­gue, which lists all pro­ducts and infor­ma­ti­on and enables con­fi­gu­ra­ti­on. Search func­tions in the dash­board pro­vi­de quick access to shop­ping bas­kets, offer sta­tus and cus­to­mer con­fi­gu­ra­ti­ons. Work­flows in the dash­board enable the pro­ces­sing of spe­cial requests and con­trol by aut­ho­ri­sed per­sons.

Admi­nis­tra­ti­ve manage­ment includes user and cus­to­mer manage­ment as well as work­flow design. Users can be sum­ma­ri­sed in groups and cus­to­mer data can be retrie­ved. The CREALIS® CRM exten­si­on enables appoint­ment sche­du­ling, docu­men­ta­ti­on of cont­act histo­ry and sta­tis­ti­cal ana­ly­ses.

The topics descri­bed here only pro­vi­de a super­fi­ci­al over­view of the CREALIS® ran­ge of func­tions. The­re are many sub-func­tions in each indi­vi­du­al area, the scope of which can­not be descri­bed here. The list of exis­ting pro­ce­du­re rules alo­ne con­ta­ins over 60 ent­ries. The­se ran­ge from simp­le cal­cu­la­ti­on func­tions and com­plex algo­rith­ms to the inte­gra­ti­on of exter­nal tools such as Excel for out­sour­cing cal­cu­la­ti­on sche­mes. Their ver­sa­ti­le usa­bi­li­ty within the set of rules offers maxi­mum pos­si­bi­li­ties when model­ling com­plex con­fi­gu­ra­ti­on pro­ces­ses.