Performance_Work_Statement_-_Medical_Operational_Data_System_(MODS)_(Bridge__7).doc

PERFORMANCE WORK STATEMENT

1. Scope of Work

The mission of the Medical Operational Data System (MODS) is to provide Army Medical Department (AMEDD) commanders, managers, and consultants with a responsive and reliable human resource and readiness, information-management data system for all categories of military and Department of the Army (DA) civilian medical and support personnel.

In order to accomplish this mission, the Government will continue to use teams of Office of The Surgeon General (OTSG), Medical Command (MEDCOM) staff, and contractor personnel to maintain existing application systems, upgrade and enhance existing application systems, and to extend and expand existing capabilities in an evolutionary manner. As directed by the MODS Configuration Control Board (MCCB), web-based conversion will continue for non-web based applications. All new work will be web based.

The Government requirement in this Performance Work Statement (PWS) is a comprehensive set of integrated data and application systems capable of supporting many related functions throughout AMEDD organizational units. In order to support this task, the contractor shall provide highly capable staff, experienced in the kinds of tools and applications described below, who are able to work in a dynamic environment.

1.1. Purpose

The contractor shall provide personnel who possess the knowledge, skills, and abilities to support the MODS Program Office and the U.S. Army Medical Information Technology Center (USAMITC), Project Management Division (PMD), in project management support for Maintenance, Software Development, Implementation, and Sustainment of the MODS system. This task is neither inherently Government nor personal services in nature.

1.2. Background

1.2.1 Functional Description

MODS is designed to provide the AMEDD leadership with an integrated system to manage AMEDD human resources (HR), logistics, education, manpower, and Army medical readiness programs. MODS is an integrated automation system that supports all phases of the AMEDD Human Resource Life-Cycle management processes in both peacetime and mobilization. The objectives for MODS are to enhance Human Resources management, manpower utilization, fiscal execution, medical logistics management and medical readiness program management. MODS was placed into production in 1992 and it supports the following functions:

MODS Supported Functions

Sustainment

1.2.2 Current Operating Environment

To provide interactive access to over 750,000 users worldwide, MODS utilizes three distinct platforms: 1) the US Army Network Infrastructure Support Command – Pentagon Enterprise Server; 2) the MODS Web Server; and 3) the user's desk top. AMEDD medical treatment facilities and administrative offices have adequate hardware and connectivity capability to utilize MODS’ web-based solutions without additional hardware or infrastructure.

The hardware architecture consists of an Enterprise and Internet architecture. The fundamental host for the hardware environment is an IBM Z9 mainframe with z/OS 1.8 operated by ITA. It employs the IBM DB2 v8.1 RDBMS for transactional processing using a CICS interface for data entry and reporting using TSO, and the communications protocols for the various networking environments reside on the Enterprise Server. The web server environment consist twenty-nine blade servers (IBM LS24 & HS21) that subscribes to a NetApp storage array and Tivoli management services furnished at the enterprise (hosting) level. There is a collection of equipment to support the communications connections including an IBM Open Systems Adaptor, an IBM 3172, multiple IBM 3174’s, several Cisco routers, Ethernet hubs and switches, digital telecom switches, a bank of modems, and several CSU/DSU.

The principal Internet component of the environment is the MODS Web Server environment is located at the Pentagon Data Center, Arlington, VA. This provides a stable, fault-tolerant and scalable server platform that supports the MODS Web Applications.

The fifty MODS Web Server applications are hosted on an infrastructure of clustered and load-balanced web application servers, clustered and load-balanced web service servers, and clustered database servers. Critical storage requirements are supported by a Storage Area Network (SAN). The servers are configured with a combination of Microsoft Windows 2008 Server Standard and Enterprise Editions. The database servers use a combination of Microsoft SQL Server 2008 Standard and Enterprise Editions. Software is developed using the Microsoft .NET Framework primarily written in the C# Language. The Integrated Development Environment used as Microsoft Visual Studio 2012, Team Foundation Server, SQL Server Enterprise Manager and other applications.

The MODS Web Server environment is also used in-concert with the MODS Data Warehouse (MDW). The MDW is the most recent addition to the MODS operating environment. It is the principal data analysis environment slated for analytical super-users. The MDW was constructed with the Dell/Microsoft Parallel Data Warehouse - Massively Parallel Processing (MPP) Appliance (Microsoft SQL Server 2008R2 & HPC) coupled with MicroStrategy 9.4.1 for data visualization. The MDW servers and its data must operate and be maintained at the same operational levels necessary to keep MODS' transactional servers, applications and data functioning properly at all times.

The current operating environment is replicated at a remote Contingency Operations (COOP) site. MODS’ COOP components operate as mixed hot and warm site designed for rapid disaster recovery.

Server based and web based applications are developed to run on Army standard desktop configurations. The customer workstations primarily run DoD supported Operating Systems with supported Web browsers. Additional software applications can be required to meet customer requirements.

