Carlton O'Neal: I'll start with introducing myself. I'm Carlton O'Neal. I'm a product manager at Ketryx. I've been with Ketryx for a few years in various roles. I think most heavily, prior to this, I was working on the implementation side.
I've worked with a lot of great customers, some of which are on our webinar here today. I worked in a variety of different use cases, different regulated processes across the SDLC and beyond, into eQMS flows and post-market surveillance activities. So I learned a lot through that, and it really helped me build on my experience. I was coming from Amgen, owning CAPAs, owning nonconformances, and really got into the QMS workflows. Now I've built on that with my time at Ketryx to learn more about the SDLC workflows, learn more about medical devices, and best practices across the industry rather than just within one company.
And, yeah, I'm here today to show you the new Google Drive integration with Ketryx. I'll start with giving you a very brief overview of what Ketryx is, how we think about things, and the inspiration for the Google Docs integration.
And then I'll show it to you in two key workflows. Like I said, for anyone who was here when I was rambling at the beginning, there are so many use cases that this very general feature now covers. But I'll show you the main two we set out to help folks with, and then I'm happy to take any questions if you have a particular use case you're interested in. I can definitely show you that as well. I'm happy to go off on some tangents for anything that someone is particularly interested in on this call.
And, of course, we have lots and lots of staff here at Ketryx. If you really want to dive deeper into this feature or any other feature you see here today, and see how it can bring your team value, help your team move faster, and help your team reduce the instances of inaccuracy in your process, you can always book some time with Ketryx, and we're happy to set up a demo that shows you how we'd approach your use case.
So I'll jump into this insulin delivery project here. I have a few projects: some managing hardware, some managing a system of systems, some managing, specifically, documents.
The projects here in Ketryx are very, very flexible. And you'll see in this project, I have a variety of different items. I have an SOP, a vulnerability impact assessment, and then items that are coming from the IEC 62304-compliant workflow: software items, test cases, requirements. All of my design controls are here on this change control board. These items are also coming from a variety of systems. At Ketryx, we want to allow you to interoperate across tools, to speed up your development cycle, and also to make the documentation that results from your development cycle more accurate.
We do not want folks to have to work in Git and do the documentation twice, once in Git and once in Word or Google Docs. The tool pulls in all these items from various systems. I have Git and Jira connected to this project and, of course, Google Docs. That's why we're all here. And this project is actually operating between those systems.
So we're running the entire life cycle, the entire process for our release, across Jira, GitHub, and Google Drive. And, of course, we connect with many, many systems and have supported customers across many different tools, particularly very large customers who have lots and lots of tools and teams that prefer one tool to another. Resolving any tension there is possible because you no longer have to pick. If the engineering team wants to primarily work in GitHub, Ketryx is able to support that and give the activity-level views so that their work, as they're doing it in GitHub, is reflected in the documentation, and other teams have visibility into it. Even if they aren't familiar with GitHub, they're able to see that here's a test case coming from GitHub. Same with Jira, ADO, Xray, TestRail, a lot of different tools.
And ultimately, what we're able to do with these items is enforce compliant workflows, such as reviews and approvals, and also enforce some rules in the system, such as traceability. And you can see here I have a traceability matrix that's pulling these items from all these different systems and showing me where I'm missing coverage with a click of a button, so that we have a real-time traceability matrix. Ketryx is always syncing with those external systems on the scale of seconds. So throughout our process that we need to complete to release, we're always able to see across Jira, Git, and Google Drive the status of the activities we need to complete to release. And then the best part is, once you finish these activities across these systems, the evidence is now within Ketryx, because we're syncing all the evidence onto these items, and you can work through a release.
And you can see we have a release dashboard here. This is the central place to look at the status of these activities. I have some milestones. I have the approval status for my items, a checklist, and even natural language telling me what I need to do next according to my process to release this version of my monolithic product here. Once you complete all those activities, of course, you're going to want to generate documents.
It's the common interface for compliance evidence. So it's, of course, what Ketryx will give you in the end. We can generate lots and lots of documents. You can see I have a very long list here spanning vulnerability management workflows, cyber risk workflows, and requirements management workflows. We won't have evidence spread across different systems.
Maybe our vulnerability report is living in a cybersecurity tool. Our system requirements specification is living somewhere else. Because Ketryx is connected everywhere, we're pulling it into a flat list, maybe your entire DHF. Maybe your entire DHF plus some other evidence you produce outside of that for certain certifications or as a part of your QMS. In this case, I'm even producing documents from those items for both the EU and the US.
So I can have a version of my system requirements specification that's for the EU. Maybe that one includes some GDPR-specific requirements, and then also one for the US. And this can break down into as many jurisdictions as you want. If you needed to go state by state, maybe for privacy laws, it's very easy to create these documents and then create these document variants.
What we're here to show today is the Google Drive integration. So the core use case here is that we're able to automatically generate these documents. But oftentimes, just pulling the requirements out of the requirements management tool to make the system requirements specification isn't all the information. You might want to work collaboratively with the team. Or even just to review, you can open it in Google Docs, chat with the team in the comments, and use all those collaboration features that we know and love. Maybe you have notifications set up for people mentioning you in comments or assigning you tasks in comments in Google Docs.
All of those features become available because, after we generate this document, we can post it into Google Drive. So you'll see I have the system requirements specification. You'll see I have a Google Drive section here, and I can view this document in Google Drive. And it has all this information coming from Jira and from GitHub. You can see this is a system requirement that's coming from Jira in this case.
And just like I said, all the normal Google Docs features that we know and love are available. Even Gemini, which I think is a very interesting part of this. How can you integrate AI into your review workflow, maybe even just to search for a particular requirement very quickly? Of course, if it's in Google Docs, then you get access to Gemini built in with the "Help me write" feature and also with the Ask Gemini sidebar.
So how does this work in the first place? Well, all you have to do is pick any document that's generated and click "Create in G Drive." In this case, it was a test plan. Ketryx says, okay, I'm working on it. I'm uploading it to G Drive.
Ketryx will put it in a project- and version-specific folder within a specified location in G Drive, so it's nicely organized. In this case, it's going to go into a "Monolithic System version 1.1.1.0.1" folder. And, of course, it's going to have the name "Test Plan." And you can see it's a matter of seconds until it creates it in Docs. And now this generated test plan, containing maybe test cases from Xray or TestRail or both, or Jira and GitHub, all comes together into a Google Doc that, again, I can edit as if it's a Google Doc.
And whenever I'm satisfied with the result of what this document looks like, I can always come back to Ketryx and load in changes. And this goes both ways. So I can tell Ketryx to ingest what is now in Google Docs, maybe after we made some suggestions, went through commenting, and accepted those suggestions. And I can also say, hey, whatever is in Ketryx now, maybe I generated a new version of the test plan because I've edited what's in the test plan, let's apply those changes to the Google Doc where we were working.
Okay. So that's use case one. First and foremost, we're automatically generating this document, which is already a huge efficiency gain, and we're bringing value to your SDLC by reducing the amount of duplicate documentation you're doing, pulling information directly from the source systems and generating the artifacts you need to release. And now, on top of that, we're allowing you to post the document into Google Docs, work with your team there, and use all the features you're familiar with.
You probably will never have to train someone on how to use Google Docs, and your compliance artifacts are updated and syncing back into the system of record where you have the approval.
The second case that I'll go over is for documents that are not generated from items coming from a system. You're going to have a lot of these documents. In this case, I'm going to focus on eQMS documents: plans, policies, procedures. But, of course, you could have maybe an installation form that's filled out by hand by a service provider and then uploaded, or maybe a certification coming from a notified body that you need to upload. In this case, I'll just focus on QMS documents, and you'll see I have plans, policies, and procedures.
We'll focus on the procedures today. You can see that these documents have a status, and Ketryx has a type for them as well. And if I click into one of them, you'll see Ketryx is providing a preview of the document. This is one of our draft or example SOPs. It's a pretty standard good documentation practices document.
Of course, we have the full history of this document and the ability to approve and assign approval to particular people. But this document is actually living in Google Drive. This is not some document that we've uploaded to Ketryx as a single copy. It's actually connected in real time to a Google Doc. And, again, just like before with the documents we were generating from items in the connected systems, you can use all of the Google Docs features that you're familiar with.
In this case, I'll just make a small change here. I'll say this SOP applies to all manufacturing sites. And, of course, again, I can comment. I can maybe tag my coworker, Kevin, and say, can you verify that this is true? Maybe he comes in and suggests, with the suggestion feature, "Oh, no, I think this is not including our Puerto Rico facility." Whatever teammates need to get involved can use the normal collaboration features.
Of course, again, you don't need to train anyone on Google Docs. We're now editing this SOP directly in Google Docs. And the real value Ketryx is bringing here is that we don't have to set up some approval workflow or review workflow that's completely separate from Google Docs. I know from my time previously, I had a lot of trouble downloading a DOCX record from Google Docs, uploading that to an eQMS system, and then the formatting going crazy, the document looking nothing like what it looked like when I was working on it in Google Docs, because of that transfer step.
And, of course, that transfer step also just takes time. Every single time I wanted to upload a new draft to the system of record so that I could go through review and approval, I was manually downloading and manually uploading. Because Ketryx is pulling this directly from Google Drive, at any time I want, I can click this sync button, and Ketryx asks me to confirm that I would like to update this document with what is currently in the source system, Google Drive in this case. And it says this will create a new draft revision of this document in Ketryx. So instead of downloading from Google Docs, where we were editing because it's probably the best place to collaboratively edit, having it locally on my machine, and re-uploading to the eQMS, Ketryx says, okay, I'm just going to pull in whatever is there now.
Are you, the team who can all see the document and who have all commented, satisfied with what is there? Of course, there are no comments on this one, so that's probably a good sign. Maybe we've gone through commenting and assigning, and we've resolved all those comments. We're all happy with it. And all I need to do is click sync, click yes, and Ketryx is going to update this document.
And you'll see we got a new record in the history here from today, just a few seconds ago when I pressed that sync button, and the document is updated. Great. So there are lots of things you can do here with different types of documents. That's just a high level.
I will say, to take this one step further, Ketryx is an ecosystem that connects and pulls information from different tools. It also allows you to interoperate across those tools. And I'll highlight a Jira and Google Drive connected workflow that's enabled by Ketryx in this document management project. So I have another Ketryx project. It has completely different item types. Again, a project is not opinionated about what it's helping you do, other than allowing you to review and approve items, maintain traceability, fulfill all of your activities, and automatically generate evidence.
But it could be for any process, really. And we have customers that use Ketryx for many, many processes. I think probably 20 or 25 unique processes at this point. In this case, I'm managing a change order workflow in my eQMS system. So you can see I have Google Drive connected, and I also have Jira connected.
So my change orders are living in Jira. It could be ADO, could be Jira, could be another system; whatever tool you want to use as the project management tool. We like Jira. We use Kanban boards and sprints and all those great features. And so I picked Jira in this case.
And those are the ticket items, the change orders, the point-in-time things I need to assign to somebody and put a due date on to drive work forward. And I'm actually able to take these items and connect them to the Google Drive documents. So the team can get assigned tickets in Jira and know, oh, I need to update this Google Drive document. And we also have the compliance traceability. Why did you update this Google Drive document?
And then, of course, I pull the new version and approve that in Ketryx. Well, if I look at my traceability, it was because QMS-33, which was a change order, was assigned to Carlton on some day. We can put some rationale in that ticket, and it was executed. And that's why we updated the document. Great.
We have a question here. I'll take that right now, because I think we're on the perfect screen to talk about it. It's, "What's the difference in setup for these features?" And I think this could be asking one of two questions. I'll just answer both really quickly.
The first question it could be is about Google Drive for the documents that are not being generated from external information, in my case QMS documents, plans, policies, procedures, versus the release documents where I'm generating some information and posting it to Google Drive. The setup is very, very similar. Ketryx has a concept of what is a document that's being generated versus a document that you are not generating from the information. And there are just two different settings. One says, would you like to make a Google Drive connection for the documents you're generating? You can say yes, and please put them in this location.
And then the second setting is, would you like Ketryx to look in a particular Google Drive folder to pull in documents that you already have, like plans, policies, procedures? And you can say, yes, please look at this location, and Ketryx will bring in the folders, all the folder structure, and all the documents that are in there.
And then I think maybe the second question was about how I said 20 or 25 unique processes in Ketryx are already supported across our customer base today. The setup for that is also very easy. It really just comes down to which item types you have in here, which views you have in here, what your approval workflows are, and what activities you need to complete and automatically generate evidence for as a part of whatever that process is. And like I said, we have a huge team of people who think about processes and enabling processes with efficient automated workflows, who are more than happy to show you all the different things you can do within Ketryx with that flexibility.
Wow. Another question that is perfect for the screen. The question is, "Can Ketryx AI create change requests or orders for us automatically?"
Absolutely, it can. Just like with all the other items in the system, you have Ketryx AI, the assistant here on the side, always available to help you work on or search for items. You can see we have a lot of suggested actions here where you can search for particular things. But you can absolutely use this to help you create change orders if it's hard to put into words what you want to do, or you have some context, maybe a new FDA guidance, and you just want to put that FDA guidance here and say, hey, look through all of my plans, policies, and procedures and suggest what might need to be changed by creating a change order.
Ketryx can automatically create a change order and post that to Jira or whichever system you're using to manage those change orders, or maybe you're managing them entirely within Ketryx, and say, we should update SOP-1 in this way: these sentences, this section, this diagram, based on the guidance, because it's clear now that this SOP is no longer in alignment with this guidance. That can, of course, really speed up those workflows.
Okay. So let's jump into Jira and have a look at one of these items, and I'll show you what I mean by this interoperability between Jira and Google Drive in this case. So this is just a normal Jira ticket. Again, it could be ADO.
It could be another system, wherever you like to do your project management. You can see I have a description of the change, a reason for the change, and an impact analysis. And, again, Ketryx AI can definitely help me write this if I have all the context I need, or if I just want to idea-vomit at it and have it structure a very succinct description of what we need to do here. And then you'll see Ketryx is also providing approvals for this change order. In this case, my rule is just that the owner needs to approve, and Ketryx is also providing traceability.
And this is really the key part of that interoperability. I have this change order here, and it is related to a particular SOP. Ketryx AI can also help suggest relations if you have a very large change order that lists a lot of documents, or maybe you're not even clear which documents should be there. If you click this button, you'll have the ability to have AI help you make the relation. And, of course, if you already know the relation, it's easy enough to find it in the list.
And, of course, you can search here as well. Once you make that connection, this item appears here in the traceability widget. The key thing here is that this is real-time traceability that Ketryx is maintaining. It's maintaining it according to certain rules. I can't add a related policy and then add, I don't know, an installation or servicing record or something.
It's only going to let me add policies. It's only going to suggest policies to me. And this real-time traceability gives me the ability to jump over into the connected system. So I'm in Jira. I've been assigned this ticket.
Maybe I've been given a due date. Maybe it has some priority, and all those normal Jira features: time tracking, Kanban boards. And making this connection makes it very easy for me to work on this item. It says, "Update SOP-001 to align with new electronic record retention requirements." Well, where is SOP-001?
Ah, it's right here. I can jump over there, read through it, make my changes, and even use Gemini to help me. I can use Gemini to reference the change order I've been assigned. Maybe it focuses me on a certain section. And then once I'm done, I can move this to resolved.
I just go through my normal Jira workflow, whatever workflow works best for your team. And then, of course, I can approve it and move it to finished.
And just to highlight this idea of using best-in-class project management tools to manage the change orders, or whatever tickets you need to relate to documents, I set up this Kanban board, which has all of my change orders. I have an expedite swim lane with the highest-priority ones and then everything else below. I'm a one-person army here in this project.
You can see my face is on every single change order. But, of course, with Jira, you can have teams and maybe swim lanes by team, or epics that sort work into different groups. And ultimately, this is not just some random Jira project sitting off to the side that's disconnected from my development workflows, disconnected from my eQMS or wherever my documents are living. I'm able to work in Jira, which is a great tool for project management, and I'm able to connect these Jira items to Google Drive and Google Docs, which is, at least in my opinion, the greatest tool on earth for collaborative document editing.
So instead of saying, hey, come into the system, we have project management and we have document editing, we say, use Jira for project management. It's phenomenal at that. Use Google Drive for collaborative editing.
It's phenomenal at that. Ketryx will allow you to interoperate between those systems, automatically generate evidence, automatically enforce rules, and ultimately prove compliance in those workflows without having to sacrifice the tooling the team is using.
Okay. I think that really covers it. Again, this feature has just ballooned into so many use cases.
I showed you two today, but we've already implemented a lot with different clients. So I'm happy to take any questions on specific types of use cases that folks are interested in after seeing this feature. And like I said, if you'd like to dive in with a solution expert on the Ketryx side to talk about your use case, we have lots and lots of people who think about process efficiency, automation, and using best-in-class tools in an interoperable way to drive processes forward and make them more accurate.
Kevin, great question. That is where we're going. At the moment, you have to navigate back to Ketryx to... let me say the question so I'm not just talking and everyone's in context. The question is, "If I'm editing in Google Docs, is there any way from there to sync into Ketryx without going back into Ketryx?"
The answer at the moment is no, but that's certainly the direction we're headed. We actually already have a Chrome plugin that allows you to work interoperably with Ketryx in some of our other connected systems, so that you can open a side panel that has Ketryx information. That's the direction we would go with this integration as well.
As we build more and more on it, as we have with our other integrations, you'll be able to open Ketryx without leaving Google Docs and then click "sync this information back."
Oh, another question from Kevin: a risk management matrix, and how you link this to a requirements matrix. Great question. I will show you at a high level.
This traceability matrix goes from requirements down to specifications and then up the other side of the V for testing. This is actually completely arbitrary. I have five columns here. I could have ten. This column has requirements that are not of type use case.
It could have requirements that are specifically of type system, or whatever I would like. It's just a filter. And you can see in here, I actually have a ton of different views. Within Ketryx, you're able to see these real-time traceability views. For the risk management matrix and how you link it to a requirements matrix, I would definitely set up one of these views so that, wherever those risks and requirements are living, we always have these checks to make sure that we're covering everything.
Actually, that one doesn't have enough info. But this will drive our process forward. Whatever rules we have for requirement-to-risk traceability, we can enforce here. And then, ultimately, when you're generating the documents in Ketryx, because this activity is complete, you know that the documentation automatically generated from those requirements and risks, including their relationships to one another, whether you want that in a document or in an Excel sheet, is correct, accurate, and complete according to whatever process you set up by configuring a screen like this. And, again, I don't have a requirements-to-risk one here, but you can see, like I said, tons of processes are managed in Ketryx.
I think the easiest way to show it is with this traceability matrix drop-down. That's primarily how we see people driving different processes forward: by adding all of these activities as a configuration here. Again, it's quite easy to add as many columns as you want, and as many filters as you want on particular columns and how they cover each other.
Okay. Well, thank you, everyone, for attending. If you have more questions, I think Joe has put a lot of information in the chat, including how to get in contact with us if you want to dive deep on one of your specific use cases related to any of the features you saw today, not just the Google Docs integration.
And then, of course, we do a lot of these webinars on various topics, and you can get some information about some upcoming webinars that should be quite exciting in the chat as well.