The TEAMS portal has proved to be a very popular, and valuable tool for many end users to manage their asbestos electronically, but it is not practical to log into several different portals if you work with multiple consultancies. As a result the TEAMS Enterprise system was developed, allowing end users to access and maintain all of their asbestos data from multiple consultancies in one place.
But what benefits does the Enterprise system offer to organisations that work with multiple consultancies? The below will highlight some of the key features of the Enterprise system and how it can be an invaluable tool for your TEAMS suite.
TEAMS Enterprise is able to connect to any number of separate consultancy servers at one time. This allows for reports to be delivered to the Enterprise server as soon as the report has been approved by a consultancy.
Centrally stored, and accessible data
TEAMS Enterprise allows organisations to take ownership and control of their data, as all of the data from multiple consultancies, is stored in one place. This allows Enterprise users to open up access to their data to their own staff and contractors, but also to consultancies that are connected to the TEAMS network. This proves vital when updating sites via reinspection programmes or accepting new data for new surveys.
Access, update and share your own data
As Enterprise stores all asbestos data in one place, Enterprise users have the ability to update and maintain their asbestos records themselves. This also allows sites and data to be made available to multiple parties at the same time with each job effortlessly tracked to the original supplier.
Changes made by Enterprise users are fed back to the asbestos consultancy when a survey is next booked at the relevant site. Below are illustrations of how the Enterprise system works.
The first example here shows data being collected for a brand new survey. Initially the appointment is set-up by the consultancy and this instruction to survey is sent to the surveyor in the field. The surveyor performs the work on site, collecting survey data, samples and photographs. This is then transferred back to the consultancy for processing into the final report.
Once approved within TEAMS, the data is automatically transferred to the Enterprise server where it is stored and made available to Enterprise users.
The second example here shows a reinspection scenario, where historic data already exists for the site with TEAMS Enterprise, and a chosen consultancy is instructed by the Enterprise user to reinspect the site and update the asbestos register. The appointment is set-up by the consultancy and the survey appointment is sent to the surveyor in the field as normal. At this point, the surveyors tablet pulls data directly from the TEAMS Enterprise server. The survey is completed on site utilising this existing data, and any new or updated data added by the Enterprise user.
This is transferred as normal to the consultancy for processing and approval.
Upon approval, the data is returned to the Enterprise server automatically and in turn all of the downloaded data is updated based on this latest visit.
Large scale data capabilities
TEAMS Enterprise is built upon the same data structure that powers TEAMS itself. This includes the ability to safely store, audit and account for the largest asbestos data sets that end users need to manage.
Functions, such as built in data version control, document control and access controls to this data are fully integrated and available within the underlying data storage system, with TEAMS and TEAMS Enterprise solutions.
3rd Party Integration
Where a full data exchange it not required and systems simply need to hand over to TEAMS Enterprise, smart links can be created and embedded into your applications which direct the user into the TEAMS Enterprise portal system at the correct level (whether that be site, room or item) for them to gain access to the information they require. This method allows for very little coding, but achieves instant results in terms of delivering data to the end user.