 Great, so I'll begin so today I will touch base on the version ID. I didn't see feedback for most of you and I thank you for that in advance. So. I'll discuss on that and then I'll hand it over to Brian and you'll discuss some more terminal out terminology walk through the activity feed and to do list. Feed as well, so this presentation will probably be the shortest we had. So, there'll be plenty of time for Q, and so. Based on your feedback decided during the beta, we would test using the test report. My team believes that this. The test report ID with combination of the product ID should maintain uniqueness. Since products with the same product ID that may be manufactured a different location should not be on the same test report. That's. So, that's what I learned from the last meeting and. And when I ask that question in the follow up email, many of you. State of the, you prefer to use a test report ID. I also hope that this will make things easier for end to keep track of the certificates. And for clarification, when component parts certificates are used, the test report ID can be used as a version ID for multiple certificates that doesn't negate the uniqueness factor. It's the 2 different product ideas using the 2 are the same test report ID would still have. Will still be unique and lastly, for certificates with multiple labs, I would suggest let's 1st the lab with the most citations and then you set test report. However, so this test report ID is not actually required for the citations or the CFR. So, we'll make this option, which also means that we create a system generated ID that you could use instead. I think our developers will default to the test report ID. And if you agree to that as well, we would. You wouldn't have to provide a version ID. You just use your test report ID from your certificate for the version number and then. Unless you specify and then we'll override that system generated ID, we haven't really decided on like, how many digits that will be. But we'll update you on that in the future. And so, I'll open it up right now for any questions, but we could hold off to the end after Brian. Okay, and once we develop some of the documentation, we'll clarify maybe a few more things around this from the person, I do how to use the combination certified product ID and test report ID together. So, we'll get that would be all prepared in a package later on once we get to the stage of onboarding all of you to test the system. And so, today, I'll be discussing activity even to do this under this is telechance. So, just a little bit of preamble the the screens and the flows that we're about to discuss these arose out of the need to have some sort of notification. Based system with any filing, there's a lot of different individuals who are doing a lot of different things within the system. And there needs to be some level of visibility and activities taken on a product collections to get updates, things like that. So, initially, when we began developing, we were thinking of just a standard user inbox with all the notifications and all the things that have happened on product collection. With red and unread statuses, they have the badges notice that there's a whole bunch of things you look through them and you clear those notifications. And we ended up moving away from that, because we wanted to make sure all of the updates happening within a product collection were accessible to us, but we didn't want to require visibility on them to clear badges and deal with red and unread notifications. So, we came up with the concepts of detail here that we're going to go into today, the first being the activity feed, which. Internet parlance could also be referred to as a timeline of sorts, but it's a reverse chronological list of recent actions taken product one. So, when you've updated certificates, when you've added new certificates, the test data, when a certificate been tested to these are all the sorts of things that are going to show up in that. So, scroll back very far. We haven't come up with the specific details. If it will endlessly go back to the beginning of time, or if there will be a limit to it, that's the basic function of it. Similarly, the to do list. This is either actions that do require you to do something to complete something. So, if, you know, within a given company's workflow, someone needs to provide at the station. Or a certificate, or get that final version ID. That's a relatively high profile item. So, sort of developing a messaging system where a user can paint someone inside the application, say, hey, can you do this? We came up with this concept of the to do list. Every user is going to have a to do list. And then the items that are system calculates need to be handled or can be handled by that user based on. And then clear when they've been clear automatically, once they've been dealt with, that's what we're going to be digging into today. It's the activity fee. Like I said, it's a collection of recent events in any product collection that you can access. Metribes, entry updates, imports that would occur through either a CSP upload or API import. Those will also show. Um, a user's role is going to determine what shows up in that fee. The administrators of this account, they see user related activities like. John Doe was invited to X or Y product collection. Editor roles don't need to see the individual activities, right? So there's, there's going to be a little bit of automatic filtration that happens based on what your role is in the product collection. The fee will be filterable. So the type of event that you're looking for, if you're looking for a batch of products that were imported by CSP last week. Washing to be able to filter down that activity fee to only show batch imports, the only show imports from CSP, from CSP uploads or guy uploads, things like that to really make it easier to track down. The events that are looking for similarly, when you're finding these events, when you're looking back to try and find something before it's usually going to be to follow up on some activity to finish a product entry or to the unit. So these events in the feed are going to be linked. So 14 products were imported to your product collection 2 days ago. If you click that 14 products hyperlink, it's going to show you which 14 products are going to follow up actions. So hopefully that's pretty clear. We've got a quick click through flow to show, to sort of demonstrate this in action. And just a reminder, these screens are obviously subject to change the mockups. All the work is on, I like to say between, I may look a little different in the final form, but this is to really give you an idea of what we're envisioning for the flow. So as you think through this, if there are any things you're missing, you feel like aren't accounted. To or actions you may take. That's why I wanted to voice those concerns or questions. So, so, this is our basic concept for the feed. They can pop out, scrollable and got a lot of core information right there in the feed about things that have happened specifically to this product collection. There will be feeds available from your user dashboard that are not. Limited to a specific product collection that you're used for that has access to multiple product collections. You will have the ability to see all activities across them and filter that down to specific collection on different screens. But if you navigated to a specific product collection and you pop open that feed, that product collection. So it's a context to where. The 4 products. Yep, so you click that. So that's, you can see that that's the filtering mechanism of talking about whatever. Where, you know, based on when that happened and where it came from, you want you to be able to narrow down. Find the place that you're looking for, and then easily get insight into what happens. So you can see those are the 4 products that tag that appears. Yes. That gives you insight into what the filter is that's currently 5 year collection. Change all 4 of those already 1 of those products you'd be able to do that. That clears it, you just back to the filters, I think a little twirl down. Alright, so yeah, this was another filter mechanism. I was talking about where you click on an event site, I believe it should show. So, this user is that's popped up here is an administrator because they have insights into user based events or updates to affiliated parts. So, I believe product and then the secondary context menu comes up trying to see only new enter new product entries updates to entries that already existed or entry removal. So, I think so this filters the list down. So, now the activity feeds only showing new product. Okay. So, if you only wanted to see entries made through the API. You'd be able to addition further filter it down and then get insight into which products product updates. So, that's got sort of the quick over. I think it's a really handy tool for basically just engaging with all the mass amounts of data. So, like I said, the new list plays updates that require direct action when you're invited to collaborate on a product collection. The system really does need you to accept or invitation received those require an action. So, from there to do this on your dashboard, you'll be able to you click that notification, view the invitation accepted rejected items or similarly, if you're an administrator, our products in your collection, your. Test status, which is precursor to that actually filed it using reference message sets. That's an action that we don't want to linger indefinitely. It's going to hold people up at 27 products that are waiting at the station. There's going to be a dream to do list seven products are waiting at the station. Click on it. It's going to show you those products. Do them some of them lower the number of all that sort of so this one I believe is shorter. I don't think that first accepted. See that product collection that you weren't that this user was invited to the product collections screen down there below. They can jump into it, start working, install the whole product entry. They're waiting at the station see that took this user right to those four products. The filter is to show products away at the station and be able to complete that step from turn to the dashboard that item would be clear as well. It would only pop back up once new items in the collection to that ending at the station. So that's sort of the quick, quick and nerdy overview of how we're envisioning these tools functioning. Like I said, if you guys think of anything that coming for updates, I think, delegation responsibility. Let us know hopefully that was pretty. So if you're on the line, if you have anything to add, feel free. Yeah, so can you go back to the previous screen for 1 second? Yeah, so you're noticing here a couple of items we have in the to do list also this concept of expiring soon and expired. So we're, we're talking internally, you know, a little bit about what exactly these concepts mean since certificates don't exactly expire. They're good forever as long as there's product that was manufactured in that time frame, but, but there is a need as long as you're continuing to manufacture, manufacture a product to recertify every year. So it's mostly a terminology thing. Perhaps it should be, you know, pending recertification or, you know, needs recertification soon, something like that. But again, there's this idea that where we want to help you. Has the business account administrator or even a product collection. Administrator to know when you've got. Uh, products in your collection that appear to be nearing a need for updating the certifications and or there are certifications have lapsed. Um, and we're also talking about providing the opportunity to ignore them because there are there are cases, or perhaps on an individual product ignore that if you're not planning on manufacturing any further, you don't need to. Uh, recertify with CPSC obviously. So, um, so those are a couple of other contexts where we're trying, we're thinking this to do lists can come in handy to help you to manage, uh, you know, manage. The flow of, uh, information that you need to provide into into the system here. So, yeah, it's important to point out that I spoke. Comments or questions from the group. So, essentially, you're done with the contents. Any questions or concerns about the activity for the to do list. Take no questions that's positive that covered everything to do with these 2 concepts. Let me go back to slide on the components for discussion. So, we've covered a lot of this, but of course, we still have to address. Some other things like under business intelligence, we have to report. Under certificate data management, we do a self the cover at the station. I really, we still have to cover the managing part and trade part parties and then API as well on the all the way to the right. So, those are like the final ones and. This today was a light topic because we are still developing content for the rest of it and kind of resolving some questions that we have internally before we present it all to you. But in 2 weeks time, we'll be able to cover some of these other topics as well. And then, well, now in next steps, there really isn't any next steps for you. Next steps for me and my team and is to finalize updates to the care. I've taken a lot all of your content, all your feedback and very much appreciate it's been very helpful. Especially on finding my new typos and errors, but also addressing some bigger issues. I've taken some questions to clarify. I've gone through many sections that can tear just clarify content to make it easier to follow. And if you to flip to a page, you have all your answers. Typically of a document like this to answer maybe in there, but I mean, in the section, you're looking at precisely. So I did copy and paste some lines around. And I made some clarifications to certain lines. But to that point, I don't actually have these questions written on the slide. We were internally talking about the record keeper, the individual. Who is responsible for managing the test reports. So that is actually. A requirement on the certificate, but we haven't included that in the filing. We thought that would prefer to test it for the beta pilot. And the reason being is that that is the final data element from the certificate that's not included filing. And if we were to include it, then that could inform our computer around 16 CFR 1110 and help us decide. Whether an email certificate meets the requirements for a certificate accompanying shipments and I know that was a question that was brought up from several of you. So, we'll consider it as an option, but I have a question that you could pipe up now or email me Peter. As to who internally or within your partners, it's response is actually managing the test reports. Who is that record? Is it you the importer? Do you rely on your broker to keep that or the manufacturer testing lab? We consider that those 4 are probably the most likely options. I think most likely it's the importer or broker based on my experience here at CPSC. However, you want to consider if there are other record keepers like at their party that we haven't thought of that you. May hire to manage your test report. And for the more, if it is 1 of the options, I did just suggest that makes it easy to include in the UI because then we would just have like a checkbox or a drop down feature to identify who would see record keeper because we ready. We will be ready collecting that data who is the importer, which of course is the business account holder. The broker information is being received from the entry summary and then, of course, lab and manufacturers provided. So, we hope that's not too much of a lift that would just be a drop down or check box. And so, I just wanted to get your feedback if any of you want to pipe in and let me know who primarily maintains this test reports. And you could even just type it into the chat field. I will follow up with an email detailing these questions. This was kind of last minute and I know I was not prepared and did not have a slide for this. I do want to say our next meeting we march night. I do have to postpone it to 3.30 PM. I do apologize if that's an inconvenience for you, but there is a conflict that I have and. And I figured it was funny it's 3.30 is not a big change. So, you have 1, yeah, just you want to read it off. Yeah, absolutely. So, I just mentioned that Ikea has essentially which keeps test reports. They are responsible for the. So, in that case, it would be the importer or in this case, you know, the certifier slash business account that has a comment she said from our side and macy's response is the responsible party. But we hold all certifications on the 3rd party of laboratory. Okay, so that case, it's the laboratory, which we wouldn't know on it's just okay, I will follow up with an email with these slides. This reporting, of course, because there's some people who have not. We're not here. We'll ask for that. Yeah, we're just in that. Yes, I understand. So, you're that you're addressing a different point. We will as part of in the beta pilot, like, let me take a step back. I know CVP has a definition for I, which does not always align with we consider as the order. So, we will clarify that in the future, but for the purposes of the data pilot, it is because you are the participant, you are the 1 responsible. Where the data and certifying so we shouldn't run into that issue, but when it comes to the future rulemaking, we have to clarify that difference between I, or I can just follow up. Yeah, like, you supply, well, I'm going to stop this reporting. Thank you for your time. I'll stand for a few more moments. It likes to speak to me. Thank you.