W9124J-19-R-0008_RPLANS_Amendment_0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

a. The purpose of amendment P0001 is to provide responses to questions received and provide an updated RPLANS solicitation based on responses to those questtions.

b. No extension of the closing date w as made w ith this amendment.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 66

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 05-Mar-2019

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W9124J19R0008

X 9B. DATED (SEE ITEM 11)

14-Feb-2019

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

05-Mar-2019

CODE

MICC - FSH

ATTN: MICC - FSH

2205 INFANTRY POST RD

210-466-2145

FORT SAM HOUSTON TX 78234-1361

W9124J 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W9124J19R0008

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

PERFORMANCE WORK STATEMENT

Performance Work Statement (PWS) Real Property Planning and Analysis System (RPLANS) Technical Support Services Office of the Assistant Chief of Staff Installation Management, Washington, DC

PART 1. GENERAL.

1.1. DESCRIPTION OF SERVICES/INTRODUCTION. This is a non-personal services contract to provide for planning, operating, maintenance, and enhancement of the Real Property Planning and Analysis System (RPLANS) and the analysis of data therein. The tasks within this contract require in-depth knowledge of real property policy, master planning policy, Army force structure, Army facility management, Army space planning criteria, Army Standards and OACSIM Business Systems (Headquarters Installation Information System (HQIIS), Army Stationing and Installation Plan (ASIP), RPLANS, and Installation Status Report (ISR)). The Contractor shall maintain RPLANS, as outlined in the Performance Work Statement (PWS), regardless of when a process, document, or system enhancement was developed. The Contractor shall be responsible for the maintenance of RPLANS in its entirety, even if an issue resulted from an action taken outside of their period of performance. 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. The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform services in support of RPLANS as defined in this PWS except for those items specified as government furnished property and services.

The Contractor shall perform to the standards in this contract.

1.2. BACKGROUND. The Office of the Assistant Chief of Staff for Installation Management (OACSIM) is responsible for maintaining, updating, and improving the RPLANS. The RPLANS is the Army’s automated master planning system and is the official source for Army facility requirements. RPLANS data supports the development of Army master plans, Capital Investment Strategy, Facility Investment Strategy, Total Army Analysis (TAA), Army Stationing Analysis, the Army’s Strategic Plan for Rightsizing the Installation Footprint, and the Army’s Military Construction program. This support contract ensures that RPLANS is fully functional, meets user needs, remains compatible with related Army Systems, reflects current Army space planning criteria and standards, and complies with all reporting requirements.

1.2.1 RPLANS is an OACSIM installation management system. RPLANS provides the Army with an automated planning system that generates facility allowances by location for the current year and six planning years based on units and population assigned using space planning criteria, algorithms and business rules. RPLANS supports master planning efforts at all levels, including Army Installations, Land Holding Commands (LHC), and Headquarters Department of the Army (HQDA). Users at each level share a common need to correlate real property assets with facility requirements to estimate excesses and deficits at each Army location. The modeled facility deficits help justify and prioritize new construction projects for the Program Objective Memorandum (POM) and the modeled facility excesses help support repurposing and demolition decisions.

1.2.2 RPLANS generates facility allowances by Category Code for all Army locations worldwide. The system integrates assigned population, real property assets, space planning criteria, and programmed new construction from official sources to create a Tabulation of Existing and Required Facilities (TAB) for each Army base, as mandated by AR 210-20. The TAB identifies facility excesses and deficits by location by comparing permanent real property assets, including programmed construction, to facility requirements. RPLANS generates a facility buyout cost for all facility deficits using Department of Defense (DoD) cost factors. RPLANS provides the capability for installations to edit requirements in cases where calculated allowances do not fully account for mission, equipment or personnel impacts on infrastructure; an automated process allows for review and approval or change of edited requirements by higher headquarters.

1.2.3 RPLANS provides a Planning Module to assist with unit stationing and relocation actions. The RPLANS Planning Module has been used extensively to support Base Realignment and Closure (BRAC), Army Modular Forces (AMF), Global Defense Posture Realignment (GDPR), Grow the Army (GTA), Total Army Analysis (TAA) and Installation Master Planning across the Army.

