As a result of our participation in BizBarcelona de 2012, Anella, the business competitiveness portal driven by ACC1Ó of the Catalan government, decided to publicize our case as an example of how to launch an IT company with poor resources.

Our customer support services not only include the resolution of problems which may occur in the ERP, they also include a service that is often neglected and usually our clients are not aware: the maintenance of OpenERP server operating system.

Although this work is not visible, every week or two weeks, NaN·tic updates the operating systems of the servers of our clients, applying the latest security updates.

Using Nagios allows us monitoring and supervising of the operating system without the necessity to be aware of whether the system requires updates. However, we also supervise the entire control system.

Thanks to this active surveillance we have detected some hard errors in the hard of our clients or problems of space in their disks, anticipating problems and avoiding major consequences for the user.

In particular, the monitoring is focused on:

• Status of the operating system, updating it where necessary.
• Monitoring the proper operation of the disks, notifying the client the problems identified.
• Verification of proper operation of copies of discs RAID and resynchronizing them if the problems are not from hardware.
• Charging system, checking the correct operation in case of alarm.
• Control disk space, freeing up space if it’s in our hands or asking the client action.
• Monitoring backups, checking that are current and solving any problems it may have occurred.

All this allows us and our clients to sleep more relaxed and forget about server operating system problems which may occur.

We often speak of our developments but rarely we talk about the technologies on which we base and make them possible. This want introduce about the database manage system used by OpenERP and therefore we use in all our implementations, often the customer doesn’t know its name or what it does.

PostgreSQL is the component of the ERP that is responsible for keeping the information a structured manner and allows fast access to your information. As the rest of the components of the install in the customer server, it’s free software, such as the operating system (Debian GNU / Linux) or the ERP. Our installations match the following schema:

As with the ERP or the operating system, the fact that PostgreSQL is open source and free doesn’t mean a inferior product compares to the proprietary software. In fact, it competes against Microsoft SQL Server and Oracle Database.

Moreover, several companies have established supplying highly skilled professional services in support of PostgreSQL . Companies like EnterpriseDB or 2ndQuadrant, gives additional services of support on the system, far away NaN·tic knowledge. These companies offer support to important brands as Skype or Amazon, which use PostgreSQL in production environments.

This fact brings us one of the great advantages of open source, small and medium enterprises, have free access to the same technology used by large corporations.

The new versions of PostgreSQL, as the recent 9.2, increase substantially performance of the system and have advanced features such as the replication which is already used by some of our customers. The real time replication allows have a second server with the same information as the main server, in case of failure of the first system, the second server is started in a few minutes without data loss. You could find more information of the service at the following link.

Also well known and used, MySQL is the other open source database management system. In our opinion, use PostgreSQL was the best option by OpenERP since PostgreSQL is more complete, very solid, extensible and it doesn’t depend only on a company, there are several companies and individual developers that make it progress at an impressive rate.

The problem of the dependence on a single company, has recently been a controversial issue due to the acquisition of MySQL by Oracle (the great competitor!). This is not possible with PostgreSQL as there are dozens of developers from different origins who daily improve the program.

You can find more information about PostgreSQL at its official website: www.postgresql.org

In this blog we will focus on the 5 fields available for customizing reports and graphs: Dimensions, Column Dimensions, Mesures, Order and Groups . To facilitate the comprehension we will continue with the same example as in the previous blog.

1. Dimensions

This field indicates what information is displayed in rows in the table of data, as well as how to group and order it. The example shows the following sequence:

The main branch show the products and the sales of each month in a second level.

This table allows us to modify the sorting order (Sequence), if we change the order to Month (1) and Product (2) the data tree changes and show the months in the main branch and the products sold in each period in a second level.

We can also add fields in the data source table, adding a new record to the table and assigning the order by sequence number. In the example we could display data such as country, city, payment, discount, etc…

In the creation of the data structure we must consider that the graphics only display data of one level and also we can’t make comparisons between different rows. If we want compare some data it should displayed on columns on Column Dimensions.

2. Column Dimensions

This table indicates the information displayed in columns and what you can compare in the graph, the sample shown the year (Year).

Just as in Dimensions, we can also add fields and arrange them. In this case, the OpenERP limitations doesn’t allow us create a data tree for the columns, the information is shown in severals columns, with the aggregate data in first position followed by different columns with specific data field. In the example and recovering the chart above, we see a first column with the aggregate of every year followed by several columns with units sold each year.

