Please Note: This document is a guide to the discussions between the EPA and their stakeholders during the e-Manifest Virtual Public Meeting dated November 3, 2021.

WEBVTT

1 00:00:12.269 --> 00:00:31.170 Stephen Donnelly: All right, good afternoon, everybody or morning depending on where you come from this is the second of our virtual public meetings on increasing adoption electronic manifests, I am the e-manifest program manager.

2 00:00:32.310 --> 00:00:46.980 Stephen Donnelly: Steve Donnelly and we are here to present and talk and listen about all the things electronic manifest so before I get this thing going just a little bit of kick off.

3 00:00:47.700 --> 00:00:58.080 Stephen Donnelly: activity is that we have a recording and transcription has started and you're going to be posting links to those.

4 00:00:58.560 --> 00:01:04.200 Stephen Donnelly: And the transcription in our docket we're going to make these both these meetings available, and any subsequent meetings will be made available so.

5 00:01:04.560 --> 00:01:17.370 Stephen Donnelly: These are all being recorded and transcribed for posterity so thank you all, we have a lot to cover today and kick things off, I would like to introduce our division director so nice hospital.

6 00:01:22.080 --> 00:01:32.700 Sonya Sasseville: Okay hi everybody and welcome to our e-Manifest virtual public meeting focused on increasing adoption of electronic manifests, thank you for joining us today.

7 00:01:33.540 --> 00:01:52.200 Sonya Sasseville: If you've been following our program for a while, you know that one of our long standing and top priority goals of the manifest program is to move from paper to electronic manifesting widespread adoption of electronic manifests is how we will truly unleash the benefits of the manifesting.

8 00:01:53.250 --> 00:02:12.060 Sonya Sasseville: And maximizing cost savings and burden reduction, improving the quality of manifest data integrating with Biennial Report requirements and enhancing monitoring of hazardous waste shipments nationwide were at an exciting time for e-Manifest since launching a.

9 00:02:13.140 --> 00:02:25.740 Sonya Sasseville: we've worked together to lay the foundation of our program EPA also spent time by way of several e-Manifest advisory board meetings and other user feedback venues.

10 00:02:26.250 --> 00:02:33.540 Sonya Sasseville: Learning the needs and challenges of our stakeholders with respect to electronic manifesting and we're working to try to address them.

11 00:02:34.290 --> 00:02:46.830 Sonya Sasseville: In 2020 and in 2020 and with concurrence from the e-Manifest advisory board we update date of our policy with respect to electronic signatures for generators transporters.

12 00:02:47.280 --> 00:02:58.680 Sonya Sasseville: and additional signatures by receiving facilities and we implemented the new quick sign feature quick sign was a dramatic improvement to our manifesting process.

13 00:02:59.220 --> 00:03:07.500 Sonya Sasseville: However, we know that that isn't enough electronic manifest still represent just about and of total manifest volume.

14 00:03:08.040 --> 00:03:21.690 Sonya Sasseville: In 2021 we committed to the e-Manifest Advisory Board to explore other potential solutions to increasing electronic manifest adoption online users, which brings us to today's public meeting.

15 00:03:23.220 --> 00:03:33.690 Sonya Sasseville: Our objective today is to get early input from you that we can use and defining options or potential future consideration by the e-Manifest Advisory Board.

16 00:03:34.260 --> 00:03:49.170 Sonya Sasseville: What you may hear today is by no means a type of formal proposal or concrete plans by the Agency, we are at the idea stage and your input will be very valuable in shaping where we go next.

17 00:03:50.040 --> 00:04:01.410 Sonya Sasseville: I also challenge you to keep an open mind and embrace change as it may relate to your own current practices and systems in moving toward electronic manifest.

18 00:04:02.490 --> 00:04:12.900 Sonya Sasseville: we've always taken pride in the fact that he manifested success is shared success among our users, online states and our VP at regional partners.

19 00:04:13.260 --> 00:04:23.130 Sonya Sasseville: And, among others, that use and derive value from the data, so I encourage us all to continue working together to make this next leap possible.

20 00:04:23.820 --> 00:04:41.880 Sonya Sasseville: So, with that I know that the e-Manifest team is ready to begin presenting and eager to listen and learn from our stakeholders, so I look forward to seeing the outcome of our time together Thank you again and I'll turn it back over to Steve.

21 00:04:45.600 --> 00:04:51.960 Stephen Donnelly: All right, oh, thank you, thank you so yep, so, let's just go over what we're going to be doing today so.

22 00:04:52.590 --> 00:04:59.460 Stephen Donnelly: We just went through our welcome and our welcome and then we're going to go through the meeting objectives in the background we're going to go.

23 00:04:59.820 --> 00:05:04.920 Stephen Donnelly: Why we're here while why we're doing this and what we hope to get out of these meetings.

24 00:05:05.850 --> 00:05:11.820 Stephen Donnelly: are going to have a walkthrough of the current electronic manifest workflow we're going to have some time to.

25 00:05:12.120 --> 00:05:25.620 Stephen Donnelly: have some discussion with you in the audience and hopefully answer some questions and make some new ones for consideration we'll take a break and then we're going to have a another in depth discussion on the policy.

26 00:05:26.280 --> 00:05:34.830 Stephen Donnelly: On the policy side of electronic signatures and we're going to have a discussion and follow on that we then we're going to have as we close out the meeting we're going to.

27 00:05:35.760 --> 00:05:45.750 Stephen Donnelly: throw the ball to you and ask for other potential options and considerations and we have to make this a really substantive back and forth between those of you.

28 00:05:46.470 --> 00:05:52.140 Stephen Donnelly: attending and those of us in headquarters, we might not have the answers for you right away, but we want you guys know that.

29 00:05:52.470 --> 00:06:08.820 Stephen Donnelly: We are listening to you were considering all the things you say, and we really want more electronic manifesto as well, so I'm going to pass it over to a familiar face David Graham to go through some of the some of the ground rules and West.

30 00:06:11.280 --> 00:06:19.470 David Graham: All right, thank you Steve so I know everyone's eager to provide all the comments Fortunately, thanks to zoom.

31 00:06:19.890 --> 00:06:25.590 David Graham: you'll be unable to actually unmute yourself during the presentation portion of today's meeting.

32 00:06:26.070 --> 00:06:34.260 David Graham: However, during the designated discussion portions if you'd like to provide a public comment which, again we highly, highly encourage you to do so since.

33 00:06:34.650 --> 00:06:45.960 David Graham: it's the primary reason for being here, please use the raise hand button, so a little window will pop up if you've never seen before, and one of the manifest team members will ask you to unmute yourself and then you can come on.

34 00:06:47.160 --> 00:06:48.180 David Graham: Have a conversation.

35 00:06:49.500 --> 00:06:59.790 David Graham: But during the entire length of the presentation, please put any questions comments concerns in the Q and A box and we will try to get to those as soon as we can in a timely manner.

36 00:07:00.390 --> 00:07:07.530 David Graham: And may also address some of those questions, if they are thought provoking, during the discussion portions as well.

37 00:07:09.240 --> 00:07:19.620 David Graham: Please note that the proposed times are approximate the times that Steve just showed you a minute ago, so if you're looking at the agenda, going "oh that's.

38 00:07:20.370 --> 00:07:33.780 David Graham: that's really interesting I like to come back and see that, but you know what I read e-Manifests Act everyday over breakfast and I know everything forwards and backwards skip that" just be aware that those times are approximate we highly encourage you to stay tuned entire presentation.

39 00:07:35.580 --> 00:07:44.640 David Graham: Also, please note that this meeting is being recorded and the recording and the transcript will be posted in the public dockets.

40 00:07:46.140 --> 00:08:01.650 David Graham: And where you can also provide written comments until December 30 this year, so when providing that public comment and come on, let me unmute you please make sure your comments are germane to the topic at hand and family friendly.

41 00:08:02.850 --> 00:08:05.250 David Graham: So, I'm going to pass this back over to Steve to go over.

42 00:08:09.330 --> 00:08:10.530 David Graham: Meeting objectives background.

43 00:08:11.070 --> 00:08:25.290 Stephen Donnelly: Yes, all right meeting objectives and background, yes, we can go to the next slide, this is what we go yeah, so this is why we are here, so the hazardous waste electronic manifest establish connect the manifest act.

44 00:08:27.540 --> 00:08:35.820 Stephen Donnelly: Well, they want us to have electronic manifests and we want full electric electronic manifest because as Sony said earlier.

45 00:08:36.360 --> 00:08:47.820 Stephen Donnelly: This is the this is how we decrease burden for our users, and this is how we get high quality data that can be used for integrating into by no reporting.

46 00:08:48.270 --> 00:08:55.080 Stephen Donnelly: And this can only be achieved, your wide adoption of electronic manifests electronic manifest as you are well aware.

47 00:08:55.830 --> 00:09:07.740 Stephen Donnelly: Are the smallest slice of the pie when it comes to divvying up the electronic map that's these are less than 1% of the approximately 2 million manifests the EPA receives annually.

48 00:09:08.940 --> 00:09:15.690 Stephen Donnelly: And the pace of electronic adoption false far short of agency expectations.

49 00:09:17.640 --> 00:09:29.400 Stephen Donnelly: So, the problem that is our problem alright, so our objective here is to solicit our individual feedback and ideas on ways to increase adoption of electronic manifest now.

50 00:09:30.180 --> 00:09:40.800 Stephen Donnelly: we've done a lot of high-level work for a very long time, however, today we're going to be getting very technical so moving forward as a program.

51 00:09:41.160 --> 00:09:54.900 Stephen Donnelly: We would like everybody, including industry states, regions headquarters, the public to be aware of the technical requirements and the pilot the technical policy requirements of electronic signatures.

52 00:09:55.860 --> 00:10:12.510 Stephen Donnelly: Because we want to use the information we get here from the document or from our when we have exchanges with our users here with your ideas, we want to be able to use this information to develop further options for consideration in an advisory board meeting in.

53 00:10:14.550 --> 00:10:22.320 Stephen Donnelly: And also, we want this, we want another purpose of this meeting is to increase understanding and use of the current workflow.

54 00:10:23.250 --> 00:10:39.960 Stephen Donnelly: And how it can be used, building on our data plus scanned image submission so we're going to be doing some very services-based discussions, and we want to be, we want people to understand Okay, this is how electronic manifest can work in our current system.

55 00:10:41.970 --> 00:10:42.390 Excellent.

56 00:10:44.190 --> 00:10:55.830 Stephen Donnelly: And should be noted that all these materials and resources will be added to the public docket, and we will be accepting written comments until December 30, 2021, so.

57 00:10:57.900 --> 00:11:07.770 Stephen Donnelly: If you have a question or comment and you don't get into the chat box, please use the docket to put that information in there, we would like to hear from you.

58 00:11:11.280 --> 00:11:12.360 Stephen Donnelly: All right back to David.

59 00:11:14.520 --> 00:11:25.200 David Graham: All right, thank you so a couple of more housekeeping items please keep in mind that this is not a federal advisory committee act or FACA meeting.

60 00:11:26.100 --> 00:11:41.070 David Graham: Which just means we need to ensure that we operate within a few certain parameters, so FACA generally applies to groups that EPA establishes or utilizes in the interest of obtaining group advice, recommendations and we take our FACA responsibilities very seriously.

61 00:11:42.090 --> 00:11:54.240 David Graham: However, at the same time it's also appropriate for EPA to get input from outside individuals such as yourselves and entities using other mechanisms such as this meeting that we're having today.

62 00:11:55.200 --> 00:12:04.470 David Graham: So, what you really need to take away from that is please keep in mind that we're seeking individual input not collected advice.

63 00:12:05.040 --> 00:12:13.500 David Graham: So, for example, if an organization sends an individual to more than one of these meetings or if that same organization and send.

64 00:12:14.070 --> 00:12:27.390 David Graham: Multiple representatives to the same meeting you're still providing input from that one organization right, and while we welcome discussion, we ask that you direct all your comments towards EPA not towards each other.

65 00:12:31.710 --> 00:12:35.160 David Graham: So, during today's conversation I know that there's a lot of.

66 00:12:36.060 --> 00:12:47.010 David Graham: e-Manifest hot topics that you want to talk about, but we are going to steer the conversation away from things such as data quality, paper manifest concerns, waste determinations,

67 00:12:47.460 --> 00:13:01.980 David Graham: user fees and budgets, and the highly anticipated e-Manifest third rulemaking so today our public meeting is solely focused on the discussion of increasing the adoption of electronic manifests.

68 00:13:02.850 --> 00:13:09.120 David Graham: Thank you in advance for your help, making this a fruitful conversation and I'm going to hand it back over to Steve.

69 00:13:11.850 --> 00:13:20.370 Stephen Donnelly: Yes, yeah and to sort of round up that last slide if you do have any of those concerns there's a lot of ways, we have we'll have our monthly public webinars back up.

70 00:13:20.670 --> 00:13:34.500 Stephen Donnelly: Soon, we also have our user support call so there's a lot of ways to bring up that information alright so let's go into the issue background of electronic manifests and take a brief stroll down memory lane.

71 00:13:35.670 --> 00:13:46.080 Stephen Donnelly: Now there's a lot of there's a lot of pre-history to the manifests you know we launched in 2018 there was an x signed in 2012 there was public meetings will be making.

72 00:13:46.560 --> 00:13:59.400 Stephen Donnelly: All throughout the early the early aughts in the 2010s and then there was also this was sort of bad at around the 90s, however, for the purpose of this meeting, and you get to the point.

73 00:13:59.910 --> 00:14:14.610 Stephen Donnelly: Will this will start will begin in June of 2019 when we had the advisory board meeting increasing adoption of the medical system, this was focused on the e-Manifest system has been around for a year and we were not seeing electronic we were not seeing a lot of electronic manifests.

74 00:14:15.750 --> 00:14:35.520 Stephen Donnelly: And we went to the board to specifically asked for information and action we can take to enhance the adoption electronic manifest and in September of 2019 the Advisory Board responded and recommended that the angels recommend the AMC reconsider.

75 00:14:37.350 --> 00:14:55.260 Stephen Donnelly: User registration processes and also acid we consider change to eliminate the Cross media electronic reporting real chrome air signature requirements for transactions prior to facility receipts and, in general, reevaluate the signature requirements.

76 00:14:58.230 --> 00:15:08.100 Stephen Donnelly: Alright, so following that following the Boards recommendations we recommended, we recommend it back to them.

77 00:15:09.450 --> 00:15:13.080 Stephen Donnelly: Increasing officer we so the board recommended and.

78 00:15:14.130 --> 00:15:20.190 Stephen Donnelly: We recommend it, so the board had the recommendation April 2020 and we proposed additional methods.

