PWS_82nd_ABN_DIV_Digital_Mass_Notification_03May2017.pdf

82nd AIRBORNE DIVISION DIGITAL MASS NOTIFICATION SYSTEM 03 May 2017

FY17 82nd Digital Mass Notification System

1. General

1.1 Introduction: The contractor shall work in accordance with the design, development, and/or delivery requirements identified in this Performance Work Statement. The product solution for a digital mass notification system will adhere to guidance outlined in the most current publishing of Army Regulation 525-27 Army Emergency Management Program, Chapter 6 and Army Regulation 25-2 Information Assurance.

1.2 Background:

The 82nd Airborne Division is a subordinate unit of XVIII Airborne Corps in Forces Command.

This unit has an inherent 18-hour Global Response Force (GRF) mission that includes, but not limited to: one Brigade-sized element with a Battalion-sized element as an outload support node. This specific mission set places a high-demand for efficiency and time-saving practices.

The 82nd Airborne Division needs to streamline mass notification of a critical mission or emergency event with a digital solution that can engage Paratroopers via personal means like:

cellphone, e-mail, desk phone, social media, iOS/Android application, or text messaging.

1.3. Scope:

The purpose is to provide an Emergency Mass Notification and Response System, as well as maintenance and support for that system. An Emergency Mass Notification and Response System are critical to the 82nd Airborne Division’s mission which must be able to communicate rapidly with up to 19,000 Paratroopers for a no-notice operation or emergency. The system must be a user friendly, “turn-key system” capable of providing geolocation based alerting as well as adhoc group alerting of 82nd Airborne Division Paratroopers; the capability for users to load/import Microsoft Excel data and be able to update alerting groups at user location with minimal steps; and the system should provide a text to voice capability as well as real-time monitoring and can generate reports of status of the alert.

1.3.2. Specific requirements include:

The vendor shall provide a system, maintenance and support that is:

-Located in at least three geographically diverse facilities to ensure adequate backup should the primary facility go down for any reason.

-Able to simultaneously activate personnel via personal E-mail, SMS (texting), voice calls, social media, mobile device application, and computer pop-up screens. (Web and phone based)

-The vendor shall provide maintenance and support for a system that is capable of:

Sending a minimum of 10,000 E-mail messages to the DoD email system.

-Sending a minimum of 10,000 computer “Pop-Up” messages to connected 82ND

AIRBORNE DIVISION Government furnished computers via coordination with the Fort Bragg Network Enterprise Center and 93rd Signal Brigade.

-Sending a minimum of 15,000 E-mail messages to personal email

- Sending a minimum of 1,500 text (SMS) messages to Government furnished mobile phones of various vendors

-Sending a minimum of 15,000 messages to personal cell phone numbers

-Sending a minimum of 10,000 pre-recorded or custom voice messages to Fort Bragg telephone numbers -Sending a minimum of 15,000 messages to personal telephone numbers

-Sending messages to TTY-enabled phones

-Alerting text messages and audio messages on Cisco/ Avaya VOIP phones.

-URL re-direction with website interface.

-Working with the Fort Bragg Network Enterprise Center for grouping computer systems for group notifications.

-Notifying up to 15,000 staff via the media sources listed above, within 3-minutes of the

82nd Airborne Division Duty Officers activating the system.

-Continuously notifying staff until each person responds to at least one message on the media source receiving the notification.

-The notification system must provide real-time status, reporting and acknowledgement of receipt for each media source used and store those acknowledgements for future reference and/or reuse by the 82nd Airborne Division.

-The notification system must be able to be activated by two-factor authentication from any internet location world-wide.

-The notification system must have a twenty four-seven (24x7) 365 days live technical support that can respond to requests for assistance within 10 minutes.

-Hosting facilities must be able to demonstrate 99.999% availability.

-The vendor must provide semi-annual computer based training and two onsite classroom training at the 82nd Airborne Division Headquarters in Fort Bragg, NC on the use of the system for up to 25 Paratroopers and offer training for significant software changes.

-Pop-up notification must be supported on Windows 7, Windows 10, Android 4.1 or greater and iOS.

-Communication with pop-up client software must originate from servers located on the

Fort Bragg’s network.

-System must support LDAP and/or AD groups as activation list

-System must be able to export and import system configuration in XML, CSV, or other standard formats.

