Mainframe Migration:

          Methodology & Approach




Macrosoft Capability Statement




                 February, 2...
CONTENTS
1. OVERVIEW.........................................................................................................
1. Overview
This document reviews Macrosoft experience and process methodology for migrating mainframe
applications to cli...
2. Migration Process Phases
Viewed from a high level, a complete conversion generally has the following five steps/process...
⇒ Control               Control Cards
          ⇒ MVS_Changes           Changes during the process of migration
          ...
•   Trouble shooting & Maintenance
    •   Performance Tuning
    •   Data Security Audits & fine tuning
    •   Backup, R...
IBM Utilities: We have extensive experience and partnerships in successfully converting a large
class of IBM Utilities to ...
these servers remotely. The servers are kept at the client site. There are standard processes for
downloading the blueprin...
6.2 The Customer Support Process
The typical customer support process followed at the India development center is depicted...
7.1.2 Convert database Objects
This is the major step of the schema migration process. All the database objects in the sou...
7.2.1. Data Analysis
This phase involves walkthrough of the data presently in the database (or in use). Some data
which is...
7.2.5 Conversion Tool Preparation
In this phase, the tools required for the data movement are customized/developed (or pro...
APPENDIX-A: The Mainframe Migration Toolkit
Macrosoft’s in-house “Mainframe Migration Toolkit (MMK)” facilitates back-offi...
APPENDIX-B: Macrosoft Profile
Based in Parsippany, NJ, Macrosoft delivers high-quality, cost-effective, full life-cycle so...
The chart below presents the development practice areas in which Macrosoft has in-depth
experience, as well as the technol...
OO Development Java/J2EE, JSP, Microsoft .NET, C#, C++, ASP.NET, Unix
 Application Servers BEA WebLogic, IBM WebSphere, Or...
In each write-up we provide details on the level and complexity of work flows and business rules
that had to be embodied i...
involved) is always used when a request is issued. Macrosoft Inc. developed an application that
dynamically replicated all...
7. Automated Workflow for Collateral Creation for a Large Mortgage Company
Macrosoft was engaged to automate the workflow ...
•   Integration of USA wide Street-level view
                      •   Geo-coding of USA street addresses
               ...
Upcoming SlideShare
Loading in...5
×

Duke Power

