Take Notes! Some useful tips on ERP
Through our eyes, this CIO primer on ERP systems could be viewed as a benefits list for Orchid Notes.
This recently published CIO article by Bart Perkins provides a useful primer for those new to ERP, or just setting out on an ERP implementation.
Most of our audience are established implementers or users of Sage 300, so we’d hope they aren’t still asking “What is ERP?”. It might also be a bit late for checklists on ERP planning and deployment.
Despite that, some of the content still resonated with us...
We came across the article while preparing for a presentation on Orchid’s Notes module, so we viewed the content through that lens.
The 4 headings under key features of ERP systems could be reimagined as key benefits of Orchid Notes for Sage 300.
Let’s try them on for size:
- Enterprise-wide integration:
The seamless flow of information between different business units and individuals is one of the key selling points of any ERP system, but what off-the-shelf data model encompasses all the data that companies rely on day-to-day?
Orchid Notes provides a simple, cost-effective, highly configurable way of providing relevant, custom content where and when it’s needed, throughout Sage 300 and across the business.
- Real-time Operations:
Context-sensitive Orchid Notes are displayed as soon a Sage 300 screen is viewed or refreshed, removing the need for swivel-chairing to other systems or looking up offline content.
- A Common Database:
Orchid Notes data (both content and configuration) is all stored within the Sage 300 database itself, and hence automatically included in your standard backup processes etc.
- Consistent Look & Feel:
Developed in the Sage 300 SDK, Orchid Notes forms an integral part of Sage 300, making it quickly accepted by users and requiring minimal training.
A Final Note: Avoiding Hidden Costs
Later in the CIO article, Perkins warns about some of the factors that often lead to underestimating the costs of an ERP project.
One of the key pitfalls he highlights relates to ‘custom code’, and he maintains that customizing ERP remains a bad practice.
What he has in mind is support issues through voided warranties, plus the challenges of having to retrofit custom code each time you upgrade your ERP system.
Fortunately, this isn’t an issue with Orchid Notes, or other Orchid modules developed in the Sage 300 SDK.
Our software does not make changes to the ERP codebase itself. Instead, Orchid modules are upgraded in the same way as core Sage modules, and the associated data is carried forward with the Sage 300 database.
In fact, this even applies to custom Python scripts used by Orchid’s Extender product, including those use to create ‘Extended Notes’, as these are also stored in the Sage 300 database.