Tag Archives: Using webERP

Manufacturing using webERP

This post is #4 in a series on using webERP. Search for “webERP” to find other posts in the series and please visit the demo on dalescott.net (login as “auditor” with password “guest”).

Features of using webERP for manufacturing include:

  • Efficiency. Items, Vendors, Work Orders, etc. are managed within one controlled system. Fix a problem once and it’s fixed everywhere.
  • Visibility. A visible, trusted, change management process and a chain of truth.
  • Scalable. Readily scales with users, items, vendors and orders, and adapts as your processes change over time.

In this tutorial, I will explore using webERP for manufacturing using the Swift Construction Company’s development of the Aircraft Wireless as an example.

Goals

The goal of this exercise will be to:

  • Manufacture a sub-assembly with auto-issued child (input) items.

Manufacturing Cycle

The general manufacturing cycle in webERP is:

  • Enter a Work Order to manufacture an item according to its bill of materials (BOM).
  • Receive the finished manufactured items (the output from the work order) into stock. Input items listed on the bill of materials to auto-issue input items will be transacted to the work order at this time.
  • Issue any additional input items used in in the manufacturing process to the work order).
  • Close the work order.

I will be manufacturing quantity 10 of item 20000001-00, a custom electrical coil. The assembly tree is shown below. I covered how to configure an item as Manufactured, and how to create a BOM, in the Product Lifecycle Management using webERP tutorial.

20000001-00,"IND,830UH,AIRCRAFT WIRELESS"
|-- 90000001-00,"WIRE,MAGNET,38AWG,POLY"
|-- 90000002-00,"MAG,FERRITE ROD,1/4IN X 4IN,MATL=61"
\-- 90000003-00,"TAPE,ELECTRICAL,3/4"",BLUE,VINYL"

The manual process that will be followed is:

  • Manufacturing scheduler creates work order and assigns to assembly technician.
  • Assembly technician prints work order and kits required input materials from stock room. The technician initials each input item quantity as removed from stock.
  • Technician completes finished coils.
  • Technician initials work order as complete and returns to scheduler.
  • Scheduler receives the output items into the work order, which also causes the input items to be transferred from stock.
  • Scheduler closes work order.

TODO add swim-lane diagram(s).

TODO describe the accompanying parallel paperwork process.

Setup

If you have been following my previous tutorials,  there should be no further setup required. However, if not, it may be helpful tog review building a BOM in Product Lifecycle Management using webERP, and purchasing items in Purchasing Using webERP.

Create Work Order

A work order essentially converts the list of raw material required to manufacture an item (the Bill of Materials, or BOM) into one or more outputs. The work order can be printed and used to kit the necessary raw materials, and also used as a traveller for the Work in Process (WIP).

  • Create a new work order.
  • Enter optional Reference and Remark. TODO explain why
  • Search & select output item 20000001-00. Update.
  • Enter Qty 10 and comment for output 20000001-00. Update.

The work order can be printed and signed as record of kitting, and also as a record of additional input items to enter before closing the work order. A printed copy of the work order often travels with the WIP as identification (e.g. a traveler for a tote of material). Labels can also be printed for later attaching to the manufactured items. 

Main > Manufacturing > Transactions > Work Order Entry

If you search for work orders you will see that the new work work is in the system.

The  work order status shows demand for the raw materials needed to manufacture the inductor, which indicates they have not been issued.

You will also see that there is qty 10 of 20000001-00 on order from its item screen.

Receive Output Goods

When the output items have been manufactured they are received against the work order. For simplicity I will assume the manufacturing process was flawless, with no waste and all the manufactured items meet spec (see the manufacturing and test procedure filed in the Knowledge Base).  

Items listed on the BOM as auto-issue will issue to the work order at this time.

Process Manufactured Items Received

Close Work Order

Close the work order after all raw material has been issued to the work order and all manufactured items have been received against the work order. Review the work order costing,

Main > Manufacturing > Transactions > Select a Work Order > Select > Costing

and close the work order.

Summary

This completes the overview of manufacturing using webERP. 

Product Lifecycle Management (PLM) using webERP

This post is #2 in a series on using webERP, and is a work-in-progress. Search for “webERP” to find other posts in the series and please visit the demo on dalescott.net (login as “auditor” with password “guest”).

Product lifecycle management (PLM) is the act of consciously managing a product from concept through design, into manufacturing and sales, supporting on-going production and sales through sustaining engineering, and finally winding down. PLM integrates people, data, processes and business systems, and provides a trustable and transparent product information backbone for operations.

