Purpose of the system
- Create and maintain a common environment for the flow of timber data throughout the supply chain.
- Improve and simplify processes and information flows throughout the timber supply chain, increasing supply chain efficiency – faster and higher quality movement of information and timber.
- Create opportunities to participate in e-business processes.
- Improve joint supply chain management, ability to trace timber flows.
- Reduce manual work and data entry errors.
List of documents participating in the data flow
The PapiNet International Data Standard describes the content of documents used in business transactions in the industry. The sector in this case means the entire wood supply chain up to pre-processing and the paper industry up to the sale of the final products.
- Transport work assignment
- Timber Transporter’s Report of the stowed cargo
- Registration of the timber transporter at the place of delivery
- Cargo measurement information (measurement act)
Data security
- To ensure data security, the system checks user roles and accesses in every operation.
- Access at database level only via API, not publicly available. Communication is secured using a TLS certificate and data encryption.
- Customer authorisation using a token solution. The system supports the anonymisation of data required by the Data Protection (GDPR) Regulation.
- All passwords are stored in encrypted form only so that the system administrator does not have access to them. If the system administrator needs to reset the password, this should be done via a function call that generates the new password and sends it to the customer’s registered email address.
- Every action in the system is logged, including every action that is performed directly on the database by the system maintainers.
- Data security audits will be carried out regularly.
SLA criteria
System availability time 24 hours 7 days.
The emergency response time will depend on the category.
| Name | Description | Elimination time | ||
| A | Accident | The problem causes the system or a part of it to stop working completely. The work cannot continue. | 8
|
hours |
| B | An error that cannot be bypassed | A problem that adversely affects the performance of essential functions of the system. There is no known solution to the problem, but it is possible to continue working in a limited mode. | 4 | working days |
| C | An error that can be bypassed | The problem causes minor limitations in the functionality of the system. The impact on the system is minor, but inconvenient. There is a bypass solution. | 20 | working days |
| D | The problem does not affect system capacity | The problem does not affect system capacity, but causes inconvenience in working with the system. Mainly regarding system update and/or maintenance. | 30 | working days |
Network infrastructure
Troubleshooting – Support for network connection points must be provided 365 (366) days per year.
SLA levels:
SLA 1 – maximum time for troubleshooting – within one (1) hour on working days, 24 hours a day from the moment the relevant problem is detected or logging on the data connection.
- Batch loss factor – <0.01% at data channel peak load up to 90%;
- Latency – <20 ms at data channel peak load up to 90%;
- Cumulative monthly downtime allowed – 30 minutes.