Submissions

Login or Register to make a submission.

Author Guidelines

Authors are invited to make a submission to this journal. All submissions will be assessed by an editor to determine whether they meet the aims and scope of this journal. Those considered to be a good fit will be sent for peer review before determining whether they will be accepted or rejected.

Before making a submission, authors are responsible for obtaining permission to publish any material included with the submission, such as photos, documents and datasets. All authors identified on the submission must consent to be identified as an author. Where appropriate, research should be approved by an appropriate ethics committee in accordance with the legal requirements of the study's country.

An editor may desk reject a submission if it does not meet minimum standards of quality. Before submitting, please ensure that the study design and research argument are structured and articulated properly. The title should be concise and the abstract should be able to stand on its own. This will increase the likelihood of reviewers agreeing to review the paper. When you're satisfied that your submission meets this standard, please follow the checklist below to prepare your submission.

Submission Preparation Checklist

All submissions must meet the following requirements.

  • This submission meets the requirements outlined in the Author Guidelines.
  • This submission has not been previously published, nor is it before another journal for consideration.
  • All references have been checked for accuracy and completeness.
  • All tables and figures have been numbered and labeled.
  • Permission has been obtained to publish all photos, datasets and other material provided with this submission.

Original Research Articles

Original Research Articles constitute the principal publication category of the journal. They are intended to report complete studies that make substantial and original contributions to engineering informatics and intelligent systems. Such contributions may take the form of new theories, computational methods, knowledge frameworks, models, system architectures, workflows, or rigorously validated engineering applications.

The central requirement is not merely improvement on a single performance metric, but the presentation of a reproducible, interpretable, and testable chain of evidence demonstrating why the proposed method or system is effective, under what conditions it remains effective, and where its applicability boundaries or failure modes may lie in complex engineering environments. EIIS particularly welcomes studies that integrate engineering knowledge, standards and regulations, physical consistency, and multi-source heterogeneous data processes. Authors are expected to describe clearly the engineering problem setting, data and knowledge sources, evaluation protocol, baselines, robustness analyses, and practical deployment implications. Manuscripts primarily centred on dataset release, benchmark construction, opinion-led discussion, or brief milestone reporting may be more appropriately considered under the journal's Benchmark and Resource, Perspectives, or Communication formats.

Review Articles

Review and Foresight Articles are intended to synthesise and critically structure the development of an important research theme, while also identifying future directions for the field. EIIS welcomes contributions that move beyond descriptive literature aggregation to provide conceptual clarification, methodological comparison, and agenda-setting insight. Particularly encouraged are articles addressing the limits of purely black-box paradigms, the emergence of knowledge-driven and constraint-computable approaches, the evolution of trustworthy evaluation frameworks, and the broader transformation of engineering work under intelligent systems.

These articles should help the community respond to technological opportunities and engineering constraints in a proactive and organised manner. They may be commissioned by the editorial team, but high-quality unsolicited submissions or proposals may also be considered where they demonstrate strong scholarly value and clear relevance to the journal's mission.

Benchmarks

Benchmark and Resource Articles are intended to establish reusable community assets that enable fair comparison, transparent evaluation, and cumulative progress. Rather than limiting this category to dataset publication alone, EIIS views benchmark contributions more broadly as including curated datasets, multimodal corpora, challenge problems, annotated engineering cases, reference ontologies, evaluation suites, simulation environments, baseline implementations, and reproducibility toolchains.

EIIS places particular emphasis on resources that reflect the realities of engineering practice, including heterogeneous and multimodal data, explicit engineering constraints, realistic acceptance criteria, reproducibility requirements, and trustworthiness-oriented evaluation dimensions such as robustness, compliance, traceability, or uncertainty awareness. A typical benchmark or resource contribution should clearly define the engineering problem, scenario assumptions, data provenance and licensing, uncertainty or quality characteristics, reference baselines, and the evaluation metrics through which future methods may be compared. Such articles may be submitted directly and may also be actively solicited from industrial partners, major engineering projects, and broader research communities where shared infrastructure is especially needed.

Short Communications

Short Communications are designed for the rapid dissemination of concise but meaningful advances. These may include a well-defined theoretical result, a focused methodological innovation, a compact experimental finding, a tool or workflow milestone, or a carefully delimited engineering case with broader significance. The aim is not incompleteness, but precision: a Short Communication should make one clear contribution and support it convincingly.

EIIS also welcomes practice-oriented communication from industry, public-sector organisations, and engineering practitioners. Such contributions may report deployment lessons, implementation barriers, validation experiences, data challenges, or emerging engineering needs that can inform future research. For launch-stage policy, these communications may be handled under a unified format, subject to concise length limits and clear evidential standards, while preserving sufficient flexibility for the journal to refine this category as the field evolves.

Perspectives

