This a rewrite to a common codebase with Earthwork but it is a standalone program. There is no dependence on Sitework/Gradework and Underground is not integrated either. The basic concept is:

• A shared file format. The MK3 goes away
• Users should not have to ever re-enter data (high on the annoyance factor
• Whenever possible the interface and way of doing things is identical
• The toggle between programs feature of Trackwork/Gradework is integrated although perhaps smaller for space
• The data flow is omnidirectional. It can flow from Materials to Sitework and vice-versa.

• Structures List - Multiple Lists, Master Lists on Access,
• Materials List
• Phases - Phase Regions
• Work Layers
• Entry - Lengths, Areas, Counts, Documentation Elements
• Printing - Single sheet Reporting, Layout
• Import
• Export
• Reporting - Sorting, Filtering

• Use/Applying Materials Areas as Sectional Areas (designating whether an areas should be used as a sectional areas)
• Adding Structures List to Region Entry in Sitework (Revamping of Sectional Entry for interaction with Structures List. Augmenting Line Editor for Sectional entry.)

Floating palettes during entry. May require right-click ala Sitework to go into an intermediate mode for selection of different structure

Work Layers - A user nameable organization method. For example we might create a demolition work layer with several phases.

Materials Calculator? Typing in calculations for structure entry (ie 1.4'/12) etc. or a dedicated calculator for common conversions.

User created PNG symbols - Also exported to Google Earth and supporting transparency. SVG too?

Filtering on reports reflected on graphics -

• Essentially two way filtering
• Wildcard supported

Support for PNG/SVG User patterns

Some early screen element prototypes. More designed to show the complete screens rather than steps.

This is an amalgamation of the existing materials and sitework where appropriate. The descriptions are: L-R

• Home
• Pan
• Area Select
• Layer View Control - This is new to materials but could easily be used to control visibility from one place rather than the series of places that Materials currently uses. Thing of a Work Layer, by structure, or phase control. All in one place
• Show Areas - in Materials now
• Show Lengths - in Materials now
• Show Counts - An odd oversight in the old materials program
• Show Annotation - Materials now
• Select by Line label
• Enter Benchmarks
• Offset Lines
• Templates - We don't have elevation in Materials but it seems useful to be able to create multiple lines at once with labels for materials entry.
• Join - In materials now
• Swap Ends - In materials now
• Trim - In materials now
• Force Close - In materials now
• Send to print page - In materials now
• Note - Match the documentation layer in sitework for KMZ output

Do we support Cost Codes on Structures or Materials?

Adding columns of user defined data

• Cost Codes
• Accounting codes
• Essentially freeform strings - User names the column and enters the string. Should it be part of structure and and a Material? Allows for searching

Shared Structures, Materials, Cost Code lists to and from AGTEK Access. The cost code list is already supported by Access.

Cost Codes as part of output (for HCSS, Hard Dollar, for Subs)

• Import
• PlanView
• ReportView
• Report/Plan Split View
• Print Page
• Edit
• Entry

• Home
• Pan
• Area Zoom
• Send to Print Page
• Area, Length, Measure View Filters

• Materials
• Select All
• Offset
• Join
• Swap Ends
• Close Line
• Trim Annotation

Modes moved up Ala' Sitework 4D

Joe Customer needs to bid a job and gets the PDF plan set. It's got demo, dirt, & paving on it. First step is he starts Materials and Imports the PDF sheets he cares about. As Allen explained it's often about getting info out to subs for their bid.

• Structure Measure - Detail and Summary
  • Structure name, color, pattern, type (area length, count), phase, class, seq (kill), count, area length
• Structures - Detail and Summary
  • Structure name, color, pattern, material, type, phase, class, seq (kill), measure, section, multiplier, quantity, units
• Materials Report - Detail and Summary
  • Material, type, structure name, color, pattern, phase, class, seq (kill), measure, section, multiplier, quantity, units

I haven't found anybody who uses sequence and I believe it's a vestige of the old Edge Materials that didn't have onscreen reporting for identifying item. I suggest we kill it.

Dave has a floating Report window that's a natural to float on a second screen although it can be docked like the existing one.

This example can be copied for the other reports. The primary change is the addition the code field that's sortable. Likewise the Materials report would use the code attached to that material. This is just a string designed to make integration from other systems easier.

Other changes include a visual separation between Structures, elimination of sequence, a different symbol and representation of holes instead of just negative values. A slight bolding of totals. At the bottom are buttons to print directly, send to the print page, export the results (csv, XML?, Json?) and close.

All fields allow for sorting on any column

Probably not on first release but the Report window could also serve as a unique way of reporting and filtering what is shown on the screen and reported. I'm guessing it's not possible on the first release. The idea is being able to pick any field and apply a filter based on it. For example, right clicking on a Layer cell displays a menu that allows sort changes, clearing a current filter on that column, or setting to only show that value or the inverse. Numeric values could allow greater than or less than values like Greater than 10,000 or less than. The ability to cascade filters among multiple values creates very specific reports with far greater flexibility than just the phase and work layer method and also controls visibility.

When a customer has both Sitework/Gradework and Materials one of the benefits of a shared file format is the ability to designate Sectional areas with a Structure from the structure list. Likewise, Materials Structures should be able to be designated for use as a sectional area in Site files.

This is the current Report Region Dialog modified to add the Structure information.

NOTE: The program currently brings up the Line Editor for Sectional Areas and Report Regions. It should really bring up this window instead

Notice that the Sectional Depth is greyed because the Structure is set from the Structure list. The buttons to the right of the Structure combobox are to display the structure list and add a new structure. In the case of adding a new structure we'll display the Structures windows.

And when a Structure is picked the Sectional depth is applied from that structure value and the Materials breakdown displays below it.

There's many times when the materials takeoff is done before the earthwork. In those cases we'd like to be able to apply the Area Structures as Sectional Regions in the Earthwork takeoff but that likely has to take place after the Design data is entered. In fact the user doing the sitework takeoff will likely want to snap to some of the Materials entries.

My proposal is that we add a Materials Layer. Not only does that allow segregated information that users can snap to but it also provides the beginning of a mechanism to tell the program to use an area also as a sectional area/report region. In this view we should also support the saved colors and patterns of the structures rather than the randomized ones currently done by Sitework.

While Earthwork could have this functionality I'm going to argue that this belongs in Materials to broaden our Materials only market. It actually adds the first element of 3D as well and starts the trend to make Materials a full fledged product line. If the customer does have Sitework and Materials we can leverage capabilities like conform, etc. but it has to be allowed to work standalone.

Automated machine control systems use to just read a 3d Polyline and use that for guidance. They've evolved to require COGO representations instead and that includes two lines for the curb and the centerline for the stationing. That includes both horizontal and vertical COGO. The output mechanism of choice is LandXML.

While we can offer advantages to Leica paving systems the export model extends to other brands. Some of the chief Leica advantages are the ConX connection, the use of mobile apps in demo, and our support.

Our advantages are broadening a market to companies outside of earthwork, mobile app proliferation, and expansion of tracking to paving tracks.

• Read the CAD File (geometry)
• Allow the user to tag by layer or individually geometry that's going to be used.
• Organize that data by work layer in Materials
• Ideally we'd retain this identified geometry using the same geometry even if we represent it onscreen as a polyline
• If the data is already 3D then we provide an interactive point review method on that data. If it isn't 3D or is wrong we provide an editing method ala' Sitework functionality to modify the line
• Create an Export LandXML dialog that not only allows layer export modification (color/name/inclusion) and include the capability to write it to ConX.

Happy Path

CAD file contains necessary lines specified as COGO and has three-dimensions