Attach 3 to A0007 - R-OPC-23287 Questions and Responses.pdf

Attachment 3 to A0007

R-OPC-23287

Questions and Responses

No. Section Question Response 92 B.5.02.0014AA What is the volume of mailings that are completed by the CPTA manually vs. the electronic mailings prepared by Ginnie Mae?

Manual: Approximately volume anywhere between 3000 - 3250 a month - includes Ginnie Mae II checks, customer service correspondence, unclaimed fund checks to issuers, Ginnie Mae MBS prospectus etc.

93 C.2.07(c) When will the documentation on the BPI applications, databases, integration, be available?

There is documentation on Ginnie Mae.gov that outlines the RFS, Portal and GinnieNET functionality. The replacement for IPMS has not begun yet. It is in the analysis and design phase. Refer to Pre-Conference presentations for more detail.

94 C.2.07(c) How will the implementation of the BPI impact the legacy applications?

The main goal of the BPI is to retire legacy applications with new infrastructure.

Consequently, all data currently stored in various legacy databases will be transferred to the Enterprise-wide Operational Data store (Data Warehouse). The first legacy application for the BPI is the Reporting and Feedback System (RFS) that is managed by the MBSAA.

95 C.2.07(c) For all the legacy applications that will be replaced through the BPI, please provide a schedule of when the legacy applications will be shut down and when the new replacement system will be implemented.

To date, an implementation plan has not been established for replacing the remaining legacy application (Integrated Pool Management System). It is anticipated that the new systems will be developed during the base period of the contract.

96 C.2.07(c) How will the integration of legacy applications with new Portal, RFS and EWODS work?

Initially, only RFS will be accessed through the Portal. RFS data will be loaded directly to EWODS. At some point in the future, GinnieNET/IPMS will be accessed through the Portal. However, as of November 2008, legacy IPMS will begin updating EWODS.

97 C.2.07(c) Are modifications to the legacy applications required with the November implementation of the BPI that was discussed in the pre-proposal conference?

No, modifications to legacy applications do not have anything to do with the implementation of the BPI. Also, see additional clarification to the Statement of Work, which is provided separately in this Amendment.

Questions and Responses

No. Section Question Response 98 C.2.07(c) Security Authentication and entitlements. Who needs access to what application? How is security administered to each application/user group?

This information is proprietary. Upon contract award, this information will be provided.

99 C.3.02 Will all GFITSA delivered under the contract be compliant with IT security requirements required by regulations listed in item (a) of this section?

We expect that all GFITSA will be compliant or mitigated by contract award date.

100 C.3.02 Please provide an inventory of applications (including 3rd party software such as databases, imaging & document management platforms, schedulers, system monitoring tools, archiving tools, etc) that are directly or indirectly used to support Ginnie Mae functions

Please see AMENDMENT posted to the HUD website (or Fedbizops) on 5/31/2008, which outlines proposed hardware and software for the BPI, EWODS and Portal.

101 C.3.02 Please list the entire hardware inventory -including the CPU speeds, MIPS, DASD sizes, RAID, memory, number of processors, hardware vendor, model number, operating system version, service pack level. Also include desktop configurations

This information is proprietary. Ginnie Mae's expectation is that the contractor will determine the appropriate hardware, versions and service pack levels.

102 C.3.02 Provide an inventory and locations of network components including routers, switches, hubs, firewalls, encrypters, csu/dsu, etc that are directly or indirectly used to support Ginnie Mae's business functions, inclusive of listing owners of circuits both internally and connections externally

This information is proprietary. Ginnie Mae's expectation is that the contractor will determine the appropriate hardware, versions and service pack levels.

103 C.3.02 What communication links will the Contractor be responsible for establishing and maintaining (e.g.,. T-1 lines)?

The contractor shall be responsible for establishing and maintaining the appropriate communication links to support the business functions outlined in this RFP. This may include T1, T3, and other types of secure communication links for the WEB.

Questions and Responses

No. Section Question Response 104 C.3.02 Are the existing systems at the standards required by this RFP (e.g. FISMA, NIST, A123, A127 ..)? If not, what are the exceptions?

Ginnie Mae monitors and mitigates any concerns for systems with respect to compliance with all Federal regulations.

105 C.3.02 Have the systems been audited by HUD or any other independent agency? What findings were raised? To what extent have the findings been resolved? Is any such audit contemplated or pending?

Ginnie Mae systems are audited by several entities annually. Findings, if any, are monitored, remediated or mitigated during the year following the audits.

106 C.3.02 Will Ginnie Mae provide copies of prior years technology refresh recommendation reports for the existing contract?

Copies of technology refresh recommendations are proprietary and are not available.

107 C.3.02 What is the current software/version release schedule for all legacy applications?

There are no software/version releases that are currently planned. However, if Ginnie Mae has a business need, there may be a release.

108 C.3.02 Are there any minor/major releases that will be released during the transition period or will need to be released within 90 days after the transition period?

There are no releases that are currently planned to take place during the transition period. However, if Ginnie Mae has a business need for a change, there may be a need for a release during this time.

109 C.3.02 Are there any existing FISMA security findings already documented on these legacy systems that must be addressed between transition AND the deployment of the replacement systems?

There are no major FISMA findings at this time. During the transition period, a certification and accreditation will be performed. Ginnie Mae will follow the most current NIST standards in documenting any major findings that must be addressed during the transition period and the deployment of the replacement systems.

110 C.3.02 Must all of the legacy environment be restored in the 4-hour DR timeframe or does this apply to specific legacy components ONLY? Please specify the systems that the 4 hour recovery period applies.

