Just a test. Nothing to see here.
Raspberry Pi now hooked up and powered by my solar charge controller.
Hmmmm. Last post was back in June. That’s about right. Back on July 6, my plans up here at Tunk changed pretty drastically. I was forced to scrap Plan A and move to Plans’ B and C. This required just about every ounce of energy I could muster and 100% of my focus, working tirelessly each and every day since then to get to a stable, survivable living state. My goal being to allow me to live comfortably on my 40 acres of land in my off grid cabin, able to survive life at 3600′ elevation. As a result, I had to shelve a lot of plans, projects, collaborations, and industry stuff that I had in the works.
I look forward to picking up where I left off and transition my focus from being 100% on the cabin/land project.
I’ve got a few exciting things in the works with the 502 data set and am also working on new opportunities with some fantastic folks already established in the industry.
I’m also still an account exec with a fully licensed and compliant 502 PP based in Tacoma and can assist in facilitating inventory transfers to/from other Licensed Producer/Processors and Retailers.
I look forward to more frequent and daily posts, as I will be opening up the focus of this blog to include my off grid endeavors and projects in addition to my industry related stuff.
It’s good to be back.
PS – I’m going to start posting more and more of my pics and other content here rather than on Facebook, Instagram, and Google. I’m done feeding all my original content and data to their AI/Matrix. I’ll blast out links back to my blog posts here on these platforms, but I’m done feeding them all my base.
Hi guys. Just a quick and dirty post before I head out to go paint a cabin. I’ve had email back and forth and phone calls with an MJ Freeway account representative this week. I have a link to a full demo of their platform that I have yet to watch. I did not get a demo, but spoke with the rep for about 20 minutes. Here are my takeaways:
- MJ Freeway was just made aware of this last week, just like the rest of us. They are scrambling to put a plan together. This is a little scary.
- They will develop/support/maintain an open API to allow 3rd party integration as mandated by the LCB. When I mentioned that it seemed like METRC pulled their bid because they locked people into their RFID technology, and asked how they dealt with this, he said they are committed to maintaining an open API as the state mandates and will be working on a plan for this in the coming days/weeks.
- I expressed my concern over the timeline for implementation – and also asked why the state mandates October rollout. He didn’t know either. I still don’t really understand the motivation behind the October hard date for replacement of Biotrack. Does anyone know why October is so important?
- I’ve sent follow up email asking for a call with a technical resource or product manager to get a more in depth overview of their platform, architecture, and underlying framework. Also to discuss their plans for backwards compatibility, maintaining the existing biotrack API, and how they plan to maintain/extend it with their own API approach/model.
NET TAKEAWAY: I am still deeply concerned about the viability of this massive software rip and replace project that the LCB has mandated. We already had a less than stellar list of initial vendors who submitted bids. We lost the first one because they tried to lock us into their proprietary technology and hardware. Now we are left with the “next best vendor” – ok who’s in second? Ok. Here we go again.
My request to MJ Freeway for a demo/overview was very well attended to. Within an hour or two, I received a phone call (went to voicemail as I was busy at the time) and also a follow up email with a personal offer to assist with my inquiries and questions and to setup a demo. This is encouraging. I think they may have even visited my blog and done a little digging on me. Hmmm. OK.
I have a call/demo setup next week and will ask some very important questions, mostly on the technical / software side of things. Here are a few of the items I would like to learn more about:
- Security – what have you done to address the security breach and how have you addressed the concerns of your customers.
- Robustness – deep dive on underlying framework and architecture
- Speed & Performance – how well does the app perform (with all available bells and whistles). e.g. how long to print, label, scan, and record data on a lot with 100 units.
- Architecture – hosted?, cloud? on site?
- Ease of Use – end user, manager, developer, LOB, etc.
- Openness / Integration – with 3rd party apps/services – Greenbits support? Weedtraqr support? Mr Kracken? – will MJ Freeway work with other commercial software built on top of biotrack?
- APIs – full feature parity? API updates? When? How? To whom? REST? JSON?
- Cost to business owners – how do existing investments in hardware and software to support compliance and traceability translate over to the MJ Freeway system.
- Software development methodology – agile? Release cycle? Next release plans? Features added? Features in queue? Size of dev team?
- Consulting – why needed if solution is “turn key”? What is a typical engagement? What are the rates? Who is this for?
- Number of customers? Largest deployment? Biggest project to date?
- Reference Customers – who can I go talk to that is an active (and sizeable) MJ Freeway customer?
- Corporate – history, growth, revenue, debt, legal, etc?
Hey i502 industry folks, what do you want to know about MJ Freeway, the current Apparent Selected Vendor to replace Biotrack for the state traceability system for Recreational Marijuana? Post your questions and/or concerns here and I’ll take it to the folks I’m meeting with next week.
Well, it looks like enough people spoke up to the LCB and they listened. I received the following Email from LCB yesterday regarding Franwell and their decision to pull the bid for the contract to replace Biotrack.
This is only a SMALL win. WE STILL DESPERATELY NEED A BETTER SYSTEM THAN BIOTRACK. MY NEW CONCERN: DOING THIS BY OCTOBER!!!
After spending 15 years in the Enterprise software space, I was involved in a number of large scale integration, migration, upgrade, and “rip and replace” style software development projects. These projects are costly, messy, and never go according to plan.
Why is LCB in such a rush to implement a new system by October? If this mandate stands, there is ABSOLUTELY NO WAY TO IMPLEMENT A ROBUST SOLUTION for a project at this scale. Especially one that aspires to do a full rip and replace with a standard, dev/test/release cycle in between. These types of projects take 18-24 months at best, let alone 4 months.
4 month dev cycle. With a government project?
ARE YOU FUCKING KIDDING ME?
Text from letter from LCB:
Attention Licensees: The below message was sent yesterday by Deputy Director Peter Antolin to licensees who had written to the Board and staff regarding the marijuana traceability Apparent Successful Vendor and RFID tags.
June 7, 2017
On behalf of the Liquor and Cannabis Board, thank you for writing recently to express your concerns about the change in vendors for the state traceability system and specifically RFID tags.
RFID Not Required
The WSLCB will not require RFID as part of the marijuana traceability project. Our Request for Proposal (RFP) was clear that the marijuana seed-to-sale traceability system must support a variety of tagging methodologies such as bar codes, RFID, etc. The RFP requirements did not allow a vendor to make any assumptions regarding use of a single tagging methodology or allow vendors to include any such costs affecting the state or our licensees in their proposal. In addition, unique plant and inventory identification numbers will be centrally created, maintained, and made available to third-party software systems via the API. Licensees will also be able to print their own labels.
Traceability Advisory Group
As the WSLCB prepared the RFP, we engaged representatives of the major industry trade organizations. We held several meetings together to gather input and clearly communicate our intentions. At the most recent meeting held June 6, we again asked that the representatives of the Traceability Advisory Group communicate with their members about this important point.
Change in Apparent Successful Vendor
As we have indicated, the Apparent Successful Vendor (ASV) was not final until contract negotiations were complete and a contract was signed. Earlier today, the initial ASV, Franwell, withdrew its proposal for Washington State. An ASV is the procurement term used for the highest scoring, responsive vendor.
We are pleased to notify you that the second place bidder also submitted a strong bid and has accepted our choice to be the new ASV. MJ Freeway is the new ASV. We will soon schedule a product demonstration with our Traceability Advisory Group and begin contract negotiations quickly to get this project implemented.
This project is on a tight timeline. The new traceability system must be in place Oct. 31, 2017. We are taking the necessary steps now to ensure a smooth transition from the current system to the new one.
Thank you again for writing the Washington State Liquor and Cannabis Board.
Brian E. Smith
Washington State Liquor and Cannabis Board
Nah nah nah nah,
nah nah nah nah,
hey hey hey,
The day could not come fast enough. Today, the WSLCB announced the selection of technology company Franwell as the Apparent Successful Vendor (ASV) to replace the existing Biotrack seed-to-sale traceability system in Washington State.
I can’t believe they plan to migrate to an entirely new system/framework by October 2017. I don’t see how this can be done given my background and experience working in the enterprise software space, especially when dealing with government agencies and projects. I hope Franwell has some ninjas on their team because they are going to need some serious SQL coders to port from the underlying Biotrack data model. Unless they already have a migration tool/util already built.
Need to go check into these guys ASAP. I really hope they are better. I have a ton of questions on how deep they are going to go to rip Biotrack out. Could potentially affect ALL of my data mining stuff. #buhbye#biocrapthc #goodriddance#worstdatabaseever #lcb #slcb #i502
New rules under consideration for i502 announced today. 314-55-045 has been expanded to include terms that define what rule, law, or violation history might prevent an applicant from receiving or renewing their marijuana license.
What timing – someone was just asking about this on one of my other posts. Gotta go back and tag em here.
I have a new role and opportunity in i502 helping manage, broker, and sell to licensed Producer/Processors and Retailers. I have an inventory and price sheet I can forward and am happy to assist with any type of inventory transfer desired, whether you are looking for wholesale b2b or retail transactions.
Have access to full range and spectrum of wholesale/retail products. Also buy in bulk and always looking for quality product, starting material, and trim.
DM, email, txt, or call for more details and pricing.
@eisenetics [Instagram, snapchat, twitter]
Because Biotrack is stupid and their database tables suck, this table doesn’t display the actual name of the Licensee that had the violation. Until I figure out a better way, here’s a nifty URL that you can use and just cut and paste the license number and add to the end of the URL to see who committed the violation.
https://502data.com/license/[paste license number here]
For example, https://502data.com/license/414841
[TODO: add links to table for license name lookup and WAC code and case # linkage]