Descripción
Aprendizajes clave
- Discover what the Autodesk Platform Services team is working on for the future.
- Learn about new Autodesk Platform Services APIs.
- Learn about the Autodesk Platform Services platform strategy.
Oradores
- TGTulika GargTulika Garg Director, Product Management, Developer Enablement Tulika is the Director of Products at PSET, bringing a wealth of expertise in product management, business strategy, software development and scaling platform businesses. In her current role at Autodesk, she spearheads product management focused on Developer Productivity and the Developer Ecosystem. Throughout her career, Tulika has demonstrated innovation, having filed several patents. She holds a major in Physics, a master's degree in Computer Science, and an MBA in Strategy from the Wharton School. Beyond her professional accomplishments, Tulika is deeply committed to community. She balances her career with roles as a mother, volunteer, and board member for non-profits. A dedicated mentor, she is a passionate advocate for the advancement of women, focusing on their growth, health, and empowerment.
TALIKA GARG: Hello, everyone. I'm Talika Garg, Director of Products for Developer Enablement at Autodesk. My team leads the strategy and roadmap for Autodesk Platform Services. And I'm here joined by my colleague Emile Kfouri. And I'll let Emile introduce himself.
EMILE KFOURI: Hello, folks. My name is Emile Kfouri. I'm the Senior Director of the Developer Ecosystem. The team that I lead is responsible for making companies successful on the Autodesk platform. That includes developer advocacy and support, dev portal, et cetera. And we're really looking forward to sharing with you the roadmaps for all of the APIs from Autodesk.
TALIKA GARG: Thank you, Emile. So like Emile mentioned, we are here to talk to you about Autodesk Platform Services Roadmap. Let us take a look at what all we will be covering.
So by now, many of you are probably already aware what Autodesk Platform Services stand for. But we'll start with a quick overview. What does APS mean? What does it include? And that will be a quick overview, and then we'll jump straight into the roadmap. And that is the part I know you all are excited about.
We'll talk about the roadmap of our developer portal, SDKs, AppStore, and the entire list you see here on the screen of all these APIs, where some of them are existing APIs, and the new ones also that we are introducing.
I'll take you through the developer portal, SDK, AppStore, Viewer, Data APIs, and Flow APIs. And then I'll hand it over to Emile to take you through the roadmap of ACC & Forma, Vault Cloud APIs, Tandem APIs, and Autodesk Developer Network. And at the end, we'll close out by sharing some resources with you on how you can start using these APIs for your applications.
So by now, this is known that Autodesk has created this Autodesk platform to connect your design and made data and help you all achieve your digital transformation goals faster. The base of this platform, or for these platform services, consists of a collection of cloud-based APIs that serve as the foundation of these three industry clouds-- Fusion, Forma, Flow-- and the Autodesk data model.
The APS is not only the core of the Autodesk platform, but it is also exposed as an external platform, which is trusted and used by thousands of our customers and partners to build their solutions.
By giving you access to the same APIs and services that we are building our entire design and platform on, we are giving you the key to manage, organize, and connect your enterprise data with data from our platform-- Autodesk products and third-party solutions.
With easy access to your data, you can build custom cloud-powered workflows that automate processes, connect applications, and integrate with enterprise systems. We support over 70 file formats. You can rest assured, we are committed to supporting bidirectional interoperability and open-industry workflows.
We are constantly evolving APIs. And these can be grouped in, largely, three sets of capabilities. The core capabilities that can be used agnostic to industry, this includes viewer, model derivative, design automation, authentication, which you can use to build custom, standalone solutions like dashboards and digital twins.
Then the second category is data capabilities, such as data exchange and data model APIs, that let you connect and integrate and surface your design and made data with customized data connectors.
And then the third category is the product APIs and capabilities that let you extend Autodesk product portfolio by connecting them to things like your enterprise system or as well as run Autodesk hero products in the cloud. The APIs are flexible, so can be leveraged by developers of all skill levels, in whatever program languaging they prefer.
And before we dig into where we are going next, I want to share some of the numbers which demonstrate the scale and maturity of this platform. We have had a very exciting year, where we've seen tremendous growth in Autodesk Platform Services. Today, we have over 4,000 applications in our AppStore, and we continue to see over 100,000 monthly downloads, unique downloads by users.
In the last fiscal year itself, we saw over 9 billion API calls that were made to Autodesk Platform Services. And we continue to enable the developer population on APS to make use of all these APIs that we are introducing.
Last year alone, itself, we enabled 7,000 developers on APS. We have generated a number of APIs, including AEC manufacturing data model. And we are starting to realize our third industry cloud, Flow, completing our Forma, Fusion, and Flow vision.
Now, as we talk about the APIs, what are the design principles or overarching principles that we look at as we are improving these APIs?
So our goal is to provide you more high-quality and high-value APIs in those three categories that I talked about earlier, whether it's the core APIs, data APIs, or product APIs, but also do that in a manner that these APIs are more discoverable, consistent, and modern.
And we do this with the lens of keeping an eye on the entire developer journey. As the developers go through this process of finding these new APIs, or discovering the APIs, and creating the applications on these APIs, and then start distributing them, whether it's through-- whether it's through AppStore or internal consumption.
When we have APIs which are easy to discover and the API interfaces which are consistent across our API portfolio, it allows you all to leverage the understanding and knowledge and expertise you've built on APS to create more applications with the newer APIs which are being introduced.
And the modern app experiences, such as support for webhooks, allow you to build faster and more performant applications with these APIs. So these are the three principles which continue to drive how we are evolving this API portfolio.
So let us take a quick look at, first, on what we are doing in the developer experience space. Now, you all are already familiar with probably the developer portal, where you start this discovery and application creation journey. And we have been making a lot of investment in those experiences for you.
What is already available to you now is that we have started-- we have made-- we introduced the in-product application discovery directly from our applications published in AppStore last year. And I'm very excited to announce that that experience is now available for Forma publishers today.
So if you are creating a Forma application, using Forma APIs, and you are publishing that application in AppStore, your customers, or the Forma users who are working in the Forma interface, would be able to use those-- would be able to discover those applications within the Forma interface. And thereby, it expands the reach of your applications.
We are also working on improving the experience you have in managing the application keys. So as you go about creating new application keys, or even managing your existing keys, currently, all of those experiences live in the developer portal and require human interaction. We are now planning to provide APIs, which will allow you to automate some of those experiences. And these APIs are already available in beta.
The goal behind automating some of these workflows, like rotating the client secret and retrieving the token usage data for your keys, would allow you to manage your applications better, especially as you expand your application portfolio. And as you use more APIs in creating multiple applications, these APIs will make it much more smoother and reduce the human intervention in managing those applications.
In addition to that, we are also working on expanding the capabilities for Forma customers, specifically if you are a third-party provider building standalone applications for Forma. So in addition to those applications being discoverable within Forma interface, we are looking at enabling direct purchase from Forma.
So if a user is now able to discover your application from within Forma interface, they'll also be-- and if they like that application and want to make purchase, they'll be able to directly initiate that purchase process from within Forma.
And then next in the pipeline, some of the things that we are looking at is how do we continue to improve the discovery and the enablement around all these new APIs and capabilities we are launching, by providing better resources and documentation on the developer portal and providing a better search experience. And also, how you continue to manage the permissions around these applications in the admin interface in developer portal. So these are some of the areas we are doing active discovery in and making investment in.
And then moving on to talking about SDKs. So we have made a lot of investment in providing the high-quality SDKs for some of our top-used APIs this year. And again, this is all in line with making it a faster and easier experience for you to start using these APIs and start creating applications which add value for your customers.
So we already have a model derivative OSS and authentication SDKs available. And we are looking at adding more SDKs, which are actually now already available in beta also. So you can sign up for the beta program and start trying those out.
So you can see the list on the screen. And I'm not going to read it out to you. But you can see, again, our goal is to target-- provide these SDKs for some of those most-used APIs, like data management, authentication, model derivative, and provide them in the languages that are most commonly used, like .Net and typeScript.
And later in the pipeline, we'll also be working at improving how the developer support requests are managed. So we currently provide a Zendesk-based experience, where you can raise support requests if you have an aiding program. And we are providing-- we are working towards how to make that experience more streamlined and provide, manage, and support requests in one place. And also we'll continue to invest in the code samples.
So SDKs are a great way for a starter kit, but you're still bringing in a lot of code yourself, which is use-case dependent. But we have a number of code samples that are currently available, depending on different use cases. And we'll be looking at enhancing that and making that more readily available to you so you can-- again, with that goal of that you can start developing with the APS faster.
And before I move on to the next section, I want to call out a few sessions for you if this area is of interest to you-- SDKs, AppStore, developer portal experiences. We have a session which goes deep into the developer portal and developer experiences this Thursday, and it's called, "Better Visibility For Better Outcomes with Autodesk Platform Services." The session is at 10:30 AM.
So our developer portal, AppStore, and SDK roadmaps that I just gave you a very high-level overview about, and I mentioned that we'll have a deep-dive session later on Thursday, but they're also available publicly now on Autodesk Platform Services. And our public roadmaps are great for visibility, but they're also great for interactivity.
So what I would encourage you to do is scan this QR code and access this public roadmap link. You can not only see the roadmaps, but you can upload the items that are of interest to you. So I would encourage you to just quickly scan the QR code.
And with that, I'll take us to the next section, which is APS Viewer.
Now, APS Viewer is at the heart of 80% of APS use cases today. And we are making a lot of investment in this area. We have already released a number of enhancements. Most of those are based on the feedback from you all, specifically around improving the performance of Viewer when it comes to the load time.
So we have made significant improvements there that we have reduced loading time, and we've done that via introducing streaming improvements. We've also added improved caching, and we have introduced smooth navigation. It's currently in beta. And we are also looking at GPU memory management for crash-resistance to make Viewer more resilient. And again, that's a capability which is available in beta now.
Going forward, a couple of things that we'll be working on is we are looking at optimizing the loading of the property data for large models. And right now, while the memory management for crash-resistance is available in beta, we'll also be looking at CPU memory management for crash-resistance. And we'll also be looking to provide a future-proof graphics support by introducing WebGPU.
Couple of other things which are on horizon and are in discovery stage and would be coming later in the pipeline is how we can provide better measurements and faster loading through server-side optimization. Point cloud viewing is another area I know which is of interest to many of you, and we keep getting that asked. And it is an area of interest for us, and we will be exploring that.
Enhancing the PDF quality and improving model aggregation. And I know this is an ask many of you have made over time to provide the full model experience by allowing multiple model aggregation in Viewer is an area that we'll be making investment in. Selective loading and viewing via spatial queries and incremental translation-based design changes are some more areas which are currently in discovery stages.
Next, I will take us through a very high-level overview of the data APIs. We have multiple sessions on each aspect of the data APIs, ranging from the specific data models for AEC data model, manufacturing data model, to also the improvements that are coming in the data exchange and the specific data connectors we'll be launching.
So I'll just take us through, give you a very high-level overview. But we're happy to take questions on any specific aspect of data APIs you have.
So as you are probably already aware of that, for the data APIs, we have three high-level pillars-- data granularity, data interoperability, and data accessibility. On data granularity side, AEC data model is now GA. And we have also added an ability to write back data into Fusion ecosystem via extensibility APIs.
And we are planning to add this capability also on the AEC data model side. But on the manufacturing data model side, a number of our partners are already using this capability of write back to create some really interesting workflows to have sustainability data or the EIP data available back in the design phase.
On interoperability, we have connected various Autodesk and third-party applications. We have a Power BI connector, which is in GA. We are providing ACC bridge integration. And the SDK now has advanced feature that will allow you to build custom connectors for your own custom workflows.
And as I mentioned earlier in the presentation, we are committed to providing interoperability. So you can see, we have a number of connectors that we have already pre-created, like Rhino 8 and Tekla 2023.
And then coming soon, some of the things we are very excited about-- we will be adding more data across additional products, advanced native geometry features across Data Exchange connectors, and extensibility APIs to help you connect your entire data ecosystem.
And very much like the Developer Portal SDK and AppStore roadmaps, all our Data API roadmaps are public. They provide the same interactivity features. So you can scan these QR codes to access these public roadmaps and also upload the features that you are most interested in.
Now, I'll take you through some of the APIs that we have for our third industry cloud, the Flow. And we are very excited to finally be able to talk about our API ecosystem for the third industry cloud.
On those side, the first one I want to talk about is the Flow Graph Engine API, which is in public beta now. Now, the goal of this API is that it provides you capability to offload heavy compute to the cloud. And you'll be able to execute things like Bifrost graphs in the cloud via RESTful APIs.
And why this is super important is these are some really GPU-intensive loads, and resource-intensive, and need special machines. And usually when customers were running these loads on their local environment, they would have expensive hardware tied up running those workflows.
But with these APIs now available, you can create applications that can offload that processing and those workflows to cloud, freeing up the local resources. And this is where we are looking at-- we are launching wedging, which will allow exploring various parallel design options, and again, a highly resource-intensive workflow. But now you won't need to run it on your local machine, and you can offload to that via Flow Graph Engine API and a cloud site.
This is a premium API, which will-- and since it's so resource and compute-intensive, that will be a paid API, and the pricing being determined. But it is available in public. So you can think of it similar in terms of design automation, which allows you to access-- automate Revit or Inventor in cloud, so similar to that. Pricing is yet to be determined and shared, but the API is available for you in beta to try it out.
And then on the Flow side, I also want to talk a little bit about the Flow data model. We already discussed a little bit about the AEC model and the Fusion Data model in the data APIs section. But I wanted to call out the Flow data model separately because, like I said, this is the first time we are launching it.
The first goal of the Flow data model is to assist in asset management. This will connect tools, artists, department studios together across the entire production pipeline. So essentially, think of having a single source of truth and granular access to your data from the studio all the way to the production flow.
And this out-of-box experience will act as an orchestration mechanism also for open standards. So we will be embracing open standards and contribute and extend open standards, but we'll also provide much flexibility to interact with your own data pipelines you may already have in place.
The underlying data instance is bringing the complex Autodesk data strategy to the M&E industry. And this aligns with our overarching industry data model strategy that we have across AEC data models, manufacturing data models, and Data Exchange.
And we will continue to employ the API First principle here, similar to what we've done for AEC and the manufacturing data model. That our tools and product features, which are used to making these cloud-connected data pipelines, will be available to you via APIs. And you will be able to automate and orchestrate your own standards, while we'll also be using these data model capabilities to provide out-of-the-box VFX industry standards.
And GraphQL will be the interface similar to the AEC and the Fusion data model here for the Flow data model as well, which will allow you easy access to your data in a granular fashion.
We are also planning a Python SDK to support our many pipeline developers who are out there to align with their desktop product programming environments.
With this, I'd like to hand it over to my colleague, Emile, to take you through the rest of the APIs and then close us out with sharing some of the resources, which can help you get started. Over to you, Emile.
EMILE KFOURI: Thank you very much, Tulika. So let's talk a little bit about AEC next and share with you what we're doing over here.
Early this year, submittals read API was officially released. More recently, write API was released. One of our long-overdue features, getting file descriptions, was finally made available as well.
You probably heard by now, ACC now supports storing data in Australia region. With this regionalization effort, all AC-specific API endpoints support automatic region routing. We've also made available Sheets export PDF, Cost API to add links between budget contracts, and Parameters API to set collections.
AEC data model, read API, was also released in June. This is probably the biggest news for the next generation of data access, allowing granular data access.
There are quite a few items that are in the pipeline for AEC side as well. There is a class about AEC API updates later today. I will leave the details to that class, but to just name a few, we're going to be talking about submittals API, attachments, markups, et cetera.
The Cost team continues to release APIs, such as batch creation of cost items, get taxes, and cost submits. AEC Data Model custom properties read and write API is expected to go private beta at AU.
Another very important item being worked on is about secure service accounts. Our customers and account owners have been asking for a while to control the access by third-party applications in more secure and granular ways. We hope to finally provide a solution to this problem.
For more details, check out Mikako's class on Tuesday at 3:00 PM. The class is SD 1414, titled, "Autodesk Construction Cloud API Update and Beyond."
Building Connected team continues to produce APIs as well. Early in the year, the team released a large set of write APIs, 47 endpoints to be exact, together with TradeTapp read API. Following that, the team continues to release enhanced APIs, including webhooks. Next in the pipeline is TradeTapp write APIs.
Now moving on to Forma. Since launching Autodesk Forma, the team has focused on widening the read and write APIs for in-market offering, focused on early stage design. Now, these APIs are available through SDK and HTTP APIs as beta, and you should definitely check them out.
We're especially excited about growing the ecosystem of partners and publishers. We're enabling in-product API store experience, and Forma will be the first product to launch these experiences. This will streamline processes, such as payment within Forma interface, rather than having to go outside of the product. To learn more, join the Forma session by Christoph at 4:00 PM today.
Now moving on to the Vault Cloud API. We're making a subset of your Inventor and AutoCAD data accessible through APS. It allows you to isolate the data you create-- you care about via the workflow and tools of your choice. These enable greater access for downstream stakeholders. The benefits include empowering better decisions with data accessibility, reducing development effort within intuitive APIs, and creating automations to improve collaboration.
Now let's talk a little about Tandem, Autodesk's digital twin solution. Tandem now has Tandem Connect, which is in beta. It is a new low-code node graph editing system. If you are looking to connect your facilities with Tandem, it got easier than ever with Tandem Connect.
Tandem Connect has an easy node-based graph editor and library of templates, which will allow you to build your integrations much faster than you could do in the past, by directly integrating with the APIs. While Tandem Connect is an easy, low-code system, if you want to do advanced integrations, you can directly use Tandem's API as well. You can integrate complex systems and data, and even embed Tandem within SharePoint or a Power BI report.
Our long-term vision is to enable a marketplace of digital twin integrations and data analytics, as we continue to help democratize digital twin solutions. If you want to learn more, we have two breakout sessions by James and Michael, one today at 4:00 PM, and the other tomorrow at 4:00 PM. And don't forget to bring your iPhone for an interactive demo.
Now moving on to the Autodesk Developer Network program. ADN members have already been enjoying great benefits for many years. These include event discounts, premium support, and license access for Autodesk desktop software and marketing support.
What we're doing moving forward, starting with the membership renewal for next year, we're aligning our cloud solutions with our desktop solutions for our ADN offering. You'll be able to access SaaS products, with the same ease that you can get desktop products today.
We also plan to provide members with a nominal number of free tokens based on the number of ADM licenses you have. This will help you try out APS, without worrying about the cost of using APS to do prototyping.
ADN members will be able to continue to get premium support for APS and more discounts to events. Later on, we are working on making it easier to also get preview access to SaaS products so you can prepare for new releases. And we're working on consolidating our end user license agreements for all the products that you access through your ADN membership.
We want to keep you in the know with our developer newsletter, with information about product announcements, providing sample codes, and keeping you up to date on events. Please scan this QR code and join the newsletter to make sure you're always up to date on the latest news about APS.
We have many events, every year, to help you learn about APS and build your products faster and better. These are the next two events that we have-- APS online training, November 18 through the 21st, and the Developer Accelerator in Atlanta, December 9 through the 13th. I hope to see you all at one or both of these events.
Last but not least, we really would like to encourage you to complete the session survey and tell us what you think of this session. Tell us what you liked, what you didn't like, and how we can make it better. You can access that through the SharePoint-- though-- sorry-- the AU app.
And then, of course, we'd love to see you at the APS booth at the expo. The booth is number 8.2, and it's called the Autodesk Platform Services Zone.
With that, I thank you all very much for your time and your interest. We look forward to hearing from you. And please remember to go to the roadmaps, and check those out, and provide us with your feedback.
Thank you and goodbye.
Downloads
Etiquetas
Producto | |
Sectores | |
Temas |