Depends on the extent of EPICOR deployment at the PA site and use of Projects(a bit of a stretch), along with the extent of really using Scheduling within EPICOR.
As well as if Engineers are all in PA, or some in Colorado…
Additionally, do Engineers provide work for both sites? Colorado Engineers for PA and the opposite!?!?!?
USING Epi-scheduling and all utilities of Resource Scheduling Board, Overload Informer, etc…
and the fact you already schedule PA-Engineers for PA jobs. (I presume you want to schedule these same Engineers as to time devoted to Colorado efforts.)
You are not running MRP(as shared at EUG) … no MRP suggs for Jobs
The scheduling Board and other Epi-pieces would show JOBS for Colorado engineering-efforts…
you want to be able to manage things, aligned to what you already have in place.
New Resource Group “Colorado” as any job with a CO requirement will now have visibility (as to NOT being started - see below)
NEW MFG Dept in EPICOR = COLORADO-requirements (for a dummy employe against OP 10)
An Epicor job need not be issued material, but OP sequence … humn?
OP 10 would be Colorado Prep and be backflush able and aligned to COLORADO RG (no real time, the dummy-employee, and no labor cost), ergo MFG-DEPT and Employee aligned to that dept
OP 20 would be Engineering-requirement to the Engineering RG (in PA?)…
The PA engineers, similar to what is already on-going in existing JOBs.
When engineer records first time entry on OP 20, OP 10 is backflushed.
For remainder of OP 20 you’ll see % complete based on EST hrs and Actual Hrs
Why do this with an OP 10 and an OP 20 ?
Easy to SEE all JOBS w/o any activity, as no OP 10 time-entryreporting,
These are Eng-requirements that have not started yet… but have a scheduled date (to start)
You can look at RG for COLORADO via std-EPI-access and move JOBS around, impacting the PA ENGINEERS, but also see schedule capacity conflicts as to OP 20 requirements and time-phase.
You can also play around with QUE-times… etc
If ENG-efforts need to be reviewed/approved by an ENG-MGR or others… before confirmed as ready for Colorado, use an OP 30
If Colorado needs to process MFG-and provide confirmation against their prod-completion that what PA engineer provided is OK, OP 40 (waiting for Colorado to confirm (put in a QUEUE time aligned to when they THINK they will complete First-article on their job, or when their job is scheduled in their system)
If feedback from COLORADO results in issues, and more time required for PA Engineer to manage… OP 50 (or perhaps REWORK on OP 20)
Op 10 and OP 40 would not be capturing real-time or costs, or provide for planning PA Engineers, but would allow for pushing (Time-phase) dates.
OP 50 initially, may have 1 hr on the Released JOB, as you anticipate some efforts (minimal of the PA Engineer). .
IF more work is required, UN-engineer the job and revise time required, then re-engineer and schedule the JOB.
EX: Initially 1 hr on OP 50… So the schedule will consume 1 hr of capacity avialbility.
W/o changing the time requirement on OP 50 when issues develop, scheduling availability is mis-represented.
If this cycle continues that things in Colorado require more Eng-work,… (more PA Engineer work), add more OPs to Job.
~ ~ ~
While the Project module provides for non-MFG time entry on PROJECT-Phase Jobs, you are already managing PA Engineers, so attempting to leverage PROJECTS would be craz. Although tasks can be assigned… the extent of pure scheduling… NOT available!
Unfortunately not likely to go to EYG next week, or we cud have discussed further.