Technically Speaking

The challenge of easily procuring new technology is the Old Faithful of federal IT. Regardless of the year, it’s an issue that keeps coming up. In fact, judging by a recent survey of federal IT pros at SolarWinds, procurement challenges are erupting more than ever before.

Building Information Modeling (BIM) is changing the way both the public and private sector work together to design, communicate, solve problems, and build better projects faster and at less cost. As BIM practices and technologies continue to evolve, what does the future hold? From mobile-enabled BIM to simplifying the prefabrication of building materials, this new white paper takes a look at the Top 7 BIM Trends that are Game Changers for the Public Sector. We've summarized the highlights below:

Running a large organization, private or public sector, requires a lot of IT and as technology has changed and matured data centers have exploded in number and size. As data centers grow in operational costs in a climate of shrinking IT budgets, efficiencies are being sought out in all areas; from people to support the equipment, the real estate that equipment occupies in the data center, to the power needed to both run the servers and to cool the building.

I am not going to go into the holy war of the JSON vs YAML discussion. That is something that should be left to folks that have time and willingness to discuss this, just like discussions of OS X vs Windows vs Linux, or VMware vs Xen, or iOS vs Android, or …the list could continue way past this blog. But this blog is not to discuss either/or. It is to show you a way to convert from one to another to ease the pain of dealing with one or the other side. Let’s take a simple JSON template for DynamoDB table creation in AWS.

I have always been a big proponent of making 3D views with a section box to better understand design iterations and the relationship of the parts of the building model. Taking this to high detail and illustrating a segment of the model to resolve design issues quickly can result in having to make several, if not dozens, of views during schematic and design development phases.

Government agencies are under increasing pressure to move to more agile development and operational methodologies. But what does this mean for existing legacy environments? Actually, agile development and operational methodologies can be achieved in legacy environments. The answer to this problem is rooted in IT automation, which serves three purposes: