Trimble Work Os
Eleanora Parrot
Increase construction job site productivity to stay on schedule and on budget. Track your work and jobsite data from the field with Trimble WorksOS, created for site supervisors and project managers to maximize jobsite efficiency. Explore our advanced construction technology and new cloud-based operating system delivering 3D productivity and real-time progress to plan, remotely, with critical project information straight from the machine. Never question the status of your construction jobsite progress and get a complete view of your progress to plan data to improve construction operations with our site management tools.
Easily track work completed vs work remaining on your construction project to save costs. Drive your equipment and jobsite machine activity from a central site design for real-time progress versus plan updates from the field. Allow for your construction design to model and shift the work as it changes, making sure you get the best utilization out of your machines. Translate your job site machine data from the field into timing and cost savings for the project with Trimble WorksOS.
Avoid costly re-work with WorksoS. Get complete visibility at your fingertips with real-time job site productivity data with Trimble WorksOS advanced construction operations management software. Automate field data collection for accurate, real-time information about the progress of work done with respect to the design in terms of production quantities, area graded or area compacted. With WorksOS, we provide transparency across your entire project and organization so operators and supervisors can make smarter on-site decisions.
View progressive volumes of earth moved over time to understand and analyze site productivity trends. Establish and visualize an advanced plan of project execution with emphasis on movement and flow around the jobsite. View and export accurate and real-time cumulative volumes, presented in daily or weekly totals, as a graph, table or map. Get status and on-time completion transparency for your construction operations with Trimble WorksOS jobsite management software.
WorksOS is recognized as one of the most significant new products announced in 2020 by leading construction publications. These awards aim to emphasize innovations and highlight those who are investing in research and development.
We make it easy to track how your construction project is progressing and improve productivity on the jobsite. Schedule a personal walkthrough to learn how our construction technology solutions can help you.
Drive productivity and profitability with an all-inclusive connected construction solution for a low fixed monthly price. To learn more about the Trimble Works Plus Subscription, visit civilconstruction.trimble.com/subscriptions.
Works manager has an in built file flipper which is handy if you have machines running GCS900 and the Earthworks system on the one site. It allows you to create your svl and svd files and upload to both systems in one go.
If you have both systems like Edward has said it speeds things up. It is better also because of geo fencing so the designs are only on assigned machines. Also transfering data to Siteworks is now supported. But it still s new system so it has child diseases sometimes.
I have used both and I must say that I prefer WorksManager. I know that they are working on creating a work flow to get things from TBC directly into WorksManager in the near future so I have been told. Although I have yet to use it, it sounds like you will be able to use WorkrsMananger to connect to you data collectors as well and manage your data through there. At this time I only use TCC for my TSC7 & T7's. The one thing I do like about WM not being tied to you design in TBC is that if you are doing some changes or revision or anything in TBC that might create a conflict with a design it doesn't make you update the machine file. WM is the future and TCC will go away I have been told.
I had one test project, then a machine with Earthworks overlay V.1.10 entered the site and it did't get the design. So the Earthwoks was upgraded to V 1.11 and then it got the project but the coordinate system didn't work had error of cm in the beginning and ended up in WGS 84 height that shows 60m upp from our local coordinate system. No way was to get out of this. we had to factory reset the Earthworks and install V 1.10 again.
WorksManager will be a good platform when they get it where TCC is today, that is no where near the case as it is now lots of things need to be added to accomplish the tasks you can do in TCC. One of the main things is the folder layout you can not remotely get a calibration file from your field crew to WorksManager without TCC. there are a lot of bugs in WorksManager you can't sort jobs by name or anything else your stuck with when they were created, anyone one that has access to your account can delete anyone else, you can't assign roles only admin access. no way to archive jobs for future use if inactive. IBSS bases can't be sorted by name connected devices are serial numbers with no description field if you want to know who is connected pull out a piece of paper to reference serial number to, with 65 units connected that is a royal pain. reporting of GCS devices is sporadic sometimes 15 min other times up to 60 min. in time maybe they will get it where it needs to be as for now I need to use both platforms to do the job TCC can do.
Agreeing with the comments above. We have two EW 2.0 machines that will not sync with WM for the past two weeks. I heard there was a system wide reset on Friday to correct some of the issues. Besides that issue, i like how the file conversions streamline the process of sending out files to the field. Also it becomes a little messy on a project that has has many changes to the design as the versions keep piling up on the machines. We have started creating a new design and deleting the old instead of having so many versions of the same name design(V.01 V.02 etc). I think this will be corrected though as the platform ages.
Tom,
I also have a sync issue with Earthworks 2.0 not working with Works Manager the sync fails during file transfer, if i use the web interface and uncheck every project but the one im am trying to sync that works sometimes but not always
I am curious how other users handle points from the field software, both SCS900 and Siteworks or other, and the transfer between the field software and TBC. And potentially from TBC back to the field software.
This is something I have tried to improve over the years and have had some success but still have not perfected the process. Do other people have this issue or has someone found a sure way to keep things clean and organized?
When we initially started with Trimble we were trained to use the measure command when you were measuring stuff; stockpiles, utilities etc. Stakeout was more for QA/QC of staking a model surface. Yes you can use stakeout for recording points of a line but you get the tolerance screen that yells at you every time. You also do not get connecting points as a line (without the fancy codes that is).
We have a few projects that have multiple foreman on a project. Most of our projects will have more than one foreman that will be on a job. What is the easiest way of sharing point data? I could easily take all of the points from foreman 1 and dump them on one layer and work order to give to foreman 2 but I feel like that is not helpful or productive.
The closest I have come to getting this more usable is to "connect the dots" and provide Foreman 2 with layered linework and then put all of foreman 1's points as stakeout points. However, this creates an all or nothing scenario for viewing previous points by toggling on and off the stakeout points.
I would not use Work Orders as a means of sharing this data with others. I can talk to the Logic of SCS900 as it was when we created it first many years ago and the philosophy has not changed much over the years
While it may be perfect today, I know Steve DiBenedetto and Casey Cyrus are working on this currently and I would suggest that you try to influence their development efforts to make this a stronger solution using VCL.
I agree that adding as-builts to the design or maybe even a separate category for as-builts would be the best way. Create a new spot for historical point data. Maybe lock the points down but definitely give an option for the user to edit or add information; valid, invalid, notes, fxl codes. From what I am seeing, the only thing that is missing from adding these points to a vcl is the points layering for organization.
I agree with not sharing working order. Those works orders should be unique to the person that started them. But without a lot of prep work, there is not a quick way passing this information along currently. Especially when you get a last minute phone call that XYZ is on site and needs info. Sometimes I just do not have time to clean up all of the points and create this as linework to pass on because I am given too short of a notice. Never mind presenting the points in a clean manner. Nor is it necessarily warranted. The features installed should be close to the design, it is more for a sanity check and verification of where stuff may have deviated or actually elevation.
Adding this information to a design/as-built group and the ability to layer points, I could grab all the points from a work order and add these to a new selection set, maybe rename so that you don't get duplicates and you know that these are definitely as-builts (add a prefix such as SEVAB) and then export these to the field, then the new foreman would have these to use and create work orders to track their data, and I could bring this in and keep appending it to that TBC file. You wouldn't have to worry about duplicate work orders with overlapping points and each foreman would have their own true data sets, which is what I tried to do from the start but that had some issues. So you would have something like gravel-JS and gravel-pl, as-builts-as and as-builts-pl. That sounds like a better workflow on all fronts. I think this would also tie in nicely with WorksManager.
c80f0f1006