The Perspectives section is intended for field-shaping arguments on the future direction of engineering intelligence. EIIS is especially interested in perspectives that examine the transition from isolated model-level performance to system-level engineering capability. In many high-risk engineering settings, the core limitation is no longer the absence of powerful models, but the absence of intelligent systems that can be verified, audited, governed, and responsibly deployed. End-to-end black-box decision pipelines often introduce unacceptable risks, including unfaithful outputs, hallucination, missing evidence chains, poor traceability, and weak enforcement of engineering standards or physical consistency.

Accordingly, this section welcomes rigorous, testable, and reproducible perspectives and roadmaps rather than purely opinion-based commentary. Contributions should define the system boundary of the problem under discussion, identify plausible failure modes, and propose concrete pathways for embedding engineering constraints, physical consistency, auditable evidence chains, and trustworthy evaluation mechanisms into future architectures and workflows. Strong Perspectives papers should help the field move from broad aspiration to disciplined research direction.

Privacy Statement

Effective date: 26 Feb 2026
Last updated: 15 Mar 2026

Engineering Informatics and Intelligent Systems (EIIS) and its publishing platform, operated by Informatics Foundry (“we”, “us”, “our”), are committed to protecting your personal data and respecting your privacy.

This Privacy Statement explains how we collect, use, store, disclose, and otherwise process personal data in connection with the operation of this journal website, including user registration, manuscript submission, peer review, editorial administration, publication, and related communications.

1. Data Controller

The data controller responsible for the personal data processed through this journal site is:

Informatics Foundry Ltd.
71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ
General contact: info@informaticsfoundry.org

If you have any questions about this Privacy Statement or wish to exercise your data protection rights, please contact us using the details above.

2. Scope of this Privacy Statement

This Privacy Statement applies to personal data collected through this journal website and related editorial and publishing processes, including when you:

  • create an account on the journal site;
  • submit a manuscript or act as a co-author;
  • serve as a reviewer, editor, guest editor, or advisory board member;
  • subscribe to publication alerts, newsletters, or journal announcements;
  • contact us through the website or by email;
  • browse the website where technical data such as IP address, browser type, and server logs may be collected for security and site administration purposes.

3. Categories of Personal Data We Collect

Depending on your relationship with the journal, we may collect and process the following categories of personal data:

Account and identity information

  • name;
  • username;
  • title;
  • institutional affiliation;
  • ORCID iD or other scholarly identifiers, where provided;
  • role on the platform (e.g. author, reviewer, editor, reader).

Contact information

  • email address;
  • postal address, where relevant;
  • telephone number, where voluntarily provided.

Professional and publication-related information

  • biography, expertise, research interests, keywords, reviewing interests;
  • manuscript files, supplementary files, cover letters, responses to reviewers, editorial decisions, and correspondence;
  • authorship, affiliation, funding, conflict-of-interest, and acknowledgement information;
  • reviewer recommendations, reports, scores, and editorial comments.

Technical and usage information

  • IP address;
  • device and browser information;
  • log files and timestamps;
  • security-related and authentication records;
  • cookie-related data, where applicable under the site’s cookie settings.

Communications and preferences

  • your preferences for receiving alerts, announcements, or review invitations;
  • correspondence sent to or from the editorial office.

4. Purposes of Processing

We process personal data for the following purposes:

Journal operation and account administration

  • to create and manage user accounts;
  • to authenticate users and maintain platform security;
  • to administer access rights and user roles.

Submission, peer review, and editorial management

  • to receive, process, assess, and manage manuscript submissions;
  • to administer peer review and editorial decision-making;
  • to identify, invite, and communicate with reviewers, editors, and authors;
  • to maintain the integrity, traceability, and auditability of editorial workflows.

Publication and scholarly communication

  • to publish accepted articles and associated metadata;
  • to display author names, affiliations, biographies, acknowledgements, and other publication information where relevant;
  • to index, archive, disseminate, and preserve scholarly content.

Communications

  • to send transactional and service-related communications, such as submission confirmations, editorial decisions, reviewer invitations, password resets, and system notices;
  • where you opt in, to send new publication alerts, journal announcements, and related updates;
  • where you opt in or where otherwise lawful, to contact you regarding opportunities to review submissions.

Compliance, security, and administration

  • to comply with legal, regulatory, ethical, and publishing obligations;
  • to prevent misuse of the platform, fraud, unauthorised access, or other security incidents;
  • to establish, exercise, or defend legal claims.

5. Legal Bases for Processing

Where UK GDPR and/or EU GDPR applies, we rely on one or more of the following legal bases, depending on the context:

Performance of a contract or steps prior to entering into a contract
For example, where processing is necessary to create and maintain your account, administer submissions, manage peer review, or provide publishing services you request.

Legitimate interests
For example, for operating and improving the journal, maintaining editorial records, ensuring the integrity of scholarly publishing, preventing misuse, communicating with authors, reviewers, and editors in connection with journal workflows, and securing the website and systems. Where we rely on legitimate interests, we consider and balance those interests against your rights and freedoms.

Consent
For example, where you choose to receive publication alerts, announcements, or other optional communications, or where local law requires consent for certain communications or technologies.