Features of using WebERP for PLM include:

  • Integrated data. Projects, people, hours, other expenses, purchase orders, production builds, bills of materials, etc., are conveniently managed in one controlled system.
  • A visible, trusted, change management process providing chain of truth.
  • Scales with number of users, items and complexity of item trees.

I will explore webERP’s PLM features using the Swift Construction Company’s development of the Aircraft Wireless as an example, following the SCC Product Management process

Goals

The goals of this exercise will be to:

  • Create child and parent items to model an assembly.
  • Define appropriate work centers.
  • Capture expected manufacturing labour.
  • Identify item vendor information for purchasing.
  • Identify item manufacturer information for purchasing through distribution.(manufacturer part number vs vendor part number).
  • Identify an appropriate change management or ECO process. COMING SOON 

Definitions

Here are some terms in the context I will be using them.

  • Revision Level. Each item has a unique revision level, indicating changes made to the item or its supporting documentation since it was initially defined. The revision level is changed following a well-defined sequence. 
  • Release. A release is the creation or update of a logical set of items and supporting documentation. This may be to publish information for review, to support processes such as purchasing or manufacturing, or to recognize a milestone in the development project.
  • ECO (Engineering Change Order). A well-defined process for making changes to a part or assembly, usually custom. 

Setup

Create Inventory Categories

The Swift Construction Company, like many engineering services and product companies, grew organizationally from a single-person engineering department to eventual separate mechanicals and electronics development teams. Knowing if a thing is a “mechanical thing”, or an “electronics, firmware, or basically anything but a mechanical thing” indicates which department is responsible for it.

As a result of the SCC’s organization structure, physical things are categorized as either either ELEC or MECH for raw materials and parts, or RADIOS for finished goods (currently the SCC’s only product line).  

Main > Setup > Inventory Setup > Inventory Categories Maintenance

ELEC Inventory Category

MECH Inventory Category

RADIOS Inventory Category

Create Units of Measure

An item’s Unit of Measure (UOM) specifies how the item is to be inventoried and consumed. webERP supports different purchase units, for example to purchase in US gallon jugs but inventory and consume in millilitres. 

A new unit of measure is typically created if needed when a new item is created, but using the SCC Aircraft Wireless development project documentation we can create all necessary units of measure now.

Main > Setup > Inventory Setup > Inventory Units of Measure

Create Vendors

A new vendor is typically created ad hoc, but using the SCC Aircraft Wireless development project documentation we can create each vendor now (vendors can also be imported from a CSV file). 

Main > Vendors > Add a New Vendor

Create Items

Create new items according to the SCC Aircraft Wireless development project. I will shjow details for creating sub-assembly 20000001-00 (a custom inductor), and the rest of the items and bills of materials will be similar.

20000001,"IND,830UH,AIRCRAFT WIRELESS"
|-- 90000001,"WIRE,MAGNET,38AWG,POLY"
|-- 90000002,"MAG,FERRITE ROD,1/4IN X 4IN,MATL=61"
\-- 90000003,"TAPE,ELECTRICAL,3/4"",BLUE,VINYL"

90000001-00 Magnet Wire

The unit of measure for the wire will be centimetres, meaning the wire will be inventoried and consumed by the centimeter. However, it will be purchased by the spool, which is the vendor unit of measure (the datasheet for the wire indicates a spool has 19,300 feet).

The consumption unit of measure will generally be the most relevant for any transaction other than purchasing or inventory control. When purchasing, the unit of measure will generally be determined by the vendor, and webERP supports a separate purchase unit when creating a purchase order. This means in an inventory audit that it will be necessary to convert from the counted number of full spools, add fractions of a spool for any partial spools, and convert to centimeters. However, the conversion factor can be found in the item master purchasing data, and the math is not too laborious.  

Items > Create New Item

Enter Purchasing Information

Items > Item Maintenance > Maintain Purchasing Data

Enter Standard Cost

The standard cost for cm UOM is C$0.00026308 per cm (C$154.83/spool x [ 1 / [ 19300ft x 30.48cm/ft ] ] ).

Items > Item Maintenance > Maintain Standard Cost

Upload Documentation

Upload the manufacturers’ datasheet to the Knowledge Base.

Items > Item Inquiries > Wiki Product Knowledge Base

I’m using the same template for each page. It is essentially a list of categories of typical documentation. It’s a judgement call at the time the part is created what is required though.

