What happens before you open up P6 at all? long before

we open primavera in any revision you know we're meeting with that pm team just to have a kickoff and get an understanding of what you know our work breakdown structure is going to look like what level of detail we're going to go to in the schedule just setting some fundamentals also establishing things like what external restraints do we have that we have to document in the schedule what lead times do we have to document in the schedule it's really You know, when you start a project, you have this huge conglomerate of information that may not be perfectly detailed and you almost start the schedule at that same one bar level, right? Start and finish.

And then it's decomposure, right? We're just going to decompose things into lower levels of detail, you know, more specific, more granular till we have that network at a place where we feel it's executable.

It's not over detailed, which happens a lot in schedule creation.

but it's to the level of detail that we feel comfortable that we can spin off look ahead schedules from that master schedule and do our actual execution in the field.

We probably have a couple meetings like that with the project management team before the schedule is open, before Primavera is open, and before the project team ever starts looking at those items like the project schedule, We then go and after those meetings, we'll do a little bit of development.

We'll get the WBS built.

Yeah, I think Oracle's own position is that P6 isn't going anywhere and works along from very cloud, which I think it leaves from conversation I've had with other leaders, it kind of leaves some people left sitting in the middle of a decision like do we Do we migrate over to OPC or just stay in P6? How would you summarize who should be on OPC and who should just stick with P6? Is it a clear cut decision? Is it better suited for big firms, smaller firms?