Legal obligation
Where processing is necessary to comply with applicable law, regulatory requirements, publishing ethics obligations, audit requirements, or lawful requests from public authorities.

6. How We Use Optional Checkboxes and Preferences

Where the registration form allows you to tick boxes such as:

  • receiving notifications of new publications and announcements; and/or
  • being contacted with requests to review submissions,

these options are voluntary. If you opt in, we will use your contact details and relevant professional profile information for those purposes. You may withdraw your consent or update your preferences at any time through your account settings or by contacting us.

Please note that essential service communications relating to your account, submissions, reviews, editorial decisions, security, or platform administration are not marketing communications and may still be sent where necessary for the operation of the journal.

7. Recipients of Personal Data

We may share personal data, strictly on a need-to-know basis, with the following categories of recipients:

  • editorial staff, editors, guest editors, and authorised journal administrators;
  • reviewers, where necessary for peer review workflows;
  • authors and co-authors, where necessary within submission and publication processes;
  • hosting providers, IT service providers, email delivery providers, backup providers, and other processors supporting the journal platform;
  • indexing, abstracting, archiving, DOI registration, plagiarism screening, preservation, and scholarly infrastructure services, where applicable;
  • professional advisers, auditors, insurers, or legal representatives where necessary;
  • regulators, law enforcement agencies, courts, or other public authorities where required by law or where necessary to protect legal rights.

We do not sell your personal data.

8. International Transfers

Your personal data may be processed in the United Kingdom, the European Economic Area, or in other countries where our service providers, journal participants, or scholarly infrastructure partners operate.

Where personal data is transferred outside the UK or EEA, we will take appropriate steps to ensure that such transfers are made in accordance with applicable data protection law, including by relying on adequacy regulations/decisions, standard contractual clauses, or other lawful safeguards where required.

9. Data Retention

We retain personal data only for as long as necessary for the purposes described in this Privacy Statement, including to maintain the scholarly record, support editorial transparency, comply with legal and ethical obligations, resolve disputes, and enforce agreements.

In practice:

  • account and editorial workflow records may be retained for as long as the journal account remains active and for a reasonable period thereafter;
  • submission, peer review, and publication records may be retained long term where necessary to maintain the integrity of the academic record and editorial history;
  • optional communication preferences are retained until you unsubscribe or request deletion, subject to any overriding record-keeping requirements;
  • technical logs are typically retained for a limited security and operational period.

Where a precise retention period is not possible, we determine retention by reference to the nature of the data, the purpose of processing, legal obligations, dispute risk, and the need to preserve the scholarly and publishing record.

10. Your Rights

Subject to applicable law, you may have the right to:

  • request access to your personal data;
  • request correction of inaccurate or incomplete personal data;
  • request erasure of your personal data in certain circumstances;
  • request restriction of processing in certain circumstances;
  • object to processing based on legitimate interests;
  • request data portability where applicable;
  • withdraw consent at any time where processing is based on consent;
  • lodge a complaint with a supervisory authority.

These rights are not absolute and may be subject to legal or ethical limitations, including where retention is necessary for the integrity of the scholarly record, compliance with publishing obligations, or the establishment, exercise, or defence of legal claims.

To exercise your rights, please contact: editorial@informaticsfoundry.org

11. Complaints

If you are located in the United Kingdom, you have the right to lodge a complaint with the Information Commissioner’s Office (ICO).
If you are located in the European Economic Area, you may also lodge a complaint with your local data protection supervisory authority.

We would, however, appreciate the opportunity to address your concerns first.

12. Security

We implement appropriate technical and organisational measures designed to protect personal data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure, or access. These measures may include access controls, password protection, role-based permissions, secure hosting arrangements, logging, and backup procedures.

However, no internet-based system can be guaranteed to be completely secure, and you should also take reasonable steps to protect your account credentials.

13. Cookies and Similar Technologies

This site may use cookies or similar technologies that are necessary for site functionality, login sessions, security, preferences, and analytics.

Where required by law, non-essential cookies will only be used with your consent. Further details should be provided in the site’s Cookie Notice or Cookie Settings page.

14. Third-Party Links and Services

This journal site may contain links to third-party websites or integrate third-party scholarly services. We are not responsible for the privacy practices of third-party sites or services, and you should review their privacy notices separately.

15. Publication of Personal Information in the Scholarly Record

Where a manuscript is accepted for publication, personal data forming part of the scholarly record may be published, including author names, affiliations, correspondence details where designated, funding information, acknowledgements, ORCID iDs where supplied, and other metadata relevant to publication and indexing.

Because the publication record serves academic, citation, and archival purposes, removal or alteration of published information may not always be possible except in accordance with editorial policies, legal requirements, and correction or retraction procedures.

16. Children

This journal site is intended for academic, professional, and scholarly use and is not directed to children. We do not knowingly collect personal data from children through this site.

17. Changes to this Privacy Statement

We may update this Privacy Statement from time to time to reflect legal, technical, or operational changes. Any updated version will be posted on this page with a revised “Last updated” date.