WEBVTT

00:00:06.700 --> 00:00:08.122 align:center
Hi, I'm Disha.

00:00:08.142 --> 00:00:09.424 align:center
I'm one of the project managers

00:00:09.504 --> 00:00:11.767 align:center
in Vacancy, working with Vacancy since

00:00:11.907 --> 00:00:13.209 align:center
more than five years now.

00:00:13.730 --> 00:00:15.092 align:center
I'm here to discuss one of

00:00:15.172 --> 00:00:16.254 align:center
my projects, UBIX.

00:00:16.794 --> 00:00:18.677 align:center
UBIX is AI on demand for

00:00:18.757 --> 00:00:19.478 align:center
business users.

00:00:19.979 --> 00:00:21.822 align:center
The objective of the system is

00:00:21.862 --> 00:00:24.886 align:center
to accelerate the AI-enabled solutions, whether

00:00:24.986 --> 00:00:27.250 align:center
it is enterprise or software compute.

00:00:27.530 --> 00:00:29.353 align:center
UBIX is the platform that turns

00:00:29.693 --> 00:00:33.078 align:center
complex simple by managing end-to-end data

00:00:33.198 --> 00:00:34.580 align:center
science and AI lifecycle.

00:00:34.860 --> 00:00:36.863 align:center
This platform is a combination of

00:00:37.024 --> 00:00:38.406 align:center
several internal projects.

00:00:38.867 --> 00:00:41.171 align:center
Dataspace, which pulls and stores data

00:00:41.211 --> 00:00:42.594 align:center
from several external sources.

00:00:43.014 --> 00:00:45.739 align:center
Cloudspace, which manages infrastructure.

00:00:46.040 --> 00:00:48.203 align:center
Modelspace, that is, author solution.

00:00:48.985 --> 00:00:51.870 align:center
Solutionspace, to configure workflows to create

00:00:51.950 --> 00:00:52.711 align:center
models.

00:00:52.731 --> 00:00:55.316 align:center
Insightspace, is an AI API for

00:00:55.336 --> 00:00:57.780 align:center
data visualization and process automation.

00:00:58.010 --> 00:01:00.794 align:center
and production space that helps deploy

00:01:01.034 --> 00:01:02.537 align:center
and manage production models.

00:01:02.777 --> 00:01:04.259 align:center
When I first spoke with our

00:01:04.279 --> 00:01:06.643 align:center
client named John, he shared what

00:01:06.743 --> 00:01:08.465 align:center
his end goal was and then

00:01:08.565 --> 00:01:10.308 align:center
referred to his old platform.

00:01:10.648 --> 00:01:12.511 align:center
Our team in Vacancy reviewed the

00:01:12.551 --> 00:01:15.255 align:center
platform and found complex code structure

00:01:15.516 --> 00:01:16.998 align:center
with old WebSocket.

00:01:17.018 --> 00:01:19.822 align:center
Some spaces ran on backbone.js and

00:01:20.022 --> 00:01:21.224 align:center
old Node.js structure.

00:01:21.725 --> 00:01:24.048 align:center
Many libraries were useless and were

00:01:24.108 --> 00:01:25.370 align:center
making the app run slow.

00:01:25.530 --> 00:01:28.215 align:center
Many packages and libraries lacked updates

00:01:28.375 --> 00:01:29.898 align:center
and had a Java layer to

00:01:29.979 --> 00:01:32.944 align:center
fetch metadata and reduce the performance

00:01:32.984 --> 00:01:34.567 align:center
due to multiple data requests.

00:01:34.828 --> 00:01:36.511 align:center
We shared the findings with John

00:01:36.812 --> 00:01:38.415 align:center
and set a roadmap to implement

00:01:38.435 --> 00:01:38.976 align:center
solutions.

00:01:39.517 --> 00:01:41.440 align:center
As a believer of agile mindset,

00:01:41.901 --> 00:01:44.045 align:center
we set easy to adapt processes

00:01:44.346 --> 00:01:46.470 align:center
from project initiation through delivery.

00:01:46.680 --> 00:01:48.903 align:center
Every day we conduct stand-up meetings

00:01:49.104 --> 00:01:51.487 align:center
where we discuss task priorities with

00:01:51.547 --> 00:01:53.270 align:center
the client and set up plans

00:01:53.370 --> 00:01:55.553 align:center
for the day using JiraPool.

00:01:56.254 --> 00:01:58.237 align:center
Post the day-end updates for the

00:01:58.257 --> 00:02:00.020 align:center
client on Slack.

00:02:00.040 --> 00:02:01.722 align:center
Once the task is implemented, the

00:02:01.782 --> 00:02:04.086 align:center
team gets it reviewed and approved

00:02:04.146 --> 00:02:06.129 align:center
by the client to deploy further

00:02:06.209 --> 00:02:07.150 align:center
on the production site.

00:02:07.651 --> 00:02:09.173 align:center
As a result, the current system

00:02:09.313 --> 00:02:11.316 align:center
is well-enhanced and the client has

00:02:11.436 --> 00:02:13.219 align:center
already started giving demos to his

00:02:13.399 --> 00:02:13.980 align:center
end-client.

00:02:14.090 --> 00:02:15.575 align:center
with very positive response.

00:02:15.896 --> 00:02:18.705 align:center
This way, we maintain transparent communication

00:02:18.946 --> 00:02:20.873 align:center
and focus on seamless productivity.

00:02:21.093 --> 00:02:22.197 align:center
If you're looking to build your

00:02:22.237 --> 00:02:24.404 align:center
product, connect with us to discuss

00:02:24.445 --> 00:02:25.187 align:center
your requirement.

00:02:25.629 --> 00:02:26.090 align:center
Thank you.