IT Level of Effort Document
CME Pro and CME Pro Jr. Windows XP Upgrade
Background:
The NCSC Integrated Card Production System (ICPS) is designed to provide for fully automated
multi-variant card production capability. The system possesses the capability to produce six card
variants for the Immigration and Naturalization Service including the Employment Authorization
Document (EAD), Department of State Border Crossing Card (DOS-BCC), Alien Registration
Card (ARC/PRC), Marianna Islands Card (NM), American Indian Card (AI), and Student visa
cards.
The CME Pro Card Reconciliation System was introduced to each of the USCIS Service Centers
to facilitate the functions of card production such as import/export, quality assurance (QA),
preparation for mailing, and is integrated into the ICPS. The CME Pro Card Reconciliation
System maximizes the card and process quality for each of the production lines at a given center
while more effectively tracking card inventory usage thus significantly increasing production
levels.
CME Pro Jr. works in concert with the CME Pro. It is a COM component loaded at the end of
each card production line at the scanning stations. It automates the updating of the NPS
database.
USCIS is moving toward converting their entire PC/Server platform to Windows XP SP2/Windows
2003. The CMEPro client/server and CMEPro Jr. are in need of upgrades to run properly and
reliably on the XP/2003 Server operating systems. It is known that the CMEPro Jr. will not run on
the XP SP2 platform.
Task Overview and Goals:
Our understanding of the request is that there is a need to upbgrad the CME Pro reconciliation
system and the CME Pro Jr. COM component to work on the XP/2003 Server operating systems.
Both the server components and the client components will eventually need to be upgraded to
work on the XP/2003 Server operating systems. However this LOE is focused on the upgrade of
client components only. The server components will continue to be hosted on the Windows 2000
environment.
The following technical issues have already been identifed:



The CME Pro Jr. component does not work on Windows XP SP2
The Oracle 9i client drivers are not stable with older versions of MDAC
4D 6.7.1 may be unstable in the Windows XP/2003 using commands for interacting with
serial ports (scanning devices)
Shelton Lee
Page 1
2/12/2016
IT Level of Effort Document
Suggested approach to solution:
Since we are focusing on the client components we can effectively isolate the main issues for
correction.



Update the CME Pro Jr. to work with the latest Oracle 9i native drivers
Update Oracle client to work with XP/2003 compatible versions of MDAC
Update scanning functions effectively trap errors which cause 4D clients to crash
To make these updates we propose the following approach:
1) Recreate a development platform to mimic the card production facilities.
a. standup a CME Pro server (Windows 2000)
b. standup a client system (Windows XP SP2)
c. standup a test NPS database (Oracle 9i)
2) Configure and test driver combinations to get the Oracle 9i drivers to work properly with
MDAC versions compatible with XP/2003. If this proves to be problematic then we would
test newer Oracle client software and drivers possibly 10g to work with test NPS system.
3) Integrate the connectivity of the CME Pro Jr. component to the test NPS system in one of
three ways:
a. Use the native driver combination identified in step 2
b. Use ODBC drivers to connect the CME Pro Jr. component to the test NPS
system
c. Re-engineer the CME Pro Jr. component using another development platform
(.NET, Java, Delphi, C++, etc.)
4) Modify and validate the CME Pro code for interaction with scan devices to gracefully
handle system errors
5) Conduct system testing the development environment
6) Deploy the client upgrades on a single client for integration testing
Assumptions:
The following assumptions were made during the creation of this document.
1)
2)
3)
4)
5)
All client systems will be configured to run Windows XP SP2 or higher
The client software with remain 4D 6.7.1
The client computer hardware will not be upgraded only the software and service packs
CSC will provide the latest data structure for NPS and a small set of test data.
We will standup the development platform off site
Shelton Lee
Page 2
2/12/2016
IT Level of Effort Document
Estimate of Work (EOW)
The following is a basic Estimate of Work for the update of the CME Pro and CME Pro Jr. client
components.
Initial Breakdown
Development Task
Configure development
platform
Description
Recreate a development platform configuring
server, database and client components to closely
match the production environment.
Review CME Pro Jr. &
After the development platform is configured I will
NPS Functions
need to review the CME Pro Jr. and the NPS
functionality and develop unit test cases
Configure and Test
Test different combination and configure Oracle
Oracle Native Drivers
drivers to work properly with MDAC versions
compatible with XP/2003. Without going through
CME Pro Jr.
Assemble components
Integrate the connectivity of the CME Pro Jr.
for system testing.
component to the test NPS system. This includes
re-engineering the CME Pro Jr. component if
needed.
Conduct Pre deployment Fully testing the system within the new
System Testing
environment and validating that the integrated
components work together. This includes
configuration of a test environment at the Chantilly
VA office, and support for the CSC/Datatrac QA
group.
Develop Configuration
Once the upgrades have been tested and the
and Deployment
code base locked down we will develop
Documentation
documentation for the configuration and
deployment of the new versions. This will include
documentation for rolling back updates if needed.
Integration testing Site
If the existing errors can not be reproduced in the
Visit. (if needed)
development platform or deployment of the
upgrades to a single print line at does not install or
work as expected a site visit will be needed.
These hours are for a potential three day site visit
to the Corbin CPF. A laptop containing the
software and source code needed to modify and
deploy fixes and updates to the CME Pro and
CME Pro Jr will be taken so that identified errors
can be corrected while on site.
Support for integration
Includes: phone support, debugging upgraded
testing and deployment
components, development of baseline
of upgrades
configuration and installation documents.
Time and Materials based Overall Estimated Total:
Time Frame
20 hours
12 hours
15 hours
30 hours
22 hours
14 hours
30 hours
20 hours
163 hours
Note: This LOE is based on time and materials.
Shelton Lee
Page 3
2/12/2016