1.2.4 The RPLANS system provides links to the underlying data used to generate the allowances, programmed construction assets, and real property assets allowing the users a way to validate the data accuracy. The Army Space Planning Criteria Repository within RPLANS provides a single source of facility planning criteria at the category code level and documents the algorithms or methodology that RPLANS employs when calculating facility allowances; referencing the facility standards and design criteria sources.

1.3. OBJECTIVES. Maintain and update the RPLANS system and database; provide quality RPLANS user training and technical assistance; create and update all documentation needed to maintain and update the system;

provide data requests as required; and conduct data analysis to improve accuracy of all existing data sources.

1.4. SCOPE. The Contractor shall provide all personnel and supervision necessary to perform the services defined in the PWS. The Contractor shall perform all tasks to the standards set forth in this document. The Contractor shall have an in-depth understanding of the requirements and the requisite depth and breadth of experience to make the program a success. The Contractor shall provide personnel that have the capability and experience to focus on, manage and execute the daily activities required to support this requirement. The Contractor shall identify problems and take full advantage of the expertise within their organization to resolve contract/task order issues that may arise.

1.5. PERIOD OF PERFORMANCE. The period of performance shall be for one (1), 10 month base period and four (4), 12 month option periods.

1.6. GENERAL INFORMATION.

1.6.1. Quality Control. The Contractor shall develop and maintain an effective Quality Control Plan (QCP) to perform services in accordance with this PWS. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Contractor’s Quality Control Plan is the means by which the Contractor assures that the work complies with the requirement of the contract/task order. As a minimum, the Contractor shall develop Quality Control procedures that address the areas identified in Technical Exhibit 1, “Performance Requirements Summary.” The Contractor shall submit a Quality Control Plan (QCP) with the initial proposal. The Government incorporates the QCP in the contract that results from this solicitation. The QCP is releasable under the Freedom of Information Act. After acceptance of the QCP the Contractor will receive the contracting officer’s acceptance in writing of any proposed change to the QCP.

1.6.2. Quality Assurance. The Government evaluates the Contractor’s performance under this contract/task order in accordance with the Quality Assurance Surveillance Plan (QASP). The QASP highlights what the Government must do to monitor the Contractor’s performance in accordance with the performance standards. It QASP defines application of the performance standards, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.3. Recognized Holidays. The Government does not require Contractors to provide on-site support services at government sites on Federal Holidays. Contractors shall be required to follow their respective company policy in regards to holiday and leave reporting. The following are Federal Holidays each calendar year:

New Year's Day M.L. King Day President's Day Memorial Day Independence Day Labor Day

Columbus Day Veterans Day Thanksgiving Day Christmas Day

1.6.4. Hours of Operation. The Contractor shall be responsible for conducting business between the hours of 0700

- 1700 (Eastern) Monday thru Friday except Federal holidays. The Contractor shall at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS. The Contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.6.5. Place of Performance. All work performed under this contract/task order is performed at the Contractor facility. Key contractor personnel shall be required to attend meetings and workshops at offices within the National Capital Region. It is preferred, that Contractors that require a GFE, HEN, and Server access reside within a 100-mile radius of the National Capital Region.

1.6.6. Type of Contract. The Government shall award a firm-fixed price contract for this solicitation.

1.6.7. Security Requirements. This is an unclassified contract and Contractors do not have access to classified information. However, key personnel and alternates shall be required to attend classified meetings or briefings in the performance of this contract. Therefore, key personnel and alternates in support of this contract must show a valid interim or final Secret clearance in the Joint Personnel Adjudication System (JPAS) to gain access.

1.6.8. Personal Identity Verification (PIV).

1.6.8.1. The Contractor shall comply with PIV procedures implemented by Homeland Security Presidential Directive-12 (HSPD-12), Federal Information Processing Standards Publication (FIPS PUB) Number 201-1, Office of Management and Budget (OMB) Guidance M-05-24 and OACSIM.

1.6.8.2. The Contractor shall insert this clause, FAR 52.204-9 as required by FAR 4.1303, in all subcontracts when the subcontractor is required to have physical access to a Federally-controlled facility or access to a Federally-controlled information system.

1.6.8.3. In accordance with HSPD-12, OMB M-05-24 and FIPS 201-1, unless a previous favorable background investigation has been completed in the last ten (10) years, all Contractor employees shall be the subject of the appropriate background investigation conducted by the Government.

1.6.8.4. No Contractor employee will commence work until the personnel security questionnaire (PSQ) has been completed, reviewed and submitted to the Office of Personnel Management (OPM).

