Epicor ERP Software
Search
Welcome to the Epicor blog community, covering topics to inspire discussion where Epicor thought leaders, employees and partners alike can share insight across industries.
Implementing Consignment Inventory (Part 3 of 3)

In previous blog posts, we covered the definition, initial setup and advantages of managing consignment inventory using Epicor ERP v9 or v10.

Several other questions remain to be answered, i.e.: “How do we verify the consignment inventory quantities?” and “How do we finish the contract without ending up with extra inventory?”

Cycle Counting/Physical Inventory
Consignment inventory is still an asset of the company that currently owns it. It is therefore the distributor’s fiscal responsibility to periodically count that inventory to make sure it is still in its proper place. If you have used the procedures defined in the previous blog posts, then you can use the standard cycle counting or physical inventory module that is built into Epicor ERP v9 or v10.

Since Epicor supports counting by warehouse ID, you can simply initiate a physical inventory for your consignment warehouse. If you have multiple customers, you would have multiple warehouses, with each warehouse to be counted separately.

Of course, in order to do this inventory check, you still need access to the inventory itself, or you need a trustworthy customer that will return the physical inventory results.  It is up to you to determine what you are going to do with any adjustments that are found.

  • If during the count, you find more parts that were supposed to be there, that may mean:
    • You have overbilled your customer for product they did not actually use, or
    • You shipped more parts than you acknowledged in the electronic transfer order.
  • If during the count, you find fewer parts than you were supposed to:
    • Your customer has used more parts than they have told you about.

In either of the above two cases, you need to confirm that there is a clear declaration of who is responsible for any variances found during the physical inventory. If you followed all of the procedures, there should be no unverified variances in the shipment. This would then leave only one option for the variance: issue a credit or an invoice for the difference in inventory quantity.

Closing the Contract
As the contract is coming to an end, you want to ensure that you do not end up with large quantities of inventory sitting in your customer’s consignment warehouse. At some point, they will not want that inventory anymore, and you will need to take it back (unless you have a clause in your contract to protect you).

Our recommendation is to closely monitor those parts as the contract is winding down, to make sure you have reduced or eliminated the minimum on hand/safety stock levels that you have defined throughout the system. Also, verify that any forecasts that the customer has delivered represent real, sellable product.

Posted by Tim Shoemaker, Senior Principal Consultant, Epicor Professional Services

Serving on Multiple Scrum Teams Simultaneously

A few posts back, Dawn wrote about writing technical documentation in a Scrum environment. She provided an excellent overview of what Scrum is and how to navigate it as a writer, so I won’t retread her ground here. Instead, I would like to address an aspect of Scrum development that seems unique to writers: serving on multiple teams at once.

Ideally, the way Scrum works is that everyone on a team is a 100% dedicated resource. While developers and QA analysts might have some other small tasks to do while working in Scrum, their primary focus is the team. However, a technical writer might be split between two or more teams, sometimes as many as four or five. When that happens, keep the following in mind.

1. Let it be Known
Your Scrum master has an expectation that all the people on his team are there to work on his team 90% or more of the time until the close of the last sprint. If you’re on multiple teams, you can’t do that. Let your Scrum master know this at the team kickoff. It’s important he knows this.

2. Pick Your Meetings
Scrum is a meeting-intensive development method. Scrum prioritizes its backlog into “must haves” and “nice to haves.” In a pinch, you can apply the same to meetings. Every team has the following meetings:

    • Daily Standup – 15 minutes in which everyone says what they did yesterday and what they plan to do today.
    • Story pointing – 2-4 hours in which the product owner explains the stories (features) that the team will be addressing, and after a brief discussion the team assesses its work effort. Occurs at the beginning of the sprint, and pops up again when non-assessed stories are considered later in the process.
    • Sprint Planning – 1-2 hours in which the team determines which stories they will address in the coming sprint. Occurs every two weeks at the beginning of a sprint.
    • Retrospective – 30 -60 minutes in which the team goes over what went right and what went wrong and how processes can be shored up to make the team better. Occurs every two weeks at the end of a sprint.
    • Demo – 30-60 minutes in which the team presents the work it completed in the last sprint to stakeholders. There is often an internal demo first, followed by one for customers.

