Ship Work Breakdown Structure: Fill & Download for Free

An ERP system covers the following common functional areas. In numerous ERP frameworks these are assembled and gathered as Enterprise Resource Management solution modules:Financial accounting: General record, fixed asset, payables including vouchering, coordinating and payment, receivables money application and collections, cash management, financial solidificationManagement accounting: Budgeting, costing, cost administration, activity based costingHR: Recruiting, training, rostering, finance, advantages, 401K, diversity management, retirement, detachmentManufacturing: Engineering, bill of materials, work orders, booking, capacity, workflow management, quality control, producing process, manufacturing projects, producing stream, item life cycle administrationOrder Processing: Order to money, request passage, credit checking, estimating, accessible to guarantee, stock, shipping, deals examination and reporting, deals dispatching.Supply chain management: Supply chain arranging, supplier planning, item configurator, request to money, buying, stock, claim handling, warehousing (getting, putaway, picking and pressing).Project management: Project arranging, asset arranging, venture costing, work breakdown structure, charging, time and cost, execution units, movement administration.Client relationship administration: Sales and showcasing, commissions, administration, client contact, call focus support — CRM frameworks are not generally considered some portion of ERP frameworks but instead Business Support frameworks (BSS).Data services : Various "self–service" interfaces for clients, suppliers and/or representatives.

Functional areas of ERPAn ERP system covers the following common functional areas. In many ERP systems these are called and grouped together as ERP modules:Financial accounting: General ledger, fixed asset, payables including vouchering, matching and payment, receivables cash application and collections, cash management, financial consolidationManagement accounting: Budgeting, costing, cost management, activity based costingHuman resources: Recruiting, training, rostering, payroll, benefits, 401K, diversity management, retirement, separationManufacturing: Engineering, bill of materials, work orders, scheduling, capacity, workflow management, quality control, manufacturing process, manufacturing projects, manufacturing flow, product life cycle managementOrder Processing: Order to cash, order entry, credit checking, pricing, available to promise, inventory, shipping, sales analysis and reporting, sales commissioning.Supply chain management: Supply chain planning, supplier scheduling, product configurator, order to cash, purchasing, inventory, claim processing, warehousing (receiving, putaway, picking and packing).Project management: Project planning, resource planning, project costing, work breakdown structure, billing, time and expense, performance units, activity managementCustomer relationship management: Sales and marketing, commissions, service, customer contact, call center support - CRM systems are not always considered part of ERP systems but rather Business Support systems (BSS).Data services : Various "self–service" interfaces for customers, suppliers and/or employees.

I started using Excel VBA in 1995 when a licensee wanted a sizing program, and loved the experience so much it dominated the rest of my career. Excel does a great job as a front end for inputs, outputs and user interface. VBA keeps the details of the calculations in a more tamper-resistant place, while allowing engineers to read the code and satisfy themselves that the calcs are being done properly.My previous coding experience was decades earlier using FORTRAN IV on mainframes, but the client wanted something that ran on microcomputers. I picked up a copy of Visual Basic 3 at the local computer store, after comparing the “human readability” of its code to C, C# and Java.After building a crude user interface in Visual Basic, I learned that Excel 5 had a new macro language that was based on Visual Basic. Using VBA for the calcs and the Excel grid for the inputs and outputs was a perfect solution to my problem. It meant that users could approach the finished program already knowing how the user interface worked, the code (with comments) was self-documenting, and the client had peace of mind regarding ability to modify the code in the future.I wrote user-defined functions to handle all the calculations, starting with thermodynamic and physical properties of refrigerants, water and steam. I then added code for heat and mass balances, modeled refrigerant compressor performance (volumetric flow and power consumption), evaporator & condenser performance (heat transfer coefficient, temperature approach and heat duty), and day/night temperature variations. After each building block was completed, I tested it against textbook data & worked examples.Finally, I added a master routine to call the various building blocks needed to size the equipment. It ended up being three nested trial and error loops. Fifty pages of unoptimized VBA code later, I had something that would produce answers.Unfortunately, it was much too slow to be practical. Timers in the code helped find the bottlenecks, and determine whether my algorithmic tweaks were helpful. The nested trial and error loops were the biggest problem, and semi-empirical guesses for the next value helped greatly. The next improvements occurred by transferring all the inputs into VBA as an array, and returning the results in similar fashion. Overall, these tweaks reduced solution time from 600 seconds to under 10.I liked VBA-powered solutions so much, that I started applying it over the next 20 years to every routine engineering task. I grouped related tasks to the same workbook, with each task on a separate worksheet. In so doing, I could share code, especially the functions used to predict thermodynamic and transport properties, heat transfer coefficients and pressure drops. I had three such workbooks, one for refrigerated equipment (ice-makers), one for water purifiers (evaporators and steam generators), and one for heat exchanger calcs.Another workbook was dedicated to sizing control valves and relief devices. I stored flow characteristics of each model in a lookup table on a hidden worksheet, then used a dropdown to select the best fit for each application. The VBA code would then tell me the throttled position of the control valves, depending on flow characteristic and process conditions.Next, I developed workbooks to generate instrument lists for a line of equipment that used a “models and options” approach to engineering customization. I had to submit these instrument lists for customer approval. This workbook was linked to the Material Resource Planning (MRP) system, so I could enter a part number and retrieve its engineering description from the MRP database. By using the VBA code, I cut engineering time while improving accuracy (because I could concentrate on the few exceptions rather than the large number of standard components). I then added features like using customer-generated tag numbers, ISA datasheets with process-linked data, and using customer preferences for engineering units.To assist with project management, I built a VBA-powered workbook documenting commercial and technical issues during the course of a lengthy project. Each open issue was discussed during a weekly telecon, and I documented those discussions in a separate column for each telecon. The VBA code let me add issues, hide them when they were closed, sort the list, and display only the three most recent telecons.When preparing bids for Defense Department projects, we had to break costs down by month and Work Breakdown Structure (WBS), with separate worksheets for each Contract Line Item Number (CLIN). Costs had to add up vertically, horizontally and from the first worksheet to the last. Last minute management directed changes kept the bid team working long hours. But with VBA code, I could automate building the Work Breakdown Structure, and could find errors and omissions when categorizing expenses.My last employer used engineers to write purchase orders because our time was billable to the client. The accounting department was overhead, so we were required to code the purchases by project and account number to improve the efficiency of the non-billable accounting clerks. Historically, this was done by finding an old PO and modifying it as needed. Doing so institutionalized mistakes, and wasted engineering time chasing down those accounting codes. So I built a VBA-powered workbook that built the PO from scratch using dropdown lists for the vendor, division and type of commodity being purchased. From those selections, the code looked up the required data from the company’s vendor database, and lookup tables on a hidden worksheet. It could even calculate the UPS shipping cost based on weight and type of service.