1.6.8.4.1. When access to classified information is required or the Contractor employee shall be providing full-time, on-site support at a secure Government facility, the Contractor shall process the investigation request through the Defense Industrial Security Clearance Office (DISCO).

1.6.8.4.2. When contract support does not involve access to classified information and support is not provided at a secure Government facility, the Government will process the investigation request with assistance from the Government Contract Officer Representative (COR).

1.6.8.5. In addition to the submission of the required PSI, Contractor employees not meeting the minimum requirements of HSPD-12 and FIPS Pub 201-1 will be the subject of a National Crime Information Center (NCIC) check by the appropriate security office prior to beginning work regardless of the sensitivity of the work performed.

1.6.8.6. Non-US citizens cannot perform under this contract/task order unless they complete all provisions of Army Regulation 25-2, Information Assurance and granted approval by the Government for the non-US citizen to perform the required support.

1.6.9. Visit Notifications.

1.6.9.1. If the Contractor has a valid facility clearance (FCL) through DISCO, the Facility Security Officer (FSO) shall submit visit notifications via JPAS in the format prescribed and provided by OACSIM Security through the Government COR.

1.6.9.2. If the Contractor does not have a valid FCL through DISCO, the Contractor shall submit a signed visit request on company letterhead stationary through the Government COR for all Contractor employees supporting the contract. The request will include: Full Name (last, first, middle), Date of Birth (MM/DD/YYYY), Place of Birth (city, state, country), Citizenship, Type of Last Investigation, and Date Last Investigation was completed, if any and shall be the subject of a National Crime Information Center (NCIC) check prior to beginning work.

1.6.10. Non-Disclosures. All Contractor employees fulfilling the requirements of this contract, are required to read and sign a Nondisclosure Statement, prior to beginning work. Performance of this contract may require Contractor employees to access data and information proprietary to the Government agency or of such a nature that its dissemination or use, other than in performance of this contract, would be adverse to the interest of the Government or others.

1.6.11. Security Regulations. All Contractor employees shall read all applicable Government security regulations provided by the Government. Contractor personnel shall familiarize themselves with the Government’s regulations and policies and site-specific regulations regarding access to sensitive materials, computer facility/IT network access, issue of access credentials, etc., which shall be provided as required by the Government.

1.6.12. Physical Security. The Contractor shall perform all contract tasks off the Government worksite. In the event that the Contractor employee is required to work on the Government site, the Contractor employee must safeguard all Government property provided for Contractor use. The Contractor must secure all Government facilities, equipment, and materials at the close of each work period.

1.6.13. Access Credentials. The Contractor shall establish and implement methods of making sure all access credentials (Common Access Card (CAC); DD Form 1466, DoD Building Pass; Kastle Key Systems) issued to the Contractor employee by the Government are not lost or misplaced and are not used by unauthorized persons. The Contractor shall not duplicate any access credentials issued by the Government to the Contractor. The Contractor shall develop procedures covering access credentials for inclusion in the QCP. Such procedures shall include turn-in of any issued access credentials by Contractor personnel who no longer require access to Government information systems or Government facilities.

1.6.13.1. In the event access credentials are lost or damaged, the Contractor employee shall immediately notify the COR who will notify OACSIM Security of the loss or damage and request re-issue of the credential.

1.6.13.2. Multiple occurrences of loss or damaged access credentials shall be reported to the Contracting Officer (KO). If access credentials are lost, the Government is responsible for replacement of access credentials. The Contractor must pay for the total cost associated with re-issuing the credential(s) through a monthly contract payment deduction.

1.6.13.3. The Contractor shall prohibit the use of Government issued access credentials by any persons except the Contractor employee issued the credential. The Contractor shall prohibit the opening of secure or locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the OACSIM Security Office.

1.6.14. Identification of Contractor Employees. All Contractor personnel attending meetings, answering Government telephones and working in other situations where their Contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. Contractor personnel shall appropriately disclose all documents or reports as Contractor products and all Contractor participation at Government meetings. Contractor employees with assigned duties requiring on-site performance shall meet the requirements to obtain a Department of Defense building pass.

Contractor employees requiring use of Government information systems or facilities shall meet the criteria required to obtain a Common Access Card and building specific identification badge requirements/specifications.

1.6.15. Anti-Terrorism and Operations Security Requirements.

