SMP Software SOW March 2020.docx

*MARKET RESEARCH* SOURCES SOUGHT NOTICE

FOR

Strategic Weapons Facility-Atlantic, Strategic Weapons Facility, Atlantic, Surveillance and Monitoring Program (S&MP)

This is a SOURCES SOUGHT notice. This notice is NOT A Request for Proposal (RFP). No solicitation exists at this time. The Strategic Weapons Facility, Atlantic (SWFLANT) seeks a Firm-Fixed Price (FFP) type contract to provide Commercial off-the-shelf (COTs) software or Microsoft SharePoint 2016/2019 compatible solution for our surveillance and monitoring program (S&MP) requirements that will be the central system for tracking monitors, surveillances, evaluations, discrepancies, and findings for Strategic Weapons Facility Atlantic. The statement of work will require the design, production or procurement, delivery, installation, configuration, testing and acceptance of all components of the final solution.

The applicable NAICS code for this requirement is 541519. The Product Service code is D318.

PURPOSE OF NOTICE: The Sources Sought is being used as a Market Research tool to determine potential sources prior to determining the method of acquisition and issuance of a possible RFP. The Government is not obligated and will not pay for any information received from potential sources as a result of this notice. We are only requesting capability statements from potential contractors at this time.

RESPONSE DEADLINE: Interested sources shall submit a capability package by 12:00PM (est) on 06 April 2020, (15 pages or less) containing: 1) Company Name and Address, 2) Company Point of Contact, 3) Email Address, 4) Phone Number, 5) specifics addressing the tasking listed below and company's capability, 6) specifics addressing existing subject matter expertise on VOIP conduit, 7) related past performance and 8) general corporate information. Facilities and US citizen personnel must have a Secret Clearance or higher, and be International Traffic in Arms Regulations (ITAR) compliant. In addition, prospective sources should be able to receive, generate, modify and store classified documentation.

Responders should indicate which portions of their response are proprietary and should mark them accordingly. Failure to provide a response does not preclude participation in any possible future competitive RFP for which a business is eligible to participate in, if any is issued. It is the responsibility of the interested businesses to monitor the FEDBIZOPS website for additional information pertaining to any potential acquisition and provide security clearances if necessary, to perform the statement of work (SOW).

Electronic responses are acceptable if prepared in Microsoft 2010 compatible format; Email electronic responses to Yvette Tullock (email: SPK12contracts@swflant.navy.mil) with "Sources Sought" in the subject line of the Email.

PERIOD OF PERFORMANCE: To be determined.

Contracting Office Address: Ms. Yvette Tullock, Contracting Officer, 1150 USS Los Angeles RD, Kings Bay, GA 31547-2634

Place of Performance: SWFLANT, Kings Bay, GA 31547

1.0 OBJECTIVE:

This project involves providing an enterprise Commercial off-the-shelf (COTs) software or Microsoft SharePoint 2016/2019 compatible solution for our surveillance and monitoring program (S&MP) requirements that will be the central system for tracking monitors, surveillances, evaluations, discrepancies, and findings for Strategic Weapons Facility Atlantic. The statement of work will require the design, production or procurement, delivery, installation, configuration, testing and acceptance of all components of the final solution.

2.0 SCOPE:

The milestones and deliverables in the following requirements will be implemented and thoroughly discussed with the Contracting Officer and the Government Technical Representative (GTR).

2.1 Installation Timeframe: The solution must be installed, tested and user accepted before the end of fiscal year 2020.

2.2 Design Efforts required: The contractor shall design, fabricate, integrate, test, and evaluate the software and the principle items necessary to satisfy program development requirements, and to support and operate the system. This includes the requirements analysis, design, coding and unit testing, component integration and testing, and Computer Software Configuration Item (CSCI) level testing for software. This also includes system development and Operational Test and Evaluation (OT&E), software quality, Configuration Management, and support for software. The contractor shall define a Software Development Approach appropriate for the computer software development and integration effort to be performed under this solicitation. The contractor shall document the software development approach in a SDP, shall implement the SDP requirements, and shall maintain the SDP. The contractor shall implement selected Software Metrics to provide management visibility into the software development process and progress. The contractor shall apply core software metrics, as a minimum. The selected metrics shall clearly portray variances between actual and planned performance, shall provide early detection or prediction of situations that require management attention, and shall support the assessment of the impact of proposed changes on the program. The contractor shall provide the program office routine insight into these metrics.

2.3 Software requirements:

· Software must be DON Cybersecurity RMF accreditable

· Software must have on-premise installation capability, off-premise or hybrid cloud based only software is not acceptable

· Preferred Commercial off-the-shelf product

· Real-time updates; data entered should be immediately available to all users

· Software Assurance and maintenance support available

· Must be capable of functioning within a virtualized environment

