Skip to main content

800xA

Here you find specific process information for System 800xA development.

System 800xA is not only a DCS (Distributed Control System) it's also an Electrical Control System, a Safety System, and a collaboration enabler with the capacity to improve engineering efficiency, operator performance, and asset utilization.

What to Use and Where to Find the Artifacts​

  • Brownfield documents (templates and process documents) are found in 7PAA010269_en_ Product QMS and template listing
  • Documents (product related) are found via the different release baselines
  • Applicable tools and their respective version are found via process documents and in DFN.

800xA Design Terminology​

(Extract from 3BSE044017 HW and SW Development, relating to 800xA design)

The terms below are commonly used when describing the 800xA. They can typically be found throughout product management documents, R&D design and test documents, 800xA user documents, etc.

  • System
    • Generic context: An organization of elements that together accomplish a function.
    • Products context: 800xA System is an organization of products (800xA) and traditional original component suppliers (OCS) products.
    • Functional design context: An organization of 800xA System Parts.
  • Product
    • Products context: The System (800xA) offering is built from a number products.
  • System Part
    • Functional design context: A part of the 800xA system: Control builder, 800M Hi Controller, Select I/O, etc
    • In CION products context, it is a product.
  • Subsystem
    • Generic context: A subsystem is an organization of elements, which is a system itself, or part of a larger system.
    • Functional design context: A system part is divided in sub systems. E.g. the 800M Hi controller (system part) is divided in the subsystems PM and SM.
  • Component
    • Products context: A component is an element that is contributing to the functionality of a product and can be developed separately from the main development of the product, or sourced.
    • Functional design context: A component is part of a subsystem.
  • Subcomponent
    • Products context: A subcomponent is an element that is contributing to the functionality of a component and can be developed separately from the development of the component, or sourced.
    • Functional design context: A subcomponent is a decomposition of a component.
  • Module
    • Functional design context: An element in the detailed design. The module is realized in SW or HW. Smallest possible unit that is feasible and separately testable.
      • In SW: One or more source code files, classes.
      • In HW: Circuit board, power supply, etc.

References​