MIL-PRF-28000B
3. REQUIREMENTS
3.1 General requirements. All digital product data files complying with this specification shall conform to the
identified subset or application protocol class. The specific subset or application protocol class shall be
identified by the use of global parameter #26.
3.1.1 Restrictive nature of subsets. A data file complying with this specification shall utilize only those specific
entities identified in the referenced subset or application protocol class for representing the product definition.
Additional volunteer entity types may be present as long as these entity types are:
a.
Valid IGES entities (V5.3 or greater);
b.
Not necessary to the product data representation; or
c.
Solely for the purpose of regenerating the same development environment when the file is
transferred back to the same Computer Aided Design (CAD) system which originally generated
the file and may be ignored by other CAD systems.
3.1.1.1 Additional limits. These volunteer entities do not include geometry. Rather, they typically include
IGES-defined properties, user-defined properties, and associative or color definition entities. A postprocessor
(see 6.7.14) is not required to translate these volunteer entity types into the data base of its CAD/CAM system,
but is required to continue processing the remainder of the data file.
3.1.2 Limits on Parameter Data (PD). A data file complying with this specification shall not contain scalar
values of PD outside the ranges specified by the identified subset or application protocol class.
3.1.3 Physical file structure. All digital product data files complying with this specification shall be written in the
American Standard Code for Information Interchange (ASCII) form. The binary and compressed ASCII forms
shall not be used.
3.1.4 Physical media for delivery. Unless otherwise specified in the solicitation all data files complying with this
specification shall be delivered in accordance with MIL-STD-1840.
3.1.5 Internet delivery. Files may be transmitted over the internet using the guidelines established by MIL-
STD-1840. When transmitting files the guidelines for Multipurpose Internet Mail Extensions (MIME) should be
followed. The requirements for MIME file delivery are outlined within MIL-STD-1840.
3.2 Specific requirements. The following subsections define the requirements for each defined subset or
application protocol class. A conforming data file shall use the most current IGES version entity types and form
numbers for representation of data in the identified class subset. All references to entity types, form numbers,
and data fields are references to IGES for class 1-4 and 7. Class 5, the 3D Piping AP, uses ANS US
PRO/IPO-100-1993 (IGES 5.2) entities, see ANS US PRO/IPO-110-1994 (3D Piping IGES Application
Protocol) for details. Class 6, LEP AP, uses ANS US PRO/IPO-100-1996 (IGES 5.3) entities, and ANS US
PRO/IPO-111-1997 (Layered Electrical Product Application Protocol). All IGES references in this
specification relate to the most current version of the IGES specification unless otherwise stated.
5
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business