Project Design

With a knowledge pool in executing large projects MBR has created a unique and strong design-build philosophy, we have witnessed the benefits of our solution architects and engineers' approach to the design process. Our customer-focused approach uses design milestones for concept, feasibility, design reviews, with customer approvals at each stage. Key project disciplines are represented throughout the process to ensure the design functions as one cohesive solution.

The design team knowledge base is crucial to project success, yet many end-customers do not consider system integration as one of the major disciplines included in the design process. Frequently, system integrators aren't brought into a project until the detailed design is nearly finalized and the project is moving into the construction phase. At this point in the project, the integrator is unable to positively influence a project without a significant cost impact. Altering this approach and instead of involving a systems integrator early can reduce project costs and risks compared to traditional methods, especially those that include a pre-selected product vendor.
What to expect

System integrators are tasked with creating a design that matches a customer's budget and requirements. To achieve this goal, it is necessary to not only evaluate the project at hand but also analyze the customer's legacy systems and consider possible future enhancements. By leveraging an enterprise-wide viewpoint, an integrator can add more value in the overall design, delivering results that can improve the customer's profit, growth, and corporate reputation.

The following are some primary system integrator tasks executed throughout the typical project lifecycle:

Requirements analysis
  • The requirements analysis phase enables a team to accurately determine the current and future customer requirements of the project. Tasks during this phase include:
  • Current system architecture - Examine the existing network infrastructure, data pathways, and procedures
  • Customer requirements - Identify the current system deficiencies and detail the customer requirements with regard to the existing system
  • Interface coordination-Determine the system interfaces, including current and available hardware interfaces and protocols to the system devices
  • Identify project risks-Document project integration risks with mitigation plans
  • Areas to be addressed-Detail the software, hardware, interface descriptions and approaches, data table layouts, the sequence of operations, and graphical user interface concept screens.