79 00:15:20.610 --> 00:15:26.670 Stephen Donnelly: for increasing use of electronic manifest this is now 2020, and this is our virtual advisory board meeting in April.

80 00:15:27.150 --> 00:15:36.300 Stephen Donnelly: And we proposed reengineering electronic signatures regenerated and transporters This included a non-register user.

81 00:15:36.810 --> 00:15:43.470 Stephen Donnelly: A method This included a method where the users, one person per site would be registered.

82 00:15:43.800 --> 00:15:50.130 Stephen Donnelly: This is where everyone had to be registered and then there was also a fourth solution where we discussed chromium compliance each pass.

83 00:15:50.460 --> 00:16:01.680 Stephen Donnelly: out the outcome of that meeting was the board concurred with the removal of the chroma key requirements for generator transporter signatures, as well as the initial signature by the receiving facility.

84 00:16:02.100 --> 00:16:13.230 Stephen Donnelly: So, the board listen to our proposal and said they agreed with the program's proposal that if it's not a final upload to the e-Manifest system.

85 00:16:14.070 --> 00:16:26.190 Stephen Donnelly: From the designated facility or nor correction, this is not needed to be a chromatic by signature and the board also recommended that we continue to work to integrate the manifest with the industry systems.

86 00:16:29.640 --> 00:16:32.040 Stephen Donnelly: All right, so in October 2020.

87 00:16:33.120 --> 00:16:49.530 Stephen Donnelly: EPA responded to the board's recommendations we confirmed that Cromer requirements apply only to electronic signatures for receiving facilities when submitting the final signed manifest to the EPA or when a user submits a post with the correction.

88 00:16:51.750 --> 00:17:01.770 Stephen Donnelly: And chroma requirements will not apply to electronic manifest signatures for generators transporters or the initial signature at the receiving facility when.

89 00:17:02.040 --> 00:17:12.840 Stephen Donnelly: receiving facility side to acknowledge receipt of the hazardous waste, so when that waste ends up at the loading dock and someone from the receiving facility signs electronically to say yes, we have a waste.

90 00:17:13.500 --> 00:17:23.760 Stephen Donnelly: That is a non-chromatic signature and also confirming that we will work with our stakeholders to explore solutions that will lower barriers of entry for industry.

91 00:17:24.690 --> 00:17:29.910 Stephen Donnelly: And as part of that we are here today and also in December of 2020.

92 00:17:30.330 --> 00:17:38.850 Stephen Donnelly: EPA deployed, the new quick sign functionality, which allowed those aforementioned generators transporters in the initial individuals at the loading dock.

93 00:17:39.180 --> 00:17:48.480 Stephen Donnelly: to sign a manifest electronic manifest in a non without were without using the chrome error compliant signature was clicking a button that says quick SEC.

94 00:17:52.200 --> 00:17:55.560 Stephen Donnelly: Okay, here we are, and we're almost up to we're almost up to speed.

95 00:17:56.580 --> 00:18:07.170 Stephen Donnelly: And March 2021 EPA, we had an advisory board meeting for the board to advise the Agency on its proposed program priorities and user fees or the upcoming.

96 00:18:09.150 --> 00:18:17.550 Stephen Donnelly: fiscal year the cycle and a key priority of that was direct engagements to stakeholders to increase electronic manifests.

97 00:18:19.200 --> 00:18:24.450 Stephen Donnelly: And in addition to you know reviewing the user fees, the initial program priorities which.

98 00:18:25.560 --> 00:18:27.420 Stephen Donnelly: are focused.

99 00:18:28.530 --> 00:18:29.280 Stephen Donnelly: in toto.

100 00:18:30.300 --> 00:18:33.660 Stephen Donnelly: To increasing electronic adoption of the manifest.

101 00:18:34.620 --> 00:18:45.840 Stephen Donnelly: The Board recommended the Agency address the lack of industry adoption to integrate with the hazardous waste industries private manifesting system, so a system-to-system connection with the e-Manifest and.

102 00:18:46.710 --> 00:19:01.110 Stephen Donnelly: In 2021, In June, we concur with the advisory boards recommendations, and we're committed and committed began to holding public meetings in 2021 to discuss potential options for improving the use of electronic methods.

103 00:19:03.960 --> 00:19:07.620 Stephen Donnelly: Thank you, thank you very much, there is a and, if you would like to go.

104 00:19:08.220 --> 00:19:23.310 Stephen Donnelly: In deeper to the Advisory Board recommendations and the Agency responses, this is all on the EPA website, so we have everything there if you go to the Advisory Board section, we have links to the meeting materials and the docket and also the AMC response if you are.

105 00:19:24.360 --> 00:19:33.930 Stephen Donnelly: If you are really interested in that stuff, so, I will pass this off to the e-Manifest technical lead Scott Christian take away Scott.

106 00:19:35.820 --> 00:19:36.540 Scott Christian: Thank you Steve.

107 00:19:38.220 --> 00:19:39.150 Scott Christian: Please next slide.

108 00:19:40.170 --> 00:19:43.020 Scott Christian: So, welcome to the current electronic manifest workflow.

109 00:19:44.310 --> 00:19:59.730 Scott Christian: Today we're going to go over three different sections of the agenda we're going to talk about mostly our services, those of you have been attending our monthly webinars and our packet presentations seen the user interface version.

110 00:20:01.530 --> 00:20:07.590 Scott Christian: Now we're going to go into services and explain why a little bit then I'm going to walk you through.

111 00:20:08.790 --> 00:20:23.340 Scott Christian: How the manifests API's can be used with what trunk manifests going to give you a step-by-step example with examples of a fully electronic manifest workflow as well as the hybrid manifest workflow.

112 00:20:24.870 --> 00:20:25.680 Scott Christian: And then.

113 00:20:26.820 --> 00:20:47.640 Scott Christian: William Nicholas on our team took these examples and wrote using the Python programming language, a DEMO of this and he's going to take those examples and show him but it's going to go through go pretty quickly so that's why I'm going to take the time to  explain them.

114 00:20:50.670 --> 00:21:00.630 Scott Christian: But uh yeah that's that perfect expectations explanation for the section, so what this section is technical it's going to be a technical section.

115 00:21:01.680 --> 00:21:02.340 Scott Christian: Section.

116 00:21:03.660 --> 00:21:19.170 Scott Christian: More technical and most of our public meeting sections that we've done we've had technical sessions like this in the past, but they've been more focused narrowly focused so we're trying to show you how easy it is for your system to talk to you manifest and.

117 00:21:20.550 --> 00:21:23.400 Scott Christian: Spread that information out to as many people as possible.

118 00:21:24.780 --> 00:21:29.460 Scott Christian: If you don't understand this at, all that is fine we're recording this as Steve said.

119 00:21:30.540 --> 00:21:38.160 Scott Christian: have an IT person in your company or organization look at it and be able to react and to help you.

120 00:21:39.330 --> 00:21:53.310 Scott Christian: react to your public comments I'm like I said, we are going to be providing examples of each step William's code is all on our github site The examples are all on our github site and in the docket.

121 00:21:54.870 --> 00:22:02.310 Scott Christian: So, your staff can recreate the DEMO and maybe yourself, create or recreate the DEMO.

122 00:22:04.140 --> 00:22:10.380 Scott Christian: Please contact us with questions, so we have a slide contact us slide at the end of the presentation.

123 00:22:11.430 --> 00:22:16.770 Scott Christian: We want you to use that we want to ask questions we in our team we answer questions all the time.

124 00:22:18.060 --> 00:22:31.710 Scott Christian: especially this year when we migrated from male to all electronic forms getting image only image plus data paper at this, as well as an increase in electronic map.

125 00:22:33.450 --> 00:22:38.310 Scott Christian: As you said, modest increase but it's an increase so.

126 00:22:39.360 --> 00:22:55.560 Scott Christian: we've helped people with services if you ask questions, we will answer them and probably help most of the companies on the on the call with their services questions, so we look forward to continue doing that, please use the contact us we want everyone to see the questions that come in.

127 00:22:56.760 --> 00:22:57.480 Scott Christian: On the team.

128 00:22:59.190 --> 00:23:10.740 Scott Christian: So, another explanation I'm gonna go slow on the because at the end, like I said, where it's going to go fast, I've done a little go fast, but that's the point the transaction supposed to go fast.

129 00:23:12.540 --> 00:23:18.840 Scott Christian: And then we're trying to show you options this isn't the end all be all the way we did it it's a way of doing it.

130 00:23:20.130 --> 00:23:22.650 Scott Christian: we're just trying to show there's a lot of ways to use a web services.

131 00:23:23.670 --> 00:23:35.850 Scott Christian: Finally, the main reason we're doing this is because most of the stuff comes in system to system it's actually 81% of manifests that come into the system is.

132 00:23:38.550 --> 00:23:39.030 Scott Christian: Data plus Image.

133 00:23:41.430 --> 00:23:45.360 Scott Christian: So, we have a lot of information in the system.

134 00:23:46.680 --> 00:23:47.340 Scott Christian: and

135 00:23:51.600 --> 00:23:57.870 Scott Christian: That comes in the full emits a full data let's migrate this to manifest to electronic map.

136 00:24:00.330 --> 00:24:10.080 Scott Christian: And so, getting back to that for a second and I'm going to take the section to kind of explain to everybody, what our system-to-system infrastructure is.

137 00:24:12.330 --> 00:24:25.890 Scott Christian: and hopefully you'll learn from it, so what is a ReST API we use rest APIs first of all what's an API and API is an application programming interface basically the way systems talk to each other.

138 00:24:27.990 --> 00:24:31.200 Scott Christian: And then one system sends a request the other response.

139 00:24:32.760 --> 00:24:42.930 Scott Christian: that's kind of a key piece that will get to throughout this presentation, then rest API or Representational State Transfer application programming interface.

140 00:24:44.670 --> 00:24:48.330 Scott Christian: What does that mean other than a bunch of PhD computer science speak.

141 00:24:50.640 --> 00:24:57.000 Scott Christian: it's a representation of the data in its state when it was sent to the other application.

142 00:24:58.230 --> 00:25:00.630 Scott Christian: I like to use the Mona Lisa as an example.

143 00:25:01.740 --> 00:25:11.940 Scott Christian: Everybody on this call, has seen an image of the Mona Lisa they've seen a representation of them always whether they've seen it person or they've seen it on a website.

144 00:25:13.110 --> 00:25:18.570 Scott Christian: And that representation is in the state that it was in when it was viewed.

145 00:25:20.190 --> 00:25:37.470 Scott Christian: Now let's say the folks at the Louvre want to upgrade the Mona Lisa or do something to that will make it last another 500 years.  It's 500 years old and still looks good for thousand years.

146 00:25:38.820 --> 00:25:48.480 Scott Christian: So, they do something and then they release another set of images and now you've seen another image of that same.

147 00:25:49.860 --> 00:25:50.220 Scott Christian: picture.

148 00:25:52.440 --> 00:25:56.940 Scott Christian: let's take this to manifest, probably a more relatable topic than art history.

149 00:25:58.350 --> 00:26:04.830 Scott Christian: The generators electronic manifest they see that is one representation of the manifest.

150 00:26:06.450 --> 00:26:06.960 Scott Christian: Then.

151 00:26:08.070 --> 00:26:13.950 Scott Christian: They sign it, the transport season now they're seeing a slightly different representation, because there's a generator signature on it.

152 00:26:14.610 --> 00:26:23.550 Scott Christian: Now there's a second representation, and the transporter signs.  The TSDF sees that there's two signatures on the manifest and signs and now there's three representations of the same thing, but it's how each one saw the manifest.

153 00:26:24.540 --> 00:26:34.140 Scott Christian: And so that's a reason we use rest, this is how that data is stored and kept and how it's transferred between each user that sees it.

154 00:26:35.160 --> 00:26:44.490 Scott Christian: Also, these are wildly type widely used API's they conform to certain standards, and when you use things that are important set certain standards.

155 00:26:45.000 --> 00:26:51.090 Scott Christian: are more likely to be well understood by developers, both when it's pretty much how the Internet talks rest API.

156 00:26:51.750 --> 00:27:03.960 Scott Christian: you're probably using rest API is watching this presentation if we're using teams, I would say, you were using rest APIs to watch this presentation, but I haven't looked into zoom's code so I'm going to say probably.

157 00:27:05.190 --> 00:27:13.650 Scott Christian: And then it's also more tolerant to the ups and downs of system so rest does give us some flexibility.

158 00:27:16.080 --> 00:27:16.410 Scott Christian: Thank you.

159 00:27:18.060 --> 00:27:21.060 Scott Christian: And then, this image here is just kind of helped drive in the point.

160 00:27:22.140 --> 00:27:44.280 Scott Christian: API's they're basically a lot like user interfaces 10,000 feet you user provides username and password a system provides an API key and credentials, and login sessions or API sessions are created and then people can exchange they know their trusted they can exchange information.

161 00:27:45.450 --> 00:27:47.460 Scott Christian: amongst themselves based off their.

162 00:27:48.570 --> 00:27:49.230 Scott Christian: credentials.

163 00:27:50.550 --> 00:27:53.850 Scott Christian: let's go to the next slide so that's great that they can.

164 00:27:54.990 --> 00:28:06.510 Scott Christian: communicate using the rest API but how do they speak what language are they talking what or how are they speaking to each other, this is why we use json is JavaScript object notation.

165 00:28:07.620 --> 00:28:13.710 Scott Christian: And like so with rest it's basically a fancy title for tech text file with predictable format.

166 00:28:14.730 --> 00:28:18.420 Scott Christian: I'm sure many of you heard of xml been around.

167 00:28:19.860 --> 00:28:26.280 Scott Christian: very similar it's you've got a text file with the predictable format.

168 00:28:27.630 --> 00:28:30.450 Scott Christian: The nice thing about json much more lightweight.

169 00:28:31.680 --> 00:28:36.420 Scott Christian: And we use it so when your system sends a request.

170 00:28:38.100 --> 00:28:41.340 Scott Christian: We respond in the same way with the same key.

171 00:28:42.570 --> 00:28:52.170 Scott Christian: information that you would request based off of a thing we call a schema, so how json is structured it's about it's a key value pair the key.

172 00:28:52.920 --> 00:29:07.770 Scott Christian: Is what this information generally is, and the value is what you're sending at that time, so we have an example here printed DOT information and then NA1993 waste diesel fuel.

173 00:29:09.060 --> 00:29:11.010 Scott Christian: Has a hazard Class three Packing group three.

174 00:29:12.390 --> 00:29:16.650 Scott Christian: So, the key printed DOT information it's on every hazardous waste line.

