Energy Facility Contractors Group Podcast
Maximizing DOE and NNSA mission success by sharing best practices and information to support management and operational excellence.
Tune in to hear from Contractor and Federal leaders as they discuss EFCOG’s efforts to enhance mission performance and completion across the complex. The EFCOG Exchange Podcast also features special topic episodes, highlighting digital transformation, lifecycle infrastructure management, safe and secure operations as well as other topics related to DOE’s critical missions.
Energy Facility Contractors Group Podcast
#1 EFCOG Webinar on Modernizing Operations (9/2/26)
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
NOTE: The video and audio recording of this webinar can be found here: Strategic Priorities Webinars | EFCOG.org
EFCOG hosted webinars designed to support collaboration, knowledge sharing and consistency across the DOE enterprise as the sites begin developing their implementation plans for the newly revised DOE Orders.
Guest speakers:
BJ Quigley - NNSA
Tim Bolen - Savannah River
Rich Zaharek - Savannah River
Jay Rhoderick - EFCOG Working Group Coordinator
Reach out to staff@efcog.org to be added to the webinar mailing list.
Okay, well, good afternoon, everyone. Again, thank you for joining us today. Today marks the first in a series of FCOG-hosted webinars designed to support collaboration, knowledge sharing, and consistency across the Department of Energy Enterprise as the sites begin developing their implementation plans for the newly revised DOE orders. This session, as I mentioned, is being recorded so that we can share this with others who have not had the opportunity to join us for the live discussion. As you know, we're just a little over two weeks past the department's official release of these updated orders. The immediate priority for each of the sites has been to develop an implementation plan that outlines how your local processes will incorporate and comply with the new requirements. These plans are foundational, and we hope that today's discussion and the series that will follow gives you a valuable opportunity to hear directly from your counterparts across the complex on their progress, challenges, and insights. Our goal is simple, and this is always the F. Cog's goal, to help you accelerate your own efforts by learning from others. And expect today's discussion to just surface lessons learned, highlight any potential process roadmaps or showstoppers, and offer examples of approaches that might be useful to you and your teams as you can continue to develop your deliverables. We're fortunate to have several contributors with us today. We'll begin with some opening comments from BJ Quigley from NAPAS, who'll share some expectations and some perspectives as you prepare and submit your implementation plans. After that, we'll hear from Tim Bolin and the Savannah River team, who have volunteered to walk us through some of the lessons they've learned already. And hopefully that will engage you in some dialogue and conversations of things that you have learned so far or questions that you might have. And then we'll follow that with Jay Roderick, who will highlight some of the opportunities within the FCOG working groups that can further support your planning and execution. Above all, we want this to be a discussion. Please make use of the chat and the hand raising functions. We'll be monitoring that throughout the session because we welcome your questions, your insights, and your experiences. What we understand is that the more we share, the stronger and more aligned is a complex we will be moving forward. And so again, I want to thank you for being here. And with that, I'd like for us to go ahead and get started. And so uh BJ, if you're on and available, we'd like to give you the floor for any opening comments uh that you'd like to share with uh the webinar.
SPEAKER_04Yes, uh thanks, DJ. Appreciate the opportunity to uh to talk with the uh the audience here. I think obviously this is a huge effort for us. Um you know, one of the biggest things uh that has been acknowledged throughout this process, and I think you know Jim McConnell said it um at the opening uh kickoff meeting uh earlier this week, is is that we know that everything is not perfect. Uh we know that there's gonna be some hiccups along the way. Uh, one of the things that we want to encourage everybody is as you're going through and reviewing operations, as you're working through each of the individual site alignment plans, calling out some of those conflicts, right? If you see something that doesn't work, um, you know, share it, share it with your your contracting officer, share it with your field office. Um we want to highlight those things as early as possible so that we can get folks clear answers and clear guidance. Uh if there's any ambiguity, we want to make sure we address it proactively. Um, you know, we want to move fast and we want to make sure we give folks the additional efficiency that's there, but we want to make sure we get it right. So, you know, there's opportunities outside of the official process and then obviously included in your alignment plan as well. Um we're very excited uh about uh obviously the opportunity to streamline. I think one of the things we're interested in is obviously this is setting the tone for other options that may be out there as well. So as you're reviewing these these orders and as you're looking at at your day-to-day process, if there's anything else that's out there that offers an opportunity to streamline, um, we don't want this to be sort of the end of the uh the work uh in this space in order to again operationalize some of the efficiencies that are out there. Um, you know, in terms of the next uh few uh days and weeks, um obviously the alignment plans are are gonna come due here in the next couple of weeks. Uh we're excited to look through those and then I think collaboratively work with each of you guys to figure out um which orders are already being met by the things that you're doing today, um, you know, which of the orders may take a short time period and and which orders are are gonna be deferred just because either they don't make sense or uh they require a significant amount of work, and and all of those will be done hopefully in collaboration with the field offices so that everybody would be on the same page. We can make sure that it's captured in the contractual documents and all those kinds of things. But I think the big takeaway here is uh you know, we wanted to set on the f on the federal side um set the standard and uh you know for an opportunity for us to again take advantage of some of the flexibilities that are here that are um really hopefully allowing us to move faster as an enterprise, to gain more efficiency, to achieve more mission, because as you guys know, uh we're being asked to do more today than we ever have. And so any flexibilities that we can afford, we wanted to make sure we were doing that. So again, uh if there's anything that comes up, as I said at the beginning, any conflicts that you see with your contracts, any issues that are coming up in terms of guidance that you you can that you need to give your teams uh to accomplish their day-to-day tasks, please highlight those as soon as you see them. Work with your field office, work with your contracting officer. We want to make sure that the folks that are on the operational side have clarity in terms of what they're executing, executing to and what the standards are, uh just to again to make sure that everything is taken care of there. Um certainly I'll I'll be on the line if there are any questions. Happy to respond to any of that stuff. Uh, but DJ, I'll turn the microphone back over to you.
SPEAKER_07Okay, great. Thank you so much, BJ. And and and before I turn it over to Tim, I want to first of all acknowledge all the different federal uh counterparts who are on the call today. And the reason why I want to emphasize that is this is truly a team effort. And just their mere presence demonstrates that we are we are not just throwing this over the fence to the contractors to go figure out how to do this. This is truly a collaborative effort. And as BJ mentioned, there's a great willingness to deal with any challenges, issues, questions that you have, because we all want to be part of the solution and get to the outcomes that we're trying to drive. And then the second part that I also want to mention before I turn it over to Tim is as you're thinking about your alignment and implementation plans, there is a critical need to think about the outcomes and how you want to measure those. So we can demonstrate the true measure of the outcomes related to the relaxing or changing and revising of these orders. Even from how you do your implementation alignment plans, you know, how many, how many of the orders can you actually implement is a measure. You know, how many other revisions might be necessary is a measure. And then think about the the different orders themselves and your normal processes. How many subprocesses are you going to be able to remove? Maybe that's something you want to track. But but think about these measurements that you're going to need to demonstrate the effectiveness of the revisions of these orders so that we can demonstrate that we were able to accelerate mission, improve milestones, build margin and schedule, save cost, plow that back into other mission activities. It's going to be really important as part of this implementation. So, with that, thank you again, BJ, for your opening comments. And now I'm going to turn it over to Tim, uh, who's going to walk us through from a Savannah River perspective. Tim, over to you.
SPEAKER_08All right, thank you, DJ. Yeah, yeah, I do see um Amberzone. I didn't know if there's any other federal counterparts who'd like to just chime in now or say anything in leading remarks. Um, you can either hold that or but if you're if you want to, now's the time to do that, just raise your hand or or jump in before I kind of lead through some of the um logistics on what we're trying to propose here.
SPEAKER_09Um hey, this this is Greg Soss, and I appreciate the opportunity. I was uh I had a schedule conflict scheduled, but that cleared up. So I just I was able to join. So I I missed the I missed uh most of the preamble, but uh I from what I heard from uh DJ, I a hundred percent agree with what he said. And uh um I actually today just issued some guidance to the field managers uh with a lot of similar type perspectives. So I I think we're pretty well aligned. So uh hopefully I'll uh be able to add some value. All right. Thank you, Greg.
SPEAKER_08Um anyone else? Thank you, thank you, thank you, Jay. So um what I've got won't take long. So Christine, if you don't mind, could you share the I've got just a couple of slides and and I'm I'm re uh reusing slides that I use for the the NSA production uh acceleration workshop a couple of um a few weeks ago up in DC. And and from the FCOG perspective, essentially we were preparing then to and we were making the pitch from FCOG. What better of an organization to help do what DJ has lined up? So um from an FCOG board member, I'm I'm gonna take the lead to help align and to do what the community needs to line up uh these these sessions, these webinars, whatever we need to go help make sure that we can work it from uh DOE NNSA and help share that. But uh the bottom line is um FCOG is committed, as DJ said, assisting the overall effort. We're we're ready, we're poised. Um what a better organ, what there's not a better organization than to help pull this together and keep the glue together to learn the lessons across each organization. Uh we're we're ready, we're standing by. Now that the uh the orders have been issued and the uh alignment plans in place, we're actually engaged and we're working to do that. And we can leverage our our established communications way to do that. So we we already have those pathways, so we're gonna do that and we're gonna help get those measurable outcomes to get the missions need. Um simply our goal is to do rapid sharing of information to help get these um these uh non-value added uh uh requirements that are that are in our way to help execute our mission across the enterprise and get those and tailor them to the mission needs at each site, which we understand one size doesn't fit all, and from an FCOP perspective, um that's why the lessons across each site would be very valuable. So it's one what may work at one site won't work at another. But uh our our goal is to help faster miss mission execution and to essentially go um drive schedule uh to the left and help reduce costs. Um next slide. And simply our our objective is to accelerate uh this best practices to help our best to put this on an accelerated uh pathway to get it into the system and use our existing framework uh to help do that. And so we're already engaged with workshops and webinars. We're on one today. Um we'll talk about that. We've got some tools that we're gonna learn that we can use. We'll get one example from Savannah River, but I know all of the other sites are out doing their thing now using artificial intelligence. We need to share those lessons and then to help align our implementation. And again, it's the same thing, it's faster adoption of the of the regulations to get there. So that's the pitch we did a few weeks ago up in headquarters, awaiting the guidance. Now the guidance is there from um from our our our leadership, so we're off doing that. And so, what what I also want to mention, we've invited a lot of the working group leads, they're on here. Um, the working group leads which are established already in the FCOG organization, are have a framework to where they can hone in and actually use the details and their knowledge and subject matter expertise in the areas in which the refined uh orders and directives are targeted. So we're gonna ask the working leads to be highly engaged and to um to talk about ways to go either do special meetings, targeted meetings to say where does this alignment work and we can use those working groups to help foster that information. And then also out, you know, metrics. So one of the things that we really need to talk about, and from our our standpoint is we need to measure the effectiveness of what we're doing. This isn't just an exercise, we understand that, and it's it's to help the mission forward. So, what are those mission metrics that can or those metrics that help the mission to be uh recognized as being moved forward in a fashion that we want to do that? So as as we learn those things, there may be maybe different ways to measure, uh, but we all have the same uh goal in mind is to get to get the the the best execution out of the dollars we have. Um so we're all off doing alignment plans as um as we just heard. We have till essentially the end of the month, most of us have to do that at the sites. Um we've asked uh Rich Zaharic, who's online, if you're there, Rich, to bring just an alignment plan execution process that we're doing at Savannah River. It is a complicated site based on just that it's an NNSA site with landlord and some EM interaction heavily in the in the execution of the contracts and also with partnering contracts at the site. So from that standpoint, um it is a complicated process and we're working across those um those areas. But Rich Saharic is leading that at uh Savannah River. And if Rich, if you can spend a few minutes to talk just high-level through the process, um that might spur some questions, or we can get those later, but just to kind of highlight and walk through how it's working here at Savannah River.
SPEAKER_02Certainly, thank you, Tim. Um it's a pleasure to be here. Appreciate the opportunity to present. Um so I do have a couple slides that I put together. If you can go to the next slide, please, um, which is where we are today, the bottom line up front. So some actions we've completed already. We established what AI helped me create was the impact, which is the implementation and modernization of policy acceleration change team. Um so you you talk about using AI tools that helped me in that one. Uh we've generated an AI application that's been put into production use to really perform a gap analysis and identify proposed changes. What we were able to do is put the previous Rev, the current Rev, and take our S-rids line by line and see which S-rids were affected by those changes. We went a step further where we asked the AI tool, hey, to change that step in there to meet the new requirements, propose us a change in wording. We have that done. We're sharing that with the SMEs and procedure owners. And what we're also allowing to do is we're putting the human element back into it after the AI application has provided the changes, and they have to either accept the change as written, modify it, or reject it. Um from there, that's how the process is going to work. From an SRNS perspective, we evaluated all our affected documents, and looking at it, we're over 700 site-level documents that are affected by these changes, and over 27,000 facility-level, lower level potentially uh change documents that we have to scrub. And we're over 100 and probably 8,000 S-RID sort of line items that we we need to uh tackle as well. What we did, the biggest thing besides the AI application is we created a procedure change process and we called it the MIU modification for immediate use. Um I'll go through some uh details on that in the next slide, but our next steps are really to conduct high-level impact reviews for the orders, and that's going to take place next week. We've asked all the facility area managers and the SMEs and procedure owners to come brief the impact team and tell us what changes were made, what was not provided in the DOE order, changes that we thought we might see or we would want to see, and also any contradictions in the orders to our current contract or procedures. So those are gonna take place next week. We have an executive-level team. Uh Tim is included there, Lee Schiffer and others that are gonna sit in on those meetings, and we're gonna literally challenge the teams. Did you go far enough? Um, tell us what your reasoning was for not accepting that change, justify that to us. So we're gonna get a good sense by the end of next week into the following week on uh what the impacts are to us. We've also asked them to very high level provide any um lessons learned type approach and potential cost savings at a high level. Um we're gonna implement our first group of MIUs. These are gonna be sort of a blue-line document, red line document type of thing that's gonna be added to the front of each of our DOE orders and then eventually down to our site level procedures as well. And it'll dictate what the change was and what the implementations are without having to do a full revision on that document. Um we're gonna complete the implementation of our site-wide documents by December 17th of this year, and then moving into the first half of next calendar year and complete our lower level procedures. We are looking with our tools and how things go, moving both of these dates to the left. We have a 1217 date for the site level documents, but I'll tell you the executive leadership team and myself has challenged the team to do it by the end of October. So we're calling it a Halloween gift. Um lastly, we're gonna track cost savings and share lessons learned across the complex. This is where we want to potentially start some working level meetings with our program managers and project managers and some subject matter experts. And just make sure we're headed down the same path where we're running into issues and barriers. We want to make sure that you're understanding those and see how we can leverage approval processes and AI tools to make this whole process even streamline it even further going forward. Um the next slide, please. Just to talk a little bit about the MIU process. Um it's meant to streamline and implement changes quickly, and we know in the nuclear world we take months and months, even years sometimes to implement change. It's going to add agility to the procedure owners as the more people you get involved in review processes, everyone has an opinion. So we want to minimize that number of opinions, but we want to streamline it more towards time, and the procedure owners can invite whoever they feel necessarily to provide comments. But we're going to put a deadline on when these changes need to be made. Um it's also going to allow uh the review process to work in parallel, which a lot of times we do it in series, so that that'll take um put a burden on the impact team and the procedure owners, but we think it's gonna be very value-added. And the operating managers uh for the plants, they may be overwhelmed, but with these reductions and cost savings, we're gonna repurpose subject matter experts over to help influence and drive these changes over the next six to nine months. There will be only one MIU per procedure, and then it also is gonna standardize the process to implement the other supporting documents, such as you see in the table below, training materials, desktop instructions, um, our plans, etc. And last slide. So this is just a synopsis uh schedule of what I just presented. It's a little more detailed, but um I just wanted to share that with you here. Um with that, I am that concludes my presentation, and Tim and I are open to questions.
SPEAKER_08Any questions from anyone or commentary if if that's something in terms of you're doing or seeing?
SPEAKER_07Yeah, so I I I I'd love to start with the first question and then hope we can get some others who may have questions or either comments. But uh Richard, as you guys are been working towards your alignment plans, and and right now we're about halfway through the timeline before you have to submit them. Do you feel like you're on schedule as it relates to the numbers of the plans that the orders that you have? After review, or do you feel like you're a little bit behind? How have the AI tools been of a help to you? Just trying to get a sense of where you are in the timeline.
SPEAKER_02Absolutely great questions. We, from a time perspective, we are on track. Next week is going to be our big um test of where we truly are when we have those individual briefings with the 57-ish procedure owners for the DOE order changes. So as far as AI tool, we could we would not be here where we are today without the AI tool. It has taken what I consider weeks to not even months off of our schedule as we do this. We're able to do the comparison and gap analysis within minutes, definitely less than an hour, and we've put all of our procedures in that tool, and it's providing tremendous opportunities for those folks. What we're giving the SMEs and others is a spreadsheet that has the changes, has the proposed change, and that's going to all the subject matter experts that can share that. With that tool, we've been hearing that it they would be take them two to four weeks just to go through that and create that data that they have. Now, again, this is a tool for them. They can choose to use it or not. Some of the folks that have smaller type documents, they're going to use it as a benchmark or check. But like again, they do not have to accept the recommendations that the tool provides. It's just a great opportunity for subject matter experts that are new and not in their role for very long. It gives them a step up to help them guide them through the process. So couldn't have done it without it, couldn't have done it without our AI group. We challenged them to put a tool in place within four days, and they rose to the occasion and gave it to us in three. So very smart people, smarter than me. But now we're going to take it to the next level and create personas to help us drive future contract changes down the road and proceduralize this and standardize it.
SPEAKER_07So one of the other things I'll I'll ask, and I'll ask this to you, Richard, but also to others on the line, in terms of when you're looking at the revised orders, at this point, have you found any of the orders where there are areas where there are conflicts where, you know, one order says one thing, another says a different one. And again, as BJ mentioned, this is the time and opportunity for us to bring those things forward. Is there anything that you have discovered from a Savannah River perspective? And then from anyone else on the line, do you have any other examples of conflicts?
SPEAKER_02We have found a couple of conflicts. Um we're still, like I said, next week we are going to have the true sense of those. I believe right now we have probably five or six that have been documented so far. Um, but as they do their briefings next week, that that was one of the subjects that they have to talk to us about. Any conflicts or anything we wish we had that we didn't get. Um is Ashley um Charlton on the line?
SPEAKER_01Yes, I'm here.
SPEAKER_02Um do you mind just walking through? Ashley's our project manager that we brought on, uh, and she can talk of the couple of conflicts that we may have seen over the last couple of weeks.
SPEAKER_01So one of the ones, um so the DOE order for nuclear material management states um particular material is no longer um accountable, but then the NMCNA DOE order uh still holds it accountable. So uh we are moving forward with um putting into our alignment approach and alignment plan. Our intent is to interpret the revisions um as they are meant to streamline the processes. So if uh nuclear material management says it's not accountable, that was likely the intent to translate that to the other DOE orders as well. So that was one com conflict that we um have found so far as an example.
SPEAKER_07Jerry, go ahead.
SPEAKER_06Yeah, so uh another one that the team raised also DJ's probably falls more on the contract side of the house where we have eliminated or modified uh a past DOE order, gone to uh later revision to reduce um, you know, and and bring more efficiency to the process. However, in past reviews of the old order, we may have CEO letters that may have been written to the contractors that uh may have given extra clarifications, may have even added requirements above the DOE order. So there's a um a bit of discussion here of if I have a later revision now that now supersedes the old uh DOE order, how do I deal with these CO letters that may have added, maybe addressed things in the order, but also added additional requirements? Now, our approach is going to be we're gonna execute the latest revision of the order, and any old CO letters tied to it will be superseded with this new order. Um, I don't know how clean that will be across the board, but we're taking the intent of project velocity to say the government's intent is to reduce streamline, and if these additional requirements were above the order anyway, then this project is designed to eliminate that. So um I don't know how the field would respond to those various scenarios, but we're anticipating that that level of this discussion and uh friction at some point.
SPEAKER_07Okay. Well, I I think yes, yeah, go ahead, BJ.
SPEAKER_04I have to say, sorry, just responding to so I and I and I think that so the the hope of this right is again, you know, Jay, obviously pointing that out to the field office team is really important so we can make sure that we've got clarity and alignment and all that. But I do think that, at least as you articulated, the intent is right. We're looking, we're looking at scenarios where there are conflicts. And I think the default position that we have with this is the one that offers more flexibility is likely the right one moving forward. But I think we want to make that decision, obviously, eyes open in terms of you know the field office and the MO contractor together. There could be scenarios too where you're talking about where, you know, we've we've heard from other folks where that project velocity actually offers more restriction than some of the SEAL letters that were already afforded as well. Same scenario there, right? Just make sure you point it out to your your field office and we can work through and make sure whatever the right decision is, whether again project velocity holds or we have a sealed letter that offers more flexibility. The likelihood is that's where we're gonna err on the side of here. But we want to make sure that we iron those conflicts out and then everybody knows you know what the what orders and what the requirements are that we're operating to.
SPEAKER_06Right, great, great, thanks. Great.
SPEAKER_09Uh yeah, the um timely, um, timely discussion because before joining this, I was on a phone call with one of our sites over a similar type conflict, and it it it was actually associated with 470. So I not to go into any detail on this, but it would not surprise me if you run into situations where you're working on a site with multiple programs and those programs interpret things differently, and you're trying to um uh please two federal entities. So that's exactly the kind of thing that we want to hear about. Um, and you know, make sure you write it down uh exactly as you're doing with proposed resolution because I I agree that you know what the intent of project velocity is probably you know the intent we want to follow, but we also want to make sure that we don't violate any requirement that you know was maybe overlooked. And and uh that's one we're researching right now at one of our sites. So uh I to make sure that uh everybody is uh in in a good spot. Um I'd like to see those uh you know potential conflicts. Um when it comes to flat out requirements, um you know, bubble up so that we we can talk to it and you know I can uh talk to the powers that be with project velocity uh to see if you know we may need to revise some other orders so that they don't conflict with project velocity, say, um, which I'm I'm kind of anticipating right now at this moment, especially in the security directive. So um, you know, just communications and staying aligned and letting us know what the issues are, we'll we'll try to try to get ahead of them. But uh uh I would you know you don't want to put yourself out there as a site, you know, making a determination that winds up being, you know, a violation of federal law or something. So um, you know, we want to we want to work with you on that as and again, I I don't know of anything that is in that category at this point, but the devil's in the details, as you know.
SPEAKER_07Yeah, yeah. Thanks for that, Greg. And then Craig, I'm gonna come to you next, but but Craig, before you go, um I do want to emphasize that is one of the reasons why we really wanted to have Savannah River give that kind of their presentation because I mean they literally have two different field offices representing two different offices within the Department of Energy. And there are clearly opportunities where things could potentially be in conflict with one another. And I think you know, if we can solve for things at Savannah River, it solves for a lot of other problems or challenges across the enterprise. So that's why I really want to be, I want to thank the Savannah River team for kind of bringing this forward and having this discussion. Uh, Craig, let's let's go to you next.
SPEAKER_05Thank you, DJ. Can you hear me okay?
SPEAKER_07Yes, loud and clear.
SPEAKER_05Okay, great. So just as an example, in terms of uh measuring our success, for the 413 order that was changed, you know, part of the cancellation language says, hey, uh cancellation in and of itself doesn't uh absolve you of your obligations. So uh the contracting officer has to pull that off and modify that contract with the new uh CRD. So that might be one area we could measure right out of the gate is we know how many need to be modified, how many are modified, because that's the first, that's the first tripping hazard right there. So that's it.
SPEAKER_07Yeah, great, great suggestion, Craig. And I hope others heard that because I think just getting the alignment plans and what downstream of those have to be done is a measure of progress that we that I think we clearly could make. So thanks for contributing that. Okay, other other thoughts, feedback, other contributors or other questions? Okay, hearing none or seeing none again, Tim, Richard, thank you very much. I'm gonna go to Jay, Roger, Jay. I'm gonna give the floor over to you as part of our last section, and then we'll do a wrap-up and then we'll be ready to close out for today.
SPEAKER_03Thanks, TJ. So as you can see in in what Richard laid out, we're we're in a sprint to get to the alignment plan, but it's a marathon. There's an awful lot of activities that are gonna have to happen in time. And one of the roles that we're hoping that FCOC can play is a sharing of lessons learned, uh best practices, as we've always done in the past. So the way we've been thinking about organizing this is we're gonna have a uh webinar on a bi-weekly basis to allow a sharing session of uh where people are running into problems, where they've uh mitigated a problem. That would also be a good area to present. Uh but what we need feedback on is uh how long should that forum be? Uh we also talked about should we have separate formins for EM in an SA? Uh is there an advantage of having it jointly? So everyone's having a sharing session. Uh so we'd like to have some feedback on that. Uh we will be having our working groups focus on this, looking at the orders that are in their specific areas. Uh we're contemplating out of that that either that's going to be a mainstay in their agenda for their annual meetings. Um, so we're we're working through all that process as well. So any feedback that that you can give us on what you would like to see, because this is this is all to benefit our members. So we're we're looking at what do you need from FCOG uh in order to facilitate your implementation of the the new Orner Roosing requirements.
SPEAKER_07Great. And and and as you can see in the chat window, for those who have access, we do have our our staff at FCG.org email address. So you can certainly send any feedback or suggestions on how we can improve this process. As Jay mentioned, we'd like to do this on a on a bi-weekly basis, just every other week, have a reserve time. I I call it kind of an office hours. You know, you you don't have to attend, but if you want to attend to either share or hear others' stories, it's an opportunity for you to hear that. And again, if you want to have a separate session for just EM sites, because there may be some more EM unique type things, we can help facilitate that. Or if we want to do it collaboratively, jointly across the entire department, we're happy to do that as well. Either way, we want to just be a facilitator of that communication across the entire complex. Uh and again, we will have the recording of this up on our website as soon as it's available. So, again, if anyone that also uh did not get an opportunity, or if you want to tell someone, hey, go listen to this, you might get a few ideas. You're welcome to come back and look at the recording. Okay. All right. Tim, go ahead.
SPEAKER_08Yeah, just one suggestion, DJ, and I it just occurred as we were as um Jay was talking, is is you know, Rich, Rich is the point lead for Savannah River Nuclear Solutions, which has, again, the complex task of working across two programs. But every site should have somebody like Rich, I would assume. There's somebody out there like Rich. So if we want to start with maybe providing those names in the chat, or if if you want to start with that kind of a small list that we can have, those would be the ground level folks that are dealing with the day-to-day that we could help. You know, that would be a starting point to have, you know, from a uh um the leader point to to say what are those ground level activities. So just one suggestion, we may want to populate our chat with those names and those kinds of people that we can start with. That Jay, that might be the starting point we want to begin with, is just to bring that up.
SPEAKER_07Yeah, I think that's a great idea, Tim. And and we'll leave the chat window up for those who can, you know, if you know who that point of contact is, if you could put that in the window, or if you think that that's the right person, we'll reach out to them later and try to make sure that we've got the right person named for each of the sites. But again, I think it's a great starting point so that way we can focus on the people who are kind of quarterbacking these for your respective sites. Great suggestion. Okay, any other comments, questions, closing discussions before we get ready to say goodbye for the rest of the day.
SPEAKER_00I just want to add one key point. I think it's very important in regard to lessons learned. I think it's it's very important if we can you know compile all this information into a one location so people can have access to it. At one point we addressed this point or this challenge or this gaps, and how did we resolve that gap so people can go into it and look at and see the reasoning behind how we move forward in addressing that gap. So I think that would be a very helpful. Um lessons learned is going to be big things in this effort, quite frankly, because we are all learning into this and getting into it. I will highly emphasize the importance of lesson learned to share between different programs and put different sites. Thank you.
SPEAKER_07Thanks, Ahmad. That that's a great suggestion. And and I mean, we will certainly, from an FCOC perspective, offer our website as a place where we could put that. But you know, certainly I want to make sure that we consult with our federal customers to understand if that's acceptable for them or if there's someplace else. Because I know we have a what they have a SharePoint site already that has some information on it. And maybe that might be the more appropriate place, but we can certainly take that as an action to work with them as to where's the most appropriate place to do it. Great suggestion. Okay, all right, and thanks for those who are populating um the chat window with your points of contact. And Carolyn, thanks for the reminder of the NNSA SharePoint site. Again, that could be a good location if we segregate this by lessons that are being learned and resolved through the NNSA versus those that may not be applicable to EM. Maybe there's something separate from an EM perspective, but we'll work with the federal team to figure out the best place where we can document and and and capture that information. Any other comments? Okay. All right, seeing none, uh I just want to again thank everyone for spending the time with us this afternoon and and for contributing to uh what I would consider a pretty thoughtful and productive discussion. I think we have learned a lot and heard some approaches that I think people will take as useful. And and I really can't uh begin to express the appreciation that we have for the federal staff for listening closely to us here in the complex in terms of what we needed, the support for, our shared desire to streamline the DOE orders so that we can deliver the mission faster and within the resources that are provided. And so it's really important of the engagement that we've had with the customers and their openness to make this enormous change. I think it's really going to be a difference in terms of how our sites work and our alignment activities. Um, I also want to thank all of you who are on the call today for participating. Um, really want to thank our presenters, BJ, for giving the comments he provided, Tim and Richard for their presentations, uh Jay for providing some of the guidance that we need in terms of how we can best support you. And so, again, just want to thank everyone for your time today, your engagement, and your willingness to share in this discussion. So, if no other comments, I want to thank everyone. Hope you have a rest of the a great rest of your day. And let's just stay in touch. If there's anything else that we can help you with, please let us know.
Podcasts we love
Check out these other fine podcasts recommended by us, not an algorithm.