GDC780BE21 3BHE004468R0021 高压变频器主板

GDC780BE21 3BHE004468R0021 高压变频器主板 

描述资源（物资、信息、执行者或地缘政治）的期望状态
范围。）目标数据可以表示为企业目标、战略目标，即：
适用于整个组织，或作为定义所需的更具体的运营目标
工作过程的结果。
数据组描述
关于目标数据组，应注意以下几点：
a、 虽然语言听起来不同，但预期效果的含义（变化
某些对象的状态）与目标的含义相同。
b、 某些对象状态的所需更改会导致受规则约束的活动
由表演者执行。某些活动被视为事件，因为：
它们相对于视觉的辨别框架具有接近零的持续时间，
表演者等。
c、 在DoDAF中，确定和描述目标，为活动和
以使这些活动朝向期望的效果。当执行者执行
活动，执行者在活动规定的限制范围内执行
（规则）并以期望的效果为目标。这种效果要么满足，要么有助于
实现反映组织愿景的既定目标。
核心流程中的使用
目标是在组织的各个层次和国防部的每个核心过程中制定的。
目标可以应用于企业或解决方案架构工作。目标特别重要
对于从事体系结构开发工作的团队评估以下方面的成功非常有用：
努力以及努力如何有助于实现更别的目标、使命
需求、能力开发或服务和系统开发，以支持
部门或组织业务运营。
目标数据有助于：
a、 确定活动范围，以确保在执行活动时使用的资源有助于
组织的总体目标和愿景。
b、 建立执行活动的规则，以创建边界
效率和有效性（约束条件），并确定以下情况
其中执行活动（事件）。
c、 确定确定活动成功与否的措施，符合
这是既定的目标。
出身背景
建筑发展
元模型
概念的
必然的
表演者
资源流动
信息和数据
规则
目标
能力
服务
项目
物化
组织结构
措施
位置
纯种
PES
思想基金会
本体论
观点和模型
展示技巧
配置管理
概述
缩略语列表和词汇表
术语
网站地图
档案
国防部
60
DM2-目标
http://cio-nii.defense.gov/sites/dodaf20/goals.html[2011年3月3日下午3:43:20]
项目数据可通过以下方式用于六个核心流程：
a、 JCIDS：建立所需和阈值能力。可追溯性应始终
保持在目标和能力之间。这应包括措施、规则和
纯种
b、 PPBE、DAS、SE：在设计、开发和
收购过程。各个级别的可追溯性对于
适当管理和控制成本、系统工程和采购。
c、 运营计划：在制定运营计划时，确定目标和目的
与特派团有关。目标可以描述为战略和战术。
d、 CPM：建立投资组合的技术和计划方面。
演示
目标通常以表格或文本形式描述。目标好以
以结构化的方式显示主要目标和衍生目标。这增强了项目
可追溯性。
转到页面顶部↑
隐私政策|网络政策124;联系人
61
DM2-能力
http://cio-nii.defense.gov/sites/dodaf20/capability_mm.html[2011年3月3日下午3:43:27]
首页DoDAF-DM2工作组DoDAF期刊国防部元数据注册想法链接
DM2数据组
能力
能力数据组提供有关活动收集和集成的信息
它们结合起来响应特定要求。此处定义的能力是
在规定的标准和条件下，通过以下方式实现预期效果的能力：
执行一组任务的手段和方法的组合。“这一定义符合
包含在联合参谋部发布的JCIDS指令中。
数据组描述

GDC780BE21 3BHE004468R0021 高压变频器主板 

GDC780BE21 3BHE004468R0021 高压变频器主板 

describe a desired state of a Resource (Materiel, Information, Performer, or Geopolitical
Extent.) Goals data can be expressed as enterprise goals-high-level strategic goals that
apply to the entire organization-or as more specific operational goals that define desired
outcomes of the work process.
Data Group Description
The following should be noted about the Goals Data Group:
a. Although the language sounds different, the meaning of a desired effect (a change in
state of some object) is the same as the meaning of goal.
b. A desired change in the state of some object leads to activities constrained by Rules
that are performed by Performers. Some Activities are considered Events because
they are of near-zero duration with respect to the frame of discernment of the Vision,
Performers, etc.
c. Within DoDAF, goals are identified and described to provide direction to Activities and
to orient those Activities toward a desired effect. When a Performer executes an
Activity, the Performer does so within the limitations prescribed for the Activity
(Rules) and aims toward a desired effect. That effect should either meet, or contribute
to meeting, established Goals that reflect the vision of the organization.
Usage in Core Processes
Goals are established at all levels of the organization and each of the core DoD processes.
Goals can be applied to the Enterprise or Solution architecture effort. Goals are particularly
useful to teams undertaking an architecture development effort to evaluate the success of
the effort and how the effort contributes to achieving higher level goals, mission
requirements, capability developments, or development of Services and Systems to support
Department or organizational business operations.
Data for Goals are useful for:
a. Scoping an activity to ensure that resources utilized in executing an activity contribute
to the overall goals and vision of the organization.
b. Establishing rules under which activities are executed to create boundaries for
efficiency and effectiveness (Constraints) and establishing those circumstances under
which an activity is executed (Event).
c. Establishing measures to determine the success of an activity, consistent with an
established goal.
Background
Architecture Development
Meta-Model
Conceptual
Logical
Performers
Resource Flows
Information and Data
Rules
Goals
Capability
Services
Project
Reification
Organizational Structure
Measures
Locations
Pedigree
PES
IDEAS Foundation
Ontology
Viewpoints & Models
Presentation Techniques
Configuration Management
Overview
Acronyms List and Glossary
of Terms
Site Map
Archives
Department of Defense
60
DM2 - Goals
http://cio-nii.defense.gov/sites/dodaf20/goals.html[3/3/2011 3:43:20 PM]
Data for Projects can be used in the six core processes in the following ways:
a. JCIDS: In establishing desired and threshold capabilities. Traceability should always be
maintained between Goals and capabilities. This should include measures, rules and
pedigree.
b. PPBE, DAS, SE: Goals are established at all level of the design, development and
acquisition process. Traceability throughout the various levels is essential to the
proper management an control of cost, systems engineering and acquisition.
c. Ops Planning: In establishing Operational Plans Goals and objectives are established
related to Missions. Goals can be described as both strategic and tactical.
d. CPM: In establishing both the technical and programmatic aspects of the portfolio.
Presentation
Goals are typically depicted in tabular or textual form. It is desirable that Goals be presented
in a structured manner showing primary and derived goals. This enhances project
traceability.
Go to top of page ↑
Privacy Policy | Web Policy | Contacts
61
DM2 - Capability
http://cio-nii.defense.gov/sites/dodaf20/capability_mm.html[3/3/2011 3:43:27 PM]
Home DoDAF-DM2 WG DoDAF Journal DoD Meta Data Registry IDEAS Links
DM2 Data Groups
Capability
The Capability Data Group provides information on the collection and integration of activities
that combine to respond to a specific requirement. A capability, as defined here is "the
ability to achieve a desired effect under specified standards and conditions through
combinations of means and ways to perform a set of tasks." This definition is consistent with
that contained in the JCIDS Instruction published by the Joint Staff.
Data Group Description