FiberCop EASY IP NGA: setup and orders

Module scope

The module covers FiberCop EASY IP NGA: dashboard, orders, NOW notifications, SFTP archive, settings, and NGASP diagnostics. It must not be used for unrelated Bitstream, VULA, Semi-VULA, or Full GPON flows. FiberCop is independent from OLO2OLO Panservice.

SFTP setup

Enter host, port, username, and authentication mode. Authorized SSH key is recommended; password is supported. Add the key passphrase only when required. Save and test SFTP, then verify read/write access to each configured directory.

Protect private keys and never copy them into tickets or documentation.

Operator identifiers and directories

Configure numeric ISP code, alphanumeric OLO XXX, and numeric OLO YYY. Set the EASY IP order directory and choose NOW sources: both, adsl_YYY, or ACCESSO_UBB/gpon. Directory names do not change the XML specification.

Activation order

The wizard begins with work type and customer; order code, OAO, and date are automatic. Review customer/address, contact, technology, line profile, Assurance SLA, and delivery mode. EASY IP uses LineaNonFonia.

Use compatible V/X profiles for FTTC-class services and Z/X for FTTH. Validate ISTAT municipality, street code, and NetMap-derived values instead of inventing them.

Complete Step 2 correctly

Street particle, street code, number, locality and municipality code are mandatory. Postal code, complex, staircase, floor, unit and Address Code complete the site where required. The municipality lookup returns ISTAT data while Address Code comes from TIM NetMap; they are not interchangeable free text.

Enter surname/company name and exactly one of tax code or VAT number. The contact needs role, first name, surname and mobile number. EASY IP accepts only LineaNonFonia: technology V and a V/X profile for FTTCAB, technology Z and a Z/X profile for FTTH. Delivery mode accepts 1–4; Provisioning SLA accepts SI/NO and Assurance must match the contracted Base, H.24, Saturday, FAST or GOLD option.

XML review, draft, and SFTP transmission

Step 3 renders the NGA XML preview. Saving as draft preserves the record without transmitting it; the send action creates the order XML and an empty marker file. Names combine the fixed nga prefix, ISP code, date, next remote progressive number and the configured marker suffix.

The order becomes sent only after both uploads succeed; a failure changes it to error. SFTP diagnostics search the recorded names in the order directory and its _bad, _log, _old, _esc and _riscontri variants. Finding a file does not replace the official FiberCop notification.

Termination and other order types

Termination is a separate flow and is not offered during first activation. Use variation or migration only when the current specification and form expose the required case. Keep submitted orders and history; only drafts may be deleted safely.

Provisioning from a service instance

The panel appears on compatible in-progress FTTH, FTTC/VDSL2, or EVDSL services. Coverage is checked explicitly through Coverage Map and only active compatible providers are shown. FiberCop creates a prefilled draft linked to the source service.

NOW notifications

SFTP sync ignores files without meaningful requests and persists one row per request with status, readable result, detail, and original XML. Scheduled sync uses a recent window; authorized manual recovery offers 24 hours or 30 days and runs in background.

SFTP archive and recovery jobs

The SFTP archive browses normalized remote paths, places folders first, paginates up to 100 items per page and downloads individual files. Treat downloads as sensitive technical and personal data; use the Notifications view for structured status, cause, message, appointment and request history.

The ordinary cron defaults to a light seven-hour window and processes enabled FiberCop tenants. A manual 24-hour or 30-day recovery is queued, guarded against overlapping runs and consumed by the cron in batches. Its state progresses through queued, running, completed or error and reports new, existing, unchanged and analyzed rows.

Calendar appointments

A notification with appointment date/time can create a one-hour activity. Configure separate activity types with and without customer. Customer-linked activities may send email/WhatsApp reminders one hour before; unlinked ones do not.

NGASP

Enable NGASP and configure timeout, TLS verification, Client Key/Secret, and X-OLO header. Portal credentials are not necessarily API Gateway credentials; authorized client scopes are required. Keep TLS enabled and exclude tokens and payloads from documentation.

Checklist

• Confirm EASY IP NGA agreement
• Configure ISP/OLO codes
• Use an authorized SFTP key
• Test directories
• Select NOW sources
• Run coverage explicitly
• Validate technical profile and address codes
• Follow notifications to closure
• Configure two appointment types
• Use dedicated NGASP credentials