175 00:29:18.600 --> 00:29:23.460 Scott Christian: There is, but the value is going to be different, on the same manifest evaluate the different.

176 00:29:24.570 --> 00:29:27.870 Scott Christian: And there's a colon to separate the words as well.

177 00:29:28.920 --> 00:29:35.760 Scott Christian: So that's that now we're going to look at it, an example, this kind of mapped out the next slide.

178 00:29:40.170 --> 00:29:45.120 Scott Christian: Please, so we look here, this is a json.

179 00:29:47.100 --> 00:29:53.070 Scott Christian: we'll call it a file, but right there and then at the bottom, you see them.

180 00:29:54.570 --> 00:30:00.180 Scott Christian: waste line a waste line typical line one waste line printed from our system.

181 00:30:01.980 --> 00:30:04.710 Scott Christian: And DOT Hazardous is true.

182 00:30:06.090 --> 00:30:18.810 Scott Christian: If you look up their scopes goes down to 9a and you have X marked off its hazardous material then print DOT information, the same example from the previous slide and it's right there in 9b.

183 00:30:20.070 --> 00:30:22.950 Scott Christian: You have that there now as we look through.

184 00:30:24.630 --> 00:30:30.300 Scott Christian: A you have your number of containers type total quantity and.

185 00:30:31.470 --> 00:30:40.650 Scott Christian: Your unit of weight of volume, as well as the least code and those all mapped out now nice things we do is we have description, so if you were to retrieve this manifest.

186 00:30:41.550 --> 00:30:58.110 Scott Christian: you'd be able to see all the DM means battle drums barrels kegs chances are your system already knows that, but we have it in there, so for humans reading this json they have an easier time doing it or D001 they might not have all that stuff memorized so oh it's ignitable waste.

187 00:30:59.700 --> 00:31:01.380 Scott Christian: Depending on who's looking at.

188 00:31:02.940 --> 00:31:04.980 So, you can see, and.

189 00:31:06.030 --> 00:31:06.420 Scott Christian: perfect.

190 00:31:07.800 --> 00:31:08.340 Scott Christian: Now.

191 00:31:09.900 --> 00:31:22.620 Scott Christian: it's great I've just explained, all that, but why would you use API's. David Graham who spoke earlier summed it up great reason you use API's for the same reason you didn't nail gun instead of a hammer.

192 00:31:23.520 --> 00:31:32.190 Scott Christian: a hammer, you can build a house with a hammer and nail people done it for centuries, but it's a lot easier and it provides things in a more.

193 00:31:33.210 --> 00:31:42.690 Scott Christian: Reliable and repeatable format for a way of doing things so it helps take user error, out of the situation.

194 00:31:44.370 --> 00:31:50.010 Scott Christian: yeah, everybody here has ever used hammer nails probably smash their thumb you don't do that with a Nail gun.

195 00:31:52.290 --> 00:32:04.230 Scott Christian: So, you can take that either air out in a way, you can also help improve your compliance you by using API's and system, the system to kind of repeat those tasks that are repeatable.

196 00:32:06.030 --> 00:32:10.590 Scott Christian: And also have your insurances So if you look at our schemas there are.

197 00:32:11.940 --> 00:32:15.690 Scott Christian: Some basic insurance is on making sure that data is correct, but.

198 00:32:17.460 --> 00:32:23.670 Scott Christian: We also have business rules in the system as well, so the nice thing is using the API is.

199 00:32:25.110 --> 00:32:36.630 Scott Christian: You have some flexibility using your own programs and systems and adapting to this, so you can take a step out of the whole process rather than having to fill out paper forms.

200 00:32:40.020 --> 00:32:48.600 Scott Christian: So, and you know people we do recognize people have more patience with a paper form than they do with an electronic interface.

201 00:32:50.730 --> 00:32:51.180 Scott Christian: But.

202 00:32:52.650 --> 00:32:58.920 Scott Christian: They want once implemented those but try forms can work.

203 00:33:00.120 --> 00:33:00.720 Scott Christian: Very well.

204 00:33:02.460 --> 00:33:02.940 Scott Christian: So.

205 00:33:04.140 --> 00:33:07.350 Scott Christian: What and Why is he manifest using json well.

206 00:33:08.610 --> 00:33:16.020 Scott Christian: Like I said before, it's the same reason rest APIs are widely adopted standards more people can understand it.

207 00:33:17.130 --> 00:33:19.620 Scott Christian: How to use it more folks can.

208 00:33:20.670 --> 00:33:29.880 Scott Christian: be there to develop and there's a lot of tools available to support you and your developer. Nearly every tool set available can interact with ReST API's and JSON.

209 00:33:30.660 --> 00:33:41.550 Scott Christian: you're going to see a DEMO written by William on our staff, it was written in Python he manifests is written in Java David Graham he wrote some stuff using JavaScript.

210 00:33:42.690 --> 00:33:47.580 Scott Christian: Seen some commercial off the shelf products, a homebrew.

211 00:33:48.930 --> 00:33:51.540 Scott Christian: stuff that people use so.

212 00:33:53.580 --> 00:33:59.520 Scott Christian: chances are if there's a tool set out there, it can use API's even excel.

213 00:34:00.540 --> 00:34:04.620 Scott Christian: can use API's and word, as I was recently reminded.

214 00:34:06.540 --> 00:34:18.450 Stephen Donnelly: yeah, we build a manifest scalability manifest to be as neutral as possible that's why we go so far as you know, with the services and the data structures, because we know you have your systems.

215 00:34:19.260 --> 00:34:25.350 Stephen Donnelly: We have our system, so you can call it whatever you want, in your system, but if you're sending up do T hazardous.

216 00:34:26.130 --> 00:34:32.910 Stephen Donnelly: it's you're just going to send them something and you say, whatever your system says God has, as long as you send that marker up to our system and said.

217 00:34:33.300 --> 00:34:39.750 Stephen Donnelly: we're telling you manifest is do T hair, is it is this is the structure, they want this is what they want in that field we're good where is.

218 00:34:41.310 --> 00:34:42.870 Stephen Donnelly: Your is, we want to be as.

219 00:34:44.250 --> 00:34:45.120 Stephen Donnelly: easy as possible.

220 00:34:47.280 --> 00:34:52.470 Scott Christian: Perfect thanks day and then so now we're getting to the second phase of.

221 00:34:55.560 --> 00:35:11.460 Scott Christian: Our agenda, which is the workflows and we're going to do a fully electronic and go through it fully trying to go through a background of the shipment what the shipment basically is and then go through the.

222 00:35:12.990 --> 00:35:16.590 Scott Christian: process, step by step, and then we're going to go over we're going to do the same thing with the hybrid.

223 00:35:17.730 --> 00:35:22.020 Scott Christian: So just one sheet all see that goes this this next slide.

224 00:35:23.730 --> 00:35:26.070 Scott Christian: So, the full electronic background of the shipment.

225 00:35:27.210 --> 00:35:34.230 Scott Christian: In this example, a Tsdf company is arranging the shipment for a generator that can use fully electronic manifests.

226 00:35:35.370 --> 00:35:44.940 Scott Christian: The generator recently submitted a notification for the quadrennial sqG renotification and the Tsdf needs to update their systems information regarding this customer.

227 00:35:45.720 --> 00:35:57.240 Scott Christian: Now one little caveat So yes, this is a public service announcement to use our services to update your data, because a lot of sq geez have re notified.

228 00:35:58.380 --> 00:36:09.000 Scott Christian: Of the system does have I'll get into that when we go to the save a tool that will allow you to use them use record for data straight without you needing to.

229 00:36:09.300 --> 00:36:16.830 Scott Christian: upload the information, but in this case the Tsdf likes to upload the information from their system, and that is something that they can do.

230 00:36:18.630 --> 00:36:27.420 Scott Christian: And in this exercise will also update a waistline and take a manifester receipts, so this is, you know what has been described as kind of the typical shipment.

231 00:36:28.500 --> 00:36:36.120 Scott Christian: The driver shows up and change needs to be made to the manifest you can do that, via services and then move us along.

232 00:36:37.980 --> 00:36:45.060 Scott Christian: let's get So the first thing and going back several slides authentication out of the key to this.

233 00:36:50.130 --> 00:36:55.650 Scott Christian: To everything it tells us what you your user can do and what it cannot do.

234 00:36:57.480 --> 00:37:09.450 Scott Christian: and make sure you are so the authentication calls a simple call you'll see down here in the examples it's a request get.

235 00:37:11.670 --> 00:37:13.350 send them.

236 00:37:15.300 --> 00:37:27.270 Scott Christian: That was my water that almost spilled, sorry for all you have to hear that you send that URL with the API key and API key

237 00:37:28.200 --> 00:37:35.250 Scott Christian:  as another public service never shares your API key it's just like a username and password you shouldn't share it.

238 00:37:36.390 --> 00:37:38.370 Scott Christian: But this API key.

239 00:37:39.900 --> 00:37:53.700 Scott Christian: Is there a substitute those send it off, you get back a token and an expiration 20 minutes later the expiration that we use which will get back to open for the next 20 minutes use that token, for all your all your calls.

240 00:37:54.780 --> 00:38:03.510 Scott Christian: And then we show you the Python function that blame wrote you man off is the function and where you can get it on github.

241 00:38:04.650 --> 00:38:05.100 Look at.

242 00:38:06.270 --> 00:38:16.440 Scott Christian: Finding a generator so with the public service announcement, we do have a site search and we released this rather recently within the past year.

243 00:38:17.910 --> 00:38:32.610 Scott Christian: And we want folks to use it, because it gives you a chance of getting the best information about your sites and ensuring that sites easy manifest because if you put a needle or C suite and they actually have an ID.

244 00:38:34.710 --> 00:38:43.830 Scott Christian: they're not going to see that manifest until that manifest is corrected so it's important to make sure your data is up to date, and we have the site search.

245 00:38:45.630 --> 00:38:46.170 Scott Christian: API.

246 00:38:47.220 --> 00:38:53.160 Scott Christian: And what it does is you send criteria that may make So if you have the ID and send.

247 00:38:53.730 --> 00:39:10.020 Scott Christian: A site id with the site search or one of our other site services and get information back about that site, whether it exists the details about that site, but you can also send the site search up and let's say you wanted to know all the CVSs in DC.

248 00:39:11.100 --> 00:39:22.560 Scott Christian: You can do that you would get back a lot of pages of results, you can cycle through, and the response is what you would get back and shows you details but CBS and Washington DC area.

249 00:39:25.200 --> 00:39:30.540 Scott Christian: William's function Python site search, if you look in the looking that.

250 00:39:32.160 --> 00:39:39.330 Scott Christian: Python file you'll be able to see it and see how he built that and then you can test out with those examples.

251 00:39:39.570 --> 00:39:45.300 Stephen Donnelly: Yes, really answer updating that stuff every day, every single day, those that site information is getting updated so.

252 00:39:46.710 --> 00:39:47.370 Scott Christian: You know.

253 00:39:47.970 --> 00:39:56.040 Stephen Donnelly: As soon as they submit it, they click enter on a submission to update or create a new site that is available to you for you to start off so yeah.

254 00:39:56.460 --> 00:39:59.730 Scott Christian: I'm willing to bet that while I've been speaking several sites have been up there.

255 00:40:03.000 --> 00:40:04.290 Scott Christian: So, the.

256 00:40:05.880 --> 00:40:15.720 Scott Christian: To create a fully electronic manifest safe so they're going to go through they know that the generator is fully electronic.

257 00:40:16.290 --> 00:40:31.470 Scott Christian: they're sending up that new site information that they pulled down from RCRA info in there, they didn't necessarily have to do that, they can just send the ID and the generators site and mailing address will be populated if it is in the database.

258 00:40:33.990 --> 00:40:40.290 Scott Christian: And you can use that so that way what you're sending up is what matches RCRA Info.

259 00:40:41.340 --> 00:40:42.840 Scott Christian:

260 00:40:44.040 --> 00:40:58.470 Scott Christian: They can you send the manifest up, and the response, and the response back is the manifest tracking number that this manifest will have throughout and will be used on every subsequent call to manifest in relationship to this manifest.

261 00:40:59.610 --> 00:41:00.180 Scott Christian: So.

262 00:41:01.950 --> 00:41:07.530 Scott Christian: Now that this manifest has been created that the  dispatcher driver to the generators.

263 00:41:08.610 --> 00:41:11.100 Scott Christian: Please go to the next.

264 00:41:12.720 --> 00:41:17.640 Scott Christian: If they dispatch the driver to the generator and the driver is loading the.

265 00:41:18.690 --> 00:41:20.670 Scott Christian: drums on to their vehicle.

266 00:41:21.720 --> 00:41:24.690 Scott Christian: And they noticed couple drums can't go on.

267 00:41:26.100 --> 00:41:41.160 Scott Christian: and those drums are not ready to be shipped or they're not labeled properly, so we're not going to take these two this time, we'll come back and get it on our next scheduled shipment.

268 00:41:42.300 --> 00:41:47.850 Scott Christian: And so, the transporter in this case you have it as an example, using their own phone.

269 00:41:50.190 --> 00:41:52.140 Scott Christian: And an APP within their phone.

270 00:41:53.520 --> 00:42:08.700 Scott Christian: They make an update on their device they send that update with that manifest tracking number that was previously begun, and they get a confirmation that the update has been made, again we have the Python code for how you can do an update.

271 00:42:11.220 --> 00:42:16.950 Scott Christian: So, now that everything's ready this manifest is ready to go packed on the truck the.

272 00:42:17.970 --> 00:42:31.680 Scott Christian: transporter than says all right, the generator needs to sign, so they send a request, we have a user interface a link service and this user can be used for signatures and needs to get to the dashboard to get to the bulk sign page.

273 00:42:32.070 --> 00:42:39.330 Scott Christian: It can be used to get to a manifest and read only be used to get the manifest and the ability to sign it as well, in this case we're doing is just sign it.

274 00:42:40.350 --> 00:42:48.570 Scott Christian: And they send the request for info sends it back to the transporters phone because that's who requested the generator could have done it themselves as well.

275 00:42:49.110 --> 00:42:59.190 Scott Christian: And then the transporter out of band, out of the system  emails or texts, the link which came back in that response to the generator.

276 00:42:59.970 --> 00:43:09.600 Scott Christian: And then the generator could simply click on the link logs into RCRA info and goes to the quick sign for taking right to the signature page to click sign.

277 00:43:11.220 --> 00:43:16.590 Scott Christian: You will see this very fast quickly in Williams DEMO but.

278 00:43:19.410 --> 00:43:22.770 Scott Christian: There you have it now; we go to the transport us to do the same thing.

