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 the ISP code as exactly three digits, alphanumeric OLO XXX, and numeric OLO YYY when required. For EASY IP, the nga file prefix and f marker suffix are fixed; only use the order directory assigned by FiberCop. Choose NOW sources: both, adsl_YYY, or ACCESSO_UBB/gpon. Directory names do not change the XML specification.

Create, edit, or correct an order

The three-step wizard covers customer and request, FiberCop data, and final review. After customer selection it shows a complete customer card with the primary billing address; the installation site is searched among additional addresses. If it is missing, Add new address opens the shared CRM form, which also stores coordinates when available. Order code, OAO, date, customer, contact, and technology are prepared automatically when source data is available.

Edit reopens drafts, queued orders, and errors. A deposit remains immutable. Correct appears after a negative NOW notification or after whole-file rejection is detected in SFTP. It creates a new draft with a new order code, preserves the data for review, and retains the original record in history. When no notification has arrived three hours after deposit, Verify and regenerate appears. Use it only after checking the FiberCop portal and confirming that the file was not acquired. Confirmation closes the workflow locally but sends no cancellation to FiberCop, creates only one new draft with a different code, and records the relationship in history. Any incoming notification disables this option.

Complete FiberCop data correctly

Street particle, street code, number, locality, and municipality code are mandatory. ISP Billing resolves ISTAT from the indexed local ispbilling_netmap.openfiber_comuni table and uses province to disambiguate. If the locality is not recognized, the warning remains visible and the field is highlighted; correcting its name automatically repeats the lookup and fills the code when found. The wizard cannot continue while the municipality remains unresolved. Address Code is separate TIM NetMap data.

Enter surname/company name and exactly one of tax code or VAT number. The contact is sent with the official CF or O role and requires names plus a telephone contact. Phone values use the national digits-only format: +39 or 0039, spaces, and separators are removed, while a fixed-line leading zero is preserved. The limit is 15 digits. EASY IP accepts only LineaNonFonia: FTTCAB supports V0, V5, and V7; FTTH supports Z and X profiles. Delivery accepts 1–4. Provisioning SLA is not used for EASY IP; Assurance uses official codes 0 and A–G. Quality X/Y/Z, Delivery Code, date-formatted DAD, and slot 01–04 are contractual options.

XML review, draft, and SFTP transmission

Step 3 renders NGA XML with the encoding="UTF-8" declaration and validates it against the official v5.3 XSD. A non-compliant order cannot be queued or connect to SFTP. Keep as draft saves without transmission; Queue hands the order to the scheduled dispatcher. While queued, Send now remains available in the list. A confirmed technical failure exposes Retry send.

The send action creates nga_ISP_DDMMYYYY_PROGR.xml and the empty nga_ISP_DDMMYYYY_PROGRf.xml marker. The ISP code is exactly three digits and the progressive number is calculated only after the remote directory is read successfully. Cron and manual sending share the same atomic duplicate guard. After both uploads, Deposited means the files reached SFTP; it does not mean FiberCop accepted the order. Individual results arrive through NOW. If FiberCop rejects the whole container, scheduled synchronization matches a renamed .bad file or the saved XML filename in _bad/_esc and shows File rejected even when no order-level NOW exists.

Termination and other order types

Termination requires service and resource identifier. Its optional previous reference is either TI or ISP, mutually exclusive, inside the v5.3 IDRiferimento container. Use variation or migration only when the current form exposes the required case. Keep submitted orders and history; unsent drafts may be edited or deleted.

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

FiberCop specifies hourly partial NOW and acquisition ACQ files, identified by HH from 00 to 23, plus a daily RG summary by 10:00 the next day. Appearance in ISP Billing also depends on the configured SFTP synchronization run.

Sync 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