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.

Friday, February 19, 2016

Perbedaan Produk AKCP


sensorProbe2sensorProbe8securityProbe 5ESsecurityProbe 5E
DimensionSize 4.5″ x 2.5″ x 1.25″Size: 8.5″ x 5.43″ x 1.80″1U Rack Mount StandardSize 8.5″ x 5.43″ x 1.80″Size: 8.5″ x 5.43″ x 1.80″ (camera dome height 3.62″)
Weight0.242 pounds1.72 pounds2.2 pounds2.4 pounds
Mounting0u rackmount, or wall hanging1U rackmount includes rackmountkit.1U Rack Mount StandardRack mount brackets included
Status IndicationLED indication for PowerLED for Network ConnectivityLED for Sensor online and threshold statusLED indication for PowerLED for Network ConnectivityLED for Sensor online and threshold statusLED indication for Power
LED for Network Connectivity
LED for sensor online and
threshold status
LED indication for PowerLED for Network ConnectivityLED for Sensor online and threshold status
Interface portsStandard 10 Base-T Ethernet RJ-45Standard 10 Base-T Ethernet RJ-454x RJ-45 Expansion Ports
115.2K BPS Data Transfer Rate
Simultaneous functionality
between Expansion Ports &
RS485 port threshold status
1 RS485 Modbus port1 Standard 10/100 Base-T Ethernet RJ-45 port
Power Requirements7.0 – 9 V/> = 1 Amp7.0 – 9 V/>= 1 Amp7.0 – 9 VDC, 3Amp7.0 – 9 V/>= 3 Amp
Power ConsumptionTypical 1.125 Watt, 0.15ATypical 1.425 Watt, 0.19ATypical 5.025 Watt, 0.67ATypical 6.150 Watt, 0.82A
Input2 RJ-45 ports for connecting AKCP SensorsConfigurable analog inputs on any of the 2 RJ-45 Sensor ports(0-5VDC)8 RJ-45 ports for connecting AKCP SensorsConfigurable analog inputs on any of the 8 RJ-45 Sensor ports(0-5VDC)8x RJ-45 Sensor Ports
4x RJ-45 Expansion Ports
1x USB port (Version 2.0)
Audio In (Analog) 2.5″ jack
RS485, 2 Pin Terminal box, (used for Modbus)
8 RJ-45 ports for connecting AKCP SensorsVideo Input port VI-4, NTSC/PAL, Jack BNC 750 hm 30 Au1 USB port (Version 1.1)RS485, 2 pin Terminal box
Line In, 3.5mm jack
4x E-in for expansion module input
OutputConfigurable output signals (0VDC/5VDC) on any of the 2 RJ-45 Sensor portsConfigurable output signals (0VDC/ 5VDC) on any of the 8 RJ-45 Sensor portsExt. Speaker Out, 2.5″ jack (Analog)
Mic Out, 2.5″ jack (Analog) (For modem application)
Ext. Speaker Out, 2.5″ jack (Analog)Mic Out, 3.5mm jack (Analog)M (for modem application)
Operating EnvironmentTemperature : Min. -35°C – Max. 80°CHumidity : Min. 20% – Max. 80%(Non-Condensing)Temperature : Min. -35°C – Max. +55°CHumidity : Min. 20% – Max.
80%(Non-Condensing)
Temp : Min. -35° C – Max. +55° C
Humidity : Min. 20% – Max. 80% (Non-Condensing)
Temperature : Min. -35°C – Max. +55 CHumidity : Min. 20% – Max.
80%(Non-Condensing)
ComponentsManufactured using highly integrated, low power surface mount technology to ensure long term reliability.Manufactured using highly integrated, low power surface mount technology to ensure long term reliability.Manufactured using highly integrated, low power surface mount technology to ensure long term reliability.
CPU: AKCP i.MX25 Processor
On-board SD Flash Slot
Manufactured using highly integrated, low power surface mount technology to ensure long term reliability.32-bit Xscale PXA270 520 MHz Processor running Linux Kernel8 MB Flash memory128 MB SDRAM
2 Gb SD Card

Tuesday, February 16, 2016

5 Keuntungan gunakan cloud-based Mobile Device Management

5 advantages of using cloud-based mobile device management