279 00:43:23.940 --> 00:43:26.850 Scott Christian: So, they click you I link service.

280 00:43:27.930 --> 00:43:35.730 Scott Christian: So, they can sign in their in their system they see the login to record info they click quick sign and finally.

281 00:43:38.130 --> 00:43:38.850 Scott Christian:

282 00:43:40.800 --> 00:43:52.440 Scott Christian: Now go to the next slide and they need to get the printed manifest for the truck and, of course, we have a service for that, too, and the transporters phone calls it up.

283 00:43:53.850 --> 00:44:12.510 Scott Christian: Whether the unbeknownst to us or not calls it gets that image back and the transporter then just needs to send it to a printer whether they have not as remember may remember these electronic methods can be done on an eight and a half piece of paper in 8 half by 11 pieces of paper.

284 00:44:14.430 --> 00:44:14.940 Scott Christian:

285 00:44:16.200 --> 00:44:39.150 Scott Christian: You don't need an impact printer or a dot matrix printer for it just need a printer little handheld printer, or the generator printed out for you, but the one sheet of paper goes in the truck and the TSDFs on their way they drive on the highway get to the TSDF.

286 00:44:42.900 --> 00:44:51.450 Scott Christian: And then the Tsdf user uses the UI link service in their application or they just login to the system.

287 00:44:52.380 --> 00:45:05.880 Scott Christian: And they send the request, and they get the link for that individual sign, so they can sign for receipt we're only showing quick sign in these examples today.  hopefully you have seen the full CROMERR sign before.

288 00:45:06.990 --> 00:45:15.330 Scott Christian: But this is to show you can quick sign for initial receipt a the Tsdf and then do a full sign later.

289 00:45:19.680 --> 00:45:25.920 Scott Christian: Next, we'll have hybrid scenario.  Scenario two is the same exact thing as scenario one except.

290 00:45:27.060 --> 00:45:35.700 Scott Christian: None of the generator's, registered signers are not on a site at the time shipment another individual that's trained with under.

291 00:45:36.870 --> 00:45:43.380 Scott Christian: Duty transportation title 49 training requirements is on site and can sign as a generator.

292 00:45:44.430 --> 00:45:49.170 Scott Christian: This is why we recommend people when they're doing their training, they.

293 00:45:50.280 --> 00:45:57.630 Scott Christian: They register for he manifests would cut down on this, but it's a situation Somebody needs to sign and.

294 00:45:59.340 --> 00:46:08.280 Scott Christian: That wasn't available on this date, but we have the hybrid option to protect that, as well as for sites that aren't registered yet.

295 00:46:10.560 --> 00:46:12.600 Scott Christian: And then in this exercise we.

296 00:46:14.370 --> 00:46:23.730 Scott Christian: will change the manifest to a hybrid make an update and take it through two to the TSDF.

297 00:46:24.990 --> 00:46:25.770 Scott Christian: The next slide.

298 00:46:26.790 --> 00:46:31.350 Scott Christian: The electronic manifest, this is the same exact thing we did before same exact manifesting.

299 00:46:32.550 --> 00:46:38.370 Scott Christian: And they sent the manifest that get back to manifest tracking numbers, the response.

300 00:46:40.050 --> 00:46:40.620 Scott Christian:  301 00:46:42.960 --> 00:46:45.240 Scott Christian: So, when they came to the.

302 00:46:46.260 --> 00:46:49.290 Scott Christian: transporter comes to the site they notice person isn't there.

303 00:46:51.120 --> 00:46:55.950 Scott Christian: So, they have to make an update like they did before it's the same if you notice the same update call.

304 00:46:57.150 --> 00:47:12.360 Scott Christian: William made so you'll see that later same function like, I said it's repeatable reliable and, but this time instead of updating a waste line they're updating it from electronic to try Memphis to.

305 00:47:14.100 --> 00:47:24.660 Scott Christian: The nice thing is the generator was prepared, in this case, so they already have the printed piece of paper that they need to sign on paper per the hybrid.

306 00:47:25.890 --> 00:47:38.940 Scott Christian: Regulations they don't need to open upload that piece of paper they keep that on site, I believe, three years for the regulations, whatever the regulations say for record keeping requirements for hybrid manifests.

307 00:47:40.020 --> 00:47:51.090 Scott Christian: And they keep that piece of paper, but they have pre- printed because they knew the registered signers will not be off that day, so they wanted to save some time that's already there.

308 00:47:53.460 --> 00:47:58.440 Scott Christian: So, now that the manifest been update the UI link service is there, they.

309 00:48:00.540 --> 00:48:05.220 Scott Christian: transporter sense up the log in the system, the request, just like last time.

310 00:48:06.930 --> 00:48:07.920 Scott Christian: To get updates.

311 00:48:11.880 --> 00:48:16.710 Scott Christian: same exact things last time to send it to a printer with that.

312 00:48:18.120 --> 00:48:19.170 Scott Christian: generators.

313 00:48:20.970 --> 00:48:25.230 Scott Christian: printed name that was also sent when they sent it to change it to a hybrid.

314 00:48:27.000 --> 00:48:38.130 Scott Christian: On the manifest as well as the quick signing the transporter and the transporters on their way so see this repeatable process going much quicker and then use the UI link service.

315 00:48:39.540 --> 00:48:56.520 Scott Christian: So, in this case we're giving the same UI link service we're trying to show the flexibility of unique user interface link service this one goes to the bulk sign page, so the TSDFs computer they send it up and then they're taken to the bulk sign like sign multiple quick sign manifests.

316 00:48:58.140 --> 00:49:18.810 Scott Christian: So, they don't have to do just one, at a time, if you know we got a question last week, where a site was if I'm the transporter can I use the box answer, and the answer is yes, so the if the second transport is taking a waste that has 50 manifests on it.

317 00:49:20.460 --> 00:49:26.670 Scott Christian: The driver doesn't have to sit there and sign each one individually, they can quick sign off.

318 00:49:29.250 --> 00:49:42.450 Scott Christian: there's definitely some power here now with this, I am going to hand over the MIC to William Nicholas to go over the DEMO and thank you all very much for your time today.

319 00:49:45.240 --> 00:49:45.900 William Nicholas: Thanks Scott.

320 00:49:46.980 --> 00:49:56.940 William Nicholas: So, what you're about to see is a video, and while Scott correctly notes that this will go a little bit quicker it's still going to be significantly slower than if we.

321 00:49:57.480 --> 00:50:13.950 William Nicholas: were doing this live with a computer all the steps that you're going to see will have explanations and the advantage of using a tool, like our services is that this can all happen lightning fast in the background once you've set up a process using your computer code.

322 00:50:15.750 --> 00:50:25.950 William Nicholas: As noted the DEMO and the associated json files will be on our website and the Federal Register docket. Couple of notes: the runtime is about 16 minutes.

323 00:50:26.460 --> 00:50:38.220 William Nicholas: The audio on this is a little quiet, so I encourage you to turn up your speakers and I'll put a note in the chat when we're wrapping up to remind you, to turn it back down so we don't blow out your eardrums we're talking to you later.

324 00:50:39.090 --> 00:50:50.760 William Nicholas: And the final thing I'll remind you, is if you're having trouble seeing the video. I'll encourage you to go up to the top right corner of your screen there's a view button in the zoom tab.

325 00:50:51.210 --> 00:51:00.300 William Nicholas: And you can play with some options there in case you have some issues with visibility with that I'm going to turn it over to Steve and encouraged him to roll the video thanks.

326 00:51:08.970 --> 00:51:14.280 Hello everyone, welcome to the he manifests Python services DEMO.

327 00:51:15.330 --> 00:51:24.990 you've just heard from us explaining the details of how to use our restful API services to.

328 00:51:26.370 --> 00:51:39.840 Set up sign and distribute links for generators transporters TSETFs to process a manifest foil electronically, and then additionally in a hybrid status.

329 00:51:41.070 --> 00:51:57.750 What we're going to show you here is a live DEMO of all of that process demonstrated in Python using our e manifest package, enabling you to with your own Python installation.

330 00:51:58.260 --> 00:52:11.490 conduct this business and utilize services to take advantage of the benefits of fully electronic manifests and hybrid manifest and to make the process easier faster for you.

331 00:52:12.750 --> 00:52:30.420 So, just like the slides, we have the same objectives we're going to set things up authenticate and then generate sign and update a foil electronic manifest However, unlike the slides we're going to start with the Python specific setup.

332 00:52:32.100 --> 00:52:47.070 To do that we're first going to bring in the record info teams, he manifests package This assumes that you've installed it ahead of time using you know for Python your pip install process or you can also do this via conduct.

333 00:52:49.080 --> 00:53:03.570 Next, we're going to authenticate our account This assumes ahead of time that you have enabled API access in record info if you have questions about that feel free to consult the documentation or send us an email.

334 00:53:05.040 --> 00:53:20.670 But I'm going to feed the variables for API ID and our API key into the system if you're working in an environment where you have multiple users, you can certainly set that up to be variable and to require somebody to put it in each time.

335 00:53:23.070 --> 00:53:38.250 Next, we're going to authenticate using the manifest package we've used the authentication command, as well as the variables we've just selected to authorize us for the pre prod instance.

336 00:53:40.560 --> 00:53:49.260 That tells us with this authentication successful message that we are ready to go and that we can access anything that our record info account has permissions for.

337 00:53:51.030 --> 00:54:04.620 Start we're going to find our generator and we're going to put in some search parameters here the name and the zip code that we'd like, in this case Jen 2021 here in our own tenant 22202.

338 00:54:06.510 --> 00:54:13.740 And that might take a second depending on how many parameters you put in and how much it has to come back.

339 00:54:14.520 --> 00:54:29.580 But after we send out that command, you'll receive something that looks like more or less than excel spreadsheet what's called a pandas data frame if you're familiar with Python and that will include whatever is relevant to your search parameters.

340 00:54:30.660 --> 00:54:37.110 So, we've got the one back that's you know, an EPA site ID our test generator right here and.

341 00:54:38.610 --> 00:54:51.390 that's when we would create you know we'd use some of this information to populate our manifest so we would need to generate a json file I'll show that here.

342 00:54:53.310 --> 00:54:58.020 And this includes information about say that generator right there.

343 00:54:59.430 --> 00:55:00.960 That we can pull from.

344 00:55:02.550 --> 00:55:03.570 This output here.

345 00:55:06.990 --> 00:55:11.070 And we save this file as a json object.

346 00:55:14.160 --> 00:55:31.980 Once we've saved that file here in our local folder, we can use the SAVE command again in the manifest package to send that to record info and we get back confirmation that it's been saved, and we get our manifest tracking number.

347 00:55:33.510 --> 00:55:53.760 That manifest tracking number, we can use to populate other commands but for now we're going to use it to populate an update so again we're going to open up a json file that we've created you know we've put in the manifest tracking number that we got back from step four.

348 00:55:55.500 --> 00:55:59.040 and any other information that we would want to update.

349 00:56:01.860 --> 00:56:13.500 Once we've done that, we use the update command to send that out to recur info and to make some changes we've gotten confirmation here that says that that has been successfully updated.

350 00:56:14.910 --> 00:56:21.150 Now, as the generator I can generate the I'm going to generate the link to sign that.

351 00:56:22.200 --> 00:56:31.890 So, we've generated our link I can go ahead and click that and because I'm logged in to record info it will open up the manifest.

352 00:56:33.330 --> 00:56:38.910 And if we scroll all the way down to the bottom, here I can go ahead and click sign because I've got the permission for that.

353 00:56:42.270 --> 00:56:47.490 And that's great so now returning here, I can generate a link.

354 00:56:48.690 --> 00:56:52.050 That I'll go ahead and send to the transporter.

355 00:57:07.680 --> 00:57:19.560 Now that I've gone ahead and done that I'm going to pass things over to Scott serving as our transporter and will demonstrate how someone working through transporter could sign this even from their phone.

356 00:57:21.090 --> 00:57:31.860 Thank you, William and as the transporter I'm taking this link I could have clicked on it, but I'm going to paste it in and I'm brought to the pre-production login screen.

357 00:57:32.910 --> 00:57:36.630 Where I click on scotty Christian rapper for.

358 00:57:37.680 --> 00:57:38.430 Sunday sign.

359 00:57:40.200 --> 00:57:53.820 And I'm in here I'm taking directly to the sign screen, I can review the manifest that I've just worked on, with my client the generator scroll all the way through.

360 00:57:57.240 --> 00:57:59.520 right here, I can now click quick side.

361 00:58:01.140 --> 00:58:04.860 Last me some questions quick sorry and.

362 00:58:06.120 --> 00:58:07.920 There we go I'm taking back to.

363 00:58:13.230 --> 00:58:15.840 The screen, where I can see that I have just.

364 00:58:18.690 --> 00:58:19.500 sent it back to you.

365 00:58:22.830 --> 00:58:41.670 Great and now that our transporter has signed, I can get any of the details I want I'm going to call out for updates so I'm going to use the manifest package, the get attachments function and I'm going to plug in the manifest tracking number that we have for this manifest.

366 00:58:42.900 --> 00:58:48.750 And you'll see here over in my folder structure as I refresh that.

367 00:58:49.920 --> 00:59:01.890 PDF and json come back with additional detail about that manifest and so, if I want to review that here in the process that's available tonight.

368 00:59:02.910 --> 00:59:10.320 But we're going to assume that I'm comfortable with things and I'd like to finish it up and send it for receipt at the.

369 00:59:11.190 --> 00:59:24.390 Tsdf so again I'll generate a link and this time this link will be specific to the Tsdf and I'm going to send that over to David, who is serving as our receiving facility.

370 00:59:27.150 --> 00:59:33.690 Thank you, William as the Tsdf now I now have that URL link that.

371 00:59:34.860 --> 00:59:38.250 William's application generated from me and paste that here.

372 00:59:40.290 --> 00:59:42.450 Only again, you could just click it but.

373 00:59:44.370 --> 00:59:58.860 for purposes of this demonstration already have that URL copied to your clipboard so this point, I can go through, I can specify the information generator information, the generator ids correct transporter information all the stuff.

374 01:00:00.960 --> 01:00:06.480 Like that again, all the way down to the bottom, just like Scott, did I can click some like such.

375 01:00:07.800 --> 01:00:10.410 confirm that all the information is again correct.

376 01:00:14.190 --> 01:00:19.320 Now that manifest has been signed by the generator transporter and it doesn't need to receive facility.

377 01:00:23.700 --> 01:00:33.840 So, thanks to the work of David Scott and myself we've now set up the Python environment authenticated our account.