1.6.15.1. AT Level I Training. All Contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract/task order start date or effective date of incorporation of this requirement into the contract/task order, whichever is applicable. The Contractor shall submit certificates of completion for each Contract employee and subcontractor employee requiring access, to the COR or to the KO, if a COR is not assigned, within 15 calendar days after completion of training. AT level I awareness training is available at the following website: https://jkodirect.jten.mil Course # JS-US007-14.

1.6.15.2. Access and General Protection/Security Policy and Procedures. Contractor and all associated subcontractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by Government representative). The Contractor shall also provide all information required for background checks to meet installation access requirements to the installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce 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.

1.6.15.3. iWATCH Training. The Contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training informs employees of the types of behavior to watch for and instructs employees to report suspicious activity to the COR. The Contractor must complete iWATCH Training within 30 calendar days of contract award and within 15 calendar days of new employees commencing performance with the results reported to the COR NLT 45 calendar days after contract award. The COR will provide training slide deck.

1.6.15.4. Contractor Employees Requiring Access to Government Information Systems. The ATCTS (Army Training Certification Tracking System) must identify all Contractor employees requiring access to a Government information 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.

1.6.15.5. Operations Security (OPSEC) Training. Per AR 530-1, OPSEC, new Contractor employees must complete Level I OPSEC training within 30 calendar days of their reporting for duty. All Contractor employees must complete annual OPSEC awareness training and adhere to the organization’s security program. OPSEC training is available at the following website: http://cdsetrain.dtic.mil/opsec/

1.6.15.6. 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 and annually thereafter. All Contractor employees working IA/IT functions must comply with DoD and Army training requirements identified in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of employment.

1.6.15.7. Information Assurance (IA)/Information Technology (IT) certification. Per DoD 8570.01-M, DFARS

252.239.7001 and AR 25-2, the Contractor employees supporting IA/IT functions shall be appropriately certified upon contract award. The baseline certification, as stipulated in DoD 8570.01-M, shall be completed upon contract award.

1.6.15.8. Common Access Card (CAC). Before CAC issuance, the Contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries Tier 1 or an equivalent or higher investigation in accordance with Army Directive 2014-05. The Contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non DOD- federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. The sponsoring activity may issue an initial CAC based on a favorable review of the FBI fingerprint check and a successfully scheduled Tier 1 at the Office of Personnel Management.

1.6.15.9. Threat Awareness Reporting Program. For all Contractors with security clearances. Per AR 381-12 Threat Awareness and Reporting Program (TARP), Contractor employees must receive annual TARP training by a CI agent or other trainer as specified in 2-4b. Threat Awareness training is available at the following ALMS website:

https://www.lms.army.mil

1.6.16. Special Qualifications. Paragraph 1.6.19 denotes specific Key Personnel qualifications.

1.6.16.1. The Contractor’s firm and the key personnel assigned to work these contract tasks shall have at least three

(3) years of current working experience with Federal Real Property, Army Space Planning Criteria, Army Standards, Army Force Structure, and DoD Business Systems (ASIP, GFEBS, HQIIS, RPLANS, ISR) within the last five years. The work associated with this contract is complex in nature and requires current specialized work experience.

The Contractor shall assign a Senior Project Manager to oversee the work execution.

1.6.16.2. All Contractors shall be functionally proficient in Microsoft Word, Microsoft Excel, Microsoft PowerPoint, Microsoft Visio, Microsoft Outlook, Microsoft Access, Adobe Acrobat and Internet Explorer (or a comparable internet browser application).

1.6.16.3. The specific Contractors who will directly support RPLANS system operations shall be functionally proficient in MS Server 2012 or 2016, Oracle 12c., Oracle APEX 5.1, Oracle APEX FOEX, DHTMLX, Oracle JET, Any Chart, jQuery, ExtJS, JavaScript, HTML, SQL, PL/SQL, CSS, Oracle Database Administration, and Oracle HTTP Server/Oracle Web Tier.

1.6.16.4. All Contractors shall have a bachelor's degree in any discipline from an accredited college or university.

Work experience is not a replacement for a completed bachelor’s degree. Additional qualifications are required for key personnel as noted below in 1.6.19.

