Infor VISUAL 10 was released in December 2020, and quite a few features were added. There are many resources that go into great detail about the new functionality, including release notes, but here are the highlights we think are most important to know. If you want more details, go to the Visual South VISUAL upgrade page here.
Infor SyteLine has been around for over 30 years and has operated under a few different names and brands during that time. The product has been called Symix, Frontstep, and SyteLine. Most recently, Infor rebranded to CloudSuite Industrial, but the SyteLine name really never went away, so you will hear these terms used interchangeably among people who work with the product.
Overwhelmingly, project-based manufacturers have a requirement for a physical project plan to execute against, where costs can be captured at many levels. That is why Infor CloudSuite Industrial/SyteLine ERP provides a good solution for traditional build/engineer/configure-to-order manufacturers who need to manage a more complex series of events to manufacture finished goods.
You need a plan to select the right ERP
Visual South has helped thousands of manufacturing businesses evaluate ERP software since we launched in 1994. During all those evaluations, we have engaged in both good and bad experiences.
The answer to the question of “Do your need ERP software development services?” is typically “no,” but that’s based on having a capable and purpose-built ERP application, such as Infor CloudSuite Industrial ERP. There is a caveat: Sometimes you may need to extend the application using the native toolset to address business-specific requirements.
The development team for Infor’s CloudSuite Industrial ERP continues to follow the well-planned product roadmap, and is executing the plan efficiently. The roadmap enriches and extends the highly ranked and widely accepted application, which now has well over 5,000 manufacturing sites running it worldwide.
In this article, we’ll highlight our favorite features that have been released since the CloudSuite Industrial/SyteLine 10 core application debuted in 2018.
I speak with lots of companies and many of those conversations revolve around ERP software evaluations. Recently, I’ve had quite a few conversations with companies that are running Sage 500, or any of the other Sage products. They ask me whether the rumors about a Sage 500 end of life are true and if so, what the future holds for their ERP system. To be clear, I represent Infor ERP and that is where my expertise lies. I am not an expert in any competitive solutions, but my views are shaped by what I hear from the people I talk with. In this article, I’ll give a quick rundown of what I think you should expect with your Sage 500 ERP.
Medical device manufacturers need specific functionality in their ERP system. The functionality requirements fall into three main categories: in-depth abilities to handle cradle-to-grave lot and serial traceability; integrated quality control; and extensive abilities to meet demand requirements and schedule the associated work orders to build-to-stock, build sub-assemblies, and produce finished goods.
When a company decides to start an ERP search, the people involved can articulate why they are looking for ERP because it’s their reality. But finding the right solution is more difficult because looking for a new ERP system isn’t something they do every day. In many cases, people involved in the search have never looked for a new ERP system. In other words, it’s a lot easier to identify why you need an ERP rather than what ERP you need.
I want to start by telling you a little bit about my background because I believe it will give some context to this blog. I proudly represent Infor ERP products and have been at Visual South since 2002. Five years prior to coming on board here, I was an SAP consultant. My specialty was the sales/distribution module, along with the variant configurator. I was part of many full implementations in a variety of industries, taught training classes, and helped with presales efforts. My first implementation was on R/3 version 3.1G and my last was on version 4.6.