378 01:00:34.200 --> 01:00:54.900 found the generator created update and distributed for signature our electronic manifest and along the way we called out for updates and got those files back to us all with the simplicity of the restful API is and the repeatability of a Python process.

379 01:00:57.300 --> 01:01:03.840 Now we're going to take some time and show you how this might work with a hybrid manifest.

380 01:01:06.780 --> 01:01:17.730 And now we're going to demonstrate the hybrid manifest that we again discussed on the slides previously, this is similar to the foil electronic process but.

381 01:01:18.270 --> 01:01:30.450 Has a couple of notable differences will start out the same way, we will bring in the manifest package, and then we will authenticate ourselves with record info.

382 01:01:31.800 --> 01:01:40.770 Now that we've successfully done that, we will again pass a json object containing the information about our manifest to record info.

383 01:01:43.140 --> 01:01:51.030 And again, we've got a successful message telling us it's been saved and the manifest tracking number that's associated with this manifest now.

384 01:01:52.740 --> 01:02:01.680 However, now we want to change the manifest to a hybrid because we've heard from our partners in this process that this one will need to be a hybrid.

385 01:02:03.030 --> 01:02:17.280 And, like the full electronic process, we can accomplish a change, using the update command and, in this case, we're going to send the update json but we've now changed the submission type to hybrid.

386 01:02:18.540 --> 01:02:20.190 So, when we send this out.

387 01:02:23.130 --> 01:02:29.880 we've updated the manifest and the status and record info will show as hybrid.

388 01:02:31.260 --> 01:02:40.440 Now that we've updated, I'm going to go ahead and generate a ui link and send that directly to Scott, who is serving as our transporter.

389 01:02:41.760 --> 01:02:54.570 Thank you get William, so this new user is using a tablet they've already from there from their tablet and the APP that they're they built on their there's their company built on their tablet.

390 01:02:55.290 --> 01:03:02.310 The transporters taken directly to the link for the manifest that was just updated from electronic to hybrid.

391 01:03:05.400 --> 01:03:06.090 I log in.

392 01:03:07.590 --> 01:03:17.910 And I see the tesla and I see yes, it's now a hybrid manifest, then I scroll down and there's a lot here, because the review is kind of big manifest.

393 01:03:20.130 --> 01:03:20.640 and

394 01:03:21.840 --> 01:03:33.750 generator and we see oh perfect so Jim tester who's the generator and they sign, and I can now quick sign this manifest so the information was uploaded.

395 01:03:34.530 --> 01:03:46.260 And I can now go and click sign see the transporting knowledge we receive materials quick sign again and I'm taking back to the dashboard.

396 01:03:47.970 --> 01:03:50.160 And then I drive away and.

397 01:03:52.530 --> 01:03:53.340 And it backed away.

398 01:04:00.780 --> 01:04:09.120 Excellent thanks Scott, and so, if I want to get an update on that and confirm that we've gotten our transporter signature.

399 01:04:09.870 --> 01:04:31.740 I can go ahead and run that get attachments command and you'll see here and my file structure that I've gotten that information and this you manifest json object is going to include information about the manifest the status of it, and you know who has signed.

400 01:04:33.690 --> 01:04:37.410 In this case, I've just seen that Scott has signed up.

401 01:04:38.610 --> 01:04:54.540 So excellent now it's ready to be signed once it gets to the TSDF and so I'll generate a link specifically for are receiving facility and I'll send that over to David, who is serving as our receiving facility.

402 01:04:57.270 --> 01:05:05.820 All right, thank you, William again so for purposes of this demonstration I'm already logged in as our Tsdf.

403 01:05:06.960 --> 01:05:11.640 And then I click on that link that Williams DEMO application 70.

404 01:05:13.980 --> 01:05:17.070 pulls up a new tab again I'm already signed in.

405 01:05:18.480 --> 01:05:33.720 I can see, I have the option to chrome air sign or click sign these manifest that were just sent to me I'm going to go ahead and click science and that's all I needed a moment and I click both like dollar.

406 01:05:34.830 --> 01:05:39.120 filter or just sign manifest that I want to sign.

407 01:05:40.650 --> 01:05:46.320 Also review if you'd like but for purposes of the day we're just going to go ahead and click sign both these manifests.

408 01:05:47.340 --> 01:05:49.830 Again, confirmed information is correct.

409 01:05:52.380 --> 01:05:54.960 And our electronic manifest now complete.

410 01:05:57.390 --> 01:06:09.000 Thanks David so now we've managed to show you both fully electronic and hybrid options to complete the manifest process.

411 01:06:09.570 --> 01:06:22.380 all the way from the initial creation of the manifest through the signature at the receiving facility in this case, using Python and the restful APIs.

412 01:06:22.920 --> 01:06:38.310 Of the record info system enabling you to leverage new tools and reduce the friction allowing you to have a more pleasant rapid and efficient manifesting experience.

413 01:06:40.140 --> 01:06:54.360 we're going to come back to our presentation now, but if you have questions about this, we encourage you to reach out to us individually or to check out our<EMAIL_ADDRESS>slash us EPA slash you manifest.

414 01:06:55.410 --> 01:06:55.800 Thank you.

415 01:07:07.410 --> 01:07:10.470 Stephen Donnelly: All right, what a video Thank you.

416 01:07:14.370 --> 01:07:26.610 William Nicholas: So, thanks everyone for watching the DEMO as a reminder, this is sample scenario, this is simplified one transporter, and everything takes a little bit longer because we're explaining.

417 01:07:27.360 --> 01:07:34.290 William Nicholas: When you're implementing this in your own system, this is, you know more or less instantaneous. The power that these.

418 01:07:34.830 --> 01:07:44.430 William Nicholas: APIs offer you is their flexibility, whether you want to use Python any number of other programming languages or extend them as part of tools you already have.

419 01:07:45.210 --> 01:07:58.440 William Nicholas: You know, regardless of your systems and your processes, you can adapt these to achieve your goals take advantage of the cost savings, the data quality improvements and the overall efficiency of electronic manifesting.

420 01:08:00.000 --> 01:08:10.590 William Nicholas: One note the receiving facility will still need to finalize the manifests at the end to be compliant but the UI link service you saw provides an API to help with them.

421 01:08:11.430 --> 01:08:20.160 William Nicholas: And while the generator signs the hybrid manifest on paper it's the electronic representation of that signature that's uploaded to the system via the API.

422 01:08:21.120 --> 01:08:28.440 William Nicholas: As I note in the video if you've got questions about this from a technical perspective you'd like to dig in and understand how it applies to your own systems.

423 01:08:28.890 --> 01:08:45.780 William Nicholas: You know I encourage you to reach out to us to check out our github to join our developer's listserv and to attend our meetings in the meantime I'm going to hand it over to my colleague tests, who will open it up to Q and A and some discussion points that we'd like to answer, thank you.

424 01:08:47.040 --> 01:08:48.660 Stephen Donnelly: that's real quick William I.

425 01:08:48.750 --> 01:08:58.200 Stephen Donnelly: would like to point out, and he said this, and it gives you bears repeating that you can send a link to someone with.

426 01:08:58.860 --> 01:09:10.080 Stephen Donnelly: hundreds if not thousands of manifests that need to be signed, using the chrome air compliance, it gives you this could go for your final submission to the EPA or, as well as correction so.

427 01:09:10.710 --> 01:09:19.950 Stephen Donnelly: Is that just quick sign, you can use these links, for, if you have somebody in your organization and needs to that you designate assigned to manifest you can create that badge for them and send it right to the music.

428 01:09:23.670 --> 01:09:26.280 Stephen Donnelly: What we live in the future to bass.

429 01:09:27.030 --> 01:09:27.600 Tess Fields: Thanks Steve.

430 01:09:28.770 --> 01:09:39.870 Tess Fields: So now we have some time set aside to discuss some questions that we would like to pose to you and hear your feedback, as well as answer questions that you all have put in the chat.

431 01:09:40.470 --> 01:09:49.530 Tess Fields: But before I read these discussion questions, I see Angel you have had your hand raised for a little while so if you'd like to unmute yourself and.

432 01:09:50.580 --> 01:09:52.260 Tess Fields: chime in please feel free now.

433 01:09:56.250 --> 01:09:56.700 Angel: Can you hear me.

434 01:09:57.270 --> 01:10:02.010 Angel: Yes, okay, so if I'm understanding this correctly.

435 01:10:05.430 --> 01:10:11.070 Angel: Once the transporter leaves the generator site and.

436 01:10:12.390 --> 01:10:13.230 Angel: delivers.

437 01:10:15.090 --> 01:10:17.910 Angel: The shipment to the designated facility.

438 01:10:19.050 --> 01:10:28.260 Angel: I can get an electronic copy of the designated facilities signed copy to download and keep in my files.

439 01:10:34.290 --> 01:10:35.400 Scott Christian: Tess, you want me to answer this one.

440 01:10:35.490 --> 01:10:37.380 Tess Fields: yeah, correct.

441 01:10:38.340 --> 01:10:39.630 Scott Christian: So, you can get the.

442 01:10:40.710 --> 01:10:44.160 Scott Christian: copy so record for each signature.

443 01:10:44.970 --> 01:10:51.990 Angel: Okay, and then for the generator copies still have to, we still have to sign a copy of that the transporter has Is that correct.

444 01:10:52.890 --> 01:11:07.470 Scott Christian: assume that depends on the situation so in the hybrid Yes, they stopped the sign that piece of paper copy but for the fully electronic they're designing it like I like I tried to show electronically.

445 01:11:07.950 --> 01:11:09.570 Angel: uh huh so.

446 01:11:11.190 --> 01:11:13.650 Scott Christian: The record keeping requirement is the system.

447 01:11:15.150 --> 01:11:20.640 Angel: OK, so the transporter will have an electronic system that I can just tune.

448 01:11:21.960 --> 01:11:25.290 Angel: Like you, when you sign your signature on a credit card.

449 01:11:26.340 --> 01:11:27.390 Angel: Debt machine.

450 01:11:31.470 --> 01:11:40.350 Scott Christian: All right, yeah, I think I guess you mean like when you're signing at the at the grocery store on the little pad yes so, it's similar to that.

451 01:11:40.890 --> 01:11:41.220 Angel: Okay.

452 01:11:41.430 --> 01:11:47.910 Scott Christian: good example so be electronic representation that quick sign representation is in the system.

453 01:11:48.990 --> 01:11:51.000 Scott Christian: and not on paper for full electronic.

454 01:11:51.900 --> 01:12:05.520 Angel: Okay, so then well, I still have to wait to get an electronic copy of the generators portion of that manifest or will I, will she be able to print one for me.

455 01:12:07.170 --> 01:12:17.130 Scott Christian: I'm the generator would be so if you're the transporter and you need the copy for the truck anyone with access to them manifest can print out that car.

456 01:12:18.270 --> 01:12:19.560 Angel: Okay, as the generator.

457 01:12:20.760 --> 01:12:24.900 Angel: If it's fully electronic how do I get my copy of the generators.

458 01:12:26.820 --> 01:12:29.490 Angel: Which is the final of the Multi form.

459 01:12:31.260 --> 01:12:35.670 Scott Christian: You login the there's no more mail and with the whole electronic manifest there's no mailing.

460 01:12:38.220 --> 01:12:38.580 Angel: Okay.

461 01:12:38.640 --> 01:12:42.000 Scott Christian: So, you just log in in that the system is the record keeping requirement.

462 01:12:42.840 --> 01:12:47.970 Scott Christian: Okay I'll let test and Bryan on the exact language on that, but the system.

463 01:12:48.030 --> 01:12:59.280 Bryan Groce: Okay, so Scott, this is Bryan so for the hybrid manifest the generator is not registered or is unregistered for manifest access so.

464 01:12:59.700 --> 01:13:17.370 Bryan Groce: Although the manifests originate in the system as electronic manifests that manifest is printed out for the generator by the initial transporter generator signs that manifest the printed copy and keeps that copy, as well as the transporter, generator keeps that copy.

465 01:13:18.390 --> 01:13:19.320 Bryan Groce: For its records.

466 01:13:20.760 --> 01:13:27.990 Bryan Groce: The other workflow the electronic aspect of it, the initial transporter and subsequent transporters and the receiving facilities.

467 01:13:28.440 --> 01:13:43.710 Bryan Groce: Their copy of record will be that final signed copy by the transporter I mean I'm sorry by the receiving facility so which would be in the system so unless a generator has access to the system, they must keep a hard copy of that manifest on record.

468 01:13:45.000 --> 01:13:45.540	 Bryan Groce: on file.

469 01:13:46.620 --> 01:13:48.750 Angel: Okay, and as the electronic.

470 01:13:50.730 --> 01:13:54.810 Angel: system available for the generator to register to use or is.

471 01:13:55.410 --> 01:13:57.750 Angel: It it's available to any.

472 01:13:58.650 --> 01:14:13.680 Bryan Groce: company or site that wants to participate in electronic manifest or perhaps that wants to have access or use the system for its for record purposes if they register they have that opportunity.

473 01:14:14.700 --> 01:14:15.030 Angel: Okay.

474 01:14:16.770 --> 01:14:20.460 Angel: That clears up my questions I like it, I like system.

475 01:14:21.240 --> 01:14:30.120 Stephen Donnelly: And we have a for registration in order to get ahead of ourselves, we have a help desk, and we have a lot of materials on the website I'll throw that into the chat as well, so for people to see.

476 01:14:31.170 --> 01:14:33.840 Angel: Excellent Thank you very much, this is great.

477 01:14:34.020 --> 01:14:34.410 Tess Fields: I love it.

478 01:14:37.860 --> 01:14:53.340 Tess Fields: um so David if you could go to the next slide I will read through these questions and we'll take comments on them or other related topics, so if you'd like to speak, please click the raised hand button and I'll unmute you in the order in which your hands are raised.

479 01:14:55.170 --> 01:15:06.300 Tess Fields: So, the first question is what improved understanding of the existing electronic manifest workflow similar to today's presentation encourage users to adopt electronic manifests.

480 01:15:07.350 --> 01:15:15.090 Tess Fields: And what types of assistance from EPA, for example, would be needed for users to adopt the existing electronic manifest process.

481 01:15:17.130 --> 01:15:22.860 Tess Fields: So, if you have thoughts on either of these questions or.

482 01:15:25.500 --> 01:15:33.660 Tess Fields: The e-manifest system or process in general, please feel free to raise your hand and give us some feedback.

483 01:15:36.360 --> 01:15:37.380 Tess Fields: Yes, Robert.

484 01:15:42.660 --> 01:15:43.290 Robert Fronczak: Can you hear me.

485 01:15:43.650 --> 01:15:51.570 Robert Fronczak: Yes, okay um yeah, I mean what I saw it looks pretty simple. I've talked to my members and.