3. Mesures

The third table shows what data we want to display and how these will be aggregated: costs, sales, units, etc… As in the previous tables we can add and order more fields that will be displayed as new columns.

We will find a new parameter related to the field: (Aggregate). It defines how the information will be grouped, there are several options:

• Average:  The aggregate shows the average values.
• Sum: The aggregate is the sum the displayed values.
• Count: The aggregate shows the number of entries.

 4. Order

This table allows us to define the order of the information in the data tree. We can add the expressions Dimension and Mesures of the tables 1, 2 and 3, and indicate the priority order with the sequence number. We have the following sort in the example:

First will sort the data by number, followed by the product name and the month.

We can also define what sort criteria are followed for each concept, with a double click in the column log Order we can select:

• Ascending: Sort the data lowest to highest numerically or alphabetically.
• Descending: Sort the data highest to lowest numerically or alphabetically.

 5. Groups

Finally we have the table Groups which allows us to specify the groups or profiles of users who have access to the report. It uses the same user groups defined in OpenERP.

Initially the menu of Business Intelligence only shows two options:

• Configuration: shows the data for analysis (Expressions) and the filters applied in the basic reports (Filters).
• Reports: The list of 30 reports that are delivered with the module.

We start with the standard templates you can find in Reports, its characteristics are described briefly with the name, model (table of OpenERP with data analyzed), a brief description of report and the filter applied. We will use the report Year/Products/Month as an example of the blog, a report that shows the sales by product, year and month based on data of the invoices

First step is create the menu entries, we click Year/Products/Month and open the tab of the report. There you could find two tabs and several fields to define the parameters of the report, they will be explained below. At the moment we concentrate on the three buttons on the bottom.

• Update data.
• Create Menu Entries.
• Remove Menu Entries.

We create the report with a double click on Create Menu Entries and load the first data Data Update. Returning to the main menu and refreshing OpenERP you will find a new entry in Business Intelligence, the report Year/Products/Month, with information of the date and time of the last data update on brackets. One of the characteristics of the module is that it kept in memory the latest data analyzed so you can consult it immediately if don’t need it completely updated.

We find two additional entries, one with the same name of the report with all the data analyzed in tabular format, and the action Update Date Year/Products/Month that allows update the data directly without entering in the setup of the report. The more interesting results are sorted in the main entrance.

Inside the report, the first column displays the information specified in Expression of the setup . These data are sorted and grouped sequentially by the sequence. In the example the order Products and Month shows first the products and inside them the month with sales. Please note that the line with the product name shows the aggregated total sales.

The other columns show data to analyze, these data are defined in measures on the setup of the report. The example specifies the cumulative quantities sold and as we are interested in the sales for different years, we find Year in Column dimension.

Before entering in the graph view, a comment of the two tables pending in the setup of Report:

• Order: The sequence indicates how are the data sorted. The example shows the products ordered first by amount sold, with the best selling product in the first place.
• Groups: Where define the user groups that can view the report.

An interesting data in the tab Internal Information: the fields Last Update Duration indicate the time taken to perform the last update, an interesting data to check before a new loading.

Let’s finally to the display of the graph back to the table with the data in tree format, a double click on the main entry shows the graph of the internal entries. Please note that the graph only shows one level of information, if we select the main branch we will see the sales of all products grouped without information of the months, however if you select a specific product you will see the sales aggregated for each month.

Once the double-click is done, the wizard appears and you can select the type of graph, bar or pie, and the data in Measures.

Finally note that you can use the fields at the top of the chart to filter the information.

In a forthcoming publication we will explain how to configure basic reports and adjust them to the interests of the company.

For those who have not followed this serial, we suggest start reading the previous publications in Quality Control and Quality Control in Production Lots and Incoming Pickings

The first module, nan_prodlot_quality_control_production, integrates the quality control in the production using the same structure of the incoming pickings, described in the previous blog entries. The creation of a new production lot automatically creates the defined quality tests leaving the lot in inactive status and waiting to pass the quality controls. Once passed, the lot will be activated for normal use in business processes.

Some quality control involve taking and storing samples. We have created the second module, nan_prodlot_sample_library, to facilitate the collection and the organization of the samples. This module adds a step prior to the validation of the lot and gives an identification number to the sample.

Github

• nan_prodlot_sample_library: https://github.com/NaN-tic/oo_nan_prodlot_sample_library.git
• nan_prodlot_quality_control_production: https://github.com/NaN-tic/oo_nan_prodlot_quality_control_production.git