That’s quite a list, but it’s manageable, and a lot of these only happen bi-weekly, so it’s a little hiccup in the work schedule and then back to it. . .  until you double it, or triple it, or more. At that point you will spend all of your time in meetings and none of your time actually writing anything. If you’re going to have any time to work, you may have to skip some meetings. But which ones?

Story pointing meetings are a must. Of all the meetings, this is close to the top of importance. Remember, Scrum uses no specs. Since everyone (except you) is only working on this team’s work and in constant contact with one another, there is little written material for these features. That’s what you’re there for. So, the best way to get a handle on what the features are and what they do is in the story-pointing meetings.

The other essential component as far as meetings go, is the standup. I’ll admit that I work through most of mine; when developers start talking about the particulars of code they’re not having a discussion I need to be a part of. However, by being present at the standups you establish yourself as a member of the team. This is vital for building your relationship with everyone else and putting the idea in everyone’s mind that yes, there is a writer here, and yes, we need to tell him when we change something. And things will change; that’s why it’s called agile.

As for the rest of the meetings, it’s always better to go if you can, but you’ve got documentation to produce, and that takes time too. You have a responsibility to your teams to complete the doc tasks for each story. Sometimes that means you can’t attend every meeting. This is part of the discussion to have with your Scrum master when you explain you’re not an exclusive asset.

3. Focus and Float
Did you know that every time you receive an email it costs you 3 seconds? That’s assuming you don’t open and read it. From the time you see the notification that you have new mail, it takes 3 seconds to reorient your brain back to the task at hand.

The moral of this story is that to be truly effective, you need to focus and shut other things out. No, I’m not telling you to kill your IM channel and close Outlook. But I am suggesting to you that doing one story for one team and then one story for another is slower than taking a chunk of related stories for one team and working on only them for the day, or even the week, and leaving the other teams’ tasks for another time.

Yes, this means that you’ll be going to most your standups and saying: “I have nothing to report today.” That’s fine. Do that.

Understand this might also mean that a sprint may close without your doc tasks complete. How the team handles this logistically depends on the Scrum master. Most of the ones I’ve worked with will pull those stories into the next sprint with a “doc only” tag on it, meaning everything else is done.

Scrum purists might be gnashing their teeth at this, but if you’re willing to give it this little bit of flexibility and break from the ideal of the process (because really, if this were implemented ideally, you wouldn’t be on more than one team), I can promise you this works. While all of my teams regularly carry doc only stories from sprint to sprint, I also always finish ahead of development before the final sprint.

4. Educate Your Scrum Master
When I first started writing for Scrum teams, the Scrum masters would create the same array for each story: a programming task, a QA task, and a doc task. However, not all stories require a doc task. Speak up in the sprint planning meetings and let everyone know what does and doesn’t have to receive documentation so that your workload is accurately reflected in your team’s tracking tool. If you have to miss a sprint planning meeting and you find a story with a doc task that isn’t needed, bring it up with your Scrum master and explain why. Eventually they’ll learn, or at least default to the behavior of asking you first.

Serving on multiple Scrum teams takes some juggling, but it’s certainly manageable. In fact, I’ve come to prefer serving on two at the same time. However, when doing this it’s important to understand that you’re not in the same position as the rest of your teammates, and so you need a different set of rules to be effective.

Posted by Cliff Horowitz, Prophet 21 Content Team Lead, Epicor University

Implementing Consignment Inventory (Part 2 of 3)

In the previous blog post, we covered the definition, initial setup and advantages of managing consignment inventory using Epicor ERP v9 or v10.