90000002-00 Ferrite Rod

Items > Create New Item

Enter Purchasing Information

Items > Item Maintenance > Maintain Purchasing Data

Enter Standard Cost

Items > Item Maintenance > Maintain Standard Cost

Upload Documentation

Upload the catalogue page, datasheet and application note to the Knowledge Base.

Items > Item Inquiries > Wiki Product Knowledge Base

90000003-00 Tape

Items > Create New Item

Enter Purchasing Information

Items > Item Maintenance > Maintain Purchasing Data

Enter Standard Cost

Items > Item Maintenance > Maintain Standard Cost

Upload Documentation

Upload the product datasheet and MSDS to the Knowledge Base.

Items > Item Inquiries > Wiki Product Knowledge Base

20000001-00 Inductor

Item 20000001-00 is a custom inductor that will be manufactured in-house using the parts listed in a Bill of Materials (BOM). An item must be explicitly specified as Manufactured in the Item Properties for a creation of an associated BOM to be allowed.

Items > Create New Item

Enter Standard Cost

Set the standard cost to be the total calculated cost including labor and any fixed overhead costs.

Items > Item Maintenance > Maintain Standard Cost

Enter Standard Price

Items which may be sold require pricing. It is expected field technicians may wish to purchase 20000001-00 for maintenance repair.

Items > Item Maintenance > Maintain Pricing

Create Bill of Materials

The raw material required to manufacture one item 20000001-00 are specified by creating a Bill-of-Materials, including quantities. The raw materials are also referred to as child items of the parent 20000001-00, and are set to auto-issue, which will simplify creating a manufacturing work order later.

Main > Manufacturing > Maintenance > Bills Of Material

Reporting

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Managing Change

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. 

Summary

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Installing WebERP

This post is the first in a series on using webERP. Search for “webERP” to find other posts in the series and please visit the demo on dalescott.net (login as “auditor” with password “guest”).

webERP is a mature open-source ERP system providing best practise, multi-user business administration and accounting tools over the web. webERP can be used with a wiki CMS to provide an integrated Knowledge Base. I will be installing MediaWiki, one of the supported wiki applications.

Goals

The goals of this exercise will be to:

  • Install webERP software.
  • Install MediaWiki software.
  • Configure webERP and MediaWiki for use.

Install Applications

I will be hosting webERP and MediaWiki on FreeBSD, a unix-like operating system (GNU/Linux is another popular unix-type operating system). The server has been previously configured with Apache 2.4 for the http (web) server and MariaDB 10.0 (compatible with MySQL) for the database server.

webERP

Copy the webERP software files to the server and configure the Apache web server.

  • Extract distribution to /usr/local/www/
  • Rename extracted directory webERP/ to weberp-4.13.1
  • Create soft link “weberp” to weberp-x.y.z
  • Create Apache virtual server e.g. http://weberp.dalescott.net

Access http://weberp.dalescott.net with a web browser to run the installer.

  • Language: US
  • Db user and password: root (only for install, future access will be changed to a dedicated user after installation)
  • Company name: e.g. Swift Construction Company
  • Install demo data: YES
  • User “admin” email: e.g. dale@dalescott.net
  • admin user password: (keep this safe)

After the installer has completed, change the database access user to a new database user with privileges to webERP databases only.

  • Create a new database user “weberp” with all privileges to the weberp and weberpdemo databases.
  • Edit the webERP configuration file weberp/config.php and change the database access user and password to the new dedicated user.

MediaWiki

Copy the MediaWiki software files to the server and configure the Apache web server.

  • Download a release archive.
  • Extract the distribution to /usr/local/www/ (which will create mediawiki-x.y.z/) 
  • Create a soft link “wiki” to mediawiki-x.y.z/
  • Create an Apache virtual server http://wiki.dalescott.net

Access http://wiki.dalescott.net/mw-config/index.php with a web browser to run the installer.

  • Name of wiki: webERP
  • User rights profile: Authorized editors only (public viewing is allowed)
  • Enable file uploads

Configure Applications

webERP

Log into webERP using the admin user credentials entered into the auto-installer and create new named user e.g. dalescott. The new user will be used for all subsequent work to identify the administration user specifically for audit purposes. 

  • email: e.g. dale@dalescott
  • system administrator privileges

The original admin user (created by the auto-installer) cannot be deleted due to a now existing audit trail.

Location

I will create a new location “Shopton” for the SCC headquarters.

Main > Setup > Inventory Setup > Inventory Locations Maintenance

