Josh:

Hi guys, thank you for coming along to our June TDS reference group webinar. Apologies for our last postponed webinar in April. It was postponed due to the COVID-19 impacts. We were advised by our communications group not to schedule that particular webinar. So apologies for that. But hopefully today we can catch you up on our progress generally, and some of the new shifts in focus, I guess, for the program in the next financial year. So I just wanted to introduce on the webinar today some of my broader team. So Emily and Deanna, a lot of you guys are probably in direct contact with both due to onboarding and any direct engagement around IPR onboarding or integration. So I just wanted to, I guess, recognize those two for their work so far, but also they're the key contact point within the program group. So we've also got Cam here today. You guys have met or heard from Cam before. He's our senior delivery manager. He's going to go through a demonstration for us later on in the webinar.

Just general housekeeping. We've using GoToWebinar again for today's session. It's best if we leave any questions to the end of today's slide pack, so we've got a question slot at the end. During the demo there's I guess a window ask for questions at the end of Cam's demo. Any technical questions or any other requests, I guess, for any other type of demonstrations that you might be interested in. The webinar should today probably run from a maximum of 30 minutes. We've got some high-level information to give you on, I guess, the next stage of the program, but it's fairly light today. Let me know if you cannot hear or view any of the screens by the chat option, we can fix that for you. And just the fact that the webinar today will be recorded and we can publish that by the website, our corporate website, probably tomorrow or the next day. So we'll send out an email wrapping that up to all attendees and all reference group members.

All right. So just as I mentioned, today's agenda included API got demonstrations that Cam will take us through. The focus of those demonstrations today will be new design application API. There's I guess, room for other demonstrations, but it depends on the nature of the transaction that you're keen on. If there is something else that you are interested in terms of demonstration or more direct engagement with us, please reach out via our inbox. We can set those up at any time. We do a lot of direct engagement with interested customers. So we can take you through all of that with our development team, do demos, that sort of thing, so please reach out. We'll go through a general program update, including I guess, a wrap-up of progress of the API build. So we'll go through that delivery roadmap and give you some detail on what the minimal paths we've got left to complete that scope.

We'll also, I guess, provide a brief update about some improvements we have made to our developer portal. Now, existing customers will know that we were using MuleSoft Anypoint platform, and we've upgraded that or the vendors upgraded that to a platform called ACM. So it's fairly similar, but there's some different elements and we're to start moving people across to that realm soon-ish. We've got some existing customers using it. We're refining some of the feedback with that vendor, but we'll take you through, I guess, a bit of high-level information about that platform.

We'll introduce stage two of the program, and that's all about replacing e-services and I guess creating a new web experience on top of the API foundation that we've built over the last sort of 18 months. So again, that'll be fairly high level. We'll touch on, I guess, the first quarter delivery items we might have to get who... I guess the customers who are interested in that realm across the near future roadmap for that replacement.

We're going to share a new API video with developed, which I guess might give some interesting customers and their, I guess, exec or partners or investors some information, some context around what our API's actually do. So it's fairly high level, but it might be a good way of sharing with your broader firms about what benefits these API's can bring your business. As always we'll do a quick poll just measuring our level of engagement throughout the program. That will continue. We'll talk about what is next from this reference group webinars standpoint is, and just at a high level we're keen to continue it and we will, but we want to refresh it and shift the focus to that web offering or the replacement of e-services as we push forward.

And finally, we'll conclude with any questions that we have. So we haven't set a date for the next webinar yet, but that should be in the near future with one of our first, I guess, releases in the web space. So keep an ear out for that and we'll be in contact. So, so we might move on to the API demonstrations with Cam. I'll hand the platform over to Cam. Please, as I said, any questions, probably leave until the end of Cam's demo, and we can unpack those when he's finished. Thanks Cam.

Cam:

