By Khurram Ahmad, CEO of Smart IS International Working with the Blue Yonder (BY) WMS application can take on many roles. Your relationship with it could be that: You are a general user that primarily interacts with the application through the provided screens and navigate using the menu options. You are super user and often end
Tag: WMS
Auto-Waving in BlueYonder WMS Application
By Khurram Ahmad, CEO of Smart IS International The BlueYonder TM (BY) WMS product comes with a rich featured Wave Planning process. However, it is limited in automating the business rules that are generally operationally implemented during the wave planning process by an organization. When we evaluate Wave Planning SOPs for an organization the following common
Business Intelligence for JDA/BlueYonder Systems:
Analyzing Need for a Labor Management System By Saad Ahmad, Executive VP of Smart IS International Abstract Blue Yonder (BY) tables contain valuable information that can determine important Key Performance Indicators (KPIs) for a site. Such data exists in tables like “dlytrn” that are extremely large and not easy to query. Moreover, due to deployment decisions
Right way to tackle JDA/BY Interfaces
By Saad Ahmad, Executive Vice President of Smart IS International Every WMS implementation needs to deal with interfaces. This includes host interfaces, e.g. interfacing with SAP, Oracle, JDE, etc. and also to the automation equipment. Many times the project plan calls for these tasks at the wrong time and that can lead to overall delays and
Web Framework of JDA/BY WMS 2017
Considerations for an Upgrade By Khurram Ahmad, CEO of Smart IS International As an organization you have committed to upgrade to JDA/BY WMS 2017+ and are in the process of evaluating the effort required for this upgrade and whether this upgrade can solely be considered a “Technical” upgrade? Like any organization running pre-JDA/BY WMS 2017+ software,
Querying JDA/BY WMS Data for Adhoc Analysis
By Saad Ahmad, Executive Vice President of Smart IS International Overview JDA/BY instances can have over 1000 tables and over 5000 distinct field names. Exact counts can vary based on the options that are installed and if there are customizations. Typical RedPrairie installation is in a single schema for oracle or a single database in SQL