Understand the modules, the implementation and what goes into your proposal
The scope depends on the laboratory's needs. Explore the available areas and see which items are defined during the assessment.
What exists today and what depends on your case
Availability shows what the system offers today. Whether each item is part of your plan is defined in the proposal.
| Module | Availability | What does it depend on? | Validate in the proposal |
|---|---|---|---|
| LIMS, samples and analyses |
| The laboratory's methods, parameters and report templates, configured during implementation. | Which methods and report templates are part of the initial setup. |
| Quality management |
| The laboratory's management system processes. Quality policy and objectives have no dedicated module and can be controlled as documents. | Which routines are in scope: documents, nonconformities, internal audits and risks. |
| Sampling and mobile |
| The field team's devices and the sampling flow. Offline mode is validated in airplane mode during implementation. | Which sampling routines and checklists are part of the setup. |
| Finance |
| NFS-e service invoices issued under Brazil's national standard, depending on the municipality joining it, an A1 digital certificate and the company's tax setup. | Tax document issuance depends on the document type, the location and the available integrations. Confirm coverage for your operation in the demo and in the proposal. |
| CRM |
Sales module available according to plan | The contracted plan and the permissions set for each user group. | Whether the sales module is part of the chosen plan. |
| Integrations |
| Each instrument's file format, the ERP in use and the development done on the external system. Other ERPs require a case assessment. | Which integrations are in scope, who builds each part and how each instrument will be tested. |
| Training and migration |
| The volume and format of the data history, the number of people to train and the team's availability. | Which data will be migrated, in what format, and how training will be delivered. |
| Support | Defined in the proposal | The contracted support channels and terms. | Channels, hours and support terms. |
Module availability and what to validate in the proposal
LIMS, samples and analyses
- Availability
- Available
- What does it depend on?
- The laboratory's methods, parameters and report templates, configured during implementation.
- Validate in the proposal
- Which methods and report templates are part of the initial setup.
Quality management
- Availability
- Available
- What does it depend on?
- The laboratory's management system processes. Quality policy and objectives have no dedicated module and can be controlled as documents.
- Validate in the proposal
- Which routines are in scope: documents, nonconformities, internal audits and risks.
Sampling and mobile
- Availability
- Available
- What does it depend on?
- The field team's devices and the sampling flow. Offline mode is validated in airplane mode during implementation.
- Validate in the proposal
- Which sampling routines and checklists are part of the setup.
Finance
- Availability
- NFS-e:Depends on configuration
- What does it depend on?
- NFS-e service invoices issued under Brazil's national standard, depending on the municipality joining it, an A1 digital certificate and the company's tax setup.
- Validate in the proposal
- Tax document issuance depends on the document type, the location and the available integrations. Confirm coverage for your operation in the demo and in the proposal.
CRM
- Availability
- Available
Sales module available according to plan
- What does it depend on?
- The contracted plan and the permissions set for each user group.
- Validate in the proposal
- Whether the sales module is part of the chosen plan.
Integrations
- Availability
- Instruments:Via file import
- Omie ERP:Via integration
- API and webhooks:Available
- What does it depend on?
- Each instrument's file format, the ERP in use and the development done on the external system. Other ERPs require a case assessment.
- Validate in the proposal
- Which integrations are in scope, who builds each part and how each instrument will be tested.
Training and migration
- Availability
- Requires case assessment
- What does it depend on?
- The volume and format of the data history, the number of people to train and the team's availability.
- Validate in the proposal
- Which data will be migrated, in what format, and how training will be delivered.
Support
- Availability
Defined in the proposal
- What does it depend on?
- The contracted support channels and terms.
- Validate in the proposal
- Channels, hours and support terms.
Modules available according to the contracted scope.
Implementation
Implementation happens in stages, with the laboratory team taking part.
1. Assessment
We learn the routine, methods, reports and systems the laboratory uses today.
2. Data scope
We define which records and history go into the system and in what format.
3. Setup
Methods, parameters, report templates, permissions and in-scope integrations are configured with the team.
4. Acceptance testing
The team tests the flow with examples from its own routine and points out adjustments before daily use.
5. Training
Training with scenarios from the laboratory's routine, according to each person's role.
6. Go-live
The system starts being used in the routine, with support during go-live.
Timeline: The schedule depends on the number of methods, the data history, the integrations, the contracted modules and the teams' availability. The estimate is presented after the initial assessment.
See the stages in detailCosts to clarify
Ask for the proposal to make each item below clear.
License or plan
The fee for using the system, defined according to the laboratory's operation.
Optional modules
Which modules are part of the chosen plan. The sales module, for example, depends on the plan.
Implementation
Assessment, setup, training and go-live support, with the scope defined after the assessment.
Integration
Connection with instruments, ERP or other systems, according to the assessment of each case.
Support
Channels, hours and support terms.
Commercial terms
Contract length, payment method, price adjustment and data handover at the end of the contract.
Questions about plans and implementation
Is there a user limit?
There is no limit on registering users. The plan may set how many people can access the system at the same time; that number, the modules, the services and the terms are confirmed in the commercial proposal.
Does the plan keep up as the operation grows?
When the operation changes, with new modules, new integrations or new services, the scope can be reviewed with the sales team. The change is recorded in a proposal.
Which services are part of the implementation?
Implementation covers assessment, setup, training and support during go-live. What goes into each stage and the schedule are defined after the initial assessment.
What are the support channels?
Support is provided in Portuguese. To reach our team, use WhatsApp or email contato@gerencialab.com.br. The contracted support channels, hours and terms are confirmed in the proposal.
What determines whether my data can be migrated?
Migration requires a case assessment. What matters is the format and organization of the source data, the volume of history, which records need to come over and the team's time to check the result. The migration scope is defined during the assessment and recorded in the proposal.
Want to know what goes into your laboratory's plan?
In the conversation, our team learns about your operation and suggests modules, integrations and services for the proposal.