Cool. Hey guys, sorry, I'm just messing up Josh's presentation. So just bear with me. I just need to jump into Postman. I think most of you guys have seen the tools that I have done a demo with before. So again, it's just a mocking tool, like a test harness, which is used to integrate with IP Australia's APIs. Today I just want to quickly go through the designs new app, which kind of rounds out our API coverage in terms of applications. Obviously we've previously been through trademarks, designs and patents as well as things like correspondence and renewals. So again, as Josh said, if anyone's keen to say something in particular or a one-on-one time about a specific matter, just let us know and we can set that up for you guys.

So just to dive into the demo, obviously I won't harp on too long because I'm assuming most of you guys have seen how the general flows of the API is work. Obviously our APIs are secured by OAuth, so obviously in this screen all I'm doing is using my customer ID to grab an access token. That access token will be persisted onto all of my requests and is valid for, I think we've set up for roughly an hour, but we're also looking to extend that out if that's suitable for some people just to minimize the amount of calls people have to make, and hopefully save a bit more time. So obviously with designs, it is very similar to a trademark application and I'll just try and show you guys the structure of the request there. We cater for all types of design requests. And I know it's not a super popular IP right, but again, it is an important part of our portfolio. So we cater for a single designs, multiple designs excluded and also further designs.

This structure is very much similar to patents and trademarks where you call out your design category, your agent and your applicant customer IDs, which you create through the customer flow. You can then add any designers, for example, as metadata in the application, as well as your product name and your representation. So I'll quickly dive through the actual flow of a whole design app. So the initial step... Well, it's up to you guys which order you want to use, but the initial step would be to create a new customer for the relevant applicant, or agent if you're not the agent for the case which is probably unlikely, but simply by calling the customer end point for creating a contact. That ID you get back in the message, which we've kind of touched on before is then persisted into the application payload as the agent or the applicant. Just for simplicities sake I've preloaded a customer here that I'm applying for the agent and the applicant role, and then I've got obviously my designer metadata down here.

The second step would be, and probably the most important for designs is the representation. So again, it's using the same document API flow that we've shown before where you just simply upload your attachment with your IP right type, your file name and your image types, that sort of thing. So I'll just send that in. I'm hoping it works. cool. So obviously I've got my attachment ID back and that means that you've uploaded it to IP Australia.

Obviously it's not lodged. And I think we've again, gone through this before, but this is the file ID you then attach to your application. So again, here, I'm simply passing that ID into the design payload down here, and then that payload will get sent off to IP Australia once it's complete with all its relevant information, and it looks like I'm having a good day and it's working. So obviously this is the payload you'll received back upon a successful submission of a design. You will get your batch ID and you'll note that it has an AD which is for a design, your IP right number, your reference, any fees payable, as well as some fee descriptions and fee calculated amounts, which is obviously probably most relevant to you guys.

So it is fairly simple. And again, it's very similar to designs and trademarks. So I'd probably just want to throw it open to questions. Obviously I don't want to dig through every permutation of designs because there's quite a number, but those are in exchange or Anypoint... Sorry, or ACM if you want to have a look there at the RAML spec, otherwise sing out and we can dive into those in more detail either offline or on this call. So is there any questions on that type of flow?

Josh:

I think guys you can put your hand up or topic type a question in for Cam. Either or. And bear with us, we're running the webinar technology today. We normally have an expert with us, but we're trying our best, so apologies if we get something wrong.

Cam:

So does anyone have any questions or want to prompt anything? And again, if you're having trouble with the technology or where... Here we go, here we do have a question. The application date filed.

Josh:

So that should be part of the response, Jason.

Cam:

Yeah. So the question is just around the filing date of the response, obviously that will be deemed once you have this response payload, the time and date of that response will be when it was deemed filed. So this is pretty much your filing receipt that you get with IPA. If it was currently through B2B ORI services, as soon as you've seen that filing notice... Sorry, I'll say filing receipt, that means we've got it and it's deemed filed with us. Obviously once it's processed through the backend in our admin systems, you will receive your correspondence. And so what you can do as well, once you've got this transactional ID, you can call the transaction API with the batch ID and it will confirm the status of that transaction. But as I said, you can rely on this as the filing time and date.

