Data Center is our focus

We help to build, access and manage your datacenter and server rooms

Structure Cabling

We help structure your cabling, Fiber Optic, UTP, STP and Electrical.

Get ready to the #Cloud

Start your Hyper Converged Infrastructure.

Monitor your infrastructures

Monitor your hardware, software, network (ITOM), maintain your ITSM service .

Our Great People

Great team to support happy customers.

Wednesday, August 27, 2014

Bagaimana e-commerce mempengaruhi pola beli offline ?

How Will E-Commerce Evolve to Reflect Real-World Purchasing Behavior?

  • Tweet 
  • LinkedIn 
  • Facebook 
  • Google plus 
  • Send to Kindle
  • Send to 
Creating innovative purchasing systems to better reflect people's online behaviors can have greater influence than forcing users into a single "buy" option.
We recently had the privilege of presenting at the ClickZ Live conference in Hong Kong, where we spoke on the topic of smart analytics and how organizations can use design to make better sense and use of data.
One of our key points was around conversion rates: As marketers, we spend much of our lives trying to improve these. And often, the best we can ever hope for is an incremental improvement on an average. For all of 2013, theaverage conversion rate for mobile visitors to e-commerce sites across all sectors of the economy was 1.795 percent. Although ongoing, 2014 shows little sign of fundamentally changing this number.
To look at it a different way, try selling your services to a client where you deliberately and explicitly highlight that 98.205 percent of the people you direct toward your work will neither convert, refer, or return. Handshakes will be a lot harder to get.
Related articles
No matter how you cut it, conversion rates for most types of e-commerce stores are abysmal. There's very little room to escape the fact that we are really terrible at influencing human behavior. Why is this so?

Where Conversion Rates Come From

Human behavior - although complex in its manifestations and motivations - tends not to change very much over time. Marketers are often charged with improving these numbers, usually through optimizations to a landing page. This often boils down to finding ways to make more people click a "buy" button.
The problem with this approach is the assumption that the behavior of users can be easily changed or manipulated toward the outcome we want them to complete. But the opposite is almost always the case: Whenever you try to change an existing behavior, you are preparing to enter a long, hard fight which you almost certainly will not win.
The solution to this lies not in finding ways to modify human behavior, but to let the systems we create more neatly reflect existing behaviors while influencing and encouraging the behaviors we want customers and users to exhibit.

You Can't Change Behavior, But You Can Design for It

For e-commerce, this problem is neatly captured in the "buy" button. It is the main objective we have for every visitor we get to a page. Clicking that button is, unfortunately, also historically and behaviorally, the last thing customers are interested in doing.

"Buying" Is New, but Bartering Is Eternal

Trade is not new. It is one of the fundamental drivers of human progress throughout history, and has done more to shape the economic, political, and moral landscape of our world than any other activity in human existence.
So how did we get to a point where a force of nature has been reduced to an interaction which is, on average, 98.205 percent ineffective?
The answer comes down to understanding the difference between buying and purchasing, and how we express that in terms of an e-commerce purchase. Buying, at a discrete and fixed price, is a modern invention, and more an exception to the habits and behavior around commerce that has evolved over millennia. The department store itself - one of the institutions which caused the concept of fixed pricing to be widespread - has only existed for just more than 100 years. Rather, human behavior around commerce is geared toward negotiation and barter as the mechanism that facilitates purchasing. It is small wonder then, that most people, most of the time, do not make a purchase when visiting an e-commerce website. We are giving them a single, hard, and fast choice: buy now or leave instantly.
And given the option, we know what most people choose.

"Negotiate" Is the New "Buy Now" Button

Conversion rates - or at least the low numbers we tend to see for them - are a consequence of this dynamic. Constraining customers to the constraints of our own systems causes us to miss many opportunities.
The solution to this lies not in finding ways to modify human behavior, but in letting the systems we create more neatly reflect existing behaviors while influencing and encouraging the behaviors we want customers and users to exhibit.
It is in this context that we were recently lucky to have been introduced to a company that specializes in this type of service. And by making that change, we have seen the difference that introducing an automated negotiation mechanism to the e-commerce purchase process can make to customers and vendors.

Image used with permission from