· Data cannot be accessed outside of the network environment

· Software must be compatible to run in a Microsoft Server/Desktop OS environment

· Non-repudiation

· Capable of data imports from Microsoft Office products (e.g. Excel, Access)

· User-customized reports and built-in/preconfigured reports with capabilities of graphs, charts

· Concurrent use by a minimum of 20 personnel across internal network

· Data exports via Excel, Text, and PDF

· Form/document filling export to Word, Excel, and PDF

· Role based security with multiple levels of access (e.g. Read-Only, Users, Application Managers)

· Capable of Microsoft Active Directory Integration

· Web-based client interface and does not require client software to be installed on workstations

· E-mail notification capability for workflow process

· Customizable workflow personnel and groups

3.0 SPECFIC TASK REQUIREMENTS:

3.1 General Information: The Surveillance and Monitoring Program S&MP is the authoritative system for tracking monitors, surveillances, evaluations, discrepancies, and findings. As such S&MP will facilitate:

· Assignment of monitors, surveillances and evaluations to personnel.

· Monitors, surveillances and evaluations are derived from templates that are modified for specific assignment, with the specific assignment having a unique identifier assigned.

· Discrepancies or findings found during a monitor, surveillance or evaluation will also be are derived from templates that are modified for specific assignment, with the specific assignment having a unique identifier assigned.

· Ability to add notes, comments, write-ups or supporting documentation in the monitors, surveillances, evaluations, discrepancies or findings.

· Workflow with email notifications to assignees, reviewers, approvers, or other personnel indicated when the assignment is assigned.

· Tracking the current status of all items assigned, ensuring compliance by assigned completion date(s).

· Multiple user types and groups to complete tasking.

S&MP shall have the capability to create multiple segments, to support slightly differing reporting or data gathering requirements, utilizing the customized fields available.

3.2 Submittals:

3.2.1 Post Award:

1. Provide within one (1) week of award:

a. Work Breakdown Structure (WBS)

b. Integrated Master Plan (IMP)

c. Integrated Master Schedule (IMS)

d. Software Development Plan (SDP)

e. Software Quality Assurance Plan

f. User Acceptance Test (UAT) Plan

a. To include a Requirements Traceability Matrix (RTM)

g. Host environment Requirements Document

a. To include hardware, software, and connection requirements for the software host environment.

3.3 Deliverables: Any deliverables under this SOW will be accepted or rejected in writing by the GTR. If a custom application is the final solution, the Contractor warrants against latent defects for a period of two years all analysis, designs, plans and specifications produced under this SOW. Such products will be accepted on an interim basis for payment, but must perform satisfactorily from period of acceptance date for 12 months. During this period the GTR (or designee) will have the right to reject or require correction of any deficiencies found in the deliverable that are contrary to the information contained in the Contractor's accepted proposal at no additional cost to the government. In the event of rejection of any deliverable, the Contractor will be notified by the GTR of the specific reasons why the deliverable is being rejected. Deficiencies discovered within this period will be articulated by the government and the Contractor shall correct them within a period of 28 calendar days. Services will be requested and controlled by means of written/verbal descriptions of specific requirements for each task, which will delineate specific objectives, deliverables and information protection and system security (IPASS) issues and controls as required. The Contractor shall be responsible for delivering all end items specified in the work request. Specific acceptance criteria, delivery schedules, and delivery instructions will be included in for each task where necessary. Services will be requested and controlled by means of production logs, which will delineate all processed deliverables. The Contractor shall be responsible for delivering all end items specified in the procedures as well as production logs. When workload exceeds the production capabilities of the Contractor staff, priorities will be annotated by the government to ensure that critical tasks are completed in a timely manner. The following are deliverables that fall within the scope of this SOW and are illustrative of some of the types of work the Government expects to order:

1. System requirements documentation

2. System specifications documentation

3. Program specification documentation

4. Data analysis

5. Software maintenance

6. Quality assurance and quality control analysis and documentation

7. System/program test plan and analysis report

8. System software quality assurance report

9. Joint application design reports

10. Telecommunications, network and system analysis reports.

11. Source Code, if applicable

3.4 Software Component Requirements: See enclosure 1.

3.5 Warranty: Warranty information provided needs to indicate the length, what is covered, if labor services are covered, and the usage that warranty covers (24/7 or 8 hour work day, etc.)

1. The Contractor shall ensure minimum warranty is 12 months.

4.0 EXECUTION:

4.1 Installation:

1. All items shall be installed by certified installers in accordance with manufacturer's recommended installation instructions.

2. The final software installation will be accomplished in one phase. This will include software installation, user acceptance testing and verification, administrative and user training, and media/artifacts delivery.

4.2 Scope of Inspection:

4.2.1 All deliverables will be inspected for content, completeness, accuracy and conformance to SOW requirements by the GTR. Inspection may include validation of information or software through the use of automated tools and/or testing of the deliverables, as specified in the SOW. The scope and nature of this testing must be negotiated prior to SOW award and will be sufficiently comprehensive to ensure the completeness, quality and adequacy of all deliverables.

4.2.2 The Government requires a period of not to exceed fifteen (45) work days after receipt of final deliverable items for inspection and acceptance or rejection.

4.2.3 User Acceptance Testing (UAT): The Government will perform acceptance testing of the new systems’ code and/or database changes/additions after successful completion of Contractor testing. The Contractor shall prepare or update a User Acceptance Test (UAT) plan and test scenarios/scripts for users to follow during the initial structured portion of the UAT (following structured testing the users are encouraged to conduct their own free-form testing). The Contractor shall assist the Government during the preparation and execution of the acceptance test by establishing test data and maintaining the test environment. The Contractor shall provide the draft version of all documentation, including the Requirements Traceability Matrix (RTM), which shall be delivered with the final product at the time of the initiation of the UAT period. The RTM shall clearly link the new and/or changed requirements to where and how they have been implemented in the system, to assist the users during testing. The Contractor shall correct any errors identified by the User Acceptance Test team. The Contractor shall document the results of the testing in the Test Report. Upon receipt of the report, the Government will examine the test results and make a determination as to the readiness of the new systems’ code and/or database changes/additions to be released into the production environment. The Government will certify the planned release under one of the following categories: It is virtually error free and should be released into production. Errors still exist that should be addressed, however, a decision could be made that either: a. the release can proceed intact and the errors will be corrected and implemented through a subsequent release or, b. the release can proceed but the portions determined defective will be removed from it and errors will be corrected and implemented through a subsequent release. It has major shortcomings and should not be released into production at this time. Instead, it should be returned for further development and re-testing.

4.2.4 Releases: Once the Government has performed UAT and final system performance load and stress testing has been completed, the product shall be released to the customer, along with all associated documentation required for the release. This shall include the provision of production and test ID(s) and Password(s) and the necessary software code. The Contractor shall prepare and manage the Release Package to include, notes to document the fixes/changes/enhancements included in each system release, technical release instructions, scripts, schedule, and other documentation.

5.0 Special Provision: All contract employees working onsite supporting this task must be US Citizens and capable of obtaining a favorable NCIC check.

Enclosure 1

S&MP Functionality Requirements

S&MP runs as described below:

· Various surveillance and monitoring formats exist and conform to multiple program requirements

· Capability to create multiple segments, to support slightly differing reporting or data gathering requirements, workflow processes, sets of templates, and assign different user roles to manage each segment.

· Capability for customizable role based security with multiple levels of access and assign user roles based on Active Directory accounts.

· All forms will have the ability to be customized with a set of characteristics and saved for use by other user roles as templates.

· Form characteristics provided in section below.

· Surveillance and monitoring forms require ability to have user defined routing/review process per saved form template.

· All forms will have the capability to be tracked by user roles assigned to form, (e.g. user assigned to, user who assigned, user who modified).

· Capability for forms to be assigned user defined status’s during workflow (e.g. Assigned, Initiated, Completed, Open, Recommended for Closure, Closed)

· Capability to define user roles to be notified as forms move through their workflows at change of status or when predefined actions occur.

· Capability for a built in change request feature for requests for modifications to finalized forms, templates, or groups.

· Change request process will have user customizable workflow capability, defined by segment.

· Capability for a built in scheduling feature for planning and workload management, for forms with periodicity characteristic defined.

· Ability to query data within system to create custom reports.

· Reports will have ability to be displayed as charts/graphs based on queried data.

· User defined roles will have the ability to create and save custom reports.

· Capability to export forms to various output sources, (e.g. Print, Word, Excel, PDF)

Form characteristics required:

· Capability for user defined form characteristics, (e.g. Date completed, category, location, operation, user name, references, date closed, department assigned, description).

· Capability to define what roles have ability to create, modify, assign, and close this type of form.

· Capability to define form types (e.g. SI, PM, OFI, Deficiency)

· Capability to link other system created forms for use or reference when completing a surveillance or monitor.

· Capability to import data or documents from various import sources, (e.g. Word, Excel, PDF)

· Forms that are assigned to a user role, but not initiated will automatically update as associated documents, characteristics, forms, templates are updated.

· All assigned forms will have a unique identification number for tracking.

· Capability for forms to have a defined periodicity.

· Capability to initiate another form type (from the system) if required during the evaluation, that will tie the closing of an evaluation to the closing of the other form type.

· Capability to define form severity codes, (e.g. Minor, Significant, and Critical).

· Capability to save a defined form as a template for reuse.