Amend_4_Questions_and_AnswersAugust_30.docx
DOCX document 25 KB Posted
- Solicitation number
- AG-7604-S-13-0033
About this file
Questions/Answers dated Aug. 30 2013
View the file
Other files
Show all 29
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
AG-7604-S-13-0033
Questions and Answers August 30, 2013
1. Question: With IPS-1, USDA referenced web-based applications. Please state whether your definition of web-based is accessed:
a) via the web with a desktop smart client? or
b) via web browser only?
Answer: The USDA Forest Service is looking for a solution that is web-based via a web browser. We will not be using any form of a “desktop smart client”.
2. Question: To support the Interfaces requirements, can you provide further details related to the EDI fields for each of the interfaces to be supported? If possible please provide a “real-life” example to help us put this requirement into context for us.
Answer: Pre-defined standard data fields (i.e., Name, SSN, Injury Type, Source Code, etc.) will be transferred between the selected solution and the DOL Data Repository (DDR) API using industry standard Web Services Description Language (WSDL) and XML to communicate. In addition, we have included all relevant information for the interfaces in the SOO Section 12, Attachment D and Attachment E.
3. Question: To support the Interfaces requirements, can you provide a high level process description for how the bi-directional and inbound only interfaces will operate for each of the interfaces listed (i.e. DOL, DOL OWCP, EmpowHR, T&A, CRM, EMIS, GSA, GovTrip)?
Answer: We have included all relevant information for the interfaces in the SOO Section 12, Attachment D and Attachment E. As stated in the SOO Section 12, the offeror’s capability to meet mandatory and critical interfaces will be required as part of the evaluation process. Therefore we have only addressed the mandatory and critical interface requirements below.
High Level Process Description
| How Bi-Directional Interface will operate? |
| How Inbound Only Interface will operate? |
| DOL |
| Pre-defined standard data fields will be transferred between the selected solution and the DOL Data Repository (DDR) API using industry standard Web Services Description Language (WSDL) and XML to communicate |
| DOL OWCP |
| Same as DOL above |
EmpowHR
Uploaded biweekly via flat file, File Transfer Protocol (FTP), API or other Web services
T&A uploaded biweekly via flat file, File Transfer Protocol (FTP), API or other Web services
| CRM |
| Standard Oracle application; Information will be transferred via a nightly feed |
| EMIS |
| Useful requirement |
| GSA |
| Useful requirement |
| GovTrip |
| Useful requirement |
4. Question: Will the use of SAML 2.0. be considered to support SSO?
Answer: Currently, ConnectHR's SSS API is not built using SAML 2.0. The current API is built on other industry standard implementations using WSDL, SOAP, and XML Web Services. If there is a new requirement for ConnectHR to provide an implementation using SAML 2.0, the Level of Effort would have to be researched and developed, and the Level of Effort discussed with Forest Service and other clients.
5. Question: Can you provide the Section 508 compliant guidelines utilized by the Target Center?
Answer: The USDA Target Center guidelines for website accessibility can be found on the USDA website at http://www.dm.usda.gov/oo/target/subjects/508/reqs.html. For a complete list of the 508 Standards, including the official text of the Web Requirements, please visit http://www.section508.gov.
6. Question: What 508 testing tools are utilized by the Target Center?
Answer: See response to question 5.
7. Question: Can you expand on what the special data entry techniques are for requirement IPS-265? If not, can you provide us with resources about requirement IPS-265?
Answer: Aviation has an MS Excel database of aviation incidents. In addition, the Aviation official Safety notification system would need to link notifications to the appropriate incident. Typically the notification is an email message linked to a MS Word or PDF document posted to a web site. These notifications would be uploaded to the aviation incident record as supporting documentation. This would be an as-needed action, not an automated action.
8. Question: The term “mature” in reference to the solution is a somewhat subjective term open to interpretation. Please provide some context or an example of how you envision a “mature” solution functioning.
Answer: We are looking for a mature system, and by mature we mean a system that is in use (i.e., in production) within another government agency or private organization and that allows full end-to-end integration from point of incident to submission of related WC claim data to Agency case management activities.
9. Question: For the purposes of meeting submission requirements, please confirm there is no page limitation for:
a) Volume II. Mission Capability, Management Section
b) Volume II. Mission Capability, Transition Section
c) If a page limitation exists. Please specify that requirement for each section mentioned in 9a and 9b above.
Answer: For volume II Mission Capability, there is a page limitation. Technical, Transition and Management all fall under Mission Capability. The page limitation is thirty (30) pages all inclusive for Technical, Transition and Management. The page limit can be found on page 16 of the RFP. There is also a 2 page limit for the executive summary under Volume II of Mission Capability.
File details come from the government source that posted it. Updated .