The purpose of the process is to avoid any legal or commercial risks related to 3rd-party software that is either shipped by PAPCP R&D as a part of software acquired by the channel or by the customer as a pre-requisite for functionality. The coverage of 3rd-party software includes commercial software, OSS components, and OSS code snippets.
"Architecture is the fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution." [IEEE 1471]
Definition
For an introduction to the concept of baselining, see the High-level baseline guide.
Product Portfolio Management (PPM) defines the standards a product or system must fulfill based on legal requirements and on a business perspective. The system requirements (SRs) specify the regulatory requirements. PPM and R&D collaborate to ensure the standards are followed.
Configuration Management is the process of identifying and defining the items in the system, controlling the change of these items throughout their lifecycle, recording and reporting the status of items and change requests, and verifying the completeness and correctness of items. [IEEE-Standard-729-1983].
To help our customers protect their critical systems and sensitive information from digital attacks security has to be built into our products.
The Development Stream process manages the planning, prioritization, and visualization of all activities related to product and component releases of different sizes, such as new versions, rollups, and temporary corrections. The main development streams are Operations, Engineering, Control & IO, and IIoT Platform & Applications.
The Development Team process manages the planning, prioritization, and visualization of all activities related to the development of software and hardware components. There are multiple development teams in each development stream.
Explosion protection is the method called which reduces the risk of an unwanted ignition of an explosive atmosphere. The statutory definitions of explosion protection - derived from the health and safety at work regulations - are related to workplaces.
General Introduction
Hardware development involves the design and manufacture of electromechanical devices. It includes CAD models, prototypes, manufacturing documentation, and certifications.
The PCP Intellectual Property process aims to maintain a strong intellectual property portfolio consistent with the market and thought leadership position. IP-related activities in the R&D processes are carried out in the context of PCP’s active, market-oriented IP protection strategy.
The process is mainly divided into two parts: continuous maintenance of existing products during the product life cycle, and an event-driven part handling both customer problems via Support Level 3 and manufacturing problems. The process covers both hardware and software.
The quality process describes how to create and maintain the PCP R&D processes. It also includes quality control, definition and evaluation of KPIs, and how to facilitate process improvements.
The Release process is valid for component, product, and system releases, including limited releases such as roll-ups and expansion packs. It deploys new functionality into production - continuously or on demand - and ensures that all R&D deliverables are ready to release.
The requirements process describes how the market opportunities and system requirements are received from Portfolio and Product Management and transformed into epics, features, and stories.
Software development supports the incremental development of features that can be delivered to streams or other stakeholders. Included are design, implementation, unit tests, component tests, and bug fixing. Software development can result in deliverables, e.g., firmware, applications, and tools.
The Synchronized Program Increment (SPI) sets a common cadence, synchronizes, and aligns the PCP organization (e.g. PPM, R&D, and Operations) towards common PCP business goals. The SPI also creates openness and transparency across organizational functions by inviting key stakeholders to synchronization meetings where issues, conflicting expectations, and dependencies are highlighted before they get critical.
The System Stream process manages the planning, prioritization, and visualization of all activities related to system releases of different sizes, such as new versions, rollups, and temporary corrections. The main systems are 800xA, Symphony Plus, Freelance, and Heritage.
The system and products are integrated and tested to provide stakeholders with information about the quality of potential deliverables or releases.
This process area is responsible for the key processes involved in creating and maintaining user documentation. It covers principles, activities, artifacts, and dependencies to ensure comprehensive and accurate documentation.