- Working Model [not distinct enough]
- Working Model Engineering Framework (WMEF)
- Western Massachusetts Enterprise Fund
- FM-106.5, Fort Kent, Maine
- Integrated (Civil) Engineering Modelling
- Modelling Environments
- Shapes (Boundaries?)
- Test Conditions
- Constraints (Code Compliance)
- Data Input/Summary and Reports
- Graphs and Charts
- 2D Projections
- 3D Rendering
- Data Conversions (I/O)
- Data Sources/Citations
Typical Data Flow
Raw ==> Triples <=> XML? <=> Editing Screens ==> Database <=> Application
Re: The Mandatory Three, The Easy Road to Success, and Relevant Inexperience 2008-11-25 14:41 • by Heron230886 in reply to 230850 Reply Quote
Jay: “And in a similar vein, when I worked for the government, there used to be a rule that we could not buy anything without getting at least three competitive bids, and then we had to fill out forms showing how we compared these bids, and if we didn't pick the one with the lowest price, justify why another was clearly better.”
The company I work for makes water modeling software for civil engineers, and this software is used quite often by government agencies (e.g. the Federal Highway Administration). They are required to get at least two bids before they can buy our software.
So what's our solution? We own a subsidiary (with one employee who “also” works for us) which resells our software for $5 more. We offer our software for $x, the subsidiary offers it for $x + $5. This appeases the government's bureaucracy (since multiple bids were available) and we get our sales. The government is aware of this situation, but because legally they're two separate companies offering bids, they don't care.
What's funny is that (as far as I'm aware) there isn't a competing product from another company, so if there *wasn't* a second bid, the government simply couldn't buy anything at all with which to do their work.