Browse Topic: Systems management

Items (160)
Find
Standard Practice for HabitabilitySAE1007 (Historical)09/14/2021
This Standard specifies the Habitability processes throughout planning, design, development, test, production, use and disposal of a system. Depending on contract phase and/or complexity of the program, tailoring of this standard may be applied. The primary goals of a contractor Habitability program include: Ensuring that the system design complies with the customer Habitability requirements and that discrepancies are reported to management and the customer. Identifying, coordinating, tracking, prioritizing, and resolving Habitability risks and issues and ensuring that they are: ○ Reflected in the contractor proposal, budgets, and plans ○ Raised at design, management, and program reviews ○ Debated in Working Group meetings ○ Coordinated with Training, Logistics, and the other HSI disciplines ○ Included appropriately in documentation and deliverable data items Ensuring that Habitability requirements are applied to all personnel environments, including operators, maintainers, trainers
G-45 Human Systems Integration
Technical Standard
Standard Practice for HabitabilitySAE1007-TEST-REC (Historical)09/14/2021
This Standard specifies the Habitability processes throughout planning, design, development, test, production, use and disposal of a system. Depending on contract phase and/or complexity of the program, tailoring of this standard may be applied. The primary goals of a contractor Habitability program include: Ensuring that the system design complies with the customer Habitability requirements and that discrepancies are reported to management and the customer. Identifying, coordinating, tracking, prioritizing, and resolving Habitability risks and issues and ensuring that they are: ○ Reflected in the contractor proposal, budgets, and plans ○ Raised at design, management, and program reviews ○ Debated in Working Group meetings ○ Coordinated with Training, Logistics, and the other HSI disciplines ○ Included appropriately in documentation and deliverable data items Ensuring that Habitability requirements are applied to all personnel environments, including operators, maintainers, trainers
G-45 Human Systems Integration
Technical Standard
Systems Engineering Capability ModelEIA731_1A (Current)03/16/2021
The purpose of this Standard is to support the development and improvement of systems engineering capability.
G-47 Systems Engineering
Information Report
Systems Engineering Capability ModelEIA731_1A-TEST-REC (Historical)03/16/2021
The purpose of this Standard is to support the development and improvement of systems engineering capability.
G-47 Systems Engineering
Information Report
Processes for Engineering a SystemEIA632A (Current)02/23/2021
The purpose of this Standard is to provide an integrated set of fundamental processes to aid a developer in the engineering or reengineering of a system. Use of this Standard is intended to help developers a) establish and evolve a complete and consistent set of requirements that will enable delivery of feasible and cost-effective system solutions; b) satisfy requirements within cost, schedule, and risk constraints; c) provide a system, or any portion of a system, that satisfies stakeholders over the life of the products that make up the system. NOTE—The term product is used in this standard to mean: a physical item, such as a satellite (end product), or any of its component parts (end products); a software item such as a stand-alone application to run within an existing system (end product); or a document such as a plan, or a service such as test, training, or maintenance support, or equipment such as a simulator (enabling products). d) provide for the safe and/or cost-effective
G-47 Systems Engineering
Information Report
Processes for Engineering a SystemEIA632A-TEST-REC (Historical)02/23/2021
The purpose of this Standard is to provide an integrated set of fundamental processes to aid a developer in the engineering or reengineering of a system. Use of this Standard is intended to help developers a) establish and evolve a complete and consistent set of requirements that will enable delivery of feasible and cost-effective system solutions; b) satisfy requirements within cost, schedule, and risk constraints; c) provide a system, or any portion of a system, that satisfies stakeholders over the life of the products that make up the system. NOTE—The term product is used in this standard to mean: a physical item, such as a satellite (end product), or any of its component parts (end products); a software item such as a stand-alone application to run within an existing system (end product); or a document such as a plan, or a service such as test, training, or maintenance support, or equipment such as a simulator (enabling products). d) provide for the safe and/or cost-effective
G-47 Systems Engineering
Information Report
Standard Practice for Manpower and PersonnelSAE1010 (Current)09/18/2020
This Standard covers Manpower and Personnel (M&P) processes throughout planning, design, development, test, production, use, and disposal of a system. Depending on contract phase and/or complexity of the program, tailoring can be applied. The scope of this standard includes Prime and Sub-contractor M&P activities; it does not include Government M&P activities. The primary goals of a contractor M&P program typically include: Ensuring that the system design complies with the latest customer manpower estimates (numbers and mix of personnel, plus availability) and that discrepancies are reported to management and the customer. Ensuring that the system design is regularly compared to the latest customer Personnel estimates (capabilities and limitations) and that discrepancies are reported to management and the customer. Identifying, coordinating, tracking, and resolving M&P risks and issues and ensuring that they are: ○ Reflected in the contractor proposal, budgets, and plans. ○ Raised at
G-45 Human Systems Integration
Technical Standard
Configuration Management Requirements for Defense ContractsEIA649_1A-TEST-REC (Historical)08/10/2020
This document applies to hardware and software and provides CM requirements to be placed on contracts after being tailored by the Acquirer. The requirements have been organized by the following five CM functions: a Configuration Planning and Management b Configuration Identification c Configuration Change Management d Configuration Status Accounting e Configuration Verification and Audit
G-33 Configuration Management
Technical Standard
Configuration Management Requirements for Defense ContractsEIA649_1A (Current)08/10/2020
This document applies to hardware and software and provides CM requirements to be placed on contracts after being tailored by the Acquirer. The requirements have been organized by the following five CM functions: a Configuration Planning and Management b Configuration Identification c Configuration Change Management d Configuration Status Accounting e Configuration Verification and Audit
G-33 Configuration Management
Technical Standard
Defining an Open System Architecture Standard for Defense SystemsTBMG-3535510/01/2019
For many years now, there have been efforts within the US defense community to adopt “Open System Architecture” principles (or OSA) for defense computing platforms. Stretching back to the mid-2000’s there have been numerous efforts by all service branches to define sets of OSA principles or requirements on the embedded computing systems they procure and deploy. While these efforts have resulted in widespread adoption of POSIX functions for common tasks and a gradual shift in the use of common form factors and technologies such as VPX and Ethernet, there are still wide disparities between products from different suppliers, which creates difficulties for integrators. Product variations also make technology insertions or system configuration changes expensive, time consuming, and often locked to a particular vendor.
Magazine Article
Defining an Open System Architecture Standard for Defense Systems19AERP10_0410/01/2019
For many years now, there have been efforts within the US defense community to adopt “Open System Architecture” principles (or OSA) for defense computing platforms. Stretching back to the mid-2000's there have been numerous efforts by all service branches to define sets of OSA principles or requirements on the embedded computing systems they procure and deploy. While these efforts have resulted in widespread adoption of POSIX functions for common tasks and a gradual shift in the use of common form factors and technologies such as VPX and Ethernet, there are still wide disparities between products from different suppliers, which creates difficulties for integrators. Product variations also make technology insertions or system configuration changes expensive, time consuming, and often locked to a particular vendor. In 2019 the US defense embedded computing market underwent a transformation. Started in 2017, the Sensor Open Systems Architecture group (or SOSA) is an organization
Magazine Article
The Road to the Top is Not on the Map: Conversations with Top Women of the Automotive IndustryR-49109/04/2019
Carla Bailo, CEO of the Center for Automotive Research, and Terry Barclay, CEO of Inforum, bring together over 30 of the most influential women in the automotive industry to share their insight and advice. From suppliers to OEMs, they hail from every corner of the industry. Readers will learn how to take charge of their own careers by understanding the experiences these professionals. Topics include: • Work-Life Integration - How can you be whole at home, at work, and in the community? • Education and Lifelong Learning - Do you really need a graduate degree? • Mentor and Sponsor Relationships - How do you find mentors and sponsors and form productive relationships with them? • Career Challenges - How do you evaluate when to take career risks? How do you say yes when all the boxes aren't checked? • Resilience - Where do you find the internal fortitude to keep going? • Personal Satisfaction - What do these leaders find most joyful about their careers? The Road to the Top is Not on the
Bailo, Carla, Barclay, Terry
Reference
Standard Practice for Human Systems IntegrationSAE6906 (Current)02/08/2019
This Human Systems Integration (HSI) Standard Practice identifies the Department of Defense (DoD) approach to conducting HSI programs as part of procurement activities. This Standard covers HSI processes throughout design, development, test, production, use, and disposal. Depending on contract phase and/or complexity of the program, tailoring should be applied. The scope of this standard includes prime and subcontractor HSI activities; it does not include Government HSI activities, which are covered in the DoD HSI Handbook. HSI programs should use the latest version of standards and handbooks listed below, unless a particular revision is specifically cited in the contract.
G-45 Human Systems Integration
Technical Standard
Configuration Management StandardEIA649C (Current)02/07/2019
This standard defines five CM functions and their underlying principles. The functions are detailed in Section 5. The principles, highlighted in text boxes, are designed to individually identify the essence of the related CM function and can be used to collectively create a checklist of “best practice” criteria to evaluate a CM program. The CM principles defined in this standard apply equally to internally focused enterprise information, processes, and supporting systems (i.e., Enterprise CM - policy driven, supporting the internal goals needed to achieve an efficient, effective and lean enterprise), as well as to the working relationships supported by the enterprise (i.e., Acquirer/Supplier CM - contracted relationship to support external trusted interaction with suppliers). In an Enterprise CM context there are several methodologies for principle use by the enterprise: The principles of this standard provide direction for developing enterprise or functional CM plans focused on
G-33 Configuration Management
Technical Standard
End Public ‘Shadow’ Driving!19AVEP01_0701/01/2019
The best way to test and train AI for autonomous vehicles is through proper simulation, systems engineering, and an end-state scenario matrix. A veteran engineer explains why the current AV testing paradigm must change. Autonomous vehicle developers are widely using public “shadow” driving which involves a human in the driver's seat letting go of the steering wheel and ceding control to the system under test to observe how it performs. The fundamental premise of this process is that the vehicle has learned the proper management of possible events which may occur during the maneuvers, and the human observer can react fast enough to stop any negative results from occurring. It is a myth that public shadow driving is the best or only solution to create a fully autonomous vehicle, for several reasons.
DeKort, Michael
Magazine Article
Standard Best Practices for System Safety Program Development and ExecutionGEIASTD0010A (Current)10/18/2018
This document outlines a standard practice for conducting system safety. In some cases, these principles may be captured in other standards that apply to specific commodities such as commercial aircraft and automobiles. For example, those manufacturers that produce commercial aircraft should use SAE ARP4754 or SAE ARP4761 (see Section 2 below) to meet FAA or other regulatory agency system safety-related requirements. The system safety practice as defined herein provides a consistent means of evaluating identified risks. Mishap risk should be identified, evaluated, and mitigated to a level as low as reasonably practicable. The mishap risk should be accepted by the appropriate authority and comply with federal (and state, where applicable) laws and regulations, executive orders, treaties, and agreements. Program trade studies associated with mitigating mishap risk should consider total life cycle cost in any decision. This document is intended for use as one of the elements of project
G-48 System Safety
Information Report
Transmitted Enhanced Loran (eLoran) Signal Standard for Tri-State Pulse Position ModulationSAE9990/1 (Current)09/17/2018
This eLoran transmitted signal standard provides technical descriptions of a data channel based on the tri-state pulse position modulation technique. The eLoran transmitted signal standard, to which this data channel technique applies, is part of the SAE9990 family of standards covering data channels, receiver specifications, and recommended practices for eLoran.
PNT Position, Navigation, and Timing
Technical Standard
GUIDANCE FOR USAGE OF DIGITAL CERTIFICATESARINC842-2 (Current)07/11/2018
This document sets forth guidance for life-cycle management of public/private (i.e., asymmetric) keys that are used to secure interactions among systems.
Airlines Electronic Engineering Committee
Information Report
WCX18 Day 1 Highlights1234704/11/2018
Highlights and interviews from the first day of WCX18
Video
System and Method for Managing Autonomous Entities Through ApoptosisTBMG-2870604/01/2018
This NASA innovation is a biologically inspired system management method designed to make sensor webs as well as other autonomous and autonomic systems more self-directing and self-managing. Based on the mechanisms of cell apoptosis, this method ensures safe and correct operation over time by enabling self-destruct, self-sleep, or standby actions in response to potentially harmful or compromising situations. The capabilities provided by this technology will benefit systems such as sensors, computer systems, and spacecraft.
Magazine Article
Cooling Your Embedded System: What Can Your Open Standard Architecture Handle?TBMG-2643702/01/2017
Embedded computing systems for Mil/Aero applications are often conduction-cooled in an ATR or nonstandard chassis. However, there are many designs that require 19" rackmount systems with forced-air cooling. As more processing performance is packed into tight spaces, enclosures that provide advanced cooling options are increasingly common.
Magazine Article
Cooling Your Embedded System17AERP02_0202/01/2017
What Can Your Open Standard Architecture Handle? Embedded computing systems for Mil/Aero applications are often conduction-cooled in an ATR or nonstandard chassis. However, there are many designs that require 19″ rackmount systems with forced-air cooling. As more processing performance is packed into tight spaces, enclosures that provide advanced cooling options are increasingly common. The open-standard embedded architectures have different recommended limitations for power. Sometimes these are electrical pinout limitations, and other times they are recommended thermal limitations. There are “tricks of the trade” to extend the power for certain architectures as well as the ability to maximize the thermal limits.
Magazine Article
Statement on Requirements for Real-Time Communication Protocols (RTCP)AIR4886A (Current)10/21/2016
The purpose of this document is to establish the requirements for Real-Time Communication Protocols (RTCP). Systems for real-time applications are characterized by the presence of hard deadlines where failure to meet a deadline must be considered a system fault. These requirements have been driven predominantly, but not exclusively, by aerospace type military platforms and commercial aircraft, but are generally applicable to any distributed, real-time, control systems. These requirements are primarily targeted for the Transport and Network Layers of peer to peer protocols, as referenced in the Open System Interconnect Reference Model (2.2.1 and 2.2.2), developed by the International Standards Organization (ISO). These requirements are intended to complement SAE AS4074 (2.1.1) and AS4075 (2.1.2), and future SAE communications standards. Although information transfer objectives herein concentrate primarily on digital data flow attributes, efforts have been made such as not to preclude
AS-1A Avionic Networks Committee
Information Report
National Electronic Process Certification StandardEIA599A (Current)06/17/2016
This Standard is applicable to suppliers of electronic components, assemblies, equipment and related materials. This standard establishes the general requirements to achieve a certified process. The use of this standard is intended for any manufacturing or service company whose goal is to achieve customer satisfaction through continuous improvement.
Systems Management Council
Information Report
Software Life Cycle Processes – Life Cycle DataIEEEEIA12207_1 (Current)06/16/2016
This guide provides guidance for recording life cycle data resulting from the life cycle processes of IEEE/EIA 12207.0. NOTE—For informative references, see annex A.
Systems Management Council
Information Report
Software Life Cycle Processes – Implementation ConsiderationsIEEEEIA12207_2 (Current)06/16/2016
This guide provides implementation consideration guidance for the normative clauses of IEEE/EIA 12207.0. The guidance is based on software industry experience with the life cycle processes presented in IEEE/EIA 12207.0.
Systems Management Council
Information Report
CDIF Integrated Meta-model Data Flow Model Subject AreaEIAIS115 (Current)06/16/2016
The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards that form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards. This
Systems Management Council
Information Report
Using EDIF 200 for Schematic TransferEIAEDIFAG1 (Current)06/16/2016
Systems Management Council
Information Report
Style Manual for Standards and Other Publications of TechAmericaGEIAOP0002 (Current)06/16/2016
This style manual establishes requirements for the preparation of standards1) and certain other publications of TechAmerica. It also gives some indication with regard to presentation.
Systems Management Council
Information Report
Model for Integrating Metrics into the Procurement ProcessEIA830 (Current)06/16/2016
This model is designed to enhance insight into the application of meaningful metrics. The emphasis is on business processes which may best provide indication of the level of risk to the customer when contemplating or continuing business with the supplier base. (E.g., the RFP/RFQ, proposal, supplier selection, and performance).
Systems Management Council
Information Report
Industry Implementation of International Standard ISO/IEC 12207:1995 (ISO/IEC 12207) Standard for Information Technology Software Life Cycle ProcessesIEEEEIA12207_0 (Current)06/16/2016
This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products. Software includes the software portion of firmware. This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.
Systems Management Council
Information Report
Systems Engineering Capability ModelEIAIS731_1 (Current)06/16/2016
The purpose of this Interim Standard is to support the development and improvement of systems engineering capability.
G-47 Systems Engineering
Information Report
Systems EngineeringEIAIS632 (Current)06/16/2016
This standard defines a total system approach for the development of systems. The standard requires: establishing and implementing a structured, disciplined, and documented systems engineering effort incorporating the systems engineering process; multidisciplinary teamwork; and the simultaneous development of the products and processes needed to satisfy user needs. The systems engineering process is defined generically to facilitate broad application. This standard defines the requirements for technical reviews. The tasks in this standard provide a methodology for evaluating progress in achieving system objectives. This standard provides a comprehensive, structured, and disciplined approach for all life-cycle phases, including new system product and process developments, upgrades, modifications, and engineering efforts conducted to resolve problems in fielded systems. This standard is applicable to technical efforts in support of advancement and development of new technologies and
G-47 Systems Engineering
Information Report
CDIF Integrated Meta-model - State/Event Model Subject AreaEIAIS116 (Current)06/16/2016
The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards that form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this standard and its position in the CDIF Family of Standards.
Systems Management Council
Information Report
EDIF Connectivity, Volume 2EIAEDIF2 (Current)06/16/2016
Systems Management Council
Information Report
Manual of Organization and ProcedureGEIAOP0001E (Current)06/16/2016
The TechAmerica Standards & Technology department is responsible for standardization activities, and provides other appropriate technical and engineering services within the scope of TechAmerica by-laws. Standardization activities shall include those associated with Business, Engineering, and Operations Management and Processes. All activities shall be conducted in accordance with appropriate legal guidance.
Systems Management Council
Information Report
Harmonizing CALS Product Data Description StandardsEIACALS (Current)06/16/2016
Systems Management Council
Information Report
Engineering & Operations Council Organization and Operation ManualEIAEP2F (Current)06/16/2016
Systems Management Council
Information Report
CDIF Integrated Meta-model Presentation Location and Connectivity Subject AreaEIAIS118 (Current)06/16/2016
The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model also has applicability as the basis of standard definitions for use in repositories. The standards that form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards. This standard, EIA/IS-118
Systems Management Council
Information Report
CDIF - Transfer Format Syntax - SYNTAX.1EIAIS109 (Current)06/15/2016
The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards which form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and the role that it plays in the CDIF Family of Standards
Systems Management Council
Information Report
CDIF - Transfer Format General Rules for Syntaxes and EncodingsEIAIS108 (Current)06/15/2016
The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards which form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards. This
Systems Management Council
Information Report
CDIF - Integrated Meta-model Data Modeling Subject AreaEIAIS114 (Current)06/15/2016
The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards that form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards. This
Systems Management Council
Information Report
CDIF - CASE Data Interchange Format - OverviewEIAIS106 (Current)06/15/2016
The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The CDIF Family of Standards includes an Integrated Meta-model and a Transfer Format definition. It also includes the specification of a meta-meta-model and associated rules that define a framework for the Integrated Meta-model and the Transfer Format. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export for repositories. The CDIF Integrated Meta-model also has applicability as the basis of standard definitions for use in repositories. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards. This document
Systems Management Council
Information Report
CDIF - Integrated Meta-model Foundation Subject AreaEIAIS111 (Current)06/15/2016
The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards which form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards. This
Systems Management Council
Information Report
CDIF - Transfer Format Encoding - ENCODING.1EIAIS110 (Current)06/15/2016
The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards which form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards. This
Systems Management Council
Information Report
CDIF - Framework for Modeling and ExtensibilityEIAIS107 (Current)06/15/2016
Systems Management Council
Information Report
CDIF - Integrated Meta-model Common Subject AreaEIAIS112 (Current)06/15/2016
The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards that form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards. This
Systems Management Council
Information Report
Electrical and Mechanical Interface Characteristics and Line Control Protocol Using Communication Control Characters for Serial Data Link Between a Direct Numerical Control System and Numerical Control Equipment Employing Asynchronous Full Duplex TransmissionEIA484A (Current)05/31/2016
This standard specifies services whose architecture can be described in the context of the physical layer architecture (1) and the data link layer architecture (2) of the ISO Open Systems Interconnection Basic Reference Model - ISO 7498.
Systems Management Council
Information Report
Managing the Development of Artificial Intelligence SoftwareCRB1 (Current)05/31/2016
Systems Management Council
Information Report
Lot Acceptance Procedure for Verifying Compliance With the Specified Quality Levels (SQL) in PPMEIA555 (Current)05/31/2016
This Specification covers a statistical sampling plan for lot inspection by attributes. It verifies that the customer's specified quality level (SQL) is not being exceeded. The estimate of fraction nonconforming determined by EIA Interim Standard No. EIA-554 is used to select the optimum sample plan for verifying that a given lot meets the specified quality level (SQL).
Systems Management Council
Information Report
Items per page:
1 – 50 of 160