The RFP requires that all systems are restored within 4 hours. Refer to the RFP.

111 C.3.02 Please provide the requisite service level agreements ( transaction processing speed, report generation speed, batch processing) for IPMS-Pool Reporting Module

There is no SLA for IPMS. Please refer to RFP for specific timelines for processing.

Questions and Responses

No. Section Question Response 112 C.3.02 Please provide hardware deployment information

(servers, firewalls, etc) for IPMS-Pool Reporting Module-Pool Reporting Module - across dev, qa and prod environments. Also mention any special requirements such as failover, load balancing, replication, etc

The Offeror has to define transition activities related to hardware deployment, failover and replication as part of the response to the RFP. The transition cannot disrupt Ginnie Mae operations.

113 C.3.02 Please provide the system security categorization for IPMS-Pool Reporting Module

IPMS is moderate. Pool Reporting which is a module of IPMS is not evaluated separately from IPMS.

114 C.3.02 Please provide system utilization statistics (CPU, virtual memory, etc) for IPMS-Pool Reporting Module-Pool Reporting Module

We do not have separate system utilization statistics for the Pool Reporting Module.

115 C.3.02 Please specify data archival requirements (frequency, data volumes, etc) for IPMS-Pool Reporting Module

Currently data is archived nightly for IPMS.

There are not separate requirements for Pool Reporting.

116 C.3.02 Please provide availability requirements (24X7, 24X5, etc) for IPMS-Pool Reporting Module-Pool Reporting Module

Currently, IPMS, which includes the Pool Reporting module, is available to Ginnie Mae from 7am to 6pm Eastern time. Ginnie Mae's plans are to move to same day pool processing as defined in the RFP, which may

117 C.3.02 Please provide sizing parameters for IPMS-Pool Reporting Module - no. of screens, no. of batches, no. & size of tables/files, etc. Please provide the data storage file types (e.g. DB2, VSAM, Oracle ..) and number of those tables

There are approximately 155 DB2 tables organized in four table spaces. These tables take up 125,000 tracks. There are approximately 50 main VSAM files and the total allocation for VSAM and flat files is about 3.8 million tracks. There are 1311 modules in Endevor, 260 of which are online screens

118 C.3.02 Please provide interface details for IPMS-Pool Reporting Module-Pool Reporting Module - no. of interfaces, interface type (file, synchronous calls, asynchronous calls, etc), data transfer volumes

Currently for IPMS, there are 54 transmissions using combination of Network Data Mover (NDM) and Bulk Data Transfer (BDT). Pool Reporting is a module is a component of IPMS.

119 C.3.02 Please provide usage parameters (average & peak levels) for IPMS-Pool Reporting Module -transactions per day, concurrent users, response times

For IPMS (Pool Reporting is a module of IPMS), the average number of non-system transactions per day in June is 4,535. The peak number (on June 3) was 11,177. Daily average response time is less than 0.15 seconds.

Questions and Responses

No. Section Question Response 120 C.3.02 Please mention the average number of support/enhancement requests (per month) for IPMS-Pool Reporting Module-Pool Reporting Module.

The number of systems modifications and enhancements for IPMS varies depending on requests by Ginnie Mae

121 C.3.02 Please provide estimated growth statistics for IPMS-Pool Reporting Module over the base period, option period 1, option period 2 - in terms of number of users, growth in data volumes

There are no growth statistics for the Pool Reporting System. There are currently less than 100 user ids for IPMS mainframe access for Ginnie Mae and contractor staff.

122 C.3.02 Are there any known performance related issues with IPMS-Pool Reporting Module-Pool Reporting Module - such as online response times, batch processing windows, etc

IPMS, and Pool Reporting which is part of IPMS, has no known performance issues currently.

123 C.3.02 Please mention any known environment/design/architectural issues that make it difficult to extend/enhance IPMS-Pool Reporting Module

IPMS is a legacy COBOL/Db 2 application that will be rewritten during the base period of the contract in order to utilize more current technology. Legacy source code documentation is available in Binders 10, 11,13, 14, 14 (a), 15, 15(a), 16, 17, 17 (a) and 22 in the Ginnie Mae reading room.

124 C.3.02 Please provide the list of enhancements that are planned for IPMS-Pool Reporting Module-Pool Reporting Module over the next 12 months

IPMS which is a legacy system will begin to be rewritten in the next 12 months.

125 C.3.02 Please provide a list of third party software licenses that are required for IPMS-Pool Reporting Module. Also mention the estimated annual licensing cost and indicate whether these licenses are transferable

There are no third party software licenses that are required for the IPMS-Pool Reporting Module.

126 C.3.02 Please provide the requisite service level agreements ( transaction processing speed, report generation speed, batch processing) for GinnieNET

There are no SLAs. Please refer to RFP for specific timelines for processing.

127 C.3.02 Please provide hardware deployment information (servers, firewalls, etc) for GinnieNET - across dev, qa and prod environments. Also mention any special requirements such as failover, load balancing, replication, etc

The Offeror has to define transition activities related to hardware deployment, failover and replication as part of the response to the RFP. The transition cannot disrupt Ginnie Mae operations.

Questions and Responses

No. Section Question Response 128 C.3.02 Please provide the system security categorization for GinnieNET Moderate

129 C.3.02 Please provide system utilization statistics (CPU, virtual memory, etc) for GinnieNET

Utilization statistics are not currently captured for GinnieNET.

130 C.3.02 Please specify data archival requirements (frequency, data volumes, etc) for GinnieNET