Note: Delivery Address 1 must be given a value, otherwise a “missing delivery address” error will occur when later attempting to create a purchase order.

After creating the new location, change the location of the administration user to the new location (and of any other users). 

Currencies

I will create a new CAD currency as some items will need to be purchased in Canadian dollars. webERP will obtain currency exchange rates from either Google or the European Central Bank (Main > Setup > General > System Preferences).

Main > Setup > General Setup > Currencies Maintenance

“USD” is shown as the “Functional Currency” because United States is set as the SCC company currency in the Company Preferences.

Company Preferences

Operating practices for a specific company are configured in the Company Preferences screen (webERP supports multiple companies and the desired company is selected at login). 

Main > Setup > General > Company Preferences.

System Preferences

General system-wide behavior is configured in the System Preferences screen. I will quickly review some interesting parameters, and get into a bit more detail with a few specific parameters.

  • Date format: Y-m-d. I prefer ISO 8601 dates for clarity over familiarity (e.g. 2017-03-08 for March 8, 2017), which avoids the ambiguity of d/m/Y and m/d/Y.
  • Frequently Ordered Items: 0. I left this disabled but may experiment with it once the system has some orders entered.
  • Sales Order Allows Same Item Multiple Times: Yes. I will revisit this later, but at least initially I don’t want anything to block operation.
  • Languages to Maintain Translations for Item Descriptions: None. Don’t complicate things at least initially.
  • Picking note must be produced before an order can be delivered: No. I don’t want to complicate the process too soon.
  • Auto Update Exchange Rates Daily: Automatic. Source Exchange Rates From: Google. 
  • Create Debtor Codes Automatically: No. I want to use my own mnemonic codes, but set to Yes if you don’t care and would prefer to let the system assign a sequential integer.
  • Create Supplier Codes Automatically: No. I prefer to use my own mnemonic codes.
  • Country of operation: United States (used when calculating shipping costs).
  • Purchase Order Allows Same Item Multiple Times: Yes. I will revisit this later, but at least initially I don’t want anything to block operation.
  • Automatically authorise purchase orders if user has authority: Yes. I will disable this later so I can follow the approval process.
  • Financial year ends on: December (if only to avoid having to answer of why not calendar years).
  • Maximum Size in KB of uploaded images: 300. I left this at its default value, although some images and screenshots will likely require re-sizing before uploading.
  • Directory to store images: part_pics (directory already exists)
  • Directory to store reports: reports (directory already exists)
  • Wiki application: MediaWiki (I’m already familiar with MediaWiki), Wiki Path: http://wiki.dalescott.net/ 
  • Inventory Costing Method: Standard. webERP also supports weighted average, but Standard Costing behavior will be more obvious to start with.
  • Auto issue components: Yes. Automatically decrement items from stock according to the BOM for an Item when it is manufactured to reduce admin effort.
  • Prohibit Negative Stock: No. I’m pretty sure I will set this to Yes later, but prefer no blocking operations at least initially.
  • Log Severity Level: All, Path to log files: log. I want to see all possible log entries initially and can be reduced later (I also had to create the “log” directory and set ownership of the directory to the www:www, which is the Apache http server user on FreeBSD).
  • Controlled Items Defined At Work Order Entry: Yes. When set to yes, controlled items are defined at the time of the work order creation. Otherwise controlled items (serial numbers and batch/roll/lot references) are entered at the time the finished items are received against the work order
  • Auto Create Work Orders: Yes. Setting this parameter to Yes will ensure that when a sales order is placed if there is insufficient stock then a new work order is created at the default factory location
  • Default Factory Location: Shopton. This will be the default location for automatically created work orders.
  • Factory manager email: dale@dalescott.net, Purchasing manager email: dale@dalescott.net, Inventory manager email: dale@dalescott.net. I’m setting all email addresses to me for convenience so I see the traffic.
  • Using Smtp Mail: No. My server will route email from webERP out through my ISP’s mail server.

Main > Setup > System Preferences

Wiki Application

In particular, note the setting for “Wiki application”. When enabled by selecting a particular Wiki dialogue (MediaWiki, WackoWiki or DokuWiki), a link to the “Wiki Product Knowledge Base” will be shown in the Inquiries column of the main Items, Vendors and Customers screens (once an Item/Vendor/Customer has been selected).

You also need to set the root path to the wiki (that webERP will append to) in the system parameters screen. In my case, I needed a trailing “/” in the Wiki Path, but YMMV.

