Proponent:

PROPOSAL EVALUATION SUMMARY

Evaluation Category Proponent Response

1. Meeting SGI's Business Requirements

1.1 Recommended analysis, design, build and deployment plan
Quality and likelihood of the plan to result in a successful
1.1.1 implementation
Efficiency of the plan in meeting SGI's needs, both in
1.1.2 duration and usage of resources

Facilitate the discovery of all external to PowerBuilder touches

(eg calls to external DLLs or libraries); document the
relationship between the application and external components as
well as the constraints, assumptions, risks and dependencies
found therein; detail any risk mitigation that must be addressed
1.2 due to this discovery
Recommend solution architecture, which must include a
definition of the logical layers and/or physical tiers. Differences
from SGI's intended solution architecture must be identified and
1.3 reason(s) given for the difference.

Recommend user interface strategy assuring functional

equivalence and connectivity for other dependent interfaces,
1.4 protecting the integrity of the user experience and process flow.
Migrate GIS from PowerBuilder 12.5.2 to the Java application
stack as identified in the RFP; identify method of code
1.5 migration.

Note: SGI will facilitate and support development environments

(establishing adequate development environment and local or
remote access to that environment for developers as required,
preparing data to support test scenarios within modified system
as well as managing the relationship with all interfaced systems
necessary). Solutions should indicate what they will require of
SGI towards this, or if they require copies of SGI code base and /
or sanitized test data in their own environment to perform
development activities.
 Re-factor the application into a logical (not physical) multi-tiered
architecture, extracting business logic and data access from the
1.6 presentation layer and implementing it into MVC architecture.
Redesign the User Interface when/if necessary to accommodate
1.7 differences between PowerBuilder and Java
Code using best practice tools and techniques consistent with
1.8 SGI architecture and development standards

Facilitate periodic code reviews with the SGI integration team;

reviews which must include senior representation from both the
development team and the SGI implementation team; monitor
1.9 and track issues, providing written results to SGI
Minimize potential performance issues and, where possible, use
techniques such as pagination to manage large data volumes and
1.10 AJAX to minimize network traffic

1.11 Include structured exception handling in the migrated application

Keep code base current with required changes in the source
PowerBuilder applications during development and testing
1.12 stages (eg production fixes)
1.13 Recommend test planning
Facilitate unit, integration and system testing, assuring functional
1.14 equivalency; test cases will be written by SGI
Include the SGI integration team in the unit, integration and
1.15 system testing
These test plans shall include, but are not limited to, all
functional and non-functional software, hardware, equipment
1.16 and accessories
Provide an audit trail and summary for all defects identified in
1.17 unit, integration and system testing
Document validation and test plans including expected results
1.18 and testing techniques
Meet weekly, or more frequently if needed, to review testing
1.19 status
Participate in user acceptance testing, assuring functional
equivalency; test cases will be written by SGI and the testing
1.20 time frame will be determined by SGI
Assist SGI in user acceptance testing, including installation
1.21 support
Provide an audit trail and summary for all defects identified in
1.22 testing, utilizing SGI's JIRA issue tracking system
 Allow the SGI integration team to re-test previously failed test
1.23 cases

Note: SGI will facilitate and support user acceptance testing

(establishing adequate test environment, preparing data to
support test scenarios within modified system as well as
managing the relationship with all interfaced systems as
necessary). Solutions should indicate what they will require of
SGI towards this.
1.24 Participate in end-to-end testing

1.25 Assist SGI in end-to-end testing, including installation support

Provide an audit trail and summary for all defects identified in
1.26 testing, utilizing SGI's JIRA issue tracking system
Allow the SGI integration team to re-test previously failed test
1.27 cases

Note: SGI will facilitate and support end-to-end testing

(establishing adequate test environment, preparing data to
support test scenarios within modified system as well as
managing the relationship with all interfaced systems necessary).
Solutions should indicate what they will require of SGI towards
this.
Allow for performance testing and prove results are as good or
1.28 better than previous system
Allow for vulnerability scans to be performed against the new
application platform, with a plan to address issues of a high
1.29 enough severity prior to production implementation.
Propose an automated testing approach for both system and user
1.30 testing
1.31 Correct defects found as a result of testing efforts
Assist SGI in support, implementation and deployment of
1.32 application and platform environment
Appoint senior development staff from the development team to
1.33 support implementation
Recommend operations and administration procedures related to
1.34 code implementation
Allow the SGI implementation team access to periodic code
reviews (as already detailed in the development section of this
1.35 RFP)
Provide knowledge transfer documentation in the form of a
1.36 technical design document
 Provide, maintain and update project plans, identifying critical
path dependencies, major critical milestones and project
1.37 deliverables
Provide regular status reviews and progress reports every two
1.38 weeks
Ensure the SGI team has as much prior notice as possible
regarding all tasks required of it for the successful completion of
1.39 the project
1.40 Provide communication plans for all aspects of the migration
Maintain the involvement of suitably qualified and experienced
1.41 people throughout the project
Provide adequate handover if staff changes throughout the
1.42 project
Proponent:

PROPOSAL EVALUATION SUMMARY

Evaluation Category Proponent Response

4. Pricing
4.1 Software licensing to purchase the solution.
4.2 Specialized hardware required to deliver the solution.
Maintenance and support costs of the software for the
4.3 solution.
A statement of assumptions on factors that could affect the
4.4 costs projected above.
Identify any costs associated with changes to the original
4.5 proposal and costs for future changes
Services required to design and build the solution to SGIs
4.6 specifications.
4.6.1 Planning
4.6.2 Design
4.6.3 Development
4.6.4 Testing
4.6.5 Implementation
4.6.6 Warranty

349348677.xlsx Page 5
03/24/2017