GinnieNET data is archived nightly.

Frequency and volumes will vary according to market conditions.

131 C.3.02 Please provide availability requirements (24X7, 24X5, etc) for GinnieNET

The system is available except for a maintenance window from 2:00am to 4:00am

132 C.3.02 Please provide sizing parameters for GinnieNET -

no. of screens, no. of batches, no. & size of tables/files, etc

There are 96 pages in GinnieNET on the Web. There are 72 screens in non-Web applications. There are 84 batches. The GinnieNET database contains 1,182 tables, indexes, etc using 14 GB. All of GinnieNET consumes 132 GB

133 C.3.02 Please provide interface details for GinnieNET -

no. of interfaces, interface type (file, synchronous calls, asynchronous calls, etc), data transfer volumes

GinnieNET interfaces with IPMS and the Web . Citrix is used internally by incumbent.

Refer to RFP for data transfer volumes.

134 C.3.02 Please provide usage parameters (average & peak levels) for GinnieNET - transactions per day, concurrent users, response times

There are 1700 registered users and the usage is peak in the first 5 business day of a month. There are over 50,000 hits per day during the peak period. The average excluding the monthly peak period is about 5000 hits per day.

135 C.3.02 Please mention the average number of support/enhancement requests (per month) for GinnieNET.

Ginnie Mae enhancements/modifications average 4 to 5 a year. We do not have monthly statistics.

136 C.3.02 Please provide estimated growth statistics for GinnieNET over the base period, option period 1, option period 2 - in terms of number of users, growth in data volumes

GinnieNET was launched as a web base application during Option Year 1. Growth statistics are unavailable. There are approximately 880 users off the system.

137 C.3.02 Are there any known performance related issues with GinnieNET - such as online response times, batch processing windows, etc

There are no performance related issues at this time.

Questions and Responses

No. Section Question Response 138 C.3.02 Please mention any known environment/design/architectural issues that make it difficult to extend/enhance GinnieNET

None at this time. As part of Ginnie Mae's modernization efforts, new technologies and best practices are considered. Any new business requirements defined by Ginnie Mae, may result in changes.

139 C.3.02 Please provide the list of enhancements that are planned for GinnieNET over the next 12 months

Currently, GinnieNET is being enhanced to add new pool types, additional data fields to support RFS and data disclosure.

140 C.3.02 Please provide a list of third party software licenses that are required for GinnieNET. Also mention the estimated annual licensing cost and indicate whether these licenses are transferable

Sargent Technology, Inc. site license for Geo Scan Libraries. Annual licensing costs should be obtained from Sargent Technology Inc. This license is held by the Contractor.

141 C.3.02 Please provide the requisite service level agreements ( transaction processing speed, report generation speed, batch processing) for the Letter of Credit Module

There are no SLAs.

142 C.3.02 Please provide hardware deployment information (servers, firewalls, etc) for the Letter of Credit Module - across dev, qa and prod environments.

Also mention any special requirements such as failover, load balancing, replication, etc

The Offeror has to define transition activities related to hardware deployment, failover and replication as part of the response to the RFP. The transition cannot disrupt Ginnie Mae operations.

143 C.3.02 Please mention any special security requirements (user access, data security & privacy) for the Letter of Credit Module

There are no other special requirements. It complies with NIST and Federal regulations.

144 C.3.02 Please provide system utilization statistics (CPU, virtual memory, etc) for the Letter of Credit Module

We do not have separate system utilization statistics for the LOC module.

145 C.3.02 Please specify data archival requirements (frequency, data volumes, etc) for the Letter of Credit Module

IPMS The Letter of Credit Module is archived nightly as a component of IPMS.

146 C.3.02 Please provide availability requirements (24X7, 24X5, etc) for the Letter of Credit Module

The application is available from 7:00 AM thru 6:00 PM Monday through Friday. Batch processing takes place nightly.

Questions and Responses

No. Section Question Response 147 C.3.02 Please provide sizing parameters for the Letter of

Credit Module - no. of screens, no. of batches,

no. & size of tables/files, etc

VFP framework - Flash Mgt – 596 files, 33 form libraries,12 program files, 22 report files,113 VFP DB files 249MB

148 C.3.02 Please provide interface details for the Letter of Credit Module - no. of interfaces, interface type (file, synchronous calls, asynchronous calls, etc), data transfer volumes

The LOC is a module of IPMS. IPMS posts reports to eNotification.

149 C.3.02 Please provide usage parameters (average & peak levels) for the Letter of Credit Module -transactions per day, concurrent users, response times

The LOC is a module of IPMS. Currently, there are 5 users that have access to LOC.

150 C.3.02 Please mention the average number of support/enhancement requests (per month) for the Letter of Credit Module. For an average maintenance request, what is the typical FTE requirement?

The LOC is a module of IPMS. The changes to this module are rare. There is no separate FTE requirement for this module.

151 C.3.02 Please provide estimated growth statistics for the Letter of Credit Module over the base period, option period 1, option period 2 - in terms of number of users, growth in data volumes

This information is not available.

152 C.3.02 Are there any known performance related issues with the Letter of Credit Module - such as online response times, batch processing windows, etc

No, there are no performance related issues with the Letter of Credit Module at this time.

153 C.3.02 Please mention any known environment/design/architectural issues that make it difficult to extend/enhance the Letter of Credit Module

There are no issues at this time.

154 C.3.02 Please provide the list of enhancements that are planned for the Letter of Credit Module over the next 12 months

Currently, there are no planned enhancements over the next 12 months.