-Contractor will provide one (1) year on-site assistance with the system with a minimum 4 hour response time for break-fix.

1.5. Period of Performance:

The period of performance for this contract is from June 01, 2017 through June 02, 2018 with two (2) additional option years.

1.5.A Place of Performance: The vendor must provide semi-annual computer based training and two (2) onsite classroom training at mutually agreed dates after contract award on the use of the system for up to 25 82nd Airborne Division Paratroopers at the headquarters location below:

82nd Airborne Division Headquarters 1 All American Way Building C-7023 Fort Bragg, NC 28303

Equipment, software and hardware will be housed and maintained by the vendor at the facility servicing the 82nd Airborne Division.

2.0. General Requirements

2.0.1. Deliver Quality Products: The contractor shall ensure that all deliverables meet the quality requirements of the base contract. When products are submitted by the contractor for acceptance by the Government, the contractor shall submit reports of testing and certify that quality testing was conducted and that products comply with quality requirements as established under the base contract.

2.0.2 Quality Assurance: The Government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s) (Appendix B).

2.0.3. Software deliverables: All digital notification system graphical user interfaces/ software applications shall be previously tested on target systems by the contractor (e.g. Digital Training Facility or Home-based Computer Configuration).

2.0.4. Required Corrections: The contractor shall deliver T&E products to the Government as required for content review and technical testing. Based on this review, the contractor shall make, at no additional cost to the Government, changes to the digital notification system that the Government identifies as necessary to ensure accuracy, functionality or operability.

2.0.4.1. The standard for implementation of agreed upon changes is 100% implementation of required changes and no new errors in previously reviewed products.

2.0.4.2. If technical faults are discovered within one year of Government final acceptance, the contractor shall correct the reported faults and provide the Government with updated versions of all corrected files in the proper formats for distribution and/or deployment on the internet, and archival.

2.0.5. Protect and Return Government Furnished Materials (GFM), Government Facilities and Government Furnished Information (GFI): Any Government furnished materials or information required for use by the contractor will be identified.

2.0.5.1. GFM and GFI shall be returned to the Government within 15 days after completion of the work.

3.0 Administrative Requirements: Contractor must adhere to administrative Requirements in contract.

3.1. Meetings. The contractor shall conduct Post-Award and In-Process Review (IPR) Meetings as specified within this PWS. The contractor shall provide a proposed Meeting Agenda at least 2 days before each IPR or post award. The contractor shall write minutes of all meetings with input from all concerned, coordinate the minutes with the attendees before departing from the meeting, and provide draft minutes NLT 5 days following the meeting. IPRs may be held at the contractor's facility or the applicable school or agency or another location as stated. Use of video teleconference centers (VTC) and other distance collaboration strategies Defense Connect Online (DCO)https://www.dco.dod.mil/public/dsp/dco_login.cfm?banner=true or phone teleconferences shall be considered for all meetings.

3.1.1. Post-Award Meeting. A Post-Award Meeting shall be conducted within 15 calendar days after the effective date of award. The purpose of the meeting is to discuss GFI, GFM, the milestone schedule, policies, and procedures.

3.1.2. In Process/Progress Review (IPR) Meetings. The contractor shall conduct In-process/progress review meetings to review and discuss technical issues or products and/or to discuss issues that affect product delivery - Government review comments, contractor correction requirements, scheduling problems, milestone schedule, and similar issues.

Proposed IPR schedule will be included in the Milestone Schedule as submitted by the contractor.

3.1.3. Contractor Performance Meetings: The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the Government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced.

Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

3.1.4 Monthly Status Report: The contractor shall submit a status report by the 5th day of the month starting with the effective date of award and continuing until final acceptance of all deliverables. Status reports shall include the current status, the projected completion date (milestone) for each stage of development, and completed/projected contractor travel. The report shall also describe any difficulties or problems encountered, anticipated, or which previously existed that could alter the progression of work. The report shall include recommendations for resolution of problem areas.

3.2 Milestone Schedule: The contractor shall submit a milestone schedule that provides a description of the work processes and timing of work effort from award to completion (acceptance of final products). The schedule shall allow time for and depict all events of contractor performance, Government review, and contractor correction of errors found, resubmission, and acceptance of deliverables. A revised schedule may be approved by the COR provided the end period of performance date does not change. Government review times will be specified.