apps.openerp.com

In this article we will continue with the quality control initiated in the previous post http://www.nan-tic.com/en/2012/control-de-calidad/ and its integration to OpenERP processes. Today we will talk about our modules nan_prodlot_quality_control and nan_prodlot_quality_control_input.

• The first module, nan_prodlot_quality_control, adds the quality control in the production lots, changing the standard work flow, and adds the configuration of the quality control in the company and in the product. Also the module adds the base for the triggers.
• The module nan_prodlot_quality_control_input takes care of create and assign the quality test to the production lot once the input material is done.

This modules add a section for quality in the company tab where configure the quality controls. There you can globally define the quality controls to apply to the products, in this way, when you create a new product, the quality controls will be automatically added.

We also have the possibility to select which products needs a quality control, we must leave in blank the quality section on the company tab and specify the quality control directly in the product details.

Today we will review our Quality Control module for OpenERP, updated to version 6 where we have added some interesting features.

The Quality Control module is a generic module that allows us to do any quality control system to different models manually (without being integrated into the ERP processes). Next weeks we will present other modules that automate and integrate quality control in the production lots or in the pickings.

Glossary:

• Method: The different methods available to test.
• Proof:  The test to check. We have two types of proof:
• Qualitative: The result is a descriptive term such as color, flavor, etc.
• Quantitative: The result is a numeric value.
• Possible Values​​: Values ​​or terms that we can choose as a result of qualitative proof.
• Synonyms: Different names for the same test.
• Test references: The various models of the application which can apply a quality proof.
• Template: The set of proof to be used in a test.

For those who have not tried the module in previous versions, we will show the basic operation of the Quality Control module with an example that includes a qualitative proof and a quantitative proof.

• We begin by defining the possible values ​​of the qualitative proof.

• We define the different methods.

• And the different proof to do.

• An example of qualitative proof.

• And an example of quantitative proof.

After setting the previous values​​, we start to define the test to be performed.

In this example we define a generic test applicable to any model, in this case the model Company. We also have the possibility of creating a template for a specific model, so if we specify that the template is related, we would select the Company and the Company model on which to apply the template.

One of the news in the update for OpenERP 6.0 has been the creation of the field formula to display the result of a proof. To define the formula should you only have to use the name of the lines as operands. In the example, we can link the proof result with the value of the line of pregnancy. Similarly, we could link the field with the result of the formula: (Pregnancy + Pregnancy2 * Temperature) / pregnancy, but it have not sense.

A practical example: the formula field has been used in one of our customers, dedicated to artificial insemination, to calculate the resulting dose according to the values ​​of quality tests made in each extraction.

Once finished the definition of all previous parameters, we only need pass the test. We must create a new test and the relationship with the company, we press “Select Template” and choose the test we need. The different lines will be automatically filled depending on the selected template.

The we only need to fill the test lines. In this case, it is not necessary to fill all the test lines as there is a test with two methods, only completing the test method is used, the quality test result “Success”

The last step is the validation of the test.

And supervisor approval if necessary.

You can download this module at:

github: https://github.com/NaN-tic/nan_quality_control

openerp.apps: http://apps.openerp.com/addon/2063

Today we present a new module developed by NaN·tic for OpenERP 6.0 which simplifies the production orders in cases where you do not need an intermediate step of picking, the gathering of the available components in the stock and the movement to the production area.

The module lets check the availability of the material directly from the production order and determine whether production is possible or not. The development has been designed following the normal flow of the application and respecting the use of supplies, allowing the calculation of the supplies or the planned application, also the module lets change the status of planned production orders if they can be done and send the purchase or production orders required to start production.

If you want to prioritize a production order, the module allows the cancellation of the reserved components and releasing them for the priority order.

You can download our new module at:

git-hub: https://github.com/NaN-tic/nan_mrp_without_internal_picking

apps: http://apps.openerp.com/addon/8112

NaN·tic info is a monthly newsletter published in Catalan ans Spanish which discuss issues related to NaN·tic and open source ERP. Among the articles you will find information about our news modules and improvements of the old ones, and also news about the ways of development of our RDI department. The publication will also link to our major study cases and it will be our communication tool for launching new services and promotions.

The purpose of this newsletter is simply improve our communication with the open source community. Not only user, also implementers, developers, consultant and everybody interested in.

If you wish receive NaN·tic info by mail, don’t hesitate send us an email by out contact page

