only grabbed a couple. might take some more next time I can get in there. Only get an hr at a time. sandbox clears between visits. had they rolled this out in 2016 we’d be in decent shape at this point. it looks reasonable. mostly.
OLCC apparently expects chaos, and I believe they’re correct. because I don’t think they understand what we do. still.
For extractions, the waste weight should be calculated as the difference between the weight of the source cannabis material and the weight of any cannabinoid concentrates or extracts created during the processing job. For example: A processor uses 100 kg of bulk flower in an extraction and distillation process. The process results in 1 kg of terpenes and 15 kg of distillate. They would record the waste as
84 kg of spent biomass (100 kg - 1 kg - 15 kg = 84 kg).
anyone else having trouble with OR METRC’s latest training videos, as embedded on the WIKI (Metrc Oregon Wiki)…turns out they were recorded and posted at reasonable resolution.
so rather than calling OLCC idiots, like I did, click on the settings icon, and select a more reasonable resolution, so you can see what they’re trying to tell you.
Or just click the links from the bulletin in metrc instead of the wiki. Those links work just fine, or at least they did earlier this week. They (OLCC) are probably unaware of the issue on the wiki.
Five days out, and OR’s Metrc specialist admits that the training “scenarios” they’ve been pointing at for days now haven’t actually been created yet…
Thank you for letting us know about the link issue. We do not have a process job scenario created yet. The scenario link was removed until we can get the scenario created.
so… the first thing you need to do when you get in your sand box is adjust yourself up some damn weed.
they provision you with only two 20g packages of “buds” and two 20g packages of trim. Supports the hypothesis that “they just don’t understand what we do…”
then we create some processing jobs. this set almost covers what we do. need a couple more.
not impressed that we can’t push these via CSV…nor that CSV downloads don’t include the attributes.
pulled two pakages from the incubation; “huffables” and “spinnables”. huffables go on to “purge” spinables go to "spun. should have included waste, but was in a hurry…
You’re my favorite pnw member that actually gets down to business. Love watching your solution making / shit talking / begging the question. You make your crew look 2x cooler by being a leader in the present. I literally apply a mental note on your associates/ coworkers that communicate here and try to respect them more because they work with or around you.
Straight fuck you with a little icing on the cake to appear friendly or / here’s how I skin a cat no bullshit.
I’ll take your discourse any day. Positive. Negative. Intentionally with reason. The entire west coast could learn from your ability to communicate with the world. You could literally be trying to offend me and my friends / people I support and I’d be trying to look at your words from a different angle before responding. You dispell and your magic is noticable. You, good sir, have found the key to real neutrality/discourse and I’d love to highlight/reflect upon that.
Seeing as how you’re the associated team, I’ll take your direct word he’s special and something else to be around. If you couldn’t tell, based on our discourse you have maintained my respect during your moment of independence channeling fire yum yum spices to all, but he knows all and all you’ve done or said and holsters it with his verbal pistol ready to take fire. Even if you don’t like me, I like you because I know you’re associated. Trusted. @Akoyeh I welcome any attempts at breaking my opinion. I don’t think you’ll understand I am constantly engaged in your community.
You rock so much. <3 Thank you for the share. Looks like Michigan will not be getting this new tool this year…maybe but probably not. So I’ll still have my paperwork and all those tags.
how would you interpret this directive (attribute)?
"Outputs are intended for oral consumption or intended to be used as an ingredient in a product intended for oral consumption.”
a. Includes edibles and tinctures, as well as extracts and
concentrates that are intended to be consumed orally (e.g.
"RSO”). Also includes extracts, concentrates, and products that may be used as an ingredient in an edible or tincture.
All of the hash in our inventory might be sent to edibles. the vast majority is unlikely to go there, but certainly any of the decarbed BHO or THCa we prep for carts could be diverted to the kitchen if they required cannabinoids.
does it all need the “custie might swallow it” designation?
Because one day someone might select that jar to make edibles?
probably not the intent.
Not sure how else to interpret may in this context.
I’ve asked for clarification, but the response I got back when asking if the attribute “none of the above” was appropriate in a specific situation
If none of the other five options available are applicable, then “None of the other options” is what you should use.
doesn’t leave me with any real expectations of receiving “clarity”.
So do I just proactively add “could be eaten, one day, maybe” to our decarb process(es) and call it good? Or perhaps create a special “decarb for edibles” process that does nothing other than add the required attribute after a perfunctory heating (“sterilization”) step?
Did your user group sessions explore these concepts?
Our most recent one did not.
I hate to interject with some off-topic, but what are the odds that Metrc is the forever solution? At the point my state gets its ass in gear, I’d prefer they weigh out some options instead of joining the pack of states lining Metrc’s coffers.
Damn, sad to see. I hate all the little random bits of plastic junk that come along with our industry. I’d go mad having to tag my turds before I flushed ‘em,
Iirc WA tried Biotrack. It sucked more. Metrc allows you to do things you shouldn’t do. Biotrack constrained you to the point where it was often impossible to document allowable activities. It was also a big ball of mud, having clearly been repurposed. I was so pissed off I threw opensource tools at it to get at the underlying schema, and found things like a fully populated ZIP code table in there. Got into some very heated calls with their ceo at one point.
At least one of them was because they were treating the thing like excel and not a relational database. Storing the same value thousands of times as if their programmers didn’t understand normalization. Wasn’t clear their CEO understood that term….it was also programmed in Visual Basic, which had already been deemed “legacy” by Microsoft at that point. CEO claimed to be a self taught programmer. which I’m guessing meant “nobody else could understand his code”…I may have told him that.
which means the person I emailed saying that the above link pointed at a page that had not been updated since 12-2020 responded by deleting the page?!?
seriously?!?
It’s the third or fourth time they’ve shuffled the links around and not actually pointed anywhere useful (because they have not built the thing they are trying to show us!!!).
Edit: last email said that those scenarios won’t be created before the new features go live, and that OLCC never claimed they would be, and have no obligation to do so.
So why the links?!?
NOTE
One neat thing our guru noticed while playing in the sandbox is we now DO have accumulators.
They’re not tags.
They’re the PROCESS JOB of “Sock run” or “Solvent washing Pans/jars” which are both “extraction”.
You can keep adding tags (dribs and drabs left over that would otherwise be “wasted”) to a job until you pull the first package. So I can solvent wash dishes for a week or two, recover the solvent for reuse, and actually document where the hell that kg of winterized extract came from. without burning tags at every addition. Or at all until I pull the extract!
Now the only thing holding us back from “dish-tillate” is the sharpie on the containers.
If anyone in Oregon is having trouble accessing the new jobs “feature” that went live today, one has to update the permissions in the admin-employees tab before they can be viewed by anyone, edited, or accessed without the system crashing. Took me a minute to figure that out after @cyclopath reported non-functionality. Staying compliant is going to be a lot more complicated as of today, so we will try and keep everyone updated as we encounter more problems and solutions.