155 C.3.02 Please provide a list of third party software licenses that are required for the Letter of Credit Module. Also mention the estimated annual licensing cost and indicate whether these licenses are transferable

See Attachment B

Questions and Responses

No. Section Question Response 156 C.3.02 Please provide the requisite service level agreements ( transaction processing speed, report generation speed, batch processing) for Multifamily DB Module

There are no SLAs for the Multifamily Database Module

157 C.3.02 Please provide hardware deployment information (servers, firewalls, etc) for Multifamily DB Module

- across dev, qa and prod environments. Also mention any special requirements such as failover, load balancing, replication, etc

The Offeror has to define transition activities related to hardware deployment, failover and replication as part of the response to the RFP. The transition cannot disrupt Ginnie Mae operations.

158 C.3.02 Please provide the system security categorization for Multifamily DB Module

The Multifamily DB module is a component of GinnieNET. GinnieNET is moderate.

159 C.3.02 Please provide system utilization statistics (CPU, virtual memory, etc) for Multifamily DB Module

We do not have separate system utilization statistics for the MF database module.

160 C.3.02 Please specify data archival requirements (frequency, data volumes, etc) for Multifamily DB Module

The Multifamily DB module is archived nightly.

161 C.3.02 Please provide availability requirements (24X7, 24X5, etc) for Multifamily DB Module

This application is available 24x7 via the web.

162 C.3.02 Please provide sizing parameters for Multifamily DB Module - no. of screens, no. of batches, no. & size of tables/files, etc

4 Web Pages, 3 Data entry screens, batches and database included in GinnieNET

163 C.3.02 Please provide interface details for Multifamily DB Module - no. of interfaces, interface type (file, synchronous calls, asynchronous calls, etc), data transfer volumes

Refer to Question 58.

164 C.3.02 Please provide usage parameters (average & peak levels) for Multifamily DB Module -transactions per day, concurrent users, response times

The Multifamily DB module on the Web averages 150 inquiries per day. The highest to lowest range of inquiries is 640 to 4.

Concurrent users and response time is not available.

Questions and Responses

No. Section Question Response 165 C.3.02 Please mention the average number of support/enhancement requests (per month) for Multifamily DB Module.

Less than one a month.

166 C.3.02 Please provide estimated growth statistics for Multifamily DB Module over the base period, option period 1, option period 2 - in terms of number of users, growth in data volumes

This information is not available.

167 C.3.02 Are there any known performance related issues with Multifamily DB Module - such as online response times, batch processing windows, etc

There are no known performance related issues at this time.

168 C.3.02 Please mention any known environment/design/architectural issues that make it difficult to extend/enhance Multifamily DB Module

There are no known environmental/design/architectural issues.

169 C.3.02 Please provide the list of enhancements that are planned for Multifamily DB Module over the next 12 months

Currently, there are no planned enhancements for the Multifamily DB.

170 C.3.02 Please provide a list of third party software licenses that are required for Multifamily DB Module. Also mention the estimated annual licensing cost and indicate whether these licenses are transferable

See Attachment B

171 C.3.02 Please provide the requisite service level agreements ( transaction processing speed, report generation speed, batch processing) for New Issuer Module

There are no SLAs for IPMS (the New Issuer Module is part of IPMS).

172 C.3.02 Please provide hardware deployment information (servers, firewalls, etc) for New Issuer Module -across dev, qa and prod environments. Also mention any special requirements such as failover, load balancing, replication, etc

The Offeror has to define transition activities related to hardware deployment, failover and replication as part of the response to the RFP. The transition cannot disrupt Ginnie Mae operations.

173 C.3.02 Please provide the system security categorization for New Issuer Module

This is a module of IPMS. IPMS is Moderate.

Questions and Responses

No. Section Question Response 174 C.3.02 Please provide system utilization statistics (CPU, virtual memory, etc) for New Issuer Module We do not have separate system utilization statistics for the New Issuer Module.

175 C.3.02 Please specify data archival requirements (frequency, data volumes, etc) for New Issuer Module

IPMS (which the new Issuer module is a part

of) is archived nightly.

176 C.3.02 Please provide availability requirements (24X7, 24X5, etc) for New Issuer Module

The application is available from 7:00 AM thru 6:00 PM Eastern time, Monday through Friday. Batch processing takes place nightly.

177 C.3.02 Please provide sizing parameters for New Issuer Module - no. of screens, no. of batches, no. & size of tables/files, etc

VFP framework - Flash Mgt – 596 files, 101 program files, 59 forms libraries, 18 reports,95 VFP DB files 11 MB

178 C.3.02 Please provide interface details for New Issuer Module - no. of interfaces, interface type (file, synchronous calls, asynchronous calls, etc), data transfer volumes

The New Issuer Module is part of IPMS.

Currently, there are 10 users with access to the New Issuer Module. There is minimal data transfer activity.

179 C.3.02 Please provide usage parameters (average & peak levels) for New Issuer Module -transactions per day, concurrent users, response times

The New Issuer Module averages 1-2 inquiries per month.

180 C.3.02 Please mention the average number of support/enhancement requests (per month) for New Issuer Module.

This information is not available.

181 C.3.02 Please provide estimated growth statistics for New Issuer Module over the base period, option period 1, option period 2 - in terms of number of users, growth in data volumes

This information is not available.

182 C.3.02 Are there any known performance related issues with New Issuer Module - such as online response times, batch processing windows, etc

There are no issues at this time.

183 C.3.02 Please mention any known environment/design/architectural issues that make it difficult to extend/enhance New Issuer Module

None, at this time.

Questions and Responses

