DSBC173N 3BNP000468R1 现场总线DCS控制PC板

DSBC173N 3BNP000468R1 现场总线DCS控制PC板 

请注意，发布通常不与订阅同时进行，但
订阅服务器必须访问发布位置才能检索资源。对于
例如，数据可能在格林尼治时间2:00发布在位于某个URL的服务器上，并且
订户在格林尼治标准时间10:00之前不得重叠。请在图表中注意重叠
是生产活动、消费活动和资源的三重结构。
c、 交换或流量三元组可能有与其相关的标准（规则），例如：
信息保证（IA）/安全规则或数据发布或订阅
COI和web服务标准。
d、 规则和措施适用于特定活动及其执行者。活动，
系统和人员可以分配到位置，也可以进一步分配
条件和约束。
e、 术语流意味着某些东西（如物资、信息）正在从
点A到点B，因此使用了“重叠”的基础概念。
f、 交换或流三重可以具有与之相关联的度量，
吞吐量、可靠性或QoS。
g、 资源流建模可以在不同的细节和保真度级别上执行
这取决于正在分析的关注领域和正在寻求的解决方案。这个
在先前版本的DoDAF中，上层聚合被称为需求线。
使用表示聚合级别的其他术语，具体取决于
兴趣社区（例如，SysML建模标准使用生命线）。
h、 应该指出，资源之间的信息输入和输出
分解级别可能比信息的抽象级别更高
矩阵中表示的特征。这通常是为了简化图形
信息流的表示或在初始定义阶段，其中
特征仍然未知。在这种情况下，将映射多个信息交换
到单个资源输入或输出。同样，信息输入和输出
在资源之间，低层次的分解可能在更高层次的细节
而不是矩阵中的信息交换以及多个信息输入
输出可以映射到单个信息交换。在这些情况下，提供
必要的清晰和，信息的本体或分类结构
应开发聚合，以用于
资源流模型（例如，海军通用信息交换列表[CIEL]
表示显示分类结构或聚合级别的计划）。
47
DM2-资源流
http://cio-nii.defense.gov/sites/dodaf20/resource_flows.html[2011年3月3日下午3:43:08]
DoDAF资源流元模型
（点击放大）
核心流程中的使用
资源流建模是一种基于工程的信息技术
技术（IT）架构、系统工程、流程再造、资源
规划和许多其他学科。
a、 JCIDS
1.流程瓶颈在哪里？
2.活动和程序是否可互操作？
3.确定新的和新兴的系统互操作性需求。
4.发现不必要或低效的运营活动和信息流。
5.评估具有不同连通性和资源流的替代架构
以大化能力和小化自动化复杂性。
6.确定关键连接需求和接口（或关键接口配置文件
（KIP）活动及其执行者（组织和人员）之间
类型）。
7.关键接口通常记录在正式接口文件中
由负责当局签署（信息供应商和信息
消费者）负责接口的每一端。这种类型的接口可能是：
注释为键接口（KI）。KI定义为一个接口，其中
满足以下更多标准：
8.支持备选方案分析（AoA）和其他系统工程分析。
b、 达斯
1.接口跨越组织边界（可能跨越

DSBC173N 3BNP000468R1 现场总线DCS控制PC板 

DSBC173N 3BNP000468R1 现场总线DCS控制PC板 

Note that publication is typically not at the same time as subscription but the
subscriber does have to go to the publication place to retrieve the Resource. For
example, data might be published at 2:00 GMT on a server located at some URL and
the subscriber may not overlap until 10:00 GMT. Also note in the diagram the overlap
is a triple - the producing Activity, the Consuming Activity, and the Resource.
c. The exchange or flow triple may have standards (Rules) associated with it such as
Information Assurance (IA)/Security rules or, for data publication or subscription, data
COI and web services standards.
d. Rules and Measures are applied to specific Activities and their Performers. Activities,
Systems and Personnel can be assigned to Locations and further can be assigned
Conditions and Constraints.
e. The term flow implies that something (e.g., materiel, information) is moving from
point A to point B, hence the use of the foundation concept of "overlap".
f. The exchange or flow triple may have Measures associated with it such as timeliness,
throughput, reliability, or QoS.
g. Resource Flow modeling can be performed at varying levels of detail and fidelity
depending on the areas of concern being analyzed and the solutions being sought. The
upper-level aggregations have been termed need lines in previous versions DoDAF.
Other terminology expressing levels of aggregation are used depending on the
community of interest (e.g., The SysML modeling standard uses lifeline).
h. It should be noted that information inputs and outputs between resources for some
levels of decomposition may be at a higher-level of abstraction than the information
characteristics represented in the matrix. This is commonly done to simplify graphical
representations of information flow or in the initial definition stages where the
characteristics are still unknown. In this case, multiple information exchanges will map
to a single resource input or output. Similarly, the information inputs and outputs
between resources at a low-level of decomposition may be at a higher-level of detail
than the information exchanges in the matrix, and multiple information inputs and
outputs may map to a single information exchange. In these cases, to provide the
necessary clarity and precision, an ontological or taxonomic structure of information
aggregation should be developed for use in each level of decomposition of the
Resource Flow models (e.g., The Navy Common Information Exchange List [CIEL]
represents initiatives showing taxonomic structure or levels of aggregation).
47
DM2 - Resource Flows
http://cio-nii.defense.gov/sites/dodaf20/resource_flows.html[3/3/2011 3:43:08 PM]
DoDAF Meta Model for Resource Flow
(Click to enlarge)
Usage in Core Processes
Resource Flow modeling is a fundamental engineering based technique used in Information
Technology (IT) Architecture, System Engineering, Process Re-engineering, Resource
Planning and many other disciplines.
a. JCIDS
1. Where are the process bottlenecks?
2. Are the activities and procedures interoperable?
3. Identify new and emerging systems interoperability requirements.
4. Uncover unnecessary or inefficient operational activities and information flows.
5. Evaluate alternative architectures with different connectivity and Resource Flow
to maximize capability and minimize automation complexity.
6. Identify critical connectivity needs and interfaces (or Key Interface Profiles
(KIPs) between activities and their performers (organizations and personnel
types).
7. Critical Interfaces are generally documented in formal interface documentation
signed by the responsible authorities (both information supplier and information
consumer) in charge of each end of the interface. This type of interface may be
annotated as a Key Interface (KI). A KI is defined as an interface where one or
more of the following criteria are met:
8. Support Analysis of Alternatives (AoA) and other Systems Engineering Analysis.
b. DAS
1. The interface spans organizational boundaries (may be across instances of the