-
Page 1 of 25
RFP ADDENDUM RFP-18 Rev. 11/17/16 Prev. Rev. 3/13/14
STATE OF CONNECTICUT DEPARTMENT OF ADMINISTRATIVE SERVICES
RFP NO.:
18PSX0277
Susanne Hawkins Contract Specialist
PROCUREMENT DIVISION 450 Columbus Boulevard, Hartford, CT
06103
Proposal Due Date:
12 July 2019
860-713-5064 Telephone Number
Date Addendum Issued:
10 June 2019
PLEASE NOTE: This document has been marked as “Returnable”.
Electronic submittal of this document indicates that your
company has read and accepted any modifications to the RFP that
are contained in this Addendum.
RFP ADDENDUM #3 DESCRIPTION: CCSES Replacement Project - Design,
Development & Implementation FOR: Department of Social Services
PROPOSERS NOTE: Responses to submitted RFP #18PSX0277 questions
posted below: Question 1: Has a budget been allocated for this
project? May I know an estimated contract value if possible? Q1
Response: Yes. The Feasibility Study in 2017 estimated the total
cost for implementation of a hybrid solution to be $68 million of
which the DDI cost (including infrastructure – hardware and
software license) was estimated to be about $43 million. The State
would like the vendor community to address the project’s
requirements in detail and propose their approach to the solution.
It is important to be strategic about what the vendor can do versus
what is cost effective for the success of the program. Proposers
should calculate their cost proposal for a solution that is within
a reasonable margin. As mentioned in the RFP, the State is looking
for the total cost of ownership for 10 years. Question 2: To
provide our firm with enough time to develop a responsive proposal
that outlines our approach to meeting the requirements and
objectives outlined in the RFP, will the agency extend the due date
by one month? Q2 Response: Reference RFP Addendum #2 issued on
Wednesday, May 29, 2019 to extend the RFP due date. RFP #18PSX0277
due date has been extended through Wednesday, August 7, 2019 at
2:00 pm (Eastern Time). Question 3: Will you please extend the due
date for the proposal 4 additional weeks? Please note that the
State of Indiana also has a similar Child Support Modernization RFP
released which is due very close to the State of CT's. The extra
4-weeks will provide the vendor community more time to author the
highest quality responses to CT given the conflicting schedules. Q3
Response: Reference Q2 response. Question 4: Will there be an
option to join the Thursday May 23rd bidder’s conference virtually?
Can a conference call line be set-up to allow for remote
participation? Q4 Response: No, the May 23, 2019 optional
pre-proposal conference is an overview of the RFP process and
project information for the solicitation. After the conference,
slides from the conference will be posted on the Bidder’s
Library.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 2 of 25
Question 5: Is the SP-26 Contractor Information Form the only
document that requires to be e-signed. Q5 Response: Yes and the
form needs to be submitted and uploaded from the email of the
person that has corporate authorization to bind the company into
contract. Therefore, the person that has corporate authorization
will need to have a BizNet Account created for their email and
their email will need to be connected to the company BizNet
account. Question 6: All Affidavits need to be submitted and signed
by the person that Corporate Authorization even if the Affidavit is
Not Applicable? Q6 Response: Yes, all affidavits to be submitted
with the proposal submission and must be signed by the person that
has corporate authorization to bind the company into contract.
Please reference on Page 3 and 4 of the RFP Document Instruction
Link for Uploading Affidavits. Question 7: Does the State desire
prospective bidders to comment on the Attachment 1 – Sample
Contract in their proposal response? Q7 Response: No, the Sample
Contract Document is not a required returnable document, this is a
sample Contract Document only that contains our Standard Contract
Language Terms and Conditions. Question 8: On page 13 of the RFP
Document, per the roles and responsibilities of the key project
teams outlined in the RFP document, can the Department clarify if
IV&V, the QA and/or the PMO have been selected for this
project? If so, can the Department provide the names of the
vendors? If not, does the Department intend to release separate
RFPs for the procurement of these services with another vendor? Q8
Response: IV&V is in procurement phase which will be finalized
before bringing DDI vendor on board, the PMO function is already in
place which is managed by Department’s EPMO Group, and the QA
function is anticipated to be done internally. Question 9: Are
bidders permitted to include a letter of transmittal? Q9 Response:
Yes. Question 10: With the RFP extension of the due date for
proposals, would the State consider allowing for a second round of
questions? Q10 Response: No, not at this time. Question 11: In the
RFP Document, on page 94 of the Submittal Requirements may bidders
submit longer documents in a separate section 7? (e.g., Project
Schedule, Financial Statements, and Other Applicable Value-Added
Services) Q11 Response: Yes. Question 12: For clarification, would
the State please confirm which percentage of System Availability
will the one expected from Vendor, 99.96% as per RFP, or 99.9% as
per Contract? Q12 Response: System Availability 99.96% as per RFP
specifications. Question 13: Included in the conceptual technical
architecture of the new CCSES system is a Master Data Management
Database. Does this already exist and require integration as part
of the modernization? Or, is this a new requirement for the new
system to support a master client record? Q13 Response: Child
Support is currently not using an MDM solution. The conceptual
architecture provided is meant to be suggestive and should be used
as a guidance by the vendors to get a high level perspective of the
new system– State is not prescribing a certain solution and is
looking for the best approach and solution from the vendors.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 3 of 25
Question 14: How many users are anticipated for the new CCSES
system? Q14 Response: There will be a total of about 2600 users who
will have access to the system (besides citizens who can log in
online for viewing/updating some limited information). Out of the
2600 internal State users, about 2000 will have inquiry only access
and about 600 will be able to enter/update/modify information.
Question 15: Is the Enterprise Project Management Office fulfilled
by state staff or will a contractor be procured to provide these
services? Q15 Response: Reference Q8 response. Question 16: Is data
conversion required for the Fatherhood Initiative separate/in
addition to the legacy data? If yes, in what format is the legacy
Fatherhood Initiative data? Q16 Response: There is no requirement
for legacy Fatherhood data conversion. Question 17: How many legacy
data systems will conversion be required and was is the source
format of each? Q17 Response: Only current CCSES legacy data needs
to be converted which is in UniVerse DB (hierarchical flat file
format). Also, Vendors may need to associate some (low number) of
the case related documents, with the existing cases. Question 18:
RFP requirement in Section 1.1.10 Security, the system must comply
with IRS Publication 1075, does the State anticipate storing FTI
data as a part of the solution? If so, will you accept a hybrid
solution where FTI data is stored on-premise or in a third-party
solution that meets IRS 1075 requirements? If the State does not
anticipate storing FTI data in the solution, can the State please
adjust and remove the RFP requirements that refer to mandatory 1075
compliance? By not removing this requirement, this will make a
significant difference in complexity and cost in the vendor's
proposed solution. Q18 Response: System and any component of the
system that has FTI data (stored, processed or transacted) must be
IRS Publication 1075 compliant. Question 19: RFP requirement for
System Availability, the Contractor should ensure application
software component uptime (CCSES availability) is no less than
99.96% of host environment uptime (server, operating system, and
storage) for all major functions excluding scheduled downtime or
CCSES-initiated downtime. Cloud Services Provider (CSP) uses
commercially reasonable efforts to make its on-demand services
available to its customers 24/7, except for planned downtime, for
which the CSP gives customers prior notice, and force majeure
events. While availability SLAs can be negotiated in a contract,
the calculation is measured quarterly and not monthly. Can the
State please adjust this requirement and specify that the SLA
requirements can be negotiated based on the Service provider
chosen? Q19 Response: SLA requirements will be negotiated. Question
20: Are bidders allowed to provide any exceptions to the RFP
requirements? For example, there are requirements that would not
apply to cloud-based solutions or, in some cases, the Cloud
Solution Provider does not fully meet requirements explicitly as
written. How are bidders to include these exceptions or
assumptions, with explanation, in their proposal for the City's
review and consideration without being non-compliant with the RFP?
Q20 Response: Please follow the instruction in Appendix A -
Requirements Matrix. If the requirement cannot be met, please
select NM against the requirement and provide an explanation as to
why it cannot be met.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 4 of 25
Question 21: What is the number of end users and split of the
users between functions (RFP says minimum number of users as 500)?
Q21 Response: There will be a total of about 2600 authorized users
who will have access to the system (besides citizens who can log in
online for viewing/updating some limited information). Out of the
2600 internal State users, approximately 2000 users will have
“inquiry only” access and about 600 will be able to
enter/update/modify information. The ‘highwater’ mark for the most
concurrent users in the last four years was 463 on July 25, 2016.
Question 22: Should the infra costs be included in the cost of the
solution? Q22 Response: Yes Question 23: Does the State have any
preferred cloud solution provider? Q23 Response: No.
Question 24: Has the State seen demos of any other vendors? Q24
Response: The state has not seen any Vendor demos. However, some
states were contacted for information during feasibility study,
please refer to Appendix I for details. Question 25: Do you have
any integration with external systems? If so, how many systems
integration required? Q25 Response: Yes, please review Section 1.1
- Functional Requirements for system integration needed for various
system functions/modules. The exact list of all interfaces will be
finalized during the project but the Function Description and the
graphics in Section 1.1 provides a good idea of all the key
interfaces expected in the new CCSES system. Question 26: How many
years of legacy data should be migrated to the new from existing
system? Q26 Response: All legacy data needs be converted to new
system. Any exceptions will be discussed during the project
execution phase. State is already analyzing the legacy data quality
and will do some cleansing prior to the start of the project so the
vendors can focus more on the data mapping and business rules to
convert the data. There will be some data issues/errors found
during conversion process and will need to be fixed by the vendor
during the project based on the results of mock and test
conversions.
Question 27: Will all users/functions require Web / Mobile /
Tablet accessibility? Q27 Response: Only some limited functions
will need to be available to citizens and business partners via the
web portal and mobile. Question 28: Please provide the number of
concurrent users? Q28 Response: Reference Q14 and Q21 responses for
user counts and number of concurrent users.
Question 29: Any specific choice of technologies to be used in
the proposed solution Q29 Response: The State does not prescribe a
specific technology or solution – we are looking for the best
solution and approach from the vendors.
Question 30: What is the State’s preferred reporting solution?
Q30 Response: Refer to the table on page 35 of RFP Document. State
is expecting the vendors to propose a reporting solution.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 5 of 25
Question 31: Does the state have common master data with other
IVA and IV E agencies? Q31 Response: State uses EMPI (Enterprise
Master Person Index) based on the NextGate platform to keep a
central repository of clients between some DSS systems. It is
envisioned that Child Support system will also be linked to this
system and EMPI will be used to create unique client IDs and
exchange client data between agencies like IV-A and IV-E. Question
32: How is the Total Cost of ownership common sized? - Should we
include infra costs in the Total cost of ownership estimate? If so
can the State provide the list of infra assets they have in place?
Q32 Response: Proposer to price all hardware and software
components for all environments.
Question 33: Go Live date? Do you prefer county wise go live
with full feature set or feature wise go live across the State? Q33
Response: Refer to Implementation Section 1.3.15 in the RFP
Document. Vendor to propose their recommended approach for a
successful implementation. Question 34: What is the budget of this
contract? Q34 Response: Reference Q1 response. Question 35: Who is
currently providing the M&O services for the current program? Q
35 Response: Auctor Corporation.
Question 36: In the TCO, if we assume an Early go live compared
to the estimated 40 months, should we reduce the M&O costs of
the current system? Q36 Response: No, State is looking for ten
years TCO as requested in cost proposal. Question 37: Can
Engineering and Configuration work be done off shore with the Data
not leaving the US soil? Q37 Response: Yes, however the Data can’t
leave the United States. Question 38: Does the State have license
for any data migration/ETL tool? Q38 Response: No Question 39: Has
the Agency had any contract with any other States where their
process and technology modernization may provide a blueprint for
your to-be CCSES model? Q39 Response: No Question 40: RFP says DDI
Proposer developed training material to deliver functional training
to the remaining State users. How many State staff members will be
needed to be trained? Q40 Response: Please refer to Section 1.3.13
TASK 13 – END USER TRAINING Question 41: With regard to Training
Will the agency manage the logistics associated with classroom
training (providing lab space and computers, enrolling users,
managing travel, etc.) or should the vendor plan to deliver those
services. Q41 Response: Yes, State will provide classroom
facilities for training and enroll users. For Travel to office
locations, State will only manage for State staff. Vendors will
manage their own travel.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 6 of 25
Question 42: How much time is the agency willing to allow to
fully train all users? Do you have a training interval in mind
(both before and after system go-live)? Q42 Response: Please refer
to Section 1.3.13 TASK 13 – END USER TRAINING and propose
accordingly. Question 43: Ref RFP page # 95: Can the Proposer have
a partner/subcontractor? (In the RFP does not mention about this
other than Staffing) Q43 Response: Yes, however, the awarded
Contractor will be responsible for their own proposal submission
and will be responsible manage the Contract and lead the project to
a successful implementation. Question 44: What are the different
types of users (e.g., citizens, business partners, employees,
administrators etc.) and what are the user counts respectively Q44
Response: There will be a total of about 2600 users who will have
access to the system (besides citizens who can log in online for
viewing/updating some limited information). Out of the 2600
internal State users, about 2000 will have inquiry only access and
about 600 will be able to enter/update/modify information. The
different types of users are – Employees of OCSS/SES, other agency
(IV-A, CT Care for Kids, DSS Auditors, ITS), Help Desk and
Administrators. Question 45: Is Agency going to support multi
browsers? If yes, what are all the browsers that need to be
considered for Browser Compatibility testing? Q45 Response:
Internal State Users will only use one browser as approved by State
(refer Appendix F). Citizen-facing functionality (portal and
mobile) will be browser independent. Question 46: Do all referrals
have the same format and data type irrespective of sources of case
initiation (e.g. TANF, Medicaid, Child Welfare, CT Judicial
Department and others)? Q46 Response:
1) Referrals from TANF and Medicaid are in the same electronic
format – a file of new referrals, updates, and closures is created
during their nightly batch processing window. The file is
transmitted from the statewide eligibility system to CCSES via a
managed file transfer. Hard copy supporting documents may be routed
from the eligibility workers to the child support unit as
needed.
2) Referrals from sister states for action under UIFSA may be
received by CSENet and US Mail 3) Non-IV-D cases are received as
paper referrals by mail or in person. 4) In person applications are
paper based.
Question 47: What is the format and layout of referrals that the
Department currently receives from other sources? (does it include
only data, paper documents/files, or combination of data and
documents) Q47 Response: The agency receives electronic referrals
from two sources – in state TANF and Medicaid (including ‘inferred’
Foster Care cases) from the agency’s integrated eligibility system
(ImpaCT). Interstate cases may be received electronically via the
CSENet interface. The CSENet formats are promulgated by the federal
Office of Child Support Enforcement. The referrals from the
integrated eligibility system follow the same format regardless of
program type. See Attached Document to this RFP Addendum 3 for
various record layouts used in the Eligibility to Child Support
interfaces. The file layouts are provided for illustration purposes
only and should not be considered authoritative. Question 48: What
is the average daily number and frequency of new referrals that the
Department receives? Q48 Response: For the five year period ended
5/31/2019 a total of 32,085, and based upon 249 work days a year,
the agency has received approximately 26 referrals per day. Support
Enforcement Services averages 4 new interstate referrals and 4
status updates per work day.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 7 of 25
Question 49: What is a typical number of documents per case? How
many of them are generated by the system throughout the process and
how many originate from the source/recipient? Q49 Response: The
number of documents depends on the type of data that is being
entered or updated. At the time of case initiation, there are some
documents which are needed for verification that will need to be
scanned as part of the case setup. As the case flows through
various stages, there are several notices and forms generated by
the system based on business rules. Question 50: How many external
systems would interface with the new CCSES system in total? Q50
Response: Reference Q25 response. Question 51: What is the current
Interactive Voice Response (IVR) platform? Does the Department plan
to replace the existing contact center/IVR platform with the new
one? If it does, is it in the scope of this RFP? What would be the
preferred IVR platform in that case? Q51 Response: The Department
is in the process of reviewing the feasibility of replacing the
current IVR system. The replacement of the IVR system is not in the
scope for the vendor. Setup of the IVR menu system and integration
with the new CCSES system for it to provide real time information
to the customers is in scope for the DDI vendor. Question 52: If
the contact center platform/IVR will remain the same, what
Application Programming Interface (API) is exposed by the platform?
Q52 Response: Please reference Q51 response, the IVR system
software can consume SOAP and RESTFul web services. Question 53: In
reference to the following: “Prior experience in delivering Child
Support Enforcement systems would be desirable.” Would a
subcontractor’s past performance in delivering Child Support
Enforcement systems be acceptable? Q53 Response: Yes. The
Department would however expect key team members to have relevant
experience in implementing similar large public sector projects,
preferably Child Support. Question 54: We recommend that the State
request demonstrations of proposed solutions. Q54 Response: Please
see RFP Document page 91 – Proposer Requirements Question 55: We
recommend that a FedRAMP approved environment be mandatory. Q55
Response: For Cloud Solutions, FedRAMP is a requirement that needs
to be met by the Vendor, as specified on Page 8, 19 and 35 of the
RFP Document. Question 56: On page 9 of the solicitation under
“Business Goals and Objectives” there is a mention of dual agency
arrangement. Can we have more information on this arrangement as it
pertains to the solicitation? Q56 Response: As specified on page 12
of the RFP Document, The Child Support/IV-D Program is administered
by the Department of Social Services, Office of Child Support
Services (OCSS) which works closely with the Support Enforcement
Services (SES), Judicial Branch, through a cooperative agreement.
SES is responsible for court-based enforcement and most order
modification processes. Briefly, the Case Establishment/Management,
Locate and Financials are handled by the OCSS and SES is
responsible for all Enforcements. There are users from both offices
that will use the new system.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 8 of 25
Question 57: For data migration – what is the volume of data in
the existing system (database, FileNet and Sharepoint) that needs
to be migrated to the new CCSES platform? Q57 Response: Data will
only be migrated from the CCSES UniVerse application. In the
UniVerse DBMS data are stored in files rather than tables. The
CCSES application has some 626 files. Many of these files are parts
of a whole. For example, the file for receipts may be viewed as one
monolithic file, or as 31 sub files. Therefore, the receipts alone
account for 32 of the 626 referenced files. There is approximately
300gb of data as measured by disk usage. Question 58: Where does
the Department’s Enterprise Master Person Index (EMPI) first
mentioned on page 21 reside – is it maintained in a database – if
so, what database is used? Q58 Response: EMPI platform and database
resides in CT State Data Center, hosted by the BEST and supported
by NextGate. www.nextgate.com. Question 59: The “Key Interfaces”
depicted in Figure 3 on page 22 – are these bi-directional or
uni-directional – How is it interfaced today – SOA, data exchanges
through an enterprise bus or simple data import-export? Q59
Response: Some interfaces are unidirectional (sending or receiving
information) and some are bi-directional based on the function
being performed. Most of the interfaces today are point to point
and use batch exchange of data. Though the State has an ESB, it is
not being used by CCSES today. State is looking for the interfaces
to be re-engineered using web services, where possible, and use of
an integration engine that will make It easier to maintain the
interfaces in future. DDI vendor will lead the design for all the
interfaces during the project. State has licenses for Pilotfish
which can be provided to the vendors if that is the solution
recommended. Question 60: For Financial Management and payment
processing – does the state use any preferred payment gateway like
Pay.gov? Q60 Response: All payments are currently handled through
State Disbursement Unit. Question 61: Is there an existing
Interactive Voice Response solution in use today at the State of CT
or is the vendor expected to provide IVR options as part of the
proposed solution? Q61 Response: Reference Q51 response. Question
62: Can the State provide a list of imaging hardware (scanners) in
use today that is expected to be integrated into the CCSES? Q62
Response: Each office has multifunction devices with scanning
capability. As of this writing they are primarily Toshiba eStudio
devices. Question 63: How many named users will be using the new
CCSES platform? How are these distributed – staff, registered
users, guests? Q63 Response: Reference Q14 and Q21 responses.
Question 64: What are the State’s data retention policies? Q64
Response: Standard retention requirements are established by the
State Librarian. Schedule S6 pertains to Information Systems
Records (See
https://ctstatelibrary.org/wp-content/uploads/2018/02/S6-Information-Systems-2010.12.pdf)
http://www.nextgate.com/https://ctstatelibrary.org/wp-content/uploads/2018/02/S6-Information-Systems-2010.12.pdfhttps://ctstatelibrary.org/wp-content/uploads/2018/02/S6-Information-Systems-2010.12.pdf
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 9 of 25
Question 65: Is the new CCSES platform expected to support
internationalization and Section 508 compliance? Q65 Response: Yes,
the system needs to be ADA (section 508) compliant.
Internationalization – if the question pertains to maintaining
international addresses, the system needs to take care of that.
Question 66: Could we assume that the vendor(s) and their
sub-contractors who participated in developing the feasibility
study will be precluded from bidding as a prime or a subcontractor
to another for this solicitation? Q66 Response: Yes. Question 67:
On page 95 of the RFP Document, RFP Section 5, Business Information
states, “Should proposers wish this information to be considered
confidential, proposers should mark this information as
“Confidential”. Any “Confidential” information will not be made
available to the public and will only be reviewed by the evaluation
committee.)” We assume that this protocol be followed for any
sections considered to contain information that is nonpublic,
confidential, proprietary and/or trade secret information. Is this
a correct assumption? Q67 Response: Yes, only proposal information
that is truly nonpublic, confidential, and proprietary and/or a
trade secret information can be considered confidential
information. Please note that project pricing is not considered
confidential and the entirety of the proposal document can’t be
marked as “Confidential”. For further information, please reference
contract language requirements in Attachment 1 – Sample Contract,
Section 35 Public Records and FOIA for further information on the
State’s obligation under the Freedom of Information Act. Question
68: Instruction to Proposers – Proposal Schedule What are the
tentative award date and start date of the project? If these are
unknown, can OCSS suggest a tentative start date vendor should use
for the preliminary project plan to be submitted with the RFP
response? Q68 Response: Assume a tentative start date of Mar 1,
2020. Project Plan can also be prepared using generic Month 1,
Month 2 to show a relative schedule of tasks and deliverables.
Question 69: Section 1.1.11 Document Management (Scanning and
Document Generation) Do you currently use any central or
distributed capture tools, such as Datacap, to scan inbound
documents? Q69 Response: No. Vendor to propose their capture and
document management solution. Question 70: Section 1.1.12 –
Workflow Management & Business Rules Engine Will the State
consider the workflow management functionality used by the New
Jersey child support system or is the State looking to replace
workflow management using a BPMN engine? Q70 Response: State is
open to all options and the best solution that meets the
requirement. State is not prescribing a solution. The requirement
as specified in the RFP is for a scalable, flexible solution that
is user friendly, easy to maintain and uses a platform that will
last for the next few decades. Question 71: Section 1.1.12 –
Workflow Management & Business Rules Engine Will the State
consider the table-driven rules management coded within the New
Jersey child support application that fulfills all requirements or
will the State exclusively consider the integration of a Business
Rules Management Engine? Q71 Response: The requirement is for the
business rules to be abstracted thereby providing more flexibility
and improved maintainability of business rules by the Department
staff.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 10 of 25
Question 72: Section 1.1.13 – Quality Control If a vendor offers
a dashboard that it believes meets the state’s functionality and
configurability needs for the desired Quality Control Dashboard but
also includes other features, is that sufficient to meet the
requirement in section 1.1.13 Quality Control at the top of page 32
of the RFP? Or does the state firmly require a separate Quality
Control Dashboard? Q72 Response: Vendor to recommend the best
solution for this requirement. Requirement is for the Agency
Quality Control staff to view case data, events in case history,
statistics on performance etc. as described in that section.
Question 73: Section 1.2.2 – Web Portal and Mobile application
During the initial phase of the project would the State consider a
mobile application that supports all of the requirements for the
customer portal accessible in phones and tablets? Or will the State
require a separate Windows-based customer portal in addition to the
mobile application? Q73 Response: The State expects the Vendors to
recommend the best solution/approach for web portal and mobile
application. Question 74: Section 1.3.1 – Office space for core
team member -- State Facilities for vendors
I. What are the available access hours to the State’s
facilities? II. Will the facilities be available during
after-hours, weekends, and holidays?
III. What are the requirements for the vendor’s staff to obtain
access (e.g., access cards, user accounts, etc.)? Are there
conference rooms available to the vendor staff?
IV. How many people can be accommodated? Are there projectors
and WiFi available? V. What is the available LAN bandwidth in the
facilities available to the vendor (e.g., 100Mb, 1000Mb)?
Q74 Response: I. The facilities will be available during
standard working hours.
II. Availability for after-hours and weekends will be based on
the needs of the project. III. DSS will be responsible for
obtaining vendor access cards and user accounts. Conference rooms
are available
by reservation. IV. There will be sufficient space for up to 25
staff. Projectors are not available as of this response. Wifi is
not
available as of this writing. V. Bandwidth is 100 Mbps
Question 75: Section 1.3.1 – Office space for core team member
-- State Facilities for vendors -- Network
I. How many ports are available for each office space? II. Will
phones be available?
III. Will WiFi be available and if so, at what speed? IV. What
are the existing connection speeds to the internet? V. Are
connections to the internet with or without proxy?
VI. Will the vendor have the ability to establish VPN
connections to their headquarters? VII. What is the available
bandwidth for the vendor-designated area to the state’s data
center?
VIII. What are the requirements for the vendor to connect to the
State’s network (e.g.., anti-virus software, operating system patch
management, etc.)?
Q75 Response: I. To be determined
II. Yes III. No IV. 100 Mbps
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 11 of 25
V. Filtered, no proxy configuration required to PCs VI. Yes,
either branch to branch VPNs or individual VPN access using Cisco
AnyConnect are supported.
VII. To be determined VIII. Vendor will need to follow state
policies, will be provided to the selected vendor Question 76:
Section 1.2.1 Conceptual Technical Architecture of the new CCSES
System – Service Oriented Architecture (SOA) & Requirement
#1.1.9 -- Requirement Matrix Page 35 of the RFP document states
that "The system must be designed using a Service Oriented
Architecture (SOA)." and requirement number 1.9.1 from the
requirement matrix states that "The system must use an integration
engine to automate the interfaces using a SOA based architecture,
where possible." Will OCSS consider microservices architecture? Q76
Response: State is open to all options - Vendor to recommend the
best approach/solution. Microservices architecture is a variant of
SOA architecture and if that is the recommendation, the Vendor
should provide information on how it will be designed, implemented,
rolled out, and maintained including benefits to the State.
Question 77: Section 1.2.2 Conceptual Architecture of the new CCSES
System Is PilotFish the preferred platform for enterprise
integration? Q77 Response: Yes, PilotFish is preferred but the
State is open to other solutions too. State currently owns
perpetual enterprise licenses for PilotFish, so there is no
licensing cost to use PilotFish. Question 78: Section 1.2.2 –
Document Generation -- Document Capture/Scanning Do you currently
use any central or distributed capture tools, such as IBM’s
Datacap, to scan inbound documents? Q78 Response: No, Child Support
is not using integrated document capture and generation tools
currently. Most of the documents generated use a manual process
with little automation. Question 79: Section 1.2.2.2 – Technical
Requirements – Document Generation On page 35 of the RFP, it states
that "Child Support currently uses PlanetPress, but the Department
is open to other solutions. As Adobe Experience Manager (AEM) is
listed as an emerging standard, do you anticipate any issues
migrating from PlanetPress to AEM? Does OCSS have any preference
between PlanetPress and Adobe Experience Manager? Q79 Response: As
stated in the RFP, Vendors to propose the best solution for an
integrated document generation that meets the State needs. However,
DSS and SES has experienced form designers who work on PlanetPress
to create and maintain form templates and the PlanetPress solution
can be integrated with other solutions. Question 80: Section
1.2.2.2 – Technical Requirements – Application Lifecycle Management
Tools Will the State consider the use of Atlassian tools such as
Jira, Bitbucket, and Confluence to handle the application lifecycle
management (ALM)? Q80 Response: Department does not have a
preference and is open to the best solution for ALM. Question 81:
Section 1.2.2.2 – Technical Requirements - Database Does the State
have a preference between SQL Server, Oracle, and DB2? Will the
licensing cost be a determining factor in your final selection? Q81
Response: No, there is no preference. Department wants the best
overall solution and value. Question 82: Section 1.2.2.2 –
Technical Requirements -Commercial cloud vs. Gov cloud Do you have
any sensitive data that requires the use of Gov Cloud instead of a
FedRAMP authorized commercial cloud? Q82 Response: As specified,
the requirement is for a FedRAMP certified cloud solution.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 12 of 25
Question 83: Section 1.2.2.2 – Mobile Applications What is the
vision behind mobile application development? Do we need to use
frameworks, such as Xamarin, PhoneGap, or ReactNative to develop
code once and deploy on multiple OS? Or does the Mobile app need to
be developed in native code for Android and IOS? Is OCSS expecting
clients to submit new applications via mobile devices? Should the
mobile app have the ability to support direct and recurring
payments through credit/debit cards? If the mobile app needs to
support direct payments, please provide the list of current
payments providers currently under contract with the State. Do you
have any statistics currently available for the web site which
depict device types used to access the current web site, (i.e.
Desktops/PC’s running Windows, Mac or Linux, Mobile devices running
Android or IOS) Q83 Response: Develop once and deploy on all OS
(Progressive App preferable). Clients should be able to submit new
applications online. They may still need to come into the office to
complete their case related paperwork and get their documents
verified. All payments for Child Support are handled/processed
through the State Disbursement Unit that sends the information to
CCSES system for tracking. Child Support is not using a web portal
or mobile app currently in the existing legacy system. Question 84:
Section 1.3 – Project Tasks and Deliverables – Source Code Page 41
of the RFP states that The Department should own all the
deliverable, working products, and program/applications source
code. Outside of the core child support application, is the State’s
intention to also own the source code of third-party applications
(e.g., customer service portal and mobile applications)? Is the
State open to evaluating a perpetual licensing model if it would
results in both short and long term cost savings? Is the State
interested in entertaining SaaS (Software As A Service) solutions
to reduce the Total Cost of Ownership of the mobile app and
customer facing services? Q84 Response: The State’s intention is
not to own source code for 3rd party applications and licensed
software platforms. Department will own the
code/configurations/customizations using those platforms.
Department is open to all options and the best solution from the
vendors that meets the requirement and reduces the total cost of
ownership. Question 85: Section 1.3.6 – Assessments and
specifications
I. Can you provide details on the existing CCSES core network
hardware? II. Can you provide details on the existing hardware for
core and parameter firewalls?
III. How many ports are available or reserved for the new
infrastructure? IV. Can you provide more details on the existing
backup equipment and solution? V. Is there currently any network
connectivity from the data center to a cloud service provider?
Q85 Response: Vendors to assume that the On-Premise Networking,
Firewalls and any other State supported systems that would interact
with the new CCSES solution will be the State’s responsibility.
Vendor will work with State IT to ensure that the new solution will
work with the State networking environment. The details will be
shared with the selected vendor. Question 86: Section 1.3.9 Task 9
– Data Conversion and Migration - ETL tool Can you please confirm
if SAP data services are in use for ETL (Extract, Transform and
Load) and data quality jobs? Q86 Response: No.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 13 of 25
Question 87: Section 1.3.10 Task 10 – Construction (Development)
-- Batch Scheduler Do you currently use any batch scheduling
software, such as CA Workload automation? Q87 Response: The current
system makes use of both cron at the Linux level and schedulers and
job orchestration facilities that are organic and peculiar to the
CCSES application. Question 88: Section 1.3.10 Task 10 –
Construction (Development) -- Backups Should the State opt for a
cloud-based solution, what would the OCSS’ preferred backup
location (i.e., State's data center, backup cloud provider, or on
the same cloud provider)? For example, if AWS is selected as
primary, backups can be stored on the State's data center or
Microsoft's Azure cloud. Q88 Response: Vendor to recommend the best
approach with pros and cons. Question 89: Section 1.3.9 - Data
Conversion and Migration
I. During conversion, can we make up dummy dependents records if
the case is missing dependents? II. If cases with arrears are in
inappropriate buckets, can the conversion program automatically
move the funds to
the correct buckets (e.g., Never Assistance with PA arrears the
arrears will moved to the NA Arrears bucket)? III. How does the
State expect TANF cases to be converted if the grant amount is
missing? IV. Is there any existing process for member merge? What
is it?
Q89 Response: Selected vendor to work out the details of data
mapping, data cleanup and conversion during the project. Question
90: Section 1.3.9 - Data Conversion and Migration Strategy
I. Will the State make available actual full production data to
assist in pre-conversion activities? With the appropriate security
mechanisms, can this data be exported to the new conversion
environment?
II. How many external systems currently in place and outside of
CCSES would be required for conversion? Can you name these external
systems (e.g., Attorneys, Judges, Courtroom locations,
laboratories, etc.)?
III. What is the State’s preference for the rollout schedule?
Big bang or by region? IV. Conversion activities will require s
system downtime, which will be maintained at the minimum possible
levels.
Does the State have any constraints that would set a hard limit
to this timeframe? V. Is the State planning to keep the legacy
system in read-only mode for the regions that have converted to
the
new system? For how long? Q90 Response: Selected vendor to work
out the details of data mapping, cleanup and conversion during the
project. Vendor can make appropriate assumptions based on their
experience with similar projects. There are no external systems for
conversion – only CCSES data needs to be converted. Payments cannot
be impacted due to down-time. Yes, the State is planning to keep
the legacy data in read mode. Question 91: Section 1.3.9 -- Data
Conversion and Migration Management Plan
I. What is the State’s expectations regarding the conversion of
historical financial transactions? II. Does CCSES currently have
archival procedures for unused records? What are the archival
procedures and
policies in place? III. Does CCSES allow a case type to change
from Non-TANF to IVE or vice-versa? IV. Does CCSES have skeletal
cases (case records that were initiated but the case creation
process was never
completed (i.e., incomplete data)? If yes, what is the
expectation for converting incomplete cases? V. Does CCSES have an
expected success rate for cases to be converted?
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 14 of 25
Q91 Response: Selected vendor to work out the details of data
mapping, cleaning and conversion during the project. Question 92:
Section 1.3.13 – End User Training Does the Department have a
Learning Management System (LMS) they use for their web-based
training? Q92 Response: Yes, DSS uses the SABA learning enterprise
software for a learning management. Web based training is developed
in Articulate Storyline V3 and launched through the DSSLearnCenter.
Question 93: Section 1.5 – Key Staff Is the Test Manager required
to have 15+ years of experience in training? Q93 Response: Please
read this as “15+ years of managing and delivering Testing of
large, complex systems preferably Child Support”. Question 94:
Appendix A – Requirements Matrix – Requirement #1.12.7 - Backups
The requirement states that “Current product is VEEM”. Please
confirm that this refers to the VEEAM product
(https://www.veeam.com/)? If so, does state have any long term
contract with VEEAM backup and recovery product? Will the State
consider other options? Q94 Response: We apologize for the
typographical error. The current backup solution is indeed VEEAM.
There is no long term contract. The agency will consider other
options Question 95: Appendix A – Requirements Matrix - Requirement
#5.5.1 – Translations
I. Does state have any restrictions on using external APIs, such
as Google translate, Twillio, etc.? II. Can this data be sent
outside of the OCSS and cloud infrastructure for translation? For
example, to translate a
document from Spanish to English, CCSES application needs to
send Spanish text to Google API over a secure channel. Then the
Google API will process and return English text back to the CCSES
Application.
III. Can you describe the format of the original documents
(e.g., word documents, emails, and .pdf? Q95 Response: This
requires further research. The Agency is responsible for obtaining
approved translations of document templates that are used for
outbound notices etc., however, the ask here is for the ability to
translate inbound documents. Question 96: Appendix A – Requirements
Matrix – Requirement 1.2.1; 11.3.8, 11.4.4 SMS messages - What is
the anticipated volume of SMS and push notifications per month? Q96
Response: Initially the number may not be high, but the Department
would like to use this as the preferred option to communicate with
most customers. It is anticipated that the volume will ramp up over
time. Question 97: Appendix A – Requirements Matrix - Requirement
#1.13.8 – Portals Requirement 1.13.8 states that "Capability for
reuse of existing "portal" technologies, if needed, combined with
any new proposed portal solution." Please provide details on portal
technologies currently in use in CT. Q97 Response: State is
exploring the use of progressive app that can be used across
different mobile devices and as a web portal. Vendor to propose
their solution and the State will work with the selected vendor to
finalize the best option for mobile app and web portal. Question
98: Appendix A – Requirements Matrix - Requirement #11.2.12 Fax
Server - Do you envision the need to send or receive documents via
Fax? If yes, do you have a fax server software in place? Q98
Response: No – Fax Server/software is not in place currently. State
has a Fax machine.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 15 of 25
Question 99: Appendix A – Requirements Matrix - Requirement
#5.6.1 Does the State have the means to store court recording? If
yes, where are they stored? Can the new system interface with that
repository? Q99 Response: This requirement does not pertain to
court recording. It is for the State to take automatic actions
based on business rules and record those actions taken by the
system. Any changes to the case needs to be tracked to be able to
view the case history/chronology. Question 100: Appendix F - CT-DSS
Technology Catalog -- IBM Qradar and Splunk. There is an overlap
between these products for log management. Can the State provide
specifics on how you are using them currently and the purpose of
each product in the context of CCSES? Q100 Response: These are the
tools used today by different agencies for logging any
events/exceptions and producing reports/dashboard for continuous
monitoring of the platforms. These tools are not used for CCSES
today. State is not prescribing a solution and is looking for the
best solution and approach from the vendors. Question 101: Appendix
F - CT-DSS Technology Catalog – Customer Relationship Management
Since Salesforce is in the watch list for CRM, does OCSS prefer to
build the customer portal using Salesforce, or would the State be
open to reusing existing solutions for CCSES? Q101 Response: The
state is not prescribing a certain solution and is looking for the
best approach and solution from the vendors. Question 102: Appendix
F - CT-DSS Technology Catalog – Business Intelligence – Zato Health
Interoperability and SAP Both Zato Health Interoperability Platform
and SAP Business Objects and SAP Business Objects are mentioned
under the category of Analytics. Can you provide details on how
Zato Health platform used for Analytics? Do you envision the need
for both products on analytics, or do you anticipate delivering
entire analytics on one platform for the new CCSES? Q102 Response:
One platform. Subsequent to the creation of Appendix F, the Agency
has added Tableau to the list of standards for reporting and
analytics. The state is not prescribing a certain solution and is
looking for the best approach and solution from the vendors.
Question 103: Appendix F - CT-DSS Technology Catalog – Enterprise
Document Generation Is Adobe Livecycle ES4 used by OCSS, SES or any
other department or divisions in CT? What types of documents are
produced with Adobe LiveCycle ES4? Q103 Response: Adobe Livecycle
is used by other systems/agencies within DSS. The current child
support system uses PlanetPress Suite from ObjectifLune
(PlanetPress Design and Office Flow,
https://planetpress.objectiflune.com/en/suite) for both OCSS and
SES forms, court documents, and notices. The state is not
prescribing a certain solution though and is looking for the best
approach and solution from the vendors. Question 104: Appendix G –
CT DSS Enterprise Architecture Principles - Cloud vs. On-premise As
per the enterprise architecture principle BP-007, DSS preferred
option is cloud. What is OCSS’s preferred alternative for the new
CCSES system between Cloud vs. On-premise? Q104 Response: Cloud.
Question 105: Appendix G – CT DSS Enterprise Architecture
Principles - Cloud Service Provider Do you have a preferred cloud
provider (CSP)? (Ex: AWS, Azure, etc.) Are other DSS application
hosted on the cloud? If yes, who is the cloud service provider?
Q105 Response: No. The state is not prescribing a certain solution
and is looking for the best approach and solution from the
vendors.
https://planetpress.objectiflune.com/en/suite
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 16 of 25
Question 106: In Section 1.1.11 (Document Management), Scanning
Operation – Will scanning take place on a “go-forward” basis or
will legacy document scanning be required? If so, what is the
approximate volume of legacy scanning? Q106 Response: Go Forward
only. Vendors may need to convert some (low number) of the case
related pdf documents and associate them with the existing cases.
Question 107: What is the current size of database footprint
(Current number of Databases, Tables, Size)? How far back is legacy
data planned to be kept? Q107 Response: Reference Q57 response.
Question 108: What is the approximate number of named users that
will be using the system both within the agency and across the
state? Q108 Response: Reference Q14 and Q21 responses. Question
109: What is the expected deliverable – SOW or Binding Proposal, or
both? Q109 Response: The expected deliverable will be both the SOW
and Contract Documents. Question 110: How many offices and internal
users of the system will there be? Q110 Response: For number of
users reference Q14 and Q21 responses. Vendors should plan their
solution assuming 24 offices in the State - Refer to page 71 of the
RFP Document. Question 111: What rollout plan do you envision – a
big bang single-cutover, or slower rollout with current system in
parallel with new system until all offices/users are migrated? Q111
Response: Vendor to recommend the best approach for a successful
implementation with reduced risk. Question 112: Can you provide
information about data volume? (total current database size,
breakdown of database size for documents (and are they stored in
current database or another document management system), and can
you provide top tables utilized, with row counts? Q112 Response:
Reference Q57 response. Question 113: In Section 3.1.6 – The System
must provide a Quick interface that exchanges all available data.
Can you be more specific about the requirement? Does this refer to
the Service Bus requirement listed in the Solution Architecture?
Q113 Response: QUICK is a federal interface that allows States to
share/exchange data in intergovernmental cases. Please click on
this link for more details on QUICK.
https://www.acf.hhs.gov/css/resource/about-quick Question 114: In
Section 8.15.3 – The system shall backup all created reports to
storage. Often times, a generated report output isn’t saved to
storage. However, the report can be generated again at will based
on the same criteria. Does saving the report definition (but not
the generated report) satisfy this requirement? Q114 Response:
State needs to save some reports as a point in time document.
Question 115:
I. Do you have a current IVR today? Which company provides your
phone switch? II. Do you have a current chat provider?
III. Who provides your credit card payment processing today? IV.
Do you have an electronic document signature provider today? V. Are
the technologies listed in the Standard Box in Appendix F the
existing assets the State wants the vendors to
leverage in the new CCWIS system per the Hybrid approach? If
not, what are the existing technologies the State wants
leveraged?
https://www.acf.hhs.gov/css/resource/about-quick
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 17 of 25
Q115 Response: I. There is an IVR in use – it is based on the
Avaya platform – The State is currently in the process of
upgrading
this and the vendors will need to interface with it. II. State
does not have a chat provider – State is looking for a solution for
this III. All payment processing functions are provided by the
State Disbursement Unit. The CCSES system just
needs to keep track of the financials linked to the customers
and the case, based on information sent by the SDU.
IV. Department does not have an electronic signature provider V.
Appendix F lists the DSS standard technologies and may be in use in
other agencies within DSS. Child
Support Agency does not have licenses to any of these
technologies and is open to the vendors using these (if they are
the right solution) or any other technology options. The vendors
will leverage State’s networking infrastructure and firewalls.
State’s Security system for authentication is IBM ISIM/ISAM – that
can be leveraged, if needed, by the vendor. Also, State has
licenses for an integration engine (Pilotfish) that can be provided
to the vendor, if needed. Other than that, Vendors should propose
their best solution and approach for the new system.
Question 116: In Section 2.7.1 – The system must accommodate
collecting detailed occupation information to allow correct
application of guidelines and correct current ability to pay data.
Final Rule Jan 2017. What are the guidelines/data sources that
State is using to determine current ability to pay? Q116 Response:
State will discuss the details of this requirement with the
selected vendor. Question 117: In Section 15.1.2, Identifying cases
potentially eligible for Fatherhood services and automatically
taking the next case action, such as notification generation,
invoking a workflow to automatically track the next action which
may include notifying the staff member, and including actions in
the case record and on reports. What is the criteria the state is
using for eligibility for Fatherhood Services? Q117 Response:
Anyone who is interested in accessing Fatherhood Services would be
automatically referred to a fatherhood program site closest to
their location and that referral would be the warm handoff to the
program site. Those referrals to the fatherhood sites would then be
tracked in the system. If a referral could not be made because
there is no such program in the immediate area then State would be
able to track that information as well to assist in making a case
for program expansion. State also wants to track if a parent is
interested/not interested in the Fatherhood services and the reason
why they were not interested. Question 118: On page 6 in the
Overview Section of the RFP Document - Are there examples of each
of the standard reports (OCSE, IRS, balance, claims)? Q118
Response: Formats of all the reports will be provided and finalized
during the project. Question 119: On page 6 in the Overview Section
of the RFP Document - What are the interface specifications to the
other agencies and financial institutions? Q119 Response: Reference
Q59 response.
Question 120: On page 6 in the Overview Section of the RFP
Document - Do parents / 3rd parties already have login credentials?
If so, in what mechanism? Q120 Response: No, Child Support does not
have a web portal for self-service today.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 18 of 25
Question 121: On page 6 in the Overview Section of the RFP
Document - Are there examples of the federal / state interfaces for
data sources? Q121 Response: Key Federal and State interfaces are
mentioned throughout the RFP document in relevant sections that
describe the functional requirements. They are also in the Appendix
A – Requirements Matrix and are described in Appendix E - Federal
Guide to States.
Question 122: On page 7 in the Overview Section of the RFP
Document - What are the metrics which define the ranking of the
Child Support programs to measure if it is in the top 5 in the
country? Q122 Response: There are Performance Measures established
by the Federal Office of Child Support (OCSE):
1. CSE Paternity Establishment 2. CSE Order Establishment 3.
Child Support Collections 4. Child Support Arrearage 5. Cost
Effectiveness
Question 123: On page 7 in the Overview Section of the RFP
Document - What is the technology of the current system? Q123
Response: The legacy system is an older Unix-based, monolithic
character-based application using an older UniVerse multivalued
database system, currently at version 11.2.5 (See
https://www.rocketsoftware.com/products/rocket-universe-0 )
Programs are written in UniVerse Basic. See
https://docs.rocketsoftware.com/nxt/gateway.dll?f=templates$fn=default.htm
for the Rocket Software’s UniVerse System Description manual.
Question 124: In Section 1.1.1 on page 22 of the RFP Document -
Do metrics and measures already exist for the Key Outcomes? (Same
question for all Section 1.1.X Key Outcomes) Q124 Response: No –
The State anticipates that the vendor, using their experience in
similar projects, will show how these key outcomes will be met.
Question 125: In Section 1.2.2.2 on page 37 of the RFP Document -
What are the expected capacity requirements for concurrent users
during peak business hours, split by internal and external? Q125
Response: It is anticipated that capacity planning will be
finalized, completed and approved as a deliverable during the
project prior to ordering or subscribing the hardware and
software.
Question 126: In Section 1.2.2.2 on page 37 of the RFP Document
- What are the current business process response times? Q126
Response: The Department is happy with the response times of the
current system. It is anticipated that the new system will be able
either match or better the response times of the current
system.
Question 127: In Section 1.2.2.2 on page 38 of the RFP Document
– What are the minimum and maximum screen sizes to be supported?
Q127 Response: State is looking for a responsive app that will
support all popular screen sizes.
https://www.rocketsoftware.com/products/rocket-universe-0https://docs.rocketsoftware.com/nxt/gateway.dll?f=templates$fn=default.htm
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 19 of 25
Question 128: In Section 1.2.2.2 on page 38 of the RFP Document
- What versions of Android and iOS need to be supported? Q128
Response: Latest versions and 1-2 previous versions to be
supported. State understands the complexity of managing software on
different versions and will be reasonable in their approach. This
will be finalized during the design phase of the project.
Question 129: In Section 1.3.14 on page 74 of the RFP Document -
What are the skill sets and number of people who will receive the
technical training and knowledge transfer? Q129 Response: The State
staff will have basic skills in the technology platform. Number of
people will be finalized based on the solution.
Question 130: On page 95 of Appendix E - In the cases where the
state moves historical information offline, do federal auditors
still require access to the offline location of this information?
Q130 Response: Per the guide, auditors will require access.
Question 131: On page 49 of Appendix I - Does the state have any
currently ongoing efforts to make historical documents available
online? Is there a mandated timeframe by which this activity must
be completed? Q131 Response: No, this is not an initiative that the
State is pursuing currently.
Question 132: On page 50 of Appendix I - Is the Judicial filing
system modernized appropriately to handle the desired integration?
Q132 Response: This is a requirement and the details will be
discussed with the selected vendor. Question 133: Attachment 1 –
Sample Contract Document - Please confirm the contract (sample) can
be revised by the vendor to include proposed revisions which can be
negotiated during the award process accordingly. Q133 Response: At
this time that is not necessary, the Sample Contract Document is
not a required returnable document, this is only a sample Contract
Document that contains our Standard Contract Language Terms and
Conditions. Question 134: Will the RFP be awarded to multiple
vendors? If so how many multiple vendors will be awarded? Q134
Response: Unknown, need to review and evaluate all proposal
responses. RFP Document states that DAS may award by individual
item, group of items, or the entirety of all items. DAS may reject
any and all RFP’s in whole or in part, and waive minor
irregularities and omissions if the best interest of the state will
be served. Question 135: Please confirm we can team with additional
solution partner firms to be part of our proposal response of which
will be subcontractors to the Proposer is we will be the prime
vendor if we are awarded the bid.
Q135 Response: Reference Sample Contract Section 33 which
requires Chief Information Officer SubContract Approval
language:
In accordance with Conn. Gen. Stat. § 4d-32, the Contractor
shall not award a subcontract for work under this Contract without
having first obtained the written approval of the Chief Information
Officer of the Department of Administrative Services or their
designee of the selection of the subcontractor and of the
provisions of the subcontract. The Contractor shall deliver a copy
of each executed subcontract or amendment to the subcontract to the
Chief Information Officer, who shall maintain the subcontract or
amendment as a public record, as defined in Conn. Gen. Stat. §
1-200.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 20 of 25
The Prime Vendor is responsible for the RFP proposal response
submission and if awarded onto contract award will be the one named
on the Contract and are responsible for approval for any
subcontractors working on their behalf. Question 136: Can we also
include references, qualifications and credentials from our team
partners (sub cons) for the proposal response? Q136 Response:
Reference Q135 response, please only submit references for the
proposer submitting the proposal response. Question 137: Is there a
requirement to include a minority/women owned firm in our proposal
response? Q137 Response: No, but if a company is a Connecticut
Certified Small / Minority Business, please provide proof of the
certification within the Submittal Requirement Section for the
Business Information proposal response. Question 138: On page 29 of
the RFP Document, Section 1.1.9 Customer Relationship – Self
Service RFP Requirement Question - Is the self-service portal
intended for non-custodial parents only? Q138 Response: No, any
client with a secure account should be able to view information.
Question 139: On page 30 of the RFP Document, Section 1.1.10
Security – RFP Requirement Question: “The State intends to leverage
its existing IBM Security Identity Manager / Security Access
Manager (SIM/SAM) identity and access management solution” - We
assume that this applies to the internal state agencies, partners’
/ employers users as well external self-services portal users.
Please confirm. Q139 Response: Yes. Though the State uses IBM
ISIM/ISAM solution for authentication, we are open to other
solutions too. Question 140: On page 30 of the RFP Document,
Section 1.1.11 Document Management (Scanning and Document
Generation) RFP Requirement Question: Does the state have any
existing scanning solution to which the system should integrate? If
the state expects the vendor to provide the scanning solution, can
you please indicate if state will provide the scanning hardware?
Q140 Response: Each office has multifunction devices with scanning
capability. If additional equipment is required, the State shall
procure it. Question 141: On page 31 of the RFP Document, Section
1.1.12 Workflow- RFP Requirement Question: Does the state have any
existing workflow engine solution which the state expects the
vendor to leverage? Q141 Response: No – Vendor to propose the best
solution. Question 142: In the RFP Document, Section 1.2 Technical
Requirements – RFP Requirement Question: What is the MDM solution
currently being used by the state? If there is no MDM solution in
place, can we assume that the state will procure MDM solution
outside this RFP and the proposed vendor solution will integrate to
the MDM? Or, is it the expectation of the state that the vendor
should propose a MDM solution as part of this RFP? Q142 Response:
State does not have an MDM solution currently. Vendor to price an
MDM component if it is part of their solution. Question 143: On
page 41 of the RFP Document, Section 1.3 Training RFP Requirement
Question: Develop and deliver train-the-trainer training –
functional (train-the-trainers) and technical training/knowledge
transfer; the State will use the DDI Proposer developed training
material to deliver functional training to the remaining State
users - Can we assume that the vendor is expected to provide the
Train-the-Trainer training only in one central location? If yes, we
are assuming Hartford is the location?
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 21 of 25
Q143 Response: Yes, it will be train-the-trainer as stated in
the RFP. The training will be at one of DSS offices based on
availability of training facilities (may not be Hartford). Question
144: On page 53 of the RFP Document, Section 1.3.8 Technical System
Design RFP Requirement Question: Can you please explain what is the
State’s expectation about the “Joint Technical Design (JTD)
session” for the vendor and what would be CT State’s involvement in
it? Q144 Response: Review and Approve the Design Question 145: On
page 60 of the RFP Document, Section 1.3.10 Task 10 – CONSTRUCTION
(DEVELOPMENT) RFP Requirement Question: “…with full access for the
Department to all source code throughout the life of the Contract”
- Does this also apply to the source code of the COTS or SaaS
product that may be provided based on a license agreement? Q145
Response: No. Only the Software Application being developed by the
Vendor. Question 146: RFP Requirement Question – “Provide
Department and Department partners access to the Test Environment”
- How many department / department partner users are expected to
access the following non production environments? Please see below
also:
• Development and unit test • System and integration test •
Conversion • User Acceptance Test (UAT) and Certification •
Training
Q146 Response: State anticipates about 35 users to have access
to the system for testing. Question 147: On page 69 of the RFP
Document, Section 1.3.12 RFP Requirement Question “The DDI
Contractor shall deliver the User Acceptance Test Tools” - Can we
assume that the “UAT Tools” mentioned here refers to the test
management tool? Q147 Response: Yes, the State is expecting Test
Management and Testing Tools for functional and stress testing. The
requirement is for a completed Application Life Cycle Management
Tool/System that will be used to manage the process of requirements
gathering & traceability, source code/deliverable repository
& version control, test case traceability and monitoring
testing progress and bug fixing, and automate the deployment of
application software on various environments. Question 148: On page
70 of the RFP Document, Section 1.3.16 Task 16 – CERTIFICATION RFP
Requirement Question - It is our understanding that the department
will lead and manage the certification and the DDI vendor will be
in supporting role. Please confirm. Q148 Response: No, It is
anticipated that the Certification will be lead by the Vendor.
State resources will assist in testing the system. Question 149: In
the RFP Document, Section 1.3.18 – TASK 18 – OPERATIONS AND
MAINTENANCE (OPTIONAL) Question - Can we assume the department will
own and operate the Tier 1 and Tier 2 Help desk / service desk and
only the L3 support is in scope of the optional O&M task for
the DDI vendor? Q149 Response: Yes. The department will provide
Tier 1 and Tier 2 help desk functions.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 22 of 25
Question 150: On page 89 of the RFP Document, Key Staff
Question: The test manager minimum qualification states “15+ years
in developing and delivering training”. Can you please clarify if
prior training experience is required for the test manager? Q150
Response: Yes. Question 151: RFP Appendix A – Requirement Matrix
Questions: The “requirements detail” column for some of the rows in
the requirements matrix are introduction / header (high level
requirements) to the list of detailed level requirements in the
subsequent rows. How do you want us to respond in the “Response
Code” column for those high level requirements if the detailed
requirements under the high level requirements do not have the same
“response code”. Please see examples below: E.g. “1.12.1 - The
system must meet Connecticut's processing needs, which include:”
“4.4.1- The system must accept, maintain, and process information
concerning established support orders. The system must:” “5.1.1 -
The system must automatically direct cases to the appropriate case
activity. The system must:” Q151 Response: For the high level
requirement, use one of the codes used for the detailed
requirements in this order – If any of the detail level requirement
has CD, use CD for the high level requirement. If any of the
detailed level requirement has SC (and no CD), use SC. Similarly,
OT and NM in that order if the detail level requirement does not
have any SC or CD. Question 152: RFP Appendix B Question: Can you
please indicate what time period the “Number of Times Executed”
column captures the data for? Can these be considered as frequency
of reports? Q152 Response: The number of times executed means the
number of times a user or scheduled process executed the report.
Some users may execute a report multiple times with different run
time options. Question 153: RFP Appendix B Question: There is a
table with a header “Brief Listing of Reports on Legacy CCSES
System Sorted in Descending order of Execution Frequency” followed
by a list with header “List of All Reports run against CCSES System
in 2018”. Are they different sets of reports or different views of
same reports? If they are 2 different sets are there any common
reports between the 2 lists? Q153 Response: The first list
represents reports created in a third party reporting tool called
Informer (https://entrinsik.com/informer/ ). The second list are
reports organic to the original CCSES application. These are
written in either UniVerse BASIC, the UniVerse RETRIEVE language,
or a combination of both. Question 154: RFP Appendix J Question:
The timeline does not refer to any pilot however the RFP section
1.3 includes the task “Implement the full system with pilot
implementation”. Can we consider milestone 50 in appendix J as end
of the pilot and statewide implementation and the pilot phase
somewhere between milestone 39 (end of UAT) and 50? Q154 Response:
Yes. The Project Schedule provided was for guidance only. Vendors
to create their schedule based on their approach to implementation.
Question 155: Exhibit B Product & Pricing Schedule Question:
Can we assume that the first 6 years will be base year and next 4
years are optional years? Q155 Response: Maintenance and Operation
phase (after system warranty is complete) is optional from a
contract perspective but the State may decide to continue with the
vendor. The vendor needs to provide cost for all 10 years.
https://entrinsik.com/informer/
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 23 of 25
Question 156: Exhibit B Product & Pricing Schedule Table C
Question: Can we consider the milestone 50 - Implemented CCSES
System (Production Code) as the milestone of pilot start date? Q156
Response: No, Pilot will be completed before Milestone 50 which is
when the System is expected to go live in production. Vendors can
include the cost of Pilot in Milestone 50. Question 157: Exhibit B
Product & Pricing Schedule Table C Question: There are some
recurring deliverables like status reports – shall we provide the
cost for each instance and consider the planned number of instances
to arrive at the subtotal? Q157 Response: No, Just the Total Cost.
State would like the vendors to propose the payment plan,
considering the payments not be front-loaded within the project,
and perhaps should follow the following guideline:
Key milestones % of total DDI cost Requirements 10% Design 20%
Development & Testing 30% UAT 20% Implementation 15% Warranty
5% State will negotiate the payment schedule with the selected
vendor. Question 158: On page 70 of the RFP Document – TASK 13 –
END USER TRAINING Questions:
I. Does the State expect the DDI Contractor to "partner" with
the OCSS/SES/OSD on all classroom training delivery sessions for
500 internal staff at 13-24 offices? Or a subset?
II. Does the State have computer training facilities? How many
and where are they located?
III. How many internal end user trainees can attend a classroom
training session?
IV. What is the scope of the training needs assessment? Does it
include areas such as Windows literacy or primarily the delta
between as-is and to-be processes and application use?
V. How many UAT testers will require training? Location(s)?
VI. How many Help Desk staff will require training? Location(s)?
Q158 Response:
I. Pl refer to 1.3.13 TASK 13 – END USER TRAINING on P70 of the
RFP. This is to be decided based on the Project End User Training
Management Plan.
II. DSS has the labs listed below at DSS sites:
1. Bridgeport PC lab – 1 PC lab (13 computers including a
trainer computer) 2. Harford CO - 55 Farmington Avenue – 2 PC labs
(20 computers in each lab including trainer computers) 3. Greater
Harford Office – Windsor CT - 2 PC labs (20 computers in each lab
including trainer computers) 4. Manchester – 1 PC lab (20 computers
including a trainer computer) 5. Middletown – 3 PC labs (17
computers in each lab including trainer computers)
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 24 of 25
6. New Britain – 1 PC lab (13 computers including a trainer
computer) 7. New Haven - 1 PC lab (13 computers including a trainer
computer) 8. Norwich - 1 PC lab (13 computers including a trainer
computer) 9. Waterbury - 1 PC lab (18 computers including a trainer
computer) – for Waterbury staff only – parking limited 10.
Willimantic - 1 PC lab (13 computers including a trainer
computer)
SES Training Locations for Judicial Staff are as follows:
1) 99 East River Drive, East Hartford (fits 18) 2) 1 Lafayette
Circle, Bridgeport SES Training Room (fits 17)
III. See above. IV. Delta between as-is and to-be processes and
application use. V. The State anticipates this to be around 20-25
UAT testers. VI. Assume about 15-20 Help Desk staff requiring
training.
Question 159: On page 37 of the RFP Document, Section 1.2.2.2
Technical Requirements RFP Requirement Question: The CCSES solution
should allow access to a minimum of 500 internal users and have the
capability to support all external registered users, and external
non-registered guest users – What is the number of end users and
split of the users between functions (RFP says minimum of users as
500? Q159 Response: Reference Q14 and Q21 response. Question 160:
Does the State have any preferred cloud solution provider? Q160
Response: Reference Q105 response. Question 161: Has the State seen
demos of any other vendors? Q161 Response: Reference Q24 response.
Question 162: Do you have any integration with external systems? If
so, how many systems integration required? Q162 Response: Reference
Q25 response. Question 163: How many years of legacy data should be
migrated to the new from existing system? Q163 Response: Plan on
migrating all data. Question 164: Will all users/functions require
Web / Mobile / Tablet accessibility? Q164 Response: No. Only a
subset of functions will be provided on the web portal and mobile.
As mentioned in the RFP, key functions anticipated to be online are
viewing case and payment information and submitting applications
online. Question 165: Please provide the number of concurrent
users? Q165 Response: Please refer Page 71 of the RFP Document.
Question 166: Any specific choice of technologies to be used in the
proposed solution? Q166 Response: No, Vendors to recommend their
solution. State is open to all solutions. Question 167: What is the
State’s preferred reporting solution? Q167 Response: Please see
table on page 35 – Vendor to propose their solution.
-
RFP ADDENDUM RFP-18 Rev. 3/13/14 Prev. Rev. 10/17/13
RFP NO.: 18PSX0277
Page 25 of 25
Question 168: Does the state have common master data with other
IVA and IV E agencies? Q168 Response: State is looking at a common
EMPI (Master Person Index) that in future will be common between
agencies. Question 169: How is the Total Cost of ownership common
sized? Q169 Response: All vendors will bid costs to procure,
implement and maintain the solution and the infrastructure for 10
years. Question 170: Should we include infra costs in the Total
cost of ownership estimate? If so can the State provide the list of
infra assets they have in place? Q170 Response: Vendors to assume
that Department does not have anything (but the networking
equipment, IVR equipment, IBM ISIM ISAM for Authentication, and
PilotFish licenses as an Integration Engine) in place. Vendors to
propose all environments as specified in the RFP and Cost Proposal.
Infra costs are included in the total cost of ownership. Question
171: What is the planned Go Live date? Q171 Response: Department
does not have a date in mind. Vendor to prepare their schedule
based on their recommended approach and show the go live date in
that. Question 172: Does the state prefer county wise go live with
full feature set or feature wise go live across the State? Q172
Response: Connecticut Child support system is not county based.
Vendors to propose their recommended approach for a successful go
live. Question 173: In the TCO, if we assume an Early go live
compared to the estimated 40 months, should we reduce the M&O
costs of the current system? Q173 Response: Vendors need to bid 10
year cost Question 174: Can Engineering and Configuration work be
done off shore with the Data not leaving U.S territory? Q174
Response: Yes. Question 175: Does the State have license for any
data migration/ETL tool? Q175 Response: No.
-
IF2600 IV-A File Format
Tape Characteris�cs:
Configura�on 9 track odd parityCharacter Code EBCDICRecording
Density 6250 BPILabel (Header & Trailer) IBM Standard
Data set name = IF2600Record Size 464Blocking Factor 1Block Size
464
Flat File Characteris�cs:
File SQ.FLECharacter Code ASCII TextRecording ID
P50070.IF2600PA.YYYYMMDD and P50201.IF2600SA.YYYYMMDD
where YYYYMMDD = the flat file dateRecord Length 464Record
Delimiter ASCII char(12) = Carriage Return/
Descrip�on Posi�on Mask DataImpaCT Sequence Number 3 - 9 X(7)
Record type 10 - 11 X(2) Agency Code 279 - 280 X(2) AP Key 457 -
464 X(8)
Referral (PW) Record (70):
Descrip�on Posi�on Mask DataImpaCT Sequence Number 3 - 9 X(7)
IF3170.TEMP(46)Record type 10 - 11 X(2) '70'Program code 12 - 13
X(2) PA.FLE(34)Status code 14 X(1) PA.FLE(29) 15 - 16 X(2) Type 70
SSN 17 - 25 9(9) Closure reason 23 - 31 X(9) PA.FLE(32)Benefit
Start date 32 - 39 9(8) PA.FLE(30)
-
Descrip�on Posi�on Mask DataBenefit End date 40 - 47 9(8)
PA.FLE(31)
IF3170.TEMP(6) 48 - 65 X(18) City 66 - 87 X(22) PA.FLE(23)
IF3170.TEMP(15)State 88 - 89 X(2) PA.FLE(24)
IF3170.TEMP(16)Zip 90 - 98 9(9) PA.FLE(25)
IF3170.TEMP(17)Resident Start Number CP Residence Address 1 99 -
131 X(33) IF3170.TEMP(13) CP Residence Address 2 132 - 136 X(5)
IF3170.TEMP(14)No CP Residence Street Number CP Residence Address 1
137 - 158 X(22) IF3170.TEMP(13) 159 - 168 X(10) CP Residence
Address 2 169 - 190 X(22) IF3170.TEMP(14)CP Residence Street Number
Street number 99 - 103 X(5) PA.FLE(21) Street direc�on 104 - 105
X(2) IF3170.TEMP(13) Street name 106 - 125 X(20) Street type 126 -
129 X(4) City direc�on 130 - 131 X(2) Apartment number 132 - 136
X(5) PA.FLE(22)No CP Residence Street Number Street number 99 - 103
X(5) PA.FLE(21) 104 - 105 X(2) CP Address 1 137 - 158 X(22)
PA.FLE(21) CP Address 2 159 - 180 X(2) PA.FLE(22)Home phone 181 -
187 X(7) PA.FLE(14)Town code 188 - 190 X(3) PA.FLE(13)IV-A Client
ID 191 - 199 X(9) PA.FLE(36)Last name 200 - 218 X(19)
PA.FLE(16)First name 219 - 230 X(12) PA.FLE(17)Middle ini�al 231
X(1) PA.FLE(18)SSN 232 - 240 X(9) PA.FLE(12)Birth date 241-248 9(8)
PA.FLE(19)
IF3170.TEMP(26)Marital status 249 X(1) PA.FLE(20)CL Status code
250 X(1) PA.FLE(26)
-
Descrip�on Posi�on Mask DataCL Status date 251 - 258 9(8)
PA.FLE(27)Applica�on Date 259 - 266 9(8) PA.FLE(28)Previous IV-A
number 267 - 275 X(9) PA.FLE(15)Sex 276 X(1) PA.FLE(37) 277 - 285
AU Benefit Amount 286 - 294 9(7)V99 PA.FLE(33)MA Coverage Group
Code 295 - 297 X(3) PA.FLE(38)MR Status Code 298 X(1)
PA.FLE(02)Child Support Amount 299 - 307 9(7)V99 PA.FLE(04)Child
Support Date 1 YYYYMM 308 - 313 9(6) PA.FLE(05)Child Support Amount
314 - 322 9(7)V99 PA.FLE(04)Child Support Date 2 YYYYMM 323 - 328
9(6) PA.FLE(05)Child Support Amount 329 - 337 9(7)V99
PA.FLE(04)Child Support Date 3 YYYYMM 338 - 343 9(6)
PA.FLE(05)Child Support Amount 344 - 352 9(7)V99 PA.FLE(04)Child
Support Date 4 YYYYMM 353 - 358 9(6) PA.FLE(05)Child Support Amount
359 - 367 9(7)V99 PA.FLE(04)Child Support Date 5 YYYYMM 368 - 373
9(6) PA.FLE(05)Child Support Amount 374 - 382 9(7)V99
PA.FLE(04)Child Support Date 6 YYYYMM 383 - 388 9(6) PA.FLE(05) 389
- 397 IV-D Reinstatement Flag 398 X(1) PA.FLE(06)Welfare reform
group code 399 X(1) PA.FLE(60)Welfare reform group date 400 - 405
9(6) PA.FLE(61)Experimental flag 406 X(1) PA.FLE(64)Non-Ci�zen CA
Fund Type 407 X(1) PA.FLE(270)Non-Ci�zen MA Fund Type 408 X(1)
PA.FLE(271) 409 - 464
Dependent Record (71):
Descrip�on Posi�on Mask DataRecord Type 10 - 11 X(2) '71'Client
ID 12 - 20 X(9) PA.FLE(44)Dependent last name 21 - 39 X(19)
PA.FLE(85)Dependent middle ini�al 40 X(1) PA.FLE(86)Dependent first
name 41 - 52 X(12) PA.FLE(87)Dependent SSN 53 - 61 9(9)
PA.FLE(88)Dependent birth date 62 - 69 9(8) PA.FLE(89)
-
Descrip�on Posi�on Mask DataSex 70 X(1) PA.FLE(90)Birth hospital
71 - 103 X(33) PA.FLE(91)Birth county 104 - 125 X(22)
PA.FLE(92)Birth state 126 - 127 X(2) PA.FLE(93) 128 Rela�on To CP
129 - 130 X(2) PA.FLE(94)Client status code 131 X(1) PA.FLE(95)AU
Benefit Beginning Date 132 - 139 9(8) PA.FLE(96)NCP 1 Rela�onship
to DP 140 - 141 X(2) PA.FLE(97)NCP 1 Sequence Number 142 - 146 X(5)
PA.FLE(42)NCP 2 Rela�onship to DP 147 - 148 X(2) PA.FLE(97)NCP 2
Sequence Number 149 - 153 X(5) PA.FLE(42)NCP 3 Rela�onship to DP
154 - 155 X(2) PA.FLE(97)NCP 3 Sequence Number 156 - 160 X(5)
PA.FLE(42)NCP 4 Rela�onship to DP 161 - 162 X(2) PA.FLE(97)NCP 4
Sequence Number 163 - 167 X(5) PA.FLE(42)AU Paid Through Date 168 -
175 9(8) PA.FLE(96)Non-Ci�zen CA Fund Type 176 X(1)
PA.FLE(272)Non-Ci�zen MA Fund Type 177 X(1) PA.FLE(273) 178 -
464
TPL Insurance (72):
Descrip�on Posi�on Mask DataRecord Type 10 - 11 X(2) '72'Client
ID 12 - 20 X(9) Carrier number 21 - 25 X(5) 26 - 33 Policy effec�ve
date 34 - 41 9(8) PA.FLE(50)Policy end date 42 - 49 9(8)
PA.FLE(51)Individual policy number 50 - 62 X(13) PA.FLE(52)Group
policy number 63 - 77 X(15) PA.FLE(52)Policy verifica�on date 78 -
85 9(8) PA.FLE(53) 86 - 102 Policyholder name 103 - 132 X(30)
PA.FLE(54) 133 - 134 Policy change date 135 - 142 9(8) PA.FLE(55)
143 - 145 Coverage type code 1 146 X(1) PA.FLE(56)
-
Descrip�on Posi�on Mask DataCoverage effec�ve date 147 - 154
9(8) PA.FLE(57)Coverage end date 155 - 162 9(8) PA.FLE(58) 163 -
164 Coverage type code 2 165 X(1) PA.FLE(56)Coverage effec�ve date
166 - 173 9(8) PA.FLE(57)Coverage end date 174 - 181 9(8)
PA.FLE(58) 182 - 183 Coverage type code 3 184 X(1)
PA.FLE(56)Coverage effec�ve date 185 - 192 9(8) PA.FLE(57)Coverage
end date 193 - 200 9(8) PA.FLE(58) 201 - 202 Coverage type code 4
203 X(1) PA.FLE(56)Coverage effec�ve date 204 - 211 9(8)
PA.FLE(57)Coverage end date 212 - 219 9(8) PA.FLE(58) 220 - 221
Coverage type code 5 222 X(1) PA.FLE(56)Coverage effec�ve date 223
- 230 9(8) PA.FLE(57)Coverage end date 231 - 238 9(8) PA.FLE(58)
239 - 240 Coverage type code 6 241 X(1) PA.FLE(56)Coverage effec�ve
date 242 - 259 9(8) PA.FLE(57)Coverage end date 260 - 267 9(8)
PA.FLE(58) 268 - 464
NCP ID (73):
Descrip�on Posi�on Format DataImpaCT Sequence Number 3 - 9 9(7)
Record Type 10 - 11 X(2) '73'NCP Sequence Number 12 - 16 X(2)
PA.FLE(100)NCP SSN 17 - 25 9(9) PA.FLE(101)Last name 26 - 44 X(19)
IF3170.TEMP(9), IF3170.TEMP(12)
PA.FLE(102)Middle name 45 - 56 X(12) IF3170.TEMP(8),
IF3170.TEMP(11)
PA.FLE(103)First name 57 - 68 X(12) IF3170.TEMP(7),
IF3170.TEMP(10)
PA.FLE(104)
-
Descrip�on Posi�on Format DataAddress date 69 - 76 9(8)
IF3170.TEMP(6)
PA.FLE(105)Street 1 77 - 98 X(22) IF3170.TEMP(13)
PA.FLE(106)Street 2 99 - 120 X(22) IF3170.TEMP(14)
PA.FLE(107)City 121 - 142 X(22) IF3170.TEMP(15)
PA.FLE(108)State 143 - 144 X(2) IF3170.TEMP(16)
PA.FLE(109)Zip 145 - 153 9(9) IF3170.TEMP(17)
PA.FLE(110)Phone 154 - 163 X(10) PA.FLE(111)Previous address
date 164 - 171 9(8) PA.FLE(112)Previous stree