Under the “Project Management” sub-menu, click <Project List> to view all open projects and to create new ones. One company may have multiple projects on VeChain ToolChainTM. The enterprise admin can set the number and type of users based on business need.
When you go to <project list> for the first time, it will be empty.
<Project list> in <Project management>
To create a new project for the first time, you will need to select a process template. You have one of two options to locate a template:
- <My Process> gives access to any customized templates created in the <Process Builder>.
- <3rd Party Process> provides a set of detailed templates customized for different specific industry verticals. There is also a General Traceability template, a standardized traceability process template developed by VeChain based on their long-term experience with enterprise customers in different industry verticals. This template is considered the default process template for all ToolChain users.
Project Management → Project List
Once you have determined which template you wish to use, click <use>.
Complete the dialog box that appears and hit create.
The project will take a few moments to complete setup. It will say “creating” until fully provisioned.
Once the project is initiated, you can use the <details> button to further refine the setup of the project through four tabs:
- Profile Information,
- Access Permission,
- Professional Service,
- Operation Log.
Under Profile Information, you can see basic information about the project and make updates. If you need to update the template from <process builder>, you will need to pause the project that’s currently in use by using <Project status>.
You will need to use <Access Permission> to authorize and assign users to collect different data points (based on appropriate access rights). There are two ways to assign access permissions.
In the first instance, you can assign multiple access permissions to a single user.
Click <Set User Rights> and use the dialog box to assign accordingly by checking the boxes for all permissions you wish to assign that user.
The second way allows you to assign a specific authorization to specific DCP to multiple users at a time.
Simply click on which user you want to include and adjust accordingly.
“3rd Party Services” grants third-party service providers the permission to access (and by extension, verify) a particular datapoint in the traceability process. We have been cooperating with third-party agencies (such as DNV GL) to provide diversified and professional verification services. If you would like to know more about third-party services, please contact firstname.lastname@example.org.
To utilize third party service providers for data verification, a business must submit an application and be approved by the provider. Accessing third party verification is not guaranteed, and the providers reserve the right to decline your application.
The process to select and authorize third-party service providers is as follows:
Step 1: Click <use now> to access the professional services application.
Step 2: Complete the application dialog box by selecting your service provider and service name.
Step 3: Check or uncheck which DCP you want to share with the third-party and click submit.
After your configuration is completed, the third-party external verification company will receive your service application, and will check and confirm whether to accept your application. When your application is accepted, the designated data points will be automatically sent to the service provider, and you can view the results at the Console.
All actions that consume TCC in this project will be logged under Operations Log. Normally, project level TCC consumption is DCP uploads/updates and verification services.
Managing the DCP is an essential part of designing your business process template. You access this section by going to <Project List> from the Project Management sub-menu from the Workspace menu.
Once you enter the project list, just click <Enter> to access the DCP management portal.
In the <General traceability process> template, the product information will be recorded at 6 data points:
- Create new SKU,
- bind the SKU,
- Add traceability steps
- customized display information,
- bind group,
- unbind group, and
- landing page list.
You can refer to the Data Collection Process (DCP) and Data Collection Unit (DCU) section under Process Builder Manual for detailed information. ToolChain’s processes enable users to build data fields (i.e. DCU) into identified supply chain processes (i.e. DCP) in a building blocks manner. In this section, we take the <General traceability process> as a generic sample.
Due to the immutable nature of blockchain, you can’t delete data submitted. However, you can update the data, and ToolChain will store the updates to the blockchain so the update history can be reflected on-chain. The user experience across all DCPs in the Workspace is the same. Whether it’s a draft DCP you’ve saved or one that you’ve submitted, click <Details> in the DCP list, and scroll down to click <Edit> to complete the draft or update a submitted one.
Click <Details> in the DCP List -> and click <blockchain records> to see the update history on-chain.
Due to the fact that you are not able to delete a DCP record and the list of records will be long over time, a filter function is provided for you to more efficiently locate your records in each DCP.
Click <Create SKU> -> <New> to complete the SKU form including SKU code, product name, description, SKU image, product parameters, and product files. Sections with an asterisk are mandatory.
Please note that:
- Each SKU is unique, and there will not be any duplicate SKU in the system.
- The size of the image is limited to <10MB, jpg/png file format only.
- You can add up to 50 product parameters.
Click <Submit> to upload the SKU to VeChainThor Blockchain. When the status turns to Success, your SKU has been successfully uploaded. This upload consumes 1TCC.
When the SKU information is uploaded successfully, you can click <Details> to view the records.
<Details> -> <Archive> in the SKU List: if your product is no longer being produced or sold (end-of-life), the admin can <Archive> the product. Once archived, no further operations are available (unless unarchived). Please note that only the admin can archive/unarchive a product.
Unarchive: if the same product is being produced again, it can be unarchived to resume SKU management.
If you would like to bind the products with physical tags (QR codes or chips), there are two options: 1. Bind through webpage. 2. Bind on VeChain Work App.
Here are the steps to bind through webpage:
- <Bind SKU> -> <New> and enter the VID list.
In the VID list, you can click <+> to select the order that needs to be bound with SKU，and choose the quantity of VIDs.
You can <Enter VID> , or <Select VID> to bind it with the SKU.
Select the order that needs to be bound with SKU
Select the quantity of VIDs
- Click Custom ID to bind sku with your Customised ID
- You can select an order to bind all the custom IDs from that order
- Or enter Custom ID number manually
- The last option to enter a custom ID is enter the initial and end Custom ID to add the selected ID range
- Click <Submit> to confirm the chosen VID; or click the drop-down box to choose the SKU. You can <save as draft> or <submit>.
Please make sure the information in VID fits the product. Several minutes after the submission, go to <Bind SKU> to see the status. <Success> indicates it has been uploaded on the blockchain.
View the status of SKU binding
If you would like to view the operation history and data on the blockchain, please click for this SKU <View more>
You can add new traceability information using the web page or the VeChain Work App. Here are the instructions for adding traceability steps via the web page:
- Create traceability information:
Enter <Create traceability information> -> click <New> -> edit the name of traceability, select traceability information and VIDs to be traced -> choose the responsible department -> set track time, latitude, longitude, image, video and other files.
View the traceability information: after you finish inputting the display information, click <Confirm> . Once the status reads “Success”, the new traceability information is uploaded onto the blockchain. You can see all the details in <Details> . Please note: if you have been using the VeChain Work App to collect traceability information, and your operations are not included on this page, please view the history using the VeChain Work App.
Customized display information
<Customized display information> is an additional marketing opportunity section on the consumer landing page. Go to <Customized display information> to upload marketing and brand assets to show to your consumers.. Select the SKUs that need customized information.
You can only upload jpg/png images within 10MB, and MP4 videos within 30MB. You can add or delete the images, videos, and websites.The new page can be saved as a draft and be edited later.
During the delivery process, there will be occasions where many products are packed into a unit or many collections of boxes are packed into a vehicle. For example, wine is packed a dozen bottles in a box. When this happens, you need to <Bind group> , that is to bind VIDs of each wine bottle with the VID of the box, so that you can collect data via scanning the VID on the box and update it to each VID on the bottle. Please note that group VID can not bind to a SKU, it only binds to the product.
<Bind group> can be accessed by webpage and the VeChain Work App. Here are the instructions for group binding via the web page:
Click <Bind group> -> <New> and enter the name of the group, such as box/second grade, pallet/third grade, car/fourth grade. After you submit all the Parent VIDs and Sub VIDs, click <Confirm> to bind.
Add a Parent VID in an existing order, then select other VIDs to bind with it as Sub VIDs. You can also enter existing VIDs to bind with it.
View the information on <Bind Group> : After you submit the binding, it will be processed by the system. When the status turns “Success”, the binding operation has been recorded by the blockchain. You can see the details in <Details> . Please note that: if you have been using the VeChain Work App to bind VIDs, and your operations are not included in this page, please view the history using the VeChain Work App instead.
Please make sure you have completed the unbinding appropriately before the next user accidentally updates incorrect traceability information to the group of VIDs. It’s irreversible in both data upload and TCC consumption perspectives. Can you unbind groups via Workspace or VeChain Work App.
Instructions for how to unbind groups via Workspace is as follows.
- Click <Unbind Group> - enter the name of the group and select the bound Parent VID and Sub VIDs -> click <Confirm>
When the status displays “Success”, the unbinding is completed by the system.
Landing Page List
The landing page is where your end users will see the various DCP that you’ve chosen to share with them. (This is most usually a mobile landing page that is shared with consumers who scan a QR code.)
The Landing Page List page is where you can set up and preview the landing page.
Click <Landing Page> from the left-hand DCP menu, and complete the popup dialog box and confirm.
You will then be taken to the landing page setup page.
Here are some things to keep in mind:
- Publish Setting: Choose “Yes” to make the QR code scannable to end-consumers and allow them to see your landing page.
- Activation content page: all DCPs associated with this project are shown in this section and you can hide or show specific DCP on the landing page, depending on what is relevant to your consumers.
- Set default at the bottom: checking this box allows you to set the landing page as default for the SKU. If you have multiple different landing pages you’d like to apply to different product SKUs, you will create multiple landing pages accordingly.
The Process Builder is a special functionality for the creation of customized business process templates. As this functionality is more advanced, it has its own user manual, located at <Process Builder Manual>.