No. Section Question Response 184 C.3.02 Please provide the list of enhancements that are planned for New Issuer Module over the next 12 months

None, at this time.

185 C.3.02 Please provide a list of third party software licenses that are required for New Issuer Module.

Also mention the estimated annual licensing cost and indicate whether these licenses are transferable

See Attachment B

186 C.3.02 Please provide the requisite service level agreements ( transaction processing speed, report generation speed, batch processing) for Pool Transfer Module

There are no SLAs for the Pool Transfer module which is part of IPMS.

187 C.3.02 Please provide hardware deployment information (servers, firewalls, etc) for Pool Transfer Module -across dev, qa and prod environments. Also mention any special requirements such as failover, load balancing, replication, etc

The Offeror has to define transition activities related to hardware deployment, failover and replication as part of the response to the RFP. The transition cannot disrupt Ginnie Mae operations.

188 C.3.02 Please provide the system security categorization for Pool Transfer Module

This is a module of IPMS. IPMS is Moderate.

189 C.3.02 Please provide system utilization statistics (CPU, virtual memory, etc) for Pool Transfer Module

We do not have separate system utilization statistics for the Pool Transfer Module.

190 C.3.02 Please specify data archival requirements (frequency, data volumes, etc) for Pool Transfer Module

The Pool Transfer Module within IPMS is archived nightly.

191 C.3.02 Please provide availability requirements (24X7, 24X5, etc) for Pool Transfer Module

The IPMS application is available from 7:00 AM thru 6:00 PM Monday through Friday.

Batch processing takes place nightly.

192 C.3.02 Please provide sizing parameters for Pool Transfer Module - no. of screens, no. of batches,

no. & size of tables/files, etc

VFP framework - Flash Mgt – 596 files, 188 program files, 66 forms libraries, 53 reports,73 VFP DB files 149 MB

Questions and Responses

No. Section Question Response 193 C.3.02 Please provide interface details for Pool Transfer

Module - no. of interfaces, interface type (file, synchronous calls, asynchronous calls, etc), data transfer volumes

Citrix (Ginnie Mae Staff, BNY Operations), CONNECT: Direct

194 C.3.02 Please provide usage parameters (average & peak levels) for Pool Transfer Module -transactions per day, concurrent users, response times

There are about 20 users. The transactions are minimal.

195 C.3.02 Please mention the average number of support/enhancement requests (per month) for Pool Transfer Module.

There has been one or less requests for the Pool Transfer Module.

196 C.3.02 Please provide estimated growth statistics for Pool Transfer Module over the base period, option period 1, option period 2 - in terms of number of users, growth in data volumes

This information is not available.

197 C.3.02 Are there any known performance related issues with Pool Transfer Module - such as online response times, batch processing windows, etc

There are no known issues

198 C.3.02 Please mention any known environment/design/architectural issues that make it difficult to extend/enhance Pool Transfer Module

Application platform nearing end of life

199 C.3.02 Please provide the list of enhancements that are planned for Pool Transfer Module over the next 12 months

None

200 C.3.02 Please provide a list of third party software licenses that are required for Pool Transfer Module. Also mention the estimated annual licensing cost and indicate whether these licenses are transferable

See Attachment B

201 C.3.02 Please provide the requisite service level agreements ( transaction processing speed, report generation speed, batch processing) for Unclaimed Funds System

There are no SLAs for the Unclaimed Funds system.

Questions and Responses

No. Section Question Response 202 C.3.02 Please provide hardware deployment information

(servers, firewalls, etc) for Unclaimed Funds System - across dev, qa and prod environments.

Also mention any special requirements such as failover, load balancing, replication, etc

The Offeror has to define transition activities related to hardware deployment, failover and replication as part of the response to the RFP. The transition cannot disrupt Ginnie Mae operations.

203 C.3.02 Please Provide the system security categorization for the Unclaimed Funds System

Moderate

204 C.3.02 Please provide system utilization statistics (CPU, virtual memory, etc) for Unclaimed Funds System

System utilization statistics are not available for Unclaimed Funds System.

205 C.3.02 Please specify data archival requirements (frequency, data volumes, etc) for Unclaimed Funds System

The Unclaimed Funds System is archived nightly.

206 C.3.02 Please provide availability requirements (24X7, 24X5, etc) for Unclaimed Funds System

The application is available from 7:00 AM thru 6:00 PM Monday through Friday. Batch processing takes place nightly.

207 C.3.02 Please provide sizing parameters for Unclaimed Funds System - no. of screens, no. of batches,

no. & size of tables/files, etc

45 form libraries, 5 program files, 40 report files, 71 VFP DB files, 191 MB

208 C.3.02 Please provide interface details for Unclaimed Funds System - no. of interfaces, interface type (file, synchronous calls, asynchronous calls, etc), data transfer volumes

The Unclaimed Funds System interfaces with the PPA's LAN.

209 C.3.02 Please provide usage parameters (average & peak levels) for Unclaimed Funds System -transactions per day, concurrent users, response times

There are about 5 users with minimal transaction

210 C.3.02 Please mention the average number of support/enhancement requests (per month) for Unclaimed Funds System.

There has been one or less requests for the Unclaimed Funds System.

Questions and Responses

No. Section Question Response 211 C.3.02 Please provide estimated growth statistics for

Unclaimed Funds System over the base period, option period 1, option period 2 - in terms of number of users, growth in data volumes

This information is not available.

212 C.3.02 Are there any known performance related issues with Unclaimed Funds System - such as online response times, batch processing windows, etc

There are no issues at this time.