5.0. Travel: It is anticipated that travel will be required for this contract. The Government will pay up to the rates specified in the Government Federal Travel Regulations (FTR) for travel destination. Documentation/receipts shall be sent to the COR. NO PAYMENT WILL BE MADE

WITHOUT DOCUMENTATION/RECEIPTS.

5.1. Location and number of trips is unknown at this time; however, travel costs shall not exceed the contract line item number (CLIN). Anticipated travel may include: Post Award Meeting, three (3) In Progress Reviews (IPRs), Validation, and a Train the Government Developer (TTGD) work session. Travel must be approved, in advance, by the COR.

6.0. Other Requirements:

7.0. Constraints: The contractor’s solution shall comply with all applicable Government regulations, which include those found in Appendix A and within this PWS.

8.0. Points of Contact for Deliverable Distribution

Contracting Officer (KO):

Ms. Linda McLean linda.f.mclean.civ@mail.mil

Contract Specialist (CS):

SFC Jalila A. Wahid jalila.a.whaid.mil@mail.mil

Integrated Product Team: (All Deliverables)

Contracting Officer Representative (COR):

Technical Representative:

9.0 ORGANIZATIONAL CONFLICT OF INTEREST

9.1 The provisions of FAR 9.5, titled Organizational and Consultant Conflicts of Interest, govern performance under this contract. As stated at FAR 9.502©, an organizational conflict of interest may result when factors create an actual or potential conflict of interest under this contract, or when the nature of the work to be performed under this contract creates an actual or potential conflict of interest on a future acquisition. In the latter case, some restrictions on the future activities of the contractor may be imposed by the Contracting Officer for the future acquisition.

3.2 FAR 9.505 states that the two underlying principles are (a) preventing the existence of conflicting roles that might bias a contractor’s judgment; and (b) preventing unfair competitive advantage. It further states that organizational conflicts of interest may arise in situations covered by FAR 9.505, or the example in FAR 9.508, or in situations not covered by those provisions.

3.3 Under this PWS, the contractor may be required to perform services that trigger the concerns and restrictions described in FAR 9.5. Two examples of such situations and related restrictions applicable to performance hereunder, are set forth below.

3.4 Under this PWS, the contractor may be required to evaluate offers for products or services.

The contractor agrees that it will neither evaluate, nor advise the Government with regard to, its own products or services. In addition, the contractor agrees it will objectively evaluate, and advise the Government concerning, the products or services of its actual or prospective competitors.

4.0 NON-DISCLOSURE

4.1 In the course of performance, the contractor will access nonpublic information, including acquisition sensitive information. The contractor agrees that it will not use or disclose any such information unless authorized by the Contracting Officer.

4.2 The contractor further agrees that it will use its best efforts to ensure that its employees and others performing services under this contract will not use or disclose any such information unless authorized by the Contracting Officer. To that end, contractor agrees that its employees and others performing duties under this contract will sign the Certificate of Nondisclosure.

4.3 By agreeing to this PWS and/or any amendments, the Contractor acknowledges, understands, and accepts the following:

4.3.1 The Contractor and any Subcontractor(s) shall presume that the 82ND AIRBORNE DIVISION computer systems and storage media that the Contractor or Subcontractor access have sensitive information and applications. The Contractor will comply with the contractual security requirements.

4.3.2 Any 82ND AIRBORNE DIVISION information, software, applications, computer systems and hardware accessed by the Contractor in the performance of the requirement remain the sole property of 82ND AIRBORNE DIVISION.

4.3.3 To the extent that any software or applications on the 82ND AIRBORNE DIVISION systems are protected by copyright, the Contractor agrees that it will not copy or disclose them without first obtaining the 82ND AIRBORNE DIVISION’s prior written authorization, which will be provided only where authorized under applicable copyright law.

4.3.4 The Contractor, the Contractor’s employees, and any Subcontractor and Subcontractor’s employees will access, or be provided access to, the 82ND AIRBORNE DIVISION information, software, applications, computer systems and hardware only to the extent necessary, and only for the purpose of, performing the work outlined in this PWS. The Contractor will take reasonable steps to ensure that it will allow only those Contractor and Subcontractor employees who need to see the 82ND AIRBORNE DIVISION materials to perform the requirement to do

so. This agreement also applies to any other 82ND AIRBORNE DIVISION systems or data to which the Contractor may have access to or be disclosed to the Contractor.

