You will identify which components and interfaces will be included in the System Integration Project, and you will discuss the advantages and disadvantages specific to your project.You are now progres

System Architecture and Integration (ITCO425-1804A-01)

Systems Integration Design Plan 

Jacqueline Calloway

AIU

August 14, 2018

Table of Contents

Project Information .....................................................................................................................3-4

Project Plan ………...............................................................................................................................5

System Integration Best Practice.........................................................................................................6

Requirements Specifications.................................................................................................................TBD

Enterprise System Integration Analysis.................................................................................TBD

Systems Integration Approach Evaluation and Selection...........................................................TBD

Proposed System Integration Components Architecture............................................................TBD

Implementation Framework.................................................................................................................TBD

System Integration Implementation Plan......................................................................................TBD

Project Information (Week1)

The MaintMax Project will be implemented in Ace Corp.’s Maintenance Division to replace the existing maintenance tracking system which is inadequate for expanding operations. The implementation of this database is a deliberately planned and highly technical effort. This description of the implementation will provide all stakeholders with a detailed understanding of how the implementation will occur.

Upon completion of the design for the MaintMax Database, a beta version of the database will be loaded in Ace Corp.’s virtual testing server. Ace Corp.’s IT Group will capture all existing data from the existing database and load that data into the MaintMax database in order to test data integrity and compatibility between how maintenance data is captured and the new MaintMax database. Once testing is complete and functionality of the MaintMax database is verified, operator training will be conducted with maintenance staff on the new tool. Once training is complete, the MaintMax Database will be loaded onto Ace Corp.’s maintenance servers and partitioned off to prevent user access. Ace Corp.’s IT Group will then verify functionality of the database on the actual Ace Corp. maintenance servers.

Once functionality on maintenance servers is confirmed, a notification will be distributed to the entire organization communicating the transition from the legacy maintenance database to the new MaintMax Database. At this point in time, the maintenance staff, in conjunction with the IT Group will conduct a final data capture of all maintenance data on the legacy system and the data will be imported by the IT Group to the MaintMax Database. Once the data import has been deemed successful by the IT Group, the legacy system will be turned off. At this point in time a manual contingency operation will be employed wherein maintenance technicians capture all maintenance actions manually for a period of two days while the MaintMax Database is prepared to go live. Upon approval from the IT Group, the MaintMax Database will go live and be used for a period of forty-eight hours by the maintenance technicians with IT Group support to ensure acceptance criteria are met. Once the team verifies that the acceptance criteria have been met, the manually captured maintenance data will then be entered into the MaintMax Database. Completion of entering the manual data and achievement of the acceptance criteria formally ends the implementation phase of this project.

Project Plan (WEEK1)

This Implementation and Migration Plan has been developed to communicate how the MaintMax Maintenance Database Project will be implemented, installed, and migrated to its operational environment within Ace Corporation’s Maintenance Division. The purpose of this plan is to ensure all stakeholders are aware of the details, requirements, and responsibilities involved in successfully completing this project and migrating the product to the operational group. Any requested changes to this plan should be submitted through the project’s change control process for review and approval prior to implementation.

System Integration Best Practice (WEEK1)

The MaintMax Database Project requires a database design on an upgraded Smarttech II platform as opposed to a Smarttech platform where the existing database resides. While this allows improved functionality and capability, it does not require any additional hardware or upgrades to existing hardware. Likewise, no additional facilities are required to complete the implementation and migration of this project. This project will be completed within the existing capabilities of Ace Corp.’s hardware and current facility.

The MaintMax Database will provide not only the same capabilities as the legacy database, but additional functionality as well. As such, these additional functions have been included by the design team in planning for ongoing performance monitoring of the MaintMax Database. To accomplish this, additional monitoring criteria have been added to the operational environment to collect real-time data once the database is migrated to its operational environment. The Maintenance Operations Lead is responsible for monitoring performance and producing weekly reports which will be provided not only to Ace Corp. senior management, but to the IT Group Lead as well. If MaintMax performance monitoring indicates any database performance outside of the acceptable levels, the issue will be escalated immediately to the Ace Corp. staff leads to determine and execute corrective measures and initiate a root cause analysis. This is the existing procedure Ace Corp. utilizes for all IT tools.

Requirements Specifications (WEEK2)

TBD

Enterprise System Integration Analysis (WEEK3)

TBD

Systems Integration Approach Evaluation and Selection (WEEK3)

TBD

Proposed System Integration Components Architecture (WEEK4)

TBD

Implementation Framework (WEEK4)

TBD

System Integration Implementation Plan(WEEK5)

TBD