From Code to Capability Exploring the Dynamics of Connixt’s Open Architecture

0:03
those uh in joining here joining us here today uh we’ll send all the attendees a
0:08
link to the recording uh in the next couple days the session will last about a half an hour uh after which we’ll be
0:15
taking some questions for by uh for about five minutes so uh again feel free
0:21
to post any questions you have throughout the presentation in the chat box on the toolbar below and with that
0:29
being said we can go ahead and get started Evan relevant questions Evan not
0:35
any question relevant no questions so far perfect
0:40
okay conveying the message clearly so just to quickly introduce
0:47
myself uh my name is Evan nus and I work here with the business development team at conx and most of you may already know
0:55
pru our CTO and co-founder here at conx now today is I would say a bit of
1:02
an unusual oh my apologies today is a bit of an unusual webinar uh we usually
1:09
talk about what we are doing uh and this one is more about the
1:14
why and the question of why we do what we do uh sort of talking about the DNA
1:21
of conx and exploring the Dynamics of our open architecture
1:28
capabilities just to quickly summarize our agenda for today’s webinar we will begin with the background of open
1:36
architecture and what it means for us and our customers from there we will
1:41
explore why we choose to be open next we will dive into the conx
1:47
data model uh within this area we will examine both the pitfalls and uh of an
1:53
opinionated data model as well as the benefits of imar being open uh following
2:00
this section we will move into the conx API we’ll talk about extensibility as well as our
2:06
integrational possibilities and then finally we’ll wrap up with the conx road
2:11
map to get a glimpse of uh where we’re headed so pru uh please uh if you if you
2:20
don’t mind taking over here go for it thanks thanks Evan hi meeting you nice meeting you all uh pru eam co-founder
2:27
and C at K before even get into the open architecture right I’m originally a mechanical engineer worked for a leading
2:35
um truck manufacturing company and still love the you know smell of diesel uh was
2:41
in R&D um and landed up getting into Sap’s world and then here I am talking
2:47
about kex after what um 25 years 30 years of experience in this field now
2:53
having said that open architecture itself right what is open architecture
2:59
or why we chose open architecture which we are going to you know um talk through
3:05
this this presentation but having said that easy to add a functionality and
3:11
easy to connect with exter external World those are all the two things that we emphasize when it comes to our open
3:17
architecture our product is modular configurable and using standard apis
3:22
right so um having said that from the Imark as a product itself
3:30
right it’s a cloud mobile solution that sits in the middle which connects your
3:35
field Workforce and your back office back office can be our own website or
3:41
your system of choice which is your E Systems so what we do is we connect the
3:48
operations that are done in the field and push it into your backend system your system of choice now with that in
3:56
mind we made sure that our architecture we follow we we we go with an open architecture which is not open source
4:02
again I want to reemphasize that it’s not open source but it’s an open architecture which is modular in nature
4:08
configurable in nature uh which is easy to integrate to any backend system and
4:13
also extend the product with additional modules and functionalities
4:18
now how we do that by reducing the overhead which is right there on the
4:24
slide uh and development time because the product is configurable
4:30
reuse components and modules as much as possible and coexist in the existing
4:35
environment because when we go and talk to our customers right they have their own uh environment they have invested
4:42
millions of dollars in coming up with their e system we don’t want to rock that board we don’t want to change their
4:48
environment but we go and extend their environment in such a way that we
4:53
digitize all their U you know um field processes and then try to push pushing
4:59
the data back into uh the E system so having said that overall we would like
5:05
to coexist in the existing environment and also end of the day cost to customer
5:10
is low that that’s the key here um they they have good return on investment by
5:16
using our product at the same time the implementation goes through seamless extremely well said pru so the
5:23
real question is why go yeah like touched upon uh these
5:31
pointers earlier it’s flexible because the product is completely configurable at both ends when I say at both ends I
5:39
go back to our topology right we sit in the middle we connect your field Workforce and back end office right now
5:45
when it comes to field work Workforce operations anything and everything is configurable for collecting data from
5:52
their workshops from their um uh field work anything that they perform um uh
5:57
you know it’s configurable on on the other end of the Spectrum which is connecting to an AM system we have
6:03
standard set of apis through which we will be able to connect with an existing environment
6:10
having said that like I mentioned earlier we try to reuse as much as possible the components and also scale
6:17
um the product is scalable for faster deployment in the end we would like to be Erp or E agnostic telematics agnostic
6:27
iot agnostic and we are also getting into into AI platforms where you know we can connect with multiple uh systems out
6:34
there so having said that this again goes back to what I mentioned earlier coexisting
6:41
with an existing environment and extending the customers environment now having said that let’s
6:49
get into the goal of this connect to data model itself right built to scale
6:54
right or built for scale now uh the key here is
7:01
more customers right from the beginning when myself and Satish met u in fact we sat in a Starbucks and we were talking
7:07
about it um so right from the beginning we made sure that the more customers
7:14
should not lead to more resources so that the product is scalable configurable so that it runs like
7:22
WhatsApp or Facebook you know we cannot it’s not Apples to Apples but still we
7:27
want our product to be uh simple and easy to use the next is we EMP emphasize
7:33
on your business process we don’t come and say hey my product does this so you
7:39
have to change your process to go ahead and adapt my product so we are not going
7:44
to say that we are going to say hey tell us what process you are uh you know following as of now we try to optimize
7:52
the process if there is a uh there is a space to optimize having said that we
7:58
try to adapt your business process and then Implement our product this we
8:03
achieve through our open architecture by configurable um you know um front end
8:10
and also APA based backend right which leads to the next one which is easy to
8:16
integrate now when it comes to easy to integrate right I want to emphasize on this we can connect with more than one
8:22
systems at any given point of time we have a set of um out you know outof the boox adapters which we connect with your
8:29
am systems you can Vis visit our website to go over it but to cut the long story
8:34
short our whole integration platform is configurable with parsers with apis rest
8:40
apis and things like that so that the the the integration to your backend system becomes easier now having said
8:49
that your data is s sitting in the cloud right it is with us your data is your data right it is available everywhere
8:55
based on how you choose to be we have our own standard apas again it goes back
9:01
to our open architecture that we are talking here where we have our own standard apas using which you can use
9:07
the data utilize the data for analytics purposes we have our own analytics platform but but at the same time if you
9:14
are using say powerbi for your analytics purposes you can access your data using
9:20
our standard apis and also it is secure uh when I say secure um you know each and every call
9:28
that is made into our environment is authorization and role based
9:33
authentication and authorization is always there in each and every call we have built our apis in such a way that
9:40
each and every call goes through these layers and then hits our uh data itself
9:45
now having said that again the overall goal here is product is easy to use
9:51
product is easy to implement the cost to customer is low that’s the key and that’s the reason why we basically
9:58
selected this data model model and we also selected open architecture and also being a product company right sitting in
10:03
the middle when we go to our customers each and every customer is going to use are going to have their own e system so
10:10
again goes back to we being Erp or E agnostic
10:17
on so that I mean that brings us into the challenge you know with these opinionated data models would you mind
10:23
speaking to that a little bit yeah yeah we kind of touched upon this um um in the in the the earlier slide itself your
10:30
business must adapt to resultant software design right I touched upon that in the very beginning where we work
10:38
with your own process we don’t dictate this is what you need to do because my product or our product does only uh
10:44
things in certain way right we don’t we don’t dictate that we adapt because the product is configurable because it is
10:50
open to connect to any environment out there it is um um you know we we
10:56
basically adapt to your business processes and and your way of doing business training right um the the
11:04
product is so simple and easy to use there is not much training needed when
11:09
it comes to our product we we emphasize on that because we are talking thousands of users or hundreds of users given for
11:16
any organization size right so we we want to emphasize on that and also development overs again it goes back to
11:22
Product Company right um we don’t want to have U more uh development resources
11:29
based on our number of customers so we try to reduce that to um so in a nutshell again it goes back to being
11:36
effective simple and easy to use and uh low
11:41
costone love it love it so I I would say if there is one question that I
11:47
continually address you know being in my role with everyone I speak with it’s how
11:52
does Imark make life easier for your crew are does it make life easier for
12:00
the crew right yes right it does it does you can talk to our customers they they
12:05
they will uh you know talk about it now how it is um how this architectural
12:13
approach or this way of configurability makes the life of the uh crew to be
12:19
easier it’s transparent it’s non-invasive that’s the key there the
12:25
end user will not even know what is happening in the background but it
12:30
provides enough information for him for him he or she to do the task on a
12:36
day-to-day basis like for example say they are doing a maintenance task they are working on a specific truck we make
12:43
sure that that specific individual gets all the information related to the truck
12:50
that he needs to perform or that helps in him performing that specific task
12:56
right so it is seamless it is non-invasive again the the the end user
13:01
the crew will be clicking on certain buttons and that’s it all the thing happens in the background we go grab the
13:08
information from multiple systems and show it to the user so that he has all the information that he needs so how we
13:15
make the life of the crew Easier by being non-invasive by being non-invasive
13:21
at a level where the end user doesn’t even need to know all that he needs is a tablet that he needs to work with that’s
13:28
it that that’s all tablet or a phone um that that he needs to work with so so
13:34
that’s how we achieve it in fact you know I would like to um touch upon one thing you know my my hobby is watching a
13:41
lot of movies and I have interest in watching movies right you
13:47
know how you can tell that is a the art director of that movie is a best art
13:53
director only if you know the set they have made right is not a when you see the movie you should you should not feel
13:59
that it’s a set you should feel that hey it’s it’s it’s happening in the real world right so like that when when when
14:06
a uh when a uh technician is using our product he will not even know the
14:11
complications that is happening in the background but from his or uh her perspective they will have enough data
14:17
in their hands for to perform their
14:23
task I really like that part about the seamless uh transfer of data between
14:28
systems I mean aside from that I see multiple benefits you know that stem
14:33
from that exact foundation and firstly being a faster deployment you know our
14:40
goal as uh you know as uh developers and people that are helping these customers
14:46
of ours is to get their Crews using the app uh effectively doing their jobs
14:51
within the first four weeks I think this timing is absolutely critical to
14:57
understand you know where we can identify efficiencies within those processes but also boost that user
15:03
adoption and I feel like you’ll hear it like you’ll likely hear it you know from the crew first that are that’s using
15:10
imar along with all of the Native features like the camera the microphone
15:16
uh the GPS capabilities that really are built in there to simplify their tasks
15:23
and allow more time for other projects or other time on tools right and these features will also really enrich that
15:30
data being recorded within those tasks so again those the seamless use from
15:36
system the system but also within the mobile uh device itself uh really comes
15:42
together well we also inforce uh like you mentioned security and that data
15:47
validation to you know ensure those tasks are being done correctly but also
15:52
safely you know within that uh safe Cloud environment and then lastly imar
15:58
is really built for scalability I know you touched on this several times but I talk with numerous customers about where
16:05
they started with Imark and where they are currently and I’ll tell you once imar starts serving one part of their
16:12
business or operations they’re likely soon to find that other areas it can be applied to
16:18
that it’s going to seriously help and step in and just to reemphasize on the first
16:24
one right your process can be digitized in four weeks the key there is a again open architecture it goes back to the
16:30
topic that we are discussing today configurability of the product it’s 100% configurable And we are very proud of it
16:37
uh doing it that way and now when it comes to enforcing security also we always track who did what when back
16:44
that’s always there each user will have their own user aident password the support single sign on and all these uh
16:51
you know connectivity to the external systems is made possible by our open open
16:57
architecture so if you don’t mind talking about the imar API here I think this is really where the connection is
17:04
built and governed between those systems yes so um to start with right from early
17:11
early on right um any communication that um that happens again to start with
17:19
going back to how the product is laid out it’s a cloud mobile solution our business objects and you know business
17:25
logic sits in the middle hosted of Microsoft issue and there is uh imar mobile app that
17:32
accesses the cloud and the E system can access the cloud so we sit in the middle also right now we call it as mobile
17:39
extension framework so any communication that happens either to a mobile device
17:45
or to a backend system right from day one wire through apis uh rest apis and
17:51
we even have soap web services I know for some of them it could be old but we deal with customers who have home grone
17:58
systems um and things like that so we even support soap up services and rest apas Json objects so right from day one
18:07
um you know it was API driven access all the data in the backend system
18:13
seamlessly this is again having enough hookups in our system so that we can
18:18
coexist and connect to multiple systems at any uh given point of time which also
18:24
goes back to integrating with e CS Erp and even operatory applications right
18:30
when it comes to integration to the backend system we have customers uh in
18:35
all Spectrum where if your e system has uh a set of apis a middleware layer we
18:42
can work with that API by leveraging whatever that is available with the E
18:48
system itself uh the the next level is if uh an e system does not have an API
18:56
uh or if the customer doesn’t want us to touch their API layer or their we have
19:02
our own set of rest apis using which you can push and pull data with our system
19:07
again standard uh rest apas with Json object now the third is homegrown
19:14
systems right if there is a e out there which could be an homeg Grom system or
19:19
an e system that does not have an API layer as long as we have access to that
19:25
uh database as long as the customer provid the access to that environment we
19:30
are capable of you know creating an adapter layer so that it gets connected with our Cloud environment and uh you
19:38
know I don’t want to name any customers here but uh you know we have done we have examples on all these scenarios um
19:47
working with customers where we creating an adapter for them or working with an layer that is already available or
19:54
customer working with our API layer that is out of the box uh that is available and like I mentioned earlier it is
20:02
hosted and run out of you know Microsoft asure we support single syon so um
20:07
single signon in the sense where authentication like U um adfs or masabi
20:13
or in as long as there is an APA available for us to talk to we will be able to work with that system again goes
20:20
back to the open architecture APA driven open architecture I think I see we have a
20:26
couple questions here if we can address them really fast sure there’s a question coming in says that our architecture has
20:32
a significant impact on implementation timelines can you speak to that a bit more yes this again goes back to um
20:42
integration through the standard apas and configurability right we talked about you know you know seeing your
20:49
process within four weeks we can Implement your process within four weeks right because our both ends are
20:55
configurable and it’s all APA driven we can uh the implementation timeline goes
21:02
u u into four weeks or six weeks or eight weeks based on the complex complexity of the process again I I I’ll
21:09
will be very cander here if there is a system out there which does not have a
21:14
uh uh middleware layer to talk if we land up creating it based on the
21:19
complexity it may add some couple weeks two three weeks uh to the project timeline but again because the product
21:26
is configurable uh from our scope of things implementation timeline is is uh
21:33
so low u in fact there is there is a there is one customer which we made them
21:39
live in five weeks actually with some uh with the doot inspections and things like that uh we made them live within
21:46
five weeks again configurability plays a vital role here of course of course
21:52
another question here it says Enterprise systems integration is a bit of a challenge for their business
21:58
they use a legacy environment with minimal capabilities can we really
22:03
accomplish integration with any system including that one yes we have done that
22:09
uh the reason why we say uh um why why you hear a confident yes there is
22:14
because we have done that before um if again like I mentioned earlier if there is a homegrown system as long as we have
22:21
access to that data to that database to that environment we will be able to you
22:26
know uh uh develop a layer for your environment and then expose it to the outside world
22:33
again once you allow access we will go through the standard processes like creating rest apas um you know only
22:41
Access Data through St procedures I I don’t want to go too technical but at the same time I just want to let you
22:46
know that we will follow all the best practices and we will be able to connect any system out there and especially if
22:53
an e has a middleware layer it’s a Nob braider just use their apas and we will be able bble to um uh connect with that
23:00
uh E Systems out of the box sap Oracle uh trapes Trimble um all these systems
23:07
we have outof the box adapters um which which can talk to the system directly
23:13
maximos right all these systems but again like um the the question if there is a homegrown system if there is a
23:19
pretory system as long as we have access to that environment we will be able to
23:24
come up with an adapter for you I hope the question right yeah I believe so and
23:30
then there’s one more here coming in is there a fundamental difference uh in
23:35
architecture between you know what we offer and for instance uh another E
23:40
maybe I’m kind of blanking on some specific third party eam at the moment
23:46
but is there a fundamental difference yes um that is it it goes
23:51
back to our uh DNA right um see to start with we are
23:58
um our DNA is a cloud mobile product we we do product for digitizing the field
24:06
uh tasks right so we emphasize on that we are geared to uh you know um
24:13
emphasize what the mechanic and technicians do in the field so again to
24:18
start with our apps are native apps right it is driven for IOS and Android smartphones and tablets that itself uh
24:25
the user experience is far far better when it compared to other U products but
24:30
having said that uh you know fundamentally we are geared towards end users and Cloud Mobile on top of it um
24:39
we are Erp agnostic when I say Erp agnostic it goes back to what we talked earlier right set of apis uh and when we
24:46
say Erp agnostic we can connect with more than one system at any given point
24:51
of time um um how we can achieve that through our apis uh through
24:57
configuration through through communication ports uh through parsers and things like that but having said that what is the use case right let’s
25:04
also talk about a little bit of use case right so uh say uh they are performing a a task that is based on a work order uh
25:11
and they also have a system for time management we as a product who who
25:17
collects data from the field we collect that maintenance task related data and also the time consumed associated with
25:24
those tasks and then store it in our cloud and when we come in to your backend system we communicate to your
25:30
both your systems like the the maintenance task related information goes into your e system if you if you
25:37
use uh uh time management system we can post the time management system to uh
25:44
your uh or time management data to your time management system so we can connect to more than one system at any given
25:51
point of time and we can also pull data from more than one system and E system
25:56
or E based uh software cannot do that or even if it has to be done there will be
26:02
a lot of um implementation that’s going to happen so having said that we can also pull data from multiple systems
26:09
because our architecture is um basically open now last but not the least um I I
26:16
should tell you this um you know we can we can work with what the the the enterprise system
26:24
provides in their own format not only that we can handle more than what an e
26:30
can handle let’s take an example right there is a specific asset um you know as
26:36
a as a company you have to collect like 100 different characteristics for that specific asset but your e can only store
26:44
50 of them what happens to the rest 50 we can store it you can run reports and
26:49
analytics in our system we can generate PDF reports in your own format and push it into your em system so essentially we
26:57
can handle more than what an em can handle this goes back to working with
27:02
your own process we don’t ask you to change your process we adapt your process and implement it perfect and one
27:11
quick question coming in lastly here is is the data transfer live or can you talk about if there’s a time delay in
27:18
the push uh in transferring information that’s a good one right again it goes
27:23
back to configurability of the product now based on the sensitive ity of the transaction you can configure our system
27:30
to be either real time or asynchronous like for example um say they are
27:35
performing a maintenance task right whatever the result of that maintenance task getting pushed into U an em system
27:43
can go in an asynchronous way because it’s going to go back and update a workorder whereas while doing the
27:49
maintenance task itself say they are consuming Parts a user wants to know do I have the parts in the uh in my
27:57
inventory that will be real time because he needs to know uh whether a part is available
28:02
or not so depending on the sensitivity of the transaction or or nature of the
28:08
transaction it can be either uh batch mode or asynchronous or real time so
28:15
even the data transfer itself is configurable yes essentially yes
28:21
perfect so just moving on here’s a quick screenshot of our current Partnerships
28:26
um again these are win-win Partnerships for our joint customers I know a lot of people out here are familiar with some
28:32
of these uh companies but if you want to speak to any of these you know please oh um yeah see uh when it comes
28:40
to um some of these products right um I don’t want to again name them some of these products have an extensive set of
28:48
uh rest apas using which we are pushing and pulling data when it comes to these telematic devices right geotab samsara
28:55
uh and go motive right that’s motive there right so those three we even automate PM work orders um we again
29:03
there is a common framework it goes back to open architecture set of apas there is a common framework that we have come
29:10
up where you configure our system to connect to these uh multiple environments out there and then grab the
29:17
data for that asset like for example um you know during our demo that’s always
29:22
interesting when we show um we have three assets one goes to geotab one one goes to samsara one goes to go motive
29:29
right we are capable of connecting with multiple telematics platforms under one single host it may not be the case in a
29:36
real life uh scenario but that shows the flexibility of our product right so we
29:41
can connect with more than one system under a single host um at any point in time uh similarly uh take Trimble or
29:49
Maximo sap all these environments we use their standard apis they have not customized anything on their side we
29:56
have worked with their their own apis and we are able to uh push and pull data into these uh E Systems in fact um you
30:04
know MTA is not listed here but uh for um customers like MTA we developed our
30:09
own adapters for them so um to cut the long story short yes we are working on
30:16
expanding this uh partnership footprint also by connecting with additional telematic devices and also um you know
30:23
in a moment we will also go through the um road map we we are extending our
30:29
product to connect to this AA platforms out there which brings us right to that so please uh okay for now um again we we
30:39
touched upon this um you know um road map itself in our earlier webinar when
30:44
myself and Satish were talking um but we started with digitizing which is
30:50
in the uh past right and then uh the present is uh basically making adding
30:56
additional modules and then you know our our apps being built to scale and all
31:02
those things but I want to emphasize on the future right we are planning to expand into um other verticals which is
31:08
healthare energy and insurance uh right now um uh we have Transit utility
31:16
construction um and tracking uh Logistics right so uh we do um um have
31:22
are playing a role in those verticals but we are planning to extend now how we can extend into all these other uh uh
31:30
verticals with minimalistic change to the product uh uh itself through
31:36
configurations we are able to extend our product even to new verticals we are
31:41
very proud of this where our our product is a single code base that is used
31:47
across verticals even today uh trucking companies uh uh Transit companies uh uh
31:54
utility uh customers and some construction companies too they use one single uh code base one single product
32:00
for all their uh maintenance needs because the product is configurable and we are system agnostic Erp agnostic uh
32:09
environment agnostic and device agnostic we support both IOS and Android so um
32:14
that is when it comes to you know extending into other verticals and we are also planning to add modules for uh
32:21
procurement and scheduling when it comes to procurement um not on a typical procurement basis but for parts right we
32:28
talked about that um right now we are allowing our you know mechanics and
32:33
technicians to go over how many parts is available looking over the inventory and
32:39
then consuming those parts right now next is we are planning to uh expand or introduce a module for procuring those
32:46
parts and automating uh the procurement through AA platforms um in fact there
32:52
are like five six different use cases that we have identified using which um
32:58
we are going to basically uh you know expand our footprint and play a role into um you know AI itself now when it
33:07
comes to AI right artificial intelligence I have I want I want to go back to our design philosophy itself
33:14
this again I have talked many times uh through Linkedin I have talked many times to the to our customers we don’t
33:20
do anything in our product sorry uh we don’t do anything in uh in our product
33:27
for the sake of Technology we never do that unless there is a value ad there is
33:32
a use case there is sense in adding that technology to our product we will go
33:38
ahead and add it otherwise no we we we never add anything for the sake of technology that is the reason why when
33:44
everybody was talking about AI we were working on a realtime use cases using
33:50
which our product can benefit and then get into the AI platform itself and
33:55
right now we have started working on it uh the use cases I I just touch upon this again uh failure pattern based
34:03
alerts uh you can ask our um uh app talk to the app and ask hey how to do this
34:09
specific maintenance task and translation Speech to Text uh Parts
34:14
ordering like I mentioned earlier and also work instructions automation so these are all some of the
34:20
use cases that we have identified um uh when it comes to um you know implementing AI platform uh into our
34:27
product itself now having said that all these things that we are
34:34
doing because our architecture is open there are enough hookups in the product
34:40
it becomes easier for us uh you know when I say easier there is not much
34:45
change to our base framework itself with minor modifications we are able to extend into all these additional modules
34:52
platforms and verticals great than thanks BR I
34:57
appreciate that so again I’ll just quickly touch on this and what do this all boiled down to
35:05
our solution is in my opinion it’s designed to make life easier for your
35:10
crew yes that the tech is great but really that’s not the point we aim to create more efficiencies and better
35:17
results within your operations uh High user adoption is a great way to measure
35:23
its success and we really achieve this by you know ultim Ely coexisting and
35:28
being non-invasive and all the things that you’ve you’ve touched on throughout this webinar and thank you again for for
35:34
going into detail on on all of those
35:40
things sure so with that being said I’m just going to leave it open for questions um if if you have anything
35:47
please feel free to throw it in the chat box and we can address them right
35:53
now or if you want to talk to us talk to
35:58
toen yes of course I will make myself available to anyone and everyone who is
36:04
uh who’s on today and if anyone has any further questions please feel free to to
36:09
reach out again a copy of this webinar will go out to all the attendees so
36:14
you’ll be able to review everything that we’ve talked about today but if there’s anything specific that you have
36:20
questions on that we can address please again feel free to reach out to me I’ll be happy to um hop on a call if necess
36:27
or email correspond back and forth if that’s the way you prefer to do
36:36
it
36:46
perfect looks like may
36:51
have think we addressed all the questions in the Box here
36:57
oh I see a question come up um isn’t native apps higher over
37:04
there is some question out there related to that native apps yeah okay so the question is um you
37:12
know is it overhead to have native apps yes as a product company yes we do have
37:20
an extra overhead because we have to maintain uh two versions of the uh
37:26
product same code base when it comes to our business Logics but yes we have to
37:32
maintain but but I want to emphasize on this user experience and adoption rate
37:39
those are all the key aspects for us right which we touched upon earlier so having native apps helps us a lot to
37:47
achieve that so we never want to go back uh to any other uh way of doing apps um
37:54
based on these things that we hear from from our customers like for example uh I talked about speech to text right there
38:00
will be a seamless transfer like you click on a mic icon there you talk to the app it’ll type it uh for you so that
38:08
becomes seamless say there is a barcode right uh for a for a part number or an
38:13
asset number there is a barcode you don’t need to have an external device or extra device you just uh scan the
38:21
barcode and then it grabs it and then puts the value there so that is uh basically Ally barcode scanning without
38:28
any external devices right native apps helps us to achieve that also you know a
38:33
Matthew which is used by one of our customers like say there are 10 tasks that needs to be performed by a user at
38:40
any given point of time right as long as there is an address or a latitude and longitude associated with that specific
38:47
set of tasks we’ll be able to put a pin in the map view and then show hey this is where the tasks are distributed so
38:53
that the user will know that’s my current location my closest job is there so I’m going to get there and then go
39:00
ahead and perform the task so things like that are possible so why um um why native apps there is a
39:09
seamless transfer between the mapping software between the speech text SDK uh
39:15
barcode scanning SDK so all these things happen seemlessly because of our apps or native app so the benefits we get out of
39:22
it overwhelms the the the over it that we have on maintaining the native
39:28
apps uh that is one um and there are other questions too hold on yeah there
39:35
is why conect why not incomp yeah I think we we kind of touched upon this earlier why conect why not incumbent
39:42
Enterprise lender right so yeah again like like I told we can handle more than what an can handle uh we can connect to
39:50
more than one system at any given point of time and the product is configurable to start with um you know you it’s it’s
39:57
a um true U I should not say true awesome user
40:03
experience when it comes to our mobile apps you don’t need to you know um uh believe me you can talk to our customers
40:10
they say that actually so it’s an awesome user experience so once they start using our product they don’t want
40:16
to go back to uh paper or any other product for that matter and if there are any other
40:22
questions we can cover those I think that’s it unless anyone has anything
40:28
left please feel free to to go in and again please um reach out to me if you have anything further but I just want to
40:35
say thank you for your time and participation with us today this was uh really fun for us to engage and talk
40:41
about really where we’re going and what we do best uh from for everyone watching again you’re going to get a recording of
40:47
This webinar via email and it’ll be hosted on our YouTube channel and our website as well please feel free to
40:54
follow us on LinkedIn if you’re not ready and subscribe to our newsletter to stay up to date with all the
41:00
developments we have here at conx and with that I’d like to come to a
41:05
close Ru there anything else you would like to add no I’m good thanks a lot nice meeting you all any questions
41:12
please reach out to us bye thank you