Glossary · Software
Factory: where watch signals are processed, classified and validated
Factory is the space where Innguma processes and structures signals: the analyst's working environment, in which captured information is filtered, the AI groups duplicates and classifies them, and a person reviews and validates what is relevant before it passes to the Library. Its purpose is for the analyst to start from ordered publications with no repetitions, and to devote their judgement to deciding what matters and to whom.
Which stage of the watch process does Factory cover?
Within the operation of the system, UNE 166006:2018 distinguishes source control, search, processing, value-adding, distribution and storage[1]. Factory brings the first four together in one place:
- Capture. The sources of each watch are monitored continuously: news and websites, patents, regulation and Spain’s Official State Gazette (BOE), tenders, competitors’ websites and specialist sources.
- Filtering. Each watch’s criteria decide what comes in and what stays out.
- AI processing. Innguma’s AI groups duplicates and classifies each signal by category, technology, entity, type of event, place and tone.
- Review and validation. The analyst discards the noise, validates what is relevant and records why it matters.
What is validated goes to the Library, which keeps it with its source and from which newsletters are sent.
Why group duplicates before reviewing?
A company’s press release or an official announcement is reproduced in dozens of outlets, with minimal changes to the headline or paragraph. The information retrieval textbook by Manning, Raghavan and Schütze notes that, by some estimates, up to 40% of web pages are duplicates of others[2]. If each copy arrives as a separate entry, the analyst reads the same thing several times, and the genuinely new news item is buried.
Not all repetitions are alike, and it is worth distinguishing them because they are detected in different ways:
| Type of repetition | Example | How it is usually detected |
|---|---|---|
| Exact duplicate | The same item published on two websites without changes | Direct comparison of the text or of a fingerprint of the document |
| Near duplicate | The same wire story with a different headline or a trimmed paragraph | Comparison of overlapping fragments of text (the shingling technique)[2] |
| Same fact, different wording | Three outlets describe in their own words the same agreement between two companies | Grouping by content similarity and by shared entities and dates |
The third case is the most useful for the analyst and the most delicate: grouping well avoids reading the same agreement three times; grouping badly can hide a nuance that only one of the outlets provides. That is why grouping organises, but each publication’s source remains available.
What does classification add when reviewing?
Classifying each signal by technology, entity, type of event, place and tone makes it possible to review in blocks rather than in order of arrival: first regulatory changes, then competitors’ moves, then everything else. It also helps detect gaps, such as a technology that has not had a new item in weeks.
Classification is an aid, not a verdict. In information retrieval a distinction is drawn between rules written by people, which are transparent but costly to maintain, and automatic classifiers, which learn their criteria from examples and scale better[3]. Each makes mistakes in a different way, which is why Factory combines explicit filters with AI classification and leaves the final word to a person.
Why is validation done by a person?
NIST’s profile for generative AI (NIST AI 600-1, July 2024) describes confabulation as the production of erroneous or false content expressed with confidence, and also warns of automation bias: the tendency to place excessive trust in what the system proposes[4]. In watching, the natural control point is review before publication: this is when someone with knowledge of the business checks the source and decides whether the signal changes anything for the person who will receive it.
At Innguma, the AI processes; people decide what is watched, what is published and who receives it.
How to review well in Factory
- Review with the information needs in front of you. The question is not ‘is it interesting?’ but ‘does it change anything for whoever will receive it?’.
- Start with the types of event that weigh most. A published rule or a patent granted to a competitor usually has more consequences than an interview.
- Open the source when in doubt. Each signal links to the publication it comes from; the original resolves what a headline leaves ambiguous.
- Write down the why when validating. A one-line comment (‘affects the packaging line; alert Quality’) is kept with the signal in the Library, and gives context to whoever reads it months later.
- Fix the source of the noise. If you always discard the same thing, the adjustment lies in the filter or the source, not in reviewing faster.
Sources and references
- [1] Utrilla, F. (UNE). Watch and intelligence systems in R&D management. UNE Magazine, No. 3. 2018
- [2] Manning, C. D., Raghavan, P. and Schütze, H. Introduction to Information Retrieval, ‘Near-duplicates and shingling’. Cambridge University Press. 2008
- [3] Manning, C. D., Raghavan, P. and Schütze, H. Introduction to Information Retrieval, ‘Text classification and Naive Bayes’. Cambridge University Press. 2008
- [4] NIST. NIST AI 600-1, Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile. 2024