One of the most popular topics during this quarter’s Momentum conference was the ‘Odata Connections: Microsoft Power BI & Excel’. Presented by Tensoft Supply Chain Consultant and Power BI Black Belt Pro Jeff Piaskowski, this webcast covered some of the API connections for Tensoft SemiOps and DemandOps. Jeff provided a demo into the Power BI application with step-by-step instructions on how to connect and the possibilities built from this connection.
Below is a partial transcription of the beginning of this presentation:
“First place we’re going to start is with our FSM SemiOps APIs. What we see here at the top is the URL used to access the Odata API for the FSM application. Below the URL, you see the different data points or data sets that we have available here. The way that the Odata works is that we can use the main URL at the top there. Once we use that URL, all the available data sets below that would be available to us.
Let’s start in the upper left-hand Corner. We do have an AttributeSetup. This is the setup table for your collected attributes- things like wafer lots, vendor lots, test programs, date codes, etc.
Below that is our CycleTime. In that table, we have cycle time and queue time. We are able to link that to the attribute setup as well as the output attributes that we will get to here shortly. So, what’s the cycle time, and the queue time that was captured from the actuals and what were the lot numbers, PR numbers, receipt numbers and dates associated with that.
Next one you see here is the IBOMProcessDetails. This is pretty much a flat IBOM structure. It also includes the available inventory. So, what we’ve done here is kind of link those building blocks of your IBOM together and enable you to report on the inputs and outputs. I believe it’s at item level, process level and then I think the highest level there is a vendor level.
Next, we have InventoryInfo. This is all your inventory data. So those of you that know how FSM or SemiOps tracks the inventory, we never actually remove the inventory from the system. The record is always there. We just change the status to determine what to show you on particular screens, or include in your on-hand value. So, when you do use this, you will notice that there’s a large amount of data there, you will want to create groups or filters to make sure you’re looking for the correct status. We will touch on that a little bit as we move on here.
The next is a LotHistory. This is a genealogy and process history. So, we can look for a particular lot. Maybe not even a lot. We could look for a test program if we wanted to, an attribute value and look at the full process history where it went, what purchase documents were used, when it was received, what was my good output, my yield lot, vendor lot, things like that.
Next is OrderDetails. This is coming from the SemiOps side. We will get into the DemandOps side here in a minute. On the FSM side of things these are your sales order schedules. So this is the lowest level of data that we have available. Pretty much what you are looking at through the hierarchy is the sales order, the sales order line, and then a sales order schedule. So, there’s a one to many relationships between sales order line and sales order schedule and that’s the data that we’re showing you. A lot easier to come up when you have the detail information and then trying to go down.
OutputAttributes. This is attribute value by receipt. So, these are again your date codes, your lot numbers, your test programs, your attribute values pretty much that are collected upon receipt- like per receipt, what were those values?
ProdReleases. Pretty much PR and receipt data- what did I order, who did I order from, what was the quantity, what was the value and what was received and what remains open.
Last one is a Dates Table. You could create a custom Dates table in Power BI if you wanted to. We’ve created one for you, so you could easily just connect to it, load it in your data model and then start joining it to these different data sets or queries you see here. You can also just copy that dates table. So, by providing a dates table makes a little bit easier on the user side. There’s no need to really create your own custom dates table…”
Tensoft utilizes Microsoft Power BI with its vertical industry solutions to provide customers with deeper insights into their data. You can view the Power BI dashboard examples created for the Semiconductor and IoT industry here. To learn more about Microsoft Power BI and it’s implementation, contact us.