Quality management is the process where the quality of the product or service is questioned. This includes all the procedures involved to fix the situation, so all parties are satisfied.

Output from quality management process

  • Corrective and preventive actions are implemented.

  • Complaints are registered and handled.

  • Returns are performed for suppliers and customers.

  • Statistics regarding quality are exported.

Every company should prioritize resources to keep the quality of the product or service as high as possible. Mistakes and errors can happen, and it is important to have a set routine to handle these situations without losing customers. RamBase offers a module for these instances, where both corrective and preventive actions are performed, to fix the situation at hand in addition to avoiding such instances in the future. The function for returning goods or allowing a customer to return goods is integrated into every aspect of RamBase that deals with deliveries. To get an overview over the quality over a period, the Quality Management module in RamBase offers reports where the statistics are clearly presented.

Tasks involved in this process

  • Corrective and preventive actions - Actions need to be taken in situations where the quality is less than ideal. Corrective actions are taken to fix the situation and preventive actions are needed to avoid the situation to reappear.

  • Complaints and returns - Complaints from customers need to be resolved, and any defective/damaged goods need to be returned.

  • Statistics - All businesses live by their reputation, and statistics regarding the quality of deliveries are key to find how well the business avoids quality issues.

Corrective and preventive actions

Link to interaction.

Corrective and preventive actions are registration of typical quality events directly from the place in the ERP system where the event occurred.

Output from corrective and preventive actions process

  • The quality issue is reported.

  • The quality issue is followed up.

  • The issue is resolved.

RamBase supports standard corrective and preventive action processes with no extra logins and no sub-system. Registration directly from different applications in the system makes the registration close to both the place and time for the issue, makes it easy to register accurate quality issues. The issue is then followed up and actions are taken to both fix the issue at hand and to avoid similar situations in the future.

Tasks involved in this process

  • Registration of a quality issue - The quality issue is reported by the customer and registered into the system.

  • Follow up on the quality issue - The quality issue is followed up and methods of fixing it are presented.

  • Close the quality issue - The quality issue is resolved, and the issue is closed.

QA Reports

The Quality Assurance Report archive (QAR) contains reports on quality deviations and actions taken to improve the overall productivity and service quality. The archive is managed by the QAR program.

To inspect the archive content, write QAR in the program field and press ENTER.

To inspect a single report, click the DocId link or highlight the report entry and press ENTER.

Searching the QAR archive

The list of quality reports may be restricted by filters and by their report status. It is also possible to list predefined sets by clicking the radio buttons below the menu listing.

  • Simple search strings - The QAR program searches the DocId field. If you add a number to the program name (for example QAR 101137) the program searches for reports with a similar document id.

  • Predefined subsets - Select the predefined subsets by clicking the radio buttons below the list. In addition to the All documents subset, and the My documents subset, you may list reports for which the deadline has expired, as well as reports that are still open.

  • The Source document drop down box - The Source document drop down box allows you to list reports that have been created from a certain document such as ART, LCM, and PWO.

  • The Delayed drop down box - The Delayed drop down box allows one to select and list reports for which the due date is exceeded.

  • The Group by folder - The Group by folder allows you to construct a filter to pick out specific subsets of reports.

To group reports by a certain property, open the Group by folder and select one of the options in the dropdown-box to the left. Select a message type, and press ENTER. The selected message type is added in the QAR Menu header along with a paint brush to remove the filter, and a Filter button to apply the filter.You may create a second, and a third filter before applying it.

  • Complex searches - To do more complex searches, click the Add Filter icon. A complex filter of up to 8 fields can be created by constructing conditions.

Extracting basic data for statistical analysis and graphical presentations

In order to analyze data, or present data graphically, data from the QAR archive can be extracted to a CSV file:

  1. Create a filter using the Add Filter button, unless you want to extract data from all QAR reports in the archive.

  2. Press F12 to open the action menu and choose the option Send CSV-file to myself. A spreadsheet file is created and sent to the user's email.

Register a quality issue

A Preventive Action is an action to prevent the occurrence of a potential nonconformance, such as harmful behaviors or processes.

