|
CNSI provides a wide range of EA development and support services, including EA development, governance processes and procedures, Capital Planning and Investment Control (CPIC), legislative compliance, EA Assessment, and the entire EA Life Cycle (EALC) – Framework and Repository Tool Selection, As-Is, To-Be, Gap Analysis, and Transition Plan Development.
|
Framework and Repository Tool Selection : Central to the development of any EA is the selection of the Framework upon which it is built, and the repository in which it is to be stored. CNSI can work with the well-known frameworks (Zachman, DODAF/C4ISR, FEAF) as well as developing custom frameworks based upon them. CNSI is familiar with all major repository tools, including ad hoc tools for repository development.
Legislative Compliance : Federal EA efforts are driven by and accountable to legislative drivers, and must conform to these drivers. The legislation includes the Clinger-Cohen Act, the Government Paperwork Elimination Act, and the President’s Management Agenda.
Enterprise Service Bus (ESB) : The development of integrated EA components relies upon standards of data communication across the Enterprise, via an Enterprise Service Bus. This is the mechanism by which standard communication is enforced between services within an Enterprise.
Service-Oriented Architecture (SOA) : An Enterprise relies more than ever on a collection of inter-operating Services rather than a set of stand-alone legacy “stovepipe” systems. An SOA is the method by which this set of Services is developed and maintained.
FEA Expertise : Development of an EA for any Federal Agency requires the use of the Federal Enterprise Architecture Framework (FEAF) model. Use of the FEAF requires knowledge of the model and its constituent Reference Models (Business, Data, Performance, Service Components, Security, and Technical).
EALC : Development of any EA involves a standard Life Cycle consisting of (at a minimum) Stakeholder Buy-In, Framework Selection, Tool Selection, As-Is EA Development, To-Be EA Development, Gap Analysis, Transition Plan Creation, EA Usage, and EA Maintenance.
FEA Assessment : The Office of Management and Budget (OMB), in addition to enforcing the Clinger-Cohen Act (the development of Federal EAs), has also mandated the assessment of Federal EAs. The assessments are designed to show that the developed EAs are actually being used to improve aspects of the Federal Agencies to which they belong.
MITA Assessment : The Department of Health and Human Services is using a variant of the FEA, the Medicaid Information Technology Architecture (MITA), to develop architectures for states in the Medicaid program. These architectures include the Medicaid Management Information System (MMIS) technologies that process Medicaid information. The Centers for Medicare and Medicaid Services (CMS) are the owners of MITA and its assessment mechanism. Over time, all MMIS systems will be expected to pass a “MITA assessment” that shows a maturity level and a plan for improving the maturity of the MMIS.
|
|
 |
|
