In early December 2011, Xentity architects had a chance to discuss future progression with OMB current and former Chief Architects. The following captures some of the concepts discussed for architecture in context of the overall IT progression in Federal Government both looking back at where IT has been, but given current initiatives, but could be further emphasized, integrated, or uncovered moving forward.
IT originally was built as a Federated cost center. IT moved into Agency Data Centers model for archive/records. Commerce Models of economy drove eGov without migrating IT to Service models. Govt swamped in the T of IT, haven’t got back to the I.
IT Acquisition originally was about financing/leasing federated shared manufactured systems Then Client/Server came, which is solution architecture, and 1000s of stacks came. Acquisition never got trained or linked with EA, and engineering mostly got outsourced
Federated Regional Centers moved to Mission Centers moving to Server Rooms due to 1000s of system configurations. Initial FDCCI will close 1/3 of the portfolio count, but other 2/3s will have high transition costs
IT stack started monolithic and slowly moved into server tiers then into service components. Though reduced individual system develop. cost, O&M Total Cost of Ownership was ignored and system security and interoperability was low.
– Institutionalized Funding for Enabling G2G IT Services at GSA
– Position G2C Services as High-Available Service Centers
– Focus Mission on Data Services training on Data Lifecycle that allows Private, NGO, Citizens to build on top of
– Increase EA role in support of mission and policy analysts for depth reach back to increase new political appointee effectiveness and limit turnover/ takeover disruption
– Position EA as depth knowledge base for acquisition guidance reachback
– Train all 3 workforce components on Performance maturity, Common Stack Architecture, and FEA/FSAM v2
– Establish CIO and EA relationship formerly with Acquisition
– Retire ineffective, existing burden to demonstrate credibility, eating own dog food, and increase success chances
– Increase CMMI/ITIL Requirements to lower O&M
– Continue FDCCI
– Guide 2nd Consolidation Phase through taking advantage of CPIC renewal or new system cycles to assure re-use of new platform or data services in new shared platform environments to avoid simple hardware/system “cowpath” migration
– Establish a Common Stack Architecture to be cloud managed service platforms by Select Large Agencies, waived Large Programs, and GSA
– Manage a True Common Stack Portfolio definition and implementation status
– Target New Solutions and Existing Systems for collaborative evaluation