Below are the steps that must be done to implement a new consignment customer with a new consignment part, assuming that you already have a consignment plant (in v9) or site (in v10) set up in the system.

  1. New consignment agreement is placed by the customer
    • Create a “Consignment Warehouse” for this new customer (one time for each customer).
    • Define minimum stocking levels in the consignment plant/site; i.e., if your contract says you are to always have 100 on hand, then set 100 as the minimum on hand for the consignment plant/site.
    • Define minimum stocking level at the manufacturer’s local plant. This would be any inventory that you want to keep on hand to fulfill any rush requirements. Typically, this is less than or equal to the minimum consignment level above.
    • In the consignment plant/site, specify that this item is a “Transfer” item, and that the “Supply Plant/Site” is your main manufacturing plant. Also specify the transfer lead time (the number of days that the item will be in transit).
    • Create the MRP forecast for this customer part in the consignment plant (i.e., you are forecasting that the inventory will be consumed from consignment, not from your local stores).
    • Note: at this point, you do not have to have any firm Sales order entered… MRP Forecasting + minimum on-hand will drive the first fulfillment of consignment inventory.
  2. Run MRP
    • MRP will see that you are currently below the minimum in the consignment plant, and will generate suggested transfer order requirements from the manufacturer’s plant to consignment.
    • MRP will then add these requirements to the minimum on hand specified in the manufacturer’s plant, and will generate “unfirm jobs” to fill these demands (even without a firm sales order).
  3. Firm Job, and Make Product
    • This is a normal job in your local plant.
    • When complete, the product is received to stock.
    • Once in stock, it will show on the suggested transfer order shipments.
  4. Ship Transfer Order from the manufacturer’s plant
    • Transfer orders generate Transfer Order Packslips. These packslips show the address of the demand (the consignment plant). It is your paperwork that goes to the customer.
    • Note that this is not a customer shipment…it is a transfer, because you are not transferring ownership, only moving inventory locations.
  5. Receive Transfer Order into Consignment
    • This is done once you receive confirmation from the customer that they have received the shipment.
    • This function actually takes the inventory out of “In transit” and puts it into the consignment plant.
  6. Consumption of Consignment Inventory
    • In most cases, your customers give a report showing what items were consumed. When this happens, an order needs to be entered, shipped and invoiced.
    • There are several ways that this can be done, but easiest is to create a new “counter sale” sales order. Counter sales allow for an order to be entered, “shipped” and immediately invoiced without all the extra processing.
    • When you create the counter sales order, you tell the system that you are selling it from the “consignment warehouse” location. This then automatically reduces the quantity on hand in consignment.
    • If there are a large number of parts consumed each day, then this could be automated with a Service Connect process to create and ship the orders. Alternately, an Excel spreadsheet could be copied and pasted into the counter sale section on the sales order.
  7. Replenishing consignment locations (basically, Go to Step 2 above)
    • If the customer’s consumption above did not reduce inventory below the “minimum” on hand in the consignment plant, then nothing will happen.
    • But, if it does reduce the on hand below minimum, then when MRP has its nightly run (see step 2 above), it will create another transfer order suggestion to move more inventory from your main stock to consignment.

Consignment Summary
While there are “urban legends” that Epicor ERP v9 and v10 cannot do consignment inventory because there is not a consignment module, this is not true, and as shown above, the actual steps are not difficult. In fact, once set up, the system will self-fulfill as the customer consumes the inventory. The manufacturer may need some help from an Epicor consultant in setting this up the first time, but once the model is complete, it can be easily replicated.

In the last part of this series, we will discuss how to verify the quantities and finish the contract for consignment inventory.

Posted by Tim Shoemaker, Senior Principal Consultant, Epicor Professional Services

Epicor Eagle Hosting Named Winner in 2014 Network Products Guide Awards Program
The 9th Annual 2014 Hot Companies and Best Products Awards program honored companies from all over the world in San Francisco on June 23, 2014 during the 9th annual awards dinner and presentations. Network Products Guide, the industry’s leading technology research and advisory guide selected Epicor as a Silver winner in the category of Cloud Computing/SaaS.
 
“We are proud to receive the Network Products Guide award for the fourth consecutive year,” said Mark Fair, vice president, customer services and support, retail distribution solutions for Epicor. “The Epicor Eagle Hosting solution was designed to help small to medium-sized retailers manage their IT infrastructure without the hassle of maintaining a server on premise.”
 
