infor.com
concierge
infor u
developer portal
Home
Groups
Lawson - Supply Chain Management Customer Community [READ ONLY]
IC182 - Par Location Utilization
Stace Webley
I'm currently exploring the option of using IC182 to update par location par levels. It has taken me a few days to figure out each piece of data in the report. The ones that I struggled with were"Avg Utilization" and "Recommended Par Level."
Apparently, "Avg Utilization" is the sum of all pieces issued out within the time period in the report parameters divided by how many reqs there were plus one. Ex: 1000 pieces divided by (9 reqs + 1) = 100. What I don't get is why add one to the number of reqs you had? This dilutes the average number of pieces requested on each requisition.
The other piece of data, "Recommended Par Level" is still strange to me because in many cases this value is higher than the "Avg Utilization", but in some cases it is lower. How is this value calculated and does it take into account the "Replenish Frequency" (how many days between replenishment) used in the report parameters?
Any one using this report or have answers to these questions? Thanks!
Find more posts tagged with
Comments
jon-athey
I've never liked this report. It's hard to understand. I created this report in Crystal that suggests a par level of 2 weeks average usage based on whatever range of usage you enter. I ususally go 6 months.
dechevar
Jon, Can you share the code for this report? I agree that the IC182 is not user friendly. We are currently designing a new PAR utilization report that we are hoping will not only address the utilization, but also help formulate KanBan opportuinities. We have implemented Kanban on a number of PAR locations with great success.
jon-athey
I'm not familiar with Kanban but just from some initial Googling it looks like JIT. How is that accomplished for a par location? Doesn't it require replenishing the location daily? Here's my report.
Stace Webley
We have the KanBan system going for half our org right now. Basically, a bin has a card placed in it at a reorder point. When users take the supplies they are supposed to pull the card when it gets to that point and put them in a place for the next order or order it themselves. Then when the supplies come in they place the card back in the rotation. This makes the location user managed and never counted. Requisitions are placed by a person in the department as the KanBan card is pulled. Basically it is like a visual for reorder just like a dashboard indicator in a car.
dechevar
Thanks Jon.
Kanban is not JIT, but works well with it. Basically we have set up a two-bin system in nursing locations for low value inventory and overstock. Once the first bin is used, it is pulled and put on top of the shelf. The PAR counter only needs to scan the empty bins for replenishment with no need to count - just enter 0. We do this for stock as well as JIT orders. The nurses have been very responsive.
Here is a link to a similar system:
www.leanblog.org/.../
Here is what one of our nurses wrote: Kan-Ban Supply System at Premier Heath
Last fall, the surgical patient care unit (6SS) had the opportunity to pilot Kan-Ban, a new and exciting organizational supply system. Kan-Ban is a two-bin system that maximizes inventory rotation to eliminate expired items, as well as initiate restocking of supplies, prior to depletion. We were excited to trial the new system, because our previous supply carts were often missing items or were overstocked, making it difficult to retrieve the needed item. Since implementing the new system, we no longer run out of supplies. When the first bin becomes empty, the bedside leader will pull it out and place it on the top of the cart, and then pull the secondary bin forward. Because the secondary bin is in place, the bedside leader still has adequate supplies available, and, by placing the bin on the top of the cart, it will “signal" central supply that the bin needs replenished. Placing the bins on the top allows central supply the ability to quickly and efficiently see those items that are low on supply.
Based on a post implementation survey, the bedside leaders indicated the following:
- Supply availability improved 39 percent, and frequent delays in patient care decreased by 17 percent. Many respondents noted that the availability percentage will likely increase over time, as they are still learning the locations of items.
- Initial barriers, such as learning locations, PAR level adjustments, and addition of new supplies, have been resolved with the collaboration of central supply. Based on bedside leader feedback, we have created consistent locations for supplies, added labels, and adjusted supply layout, which has increased both functionality and efficiency.
- Other items or areas to consider include adequate spacing for carts, increasing font size on labels, and the height of shelving specific to the bottom of the cart.
Overall, bedside leaders report great satisfaction with this change, and 100% of survey respondents prefer the new system as compared to the old PAR level system.
kim-gonzalez
We scan the card with our MSCM handheld and zero the qty to order the par amount. Wish we could get MSCM to automatically put the zero in..... We are going to look at using Mobile Requisitions with the PO15 quantity set to the par when we go to Lawson 10 next year.
dechevar
You are exactly right, just scan and enter 0. The difference with a two-bin system is that the safety stock is in the second bin so nursing does not run out of product. In addition, items are automatically rotated upon putaway to avoid outdated product. The empty bin is filled and put behind the other bin - new product is not thrown in with older product.
[Updated on 6/25/2014 4:39 PM]
Legacy Contributor
Does anyone have an documentation on this process that they would be willing to share?
Thanks!
Stephanie
stephanie.kowal@baystatehealth.org
dechevar
Here is another KanBan method utilizing RFID video. The access code is "supply" (lower case):
vimeo.com/72234146
Important Links
Community Hubs
Discussion Forums
Groups
Community News
Popular Tags
ION Connect
ION Workflow
ION API Gateway
Syteline Development
CPQ Discussion Ask a Colleague
Infor Data Fabric
Infor Document Management (IDM)
LN Development
API Usage
FAQs, How-To, and Best Practices