Database Maintenance

webERP can be configured to lock out users by setting Perform Database Maintenance at Logon to Allow SysAdmin Access Only. Only users with security profile “System Administrator” will be allowed to login or enter data when this is set, which is important when performing maintenance on the application code or database. A maintenance notice also appears on the login prompt when Allow SysAdmin Access Only is set.

Main > Setup > General > System Parameters

This parameter can also be used to periodically run the query “OPTIMIZE DATABASES” at set intervals. It is not clear how often this should be run, or even if there is a significant benefit. However, users will notice a slight delay during login when the it runs, it might have been a half-second with an almost empty Swift Construction Company database (on a older dual-core desktop PC with 4GB memory). If periodically running OPTIMIZE DATABASES is desired, you may consider creating an entry in the cron table to run the mysql command line interface, giving the query as a command argument.

MediaWiki

The webERP Knowledge Base, MediaWiki in my case, is a completely separate system from webERP, including separate users, user permissions, etc. webERP simply provides structured links into the Knowledge Base (with some variation depending on the wiki protocol selected in webERP Main > Setup > General > System Parameters > Wiki application).

I intentionally configured MediaWiki during install for public access, but required that a user be logged-in to create a new page, edit an existing page or upload a file. This allows anyone to see information, and in most cases get on with their job, without having to be concerned with logging into the Knowledge Base. For me, this is a nice balance of visibility and trust within a homogeneous organization. Users can also set their browsers to remember their login credentials and once set won’t be inconvenienced again (I wouldn’t necessarily recommend this when there are shared workstations, but then again many people use shared workstations and don’t control who the user is, it all depends….).

Upload File Types

I configured the permitted upload file types to include OpenOffice/LibreOffice files, dwg files and zip archives (see MediaWiki documentation).

$wgFileExtensions = array( 'png', 'gif', 'jpg', 'jpeg',
 'odt', 'ods', 'odp', 'odg',
 'txt', 'pdf', 'zip', 'dwg'
);

Site Logo

I also uploaded the SCC logo as a media file and edited LocalSettings.php to use new logo.

Summary

This completes basic webERP and MediaWiki installation and configuration.

Managing projects using WebERP

This post is #5 in a series on using webERP, and is a work in progressSearch for “webERP” to find other posts in the series and please visit the demo on dalescott.net (login as “auditor” with password “guest”).

In this tutorial, I will explore webERP’s project management capability using the Swift Construction Company’s development of the Aircraft Wireless as an example.

Features of using webERP for project management include:

  • Integrated data. Projects, people, hours, expenses, purchases, prototype manufacturing, etc. are managed conveniently in one system.
  • Visible and trusted.
  • Readily scales with users, projects and project complexity.
  • Can be used to save money and even generate revenue. For example, the Canadian SR&ED (Scientific Research and Experimental Development) tax incentive program generally requires detailed project information to support a claim.

Goals

The goals of this exercise will be to:

  • Demonstrate basic project management functionality possible using existing webERP functionality.
  • Determine if webERP is missing any features critical for project management, or which would significantly enhance its ability to be used for project management.

Definitions

Here are some terms in the context they will be used here.

  • Project: A temporary activity to achieve a specific goal. Projects have expenses, milestones, phases and tasks.  Labor, and other expenses, are consumed expended to complete tasks.
  • WBS: Work Breakdown Structure. An ordered tree of tasks and sub-tasks. WBS number: how an individual tasks is identified (e.g. “8.3.2” for a child-of-child task).
  • Gated development process. A water-fall-like product delivery process divided into major phases for clarity. E.g. Investigation (Concept), Definition (Requirements), Design (the real work, including prototyping), Verification (Beta-Test), Pilot (pre-launch process reviews), Production and Termination. A development project is often closed when it reaches Production, with subsequent work allocated to a general-purpose maintenance project.

Tracking Time

The most fundamental aspect of project management is recording the effort spent to achieve a goal, or complete a task. The ubiquitous Gantt chart has become synonymous with project management, but without knowing how much time has actually been spent, it is impossible to know if the plan is optimistic or conservative, and to actually manage the project.  

Many organizations use timesheets to record employee hours for payment, or in the case of salaried employees, to record vacations, sick leave and other time off for payroll and accounting purposes, and the time data may not even be assigned to a particular project, or task. However, if an organization uses timesheets and it undertakes projects, it should be clear there are advantages to having the data in one system, where it can also be available for project management.