1.6.16.5. It is recommended (not required) that the Contractor’s firm posses a Capability Maturity Model Integration (CMMI) Maturity Level 3 and an ISO 20000 certification. The CMMI Maturity Level 3 demonstrates that the Contractor follows best practices to ensure effectiveness, efficiencies, and quality of services and that they are committed to providing the Army with reliable, high quality services, and solutions. The ISO 20000 certification ensures that the Contractor has institutionalized quality management best practices that mirror the Information Technology Infrastructure Library (ITIL) framework and therefore are committed to providing quality IT services and support.

1.6.17. Post Award Conference/Periodic Progress Meetings. The Contractor shall attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The KO, COR, and other Government personnel, as appropriate, will meet periodically with the Contractor to review the Contractor's performance. At these meetings the KO will apprise the Contractor of how the Government views the Contractor's performance and the Contractor will apprise the Government of problems, if any. The Contractor must take appropriate action to resolve outstanding performance issues. These meetings shall be at no additional cost to the Government.

1.6.18. Contracting Officer Representative (COR). The COR will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract;

perform inspections necessary in connection with the contract performance; maintain written and oral communications with the Contractor concerning technical aspects of the contract; issue written interpretations of technical requirements; including Government drawings, designs, specifications; monitor Contractor's performance and notify both the KO and Contractor of any deficiencies; coordinate availability of Government furnished property, and provide site entry for Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting contract.

1.6.19. Key Personnel. The table below identifies Key Personnel required to perform this contract. The Contractor shall provide complete resumes for key personnel and proposed substitutes including any additional information requested by the KO. The Contractor shall notify the KO in writing if any replacements for key personnel and provide the replacement name(s) and telephone number(s) within 14 calendar days. The KO will notify the Contractor within fourteen (14) calendar days after receipt of all required information to approve the key personnel replacements. The Government must review all key personnel resumes to ensure they meet the qualifications listed in the table below. Key personnel must be able to attend in-person meetings in the Pentagon when remote participation is not possible. The key personnel required to attend meetings in the Pentagon, or within the NCR, on short notice (one to two work days), are the Senior Project Manager, Senior Systems Technical Architect, and Senior Functional Analyst. Typically, Contractors are required to attend one meeting per week onsite at the Pentagon, if teleconference capability is not available. The Government Program Manager (PM) determines the required Contractors based on the subject of the meeting. In addition, the Contractor shall provide a project manager who shall be responsible for the performance of the work. The Contracting Officer receives notification in writing of the Project Manager and alternate. The project manager or alternate shall have full authority to act on all contract matters relating to daily operation of this contract. The project manager or alternate shall be available between 0700 and 1700 EST, Monday thru Friday except Federal holidays. All key personnel must have at least a bachelor’s degree from an accredited college or university recognized by either the Council for Higher Education Accreditation or the U.S. Department of Education. Higher education (i.e., a master’s degree) is not a substitute for work experience. All key personnel must have a valid Secret security clearance in place at time of proposal submission from the Defense Industrial Security Clearance Office.

Key Personnel

Completed Degree from Accredited College or

University

Five* Years Current Work Experience

Three* Years Current Specialized Work

Experience

Security Clearance

During Contract

Performance

Minimum Certifications

Senior Project Manager

Business Administration, Management Information Systems degree, Engineering degree, Management degree

Directorate of Public Works (DPW) or DoD equivalent

Federal Real Property, Army Space Planning Criteria, Army Standards; Army Force Structure; and DoD Business Systems (ASIP, GFEBS, HQIIS, RPLANS, ISR).

Secret Project Management Institute (PMI), Project Management Professional

Senior Systems Technical Architect

Computer Science degree, Computer Engineering degree, Cyber Security degree, Computer Information Systems degree, Management Information Systems degree

Chief Information Officer (CIO)/G6, Network Enterprise Technology Command (NETCOM), or other DoD equivalent.

DoD Information Technology and DoD Business Systems

(ASIP, GFEBS, HQIIS,

RPLANS, ISR) and RPLANS official data sources

Secret Certified Information Systems Security Professional (CISSP), Security+, or Global Information Assurance Certification (GIAC), APEX 5.1, APEX 5.1

Plug-in FOEX, **Senior Database Administrator (DBA)/System Administrator

(SA)

Computer Science degree, Computer Engineering degree, Cyber Security degree, Computer Information Systems degree, Management Information Systems degree

CIO G6, NETCOM, or DoD equivalent

