Desk method

LinkScope Sourcing 19

LinkScope Sourcing 19 records a buyer brief for industrial LTE routers, sends that brief to factories, and lines the replies into one comparison. The service name is the desk’s own. It is not a router brand and it is not a carrier. It does not claim authorized distributor status. Factory history, capacity, and certificates stay on the proposed supplier’s documents.

Step 1. Capture bands, ports, power, quantity, destination.

Step 2. Ask for exact-model evidence, not a family brochure.

Step 3. Compare scope before any commercial rank.

Evidence ledger the desk actually keeps

Each row below is a check, not a claim that LinkScope Sourcing 19 has already passed it. If a document is missing, the row stays open.

Ledger rowWhat the buyer suppliesWhat the factory must attach
IdentityProduct family and site useManufacturer name, model, and hardware revision
RadioNeeded bands and MIMO questionBand table and antenna connector on that model
EthernetPort count and port speedInterface drawing or datasheet port map
PowerDC range or PoE classInput range and watt draw at stated conditions
Compliance questionUS destinationFCC equipment authorization file if the rule applies to that model
CommercialQuantity, timing, optional budgetCurrency, Incoterm, exclusions, lead-time basis

How a note moves through the desk

A network engineer may write frequency range, channel width assumptions, and whether the router must fail over between two SIM sockets. A procurement manager adds the US ship-to city, the piece count, and whether the budget figure is per router or for the release. A field technician adds DIN-rail depth and the ingress protection the cabinet drawing expects. LinkScope Sourcing 19 does not merge those notes into a single invented specification. Conflicting numbers stay visible as conflicts.

Public references used as question prompts include the IEEE 802 overview at standards.ieee.org and the equipment authorization rules in 47 CFR Part 2. Neither page is a test report for an unnamed router. India TEC infrastructure lists are not US approval evidence. They can still remind a buyer to ask about enclosure, input voltage, and monitoring.

The desk will not write “lower by a stated percent,” will not borrow another sourcing site’s project map, and will not say a factory was audited because a brochure shows a building. When a supplier offers an alternative modem, the ledger asks what changes: bands, MIMO, management method, license, or power draw.

Roles on one release

Related pages: configurations, BOM workflow, and the brief article.

Compatibility questions the desk will not skip

Does a matching SMA photo prove the band plan?

No. Connector sex and thread are mechanical. Band support, carrier aggregation, and MIMO layers come from the model’s radio table. Ask for that table before accepting a look-alike chassis.

Can a managed and an unmanaged path share one comparison?

A router with SNMP, a firewall, and remote firmware is a different lifecycle than a fixed bridge with no login. If both are offered, split the rows. Do not average their prices.

What if the host switch is already chosen?

Name the host, the VLAN, and whether the router is a WAN device or a LAN client. Power over Ethernet from that switch needs the class and the watt budget at the router, not the switch nameplate alone.

Send the ledger as a requirement

Put manufacturer questions, open bands, port map, power method, quantity, and destination in the form. The desk will not invent a street office for this conversation. Replies go to the work email you type.

Request Factory Quotes