Data Management & Integration

Plan and execute the migration of legacy data into IFS Cloud using the Data Migration Manager and Data Migration Jobs in Solution Manager. Covers defining migration jobs against logical units, applying rules/validations/transformations, executing loads online, in background or on schedule, and reconciling error rows through iterative loads up to cutover.

Enable business users to load and maintain IFS Cloud data through the IFS Data Migration Excel Add-In. Migration jobs with procedure type Excel Migration let authorized users query data from and save data into single or multiple logical units directly from Microsoft Excel, governed by method lists and column mappings defined centrally.

Design and operate message- and file-based integrations using IFS Connect: transport connectors (Readers for inbound, Senders for outbound), routing rules with destination addresses, and transformers (XSL or Java) that reshape payloads. Provides the standard asynchronous integration backbone between IFS Cloud and external business systems, hubs and devices.

Expose and consume IFS Cloud functionality through RESTful OData APIs based on the same projections used by IFS Cloud Web, discovered via the API Explorer as OpenAPI/OData specifications. Covers API discovery, client registration/authentication, efficient query design and API lifecycle governance for synchronous integrations.

Establish the foundational data model of IFS Cloud: create companies from delivered company templates, set up basic company data (valid-from date, accounting currency, chart of accounts), define sites, persons, resources and calendars under Application Base Setup, and govern ongoing basic/master data maintenance across modules.

Move aged transactional data out of the IFS Cloud production tables to an archive destination to protect performance and meet retention policy. Built on data archive objects (table trees driven by a master table), generated archive packages, and data archive orders that schedule which objects execute when — with view/restore possible when archiving to an Oracle table in the same database.

Provision IFS Cloud data for reporting and BI: Information Sources expose star-schema views of application data in OnLine or DataMart access modes, Analysis Models deliver business-oriented star schemas optimized per application area, and IFS Business Reporter consumes the Business Reporting & Analysis framework for financial/operational report design. Covers access-mode strategy, data mart refresh and downstream BI export.

Exchange structured text files with banks, authorities and other external parties using the External Files Interface — a general toolkit for input and output of text files in online or batch mode. File types tie a file to an interface, file templates define the layout, and delivered templates cover common financial documents such as external vouchers, customer payments and supplier invoices on file.

Manages the site environmental permit and waste duty of care obligations in IFS Cloud, holding permits, exemptions, waste transfer notes and hazardous waste consignment notes as controlled Documents against the Project. Waste carrier and receiving site registration checks are recorded on the Supplier record and enforced before award of a waste contract. Waste movements and recovery rates are reconciled against project targets for client and regulator reporting.

Runs the recurring internal and external audit cycle for the data centre - Uptime Institute M&O Stamp of Approval, ISO/IEC 27001 and SOC 2 - from a single control and evidence register in IFS Cloud. Each control is mapped to the PM Action, Work Order, Measurement history, Document or qualification record that evidences it, so producing an evidence pack becomes a query rather than a collection exercise. Findings and non-conformances become tracked corrective actions with owners, due dates and closure evidence.

IFS Cloud ships a genuine Export Control capability: export control codes and classification schemes held per part and per order country, approved codes on Supplier for Purchase Part, and Export License records carrying effective dates, coverage and restrictions on site, consignee, supplier, forwarder, customer, end user, end usage and nationality, which the purchase, customer and shop order flows test through Find and Connect Export License. What IFS does NOT do is determine the classification: ITAR USML categories and EAR ECCNs are regulatory constructs that IFS neither ships nor interprets, so the control code values are customer-maintained master data. Licence applications, TAA/MLA agreements and any government filing happen entirely outside IFS.

Contract data deliverables can be run in IFS Cloud using standard building blocks: Document Management document classes and revisions with approval routing, access control and document distribution for the deliverable artefacts; Project and Project Activity for the schedule the deliverable is due against; and Information Sources with Business Reporter for producing the reported content. What IFS does not provide is the contractual construct: there is no contract data requirements list, data item description, deliverable-due-date-driven obligation object, or acceptance/rejection cycle in the product, and no interface to any government invoicing or receipt-and-acceptance portal. Those are modelled as project activities and document classes by convention, or held in an external contract management system.

Establishes the data governance regime that keeps the FM information estate trustworthy across IFS Cloud and any surrounding CAFM/IWMS, CAD and sensor systems. It fixes the golden source per data domain, appoints owners and stewards, enforces validation at entry, and runs a recurring data quality scorecard with a controlled remediation workflow. Without it, space, asset and PPM reporting degrade faster than they are maintained.

Governs the recurring PHMSA reporting calendar and the retention regime behind it. Mileage, facility, material and installation-date data is extracted from the IFS Cloud asset register, leak and damage counts from Work Orders and Fault Reports, reconciled against the prior submission, approved, and filed through the PHMSA Portal. Submitted reports, supporting extracts and integrity management records are retained as controlled Documents for inspection.