DoD Information Technology and DoD Business Systems

(ASIP, GFEBS, HQIIS,

RPLANS, ISR) and RPLANS official data sources

Secret Oracle 12c APEX 5.1, Developer Certified Expert or Oracle 12c PL/SQL Developer Certified Associate or Oracle 12c Advance PL/SQL Developer Certified Professional Per DoD 8570.01-M, IA Baseline IA Certification Technical Level II (one of the following - GICSP, GSEC, Security+ CE, SSCP, CCNA-

Security) and CE/OS Certificate

**Senior Information

Computer Science degree, Computer Engineering

CIO G6, NETCOM, or DoD equivalent

DoD Information Assurance/Network Security

Secret Per DoD 8570.01-M, IA Baseline IA

Assurance Security Officer

(IASO)

degree, Cyber Security degree, Computer Information Systems degree, Management Information Systems degree

Certification Technical Level II (one of the following - GICSP, GSEC, Security+ CE, SSCP, CCNA-

Security) and CE/OS Certificate

Senior Functional Analyst (Subject Matter Expert

(SME))

Bachelor’s Degree Directorate of Public Works (DPW)

Military Planning, Federal Real Property; Army Space Planning Criteria; Army Standards and Standard Designs; Army Force Structure; DoD Business Systems (ASIP, GFEBS, HQIIS, RPLANS, ISR);

statistical modeling techniques

Secret

* The three years of current specialized work experience can be a subset of the 5 years of current work experience, in installation management, if the work experience was in one of the specialized experience areas.

** One person can hold more than one of the following key personnel positions Senior DBA/SA and Senior IASO, as long as qualifications for both positions are satisfied and all required tasks supported.

1.6.19.1. Senior DBA/SA: At least one Contractor shall obtain and maintain the training necessary to perform server administrator tasks and stay current with emerging administrator requirements. Upon award, the Contractor shall obtain the necessary certifications and requirements necessary to access the government network and RPLANS servers. The Contractor shall maintain the necessary certifications and requirements throughout the life of the contract.

1.6.19.2. IASO: Upon award, the Contractor shall assume the role of IASO to ensure compliance with the requirements of DoD 8570.01-M, Information Assurance (IA) Workforce Improvement Program and maintain compliance throughout the life of the contract. The Contractor shall work with designated personnel in the OACSIM Information Technology Directorate and the designated host environment to ensure RPLANS maintains compliance with all required scans, tests, and updates in support of the certification and accreditation/authorization of RPLANS. The Contractor shall perform annual tests on RPLANS such as Contingency Test, Security Control Test, and the Annual Security Review.

1.6.19.3. All questions raised by the KO related to qualifications or competence of any person assigned to perform under the contract, requires that the Contractor provide the burden of proof that the person is qualified as prescribed herein.

1.6.19.4. The Contractor shall have personnel, organization, and administrative control necessary to meet all requirements specified in the PWS. The work history of each Contractor employee shall identify experience directly related to perform the required contract tasks and functions. The KO in conjunction with the Government Program Manager reserves the right to determine if a given work history contains the necessary and detailed experience to ensure effective and efficient performance.

1.6.19.5. An emergency notification list shall be maintained for all key Contractor personnel and made available to the COR and PM.

1.6.19.6. The Contractor shall ensure that its personnel are qualified to perform their assigned tasks at the beginning of the period of performance and that the key personnel work full-time on the RPLANS contract.

1.6.20. Contractor Travel. The Contractor may be required to travel to Government-designated sites within the National Capital Region to attend meetings at no additional cost to the Government. No travel is anticipated outside the National Capital Region.

1.6.21. Phase-In/Phase-Out Period. The Government will provide a list of phase-in tasks to minimize any decreases in productivity and to prevent possible negative impacts on additional services. The incoming Contractor shall have the key personnel on-board, at the onset of the sixty (60) day phase-in / phase-out period. During the phase in period, the incoming Contractor shall become familiar with all contract requirements in order to commence full performance of services on the contract start date. The phase-in tasks must include all tasks associated with the performance of a quarterly update.

1.6.21.1. The incoming Contractor shall accomplish all required phase-in tasks associated with maintaining, supporting, and updating RPLANS from their off-site location. The Government will assist with obtaining access to required facilities and systems.

