 And so today, Brian, my colleague will be assisting me and he would be the one actually showing you the walkthrough of each feature of the product registry. Brian, you could go to the next page. So in today's agenda, we'll cover the objectives and we'll provide an overview of the product registry and business account. We'll discuss the business account roles and responsibilities. The business account setup user access setup, trade, party entry, new product entry bulk upload, and then we'll finish with a Q and a discussion and next steps. Next slide please. So today's objectives. Are these six you will learn how to invite administrative users to manage the business account and or product collection. I do want to clarify the business account. When we use that term, we're referring to the account exclusive to the importer or to the company. If you are a broker or developer or another partner on this. Joining us today on the training, you won't have your own separate business account, but you may be invited to collaborate on a product collection and existing business account. So, whenever we use the term business account, we're really referring to the importer who's participating with us on the pilot and we're referring to the company as a whole, not the. Not in particular to the individual as a part of the company. Second, you will learn how to create a new business account for the participant company is kind of what I just expressed. 3rd, create new collections and invite users to collaborate or add trade party data that lines to the product, 5th, add new products to a collection and lastly, complete product review and certification next slide. Please. So, let me review what the product registry is. I'm sure many of you know what it is. I've talked about it many times before. But just to repeat myself, it is a secure online application or business accounts and product collections are created to help file organized and managed certificate data. The business account is a central account within the product registry for each participant's company's users to organize and manage data. So, the business account administrator is the participant is who is legally responsible for certificate data and delegates business account administrators. So, the company itself is the one. Legally responsible for the certificate data, of course, but within that company, of course, you have users, those users would be the business account administrators. The primary row of 1 includes establishing the business account. This only is for the initial business account administrator. You could be, you could become 1 if you're invited by the initial administrator into that account. 2nd is account management, such as setting up product collection or adding collection administrators or other users and lastly, certifying products entered in the product collection. The participant may choose to delegate this role to a 3rd party, but it's still legally responsible for the certificate data. So, in the end, like what the business account administrator is or. Or slash the participant company that is essentially. The on the certificate itself, that is where we ask for the certifier. Or the importer, for example, so this just to clarify, when you do provide us the information to set up an account, you are claiming that this company is certifying the certificates. Within this collection and the business account administrator is employee of the participant's company, which I mentioned before. And they will have delegation authority to add or remove other business accounts administrators, collection administrators, editors and viewers. And they will have full access to view, add and update all data within the business account. Next slide please. So here you could see the user roles. This is a very clear setup. So, the business account administrator has the most permissions essentially has full control over the business account. The collection administrator has less. They only have access to the specific collection in their business account. The collection editor has even fewer and only has access to add and update data and certified products in a collection. The certifying of the product is only when the permission is provided directly from the business account administrator to that specific user. So, that is an additional level of permissions and the person receiving that ability to certify would have to accept because there are, there is some legal responsibility when you do certify the products. And we just want to, so we have a step by step process to make sure that the person providing the permission and the person accepting the permission understands those responsibilities. Lastly, there's a role for collection viewer, which is simply only view only access. Next time. So here we'll discuss the business account setup. So earlier, an invitation was sent out to the business account, the initial business account administrator. If your company hasn't responded to us regarding who that initial business account administrator is, please don't do as soon as possible. So we could get you that invite. I do want to clarify a few things because this has come up as to how at what points should a new business account be created? I've received questions where, for example, an importer has multiple brands. And what it comes down to is if that importer or that company is certifying the products, all the products, even under different brand names, they are still, they, they are the certifying, therefore only requires 1 business account. However, there are scenarios where an individual may work for 2 closely related companies. They may be owned by a larger company, but those and it really comes down to how those 2 companies function. If both companies are certifying products, they then, at that point, a business account should be created for each individual company. If you are a user of business account administrator for 1 company business account, you cannot have access to another business account. Unfortunately, this. This is just a feature of the product registry for the duration of the pilot. We may consider changing that in the future. But for now. When you have, when you are a business account for 1, excuse me, administrator for 1 business account, you may not even have access to a 2nd business account. So, understandably, this may become an issue. If you. Conduct compliance for 2 companies. However, the alternative is to be a collection administrator instead. If you instead, in this scenario, you could. Request that 2 other individuals be business account administrators for the separate companies, create the accounts and then invite you as the collection administrators to both accounts. Collection administrators can have access to as many business accounts as they need. It's only that a business account administrator. Cannot be a business account administrator in a 2nd. Account, so just to kind of summarize very quickly, what it comes down to is. Which company is certifying if the company is certifying multiple brands and their name is being placed on the certificate as a certifier, then 1 account is needed. If there are 2 company or if you work for multiple companies. Even if they're these companies are closely related, but the individual company names. Are the ones are the official certifiers for those products. Therefore, you would need separate business accounts. You have more questions. We'll be happy to answer. Those just email us at the support email box. So, when it comes to the business account set up, what you would need is the invitation to the product registry from CPSC. You would have to provide your company name and the company contact information. And you also have to set a certifier ID. This is the ID you provide to reference. You as a as a certifier in the in the reference message set. It cannot be greater than 23 characters and it cannot be changed once it's been saved. This the ID is something of your choosing. So, we do encourage that it's something simple and easy for you to remember. And perhaps has your company name in the in the ID itself. It doesn't have to be really long. It just needs no longer than 23 characters. But you and of course, it will be alpha numeric and we do allow special characters in the ID. So, you have a lot of options here. And then lastly, once you create a business account, you could go forward to create other collections and invite other users. And now I'll throw it over to Brian and he will provide a demonstration of the business account set up. Thanks, Arthur. Before we get started with that, I have a couple of little disclaimers. I'd like to throw out to the larger group here. The product registry, everything I'm about to show you the product registry is still under active development. So, some of the screens and features are going to see today will definitely look slightly different as soon as next week. We're adding features all the time. We're getting rid of bugs. We're cleaning things up. We're improving the overall usability. And we have an upcoming patch that's going to fix a couple of things, add a couple new features. So, if you log in for the 1st time next week, it might look a little bit different than it does today. But it's nothing earth shattering. It should all be pretty self-explanatory. So just wanted to give that slight little disclaimer. Additionally, there's 1 issue that we currently have live in the application related to user session timeouts. And I only raise this now because it's probably going to impact me as I'm doing this demo today. Due to the length of this training, I'm almost definitely going to get logged out of the system behind the scenes at some point. We are actively working to fix this. It's proven to be a very tricky little bug and it requires coordination with teams that are outside of our immediate development group. So, it's been a little bit stubborn, but we are close to resolving it. So, for those of you who have already jumped into the registry or going to in the next couple of days. Just keep in mind that, you know, if it's been 15, 20 minutes, occasionally, if you try to do something and you get an error from the system, it's likely that you were logged out behind the scenes and we do apologize for the inconvenience. If you reload your browser window, you will more than likely just see the login screen again. And that'll be your confirmation that that was what happened. If your page doesn't reload and you get asked to log in, that's a sign that you were logged out. And that will hopefully be fixed very shortly. So we are actively working on it. And again, I apologize for that. And final disclaimer, I'm running a lot of screens here today. So there's going to be a lot of jumping around and I'm going to do my best to keep it clean for everyone. But the registry gets a little touchy when 1 user tries to do multiple different things in it. So, as I'm going to, I'm going to be trying to use private browsing windows to keep my cash from like storing things. But you can still, still occasionally come across issues. So with that said, thank you for bearing with me. I'll do my best here. So for the business account setup procedure, as Arthur mentioned, in order to start that process, you need to get an email from CPSC. So that's the point of identifying those points of contact for us. The email looks like this and it's got a link in it. And when you follow that link, you'll see some details about the invitation. It's where it was sent who invited you and that you're being invited to become a business account administrator. So that email gives you the access to this create account button, which is not available to just the general public yet. And then you click through that legal disclaimer and provide some information. Let's do auto fill stuff and then some company details as well. And as Brian takes some disinformation, I just wanted to address 2 fields here that are optional. 1 is the division. And we created this with the thought that within a company, if there are companies that are closely related that maybe the company has the same name, but 2 different divisions are involved in imports. And therefore they may want to have separate business accounts because both divisions are certifying. This is where you could reference that with a different division name, but that's not necessary. And then the GLN, which is a global location number this, of course, an optional field in the future. We do want to attempt to connect to the GDS and cloud. It'd be able to pull in GLN. So you would see GLN fields throughout this registry. For now, if you do provide a GLN, you have, you still have to provide all the remaining address and contact information. Yep, thanks Arthur, an additional note here. You can see the fields with the little asterisk are required fields. We would love corporate phone email and website identification as well. But those are not required at this time. So for the purposes of expediency, I'm going to be leaving out not required fields. So you can also spend a little less time watching me do data entry because it's not super fun for anything. And if you do provide the corporate phone and email in those fields, it could be a generic phone or email. Be considerate of like what email or phone you're providing because you may want to provide your own personal work email. But then let's say if you move to a different team on the company or you leave the company like that email still available. Of course, it can be updated, but just be considerate of what email you're providing. Because that that's a contact information if 1 of our staff needs to reach out to you. Appreciate that Arthur. So, as you'll see, I want to add and click the create account button a little early there because there is a necessary process of verifying the email address that was provided. And I wanted to give the system a little bit of time to send that out here. So it just came through and so you can see that that provides another confirmation link that verifies you're the owner of the email address you gave. So, drop this in here and so following that link successfully verifies the email address. And now you should be able to log in as soon as I remember what email address I used and then you'll see this pop up here and this handy to do item setting the certifier ID is that. Yeah, that's within this that's within the scope. Okay. I didn't want to jump ahead here. So, as Arthur mentioned, the certifier ID is what you'll 1 of the items you'll provide. When filing reference message sets, so the system will try to populate 1 for you based on your company name and division. If you'd given 1. So, like, if it was East, then this would have been what was dropped in there. But, you know, keeping it simple is in your best interest, something like that, you know, or company name, you know, like just as simple as possible because it's it gets filed a lot. So, once you set that make verifying your company details there. Save it that would that process would have failed if example ID was already taken because that. Identifying your your company needs to be unique within the system. Obviously, we can't have companies sharing certifier IDs. So, it'll let you know if you haven't picked a unique 1. You can tweak it as needed. So, I think that's covers the scope of the setup. Correct, Arthur. Okay, so I'll toss it back to you. Great, all right, and now we're at the point of user access setup. So, this is account administrators can invite users to collaborate. As a business account administrator earning product collection role. Collection administrators can only invite users to collaborate in their assigned product collections. So, if you invite another business administrator, you need their email and then you just select the role. And similarly for collection admin or collection editors. You just see this submit provide the email address, select their role, and here you'll be prompted whether you want to provide them certification permission. So, as I mentioned earlier, you could delegate that permission to 1 of your trade partners. This, this permission isn't listed under the business account administrator, because of course this is counted administrator as a representative of the participant company or the importer company. Automatically can certify certificates. So, it's so the permission to delegate comes from the business account administrator. There would be a pay a short paragraph that you read and you confirm. And then when the product collection administrator or editor accepts this permission, they also have to read. Through a paragraph before accepting and next slide. So, back to you, Brian, all right. So, this one's a little tricky because, like I said, jumping in and out of user accounts is not super. So, for this user here, this is a business account administrator and there are no product collections yet. The process of creating a product collection is extremely simple. Um, you just give it a name. So, like, it could be by type of product or by, you know, by brand, you know, however you want, or there's a lot of different ways that your business processes could dictate how to organize the product collection system. Um, let me jump in here speaking about collections at the minimum, you need 1, you could have all your certificates that are 1 collection, but we built in a future where you have multiple collections. And the reason we did this is for 1 example, if you want to organize by certain products or product categories, you could therefore create different collections. Or if you work with multiple trade partners, such as multiple brokers and you want to provide 1 broker, this case, broker, why access to 1 collection and then maybe broker is the access to a 2nd collection. They won't have access to the other collections only to the ones they are assigned to so that in that way, you could keep things separated and this also protects confidential business information. Yep, so I'll just go ahead with that broker Z collection because in order to invite users, you need to invite them to something that is technically not true of the business account admin. You could invite a business account admin to this account, but that will be done very shortly from a user management page that is currently being finalized. So, for the purposes of this demo, this collection that we just created is empty, but you can see it has this invite a user button here. So, you know, we can send out an invite to for any of these roles that Arthur's already discussed for, you know, this demo, I'll just select collection administrator and I'll send 1 to at cpsctest.com and you can see, as Arthur mentioned, there's this offer user permission to certify option here. So, I'll leave it off for the time being. It's like, I don't want to delegate that and just send this invitation out. So, this user, I'm obviously sending all of these to our internal development group. This user will receive an email. It says, you've been invited to collaborate on a product collection and then just like setting up the initial account. They can follow a link in that email. If they already have an account within e filing within the product registry, they can just log into it and they'll see the invitation. You know, popped up on their user dashboard. If they do not have 1, they'll be given the opportunity to create 1, just identifying themselves, their name, their email, which company they work for. And then when they log in, then they'll see that invitation and then they'll have the option of declining or accepting that collection invite with the offered permissions. So, I don't know, Arthur, if you want me to try and actually go through that process of setting up a new account, or if you think. Um, I don't think we quite need to, because it's very similar to the initial user setting up an account. Okay, yeah, well, then, I go to the presentation for now, and we can want it to address 2 other things about inviting users. So, as you saw, you could invite a business town administrator. You know, the product collection, however, I do under correct me from wrong, but we're going to change that so you. Do not have to go through a collection to invite another business account administrator. Correct. Yeah. And in your future implementation on this dashboard, there will be a user management screen. And that user management screen will be the launch point for inviting business account administrators because it's a little bit counterintuitive to go into a collection to invite someone who has. Account level permissions that are not collection level permissions. So this invited user will be updated and you will only see the collection roles here in the future. So, that's a good call. Arthur. Thanks for calling that out. Welcome. Um, yeah, and let's move forward. So, next is trade party entry data users can create and or edit trade party data. So, this is a town. Establishing a record of trade parties within a business account allows users to quickly reference those trade parties during the product certificate data entry process. So, trade parties here, we are referring to mainly the manufacturer or the laboratory. There would be a means to add those trade parties directly on your business account page. If you are the business account administrator. Or if you are a collection admin or editor, you could add those trade parties. During the certificate during the steps to upload a certificate. So, there are, as I'm trying to say multiple ways to add this information. The 1st time you add a new trade party, you would be prompted to provide a GLN or alternate ID so you can reference that trade party in the future. But that 1st time around, you do have to provide all the required information such as address and phone and email. So, as you see below the information needed to complete each task, again, if you do provide a GLN, you still have to provide all the other information in the future. We do. We are considering trying to connect to the GDS and cloud. But in either way, you are prompted to provide some form of an alternate ID. So, by by that additional step, it makes things easier in the future. Plus all your trade parties will be saved in your account. So, when you're using the user interface, you will see a nice list all your trade parties and then you can just select them. Then just referencing right here, the 2nd bullet point is this batch manufacturer ID. That is, if your manufacturer qualifies for that, there's more information at some places website. Cool back to me, Arthur. So, I'm immediately worried about the time out issue. I'm going to refresh my browser here. It looks like I'm still logged in. So, we're going to try and try and get through this process. So, the trade parties, you can go to this managed page, or you can just click the add button directly from that dashboard screen. Adding them is basically as simple as providing all the required fields are they're just referenced. So. I do that real quick and it's Brian is doing this. I just wanted to answer a question I received before, but who is manufacturer. CPC considers the manufacturer as a facility that produce manufactured or assembled the final product. Even if that manufacturing facility is owned by your company, we're looking for specifically for that facility that manufactured that product. So, in other words, we want the exact address. So, as if we're dropped in that city, we're able to find that manufacturer. I'm just going to go ahead and add a lab here too, just so I can definitely later where they show up. Of course, and you only have to provide lab information for testing labs that are not CPC accredited. If you're using a CPC accredited laboratory, which you need to for a children's product certificate, you just have to provide the lab code, which is found on our website. Cool. So, yeah, that's the process. As Arthur mentioned, this all this comes up again and can be done from a different pathway in the application when you're providing user or product certificate data. Excuse me. There's the option to add new labs and manufacturers and points of contact in the middle of that process as well. So, if you end up having a lot of them here, they can be searched. They can be filtered so you can easily find them and check out what their GLN or alternate ID that you've provided is for them. One quick note, these are not currently editable within the system. There are some complications with making allowing users to change data because these get associated with the product certificates. So, if you update it now, it basically is updating it for a whole bunch of certificates that may have already been certified to so we're kind of working out the kinks of how to deal with that process moving forward in the short term. If you made a mistake or some up some information changed for one of your trade parties, you've entered into the system. You can just go ahead and create a new one and you can append a dash to or just make sure the alternate ID is something slightly different and just, you know, have everyone start using the new one. Anything else to say on that, Arthur? No, and that's it. All right, back to you. Okay, adding a new product certificate data is manually entered in the product registry review at the user interface. It must be reviewed and certified by the business account administrator or designee. So, this is a core function of the product registry system and when most of the data entry occurs, there are several data elements required for the product certificate to be completed and ready for certification. However, an incomplete product certificate record can be saved and completed later by the same or a different user. A product certificates considered completes after all mandatory certificate data has been entered and certified. So those who could enter a certificate are the business account administrators, collection administrators and collection editors. And this, this is 1 means of providing certificate data 1 of 3 using the user interface. And next slide. So these are the fields that you'd be prompted to provide data for and so, I mean, these are the same fields that found in the certificates. I'll just go through these quickly. You'll be 1st month for product information and then additional product identifiers. Many of those are optional. Those of an asterisk here are required. Manufacturing data, if it's a new trade party, you need to provide the full information. If it's an existing 1, you just provide an alternate ID and similarly for the laboratory and for the laboratory, you have to provide the data testing citations, the exemptions. And as an optional field, we're asking for the test report URL or test report ID if available. Alrighty, so now we can demo that process. I'll just jump into this collection. We've already created refresh. Make sure I'm logged out this ad products button here. We'll pop up a modal where you can provide all the required information. Require at least 1 primary identifier for the product. There's a lot of different types here. Just select G 10. I'm obviously not putting in super valid data. Once again, non asterisk fields are recommended, but not required. And you can see that that manufacturer information that I've provided before that pops up in this drop down. So that's, you know, we don't want you to have to keep putting in the same data over and over again. So, but if, you know. You hadn't already put in the bike manufacturer, then there's this great new manufacturer button here that pops up this window. So you can provide trade party details that way. And once it's been provided here, that's going to be stored into this business account. And we'll be reusable again in the future for this 1, I'll just select the pre existing 1. Say, this was made this month we've got little date pickers and the production started and dates are optional. Same with the lot number. Correct, so I'll skip some of them. Certificate type. Last test date labs, as Arthur mentioned, CPSC accepted labs that those are from a list that we maintain and they have their CPSC for digit ID at the front here. So you will not need to manually input any of that data if you're using them. Test URL, test report ID. Same as citations, citations are searchable. So you can filter ahead to find the 1 you're looking for. Just be sure to click this plus button to actually add it to the certificate. You can add additional laboratories. So. We select the other type in this drop down, you'll see the 1 I entered on the 1st screen. I can add a couple more citations and it's important to know that if you go back, Ryan, you have to press plus. Yeah, yep, you need to hit that plus button. Otherwise, they won't actually get stored in this final screen. This is actually already been updated. This will have an update live in the next couple of days. The handling of version ID we are putting that more in control for the users. We were working on a system where we auto generate them. Very consistently and, you know, we constantly try to update them for you to make sure they're unique and it was ultimately getting a little bit confusing for users. So in the near future patch, there's a generate version button here. So this will not be auto populated, but you can click the button if you don't care what the version ID is going to be. But the version ID identifier just needs to be unique within a business account. They can't be duplicated because again, that's 1 of the 3 pieces of information we collect. When you're filing a reference message set and that piece directs us to exactly the certificate that that import is referring to. So this is generated an automated 1 for us. It's just an alphanumeric. So I'll just leave that for the time being, but this behavior that you're going to see here is already being updated. So it'll look a little different next week. Point of contact if it's 1 of the trade parties, we already have the information for you just need to specify it. Other will bring up another trade party modal where you can give us detailed information about who is maintaining the test result records. And lastly, you'll see that this button here is certify and that is because this user is a business account administrator. So they have the certified permission by default. If I were logged in with a collection editor or a collection admin who didn't have certified permissions. This would say submit for certification and then the product would be in sort of a waiting state until an authorized user came in and certified it. So, yeah, you can see the product now appears in this collection list and we expand it. You can see all the details that were provided the different labs, manufacturing information, et cetera. Alright, thank you, Brian. There's a few questions in the chat that I want to address. Okay, so 1 is from Eric, he writes, what controls are in place to avoid. Multiple users from creating several different new account entries for the same manufacturer. So, Brian, correct me if I'm wrong, but there are, there's going to be some checks in place that compares manufacturing names and addresses provided previously. Different users in the same account to prevent duplication. Is that right? That has been discussed as something we would look to implement moving forward. However, due to the aforementioned inability to edit the trade parties, we don't restrict that right now because if you provide of manufacturer information and it's not correct. We want to allow you to be able to provide a correct entry for that same manufacturer. So, the only check is that the GLN and alternate ID cannot be duplicated. So, as long as you create a new entry that does not share an alternate ID, both of them would be valid. So, obviously, you want to make sure the information you're putting into the system is correct because it avoids a lot of headaches later with having to double up and create new entries that are updated. And make sure everyone knows which entry to use. We will be implementing an archive system that basically removes a trade party from your view. So, you know, it's like a clear indicator that you don't want people, users of your account using that trade party anymore. It's basically deprecated. We have to keep the information around because it was likely attached to product certificates, but yeah, it's, it's sort of an in progress business rules process that we're developing there. Thank you. Another question from Michael writes the list of citations in the testing tab of product creation does not include every regulation listed on the CPC. Are we only required to enter the citations up here in the drop down menu? Well, that that drop down menu will include all citations. I'm not quite sure if I, I wasn't quick to notice if that list was missing any, but it's also a. There is a scroll bar in that drop down list. You may just have to scroll and find the citation and that citations themselves are based off of the CFR. Except for toys so that for children's products so that you have to put in that 4 digit CFR in most cases when it comes to the ASTM F 9 6 3 standard, you actually just provide the section number that you are certifying to. And there is additional documentation on our web page that explains all of this. And lastly, a question from gift craft, what is the test report URL? So that's an optional field. Because we're considering how can we verify the certificate data? Or how can our investigators verify? And if 1 thing of access to the test report, they're able to verify the. Certificate data is valid. When, when this information is received prior to entry or excuse me prior to arrival. So, if you do provide that URL, just makes things easier for investigators be able to verify the certificate. And then next slide, so now we'll discuss the bulk upload. If you were attending, if you attended the status meeting last week, we did discuss this in detail. We covered the templates. So I won't cover that today. But this is a 2nd option to provide the certificate data. The data is entered in bulk using a comma separated value. File format to upload data or through an API, which is an application programming interface. CPSC will provide on our web page the templates. Season file data and prepare for bulk upload. I already emailed out those templates to all of you. So, instead of using the interface uses use the bulk upload template to edit product certificate data for multiple products in a product collection. If no error exists, the station will occur as part of the upload process. Additional information versus the requirements are located in the filing SOP. So, who are able to do this business account administrator and the collection administrator and editor. So, this is the information needed for bulk upload. It's the same information that you saw on a previous slide. So, I won't go through. We'll go through this, but the template has all this information as well. Alrighty back over to me. So, let me see, I'm still logged in. I try and show a couple of things here. So, I think I already have. Account set up that I could log in as to sort of demonstrate different user permissions. Section editor, send invitation. One second, there we go. So, I just sent an invite from that other business account. We all set up together to a collection editor who already has access to a different product collection under a different business account. You can see, this is what that imitation process looks like. It pops up here and says what you've been invited to who invited you. And this is that extra blurb Arthur was talking about of legal ease where we need you to read this because this user's been offered permission to certify. So, if they accept that, yeah, go ahead and accept that, but this is a page that a third party user would see. So it's looks very similar to business account page, but as you can see, very limited only shows you the product collections you've been invited to. Right and an activity feed and to do less. Yes, so there are no, you know, trade party management options on this screen, but you can see this user has access to a variety of product collection. So, the 1 I just created new products. They can go in here and they have the ability to provide certificate data. To this product collection. So, I'm going to see if we could do the product import. Let me find my files here. By this 1, our, our imminent patch also has addressed some performance improvements in the CSV upload process. So, like, better feedback with the progress bar and slightly faster. This is obviously very small file, but we, because I've only updated uploaded 9 products. The intention behind CSV upload and API is to be able to handle much, much larger quantities of product data. So you could manage all offline in your own independent systems and then send it all to the registry. In 1 move for efficiency, so I selected a file that contains 9 new products. I uploaded it and basically the system parsed that file for all the data that it contained. And it shows a summary here. So I just put this together just before this meeting and you can see all the required fields are provided. So it identifies them as ready to import. If I'd had errors, like missing required fields, if I left off a primary product ID, or didn't provide a manufacturer. That row would be that product entry would be highlighted in red. And when you hovered over it, it would specify, which, you know, what was the problem with that line, why it had an issue. So, if it calls out the errors, you have the option to just cancel, fix those errors in the file and then re upload, or you could just import the valid products, fix up those error ones later. However, you want to handle it. But yeah, this is, you know, you can see there's pagination here meant to handle much larger quantities of products. So this is a small one, but let's see if we can just import the valid products now. And for now, we ask that you only upload 100 products at a time using a template. We will increase that number in the future. But for the sake of development right now, and not to run into any issues, just stick to 100. Right. Thank you for remembering to point that out Arthur. Yeah, the smaller the quantities we can use at the beginning. It's just going to make everyone's lives easier because any issues that we encounter, like I said, it's an active development application. So, there are going to be little bugs and errors here and there. We're working to fix them as quick as we can, but we do rely on feedback from everyone participating to kind of help us identify those and get them remedied as quickly as possible. But you can see that all these products are now in this product collection. So we didn't have to go through the one off ad product one at a time. We were able to upload a whole bunch of products all at once. And this spelled everything that's unfortunate. You'll also notice that these are all in a waiting certification status. So when you bulk upload products, they need to be certified to separately. It's that's just the way the system is built in the future. We may have it set up so that if you're an authorized user who does have certification permission, you can do it all at once in one process, but currently, that's not the way we have it written. So this user, actually, I did offer certification permissions. So they should be able to certify these. There's a little certification text. Let's see if we can. And your products have been successfully certified. So now these products would be ready to file against. So that's great. I'm glad to see that working. Excellent. Any comments on that, Arthur? Just move on. No, we can move on. You want to step forward because I was going to first talk about product certification, but to be quite honest, product certification is integrated to into the user interface and the bulk upload that it's. So that it's almost seamless. So that's the final step. So on the user interface. On that last slide where you ask for a version number and a point of contact for the test result records, there would be a field below where you certify. There's some legalese that you have to read or check off to and then you certify at that point. If you have the permissions, of course, if you don't, then you actually just save the certificate. There will be some language there that says that the information you provide is truthful and accurate. Pretty typical language against fraud. And the next slide. And for the bulk upload, this is what Brian just showed you. If you have the permissions, you could select multiple products at once and then you certify them all at once. And that is during the staff of the bulk upload. If you were. If, for example, if you as a business account administrator are coming back in the system to certify certificates someone else provided, you could do a bulk upload from your product collection page. So next slide. This is demonstration. So Brian, maybe you could just show where in the product collection you could do bulk certification. Yeah, that was actually what I did for these 9. Sorry, sorry for jumping. If you select multiple products, there's there are a couple of bulk actions you can carry out and certification is 1 of them. So that's that's the simplest way if you're doing multiple products at once. You can certify from the actual product screen. Like so products are editable once you've saved them. But if this product had been in a waiting certification status, this user could look at it and could come over to here and they'd see the certify button so they could certify it to it. I believe they also should be able to see certify in this drop down here. I think I noted that that might not currently be showing up. But yeah, so just selecting a product and going here and certify is a very easy way to accomplish it. One other thing to point out. Because certification is a permission like not everyone can do it. Users of a business account who do have that permission will see a note. A message on there in there to do list when there are products in the collection that are ready to be certified that they're in that awaiting certification status, which means all the required fields have been provided. And there'll be a link that'll, you know, it'll be hyperlinked and it'll say like 20 products are awaiting certification. And if you click the 20 products, it's going to take you to. The collection page and it's going to be filtered by awaiting certification. So you'd see all the all the products that are waiting to be certified. You could select them all at once and then you could certify them all at once. So we really didn't want it to be a painful process, but it is important to call out all the same. Anything else? No, I think. All right, we finished. We finished our training. So. Thank you for your help Brian on this and I hope all of you. Got a lot of this training and find that the product registry system is simple to use. One last feature that we did not share yet because it's so in development is the API upload. Once that is available, we will create some guidance documents and provide that to you. I. Do you want to say or refer you to our webpage, which is not actually available here, but if you go to cpse.gov forward slash e filing, you find all our documentation. There's the SOP for this, which provides step by step documentation. You find this CSB templates or bulk upload with a guidance document explaining how to use that. There's also documents. Referring to the citations and exemptions. The 2 page guidance document plus the list of citation and exemption codes to get an idea of how. How the codes and the descriptions of the citations will appear in the registries. Or you just provide those cold codes in the bulk upload. Therefore, you don't have to type out the citation and everything is kept in uniform. Also on that webpage, you could find the code list. And so the list of approximately 260 hts codes we expect. Importers to file message sets for, but that is an incomplete list because. That was just based on our targeting efforts. And so we do expect. You as a participant to file. Certificates for hts codes now found on that list. We do actually encourage you to do so because that would help inform us. Which hts codes will be affected by e filing once it's fully implemented and we could. To be flagged those during the full implementation during the pilot. We won't be flagging. Each test is because that is a flag sent out to anyone in parade who files under that certain hts code. And that would just cause more confusion. To people not participating because I said, there's only approximately 38 of you participating in the pilot with us. So, before I open up to questions and feedback, I do want to say that there would be a survey sent out following this training. I will send it out to either the initial business account administrator or the main contact for your company that's been. Contact with us regarding the pilot. I'm only sending it to the importer participants. But of course, you're encouraged to work with your trade partners to answer the questions. The questions. It's, they're only approximately 7 questions from what I remember. We're curious about whether any of you are going to file using type 86 or the minimus or entry type 06 import because. We just want to extract those those scenarios and make sure they're functioning well. There really won't be such a big difference between filing and entry type 0106 or 86 and using the message. But we just want to cover our faces there. We will also ask whether you intend to use the full message that or reference message and whether you intend to this claim any messages. And this play message is to review our for our products that are captured by our but our products that do not require a certificate. And the guidance documents on our web page explains this more. So I'll refer you to that. If you. This is different from products that I may have an exemption from testing. If a certificate is still needed for a difference. A different citation and you for a 2nd 1 have an exemption that is where you provide an exemption code. A this claim message is when no certificate is required. Period. Next, on this list, of course, if you have any questions, please reach out to e filing support at cpsc.gov. And then the next steps for you is please go ahead and create your business account. Start testing out that registry. Adding new collections, adding users and certificate data. You go ahead and test and with your broker, you could test submitting messages. We the message set is now in the production environment, which means that you could test using real data. And on our end, our developers will receive that data and be able to process that through our risk assessment methodology. And at this point, I will open it up to any questions you may have. I see a hand is raised by Eric. And question for you. I know we've talked about the, the uniqueness of the business account and you can't be the owner of more than 1 business account. What is the driver on that? What's the unique element that's preventing that? Is it the email address or. Or what, what. Yeah, it would be the email address as the system is built right now and Brian could correct me from wrong. It's that the accounts are based on the email address and you're associated to a specific business account. So, if you were to provide me a separate email address, you could in theory have access to 2 business accounts. Perfect. Okay. Thank you. Yeah, that is correct. Actually, I saw your email and that that is the limiting factor. So, if there are separate emails for the separate organizations, that's a really valid work around. Okay, I'll follow up with you guys. Thank you. Okay. Do you have another question Eric is so very sorry. I actually do. So the emails. That controller here, the emails that you sent out, are those just. Do those have any control over the an email address? So, was that just an invitation to get you in and you can put whatever you want in there. Once you have that invitation. Or, or is it, is it assigned to the email that we gave you in a previous message? It is. Yeah, they're email specific. So when you click that link, it'll, you know, if you, it'll take you to that landing page. And when you try to create an account, the email field will be locked. And that's, you know, 1 of the mechanisms that that is preventing someone from using 1 invitation to create multiple different business accounts. So, if you're going to go the route of different emails for different accounts, you'll need an invitation for each of them, but we can certainly coordinate that. Not a problem. Thank you very much. Yep. Thank you. I think I just answered that. So that's just on the initial business account owners. So if I add, if I add. An associate and we have to set up a 2nd company that associate can be the new admin, the owner of the 2nd. Entity we have to set up. Correct. In that case, you have to email us with that individual's email. We'll send out the invites. The registry is on an invite only basis in the future when we do full implementation. We're going to remove that step and anyone could go in with an email and create an account. So just follow up with us and we'll get that. No, it was just as you guys were saying that I was like, I just wanted to make sure just in case. Thanks. Of course. Charles, I see you have a question. Yes, Arthur. So, and we had an email this morning, you might ask Timmy yet. Based on back on the importer accounts. We are in charge of our parent company plus our holy own subsidiaries. Totally different name, totally different importer record numbers. Is there going to be an enhancement before because mandatory to allow 1 email address to be. Responsible for 2, 3 different business accounts. I know this won't just be an issue for us. And each of those. And just to clarify each of those separate entities will be certifying. Correct. Okay, at the moment, like. As we mentioned, it would have to be a separate email accounts. We will consider and try to possibly in a future iteration build out where 1 user could have access to multiple business accounts, but. Not for the pilots, unfortunately. Bill go ahead and then I'll go to the chat because I see there's a lot of questions. Yes, Arthur. Is it possible when you look at the testing is asking for a certificate type. It'd be easier to have a field. Is this a children's product and you have yes, like in the uploader. And that would default to CPC. So you have to make that choice every time. Because you either have a, you assign it either a GCC or CPC to the product, right? And you wouldn't have to make the choice. It automates that step. Well, we can consider that as an option for development. Okay, thank you. Thanks. I'm going to go to the chat apologize. I didn't see these questions earlier. Amy writes, how do you enter information for product of the company's leveraging component testing with different test reports from different laboratories? That's a very good question. You have the ability to enter additional labs. In the UI and also in the bulk upload. If I mean, Brian, maybe you could quickly go back to an example of the UI so we could show Amy where you could add the new labs. And as he pulls that up in the bulk upload. The fields are listed as lab 1, lab 2, etc. If you have multiple labs and you could in that scenario. Just create more columns keeping the field names the same just changing the number from 1, 2. Yeah, so in this, this screen here, we're providing all the testing information. Multiple labs are handled by just adding the information for 1 and then adding another with that new laboratory button there. Yeah, so just for that one. You have multiple component parts that will come into effect. Yeah, so you can keep adding them for all the labs you have and then we didn't really speak to the exemptions. But this, you know, this button here obviously is for adding any exemptions. You don't add multiple of them all the exemptions go in 1 place. And we'll certainly verify that these drop downs are comprehensive. I know that was brought up. Maybe we could be missing a few, but we'll double check on it. Yeah, and another 1 of our developers didn't mention that that the citation field and exemption fields are also type ahead. So, if you, I mean, let's just. Type in toy or some. Yep, tell there we go or this case toy and you see all the options for toys. And as you can see the standard it's based on their section number. And that's an option. This example, you probably will never have a product that has a safety standard for matchbooks and toys. But we'll keep it for now. Well, that's what this little trash cans here for we can, we can delete them. You accidentally added 1 you get rid of it. But remember to press that plus even if there's 1 citation, you have to press a plus sign to the right. Yeah. That's a good reminder. Okay, I see a question from Kelly. It's not clear from the example, but it's the same version ID allowed as long as the product ID is different. Yes, it's allowed. You just have to make sure that the product ID and version ID are unique. 1 in combination and we'll have checks in the system so you'll be prevented if that is not unique. Dina writes, is there a target amount of products to include in the pilot? Very good question. I would say I encourage you to file for as many products as you can. Any of the ability to. I do understand that it may be easier for some of you to start with a certain product category because you may have that information. More readily accessible in a data format. But we do encourage you to kind of build up over time throughout the pilot. We do intend to make this permanent at the end of by the end of 2024. So even when the pilot ends, we'll be on a voluntary basis where you can still file and just kind of build up to that your capacity of all products that require a certificate. But for the pilot, I do encourage you do as much as possible. I do understand there are limitations in your company. I do understand and this is a voluntary program and we do very much appreciate your participation on this. But we're not going to dictate for how many products or what percent of your products. Let's see other questions here, BJ asks, does the collection editor only has permission to certify the product? Yeah, the collection editor can add and edit products in the collection. And they could be provided the permission to certify. I think in this example, we, we only show it how to certify, but they have the ability to create products using the UI or the bulk upload. And that asks, will this recording be available? Yes. So I will follow up. It's the latest tomorrow morning with a recording of this presentation. You receive a link with access code. And I'll later post this recording on our webpage for all. For anyone in the public to view. Let me see. Okay, ready answer question from Amy about component tests reports. Five, how about us when the API integration be available? Brian, do you want to answer that? Yeah, we don't have a firm date currently. Unfortunately, I know a lot of people are very interested in that functionality and our timeline has slipped forward a couple of times already. Fortunately, it is very, very closely related to the CSB upload functionality. So, as I mentioned, our imminent patch addresses a lot of the issues we were seeing with the CSB upload. So the API, because it utilizes a lot of the same mechanics for parsing, you know, the massive data and like, you know, generating an import review log and stuff like that. Because it used a lot of the same things. It shouldn't be very far behind, but the developers are actively working at right now. So we're certainly hoping that we'll have the 1st pass at it. What is the date? Yeah, I mean. Mid month would be our target at this point, I think. Thank you, Brian. I have a question about whether from Amy, whether the list of pilot participants will be published. Yes, we will publish a list of all participants. We will do, we will draft a report after the pilot is done. I could, I do also want to add that anytime we have a meeting such as this with individuals from the public, we create a meeting log that does list all participants and that's listed. In the docket of our federal register notice for this project. So you could go back and go back to the link for the FRI and and you're able to view past meeting logs. I've asked how long will the pilot run for. So we are going to run the pilot for 6 months. After that, we will just continue on a voluntary basis. So you don't have to stop and then restart when we do permanent. Violings. Okay. Give me 1 moment. I'm quickly going through the questions. A shoe on ask. Do we need to create a new certifier certify ID and new product collection when it finds in the next year for all importers. No, that's what I reference to. That once you create an account here. Even once the pilot is over. Everything will still be operational. You could voluntarily file and you keep your account and certifier ID. A shoe on ask we have different brokers file entries for us. Can we only choose 1 broker to participate in you filing? No, you can have multiple brokers assist you. And that's why the collection are built in such a way where you have 1 collection for 1 broker, a 2nd question for a 2nd broker. BJ ask is the process required to be completed by the company that has IRR or does the company importing the goods and paying the taxes does it. So, this is where definitions of importer record and who's actually shipping the product and who certifying kind of gets. Where lines may cross here. So, in this case, BJ. Who the business account owner is a certifier on the certificate in many cases that is we make a locally call you the importer as well. And in many cases that may be the IRR, but it does not necessarily have to be the IRR. We're not kind of we're not confirming IRR versus the certifier business account. We're not doing a check right there because there are many scenarios as I repeat myself where the IRR could be like a freight forwarder. An express carrier or someone else. Bringing the product on your behalf, but you are still. You as a business account slash imported. You are the 1 certifying that's why we can you create the business account. We request all that information upfront because that is like the 1st item of information required on the certificate. And then. Lastly, I had a question. Can you review again when you say at the beginning the call about possible laughs and funding. Sure. So, so we are aware that this is still developing situation. We understand that Congress has a deadline until Saturday at midnight. And so we will send out more information next week. Once we know more and the outcome. Come this weekend. Our email inbox will still be monitored. And so you can still send emails to support at CPSC dot go. I do encourage you to go to our web page to review the documents because I believe many of your questions may be right answered in those documentations. So, please take a look at that 1st. However, if you have issues with creating an account or some other technical issues, then this email is that you find support at CPSC dot go and we will respond as soon as possible to those emails. And then. And we do also encourage you to continue testing and checking out the product registry. So, this is to say that. We really don't know at this moment how things will hand out as of next week. So, that's all I could tell you today. I do not see any more questions in the chat nor any more hands raised. So, at this moment, unless someone comes up with a question, I'm going to end the meeting. Thank you for your time. We appreciate again I want to express on behalf of everyone at CPSC, even from people above me that we really appreciate your participation. And your involvement on this e filing project. I know this again is a voluntary process and it's nice when we have scenarios like this where government and industry can work together on a project that can benefit both of us. So, again, once again from all of us CPSC. Thank you. Hi. We and again, if you have any questions, you know how to reach us. Have a good rest of your day.