ABB 自动化过程电路板 6205BZ10000M AA p198078
¥6973.00
PM152 3BSE003643R1 ABB
¥3137.00
PM152 3BSE003643R1 模拟量输入输出 ABB
¥6973.00
PM152 3BSE003643R1 模拟量输入输出DCS模块 ABB
¥6973.00
83SR09E 83SR09D-E GJR2366500R1010 控制单元 ABB
\
83SR09E 83SR09D-E GJR2366500R1010 控制单元 ABB
a、 地址，例如URL、通用资源名称（URNs）、邮政地址、数据
链接地址等被认为是位置的名称。例如，邮政
地址是建筑物位置的命名系统。通用资源
定位器是位于Web上某个位置的服务器的名称。
b、 命名模式通过识别以下内容来工作：
1） 名称字符串，
2） 被命名的对象，以及
3） 名称的类型（例如，邮政地址）。这里使用的名称是***义的，
使得描述被认为是长名称。
c、 图的左下角是位置对象类型的模型。这些可以是
或者，使用左上角的命名模式命名，并使用
右下角的扩展模式。
d、 空间范围的最小部分（点、线、曲面和实体体积）是
由于联邦成员内的不同需求而详细。即
联邦成员可能需要专门化空间范围。一些普通和简单的
类被建模，例如由两点和平面描述的线
由线和点定义。
e、 设施是位置的类型。在DoDAF的早期版本中，不清楚设施是否：
出身背景
建筑发展
元模型
概念的
必然的
表演者
资源流动
信息和数据
规则
目标
能力
服务
项目
物化
组织结构
措施
位置
纯种
PES
思想基金会
本体论
观点和模型
展示技巧
配置管理
概述
缩略语列表和词汇表
术语
网站地图
档案
***部
85
DM2-位置
http://cio-nii.defense.gov/sites/dodaf20/locations.html[2011年3月3日下午3:43:53]
可以被认为是一个系统或只是一个位置。现在已经澄清了这一点。描述
设施的功能，位于
描述了设备。
f、 安装、现场和设施遵循陆军不动产库存指南
要求（RIPR）。类似地，设施可以是线性结构，如道路或
管道
g、 地理特征（在联合咨询、指挥和控制信息中称为特征
交换数据模型（JC3IEDM））包括人工控制功能，以及
地球物理特征（包括气象和海洋学现象）。
DoDAF位置元模型
（点击图片放大）
建模位置数据时的其他注意事项如下：
a、 对于许多建筑应用，定位方案是某种几何形式
这是因为许多用途（见下一段）需要几何计算。
b、 命名位置（如设施、基地、安装、区域名称）可适用
因为它们的使用可能仅仅是描述性能发生的位置。此外
命名模式基本上可以使用名称作为几何位置的代理，
例如邮政地址很少适用于架构。
c、 如果需要几何系统，坐标系、参照系和单位
被选择。地理空间标记语言（GML）定义了26种不同类型的
坐标系，包括用户定义的坐标系。在许多情况下，联邦成员可以
选择参考GML，这样就不必考虑手部和方向等问题
再次定义。
d、 应确定准确度。对于许多用途，位置可能不需要
某些地理空间系统可能非常***，因为使用计算可能有许多
近似值、假设和选择的次要影响变量
忽略。
e、 在某些情况下，可能需要速度和加速度范围。因为这些
不寻常的是，它们不是核心DM2的一部分，但将作为扩展添加
各种型号。速度可以扩展为属性或轨迹
由一组时空点组成，其中轨迹是一个整体
点是部分。
86
DM2-位置
http://cio-nii.defense.gov/sites/dodaf20/locations.html[2011年3月3日下午3:43:53]
核心流程中的使用
位置数据用于描述性能的位置
83SR09E 83SR09D-E GJR2366500R1010 控制单元 ABB
83SR09E 83SR09D-E GJR2366500R1010 控制单元 ABB
83SR09E 83SR09D-E GJR2366500R1010 控制单元 ABB
a. Addresses such as URLs, Universal Resource Names (URNs), postal addresses, data
link addresses, etc. are considered Names for Locations. For example, a postal
address is a naming system for the Location of a building. A Universal Resource
Locator is a name for a server that is located somewhere on the Web.
b. The naming pattern works by identifying the following:
1) the name string,
2) the object being named, and
3) the type of name (e.g., postal address). Name here is used in the broadest sense,
such that a description is considered a long name.
c. The lower left of the diagram is a model of types of Location objects. These can be
alternatively named using the naming pattern in the upper left and delineated using
the Extent pattern in the lower right.
d. Minimal parts of the Spatial Extent (Point, Line, Surface, and Solid Volume) are
detailed because of the varying requirements within a federate. That is, member of
the federate may need to specialize the Spatial Extents. Some common and simple
classes are modeled, such as a Line described by two Points and a Planar Surface
defined by a Line and Point.
e. Facilities are types of Locations. In prior versions of DoDAF it was not clear if a Facility
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
85
DM2 - Locations
http://cio-nii.defense.gov/sites/dodaf20/locations.html[3/3/2011 3:43:53 PM]
could be thought of as a system or just a Location. This is now clarified. To describe
the functionality of a Facility, the Activities performed by the Performers located at the
Facility are described.
f. Installation, Site, and Facility follow Army guidance from the Real Property Inventory
Requirements (RIPR). Similarly, a Facility can be a linear structure, such as a road or
pipeline.
g. Geofeatures (called FEATURE in Joint Consultation, Command and Control Information
Exchange Data Model (JC3IEDM)) cover man-made control features, as well as
geophysical features (including meteorological and oceanographic phenomena).
DoDAF Meta Model for Locations
(Click image to enlarge)
Additional considerations in modeling Location data are as follows:
a. For many architecture applications, a locating scheme is some kind of geometric
system because many uses (see next paragraph) require geometric calculations.
b. Named locations (e.g., facility, base, installation, region names) can be applicable
since their use may be merely to describe where performance occurs. In addition, the
naming pattern basically can use the name as a surrogate for the geometric location,
such as postal addresses are rarely applicable to architectures.
c. If a geometric system is needed, the coordinate system, reference frame, and units
are chosen. The Geospatial Markup Language (GML) defines 26 different kinds of
coordinate systems, including one called user defined. In many cases, a federate may
choose reference to GML so issues like handed-ness and orientation don&＃39;t have to be
defined again.
d. The accuracy should be determined. For many uses, Locations may not need to be as
accurate as some Geospatial system can be, since the use calculation may have many
approximations, assumptions, and minor influencing variables that are chosen to be
ignored.
e. In some cases, there may be need for speed and acceleration ranges. Since these are
unusual, they are not part of the core DM2 but would be added as extensions for these
kinds of models. The speed could be extended as an attribute or as a trajectory
consisting of a set of spatial-temporal points, where the trajectory is a whole and the
points are parts.
86
DM2 - Locations
http://cio-nii.defense.gov/sites/dodaf20/locations.html[3/3/2011 3:43:53 PM]
Usage in Core Processes
Data for Locations are used to describe where Perfor
83SR09E 83SR09D-E GJR2366500R1010 控制单元 ABB
83SR09E 83SR09D-E GJR2366500R1010 控制单元 ABB
在线问