486 01:15:52.800 --> 01:16:05.340 Robert Fronczak: Which are the railroads and it, you know what they would like is a system that notifies them when a manifest is you know coming to them for signature.

487 01:16:05.880 --> 01:16:19.770 Robert Fronczak: In other words, you know, a shipment is coming to them for pickup it do you have to be in into the email for system to get that notice or can that be sent to an email address.

488 01:16:22.890 --> 01:16:26.400 Tess Fields: Thank you for your question, Steve or Scott, do you want to.

489 01:16:27.600 --> 01:16:27.870 Tess Fields: Address?

490 01:16:31.980 --> 01:16:36.840 Scott Christian: To a user would has to be in the system in order to.

491 01:16:38.910 --> 01:16:41.160 Scott Christian: With the credentials in order to see a manifest.

492 01:16:42.390 --> 01:16:43.170 Scott Christian: So.

493 01:16:46.020 --> 01:16:50.070 Scott Christian: A user would have to have access to been to several sites.

494 01:16:52.440 --> 01:16:53.820 Scott Christian: In order to do that so.

495 01:16:56.340 --> 01:17:00.570 Tess Fields: And I think this question also is about like notification of when you.

496 01:17:01.530 --> 01:17:04.500 Scott Christian: need to sign soon so you're.

497 01:17:04.530 --> 01:17:16.020 Robert Fronczak: not always they don't want to have to go in and check the system to see if they've got a manifest waiting for them, they want some sort of notice from you that there's one they're ready for them right.

498 01:17:16.110 --> 01:17:18.060 Scott Christian: And one thing that.

499 01:17:20.580 --> 01:17:28.770 Scott Christian: I know some of the sites that use the manifest have done is they set up a poll in their system to.

500 01:17:29.880 --> 01:17:40.380 Scott Christian: ask us if so there's that there's a one of the services we did not show is a manifest search service.

501 01:17:41.490 --> 01:17:49.500 Scott Christian: And what those services been used for is to pull email, and the first to see if there's any manifest waiting for them.

502 01:17:51.120 --> 01:17:58.500 Scott Christian: So, they on the hour on the half hour send hey, are there any manifest since the last time I call.

503 01:18:00.030 --> 01:18:07.320 Scott Christian: No, it's also actually our other systems to interact with the manifests as well with.

504 01:18:09.090 --> 01:18:21.750 Robert Fronczak: That and that sounds reasonable, but would it be possible for us to set up a webinar with you guys to go over this so that you know they can see this and get their questions answered.

505 01:18:22.800 --> 01:18:30.840 Scott Christian: Actually, yes, it's kind of funny we're in preparation, we had a hunch that you had your job.

506 01:18:32.580 --> 01:18:33.480 Scott Christian: So, a.

507 01:18:34.470 --> 01:18:39.810 Stephen Donnelly: ar is we've been around that's that type of the history of the manifest you guys have been around for a very long time.

508 01:18:40.140 --> 01:18:41.160 Robert Fronczak: 20 years.

509 01:18:42.390 --> 01:18:43.260 Scott Christian: So.

510 01:18:44.280 --> 01:18:48.240 Scott Christian: It would, it would be good to see and hear and because.

511 01:18:50.250 --> 01:18:51.990 Scott Christian: The json and.

512 01:18:53.100 --> 01:19:01.140 Scott Christian: edi won't talk to each other, but you know, like you know my first job out of college, I had to translate API to.

513 01:19:02.430 --> 01:19:06.540 Scott Christian: Something else to make it so that my database, we talked to it.

514 01:19:08.520 --> 01:19:15.360 Scott Christian: So, we get it, but there, you know that those interfaces kind of happen to happen, and how can that happen.

515 01:19:17.460 --> 01:19:20.580 Scott Christian: So, contact us okay let's do.

516 01:19:21.330 --> 01:19:25.230 Stephen Donnelly: From what I'm hearing, too, is that.

517 01:19:25.260 --> 01:19:27.780 Stephen Donnelly: What specially the second question is.

518 01:19:29.310 --> 01:19:37.290 Stephen Donnelly: Users that we heard this in the first session, where you can now is people would like the manifest system to tell them there there's a manifest themselves.

519 01:19:38.880 --> 01:19:40.470 Stephen Donnelly: They want you know they want.

520 01:19:42.270 --> 01:19:49.140 Stephen Donnelly: They want hey here's your manifest xyz here it is they want the system to copy that, so I've heard that a few times.

521 01:19:57.240 --> 01:20:01.830 Robert Fronczak: So, so should I just talked to you Steven offline to try to set something up okay.

522 01:20:01.890 --> 01:20:15.420 Stephen Donnelly: Well, if you have, if you have any more, if you have any more input or questions, please share that but also, you will have a we have a contact us slide so yeah do not be awake scout saying don't don't hesitate to contact us with many any and all concerns.

523 01:20:15.750 --> 01:20:17.190 Robert Fronczak: No, I'll stay on the line.

524 01:20:20.730 --> 01:20:21.330 Tess Fields: hey Thank you.

525 01:20:28.200 --> 01:20:31.200 Tess Fields: Stacy, please, go ahead and unmute yourself.

526 01:20:33.060 --> 01:20:58.980 Stacy Sinclair: hi Thank you so much for the opportunity um I am working in a hybrid situation and by local area has said that we need, we need to go completely digital I'm trying to figure out how to do this on construction sites where our transporters don't have.

527 01:21:00.090 --> 01:21:12.690 Stacy Sinclair: Access to printers neither do our on-site workers and due to security and safety requirements, they cannot have access to tablets.

528 01:21:14.130 --> 01:21:22.380 Stacy Sinclair: So, we can't go full electronic, and we can't print for hybrid.

529 01:21:31.020 --> 01:21:33.030 Tess Fields: Scott or Bryan?

530 01:21:37.980 --> 01:21:41.340 Scott Christian: To Brian because of the whole timing of a signature.

531 01:21:43.080 --> 01:21:44.040 Scott Christian: There is a.

532 01:21:48.060 --> 01:21:49.800 Scott Christian: yeah, the whole timing of the signature.

533 01:21:50.880 --> 01:21:52.020 Scott Christian: Part of the conversation.

534 01:21:53.250 --> 01:22:06.030 Scott Christian: Because it is also has come up with like national security sites as well, where they get their devices back after a certain point, if they can go in, but they have to hand their devices over.

535 01:22:08.190 --> 01:22:12.930 Scott Christian: And then, then they can go and sign up at that point it's a but.

536 01:22:14.910 --> 01:22:19.140 Scott Christian: I know that, to a quote policy, I can quote the system, but not the policy terms.

537 01:22:20.160 --> 01:22:20.520 Scott Christian: Right.

538 01:22:20.880 --> 01:22:22.950 Bryan Groce: yeah, this is Brian edible.

539 01:22:23.040 --> 01:22:26.550 Bryan Groce: necessarily have answered this time I think one of the things that we are.

540 01:22:28.380 --> 01:22:29.580 Bryan Groce: hope to discuss today.

541 01:22:31.410 --> 01:22:40.470 Bryan Groce: Is in terms of what are legal, legal and valid signatures for electronic manifest purposes, so I just want to hold off and reserve any.

542 01:22:41.610 --> 01:22:47.670 Bryan Groce: questions you might have for that time but, at the very least, if we cannot answer that question today.

543 01:22:48.870 --> 01:22:55.860 Bryan Groce: Please submit your comments his issues comments and questions to the docket and we will address them at a later date.

544 01:22:57.180 --> 01:22:57.540 Thanks.

545 01:23:01.770 --> 01:23:03.540 Tess Fields: Thanks bye Thank you Stacey.

546 01:23:06.060 --> 01:23:07.980 Tess Fields: yeah, that's a good reminder by Brian.

547 01:23:09.180 --> 01:23:14.910 Tess Fields: Please submit your fleshed out comments your written comments into our public docket.

548 01:23:22.650 --> 01:23:32.550 Tess Fields: Many one else who would like to provide some feedback or ask questions and we'll have time at the end of our session today as well to.

549 01:23:33.180 --> 01:23:47.130 Tess Fields: ask questions and comment again so you can even think about it for a little while but uh I'll pass it over to Brian to answer some questions that have been posed in our Q&A box.

550 01:23:50.340 --> 01:23:57.060 Bryan Groce: Thanks to So yes, so we have received a lot of questions from the railroad industry regarding.

551 01:23:58.620 --> 01:24:11.070 Bryan Groce: Some strong desire to have discussions with us EPA regarding sort of the communication between their Idi I believe that's the electronic data interchange.

552 01:24:11.580 --> 01:24:34.860 Bryan Groce: And perhaps json or just our system in general, so I think there was an agreement to have perhaps having a webinar I don't so again, I strongly suggest that you submit your comments and your request to our docket, and we will address those at a later date there's also.

553 01:24:36.000 --> 01:24:40.320 Bryan Groce: Other questions, besides the road wins on.

554 01:24:42.330 --> 01:24:51.540 Bryan Groce: there's a question about is the driver required to register to quick sign are just Trent just transport company so at this time.

555 01:24:52.890 --> 01:25:12.090 Bryan Groce: The driver is required to register for he manifests us and signing up the using the quick sign the process, the registration process is not as rigorous as the registration process for the fully compliant premier signature.

556 01:25:15.120 --> 01:25:19.650 Bryan Groce: I believe in terms of quick sign; you can register as a preparer when you.

557 01:25:20.790 --> 01:25:24.660 Bryan Groce: In your county register as a preparer, you don't necessarily have to.

558 01:25:26.010 --> 01:25:41.430 Bryan Groce: develop the challenge questions and there's no I I believe there's no identification validation component, but I will defer to Steve or Scott on that so to answer your question, yes, you still must register, but the registration process is much simpler.

559 01:25:42.930 --> 01:25:44.250 Scott Christian: Bryan, you nailed it on that.

560 01:25:44.580 --> 01:25:48.030 Stephen Donnelly: One again this is sort of let throw this out there to everybody, one of the.

561 01:25:49.200 --> 01:25:57.870 Stephen Donnelly: One of the sort of ground rules of like federal system management security management is that going to be changing something or accessing a system.

562 01:25:58.290 --> 01:26:10.710 Stephen Donnelly: For the most part, you need to be registered so for all intensive purposes, if yeah someone a driver is going to be signing a manifest, then the system would.

563 01:26:11.190 --> 01:26:18.390 Stephen Donnelly: really like to know who that person signing the manager so like a lot of a lot of anonymous changes or non-registered changes to a system.

564 01:26:19.170 --> 01:26:34.950 Stephen Donnelly: I'm not gonna say impossible, but in terms of like you know Federal Security and system management, the way EPA and federal government likes it is that yeah, you're going to be sunny manifesto change can manifest or doing a to manifest the system wants you to have your own individual.

565 01:26:38.490 --> 01:26:42.690 Bryan Groce: Thanks Steve so yeah So there are a few other questions here.

566 01:26:44.460 --> 01:26:54.900 Bryan Groce: One question will this presentation be available, once this zoom meeting ends and, yes, the answer is yes, in fact, the presentation is already available.

567 01:26:55.710 --> 01:27:09.690 Bryan Groce: In our docket we recently held our first public meeting on October 27 and that presentation, along with the transcript is available, and we will post our.

568 01:27:11.070 --> 01:27:12.330 Bryan Groce: transcript to this meeting.

569 01:27:13.560 --> 01:27:25.800 Bryan Groce: Following the completion of this meeting, so let me correct myself so the presentation itself the slide presentation is available for this meeting and the previous one transcripts, however, will not be available.

570 01:27:27.120 --> 01:27:32.790 Bryan Groce: Until we post them in the system, into the FDMS system.

571 01:27:34.110 --> 01:27:35.730 Bryan Groce: And that will happen, following this meeting.

572 01:27:38.430 --> 01:27:39.750 Bryan Groce: there's another question.

573 01:27:41.820 --> 01:27:44.370 Bryan Groce: generators, the question is, do generators.

574 01:27:45.630 --> 01:27:48.000 Bryan Groce: Each only register in America info.

575 01:27:49.530 --> 01:27:56.070 Bryan Groce: Without the transporter being registered in the system so essentially, I guess this question is.

576 01:27:57.720 --> 01:28:03.990 Bryan Groce: Can the generator participate and use electronic manifest without the transporter participating.

577 01:28:05.940 --> 01:28:07.680 Bryan Groce: So really it.

578 01:28:08.730 --> 01:28:13.650 Bryan Groce: depends for fully electronic, if you want to use a fully electronic workflow.

579 01:28:16.050 --> 01:28:20.460 Bryan Groce: All parties involved on manifests or in the manifest ys.

580 01:28:22.110 --> 01:28:23.670 Bryan Groce: tracking have to be.

581 01:28:25.020 --> 01:28:27.780 Bryan Groce: registered in the system for access.

582 01:28:29.580 --> 01:28:36.450 Bryan Groce: However, in this way, so for the hybrid manifest as we mentioned, as mentioned previously, the generator does not need to be registered.

583 01:28:37.050 --> 01:28:45.420 Bryan Groce: However, the transporter and subsequent transporters, as well as the receiving facility must be registered in the system.

584 01:28:46.350 --> 01:28:52.860 Bryan Groce: So, it really depends on if you're a generator and you want to participate in in a fully electronic workflow.

585 01:28:53.340 --> 01:29:05.610 Bryan Groce: All parties involved with your shipment must be registered in the system for that, and if other parties other than generator want to participate in the electronic tracking workflow.

586 01:29:06.420 --> 01:29:16.290 Bryan Groce: They must be registered generator does not have to be but they have to provide that generated with a hardcopy printed copy of that electronic manifests for their record keeping purposes.

587 01:29:16.920 --> 01:29:24.030 Stephen Donnelly: And so quickly, I know that in the system, but the user interface with you, if you search for a site ID it'll tell you that.

588 01:29:24.510 --> 01:29:29.280 Stephen Donnelly: If that transporter site has a registered user, so you can participate in electronic manifests.

589 01:29:29.670 --> 01:29:41.820 Stephen Donnelly: And also, that same information is available in using services when you do a site search show the system knows that you want to know that hey does this transporter have electronic a person who could do a manifest or not.

590 01:29:49.140 --> 01:29:49.590 Bryan Groce: Thanks, see.

591 01:29:50.970 --> 01:29:53.220 Bryan Groce: It see there are questions here.

592 01:29:57.960 --> 01:30:00.540 Bryan Groce: yeah, I think, for the most part we've answered.

593 01:30:02.100 --> 01:30:06.120 Bryan Groce: The relevant questions again, there are a lot of questions regarding API.

