All language subtitles for meeting_mike

Hello Mike, good morning.

Yeah, fantastic.

Thanks for finding the time so early and
sorry for the short notice.

Oh, this is a one -on -one. It's just
the two of us.

Yeah, yeah.

In fact, I've scheduled a one -on -one
with Andy, with Matt,

and with somebody else. So, Daniel,
thanks.

Andrew, okay.

Oh, sorry.

Because I saw in Daniel's...

signature in his email that it says
Danny.

Okay, okay, thanks.

Thanks for the heads up, I appreciate
it. So I think we've got Simon's note

taker trying to join.

I can do that.

Do you mind if we take notes?

Okay, cool.

So, Mike.

I'm basically going to be asking really
simple questions like what kind of pen

do you use and how do you take notes and
things like that so sorry if it sounds

too silly but really it's about having a
low -level understanding of

the kind of work that you do within the
document

standardization process so that I can
both get the AI to

understand it and then get the ai to
help you throughout that process so in

mind there's a physical machine and that
machine has a lot of properties and

documents attached to it and what you
guys are trying to achieve is to create

three pdfs that ship together with the
machine one is the service

manual for the service partner one is
the operations manual for the actual

the end user, and then the parts list,
which is essentially the CAD diagrams.

So are we on the same page? Okay, great.

So I'd like to understand from the very
point where you get involved

all the way to these manuals getting
shipped, what

work do you do?

Please feel free to go into detail.

Okay, thanks.

It's a lot.

Okay, so like a pneumatic hose or a
washer is going to be stocked and then

custom parts that are like plastic parts
you'll presumably have to come stock

and then so

Okay, okay, got it. I guess the parts
list is only relevant in terms of what's

documented as part of this project.

So it's helpful to have the knowledge
about what it is and what its

are, but it's not really the core of how
the documentation is

handled. So can you maybe explain

How you store that work? Where you write
things down? Are you interfacing with

a database or sending the information
via email? Is there a text document

acting as reference?

Where are these decisions stored?

Okay, got it.

So I'd like to put something on the
screen and just have a

look at some of the documents that we've
received from you guys.

And if you can tell me, right, so here's
the RC450

document again.

And say I'm working on the user manual.

you'll receive this kind of information
which is not in code format and a lot of

things need to be changed and then you
want to turn that into

something

like this where

you've got a different structure but the
information is essentially the same

This

is

the old

manufacturer's use and maintenance
manual and you want to convert that into

your own

manual.

So where is the intermediate work
stored? You mentioned

that you've got a score of the old
documents and that you've got

emails. I'd like to know where the new
document is.

No, no, no. While it's being worked on.

So who's responsible for, say, I don't
know, writing some

of this non -generic text?

Somebody gets to decide that you need
these label locations, text them, and

somebody's writing this.

Do you make the request to the relevant
person via email, or do you make edits

in the document itself?

So there's a print version.

Okay, okay, got it.

So how many rounds is the document going
to make in the printed form before

being ready?

Is it just a one -off?

Are you making the edits in red pen in
the document once and then it's

good? Or is this like happening over a
period of a month?

All right, that's helpful.

So you start with the structured
baseline on a document that contains a

blanks. You build the sections that go
into the table of contents, and then

you flag all of the things that need to
be done.

And in the draft too, As some of those
things get filled in, you verify them

you verify the overall technical flow
and you make sure that it matches the

table of contents.

And I guess drafts three and four are
just ironing things out.

Okay, okay, got it.

Do you guys use AI in that loop? Is
there some, like, do you use ChatGPT to

write some stuff for you?

Okay, okay, got it. So from what you're
describing, it sounds like the right

approach would be to create an interface
where that document lives that's

accessible by everybody at the same
time. It's somewhere on the web. You can

the draft and you can click in and make
comments and then you get an AI draft

right away.

So it's not,

send off to the relevant people having
to wait

for them to reply for you to validate
but instead the ai which has a concept

the wider context can do a lot of that
work on its own and it can do it faster

and so we can tighten that loop of
coming up with what needs to be done and

approving it and sending it to other
people

So I think I've got a clear idea of

what you need and what the current
approach is.

And I've got a couple more questions,
though we are running out of time.

I mean, you've answered what kind of,
what's the source of knowledge that you

draw upon, thanks.

You mentioned AI and how things can be
drafted.

What kind of visibility?

So imagine that this

42 -page ops document is in its version
3 and

a lot of things have been edited and
removed and added.

What kind of things do you want your
attention to be drawn to?

do you just want to see it like this
blank or do you want like highlight hey

should focus on this

Okay, okay, got it. So it'd be helpful
for you to have the AI identify

discrepancies within the document. Say
on page three, it says that the nut is

this size and on page 25, it says a
different size.

And I guess discrepancies between the
document and like the general

that you have.

Okay.

So what the current plan for the AI
knowledge base looks like is

that there's going to be a code document
writing knowledge base, like a

reference of what things should look
like. Then there's going to be the

reference for a particular product

line. For example, the wheel balancers,
which...

have their own structure, the table of
contents, and a new wheel balancer from

different manufacturer is still going to
have the same table of contents.

And then there's going to be a reference
information on the styling and

formatting. And the AI hopefully will be
able to put as much of that together

for you to just click through and review
and flag things that you'd like to

revisit.

Do you ever...

okay okay um

Yeah, because presumably the manual you
receive wouldn't have that.

Okay.

Yeah, sure.

Yeah, so Mike, thank you so much for
your time.

Is there anything else that you'd like
to ask me or anything I've missed,

anything I should know?

Great.

Yeah, that'd be fantastic.

Thanks.

Feel free to share it over Teams and
I'll have a look.

There's going to be a new detailed
version of that flow diagram coming out.

So I'll keep you posted.

All right. Thanks. Have a great day.