213 C.3.02 Please mention any known environment/design/architectural issues that make it difficult to extend/enhance Unclaimed Funds System

Application platform nearing end of life

214 C.3.02 Please provide the list of enhancements that are planned for Unclaimed Funds System over the next 12 months

None

215 C.3.02 Please provide a list of third party software licenses that are required for Unclaimed Funds System. Also mention the estimated annual licensing cost and indicate whether these licenses are transferable

See Attachment B

216 C.3.02 Please provide the requisite service level agreements ( transaction processing speed, report generation speed, batch processing) for REMIC & Platinum Securities Search Pages

There is no SLA particular for this application

217 C.3.02 Please provide hardware deployment information (servers, firewalls, etc) for REMIC & Platinum Securities Search Pages - across dev, qa and prod environments. Also mention any special requirements such as failover, load balancing, replication, etc

The Offeror has to define transition activities related to hardware deployment, failover and replication as part of the response to the RFP. The transition cannot disrupt Ginnie Mae operations.

218 C.3.02 Please provide the system security categorization for the REMIC & Platinum Securities Search Pages

This is a module of IPMS. IPMS is Moderate.

219 C.3.02 Please provide system utilization statistics (CPU, virtual memory, etc) for REMIC & Platinum Securities Search Pages

Separate system utilization statistics are not available for the REMIC and Platinum Securities Search Pages.

Questions and Responses

No. Section Question Response 220 C.3.02 Please specify data archival requirements

(frequency, data volumes, etc) for REMIC & Platinum Securities Search Pages

REMIC and Platinum Securities search pages are archived nightly.

221 C.3.02 Please provide availability requirements (24X7, 24X5, etc) for REMIC & Platinum Securities Search Pages

24x7

222 C.3.02 Please provide sizing parameters for REMIC & Platinum Securities Search Pages - no. of screens, no. of batches, no. & size of tables/files, etc

5 Web Pages, batch and database included in GinnieNET

223 C.3.02 Please provide interface details for REMIC & Platinum Securities Search Pages - no. of interfaces, interface type (file, synchronous calls, asynchronous calls, etc), data transfer volumes

Web, CONNECT: Direct

224 C.3.02 Please provide usage parameters (average & peak levels) for REMIC & Platinum Securities Search Pages - transactions per day, concurrent users, response times

The average is about 500 hits per day

225 C.3.02 Please mention the average number of support/enhancement requests (per month) for REMIC & Platinum Securities Search Pages.

There were two or less requests for REMIC & Platinum Securities Search Pages.

226 C.3.02 Please provide estimated growth statistics for REMIC & Platinum Securities Search Pages over the base period, option period 1, option period 2 -in terms of number of users, growth in data volumes

This information is not available.

227 C.3.02 Are there any known performance related issues with REMIC & Platinum Securities Search Pages such as online response times, batch processing windows, etc

There are no known issues

228 C.3.02 Please mention any known environment/design/architectural issues that make it difficult to extend/enhance REMIC & Platinum Securities Search Pages

None

Questions and Responses

No. Section Question Response 229 C.3.02 Please provide the list of enhancements that are planned for REMIC & Platinum Securities Search Pages over the next 12 months

None

230 C.3.02 Please provide a list of third party software licenses that are required for REMIC & Platinum Securities Search Pages. Also mention the estimated annual licensing cost and indicate whether these licenses are transferable

See Attachment B

231 C.3.02 Please provide the requisite service level agreements ( transaction processing speed, report generation speed, batch processing) for REMIC Database

There is no SLA particular for this application

232 C.3.02 Please provide hardware deployment information (servers, firewalls, etc) for REMIC Database -across dev, qa and prod environments. Also mention any special requirements such as failover, load balancing, replication, etc

The Offeror has to define transition activities related to hardware deployment, failover and replication as part of the response to the RFP. The transition cannot disrupt Ginnie Mae operations.

233 C.3.02 Please provide the system security categorization for the REMIC Database

This is a module of IPMS. IPMS is Moderate.

234 C.3.02 Please provide system utilization statistics (CPU, virtual memory, etc) for REMIC Database

Runs on a server shared with other applications. Cannot isolate.

235 C.3.02 Please specify data archival requirements (frequency, data volumes, etc) for REMIC Database

The REMIC database is archived nightly.

236 C.3.02 Please provide availability requirements (24X7, 24X5, etc) for REMIC Database

24x7

237 C.3.02 Please provide sizing parameters for REMIC Database - no. of screens, no. of batches, no. & size of tables/files, etc

This overlaps with the REMIC & Platinum Search above. 5 Web Pages, batch and database included in GinnieNET

Questions and Responses

No. Section Question Response 238 C.3.02 Please provide interface details for REMIC

Database - no. of interfaces, interface type (file, synchronous calls, asynchronous calls, etc), data transfer volumes

Web, CONNECT: Direct

239 C.3.02 Please provide usage parameters (average & peak levels) for REMIC Database - transactions per day, concurrent users, response times

The average is about 1500 hits per day

240 C.3.02 Please mention the average number of support/enhancement requests (per month) for REMIC Database.

There was less than one request for the REMIC Database.

241 C.3.02 Please provide estimated growth statistics for REMIC Database over the base period, option period 1, option period 2 - in terms of number of users, growth in data volumes

This information is not available.

242 C.3.02 Are there any known performance related issues with REMIC Database - such as online response times, batch processing windows, etc

There are no issues at this time.

243 C.3.02 Please mention any known environment/design/architectural issues that make it difficult to extend/enhance REMIC Database

None