1.6.21.2. The incoming Contractor shall provide a final phase-in report, covering all phase-in tasks, no less than five days prior to the conclusion of the phase-in period.

1.6.21.3. If phase-in tasks are not accomplished, the COR will notify the KO in writing and the KO will require the Contractor to remedy or cure performance. If the Contractor fails to remedy performance issues the KO will take the appropriate action.

1.6.22. Deliverables. The Contractor shall submit all draft and final deliverables on the Government network by the 10th of each month. The Contractor shall include each deliverable number in the title. If the Contractor is not able to perform this function, the Contractor shall notify the Government PM or COR no less than three (3) business days prior to the due date.

1.6.23. Organizational Conflict of Interest. The Contractor and subcontractor personnel performing work under this contract may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the KO immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the KO to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the KO and in the event the KO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the KO may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements, which may be affected by the

OCI.

1.6.23.1. Purpose of OCI clause.

1.6.23.1.1. The Contractor does not obtain an unfair competitive advantage by establishing the ground rules for a future competition.

1.6.23.1.2. The Contractor's objectivity and judgment are not biased because of its present or future interests (financial, contractual, organizational, or otherwise), which relate to work performed under this contract.

1.6.23.1.3. The Contractor does not obtain an unfair competitive advantage by virtue of its access to non-public or proprietary information belonging to others.

1.6.23.2. Definitions.

1.6.23.2.1. The term “Contractor” herein used means: (a) the organization (hereinafter referred to as "it" or "its") entering into this agreement with the Government; (b) all business organizations with which it may merge, join or affiliate now or in the future and in any manner whatsoever, or which hold or may obtain, by purchase or otherwise, direct or indirect control of it; (c) its parent organization if any and any of its present or future subsidiaries, associates, affiliates, or holding companies, and; (d) any organization or enterprise over which it has direct or indirect control now or in the future.

1.6.23.2.2. The term "proprietary information" for purposes of this clause means any information considered so valuable that the owners classify the information and licenses as secret. The Government can furnish non-proprietary information without limitations on its use, or which is available without restrictions from other sources.

1.6.23.2.3. Organizational Conflicts of Interest Examples. The following examples illustrate situations in which organizational conflicts of interest may arise. These examples are not all inclusive.

1.6.23.2.3.1. Biased Ground Rules. This type of conflict may arise in situations where a company sets the ground rules for a future competition. For example, when a Contractor develops requirements then competes to provide products or services to satisfy those requirements, thus obtaining a competitive advantage.

1.6.23.2.3.2. Impaired Objectivity. This type of conflict may exist where a Contractor’s obligations under a contract require objectivity, but another role of the Contractor casts doubt on its ability to be truly objective. An example of this type of conflict is where a Contractor’s work under one contract entails evaluating itself, its affiliates, or its competitors under a separate contract.

1.6.23.2.3.3. Unequal Access to Information. This type of conflict may arise when a Contractor has access to nonpublic or proprietary information as part of its performance under a contract that gives it an unfair advantage in a competition for a later contract.

1.6.23.2.3.4. General Constraints. The provisions of FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest, concerning organizational conflicts of interest govern this contract. Potential conflicts may exist in accordance with FAR 9.505-1, Providing Systems Engineering and Technical Direction, through 9.505-4, Obtaining Access to Proprietary Information. In this regard, the Contractor is responsible for identifying any actual or potential organizational conflicts of interest to the KO that arise as the result of performance under this contract. To avoid or mitigate a potential conflict related to performance under this contract, the KO will impose appropriate constraints such as the constraints discussed below. Since it is impossible to foresee all of the circumstances that might give rise to organizational conflicts of interest, the constraints discussed below are not all inclusive and the KO may impose constraints other than, or in addition to, the constraints listed below.

(1) The Contractor agrees that if it provides, under a contract or contract/task order or delivery order, systems engineering and technical guidance for systems and programs, but does not have overall contractual responsibility, it will not be allowed to be awarded a contract or task or delivery order to supply the system or any of its major components or be a Subcontractor or consultant to a supplier of the system or any of its major components. (FAR 9.505-1).

(2) The Contractor agrees that if it prepares complete specifications for non-developmental items or assists in the preparation of work statements for a system or services under a contract or contract/task order or delivery order, cannot furnish these items, either as a prime Contractor, a Subcontractor or as a consultant. (FAR 9.505-2).

