The main goal of the current product description is to serve as a general description of Havelock product for the purposes of Individual contract with the Customer. The Customer understands that this document is not an Еnd user manual neither it could describe all the business logic that underlies the product’s functionalities. Shall any questions arise or additional explanations are needed the Customer shall contact Havelock JSC representatives on the designated email listed in the Individual Contract.
Havelock (the product) is a software product aiming to facilitate the management of the processes related to production of goods or delivery of services.
Havelock is based over the management concept for proactive dynamic planning.
3. Access to Havelock
The product is cloud based and the access to the End User Interface is provided through any contemporary web browser on a designated URL address, specified in the Individual Contract.
Customer specifies the users that will have Administrator role in the Individual contract. Once the contract is executed Havelock shall provide on their individual email addresses access details to the product.
The users with Administrator role shall create the remaining number of users as specified in the Individual contract. Based on the specific roles they have been given from Administrators, End users will have access to different parts and functionalities of the product (see below for more details).
4. Integration of Havelock with 3rd party software
Havelock is based on Rest API architecture which allows integration with other API based third party software. Please refer to Havelock Services and Support Policy for more details how to request such integration.
5. Key entities
Below are listed the key entities of Havelock Product.
The projects are the main entity of Havelock. All activities in one organization could be organized in projects.
The milestones are the main activities that need to be completed in order to fulfill a specific project or produce a specific product. The milestones could be organized in predefined templates / procedures (if the management requires specific process to be followed) or could be added one by one for a specific project.
5.3. Milestone templates / Procedures
The Milestone Templates (procedures) represent predefined list of Milestones with assigned Days to Project Deadline. Only specific roles are able to create Milestone Templates. Once created Milestone Templates might be used for all Projects.
The tasks are the most granular type of activities. If a given job requires something to be completed from another user than a new task has to be created.
The comments module is only on a task level. The goal is to have all the communication related to a specific task in one place.
On top of the comments submitted by the users on the same interface appear the system notifications (activity logs) related to the specific task, ordered within the comments by chronological order.
The goal is to have everything important related to the existence of a specific task – in one place.
The attachments are the file storage functionality of Havelock. The attachments could be organized in folders and each user can be assigned access rights to specific folders.Once uploaded the files could be moved between the folders that the specific user has access to.
5.7. User roles
The main purpose of the user roles is for the organization to create clear responsibility matrix between the employees who have access to Havelock.
The settings area of Havelock contains the so called nomenclatures for the system to function. In this area, the users with Administrator role create the remaining users of Havelock and all other predefined properties of the key entities.
6. Language versions
The End user interface of Havelock is available on English, French and Bulgarian languages. However the content that end users enter into the product is only in the language they have used.
The present version of these Terms was adopted by Havelock JSC on October 28th, 2019.