We can approach architecture for other implementers

Blog post
edited by
Wiki Admin

For a large majority of consulting companies both design and implement for ALL projects.  Though profitable for many firms, the best design can end up biased towards the agenda of the implementer which may be to sell more components, get more bodies. Now, we have the capability to implement architecture, but our end goal is not to design an architecture that is for us to implement, but an architecture that is implementable. 

Many times, the client knows that the implementer will design with a bias, so the client chooses to or must design blind without considering the maturity of what an implementer can provide. In those cases, we can come in, architect, and be a third party to help do the concept, design, and design the requirements and performance work statement basis.

This approach with these services buy-back risk to your implementation and increase the likelihood of achieving your metrics and goals.

  • In Architecture, We can design and not implement. Though all our designers come with deep experience in implementing, and we can, in cases as independent designers, we can provide the best design recommendations without bias for implementation.
  • In Management Consulting, we can stand-up program management, execute a program management or governance support in lieu of existing support, or transition to existing support. 
  • In FedBiz, we train, support, and consult implementers on federal business management, so they can focus on delivering a solid implementation. Quality contractor support to implement a design, project, or program is hard to find. Compliant, Responsive, Reliable is even harder in Government space
  • In Communications, we help promote the transformation effort
  • In Research, we continually re-invest in new models, patterns, and constructs that go back into our designs.

 Why do we do it? We are all stuck if there are not good implementers or integrators to implement the designs, so it is more important for us to see the transformation designs move forward.

Whiteboarding Data.gov and Geoplatform Original Vision

Blog post
edited by
Matt Tricomi

During the same week Xentity Team members presented on the data.gov and geoplatform integration vision at the International Data Conference, we had the opportunity to hold an information sharing exercise and whiteboard sessions with FGDC and data.gov executive sponsors to capture What does geodata.gov mean to data.gov.

In this session, we covered various user stories on the haves and have nots for the current data suppliers and what our analysis is suggesting data users want and how they want to access the data. Finally, we had discussions on how data.gov, geoplatform.gov can work with agencies to get these services funded and how geoplatform could serve the community.

The following captures a series of potential services that agencies may be requesting on geoplatform.gov as it unfolds. As the concept of geoplatform is for agencies to build out services as it sees fit and geoplatform.gov is more of the conveyance, governance, and service provider, how the actual services unfold could go anywhere.

 

 

What does geodata.gov mean to data.gov

Blog post
added by
Wiki Admin

During the First International Open Government Data Conference in November 2010, Xentity Geospatial Services and Architect Lead, Jim Barrett had the opportunity to present alongside colleagues such as the OMB Federal CIO, CTO, Sir Tim Berners-Lee and several other name-dropping figures in this space.

Jim, at the time part of the XPN as independent consultant, presented on our recent conceptual architecture work for data.gov that looked to integrate the previous administrations geodata.gov. Geodata.gov open data registration accounts for over 80% of all data in data.gov, so its by all means a major impact to where data.gov would need to focus.

The conference appears to continue as a bi-annual event with the last one being held in July 2012

The following captures the extended version of his presentation:

Xentity supporting scanning maps

Blog post
edited by
Wiki Admin

Xentity won multi-year work to support creating high-quality scanned maps. See the handout on this program.

The USGS Historical Quadrangle Scanning Project (HQSP) is scanning all scales and all editions of approximately 200,000 topographic maps published by the U.S. Geological Survey (USGS) since the inception of the topographic mapping program in 1884. This scanning will provide a comprehensive digital repository of USGS topographic maps, available to the public at no cost. This project serves the dual purpose of creating a master catalog and digital archive copies of the irreplaceable collection of topographic maps in the USGS Reston Map Library as well as making the maps available for viewing and downloading from the USGS Store and The National Map Viewer.

Staff from Xentity supported the arduous process for scanning and cataloging. The Madison, WI based staff over a couple calendar years were able to complete these very high-resolution scans. The process required an eye for detail and to not be complacent with simply getting the job done. The tasks included:

  • converting printed scientific reports and maps to an electronic format
  • create geo-databases for containing the scientific reports, maps, and satellite imagery
  • scan multiple scales and editions of the more than 75,000 reports published by the USGS since 1879.
  • accurately referencing the Geographic Names Information System and Topographic map metadata and data dictionaries for project completeness
  • Creating, managing, and running the metadata QA/QC process and metadata verification processing.
  • Maintaining end user documentation
  • Creating batch scripts for post-processing of image files.
  • manipulating the resulting scans in multiple GIS formats
  • Maintaining databases and front-end catalog systems