All right. Good morning, everybody. Welcome. I want to welcome everyone that's attending our e-filing workshop virtually and here in person at the CPSC hearing room. We're really looking forward to today's meeting and being able to walk through the e-filing project, give an overview of where the project is and where we're going and in particular our beta pilot. So speaking of the beta pilot, this is not the last time you will hear this today, but we need you. We are still in need of volunteers to participate in the beta pilot, especially importers, because the importers will be the companies whose certificate of compliance data is filed and that we will use to analyze as part of the pilot. So, as you're listening to the, to the meeting today, please think about whether participation in the pilot would work for you because we really do need you. It's critical. Trade participation in these things is critical. We want to get this right. We want to make sure that we fully test the pilot, the infrastructure, the processes before we move to a final rule and then final implementation. So please consider volunteering. In short order, I'm going to, we're going to turn the floor over to Arthur Laciak, who is our e-filing program manager. Many of you have corresponded with him via email or received emails from him. So he'll sort of formally walk through the agenda and get our, get our day started. But first, we are very honored to have CPSC chair Alex Hoensarek with us today to provide some opening remarks and I'd like to just introduce him very, very quickly. So, Alexander Hoensarek was nominated by President Biden on July 13, 2021 and confirmed by the U.S. Senate on October 7, 2021 to become the chair of the CPSC. Prior to joining the commission, Mr. Hoensarek was chief counsel for communications and consumer protection with the U.S. House of Representatives Committee on Energy and Commerce. In this role, he served as the chief legal advisor to chairman Pallone on the committee on consumer product safety, auto safety, consumer protection, privacy, broadband and other communication issues. During his tenure, Mr. Hoensarek was instrumental in oversight of consumer product safety matters and drafting legislation to increase the authority and resources of CPSC, which we always appreciate. So, chair, please. Thank you and thanks to everybody for joining today, both in person and virtually, I got to meet at least a couple people on the elevator right up this morning. So, I was hoping that you were able to find the coffee and get, get a cup before you came here. But I was also encouraged to see the list of attendees and see the wide range of expertise, both governmental industry that it represents. Because in the current trading dynamic, it is critical for CPSC to keep evolving to be able to best target hazardous products as quickly as possible as they're coming into the country. E filing certificate of compliance is a critical initiative here at CPSC. We get it right. E filing will enable us to target shipments that put Americans at risk. Well, let me step back and allow us to target shipments that are putting people at risk as quickly as possible. But at the same time, allow shipments who have good histories of safety to be able to move their products quickly through the ports. You know, when it's up and running, E filing will improve our targeting enforcement capabilities by incorporating certificates and compliance data into our RAM assessment methodology. And by collecting that certificate information electronically, compliant cargo will be facilitated. We're going to be able to check on the certificates electronically as the products enter the ports as opposed to when a product was stopping shipments and taking a look at it physically. CPSC staff of the ports are going to be able to target substantive violations and look for things like lead and phthalates as opposed to slowing down some of the commerce that we see at times. Doing our job as we need to do it, but without the electronic filings makes it more difficult makes it slower. This is a multi year project the CPSC has been working on, but we've had a alpha pilot already and there's certificate of compliance study and both these have supported the benefits that this project will have on CPSC's import targeting. The next stop after this workshop is Jim's talked about is the beta pilot and it's going to further test the E filing system and inform our rulemaking going forward. Those of you who are industry representatives, as Jim has said, and I think you're going to hear again and again throughout the day, we're going to urge you to participate. And for those who have signed up already, I want to thank you. I think that is very important for the work that we're doing and appreciate that. For those of you who haven't signed up yet, I encourage you to do so and think about it. Because by volunteering, you can have the opportunity to test the filing as well as ability to provide feedback on the PGA messaging set and product registry. As I mentioned, we are going to be moving forward with the rulemaking and this is a great chance for you to have an opportunity to have early input on that process. The more firms that participate, the more we're going to learn about how to make the E filing system work successfully. And of course, firms that volunteer will be able to have a direct impact on the direction that E filing takes. For now, I just want to encourage all of you to actively participate in today's discussion. We want to learn from you. We want to learn from your expertise going forward. And I look forward to discussing the outcomes of this workshop with staff as we discuss where go next with the beta pilot and with the rulemaking. But before I turn this back over, I do want to take a moment and thank the CPSC staff who have been working diligently on this, not only putting together today's workshop. But also, as I said, for years working on the E filing system. So thank you very much. I appreciate all of the work that you've been putting into this. And going back, thanking all of you as well for being here today and for hopefully engaging them in the beta pilot as well as providing more information for us as we go forward. So thanks again, and I'm going to turn this over to Arthur, I believe at this point in time. Welcome everybody. Thank you for joining us in person or virtually. I know for many of you who woke up and saw the weather this morning was probably thinking, why did Arthur select this day of any. But I can't predict the weather 2 months in advance. So thank you for coming and thank you for your remarks chair and thank you Jim for your remarks as well. And let's begin. So just some housekeeping notes. This workshop will be recorded and will be transcribed and it will be. Trans the recording will be available later at CPSC dot gov. Or if you're an in person attendee, please make sure to sign in at the front door. At some point today and pick up any of the papers at the front door. Wifi is also available if you're here in person. Of course, bathrooms and water fountain in the elevator lobby. There is a map for lunch places during our lunch hour. So the agenda on the agenda today, I will provide a brief overview of our history of e filing what we have done in the past and our hopes for the future. And then I'll later pass the mic to our 2 compliance investigators cat rickerson and Hector. Ramirez who will be providing an overview of our current certificate requirements. Then I'll pass the torch to John bless your international trade specialists who will provide an overview of our risk assessment methodology and our targeting efforts. And then I'll go in and provide a very detailed overview of the beta pilot itself. Starting at 11 p.m. or sorry, 11 a.m. We'll have 4 sessions where we'll have opportunities for the audience, both in person and virtually to provide feedback. I'll be addressing for individual topics. The 1st 1, the PGA message that data elements themselves. The 2nd, the product registry features. 3rd, the HTS codes, his claims and exemptions. And lastly, the minimus and directed consumer shipments. I will CPC staff will provide a brief overview of each topic will provide some questions that we would like feedback on or just general comments. Again, you have the opportunity to. Provide comments here in the hearing room or virtually I'll provide directions later later on. And. And you will also have the opportunity to provide any additional comments. Through regulations of I'll provide that link at the end of this workshop. So. Right. So, I'll just begin on our e-failing program overview. You may have heard me at different trade events or at virtual events. So you may already know what he filings all about. But I'll take this opportunity to repeat myself. So he filing is essentially our PGA message set. It is in order to electronically collect the data elements from the certificates of compliance and incorporate that into our risk. Method risk assessment methodologies. So, why are we doing this? So, for 1. As a procedure now. We have now have a we can't use the risk the data elements from the certificates for actual risk assessment and targeting. Our investigators only view the certificates once they place a hold on the cargo and then open up the cargo and request the certificates at that point to certify or verify that the certificates are valid. So, in that case, we don't actually use the certificate data elements, but we instead we want to incorporate that into our risk assessment methodology. This will improve our targeting and enforcement efforts. And as a chair mentioned previously, it will allow us to focus more on substantive hazards instead of searching for certificate violations. And in our book, a substantive hazards or something like lead, phthalates, small parts, sharp edges, the list goes on and on. We want to focus our risk targeting on those elements that show proved to be a physical hazard to the public, especially children. And move away from targeting cargo for administrative violations such as certificates. So by you incorporating those data elements into our risk assessment methodologies will be more precise and be able to target. Hazardous shipments more precisely. Here's a brief overview. So in 2008, Congress passed the Consumer Product Safety Improvement Act, which required importers to test and certify children's and other general use products and provide certificates upon request. That was codified under 16 CFR 1110. This act also provided us the authority to require the electronic filing of certificates. In 2013, we issued a notice of proposed rulemaking that among other things would require the electronic filing of certificates. We placed it on pause for in order to conduct several studies. Also, CBP was not ready at that point with ace. So we postponed that rulemaking in 2016. We conducted an alpha pilot with eight participants that tested the pj message set and the product registry. We found it to be a great success. And we received positive reviews from our participants. The alpha pilot is the basis for the beta pilot. We are keeping many of the same elements the same. And we're just branching off from there. In 2017, we conducted a certificate study that analyzed the risk of potential certificate data elements. In this study, our investigators transcribed the data from the certificates that they collected at the ports incorporated. And then we had a team to conduct some data analysis to actually look at which elements lead to increased risk of a potential violation. We also found that there was increased risk if a certificate was not provided at all. And lastly, our commission in 2020 unanimously approved our staff briefing package to continue with e filing and to conduct the beta pilot. So let me continue and discuss the alpha pilot results. So as I mentioned previously, it was only with eight participants, but we did have over 1200 products in our product registry. There was over 15,000 message sets transmitted into ACE. Most of them were using the reference message set. I will go into more detail the difference between the reference set and the full message set. This was a pilot that lasted six months, which would be similar to our beta pilot and we did result in an error rate of less than 1%. So what we found from the study is that providing the additional data elements did not significantly affect the importer's operations. Participants who chose to automate data collection and data entry did experience an initial it investment, but the ongoing entry costs will were reduced to be negligible on a per product and per line basis. We expect the same results for during the beta pilot. For participants who experienced delays and errors. That was a result in many cases of the code delivery from the software vendors to the brokers. That is 1 of the reasons why we want volunteers to participate. As early as possible in the beta pilot, especially starting from this point on. We have 1 year to prepare for the beta pilot. So the earlier. A volunteer a broker and importer could get on board with us. The more time will have to iron out any kinks and. Make sure e filing is successful. We also found that there were some errors in reference to the reference number from the product registry as it was transmitted or inputted into the pj message set. We're going to take the results we learned from the alpha pilot and incorporate it into the beta pilots. We don't run into similar errors. Also briefly address the certificate study results. As I mentioned, so on these next 2 slides, I will provide you some charts and to provide some background as to why we want to collect the certificate data elements. As a side note, though, you could go to our web page where you could read through the whole certificate study. Report as well as the alpha pilot report. I'm only providing a very brief overview, but there are many more pages on our website cpsc.gov forward slash e filing. On this slide, it shows 2 different 2. Very important risk factors. So for 1, we found an increased risk if a certificate. Did not accompany the shipment and was not received within 24 hours. Or if a certificate. Was never received after being requested by an investigator and that is compared to a certificate accompanying the shipment. So if you see the red line, the first was very low if. Sorry, the risk was very low for substantive hazard. If a certificate accompany the shipment. But if there was no certificate provided that risk increases almost up to 5 times more. Of a greater risk of a substantive violation and that was in the last column if a certificate was never provided. We also found when comparing the manufacturing date and the lab test date. An increased risk. We found that. Certificates with a testing date. After the manufacturer dates were more than 3 times more likely to have a violation. So if you look at the chart on the right. The dark blue is a testing date after the manufacturing date as you can see it. That certificates with a testing date after the manufacturing date counted for over 50% of. Product violations and that is significantly different when you look at the column on the left. Where the majority of certificates with no substantive violation had the man, the testing date before the manufacturing date. I do have to note that this. This is only a factual finding of the study and does not indicate compliance with. Or violation of the commission's testing regulations at 16 CFR part 1107. Compliant testing regimes depends on each manufacturer's testing and manufacturing scheme for which they're required to have appropriate documentation. Staff did not assess whether firms with violative products were otherwise compliant with the commission's testing regulations. To continue looking at very specific data elements found on the certificate. We found increase increased risk of a substantive violations. For certain manufacturing cities, the data here is anonymized. As you can see on the far right or sorry in the chart on the left in the far right there are 2, there's 1 city in particular that had a much greater risk of a potential substantive violation. Although our sample size was small, we still found this to be significant and using the data we will collect in the beta pilot will be able to analyze this. Deeper and try to find a greater correlation. Also related the chart on the right. Whereas the violation violation rates by laboratory. We again found 2 labs that had a risk of a greater risk. Excuse me of a potential violation. So this is very similar to the manufacturing city. All these labs. Although there was a small sample size, all these labs did issue at least 20 certificates during the alpha pilot. And as you can see 2 of them had rates of at least 20% violations. So we do find significant risk there and 1 of the purposes of the beta pilot is to study this more. And then lastly. In December of 2020, the commission voted for 0 to implement the staff's recommendation for you finally. I will go more detail about the specific elements, but it could be broken down into 3 points here. So we are only going to focus on our priority. HTS codes, which is approximately 300 HTS codes. These are HTS codes that. Primarily, the codes. Sorry, these products would be the ones that require a certificate. We'll go more detail later on the session regarding the HTS codes. Second, the determining the data requirements. So the commission agreed that we will select all fields with potential risk targeting value. So these are all the same data elements found in the alpha pilot in addition to 2, which are the manufacturing date and the lab test date. And lastly, we plan to to update and maintain the product registry is done in alpha pilot. When we use that in the alpha pilot, we got really great review. So we're going to continue to use that. Alright, so I'm going to pass the torch to our investigators right there. Kat Richardson and Hector Romero. They will be providing you an overview of the current certificate requirements. Good morning everyone. I'm Kat Richardson and this is Hector Romero. I'm here to talk about our current certificate requirements. The products that must be certified is any product that is subject to a consumer product safety rule ban similar rule standard or regulation. And which is imported for consumption or warehousing or distributed in commerce. These are the items that must be certified. Certific, certification is ultimately the responsibility of the importer. However, importers and manufacturers should have a clear understanding of exactly which standards need to be met. Foreign manufacturers suppliers should insist on a list of mandatory and consensus standards to which they apply. So that's something that we deal with a lot with foreign manufacturers. There are 2 types of certificates. We have what's called a children's product certificate, which we call CPC and a general certificate of conformity, which is a GCC. The CPC is only for children's products, which are primarily intended for children 12 and under. And the manufacturer importer certifies that it's children's product complies with all applicable children's product safety rules, bans standards and regulations. The certification of children's products must be based on the passing test results of 3rd party testing. The 3rd party testing laboratory provides the testing service and results, but does not issue the CPC. That is the responsibility of the importer. For general certificates of conformity, the manufacturer importer is stating that it applies with all consumer product safety rules. A GCC must be based on a test of each product or a reasonable testing program. These are the elements that a certificate must include the identity of the exact product and no others. So we need to be able to ascertain that that product is the product that is in front of us for examination. So it has to be very clear. The part of the party certifying compliance. That could be the importer or the domestic manufacturer. It would have to include the name address and phone number. Then the citations to each applicable CPSC rule of regulation to which the product is being certified. In most cases, there will be quite a few citations that will need to be on the certificate. The date and place where the product was manufactured. So for the date purposes, we need at least the month and year for that. The name of the laboratory along with the place and date of testing. And sorry, and the contact information for the person who is maintaining the test records, which would include name address email address and phone number so we can contact that individual. Pass it over to Hector. Good morning availability of the certificates certificates must accompany each product or shipment of products covered by the same certificate. A copy of the certificate must be furnished to each distributor or retailer of the product. It's not it's not a requirement to provide to the ultimate consumer. It doesn't necessarily need to be a paper copy. Mostly it's electronic. A copy of the certificate must be made available to the commission and to custom CDP UP requests. Third party testing for children's product certificate is based based on testing by independent third party laboratory that CPSC has a set to perform the specific test for each applicable children's product safety rule. And we include the link for that is in our webpage for generic certificate of conformity or GCC is any laboratory and in house or external third party laboratory can perform the testing require. And this is for non children's products. Here you have the list of the products are requiring requiring children's product certificates and products requiring in general, certain certificate. You can see here. And now I'm going to pass to. Yeah. Good morning everybody. My name is John bless here. I'm an international trade specialist with the office. I need to bring this up. I'm naturally loud. So, you know, sometimes having a speaker right in front of me might be. Overwhelming and I wanted to review. What our risk assessment methodology is and specifically. As it involves a filing a lot of this information. Is critical for our targeting and alignment with the exam efforts that our compliance investigated doing out in the field. This provides a lot more information. And as was specified by the chair and others. This allows us to facilitate. Legitimate cargo and differentiate and get much more specific with the. The more risky product as Arthur had identified in our studies. So I'm going to review our system review the overall approach to our response. To the legislation and and. Pretty much the the founding legislation for this was the section 222 of the improvement act. Of 2008. Again, I'm going to read this. We have a bit of time here. Specifically, we're trying to find consumer products that violate health and safety rules. That are not accompanied by a certificate. That are eminently hazard. We'll talk about that in a second. Create a substantial product hazard. Or are from a manufacturer in violation of record keeping requirements. Now, he filing is as was described by Arthur. Specifically, we're looking for those that are going to have mandatory standards. For which we're going to be requiring a certificate. So imminent hazard declaration, which is under our 15 J is not going to be. Those HTS codes are not going to be part of that part of this review process, obviously. And substantial product hazard determination is for our. Non regulated products. So those are not going to be addressed under E filing, but he filing addresses our capability to do the 1st to. And the 5th 1. So. Now under 222 within the required legislation was the statement that we need to. Work with customs and border protection, their itds effort international trade data system effort. Which is the health and safety agencies, how we are going to line up with the ace modernization over time. We need to make it part of our it modernization effort. So, as we modernize our tools within the agency, as we work through our systems development life cycle. We are going to be, you know, integrating a lot of these efforts as best we can depending on funding. And capabilities at the time. And then we need to work with. CBP as well as the trade community. And as well with other PGA's and trying to identify the best ways to. I find those and examine risky shipments. So the philosophy behind the overall risk assessment methodology. I like to summarize as total risk management at import. It's kind of. Catchy at least in my mind that what we're really trying to do is to monitor the overall importation of goods coming into the country. Okay, so the expectation is through the monitoring of the shipment activity by product entity. And port region. So what we're looking for here is good product identification. Specific entity identification, which can be challenging and the current environment that we're in. As well as knowing where and when the product is coming in. We want to be able to get to the appropriate product. We also then match that up with our violation history on the same thing. To be able to optimize our folks responsible. The idea is if we understand the risk at the ports by certain actors for certain products. We can spend our time in those areas and avoid others that are that are lower risk. Some product areas that are great examples here. Our all terrain vehicle product area the program that we have. There's only so many people that are importing those into the country. We do recognize the importing community. We are able to review that importation regularly with them. And if others bring them in, we recognize who's participating with us through our ATV program. And so in that instance, the ATV is not only are they managed in terms of entity, but they're managed very well in terms of the HTS codes that are declared. We got that under control back in 2011 when we worked with the ITC. US ITC to to segregate those out and have those declared separately from small vehicles. A high complexity area is toys. Everybody's importing toys, you know, grocers are importing toys. Every store that you're going to have is going to have toys sitting somewhere. I was just at the at the food market the other day.  Everybody's got them. Everybody's bringing them in. And there are tons of manufacturers. So the product area itself and the wide range of types of products and risks that are being introduced based off of the toys makes it a tough area for us to as an agency control. So that one's more of a, we have to have a different methodology than we would for ATVs, for example. I think our audio issue has been solved. Knock on wood. Okay. So when we think of an overall risk assessment program, I want to look at the big picture and introduce you all to the big picture here, which is that we have to have in place memoranda of understanding with with agencies for which we're working with. For example, Customs and Border Protection. We have to tell them how we're going to work. We have to explain to them our expectation given our jurisdiction for the information that we collect. We have to work with them to optimize the situation so that they get the best response from our work that they can in cooperating with us in terms of seekers and working on those violations. So these memoranda of understanding are important and we keep them up to date as best we can and as required. Another component is that we co-locate staff. You've got to hear from Hector and Kat, who are co-located at a couple of our ports. We have many folks across the country working at the largest ports. That's the operational component and it's our need to get the information to them adequately and timely that this effort is really trying to help optimize. And this is one of the components necessary for that. Ours is a different flavor, but many other health and safety agencies are utilizing the same technology today to be able to get the information that they need on documents. We are just operationally using the information in a potentially a different way, a little bit more like an FDA model per se. And then we have other improvement projects that we work on within our overall risk assessment methodology. They include trying to understand those darn HTS codes. I don't know if you've gone through that 3,000 page monster, but they update them, they change them all the time. It's called master data management, the overall area for the product area. But that's one element of just trying to make sure that our jurisdiction and our risks are cleanly identified as much as possible and trade in terms of notification that these are the product codes that we really want. And then you can expect these products to go under review at a high rate or at a medium rate and we'll try to stay, you know, out of the way for ones where it's under our jurisdiction, but we don't expect, you know, products with mandatory standards to actually come through. So I want to highlight one of our gems of cooperation that we've got here at CPSC, which is our participation at the commercial targeting analysis center. We have an effort which we are meaning. We were the first agency to sit down with CVP at the CTECH at the fusion center. Through that fusion center, we have access to additional information to help us understand what's going on with the high risk areas, but it also allows us to better study process improvements like e-filing. So we'll be using some of this data maybe to help us in retrospect double check the information that's coming through. Recognize that through that mechanism, we're targeting using CVP tools and we're using automated targeting system at CVP to get at the worst defenders and to be able to work in areas where we're trying to be prospective, trying to get improved control in certain product areas. So you'll see some CPSC stops coming straight out of ATS that are going to be potentially the messaging is going to be a little different than what you would have coming out of our own system. We have co-located staff, which we've talked about. They are on the ground and in hand with CVP will not holding hands, but hand in hand next to, you know, working together getting to those shipments where they're doing X-ray fluorescence phthalate testing. They're doing mechanical use and abuse testing physical assessment. They're reviewing documents and they will collect evidence, investigate local and you will hear directly from them as needed to conduct examinations. So when we talk about certificate review, e-filing, that's going to obviate potentially some of the requests that you would get and some of the delays that you would get for people asking you to provide certificates at the time. If you provide it electronically, we don't necessarily need to see the paper if everything's lining up. That being said, there still needs to be a certificate, you know, attached until otherwise stated. We actually call the ITDS RAM system. It integrates our available risk information to model and support commission enforcement strategy involving product hazards and importation. So we're collecting shipment information directly from CVP. We have our own CPSD case history, the violations that we work through that actually tell us what product areas are having problems coming into compliance. We have importer entity issues, you know, in terms of lack of control that's being expressed by that company with respect to certain product areas. That type of information we have available. We align with CVP as best we can through their case history information as they make it available. We'd like to get more, but, you know, that's something that's going to take time. We also review based off of screening history. If we see that a product coming through an importer is tested clean five or six or ten times, we don't want to see it again. So, you know, that will feed into the model. Injury and death data right now indirectly inform our response. We get that information. We process it through and we prioritize internally to be able to review what products are causing injuries and deaths. And we go after as best we can and as timely as we can prioritizing those products forward with you at importation. And then the commercial information, some third party information that we're looking to bring in would be GS one product code associated information, Lexus Nexus information. These are going to be product areas that can better specify the product that's coming in better identify the companies that are involved and support additional risk. So the system itself, these are the mechanisms that it uses. We do statistical modeling to prioritize project and operations. We provide reporting out of the system to be able to let managers and staff know what's going on. How are things going in terms of your ports in terms of these products? How are things lining up? We have a, I would say a state of the art graphic user interface that our folks can actually interact with to be able to provide timely feedback directly into the system back here at headquarters. And to be able to manage how they're working through entries as they're doing their exam as well as logging the results as quickly as they can in terms of screening. And then the Ram methodology also provides a systematic review and prioritization of products of interest as I've already highlighted. The next couple slides are just going to highlight the general methods and provide kind of some graphics that let you know what the system is actually doing. So in this instance, this is how we're coordinating with CBP utilizing their tools. I'm not sure if the graph of the graphic can be well read. This is a standard one that's been out there since since, you know, 2010 2009 brokers as the brokers file the information through and through e filing additional information will be provided by the brokers to inform us of what the product is that's coming through. It gets fed directly into CBP systems, which through we have a direct connection which collects that information from CBP ACE, which feeds our methodology, our data system, which then our inspectors get to look at that information directly off the system using the GUI. And through pre planning, which is at the top of the chart there. They can do localized targeting. There's national targeting gets coordinated through the system. And then we know where targeting has not been specifically identified for the day for activity. If shipments come through that the local port inspector is interested in reviewing they can indicate that directly through the system. They notify CBP not necessarily in the mechanism shown. They don't hand a piece of paper, but really what it is is there's direct notification system to system that we're working on this shipment and that we want to coordinate. Then when CBP and CPSC come together, the examination occurs, we do screening, we will package the sample, send any samples that are collected to be found problematic at screening. That gets sent back to our labs for review and testing for confirmation. For the majority that screen clean and we're at about 88% of what we end up examining being clean. Those get sent right on their way. Those that we don't get sent right on their way. They get loaded on the truck and they're off to be distributed into commerce. So this is our general high level view and my last slide here. I want to highlight specifically that it actually is a relatively simple set of steps that we're doing. And E filing is a key component that helps us to identify and differentiate the blue, which is what do we want to examine. Improving the specificity of the product that's being provided and getting direct linkage and identification of the product that's being imported. We can track much better to our history and make better determination on what needs to be examined and get that. Rate of work that we're doing at 11% 12% being sampled up to 15 and 20. And us not touching some of the ones that are in the 88% and saying, hey, we were able to see that that was cleaned through information. We're just passing that on through and so recognize that that the less we're utilizing getting our hands on it in the top. The less time is being spent working on legitimate trade. The faster it gets out into commerce and do recognize this initiative is a critical one for us to get right and will yield. Rate results I think in the long term in terms of CPSC getting out of the way for legitimate trade and getting to more product and optimizing the time of folks like Hector and Kat. This diagram is also one that's out there in the public sphere. Feel free to utilize it. And if you have any questions, these are in a high level that the steps that we utilize and we can talk about each and any of these as you need. So I'll provide a brief overview of the e filing beta pilot. So I'm going to give it like a very quick rundown of essentially what we are planning to do. So the agenda and after we do, after I provide this overview, we're going to lead into these into four sessions discussing specific points about the beta pilot. The first one being the PJ message set data elements. The second, the product registry features. The third, the HTS codes, disclaims and exemptions. And lastly, the minute the minimists and directed consumer shipments. So on those last four bullets. Those will be the opportunities where you and the general audience in person and virtually will be able to provide feedback. So the beta pilot is set to begin in the fall of 2023. We are looking for approximately 50 volunteer participants and this pilot will allow us to test the PJ message set with many more entry lines than in the alpha pilot. Primarily, we're looking at testing the implement implementation processes and procedures on our end and also on the end of the filer. So the broker or importer. And when I say we're looking for 50 volunteers, we're looking for both brokers and importers to participate ideally together because we need to test the PJ message set with real data. So of course we need both both parties working together in order to test this. So how we will, how will CPSU use these beta pilot results. So first of all, it's a scale up our IT systems to be able to accept the data on regulate regulated consumer products. Second to refine the required infrastructure for real time collection. So that means. Receiving that data from ACE incorporating that into our RAM, which John just spoke about and making sure that infrastructure works. Also, we want to test the capacity making sure we have that that infrastructure when it's built out and once you filing does become permanent that we have the appropriate capacity in order to collect all the additional data. We also want to test internal external procedures to supply use and maintain certificate data that would be working with you the volunteers making sure you are capable of obtaining that data in an electronic format and submitting that through your ABI via ACE. And we want to test that with, of course, different product categories, not just children's products or toys as you saw previously. As Kat and Hector did present that there are two different type of certificates and different requirements for different products as you compare general use products to children's products and even within children's products are different regulations. So, so my, so when I'm looking for volunteers, I mean any of you live here in person or listening virtually. If you import consumer product, please volunteer with us. That's my plea. We're trying to get a pretty broad group and diverse group of importers and brokers to participate. We're looking at any importer of any size. You don't we because when we test the beta pilot features, we want to make sure everything works, not just for the biggest importers and brokers, but also the smaller ones who may have smaller teams. We want to make sure the participants are able to collect the certificate data. It is a requirement to have the certificate, but there's, there will be the additional staff to make sure that it is electronically available. And we want to again test it with different consumer products under our jurisdiction, not just for, you know, toys, for example, we want to also test it for mattresses or ETVs, for example. And lastly, this will inform our rulemaking. We do plan to make e-filing permanent, but that will be well after the pilots. And how will this benefit you industry? The probably the most important question of the day. So this, as I said, will improve risk assessment enforcement and trade facilitation on our end. We as e-filing becomes permanent, risk scores will decrease for importers who electronically file valid data elements, resulting in fewer examinations of cargo at their ports. So to repeat what I said before, we really want to focus on substantive violations. We want to shift away from targeting for certificate violations. And so by collecting this data and ensuring that the certificate data elements are valid when filed at entry, we'll have, those of you who file valid entries should expect to have lower risk scores, which results in fewer exams at the ports, fewer days held at the ports. And just, and if there is a hold done, it would be for a substantive violation. So we are, here are the seven data elements that we are collecting as part of e-filing. Most of them are very related to the requirements of the certificate. Later on, I'll go into more detail about the specific data elements. And as I mentioned previously, these are the same data elements as in the Alpha pilot in addition to two. We are collecting, of course, the identification of the finished product, which would be a product ID number, which could be anything that you as a filer would like to use, something like a model number or skew. I'll discuss that in more detail later. Each consumer product safety rule to which the finished product has been certified. The date when the finished product was manufactured. Again, that would just be the month and year. The place where the finished product was manufactured, produced or assembled. The date when the finished product was most recently tested for compliance. The parties on whose testing certificate depends, which would just be the testing laboratory. And lastly, a check box indicating that a required certificate currently exists for the finished product. Again, these are the same elements from the Alpha pilot, but we are not requiring two elements specifically. We won't be collecting specifically the party certifying compliance because that information we could get from the entry documents and also the individual maintaining the records. The last item, which is new, which is actually not on the certificate is a check box. That is just an additional requirement that the filer is. They're excusing that the filer is in compliance with section 14 and 17 of the consumer product safety act. So to provide an overview of how this will look. I'm going to start with option two at the bottom. So the importer or broker has the option to file all seven certificate data elements via ace directly and that will be processed into our Ram. The other option, which includes a product registry, the importer will file those same data elements into the product registry. We want to use the product registry. We actually encourage and we found that like 99% of cases of product registry was used during the Alpha pilot. Because we find that the importers and brokers, of course, if they're bringing the same product over and over again during the same year with the same certificate. Why file the same data multiple times instead use the product registry. You filed that data once and then you incorporate the product registry ID number, which could be any number of your choosing something like a skew or model ID. Something that's easy for you to maintain records of and the broker will file that information via ace. So in that case, we're really only talking about one data element filed at the time of entry and that data will be incorporated into Ram. The product registry is something that we CPSC will develop and maintain. And I'll go into more detail about specific features about the registry and we do want feedback on the registry itself during during the pilot during this next year of development and the pilot itself. So that is another reason that I'm asking for volunteers in order for you to participate and provide feedback on this procedure and the product registry itself. If you use foreign trade zone, sorry, excuse me, foreign trade zones. The PGA message set would be filed at the time of entry. So when you use form 3461 and not when entering the foreign trade zone, but we would encourage to use a product registry. In that case, it would be easier for your for record, record keeping purposes here. Can you hear me? Okay. Okay. Okay. Later. Thank you. So the timeline here. So in this beginning now we will begin it development. As I said, next fall will fall 2023 is when we begin the beta pilot. So starting this fall, we'll have development during the next few months. We'll receive it or a feedback from the volunteers. And in the spring of 2023, we will finalize the development of the PGA message set. The summer of 2023 would be testing of the message set with a first fake data and then real data and then volunteer volunteer onboarding. Once the pilot begins in the fall of 2023. And throughout the six months process, we will receive iterative feedback and the pilot will end in the spring of 2024. And at that point, we'll begin the final rulemaking, which we expect to complete at the end of the year 2024. In the next few months, we'll begin developing the catare volunteers have the opportunity to provide feedback on the catare. We'll be using the alpha pilot catare as a base point for this. As I mentioned before, the beta pilot is heavily using features from the alpha pilot. And copies of the alpha pilot will be distributed to the volunteers who participate and they'll be encouraged to provide feedback. And specifically regarding the PGA message set development. So from essentially starting now into February is when we're us working with the participants will develop the initial draft the catare. A draft version that will be mostly finalized by February. Between March and May, that'll be the time for CBP to develop their the PGA message set and also for the software developers to develop their software for the message set itself. June to August would be certification environment testing. September will be production environment testing. And lastly, in October, that's when the beta pilot will begin. So if you're interested in participating, of course, if you are in the room here in person with me, you could always stop me and ask to participate. If you are virtual, you could email you filing pilot at CPSC.gov. We are looking for importers to volunteer, but of course brokers, software developers and labs are able to participate by dealing with an importer so we could collaborate together. We are also seeking a subset of nine volunteers to participate in the IT development process. So at this point, we are actually ahead of schedule so I would take a break at this moment as per the agenda and that will give us enough time to make sure we have all the WebEx features ironed out before we begin our next session. So, yeah, take your time. And, okay, as we continue on, we have about half an hour for any questioning. If you are here in the hearing room, please just raise your hand and and to my right will pass a mic to you. Please speak into the mic so everyone here and online can hear you. And please present your name and the company you work with. If you are attending virtually, you could type your question directly into the Q&A feature. Please include the company you work with. So we have the record of that cat here will read your question to me. If you would like to and you're attending virtually you can speak up, please select the raise your hand icon. And at that point Hector in the back room will select you and will select you and unmute you and for that period of time you'll be able to speak after you're done speaking, you'll be muted again. Again, please provide your name and the company you work with before you ask your question. This is the first time we're doing a hybrid workshop like this. So please hold tight and thank you for all your patience earlier today. So the floor is now open for questioning. Oh yeah, my colleague John here gave me a good recommendation I should have introduced my team here in front of me I forgot to do that early this morning. So, of course, you heard John, our international trade specialist speak earlier today, Jim Jiholsky, the director of the Office of Import Surveillance. To my left is Andrew Rucker Yarosh, who is the supervisory management and program analyst for our office. You already met Kat Richardson and Hector Romero. Hector is in the back room. And Mary House is our attorney and Anne Hamilton is one of our new staff members at in our office of import surveillance. Now I will open the floor to questioning and I will begin with Michelle back there. Hi, good morning everyone Michelle Pierce. I'm with Ann Derringer and we are a customs broker. I actually have three questions if that's okay. Question number one. You would mention something earlier about the certificate or someone did in their presentation about the paper certificate. Is the paper certificate still needed if the information has been e filed? Is there still an expectation that it's going to accompany the goods? Mary, you want to take that question. Can you guys hear me. So the statute requires the certificate. So that is an open question. It depends on what the final e filing requirement is. So if all of the data elements are collected, then I think through rulemaking, we could say, yes, that satisfies the certificate requirement. If we were to narrow. The requirements for e filing. You would still have to have all of the data elements. So it's an open question. Something that we will. We're testing in the beta. We're giving most of these certificate data elements. So through the rulemaking, we'll have this discussion. People will be able to comment. We'll take in the information. We'll take it under advisement. But that's a possibility. If we have all the data elements, then. Through electronic means, then we may not need. Anything else. So you're coming about the narrowing of the debt elements. Are you considering then not taking in all the data man? Not taking out data pilot. We're going to be doing a rulemaking. People may have comments. I'm not saying yes or no. I'm saying we're testing it. That's the purpose of the pilot. Sure. That's the purpose of the rulemaking. So. We're, we're, we're thinking about it and testing and that will be determined at some point. Okay. I understand. Thank you. My second question will if filing become mandatory, you know, we have some agencies where like FDA, yes, it's mandatory. You don't have an option, but then you have like fsis where it's an either or. Yes, we plan to make it mandatory and. But we don't plan to do the final rulemaking until after the pilot is complete. So lessons learned from the pilot could be incorporated. The estimate now is end of calendar year 2024 is when that final rule be sent to the commission. Okay. Understood. Thank you. And then let's talk about the HTS, the 3000 page beast that John mentioned earlier. Have you guys completed your combing through of that monster and have you determined which tariff numbers will or will not be possibly disclaimable. Has that work already been done or is that something you're still working on? Used to these. Oh, no, that came through. Okay. So, Michelle. It's going to have to fall within the 2 a messaging construct that we have in place. So, it will be a subset of those HTS codes in terms of the HTS codes that will be part of this. We have to decide how we're going to. Get a reduced volume for the test. So those HTS codes while they are a full 300 and plus set used for 2 a messaging is identified. We have to pick a subset and how broad that subset would be for the test as compared to full production has not yet been determined. Okay, so it's not going to be open to the I've got a list of HTS. We have a list of HTS codes. We don't know yet how we're going to feather this in terms of the test. So there's only going to be certain products allowed in the test that fall under that subset of HTS codes. Correct. Okay. All right. Thank you very much. It will be the subset will be close to the codes you're ready to target in Ram. But we still have to go through it come through it because there's some HTS codes such as like hairdryers, for example, that are targeted in the Ram. But won't be part of this pilot because hairdryers don't require a certificate. So we're going to finalize those details. Okay, so you guys you do then have products where you target but will not be part of this. Right. So there are products there are products for which we do not work. There are products that we target for hazards for which we do not require a certificate. So a great, a great example would be an adult hoodie that if the hoodie comes in. We're looking for children's hoodies for the potential of a drawstring violation, which would be a 15 J. We've got a lot of product codes for which the strangulation hazard can occur on the on the children's hoodies that we're looking for. In those instances, those HTS codes would would not be part of the filing because we're not collecting certificates for those. And if we're as part of the construct going to go any further than just the 15 J that's I think for the team has to make a decision if we're going to go and do a subset of the ones that require certificates. I don't I don't know at that point. Now, now previously we've been unable to obtain a or you've not provided a list of the HTS codes that you guys we will you okay I was going to say I saw a presentation at Westcon where it's had said there was a link to where you could find the HTS codes right. So that link is only to the product categories. Okay, so far we don't have the list of HTS codes published yet. Okay, we will as part of the pilot. Okay. So you on our web page you can find this categories also that nice slide that listed in like type eight font, those are the products that we would include in the pilot. And in the FRN, if you look closely one of the footnotes it does list all the product categories. We will address HTS codes and this claims and exempt exemptions this afternoon so. Okay, perfect. Thank you. I have a question from Adam Lee's geodes which is a customs broker. It says your presentation showed a list of products requiring certs of conformity, regardless of whether they are children's products or general products. Will this list be constant or will it change periodically as new products are identified by CPSC for targeting. Okay, so I'm going to repeat the question. This was from Adam Lee's from geodes regarding that same list of products. His question is, is that list going to change over time. So those lists of products, especially general use products have been identified by the commission requiring a certificate. That list will only change if there is any rulemaking or any decision made by the commission where a product would need additional certificate. Just momentarily. That so in terms of the identification of the products themselves. What Arthur said is absolutely correct, but do recognize that we are not in control of how those get classified in terms of HTS codes. So do recognize that as HTS codes change. The commission has to be able to change the HTS codes that align to this requirement. To be able to hit those products that are part of the certificate. Effort, so the e filing effort, so do recognize HTS codes can change. But in terms of legally what's going to be happening. You have to have a certificate requirement for the product group. Then we have to go get the HTS codes. Those HTS codes can change independent of any types of, you know, authority concerns as well. So do recognize the HTS codes. We'll change a little more often than that asks and in conjunction with Michelle's question about HTS codes. Will you be flagging them as other agencies do. Yes, we plan to. Hi, I'm Diana guild with FedEx trade networks. I had a question regarding the product registry ID. You'd mentioned the importers can go online and register their products there and then they could provide a product registry ID number to their broker. Will that product register ID be the entire e file data set or will it just be a portion of it. So with that product ID. When we input it into ace with that take the place of the full message set or would it be in addition to the message set. No, take the place of the full message set so that reference message set would be shorter than the full message set. So there would still be some data elements they would. So for instance, if the manufacturer varied for the product or the date of testing, they wouldn't file separate project excuse me product registry IDs. For each manufacturer of a product, they would just fill that in in the message set. No, those products that they have different manufacturers would then have to have different certificates. Okay, so the reference number. Yes, so for instance, if you had a customer that was importing a certain toy, but sometimes they have it manufactured at one facility, sometimes at another. Is that information that they would be putting into the message set as opposed to the product registry ID. No, if they enter that into the registry, because the registry will request the information that the manufacturer the lab so that differs that importer have different certificates for those. So they'll have two certificates for those two different products. And so when that is filed a certificate will be filed for each product that comes in. Okay, thank you. I think I have another question. So for each unique combination of product testing date manufacturer result, you know, certification would need a separate certificate. Right. So there, there isn't going to be any sort of crossover. Right. Yes, for purposes of e filing and I was actually going to address this later. Because of how data has to be entered into the registry. We find it only possible that you have a unique certificate for products if there's a substantial change such as a different manufacturer or different lab or date, you have to have a different certificate. Later on we'll go through the product registry features and we have some ideas to make copying and versioning control easier on your behalf and we will like input there. We, I would say we you only have the same product like multiple products on one certificate. If it's very similar like the same model and all the information is the same including the citations. That's right. That's what's happening now. Most people are doing separate certificates and there's we've provided guidance. And so it really shouldn't change that much. I think some people maybe group things on a certificate. But I think a lot of people already understand when they need a new certificate. So it shouldn't be a huge, a huge change for people. Back row. No, back row. Ryan Redford from Amazon. Similar to that, if multiple importers are importing the same product, same manufacturer, probably the same certificate, could they potentially both use the same reference number to that registry entry? I'm not quite sure how we would approach that. That's a really great question. And I think that's something we have to work out before we test in the beta pilot. I think my concern in that type of a situation ends up being the importer control of their product registration records that are in the database. So if you have multiple importers importing the same product, somebody is going to have to be responsible for that information. So the question is going to be who's managing that data within the registry. Right. I mean, technically, the importer is responsible for that information. We have a rule. It's 16 CFR part 1109 that allows an importer to rely on another party's testing and it even allows them to rely on another party certification if they take certain do care concerns. Like they can't just willy-nilly copy somebody else's certificate. They have to ask questions beyond that and the rule lays out what's required. They have to have access to the testing data, access to the underlying information and ask the right question so they know that's right. So each importer would have that responsibility and that's what you're certifying to. So I would expect even if they're relying on the same data that they would be independently certifying because they're saying, yeah, I looked at that information. They're making that affirmation. So even if it looks the same, each importer will be responsible for making that affirmation on their own. Avenue where maybe the manufacturer would be the one to complete the product registry and then supply that number to their importer. A manufacturer could certify, a foreign manufacturer could certify a product, could provide the underlying testing under part 1109. What I'm saying is the ultimate person who's certifying is the importer. So they could have mass data, but the person who's on the hook for that is the importer who's saying, yeah, I checked that information and it's right. So they're the person who's certifying there on the on the hook, so to speak, if they're relying on a third party's information. They have to look beyond it and make sure it's accurate. So potentially more than 1 person could rely on a manufacturer's testing and certification another person's right as long as they take due care under our regulation at 16 CFR part 1109. Okay. Okay. Thank you. Is that better? Okay. So let me start all over again. Hi, I'm sumo rock with FedEx trade networks. And I wanted to ask a question about the timing of the filing of the message set. In, in one of your slides, you had mentioned that the message set can be filed at the time of entry or at the time of entry summary if entry summary and entry occur at the same time. So my question is, are you looking for the PGA message set to be filed prior to arrival at the time of arrival, or are you even willing to accept it if it's after arrival. So, Mary, you can make correct me, I believe, per our statutes, it says we could request the electric filing of certificate within 24 hours of entry. Yeah, maybe a little bit different. So we interpreted that entry entry summary. So when you file your entry information, we asked to also submit the message set information. Right. So, yeah, so it's possible that the goods could have arrived. Like the day before that the entry or entry summary is filed by the broker. It's also possible that the goods could have arrived. After the broker files the entry entry summary prior to the arrival of the goods. So does, does arrival of the goods mean anything to the. The arrival. In terms of the review for the exam process recognize that the data needs to be able to be reviewed by somebody that's in the field and it has to be able to be reviewed by the system. And so if the product arrives and then entry is filed after the product arrives, as you're stating, we're still going to need that window of time that's under the 2 a messaging. That's going to state, hey, we're reviewing this, this data. This is going to be data that's reviewed. Now it's not just entry. It's going to be entry plus these data elements. So, the, the windows are still going to be in effect that we've got within the 2 a messaging environment. So, in an air environment, it would be 8 hours after the ladder of entry or arrival. So recognize that that if entry happens after arrival, you still got 8 because we haven't gotten the data yet system hasn't reviewed it. And our folks haven't had a chance to say, hey, the products here. I want to I want to look at it now. So we need that capability to have that window to be able to say. Oh, yeah, that lab isn't on the list. The system said it's a problem. I want to get on that exam and get on that product before it before it disappears. So, to be able to have those eyes, we need to be able to see the information. Okay. All right. Thank you. Linda Rothfield, Ikea purchasing. I have a follow up to that question and it actually relates more to the release of when CPSC will release the merchandise. Typically, PGA is released during the same period of time customs releases, which is 5 days prior to vessel arrival. Will CPSC do the same? Yeah, so CBP releases before the product gets in the country. I think that we have to still evaluate CPSC's response. And the 2 a messaging can, as it matures, decide if we're going to provide release prior to arrival based off of entities. You know, compliance and history. We don't have that in the books right now. Okay. Thank you. But that is something for us to evaluate. And I think as part of the beta, that's something that we can improve. You know, over time is, is try to give more for warning of clearance for certain entities that prove to be not problematic. Something like that. Yeah, we're not going there. We're not using that. So, so that language is something that we're going to let CBP utilize. They need to develop that program over time. I think you can think of it more if the data supports it, the analytics support it, the system will identify as, you know, a preferential type, type situation. I recognize that CPSC, and I'm just reiterating this. We have domestic authority if there's ever going to be a concern, even for a trusted type scenario or preferential type scenario, we can always get to the product to examine it. At the time that I mean, when it's in the marketplace, we can always follow up if we need to in those environments. That a may proceed in the important environment does not indicate a statement of assurance that this product adheres to health and safety standards. It's only an indicator that the, the, our review period in an automated fashion has been concluded. And we always have the capability to go in after the fact in the domestic commerce to go and evaluate product and evaluated at a later date. As another question relates to a unique situation with FDA, Food and Drug Administration, where they have line level holds instead of holding the entire container, a particular line on an entry is held. And that container is allowed to customs clear moves off site to the imported premises for inspection by the FDA officer. Will CPSC consider something similar? Okay, so I'm going to say my piece and I think Jim and others may have to add to it. We indicate on a line basis, whether something needs examination. It's CBP's difficulty and challenge with the importer and broker to designate whether they need to break out that product and segregated for examination. That's more of an operational question I think for CBP than it is for CPSC. We will indicate it on a line basis and it's that product. If you can map that product to that line and we're going to be able to do that much more effectively through e-filing. You're going to be able to tag that model number and we're going to be able to say now much more definitively at the line level. It's that model that we need to be able to look at in those instances when we indicated a line level that that's what needs to be held. As long as that model is what's being stopped and segregated the rest of it can go. That's a CBP problem and I don't know how FDA solving it. Others can speak to this operationally. I guess I would just add that as a small agency with very limited resources, our sort of operational model is to do the exams at the port. So I think I would say that we will continue that. I think we would like to be as efficient as possible with targeting at the line level. But when it comes to the exams themselves, I do continue to see them being done at the ports and probably in a very limited situation would they be done at the importer's premises. Okay, John, let me just add. I'm sorry. Did you want to we have a few more questions and it is 11 o'clock. So just one follow up statement just real quickly right now the way that it's working just because we don't know where the product ends up sitting. While we do indicated at the line level, the whole entries getting impacted in terms of examination. We recognize that that's a problem and sometimes examination of the product within that entry ends up yielding violations and other products other than what would have been on that particular line. But due to the lack of mapping, you know, hopefully he finally is going to help the situation. I'm going to go to Kat. We have to quit more questions from our virtual attendees and then this gentleman will have the last question before we go on to the next session. I do want to remind you if you look at the agenda, there is a time for open forum at 315 today. So if you have any more questions, please hold them till then. Go ahead, Kat. One of the questions we've received is, is it possible to add more than one third party lab information in one children's products certificate? Yes, it will be possible. And I'll discuss that later on. And the second question I received was, if a certificate is reused, then can you just send the certificate number in the PGA message set instead of sending all the details for the product? Yes, that's the idea of the registry that the importer will bring in same product with the same certificate. So you're able to reuse it until to the point where you have to do retesting. Therefore, you would have to issue a new certificate. Let me add to that though. If you file the full message set on a shipment and you're not using the registry and you're not indicating the registry whatsoever, filing a full message set and then two weeks later you're importing the same product. If you're not using the registry, we expect, we expect a full PG message set again. You have to use the registry and you have to manage via the registry for us to be able to use that optimization of just using the certificate number. So I wanted, I think that answers more fully the question. Hello. Hi, my name is why I'm from IKEA. I have a question regarding to the information and certificates. Would it be an issue if the certificate or the information that we sent over to include additional citation that's not applicable to the product. So for example, it will include citation for children's product, but the product is not a true product. Yes, so the certificate when you list the citations and you are essentially as the importer certifying that this product was tested to those citations. So you shouldn't add any additional citations. So if we, so for a non children product and then we put the citation. So, so what you were saying, you tested that non children product to that citation. Yes, you could do that. Yeah. So anything on the certificate, your certifying was tested to that citation. Okay. Thank you. You might be making a risk. That's the kind of thing we're going to test in the beta pilot. Those kinds of things we're not expecting because if it is a children's product will be expecting certain things and it's not a children's product will be expecting certain things. So it, if that, I don't think that happens a lot, but if it does, it might confuse things a bit. I mean, just a piggyback on that is if you're going to add a citation for a children's product, we're going to be looking for an accepted CPSC laboratory that's done the testing to support that. So, you know, you just would need to think that through completely in terms of all the additional information that may be required. All right. Well, thank you. I will continue on. I just like this question and answer period worked out successfully. These were the directions or it's so not going to repeat myself and I'll continue. So the remainder of this time, it's divided into four sections, as I mentioned earlier, there will be a few slides presented, and then there'll be another period of comments questions regarding the slides I just presented. The first session is regarding the PGA message set data elements. So, first of all, the first element is the identification of the finished product. So we, it should be a unique ID that would be provided by the filer. We would allow for options such as the G 10 the UPC skew model number or any other identifying number, but that would be the responsibility of the filer to keep track of that. That's the idea is here that when you file in the registry, use a number that you are easily able to keep a record of, we won't be providing that ID number. The G 10 in the future CPSC hopes to connect to GDSN and if provided G 10 be able to pull that data from GDSN incorporated into our RAM, but at this moment we don't have those capabilities. So if you're using G 10, you would still be required to file the certificate data, at least during the pilot, if things change over the next year, we will of course keep you informed. The next bullet, as I mentioned previously, one product per e-filing certificate. This is due to the nature of the product registry itself. It will be in purposes of data quality and IT development, it will be just much less complex to only have one product per certificate. As Mary mentioned, most importers already do that. We would allow multiple models as long as all the certificate information remains the same. So across the board, like the lab, the manufacturer, the dates, etc. So if you have two products with two or multiple models that are very similar, just maybe a change in the color or something, but everything remains the same, they could be on the same certificate. And the party certifying compliance is always legally responsible, even if a third party test laboratory or another third party such as a manufacturer helps draft a certificate. Also related to what Mary said earlier, if you're using certificates from someone else, you are certifying the compliance. You can also use parts certificates and incorporate that into your certificate, but again, you are the one certifying compliance on that certificate. There is additional guidance available on our website if you go through a small business and Budsman page. Additionally, the party must, the party certifying compliance must respond to CPSC's request within 24 hours. And although this has been our process for now, although that has been our procedure now that the importer is the one responsible, we would like your feedback whether any other party should be allowed to certify compliance. Next, the contact info for individual maintaining records. This information actually not to confuse you, this is required on the certificate but won't be required for e-filing because typically we contact the broker if we are looking for the individual maintaining the records. So, I'm not a good, excuse me, so typically on the certificate, you're required to provide the individual's name, address, phone and email. And it could be just a position title for generic email, but the individual must respond within 24 hours. Again, though this information won't be required to be e-filed, but it's still technically statutory required on the certificate. Next, the date and place of manufacturing. For the date, we only consider the month and year because we understand that sometimes products are created in batches over several days or weeks. And in that scenario, we only need this start date for the certificate. For the place, it would be, of course, the identity of the manufacturer, including the full address, phone and email. Next, the date and place of lab testing. So, the date would be the month, date and year. And for products tested over several days, we would require only the last date, which is different from the previous slide. So, for your manufacturing date, it would be the first date. The lab test date would be the last date. The place would be the identity of the testing lab, including full address, phone and email. Since we at CPSC accredited third party labs, we also have an ID for each of these labs, which you could find on our website. In that case, if you're, well, in any case where you import a consumer product, you have to provide a CPSC accredited lab. So, you actually would only have to provide us that ID number, not the full information. If you are using, excuse me, for general use products, because there are multiple means of testing for general use products, if you use a CPSC accredited laboratory, again, you just have to provide the CPSC lab ID number. If you're using a different laboratory, you have to provide the full information, including if you test in-house, you would also have to provide the full information in the laboratory, the address, phone and email. Again, that is only for GCCs if you're not using a CPSC accredited laboratory. The last bullet here is something of consideration. CPSC staff would like to test having filers provide a web link to the lab test reports. The reason for this is for the investigators to be able to validate the certificates when reviewing the documents. As the process is now, our investigators, after placing a hold, would request the certificate and test reports from the party certifying compliance, and at that point would confirm and validate whether that certificate is valid and the test report information is valid for the product in the cargo and everything matches up. So we want to consider how we could do, how can we validate certificates at the time when the data is sent to us before placing a hold. This is something new that we haven't approached before, so that's why it says optional in the parentheses, and we're looking for feedback from you, whether this would be feasible or if there's any other means to do so. So the idea here is if we're able to get information from, if we're able to have access to the test reports when also reviewing the entry documents and the certificate data will be able to validate that certificate is from, has been created from those test reports and therefore we wouldn't have to place a hold on the shipment to make that check. Again, this is something optional that we are considering, but we're hoping the participants of the beta pilot will be able to provide input on this and provide us some ideas on how to do so. I do apologize for those attending virtually. You did not see any of these slides, but these slides will be made available afterwards. Also, this recording will be made available afterwards, so, and let me go on to the last slide. That is a checkbox. So a checkbox indicating that a required certificate currently exists for the finished product. This is an attestation done by the individual certifying compliance, so the certifier would attest that the finished product or component parts covered on the certificate complies with the rules, bans, standards and regulations stated in the certificate and the information in the certificate is true and accurate to the best of the certifier's knowledge, information and belief. Some portions of the applicable consumer product safety rules that require compliance such as a certain labeling requirement and exemptions are not subject to testing. So this attestation is an affirmation by the certifier that the product complies with all requirements of the applicable rules, not only those provisions for which there are test results. Sorry, that was a little bit long-winded, but the checkbox just to confirm attestation. All right, and so to conclude this session, these are the questions that we CPSC staff have for you, the audience of this workshop. What additional product identifiers should CPSC consider? Second, would you use a G10 as a product identifier? Third, would you be able to readily provide product description information? That was the second slide here to provide sufficient description of the product. Therefore, investigators are able to validate that that certificate is for the product they are examining. So that could be model name, color, color, description and style. Does the product registry address any issues importers may have with product certification? And would providing the URL to lab test reports be feasible? So at this moment, I will open the floor to any questions or any comments or answers to these questions that I presented to you. And so, pass it to Michelle firsthand up. Every time, do I? Okay, so for example, the unique ID for the product, not all products necessarily have the unique ID. A SKU or a product, will that maybe be optional as long as we're able to provide the detailed description? Or would you have us maybe repeat the same information in the description as the product identifier? So when using the registry, you have to create some ID number. Okay. So I think previous in Alpha pilot, we created the ID number, but then we ran into issues there where the ID number was incorrectly entered into the PJ message set. And that's where we found a lot of errors. So we want to instead test, in this case, where you as a filer would create and manage the ID number. So we'll be open to the idea that you could create just an additional ID number, like just a product registry ID number that doesn't have to be a model number or SKU. Does the certificate currently require an actual ID number or not necessarily? Not necessarily. Okay. Another question that I had. So that checkbox, you talked about earlier how one of the requirements on the certificate is the importer's information. And that is that they're certifying the product. The checkbox sort of just takes the place of that, right? Because you're already getting the importer from the message set or from the entry, right? Passed through. So the checkbox just sort of says, yes, the importer certifies, right? Yes. The checkbox is actively, and this is something I was pointing to Mary. The checkbox is required that the importer either does it or the person who's empowered by the importer fills that out. So you couldn't have a manufacturer go and click that checkbox. If I remember properly, it has to be the importer or the legal representative that the importer allows to provide attestation, correct, Mary? And that's it. The importer or their agent. Okay. So I guess as the broker, we would as the broker, you can click on that checkbox with the understanding that you're providing to do care with the expectation that the importer understands that they are on the hook for what you're clicking. Now you had talked about the labs and accredited labs and them having ID numbers. So will that be an either or we can either provide the full name address, phone, email of the lab or the ID number? Yes, either or. So already on our website where you can find the list of accredited labs already is an ID that we issue to keep track of them. So we advise just to do that because it's quicker and easier and takes up less space. As the broker, we're always looking for the less keystrokes, right? Less, less data elements. You're welcome to put in the full. Yeah. I do make the recommendation that you try to find the ID as best you can because of people, fat, thumb, data entry. Absolutely. Us having to clean up that data is a pain and we'll slow things down. Well, understand, we do when we create the registry, we want because we have the available list, same with the citations that we will provide a drop down list. So that information is already should be coded in the registry in order to prevent the. So if you're using a lab that's not on that list, then it's not CPSC certified is what we're saying, right? If you, which is fine for GCC. Yeah, but if you have a GCC and you tested at it accredited CPSC accredited lab, you could just also just provide that ID number. You don't have to go through the steps of providing the full information. And also to that point, many laboratory companies have multiple labs in different countries. You have to provide us the correct one, not just the name of the lab, but like the location and we will clarify that in the registry so it's as clear as possible for you. Sure. And then your, your request for the URL for the lab test report, are you considering using DIS to actually upload a copy of the report or are you pretty much you're just looking for a link. So we're open to different ideas. We could consider DIS and I know that investigators when they request the test reports sometimes submitted to DIS, but we understand DIS is an extra step in the process. So that's why we came up the idea about URL if that's plausible, but we're considering other ideas in order for our investigators to get access to the test reports. At the same time, they have access to the data in order to review it while like the shipments under review, so they don't have to place a hold in order to make that validation. And I'm not really familiar with the lab test reports, but like, is that something that would typically be available is a URL to be able to access? That is my question for all of you that typically available or is there another means that we haven't considered. Okay, thank you. The test reports. So the test reports would be the result of a contract between the importer that's getting the test for the product and a test lab. Now, we are finding that some test lab organizations are willing to upload their test reports into required repositories for information. So if let's say FDA requires a test report, I hear, I do not know this for a fact, but I do hear that some test labs do load them up proactively for the importer and manage some of those data concerns. I think it's, it would be a inefficiency. I think in the overall review process to have a URL that goes directly out to the product. It's, you know, one less PDF that needs to be stored somewhere in DIS that needs to be manually as a form owned and ace. I think there's a lot of reasons why I think the URL would be so much more efficient. All right, I'm going to go to Kat. She has a few questions from our virtual attendees. If a manufacturer and a retailer direct import shipments import the same item. Can the PGA message set E filed by the manufacturer be utilized for both manufacturer and retailer importer. I'm under, I just want to make sure I understand the question. I think it's similar to what's been asked before. Can 2 different importers rely on the same data. And the answer is yes, as long as you're following the requirements and 16 CFR part 1109. Read that regulation and it tells you what you have to do to rely on another party's testing. Or another party's testing and certification. We always anticipated that people like importers who are required to certify. They're importing lots of stuff from lots of different manufacturers. They may not know all of the manufacturing information. They may not have done the testing themselves. So we wanted to provide a way for that to happen. So we did and we put some requirements. You can do it. You just need to follow the rule. And part of that is do care and it'll explain in the rule what that do care is. So each importer has to certify separately. The information might be the same, except for who's importing it. But each importer saying, yeah, I relied on this testing. I did my do care, right? So I'm certifying it. I'm content that they actually did test this correctly. So you need to have access to the test records, right? You can't issue a certification if you have no idea whether it was actually tested. You have to know that testing exists. You have to have asked a couple of good questions and satisfy yourself that this is an accurate certificate and then you may rely on it. You can issue your own certificate based on that information. And if I could just add, and I think that's the key, it's the issuing of the certificate, right? Because when an entry is filed, you know, a product is going to be tied to a line. That product that's tied to that line needs to be able to map back to the registry, right? Which is going to be data that's either inputted by the importer on behalf of the importer. So you've got to have that connection. So you've got to have all of that information available to be able to map back to that product when the entries filed. I'll go back to Kat for a question. Would an image of the product on the CPC cover the model name, color, description and style request? Yeah, I'm not quite sure if we have the space for the images as part of the message. But you can't search data off of pictures. So we can't key off of it and we can't do systematic research in terms of trend work. Kelly Nasredi and I with Bureau Veritas as a test lab here. So we were talking a lot earlier about identifying test labs based on an ID associated with them. Would that be citation specific? You know, like if one citation was tested at X lab, another citation tested at Y lab. Would that be citation specific or certificate specific? So I think you're asking whether you have multiple labs listed on one certificate. Correct. Yes, we will allow for that. So if you do have that means where you have one lap, one citation, one lab, another citation, a different lab. We'll built in features. And then as testing is updated, say on, on repeat products and things like that, would there be an ability to update those locations, update those IDs, or would that be a new message that No, there'll be means in the product registry to update that information. We'll discuss this later, but we want to create some form of versioning control. We're able to create new versions of certificate for that reason, when you have an update, such as a new citation or a date, for example. Okay, great. Thank you. You have been waiting. Hi, Diana guilt with FedEx trade networks. I had a couple of questions. By first is, is the expectation on the broker. When we receive a product registry ID on the paperwork that we are going to go and look at that ID and confirm that it matches the item that's on the invoice for every shipment. Or are we allowed to be comfortable with trusting the party who's putting that information on the paperwork. Go ahead, Mary. I think that's something we'll have to consider because you are acting as an agent of the importer. So what does your that something maybe the rulemaking should consider. So we'll collect your thoughts and information. I'm interested to hear it sounds like you probably don't want to do that based on the way you ask the question. So that's something we can consider during the beta pilot and during the rulemaking on how that should occur. Okay. My second comment, more of a suggestion. They mentioned providing the URL for the lab test. So I myself processed entries for 10 years and I can say lab paperwork. Very rarely in my opinion would be available online. The vast majority of the time they're sending in a copy of the actual lab paperwork that they've received. I'm not at all against the possibility of providing a URL. I think that's a fantastic idea. But a lot of companies that are testing their own products may not have the ability or the interest or the knowledge to put that information online. And they would probably prefer to send in a copy with their shipment documents and then we would upload through DIS or however that's handled. Just a suggestion. All right. Thank you for that. A comment on filing from FTZs. The 3461 is an estimate or projection of what could ship from a zone in the coming week. The 3461 is reported, summed up at the HTS country of origin and manufacturer ID number, not at the product level. Therefore, for every line on an FTZ 3461, you could have many different products. If each product requires a unique registry number, it would be impossible to report on the 3461 because ACE has a line limit of 999 lines. Product level would result in many thousands of lines. I think I misspoke earlier when I said form 3461. I'm not well versed with FTZs, but the idea here is if you, the certificate or the e filing requirement would occur once that product leaves the FTZ and enters commerce. So not when it's, so that's a 75 01 I believe. Okay, I see a nodding head in the back. So I misspoke. So it's just keep in mind it's when it's exiting FTZ. And then there's 1 more. Will the product registry be accessible to customs brokers based on importer, or will it be general access? In other words, will an importer be able to control who has access to their products in the product registry, ie a manufacturer or customs broker and control what access they have. So the only idea that I have, that's something we still have to discuss in more detail and figure out. That's actually a good comment for our next session when we discuss the specific product registry features. Okay, Hector, are you ready back there? Hello, this is funny again. Can you guys hear me better? Arthur, could you confirm? Okay, wonderful. Thank you guys. Again, my name is funny flores faster. I'm with the car systems group. And my question is related to the message set checkbox field, which is the 1 of the added new field. Where is supposed to attest that the individual certifying compliant is certifying that they have the product and the certificate for it. My concern is that most of the time the PGM as I said, it transmitted by the, by the broker. While the certificate from what I'm hearing is mostly done by the importer. So when we are doing this checkbox and is being sent by the broker, who is really attesting the broker or the importer. The testing is the, is the importer. So if the person has used the product registry, the checkbox is in the product registry. So they will be whoever's uploading that information is attesting right on behalf of the importer. So as the broker, if you're using just a reference, you're just typing in the reference number. So I don't think you ever get to the checkbox if you're doing the full PGA message that then you're typing in all the information including the checkbox. And then you're an agent of the importer. So it's the importer is making that attestation. Okay. So, so I guess I just want to make sure that when the message set is prepared, there is a clear statement that clarifies that point that even though the broker is doing the filing really who is checking the box is the importer. Right. Yeah, that should be clear on the software. And also, I believe we do have an NPR sitting out there from 2013 that talks about this stuff. We're going to be doing an SNPR supplemental NPR next year. So it does talk about this to who's on the hook or the attestation and it is right now the importer of record. Thank you. Okay.  You're in the hearing room. Hi. Is the registry going to be able to accommodate duplicate entries with the same ID number? Like if two retailers are importing same product has the same UPC, but maybe different batches, clearly different entries. If it's the importer managing the ID numbers and creating the ID numbers rather than CPSC, is it going to accommodate for duplicates? So the idea here with the registry is that any filer, the importer in this case will have an account. So we have that additional verification information that's the importer and the ID. And so we haven't resolved that issue entirely, but the thought process is that when they, when that's filed, we're able to also match on the importer, not just the ID. Right. Because we're looking at two pieces of information. We are. Okay. So your primary key basically is going to be like the importer number plus the product ID. Yeah. And so those will have to be unique. You can't have the same product ID with the same importer. Yeah. So if the product, yeah, so the importer has is using the same ID number, that'll be an issue because then we don't know how to match it out. Or it'll be, or it'll be the importer and the reference number based off of the fact that you're saying that there's a lot of product that doesn't have product IDs. And so if you don't have a product, you know, like a handmade something coming from the Andes in those types of situations where there isn't an identifier, there'll be the reference number that you're using for, you know, a test station and certification. That's going to be on the registry. That would be the identifier. And then the importer would be the one who's managing. And then that could also track. So then you're going to have that probable double primary key match that we're talking about there. This is all, you know, part of development that we're going to have to work out. Sure. And that brings me then to my next question. I'm assuming that you're going to have some sort of validations in place that you can only transmit. Product registry ID that belongs to that importer. Yes. Okay. So, okay. But that's a good idea to bring up during the development. I think as we, as we review development, part of the problem is going to end up being that there's going to be certification that an importer is going to manage that's going to be. There's a lot of importers of the same product models that are going to end up occurring. And so there's going to be a lot of repeat data that's going to have different reference IDs. And so that managed information is going to be tracked by the importer. We're going to have to make sure that those databases are working properly when we match it up with CBP. Right. So this, this complexity is something that we're going to have to work out and it's going to get worked out with our nine, nine practice people. So please volunteer and become one of those to help us make sure we get this right. I already have. Okay. So then that brings me to the next question. So you talked about product, product registry updates, being able to update a product registry. Is that going to then generate like a new identification number, like a dot one or something so that you can then identify which. So that's, I'll address that in the next session. But okay, fine. And then one more question when we talked about multiple labs and certain labs certifying to certain certification rules. Is there going to be like a linking there?  Or are you going to report lab one, rule one, lab two, rule two and rule three? Yeah, it would be. They'll have to be there. That would be like, that's what we did in alpha pilot. You first actually identified the lab, the citations below, and then you're able to create a new line next lab, the citations and so on. Okay. And then I just have one more question. Who actually completes these certificates? Is it the importer that's doing the certificate? The manufacturer? Well, it could the manufacturer. The guy that gets it down the road. So the importer still has the responsibility of certifying and typically they will create it. But we've seen in the past where a manufacturer or laboratory would also would create the certificate or for the most part create the majority of the certificate. But then the importer, so certifying compliance has to finalize that certificate. Okay. Is there any indication on the certificate that it was created by one party and certified by another or not necessarily? Not necessarily. It's just the importer is responsible for the accuracy of the certificate. We've seen like, there's no actual template to the certificates. So we've seen different headers. So we could identify sometimes a lab has created it, but it's still the onus on the importer. Okay. Thank you. Okay. Hector. Go ahead. Yes, we have another participant. Katie Tangman, please. Hello, can you hear me? Yes. Okay, great. Hi, thank you. I'm Katie Tangman with Columbia sportswear company. First of all, thank you for hosting this workshop. I've always admired how. The amount of study and thought that CPSC has put into these programs. So thank you for that. I'm also a board member of the national association of foreign trade zones. So when you're, when you're, when you saw that last comment about foreign trade zones. I'm also representing that program here. So the other comment that I would make is that the challenge with reporting this on a 70 501. Is the zone 70501 occurs after all of the goods have shipped from the zone into the commerce of the United States. So those goods are then no longer available for inspection. The other issue again, it relates to that issue that we have on the 34 61 is also on a foreign trade zone. 70501. The goods are summed at the HTS and country of origin level on that 70501 not at the product level. Every line on that entry could contain anywhere from 1 to a couple hundred different products. And again, we're limited by the ace limitation of 999 lines on both the 34 61 and the 70501. So, so there are some challenges unique to foreign trade zones. I would actually highly recommend and I think I put a follow on comment there in the Q and a that's that the team meet with the executive committee of the foreign national association of foreign trade zones. To better understand or more than likely will be a subcommittee that will be speaking on this topic. To really better understand the nuance and the complexity associated with foreign trade zones. And to find out if there's a better way. You know, I know that foreign trade zones ended up being excluded from the alpha pilot because of these complexities. I suspect that they will be excluded from the beta pilot because of these complexities, but I, you know, obviously. When you want to make that final rule making and have the entire trade be participating in this. There's going to have to be something different. For foreign trade zones. So. So, Katie, we would love to have your participation or any of these participation in the beta pilot because this is an issue we need to resolve before we make the filing permanent. So, although it was excluded in alpha, we won't exclude foreign trade zones in the beta. And also, if I could speak, this is John will share it just real quickly. The information that comes out of the FTZ's we can actually act upon by knowing that the product is then present in the FTZ and then be able to follow up in the FTZ as necessary. We do have examination capabilities and FTZ's. We've had that recently. I understand that, but in that case, then you're going to follow up on product models that sit in the FTZ. And that remain because there's an expectation that the weekly delivery isn't necessarily exporting everything. So that's always, and then again, we always have domestic capability to get to product. So in either instance, we can follow up based off of the information that comes off of a 7501 is necessary. So that's number one. Number two, a lot of our targeting ends up coming off of entry, the 3461. So as the information matches up off the 7501 and trying to get it down to the product model as you stated is going to be a challenge. So as Arthur stated, we really would love to have you as a participant to help us work through these types of nuances because we definitely are aware of a sector of commerce that we need to be able to get to in the FTZ. Hi, Katie. This is Jim jaholsky question for you. And I think this is a. I think a question that would sort of apply to a number of areas that we may touch on today, but for for FTC FTZ. Admission or. Entry out of an FTZ. To what extent do you know now how PGA message that data is attached for other agencies like FDA or. Anyone else because, you know, we're, you know, to the extent that we can, we're not trying to reinvent the wheel here. We'd like to be able to leverage if if there is a process in place where other agencies are. Receiving PGA message that data, you know, we'd like to be able to leverage that to the to the best we can. So I don't know if you can can share anything about how PGA data is is provided for other agencies. Yeah, and I my my knowledge is somewhat limited because. There are such a broad group of PGA's and of course, a large number of, you know, different commodities that. Come out of foreign trade zones and of course, apparel and footwear. Fish and wildlife ended up with just maintaining their external system. For registering importations because it was not feasible for them. To utilize the, you know, the 734 61 or the 7501 an ace. EPA as well. Just based on the point in time at which they need to actually. Target and capture goods. So, some some PJ's have actually chosen to not participate. In this model because of those complexities and I think there are certainly some. That are participating, but, you know, they're, they're. You know, I think we would have to get some other people on to a, you know, a call to sort of help help you better understand how that's being used in. In the foreign trade zone realm and ace. All right. Thank you, Katie. You have response. Okay, so I'm going to. In person audience. Thanks, Katie. I just wanted to let you know that for a fist or a fist Lacey. There is a the ability. There's a registry on their site called logs. And you file your data there. And you then in the zone. Information on the, I think it's the 751 you disclaim. Because and the disclaimer is that's filed in a different means. It's not in the message set. So that might be a model that you might want to look at. FDA has a slightly different model. They have what's called Weff. Where you have to seek their approval. Yeah, thank you. That's a good idea. Okay. I have a quick question regarding to the point three. So right now I understand that the product description is one data field as a free text field. Is that correct? Yes. So do you have plans to break it into more modular field like one field for model name one field for color one through for description. Well, that's something we would discuss as we develop the beta pilots. That's something we would discuss with the participants. What is the best approach to that? Whether a free text field is best or break it up and keep those all those fields optional. So you fill in which field you think is as suited to your needs. Okay. Thank you. Any more questions? Okay. I at this point, I will end this morning session. We'll break for lunch and resume at 1pm. All right, welcome back everybody. We're going to continue on with the second session discussing the product registry features. Andrea, I want to take it away. There we go. All right. Thanks to everyone for coming back. I know it's lunch is a very time to say. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. I'm Andrea. According to this day 6. How we're going to access the product registry, that's something that we are going to build in house. It will be a software solution designed and developed within CPSC alongside our e-filing program or an e-filing infrastructure more broadly. As we've mentioned before, the importers who use the product registry will create their own unique profile. Which should help with discerning two importers using similar products or even the same products with the same certificates. Brokers and labs can be granted third party access by the importer. This is a question that I've gotten as I've been doing presentations alongside Arthur. So we will not be just putting all of the onus on the importer for this. We will be able to open this up to brokers and labs, but it will have to be managed through the importer. You won't be able to do things independent of the importer for information control and security purposes and all of that important stuff. So we're going to have the option for batch uploads, which is going to be very nice as you think about your data entry requirements. We will have the ability to just load a single spreadsheet in and load up all of your certificate data that way. The way this would work, you would load and of course take this with a grain of salt because this is all sort of in development. We don't know exactly how it's going to work, but this is our idea. The product registry will be able to ingest a spreadsheet of a bunch of different certificate data for different products. And then you will be able to get your product, your product registry ID out from the spreadsheet that you put in. We're hoping to build that out more as we develop this system. So if you want to take part in some of that testing, you should sign up for the pilot. As we've mentioned before, one product per e-filing certificate. That's very important for data quality concerns and the fact that we are using this for targeting purposes. And we are going to allow multiple models, like we mentioned before, as long as all of the certificate information remains the same for each of those models. It's really important, and I can't stress this enough with the product registry, that the information has to be current. It has to be the same if you are using it for the same product. So if your certificate expires, a year after you put it into the product registry, you're going to have to re-upload that information. So keep that in mind. We want to make sure that everything is as accurate as possible, and this isn't just a set it and forget it type of system. So we've got versioning and copying controls, hopefully built into the system as well. The versioning would allow filers to upload certificates and update your certificates and keep the product registry ID the same. So this is what I'm talking about. You update your certificates as they need to be updated as the information expires and then is recertified. You can keep your product registry ID the same, which is great for the brokers of the room because you're not going to have to sort through a bunch of different product registry IDs to try to file on behalf of your importers. We also allow copying, which will allow you to copy the existing certificate data to a new certificate with a new product registry ID. This is really useful if you've got similar but not quite the same products. So maybe they have the same lab information. Maybe they have the same manufacturer or something like that. You can keep all of that information and more easily conduct the data entry. And that is the general overview and I will hand it over to Arthur for some discussion on this. I know it will be pretty robust with all the interest. Right. Well, thank you, Andrea and let me go through the questions we want feedback on. So first of all, would you as an importer being favor of third party access for brokers and labs and tangential to that should other parties have third party access with regards to the batch upload features that's something that you would use. What would your requirements be for batch uploads and lastly, would versioning and copying controls be useful for you to have any feedback on that. So I will open the floor to questioning for approximately the next half hour if we need all that time. All right, Michelle. So would you envision with the batch upload process when it takes in the spreadsheet then then it would lack of a better word regurgitate. One product ID that then you would use for everything that was encompassed in that spreadsheet or would it be smart enough to sort of parse it out into the unique circumstances that would require an individual product ID. So the thought is that in your spreadsheet, each line is a separate certificate. So like the first column would be that ID and the remaining columns be the additional information required in the registry. That we were going for. Okay, well that that brings up another question. So then you asked like what would the requirements be. Like, there must be a finite number of rules, right that things could be because I'm trying to think of how that would look right with you could have multiple rule and manufacturer combinations that spreadsheet could get pretty wide but I mean probably not unmanageable. But that would be different than say like a multiple record or certificate type of layout, right, because you could have multiple manufacturers so if I only had one column for manufacturer. Yeah, you know, and like you mean also for the lab. Yeah, right the lab. Yeah. And then we could work on as part of the preparation for the beta pilot, I'm not that savvy with it so I don't know what the best approach would be, but that would be something we would like input on. Okay, and then when you talk about third party access I'm assuming that would be like read only access for a broker or, I mean a lab might want. It might be advantageous to have a lab be able to actually update records. Right. I thought there is that even a broker or a lab could enter the data or update the information on behalf the importer. But the importer was still be responsible for that data. Okay understood. Thank you back grow. Good afternoon Sylvia with class twin. Assuming multiple parties can work in the module. Will there be an audit trail who change what. I would imagine so that's something we could develop as part of the registry. Thank you. One of the questions was the alpha pilot you previously completed. Was this based on air and ocean shipments. And how would he filing for work for 16 CFR 1640. Hi. I don't. First question. I'm not quite sure. I'm not quite sure. You answered. Yeah, could you answer that John. I'm pretty sure for the first question that we ran the alpha on ocean air and truck environments. And that was it. So to the second question of the 1640. Yeah, I'm not. I don't know my 16, I think, Mary, are you looking that up. So for the upholstered furniture, right? Okay. That's a new. It was a statute and we just codified the statute. The statute actually accepts. Uh, upholstered furniture from certification requirements. So we're going to have to think about that when it requires an on product certification. So that might be one where we have to do special programs or something we'll have to think about that one because. It's not by statute. It is not subject to the certification requirements. I don't know of anything else by statute that's like that. Section 14 a of the CPSA requires all regulated products to be tested and certified. So here Congress has done their own thing. So we'll have to think about how we want to enforce that particular rule. But it won't be through e filing. Right. And right now the HTS codes with respect to upholstered furniture have not been identified. Right. So we'll, we'll think about that one, whether it's. You know, there are a couple of options. Do a separate program. We could do a disclaim. We'll have to think about that one. Then someone else asked, where is the CPSC supplemental guide? Oh, the IG is. In regards to the cat hair. I, yeah, maybe, yeah, you can answer that alpha for the CPSC. The IG, the guide should be out on CBP.gov. I've not validated that it remains. I don't think they have they taken it down. They may have pulled it down. Otherwise, did we put it on our website? It's not on our website, but we have a copy of it. Do we want to put it up on e filing? Just to say, here's archive documents from the previous iteration so people can watch what we're doing. Yeah, we could do that. Okay, so there's a thought to try to get some of the alpha documents up on the website that people can refer to generally and say that these are old documents that we'll be working from. So we may take that back. Okay. Okay. Certain US states use I see to portal for CHCC reporting, which my chat just went down, which allows manufacturers to do a batch upload has the CPSC looked into the features I see to offers. I haven't heard of that. Thank you for that comment and we'll look into it. And then we have another question as a follow up will multiple users be able to access the registry for an importer simultaneously, including that audit trail. And could they access the same product simultaneously. I don't quite know how. The answer to that because that would depend on I think on our T developers, we could take that question back to them as we build out the product registry and see but I don't know. I'd have a follow up question back should it should it allow more than one person what's the benefit to that would anybody ever use it. More than 1% at the same time. AT capabilities to be able to do. Simultaneous editing and then if they save at the same time, you just have side by side versions that would then exist in the system. So we'll have to take a look obviously what Arthur just said is, you know, that's going to be part of the development considerations. Is, you know, multiple people getting in and editing at the same time and having those type of controls. Do we lock out an account if it's 1 person at a time type type controls in this type of situation. That's the kind of questions we'll have to ask. Yeah, and those are the questions we want to hear during the development. So another reason to participate, especially in the it advisement is we don't have I personally don't have this it experience. We have it developers who have more. Of course, have the experience and they will be asking the participants specific details that were specific details and we want kind of. We'll be asking detailed questions and also on detailed questions back from you. Go ahead. Yeah, she's coming. Thank you. Something to consider with the version history. If there's not a way to actually differentiate versions of the product ID. So for instance, let's just say the number is 1, 2, 3, 4. And the importer goes in they update something simple like the last date of lab testing for a new batch of products. Everything else has stayed the same. We've done a new test. This was the last day it was done. If that's not going to be 1, 2, 3, 4 a, as an example, when they ship product, their paperwork is only going to say that original version number still and it could become really difficult. If CPSC is auditing a file to know which version of that ID goes with a shipment, because just because you know lab testing was done at a certain time, and then they do another set of lab testing that initial cluster of product hasn't necessarily all been imported. So they could still be like looking back on previous versions of testing. Yeah. And we want to build the registry in a way to allow for that. My thought is to have suffix like a B or just like dash 1 dash 2. And when you file in the message that you would put the whole ID with that suffix. I think that's a great idea. Okay. But I'm open to different ideas to make it easier. For the message. If there's no other questions right now, I wanted to explore this 1st topic a little bit on. 3rd party. Access to the registry on behalf of importers and. And sort of ask generally importers. Is that something that you're looking for from our perspective what we're trying to build is something. That can be the least burdensome. As possible. I think it's still allow us to get the information and be able to process it and use it for targeting, but for the trade to make it. Set it up in a way where it is the least onerous, you know, that that we can. And so, I mean, I've had some conversations with with brokers and test labs and it sounds like, you know, a lot of brokers and test labs have this information already. So, you know, just from the broker test lab perspective, are you interested in doing this work on behalf of of importers? And I guess importers. Are you interested in having brokers and test labs do this work for you? Because we want to be able to set it up in a way that works for for everyone. So just any input that anyone has on that. I think I'm the only lab in the room. So on behalf of labs, yes, we are interested. We do have that confirming. I would think as from a broker's perspective, it's the kind of a double edged sword for integrity of data. You'd probably want one person responsible for the data. If they use a multiple brokers, you might have multiple versions of data. At the same time, we'd like to maintain our product database and order our product database. So it's kind of a double edged sword in my opinion. Yeah. And, you know, from a broker's perspective also, I would say that we want our customers to be responsible for that data. Right. We don't want to be responsible for that data. And I mean, you know, could we possibly offer it as a value added service? You know, possibly if the importers say that that's what they want. But I really think from our perspective, it would be preferable that the importers that the owners remain on them to, you know, verify that information. I do recognize that as part of the process, the audit trail is going to be robust. You're going to have a last update user type situation. We're going to have multiple user and sub user type account situations where you'll have one person who owns the information, but other people potentially updating. So there should be some type of sophisticated account capability where you can have single simple, you could have one owner with multiple users that can update and so on. And our design is going to need to be able to be robust enough to provide a full audit trail and the kind of security that's going to let you know as an account owner who's updated what and when. And so that will be a requirement. Also recognize that we see this as, you know, some of the higher sensitivity information that we would have. So we would have this be secure information in a tight, you know, secure environment. Yeah, and that audit trail would be necessary on a field by field basis, right? Because you would need to know who updated exactly what when. Right. And so probably what would end up happening in this would be part of the IT review and how this would be maintained. It would be, you'd have a recordation of. Yeah, you're going to have the 1, 2, 3, 4, half an alpha for the update of a lab. But if somebody else then comes in and does an update, this would be version 2 of the 1, 2, 3, 4 alpha or a. And then, you know, if there's a change, then it's 1, 2, 3, 4, B. And then somebody else does an update that could be a B2. And each of those would have the latest person who did those updates with the capability to track edit changes when and where that would be the kind of control. I think we would be looking for. And to add to that certificate typically are required to be recertified once a year. So the thought is, you know, the importer could go and put the certificate information or the broker could do it on the behalf of the importer, the lab on behalf. So, as John's example, I don't expect you're going to have multiple versions occurring so often, but at the minimum once a year. But that's as we have copy control too. So if you have a similar product with a very similar certificate, you could copy that, but that's a different ID number. And this is going to be kind of a weird request and this is something that we could possibly as part of version version and control and thinking to what Arthur is stating. Would it be useful to provide messaging feedback when a certificate is dead when it's gone past the 1 year and we just we kick it back to you and you say. You're the account owner.   Re up this or this product is going to fail the certificate load process. You'd appreciate that. Mary wants to speak wrong with notification, but depending on how they're set up. Some manufacturers or importers can earn a 2 year cycle and some are even a 3 if they have their own firewalled lab that's been approved. So. It depends on how they're set up. Most people are 1 year. But not all we could prop we could probably develop an account type situation where we got 1 and we have 1, 2 and 3. And that would your capability could also just be more of a reminder for the importers because. In theory, you could still bring in products under that certificate if if it's stored overseas and it was and you followed the procedures manufactured 2 years ago, test it 2 years ago, you could still bring in that product under that certificate. You're not required to have that certificate done in the most recent year, but if it was something manufactured recently needs to be updated. But if the certificate failed because it wasn't updated. But it was manufactured and tracked to a dead certificate. It could fail potentially batch 2 or a 2nd bucket check, whatever it's called. Meaning that you got all the information in we're able to read it. So it's fine there. But then on validation and review. You have to go and update your certificate or this product has to sit until you know that could be a remediate remediable. Violation per se and not violation. I guess that's not quite the term, but and yeah, an edit check that needs to be done. And if you don't do it. Then you don't have an updated certificate. Because like certificate period is not a data element. Yeah, right. So what what hinges on the eligibility of the certificate when you say 1 year, is it 1 year from the testing date? It's good for or like, where does that. Yes, I mean, it depends. There's a rule. It depends. So it's something in the beta pilot we can talk through. So it sounds like it's something people would like to use, but how exactly it functions is something we can talk through so that we're not. Holding up legitimate trade, but it's a nice notice for people to double check. A combination of like the HTS code. What was filed what you stated it was. And then from there, we would know it's 1 year, 2 year, 3 year. It's probably some type of crosswalk. So certain products are allowed. It's that's just for children's products. Okay. It's depending on the type of lab you have 1, 2, or 3 years. Okay. I don't want to get too much in the weeds here. It's really just something we can talk through. These are the kinds of issues that are going to come up and we'll need to iron out. It could be something in your profile because it's the type of lab you're using. It could be. We'll just have to see and it's really it's more complicated than this 1107 has this whole thing about labs. So. I don't think we need to go through that now, but we will have to get into these weeds. During the beta. Okay, sounds good. Thank you. There, so it would have a reporting feature as well where you could like run reports out of this. We could consider that as a possibility. I've been. I personally haven't considered that. I think that might be useful to offer something like that at a minimum. The owner needs to be able to drop the most current information out. And be able to say, this is where all my certificates are. There needs to be an export function that allows traceability and be able to say these are close to being old. We need to update and manage. And these are the kind of things that I think we need to go through in terms of the requirements that we're going to set. But reports coming out of the system is something that should be part of a requirement that we put in front of our, our contractors as well. So this, this type of reporting functionality, I think is a good ask. And if you are 1 of the 9, you can help us to identify what reports should be b