GIS Client Services: Blueprint for Success

Version 35

    Our Implementation Blueprint

    A blueprint comprises all the minute details and steps necessary to complete a large, complex task. When speaking of information technology, specifically geographic information systems, a blueprint outlines the steps that need following to complete all project goals within a specified scope, schedule, and budget. Most people appreciate the need for a well-thought out plan, yet information technology projects fail far more often than they succeed. A study published in Scientific American reports that over 30% of all projects are canceled before completion, with 70% of the remaining projects judged to have failed to deliver on some important expected functions. GIS projects are particularly notorious for overrunning their budgets and never completing on time, unless a well-defined, tested blueprint guides the way.


    Our Foundation: Building Your ArcFM (BYA) and 3D Methodology



    Enter the Building Your ArcFM (BYA) methodology.Leveraging lessons learned from thousands of ArcFM technology projects for myriad utility companies dating back to our early years of Miner & Miner, BYA is the blueprint providing a solid, predictable structure that is flexible enough to adapt to the uniqueness of each implementation.

    Encompassing the full project lifecycle, BYA is structured around three essential processes: Design, Develop, and Deploy.Within each essential process, finer granularity is provided through many subprocesses. Click the 3D Methodology graphic to view full-size image.


    Our team of professionals apply these processes to execute your project in a logical, systematic approach. We apply these best practices to ensure we meet the needs of your stakeholders while delivering your solution on time and on budget.  Best practices are the key to the blueprint, and the blueprint is the key to project success. 


    Our Evolution Within Schneider Electric

    When Miner & Miner was acquired by Telvent and then by Schneider Electric, things changed -- all for your benefit. Through years of experience delivering hardware solutions across the globe, the Schneider Electric team developed a proven implementation methodology rooted in the Project Management Institute Book of Knowledge (PMBOK). The Customer Project Process, or CPP as it is affectionately known, focuses on reducing risks on massive projects  and increasing overall performance for these initiatives.  CPP continues evolving to match the current and future needs of our customers. Similarly, our ArcFM implementation methodology continues to tap into Schneider Electric's vast project management experience and implementation knowledge to continuously hone its approach.


    Delivery Model 2.0: Building on a Solid Foundation

    Although the BYA methodology is a successful approach in its own right, we looked to 3D and CPP to enhance the process with additional phases of activities and deliverables within Design, Develop, and Deploy. This additional level of detail supports clear communication regarding project activities, ensuring alignment of all members of the project team. With these additional phases our waterfall-based method of delivery now has greater flexibility to support evolving customer environments by weaving in agile processes that provide greater involvement with users and business stakeholders.



    This first phase of every ArcFM Solution implementation is critical to providing a successful business solution. It is the all important step in connecting ArcFM with the needs and processes of your business. This phase is organized into three distinct sub-phases, each with its own set of activities, outputs, and deliverables.


    The team captures early discussions regarding scope and business goals in a high-level document that includes business processes, use cases, and identified stakeholders. This sub-phase documents the initial vision of the solution based on scope and early customer interactions. This information sets the foundation for all subsequent project workshops and requirements discussions.


    Activities during this sub-phase focus on all requirements for the project. The types of requirements include functional, technical, non-functional, data modeling, conversion, and training. The project team conducts a functional gap analysis to identify holes in both the out-of-the-box solution and the originally proposed solution. The team also documents business process workflows and software use case scenarios. A requirements traceability matrix connects all defined requirements to design documents and test cases, ensuring all items captured as in-scope requirements are tested and delivered. 


    Activities and outputs include functional design of the software functionality that needs building and the test steps that ensure quality. The team documents both the technical architecture design and environment design and develops a training plan to support the education requirements enumerated during the Analyze sub-phase. 



    During this phase of the BYA methodology, we begin taking action on the outputs from the Design phase, and the ArcFM Solution begins to take shape. The team addresses elements of conversion, configuration, and customization, as dictated by solution requirements. This phase encompasses two distinct sub-phases, each with its own set of activities, outputs, and deliverables.


    The project team translates the functional and non-functional requirements and designs into logical design detailing how the solution components will be built, and software development ensues. We document the configuration details including hardware and software settings, parameters, triggers, and other information needed for the effective running of the delivered solution. This sub-phase also generates the comprehensive test plan and necessary test scripts.


    The team plans for and conducts solution Factory Acceptance Testing (FAT) to determine the health of the new solution and to provide early visibility by the end users as to what their new solution will look like and how it will function. It is also a prelude to formal Site Acceptance Testing (SAT), performed in the customer environment following customer business processes and operating procedures. We execute SAT to ensure the system is operating properly once installed in real conditions.



    This final BYA phase is the culmination of months of hard work and heralds a new day in your organization as the team executes the steps necessary to empower the business users with the ArcFM Solution. This phase encompasses two distinct sub-phases, each with its own set of activities, outputs, and deliverables.


    The team creates a structured, repeatable plan that identifies the sequence of operations or steps that must be executed to deliver changes into the target system environment. This plan includes concrete training timelines for operations and administrative personnel during the deployment phase.

    Introduction to Service

    Included in the deployment plan are clear steps and schedule to hand-off the solution to the client support organization and specifies the related Schneider Electric support process.