Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d277569077/htdocs/hcablog/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d277569077/htdocs/hcablog/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d277569077/htdocs/hcablog/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d277569077/htdocs/hcablog/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/2/d277569077/htdocs/hcablog/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/2/d277569077/htdocs/hcablog/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/2/d277569077/htdocs/hcablog/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/2/d277569077/htdocs/hcablog/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/2/d277569077/htdocs/hcablog/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/2/d277569077/htdocs/hcablog/wp-includes/http.php on line 61

Strict Standards: Non-static method PopularPosts::install_post_plugin_library() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-content/plugins/popular-posts-plugin/popular-posts.php on line 75

Strict Standards: Redefining already defined constructor for class admin_subpages in /homepages/2/d277569077/htdocs/hcablog/wp-content/plugins/post-plugin-library/admin-subpages.php on line 22

Strict Standards: Non-static method sem_opt_in_front::init() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-content/plugins/sem-opt-in-front/sem-opt-in-front.php on line 138

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method WpWallRecentCommentsWidget::init() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 339

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::posts_join() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166
HCA Case Studies - HCA Blog

HCA Case Studies


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Rouge - Dignity & Prestige

by mouss on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55
Mar.15, 2012, under
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166
*All, Branding, HCA Case Studies, Identity, Logos, Print


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 135

Branding/ Visual Communication/ Printing/

Rouge is a trading company that deals with luxurious brands ONLY. The logo reflects the luxurious brands this company represents, and at the same time with trendy, stylish and impressive look and feel.

Leave a Comment :, , , , , , , more...


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Nadine Sidani Website

by mouss on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55
Jun.03, 2011, under
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166
*All, HCA Case Studies, Illustration, Interactive, Portfolios, Web


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 135

Branding /  Website Design/
www.nadinesidani.com

“From the moment we contacted HCA to the final website launch, we found with him an outstanding service and very professional company to work with every question was answered quickly and they made sure to go above and beyond what we asked of them. The design of the website and the launching was exactly what we wanted and was even above our expectations; and their services made every step of the process very simple.
I would recommend HCA to anyone who wishes to have a unique and up to date website.”
Nadine Sidani

Leave a Comment :, , more...


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

ICT Qatar

by mouss on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55
Apr.02, 2011, under
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166
*All, Branding, Design, HCA Case Studies, Identity, Logos, Portfolios, Poster, Print, Web


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 135



Branding /  Print Design /  Presentation /  Website Design
To  position the company as a mature IT infrastructure solutions provider,  with ability and ambition to lead niche technology initiatives

Leave a Comment :, , more...


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

fmn Energy International

by mouss on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55
Dec.30, 2010, under
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166
*All, Branding, Design, HCA Case Studies, Identity, Logos, Portfolios


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 135

Branding / Print Design
FMN’s mission is to become the world leader in creating sustainable technologies to combat climate change through the reduction of greenhouse gas pollution.

Leave a Comment :, more...


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

MTN Link

by mouss on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55
Dec.18, 2010, under
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166
*All, HCA Case Studies, Interactive, Uncategorized, Web


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 135

Web Design /  Flash Microsite /
MTN (Sudan) is in need of a web presence in order to support their Mobile Broadband service (MTN Link) re-launch.

The specific nature of their content means that it cannot be fitted into the information architecture (IA) of their main website (www.mtn.sd) in a way that meets visitor goals of information find-ability and interactivity.

Consequently, the optimum solution is to create an independent MTN Link microsite targeted to their particular target audiences.

Leave a Comment :, , , more...


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

i4 Solutions

by mouss on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55
Dec.18, 2010, under
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166
*All, Agency, Branding, Design, HCA Case Studies, Identity, Logos, Portfolios, Print


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 135

Branding /  Print Design
Based out of Qatar, i4 is providing end to end Information Infrastructure Solutions (IIS), specialized in data center consolidation, virtualization and optimization.
i4 is an affiliate of  Mideast Data Systems Qatar, and is part of the Midis Group of companies.