Installation

You can download the module in the project page https://github.com/angelnan/nan_openerp_modules/tree/6.1 and clone it using the version control system git clone https://github.com/angelnan/nan_openerp_modules.git  or download the latest version as a zipped file in  https://github.com/angelnan/nan_openerp_modules/zipball/6.1

Keep in mind that you can find more modules in the repository.

Once downloaded:

1. Unzip if necessary, and copy or move the usual route of the ERP modules.
2. Reboot the OpenERP server.
3. Log in using the client.
4. Update the list of modules (Administration/Modules).
5. Locate and install the module nan_stock_scanner.

User Guide

Configuration

We have two options, first related to production lots of the input pickings:

• Never: Don’t create production lots.
• Always: Create a new production lot in each input.
• Assing by supplier reference: Search a production lot with the supplier reference and create a new one if there is no match.

The second reports the scanned quantity:

• Add a unit in each scanning (default).
• Fill with the expected quantity of the associated movement.

Input Pickings

In any input picking, and the rest of pickings, you could find a new tab: pending moves . It indicate the quantity of products that remain to scan and information of one: quantity, the supplier reference, expiration date, purchase price, packing and EAN code.

The scanning process automatically fills the fields of quantity and unit price with purchase information associated (depending on configuration). You could manually complete the fields of expiration date and the supplier reference to create the lot with the data required.

The new tab also facilitates EAN 13 code assignment to the product if there are none associated. During the scanning process you could complete manually the field with the EAN 13 code that is automatically stored in the product on the validation.

On this screen you can see how the products have been divided, a unit has been scanned with with its production lot and the rest is pending.

In the next shoot you could see the different tabs with the updated inforamtion of the scanning process.

Finally the screen once completed the scan of the input picking.

You can also create partial picking with a ingle click on the Confirm scanned products. In this case appears a small screen where you could:

• Confirm: Create a partial picking if necessary comparing the expeted and the received quantity.
• Cancel: Abort confirmation.
• Force confirm: We assume that we have received all the goods and confirm the delivery note.

Output and Internal Picking

The output and the internal picking are simpler as there are only information about product, quantity and production lot to scan.

Just as in any picking, the products are separated by the production lot.

The rest of the process is exactly the same as the described in tne Input Picking, with full or partial picking depending on the differences between the expected and real quantities moved.

This week, the new taxes will be available to all of them and from Monday we will be available to help them update taxes in products and those sale and purchase orders that require any changes.  It has not been clarified yet when the new taxes will have to be applied but we’ll be ready to help our customers with any needs that arise.

Users will only have to review manually draft invoices and default taxes associated with accounts (typically configured in expense accounts to make it faster to code supplier invoices).

During these days we could discuss and work on the business models presented by the different participants, starting the event with a workshop on how to structure a business model and ending it with a coopetition between the different Start-ups with the aim of sharing knowledge, experiences and points of view between entrepreneurs.

We want to thank ACC1Ó and INLEA Foundation for organizing the event, and specially the invitation of Jordi Puigdellívol, mentor and sherpa for Start-ups, and congratulate him for the management of the conferences.

Tryton is an ambitious project for the continuous improvement that uses our knowledge and expertise in OpenERP. The presentation focuses on the difference for users and developers, the state of the development for the Spanish localization and the present and future plans

The presentation Tryton ERP by NaN·tic is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.

Created from www.slideshare.net.

This development is a solution that aims to improve the functionality of OpenERP for data analysis without the complexity and power of other Business Intelligence software that require parallel implementation. The presentation is focused in the objectives and main characteristics of the module, the advantages over other BI solutions and the future lines of development.

The presentation BaBI: BAsic Business Intelligence by NaN·tic is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.

Created from www.slideshare.net.

Last November we published an extensive entry in our blog: Presenting KafkaDB explaining the reasons an the  requirement of the development. Now this presentation briefly summarizes the origin and goal of the initiative to further emphasize the application performance and settings.

The presentation of KafkaDB by NaN·tic is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.

Created from www.slideshare.net.

The presentation reviews the main characteristics and functionalities, of which we highlight the possibility of working with different species, manage multiple farms with access subjected  to user permissions, complete traceability of animals, medicines and feed, integration with analytical account and the ability of configure different species and manage the events related to each one.

The presentation Verticalization for breeding and feeding farms by NaN·tic is licensed under Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.

Created from www.slideshare.net.