Change the Interaction to Reflect the Behavior (Don't Force People Into the Constraints of Your Product)

In the future, we expect, and will be excited to see, the evolution of interactions around e-commerce to more accurately reflect the nuances and preferences of human behavior. Ultimately, commerce and trade are ancient human traditions, and we should be aiming for much higher impact and return on behavior than the incremental improvements we are setting as the benchmark at the moment.

Tuesday, August 26, 2014

Remote BTS Site Access Control

The backbone of AKCP’s BTS Site Access Control monitoring system is the AKCess Pro Server. Installed at a central location, the AKCess Pro Server enables administration and control over your entire BTS Site Access Control infrastructure.

No Internet Connection? No Problem.

AKCP understand the challenges related to distributed network installations. AKCP designs and manufactures complete, off-grid system solutions that allow you to monitor remote sites, even over a cellular network.
AKCP’s on-board SIM-Modem ensures that your system is able to send and receive : 
  • New User / Card Data
  • Cabinet or Door Permissions,
  • Remote Unlock Actions,
  • Remote Access Logs,
  • Sensor Data Logging,
  • Alerts and Notifications,
  • Remote Site CCTV Video Capture and more…
Our intelligent remote site hardware allows you to schedule, not only when this information is sent but what information is transferred to the central office. This helps to lower cellular network costs by decreasing bandwidth requirements and increases the overall system efficiency.
If the data link between the central server and the remote site hardware is interrupted. The remote site hardware will collect and store all access, sensor and video information locally and send it once communication to the central server has been restored.
AKCP access control operates autonomously with no need for communication to a central server. To authenticate user access, the remote controller contains a complete database of up to 20,000 users.

Manage thousands of employees.

AKCess Pro Server makes it easy to add and manage users, groups, door or remote cabinet access schedules from any location.
  • Remote BTS Site Access Control Manage UsersTake control of one, easy-to-use interface and manage thousands of sites from any location in the world.
  • Names, departments and profile pictures are stored at each central server location.
  • Access Permissions can be added amended or revoked at any time.
  • Updates to Access Permissions are distributed to all cabinet locations from the software. No additional maintenance teams are required.

Access Logs and Door Status Reports

Each access attempt is recorded along with the door status. All door or cabinet access information can be exported as a report for internal QC checks.
Remote Card Swipe shown on Access Log


AKCess Pro Server can make a phone call to maintenance engineers if the remote BTS site they have been working on has not be secured correctly after having left the site.

AKCess Pro Server Automatically Calls Engineers
Remote Site Text MessageUnanswered calls can be automatically escalated to a follow up SMS or Email notification sent to multiple recipients.

AKCess Pro Server can also trigger additional on-site preventative measures such as turning on a siren alarm, a cooling system or a camera.

Off-grid rechargable power supply and battery monitoring

AKCP remote units can be used off-grid with a solar panel and battery charge controller. When in ultra low power mode, AKCP remote units draw a limited amount of power from the battery. This not only extends the life of the battery due to lowering heat dissipation, but also limits the amount of time taken to recharge the battery. This comes in useful in days of limited sunlight hours.
Temperature and Battery Health monitoring sensors can be added to check battery health so that scheduled maintenance can be arranged before power outages occur.

Synchronize Video with Event Data

Cabinet and Door Access videos can be reviewed using AKCess Pro Server from the central location. Review hundreds of hours of cabinet access attempts and filter to find critical status video in seconds. 
Cameras can be embedded into remote site cabinets to capture entry attempts on cabinets or in telecom rooms.
Choose to record 24/7 or on a sensor event to limit overall bandwidth usage.

Network engineer tidak perlu kuatir soal SDN

SDN Won't Annihilate the Networking Workforce

Network engineers have nothing to fear from SDN, argues guest contributor Michael Bushong.

By Michael Bushong | Posted Jul 2, 2013
Page of   |  Back to Page 1
Print ArticleEmail Article
  • Share on Facebook
  • Share on Twitter
  • Share on LinkedIn
Editor's Note: Occasionally, Enterprise Networking Planet is proud to run guest posts from authors in the field. Today, Michael Bushong of Plexxi brings his experience in SDN to bear against the idea that SDN will destroy networking jobs.
The networking industry at large is undergoing a major transition driven by a couple of important technology trends: Software Defined Networking (SDN) and DevOps. One of the basic tenets of both trends is that provisioning and maintaining a network remain exceedingly difficult and needlessly manual. Automation solves both issues. And after tasks become automated, the people who once performed those tasks become expendable. So the theory goes, anyway.
The principles driving the technological shift are sound. There really does exist a need to simplify the network. Tasks that are currently hopelessly manual will indeed be replaced by automated tools and processes. The rise of new technologies will absolutely make possible a new class of capabilities.
Enhance Reliability, Scalability, and Performance for Microsoft SharePoint, Exchange, and Lync
Two things get glossed over in most of the analysis, though:
  • These new technologies depend on the existence of a functional, performant underlying network.
  • The commercial viability of any rip-and-replace solution is low. Whatever gets deployed will necessarily live alongside existing technology for years to come.
Nothing about abstractions, APIs, or automated tools will render obsolete the physical network that serves as the foundation for all of these new capabilities. SDN and its complementary technologies build upon and extend the physical infrastructure. With the network as their foundation, they rely more heavily upon a fully functional infrastructure. And that infrastructure remains subject to the same pressures that make network engineers necessary today: the pressures of managing changes to adapt and growth to scale.
SDN's real power lies not in eliminating the need for network specialists, but rather in increasing the interaction of the network with its surrounding IT elements. Taken to its desired end state, SDN allows the network to be treated as a single resource. In concert with servers, storage, and applications, the network orchestrates workloads alongside its infrastructure components.
So who architects this infrastructure and makes all these pieces sing in harmony? DevOps. Chartered with creating the software glue that pulls all these disparate pieces together, the DevOps team simply won't have the time, expertise, or desire to become masters of everything, nor should it. Every moment the team spends working through the details of a supporting element is a moment it doesn't spend weaving it all together.
Some of this work is already happening. Tools like Puppet and Chef shift the point of provisioning from the network to the server side. The server guys specify what they need in terms they know--right now, a mix of networking and non-networking requirements--and those specifications are sent to agents on supporting devices that convert the instructions into device-specific configuration.
With SDN orchestration tools, application teams might document their underlying resource requirements beyond just networking. How many VMs, how much disk, or perhaps latency thresholds. As the model matures, those specifications become more abstract, perhaps involving HIPPA or PCI compliance, for example. Abstract requirements must ultimately be translated into device behavior, however. Who does that?
The DevOps person might own the software glue that deals with delegating requirements to individual IT infrastructure elements. But converting those requirements into specialized behavior that might vary on a device-by-device basis requires a degree of knowledge that comes only with a deep-seated understanding of the supporting technologies. And what if something goes wrong? Who will support all of this infrastructure, and how? A high-level view of inputs does not provide the full view of what's happening at a device level. Troubleshooting will invariably require someone who can plumb the depths of the infrastructure to find out what is actually going on.
In essence, these DevOps personnel will rely on their networking specialists to do their jobs impeccably. It is no more likely that IT will give up its network engineers than it is that IT will kill off the server or storage jobs.
That's not to say that the role of the network engineer won't change, of course. Over time, the growth of the network engineering field will slow from the pace it had achieved over the past couple of decades. Any new growth will likely favor those with programming skills, who can help orchestrate the network alongside applications and other resources. Those who continue to develop their skills along these lines will find themselves in the best position to take advantage of this.
The perfect candidate to lead the charge will be a programmer with a specialist background. And given that the network appears to be Ground Zero in this whole movement, it would appear that network engineers actually have a leg up on their competition.
Mike Bushong
Michael Bushong is currently the vice president of marketing at Plexxi, where he focuses on using silicon photonics to deliver SDN-based data center options. Prior to joining Plexxi, Mike spent 12 years at Juniper Networks, where he drove Juniper's SDN strategy, including product plans around OpenFlow, path computation element, application-layer traffic optimization and BGP traffic engineering. Prior to Juniper, Mike worked in the ASIC design tools industry.

Apa impact SDN bagi network security ?

Security pros speak out on SDN uses for network security

Large organizations see SDN and network security working together for malware blocking/detection, network auditing, and improving network management.

At this week’s VMworld shindig in San Francisco, many networking and security vendors will crow about software-defined security and software use cases for SDN. Some of this rhetoric will be nothing more than industry hype, while other banter may prove to be extremely useful in the near future. 
Practical advice for you to take full advantage of the benefits of APM and keep your IT environment
Yes, there are many interesting ways that SDN could work to enhance network security. That said, which SDN/network security use cases are really compelling and which could be considered second-tier? ESG research asked this specific question to security professionals working at enterprise organizations (i.e. more than 1,000 employees) as part of a recent network security research report (note:  I am an ESG employee). Here are the top 5 SDN use cases for network security:
  • 28% want to use SDN to help them selectively block malicious traffic to endpoints while still allowing normal traffic flows. In this case, SDN would be tied into malware detection appliances like those from Cisco, FireEye, Fortinet, Palo Alto Networks, or Trend Micro. 
  • 28% want to use SDN to improve network security policy auditing and conflict detection/resolution. Here, SDN could be used to aggregate and manage network segmentation for example. 
  • 23% want to use SDN to centralize network security service policy and configuration management. Similar to the use case above but in this case, SDN could be used to align network security policy with server virtualization (i.e. vCenter, MS System Center), cloud (i.e. AWS, OpenStack, etc.), or orchestration platforms (i.e. Chef, Puppet, etc.). 
  • 23% want to use SDN to automate network security remediation tasks. Think “self-defending networks” here. Based upon the latest threat intelligence, a firewall/SDN controller combination could generate new firewall rules on-the-fly. Firms like Norse, Vorstack, or Webroot could act as the security intelligence brains tied into SDN in this use case. 
  • 23% want to use SDN to implement more granular network segmentation for network security. Think micro-segmentation where specific users, sessions, or flows could communicate across a point-to-point VPN. For example, HyTrust works with Intel TXT to offer fine-grained segmentation aligning workloads with particular servers and trust zones. 
SDN technologies are still relatively immature so network security benefits may be a while. Nevertheless, enterprise security professionals seem to recognize that SDN offers some interesting security use cases that could help them improve risk management, incident detection, and incident response at their organizations. As such, security professionals should pay attention to SDN progress, and network security vendors should align physical/virtual network security products and services with enterprise requirements. 

Melindung pekerjaan Network Admin di era SDN

VMworld 2014: Protecting Network Admin Jobs in the Age of SDN

Cloud, network virtualization, and SDN are changing the enterprise's expectations of network admins. Netadmins must change, too.

By Jude Chao | Posted Aug 25, 2014
Page of   |  Back to Page 1
Print ArticleEmail Article
  • Share on Facebook
  • Share on Twitter
  • Share on LinkedIn
Whether you think SDN is hype or not, it's clear that virtualization and cloud computing are set to have a dramatic impact on enterprise networks—and, by extension, the job of the enterprise network administrator.SDN won't annihilate the networking workforce altogether, but in the brave new world of cloud, network virtualization, and software defined networking, a network admin who doesn't change with the times may soon find himself out of a job.
"Greenbeards." That's what networking management veteran and SolarWinds "Head Geek" Patrick Hubbard calls the old guard of the networking world, thanks to the tint the greenbeards' graying grizzle takes on from the green glow of their screens. Greenbeards at large organizations typically earned their stripes at a time when enterprise IT was heavily siloed and encouraged specialization. On the networking side, that meant specializing in configuration and manual provisioning. But now that the programmable network is on the rise, those specialties mean less than they used to.
In much the same way that virtualization and outsourcing are thinning the ranks of the junior network admins who rack, stack, and cable hardware on the data center floor, the programmable network is now threatening the desks of the network-admin-as-configuration-master. So are the sysadmins who stand to "walk away with" control of the programmable network, Hubbard said.
SolarWinds Head Geek Patrick Hubbard at VMworld 2014
Five Key Issues for DNS: The Next Network Management Challenge
All is not lost, however. To Hubbard, the changing face of the enterprise network provides "an opportunity for more ambitious admins—the cowboys—to get involved in applications as they never have before." It is, in fact, more of an imperative than an opportunity. Application service delivery, quality, and user experience have become critical to the enterprise. Issues must be resolved quickly; there's no time for helpdesk tickets to bounce back and forth between different IT silos as staffers attempt to identify the problem. Being able to identify whether performance issues originate in the application or the network is vital.
Also vital to SDN and the programmable network are scripting, automation, and policy management skills. The latter becomes especially important when you consider all the autonomous, application-driven policies that populate a programmable network, Hubbard explained. Making sure all those policies play well together and don't break anything will demand active monitoring and programming abilities. Luckily, many network admins already have those skills.
"We've been hackers for a long time," Hubbard said. "Now we're getting pulled in to the systems side." And that's a good thing, because while cloud, virtualization, and SDN might reduce the amount of networking infrastructure an organization keeps on premises, they also create new challenges, challenges often best dealt with by a network admin—if that network admin knows how to make his voice heard.
Being heard is particularly important given the relative ease with which the programmable network and its components can be configured and reconfigured. Many changes can undermine security in ways that non-network people might overlook.
As an example, Hubbard pointed to last year's Target data breach, which he believes "started as a PowerPoint. Someone decided to show how much money Target could save if they gave their HVAC company remote access to the network." The idea, Hubbard speculated, made its way up through the Target leadership until someone signed off on it. The rest is history (and so is Target's CEO, thanks to the resulting security disaster). In this case and others like it, Hubbard told me, disaster could have been prevented by an admin with a clear understanding of the network infrastructure and therefore the security impact that the policy change would have.
The voice of the network admin can also prove vital beyond the enterprise perimeter. Cloud computing tempts many an organization thanks to its purported flexibility, scalability, and cost savings, but with public and hybrid cloud comes a sudden reliance on the WAN and consequent loss of control over connectivity.
Hubbard calls this the "myopic LAN," where the enterprise can only see one end of the pipe. The networking industry now recognizes the importance of the wide area network and is working towards more LAN-like functionality on the WAN. Until those solutions mature, however, network admins can distinguish themselves by evaluating and diagnosing potential trouble spots on the wide area network in ways that non-networking folk might not consider, such as by testing for IPv6 peering issues and connectivity problems.
Ultimately, what will distinguish the successful network admin of the future from the greenbeard who gets phased out of a job will be leadership, according to Hubbard. Network admins must take charge and take ownership of their networks, whether in virtualized, software defined, or any other form, and must make application service delivery a priority. The network exists to enable the business. The successful network admin will use all the tools at his disposal to make sure that happens.
"As an admin, position yourself to be on the vanguard," Hubbard said.
Header photo courtesy of Shutterstock.