The annual Hot Companies and Best Products recognition program encompasses the world’s best in organizational performance, products and services, executives and management teams, successful deployments, product management and engineering, support and customer satisfaction, and public relations in every area of information technology.
 
Epicor Eagle Hosting is a comprehensive solution for new and existing Epicor customers that delivers the robust functionality of Epicor Eagle software in a hosted environment—supporting the small to midsized retail growth strategy. The solution offers end-to-end architecture, and includes protection from viruses, spyware, and hackers via Epicor Watchdog ISS Internet security service and Kaspersky anti-virus engine with SonicWALL enforced anti-virus and anti-spyware software, support and maintenance, automatic updates and upgrades, as well as all proprietary information.
 
To learn more about Epicor Eagle Hosting, please email eagle@epicor.com.
 
Posted by Epicor Social Media Team
Strategies for Planning and Scheduling in Food Manufacturing

The food industry has changed dramatically since the millennial turn. Consumers are more demanding, driving up expectations across a range of factors, including availability, price, quality, freshness, and service. Retailers are more demanding as well, expecting replenishment systems that allow them to meet volatile demand while keeping costs low. The regulatory environment has pushed tracking and traceability to the fore. Pressure on pricing is constant as well, fueled by increasing competition, and the business is ever more promotion-driven. Add to this shrinking product lifecycles and the proliferation of private labels.

In this daunting environment, small and mid-sized food manufacturers face a host of challenges, including:

  • Developing new products. In markets with an unquenchable thirst for the new, there are ever-more products and SKUs. This had led to a growing number of suppliers. Often products that are here today are gone tomorrow.
  • Customer retention. Quality is now a universal expectation, along with competitive pricing. Service demands are higher than ever before, with excellent service really being a component of quality. To meet retailers’ demands, controlling costs while meeting schedules is critical.
  • Improved process efficiency. To compete, food manufacturers have had to drive up productivity and efficiency. Supply chain integration is key to achieve this goal, along with implementation of Lean manufacturing methods. The need to improve and manage yield is constant.
  • Schedule compliance. With shortened time-to-delivery, shelf life management issues, and increasingly schedule variability, schedule compliance is a significant challenge.
  • Regulatory compliance. Compliance demands are an increasing concern as government regulations (e.g., safety, environmental) become increasingly strict and complex.
  • Market volatility. Having the ability to respond to uncertain market demand is vital, particularly as materials and energy costs rise.

From a planning and scheduling perspective, these challenges pose a litany of operational requirements to food manufacturers. Manufacturers must:

  • Execute dynamic scheduling for normal and special demand variation.
  • Support product (and especially new product) SOPs, recipes, operator instruction, and compliance.
  • Ensure schedule changes are made to accommodate contract variation.
  • Be capable of seasonal planning within forecasts.
  • Have necessary visibility to ensure efficient operation while assuring compliance.
  • Have forecasts and schedules that enable change for special and promotional products.

While this is a formidable list, successful food manufacturers are meeting these demands with a number of effective strategies:

  • Simplify forecasting, planning, and transactions.
  • Implement dynamic daily scheduling and planning systems for faster and more effective responsiveness to change.
  • Enable paperless production and control with built-in compliance to minimize risk.
  • Build in real-time visibility across the enterprise for alerts and analysis.
  • Establish closed-loop control between the back office and production floor.

Enabling technologies have provided the necessary functionality to support these strategies, including dynamic planning and scheduling tools, what-if analytics, real-time visibility, agility for seasonality, capacity, and maintenance management, and automation of process control. Among the benefits being realized by adopting these strategies and the tools to implement them: better decision making, stronger internal and external connections, more reliable delivery on shorter production and supply schedules, greater business efficiency, and significant cost savings.

Posted by Tom Muth Senior Manager, Product Marketing, Epicor

The Nexus of Forces Works Its Way Into the Enterprise