Josh:

So essentially once we get this 200 message as a success message that confirms the date. Yeah. Thanks for that, Michelle. Any other questions guys? That might be a hand up. Can we accept that?

Cam:

Okay. So I can see that we do have someone's hand up here, I'm just... please bear with us. This is our first time running the whole show by ourselves. So hold on. I'm just unmuting you now, [Debra 00:13:42].

Josh:

You're good to go now.

Debra:

Hi, can you hear me? Yes. Can you hear me?

Josh:

Yes, you're good.

Debra:

Oh, good. This looks extremely complicated and way over my head and my colleagues head. This surely isn't the new way that we're going to do filing through eServices services?

Josh:

No, so good point Debra. So what I want to make clear is this is purely, I guess, the B2B component still. So what Cam's demonstrating here is the APIs we've developed in B2B focus space. So this requires integration to your case management system, that sort of thing. So what we'll talk about, what I'll talk about later on in the webinar is the shift then to using a new e-services like platform. So we're actually going to replace e-services with a new web experience, which will have a, for lack of a better term, a UI or a screen on top of these APIs, which make it more usable for a human.

Cam:

Yeah. Sorry Debra, usually we give more context. So sorry if anyone's this is their first webinar, but again, just reach out to us and we can take you through the whole, I guess, backstory of the API channel and where it's applicable. And again, it's not for every customer, so that's a great question. Sorry for not giving that context up front guys. We do forget that we have some new guys who haven't been on every webinar.

Debra:

Then also, can I just ask as well, does every firm have to go onto the B2B platform, or can we still just use it like we're using it on the new platform?

Josh:

So another good question. So it's really up to each firm as to whether they want to invest in integrating with the newer API platform in the B2B space. So that's direct integration. What we are doing in the next part of the program, as I said, is replacing e-services in a stage type approach. So by June, 2021, end of June, 2021, we hope to then decommission e-services as it is now and actually have a new e-services experience, if that makes sense. It won't be called e-services, but it will be a experience platform using these APIs as the engine, if you like.

Debra:

Okay. But we can see there'll be in the background and we don't have to see them.

Cam:

Correct.

Josh:

Correct.

Debra:

Fabulous. You can mute me again.

Cam:

I can see you've got a question as well around the timestamp of this request. It is actually in the response, when you get this mess message back you will have a timestamp on your end that says what time you received the actual 200 back. Unfortunately the tool that I'm using is an API test for the dummies, which is why I use it, but it doesn't show that raw message you would have in your log, for example, about the timestamp. But again, you could, like you said, you could call the transaction query and it will tell you what time it was filed.

Josh:

And received.

Cam:

And received as well. Hope that answers the question. I might jump to a question on about the applicant being on record with IP Australia. This is probably a more complex subject we had touched on in a previous webinar, which is a good question. So with the new way of... with the API integration, and again, we're talking about the B2B level here, we are moving to a much more modern platform and we have the idea of customers having your own phone book, I guess, is the easiest way to explain it, so that you call our customer API and you can create customer records in there and use that reference forever going forward to refer to that customer.

Josh:

A good way to look at this, and I think the term we use as part of our platform in Anypoint or ACM is private address book. So you guys will build up, if you're keen to become a B2B API customer, you can actually build up your own private address book of your clients. That also enables us going forward to make sure that customer data is cleansed. So you guys can actually use an ID of a particular client, let's say Samsung or something like that and reuse those each time you file a new application on behalf of that customer. So it gives you cleaner data and it gives us cleaner data going forward, and I guess it gives you the ability to manage your own private address book.

Cam:

On that as well, like I said, customer is a little more complex than the design flow I just showed in terms of understanding it, the functionality is quite simple. But feel free, Catherine, if you want to reach out to the team and myself, we're happy to do a one-on-one and kind of dive into this, because again, it is a little more complex and it's very different from the current B2B setup. I have another question from yourself just around the same thing before I dive into the other questions, just around the rules. Again, if you have a look at the RABL spec in Anypoint or ACM, it does describe there the validation rules.