594 01:30:08.280 --> 01:30:20.070 Bryan Groce: By the railroad industry and again if there if your question was not answered our issue was not addressed. Please submit your comments to our docket and we will address them at a later date.

595 01:30:22.620 --> 01:30:23.040 Thanks.

596 01:30:30.510 --> 01:30:30.750 Bryan Groce: So.

597 01:30:31.860 --> 01:30:35.850 Bryan Groce: Dave or Steve out turning over turn it over to you now.

598 01:30:39.180 --> 01:30:41.160 Stephen Donnelly: Is that right now um it's good question.

599 01:30:42.870 --> 01:30:44.550 Stephen Donnelly: So, Q and A we just did that.

600 01:30:53.340 --> 01:30:56.130 David Graham: So, do we have any other additional questions like to answer.

601 01:30:58.740 --> 01:31:00.720 Stephen Donnelly: It is, I didn't see it, we have a question.

602 01:31:02.130 --> 01:31:11.430 Stephen Donnelly: Are there API services to register a quick sign user so each person needs to register their register for their own individual account.

603 01:31:12.120 --> 01:31:25.110 Stephen Donnelly: And to use API services, you need the site manager's permission, and we have all that we have all that spelled out on our website, so we do have user registration information on the website throw it in there.

604 01:31:26.130 --> 01:31:29.010 Stephen Donnelly: about what to do and how to get the access to me.

605 01:31:46.890 --> 01:31:47.220 Great.

606 01:31:49.740 --> 01:31:54.720 Tess Fields: Well, if we don't have any other questions. I believe up next is a 10-minute break.

607 01:31:59.490 --> 01:32:10.320 Tess Fields: So, we will reconvene at 250 please go take the time to stretch your legs and we will reconvene for the policy discussion.

608 01:32:11.490 --> 01:32:15.180 Tess Fields: portion of our webinar so thank you.

609 01:45:20.820 --> 01:45:25.440 Amanda Kohler: Okay welcome back from break everyone, my name is Amanda Kohler.

610 01:45:26.970 --> 01:45:30.240 Amanda Kohler: And we are going to go into the second part of our meeting.

611 01:45:33.210 --> 01:45:43.110 Amanda Kohler: And I have okay sorry just didn't set so the first part of today's discussion focused on the current electronic manifest workflow as it exists.

612 01:45:43.410 --> 01:45:57.930 Amanda Kohler: In our manifest system, this second session we'll talk more about what could be particularly your respect to options that include users uploading electronic signatures to our manifest system so for this section we're going to.

613 01:45:58.710 --> 01:46:02.370 Amanda Kohler: Have a short introduction kind of explain where we are in terms of.

614 01:46:03.300 --> 01:46:11.340 Amanda Kohler: The planning process for these will talk about applicable statutory and regulatory requirements that would apply to any future scenario.

615 01:46:11.970 --> 01:46:18.360 Amanda Kohler: You know, particularly any scenario that we envision will you know must meet the manifest act requirements.

616 01:46:18.720 --> 01:46:25.800 Amanda Kohler: With respect to regulations, we are open to regulatory change where it makes sense, but any scenario that already fits within the existing regs.

617 01:46:26.430 --> 01:46:33.660 Amanda Kohler: Maybe prefer just because rulemaking takes time and so solutions that already fit within the regulations will be faster to implement.

618 01:46:34.440 --> 01:46:52.680 Amanda Kohler: And then, this after we talked about the Statute regs we're gonna go through some electronic manifest workflows so Steve and I will volley back and forth in terms of describing some options and then coming back in applying the statutory and regulatory framework to those options.

619 01:46:53.910 --> 01:47:04.980 Amanda Kohler: And then we'll finish with valid enforceable electronic signatures and that language valid enforceable is important because that's the language that's in our existing manifest regulations for definition electronic signature.

620 01:47:09.120 --> 01:47:18.060 Amanda Kohler: Okay, so setting the stage here our last advisory board meeting focused on program priorities and user fees for FY22/23.

621 01:47:19.380 --> 01:47:24.870 Amanda Kohler: Including our long standing and highest priority goal to increase adoption of electronic manifests so.

622 01:47:25.290 --> 01:47:32.370 Amanda Kohler: With respect to that the Advisory Board recommended to us that we you know we do the following we brought in the concept of a fully electronic manifest.

623 01:47:33.000 --> 01:47:39.900 Amanda Kohler: We continue the pursuit of regulatory change where it makes sense to do so, and we integrate the manifest with the hazardous waste industries.

624 01:47:40.170 --> 01:47:53.100 Amanda Kohler: Private manifesting systems and that's really to capitalize on a lot of the success that we've seen to date with the data plus image uploads where the majority of our manifests are coming in system-to-system connection like Scott mentioned earlier.

625 01:47:55.170 --> 01:47:59.550 Amanda Kohler: So, with that you know we committed to in our response, the Advisory Board to.

626 01:48:01.080 --> 01:48:12.870 Amanda Kohler: Consider, you know potential options for increasing electronic manifest including getting stakeholder input earlier on in our in our process so with that I did want to make sure that we have.

627 01:48:14.160 --> 01:48:19.770 Amanda Kohler: set the stage completely here, so I did want to reiterate, and you know somebody had mentioned this early in her talking points that.

628 01:48:20.760 --> 01:48:29.700 Amanda Kohler: These are early concepts that we're about to discuss, they have not been fully vetted internally in our agency, we are looking forward to getting input early on.

629 01:48:29.970 --> 01:48:40.710 Amanda Kohler: So that that will really help us determine what direction we move in in order to more robustly flush out an option that we would then formally propose to the Advisory Board so.

630 01:48:41.340 --> 01:48:49.260 Amanda Kohler: So, no final decisions, you know these are just early leanings, these are not formal proposals that would then come at a future advisory board meeting.

631 01:48:53.520 --> 01:48:58.350 Amanda Kohler: David okay so let's talk about the statutory regulatory framework there's three components here.

632 01:48:59.070 --> 01:49:12.720 Amanda Kohler: The first component comes from the e-Manifest Act, which requires EPA to establish a hazardous waste electronic manifest system that may be used by any user and then the act goes on to define user and we've included a screenshot of that on the slide.

633 01:49:13.890 --> 01:49:16.860 Amanda Kohler: I wanted to point to Section five B little I.

634 01:49:17.940 --> 01:49:27.150 Amanda Kohler: saw a user as a person that elects to use the system which is the e-manifest system to complete and transmit and electronic manifest format.

635 01:49:32.040 --> 01:49:46.560 Amanda Kohler: Okay second component we're at the manifest regulations to 6224 you see electronic manifest this language is the purpose of this language is to explain the electronic manifest of the legal equivalent to paper manifests.

636 01:49:48.210 --> 01:49:58.050 Amanda Kohler: Section a (2) here, though I wanted to point out any requirement and these regulations to give provide send forward or return to another person, a copy of the manifest is satisfied.

637 01:49:58.530 --> 01:50:06.150 Amanda Kohler: When electronic manifest is transmitted to the other person by submission to the system, the system being the e-Manifest system.

638 01:50:07.020 --> 01:50:14.640 Amanda Kohler: And although to 6224 comes from the generator part of the regulations we do have similar language in the transporter and TSDF part of our regs.

639 01:50:15.180 --> 01:50:24.990 Amanda Kohler: And I will mention an astute listener of our meeting last week did point out that the hybrid manifest is an important exception to this, in that the.

640 01:50:25.740 --> 01:50:36.750 Amanda Kohler: The generator isn't getting the copy from the system actually Bryan touched on this a little bit earlier, but the regulations already have that exception built into the regulatory framework, so.

641 01:50:39.870 --> 01:50:42.000 Amanda Kohler: So, if we were to consult sorry David.

642 01:50:43.260 --> 01:50:48.450 Amanda Kohler: So, if we were to consider other exceptions, you know that that may require regulatory change.

643 01:50:49.770 --> 01:50:57.780 Amanda Kohler: All right, third and final component of the statutory regulatory framework is the definition of electronic manifest signature and 262 25.

644 01:50:58.380 --> 01:51:08.670 Amanda Kohler: And so, our definition is a two-part definition one the electronic signature must be a legally valid enforceable signature under applicable EPA and other federal requirements.

645 01:51:09.630 --> 01:51:17.970 Amanda Kohler: And then into it has to be a method that's designed and implemented and manner that EPA considers to be cost effective and practical as possible for the users.

646 01:51:21.180 --> 01:51:38.310 Amanda Kohler: Alright, so what are our main takeaway so as we see it now going through the Act and the regulations, we see we see three requirements so under the manifest act a user must use the system, i.e., manifest system to complete and transmitted electronic manifest format.

647 01:51:40.140 --> 01:51:49.890 Amanda Kohler: requirements that relations to give provide send for to return to another person to copy manifests are satisfied by submission to the manifests by submission to the system.

648 01:51:50.970 --> 01:52:04.110 Amanda Kohler: And then third electronic signature methods for you manifest must be legally valid enforceable and cost effective and practical and so we're going to come back to these requirements, after each of the scenarios that Steve describes, and I'll turn to Steve.

649 01:52:09.420 --> 01:52:24.300 Stephen Donnelly: Thanks man that would like to reiterate that mean a lot of these slides are really important but as far as like this, or the name of the game, right here for the IT system, the program is the future the present and the future are spelled out.

650 01:52:25.770 --> 01:52:31.080 Stephen Donnelly: In in between, was it 4949 to 51.

651 01:52:32.280 --> 01:52:45.210 Stephen Donnelly: there's a lot of there's a lot of great stuff in there for sort of conceptualizing and you're thinking about electronic signatures that's what you want to do, and if you need more information.

652 01:52:46.110 --> 01:52:53.340 Stephen Donnelly: you're craving I'll see and more or less access your information, the slides do have an appendix.

653 01:52:53.820 --> 01:53:06.120 Stephen Donnelly: There is there's a I believe is like 90 slides or something so there's most of the there's a lot of great information electronic signatures and regulations in the back, so please, please do take a look at those but.

654 01:53:07.320 --> 01:53:08.460 Stephen Donnelly: sort of moving on.

655 01:53:09.510 --> 01:53:14.130 Stephen Donnelly: That there are you know, in light of our advisory boards recommendations.

656 01:53:15.300 --> 01:53:35.790 Stephen Donnelly: to sort of expand the idea and the notion of electronic signature the program we see for theoretical option So these are just for theoretical options, there could be more, but we have for us today, so the four number one would be the existing electronic manifesto, I would say that's.

657 01:53:38.130 --> 01:53:40.860 Stephen Donnelly: or conceptual Susan conceptual theoretical in.

658 01:53:42.510 --> 01:53:47.430 Stephen Donnelly: Any case, so we have the first one, which is more than a concept it's real it's what we're using.

659 01:53:47.970 --> 01:54:03.240 Stephen Donnelly: Okay, that we have the second conceptual workflow which would be a user uploads the signature the all the all the all the generator transporter signatures are stored somewhere else, not in the manifest system and then, when the ship, it is complete.

660 01:54:04.650 --> 01:54:13.470 Stephen Donnelly: The manifest is sent the manifesting all the signatures are sent to us at the end upon conclusion, then the.

661 01:54:14.550 --> 01:54:19.290 Stephen Donnelly: The third the conceptual workflows would be the third-party system upload.

662 01:54:20.340 --> 01:54:26.700 Stephen Donnelly: So, this would be a a an application or program actually my dog likes that.

663 01:54:28.140 --> 01:54:28.620 Thanks Doc.

664 01:54:29.970 --> 01:54:42.660 Stephen Donnelly: The third-party system is the intermediary between the manifest system in industry system that at every point of change transfer signature is added that third party system sends that update to the manifest system.

665 01:54:43.050 --> 01:54:52.050 Stephen Donnelly: And then the fourth conceptual workflow would be a user uploads a signature throughout the throughout the system.

666 01:54:52.620 --> 01:55:12.840 Stephen Donnelly: And that would advance math so that would be essentially Amanda would be working at a generator site on the loading dock and test would be the person at the office and but upon notification that Amanda has signed the lecture Amanda has done the electronic manifest.

667 01:55:14.130 --> 01:55:27.420 Stephen Donnelly: things she would notify her, she did my tests and tests would update the system in the manifest would move throughout so basically a system to update our system run by industry systems, but we'll get into more detail.

668 01:55:30.600 --> 01:55:49.890 Stephen Donnelly: Alright, so let's go to the next slide So these are these are something to pay attention to and somebody considered though so so, the blue is a transfer of manifest data or changing says, then the red is the signer updated manifesting that little pin right there.

669 01:55:53.640 --> 01:55:55.290 Stephen Donnelly: I do this, you see a mouse.

670 01:55:56.910 --> 01:55:57.600 Amanda Kohler: I cannot.

671 01:55:59.160 --> 01:56:00.540 Amanda Kohler: keep moving Oh, I see it.

672 01:56:00.570 --> 01:56:11.010 Stephen Donnelly: I see it, okay cool, then the red is the signer updated manifest data, this is a pen fountain Pen, and this is what user interface.

673 01:56:11.430 --> 01:56:26.850 Stephen Donnelly: The user actually sees in this right here, we have our factory or generator factory with the smokestacks that we have our transporter in a box truck and then we have our treatment story and disposal facility, represented by the.

674 01:56:27.870 --> 01:56:33.360 Amanda Kohler: it's like some sort of recycling all right I'll correct the record, if you were trying to point with your cursor. I'm not seeing it.

675 01:56:33.510 --> 01:56:37.080 Stephen Donnelly: Now okay great hi this is, I can control David thanks.

676 01:56:38.280 --> 01:56:42.660 Stephen Donnelly: OK so anyway moving boldly ahead.

677 01:56:44.220 --> 01:56:58.950 Stephen Donnelly: So, let's go to the existing attract manifest workflow I hope you all were paying attention in the first part of the presentation, but essentially this is how it goes the manifest is created in the industry system.

678 01:57:00.600 --> 01:57:11.790 Stephen Donnelly: And in each step along the way the generator or transport and generator transporters receiving facility go into the system to sign the manifest.

679 01:57:14.430 --> 01:57:17.250 Stephen Donnelly: I think we're all aware that oh, thank you very oh that's Oh yes, right Thank you.

680 01:57:18.630 --> 01:57:20.970 Stephen Donnelly: cool so they're in the system to sign the benefits.

681 01:57:22.500 --> 01:57:27.150 Stephen Donnelly: And then, this next slide will ask and answer some important questions.

682 01:57:28.170 --> 01:57:28.950 Stephen Donnelly: So, number one.

683 01:57:30.330 --> 01:57:39.300 Stephen Donnelly: Who needs to be registered everybody needs to be registered to sign so everybody needs to if you want to see the manifest you need to be registered.