Register a quality issue
  1. Enter the Quality Report Archive (QAR).

  2. Click the Create New icon to create a new QAR.

  3. Choose which type of category the issue sort under using the drop-down menu called Category.

  4. Choose the type of sub-category the issue will sort under using the Type drop-down menu.

  5. The Subtype field is either drop-down menu, based on the previously chosen categories, or free text fields. The Case field is always a free text field.

  6. The field Reported By can be entered with the PID of the person who reported the issue.

  7. The Review dropdown menu has two option, Pending and Reviewed. Choose if you want the issue to go through a review process. This flags the issue and makes it visible when filtering.

  8. Click the magnifying glass called Grouping to open the QAR Grouping popup window. Here you may choose which department (DepNo field), project (PrjNo) and the Assets menu (AstNo) the issue will be related to.

  9. Add a description in the description free text box, together with any notes & attachments you want to connect to the issue.

  10. The next step is to forward the report to the next attendant which this is accomplished by pressing the Register button. The status will then change from 1 to 2, and a new folder, Temporary actions, becomes active. The new folder will typically be handled by the next attendant.

With the report in status 2, the person responsible must complete the following steps to process:
  1. Open the Temporary actions folder and enter a description of the temporary action.

  2. The Deadline will be set default to todays date. Keep this, or edit it if you need.

    • If the issue is lacking details, it may be returned to the original creator for supplemental information using the Return button.

  3. Choose the Next Casehandler using the person icon.

  4. Register the temporary actions using the Register button.

When a report on preventive action in status 2 is registered, the status is updated to 3, and a new folder, Cause, is now active.

With the report in status 3, the person responsible must complete the following steps to process:
  1. Open the Cause folder

  2. Select a Cause type

  3. Write a supplementary description of the cause

  4. Choose the Next Casehandler using the person icon.

    • If the issue is lacking details, it may be returned to the original creator for supplemental information using the Return button.

  5. Register the cause using the Register button.

When a report on preventive action in status 3 is registered, the status is updated to 4, and a new folder, Corrective actions, is now active.

With the report in status 4, the person responsible must complete the following steps to process:
  1. Open the Corrective actions folder

  2. Select an Action type

  3. Write a supplementary description of the corrective action

  4. Choose the Next Casehandler using the person icon.

  5. Register the cause using the Register button.

The Risk Assessment folder is not mandatory, but is recommended.

  1. Choose the most fitting option in the Recurrence Probability dropdown menu.

  2. Choose the degree of severity in the Severity dropdown menu.

  3. The date/signature is set automatically.

With the report in status 5, the person responsible must complete the following steps to process:
  1. Open the Verification folder

  2. Write a supplementary description of the verification if needed.

  3. Choose the next casehandler.

  4. Register the cause using the Register button.

If you need to connect the issue to an article, press F12 to open the action menu and choose the option Link to ART. If this is chosen, choose the desired article and press ENTER. There will now be a reference to the article in the QAR document. All articles with a QAR document related will have this document listed when you click the QAR Documents icon in the ART document.

QAR may also be created from a series of other documents such as CUS, SUP, PWO and LCM in addition to ART. Please look for the QAR Documents icon in the upper right corner on the document.

Closing the quality issue

After the corrective measures have been entered and the issue is in ST:5, it is time to close the issue.

  1. The issue is sent to the person chosen in the Verification folder.

  2. Enter the Completed folder and click the Close button.

  3. The issue will now receive ST:9 and the issue is closed.

Complaints and returns

Link to interaction.

Complaints and returns covers both a quality issue process and a complex logistics overview. In addition to register a quality issue, this process gives to the possibility to follow up the operational handling of a complaint dependent of a set of complaint and return scenarios.

Output from complaints and returns process

  • Complaint from customer is registered.

  • The customer complaint is followed up.

  • Handling of the financial aspects of returns or complaints.

The situation concerning complaints and returns can involve a complex logistical process with return of goods, repair or re-delivery, return to your suppliers and the financial impact this has. All these details need to be registered correctly and followed up through several steps. The reason for that is to ensure a clean and efficient complaint or return situation which result in the continued business relationship with the customer or supplier. Another aspect is the financial situation. A return situation will inevitably cause a financial disorder, which needs to be handled correctly so the ledger is true.