Now manage your mobile devices on the cloud
Image Courtesy: Google
The cloud is a game changer for the IT industry, optimizing data storage and operations. As Mobile Device Manager Plus embraces the SaaS model with the launch of its cloud edition, here’s a highlight of the top five benefits of a cloud-hosted MDM suite. 
#1 Reduced infrastructure expenditure. 
The cloud edition of Mobile Device Manager Plus doesn’t require anything more than a good computer with a functional operating system  and a browser. This means you don’t need to purchase any additional hardware or software solutions to run the MDM suite. Small businesses with little  capital investment will find this aspect particularly beneficial.
#2 Streamlined processes. 
No download, installation, or setup is required. All you need is a simple sign-up to start managing your devices. In addition to that, Mobile Device Manager Plus Cloud edition has automated a few time-consuming setup steps such as NAT, mail server, and proxy configurations. 
#3 An update for convenience.
Ever wondered what Adobe Reader keeps changing with those frequent auto-updates? Regular updates can be quite annoying. Thankfully, Mobile Device Manager Plus Cloud edition lets you forget that those pesky hotfixes and updates ever bothered you. Instead, all the progress and changes will be automatically incorporated with a brief heads up under the “What’s new” section of the homepage. 
#4 Decentralized operations, accessible at any time.
You can watch over your enterprise’s mobile devices from the luxury of, well, anywhere. No need to detain data at the workplace. It’s now possible to change profile restrictions, run scans, or generate audit reports on the go and at your convenience.
#5 Pay as you go.
Allocating capital for MDM software year after year is now passé. Mobile Device Manager Cloud edition lets you pay on a subscription basis, monthly, or yearly, for the number of devices purchased. It is scalable to match various requirements. You no longer need to worry about complicated bills or invoices because the payment for your managed devices will be charged  from your credit card or bank account as you go. There are no hidden cancellation fees or binding contracts.
For the big benefits picture, just try it out.
Mobile Device Manager Plus is fully functional both on-premises and on-demand, with the same features. There are unique advantages for each option because large organizations with sensitive data might prefer to go on-premise. The deployment decision can be based on the nature of the enterprise and IT requirements. Get a better idea by checking out the free trial for 30 days or speaking to our support executive, who can help you decide on the best option.

Password Manager Pro digunakan ISP untuk melindungi data center

Snapshot of success: Password Manager Pro helps Indian Internet service provider regulate privileged access to its data centers.

Being a triple-play service provider in India is no easy work. The bundled offering of multiple services (Internet, telephone, and television) calls for a sophisticated data center infrastructure that can handle the wide scale of operations, manage all services simultaneously, and deliver a high-speed network experience to the users. Moreover, modern communication networks face a considerable share of privacy and security threats, which can be overcome only by implementing robust controls around the infrastructure resources and their access.
Password Manager Pro telecommunication
When ACT, India’s renowned triple-play service provider, faced a similar business challenge—the need to streamline privileged access to its data center and adopt an effective password management routinethey decided to let Password Manager Pro do the job for them. With ManageEngine’s privileged access management solution, the Internet service provider has successfully established a central mechanism to regulate management of privileged passwords and access to data centers.
Read the full story of ACT’s security makeover here.

10 Best Practices terkait Incident di IT

10 Best Practices to Deal with Major Incidents in IT

ME_blog-2
Major incidents affect organizations, big and small without exception. Major incidents like bank transaction server crashes, airline check-in software crashes, and stock market outages have adverse impact on customersUnder such circumstances, help desks are slammed with calls only adding to the panic and chaos. It becomes a race against time to find a fix, as every hour of outage could translate to thousands, if not millions of lost dollars. IT technicians often find themselves answering calls and replying to emails rather than trying to find a fix. What does it take to keep a cool head and steer your organization out of the situation? Follow these 10 best practices to deal with major incidents that come your way.
Clearly Define a Major Incident
When an issue causes a huge business impact on several users, you can categorize it as a major incident. It is one that forces an organization to deviate from existing incident management processes. Usually, highpriority incidents are wrongly perceived as major incidents. This is probably due to the absence of clear ITIL guidelines. Therefore, to avoid any confusion, you must define a major incident clearly based on factors such as urgency, impact, and severity.
Have Exclusive Workflows
Implementing a robust workflow helps you restore a disrupted service quickly. Separate workflows for major incidents help in seamless resolution. Focus on automating and simplifying the following when you formulate a workflow for major incidents.
  • Identifying the major incident 
  • Communicating to the impacted stakeholders
  • Assigning the right people
  • Tracking the major incident throughout its life cycle
  • Escalation upon breach of SLAs
  • Resolution and closure 
  • Generation and analyses of reports
