TC570 3BSE001458R1 TC-570 现场总线连接模块单元

TC570 3BSE001458R1 TC-570 现场总线连接模块单元 

流程瓶颈在哪里？
2.活动和程序是否可互操作？
3.确定新的和新兴的系统互操作性需求。
4.发现不必要或低效的运营活动和信息流。
5.评估具有不同连通性和资源流的替代架构
以大化能力和小化自动化复杂性。
6.确定关键连接需求和接口（或关键接口配置文件
（KIP）活动及其执行者（组织和人员）之间
类型）。
7.关键接口通常记录在正式接口文件中
由负责当局签署（信息供应商和信息
消费者）负责接口的每一端。这种类型的接口可能是：
注释为键接口（KI）。KI定义为一个接口，其中
满足以下更多标准：
8.支持备选方案分析（AoA）和其他系统工程分析。
b、 达斯
1.接口跨越组织边界（可能跨越
相同系统，但由不同组织使用）。
2.支持测试序列和程序的开发。
3.资源流（物资、人员或数据）的详细信息通常包括：
记录在接口控制文件（ICD）中，接口要求
规范（IRS）和接口描述文件（IDD）。这个数据是
通常提供给国防部投资审查委员会（IRB）注册系统，用于：
48
DM2-资源流
http://cio-nii.defense.gov/sites/dodaf20/resource_flows.html[2011年3月3日下午3:43:08]
里程碑评审的目的是支持采办决策点。
c、 PPBE
1.确保FYDP提供运营和任务所需的流量
2.确保生产商满足消费要求
d、 SE
1.识别新系统或服务、功能（活动）、组件和
需要修改。
2.确定新的资源流和系统集成需求。
3.确定应用新标准的必要性。
4.明确识别系统之间的关系和信息流
SoS中的系统/服务或面向服务的系统中的服务之间
架构（SOA），包括发布或订阅需求的定义
5.接口识别和定义，包括互操作性分析和
标准化。
6.支持接口的配置管理。接口通常是：
记录在接口文件中，代表
负责接口各端的责任方（两个信息
供应商和信息消费者）。这绝不意味着点对点
界面使用企业服务总线实现的接口，
定义了适当的发布/订阅文档，如果
必要时，信息供应商和
消费者
7.关键接口通常记录在正式接口文件中
由负责当局签署（信息供应商和信息
消费者）负责接口的每一端。对于传统的点对点
接口这可以是接口控制图（ICD）的形式，
接口需求文件（IRS）、接口设计文件（IDD），
多址或公共连接（无线电通信或总线
类型连接性）实现可以采用正式协议的形式
（本协议中定义为双方就条款和条件达成的同意
所述各方参与的活动）详细说明
数据的实现（例如，战术数字信息链路[TADILs]）
元素实现表，或者在SOA的情况下，发布/订阅
执行文件。这些协议通常是管理的，并且
由SoS或系统项目经理控制。在新系统中，以及
如果可能，应使用
通用精度数据模型。图4说明了从
网络中心的传统点对点接口的配置控制，
使用精心管理的发布实现连接的分布式处理手段
并根据以下内容签署协议和文件：

TC570 3BSE001458R1 TC-570 现场总线连接模块单元 

TC570 3BSE001458R1 TC-570 现场总线连接模块单元 

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
same system, but utilized by different organizations).
2. Support the development of test sequences and procedures.
3. The Details of Resource Flow (materiel, personnel, or data) are generally
documented in Interface Control Documents (ICDs), Interface Requirements
Specifications (IRSs) and Interface Description Documents (IDDs). This data is
typically provided to DoD Investment Review Board (IRB) registry systems for
48
DM2 - Resource Flows
http://cio-nii.defense.gov/sites/dodaf20/resource_flows.html[3/3/2011 3:43:08 PM]
the purpose of milestone reviews and support of acquisition decisions points.
c. PPBE
1. Ensure FYDP provides flows needed for operations and missions
2. Ensure consumption requirements are met by producers
d. SE
1. Identify new system or service, functions (activities), components and
modifications required.
2. Identify new Resource Flow and system integration requirements.
3. Identification of the need for Application of new standards.
4. Clearly identify the relationship and information flow between systems and
system/services in an SoS or between services in a Service Oriented
Architecture (SOA) including definition of publish or subscribe requirements
5. Interface Identification and Definition including interoperability analysis and
standardization.
6. Support configuration management of interfaces. Interfaces are generally
documented in interface documentation representing the agreements of the
responsible parties in charge of each end of the interface (both information
supplier and information consumer). This, in no way implies a point-to-point
interface. Interfaces implemented with an enterprise service bus, for example,
are defined with appropriate publish/subscribe documentation formalized, if
necessary, with contractual agreements between information supplier and
consumer.
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. For legacy point-to-point
interfaces this may be in the form of Interface Control Drawings (ICDs),
Interface Requirement Documents (IRSs), Interface Design Documents (IDDs),
etc. In multiple access or common connectivity (radio communications or bus
type connectivity) implementations may be in the form of formal agreements
(defined herein as a consent among parties regarding the terms and conditions
of activities that said parties participate in) detailing the specific set of
implementations (e.g., Tactical Digital Information Links [TADILs]) data
elements implementation tables or in the case of a SOA, a publish/subscribe
implementation document. These agreements are, in general, managed and
controlled by the SoS or System Project manager. In new systems, and where
possible the interface should be managed and configuration controlled using a
common precision data model. Figure 4 illustrates the evolution from
configuration control of legacy point-to-point interfaces to a net-centric,
distributed processing means of connectivity using carefully managed publish
and subscribe agreements and documentation based on