Draft_PWS_ESS_SW_Mnt_070114.pdf

Performance Work Statement (PWS) for Explosives Safety Siting (ESS)

Software Maintenance

1.0 General/Organization/Background/Scope

1.1 General

This is a non-personal services contract to maintain and enhance the Explosives Safety Siting (ESS) to ensure that it continues to meet the needs of all Services. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn, is responsible to the Government.

1.2 Organization

Naval Facilities Expeditionary and Engineering Warfare Center 1100 23rd Avenue Bldg. 1100 Port Hueneme, CA 93043

1.3 Background

In 1996, the Defense Environmental Security Corporate Information Management (DESCIM) Program Management Office (PMO) embarked on an effort to automate the explosives safety planning and site approval request process. This effort has resulted in the development of the Explosives Safety Siting (ESS) software.

In March 1998, the NAVFAC Engineering Service Center (now called NAVFAC Engineering and Expeditionary Warfare Center (EXWC)) was tasked to become the Central Design Authority (CDA) for ESS and is currently providing technical and program guidance to this program. In 2002, program management of DESMS transferred from DESCIM to the Environmental Information Technology Management (EITM) Program. In 2006, program management of DESMS transferred from EITM to the Department of Defense Explosives Safety Board

(DDESB).

In 2008, three explosives safety planning software applications were in significant use in the DoD: ASHS, ESS and MSS. This software was developed by the Air Force, DoD and Army, respectively, to meet specific needs of their target customers. All three software programs were developed in response to urgent, specific explosives safety siting requirements that differed from one Service to another. Even though each meets those needs very well, evolving DoD needs and requirements for the future brought explosives safety approval authorities together to develop plans to bring the best features of each of these software applications together into one “Best-of- Breed” system that is designed to meet the needs of explosives safety planners throughout all of the DoD. A unanimous agreement was reached among members of the Joint Service Automated Site Planning Working Committee to merge the best features of the MSS and ASHS software into the ESS software to create the hybrid software system that resulted in ESS Version 6.1.

The Automated Site Planning (ASP) Configuration Control Board (CCB) developed the Explosives Safety Automated Site Planning Requirements Document (ASPRD, see Paragraph 4a) that defines the current and future required software functionality for this “Best of Breed” hybrid system. Additional software functionality is called for in the near future which will include merging the functionality of risk-based explosives safety site planning (Published in DDESB Technical Paper 14) into ESS, and adding the ability to evaluate the explosives safety siting regulations published by North Atlantic Treaty Organization (NATO) (NATO Allied Ammunition Storage and Transport Publication AASTP-1, Edition 1 and AASTP-5, Edition 1).

Minor enhancements to software functionality called out in the ASPRD will also be added via quarterly software updates throughout the life of the project.

The Department of Defense has tasked the Department of Defense Explosives Safety Board (DDESB) with evaluation and approval of all explosives storage, handling and maintenance functions that occur worldwide within the Military Services. DDESB requirements and regulations are published in DOD 6055.09-M, “DoD Ammunition and Explosives Safety Standards”. All DoD organizations that deal with explosive items must comply with these regulations. The approval process requires installation planners to prepare individual formal Site Approval Request (SAR) packages for a potential explosive site (PES) that are routed through a review and approval process, ultimately receiving final approval from the DDESB. This approval process is supported by Component explosives safety approval authorities, who have the authority to impose additional requirements over-and-above the DoD requirements.

Historically, planners have prepared SAR packages using manually-generated tables, forms and maps (typically using AutoCAD-type software). The manual creation of the SAR packages has proven to be time consuming and error prone, primarily due to the inexperience of users, misapplication/misunderstanding of the regulations, inaccurate maps, and incomplete facility information.

A Joint Service effort to automate the explosives safety siting process has been underway since the early 1990’s. The Services defined a requirement to link non-graphic facilities and explosives data to facilities represented in electronic maps, and then develop an automated process to access that information and evaluate it against automated explosives safety siting regulations that specify minimum required separation distances between a PES facility and its surrounding facilities. The automated tool, called Explosives Safety Siting (ESS) software, has been developed and fielded. ESS Version 6.1 is the currently approved software for DoD use.