Establishes IFS Cloud as the electronic system of record for medical device servicing activities, so that service records held electronically in place of paper satisfy 21 CFR Part 11 alongside the underlying Part 820 predicate rule. The design decides which records are Part 11 records, controls system access and electronic signature use, and preserves a time-stamped audit trail. Part 11 artefacts such as the audit trail and the validation record have no standard IFS Cloud object and are handled as system capability and controlled documents.

Takes a triaged complaint plus its service and diagnostic evidence and reaches a documented, clock-aware reportability decision for FDA MDR and EU MDR vigilance. IFS Cloud supplies the operational evidence - Case, Fault Report, service report, UDI and serial identification, awareness date - while the decision, the eMDR submission and the not-reportable rationale live in the regulatory system. The process exists to make the awareness date defensible and the decision traceable to a specific device and event.

Closes a field action and discharges the reporting obligations that attach to it. IFS Cloud supplies the reconciliation evidence - units corrected, removed, scrapped and unaccounted, drawn from Work Order completion and part serial history - which feeds the 21 CFR Part 806 correction/removal report, the EU MDR competent-authority notification and the recall termination request. The 806 report, the non-reportable record and the closure file itself have no standard IFS Cloud object and sit in the eQMS or Document Management.

Closes the monthly production cycle by validating metered volumes at well, battery and custody transfer points, running the allocation model that distributes measured sales volumes back to wells and joint venture partners, and reconciling allocated against custody transfer quantities. Validated volumes and values are posted into IFS Cloud Financials for revenue, royalty and partner billing, with the reporting pack issued to regulators and partners before the period is locked. The allocation engine itself sits outside IFS; IFS holds the meter and equipment master, the resulting financial postings and the reporting evidence.

Runs the leak detection and repair programme that keeps fugitive methane and VOC emissions inside permitted limits. In IFS Cloud each monitorable component is tagged as a Functional Object, survey rounds are driven by Maintenance Plans and PM Actions, screening values are captured as Measurements and every exceedance raises a repair Work Order with a re-monitoring check. The LDAR survey record itself has no standard IFS object and is retained as a controlled Document.

Manages the recurring statutory submissions an oil and gas operator owes its regulators - greenhouse gas and emissions returns, offshore safety performance measures, incident and dangerous occurrence reports. In IFS Cloud the obligation register is held as controlled Documents, each submission is scheduled so preparation work is generated ahead of the deadline, and the reported figures are traced back to Measurements, Work Orders and incident records. Submission itself remains an external electronic filing.

The monthly and annual cycle that turns raw outage events into audited reliability indices - SAIFI, SAIDI, CAIDI and the related IEEE 1366 measures - classifies major event days, publishes internal and regulatory reports, and drives the reliability improvement plan. The outage event data originates in the OMS and the customer count in CIS, while IFS Cloud contributes the asset-side attribution: which Functional Object or Linear Asset segment failed, the Fault Report cause code, and the Work Order restoration record that supports duration and cause validation. The indices then feed circuit-level worst-performing analysis, inspection cycle changes and the risk-based investment plan.

Governs the collection, retention and presentation of the evidence that proves compliance with the NERC vegetation management standard, and keeps the utility audit-ready between engagements. In IFS Cloud the evidence is the operational record itself - dated Work Orders, Work Tasks, inspection records, Documents and Measurement readings against Linear Asset spans - assembled per requirement rather than re-keyed into a separate compliance system. The process also produces the quarterly periodic data submittal on vegetation-related Sustained Outages.

Turns a confirmed order into a live, billable service by orchestrating the logical configuration and activation of the network service and keeping IFS Cloud, the OSS and the billing platform in step. IFS Cloud holds the commercial and installed-base view - Customer Order, Service Contract and the service Functional Object - and exchanges service order, activation and status events with the provisioning platform, typically over TM Forum Open APIs. Because the value here is integration and data consistency rather than field execution, the process is owned as a data and integration capability.

Aggregate monitoring results, violations, and corrective actions and submit required reports to the state primacy agency on the regulatory calendar; manage violation lifecycle including tiered public notification, produce the annual Consumer Confidence Report, and maintain an auditable submission repository.

Turns the NPDES permit monitoring matrix into a repeatable, auditable sampling cycle inside IFS Cloud. Outfall and process sampling points are modelled as Functional Objects with Maintenance Plans that generate scheduled Work Orders, and analytical values are captured as Measurement / Parameter readings with chain-of-custody evidence held in Document Management. Validated results become the single source of truth feeding DMR preparation and exceedance response.

Assembles validated effluent monitoring data held as Measurement / Parameter readings into the periodic Discharge Monitoring Report, applies permit-defined statistics, routes it for certification by a duly authorised representative, and evidences electronic submission. Under the EPA NPDES Electronic Reporting Rule the DMR is filed through NetDMR or a state eDMR system and flows into ICIS-NPDES. IFS Cloud holds the underlying data, the approval trail and the archived submission receipt as controlled Documents.