Tasks involved in this process

  • Create a customer deviation document - The customer deviation is registered in a specific document for further processing.

  • Follow up on the complaint workflow - The complains are set in a workflow where the issues are followed up.

  • Handle the accountancy impact - The solutions performed may have financial impacts which needs to be resolved for the accounts.

  • Create a supplier return document - If the quality deviation comes from the supplier side, the issue is registered as a supplier issue.

Settings for Quality management - Complaints and returns

Setting name

Description

Account for Repair Order from Deviation (CDV)

Value in this setting is the Account that should be used on Sales Order (COA) created from the Repair of loan process on a Deviation (CDV). Format to be used: NNNNNN (N for numbers)

Autoforward Sales Invoice/Sales Credit Note (CIN/CCN) from Deviation (CDV)

If this setting is "ON" - the Sales Invoice/Sales Credit Note (CIN/CCN) will be autoforwardet to status 4 when using the option 'Account Action' on Deviation (CDV)

Deviation (CDV) - Copy Freight to new Sales Invoice (CIN)

If this setting is 'ON' - On a Deviation (CDV) with 'ship replacement' or 'repaired product', the new Sales Invoice (CIN) that is created will get Freight copied from the original Shipping Advice (CSA) - the Source on Deviation.

If there is a Sales Invoice in status=1 or 2, an item will be added to this one, and the freight will be copied into this document

Product (ART) for ServiceTime