ESS is used to identify violations of the regulations when they are found to exist, and it provides tools to automate the creation of site approval request package documentation that includes tabular and graphical information that is required by Approval Authorities.

1.4 Scope

The contractor shall provide all labor, material, equipment, and services necessary to perform maintenance and enhancement work for Software Maintenance, Software Enhancement, and Software Validation as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract. The Contractor is responsible for achieving the requirements of this PWS based upon their proposed approach and internal processes.

This Performance work statement describes the type of work that may be ordered. The Contractor will maintain ESS Version 6.1 software and to enhance its capabilities as outlined in the Automated Site Planning Requirements Document (ASPRD). Specific tasks are identified in the ASPRD. The contractor shall perform to the standards in this contract. The Contractor is responsible for achieving the requirements of this PWS based upon their proposed approach and internal processes.

1.5 Period of Performance. The period of performance shall be for one (1) Base Year of 12 months and four (4) 12-month option years. The period of performance for work ordered will be defined in each individual task order.

1.6 Services Required. The contractor shall provide all labor, material, equipment and facilities to perform the work as described below.

1.6.1 Software. Maintenance Software maintenance tasks will involve responding to and resolving reported software problems and errors

a) Overview: Software maintenance tasks will involve responding to and resolving reported software problems and errors identified during software execution. Efforts will continue to improve the software validation process with automated validation tools, along with the expansion of pre-defined validation problems that assess the accuracy of computations and data exchange. The ESS software is programmed using Microsoft Visual Basic.NET. It is designed to operate in desktop/laptop mode, or on a web-based server using Microsoft Access, Oracle or SQL Server database software.

b) Work Description:

1) Maintain ESS V6.1 software and correct all reported bugs in the software as directed by EXWC. All corrected bugs will be documented in a software maintenance report.

2) Maintain logical flowcharts of the explosives safety siting criteria that are used as the basis for programming DOD and Component Explosives Safety Standards.

3) Maintain ESS software DoD, Army, Navy, and Air Force QD Engine analysis modules and interfaces.

4) All corrected software bugs, flowchart updates, interface updates, data exchange updates, and QD Engine updates will be documented in a maintenance report associated with each new software build.

5) Follow DOD spatial data standards identified in the Department of Defense Spatial Data Standards for Facilities, Installation and Environment (SDSFIE).

6) Follow DOD real property inventory (RPI) Standards.

7) Maintain ESS software to be compatible with other software updates including ArcGIS, ESRI GIS file formats, MS Access, MS Office, MS Internet Explorer, MS Windows, SQL Server, Oracle, Acrobat Reader, and AutoCAD.

c) Deliverables:

As defined in each individual Task Order.

A001 maintenance report A002 software build A003 source code

1.6.2 Software Enhancement

a) Overview:

1) The initial operational requirements for the ESS software have been satisfied with

ESS Version 6.1, Build 238. The functionality of the ESS software will be significantly enhanced as new features are added over the next five years.

2) Additional data editing tools will be added to enhance the ease of use of the software. “Turbo Tax” type help wizards will be added to assist low level users accomplish basic tasks using the ESS software and additional training aids will be developed with the objective of minimizing the cost of training and Help Desk support.

3) A second version of the ESS software will be developed to realize the benefits of Web-based software technology. The emerging Risk-Based explosives safety siting criteria will begin to be added to ESS over the next two years.

4) As the use of the ESS software becomes integrated into the Services site planning program operations, there will become a need to have ESS exchange data with DoD enterprise databases. Capabilities will need to be developed in the ESS software to import and/or export data with other DoD enterprise databases including but not limited to EES, Navy GeoReadiness (GIS data), and iNFADS.

5) As the ESS software begins to be widely utilized worldwide, plans are being made to make this software available for use by installation planners of foreign nations that have formal military alliances and cooperation agreements with the United States. This could potentially require the additional functionality of applying the explosives safety site planning regulations of foreign nations, along with providing the versions of the ESS software that function in other languages and with NATO criteria.

b) Work Description:

1) Provide robust map editing tools to facilitate the creation, import, editing and maintenance of GIS maps of DoD Installations. Additional graphical editing commands will be added to allow users to create or update maps to account for rapidly changing circumstances in the field. Special tools will be added to allow the user to automate the siting of complex objects. For example, measured distances between aircraft are different, depending on whether the aircraft being sited is a potential explosive site (PES), or an exposed site (ES). Additional tools will be provided to allow quick and accurate siting of new facilities inside existing development constraints and to account for reduced separation distances provided by barricade protection. Geospatial tools will be added to help users compare and update ESS maps as they change over time. Additional tools will be provided to closely track changes to data so that configuration management is not lost when edits are made to copies of the ‘official’ map of record at any DoD installation. In addition to tools listed above, additional tools will be added to improve productivity and ease of use of the ESS software.

2) Develop training aids, including, but not limited to, workbooks and ‘Help Wizards’ to assist users to review or learn how to use the software. Extensive wizard help routines and training aids will minimize formal training requirements and assist users to quickly become proficient with the use of the software and to recall how to execute software commands when the software hasn’t been used for an extended period of time.

3) Develop a second version of ESS Version 6.1 that will operate on web-based servers operated by Army G4, NAVFAC EXWC CIO, or other organization. The Army has identified a new requirement to field a web-based version of the ESS software within 3 to 5 years. This work is expected to require substantial revisions to the ESS software. Once the web-based version has been developed, the need to maintain a desktop version of ESS will remain, so we anticipate maintaining two versions of this software in the future.

4) Work with government and contractor subject matter experts to merge Risk-Based Explosives Safety Siting (RBESS) software such as SAFER and HAZX into the ESS software. This effort includes working with government and government contractors to merge explosives safety risk-based software, such as SAFER or HAZX software into ESS. Details of the risk-based explosives safety site planning requirements are in the Risk-Based Software Requirements Document

(RBSRD).

5) Add user interfaces to allow execution of NATO explosives safety siting criteria to ESS. Functional expansion of ESS will produce a NATO explosives safety site planning criteria option for the ESS Quantity Distance (QD) Engine software analysis module to assist expeditionary planners meet US and NATO explosives safety rules and regulations when siting explosives facilities overseas. The government is responsible for converting the NATO regulations into a flowchart structure that clearly identifies all logical branches required to determine the minimum allowable safe separation distances between a PES and ES. The government is also responsible for programming the flowchart logic into a NATO QD Engine software model that automates the evaluation of any PES-ES combination expected to be encountered on a NATO military installation. The contractor is responsible for duties such as developing the user interfaces required to gather essential facility and graphics data, pre-process and post-process NATO QD Engine analysis results, and storing all derived data in the ESS database.

6) Translate ESS commands into languages other than English, to allow software use by foreign nationals that have cooperation agreements with the US. The DOD has cooperative defense agreements with many nations throughout the world. US explosives safety site planning regulations are required on all DOD installations located in foreign countries as well as on US territory. In addition to meeting US regulations, DOD installations must also comply with host nation explosives safety siting regulations. Host nations must also comply with US explosives safety regulations on installations where their munitions are stored jointly with US-owned munitions. We anticipate requirements in the near future to provide versions of the ESS software to foreign nations that function in their native language. We expect the functionality of foreign language versions of the ESS software to be identical to the English language versions of the software.

7) Follow DOD spatial data standards identified in the Department of Defense Spatial Data Standards for Facilities, Installation and Environment (SDSFIE).

8) Follow DOD real property inventory (RPI) Standards.

9) Capabilities will be developed in the ESS software to import and/or export data with other DoD enterprise databases including but not limited to EES, Navy GeoReadiness (GIS data), and iNFADS.

10) All software enhancements will be documented in an enhancement report associated with each new software build. This will include associated design documents, presentations, and interface story-boards in digital format.

c) Deliverables:

As defined in each individual Task Order.

A004 enhancement report A002 software build A003 source code

1.6.3 Software Validation

a) Overview: All maintenance and enhancement work performed on the ESS software must be verified and validated to establish that the software was programmed properly and functions as expected.

b) Work Description:

1) Use manual procedures and automated tools to validate every new version of the software where maintenance and enhancement changes have been made.

Validation tools have been created in parallel with the development of the ESS software. Existing validation tools and established manual testing procedures will be used on all new versions of the ESS.

2) When software enhancements have been made and where validation tools are lacking, develop additional automated validation procedures to execute and test the new ESS software. As the software complexity increases, the performance of the automated validation tools must also be improved to assess the adequacy of computational accuracy and correct manipulation and display of data. Develop additional automated validation tools as directed, to enhance the validation testing process and to minimize the manual testing requirements.

3) A validation report will be developed for each software build. This document will present the results from manual and/or automated testing. Each new automated test procedure developed will also be documented in the report including a description and test procedures.

c) Deliverables:

A005 validation reports A006 software validation tools A007 validation tools source code

1.6.4 Meetings

a) Overview: Meetings are required to keep all members of the Automated Site Planning (ASP) CCB, and NAVFAC EXWC informed on the status, design, and planning of ESS software enhancements, maintenance, and validation.

b) Work Description:

1) Participation at ASP CCB meetings may be required between 1 to 4 times a year at various CONUS locations. Participation at CCB meetings might be in the form of conference calls, web-meetings, or in person. CCB meetings range between 3 hours to 4 days.

2) Participation at NAVFAC EXWC ESS status/planning meetings may be required between 1 to 12 times a year at NAVFAC EXWC. Participation at NAVFAC EXWC ESS status/planning meetings might be in the form of conference calls or web-meetings. EXWC ESS status/planning meetings range between 15 minutes to three days.

3) Participation at CCB and NAVFAC EXWC ESS status/planning meetings may require presentations to be made on the status, planning, design, operation, or demonstration of software enhancements, maintenance, or validation. A copy of the meeting documents and presentations will be provided to NAVFAC EXWC in digital format.

c) Deliverables:

A008 meeting documentation

2.0 Definitions and Acronyms

2.1 Definitions

2.1.1. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.2. CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government.

Note: The only individual who can legally bind the government.

2.1.3. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S.

Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.5. DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.6. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.7. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.8. QUALITY ASSURANCE. The government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.9. QUALITY ASSURANCE Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.10. QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.11. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.12. WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.12. WORK WEEK. Monday through Friday, unless specified otherwise.

2.2 Acronyms

Acronym Description CONUS Continental United States COR Contracting Officer’s Representative CVS Contractor Verification System DFARS Defense Federal Acquisition Regulation Supplement DoD Department of Defense DoDESB Department of Defense Explosives Safety Board FAR Federal Acquisition Regulation NAVFAC Naval Facilities Engineering Command NAVNETWARCOM Naval Network Warfare Command EXWC Naval Facilities Engineering and Expeditionary Warfare Center NMCI Navy Marine-Corps Intranet OCONUS Outside Continental United States POC Point Of Contact PWS Performance Work Statement QA/CM Quality Assurance/Configuration Management QASP Quality Assurance Surveillance Plan QC Quality Control SECNAV Secretary of the Navy SDSFIE Spatial Data Standards for Facilities, Installation and Environment USC US Code (US Public Law)

3.0 Special Requirements

3.1 Clearances and Licensing

Contractor personnel working on this contract shall be U.S. Citizens. Work under this contract will require application and compliance with the following regulations: SECNAV Instruction M-5239 Department of the Navy (DoN) Information Assurance (IA) Workforce management Manual to Support IA Workforce Improvement Program, and Department of Defense (DoD) 8570.01-M, Information Assurance Workforce Improvement Program.

3.2 Security Requirements

a) Unless otherwise directed, all contractor employees and sub-contractor employees working on task orders must be U.S. citizens.

b) Upon completion of this contract, all Controlled Unclassified Information (CUI) documentation (reports, working papers, photographs, drawings, etc.), and materials associated with this contact will be turned over to: NAVFAC EXWC, Code CI7, 1000 23rd Avenue, Building 1100, Port Hueneme, CA 93043-4370.

c) Any contractor personnel required to travel overseas will complete SERE 100 Level B training.

d) Contractor Common Access Card (CAC) requests shall be coordinated following the task order award with the Navy Technical Representative and Contracting Officer’s Representative (COR). The issuance of the CAC is subject to the approval by the NAVFAC EXWC Security Office.

3.3 References

The contractor shall adhere to the current version of the following documents.

a) Automated Explosives Safety Site Planning Requirements Document, Revision 3, NAVFAC ESC Technical Report TR-2310-SHR, August 2011.

b) Software Requirements Document, Risk-Based and Hybrid Explosive Safety Siting (RBESS) Version 1.0, CC8-26500, A=P-T Research, Inc, 9 July 2013.

c) ESS v6.1 Reference Guide, November, 2012

d) ESS v6.1 User’s Guide, November, 2012

e) DOD Ammunition and Explosives Safety Standards, DoD 6055.09-M, Volume 1 Change 1, 12 March 2012.

f) Explosives Safety Standards, Air Force Manual 91-201, 12 January 2011.

g) NAVSEA OP-5 Volume 1, Ammunition and Explosives Safety Ashore, Seventh Revision Change 10, 1 July 2011.

h) Department of the Army Pamphlet 385-64, Ammunition and Explosives Safety Standards, 24 May 2011.

i) Allied Ammunition Storage and Transport Publication, AASTP-1, Edition 1 Change 3, Manual of NATO Safety Principles for the Storage of Military Ammunition and Explosives, May 2010.

j) NATO Standard AASTP-5, NATO Guidelines for the Storage, Maintenance and Transport of Ammunition on Deployed Missions or Operations, Edition 1 Version 2, June 2012.

k) SDSFIE Version 3.0.

3.4 Privacy Act:

Work on this contract requires that Contractor personnel have access to Privacy Information to legally support NAVFAC Business Systems. Personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code (USC), Section 552a and applicable agency rules and regulations.

Contractor will be held liable for all data breaches where he/she is determined to be culpable (e.g., contract proprietary information, social security numbers (SSN) and other sensitive personnel information). Contractor will be held liable and will be required to take steps such as notifying affected parties or providing credit monitoring.

Contractor personnel shall sign a Non-Disclosure Form (Attachment X).

3.5 Access Requirements:

Contractor employees shall fill out a Department of Homeland Security Employment Eligibility Verification, Form I-9 (Attachment X).

Contractor personnel shall coordinate with the Government sponsor to complete and submit an application for a DOD Common Access Card (CAC) through the Contractor Verification System (CVS), see Attachment 05 for the application procedures. The issuance of a Common Access Card (CAC) to a contractor requires, at a minimum, a completed National Agency Check (NAC), or what’s considered a trustworthiness check, as well as an initiated National Agency Check with Written Inquiries (NACI). Companies who employ government contractor personnel will have to complete and submit the NACI on behalf of the individual prior to the start of work. The contractor shall complete and submit a NACI on behalf of their employees to the local Security Management Officer at the work location specified within the task order. This policy is in accordance with the DoD Physical Security Program, DOD 5200.8-R and the Contractor Verification System (CVS) Trusted Agent program.

Once the CAC request has been approved, contractor personnel will proceed to the designated CAC issuance location identified by the Government sponsor with the appropriate documentation to support their identification and/or citizenship. The CAC issuance location will then issue the CAC.

Contractor employees traveling overseas must be eligible to obtain a passport.

Contractor employees shall successfully complete an online Information Assurance (IA) training class (approximately 1.5 hours in duration) each year. This and other government -mandatory trainings will occur at Government’s expense.

Contractor employees shall fill out a System Authorization Access Request Form (SAAR) to obtain access to any Government system (remote or otherwise), see Attachment X.

Within 7 working days of termination/conclusion of this contract, the contractor shall adhere to government checkout procedures for the termination and/or collection of all Public Key Infrastructure (PKI), CAC, NAVFAC Badges, Parking Passes, and Parking Decals. This pertains to NAVFAC support contractors both on site and off site.

3.6 Contractor Identification

All Contractor employees shall ensure that, when participating in meetings with Government and/or other Contractor employees, their personnel properly identify themselves as Contractor employees so that their actions will not be construed as acts of Government officials.

In accordance with DFARS 211.106. Contractor shall ensure that external correspondence signed by Contractor employees is on company letterhead. Internal correspondence, including e-mail and memoranda, must include the name of the company in the signature line or in another clearly identifiable location. In all contact with the public and Government officials, contractor personnel shall identify themselves as contractor employees working under contract to

NAVFAC.

Contractor shall ensure that their onsite personnel, when receiving or placing calls using the government telephone, identify their employer, in addition to whatever other appropriate greeting are used.

All Contractor staff working on a Government installation shall wear at all times while on the installation a DoD or Contractor furnished Identification. If the contractor is assigned workspaces in a Government facility the contractor shall clearly mark them “contractor” and their company name and their name.

The Contractor must comply with the implementation of Federal Information Processing Standards (FIPS) Publication Number 201, Personal Identify Verification of Federal Employees, and Contractors.

3.7 Physical Security

The Contractor shall be responsible for safeguarding all Government property provided for Contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured in accordance with federal, DoD, DON, and local policy requirements.

3.7 Compliance with Rehabilitation Act of 1973 (29 U.S.C. 794d):

This requirement is for Information Technology (IT) and meets the Technical Standards described in Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d), as amended.

Specifically, in accordance with FAR Part 39.203, it is determined after the user input data to the GSA Wizard, that the following accessibility standards at 36 CFR Part 1194 are applicable:

Subpart B §1194.21 Software Applications and Operating Systems:

a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.

b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.

c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that assistive technology can track focus and focus changes.

d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to assistive technology. When an image represents a program element, the information conveyed by the image must also be available in text.

e) (e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance.

f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes.

g) Applications shall not override user selected contrast and color selections and other individual display attributes.

h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.

i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided.

k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.

l) When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

Subpart C §1194.31 Functional Performance Criteria:

a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided.

b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for assistive technology used by people who are visually impaired shall be provided.

c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for assistive technology used by people who are deaf or hard of hearing shall be provided.

d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.

e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for assistive technology used by people with disabilities shall be provided.

f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.

3.8 Compliance with Rehabilitation Act of 1973 (29 U.S.C. 794d):

This requirement is for Information Technology (IT) and meets the Technical Standards described in Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d), as amended.

Specifically, in accordance with FAR Part 39.203, it is determined after the user input data to the GSA Wizard+, that the following accessibility standards at 36 CFR part 1194 are applicable:

Subpart B §1194.21 Software Applications and Operating Systems:

a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.

b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.

c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that assistive technology can track focus and focus changes.

d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to assistive technology. When an image represents a program element, the information conveyed by the image must also be available in text.

e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance.

f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes.

g) Applications shall not override user selected contrast and color selections and other individual display attributes.

h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.

i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided.

k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.

l) When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

Subpart C §1194.31 Functional Performance Criteria:

a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided.

b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for assistive technology used by people who are visually impaired shall be provided.

c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for assistive technology used by people who are deaf or hard of hearing shall be provided.

d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.

e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for assistive technology used by people with disabilities shall be provided.

f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.

Subpart D §1194.41 Information, Documentation and Support:

a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charges.

b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats, or alternate methods upon request, at no additional charge.

c) Support services for products shall accommodate the communication needs of end-users with disabilities.

d) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charges.

e) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats, or alternate methods upon request, at no additional charge.

f) Support services for products shall accommodate the communication needs of end-users with disabilities.

4.0 Personnel Qualifications

4.1 Key Personnel:

The following definitions establish key labor categories under this contract.

Senior Software Applications Engineer

This individual must have:

a) In-depth understanding of the data attributes used in automated explosives safety site planning.

b) Knowledge and experience in the application of DoD, Army, Navy and/or Air Force explosive safety criteria to the automated explosives safety site planning process.

c) Experience in the use and application of explosives safety automated site planning software.

d) In-depth experience in software development, including GIS software development.

e) Experience in:

1) The use, application and creation of ESRI shapefile and geodatabase file structures

2) The use of ESRI ArcGIS software applications.

3) Software development using ESRI ArcGIS for Desktop, ArcGIS for Server and MS Visual Basic.NET applications.

4) Database development and database administration for Oracle, SQL Server and Microsoft Access databases.

5) The application of ADO.NET and ESRI Arc Server/SDE interfaces with MS Visual Basic.NET for Oracle, SQL Server and Microsoft Access databases.

f) Experience using AutoCAD, Autodesk Map, and Micro Station software applications.

g) Experience converting data from AutoCAD, Autodesk Map, and Micro Station to ESRI GIS formats.

Senior Computer Programmer Analyst

a) An in-depth understanding of the explosives safety criteria and regulations, along with GIS data attributes used in the ESS data model.

b) Experience in the use and application of automated explosives safety site planning software.

c) In-depth experience in software development, including GIS software development.

d) Experience developing GIS software applications using ESRI ArcGIS for Desktop, ArcGIS for Server and MS Visual Basic.NET applications.

e) Experience in the application of ADO.NET and ESRI Arc Server/SDE interfaces with MS Visual Basic.NET for Oracle, SQL Server and Microsoft Access databases.

f) Experience using AutoCAD, Autodesk Map, and Micro Station software applications.

g) Experience converting data from AutoCAD, Autodesk Map, and Micro Station to ESRI GIS formats.

4.2 Other than Key Personnel Qualifications:

Junior Software Applications Engineer

This individual must have experience in:

a) Software development, including GIS software development.

b) The use, application and creation of ESRI shapefile and geodatabase file structures

c) The use of ESRI ArcGIS software applications.

d) Software development using ESRI ArcGIS for Desktop, ArcGIS for Server and MS Visual Basic.NET applications.

e) Database development and database administration for Oracle, SQL Server and Microsoft Access databases.

f) The application of ADO.NET and ESRI Arc Server/SDE interfaces with MS Visual Basic.NET for Oracle, SQL Server and Microsoft Access databases.

Project Manager

a) A demonstrated capability to organize and direct technical and management programs which include multidisciplinary tasks and requirements.

b) In-depth experience in software development, including Geographical Information System (GIS) software development.

c) In-depth experience in the application of DoD, Army, Navy and/or Air Force explosives safety criteria.

d) Experience with, and an understanding of, the DoD explosives safety site planning submittal and approval process.

5.0 Contract Description and Deliverables

5.1 Contract Description

The Government intends to award this requirement as a single-award Indefinite Delivery/Indefinite Quantity contract, for a contract period of five (5) years, a base year with four one-year options. Task orders will be Firm Fixed Price (FFP).

5.2 Task Order Deliverables

Task Orders negotiated under this contract shall include their own specific list of deliverables and/or Contract Data Requirements List (CDRL) as specified by the Government. They will include appropriate details such as content, format, timing, and receiving party.

The ESS software including all enhancements, maintenance updates, validation tools, and source code are owned by the US Government. The ESS software or any part of it may not be modified, translated, reverse engineered, decompiled, disassembled, or updated unless agreed upon with NAVFAC EXWC or DDESB. The ESS software or any part of it may not be distributed or shared with other companies or organizations unless agreed upon with NAVFAC EXWC or DDESB. Removal of any proprietary notices or labels on the software is prohibited.

Deliverables may include, but are not limited, to the below items.

5.2.1 Status Reports

Monthly Status Reports shall address the current status of all work and plans for coming months.

Contractor format is acceptable. Electronic delivery, in the form of email attachments, is acceptable.

5.2.2 Software Engineering Tools

Computer assisted software engineering (CASE) tools shall be used to increase productivity and for documentation of source code. These tools could include ModelMart, ERwin, and PBwin from Platinum Technologies. The Contracting Technical Representative (COR) shall be consulted regarding the application of these and other CASE tools that may achieve these objectives. The COR will reserve the right to direct the contractor’s application of CASE tools as necessary.

5.2.3 Contract Data Requirements List (CDRL)

The Contractor shall provide the following documentation according to the delivery scheduled shown in Table below.

CDRL

DESCRIPTION PWS DUE

DATE

FREQUENCY

TBD at task order level

5.3 Format

All reports and CDRLs will be submitted electronically in two formats. A Microsoft Office 2000 compatible format and an Adobe Acrobat PDF version 5.0 or higher. Documents shall be supplied electronically via a readable media (CD, E-mail).

Note: Minimum Protection Requirements for Controlled Unclassified Information: Security Classifications Guides (OPNAVINST 5513 services) and unclassified limited documents (e.g.

FOUO, Distribution Statement Controlled) are not authorized for public release and, therefore, cannot be posted on a publicly accessible web server or transmitted over the internet unless appropriately encrypted.

Reports shall provide a comprehensive description of work being documented. Drawings, charts, illustrations and other material needed to clarify the presentation shall be included. The format for required reports shall reflect the appendices to the report.

Reports shall be clearly written, described the work adequately, be well edited and be acceptable for release as a quality document. The report shall document the results of all analyses performed. Draft reports shall be finished products requiring only technical changes as the result of Government review.

6.0 Performance Requirements

The contractor Performance Requirements are outlined in the Quality Assurance Surveillance Plan (QASP). Specific performance requirements for each subsequent task order will be provided when a Task Order Request for Proposal is submitted to the contractor.

6.1 Performance Objectives.

The performance objectives described below are applicable to the total scope of services being performed under this contract. Additionally, the performance specifications will be addressed in each task order. The measurable objectives that may be used include the following;

a) Timely proposal submissions that meet project requirements.

b) Ability to meet project schedule milestones.

c) Creation and management of an effective QA/QC and Health & Safety Program

d) Ability to manage multiple contract task orders.

e) Ability to demonstrate technical competence and innovation

f) Ability to perform project planning and produce appropriate technical documents/drawings as required.

g) Effective control and management of subcontractor efforts.

h) Ability to meet required performance specifications.

i) Ability to manage and execute task orders within the negotiated budget.

6.2 Performance Measurement.

The following will be used to measure performance of the above stated objectives.

a) All proposals are submitted on or before the due date and meet all project requirements.

b) In performance of task orders, all project schedules are (excluding government accepted delays) adhered to.

c) Projects meet all OSHA and other standards as identified in the individual task orders.

d) Multiple contract task orders are managed while meeting all task order requirements.

e) Performance of the task order reflects technical competence and innovation that adds value to the overall project.

f) Technical documents and drawings meet program requirements.

g) Subcontractor cost, schedule, and technical competency meet project requirements.

h) All task order performance specifications are met.

i) All task orders are completed within the negotiated budget.

6.3 Project Management and Contract Oversight

The contractor is responsible for the quality of all work performed. The contractor measures that quality through the contractor’s own quality control (QC) program. QC is work output, not workers, and therefore includes all work performed under this contract regardless of whether the work is performed by contractor employees or by subcontractors. The contractor’s QCP will set forth the staffing and procedures for self-inspecting the quality, timeliness, responsiveness, customer satisfaction, and other performance requirements in the PWS. The contractor will develop and implement a performance management system with processes to assess and report its performance to the designated government representative. The contractor’s QCP will set forth the staffing and procedures for self-inspecting the quality, timeliness, responsiveness, customer satisfaction, and other performance requirements in the PWS. This QASP enables the government to take advantage of the contractor’s QC program.

The government representative(s) will monitor performance and review performance reports furnished by the contractor to determine how the contractor is performing against communicated performance objectives. The government will make determination regarding incentives based on performance measurement metric data and notify the contractor of those decisions. The contractor will be responsible for making required changes in processes and practices to ensure performance is managed effectively.

6.4 Contract Review Meetings and Materials for Review

a) Program and contract management requires day-to-day oversight of resources associated with all task orders under this contract. Program oversight shall include a well-defined and efficient line of authority, responsibility, and communication in managing all task orders.