I’m using the term Project Management here fairly loosely. It might be more precise to say time recording and reporting, but that’s just where it starts. As Quality people say, you can’t manage a process if you can’t measure it. The first step on the path to effective project management is to record specifically the projects that the organization has determined it will spend effort on, how effort is being spent, and to be able to report the effort spent by project, employee or task. For many organizations, doing just this will provide an enormous payback in understanding where effort is being consumed, and will focus the organization on what it has determined are its key goals.

Two Possible Strategies

webERP does not specifically support project management. However, it is possible to overlay project management tasks onto existing functionality.

  • Manufacturing Strategy. A project is modeled by an item tree. Each project has its own item number. Work orders are used to capture project labor and other costs. As many labor type items can be created as necessary. A labor type can be defined when a stock category is defined for a stock type, which allows for GL entries to recover labor (CR a P&L account and DR WIP) when labor is issued to (or consumed by)  a work order. Labor items can be included in a bill of materials at a particular work center, and work centers can be mapped to labor items. Having created a work order, you then issue materials and labor to it and receive finished goods from it. When all the materials and labor have been issued and the finished goods received from it the work order is closed and the stock of the (unsold) finished items are revalued as necessary.
  • Contract Strategy. A project is modeled by a contract. webERP contract functionality allows for entry of nominal items directly to a contract’s cost, and stock and labor can be issued to a contract work order. If necessary, multiple contracts can be used with each contract a different section of the project (e.g. prototype, software development…). Contracts can have dates associated with them, as well as inter-dependencies, and could be presented using a Gantt or PERT chart. Phil Daintree, founder of the webERP project, discusses this approach in the webERP wiki page Proposed Project Management Model.  

Manufacturing Strategy

The following must already have created:

  • Inventory category for project virtual items
  • Inventory category for labour virtual Items
  • A work centre
  • Customer type
  • Customer price list
  • Sales region

Setup

Create Virtual Inventory Categories

Virtual items have value and a desire to track and manage, but can’t physically sit on a shelf somewhere. Virtual inventory categories must be created to manage projects and the labor they consume.

PRJ Virtual Inventory Category

LABOR Virtual Inventory Category

Create a Work Center

A Work Center is a place where production activities are performed. Resources such as people and machines are associated with a work centre, and together they become the functional planning unit. A work centre must exist before a work order can be created for the work order to reference.

Main Menu -> Manufacturing Maintenance -> Work Centre.

Create a Default Customer Type

Main Menu -> Setup -> Receivables/Payables Setup -> Customer Types.

Create a Default Sales Type

Main Menu -> Setup -> Receivables/Payables Setup -> Sales Types.

Create a Default Sales Territory (Area)

Main Menu -> Setup -> Receivables/Payables Setup -> Sales Areas.

A default price list can also be defined, but is not required unless the customer price list does not provide pricing for some item. (Main > General Setup > System Parameters.)

Create project and labor items

Create a Manufactured item to represent a project (it must be of type Manufactured so that a manufacturing work order can be created),

weberp-create-project-item-manufactured

and a Labour item of type Service/Labour to represent the project labor.

weberp-create-labour-item

Note that the new items will appear in an item search.

weberp-project-labour-items

Create a project BOM

Create a manufacturing BOM for the project item so that a manufacturing work order may be created, although no child items will be included on the BOM.

weberp-create-project-item-bom

Create a work order to capture costs

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Issue labor to the work order

Having created a work order, you then issue materials and labor to it and receive finished goods from it. When all the materials and labor have been issued and the finished goods received from it the work order is closed and the stock of the (unsold) finished items are revalued as necessary.

Report on the project

A few standard reports will provide the basic information to gain a project overview.to understand general project status.

  • Project Summary (list of all projects with consumed labour)
  • Project Labour over Time
  • Project Labour by Activity
  • Project Labour by Employee

TODO replace screenshots with webERP examples.

Project Labour over Time

Project Labour per Activity

Project Labour per Employee

Close the work order

The work order is closed when the project is deemed complete. Don’t leave projects open indeterminately, this will reduce clarity within the organization by taking attention away from the really important projects, and adds clutter to the reporting. It’s better for the organization to decisively kill a non-viable project than it is to starve it to death from lack of resources, and a new project can always be opened if appropriate.

Contract Strategy

Setup

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Create a project contract

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Create a labor item

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Create the project contract work order

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Issue labor to the project work order

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Report on the project

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Close the project

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Summary

Strategy Comparison

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Areas for improvement

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.