Value in this setting is a ProductId (e.g. ART/#100000) used for Service hours at 'Service Deviation' (CDV). An item will be created at the Sales Order Item (COA-ITM) for the used Service time. Format to be used: ART/#NNNNNN (N for numbers). NOTE: Setting is only used by the customer Hatteland Display

Require Approval on Invoicing and Crediting from Deviation (CDV)

If this setting is 'ON' - Deviation (CDV) with AccountAction=Creditnote or Invoice will get status=7 when the goods are received from Customer. The option 'Released for Account Action' must be done before the Sales Credit Note (CCN) can be created. If the setting is 'OFF' - The Deviation will go direct to status=4 when goods are received from Customer

Service Model

If this setting is "ON" - Customer is using the old Service Model in Rambase. Only used by Hatteland Display

Set Linking Blocked in SAP for CusReturn Goods Reception (SSA)

If setting is 'ON' - Set Linking Blocked in default SAP that is created when CusReturn Goods Reception (SSA) is registered

Status on Customer returned Supplier Shipping Advice (SSA)

Value in this setting is either Status '3' or '9'. When you registrate a Supplier Shipping Advice (SSA) marked as CusReturn (Customer Return), the Shipping Advice will get Status 3 or 9 depending of the value in this setting.

Customer deviations (CDV)

There are several ways of creating a Customer Deviation (CDV) document. You can create it directly from a Shipping Advice (CSA) item, from the Life Cycle Management (LCM) part list, or create a new one from the CDV archive.

The easiest method of creating a CDV is from the Shipping Advice (CSA). When created from the CSA most relevant information is already filled in. Use the context menu option make Deviation Document and follow the same steps as when CDV is created from the CDV menu, from step 2.

To create a new CDV from the CDV menu
  1. Write CDV in the program field and press ENTER. Click the Create new CDV button.

  2. Enter the necessary information in the popup. The fields to the right in the popup will be populated with the information as you enter it.

    • Customer: Choose the customer (mandatory)

    • Shipment: Choose the CSA. If this is chosen, you will be able to choose serial numbers from a list compiled of serial numbers from the CSA in question.

    • Serial No: Choose the serial number

    • Product: Choose the product (mandatory)

  3. When you have entered sufficient information, the Next button will appear. Click this to proceed.

  4. You will now need to enter the deviation type and what caused the deviation in the drop down menus. The choices taken in the first dropdown decides the third dropdown, where the result of the deviation is entered. Click the Create Document button to go to the CDV document you have created.

  5. Press F12 and choose the option Forward to Register. This will set the CDV document to ST:2. Depending on the Corresondence settings, a notification will be sent out to the recipient(s).

  6. Depending on the deviation type, the different actions to take next will be defined in the Actions and Calculations folder. Press F12 to open the action menu and choose the appropriate option for your desired next action.

  7. Depending on the deviation type and deviation codes chosen, a new document will be created, either an SSA for the customer to return the goods, a credit note if the price needs adjustment or other document based on the previous chosen options. Click the document link and proceed with the document you have entered.

Based on the alternatives chosen earlier, you will need to complete the process with the documents which has been created during the CDV process.

Customer deviation codes (CDC)

Customer Deviation Codes (CDC) is a register which holds all valid combinations of deviation codes and associated actions. The combinations define the sequence of actions that must be taken in response to a particular deviation. Valid combinations are typically defined by the QA manager and the configuration itself is done by JHC personnel.

Field definitions CDC
  • Status - Valid statuses are:

    • St: 1: Edit mode, not yet active or available

    • St: 4: Active and available

    • St: 9: Closed, unavailable and inactive

  • Docid - CDC sequence number that uniquely identifies a particular rule set for a deviation type. Note that default rules are emphasized.

  • Deviation - Deviation type. Code and text are predefined by QA and JHC personnel.

  • Warehouse - Required warehouse action. Code and text are predefined by QA and JHC personnel.

  • Account - Required account department action. Code and text are predefined by QA and JHC personnel.

  • ICT - Actions required in case of inter company trading. Code and text are predefined by QA and JHC personnel.

  • LandedCost - Describes the basis for calculating the gross margin on the new document. Code and text are predefined by QA and JHC personnel.

  • Def - The selected default rule set for each deviation type.

  • AccountPart - Used for setting default accounting of fee, freight, and tax.

  • Prio - Used to set a priority display sequence in the corresponding CDV documents.

  • Loc - Defines the location from where the goods are sent from. If not defined, the location on the CSA will be used.

  • Rev - Revision history.

Update source on CDV

In instances where there has been entered insufficient, or wrong, information on the Customer Deviation (CDV) document, you can use the function Update Source to add a source. The criteria is that the CDV is in ST:1 or ST:2, and that an account action has not been taken. This means that there is no credit note created (the ACCDOC field is empty).

  1. Enter the CDV you wish to update source for.

  2. Press F12 and choose the option Select Source Fields. This will open a popup where you will be able to change the source using the fields Shipment (CSA), Serial No (the serial number of the shipment) or Product (ART). Click the Clear button to clear all fields. Enter the necessary information.

Note: Shipment and Serial No requires exact match to show values in this popup. Either enter the information without fault, or search. There is no option to search based on fragmented information, except for via the serial number history as described below.

Serial number history

The most used method of identifying shipments is by using the serial number.

  1. After you click the yellow arrow to see the alternatives, click the document icon to see the list of serial numbers linked to Customer Shipping Advice (CSA) documents. If you know parts of the serial number, it is possible to enter this fragment and then clicking the yellow arrow. The list will then be filtered by this criteria.

  2. When you have found the correct serial number, highlight the item line and press ENTER.

  3. You will be returned to the Serial Number History popup, and the CSA will now be visible. Click the Accept Values button.

  4. Back in the Update Source popup a new button will have appeared called Commit Changes. Click this to update the CDV and finish.

Example: Customer Deviations - Replacement of defect product

We can use an example to better illustrate how Customer Deviations (CDV) are handled.

The scenario we are going to use is that a company has sold a product to a customer, which has been broken. The warranty on the product is still valid and the customer return the goods for repair. The company perform repair on the product and return it to the customer.

Open the CDV application by typing in CDV in the program field, or by using the RamBase menu.

Click the Create CDV button. Customer and Product are the mandatory fields here. This information is already in the system as the company shipped the product in the first place. You can also find the specific shipping advice (CSA) using the Shipment field, which will fill the other fields. If you have the serial number on hand, this will also identify the shipment.

The popup you will see now asks for the serial number of the product. Choose the s/n from the list after you have clicked the yellow arrow next to the field.

The field will then update with the related Life Cycle Management (LCM) document. You will also see that the s/n appears in the field to the right.

As the product is a kit, the faulty part may only be a part of the kit, so if you click the yellow arrow next to the LCM field, you can choose between the parts that make up the kit. Click the Next button when finished.

The next popup asks for the Deviation Type and what caused the problem in the Caused By field. These drop down menus contains alternatives already defined in the Customer Deviation Codes (CDC) archive. As the product is broken, we choose the Goods Defect in the first field. This creates a second drop down menu asking what caused the defect. We will choose that we have reached an agreement with the customer. The last field asks us for the deviation code. As we are going to replace the product for the customer, we will choose CDC/1023, which is Goods Defect - Send to Cus. Ret to Stock. A new product will be sent to the customer and the defect product will be returned to stock. Click the Create Document when finished.

A new CDV document has now been created.

It is a good idea to look over and double check all the information. Press F12 and choose the option Forward to Register to register the CDV. The CDV will now go to ST:2.

As the document probably has been made while communicating with the customer, it will take some time to receive the broken product. When the product is received, press F12 and choose the option Goods Received From Customer. This will create a Supplier Shipping Advice document.

The CDV will go to ST:4. Click the link to the SSA in the CusReturnDoc field and register the article to stock as normal.

Go back to the CDV document and press F12, choose the option Ship Replacement. To wait until the damaged goods have been returned before sending the replacement is the best option for the company, but a poor choice from the customers perspective. It is not only possible to send the replacement before the damaged goods have been returned, but also recommended.

This will create a Customer Order Acknowlegment (COA) document. You can see the link in the ShipDoc field to the left.

Click the COA link and forward it to the customer as normal. Return to the CDV document and you will see that the COA has gone sto ST:8.

Press F12 and choose the option Account Action (Credit Note) to create a new credit note. You will then get the option to create a new credit note, or add this to an existing credit note. We are going to make a new one, as there are no existing for this customer. A new Credit Note (CCN) document has been created and the CDV has reached ST:9.

Click on the CCN link and forward it to the customer.

Example: Customer Deviations - Repair of defect product

We can use an example to better illustrate how Customer Deviations (CDV) are handled. In this scenario the customer has a defect product that needs to be replaced. This is not a warranty issue, so the customer will be invoiced for the repair (time and replacements, if any).

Open the CDV archive by typing in CDV in the program field, or by using the RamBase menu.

Click the Create CDV button. Customer and Product are the mandatory fields here. This information is already in the system as the company shipped the product in the first place. You can also find the specific shipping advice (CSA) using the Shipment field, which will fill the other fields. If you have the serial number on hand, this will also identify the shipment.

The popup you will see now asks for the serial number of the product. Choose the s/n from the list after you have clicked the yellow arrow next to the field.

The field will then update with the related Life Cycle Management (LCM) document. You will also see that the s/n appears in the field to the right.

As the product is a kit, the faulty part may only be a part of the kit, so if you click the yellow arrow next to the LCM field, you can choose between the parts that make up the kit. Click the Next button when finished.

The next popup asks for the Deviation Type and what caused the problem in the Caused By field. These drop down menus contains alternatives already defined in the Customer Deviation Codes (CDC) archive. The product is defect and the customer wants to return it for repair. The choices we have made is Goods Defect in the DevType field, as the product is defect, Agreement in the Caused By field, as we have reached an agreement with the customer, and CDC code 1010 (Return Goods for Repair (Invoice)) in the CDC field.

You will now see the CDV document. Look over and see that all the information is correct. Press F12 and choose the option Forward to Register to register the CDV.

The CDV is now in ST:2. The next step is to receive the defect product from the customer. Press F12 to open the action menu and choose the option Goods Received From Customer. The CDV goes to ST:3 and a Supplier Shipping Advice (SSA) has been created. Click the SSA link in the CusReturn field. Receive the goods in the SSA a normal. Return to the CDV document after the SSA has reached ST:9.

You will now have a new F12 option called Start Repair. Use this option and you will see a ship document appear in the ShipDoc field. This document is a Customer Order Acknowledgment (COA) and will contain all the costs related to the repair of the defect goods. To add the extra cost, use the plus sign next to the COA link called Add Extra cost, or click the COA link and add the extra cost using the F12 option Add Extra Cost Items. Return to the CDV document when finished.

If you need to change a part on the defect product, find the LcmDocid field and click on the LCM document link. In the LCM document, choose the item line with the part you want to change and click the Change icon represented by two overlapping sheets. This opens the Change LCM part with replacements in the item lines. Choose what happens to the replaced part, what it is caused by and other needed information. Click Confirm when finished. Return to the CDV document when finished. The replaced part is now added as a cost on the COA.

All parts that have been changed in the LCM, needs to be confirmed picked before the repair process can be completed. The PICK application can be started by clicking on the Part Change: Picking in process icon at respective line. PICK will be started with a default filter for this part, but this can be removed to confirm pick of all parts at the same time. Also if other parts have been manually added to the COA, they can be confirmed the same way. Eventually may those manually added items being confirmed picked in ordinary picking process on CSA.

When finished with the repair, press F12 and choose the option Goods Repaired. Confirm the action in the popup. The COA will go to ST:1 and the CDV to ST:4.

Enter the COA again. Press F12 and choose the option Forward to the Customer. This will set the COA to ST:8. Then press F12 again and choose the option Transport All Items. Choose the CSA in the transport alternatives popup. Click OK on the confirmation popup. You will now see the CSA document. Complete this as a normal CSA.

Go back to the CDV document and press F12 and choose the option Account Actions (Invoice) to create an invoice for the customer. This will create a new Sales Invoice (CIN) document. A link to the invoice will appear in the Account Actions box, more specifically in the Accdoc field. Enter the CIN and forward it to the customer.

Follow up on customer deviation

The most important fields in a CDV document are the DevType, which states the type of deviation, and CausedBy, which states the cause of the deviation. These fields control the further handling of the document based on the scenarios defined in the Customer Deviation Codes (CDC) archive. RamBase will offer suggestions on how to handle the document based on these scenarios, but hey may also be ignored as the document is in editing mode.

The deviation document will often need to be sent by e-mail, either to one or several recipients from the customer side. It may also be sent to yourself first if you want to double check all information in the output. The recipients are controlled by the Customer Contacts (CNT) archive as the contacts are defined here.

The deviation document will normally be sent following the default settings in RamBase at the time of registration, but it may also be sent subsequently if desired. This may be done by pressing F12, or right click, to open the action menu and choosing the option Print Copy/Resend. Then you choose if you want to send the original or a copy, and the method of sending.

To register the deviation document, and subsequently send it to the desired recipients, you must press F12, or right click, and choose the option Forward to Customer. This action assumes you have selected cause and deviation type in the CausedBy and DevType fields.

If you want to edit the deviation document after registration, press F12, or right click, and choose the option Open for Edit.

The CDV is now registered, and depending on what action registered as expected you may proceed with the processing as desired.

Register the complaint

The operator sets the deviation type and the corresponding deviation handling code. A deviation handling code decides which warehouse, financial and cost actions that should be carried out in the complaint case. Each deviation type can be set with a default deviation handling code. Therefore it's possible to only make the operator pick the correct deviation type if wanted.

Follow up on the complaint

Complaints are followed up from the action and calculation tab on the deviation document. Warehouse transactions regarding the complaint are handled at the warehouse, and the flow of goods are registered on the deviation document. Deviation handling and cost and financial transactions are carried out from the deviation document.

Quality management on complaints

Deviations in the integrated quality management system, can be entered directly from the deviation document. This gives the opportunity to carry out both transactional and QMS procedures from the same complaint.

Statistics

Based on the promised and actual delivery date, on both in- and outbound logistics, a detailed overview of delivery performance is automatically calculated by the system.

Output from statistics process

  • Overview of customer delivery performance.

  • Export the details to spreadsheet file.

Keeping an overview over the quality situation can be challenging without proper tools. In a company where quality issues are resolved ad-hoc, there will be no clear statistics regarding the company’s quality issue, and the issue may worsen before the proper steps are taken. RamBase can produce reports which details these issues clearly, which again enables the company to take the necessary steps to avoid these in the future. These reports can also be exported as Microsoft Excel files.

Task involved in this process

  • Inspect delivery performance statistics - The reports detailing the delivery performance statistics can be run and exported to several different file formats and can include several different statistics and details regarding the deliveries.

Delivery Performance Statistics (DPS)

DPS is an application which can be used to view statistics about confirmed and requested delivery date calculations for customers and suppliers. The application shows if deliveries has been done early, on time or late.

To start the application, write DPS in the program field and press ENTER.

Column descriptions
  • Time - This column shows the date intervals.

  • Total - The blue column shows the total amount of deliveries in the defined interval.

  • Early - The red column contains information regarding all early deliveries.

  • On time - The green column lists all deliveries that have been on time.

  • Late - The last static column, which is also red, shows all the deliveries that has exceeded their delivery date and is listed as late.

The rest of the columns are dynamic and shows detailed information on deliveries by the user-defined parameters set in the parameters-box.

Field descriptions
  • Column Interval - The Column Interval field indicates the interval used by the detail columns below, with a default set to 3 days.

  • Count checkbox - This checkbox gives the user the opportunity to show, or hide, the totals.

  • Pct Checkbox - This checkbox enables the percentage of delivery differences to be shown.

  • Incl Checkbox - This option ebables the user to filter non-confirmed and non-requested shipping documents.

The algorithm for calculating the required and confirmed date is stored in a batch program which runs every night in RamBase. The calculated values are stored in the CSA and SSA document fields DPCONF and DPREQ. When the batch program is not able to perform the calculation, these fields gets the value 0.

  • The first column in the application is showing the date intervals.

  • The blue column is the total number of deliveries.

  • The green column is showing statistics about deliveries done on time.

  • The red columns contains information about early and late deliveries.

  • The remaining columns in the application are showing detailed information about deliveries, based on a given day interval.

View options

First the user needs to select if the application shows statistics about customers or suppliers. This choice is found on the upper right corner drop-down list. Default view is set to customer.

The user can also choose which view should be started by simply writing DPS / CUS or DPS / SUP in the application command line field. To select between confirmed and requested, use the second drop-down list in the upper right corner of the application.

Parameters

The application is by default showing statistics on monthly basis, starting on todays date. The default column interval is set to 3 days. All parameter choices are found on the parameters task bar.

  1. In the first field select the date view you want the statistics to be presented in.

  2. If you choose the DAY INT (day interval) default interval is set to 30 days. This can changed by the user.

  3. StartDate is by default set to today's date, but can be changed by the user in the date field. Or simply click the calendar icon to choose the Startdate from the calendar. Date format is YYYY.MM.DD.

  4. The column interval field is used by the detail columns. The detail columns contains information about deliveries done early, on time and late on a given day interval. Default is set to 3 days, but this can be changed based on the users' needs.

  5. The Count checkbox is used for showing and hiding totals.

  6. The Pct checkbox is used for showing and hiding percentages.

  7. The Incl checkbox is used to include non-confirmed and non-requested shipping documents. By default the application is including early, on-time and late shipments.

An early shipment is a document with DPCONF or DPREC value less than 0. A late shipment is a document with DPCONF or DPREC greater than 0.

An on-time document is a document with DPCONF or DPREQ equal to 0. In addition, CONF or REQ date is required.

When checking Incl, non-confirmed and non-requested documents are included. A non-document has the value 0 in DPCONF or DPREQ and does not have a CONF or REQ date.

Checking Incl has impact on calculations in the total and percentages columns. The non-confirmed and non-requested totals and percentages are shown in own columns.

Blank, null and values starting with “N/A” are not included in the report.

Customer and Supplier filtering

By default, the application is showing statistics for all customer or suppliers. To filter this information,  press the Customer or Supplier icon on the parameter task bar.

This brings up the Customer or Supplier popup window where the user can filter the statistics shown in the application.

To remove the Customer and Supplier filters press the Remove Account Restriction icon.

The Production Quality Report (QAR) Widget

You use the QAR widget to see the number of quality reports related to production, by month. The Y-axis gives the number of reports and the X-axis gives the months from January to December.

  1. To add the QAR widget to your desktop, select in the desktop.

  2. Select ProductionQualityReportWidget and select .

  3. To compare the number of reports in the current year with any year in the past 5 years, select the Comparison year from the list.

  4. Hover over any bar, or the grid in the vicinity of a bar to see the month and number of reports in that month.

  5. You can view the chart as one of four types by selecting the necessary Chart type in the list.

    1. Bar. This is a typical bar chart that shows the data as color-coded bars.

    2. Fluctuating Line. In this chart, the data is represented by color-coded lines.

    3. Bar Stacked. In this chart, the bars for the comparison and current years are superimposed.

    4. Accumulated line. In this chart the data is represented by color-coded, shaded areas.