 Before we get to the presentation though, I do want to present an emailing video that we created that it is published on our webpage. It's only 3 minutes long. But if we use for. For marketing, if I link in the future, so let me get to that before I start though, I see there's some comments. That some people cannot hear me if you can hear me, I just recommend. All right, I will just move forward and share our marketing video with you now. I know this is a little bit tricky sharing this. Yeah, a webcast, but hopefully. Alright, I do understand some issues with the video and the audio, but I hope you got the gist of that video and there. I'll send out a link to our webpage, which includes a video as well. So, let me move forward with this presentation today. I'll provide a status update of where we are with the beta pilot and provide you a timeline. I will discuss and review in quarter preparation for the beta pilot launch. And how you can organize your certificate data in advance of the beta pilot, and then we'll move forward to discussion the next steps. Alright, the status of the file, so we have excuse me. I'm going to first mute everyone hearing some background noise. So, regarding the requirements, the care has been updated and completed and it's posted on our web page at CPC dot go forward slash filing. Also, on that web page, you can find several resources. Including the final citation exemption, code, listen, guidance, document. As well as our draft standard operating procedure for the product registry. You could go to our web page and begin reviewing those documents before. You receive access to the product registry, which will be sometime relatively soon. I'll talk about that more a bit later. And on our website, but you can also find more documents pertaining to the code that you could file under during the data pilot. As well as the care, as I mentioned previously. The care would be mostly used by your brokers and software developers to build out their. Infrastructure to connect to our message sent. Third is system readiness. So, the, which is a group of 9 importers that. Have participated with us in development. Have been trained to use a product registry and are currently using and testing it. They're also testing the message set and providing us with feedback. Shortly after this meeting within the next week or so. We will start sending out invites to the remaining participants to get you on board it into the product registry. And we'll provide also a training on the product registry sometime next week. And in October, we will launch the beta pilot. So, this is a time that you may have seen before broken out into 3 groups. The 1st is the IT development advisory group, which has helped assisted our CPSC developers in developing. Our PGA message that in our product registry and currently they are in the middle of testing. And providing this feedback on those tests. We are still actively working with CBP the systems have been. Already created and are now functional and live, but there's always some. Small hiccups or small issues that's only resolved. So we are developers are continuously working on. Updating the PGA message set and the product registry to make sure that it's working. Working as good as it can and lastly. When it comes to the pilot participants, we are here in September. So we're going to begin participant training for the 40 pilot participants. Participating in the pilot with a E filing pilot launch date and sometime in mid October. And then the pilot will run for 6 months through the spring where we'll collect feedback from you, the participant. And also review the data that we receive. So, in preparation of the launch. We ask you to go through these 6 items prior to the beta pilot launch. And these items you already have seen in your welcome package. There's a 6 new item that has been added. I'm going to review each of these items here versus identify the codes that you would like to file in the beta pilot and share with CPSC. These are only guidance. These are codes that we believe that most of you will file a certificate under. However, if you're filing for a product that is under a different code, we do encourage you to file a PGA message set. We will be collecting the data and that information will inform us which codes would be affected by a filing. As of now, the code list, as I said, it's only a guidance. It's only 260 codes. It's our current best. I submit of which it is going to be most affected by the filing. Second, is it determine your desired PGA message set? Whether you want to use the reference message set with use of the product registry or whether you would submit a full message set, meaning submitting all certificate data for each entry line. Third is to gather and form a certificate data as needed in preparation for e-filing. The product registry have multiple ways means of submitting data. One is to submit using a user interface, which is filing once a certificate 1 by 1. However, we also built out of bulk upload feature and have created a CSV template, which I will show you later in this presentation. You can use that template to organize your data and then submit the data either. By using the user interface or just by uploading that document to the product registry. Fourth is to perform integration for the PGA message set and the product registry. This would be mostly the role of your brokers and your software developers and you should work directly with them on this step. If it's to provide CPSC with POCs for the IT team of performing integration, so we will know who we could communicate with and lastly, it's to provide a designated business account administrator. This is someone from the importer's company who will be the who would create the initial business account. And this individual will first create their own personal account and a business account for their importer company. And then they could invite other users from their company or from other partners to participate in submitting certificate data to the product registry. That is so the role that designated business account administrator is no more than the 1st person in your company who will create an account in the product registry. So, when it comes to organizing your certificate data, we have created guidance on using the template. Which I will go through on the next remaining slides. This information will be emailed out to you later and it will be on our web page with the link at the end of this presentation. So, just some best practices and guidance. Data exported directly from a system of record can be loaded into the file. The file works best. You attend to modify product data within Excel. Excel file must be saved as a format for the bulk upload process though. So, this means that you could save it as an Excel file. However, you have to receive it as a CSV before uploading your data. The day fields in the Excel template are preformat as text to prevent the software from altering the data they contain. The column field name should not be changed unless you add additional laboratories. And all commas must be removed, especially from names because CSV files function on using commas to determine different data items. So, therefore, you have to remove any commas as in this example below. The next 4 slides will cover organizing your certificate data in the CSV template and it's broken down into 4 steps. The 1st is regarding your product information. 1st, it is important to indicate whether a new product is being added or an existing product is being updated as that impacts the data required to complete the entry. Current and new version IDs are required for an existing product. So, as you can see in the left most column. The required column, it is, excuse me, it is required to provide a yes or no, whether it is a product update. If it's a yes, then you provide the current version ID and then a new version ID because although you may be make providing an update to that certificate, it is creating a new version ID because both certificates can be used. If it's a product, if you select no for the product updates, then you provide a new version ID. You also are required to provide a primary product ID and identify what type that this is. So, in this example, you can see that there is 1 that's a G 10, a 2nd that's a UPC. You have a selection of 7 IDs for your primary ID, which includes a G 10 UPC, SKU, model number, serial number, register number, and ultimate identifier. You do not have to provide all of them. You just have to provide 1 and the rest are optional and the 1, you provide the primary. You do not have to repeat in the subsequent column. So, you see in the 1st line, the G 10 was used as a primary product ID. And the G 10 field is left as blank. Next, you provide a required certificate type. So, it's either a CPC, which is a children's product certificate or a GCC, which is a general certificate of conformity. And then you provide a product name this name should be sufficient enough that any of our investigators can match that certificate to the product. So, we do ask you to be specific. We also allow for other optional fields to provide additional information to be more specific, including the trade or brand name, the product slash model description. The product model color or the product model style. Next is to provide the manufacturer information because we understand that you we repeatedly providing the same manufacturer information. We. We added an additional step to make it easier by allowing you to use a global location number or a G L N or an alternate ID. So, this is a unique identifier for the manufacturer. So, the 1st time you submit a manufacturer either by using this template or by using the user interface in the registry. You must. Provide a G L N or alternate ID. It's a manufacturer has a G L N you could provide that, but you still have to provide all the required information if the manufacturer is new. In the future, we do hope to connect to the G D S and cloud and pull them that information for the G L N. However, if there is no G L N, you could create your own alternate ID. So the. So, these manufacturers that you provide will be stored in your business account and you'll be able to reference those anytime you submit a new certificate by just referring to the G L N or alternate ID. When you in all cases, you are to provide a G L N or alternate ID if the manufacturer is new or not. If it's a new manufacturer, you do have to provide the additional required information, which includes manufacturer name address. Phone and email. If your manufacturer is a small batch manufacturer. You could provide that ID provided from C P S C. There's more information on C P S C's website regarding that. And you and the last required field is a manufacturer date. Which is just a month and year and you have to provide that information for. Any manufacturer, even if it's previously used manufacturer. And if you're, if you manufacture over a batch run over multiple days, you just have to provide the month and year of the 1st date. There are optional fields as well, including the production start and date. If you wanted to provide a more precise field of dates and then also the lot number and lot number assigned by fields. Next, it's a laboratory information. This is to indicate whether the product assess it is at a C P S C accepted lab or another facility or whether exemption was claimed. So, the 2 types of lab fields are L. A, B, or I T L this matches the acronyms found in the chair. L. A, B, or just lab are any 3rd party laboratories. And if you do use a lab, you must provide all the required information unless that lab. Unless you, unless you previously provided that lab and you just use an alternate ID. So that 1st row is an example. The lab is new. So, an alternate ID was created similarly to how you would create an alternate ID from the manufacturer and then you provide the lab information, including name, address, phone and email. If you use it on this references, this means that it is a an independent testing lab, which would be a C P S C accepted laboratory. Therefore, you just provide the C P S C ID, which is found on our website. And you don't have to provide any more information than that. Even if that is the 1st time you use that specific I T L in yours. In the product registry, you do not have to tell us if it's new or not. You just have to provide the ID. We already have all the information. And then for each lab, you must provide at least 1 citation, as you can see on the right hand side. If more than 1 code is provided, each value must be separated by a semi colon. The citation codes and guidance on citation codes and exemptions are found on our web page, which I have a link to at the end of this presentation. And if you are providing an exemption, then you should provide an NOL, which would mean. Then there was no lab testing and so all the fields remain blank and you just provide the exemption codes in the citation code field. And lastly, you are to provide the most recent test date, which. Overall, for the product itself, you do not have to provide a last test date for each lab result. You can and we will just reference the latest 1, but you are only required to provide the last test date for that product that was tested. In this example, it's a little bit misleading that there are multiple rows here for laboratories. If you have multiple labs or exemptions for 1 product, you would just have to recreate. These lab fields in your documents. So you would copy and paste all this lab want all these lab 1 fields and. Relabel them as lab 2. You shouldn't have multiple lines. You just in your document itself, each row would be 1 product. So, again, if you need to provide. Multiple labs for 1 product, you just have to create more columns and reference those as lab 2 or lab 3, following the same jargon. More information is in our guidance documents about this. And lastly, you must provide the point of contact of the entity who maintains the records of test results. This could also be called the record keeper. We found that most POC's are either the importer, broker, manufacturer. So, when you provide the information, you could just list importer. Broker manufacturer laboratory in the 1st column. And you just leave it as that. If it is someone else, then you must provide, you must. Select other and provide the POC information and similar, similarly to what was done before you. You have to identify whether this POC is new or an existing POC and provide an alternate ID and GLN. And if this POC is new, then you provide the POC name, address and contact information. And again, no additional data needs to be provided if the POC is the importer, broker, manufacturer, or laboratory. Last, I would like to discuss about permissions in the product registry. The business account is created and managed by this account administrator. Business account responsibilities vary by role and user. So, the business account administrator, the user from the importer's business dedicated to manage the business account on behalf of the business. The business administrator can perform all functions needed to configure and manage the business account, including providing and maintaining certificate data and inviting and managing other users. I'm just going to repeat that this administrator must be in the importer's business. And we require 1 to be considered as a designated 1, we request that you send us that individual's name and email address so that person can create an account on behalf of the business. From there, they can invite other users, including other users in their business to be additional administrators and they will have essentially the. All of the same permissions, essentially full control over the product registry and every collection in your register in your business account, you could create multiple collections to organize your certificate data. And provide separate permissions per collection to different users. This is most useful if you work with multiple trade partners and. Want to keep the data that 1 party summits separate from the other party. For example, if you use 2 brokers 1 collection could be data managed with 1 broker and the 2nd 1 could be data management 2nd broker. If that's not the case for you, you do not even have to create multiple collections and you can save everything under 1. So, after the business account administrator creates a collection, they're able to invite an administrator, which could be from their company or business or 1 of their partner's business. And that individual manage certificate data and grants and removes access to a specific product collection. The collection editor is a similar role, but only is allowed to enter and manage data in a specific product collection and the collection viewer. Provides only view only access more information on these permissions can be found in our SOP. So, for next steps, we will send an invite for an official kickoff meeting prior to the data pilot launch. We will also provide an invite for training for the product registry and additional onboarding guidance. You can access all our documentation, including a video you saw earlier at the start of this meeting at cpse.gov forward slash e filing. I hope many of you already have that site bookmarked. There, you could find the care, which is the implementation guide. Which as I repeat myself would be used mostly by brokers and software developers. The standard operating procedure is for all participants to use a product registry. Then the codes, the upload guidance and templates. Those are the last 2 documents that still need to be uploaded. So they may not yet be available until later this week. But we will follow up with copies of these templates and guidance. And then the citation exemptions is clean guidance and code list. All these documents, I know it's a lot. They were, but these are all the documents you need for the beta pilot. And hopefully they're easy to understand and to digest. We will also be completed. We'll ask you to complete it integration and notify us when you're done. And to begin organizing your certificate data and preparation for e filing. And lastly, submit a Disney business account administrator. My colleague Justin has sent out emails previously. So just please respond to him with that business account administrator contact information. If you have not done so. And the next couple of weeks, we will by the end of this month schedule training and we will also send out the business account. The initial invite for the business account administrator. So that individual can begin logging into the product registry. Invite other users and kind of follow along with the standing operating procedure. Before we conduct our training and so at this point, I'm going to end my presentation and ask if there are any questions. I see by the hand raise, please go ahead. I asked her, how are you doing? I'm doing well. Thanks for joining. No problem in regards to the bulk upload template. I know that there was a revision sent out sometime last week does CPSC anticipate any more updates to that bulk upload template by any chance. I know, I don't believe so. I think our developers are on this call. So they could jump in, but from what I understand it's it's pretty much set in stone for now. Okay, cool. Thank you. Yeah, we're working on basically identifying all the data sources to input information into that file so that we don't have to manually input all this information in there. So, we just want it to be sure that that those columns are all locked down at this point. So we can accomplish what we're trying to achieve. Thank you. Hi, Arthur Michelle with Derringer. Can you hear me? Yes, I can. Okay, excellent. So my 1st question has to do with the data that's being generated by the product registry. When we transmit an ABI, everything has to be an uppercase. And I did notice that when the version IDs are being generated from the product registry, it's in mixed case. Is there any chance of having that reverted to uppercase? That's the 1st I've heard of it. So I'm going to write that down as a note and follow up with the IT developers. Great. So, yes. So the ABI requirement is everything transmitted and ABI to customs is always uppercase. Okay, so that was number 1. My 2nd question has to do with the uploads that you were showing. It appears that all uploads have to be done on a product basis. Am I understanding that? Like, are they not able to say upload directly to the manufacturer table itself and the lab table itself independent of a product? Yes, for now it's for the product itself. So each row in that template is a separate product. We are going to build out capabilities that an importer could upload like a list of manufacturers and a list of laboratories at once and then reference those in future certificates. However, that that's still like on our list of things to do. And so maybe in a future iteration, we'll release that update. But as of now, it's not critical for the beta pilot itself. Okay. Thank you. And my final question is it appears that the phone and email address for the manufacturer is a required field. However, that's not, those are not currently requirements of the certificate data. Yeah, good question. So. We are we're making this required because we are updating the. The rule surrounding certificates, which is 16 CFR 1110. And we will. And we will, we're about to publish that rule, send it to a commission published so you have time to review it and also provide comments. But 1 of the things we're, we're going to require is the email address and telephone number for manufacturers and laboratories. So we, I know it's not currently on the rule, but that's what we're going to propose. So that's why we also want to test it in the product registry. Understood. Thank you. Okay, I'm going to go to the chat. Because I, there's some questions. Amy asks if we leverage component testing support our certificate. This is generally done at different labs. In this case, we would add additional columns for lap 2 and 3 and so on. For everything would be listed on 1 row. Yes, that's correct. Each row is its own product. So you have to create new columns for lap 2 and 3. VJ Gandhi writes from an important perspective is any integration required or does a broker have to do an integration part. I think for the most part, it's the broker who's going to do the most work with the software developer, but you should speak with your broker specifically on what assistance they need from you or what data they need from you. The registry is going to is created in such a way that there's different means of uploading data. 1, using user interface to the bulk upload or 3 and API. And so we're creating a lot of flexibility for different business processes. So you should really just speak to your broker about that. Erica writes. Okay, so Erica wrote that per service rep. This is net CHB confirm they're not participating in the beta pilot program at this time. This is net CHB discard. Therefore, they're not able to assist it integration is anyone else having the same issue with the same provider. Yeah, that's good question. Erica other people have that same issue. They correspond in the chat field. Well, you could we could speak. We could take this offline and speak with you because we do want to have your continuous support in the beta pilot. And I believe there are others. Other importers who who work with a broker that work with any and sorry with net CHB or discard is. So, let's take this offline and we'll try to help you there. And then Kelly, Ness, for a dinage from BV rights regarding the manufacturer contact information. Who's considered the manufacturer for this could this be the importer? No, this would be like the manufacturer itself, like the factory who. Or the corporation that like manufacture the product. So, this should not be the importer. If the if the individual like manufacturer facility doesn't have like a contact information, even generic, but there is a generic contact information for maybe the company that manages. Multiple factories you could provide that contact information, but it should be someone who operates that facility. Okay, Phil writes it's important to note that API rollout targeting for early October was for Jason as well as CSV. And Jason would be cleaner for the system the system integrations. We'll be updating our API documentation in your term to reflect refinements and. Made since the original publication. Thank you Phil for that update. Amy writes manufacturers not required data element wise and manufacturer name required. Amy manufacturer has been a requirement on the certificates since it was first published in 2008 so. It's remains a requirement and so we'll be collecting data for that, including the manufacturer name. Okay, and. Give me 1 moment as I look at who has their hands raised. So, Bob, you have another question. I did Arthur just wanted to be clear and get clarification on the exemption versus the disclaim. Exemption codes and we have this dialogue, but I just wanted to be sure about it. So an exemption is utilized when there is a mandatory rule that applies to the product. Which would acquire issuance for either a CPC or a GCC. But you can basically claim an exemption code if there is 1 available for a particular product. But correct. Yeah, if you use an exemption code, you just provide that code on the certificate. But the point I made earlier is. If you're only providing exemption codes. And there are no other testing done on the product that was certified. That means a no certificate is actually required and you do a disclaim message. And so, if you go to our webpage, there is a guidance document on it. I have created like a step by step table. So, if I could refer you to that, take a look and maybe that can answer most of your questions. I know it's a little bit tricky between when to do an exemption to this claim, but whatever it comes down to is. If you already have an existing certificate because of other testing, then you provide this exemption codes as well. If you use those. Thank you. You're welcome. Mark, I see you have your hand raised. Hi, my questions around the contact information for the manufacturer. Could you just explain. Sort of the reasoning behind the rule change and give us a use case of why you would contact the manufacturer. Directly rather than the importer and when that would happen and why it would happen. Sure. So, just to repeat myself, this proposed rule. Is being sent to our commission so it will be published shortly and you have time to comment on it. So. So, the manufacturer information was has been required since 2008. So we're keeping that information, but now we're just asking for the email. And phone numbers, we have some contact information for the manufacturer. And the reason we decided upon this. Some are from our investigators experience. They may review a certificate. Reach out to the importer and they may not be as responsive or just non responsive. So, we would want to contact the manufacturer. We do want specific manufacturer information such the address because. In some in some cases, a manufacturer facility name can be very similar. So we want to differentiate between 1 or the other. I'm not an investigator for says I may not have too much anecdotal information, but. I mean, I could come back to you with better response. Yeah, I mean, that's sort of the thing that sticks out. You know, I think for, for, for me, it's, you know, if I think everybody here that's volunteering, of course, would be very responsive understand that you may have your unresponsive importers, but wouldn't you just hold their goods? If they were unresponsive, wouldn't that be a solution? I mean, that is a solution, but. It's that falls into our enforcement discretion and. It's not quite as easy as just saying pulling their goods. From our perspective, so I do understand that everyone participating here. I mean, you are responsive by participating in the pilot. So. We appreciate that, but when we draft a rule, we have to consider all use cases. And so we consider that asking for a phone and email from the manufacturer is not as burdensome, but it could help us catch capture some bad actors. VJ Gandhi asks, what is the criteria for exemptions? VJ, that's a good question. I would direct you to our web page and there is a document there that provides guidance on exemptions. So, essentially an exemption is something provided in an existing product safety rule. So it really depends on what product you're looking at. And. And like for for me to tell you what the exemption is because there is no like universal exemption for products. It really comes down to each product itself. So you have to review the rule itself to determine whether your product can be exempted from a certain test. Magnets. Yeah, I see that magnets rights are minor adjustments needed for the common. And that you found that he has flagging list or his information is clean be as mentioned for us, but list doesn't allow disclaimer for small rugs small rugs with labeling. I may have to get back to you Magnus on that about small rugs, but I believe. Sorry, I just have to get back to you. I don't have the answer right now. I see Linda you wrote should not the program be for the current rule and regulations out the proposed role. Because we're doing this concurrently. We are the beta pilots. We designed it in such a way to kind of go along with what the rule will be. And to be quite honest, the change from the current rule, the current regulations to the proposed regulation is. Nothing it's not major the major difference would be. I'm requiring the e filing requirements. Excuse me requiring for the electronic filing certificate data in the future. But when it came to the data fields itself, we found that the changes we made or small and more like cosmetic and more for clarifying. What's what we really are asking for in the certificate because it's sometimes it's. In some cases, if it doesn't 8 rules a little bit vague when it came around. Some of these data elements. You have the opportunity to comment on the rule of course. But when it came to designing the pilot and the registry, we figured that we should. Design it for a future case because at this moment, the test is voluntary and we want to, but we want to test it to such a point where it. It's almost in line with what our future thinking is. There's Michelle again, I just have a question. Can you maybe go back to the slide where it talked about updating the manufacturer information. The part that I'm confused about is where you talk about how you have to provide the previous version ID. Maybe it was sorry it was the product go back 1 more. Yeah. Yeah, okay. So, I guess I'm just trying to understand why it's necessary to designate a product as an update and supply the current version ID. If you're just going to give it a new version ID anyways. Okay, so in the, that's a good question. So by providing the current version ID, we kind of link the new version to that current version. So, when you're reviewing the certificates in your registry, they all will be collapsed together. Doesn't the product ID do that though? I mean, yes. No, product IDs do not are not required to be the only unique within a product collection. You could theoretically you could theoretically create multiple entries that share a product ID if they had different manufacturers and there was some reason you wanted to do it that way. Or like, you know, different batches that had unique characteristics. Um, so the version ID is the 1 thing that's required to be unique. So, in order to know exactly which record a user wants to update, we need to know which version of that certificate you want us to make the changes to. If that makes sense. Okay, somewhat. And then my other question on this screen has to do with like looking at row 1, you show your primary product ID type is G 10, but you don't have a value in the G 10 field. So that. I mean, what you're telling it your product ID type is the G 10. Shouldn't you be reporting the G 10. So that you're already providing on the primary product ID to the left. Oh, I see. Okay. Got it. So that's related to the information on the left. Okay. I understand now. So you don't repeat that information. Got it. Understood. I was looking at it from the other like it was going the other direction, but yeah, got it. Thank you. Any more questions? I'm going to take that as a no and just repeat myself in the next steps. Please go to our webpage. I can say that enough. To begin to review the documents. If you haven't reviewed them yet. I feel some of the questions I was asked today can be answered by many of these documents. And also to complete the next steps of. Working for broker software developer on it integration, organize your certificate data with the template that we'll send out shortly. And then also submit that does any business account administrator to us. All right. Cool. Well, thank you again for your time. I'll stay on until everyone leaves. Thank you, Arthur. You're welcome. Thank you.