Communications access for both the Enterprise Server and the MODS Server is provided through TCP/IP gateways over the Non-secure Internet Protocol Router Network (NIPRNet). The OTSG supports TCP/IP as a standard for Personal Computer Communications from remote locations via the NIPRNet or the Internet.

1.2.3 Contract Structure

This PWS includes a combination of Firm Fixed Price, Firm Fixed Price with IDIQ (Indefinite Delivery Indefinite Quantity) orders, and Cost Reimbursement with IDIQ orders. Using a combination of contract types is the most appropriate means to pay for required contractor performance (FAR 16.103 (b)

1. Contract line items for Operation and Maintenance overhead are awarded as Firm Fixed Price. Annual requirement and cost is fully definitized at the start of the period of performance.

2. Contract line items for Operational Support Services are awarded as Firm Fixed Price. Annual requirement and cost is fully definitized at the start of the period of performance.

3. Contract line items for MODS Service Request (MSR) labor are awarded as Firm Fixed Price with IDIQ orders. The labor rate per hour is Firm Fixed. The call order media is a MODS Service Order (MSO) issued by the HCAA Contracting Officer via task order release to the contractor as delivery dates and quantities are fully definitized.

4. Contract line items for MODS Service Request (MSR) travel/other direct costs are awarded as a Cost reimbursement with IDIQ orders. The call order media is a MODS Service Order (MSO) issued by the HCAA Contracting Officer via task order release to the contractor as delivery dates and quantities are fully definitized.

5. Use of IDIQ orders (FAR 16.501-2(2)) benefits the Government by permitting flexibility in quantities, delivery scheduling, and ordering of supplies or services after requirements materialize.

6. Use of IDIQ orders (FAR 16.501-2(2)) requires a statement that reasonably describes the general scope and nature of supplies or services to be supplied; states the procedures that the Government will use in issuing orders including the ordering media (i.e. MODS Service Order), and requires a specified minimum quantity (more than nominal) and a maximum quantity.

1.2.4 Procedures for issuance of Task Orders:

1. MODS Government Functional Proponent will identify to the USAMITC MODS Project Director the contractor labor and travel/ODC requirements for each of their respective CLINs with separate identification for modernization work versus steady state sustainment.

2. Bona Fide Need: For the identified work requirements, MODS Government Functional Proponent must ensure that there is a bona fide need during the specified contract period of performance. An agency may obligate appropriated funds only for bona fide needs that arise during the appropriation's period of availability (31USC 1502(a). Because MODS is a severable service contract, it qualifies for the exception that authorizes use of current funds to award a severable service contract for a period not to exceed 12 months at any time during the fiscal year (10 USC 2410 (a)).

3. Funding authorization will typically be provided through the MEDCOM Resource Summary or thorough a Military Interdepartmental Purchase Request (MIPR).

4. USAMITC MODS Project Director will prepare Defense Business Certification (DBC) documentation for modernization requirements for MODS Program Manager submission through HQ MEDCOM to the Defense Business Systems Management Committee (DBSMC). DBSMC certification is required prior to obligating funds for modernization requirements.

5. After approval by the MODS Program Manager, USAMITC MODS Project Director will submit purchase requests, through the USAMITC COR, to the HCAA Contracting Officer to request publication of Task Orders to obligate MODS funds. Purchase requests will include certification of funds availability and identify the amount and type of funds to be obligated by Contract Line Item Number (CLIN). For modernization requirements, purchase requests will occur after DBSMC approval. If a Task Order requires a new CLIN or subCLIN to separately track funding, then the contract must first be modified to establish those new CLINs or subCLINs.

6. HCAA Contracting Officer will publish Task Orders (or Task Order modifications) to obligate the Government's funds on the specified CLINs or subCLINs for the specified Period of Performance.

1.2.5 Procedures for issuance of MODS Service Orders (MSOs)

1. MODS Government Functional Representatives will utilize a MODS Service Request (MSR) to identify labor and travel/ODC task requirements and then submit the MSR to the Program Management Office(PMO) to prepare a price quote.

2. The contractor will submit a price proposal for the MSR work to the MODS Contracting Office within 10 days after receipt of the task description or as directed by the Government. Procedures for Emergency Task Orders that may require verbal approval will be established at the Post Award meeting and will be incorporated into the contract by modification.

3. MODS Government Functional Representatives will submit their approved MSR with contractor quote to the MODS Project Director.

4. MODS Project Director will review the availability of obligated funds on the Task Order CLIN(s) that will pay for the submitted MSR. If adequate funds are available, a MODS Service Order (MSOs) will be prepared and submitted to the MODS COR.

5. MODS Contracting Officer will release the MODS Service Order (MSO) via task order to the contractor.

1.3 Objectives

Following are major MODS objectives.

1. Interface Army and DoD standard database systems within MODS to enhance analysis and decision-making.

2. Provide interfaces to provide critical medical human resource information to the Tri-Service Defense Medical Human Resource System internet (DMHRSi).

3. Provide interfaces to standardize AMEDD-unique automated systems and databases to interact with other systems within MODS.

4. Automate and provide interfaces for AMEDD-unique manual systems and databases to interact with other systems within MODS.

5. Provide an integrated automation system to support life cycle (accessions, promotions, training, pay, transition) human resource management decisions.

6. Develop and maintain a manpower/personnel database at the Defense Manpower Data Center (DMDC), as outlined in the Office of the Assistant Secretary of Defense for Health Affairs (ASDHA) Health Manpower Personnel Data System (HMPDS) Directive.

7. Provide an automated medical logistics management and planning tool

2. General Information and Requirements

2.1 Period of Performance

The base period of performance is 1 Apr 2015 – 30 Sep 2015. This agreement will have a six -month base period. The Government may choose not to renew selected tasks in Section 5 for any reason.

2.2 Hours of Operation

If work is performed in a Government facility, or by an individual identified as “Key Personnel” in Paragraph 5.6, it will be performed during normal duty hours, Monday through Friday, excluding federal holidays, during the period 0630 to 1800 with a lunch break ranging from 30 to 60 minutes in duration. The contractor shall ensure the ordered hours for “Key Personnel” are distributed evenly by week throughout the period of performance. A tour of duty or work schedule for each “Key Personnel” shall be shall be established with the consent of the MODS Program Manager or the appropriate Functional Proponent. Total hours of performance shall not exceed the number of hours ordered in the schedule and overtime premium pay is not allowed. Subject to prior approval, by the MODS Program Manager or a Functional Proponent a variation in work schedule is acceptable when the total contract hours are not exceeded. In the event of office closure due to inclement weather, the contractor shall report to work unless otherwise directed by their company supervisor.

2.3 Place of Performance

Except as otherwise noted, the place of performance shall be at the contractor's site. During the period of performance, contractor may be required to work at sites as directed by the MODS Program Manager. The contractor has supervisory responsibility over all contractor personnel.

2.4 Transition of Services

There shall not be an interruption in delivery of the specific tasks stated in Section 5 and the contractor shall be responsible for making an orderly transition to support these tasks. The contractor shall have a minimum of thirty calendar days to make this transition commencing on the contract award date. The contractor shall submit "Contract Start" and "Contract End" Transition Plans in response to this Performance Work Statement. The Contract End Transition Plan shall address the transfer of knowledge for the tasks stated in Section 5."

2.5 Post-Award Meeting

The Government’s Contracting Officer (KO) shall schedule a meeting within 3 days of contract award to discuss this Performance Work Statement and identify points of contact on the Government and contractor’s sides and the roles each will play. The Post-Award meeting may be conducted via telephone/video teleconferencing.

2.6 Points of Contact

2.6.1 MODS Functional Program Manager (PM)

Mr. David L. Nolan

DASG-HR

Directorate of Human Resources, OTSG

7700 Arlington Blvd

Falls Church, VA. 22042-5140

Telephone: 703-981-9536

Fax: 703-681-3194

E-mail: david.l.nolan3.civ@mail.mil

2.6.2 USAMITC Project Director (PD):

Mr. James A. Starcher

U.S. Government Civil Service

MODS Project Director

USAMITC Project Management Division

4270 Gorgas Circle, BLDG 1070

JBSA Ft Sam Houston TX 78234

Telephone: 210-808-2828

E-mail: james.starcher3.civ@mail.mil

2.6.3 USAMITC Contracting Officer's Representative (COR)

Mr. John Pierce

U.S. Government Civil Service

MODS COR

USAMITC Procurement

2710 Howitzer / S-21 Street BLDG 2372

JBSA Ft Sam Houston TX 78234

Telephone: 210-295-3652

Fax: 210-295-3524

E-mail: john.j.pierce5.civ@mail.mil

2.6.4 Government Functional Proponents(FR)

The Government MODS Program Manager will be the single point of contact (POC) for all matters related to the overall management of the MODS program and will serve as the Government Functional Representative for the MODS Enterprise Portal. The MODS Program Manager will designate a Government Functional Representative for each MODS functional module and will provide a listing to the contractor and updates when changes occur.

Enterprise Portal

Enterprise (MODS Program Manager) Functional Modules

Director Human Resources (HR)

Director Logistics (LOG)

Director Health Care Operations (HCO)

Director Health Care Delivery (HCD)

Director Patient Care Integration (PCI)

Director Program Analysis & Evaluation (PA&E)

Director Emergency Medical Services (EMS)

Director Medical Education (MEDED)

2.6.5 Government Functional Proponent Responsibilities

Each Government Functional Proponent is responsible for their respective assigned MODS modules and applications. The Functional Proponent is responsible to participate in the MODS Configuration Control Board (MCCB), approve requirements for their modules and applications, establish performance measures for contracted work, perform Government acceptance of completed contract work, and approve contractor invoices for payment. The USAMITC MODS project staff will assist the Functional Proponent.

The Enterprise Functional Proponent is responsible when a tasking for the contractor encompasses multiple functional areas.

2.6.6 Contractor Functional Coordinators

For each Government Functional Proponent, the contractor shall designate a Coordinator who will act as the contractor's single point of contact for the contractor activities that support each respective Government Functional Proponent. The contractor shall provide a listing of Contractor Functional Coordinators to the Government MODS Program Manager and updates when changes occur.

Contractor Functional Coordinators shall have a strong understanding of the DBT modernization process, business rules, and timelines. With this understanding, the contractor shall make recommendations to the Government Functional Representatives concerning proper classification of proposed workloads as modernization or steady state sustainment. USAMITC will provide DBT modernization process, business rules, and timelines to the Contractor MODS Program Coordinator.

2.6.7 MODS System Structure

The MODS System, Application and Module (SAM) supports paragraphs 5.3 Software Management and 5.4 Documentation Support. The SAM will be posted, by the contractor, in the AKO MODS Documentation Library in the MODS 366_0 MODS System Level / SAM Report folder.

2.7 Security Requirements

2.7.1 Background Checks and Clearances

Contractor personnel shall be required to undergo a National Agency Check (NAC) security investigation. If derogatory information is reported, the Commander shall determine whether it is in the interest of national security to continue the contractor’s status. If a contract employee has undergone a NAC and is replaced by another contract employee at no fault/request of the U.S. Government, the contractor shall be responsible for costs of the replacement contract employee’s NAC. Foreign nationals may be granted access under the provisions of DoD Directive 8500.2 and AR 25-2.

2.7.2 IT Designation

Contractor personnel do not require access to classified data. Per the National Industrial Security Program Operating Manual (NISPOM) and AR 25-2, in order to gain access to and fully utilize the Army Medical Department (AMEDD) electronic network and to gain access to patient data as protected by the Health Insurance Portability and Accountability Act (HIPAA), all contract personnel must have an IT-II (formerly ADP-II) Clearance. Prior to the start of the contract period, the contractor shall ensure necessary actions have been taken such that the person performing work contained herein has an IT-II clearance.

2.7.3 Safety and Accident Prevention

The contractor shall conform to the specific safety rules prescribed in AR 385-55 and AR 385-10, as applicable. The contractor shall take all reasonable steps and precautions to prevent accidents and preserve the life and health of all personnel. Any violation, unless promptly corrected by the contractor, shall be grounds for termination of this contract.

2.7.4 Security and Fire Prevention

The contractor shall ensure personnel comply with Army Physical Security Program AR 190-13 and Army Fire Protection and Fire Prevention Program AR 420-90.

2.7.5 Security Environment

If working in a restricted, secured environment, contractor personnel shall comply with Army Security Programs in accordance with DoD and DA directives, to include all security regulations and policies in effect at the work site.

2.7.6 Security In-Briefing

Before reporting to each Government work site, contractor personnel shall report to the local security office for issuance of a Government badge and security briefing. The contractor security officer or manager must verify, in writing, that the onsite personnel have completed a NAC and that this NAC is on file with the Federal Government. The contractor's security officer must also provide a letter with the following information regarding the onsite personnel.

· Name

· Social Security Number

· Duration of work effort (start and stop dates)

· Level of clearance held (if applicable)

· Date NAC was completed or clearance granted

This letter must be signed by the contractor Security officer and must be faxed to the appropriate security office prior to the work being accomplished.

2.7.7 Security Badges and Common Access Card (CAC)

Contractor personnel shall wear an identifying badge issued by the appropriate facility security manager. The badge shall be worn on outer clothing between the neck and waist on the front part of the body and shall be visible at all times. If required, the CAC will be issued in accordance with Government policies.

2.7.8 System Security

MODS is expected to process information that is considered to be For Official Use Only (FOUO) which makes this system fall into the category of Sensitive But Unclassified (SBU). In accordance with AR 25-2, Information Assurance, the Government will not field systems that do not meet the following requirements:

1. Systems must meet minimum standards stated in the acquisition and procurement specifications.

2. Systems must provide complete documentation supporting certification and accreditation in accordance with DODI 5200.40, Defense Information Assurance Certification and Accreditation Process (DIACAP).

3. Systems must be fully certified or generically accredited.

a. Classified or SBU data shall not be introduced into an Automated Information System (AIS) until the data classification and sensitivity of the AIS has been determined. The appropriate AIS protection mechanisms shall be in place and Designated Approving Authority (DAA) approval to operate shall be obtained. The data owner shall approve entering the data, where applicable. Data shall not exceed the security classification level on which the AIS is approved to process.

b. Commanders will ensure the AIS under their purview is operated in a manner consistent with the system accreditation and this regulation.”

2.8. ANTITERRORISM (AT) / OPERATIONS SECURITY (OPSEC).

2.8.1. OPSEC Training. Per AR 530-1, Operations Security, new contractor employees must complete Level I

OPSEC training within 30 calendar days of reporting for duty. All contractor employees must complete annual

OPSEC awareness training.

2.8.2. Contractor employees with an area of performance within an Army-controlled installation, facility, or area shall comply with the requirement listed below:

2.8.2.1. AT LEVEL I TRAINING. All contractor employees, including subcontractor employees, requiring access to Army installations, facilities, or controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract start date or of reporting for duty, whichever applies. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee to the COR (or to the contracting Officer, if a COR is not assigned) within 5 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at https://atlevel1.dtic.mil/at.

2.8.2.2. ACCESS AND GENERAL PROTECTION/SECURITY POLICY AND PROCEDURES. The contractor and all associated subcontractors’ employees shall comply with applicable installation, facility, and area commander installation and facility access and local security policies and procedures (provided by the Government representative). The contractor shall also provide all information required for background checks (see C.4.5.1.) to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of

Emergency Services, or Security Office. The contractor shall comply with all personal identity verification requirements as directed by DoD, HQDA, and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

2.8.3. Contractor employees who require access to Government information systems shall comply with the requirement listed below:

2.8.3.1. CONTRACTOR EMPLOYEES WHO REQUIRE ACCESS TO GOVERNMENT INFORMATION

SYSTEMS. All contractor employees with access to a government information system must be registered in the

ATCTS (Army Training Certification Tracking System) at commencement of services and must successfully complete the DoD Information Assurance Awareness training prior to access to the information system and annually thereafter. Successful completion of the current version of this training must be accomplished annually thereafter.

2.8.3.2. INFORMATION ASSURANCE (IA) / INFORMATION TECHNOLOGY (IT) TRAINING. All contractor employees and associated subcontractor employees must complete the DoD IA awareness training before issuance of network access. Successful completion of the current version of this training must be accomplished annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M, and AR 25-2 within six months of employment 3 Government Furnished Items

3.1 Work Space

For contractor personnel performing work at an identified Government facility, the Government will provide workspace, office furniture, computer resources, equipment, software and tools necessary to perform the tasks specified in this PWS. The contractor shall have access to Government regulations and technical manuals. Government furnished items shall not be used for any task other than in support of this PWS.

3.2 Equipment and Software

Contractor personnel shall be responsible for all equipment and software issued to them by the Government and shall prudently maintain and secure equipment in accordance with proper office procedures. Government equipment shall be used only in the performance of the tasks specified in this PWS. Equipment shall not be removed from the building without prior approval of the hand receipt holder and issuance of a hand receipt. Contractor personnel shall not modify or load software on computer equipment without prior approval by the Government.

4. Contractor Furnished Items

4.1 Work Space

Except as otherwise noted, the contractor shall work at the contractor’s site and provide all necessary workspace, office furniture, computer resources, equipment, software and tools necessary to perform the tasks specified in this PWS.

4.2 Equipment and Software

Except as otherwise noted, the contractor shall work at the contractor’s site and provide all necessary equipment and software specified in this PWS.

4.3 Contractor Personnel

4.3.1 Assignment of Contractor Personnel

Contractor personnel shall be available to start work immediately upon start of contract. Contractor shall identify by name, labor category and resumes to be delivered to the COR, all employees subject to working these tasks.

Contractor shall maintain a list identifying personnel who depart or who are added to the project. Replacements for vacancies shall be filled within two weeks.

All personnel shall be utilized as necessary to fulfill contract requirements.

Contractor personnel assigned to support the specified tasks and technical requirements in this PWS shall possess all necessary knowledge, skills and abilities. The contractor shall not attribute a failure to meet the performance standards specified in this PWS to a lack of skills or experience.

4.3.2 Key Personnel

The contractor shall propose, among the personnel to be assigned to perform work under this PWS, certain positions the contractor designates as Key Personnel. Key personnel shall be considered essential to the work described within the PWS and they shall demonstrate experience and a solid understanding of MODS functional processes and/or its operating environment. The Government considers the personnel assigned to the tasks in Section 5.6 to be Key Personnel. By mutual agreement following contract award, the contractor and the Government may adjust the Key Personnel designations.

Key personnel shall be committed for the full duration of the effort necessary to satisfy the requirements of the specified tasks, in accordance with the work schedule and the staff assignments proposed by the contractor. Duties can be combined so that one person can support multiple tasks but the person proposed must meet all the qualifications for all the tasks they support.

Contractor shall not substitute key personnel unless such substitution is necessitated by sudden illness, death, or termination of employment. In any of these events, the contractor shall promptly notify the KO.

All requests for substitutions shall provide a detailed explanation of the circumstances necessitating the proposed substitution(s). The request shall also include a complete resume for the proposed substitute(s) and any other information requested by the KO needed to approve or disapprove the proposed substitution(s). All proposed substitutes should have qualifications that are equal to or higher than the qualifications of the person to be replaced. The KO, or his authorized representative, will evaluate such requests and promptly notify the contractor of the Government’s approval or disapproval.

If any of the listed Key Personnel are subcontractor personnel, the contractor shall include the substance of this clause in any subcontract, which the contractor awards under this contract.

4.3.3 Conduct of Personnel

The COR, with the approval of the KO, may require the contractor to remove from the job site any employee working under this contract for reasons of misconduct or security, or found or suspected to be under the influence of alcohol, drugs, or other incapacitating agents. Contractor employees shall be subject to dismissal from the premises upon determination by the COR and the KO that such action is in the best interest of the Government.

4.3.4 Reserved

4.3.5 Reserved. See HCAA Local Clause 5001 - Non-Defense Health Agency (Non-DHA) Health Insurance Portability and Accountability Act (HIPAA) Business Associate Agreement (BAA) (7 July 2014)

4.3.6 Contractor Behavior in the Workplace

Contractor personnel shall assist Government managers in achieving missions or enhancing Government services provided to internal and external clients. As such, contractor personnel play a vital role in the success of the organization’s mission. Contractor personnel may expect to encounter major areas totally supported by Contractors and be dependent on the actions of other Contractors. The Government will maintain a fair and impartial environment in the responsibilities placed on contractors. The following general guidelines are provided. Questions and/or uncertainties shall be brought to the COR or KO for clarification.

1. Contractor employees shall not make final decisions nor approve their own recommendations or the recommendations of other contractors.

2. Except as allow by FAR 9.505-2, contractors shall be disqualified if their employees participate in the preparation of a PWS or otherwise participate in the development of the requirement. This includes exposure to procurement-sensitive information not specifically related to assigned tasks and/or responsibilities as stated in the PWS.

3. Contractor employees shall identify themselves at meetings, in conferences, on the telephone and in electronic mail.

4. Contractor employees shall not task or supervise Government employees nor shall they task or supervise other contract employees unless specifically required by the PWS. This includes accepting assignments from other contractors or Government employees without the approval of the KO. Contractor employees shall not represent the Government in discussions or meetings unless approved by the PM, COR, or KO.

4.3.7 Safeguarding Proprietary/Procurement Sensitive Information

1. Some material may be considered “Proprietary” or “Procurement Sensitive” in nature and shall be treated accordingly. Proprietary information is all information, whether disclosed orally, in writings, by drawings, or otherwise, relating to the work to be performed under this contract, whether proprietary to the Government or one of its collaborating partners. Proprietary information includes, but is not limited to, financial information, contract information, properties, formulae, structures, manufacturing processes, and test results. Information ceases to be proprietary when it is generally available to the public or is available from sources other than the Army. All information submitted to the contractor under this contract shall be presumed to be Army proprietary.

2. Contractor shall safeguard proprietary information both during and after the term of this contract, and shall not appropriate, disclose, or make unauthorized use of proprietary information received under this contract. These requirements include, but are not limited to, the following:

a) Maintenance of a high degree of physical security over proprietary information at all times;

b) Discussion of proprietary information only among contractor's employees whose duties and responsibilities require knowledge of that information; and,

c) Elimination of proprietary information in open publications by the contractor and its personnel.

3. Contractor personnel who receive proprietary information shall execute the statement in paragraph d below when this contract becomes effective or when first employed. All statements executed pursuant to this paragraph shall be kept on file for review by the Government at all times during the life of the contract.

4. The following statement shall be executed on company letterhead and signed by contractor personnel pursuant to paragraph c above:

"I hereby acknowledge that I have been informed that my duties may require that I have access to proprietary information. I understand this proprietary information which I will receive includes, but is not limited to, financial information, contract information, properties, formulae, structures, protocols, manufacturing processes, and test results.

I agree that I will neither appropriate nor disclose nor make unauthorized use of proprietary information both during and after my employment. I further agree that I will neither include nor draw upon proprietary information received under this contract in open publication. This agreement is executed with the intention that collaborating partners of the United States Government who have submitted information to the Government under non-disclosure obligations shall be third party beneficiary hereunder, and shall have the right to enforce the obligations undertaken herein."

Name:

Date:

5. Contractor shall insert the substance of paragraphs a through d above in each subcontract hereunder. Compliance with the provisions of this clause shall be the responsibility of the contractor.

6. All data received, processed, evaluated, loaded and/or created as a result of this delivery order will remain the sole, unlimited property of the Government unless the KO grants specific exception, in writing. Performance may require the contractor to access data and information proprietary to a Government agency, another Government contractor, or of such nature that its dissemination or use other than as specified on this PWS would be adverse to the interest of the Government and/or others. Contractor personnel shall not divulge or release data or information developed or obtained under performance of this PWS, except to authorized Government personnel or upon written approval of the TM and/or KO. The contractor shall not use, disclose, or reproduce proprietary data that bears a restrictive legend, other than as specified in this PWS. The Government will retain unlimited rights to any software created, developed, or modified as a result of this contract.

5 Specific Tasks

The following section addresses deliverables and tasks required to satisfy all the requirements as stated in the PWS.

The contractor shall furnish the necessary personnel, materials, and other services required to perform the work described within this document. The Government will maintain MODS under the direction of the Director of Human Resources, OTSG and the MODS Program Manager. Activities for the operations, maintenance, and enhancement efforts consist of six tasks. The contractor’s delivery of services and product for these tasks falls under the direction of the Contracting Officer's Representative (COR). The specific task groups described in this PWS are summarized by the following table.

5.1 System Operations and Sustainment

The contractor shall operate, administer and sustain the MODS operating environment described in Paragraph 1.2.2.

5.1.1 Task: Enterprise Server Data Administration

The contractor shall provide, manage and maintain all MODS data on the Enterprise Server platform and provide data administration functions such as:

· Data Backup and Recovery

· Database and Data File Monitoring and Performance Tuning

· Data Modeling (physical data models)

· Problem Identification and Resolution

· Technical Guidance and Support to all MODS Tasks

Performance Measure: Data Availability Threshold:

MODS data stored on the Enterprise Server shall be available 24 hours per day, 7 days per week except for scheduled outages and with no more than 5 hours per month of unscheduled down time for any MODS module

Objective: Same as Threshold

Performance Measure: Data Reliability Threshold:

If a catastrophic loss of data occurs, the MODS data shall be recovered within 24 hours

Objective:

Same as Threshold

Performance Measure:

Problem Responsiveness Threshold:

Respond to identified problems within 2 hours 95% of the time

Objective:

Same as Threshold

5.1.2 Task: Web Server System Administration

The contractor shall provide, manage and maintain a platform hosting service for the MODS Web Server environment to include an operational capability for all MODS Web modules.

The contractor shall plan for, and manage a MODS Web Server configuration and provide system administration functions such as:

· Configuration Standards and Enforcement

· Contingency and Disaster Recovery Planning and Management

· Performance Monitoring, Trend Analysis and Tuning

· Capacity Planning and Management

· Storage Planning and Management

· Hardware Planning and Maintenance

· Software Planning and Maintenance

· OS Release Planning and Implementation

· OS Patch Planning and Implementation

· Problem Identification and Resolution

· Technical Guidance and Support to all MODS Tasks

Performance Measure:

System Availability Threshold:

All MODS modules shall be available 24 hours per day, 7 days per week except for scheduled outages with no more than 5 hours per month of unscheduled down time per MODS module

Objective:

Same as Threshold

Performance Measure:

System Reliability

Threshold:

All received web requests shall execute and respond 100% of the time

Objective:

Same as Threshold

Performance Measure:

Problem Responsiveness Threshold:

Respond to identified problems within 2 hours 95% of the time

Objective:

Same as Threshold

5.1.3 Task: Web Server Data Administration

The contractor shall provide, manage and maintain the MODS data on the MODS Web Server and provide data administration functions such as:

· Data Backup and Recovery

· Database and Data File Monitoring and Performance Tuning

· Database and Data File Maintenance

· Data Modeling (physical data models)

· Problem Identification and Resolution

· Technical Guidance and Support to all MODS Tasks

Performance Measure:

Data Availability Threshold:

MODS data shall be available 24 hours per day, 7 days per week except for scheduled outages and with no more than 5 hours per month of unscheduled down time for any MODS module

Objective:

Same as Threshold

Performance Measure:

Data Reliability Threshold:

If a catastrophic loss of the data occurs, the MODS data shall be recovered within 24 hours Objective:

Same as Threshold

Performance Measure:

Problem Responsiveness Threshold:

Respond to identified problems within 2 hours 95% of the time

Objective:

Same as Threshold

5.1.4 Task: Developmental Testing and Evaluation

The contractor shall provide, administer, maintain and support a platform that replicate the MODS operational environment and provides the capability to perform Government’s Development Testing & Evaluation of modifications to the MODS modules.

Performance Measure: Availability Threshold: The DT&E platform shall be available to support MODS DT&E testing 100% of the time Objective: Same as Threshold

Performance Measure: Reliability Threshold: The DT&E platform shall emulate the production environment

Objective: Same as Threshold

Performance Measure: Problem Responsiveness Threshold: Respond to identified testing problems within 2 hours 95% of the time

Objective: Same as Threshold

5.1.5 Task: Application Administration and Support

The contractor shall provide for the daily operation, maintenance, administration and support of the MODS application modules to include functions such as:

· Monitor all data transfers, builds and jobs

· Weekly push of new RIDES databases to production

· Monitor websites and data transfers

· Make sure scheduled jobs run

· Maintenance of daily data loads

· Create scheduled load processes and data transformation packages

· Perform routine maintenance on load processes

· Produce and distribute standard reports, Ad hoc reports and database queries

· Provide real time web based system (the government is familiar with WEBTRENDS but the vendor’s format may be substituted if agreed upon by the COR).

· Reports running and distribution

· Problem Identification and Resolution

· Technical Guidance and Support to all MODS Tasks

Performance Measure:

Delivery

Threshold:

Deliver all scheduled and ad hoc reports and queries on time 95% of the time Objective:

Improve capability so no reports time out

Performance Measure:

Problem Responsiveness Threshold:

Respond to identified problems within 2 hours 95% of the time

Objective:

Same as Threshold

This task excludes on-demand quick fix programming, ad-hoc reports, and other non-routine support tasks.

5.1.6 Task: Certification Administration

The contractor shall plan, manage, and maintain the Defense Information Assurance Certification and Accreditation Process (DIACAP) for all MODS software and hosting platforms. This shall be done in accordance with the following.

1. AR 25-1, Army Information Management, 31 May 2002,

2. AR 25-2, Information Assurance, 14 November 2003

3. DoDI 5200.40, Defense Information Assurance Certification and Accreditation Process (DIACAP), 30 December 1997 ,

4. DOD 8510.1-M, Defense Information Assurance Certification and Accreditation Process (DIACAP), Application Manual, 31 July 2000,

5. DODD 8500.1, Information Assurance, 24 October 2002, 6 ) DODI 8500.2, Information Assurance Implementation, 6 February 2003

The contractor shall:

· Ensure the DIACAP remains current as MODS changes over time

· Ensure and maintain MODS compliance with Tenant in Good Standing (TiGS)

· Establish and maintain a MODS Certificate of Networthiness (CoN)

· Identify and Resolve System Vulnerabilities

· Maintain all DIACAP Documentation for Phase IV criteria as noted in DOD 8510.1-M

· Provide Technical Guidance and Support to all MODS Tasks

Performance Measure:

Current Certificate Threshold:

DIACAP and CoN shall be current and complete at all times Objective:

Same as Threshold

Performance Measure:

TiGS Compliance Threshold:

Research and apply TiGS within 2 calendar days after receipt Objective:

Same as Threshold

5.2 Client Services

The Government shall utilize a three-tier approach to address and resolve reported customer problems and issues. The contractor shall provide Tier I, Tier II and Tier III Client Services Support to address and resolve user reported problems concerning the MODS software.

The MODS software has multiple, distinct program processes that must interact in order to make the software operate correctly. Contractor personnel shall possess the technical skills required to understand the logic and the multiple, distinct program processes that must interact in order to perform all the functions within the MODS.

The contractor shall diagnose problems, identify fixes, make necessary changes to the application code or system architecture and respond as specified below. The MODS Program Manager may establish priorities for the resolution of problems and, at any time, identify a problem as “critical,” requiring immediate response. Under this condition, the contractor shall apply all necessary resources and efforts to resolve the problem.

5.2.1 TASK: Tier I Technical Support

The contractor shall provide a centralized Help Desk function designed to receive and process first-report, customer problems and queries.

The contractor shall:

· Receive problem reports

· Analyze, troubleshoot and resolve problem reports

· Refer unsolved problem reports to Tier II Technical Support

· Enter reported problems in an electronic, problem-tracking database

· Track the problem reports to ensure that a final resolution is determined and the reporting caller is notified of the resolution

· Create and maintain MODS user accounts

· Reset expired or locked user passwords

· Identify, analyze and report on problem trends and make tactical and strategic corrective recommendations

· Produce and maintain scripted troubleshooting procedures

· Provide Technical Guidance and Support to all MODS Tasks

Provide Monthly Tier I Metric Report to the Government Program Manager categorizing Help Desk calls of a similar nature and highlighting recurring issues that may need resolution through software modification.

Performance Measure:

Availability

Threshold:

Answer an average of 3000 calls per month 24 hours a day, 365 days per year

Objective:

Same as Threshold

Answer Rate

Calls will be answered within 2 hours 95% of the time

Calls will be answered within 5 minutes 95% of the time

Troubleshooting Procedures

Troubleshooting Procedures will be current with MODS application programs 100% of the time

Problem Tracking

Ensure that 95% of referred problems either are closed within 5 business days or have an “estimated date for closure.” Ensure that no more than 5% exceed the “estimated date for closure.”

Ensure that 100% of referred problems either are closed within 2 business days or have an “estimated date for closure.” Ensure that no more than 2% exceed the “estimated date for closure.

Problem Referral

When beyond the capabilities of Tier I, unresolved problems will be referred to Tier II within 2 hours 95% of the time

5.2.2 TASK: Tier II Technical Support

The contractor shall analyze, troubleshoot and resolve MODS application specific problem reports and serve as a technical liaison for MODS users.

The contractor shall:

· Analyze, troubleshoot and resolve referred problem reports

· Maintain problem report status in an electronic, problem-tracking database

· Refer unsolved problem reports to Tier III Technical Support

· Serve as a liaison between MODS users and MODS developers

· Train help desk staff on new features and system changes

· Answer email questions submitted by users via MODS on-line training suite

· Notify users of known outages and/or technical issues

· Identify, analyze and report on problem trends and make tactical and strategic corrective recommendations (could take the form of a Request for Change)

· Provide Technical Guidance and Support to all MODS Tasks

Provide Monthly Tier II Metric Report to the Government Program Manager categorizing Help Desk calls of a similar nature and highlighting recurring issues that may need resolution through software modification.

Availability

Provide Tier II help desk support during core duty hours, 0700 to 1700 Eastern Time, Monday through Friday. Provide an on-call capability for after duty hours to handle approximately 50 calls per month.

Problem Response

An…