According to technology research firm Gartner, "Four independent forces—social, mobile, cloud and information—have converged as a result of human behavior, creating a technology-immersed environment. The Nexus of Forces (NOF) is transforming the way people and businesses relate to technology. It also leads to upheaval and change, which bring opportunities for business strategists to transform business processes and industries based on a renewed consumer focus.”

Business transformation is about developing new capabilities and when necessary, moving away from business models that are no longer competitive is the goal. The capability to transform when needed—or when better business outcomes can be achieved—is essential for survival in today’s dynamic and rapidly evolving economy. To enable this, organizations must align strategy decisions and business systems to help drive execution and support sustained long-term, continuous transformation.

So, how can NOF impact your business? View this Gartner report that presents key findings, such as:

  • Demand for IT solutions that support NOF scenarios is increasing.
  • The NOF is being embraced both strategically and tactically by most industries, whether they have "customers" or not.
  • However, the most progressive NOF solutions are those that involve customer engagement.

Gartner, “The Nexus of Forces Works Its Way Into the Enterprise,” Chris Howard, Daryl C. Plummer September 8, 2013

Posted by Epicor Social Media Team

Food and Beverage Manufacturers Drive Down Waste

In a post on thinkeatsave.org, waste reduction has been identified as the number one trend in food and beverage for 2014:

For some time now manufacturers' sustainability efforts have been zeroed in on, with a more recent shift in focus being to reduce food lost or waste, wherever possible. Food loss during production and food waste at the retailer and consumer end of the food-supply chain will be heavily scrutinized. Ingredients derived from the waste stream will also hold enormous potential.

Campbell’s Culinary TrendScape also cites food waste awareness as a top trend for the year.

These pronouncements come in the wake of the food industry’s first-ever analysis of food waste data collected directly from food manufacturers, retailers and wholesalers. Released in June of last year, the study was conducted by consulting firm BSR and commissioned by the Food Waste Reduction Alliance (FWRA), a cross-sector industry initiative led by the Grocery Manufacturers Association (GMA), the Food Marketing Institute (FMI), and the National Restaurant Association (NRA). Among the study’s findings, which are expected to accelerate industry food waste reduction efforts:

  • The food waste profiles of the food manufacturing sector and the grocery retail/wholesale sector differ significantly, which reflects their different operating environments. Extrapolated to the entire United States, in 2011:
    • The manufacturing sector generated a larger volume of food waste (44.3 billion pounds), but the large majority (94.6 percent) was diverted from landfills to higher uses, such as donation and recycling.
    • The retail and wholesale sectors generated less food waste (3.8 billion pounds), but they diverted a smaller proportion (55.6 percent) to higher uses.
  • Despite significant differences in the total amount of food waste the sectors generate, they donated and disposed of similar amounts:
    • Amount of food waste disposed:
      • Manufacturing: 2.4 billion pounds
      • Retail and wholesale: 1.7 billion pounds
    • Amount of food donated:
      • Manufacturing: 700 million pounds
      • Retail and wholesale: 670 million pounds
  • In total, 4.1 billion pounds of food waste was disposed in 2011 in landfills or incinerators. This represents only 8.5 percent of the 48.1 billion pounds of food waste generated collectively across the food manufacturing, retail, and wholesale sectors.
  • Based on the survey results, companies have opportunities to continue to reduce the amount of food waste they generate within the supply chain, as well as to identify options for directing it toward higher uses, as outlined in the EPA’s Food Waste Recovery Hierarchy.
    • Food manufacturers have an opportunity to continue to reduce the amount of food waste they generate and to move up the food waste hierarchy to increase the percentage they donate.
    • Food retailers and wholesalers have an opportunity to divert more waste from landfills to higher uses, while continuing to focus on reducing the amount of food waste they generate.

To support this effort, an article on Food Drink Europe lists six ways food manufacturers can help consumers drive down waste:

  • Extend shelf life through packaging and processing innovation.
  • Provide clear date labels.
  • Provide clear storage, freezing, defrosting and preparation instructions.
  • Make dispensing food easier.
  • Provide a variety of portion sizes.
  • Inform consumers about packaging and labeling innovations that help prevent food spoilage.

The BSR report notes eight “farm to fork” actions taking place in the private sector (of which manufacturers are a key component) that are facilitating waste reduction efforts:

 
Source: BSR
 
Enabling technologies that can affect and reduce waste through the supply chain inlcude dynamic planning and scheduling tools, what-if analytics, real-time visibility, agility for seasonality, capacity, and maintenance management, and automation of process control. Among the benefits being realized by adopting these strategies and the tools to implement them: better decision making, ,insight into waste before occurance, stronger internal and external connections, more reliable delivery on shorter production and supply schedules, greater business efficiency, and significant cost savings.
 
Posted by Tom Muth Senior Manager, Product Marketing, Epicor
Introduction to Consignment Inventory (Part 1 of 3)
Definition
Consignment inventory is inventory that is:
  1. Owned by the manufacturer
  2. Shipped to the customer, but not invoiced until—
  3. Consumption of the inventory is advised by the customer—at which time, it is invoiced.

Consignment and Epicor ERP v9 & v10
Epicor ERP (v9 & v10) does not have a “consignment module” per se, but it does support consignment very well, with well-defined procedures. For example, the method described below has been used by multiple companies in the aerospace industry.

There are several deviations from this model that can cause it to malfunction.  We conclude this post by highlighting those pitfalls so they are not pursued.

Consignment with MRP-Multi-Site Advantages
By setting up consignment in the manner described here, there are many advantages and processes that can be managed within Epicor ERP v9 or v10. These include:

  1. Forecasting of consignment usage by location
  2. Management of minimum stocking levels by consignment location
  3. Management of minimum stocking levels at manufacturer’s location to fill consignment emergencies
  4. Automatic replenishment of minimum levels at the consignment location
  5. Ability to cycle count/physically inventory a specific customer’s inventory
  6. Easy shipment of “Transfer Orders” to move inventory to consignment location
  7. Material requirements for future consignment deliveries are still calculated based on the forecast that is entered into consignment

The Required Initial Setup
To process consignment inventory, there are several modules required, as well as some specific setups.

  1. Must have Material Requirements Planning (MRP)
  2. Must have Multi-site
  3. Must create a new “Plant” (in v9) or “Site” (in v10) to hold “Consignment Inventory”

Optional Setup Items
There are some decisions that are optional, depending on the customers, and the products that are shipping to those customers:

  1. You can set up either one consignment plant/site for the entire company, or one consignment plant/site for each Customer Ship-To. The reason is:
    • If you ship common assemblies to multiple consignment sites, then it is easier to track requirements if there is a separate plant for each location.
    • But if there are no common parts between customers, then creating one plant (or site), with one warehouse for each customer, is sufficient.
  2. You can alternatively create separate cost tables for each plant. This allows the plant to have its own average cost. However, many companies do not want this to happen, and tie the costs of the consignment plant to the main plant.

Pitfalls of Skipping Steps or Incorrect Setup
As stated above, there are several pitfalls that are potential causes for failure and should be avoided:

  1. Some think that these consignment locations are supposed to be “non-net inventory”… this is not true. They must be considered “nettable” inventory in order for this to work.
  2. Ignoring forecasts, or putting forecasts in the wrong location.
    • Forecasts should always be entered, and they should be entered into the consignment plant.
    • Forecasts are what drives the future purchases (and even manufactured job orders, if the lead time on purchasing/manufacturing is longer).
  3. Forgetting transfer lead time.
  4. Entering sales orders against the wrong plant. All consignment usage must be “shipped” (consumed) from the consignment plant.

In the next post, we will discuss the consignment process in action.

Posted by Tim Shoemaker, Senior Principal Consultant, Epicor Professional Services
Invitation to Help Shape Epicor University Content

Epicor University is starting customer focus groups on content. Meetings will be held every other month in a conference call/shared desktop format. Proposed topics will include:

  • Tours and functionality demonstrations of newly-released content.
  • Sharing of prototypes of content in development.
  • Discussions of desired features.
  • Strategies for aligning shipping content to your organization’s needs.