(3) The Contractor agrees that it will neither evaluate nor advise the Government with regard to its own products or activities. The Contractor will objectively evaluate or advise the Government concerning products or activities of any prospective competitors. (FAR 9.505-3).

(4) The Contractor agrees that if it gains access to proprietary information of other companies, it will exercise diligent effort to protect such proprietary information from unauthorized use or disclosure (FAR 9.505-4). In addition, the Contractor agrees to protect the proprietary information of other organizations disclosed to the Contractor during performance of this contract with the same caution that a reasonably prudent Contractor would use to safeguard highly valuable property. The Contractor also agrees that if it gains access to the proprietary information of other companies it will enter into written agreements with the other companies to protect their information from unauthorized use or disclosure for as long as it remains proprietary and to refrain from using the information for any purpose other than that for which it was furnished. The Contractor shall provide copies of such agreements to the KO.

(5) If the Contractor, in the performance of this contract, obtains access to plans, policies, reports, studies, financial plans, data or other information of any nature which has not been released or otherwise made available to the public, the Contractor agrees that without prior written approval of the KO, it shall not: (a) use such information for any private purpose unless the information has been released or otherwise made available to the public, or (b) release such information unless release is otherwise authorized under the contract or such information has previously been released or otherwise made available to the public by the Government.

1.6.23.2.3.5. Non-Disclosure Agreements. The Contractor shall obtain from each employee who has access to proprietary information under this contract, a written agreement which shall in substance provide that such employee shall not, during his/her employment by the Contractor or thereafter, disclose to others or use for their benefit, proprietary information received in connection with the work under this contract. The Contractor shall educate its employees regarding the restrictions imposed by FAR 9.505-4 so that they will not use or disclose proprietary information or data generated or acquired in the performance of this contract except as provided herein.

Contractor personnel shall sign a nondisclosure agreement before starting work under the contract. Failure to comply with this clause shall is an adequate cause for removal of a Contactor employee from employment. The Contractor’s employment contracts with their employees shall include a provision to provide for the removal under these conditions.

1.6.23.2.3.6. Training. The Contractor shall effectively educate its employees, through formal training, company policy, information directives and procedures, in an awareness of the legal provisions of FAR Subpart 9.5 and its underlying policy and principles so that each employee will know and understand the provisions of that Subpart and the absolute necessity of safeguarding information from anyone other than the Contractor's employees who have a need to know, and the US Government.

1.6.23.2.3.7. Subcontracts. The Contractor agrees that it will include the provisions in paragraphs d., e., and f. above and this paragraph in consulting agreements, teaming agreements, and subcontracts of all tiers which involve access to information or the performance of services described in paragraph d. above. The use of this clause in such agreements shall substitute the word "Consultant" or "Subcontractor" for the word "Contractor" whenever the latter appears.

1.6.23.2.3.8. Additional Constraints. If this contract provides for the issuance of task or delivery orders, such orders may impose additional requirements and restrictions relating to this clause to include the requirement for the Contractor and its subcontractors and employees to furnish the Government with written non-disclosure agreements or statements of no conflict of interest. With regard to any proposal submitted by the Contractor in response to a Request for Task or Delivery Order Proposal, by submitting its proposal the Contractor represents that it has disclosed to the KO, prior to the issuance of the task or delivery order, all facts relevant to the existence or potential existence of organizational conflict of interest as that term is used in FAR Subpart 9.5.

1.6.23.2.3.9. Conflicts Involving Future Procurements. The award of this contract, task or delivery orders shall not constitute or be interpreted as a determination that the Contractor is eligible to participate in future procurements, developmental efforts, implementation efforts, or related activities. Only the KO for such efforts, applying the rules, principles, and procedures of FAR Subpart 9.5 has the authority to determine whether a conflict exists in connection with such procurements.

1.6.23.2.3.10. Representations and Disclosures.

(1) The Contractor shall disclose all relevant facts to the KO, prior to contract award, related to existence or potential existence of organizational conflict of interest as noted in FAR Subpart 9.5.

(2) The Contractor shall make a prompt and full disclosure in writing to the KO if they discover an organizational conflict of interest or potential conflict of interest after award of this contract. The disclosure shall include a description of the action the Contractor has taken or proposes to take in order to avoid or mitigate such conflict.

1.6.23.2.3.11. Remedies and Waiver.

(1)…