HFR memilih WebNMS untuk solusi Carrier Ethernet

HFR Chooses WebNMS to Deliver Carrier Ethernet Mobile Network Solutions with End-to-End Management

HFR Chooses WebNMS to Deliver Carrier Ethernet Mobile Network Solutions with End-to-End ManagementCalif., Pleasanton, United States (WebNMS) 
HFR, Korea’s representative vendor of wired and wireless network equipment, and WebNMS, a division of Zoho Corp. and a leading global provider of multi-vendor, network orchestration solutions, announce their collaboration in an end-to-end, MEF CE 2.0 certified solution for mobile backhaul. The HFR HA-800 series of networking systems has integrated the WebNMS Carrier Ethernet Management Solution to provide comprehensive management of high performance services from client to core.

The HFR HA-800 series combines the MEF CE 2.0 certified HA-805 10GbE Network Interface Devices (NIDs) as well as the HA-821 and HA-822 Carrier Ethernet aggregation switches to build complete mobile backhaul networks that are cost effective, simple to manage and ready for evolving high performance business and 4G services. The entire series leverages the WebNMS Carrier Ethernet Management Solution to deliver flexible MEF CE 2.0 service management. Built on the flexible WebNMS Framework, the WebNMS CE Solution delivers end-to-end service provisioning and activation, fault management, performance management, security management and QoS management.