244 C.3.02 Please provide the list of enhancements that are planned for REMIC Database over the next 12 months

None

245 C.3.02 Please provide a list of third party software licenses that are required for REMIC Database.

Also mention the estimated annual licensing cost and indicate whether these licenses are transferable

See Attachment B

246 C.3.02 Please provide the requisite service level agreements ( transaction processing speed, report generation speed, batch processing) for IPMS-New Pool Processing Module

There is no SLAs for IPMS. Please refer to RFP for specific timelines for processing.

Questions and Responses

No. Section Question Response 247 C.3.02 Please provide hardware deployment information

(servers, firewalls, etc) for IPMS-New Pool Processing Module - across dev, qa and prod environments. Also mention any special requirements such as failover, load balancing, replication, etc

The Offeror has to define transition activities related to hardware deployment, failover and replication as part of the response to the RFP. The transition cannot disrupt Ginnie Mae operations.

248 C.3.02 Please provide the system security categorization for the IPMS-New Pool Processing Module

IPMS is moderate. New Pool Processing is not evaluated separately from IPMS.

249 C.3.02 Please provide system utilization statistics (CPU, virtual memory, etc) for IPMS-New Pool Processing Module

We do not have separate system utilization statistics for the Pool Reporting Module.

250 C.3.02 Please specify data archival requirements (frequency, data volumes, etc) for IPMS-New Pool Processing Module

Currently data is archived nightly for IPMS.

There are not separate requirements for Pool Processing.

251 C.3.02 Please provide availability requirements (24X7, 24X5, etc) for IPMS-New Pool Processing Module

IPMS, which includes the Pool Processing module, is currently available to Ginnie Mae 7am to 6pm Eastern time.

252 C.3.02 Please provide sizing parameters for IPMS-New Pool Processing Module - no. of screens, no. of batches, no. & size of tables/files, etc

Please see answer for IPMS-Pool Reporting Module

253 C.3.02 Please provide interface details for IPMS-New Pool Processing Module - no. of interfaces, interface type (file, synchronous calls, asynchronous calls, etc), data transfer volumes

Please see answer for IPMS-Pool Reporting Module

254 C.3.02 Please provide usage parameters (average & peak levels) for IPMS-New Pool Processing Module - transactions per day, concurrent users, response times

Please see answer for IPMS-Pool Reporting Module

255 C.3.02 Please mention the average number of support/enhancement requests (per month) for IPMS-New Pool Processing Module.

Please see answer for IPMS-Pool Reporting Module

Questions and Responses

No. Section Question Response 256 C.3.02 Please provide estimated growth statistics for

IPMS-New Pool Processing Module over the base period, option period 1, option period 2 - in terms of number of users, growth in data volumes

There are no growth statistics for the Pool Reporting System. There are currently less than 100 user ids for IPMS mainframe access for Ginnie Mae and contractor staff.

257 C.3.02 Are there any known performance related issues with IPMS-New Pool Processing Module - such as online response times, batch processing windows, etc

IPMS, and Pool Processing which is part of IPMS, has no performance issues currently.

258 C.3.02 Please mention any known environment/design/architectural issues that make it difficult to extend/enhance IPMS-New Pool Processing Module

IPMS is a legacy COBOL/Db 2 application that will be rewritten during the base period of the contract, in order to utilize more current technology. Legacy source code documentation is available in Binders 10, 11,13, 14, 14 (a), 15, 15(a), 16, 17, 17 (a) and 22 in the Ginnie Mae reading room.

259 C.3.02 Please provide the list of enhancements that are planned for IPMS-New Pool Processing Module over the next 12 months

Currently there are no new requirements identified, however Ginnie Mae may obtain additional requirements during that period that may require change.

260 C.3.02 Please provide a list of third party software licenses that are required for IPMS-New Pool Processing Module. Also mention the estimated annual licensing cost and indicate whether these licenses are transferable

There is no third party software associated with IPMS.

261 C.3.02 Please provide the requisite service level agreements ( transaction processing speed, report generation speed, batch processing) for Master Agreement Database

There is no SLAs for IPMS. Please refer to RFP for specific timelines for processing.

262 C.3.02 Please provide hardware deployment information (servers, firewalls, etc) for Master Agreement Database - across dev, qa and prod environments. Also mention any special requirements such as failover, load balancing, replication, etc

The Offeror has to define transition activities related to hardware deployment, failover and replication as part of the response to the RFP. The transition cannot disrupt Ginnie Mae operations.

263 C.3.02 Please provide the system security categorization for the Master Agreement Database

IPMS is moderate. Master Agreement Module is not evaluated separately from

IPMS.

Questions and Responses

No. Section Question Response 264 C.3.02 Please provide system utilization statistics (CPU, virtual memory, etc) for Master Agreement Database

We do not have separate system utilization statistics for the Master Agreement Module.

265 C.3.02 Please specify data archival requirements (frequency, data volumes, etc) for Master Agreement Database

Currently data is archived nightly for IPMS.

There are not separate requirements for Master Agreement Module.

266 C.3.02 Please provide availability requirements (24X7, 24X5, etc) for Master Agreement Database

The Master Agreement Module with in IPMS is available 24x7.

267 C.3.02.01 What is the business/financial impact that is driving the desired Recovery Time Objective (RTO) of 4 hours or less?

The ability for Ginnie Mae to conduct business on a daily basis.

268 C.3.02.01 What is the current Disaster Recovery solution being provided by the current provider partner?

This proprietary information, therefore the information cannot be made available.