4.3.5 The Contractor will not authorize anyone other than those individuals who require information to perform under this requirement to access, disclose, modify, or destroy the information, software or applications on the 82ND AIRBORNE DIVISION systems provided or accessed without the COTR prior written authorization. The Contractor will refer all requests or demands for production of or access to 82ND AIRBORNE DIVISION data and systems, including court orders, to the COTR for response.

4.3.6 Except as authorized, the Contractor and its employees shall not make any copies of any 82ND AIRBORNE DIVISION information, including software or applications that are not copyrighted. Any copies made by the Contractor or 82nd Airborne Division Subcontractor shall be identified as 82ND AIRBORNE DIVISION property and handled as sensitive information under this non-disclosure agreement.

4.3.7 Except to the extent necessary to perform the work, any information that the Contractor and its employees learn from and about 82ND AIRBORNE DIVISION data and 82ND AIRBORNE DIVISION computer systems shall not be recorded and such information, whether recorded or not, shall be handled as sensitive information under this agreement. The Contractor may not use or disclose this data except as the Contractor is permitted to use or disclose 82ND AIRBORNE DIVISION sensitive information under this requirement and this nondisclosure agreement.

4.3.8 Upon completion or termination of the contract for any reason, the Contractor will immediately deliver all non-public 82ND AIRBORNE DIVISION records, data, copies of 82ND AIRBORNE DIVISION records and data, software and equipment, and information about 82ND AIRBORNE DIVISION data and systems recorded or documented by the Contractor, in its possession or the possession of any Subcontractors to the COTR.

4.3.9 The Contractor will be responsible for the actions of all individuals provided to work for 82ND AIRBORNE DIVISION -OMD under this requirement.

4.4 Removal from Duty Clause – The Contracting Officer (CO), with input from the COTR and designated 82ND AIRBORNE DIVISION Personnel Security Officer, may request that the Contractor immediately remove any contractor personnel from working on the contract should it be determined that individual(s) are unfit to perform on the contract. The 82ND AIRBORNE DIVISION will provide the Contractor, in writing, the specific reasons for removal of an individual. The Contractor must comply with these requests.

4.5 Examples of incidents involving misconduct or delinquency are set forth but not limited to the items below:

(a) Violation of the Rules and Regulations Governing Public Buildings and Grounds, 41 Code of Federal Regulations 101-20.3.

(b) Neglect of duty, including sleeping while on duty, unreasonable delays, or failure to carry out assigned tasks, conducting personal affairs during official time, and refusing to cooperate in upholding the integrity of 82ND AIRBORNE DIVISION’s security program.

(c) Falsification or unlawful concealment, removal, mutilation, or destruction of any official documents or records, or concealment of material facts by willful omissions from official documents or records.

(d) Disorderly conduct, use of abusive or offensive language, quarreling, intimidation by words or actions, or fighting. Also, participating in disruptive activities that interfere with the normal and efficient operations of the Government.

(e) Theft, vandalism, immoral conduct, or any other criminal actions.

(f) Selling, consuming, possession of, or being under the influence of intoxicants, drugs, or substances, which produce similar effects.

(g) Improper use of official authority or credentials.

(h) Unauthorized use of communications equipment or Government property.

(i) Misuse of equipment used in the performance of this contract.

(j) Unauthorized access to areas not required for the performance of the contract.

(k) Unauthorized access to employees’ personal property.

(l) Violation of security procedures or regulations.

(m) Violation of the Privacy Act of 1974, the Computer Fraud and Abuse Act of 1986, and the Taxpayer Browsing Act of 1997.

(n) Unauthorized access to, or disclosure of, agency programmatic or sensitive information, or IRS Tax Return information.

(o) Unauthorized access to 82ND AIRBORNE DIVISION’s automated information systems.

(p) Unauthorized access of information for personal gain, (including, but not limited to monetary gain) or with malicious intent.

5.0 GOVERNMENT ROLES AND RESPONSIBILITIES

Below are specific roles of Government personnel that can direct Contractor resources:

5.1 Contracting Officer The Contracting Officer has responsibility for ensuring the performance of all necessary actions for effective contracting; ensuring compliance with the terms of the contract and safeguarding the interests of the United State in its contractual relationships.