Objectives
I4 is focused, dynamic (quick to adapt and evolve), and committed to its customers. they would like their brand to be perceived as Attractive, Sexy, Young, Technology Driven, with a touch of Art.

Leave a Comment :, , more...


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Midis Group

by mouss on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55
Dec.18, 2010, under
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166
*All, Agency, Branding, Design, HCA Case Studies, Identity, Logos, Portfolios, Poster, Print, Web


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 135

Naming / Rebranding / Internal Rebranding / Branding Architecture / Web Design / Motion Graphics

Background
The MDS name stands for a distinguished group of information and communications technology companies, known for their advanced offering of software and hardware products, services, distribution, system integration and site solutions. Its 10+ sub holdings include over 100 companies and more than 2500 employees.

Objectives
The Midis brand - the natural next step for MDS - captures our role as cornerstone for a family of businesses growing to the next level in size, coverage and visibility, all while upholding our original values and identity.

Leave a Comment :, more...


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

MDS Computers

by mouss on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55
Dec.18, 2010, under
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166
*All, Agency, Branding, Design, HCA Case Studies, Identity, Logos, Portfolios, Print, Web


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 135

Branding /  Print Design
MDS Computers is an IT Systems Integrator providing different products & services ranging from hardware, software, and consultancy.

Leave a Comment :, , , more...


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Salahaddin Holding

by mouss on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55
Dec.18, 2010, under
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166
*All, Agency, Branding, Campaign, Design, HCA Case Studies, Identity, Logos, Portfolios, Poster, Print


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 135

Positioning / Rebranding / Internal Rebranding  / Print Design / Visual Communication

Background
Thebiggest holding in Iraq with the best management team doing business whileserving the community.
Workfields: Banking- Investment Hotels Construction- Oil- Medication- Agenciessuch as Scoda Suzuki- Pepsi- life water- Manufacturing plants BRC- Prefab-steel Cement Oil- Gaz stations.

Objectives
Brandidnetiy and profile should reflect how big and solid Salahaddin is, with Internationalstandards.

Leave a Comment :, more...


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

CDA - Computer Direct Access

by mouss on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55
Dec.18, 2010, under
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166
*All, Agency, Branding, Design, HCA Case Studies, Identity, Logos, Portfolios


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 135

Rebranding  / Web Design / Print Design

CDA started in 1994 as a mail order company.  They realized by 1998 that the model had to change if the Company was to survive.  Since then we became an Authorized Reseller of Apple and later we added Xerox, Acer, Adobe and Dell.

Objectives
CDA needs a new Brand as some persons will equate the CDA logo with the mail order company we were, although they stopped doing that business 10 years back.

Leave a Comment :, , , more...


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55

iTel

by mouss on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/functions.php on line 55
Dec.16, 2010, under
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method sem_opt_in_front::change_permalink() should not be called statically in /homepages/2/d277569077/htdocs/hcablog/wp-includes/plugin.php on line 166
*All, Agency, Branding, Design, HCA Case Studies, Identity, Logos, Web


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/2/d277569077/htdocs/hcablog/wp-includes/link-template.php on line 135











Naming / Positioning /  Branding  / Web Design / Presentation / Corporate Profile

Background
iTel is a newly established company, geared towards providing technical consultancy services in Information Technology (IT) and Telecom, servicing the Middle East & African regions. iTel is Focused, Optimized, and Reliable partner offering innovative and honest technical consultancy services and solutions, ranging from complete outsourcing solutions to planning, design, optimization, and operation management.

Objectives
iTel’s goals in a descending order are; being a highly skilled company, professionals, honest, focused, optimized and reliable, and affordable, great value for the money. The company’s aim is to attract new clients that have been suffering from the ordinary technical consultants and Telco suppliers, high cost and not realistic solutions.

iTel’s marketing goals are to be among the operators in the Gulf region and Africa as the first choice to outsource their technical functions. This brand will portray iTel’s values thus will help meeting the goals.

Leave a Comment :, more...

Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!

Visit our friends!

A few highly recommended friends...