B09_QnA_0001.rtf

User Access and Roles: Could you provide more detailed requirements or examples of the different user roles (administrative, read-write/edit, read/view-only) anticipated for managing the ArcGIS web connector software? What specific permissions and capabilities are required for each user role?

Only ArcGIS Online and Enterprise for ArcGIS users with the role of “Administrator” will be allowed administrative, read-write/edit, read/view-only access to the web-based software.

Integration with Existing Systems: Can you provide more details on the expected integration with existing systems, particularly with Microsoft Internet Information Server and Azure storage? Are there specific APIs or data exchange protocols that we need to support for seamless integration?

The tools should integrate with the latest version of Microsoft Internet Information Server, support HTTPS, and interface with ArcGIS Online and ArcGIS Enterprise via their native REST API.

Data Backup and Recovery: What are the detailed requirements for the backup and recovery features, such as the frequency of backups and the retention period for backup data? Can you provide more information on the process for restoring individual items and maintaining GIS Item IDs?

Backup frequency should be on demand or set via a scheduled task. Retention period is user-defined. Restoration of items should be via the same interface. Maintenance of ItemID’s is not a requirement.

GIS Item Management: Could you elaborate on the requirements for viewing and editing GIS item JSON definitions? What specific features are required for managing GIS item dependencies and updating item details?

Item details should be editable through the ESRI native REST API.

User and Content Management: What are the specific functionalities needed for user account management, such as deleting accounts, migrating users, and generating emails to users? Can you provide more details on the requirements for scanning and reporting on user activity and GIS content?

Scanning and reporting requirements are listed in the solicitation.

Scheduled Tasks and Workflows: What types of workflows are expected to be developed and scheduled within the system? Can you provide examples of administrative reports and alerts that need to be generated as scheduled events?

Scheduled task workflow requirements are listed in the solicitation.

Security and Compliance: What are the specific security protocols and compliance requirements, especially regarding the protection of personally identifiable information (PII)? Are there any additional security certifications required for the software?

Any software not already approved by NPS cybersecurity will need to go through the software review process.

Evaluation Criteria: Can you provide more details on how the proposals will be evaluated, particularly the weight given to technical specifications and past performance? Are there specific criteria or benchmarks that need to be met for technical acceptability?

Source selection procedure will be Lowest Price Technically Acceptable

Training and Support: What are the training requirements for the system? Are there specific user groups that require tailored training programs, and what level of ongoing support is expected?

Training is not listed in the requirements

Implementation Timeline: What is the expected timeline for the implementation of the software? Are there any key milestones or deadlines that we should be aware of during the implementation phase?

Completed software should be delivered 30 days after the solicitation period closes.

Cost and Pricing Structure: Are there specific guidelines or templates to follow when completing the cost breakdown? Can you provide examples of acceptable cost justifications for the various items in the cost breakdown?

The contract type will be Firm-Fixed-Price and be awarded to the Lowest Price Technically Acceptable.