Accordingly, the Contracting Officer is the only individual who has the authority to enter into, administer, modify, or terminate this contract. In addition, the Contracting Officer is the only person authorized to approve changes to any of the requirements under this contract, and notwithstanding any provision contained elsewhere in this contract or representation made by any 82ND AIRBORNE DIVISION employee, this authority remains solely with the Contracting Officer.

5.2 Contracting Officer Technical Representative (COTR) The Contracting Officer may designate other Government personnel (known as the Contracting Officer Technical Representative) to act as his or her authorized representative for contract administration functions, including technical direction, that do not involve changes to the scope, performance, price, schedule, or terms and conditions of the contract. The COTR will be named in the order when awarded. Such designation will not contain authority to sign contractual documents, order contract changes, modify contract terms, or create any commitment or liability on the part of the Government different from that set forth in the contract.

5.3 Alternate Contracting Officer Technical Representative (A-COTR) The Contracting Officer may designate other Government personnel to act as Alternate Contracting Officer Technical Representatives (A-COTR) to assist the COTR and act as the Contracting Officer’s authorized representative for contract administration functions, including technical direction, that do not involve changes to the scope, performance, price, schedule, or terms and conditions of the contract. The A-COTR may be named to assist with the administrative functions of the contract.

The A-COTR will be named in the order when awarded. Such designation will not contain authority to sign contractual documents, order contract changes, modify contract terms, or create any commitment or liability on the part of the Government different from that set forth in the contract.

6.0 SECTION 508 COMPLIANCE Compliance with section 508 of the Rehabilitation Act of 1973 (as amended) is mandatory for all 82nd Airborne Division personnel and areas with work delivered under the contract. Standards can be viewed at: http://www.section508.gov.

7.0 SUITABILITY AND SECURITY PROCESSING

7.1 General

7.1.1 All personnel are required to have a SECRET clearance upon entering the 82nd Airborne Division Headquarters for work on this requirement. No personnel may be assigned to work on this requirement without a clearance.

7.1.2 Suitability, waiver, and security clearance determination investigations are currently conducted through the Office of Personnel Management. Individual Contract personnel will be provided with a review process before a final adverse determination is made. The 82ND AIRBORNE DIVISION requires that any personnel found not suitable, or who has a waiver cancelled, or is denied a security clearance, be removed by the Vendor during the same business day that the determination is made.

Appendix A - Compliance, Guidance, and Configuration Documents

This appendix includes compliance specifications that must be met, guidance documents that are for your assistance during the development process, and platform configurations that the courseware must play on. A reference to the base contract work statement is provided for your convenience.

1. Compliance Documents. The contractor shall ensure all work complies with the following:

1.1.1. Army Regulation 25-2, current version, all chapters and appendices.

1.1.2 Army Regulation 525-27 Army Emergency Management Program, current version, chapter 6.

1.1.7. All requirements included in this PWS are subject to DFARS 252.227-7020 to include all documents, materials and source codes of any software. The contractor shall mark all works delivered under this PWS as required by DFARS 252.227-7020.

1.1.8. Personally Identifiable Information – The use of social security numbers and other personally identifiable information (PII) is forbidden in web based courseware. With the rise of personal identity theft, we must be especially sensitive to the use of any information in the text or graphics that could jeopardize personal information.

Compliance information is found at http://www.atsc.army.mil/tadlp/content/nomination/dl_pii.asp

1.1.9. Section 508 Compliance and Accessibility Requirements: The contractor shall ensure all training and education products required through this PWS comply with the provisions of Section 508 and shall meet all applicable accessibility standards. The criteria describe in Section 508, Subparts B, C, and D shall apply to content products functionality. See Section 508 Standards web page (www.section508.gov) for specific criteria references by letter (e.g., criteria (a) in Section 1194.22). For elaborations of each criterion, see Subpart B, Section 1194.21 and 1194.22 listed in the Guide to the Section 508 Standards for Electronic and Information Technology.

1.1.9.1. The contractor shall ensure that personnel with sighted (blindness), auditory (deafness) and mobility (motor hand/arm movement) disabilities are to be accommodated through Section 508 of the Rehabilitation Act (29 U.S.C. 794d), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7, 1998.

2. Configurations.

2.1 Baseline Home Computer Configuration, [version number]

<http://www.atsc.army.mil/tadlp/implementation/config/home_computer.asp >.

2.2 Army Golden Master (AGM) Army Standard Baseline Configurations, http://www.atsc.army.mil/tadlp/implementation/config/index.asp.