In terms of the rules from B2B and e-services nothing's changed from a business sense. Obviously we're being a little bit smarter around picking up more granular data and making sure the data's correct. For example, like addresses and names and things like that, and-

Josh:

Added validation on top of that.

Cam:

Some extra validation, but again, it is outlined there, but apart from that we're not changing anything. There's not a major change in the way we're accepting or denying requests, but it is all outlined there for anyone to go and have a lookout. So it is worth diving into that.

Josh:

We had a question from Greg saying, "Do I recall you saying it will not look like this?" So again, the API... I haven't got a UI on top of it yet, so we're building an experience over the top of these APIs for a replacement to e-services. So hopefully that becomes clearer as we go through the slide deck today, and as we start to release functionality in the web space. So looking at the test platform that Cam is using, I can confirm that this is not something that a firm who is using a web platform will see. This is the underlying engine that drives the experience.

Cam:

Yeah. So just to give a little bit of context. I guess the way I explain it to people is more that the first part of this program has been to build out the underlying technical layer. So the APIs to be more flexible, easier to use, easier to integrate with for not only customers who are using B2B, but any third parties who may be interested in integrating with us for services they provide.

And the second part of the program, which Josh has talked to you on it and we'll dive into probably now, is that we're using this API framework to build a UI customer experience on top of. So it's the same engine underneath, we're just offering it to people via the API and [crosstalk 00:21:32], or offering it in a UX normal website type experience as well.

Josh:

So I think the best way to capture that is the directing integration with the APIs, Greg, is it's almost like a machine to machine interaction, whereas us building an experience UI over the top of these APIs means it's a human to machine interaction. That's at the highest level. Hopefully that clears that up, but we'll cover that more as we go. Any more questions guys? We might move on to the next part of today's webinar. And I think it's where we do... We cover off or wrap up I guess our API build if we just go back to that PowerPoint. Just press play, don't you? Apologies.

Josh:

So we're just back to, I guess, the wrap-up of our delivery roadmap in the B2B space. So keep in mind, this is the B2B focused delivery scope and schedule, and as you guys can see, we've completed the vast majority of transaction and feature or API integration pieces here. I know a lot of this terminology might not make a huge amount of sense externally, but essentially what we've got left in the B2B space in terms of transactions is new plant breeders rights application requests and associated plant breeders rights associated service requests. So things like variations, payments around PBR applications, that sort of thing. So there isn't much left, I think we're over 95% in terms of coverage, transaction wise with current B2B and e-services offerings. So that's quite a good thing. So we're quite on track, I guess, in terms of our B2B delivery roadmap.

And as I said, I'll dive into next where we're at in terms of the next stage of this program and that focus on replacing e-services. Just a couple of other quick things. We've got around about 15 or 16 active API consumers in this channel now, which is really good. Now that covers transactions, but also our IP rights search APIs, and an update on that. We've got the AusPat API or patent search API around about four to six weeks off. So we'll give some more information, I guess, in the next webinar around that piece. But if you're interested again in the patent data and accessing that in a machine to machine sense, please reach out. And again, as usual, if you've got any questions around this stuff, please, please reach out to us And we can talk to you directly about your firm's interest or whether you're a Software vendor that's interested in integrating.

So just on next slide, I might get Cam to help me out with this one. This is the new developer portal, we call it ACM. So our vendor MuleSoft to our API management vendor, they've upgraded us to a new developer portal. So this houses all of our technical documentation. There is some other features that we're keen to explore, things like forums, but this hosts basically all of the technical documentation that developers and potentially business people might want to read before integrating and doing some testing. So we haven't got a whole lot to show here today, but we have got users that have migrated across, and we've had some positive feedback. We've had feedback that sort of varies, I guess, and we're working with our vendor on improving that experience. But generally all of that documentation is there. There is communication type artifacts that we published there, news around the API space in the channels and that sort of thing.