Reel in the Right Resources 
Ensure that your best resources are working on major incidents. Also, clearly define their roles and responsibilities because of the high impact these incidents have on business. You could have a dedicated or a temporary team depending on how often major incidents occur. Some organizations have a dedicated major incident team headed by a major incident manager, whereas others have a dynamic, ad hoc team that has experts from various departments. Your primary objective must be to keep your resources engaged and avoid conflict of time and priorities. 
Train Your Personnel and Equip Them With the Right Tools  
You don’t know when a major incident can strike your IT, but the first step to handling it is by being prepared. Divide your major incident management team into subteams and train them in major incident management. Assign responsibilities by mapping skills with requirements. Run simulation tests on a regular basis to identify strengths, evaluate performance, and address gaps as needed. This would also help your team to cope with stress and be prepared when facing real-time scenarios. Equip your team with the right tools such as smart phones, phablets, and tablets with seamless connectivity for them to work from anywhere during an emergency.        
Configure Stringent SLAs and Hierarchical Escalations
Define stringent SLAs for major incidents. Set up separate response and resolution SLAs with clear escalation points for any breach of the process. In addition, follow a manual escalation process if the assigned technician lacks the expertise to resolve the incident. Moreover, ensure that a backup technician is always available.
Keep Your Stakeholders Informed
Throughout the life cycle of major incidents, send announcements, notifications, and status updates to the stakeholders. Announcements in the self-service portal will prevent end users from raising duplicate tickets and overloading the help desk. Also send hourly or bi-hourly updates during a service downtime caused by major incidents. Have a dedicated line to respond to major incidents immediately and offer support to stakeholders. Use the fastest means of communication, such as telephone calls, direct walk-ins, live chat, and remote control desktop, instead of relying on email.
Tie Major Incidents with Other ITIL Processes 
After a major incident is resolved, perform a root cause analysis by using problem management methods. Then, implement organization-wide changes to prevent the occurrence of similar incidents in the future by following the change management process. Speed up the entire incident, problem, and change management process by providing detailed information about the assets involved by using asset management.
Improvise Your Knowledge Base
Formulate simple knowledge base article templates that capture critical details such as the type of major incident the article relates to, the latest issue resolved using the article, owner of the article, and the resources that would be needed to implement the solution. Create and track solutions separately for major incidents so that you can access them quickly with very little effort. 
Review and Report on Major Incidents
Document and analyze all major incidents so that you can identify areas of improvement. This will help your team efficiently handle similar issues in the future. Also, generate major incident-specific reports for analysis, evaluation, and decision making. You could generate the following reports to help in efficient decision making. 
1) Number of major incidents raised and closed each month
2) Average resolution time for major incidents
3) Percentage of downtime cause of major incidents
4) Problems and changes linked to major incidents     
Document Major Incident Processes for Continual Service Improvement
It is a best practice to document major incident processes and workflows for ready reference. This could capture details like number of personnel involved, their roles and responsibilities, communication channels, tools used for the fix, approval and escalation workflows, and the overall strategy along with baseline metrics for response and resolution. The top management must evaluate processes on a regular basis to check if targeted performance levels in major incident management are met. This can help rectify flaws and serve for continual service improvement.
Major incidents are unavoidable and each one is a learning experience for your team. Adhering to these practices could be your first step towards mastering the art of handling major incidents.

IT Asset Management Best Practice : Gunakan KPI untuk keputusan terbaik.

ITAM best practice 5: Keep tabs on the metrics that matter.

In this blog from our ITAM best practice series, you can learn how to keep tabs on the metrics that matter. The goal is to track the right KPIs to drive better decisions.
Generating specific ITAM reports can help you accomplish specific objectives. Let’s take a look at a few of those objectives and their corresponding reports. 
If formulating an effective IT budget is your goal, track the
  • Average cost of a workstation
  • Average cost of a license
  • Total asset spending, broken up by vendors
  • Total value of assets owned
If you are looking to stay license compliant, look at the
  • Ratio of used to purchased licenses
  • Software licenses by expiration date
  • Number of licenses available 
If you need to make effective purchase decisions, check out the
  • Depreciation rate of assets
  • Average lease violation fines paid
  • Average cost of maintaining an asset
  • Number of workstations in repair
If you want to identify discrepancies to your IT environment, keep an eye on the
  • Number of unauthorized configuration items
  • Assets identified as the cause of service failures 
  • Audit history 
If you need to optimally use existing resources, watch the number of
  • Unassigned workstations
  • Users with more than one workstation
  • Users without a mapped workstation
Today’s tools offer the advantage of generating both built-in standard reports, as well as custom reports. Pre-configured standard reports can be generated at the click of a button. This eliminates redundant effort and saves a lot of time if you are looking to generate a report multiple times under various scenarios. Reports can also be custom built-using an interactive platform whenever you want.
It is good practice to pin key metrics that matter to your dashboard. Some tools allow you to add generated reports as dashboard widgets. This ensures that the information you seek is readily available. Here are a few dashboard components every IT asset manager should track:
  • Workstations by operating system
  • Software usage to monitor rarely used, unused, and frequently used software
  • License compliance details
If you have any questions, please feel free to post them in the comments section below. In the next blog we will see how to conduct self audits. In the meanwhile, if you are looking for an out of the box IT service desk solution with built-in ITAM capabilities, we encourage you to check out ServiceDesk Plus.