“We chose WebNMS for its comprehensive suite of management capabilities and its flexibility in adapting to our unique features and customer requirements,” said Peter K. Cho, vice president of HFR, Inc. “HFR quickly delivered our end-to-end mobile backhaul solution with the WebNMS network and service management solution that integrates service activation, assurance, performance and fault management with powerful and intuitive visualization tools.”

Carrier Ethernet services are widely deployed and quickly growing in number and performance. In this dynamic environment, efficient service provisioning, activation and management are essential to control operational costs. As the demand for dynamic services grows, automating these functions under SDN orchestration will become increasingly important. With WebNMS supporting the HA-800 series, the end-to-end solution is ready to help transform service provider networks away from inefficient, operational silos to a unified and scalable orchestrated service delivery platform. This transformation will simplify service delivery and lower provider operational costs.

“The WebNMS Carrier Ethernet Management Solution provides a complete, standards-compliant network management platform to manage both network elements and flexibly defined services,” said Prabhu Ramachandran, director of WebNMS. “The HFR end-to-end solution demonstrates the power of network management unification which we see as a prerequisite to network automation.”

For more information about the HA-800 series of Carrier Ethernet 2.0 certified devices, please visit For more information about WebNMS, please visit

About HFR, Inc.

HFR is determined to become Korea’s leading network equipment company. HFR provides C-RAN fronthaul, carrier Ethernet, packet optical network and FTTx solutions for carriers, enterprises and data centers. The company’s key technologies include 50 patents in the radio relay transmission and WDM areas and 11 technologies in the process of patent and application registration. For more information, please visit

About WebNMS

WebNMS is a telecom software division of Zoho Corp. that specializes in network and element management framework and a software defined networking (SDN) platform that are targeted towards network service providers, managed service providers and solution vendors. With more than 25,000 deployments across the globe, the WebNMS Framework is the most preferred and reliable solution in the market today.  WebNMS has extended its features to address SDN orchestration and automate Carrier Ethernet (CE) and MPLS services. For more information about WebNMS, please visit

WebNMS is a trademark of Zoho Corp. All other brand names and product names are trademarks or registered trademarks of their respective companies.