A company's furnish chain network can be a complex animal. To assistance this network of constant data sharing and storgae requires a high performing dependable network backbone. An prominent part of the organize is the right level of bandwidth withhold .... T1, Ds3, or Oc3 bandwidth circuits to be exact. Making the right decision on what circuit to choose means navigating a amount of issues.
A company's furnish chain network can be a complex animal. To assistance this network of constant data sharing requires a high performing dependable backbone. An prominent part of the organize is the right level of bandwidth withhold .... T1, Ds3, or Oc3 bandwidth circuits to be exact.
High Bandwidth
Firstly, I would probably think getting a carrier Vpn assistance for the backbone as this removes many of the capacity planning and supervision issues. You can then merge on the bandwidth required to each of the premises and this can vary depending on the circumstances.
For dimensioning the tail circuits, you need to think the rate of transactions and the typical size per transaction. From this you should be able to work out bandwidth. If you assume largest transaction size and peak amount of transactions then this will give you the peak bandwidth. Add at least 20% to this to be safe (Tcp overhead will consume some of this). Also think the assistance response required. It may be possible to "smooth" some of the peaks by allowing some transactions to be slightly delayed.
Of policy you should, ideally, be working this out for each site over a 2 year period and planning for any growth. Find out from your assistance provider how quickly upgrades can be made and how much they are... It may be best to put in a bigger pipe on day 1. Where it isn't, keep track of the growth rate and factor in the assistance provider's upgrade time as well as internal delay caused by company case and funds approvals, Po signoffs, etc. And make sure you order in fullness of time.
What you need is a scalable (easily growth Bandwidth for growth), secured (at least as good as layer2 Os equivalent), and flexible (connect discrete entities that will be part of the Scm). Imho, I would rather recognize what Wan technology would be a best fit, for example Mpls or Vpls than entrance methods. I truly like the latter because of possible flexibility, protocol independence, coverage, scalability, security, and yes, flexibility. Some providers may also offer you Secured Internet gateway option thru the xPls backbone for ubiquitous connectivity and "bring your own internet" connectivity options for smaller B2B links.
Ds0, T1, T3 (Ds3), Oc3, Oc12 are all the same technology at different size and price points. The only dissimilarity is price ... You buy the size you need. Its like asking what is best to pump water, a half inch copper pipe, a 1 inch copper pipe, a 2 inch copper pipe, or a 4 inch copper pipe ... It kind of depends on how big the pump is and how much water you have.
You don't buy telecommunication for the future, its too flexible - you structure your contracts for the future, you configure your network to expand, you buy the services you need.
I would like to advise an application level arrival to rule your .....
1) application bandwidth requirements,
2) amount of locations,
3) extranet/partners requirements,
4) protection requirements,
5) finished network or internet based vpns.
Bandwidth doesn't solve all problems, you need a functional strategy to rule your currently capabilities, identify gaps with the solution today, identify gaps and then rule what it would take to address current, and hereafter capabilities, and bridge those gaps.
Companies rely on the technologies in discrete composition to rule company problems. They are chosen based on bandwidth requirements, cost, their quality to furnish assistance quality levels, local availability and the degree to which they can interoperate with other technologies and applications.
Given that you furnish chain network can have head office, warehouses, suppliers, branch office, wholesalers and retailers accessing it I advise a multpoint packet switched network as core (sic Mpls).
The Ip / Mpls Vpn can solve your connectivity qoute and you may go for a inevitable Cir (with time of day, tie of week flavor) that meets your traffic needs to keep cost low. The Cir can range from 1 mbs to Gbps (depending on location) and even remote login can be accomodated. The Eir can be built into the contract to compensate for any traffic fluctuation.
T1, Ds3, Oc3 are commodity products. It depends on the quality of the network that you need at the locations that you need. Not all services are ready everywhere. Also, you might want to think metro-ethernet, which might be cheaper. With metro-ethernet, you can take into account bursts of needed bandwidth easily. You might want to think Mpls as well. It also depends on the level of protection you need. Often that's dictated by patrimony systems, and the buyer is not willing to cut-over to a new network because of prohibitive costs or policy.
Although this all may sound very complex .... It doesn't need to be. You can get no cost help to find the best solution via the free services at Ds3-Bandwidth.com
What Bandwidth clarification (T1, Ds3, Oc3) Makes Sense For a supply Chain Network?
No comments:
Post a Comment