We hope that by increasing communication on content and training challenges we all face, we at Epicor University can create better content and improved content vehicles. We strive to deliver content in the way you want to consume it. We would love to find out:

  • How do you train new Epicor users?
  • How does Epicor training fit in with other systems/process training?
  • What are the content areas most consulted in regards to Epicor?
  • If you were to design your organization’s ultimate “user guide” to systems and processing related to Epicor, what would it look like? HTML? Videos? Diagrams? Clickable diagrams? Combinations of all those items?

If these topics sound like areas of discussion you would like to pursue, please send us an email at documentation@epicor.com, and ask to be included in one of our Epicor University Customer Focus Groups (CFGs). We have several groups, so also include which Epicor products you are using so that we may invite you to the appropriate group.

Posted by Charles Lloyd, WW Director Epicor University

The Manifold Productivity of ERP

A post on TechAdvisory.org points to the advantages of enterprise resource planning (ERP) for small and mid-sized businesses considering the technology for the first time; however, its list of how ERP supports today’s business requirements in terms or productivity and profitability extends to enterprises of all sizes. They cite 10 top requirements for today’s businesses and how ERP helps meet them:

  1. The need to make decisions fast. ERP delivers reports and dashboards that combine data from every department to managers no matter where they are.
  2. The need for highly productive employees. ERP automates most of the manual processes that takes workers away from more valuable labor.
  3. The need for great customer service. It’s never been easier for customers to find a new supplier. ERP connects information across the organization so that you can answer your customer’s questions quickly and accurately, every time.
  4. The need to support multiple distribution channels. To expand market reach, Internet, channel, and direct distribution need to be supported. ERP connects all systems across supply networks to improve market performance in all market channels.
  5. The need to accurately match costs with income sources. When you execute work, you need to know whether you are really making a profit on it. ERP tracks all costs related to projects or jobs to ensure profitable engagements.
  6. The need to support remote employees. Employees need to be productive wherever their work is. ERP systems allow remote workers to access and enter information where they are, when they want to—increasingly on the mobile devices they choose to use.
  7. The need to manage industry-specific requirements. Every business is unique; business systems generally aren’t. With ERP, you can build workflows and reports that specifically address the specialized requirements of your industry.
  8. The need to simplify compliance. Meeting the reporting requirements of increasingly stringent regulations can take a huge manual effort. Instead of spending weeks and months on manual documentation, ERP’s automated functionality speeds and simplifies compliance while allowing your human capital to focus on more productive and value-added tasks.
  9. The need to support global commerce. Increasingly, business crosses international markets. ERP eases complicated currency translation and supports staffing overseas by providing accurate information without undue latency (essential for efficient operation of dispersed business networks).
  10. The need to attract young workers. The aging workforce places a premium on attracting young talent. A generation that has only known the digital age has little patience for tasks they know can be simplified with technology; to this group, the technological prowess of ERP not only makes intuitive sense, it reinforces their belief in the company’s commitment to stay current with technology—something they see as highly important.

When ERP matches your business, the best practices that are part of the system can be used to automate the flow of information in the business. The key is finding an ERP that is a good fit—the general flow of the system needs to match your business practices. When this happens, many good things follow, including greater productivity and higher profitability.

Posted by By Christine Hansen, Manager, Product Marketing

1 - 10Next




Distribution
ERP
HCM Blog RSS HCM
Manufacturing
Retail
Retail CRM
Technology
University



Network with Epicor customers, employees, industry experts, and more.
Facebook Facebook
Connect with your peers and discuss best practices.
Twitter Twitter
Tweet, re-tweet, and stay up-to-date on the latest happenings with Epicor.
LinkedIn LinkedIn
Connect with your peers and discuss best practices.


Epicor Twitter Feed


© Epicor Software Corporation Home |  Investors |  Partners |  Privacy
Terms of Use |  Privacy Policy Industries |  Solutions |  Products |  Company |  Customers |  Services |  Careers