Get documents about "New Website Business Plan Sample
Description
New Website Business Plan Sample document sample
Document Sample
Project Plan for Implementing
Common Payment Service
Credit Card
Automated Clearing House (ACH)
Office of State Controller
Office of Information Technology Services
State of North Carolina
April 15, 2004
Instructions
This project plan identifies all the tasks necessary to implement Common Payment Service as part of your organization's business solution. All
deliverables required by your organization during this process are identified as well. This plan also identifies the corresponding tasks for which
the Office of State Controller (OSC) and the Office of Information Technology Services (ITS) are responsible.
There is a project plan for implementing Credit Card as well as ACH processing. Each plan is formatted such that your organization's tasks and
deliverables are identified in columns B and D respectively. It is suggested that you "cut and paste" these items from this plan into any project
plan you may have for implementing your overall business solution. Those tasks and deliverables for which OSC and ITS are responsible are
identified in columns F, G and H.
te Controller
ogy Services
orth Carolina
pril 15, 2004
tasks and
AGENCY ACTIVITIES and TASKS Agency/Project Deliverables
CORRESPONDING TASKS Date
(Agency to include this and Deliverables Task Description (by Agency-fiscal/Agency- By
(OSC & ITS Use Only) Completed
columns in their project plan) business/Agency-IT)
a) Provide instruction to the agency to visit the EPP
website for comprehensive program information.
1 Develop APA-EFT Skip this step if agency already has an APA for EFT OSC
Direct agency to the enrollment page and advise
the agency to download a copy of this workplan
1.1 Review FUNB contract summary Information available from the website.
1.2 Review Agency fiscal office responsibilities Information available from the website's Enrollment Page.
1.3 Review OSC Policies & Guidelines Information available from the website.
1.4 Sign 4 copies of APA document Template available from the website's Enrollment Page.
Send APA by inter-office mail since this document needs
1.5 Submit APA Agency Participation Agreement a) Forward APA to DST for signature OSC
to have the CFO signature.
b) Forward APA to FUNB Rel. Mgr for signature OSC
c) Send "Fiscal Officer" contact details to Sue
OSC
Rader to be added in the EPP List.
a) Upon approval by FUNB, provide the following
OSC provides fully executed copy of APA back to agency
1.6 Obtain fully executed APA to the Agency Fiscal and DST: OSC
fiscal office.
- 1 copy of signed APA
a) Provide instruction to the agency to visit the EPP
2 Identify agency project and Enroll in Porgram website for comprehensive payment capture OSC
solution information
The agency must review the available information from
the website prior to requesting a "research" meeting with
Review all Program Information from OSC
2.1 OSC and the CPS team. The CPS Agency Guide on the
website
website provides detailed information about CPS
implementation.
BY EMAIL to creditcard@mail.osc.state.nc.us. Do not a) Post a copy of the Statement of Requirements to
Complete and submit Statement of
2.2 send paper copies. Template available from the website's Statement of Requirements be accessed by the CPS Team. Notify team of OSC
Requirements
Enrollment Page. posted info via CPSTechSupport@ncmail.net
b) Review volumes, target dates, as well as the
planned Application Server location and look out for CPS Team
non-ITS-hosted servers
Prior to requesting this meeting, ensure the project has
reviewed the following sections of the website:
- FUNB Contract Summary
Request pre-project meeting with OSC if a) Conduct pre-project meeting with agency.
2.3 - Policies & Guidelines OSC
needed. Provide a copy of this workplan.
- Payment Capture Solutions: Common Payment Service
(CPS)
- CPS Service Level Agreement
AGENCY ACTIVITIES and TASKS Agency/Project Deliverables
CORRESPONDING TASKS Date
(Agency to include this and Deliverables Task Description (by Agency-fiscal/Agency- By
(OSC & ITS Use Only) Completed
columns in their project plan) business/Agency-IT)
b) Brief the project on unpublished exception
OSC
information (Initial Agency Meeting Checklist)
c) Invite rep from Tech Services to provide
guidance on security issues. Invite CS rep if CPS Team
application will be ITS-hosted.
This assessment includes cost - benefit analysis using the
cost information available from the website (FUNB
processing, CPS Usage costs, etc as well as
2.4 Assess feasibility of implementation
development costs including server hosting costs etc.
Assess also, if Transaction Fees will or will not be used.
See website for policy information on Transaction Fees.
2.5 Complete FUNB Account Set-up Form for ACH
Send FUNB Account Set up Form by inter-office mail
a) Obtain DDA-ZBA and REA Account(s) from
2.6 Submit FUNB Account set-up form since this document needs to have the Business Manager FUNB Account Set-up Form OSC
State Treasurer
signature.
b) Sen Main Acct Form to FUNB Rel. Mgr for set-
DST
up
c) Send "Fiscal Officer" contact details to Sue
OSC
Rader to be added in the EPP Contact-List.
d) Send "Fiscal Officer" account signature cards FUNB / DST
e) Send User Invision Access / Set-up package FUNB
f) Post a copy of the (1) Account Set-up Form and
(2) the final version of the Statement of
Requirements for access by the CPS team. Notify OSC
team of the posting by email to
CPSTechSupport@ncmail.net
g) Send the Account set-up form with contact
details to Sue Rader to be added in the EPP- OSC
Contact-List.
h) Create a new project folder under the Q-drive
Agency Activation Tracking folder using the CPS Team
Company Name in the Account Set-up Form.
Establish processing environment (for
4
application using ACH)
BY EMAIL to creditcard@mail.osc.state.nc.us.
Security Risk Assessment may be separately required by a) send security risk assessment to IRM security
Perform and submit security risk assessment
4.1 the IRM if the project is under the IRMC's purview. If the Security Risk Assessment staff and CPSTechSupport and request to be OSC
including technical architecture diagram
project needs assistance or direction in developing the advised in writing (email) of review results
security risk assessment - request assistance from the
IRM security staff.
AGENCY ACTIVITIES and TASKS Agency/Project Deliverables
CORRESPONDING TASKS Date
(Agency to include this and Deliverables Task Description (by Agency-fiscal/Agency- By
(OSC & ITS Use Only) Completed
columns in their project plan) business/Agency-IT)
b) CPS Team to review comments and feedback
with Agency Project Manager (APM) to resolve CPS Team
outstanding issues.
c) APM to submit revised Security Risk
Assessment for signature and approval by OSC Agency
and ITS.
BY EMAIL to CPSTechSupport@ncmail.net to obtain
access to the Technical Implementation section of the
a) Store the project CPS Set-up Form in the project
CPS Agency Guide, and agree on an implementation
4.2 Submit CPS Set-up Form - Group 1 Data CPS Set-up Form - Group 1 Data folder under the Q-drive Agency Activation tracking CPS Team
schedule. Submit this as early as possible - AT LEAST 1
folder
MONTH prior to the agency's design phase. The form is
available from the website's Enrollment Page.
b) Open a Vantive ticket to track this project
(Detail="merchant activation support", CPS Team
Description="agency - ACH activation project")
c) Send CPS Technical Implementation access
information to either the PM (if State employee) or CPS Team
to the MIS Manager
d) Assess and discuss with Telecomms and
Computing Services:
- business volumes and cycles
- project timing requirements CPS Team
- access or hosting issues
Set up a meeting with the agency project if needed
to facilitate discussion.
e) Ensure all are in agreement about timelines,
testing schedules, and roll-out approach. Access CPS Team
issues must be resolved at this time.
The CPS Technical Implementation documents include
the sample interface code, class libraries, and program
Review CPS Technical Implementation
4.3 processing descriptions. These are sensitive information
documents
and given only to projects confirmed by OSC (by the
assignment of a Merchant Name or Company Name).
Define application's payment processing requirements,
4.4 Develop the CPS interface establish testing environment, and develop the interface
to CPS
This is to be done with the agency's business operations.
4.5 Establish fulfillment process and logistics
Consult NACHA Rules for payment handling regulations
Develop Test Plan and Application specific Test Test Plan Template and sample Test Script are available
4.6
Script on the website Enrollment Page.
AGENCY ACTIVITIES and TASKS Agency/Project Deliverables
CORRESPONDING TASKS Date
(Agency to include this and Deliverables Task Description (by Agency-fiscal/Agency- By
(OSC & ITS Use Only) Completed
columns in their project plan) business/Agency-IT)
The bill code is used by the ITS billing system to generate
the monthly invoice to the agency for the CPS Usage
Fee. Your agency must decide who will shoulder this
operational cost (IT, business unit, or fiscal). Whoever
4.7 Obtain an ITS Bill Code will take up this cost should open a Bill Code with ITS by Bill Code Request Form
going to the ITS website
at:http://btsweb02.its.state.nc.us/EPP/Enroll/Index.asp
select Bill Code Request Form. If there are any questions
contact ITS Fiscal Office Robert Buckenham at 850-2733.
Submit this as early as possible - NO LESS THAN 2 ACH Only
weeks before testing the CPS Interface - BY EMAIL to b) Set-up the project as a in the Test Environment
CPSTechSupport@ncmail.net to provide test environment using test environment information provided on the
4.8 Submit CPS Set-up Form - Group 2 Data CPS Set-up Form - Group 2 Data CPS Team
set-up information and confirm testing time in the CPS form. Carry out test environment access as agreed
test environment. Use the same form submitted in step in 4.2). CPS Team to coordinate tasks with TS/CS
4.2. Attach a copy of the Test Plan and Test Script. as needed.
ACH Only
d) Provide the following to the agency project:
- any issues detected from the Test Plan and
Script CPS Team
- test application username
- test password
g) Review the production environment information
provided by the project on the form and resolve CPS Team
implementation issues detected.
Submit test results to OSC and CPS support. Testing is
supported by the CPS team during normal business a) Support project testing of the interface as
4.9 Perform CPS interface testing Test Script with test results CPS Team
hours. Make arrangements well in advance if the project needed.
needs support beyond the normal hours.
5 Establish back-office support processes
Review FUNB contract summary with agency
5.1 Info available from website
staff
Review OSC Policies & Guidelines with
5.2 Info available from website
agencystaff
Review Contact Information with agency staff
5.3 Info available from website
and operators
5.4 Review Invision Information Take the WebInvision Tour
Develop Internal Agency Policies & Procedures Template available from website. Request samples from
5.5
(for 1st agency project) other agencies from OSC.
Update the Internal Agency Policies &
5.6
Procedures (for subsequent projects)
BY EMAIL to creditcard@mail.osc.state.nc.us for review. Internal Agency Policies &
5.7 Submit Internal Agency Policies & Procedures
Do not send paper copies. Procedures (new or updated)
AGENCY ACTIVITIES and TASKS Agency/Project Deliverables
CORRESPONDING TASKS Date
(Agency to include this and Deliverables Task Description (by Agency-fiscal/Agency- By
(OSC & ITS Use Only) Completed
columns in their project plan) business/Agency-IT)
6 Perform OSC Acceptance Tasks
a) Within 1 week of submission,
- post the checklist for access by the CPS Team,
Do this AT LEAST 2 WEEKS BEFORE the planned obtain feedback on CPS requirements
Complete and submit the OSC Acceptance OSC
6.1 migration to production. Attach supporting documents OSC Acceptance Checklist - review the checklist and supporting documents
Checklist (A. Young)
and submit BY EMAIL to creditcard@mail.osc.state.nc.us - send back the form to the agency project with
comments by email if there are issues that require
resolution
b) If there are no issues, sign off on the Checklist OSC
and send back a signed copy to the agency project (A. Young)
6.2 Obtain approval and Production set-up numbers
Brief the agency's IT support, business support, and fiscal
support about the proper communication protocol when
the application becomes operational. IT and business
POINTS-OF-CONTACT have to be identified.
Identify the agency personnel who may report problems
and issues to ITS and who will be in ITS's notification list if
there are problems, changes, or issues on the Common
6.3 Conduct briefing on Contact information
Payment Service. All CPS-related problems, issues and
requests must be coursed through the ITS Customer
Support Center (helpdesk). Review website Contact
Information page for details.
Merchant business-related issues and Invision issues
must be coursed through OSC. Review website Contact
Information page for details.
AT LEAST 1 WEEK before production migration and BY
a) Using information from the Group 2 and Group 3
EMAIL to CPSTechSupport@ncmail.net to request
6.4 Submit CPS Set-up Form - Group 3 Data CPS Set-up Form - Group 3 Data set-up data, define the agency store or profile in CPS Team
merchant agency activation in the CPS Production
the respective CPS Production Environment.
environment
b) Obtain firewall policy change approval by
opening a Vantive ticket TAD= "Maintenance -
VPN/Firewall policy update" for CPS Team
- the agency production application servers
c) Add the agency's Bill Code to the CPS table CPS Team
d) Update the CPS.merchant.agency email group
CPS Team
list with agency information provided.
AGENCY ACTIVITIES and TASKS Agency/Project Deliverables
CORRESPONDING TASKS Date
(Agency to include this and Deliverables Task Description (by Agency-fiscal/Agency- By
(OSC & ITS Use Only) Completed
columns in their project plan) business/Agency-IT)
e) Update the CPS Merchant Agency Database
with Settlement and Maintenance windows, and CPS Team
other set-up information
Coordinate migration activities and schedule with OSC
6.5 Migrate agency application into production
and the CPS team.
Testers should be State employees or contractors whose
6.6 Recruit production verification testers
use of the live application can be directed and monitored.
This process takes from 1 - 2 weeks. Production
Verification means the agency application is live and will
accept and process LIMITED live transactions from pre-
identified State employees. The purpose is to determine
if the merchant agency had been set-up correctly: the
6.7 Perform "production verification" funds are received within the next business day, a) Monitor the production transactions. CPS Team
processing rates applied on transactions are correct,
processing charges are not debited against the daily
funding deposits, etc. Any incorrect set-ups have to be
corrected before making the online service open to the
public.
b) Monitor the batch settlement process. CPS Team
c) Guide agency in their initial review of the Invision
OSC
reports after the settlement is completed.
Report findings to OSC. OSC will work with First Union a) Guide agency in using Invision to review
6.8 Resolve agency set-up issues detected OSC
for any agency-set-up issues. settlement results.
a) Review results to ensure there are no agency set-
6.9 Submit "production verification" final results BY EMAIL to creditcard@mail.osc.state.nc.us for review. Test Script with final test results OSC
up issues remaining.
Issue public announcement / availability of a) Brief agency points of contact on the use of ITS
6.10 CPS Team
service if needed helpdesk support from this point onward.
b) Close the Vantive ticket for this CPS activation
CPS Team
project.
Workplan Template
For Applications using the Common Payment Service (CPS)
AGENCY ACTIVITIES and TASKS Agency/Project Deliverables
CORRESPONDING TASKS Date
(Agency to include this and Deliverables Task Description (by Agency-fiscal/Agency- By
(OSC & ITS Use Only) Completed
columns in their project plan) business/Agency-IT)
a) Provide instruction to the agency to visit the EPP
website for comprehensive program information.
1 Develop APA-Credit Card Skip this step if agency already has an APA for CC OSC
Direct agency to the enrollment page and advise
the agency to download a copy of this workplan
1.1 Review WMS contract summary Information available from the website.
1.2 Review Agency fiscal office responsibilities Information available from the website's Enrollment Page.
1.3 Review OSC Policies & Guidelines Information available from the website.
1.4 Sign 3 copies of APA document Template available from the website's Enrollment Page.
1.5 Complete Main Account Set-up Form
Send APA by inter-office mail since this document needs
Agency Participation Agreement a) Obtain DDA Account from State Treasurer and
1.6 Submit APA and Main Account set-up form to have the CFO signature. Send the Main Account Set- OSC
Main Account Set-up Form record this on the outlet set-up form
Up Form by EMAIL to creditcard@mail.osc.state.nc.us
b) Forward APA and Main Acct Form to WMS Rel.
OSC
Mgr for set-up and signature
c) Send "Fiscal Officer" contact details to Sue
Rader to be added in the EPP- Credit Card Contact- OSC
List.
a) Upon set-up by WMS, provide the following to
the Agency Fiscal:
Obtain set-up information and fully executed OSC provides Main Account information and fully
1.7 - 1 copy of signed APA OSC
APA executed copy of APA back to agency fiscal office.
- Chain Merchant Acct Number
- Agency DDA Account
a) Provide instruction to the agency to visit the EPP
2 Identify agency project website for comprehensive payment capture OSC
solution information
The agency must review the available information from
the website prior to requesting a "research" meeting with
Review all Program Information from OSC
2.1 OSC and the CPS team. The CPS Agency Guide on the
website
website provides detailed information about CPS
implementation.
BY EMAIL to creditcard@mail.osc.state.nc.us. Do not a) Post a copy of the Statement of Requirements to
Complete and submit Statement of
2.2 send paper copies. Template available from the Statement of Requirements be accessed by the CPS Team. Notify team of OSC
Requirements
website's Enrollment Page. posted info via CPSTechSupport@ncmail.net
b) Review volumes, target dates, as well as the
planned Application Server location and look out CPS Team
for non-ITS-hosted servers
1c73bdd9-3a04-471f-8048-34dbdfb445db.xls Page 11
Workplan Template
For Applications using the Common Payment Service (CPS)
Prior to requesting this meeting, ensure the project has
reviewed the following sections of the website:
- WMS Contract Summary
Request pre-project meeting with OSC if a) Conduct pre-project meeting with agency.
2.3 - Policies & Guidelines OSC
needed. Provide a copy of this workplan.
- Payment Capture Solutions: Common Payment Service
(CPS)
- CPS Service Level Agreement
b) Brief the project on unpublished exception
OSC
information (Initial Agency Meeting Checklist)
c) Invite rep from Tech Services if Application
Server is not ITS-hosted to provide guidance on
CPS Team
security issues. Invite CS rep if application will be
ITS-hosted.
This assessment includes cost - benefit analysis using
the cost information available from the website (card
processing costs, terminal costs, CPS Usage costs, etc
2.4 Assess feasibility of implementation as well as development costs including server hosting
costs etc. Assess also, if Transaction Fees will or will not
be used. See website for policy information on
Transaction Fees.
3 Enroll project into the program
BY EMAIL to creditcard@mail.osc.state.nc.us. Do not
a) Assign and email a 24-character Merchant
3.1 Complete and submit the Outlet Set-up Form send paper copies. Template available from the Outlet Set-up Form OSC
Name to the project within 1-2 days
website's Enrollment Page.
b) Email the Outlet Set-up form to WMS Rel. Mgr
OSC
for set-up
c) Post a copy of the (1) Outlet Set-up Form and
(2) the final version of the Statement of
Requirements for access by the CPS team. Notify OSC
team of the posting by email to
CPSTechSupport@ncmail.net
d) Send the outlet set-up form with contact details
to Sue Rader to be added in the EPP- Credit Card OSC
Contact-List.
a) Create a new project folder under the Q-drive
Agency Activation Tracking folder using the CPS Team
Merchant Name in the Outlet Set-up Form.
When OSC assigns a MERCHANT NAME to an agency
project, the agency project may then request access to
the CPS Technical Implementation documents to begin
their development efforts (step 4.1).
Obtain Outlet Merchant Account Number and
3.2 OSC assigns the MERCHANT NAME within 1-2 business
Merchant Name
days after receipt of the Outlet Set-up Form. Wachovia
Merchant Services assigns the OUTLET MERCHANT
ACCOUNT NUMBER within 2 weeks after receipt of the
Outlet Set-up Form from OSC. OSC will provide this
number to the Agency Project upon receipt from WMS.
1c73bdd9-3a04-471f-8048-34dbdfb445db.xls Page 12
Workplan Template
For Applications using the Common Payment Service (CPS)
The business owner will identify select staff who need to
use MyMerchantView for reconciliation and management
purposes. Access must be restricted. See the website or
Complete and submit MyMerchantView sign-up
3.3 consult OSC for guidance. The enrollment form is MyMerchantView Sign-up Form
form(s)
submitted to the Agency's fiscal office for approval and
processing (not to OSC). Instructions are on the form
which is available from the website's Enrollment Page.
MyMerchantView provides this information directly to the
3.4 Obtain MyMerchantView enrollment information
individual by FAX.
The business owner will identify select staff who need to
use WCP for reconciliation and management purposes.
See the website or consult OSC for guidance. The
Complete and submit Wachovia Connection a) Define user-ID and password for each individual
3.5 enrollment form is submitted to the Agency's fiscal office WCP Sign-up Form OSC
Plus sign-up form applicant.
for approval (not to OSC) and processing. Instructions
are on the form which is available from the website's
Enrollment Page.
OSC provides this information directly to the individual by a) Call (do not email) to provide user-ID and
3.6 Obtain WCP enrollment information OSC
phone or fax. password information to each individual.
Establish processing environment (for
4
application using CC )
BY EMAIL to creditcard@mail.osc.state.nc.us.
Security Risk Assessment may be separately required by a) send security risk assessment to IRM security
4.c.1 Perform and submit security risk assessment the IRM if the project is under the IRMC's purview. If the Security Risk Assessment staff and request to be advised in writing (email) of OSC
project needs assistance or direction in developing the review results
security risk assessment - request assistance from the
IRM security staff.
b) email review results to
OSC
CPSTechSupport@ncmail.net
BY EMAIL to CPSTechSupport@ncmail.net to obtain
access to the Technical Implementation section of the
a) Store the project CPS Set-up Form in the project
CPS Agency Guide, and agree on an implementation
4.2 Submit CPS Set-up Form - Group 1 Data CPS Set-up Form - Group 1 Data folder under the Q-drive Agency Activation tracking CPS Team
schedule. Submit this as early as possible - AT LEAST 1
folder
MONTH prior to the agency's design phase. The form is
available from the website's Enrollment Page.
b) Open a Vantive ticket to track this project
(Detail="merchant activation support",
CPS Team
Description="merchant name - merchant activation
project")
c) Send CPS Technical Implementation access
information to either the PM (if State employee) or CPS Team
to the MIS Manager
1c73bdd9-3a04-471f-8048-34dbdfb445db.xls Page 13
Workplan Template
For Applications using the Common Payment Service (CPS)
d) Assess and discuss with Telecomms and
Computing Services:
- business volumes and cycles
- project timing requirements CPS Team
- access or hosting issues
Set up a meeting with the agency project if needed
to facilitate discussion.
e) Ensure all are in agreement about timelines,
testing schedules, and roll-out approach. Access CPS Team
issues must be resolved at this time.
The CPS Technical Implementation documents include
the sample interface code, class libraries, and program
Review CPS Technical Implementation
4.3 processing descriptions. These are sensitive information
documents
and given only to projects confirmed by OSC (by the
assignment of a Merchant Name ).
Define application's payment processing requirements,
4.4 Develop the CPS interface establish testing environment, and develop the interface
to CPS
This is to be done with the agency's business operations.
4.5 Establish fulfillment process and logistics Consult the WMS Program Guide for payment handling
and fulfillment rules.
Test Plan Template and sample Test Script are available
Develop Test Plan and Outlet-specific Test on the website Enrollment Page. For CPS, make sure
4.6
Script there is a test against the maximum transaction dollar
amount.
The bill code is used by the ITS billing system to
generate the monthly invoice to the agency for the CPS
Usage Fee. Your agency must decide who will shoulder
this operational cost (IT, business unit, or fiscal).
Whoever will take up this cost should open a Bill Code
4.7 Obtain an ITS Bill Code Bill Code Request Form
with ITS by going to the ITS website
at:http://btsweb02.its.state.nc.us/EPP/Enroll/Index.asp
select Bill Code Request Form. If there are any questions
contact ITS Fiscal Office Robert Buckenham at 850-
2733.
Submit this as early as possible - NO LESS THAN 2
Credit Card Only
weeks before testing the CPS Interface - BY EMAIL to
a) Set-up the project as a CPS Store in the Test
CPSTechSupport@ncmail.net to provide test
Environment using test environment information
4.8 Submit CPS Set-up Form - Group 2 Data environment set-up information and confirm testing time CPS Set-up Form - Group 2 Data CPS Team
provided on the form. Carry out test environment
in the CPS test environment. Use the same form
access as agreed in 4.2). CPS Team to coordinate
submitted in step 4.c.2. Attach a copy of the Test Plan
tasks with TS/CS as needed.
and Test Script.
Credit Card Only
b) Provide the following to the agency project:
- any issues detected from the Test Plan and
Script
CPS Team
- test application username
- test password
- test visa card number ($1 limit)
- test mc card number ($1 limit)
1c73bdd9-3a04-471f-8048-34dbdfb445db.xls Page 14
Workplan Template
For Applications using the Common Payment Service (CPS)
c) Schedule Paylinx Client deployment and
orientation with the agency users specified on the CPS Team
Set-up Form.
d) Deploy the PaylinX Client and conduct
orientation (use the PaylinX Client Deployment CPS Team
Procedure).
e) Review the production environment information
provided by the project on the form and resolve CPS Team
implementation issues detected.
Submit test results to OSC and CPS support. Testing is
supported by the CPS team during normal business a) Support project testing of the interface as
4.9 Perform CPS interface testing Test Script with test results CPS Team
hours. Make arrangements well in advance if the project needed.
needs support beyond the normal hours.
5 Establish back-office support processes
Review WMS contract summary with agency
5.1 Info available from website
staff
5.2 Review WMS Program Guide with outlet staff Info available from website
Review OSC Policies & Guidelines with
5.3 Info available from website
agencystaff
Review Contact Information with agency staff
5.4 Info available from website
and operators
5.5 Review PaylinX Client User Guide Info available from website
Take the MyMerchantView Tour Guide at
5.6 Review MyMerchantView information
www.home.MyMerchantView-services.com
5.7 Review WCP information
Develop Internal Agency Policies & Procedures Template available from website. Request samples from
5.8
(for 1st agency project) other agencies from OSC.
Update the Internal Agency Policies &
5.9
Procedures (for subsequent projects)
BY EMAIL to creditcard@mail.osc.state.nc.us for review. Internal Agency Policies &
5.10 Submit Internal Agency Policies & Procedures
Do not send paper copies. Procedures (new or updated)
6 Perform OSC Acceptance Tasks
a) Within 1 week of submission,
- post the checklist for access by the CPS Team,
Do this AT LEAST 2 WEEKS BEFORE the planned
obtain feedback on CPS requirements
Complete and submit the OSC Acceptance migration to production. Attach supporting documents OSC
6.1 OSC Acceptance Checklist - review the checklist and supporting documents
Checklist and submit BY EMAIL to (A. Young)
- send back the form to the agency project with
creditcard@mail.osc.state.nc.us
comments by email if there are issues that require
resolution
b) If there are no issues, sign off on the Checklist OSC
and send back a signed copy to the agency project (A. Young)
c) Send an acceptance confirmation email to the
agency project including fiscal and business areas,
and to the CPS Team that includes MID,TID , and
User Profile information.
6.2 Obtain approval and Production set-up numbers
1c73bdd9-3a04-471f-8048-34dbdfb445db.xls Page 15
Workplan Template
For Applications using the Common Payment Service (CPS)
Brief the agency's IT support, business support, and
fiscal support about the proper communication protocol
when the application becomes operational. IT and
business POINTS-OF-CONTACT have to be identified.
Identify the agency personnel who may report problems
and issues to ITS and who will be in ITS's notification list
if there are problems, changes, or issues on the Common
6.3 Conduct briefing on Contact information
Payment Service. All CPS-related problems, issues and
requests must be coursed through the ITS Customer
Support Center (helpdesk). Review website Contact
Information page for details.
Merchant business-related issues, MyMerchantView and
WCPissues must be coursed through OSC. Review
website Contact Information page for details.
AT LEAST 1 WEEK before production migration and BY
a) Using information from the Group 2 and Group 3
EMAIL to CPSTechSupport@ncmail.net to request
6.4 Submit CPS Set-up Form - Group 3 Data CPS Set-up Form - Group 3 Data set-up data, define the agency store or profile in CPS Team
merchant agency activation in the CPS Production
the respective CPS Production Environment.
environment
b) Update the PaylinX Client user set-ups with the
production MID. Check that the users have
CPS Team
reviewed the User Guide and know how to use the
reports.
c) Obtain firewall policy change approval by
opening a Vantive ticket TAD= "Maintenance -
VPN/Firewall policy update" for CPS Team
- the agency production application servers
- agency PaylinX Client workstations
d) Add the agency's Bill Code to the CPS table CPS Team
e) Update the CPS.merchant.agency email group
CPS Team
list with agency information provided.
f) Update the CPS Merchant Agency Database with
Settlement and Maintenance windows, and other CPS Team
set-up information
Coordinate migration activities and schedule with OSC
6.5 Migrate agency application into production
and the CPS team.
Testers should be State employees or contractors whose
6.6 Recruit production verification testers
use of the live application can be directed and monitored.
1c73bdd9-3a04-471f-8048-34dbdfb445db.xls Page 16
Workplan Template
For Applications using the Common Payment Service (CPS)
This process takes from 1 - 2 weeks. Production
Verification means the agency application is live and will
accept and process LIMITED live transactions from pre-
identified State employees. The purpose is to determine
if the merchant agency had been set-up correctly: the
6.7 Perform "production verification" funds are received within the next business day, a) Monitor the production transactions. CPS Team
processing rates applied on transactions are correct,
processing charges are not debited against the daily
funding deposits, etc. Any incorrect set-ups have to be
corrected before making the online service open to the
public.
b) Monitor the batch settlement process. CPS Team
c) Guide merchant agency in their initial review of
the PaylinX reports after the settlement is CPS Team
completed.
Report findings to OSC. OSC will work with Wachovia a) Guide agency in using MyMerchantView to
6.8 Resolve agency set-up issues detected OSC
Merchant Services for any agency-set-up issues. review settlement results.
a) Review results to ensure there are no agency
6.9 Submit "production verification" final results BY EMAIL to creditcard@mail.osc.state.nc.us for review. Test Script with final test results OSC
set-up issues remaining.
Issue public announcement / availability of b) Brief agency points of contact on the use of ITS
6.10 CPS Team
service if needed helpdesk support from this point onward.
c) Close the Vantive ticket for this CPS activation
CPS Team
project.
1c73bdd9-3a04-471f-8048-34dbdfb445db.xls Page 17
Related docs
Other docs by zwi23778