269 C.3.02.01 Are there any Memorandum of Agreement/Memorandum of Understanding/Interconnected Services Agreement (MOA/MOU/ISA) with other parties that we need to take into consideration (i.e.

Federal Reserve Bank)?

Two: FRBNY is the depository and MERS is the mortgage electronic registry system.

270 C.3.02.01 The paragraph on COOP references Ginnie Mae's essential business Processes. Please describe the essential processes.

Pool Processing and Payment Functionalities

- Issuance of Securities, RPB Collection, Payments to Security Holders etc.

271 C.3.02.03 Within the RFP, there is no reference in section L to describe where we should address tasks related to conferences, training, travel, and technical assistance; will you consider adding additional pages?

No special requirements exist that would require additional pages. Preparation for these tasks would be fulfilled in cooperation with Ginnie Mae.

Questions and Responses

No. Section Question Response 272 C.3.03 This section requires contractor to perform daily cash reconciliation of funds paid according to fee schedule. Is this a data reconciliation? How does the process work?

When a request for Commitment Authority has been received by the Contractor, the Offeror verifies with Ginnie Mae, Office of Finance that the proper commitment fee has been received by Ginnie Mae. Once verified that the proper fees have been paid the Contractor puts the Commitment Authority request on hold in IPMS for processing by a Ginnie Mae Account Executive. Daily the Contractor performs a reconciliation that the proper amount of funds have been received for the amount.

273 C.3.03 What functions does the PPA/CPTA need to perform to assist Ginnie Mae with new Issuer applications?

Largely the PPA/CPTA process required Ginnie Mae Agreements, and enroll Issuers on Ginnie NET, etc.

274 C.3.03.01 Paragraph (h) requires the Contractor to acquire and maintain a site license for Geo Scan Libraries. What is the cost of that license?

Offeror should inquire with Geo Scan for licensing costs.

275 C.3.03.01 Is the Contractor required to have any other site licenses besides Geo Scan Libraries? If so, what are they, and what do they cost?

The Offeror needs to determine what Site Licenses are needed for their operations and contact the appropriate vendor for pricing..

276 C.3.03.01 What are the Geo Scan Libraries system requirements?

Offeror should inquire with Geo Scan for system requirements.

277 C.3.03.02 In this section, and in a number of other sections, time deadlines are stated in Eastern Standard Time. Is Eastern Daylight Time applicable when Daylight Savings Time is in effect?

No. Daylight Savings Time would take precedence.

278 C.3.03.02 Do both the IPMS and GinnieNET edit checks verify that the pool is in compliance with the Ginnie Mae Guide? Are they in sync with each other?

Yes; GinnieNET edits provide both soft (warning) edits and hard edits (Pool Processing Cancelled) to alert both the Issuer and Ginnie Mae of potential pooling abnormalities.

Questions and Responses

No. Section Question Response 279 C.3.03.02 Is there any special processing required related to HECMs? If so, can you provide the relevant documentation?

Yes. See Chapter 35 and Appendixes III-28 and VI-17 of the MBS Guide

280 C.3.03.03 Please clarify the following discrepancy between Sections B.5 and C.3: in Section C.3.03.03,the task references CLIN 201; however, there is no CLIN 201 listed in Section B.5.

The reference to CLIN 201 should be 0202

281 C.3.03.04 Please clarify the following discrepancy between Sections B.5 and C.3: in Section C.3.03.04, the task references CLIN 201; however, there is no CLIN 201 in Section B.5.

The reference to CLIN 201 should be 0202

282 C.3.03.04 Are all transfer of servicing requests submitted through GinnieNET? If not, please describe the ways in which they can be submitted.

All transfer requests are communicated by letter correspondence. See Chapter 21-8 of the MBS Guide.

283 C.3.03.05 Please clarify the following discrepancy between Sections B.5 and C.3: in Section C.3.03.05, the task references CLIN 201; however, there is no 201 listed in Section B.5.

The reference to CLIN 201 should be 0202

284 C.3.03.05 Should the reference in Paragraph (g) to "Data Collection and Risk Management Agent" read "MBS Administration Agent"?

Yes.

285 C.3.03.05 Does IPMS assign the CUSIP numbers to a pool or is there another system or manual process?

The New Pool Processing module assigns the CUSIP number.

286 C.3.03.06 Please clarify the discrepancy between Sections B.5 and C.3: in Section C.3.03.06, the task references CLIN 201; however there is no CLIN 201 listed in Section B.5.

The reference to CLIN 201 should be 0202

287 C.3.03.07 Is the prospectus for the multiple issuer pool generated from IPMS or another Ginnie Mae system?

The prospectus is generated by GinnieNET.

Questions and Responses

No. Section Question Response 288 C.3.03.08 What are the required hours of operations and days of the week for the Help Desk?

Customer Service Help Desk is 5 days a week from 8:30 AM - 4:30 PM EST, GinnieNET Help Desk is also 5 days a week from 8:00 AM - 7:00 PM EST, New Pool Help Desk 5 days a week from 9:00 AM - 5:00 PM EST, Multiclass Help Desk 5 days a week from 9:00 AM - 5:00 PM EST

289 C.3.03.08 What methods of communication are required to be available for use contacting the Help Desk?

Email, Telephone, and Fax

290 C.3.04 Who collects fees associated with transfer of servicing?

The contractor collects the fees and wires to Ginnie Mae, Office of Finance.

291 C.3.04 Is there a Ginnie Mae system that tracks fees associated with transfer of servicing?

PTS calculates the amount of the transfer fee, but the rest of the fees are tracked manually.

292 C.3.05 Are there any Uniform Commercial Codes…