ERP & operations
ERPNext for Faswall and Durable GreenBed
ERPNext deployment, full system integration, and ongoing care for a manufacturing business in Philomath, Oregon.
By Curtis Tech Solutions3 min read
An ERP system becomes part of a business’s daily work. Getting the software running is one milestone; integrating it and looking after the environment are continuing responsibilities.
For Faswall and Durable GreenBed in Philomath, Oregon, Curtis Tech Solutions handled an ERPNext deployment that included full system integration, application setup, server setup on a Brownrice virtual private server, and ongoing maintenance and management. The engagement connected implementation with the practical work of keeping the system in use.
Software for a manufacturing business
Faswall makes building materials, including wood-chip concrete wall forms. Durable GreenBed offers raised garden bed kits. These are physical products, with software supporting the people and processes behind them.
In that setting, an ERP deployment needs to fit how the business operates. Product information, staff responsibilities, and the way information moves between activities all matter when planning an integrated system. Those are useful starting points for an implementation discussion because a working installation alone cannot establish how a team should use it.
Our scope covered ERPNext setup and full system integration. It brought responsibility for the business application and its hosting environment into the same engagement, so the work could continue across both layers.
Include the server in the deployment
The hosting setup used a Brownrice VPS. A virtual private server provides the environment where the application runs; it also creates an operational responsibility alongside the ERP configuration. Someone needs to manage the server as well as the software people use through their browsers.
CTS handled that server setup as part of the project. This is an important boundary to settle in an ERP engagement: who owns application questions, who owns hosting questions, and how those responsibilities connect when an issue crosses between them.
Plan for the work after setup
The engagement also covered maintenance, management, and ongoing upkeep. Those responsibilities continue after an installation reaches its first usable state. They keep a line of technical ownership attached to the system as the business continues to use it.
For anyone planning a similar deployment, the useful question is what support will look like after launch. Routine changes and unexpected problems need an owner, a way to assess their effect, and a clear next action. Planning that work early helps make the ongoing relationship concrete.
Bring implementation and upkeep together
The defining feature of this project was its breadth: ERPNext deployment, integration, hosting setup, and continued system care. Each part supported the same business application, and each needed attention at a different stage of the engagement.
For a business considering an ERP project, that is a useful way to frame the scope. Discuss the application and the surrounding responsibilities together. Establishing who will build, run, and maintain the system gives the deployment a clearer path beyond the initial setup.