I've been looking for good resources on the differences between Policy, Process and Procedure and have found several, but I am somewhat perplexed regarding a number of ITIL references that I have found.
Most notably, a number of ITIL references only speak of "Procedure" as a process component, not as an entity in and of itself.
The intimation is that procedures only exist in the context of a defined process and are inextricably tied to that process.
My personal take has always been that a procedure is a task or set of tasks created to for some purpose. That purpose may be to complete a step or steps in one or more defined processes, but it is not an absolute requirement. We may create procedures in anticipation of process creation or need, they may be reused for multiple processes, but they are sufficiently narrow in scope to (in general) apply to a single, or at most, few, task or circumstance. As such, procedures (typically) do not cross narrow boundaries (i.e. the procedure for replacing a laptop battery is unique to the laptop model and is not applicable elsewhere). Processes have much broader boundaries (e.g. battery replacement may be a process of remove the old battery, put in the new battery and connect).
What I see as a result of all this is that Processes often span organizational boundaries (ideally the entire organization would use one process to accomplish a goal) and that Procedures more often do not span organizational boundaries (laptop battery procedures are not applicable to motorfleet battery procedures), leading to the conclusion that Process and Procedure are at their core, independent objects.
While each requires the other for practical use, they can exist independently, implying that Procedure should be spoken of as an entity in and of itself and not just as a process component...

I've been looking for good resources on the differences between Policy, Process and Procedure and have found several, but I am somewhat perplexed regarding a number of ITIL references that I have found.
Most notably, a number of ITIL references only speak of "Procedure" as a process component, not as an entity in and of itself.
The intimation is that procedures only exist in the context of a defined process and are inextricably tied to that process.
My personal take has always been that a procedure is a task or set of tasks created to for some purpose. That purpose may be to complete a step or steps in one or more defined processes, but it is not an absolute requirement. We may create procedures in anticipation of process creation or need, they may be reused for multiple processes, but they are sufficiently narrow in scope to (in general) apply to a single, or at most, few, task or circumstance. As such, procedures (typically) do not cross narrow boundaries (i.e. the procedure for replacing a laptop battery is unique to the laptop model and is not applicable elsewhere). Processes have much broader boundaries (e.g. battery replacement may be a process of remove the old battery, put in the new battery and connect).
What I see as a result of all this is that Processes often span organizational boundaries (ideally the entire organization would use one process to accomplish a goal) and that Procedures more often do not span organizational boundaries (laptop battery procedures are not applicable to motorfleet battery procedures), leading to the conclusion that Process and Procedure are at their core, independent objects.
While each requires the other for practical use, they can exist independently, implying that Procedure should be spoken of as an entity in and of itself and not just as a process component...

Thoughts (apologies for being long-winded)?

Sounds like you have a pretty good handle on the differences there but I would say that in my opinion they're not independent as the procedure should work within para,eters set out by the process and policies

Generally processes can be very long and drawn out. An example may be a process aligned with a user administration policy. There maybe procedures aligned with different groups of users such as administrators, power users, and 'normal' users.