684 01:57:39.750 --> 01:57:45.180 Stephen Donnelly: And you need to have site access to these sites named to a site name of the manifest sign it if you were a generator.

685 01:57:45.510 --> 01:57:56.490 Stephen Donnelly: You do have approved site access to the generator site name, but the manifest say, for the transporters same for the received so you need to be registered user, you need to have access to the sites named on the manifest.

686 01:57:57.930 --> 01:58:04.920 Stephen Donnelly: And then to sign the user with login to recruit info navigate to that the manifest.

687 01:58:05.940 --> 01:58:20.430 Stephen Donnelly: And, or if they have a friend who has site manager access, they could use the UI link service to send them a link directly to that manifest and they would click quick setup, so this is where the generating the transporter initial seed.

688 01:58:20.880 --> 01:58:28.440 Stephen Donnelly: So, they need to go in find a manifest and click sign or they can take the shortcut of the UI link click on that and then click side.

689 01:58:32.130 --> 01:58:39.030 Amanda Kohler: So, applying the statutory, regulatory framework to our current electronic manifest workflow you would expect to see a lot of check marks here.

690 01:58:39.750 --> 01:58:50.640 Amanda Kohler: We are using the system to complete and transmit electronic manifests we are transmitting to the other person by submission to the system and our electronic signatures are valid and enforceable.

691 01:58:51.180 --> 01:59:05.730 Amanda Kohler: However, since only a half percent of our total manifest volume or present electronic manifest it's reasonable to conclude that there are questions for whether our electronic signature method is cost effective and practical and so you see us acknowledge that here with a question mark.

692 01:59:10.740 --> 01:59:14.130 Stephen Donnelly: All right, fantastic Okay, we are at a conceptual.

693 01:59:15.300 --> 01:59:21.750 Stephen Donnelly: conceptual framework number two, this is the user uploads signature at the end.

694 01:59:23.370 --> 01:59:31.890 Stephen Donnelly: Okay, so we have here on the left Okay, so the manifest is creating the manifest is created in the manifest system.

695 01:59:32.430 --> 01:59:36.810 Stephen Donnelly: So, this is by the generator transporter or they're seeing the facility.

696 01:59:37.560 --> 01:59:49.620 Stephen Donnelly: And all the handlers are named on the manifest and there is a manifest tracking number, and this gets down so basically this manifest all the all the basic information.

697 01:59:50.610 --> 02:00:00.510 Stephen Donnelly: But then it gets taken out of the manifest system, and it goes into an industry system and there and that industry system, it goes the generator side.

698 02:00:01.290 --> 02:00:12.180 Stephen Donnelly: So, it's not a tablet of some kind of offline it's that made that no one's EMF essence was an old school, so it goes from the transporter because the generator to the transporter.

699 02:00:13.170 --> 02:00:23.460 Stephen Donnelly: To the to the designated facility and all that  electronics in our electronic signature information is captured outside the system and then.

700 02:00:24.810 --> 02:00:34.170 Stephen Donnelly: It is uploaded to the manifest system; I believe 30 days post receipts say so we'll get that information at some points about the electronic signature information.

701 02:00:37.110 --> 02:00:51.690 Stephen Donnelly: Alright, the next slide so who needs to be registered, only one person needs to be registered, this would be the receiving facility so they can use the chrome error compliance signature to submit that final completed manifest.

702 02:00:53.130 --> 02:00:57.690 Stephen Donnelly: and design, as we saw all the users allow that workflow.

703 02:00:58.110 --> 02:01:03.660 Stephen Donnelly: Or would be signing in some sort of industry system, so we don't know what it would look like we don't know what sort of things you may be leaving.

704 02:01:03.960 --> 02:01:15.360 Stephen Donnelly: But we would have no data will be transferred to the EPA manifest until that person at the receiving facility uploads that data and submits that madness.

705 02:01:18.990 --> 02:01:22.770 Amanda Kohler: Okay, so scenario two considers.

706 02:01:23.910 --> 02:01:31.470 Amanda Kohler: an option, where the receiving facility uploads the manifest data and all the electronic signatures, at the end of the process.

707 02:01:32.010 --> 02:01:39.570 Amanda Kohler: So, applying the statutory, regulatory requirements for right now we find it challenging to see how.

708 02:01:40.110 --> 02:01:53.610 Amanda Kohler: we're using the system you manifest to complete and transmit electronic manifest when it's coming all the way at the end, and on the regulatory side again find it challenging for how we're using the system to transmit the manifest copy to another person.

709 02:01:54.780 --> 02:02:02.820 Amanda Kohler: for electronic signatures question marks here and that's because we're considering electronic signatures captured outside of the EPA manifest system and so.

710 02:02:03.900 --> 02:02:10.860 Amanda Kohler: whether and how EPA will determine whether electronic signatures are valid enforceable are cost effective and practical and open question.

711 02:02:12.120 --> 02:02:14.400 Stephen Donnelly: If we just go back to the previous slide really quick.

712 02:02:16.020 --> 02:02:16.500 Stephen Donnelly: I know.

713 02:02:18.000 --> 02:02:29.730 Stephen Donnelly: Yes, what to point out so yeah at every at every step along the way, and this method, so the manifest information is sort of the workflow is being transmitted outside of the industry system outside of the manifest system so.

714 02:02:30.300 --> 02:02:39.750 Stephen Donnelly: The transporter can sign in the industry system, once the generator science, but it's a big question mark here what's going.

715 02:02:42.570 --> 02:02:46.080 Stephen Donnelly: Clear my drawings right, we can move on ahead.

716 02:02:50.700 --> 02:02:57.570 Stephen Donnelly: Okay, so third-party system upload signatures throughout the third-party advances manifest and.

717 02:02:58.770 --> 02:03:13.260 Stephen Donnelly: Not very doesn't really roll off the Tongue this method, however, it is something to consider that so someone will sit be he manifests is created in the EPA says.

718 02:03:14.310 --> 02:03:21.210 Stephen Donnelly: And what would happen here, and this is all this is all conceptual we're not conceptual models, right here is this manifest right here.

719 02:03:22.050 --> 02:03:33.000 Stephen Donnelly: gets put into a third-party system so it's a third-party device cloud applications something like that to go to be to get signatures so.

720 02:03:33.960 --> 02:03:43.500 Stephen Donnelly: The manifest created all the hammers run it all good to go it's at the loading dock and I'm on the loading dock and I just need to see whatever is on.

721 02:03:43.920 --> 02:03:52.170 Stephen Donnelly: Whatever is on my iPhone and on the generator and I write my name, or I check a box, or I signed something with my signature information.

722 02:03:52.530 --> 02:04:03.630 Stephen Donnelly: And I'm not saying I'm not logged into the manifest system, however I'm in this third-party system and once I sign this third-party system sends that info back up.

723 02:04:04.530 --> 02:04:18.030 Stephen Donnelly: To the manifest system, so now parties on the manifest or state regulators EPA regulators to see that okay this manifest was signed by the generator at this point, time and there's a shipment.

724 02:04:19.230 --> 02:04:37.950 Stephen Donnelly: The shipment has transpired, and then, once that signed from once the generator side the transport will sign that information will go back up and then it'll go through the workflow such that, so no one's signing into the manifest, but a third party is telling you manifest hey.

725 02:04:39.780 --> 02:04:45.000 Stephen Donnelly: Steve sided Amanda sided test cited and that's how the workflow goes until the end.

726 02:04:50.310 --> 02:05:00.120 Stephen Donnelly: Okay, so who needs to be registered, similar to the last conceptual model, the receiving facility so they can use that chrome error compliance into to submit the final completed manifest.

727 02:05:01.950 --> 02:05:14.250 Stephen Donnelly: And then to sign the users must be able to access that a third-party system by a verified communication email phone user account and.

728 02:05:15.240 --> 02:05:31.770 Stephen Donnelly: Just sort of spell this out plenty as possible this verification means they can access that account and that third party system to sign this is not a verification of an individual individuals ID like the electronic signature agreement we have in recruiting.

729 02:05:36.300 --> 02:05:38.970 Amanda Kohler: Okay, so you know, the biggest difference.

730 02:05:39.690 --> 02:05:50.550 Amanda Kohler: scenario three compared to scenario two is that scenario two envisions all the manifest data and electronic signatures coming in at the end and as Steve just described scenario three has that manifest data.

731 02:05:51.090 --> 02:06:01.530 Amanda Kohler: uploading to our system throughout the process, so scenario three is a bit better of a fit here as, according to the e-Manifest Act, the system is being used to complete.

732 02:06:02.190 --> 02:06:11.550 Amanda Kohler: and transmit electronic manifest we do have a question mark here just on whether we whether where we land on what transmit means and so.

733 02:06:12.510 --> 02:06:15.600 Amanda Kohler: So that is an open question as far as the regulatory requirements.

734 02:06:16.170 --> 02:06:20.490 Amanda Kohler: Are we transmitting to the person by submissions in the system, right now, are leaning is.

735 02:06:20.790 --> 02:06:29.760 Amanda Kohler: This criteria would not be met, just because the manifest is advancing outside of the system and so we're not transmitting to another person using the system.

736 02:06:30.390 --> 02:06:41.730 Amanda Kohler: And then question marks for electronic signatures for the same reason as we described in scenario to these are electronic signatures happening outside of e-Manifest and so whether and how EPA would ensure that.

737 02:06:42.330 --> 02:06:48.600 Amanda Kohler: That industry system electronic signatures would be valid enforceable and cost effective and practical isn't an open question.

738 02:06:52.650 --> 02:07:05.190 Stephen Donnelly: All right now here we go this is for user uploads signatures real out in the manifest system advances manifest so for those of you who remember.

739 02:07:05.880 --> 02:07:11.340 Stephen Donnelly: One of our advisory board meetings I can't remember which one we sort of talked about if this was um.

740 02:07:11.910 --> 02:07:20.190 Stephen Donnelly: This is April 2020 we talked about this is a this was also known as the one-person registered solution that David Graham expand upon.

741 02:07:21.060 --> 02:07:42.090 Stephen Donnelly: When it comes to capturing electronic signatures, so this is the signature is uploaded throughout the shipment by the industry system in the industries in the manifest this will be dances that so forth, it so that so our manifest is created, all the handles are on it.

742 02:07:43.110 --> 02:07:51.780 Stephen Donnelly: All that all that fun stuff everything you need to everything you possibly want on your manifest is on your manifest and the shipment can begin.

743 02:07:53.310 --> 02:08:08.940 Stephen Donnelly: Okay, however, one of the interesting things here is that I'm going to sort of spoil thing around this, but so each site along the shift that needs a site manager someone with an API DMK like managers like manager.

744 02:08:10.290 --> 02:08:22.350 Stephen Donnelly: And of course, I matter here is an API ID and key to pass a signature information back so for the purposes of this demonstration right here.

745 02:08:23.460 --> 02:08:39.570 Stephen Donnelly: hi the generator sites and I am the site manager and Scott is the person on the loading dock so that that I know Scott has notified me that the manifest shipment it has gone he has.

746 02:08:41.190 --> 02:08:53.010 Stephen Donnelly: he's accessed whatever industry system we have at our at our generator side and basically let's that industry system know that hey I signed that manifest.

747 02:08:54.150 --> 02:09:06.270 Stephen Donnelly: me being the same manager, I see that Scott has signed that manifest and what I do, since I am the site manager here is I send back that information to the manifest system saying.

748 02:09:06.960 --> 02:09:26.310 Stephen Donnelly: I inbox 15 Scott Christian has signed at on 11 3025 you know I send back that information, so it goes back here I send that information so then that goes to the transporter it goes down the transporter and that transporter lets their site manager.

749 02:09:27.600 --> 02:09:34.140 Stephen Donnelly: let you know influence our site manager through an electronic system of some kind, that they've signed the manifest in that information goes back up.

750 02:09:34.530 --> 02:09:48.330 Stephen Donnelly: And threw in through the workflow process, so the site manager is updating the manifest with the signature information from their onset person.

751 02:09:51.330 --> 02:10:01.860 Stephen Donnelly: When you go to the next slide Okay, who needs to be registered so sort of spoiled it, but each party on the manifest needs to have a site manager, with an API key.

752 02:10:03.600 --> 02:10:05.310 Stephen Donnelly: As well as.

753 02:10:07.320 --> 02:10:18.660 Stephen Donnelly: And so, to sign the users will click sign in the industry system which updates the manifest system for the API and also sort of point out here, we talked about site managers.

754 02:10:19.470 --> 02:10:26.430 Stephen Donnelly: there's each site can have we actually recommend having multiple site managers per se at least two just for redundancy.

755 02:10:26.790 --> 02:10:40.590 Stephen Donnelly: So, this could be managing uploaded this information that Scott sign manifest could be uploaded by any number of site managers associated with that with that specific sites over met Amanda was as a manager if Graham tasks.

756 02:10:41.100 --> 02:10:45.510 Stephen Donnelly: Anybody at their site my hair pro site manager that's like they could send back that information.

757 02:10:47.340 --> 02:10:59.190 Stephen Donnelly: and also, the users can use a quick side button in the manifest interface, like the current workbook so like this could be mixed and matched with our current system, so, for example.

758 02:11:00.540 --> 02:11:17.310 Stephen Donnelly: I am I, the generator side, we have a system that could potentially work with this, I let it know that's got a side, however Amanda as a transporter they don't have an industry system, she does logs into the manifest APP and.

759 02:11:18.390 --> 02:11:35.160 Stephen Donnelly: clicks click sign and David Grann his transporter company, they have a system, so he goes into their system, and they update that information, so it can be used to mix and match, and then, as always, the conclusion the manifest assigned a clear compliant signature.

760 02:11:39.030 --> 02:11:49.920 Amanda Kohler: So. scenario four is similar to scenario three except the manifests advances in the manifest in scenario four, and so this is, you know the scenarios.

761 02:11:50.400 --> 02:12:04.320 Amanda Kohler: Two through four, and this is probably the best fit for existing statute and regulatory requirements, because the manifest is advancing our system, we are using the system to complete and transmit electronic manifest we're transmitting to the other person by using the system.

762 02:12:05.940 --> 02:12:13.560 Amanda Kohler: Again, electronic signatures are question marks here just because a scenario for does involve electronic signatures captured outside of e-Manifest and so.

763 02:12:13.770 --> 02:12:28.920 Amanda Kohler: whether and how we would determine valid enforceable and cost effective and practical are open questions, and with that we've talked a lot about valid enforceable, so I let's unpack that here so I'm gonna turn it over to Tess to talk about some hallmarks of that term of art.