So we're looking at maturing that now and moving all existing users across to ACM. The other big thing I guess is worth noting with ACM is it provides a self-service ability for external customers. So previously we do all the onboarding work in the API channel. We're now looking at exposing self-service to allow people to self-register and create their own client applications that talk to our APIs. So that's again, probably talk for the developer in terms of lingo, but that does give us a self service type feature which would be really good. So we might move on to the next slide. So the next slide, and again, Cam can probably talk to this as well in his role as delivery manager, but this is our very early dynamic e-services replacement roadmap for this next 12 months.

Cam:

Yeah. So as Josh said, we're coming into the next phase of build, which is to move on to that UX experience for the TDS program and to build a UI essentially on top of the APIs we've talked about. Initially where we're looking to run it very much the same way that we have delivered the APIs, and that is in a more agile lane approach by taking, I guess, small chunks of functionality on at a time. And I guess it's important to note that as customer is expecting a new experience wholesale or like a big bang type cut-over, it won't be the reality. We are looking to, de-risk it not only for ourselves, but for you guys as well to minimize any impacts you may have around change, or if you guys have, for example, people internally work, if you guys who would have to get used to a new system, we're looking to I guess chip away at the functionality.

If you have a look at the roadmap there, obviously we're kicking off with trademark renewal-

Josh:

Feature.

Cam:

Feature. And again, we're looking into build it out in a beta approach to make sure again that we're de-risking it for not only you guys, but ourselves that we don't make any bad assumptions. I guess the other thing that Josh probably will speak to is we want to make this really a customer centric build, to the point where we want to embed customers in our build process, and we want you guys involved. If you are an e-services user to be involved and guide us in delivering what we deliver as a replacement so that it's fit for purpose.

Josh:

What we will be doing as Cam mentioned there guys, is actually doing real customer testing. So instead of a lot of you guys might've been around for when we released e-services, we had a lot of assumptions as an agency of what our customers wanted in a web experience, in a transactional experience. We were quite wrong on a lot of that because we didn't validate those assumptions with the customer. So this build is all about putting the customer at the center of the design. So we're doing real testing as part of the design process. And we'll be doing, as Cam mentioned, a closed beta, open beta type testing before we release. So look, if you guys are keen on providing influence in this realm, I'd urge you to get in contact with us and become part of that, I guess, testing community that we're starting to build.

So there'll be more information on that sort of stuff that we send out in the next two weeks. And we're looking at starting a closed beta for our first release in the next two weeks, literally. So that first release is focused on trademark renewals. Yes, it's a fairly lean start, but it gives us the ability to, I guess, stand up our frameworks for release, sorry, going forward. One thing I wanted to sort of touch on was the fact that we are keen for... a segment that use e-services is quite broad. So we're looking at with that testing approach, we want to make sure we capture anyone from a cell filer, unrepresented filer, right up to a smaller top firm that use e-services regularly.

We do see the top 20 firms have significant scale being more suited to the API, the direct API integration space, the B2B space just based on what we can support in that web space, and then obviously the benefits of integrating directly to our APIs available. So we can talk more about that. And I think it's more fruitful to talk about that directly with customers who are interested in terms of what benefits could be available for your firm. As we know, firms have different business models, they use different case management software providers, so it can vary in terms of benefits and that sort of thing.

So please, if you're interested, reach out to us. That's I guess the main message of today's webinar. Now we've quickly got... we've just done up a, a new IPO video to help you guys, I guess, convey to your decision makers the benefits of direct integration in that B2B space, so again, probably forget about the webspace here, forget about e-services. This video is focused on the benefits and the context around that B2B channel for new customers or existing customers. So what we want to do here is I guess, make it... Again, humanize it so it's consumable and people understand what the API foundation actually is and what it means. So we might just play this. Cam, I might need your help here. We'll minimize down. Hopefully it's set up in another browser.

Video: https://youtu.be/IU5FeN39v3E

Voiceover in video:

IP Australia is now offering customers cutting edge, transactional APIs. Great. But what exactly are APIs? Have you ever ordered a pizza? Would you know APIs often act as the messenger between you and the pizza store? For example, a user is requesting information such as pizza menus, adding and removing toppings, and then sending payment through with their order. Just like ordering a pizza, IP Australia provides you rich IP data on demand, which allows you to transact with IP right databases at any time, fully integrate your systems, even develop your own software.

And our APIs are also really easy to consume. A skilled IT developer with API experience could integrate with some of our APIs in as little as one day. Integrating your case management system through our APIs conduced business productivity, saving on double handling and processing by having the systems work directly with each other.

Searching for trademarks or other IP rights can also be integrated through API, allowing searches directly from your own systems, even custom automated searches. APIs can also be used to automate processes such as correspondence management, searching, polling, and downloading directly into your systems. Our APIs can save your business money. Since making the switch one of our larger customers is already seeing savings of half a million dollars per year. Our APIs are like Lego blocks. You can use them to build your own websites and mobile apps from the ground up, allowing your customers to self-serve 24 seven through your custom designed interfaces. APIs are available now from IP Australia, contact us now about how we can help your business.

Josh:

Okay. So hopefully you guys could all hear and see that video. If not, we will send it around in the wrap-up email that goes out probably tomorrow, and we'll share that in that email, but hopefully it does provide some context about what it is we've developed and what is in production now. And it might help people go back to their partners and the exec type decision makers with, I guess, more context around what benefits are offered. So thanks to the comms guys for that.

Now we'll move on to the next part of today's webinar, which is again, a quick poll on how we're doing with engagement with you. So bear with me, I'll try to generate this poll and just launch it. And we'll give you a minute just to complete that for us, just so we can measure our engagement. You should be able to see that now on screen. Let's give you 20 more seconds there and we'll move on. Thanks for completing this. It does provide valuable feedback for us around our comms and engagement going forward. All right. Thank you all for that. We'll move on to the next slide.

So the next slide is just basically what's next. So I did talk about at the start of the webinar. Basically, we haven't got a proposed date as yet, but we probably want to align it with our trademark renewal release. So in that realm, we'll probably get out to you with an email shortly around the details of the closed and open beta approach that we're looking at commencing. So there'll be details around that on how to get involved in the closed beta to provide the influence around this design, and going forward, I guess, making sure we refine this webinar forum with the right... I guess the right audience type.

Now I know a lot of firms in here will be interested in the web space as well as the API space, B2B as well as e-services. So again, feel free to remain in the group. If you do want to unsubscribe, feel free to do so if you're purely interested in that B2B space. And again, the best method to, I guess, interact with us is directly. And we can talk to your developers and your business focused staff about how to get involved, but how to also become an active consumer, I guess, in the new channel.

So the last slide we've got today is Q and A. So again, if you've got any questions, please raise your hand or simply type it in as a text question and we'll get to as many of them as we can. I am mindful that I am well over time, so apologies.

We'll just give you guys 30 seconds and if there's no questions we can close it off for today. Doesn't look to be any questions. We might let you go as go. So apologies again for going slightly over time. We will get back to you guys with a wrap-up email of what we covered today, including that video for you guys to share. Feel free to share that around in your businesses, and we'll get back to you guys very shortly around the first release in that website. So in that experienced space, we'll be contacting people around how to get involved and the details around what that release actually looks like and the change that people will see. So you'll hear from us very shortly. Thank you for being a part of today and participating as always, we're really happy with this group and the influence it provides.

If you want to catch up with us directly, please, please reach out. I think the slide previous actually has our direct email address. That's probably the best way to get in contact with us. We've got a whole team that looks after that inbox. And like I said, we can arrange a video conference, a demonstration, a teleconference to discuss your interests and any issues you might have going forward. So again, thanks for today. Thanks for Cam and the girls alongside me for planning this session, and we'll see you guys soon.

 

Last updated: 
Friday, January 15, 2021