FEA Reference Model Detailed Descriptions Sample Clauses

FEA Reference Model Detailed Descriptions. ‌ Enterprise Architecture (EA) supports planning and decision-making through documentation and information that provides an abstracted view of an enterprise at various levels of scope and detail. The Common Approach to Federal Enterprise Architecture, released in May 2012 as part of the federal CIO’s policy guidance and management tools for increasing shared approaches to IT service delivery, presents an overall approach to developing and using Enterprise Architecture in the Federal Government. The Common Approach promotes increased levels of mission effectiveness by standardizing the development and use of architectures within and between Federal Agencies. This includes principles for using EA to help agencies eliminate waste and duplication, increase-shared services, close performance gaps, and promote engagement among government, industry, and citizens. The Federal Enterprise Architecture Framework v2 describes a suite of tools to help government planners implement the Common Approach. At its core is the Consolidated Reference Model (CRM), which equips OMB and Federal agencies with a common language and framework to describe and analyze investments. It consists of a set of interrelated “reference models” that describe the six sub architecture domains in the framework: • Strategy • Business • Data • Applications • Infrastructure • Security These are designed to facilitate cross-agency analysis and the identification of duplicative investments, gaps and opportunities for collaboration within and across agencies. Also, by applying all six reference models, agencies can establish a line of sight from the strategic goals at the highest organizational level to the software and hardware infrastructure that enable achievement of those goals. Collectively, the reference models comprise a framework for describing important elements of federal agency operations in a common and consistent way. To apply the framework to an agency’s specific environment, the agency should develop a set of “core” artifacts to document its environment within the framework presented by the CRM. Each subarchitecture domain represents a specific area of the overall framework and has particular artifacts, based on EA best practices, which are described and recommended in the Framework and Artifacts document. The type and depth of documentation actually used by the agency should be guided by the need or detail and answers to questions about requirements, applicable standards, timeframes, an...
AutoNDA by SimpleDocs
FEA Reference Model Detailed Descriptions. Enterprise Architecture (EA) supports planning and decision-making through documentation and information that provides an abstracted view of an enterprise at various levels of scope and detail. The Common Approach to Federal Enterprise Architecture, released in May 2012 as part of the federal CIO’s policy guidance and management tools for increasing shared approaches to IT service delivery, presents an overall approach to developing and using Enterprise Architecture in the Federal Government. The Common Approach promotes increased levels of mission effectiveness by standardizing the development and use of architectures within and between Federal Agencies. This includes principles for using EA to help agencies eliminate waste and duplication, increase-shared services, close performance gaps, and promote engagement among government, industry, and citizens. The Federal Enterprise Architecture Framework v2 describes a suite of tools to help government planners implement the Common Approach. At its core is the Consolidated Reference Model (CRM), which equips OMB and Federal agencies with a common language and framework to describe and analyze investments. It consists of a set of interrelated “reference models” that describe the six sub architecture domains in the framework:  Strategy  Business  Data  Applications  Infrastructure  Security These are designed to facilitate cross-agency analysis and the identification of duplicative investments, gaps and opportunities for collaboration within and across agencies. Also, by applying all six reference models, agencies can establish a line of sight from the strategic goals at the highest organizational level to the software and hardware infrastructure that enable achievement of those goals. Collectively, the reference models

Related to FEA Reference Model Detailed Descriptions

  • Project Description In two or three brief sentences, provide a concise description of your exhibition. Include the subject matter, type of objects to be included (paintings, sculpture, manuscripts, etc.), those responsible for organizing the exhibition, and catalogue author(s).

  • Detailed Description of Services / Statement of Work Describe fully the services that Contractor will provide, or add and attach Exhibit B to this Agreement.

  • Budget Schedule Subrecipient agrees that the expenditures of any and all funds under this Contract will be in accordance with the Budget Schedule, a copy of which is attached hereto as Attachment C, and which by this reference is incorporated herein and made a part hereof as if fully set forth.

  • Recovery Schedule If the initial schedule or any current updates fail to reflect the Work’s actual plan or method of operation, or a contractual milestone date is more than fifteen (15) days behind, Owner may require that a recovery schedule for completion of the remaining Work be submitted. The Recovery Schedule must be submitted within seven (7) calendar days of Owner’s request. The Recovery Schedule shall describe in detail Construction Contractor’s plan to complete the remaining Work by the required Contract milestone date. The Recovery Schedule submitted shall meet the same requirements as the original Construction Schedule. The narrative submitted with the Recovery Schedule should describe in detail all changes that have been made to meet the Contract milestone dates.

  • NASPO ValuePoint Summary and Detailed Usage Reports In addition to other reports that may be required by this solicitation, the Contractor shall provide the following NASPO ValuePoint reports.

  • Product Description The lead products covered by this Settlement Agreement are limited to following Amazon Identification Number (ASIN) B07CZ1Z8QK, with the description, "63/37 Rosin Core Solder Wire Flux 2% Tin Lead Solder Iron Welding Wire Reel 0.5mm-2.0mm 50g/100g," which was offered for sale by the Settling Entity on xxxxxx.xxx, hereinafter the “Product” or “Products.”

  • ITEM DESCRIPTION Equipment (include VIN, make, model, year, serial no., accessories, or other identifying features): 12. NO. OF OPERATORS PER SHIFT 13. HRLY/ DAILY/ MILEAGE SHIFT BASIS 14. SPECIAL 15. GUARANTEE (8 HOURS) Portable Toilet Rental – Serviced(Includes first day delivery/last day pickup and daily rental rate per unit) 1 $75 Daily Ea. Portable Toilet Rental – Unserviced(Rental only, no daily service call) 1 $45 Daily Ea. Accessible Portable Toilet Rental – Serviced(Includes first day delivery/last day pickup and daily rental rate per unit) 1 $95 Daily Ea. Accessible Portable Toilet Rental – Unserviced(Rental only, no daily service call) 1 $65 Daily Ea.

  • Shift Schedule The words "shift schedule" when used in this Agreement shall mean a timetable of the shifts and off days assigned to a position or group of positions which commences at the beginning of a pay period and includes one complete rotation of said shifts.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!