549

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
549
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Duke Power

  1. 1. Mainframe Migration: Methodology & Approach Macrosoft Capability Statement February, 2008 Page 1 of 20
  2. 2. CONTENTS 1. OVERVIEW.......................................................................................................................................3 2. MIGRATION PROCESS PHASES............................................................................................................4 2.1 MIGRATION ANALYSIS...........................................................................................4 2.2 MIGRATION DESIGN............................................................................................4 2.3 MIGRATION DEVELOPMENT (CONVERSION).........................................................................5 2.4 MIGRATION INSTALLATION (LIVE MIGRATION)......................................................................5 2.5 MIGRATION MONITORING (POST MIGRATION MONITORING)..........................................................5 3. AUTOMATION AND QA UTILITIES....................................................................................................6 4. CRITICAL ELEMENTS IN THE MIGRATION PROCESS ..............................................................................6 5. VALUE-OF PARTNERING WITH MACROSOFT IN MIGRATION..................................................................7 6. DEVELOPMENT & SUPPORT PROCESSES AT MACROSOFT......................................................................7 6.1 THE DEVELOPMENT & DEPLOYMENT PROCESS.....................................................................7 6.1.1 Coordination of Different teams for collaborative development.......................8 6.1.2 The India Development Team............................................................................8 6.2 THE CUSTOMER SUPPORT PROCESS..............................................................................9 7. GENERAL DATABASE MIGRATION PROCESS.......................................................................................9 7.1 DATABASE SCHEMA MIGRATION..................................................................................9 7.1.1 Extract Database Metadata.................................................................................9 7.1.2 Convert database Objects..................................................................................10 7.1.3 Convert Queries................................................................................................10 7.1.4 Implement Converted objects...........................................................................10 7.2 DATA MIGRATION............................................................................................10 7.2.1. Data Analysis...................................................................................................11 7.2.2 Data cleanup / enrichment................................................................................11 7.2.3 Conversion Study..............................................................................................11 7.2.5 Conversion Tool Preparation............................................................................12 7.2.6 Mock Conversion..............................................................................................12 7.2.7 Conversion for Parallel Run..............................................................................12 7.2.8 Conversion for Live System.............................................................................12 8. APPROACH TO COBOL, EASYTRIEVE, AND DATACOM/IDEAL MIGRATIONS................................12 APPENDIX-A: THE MAINFRAME MIGRATION TOOLKIT....................................................................13 APPENDIX-B: MACROSOFT PROFILE...............................................................................................14 Page 2 of 20
  3. 3. 1. Overview This document reviews Macrosoft experience and process methodology for migrating mainframe applications to client server environments (UNIX, Windows). Much of our work in this area has been done in conjunction with work projects such as Vestcom Migration. These applications handle critical data for numerous leading corporations. In all of these conversion efforts, our teams have worked side-by-side with client teams in effectively and securely performing these conversions. We have our own migration tools (MMK) as described below, as well as expertise in using industry standard tools such as MicroFocus Revolve, Micro Focus Net Express, Oracle Migration Workbench, SQL Server Migration Assistant, IBM Migration Toolkit, etc. We have strong and long standing partnerships with Microfocus, Microsoft, Oracle and IBM, which help us in adapting their products on Unix/Windows for mainframe migration. We are members of “Mainframe Migration Alliance (MMA)” and “Mainframe Transformation Consortium (MTC)”. We also have partnership with many Mainframe 3rd party tool providers. Key to Macrosoft’s Mainframe-to-Server application conversion capabilities is our depth of experience in both Mainframe, as well as Server [Windows, UNIX] environments, thus insuring a smooth conversion of MVS applications to a Server platform. We have a dedicated center for IBM Mainframe Technologies, and have over a decade of successful engagements in client server technology (.Net, Java, RDBMS, etc.). The Mainframe team consists of the best global talents, and has expertise in most of the mainframe technology areas including JCL, CICS, DB2, VSAM, COBOL,CA-DATACOM, CA-IDEAL, etc. To the extent possible, we use “Lift & Shift”, which means reusing the existing code on the target platform through standard automated conversions. We have the know-how for such automated conversions to the latest technology such as .Net and MVC architectures. This helps in protecting your earlier investments in programming, debugging and business logic implementation. We also have a standard database migration process (both schema & data) which migrates large volume of data without error from the source database to target database. Our standardized conversion methodology and procedures insure that the new process will be designed and developed to work efficiently in the new system environment the first time around, and will fully conform to the business rules and processes performed in the original MVS application. We work directly with the clients to spell out and decide upon all the options for re-constructing a Mainframe application in a Server environment. We establish and maintain a conversion operations handbook that provides a full and complete blueprint and checklist of all steps required, and all processes that need to be performed, whether by us or by the client. As one example of the types of tradeoffs that we guide the client through, please refer the Vestcom Migration Case Study at http://www.macrosoftinc.com/brochures/Mainframe_CaseStudy_Brochure.pdf, wherein we have efficiently and reliably converted more than 230 MVS applications to run on either a Windows platform using an embedded Unix-like environment or directly on a UNIX platform [including Linux]. Our overall objective in all of our work efforts is to confine the conversion process to mostly mechanical execution of automation tools and QA tools, followed in the end by manual side-by- side testing. That is, there should be little or no manual or adhoc coding or programming involved in most conversion efforts. The methodology we use requires minimum interaction with the client’s mainframe production environment, thereby reducing costs and minimizing interruptions of the production system. This is achieved through a phased activity, in which first a blueprint of the application is generated on a PC, and most of the work is then done at back-office on PCs. Our global delivery model (Offshore-Nearshore-Onsite) further minimizes costs for the client. Page 3 of 20
  4. 4. 2. Migration Process Phases Viewed from a high level, a complete conversion generally has the following five steps/processes that need to be done in sequential order. Our 5-step MVS conversion methodology involves: • Migration Analysis • Migration Design • Migration Development • Migration Installation • Migration Monitoring These are explained below. 2.1 Migration Analysis This step involves assimilating whatever documentation, specifications, input/output, data formats, naming conventions, business logic, work flow, etc. available from the client, and collecting possible additional information through interactions, questionnaire, etc. This is followed by compilation and analysis of the gathered information. This phase helps in: • Forming an overall migration strategy • Identifying gaps (Lift&Shift Migrations, Component Development, Tool Partnerships, etc.) • Identifying historical, obsolete and unwanted components & data • Forming strategy for utilizing the latest technological features of the target environment • Identifying additional functional, performance and security requirements of client This step involves a joint effort of our onshore and offshore team. 2.2 Migration Design In the context of migration, this step involves the following activities: • Detailed Migration Strategy (both Application & Database) • MVS Blueprint Generation (detailed below) • Target environment selection, assessment & setup (all hardware, software & network) • Migration (Development) environment selection, assessment & setup (all hardware, software and team including Development, Test and Preproduction environments ) • Migration Tools (Lift&Shift) preparation/customization (both application & database migration tools) • Substitution/add-on components design • PoC / Prototype Migration The MVS Blueprint Generation involves application analysis for dependencies, and downloading the relevant source code, file structures, etc. to the PC for backoffice processing. This could be a phased process which can extend to the next phase of conversion. The output of this step is the application blue print on the PC in a defined directory structure such as: ⇒ JCLs JCLs ⇒ Procs JCL Procedures ⇒ Cobol Cobol source code, copy books, etc ⇒ VSAM VSAM file structures Page 4 of 20
  5. 5. ⇒ Control Control Cards ⇒ MVS_Changes Changes during the process of migration ⇒ Utility Utility components ⇒ DATACOM DATACOM data structures, definitions, etc. ⇒ IDEAL IDEAL for DATACOM components ⇒ CICS MAPS, Programs ⇒ ASM Assembler Programs ⇒ DB2 DB2 Table Structures, definitions ⇒ etc. Tools that get used in this step include: • Macrosoft’s Mainframe Migration Toolkit (especially the JCL,COBOL & DB Analyzer tool ) • MicroFocus Revolve This step involves a joint effort of the onshore and offshore teams, and can be done in three modes: - The onshore team sitting at the client location downloads the files from the mainframe and provides them to the offshore team. - The offshore team directly accesses the mainframe (from India) through high speed secure VPN connectivity, and downloads the source files directly - Client downloads the source files and provide them to the offshore team Which mode to use is decided based on security and other requirements of client. 2.3 Migration Development (Conversion) This is the major phase of the migration process and in this phase, the following activities take place: • Application Conversion & Unit Test • Database schema migration • Mockup data migration • Testing These activities and processes are further detailed subsequent sections. 2.4 Migration Installation (Live Migration) In this phase, the live cutover of applications from the source system to target system takes place. The activites involved are: • Installation (movement) of converted applications on production system for live run • Live Data Migration (This is done in one shot during off hours or holidays.) • Live cutover from source system to target system • Parallel run 2.5 Migration Monitoring (Post Migration Monitoring) This phase which could extend from 3 to 6 months, during which period the migrated systems are monitored against the set design targets and any necessary fine tuning is done, including: Page 5 of 20
  6. 6. • Trouble shooting & Maintenance • Performance Tuning • Data Security Audits & fine tuning • Backup, Recovery and Disaster Recovery Processes • Operations & Administration Processes. 3. Automation and QA Utilities Macrosoft has built up a number of unique automation tools for performing mainframe conversions that are very useful in reducing the work effort involved in conversions and at the same time significantly reduce the risks and uncertainties of undertaking a conversion effort of this type. Some example modules included among these tools are as follows. (Please refer MMK brochure for all the module descriptions.) JCL-ANALYZER This simple but powerful tool analyzes JCL to build a web view using HTML/JavaScript. The web view helps programmers understand how JCL works to put applications together by individual job step. This allows programmers who do not have much MVS experience to work on JCL to Shell conversions easily, quickly and efficiently. JCL Converter: This utility includes both JCL2KORN template and JCL2KORN shell creator. The creator uses templates and JCL step labels to create standard Korn shell for JCL. Within the standard Korn shells, all steps including program calls, utilities, SyncSort and other third party software packages can be handled as separate modules. This utility significantly reduces complexities associated with coding and testing in a teamwork environment. SHELL Generator: This utility creates execution shells for 3rd party mainframe tools such as SyncSort, that are compliant to the standard system structure set up in the new server environment, which makes migration of 3rd party tools from MVS to PC easy and accurate. Macrosoft has vast experience in using many industry standard tools for migration and testing. Our partnerships with tool vendors help us in smooth and effective use of these tools. These tools include “Microfocus Revolve” for analysis, and “Microfocus NetExpress” for cross platform COBOL recompiling. Because of our standard and system independent designs, our MVS-to-Server application conversion technology can be performed under various different work models: On-Site, Off-Site, Off-shore and any mixture of these. Macrosoft works with its clients to review these different work arrangements and assist clients to decide which will work most smoothly and efficiently for their individual circumstances. 4. Critical Elements in the Migration Process Macrosoft’s approach and capabilities to conversion projects include the following critical elements: Tools Based Approach: We have extensive experience in converting MVS applications into shell- controlled processes on Windows utilizing an embedded “Unix” environment (e.g. MKS Toolkit, UWIN, CYGWIN, etc.) or directly onto Unix (such as, Solaris, PC Linux). Our Mainframe Migration Toolkit automates the analysis and conversion process as explained above. Micro Focus Revolve: We have in-depth Micro Focus Revolve Expertise for COBOL and JCL analysis. Micro Focus Net Express: We have in-depth Micro Focus Net Express Expertise for COBOL re- builds, and data transforms. Page 6 of 20
  7. 7. IBM Utilities: We have extensive experience and partnerships in successfully converting a large class of IBM Utilities to Windows/Unix (examples include: FileAid, QuickJob, IDCAMS, Syncsort, Transformer, Dialogue, Anchor, etc.). Taping into this depth of experience significantly improves the quality, and speed of our conversion work. 5. Value-of partnering with Macrosoft in Migration Our Standardized Migration Process: We have standardized the process of migration through a collaborative development environment. The Client participates in every stage of our process. We will share with you our Migration Process Handbook, which we use to direct and manage all conversion activities Proven & Efficient Project Management Capabilities: The methodologies we use are well proven and efficient, and our Project Management team is well experienced in performing mainframe migrations, having the first-hand experience and know-how to handle most special circumstances and conditions likely to arise in any sizable conversion project. Proven & Efficient Quality Assurance Processes: Perhaps the most critical success factor in projects of this type involves the methods, technologies and know-how for quality assurance. The methodologies we use are well proven and efficient, and our Quality Assurance teams are well experienced in insuring that converted applications work correctly without significant re-work. Easily Maintainable & Manageable Code: Client staff is kept fully involved in all phases of the process. There is no ongoing cost or need to involve us further after the conversion work is completed. The client can participate in all project phases, including initial R&D and development, and is educated on the methodologies and tools we use. By the time our work is done, client staff will be fully able to maintain and upgrade the code without our further assistance. Minimum Extra Investment Required: Our methodology emphasizes utilization of off-shore development resources wherever possible (assuming client approval). Our developers at our Indian facility are able to work remotely accessing the US servers through a secure VPN tunnel connection. This serves three purposes: minimizes overall conversion costs, minimizes resource costs by sharing, and facilitates a collaborative development environment which can generate output throughout the 24-hour daily cycle. We have successfully implemented this methodology. No special requirements or changes in input data: It is a true one-to-one conversion. The data the mainframe was getting can be taken as is by the Server, and do the processing, and produce exactly what the Mainframe was producing. Hence no special pre-processing or post- processing is required in managing data I/O. The applications are intelligent to handle these issues. The data can be either EBCDIC as in mainframe or ASCII as in PC. These can be managed through configurable parameters. Batch or interactive processing: Our converted applications provide true batch processing and scheduling as well as restart facility at an intermediate stage in case of failure. The applications can be made batch or interactive, depending on the requirement. Job Management Console: Our patent software for batched job submission as well as job scheduling provides easy to use user interface to configure, execute and manage the converted applications. 6. Development & Support Processes at Macrosoft 6.1 The Development & Deployment Process This is managed through collaborative work among the US Team, the Client Site Team and the Indian Team. 3 dedicated PC servers are used for this purpose, and all the three teams work on Page 7 of 20
  8. 8. these servers remotely. The servers are kept at the client site. There are standard processes for downloading the blueprints (mainframe programs with analysis docs & input data) to the designated directories, uploading the converted modules for unit tests, integration and system test, etc. The final integrated software gets moved to preprod (pre-production) server for trial (parallel) run. On user acceptance, it goes to the production server for the actual run. The authorities and persons to access these functionalities on these servers are well defined (including directory and file name standards), and strictly monitored and controlled. 6.1.1 Coordination of Different teams for collaborative development The Project Coordinator at US does all the communications and coordination between the teams. Strict document control and flow helps in managing this efficiently. 6.1.2 The India Development Team The Technical Director coordinates the mainframe migration activity at the India development center. There is Project Manager, Quality Manager & Customer Support Manager under him. Under Project Manager two teams functions, each lead by the respective Project Leader. The Conversion team goes ahead with first level conversions (i.e. Modules). Integration and test of the various modules converted by US & India teams for an application, is the responsibility of the Integration team. Customer Support is a constant activity required by the US teams and Clients. Changes, Part works and debugging support is normally requested by US teams to the Support team. Quality is an independent entity, which controls and assures the quality of the massive works going on. Page 8 of 20
  9. 9. 6.2 The Customer Support Process The typical customer support process followed at the India development center is depicted below. Client (Overseas team) requests are routed to the support team for the development. On completion it goes to the quality team (QA) for verification, and on QC Pass, it goes to the Sys Admin for upload and delivery. There is a 24-hour support system functioning (due to the difference in working times between US & India). The requests come normally through telephone, chat and email (there are dedicated phone, chat & email ids for this purpose, which are monitored 24 hours a day). 7. General Database Migration Process This involves two main activities “Database Schema Migration” and “Data Migration”. General processes involved in these activities are briefed below: 7.1 Database Schema Migration The phases involved in the DB schema migration are shown in Fig. 1 and explained below: 7.1.1 Extract Database Metadata This phase involves extracting and analyzing the source database structure, from the source DDL statements. Modeling tools and reverse engineering can help in capturing all details of the schema. Page 9 of 20
  10. 10. 7.1.2 Convert database Objects This is the major step of the schema migration process. All the database objects in the source database need to be converted to the equivalent objects in the target system. Typically objects such as “data types”, “tables”, “columns”, “views”, “indexes”, “stored procedures”, “triggers”, “packages”, ”sequences”, “authorities”, “functions”, etc. need to be converted. Factors such as data type, scale, precision, length and default values for table columns, functions, and stored procedures, null values, etc. can cause issues. 7.1.3 Convert Queries This is the next major phase in the database schema migration process. Even though the basic SQL commands are same, SQLs differs from engine to engine. Thus movement of business logic, stored procedures, triggers, etc. to dissimilar platforms can be tough. SQL translation requires good expertise and knowledge of both the source and target systems. 7.1.4 Implement Converted objects This phase involves building the database structure, on the target platform through scripts or the facilities provided in the target system. Enhancements related to the schema or performance can also be considered in this phase, utilizing the special features in the target system 7.2 Data Migration The phases involved in data migration are shown in fig. 2 and explained below: Page 10 of 20
  11. 11. 7.2.1. Data Analysis This phase involves walkthrough of the data presently in the database (or in use). Some data which is well accommodated in the source system may not be accomodatable in the target system. Usually the volume of data is large and a full walkthrough may not be possible. In such cases random samples are taken for identifying data items which can cause problems in movement. 7.2.2 Data cleanup / enrichment A data cleanup / enrichment prior to the actual migration can help a lot in effective movement of data. There could be obsolete or unused items, as well as items which will not affect the source or target system if modified. If this step is performed well in advance, the subsequent phases in this process will get an advantage. 7.2.3 Conversion Study This phase involves assimilation of the outputs from the first two phases, and detailed study for finalization of a conversion strategy. This phase can be categorized into the following:  Fitment/conversion study – Output of this phase is a study report detailing the changes required in the data items for the movement.  Formation of migration strategy – Output of this phase is the “Migration Strategy Document” detailing the planned process of migration, tools planned to be used, etc.  Finalization of scope of migration - In this phase, the scope of migration is defined. Items such as scope, limitations, performance and maintenance issues, etc. need to be well defined.  Finalization of Acceptance criteria – This phase will define the acceptance / test criteria, test process and test procedures to ensure that the data movement is fault free. 7.2.4 Conversion Strategy Signoff - In this phase, user (client) approves all the documents mentioned in phase-3 above. This phase is very crucial, while handling critical data. Page 11 of 20
  12. 12. 7.2.5 Conversion Tool Preparation In this phase, the tools required for the data movement are customized/developed (or procured). In production systems, tools are very crucial since the final data movement is done in one shot (usually in one or two days during off hours or holidays). The tools preparation is a full project activity of its own involving all phases of SDLC. 7.2.6 Mock Conversion In this phase, a mock conversion is performed, using the existing data in the source system. This may involve several rounds as below: Mock Conversion Round 1 Fixing of mismatches observed in round 1 Mock Conversion Round 2 Fixing of mismatches observed in round 2 … It is very important to document the change records during this phase. 7.2.7 Conversion for Parallel Run Usually a Pre-production system is setup for parallel run to which the data migration can be performed to ensure that the migration is problem-free. In this phase a one-shot data migration from the source system to the Pre-prod system is performed. Detailed testing is carried out to ensure that the data migration is fault free. Detailed performance testing and monitoring is done in this phase. 7.2.8 Conversion for Live System This is the final step of actual data movement from source system to target system. In production systems, this should be done in one shot when the system is not active (usually off hours or holidays). In 24x7 systems, the system may have to be brought down to off-line mode for the data movement. 8. Approach to COBOL, Easytrieve, and DATACOM/Ideal Migrations We have standard process for shifting COBOLs from IBM mainframe to a variety of platforms by standard conversions and recompiling. No re-coding is required. On Windows, the migrated COBOLs are .NET compatible and can be easily web enabled. The original MVS COBOLs are straight away converted to Windows EXE or DLL executables. Our migration utility understands Easytrieve Plus language statements and can directly convert them to COBOL/Perl programs on Windows/Unix to produce same type reports. The reports could be in a variety of formats including HTML which can be directly deployed on to Web Server. The output also can be CSV files which can be easily used with common office applications such as spreadsheets, word processors, or distributed databases The CA-DATACOM database is normally accessed through CA-IDEAL interface panels from terminals or through COBOL batch applications. Our migration tool converts DATACOM, IDEAL, COBOL entities to standard COBOL-SQL based application supporting a variety of RDBMS platforms. We also have standard data migration tools and processes to migrate the existing data from DATACOM tables to any RDBMS database. Page 12 of 20
  13. 13. APPENDIX-A: The Mainframe Migration Toolkit Macrosoft’s in-house “Mainframe Migration Toolkit (MMK)” facilitates back-office analysis of mainframe applications and database. The source code blue print is first downloaded to a PC and analyzed at back-office on the PC using MAK, there by avoiding production system interruptions and saving on CPU costs. The MAK is a set of PC based tools which contain the following modules: MVS Analyzer: This is a set of MVS environment analysis tools. Basically it analyzes and identifies the “Parmlib concatenation”, System Procs, Linklists (directory path), User Exits, Appendages, SVCs, Started Tasks, etc. which will give an actual picture of the user application, and its run environments. JCL Analyzer: The JCL ANALYZER takes the JCLs and associated procs kept in the source directory and generates analysis documents, associating procs, separating comments, resolving steps, symbolic variables, etc. These outputs are user-friendly HTML pages with expand tabs (+). You can click on these expand tabs to zoom into details. COBOL Analyzer: This produces dependency diagrams, module cohesions, SQL calls, instream data (command line arguments), data redefinitions (REDEFINEs), etc. CICS Analyzer: This is an Interdependency Analyzer tool to identify the resources used by CICS transactions and the relationships between them. Resources identified include those associated with transactions, programs, BMS maps, files, etc. VSAM Analyzer: This analyzes the VSAM, especially KSDS and tries to create “Entity Relationship Diagrams” (ER Diagrams). For other sequential files it creates the metadata providing details of fields (name, position, width, meaning, etc.), delimiters, record formats, etc. DB2 Analyzer: This analyzes the DB2 metadata and creates the “Entity Relationship Diagrams” (ER Diagrams). Also identifies stored procedures, triggers, etc. and the authorities delegated (DB, TS, table, plan, package, etc.). CA TOOLS Analyzer: This analyzes the various CA tools, utilites and databases such as CA7 (Job Manager), Easytrieve, IDEAL, DATACOM, etc. DATACLEANER / DATAMOVER: This is a utility for analyzing and cleaning up large data files in different formats (VSAM, Sequential, etc.), hexadecimal analysis, EBCDIC-ASCII conversions, etc. Page 13 of 20
  14. 14. APPENDIX-B: Macrosoft Profile Based in Parsippany, NJ, Macrosoft delivers high-quality, cost-effective, full life-cycle solutions to complex software development projects. The company has over a decade of successful engagements and over 180 professionals working for an exceptional client list. All of our major clients are our long-term partners; we have been privileged to have major corporations as our clients for periods extending past 10 years. Macrosoft provides highly qualified and professional development teams that can span the entire development lifecycle, from business process engineering and system architecture design through testing and final system hosting and maintenance. We maintain a leading edge in software technology that allows us to design new systems efficiently and rapidly, and to successfully integrate these new system capabilities within complex business and IT environments. We continue to invest in internal development of re-usable components, systems and technologies critical to our clients' needs in the application areas of sales and marketing; e-marketing; and print on demand, thereby allowing us to offer our clients rapid solutions that conform to best business practices. Overall, Macrosoft has performed over three hundred successful software development projects for corporate clients, since its inception in 1993. Macrosoft has an exceptional client list, and in essentially all cases has developed a long-term business partner relationship with these clients. A sampling of Macrosoft’s client list is provided in the chart below. Macrosoft has over 100 technical staff at its offices in New Jersey and at US client sites. In addition to its Headquarters in Parsippany, NJ, Macrosoft has its own development facilities in India, Pakistan, and China with a current total of over 150 technical staff. Solution Areas The principal solution areas for Macrosoft are the following: • Legacy Applications Support, enhancements, integration and conversion • E-Business Implementations o Enterprise Integration o Web Portals o Content Management o Web Services o Web Flow Architectures • Custom Application Development • ERP Implementation • Device Drivers & Engineering Applications • Print on Demand & Digital Print Services • Fulfillment Applications • E-Marketing • Business Intelligence & Analytical Reporting Applications • Data Processing Services The chart below provides a cross section of the clients that Macrosoft has provided software development services, either in the form of managed teams or fixed price contracts. For many of these clients Macrosoft has maintained strong working relationships spanning 5 to 10 years in duration. Page 14 of 20
  15. 15. The chart below presents the development practice areas in which Macrosoft has in-depth experience, as well as the technology partnerships and alliances that are currently in place. In addition to these development areas, Macrosoft adheres to a strict software development process and methodology and also maintains and utilizes state-of-the-art system testing software and methods. These are considered essential ‘tools of the trade’ for conducting our business. Technology Practice Areas Page 15 of 20
  16. 16. OO Development Java/J2EE, JSP, Microsoft .NET, C#, C++, ASP.NET, Unix Application Servers BEA WebLogic, IBM WebSphere, Oracle 9iAS, Tomcat DBMS Oracle, Microsoft SQL Server e-Marketing Kana e-Marketing Platform, Macrosoft Business Intelligence/Rules Analyzer OLAP, JAnalyzer, JESS Rule Engine, Macrosoft Rule Engine Content Management Documentum, Macrosoft Digital Asset Manager IDEs JBuilder, JDeveloper, JBoss, VisualAge, Delphi Print on Demand eXstream Software Open Source PHP, Perl, MySQL, LDAP, SAMBA Print on Demand eXstream Software CRM and ERP Expertise Macrosoft has experience implementing ERP systems across a wide range of vertical industry sectors and we have consultants who have developed core competencies with the leading ERP applications, including SAP and Oracle. With our experience in other application areas, ranging from CRM to business intelligence, supply chain management, security to networks, and e-business, Macrosoft can help your organization derive maximum value from your ERP projects. Our ERP services encompass: Gap Analysis and Business Process Re-engineering Implementation Post-implementation support Application value management Functional and technical consulting Version upgrades Integration with legacy applications Business Intelligence Web enabling and mobile computing RECENT PROJECTS Below are summaries of recent Macrosoft projects having similar (or larger) size and scope to this project, and having similar or related functional requirements. Page 16 of 20
  17. 17. In each write-up we provide details on the level and complexity of work flows and business rules that had to be embodied in the system. All of these systems have extensive user interface requirements with multiple roles and responsibilities, and have substantial reporting requirements. All of the systems were built for very large corporate clients, and in some cases we continue to have work in maintaining, enhancing and upgrading the applications. Given confidentiality requirements with our clients, we do not ascribe specific projects to specific clients and contacts. However, a general list of client references, all of whom are very familiar with our work, can be provided upon request. 1. Web-based Platform for Lead Generation, Management, Distribution, Reporting This platform was implemented within a very large firm for support of both partner sales and internal direct sales channels. The system provides both intranet and extranet support. The major modules of the system include: sales lead module; channel partner management; revenue forecasting through sales funnel tracking; sales channel performance measurement; and sales channel compensation calculation. The components of the sales lead module include: lead capturing; lead qualification, evaluation, enhancement and distribution; on-going tracking of progress; sales funnel reporting and information mining. The system has the following interfaces: WAP; VoiceXML; TTS; ASR; email, and paging. The system was built with a powerful and intelligent rule-based lead-distribution engine. This allows for flexible support of complex and changing workflows through only database changes. The rules engine has an easy wizard-based interface for rule management requiring minimal training of users. 2. Web-based Work flow Management of Core Documents for a Leading Insurance Company In this particular firm, sale of an insurance plan to a corporation involves capture and aggregation of a multitude of information into a plan booklet provided to each employee of the customer. In addition, insurance plans change often, so there are continual content management challenges to ensure that booklets are up to date before issued as a result of the sale of a plan. Bringing these two functional elements together in what was previously a largely manual workflow was objective of this project. We were engaged to optimize, automate and web-enable a workflow for the management of the core documents as well as production of new benefit booklets. Our solution provided specific functionality to four different user types, each having its own role in the newly defined workflow. We automated the creation of the variable benefit booklets (variable in that the terms and coverage for every sale are different), provided an automated approval process, and seamlessly integrated this web-based system with a digital print production environment. Beyond the automated workflow to produce a variable benefit booklet, Macrosoft provided a web- based solution that allows modification of the non-variable standard language of a booklet. This was completed with a full document repository that stored both standard and modified languages as well as completed booklets. 3. Document Management and Print-on-Demand System for Large Int’l Financial Company Documents relating to financial products and services are constantly changing, due to never ending feature changes as well as SEC compliance requirements. While the challenge of maintaining these documents is big enough, there is an additional and equally critical challenge of ensuring that the most current version of a given document is used whenever one is requested to be supplied to a customer. Given the amount of change in these types of documents, there is the potential for the wrong version to be printed upon request. The consequences for producing an outdated document range from customer dissatisfaction to SEC violations. Macrosoft Inc. was engaged to develop a document management and Print-On-Demand (POD) solution to ensure that the most current version of a given document (several hundred are Page 17 of 20
  18. 18. involved) is always used when a request is issued. Macrosoft Inc. developed an application that dynamically replicated all changes to the core documents in a production print library, which was seamlessly integrated with a digital print production operation. This application is also integrated with the financial institution’s internal systems, and using site server replication technology and extensive use of XML, we ensure that all changes are dynamically reflected in the print libraries. 4. Print and Fulfillment Company Document Management System A large commercial printer engaged Macrosoft to create a customized document management system that is now used to store, retrieve and print a wide variety of documents ranging from books to brochures to wide format signage. This printer company reviewed many of the commercially available document management systems and found that none in their price range had the functionality and flexibility that they required. The solution they requested had to be fully integrated with their production print operations without any impact on processing efficiencies. Macrosoft was able to produce the document management system which provided the functionality and flexibility required at approximately 50% of the cost of their preferred commercially available package. This document management system provides the full range of functionality available one would normally look for; including document check in/out, audit trail, built-in approval processing, and configurable access controls. System has been in production since 2003. 5. Document Parsing and Distribution System for a Large Print and Direct Mail Company This project involved design and development of an automation system to mechanize the distribution of print files to distributed print sites within a national distributed print network. The system utilizes a VPN based network to greatly speed the transfer of files throughout the network. At the commencement of the project, Gap Analysis was performed leading to submission of a proposed solution (System Definition Report) along with a Time and Cost estimate. At client’s acceptance of the proposed solution, project schedules with timelines and resource allocations were prepared for the various phases of the project. A key element incorporated into the new system was an executive controlled data-driven “brain” that constantly monitors, reconciles and governs all aspects of print file distribution and alerts administration staff when active job files are late or incorrectly cataloged. The system’s confirmation to requirements was ensured through rigorous testing against formally prepared test cases. At the conclusion of the development phase, a Migration/Rollout Plan was prepared for minimal interruption during the rollout phase. The previously manual system was entirely replaced with this scalable, redundant, and highly extensible system. Using Cold Fusion, Java, XML and Oracle as the core technologies the system was rolled out on time and within budget. 6. Extranet Application for Large Manufacturing Company This project involved design and implementation of a ‘Contest and Incentive’ extranet application suite to be accessed by a large manufacturer's dealerships across the United States. The complex, but easy to navigate extranet utilized a number of technologies including Cold Fusion, XML, MS SQL Server, Visual Basic, and MS ACCESS. The application made it possible for the dealers to keep abreast of the latest incentives for the manufacturer's products. In addition, it provided the Manufacturer’s National Office with a mechanism to distribute information to its Dealerships in a secure manner. In a separate project for the same company, we lead development of the Incentive Server application for incentives information to be made available to the dealers and other authorized users running their own web sites via basic HTML Service Mode and the Syndicate Service Mode. The Incentive Server served to syndicate content to arbitrary applications in XML format. The application was developed in Cold Fusion, XML, and MS SQL Server. Page 18 of 20
  19. 19. 7. Automated Workflow for Collateral Creation for a Large Mortgage Company Macrosoft was engaged to automate the workflow associated with the creation of customized marketing collateral on behalf of a National Mortgage Company, in support of their real estate entities. Their original workflow involved personnel in at least five separate organizations, including a rigid approval process, and virtually nothing was automated. As a result, their original process took several weeks to process a request and there were far too many quality defects. Macrosoft business analysts base-lined the existing workflow and proposed a new approach that was supported and automated by a completely web-based application. This new process Provided differing functionality to each of the five unique “user types”; completely automated everything so that orders are now processed in minutes; instituted quality controls and built-in compliance mechanisms so that quality defects were virtually impossible. In response to the success of this original effort, the Mortgage Company has requested at least six new releases of this system over the past four years, each with enhanced functionality. Our automated workflow now supports at least eight additional organizations within the Mortgage Company. Most recently, the Mortgage Company demonstrated their satisfaction with our work to award us with the engagement to provide a Digital Asset Management System (DAM) and Print- on-Demand (POD) system that will support the management of over 1,000 digital documents. These new systems went into full production in 2004. 8. IBM Mainframe to Client/Server Migration for a leading print & mail business in USA The project involved migration of various print applications from IBM Mainframe S-390 to PC. Each application was unique in its own method of handling data of various important clients such as “American Airlines”, “Sony”, “Oracle”, etc. More than 230 such different applications (of different clients) are successfully migrated to PC so far. (Conversion rate of approx. 1 application/day) It involved converting JCLs, COBOLs, Assembler Programs, VSAM data, IBM utility programs such as FTP, Fileaid, Syncsort, Quikjob, Transformer, Anchor, etc. to PC (Embedded Unix). The project involved extracting the relevant program files and data files from Mainframe (Blueprint generation), Analysis, Design & Development of new programs to substitute the mainframe counterparts, Conversion of the various programs (Mainframe Cobol to NetExpress (MF) Cobol, etc.), Conversion/Migration of utilities and data, and Integration of the newly developed modules. Each application contained more than 10 JCLs & procedures, REXX and other programs, more than 10 COBOLs, multiple Assembler Programs, VSAM and other data, more than 10 IBM utilities (Fileaid, IDCAMS, FTP, etc.) and more than 10 third party utilities (like Syncsort, Transformer, Anchor, Quikjob, etc.). The applications are converted utilizing Microfocus (MF) COBOL, Korn shell scripts, Perl, C, Transformer, Syncsort, Microfocus Revolve, etc. The project is successfully completed in 12 months during 2004-05. 9. Geographic Information System for a very large firm The activities in this project may be summarized as below: Modules Functions GIS Data • Procurement of Ortho-rectified High Resolution satellite stereo pairs collection and pertaining to the area Preparation • Development of DEM • Extraction of Elevation of height of Buildings Web based • Standard User Interaction GIS Application • Detailed and overview maps with features like zoom-in, zoom out • Support of various vector formats • Search Engine for Buildings • Generating Building Foot Prints • Support advanced visualization of buildings Page 19 of 20
  20. 20. • Integration of USA wide Street-level view • Geo-coding of USA street addresses • Thematic map building using logical or regular-expression based classes • On-the-fly projection Line of Sight • Determination of Line of Sight between two towers based on CANOPY data Analysis (LOS) • View shed Analysis • Determining Blockage location and highlighting • Integrating into GIS Environment • user clicks on two locations on the map. If visibility is not there it will highlight the location where the blockage occurs using the LOS algorithm. 10. Massive Testing Project for the largest tour operator in North America The project involves testing of their “Operation LeapFrog” application which facilitates all travel and tour bookings online. The project involves development of 10000+ test cases using their 30+ functional specification documents, development of test scripts using QTP (Quick Test Professional), and testing the application. Page 20 of 20

×