Connect981 – Content Dev

Glossary Tag: signal detection

  • Hold Tag

    A hold tag is a physical tag, label, status marker, or digital system indicator used to show that an item, batch, container, asset, or work step is on hold and must not move forward until the hold is reviewed, resolved, or released by an authorized person or process.

    In manufacturing and regulated operations, a hold tag commonly serves as a control to prevent unintended use, shipment, processing, installation, or disposition of something that requires further attention. The reason may relate to quality, documentation, inspection status, deviation review, material identity, maintenance condition, or another operational concern. The term refers to the marking or status itself, not to the investigation or approval workflow behind it.

    What it includes

    • Physical tags or labels attached to parts, containers, pallets, tools, or equipment
    • Electronic hold statuses in MES, ERP, WMS, QMS, or maintenance systems
    • Temporary restrictions that block use, movement, release, or further processing
    • Identification of the reason, date, source, or responsible function when that information is part of the tag or record

    What it does not mean

    A hold tag does not by itself determine final disposition. It does not mean the item is scrap, nonconforming, rejected, or unsafe in every case. It simply indicates that normal use or progression is restricted pending review or release. In some organizations, hold tags are also used for administrative or documentation issues, not only for product defects.

    How it appears in operations

    Operationally, a hold tag may be applied when incoming material fails inspection, a batch is awaiting test results, a machine is removed from service, or a work order cannot continue because a required approval is missing. In digital workflows, the same concept may appear as a blocked lot, restricted inventory status, quality hold, maintenance hold, or routing stop.

    Common confusion

    Hold tag is often confused with quarantine, NCR status, lockout/tagout, and red tag. A hold tag commonly indicates restricted use or movement pending review. Quarantine usually refers to controlled segregation of suspect or restricted material. An NCR documents a nonconformance and related workflow. Lockout/tagout is a specific energy-isolation safety control for equipment, which is different from a general production or quality hold. A red tag in 5S is typically used to identify unnecessary items for workplace organization, not necessarily product or process holds.

  • Corporate calendar

    A corporate calendar is the organization-wide schedule used to define and communicate important business dates, time periods, and planned events. In industrial and manufacturing environments, it commonly includes fiscal periods, plant schedules, shutdowns, holidays, inventory events, audit windows, training dates, maintenance periods, and other milestones that affect operations, staffing, reporting, or system activity.

    The term usually refers to a shared planning structure rather than a personal meeting calendar. It provides a common time reference for departments such as production, quality, maintenance, supply chain, finance, and IT. In practice, corporate calendars may be managed in ERP, MES, HR, EAM, scheduling, or collaboration systems, depending on the type of event being tracked.

    What it includes

    • Company holidays and non-working days
    • Fiscal months, quarters, and year-end periods
    • Planned plant shutdowns and maintenance windows
    • Cycle count, inventory, or physical stocktake dates
    • Quality, audit, or compliance-related milestones
    • Training, reporting, and governance deadlines

    A corporate calendar does not usually mean the detailed production schedule for specific work orders, machines, or operators, although those schedules may depend on it.

    Operational meaning

    In operations, the corporate calendar acts as a timing framework that other workflows reference. For example, a plant shutdown on the corporate calendar may affect production planning in ERP, preventive maintenance timing in EAM, labor availability in HR systems, and reporting cutoffs for quality or finance. Some systems use calendar definitions directly to calculate available capacity, period-based KPIs, or transaction posting dates.

    Common confusion

    Corporate calendar vs. production schedule: A corporate calendar sets shared business dates and constraints. A production schedule assigns jobs, resources, and timing for manufacturing execution.

    Corporate calendar vs. fiscal calendar: A fiscal calendar is often one part of the broader corporate calendar. The corporate calendar may also include operational, maintenance, and administrative events.

    Corporate calendar vs. personal calendar: A personal calendar manages individual meetings and tasks. A corporate calendar defines organization-level dates that many teams or systems may use.

  • Late-arriving data

    Late-arriving data commonly refers to data that reaches a system after the time it was expected, or after downstream processing, reporting, alerting, or transaction posting has already taken place. The issue is about timing rather than whether the data is valid. The data may still be accurate and complete, but it arrives too late to be used in the intended sequence.

    In manufacturing and regulated operations, late-arriving data can appear when machine events, inspection results, operator entries, supplier confirmations, or integration messages are delayed between OT and IT systems such as PLCs, SCADA, MES, LIMS, QMS, ERP, or analytics platforms. For example, a production count may post after a shift report is closed, or a quality result may arrive after a lot has already advanced to the next step.

    What it includes

    • Delayed event records from equipment, sensors, or edge devices
    • Transaction messages posted after the expected processing window
    • Manual entries entered well after the physical activity occurred
    • Integration delays between systems that create out-of-sequence updates

    What it does not necessarily mean

    Late-arriving data does not automatically mean bad data, missing data, or duplicate data. It is different from incorrect timestamps, although timestamp errors can make late arrival harder to detect. It is also different from real-time data loss, where the data never arrives at all.

    Operational meaning

    Operationally, late-arriving data matters because many manufacturing workflows depend on event order and timing. Delayed records can affect traceability, KPI calculations, exception handling, inventory status, quality holds, electronic records, and system-to-system reconciliation. Systems often need logic to decide whether to accept, reprocess, flag, or version a late record so that history remains understandable.

    Common confusion

    Late-arriving data is often confused with stale data and backdated data. Stale data is old data that has not been refreshed. Backdated data is entered with an earlier effective date, which may or may not have arrived late. A late-arriving record can also be backdated, but the terms are not identical.

  • Materialized view

    A materialized view is a database object that stores the results of a query as physical data, rather than calculating the query output every time it is requested. It is commonly used to improve performance for reporting, analytics, dashboards, and other read-heavy workloads where the same joins, aggregations, or filters are used repeatedly.

    In manufacturing and regulated operations, a materialized view may be used to present consolidated data from MES, ERP, quality, historian, or traceability systems in a form that is faster to query. For example, it might store a precomputed summary of production counts, nonconformance trends, equipment events, or lot genealogy relationships for reporting tools.

    What it includes and excludes

    A materialized view includes persisted query results that are refreshed on a schedule, on demand, or by a database-specific mechanism. It may look similar to a regular view when queried, but it is not just a saved SQL definition.

    It does not mean the base source data has been replaced. The underlying tables still exist and remain the system of record unless a separate design says otherwise. A materialized view is also not the same as a data warehouse, data lake, or ETL pipeline, though it may be used within those architectures.

    Operational meaning

    Operationally, a materialized view is often used when teams need consistent read performance without repeatedly executing expensive queries across large transactional datasets. In integrated manufacturing environments, this can reduce load on operational systems while supporting KPI reporting, genealogy lookups, batch review summaries, or exception monitoring.

    Because the stored results can become outdated between refreshes, the timing and method of refresh matter. Some environments refresh near real time, while others refresh hourly, daily, or after specific data loads. The acceptable delay depends on how the data is being used.

    Common confusion

    Materialized view vs. view: A regular view stores only the query definition and calculates results when queried. A materialized view stores the query results themselves.

    Materialized view vs. cache: Both can improve read performance, but a cache is typically managed by an application or platform layer, while a materialized view is usually managed by the database.

    Materialized view vs. replica: A replica copies underlying database data. A materialized view stores the output of a specific query, often transformed or aggregated.

  • Plant steward

    A plant steward commonly refers to a person who looks after a defined area, process, or set of operational responsibilities within a manufacturing plant. The role is usually local and hands-on, focused on sustaining agreed standards, coordinating follow-up actions, and serving as a point of contact for issues related to the assigned area.

    The term is not a universal job title with one fixed meaning. In some organizations it is a formal role; in others it is an informal designation for someone who helps maintain ownership of a workspace, system, line, or compliance-related activity.

    What the role typically includes

    • Monitoring whether plant standards are being followed in a specific area
    • Helping keep documentation, visual controls, or records current at the point of use
    • Escalating issues involving safety, quality, maintenance, housekeeping, or workflow discipline
    • Coordinating with operations, engineering, quality, maintenance, or EHS personnel as needed
    • Supporting continuity when multiple shifts or teams use the same area or equipment

    Depending on the site, a plant steward may be associated with 5S ownership, line readiness, area governance, equipment care, document control at the work center, or other day-to-day plant coordination activities.

    How it appears in operations

    In practice, a plant steward often acts as the named owner or caretaker for a specific operational domain. Examples include stewardship of a production cell, cleanroom support area, digital work instruction station, tool crib, or material staging zone. The role commonly centers on visibility and follow-through rather than direct managerial authority.

    In regulated environments, the role may also involve helping ensure that approved procedures, training references, labels, logs, or status indicators remain available and current where work is performed. This does not by itself make the person the formal quality authority or compliance owner.

    Common confusion

    Plant steward is often confused with plant manager, area owner, or custodian. A plant manager is responsible for broader site performance and leadership. An area owner may have formal accountability for results, budget, or staffing. A custodian usually refers to cleaning or facility upkeep. A plant steward more commonly refers to stewardship of standards, condition, coordination, and local operational discipline within a defined scope.

    The term can also be confused with shop steward, which usually refers to a union representative. That meaning is distinct from plant operations stewardship.

  • Repair Limit

    A repair limit is the defined boundary beyond which a part, assembly, or feature is no longer considered repairable by an approved repair method. It commonly refers to the maximum allowable extent of damage, wear, corrosion, distortion, or material removal that can be restored while keeping the item within its specified requirements.

    In manufacturing and MRO environments, the term is used to decide whether a nonconforming or deteriorated item can proceed through repair, must be reworked by another method, requires engineering review, or should be scrapped. The limit may be expressed as dimensions, thickness, crack length, blend depth, number of prior repairs, remaining life, or other measurable criteria.

    What it includes and excludes

    A repair limit includes the measurable acceptance boundary for performing a repair. It does not by itself describe the full repair procedure, approval authority, or inspection method, although those are often linked in controlled documentation.

    • Includes: maximum allowable repair depth, remaining wall thickness, permitted damage size, or allowable number of repair cycles.

    • Excludes: general workmanship guidance, temporary deviations, and final product acceptance criteria unless those are explicitly tied to the repair definition.

    How it appears in operations

    Repair limits are commonly found in maintenance manuals, engineering dispositions, standard repair schemes, work instructions, and nonconformance workflows. In digital systems, they may appear as structured decision points in MES, QMS, or MRO software, where inspection results are compared against defined thresholds to route the item correctly.

    Example: a component may be repairable if corrosion can be removed without reducing thickness below a stated minimum. If the measured condition exceeds that limit, the part is no longer eligible for that repair path.

    Common confusion

    Repair limit is often confused with service limit or allowable limit. A service limit usually describes the maximum condition permitted for continued use in operation. A repair limit describes the maximum condition that can still be corrected by repair. It can also be confused with rework; rework usually returns a product to requirements using the original process or a defined repeat of it, while repair commonly accepts a different restoration method that addresses damage or nonconformance.

  • Design of experiments (DoE)

    Design of experiments (DoE) is a structured statistical method for planning, running, and analyzing tests so teams can determine how one or more input factors affect a measured output. In manufacturing and quality contexts, it is commonly used to study process settings, material variables, equipment parameters, and environmental conditions in a controlled way.

    DoE is more than trial-and-error testing. It is designed to separate the effect of individual factors and, in many cases, the interaction between factors. This helps explain why a process outcome changes, not just whether it changed.

    What it includes

    A DoE typically defines:

    • the response or output being measured, such as yield, strength, cycle time, or defect rate
    • the factors being varied, such as temperature, pressure, speed, dwell time, or material lot
    • the levels or settings for each factor
    • the test structure, such as randomized runs, replicated runs, or factorial designs
    • the analysis used to identify statistically meaningful effects

    Depending on the objective, DoE may be used for screening important variables, optimizing process settings, characterizing a process window, or supporting root cause analysis.

    What it is not

    DoE is not the same as changing one variable at a time without a formal design. It is also not limited to product design work. In industrial operations, it is often applied to manufacturing processes, inspection methods, formulation work, and validation-related studies.

    DoE does not by itself prove long-term process control or regulatory acceptability. It is a method for generating evidence about relationships between inputs and outputs under the conditions studied.

    How it appears in operations

    In plant and quality workflows, DoE may be used during process development, scale-up, transfer to production, deviation investigation, or continuous improvement. Results are often documented in engineering, quality, or validation records and may inform work instructions, control limits, recipes, or parameter ranges in MES, historians, or related systems.

    Example: a manufacturer may run a DoE to study how cure temperature, hold time, and humidity affect bond strength and scrap rate.

    Common confusion

    DoE vs. A/B testing: A/B testing usually compares one change against another. DoE can evaluate multiple factors at the same time and can reveal interactions between them.

    DoE vs. one-factor-at-a-time testing: One-factor-at-a-time testing is simpler but may miss combined effects. DoE is specifically structured to estimate those effects more reliably.

    DoE vs. statistical process control: Statistical process control monitors an ongoing process for stability and variation. DoE is used to learn how deliberate changes in inputs influence outputs.

  • Segregation

    Segregation commonly refers to the deliberate separation of items, activities, systems, or responsibilities so they do not improperly mix, interfere, or create control gaps. In manufacturing and regulated operations, the term is often used for physical separation of materials and product states, logical separation of data or systems, and organizational separation of responsibilities.

    What counts as segregation depends on the context. It can include separating conforming and nonconforming material, keeping different lots or part numbers apart, isolating clean and dirty areas, restricting network zones, or dividing duties so one person does not control an entire approval or release process. The core idea is controlled separation to reduce the chance of error, contamination, misidentification, cross-use, or unauthorized action.

    Segregation does not necessarily mean permanent isolation or complete independence. It usually means there is a defined boundary, control, or handling rule. For example, material may be segregated by location, container, status label, transaction state in MES or ERP, or user permissions in a software system.

    Where it appears in operations

    • Material segregation: separating raw materials, WIP, finished goods, quarantined stock, rejected parts, or customer-owned material.

    • Status segregation: keeping accepted, on-hold, and nonconforming items distinct in both physical storage and system records.

    • Process segregation: separating operations or environments to avoid cross-contamination or unintended process mixing.

    • Data or system segregation: separating networks, applications, tenants, or records based on function, sensitivity, or access rules.

    • Segregation of duties: assigning approval, execution, review, and release activities to different roles where control independence matters.

    Common confusion

    Segregation vs isolation: isolation usually implies stronger or more complete separation. Segregation may allow controlled movement or interaction across a boundary.

    Segregation vs traceability: traceability records what happened and where items came from or went. Segregation keeps items or actions separate in the first place.

    Segregation vs quarantine: quarantine is a specific hold status or controlled area. It is one form of segregation, not the whole concept.

    Segregation vs access control: access control manages permissions. It can be one mechanism used to enforce segregation in software or data environments.

    Manufacturing example

    A plant may segregate nonconforming parts in a marked hold area, keep those parts in a separate inventory status in MES or ERP, and limit disposition authority to designated quality roles. Each of those controls is a form of segregation applied to a different part of the operation.

  • Decision support system

    A decision support system is a computer-based system that helps people make decisions by organizing data, applying rules or models, and presenting outputs such as analyses, scenarios, alerts, or recommendations. It supports human judgment rather than replacing it.

    In industrial and manufacturing settings, a decision support system commonly brings together information from sources such as MES, ERP, quality systems, historians, maintenance systems, spreadsheets, or external supply data to help users assess conditions and choose among actions. Examples include systems that flag schedule risks, highlight quality trends, estimate the impact of a material shortage, or compare response options for a production deviation.

    What it includes

    • Data aggregation from one or more operational or business systems

    • Logic, rules, analytics, statistical methods, or simulation models

    • User-facing outputs such as dashboards, ranked options, exception alerts, or what-if analysis

    • Support for structured decisions, semi-structured decisions, or recurring operational reviews

    What it does not necessarily include

    A decision support system is not the same as a fully automated control system. It may recommend or prioritize actions, but the final decision is often made by a planner, supervisor, engineer, quality reviewer, or manager. It is also broader than a simple reporting tool, because it usually helps evaluate alternatives rather than only display past results.

    Operational meaning in manufacturing

    Operationally, a decision support system often appears as a layer above transaction and execution systems. It may read data from ERP, MES, QMS, EAM, or SCADA-related sources and help users answer questions such as:

    • Which work orders should be expedited based on due date, material status, and machine availability?

    • Which nonconformances show patterns that may require deeper investigation?

    • What is the likely production impact if a supplier shipment is delayed?

    • Which maintenance task should be prioritized based on risk, downtime history, and current asset condition?

    Some decision support systems are simple rule-based tools. Others use optimization, forecasting, machine learning, or simulation. The term does not require any specific technical method.

    Common confusion

    Decision support system vs. business intelligence: Business intelligence usually focuses on reporting, visualization, and trend analysis. A decision support system typically goes further by helping compare options, evaluate consequences, or recommend actions.

    Decision support system vs. expert system: An expert system usually tries to encode specialist knowledge to reach conclusions in a narrow domain. A decision support system is broader and may combine data analysis, models, and user input without trying to fully mimic expert reasoning.

    Decision support system vs. control system: A control system directly monitors and controls equipment or processes. A decision support system informs people or higher-level workflows and does not inherently perform direct real-time control.

  • Data completeness

    Data completeness is the extent to which all required data is present, captured, and accessible for a defined process, record, report, or decision. In manufacturing and regulated operations, it commonly refers to whether a dataset includes every needed field, event, result, or transaction, not whether the data is correct.

    A complete record contains the expected information for its intended use. This can apply to production records, equipment logs, batch data, inspection results, material genealogy, training records, maintenance history, or ERP and MES transactions. Missing values, skipped steps, unrecorded events, or partial transfers between systems are typical signs of incomplete data.

    What it includes

    • Required fields being populated

    • Expected records or transactions being present

    • Full coverage across time, batches, lots, units, or process steps

    • Data being available where downstream users or systems expect it

    What it does not mean

    Data completeness does not by itself mean the data is accurate, timely, consistent, or valid. A record can be complete but still contain incorrect values. Likewise, a highly accurate sample of data may still be incomplete if required records or attributes are missing.

    Operational meaning

    In operational systems, data completeness often appears as a control or quality check. Examples include confirming that all serialized units have inspection results, every work order step has operator signoff where required, all material movements are posted, or all required attributes passed from ERP to MES and back. Completeness can be evaluated at the field level, record level, transaction level, or process level.

    Teams commonly monitor completeness to understand whether reports, traceability views, KPIs, and compliance records are based on a full data set or a partial one.

    Common confusion

    Data completeness is often confused with data quality as a whole. Completeness is one dimension of data quality, not the entire concept. It is also commonly confused with data integrity. Data integrity is broader and commonly refers to the reliability and trustworthiness of data across its lifecycle, including controls against loss, unauthorized change, or corruption.