Like the list, they look so deceptively simple to make don't they?
Our SWJ community has been happily bashing powerpoint the last week... so how do we transform the resulting information into knowledge? Back in the day we did acetate overlays on maps for the Army side of my life. I guess that's part of why I enjoy Arcview so much on the civilian engineering side. Here is a typical algorithm:
1. Take geotechnical samples at set intervals, depths, and locations.
2. Use the resulting information to paint a picture of the existing underground stratigraphy.
3. Match engineering properties to each layer - ie the ability to carry a set load (ie ~2,000 pounds/sf for sand, much more for rock depending upon type), exhibit permeability (I worry about waterflow - clay cores vs. sand cores), etc.
4. Analyze data via finite element modeling to identify weak and strong areas
5. Develop a statement of work or design, cost estimate, and project schedule.
6. Get a construction specialist to build the sucker and inspect the heck out of them for QA/QC
Beyond all of the calculations paper/calculator/excel/mathcad/proprietary calculation programs we capture and share the geo-referenced knowledge using AutoCad Civil 3D (not applicable for our SWJ project) and Arcview before, during and after the project. We also use powerpoint
While developing/evaluating a business plan for a small group of investors we use excel, google earth, typical business metrics for our reference industries, capital budgeting techniques, marketing, and lots of shoe leather.
It may be just me but I see many parallels between the civilian side and the military side when we wisely decide to address the non-kinetic part of life in our solutions. Governance, economics, and security covers alot of ground...
Bookmarks