NST MAC PWS.pdf

Performance Work Statement (PWS) for NAVSUP Strategic Transformation (NST) Contract

16 December 2020

1.0 Introduction:

The NAVSUP mission is to provide supplies, services, and quality-of-life support to the Navy and Joint warfighter; NAVSUP manages supply chains that provide material for Navy aircraft, surface ships, submarines and their associated weapons systems. NAVSUP provides centralized inventory management for Navy's non-nuclear ordnance stockpile.

In addition, NAVSUP provides a wide range of base operating and waterfront logistics support services, coordinating material deliveries, contracting for supplies and services, and providing material management and warehousing services.

For the Navy Supply Chains to operate efficiently and effectively, improvements are needed to better achieve End to End (E2E) supply chain orchestration, integration, and synchronization of operations, activities and investments of all stakeholders. As such, NAVSUP and other Department of the Navy (DON) commands have endeavored on a number of large, complex transformational initiatives to address these challenges.

2.0 Background:

2.1 Recent Events: Beginning in 2017, NAVSUP began a journey of reform transformation to review and transform the internal NAVSUP supply chain efficiencies. This was in line with the Presidential and Department of Defense transformations. This transformation has made various achievements such as a 20% reduction of the most critical orders; achieving a Mission Capability for the F/A-18 of 341; reaching the lowest levels in aviation critical backorders in 10 years; and an overall reduction in unfilled customer requirements of 12%. Many of these achievements were accomplished by increasing supply chain investments in wholesale and retail stock levels and intermediate and depot-level aviation maintenance.

In Fall 2020, Navy leadership launched NSS-Supply, a cross-functional and cross command, strategic scale supply chain reform. The NSS-Supply will be governed by a steering committee co-chaired by the VCNO. It will bring together all key supply chain leaders in order to elevate strategic supply chain decision making and increase visibility and accountability to enhance supply chain performance.

NAVSUP, as the supported commander of NSS-Supply, will be responsible for framing the key strategic supply chain decisions, presenting decision points to leadership, and orchestrating implementation efforts across the supporting commands. In this way, NSS-Supply will coordinate the system and drive higher supply chain performance.

2.2 Requiring Organization: The organization requiring the services outlined in the

Performance Work Statement (PWS) is:

Naval Supply Systems Command Naval Supply Activity (NSA) Mechanicsburg, Suite 309 5450 Carlisle Pike Bldg 409 Mechanicsburg, PA 17055

3.0 Scope: The purpose of this PWS is to establish a contractual vehicle that will enable

NAVSUP and other DON commands to obtain strategic contractor support services to further address the challenges affecting the Navy Supply Chain.

3.1 Major Engagement Areas: Task orders issues will focus on provision of contractor services to support the achievement and implementation of strategic level transformation initiatives as follows:

3.1.1 NSS-Supply: NSS-Supply is a cross functional, cross command supply chain reform initiative. NSS-Supply currently has six pillars of focus to include: 1) Achieve E2E integration, 2) Establish demand management, 3) Optimize Working Capital Fund Allocations, 4) Shape Industrial Base, 5) Expand Organic Repair and 6) Increase E2E velocity.

3.1.2 Perform to Plan (P2P) Logistics: P2P Logistics is the most recent instance of P2P Navy initiatives. P2P Logistics is focused on the supply chain performance starting with the supplier and continuing through transportation, proper positioning and distribution. It is focused on understanding and reducing the Logistics Response Time as its key driver metric.

3.1.3 Supply Chain and Logistics Technology: The Enterprise Information

Technology that directly support the Navy’s supply chain are managed and operated in a way that affect NAVSUP’s and other DON command’s abilities to fulfill their Mission(s).

3.1.4 NAVSUP/DON Enterprise Transformations: NAVSUP and other DON commands continue to improve and look for greater efficiency and effectiveness in fulfilling its mission. As the Navy continues to improve and change, NAVSUP and other DON commands need to be ready to transform to be what the Navy needs.

3.2 Scope of Services: The scope also allows ancillary services in support of those objectives. Transformational tasks include but are not limited to:

• Strategic Development and Planning

• Improve Operational effectiveness and performance

• Enable enterprise-wide reform

• Create and sustain data-driven decision making

• Support broader digital transformation

• Build organizational success through redesign

• Enterprise Risk Management

• Process modeling and related data capture

• Enable Data driven decision making

• Cultural transformation

• Digital transformation

• Organizational Design

• Strategic Planning

• Data analytics

• Governance

• Enterprise Architecture

• Change Management

• Strategic communication

• Design thinking

• Knowledge management

• Cyber transformation

• Prototype Development (ancillary only)

This is NOT an Information Technology (IT) contract; however, IT services, tools, and prototypes may be used/developed as long as it is necessary to provide a total transformational solution to meet agency needs.

4.0 Deliverables: All deliverables must meet the format requirements specified at the task order by the Contracting Officer’s Representative (COR). Documentation related to these services shall be made available electronically.

5.0 Ordering Period: The ordering period for this PWS will be from the Date of Award

(DOA) for five years.

6.0 Location and Travel:

6.1 Location: NAVSUP Headquarters is located at the Naval Support Activity in

Mechanicsburg, PA. The place of performance is determined by the contractor.

The government does not intend to provide government furnished property unless deemed necessary for successful task order performance.

6.2 Travel(TDYs): There are a various number of locations that include the following:

Mechanicsburg, PA Philadelphia, PA Norfolk, VA Patuxent River, MD Arlington, VA Washington, DC San Diego, CA

For some tasks, the contractor may be required to travel to these sites or other Navy/DOD sites in support of projects pre-approved by the TPOC and COR.

Otherwise, the contractor shall use discretion when using travel in order to maximize the effectiveness, and efficiency of task order performance.

7.0 Security:

7.1 General Guidelines: The clause is applicable to United States Nationals living in the U.S. or overseas who are performing work on a Navy contract. This clause does not apply to non-U.S. Nationals (foreign nationals) who are contactor employees performing work overseas.

The investigation of a non-U.S. national at a foreign location must be consistent with a NACI, to the extent possible, and include a fingerprint check against the FBI criminal history database, an FBI investigations file (name check) search, and a name check against the terrorist screening database.

Also, the above cited reference notes that Foreign Nationals may not be granted CAC Credentials until completion of their investigation and not in the interim.

Per DoD 5200.2-R, DoD Components must initiate and ensure completion of a background investigation before applying the credentialing standards to a non- U.S. national at a foreign location. The background investigation must be favorably adjudicated before a CAC can be issued to a non-U.S. national at a foreign location. The type of background investigation may vary based on standing reciprocity treaties concerning identity assurance and information exchanges that exist between the U.S. and its allies or agency agreements with the host country.

SUPTXT204-9400(7-18) Contractor Unclassified Access to Federally Controlled Facilities, Sensitive Information, Information Technology (IT) Systems or Protected Health Information (JUN 2018) Executive Order 13467, Reforming Processes Related to Suitability for Government Employment, Fitness for Contractor Employees, and Eligibility for Access to Classified National Security Information, and Homeland Security Presidential Directive (HSPD)-12, requires government agencies to develop and implement Federal security standards for Federal employees and contractors. The 5 CFR 32 part 157 in concert with DoD Manual 1000.13, Vol 1, implements the Federal Standards.]

7.2 Applicability: This text applies to all DoD sponsored individuals who require

CAC eligibility (or login and P/W if acceptable per contract) for: Physical access to DoD facilities or non-DoD facilities on behalf of DoD; Logical access to information systems (whether on site or remotely); or remote access to DoD networks that use only the CAC logon for user authentication, or access to sensitive and protected information. This applies to the Office of the Secretary of Defense, the Military Departments, the Office of the Chairman of the Joint Chiefs of Staff and the Joint Staff, the Combatant Commands, the Office of the Inspector General of the DoD, the Defense Agencies, the DoD Field Activities, and all other organizational entities within the DoD (hereinafter referred to collectively as the "DoD Components").

Each contractor employee providing services at a Navy Command under this contract is required to obtain a Department of Defense Common Access Card (DoD CAC). Additionally, depending on the level of computer/network access, the contract employee will require a successful investigation as detailed below.

7.3 Access to Federal Facilities: Per HSPD-12 and implementing guidance, all contractor employees working at a federally controlled base, facility or activity under this text will require a DoD CAC. When access to a base, facility or activity is required contractor employees shall in-process with the Command's Security Manager upon arrival to the Command and shall out-process prior to their departure at the completion of the individual's performance under the contract.

7.4 Compliance with Safeguarding Covered Defense Information Controls: In accordance with DFARS 252.204-7008, the contractor is required to represent that it will implement the security requirements specified by National Institute of Standards (NIST) Special Publications (SP) 800-171.

7.5 Safeguarding Covered Defense Information and Cyber-Incident Reporting:

When Unclassified Controlled Technical Information (CTI) or defense information (as marked by the government) is present on the contractor’s system or must implement be in compliance DFARS 252.204-7012. In DFARS 252.304- 7012, the contractor is required “adequate security” for covered defense information that is processed, stored, or transmitted on the contractor’s internal information system or network. In order to provide adequate security, the contractor must, at a minimum, implement the NIST 800-171.

7.6 NIST SP 800-171 Compliance: The Contractor is required to have a system security plan in place, in addition to any associated plans of action to describe how and when any unimplemented security requirements will be met, how any planned mitigations will be implemented, and how and when they will correct deficiencies and reduce or eliminate system vulnerabilities.

7.6.1 NIST SP 800-171 Security Requirement 3.12.4 (System Security Plan:

The contractor is required to develop, document, and periodically update, system security plans (SSP) that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems.

7.6.2 NIST SP 800-171 Security Requirement 3.12.2 (Plans of Action): The contractor is required to develop and implement plans of action and milestones (POAM) designed to correct deficiencies and reduce or eliminate vulnerabilities in their systems.

When ‘adequate security’ requires security measures in addition to the NIST SP 800-171 security requirements (determined as necessary by the contractor), these additional measures will be evaluated and monitored in a manner similar to the NIST SP 800-171 requirements. Plans of action, continuous monitoring and the system security plan (NIST SP 800-171 Security Requirements 312.2-3.12.4)must address all security requirements

7.7 Level I Antiterrorism Awareness Training for Contractors (FEB 2019)

(a)Definition. As used in this clause - Military installation means a base, camp, post, station, yard, center, or other activity under the jurisdiction of the Secretary of a military department or, in the case of an activity in a foreign country, under the operational control of the Secretary of a military department or the Secretary of Defense (see 10 U.S.C.

2801(c)(4)).

(b)Training. Contractor personnel who require routine physical access to a Federally-controlled facility or military installation shall complete Level I antiterrorism awareness training within 30 days of requiring access and annually thereafter. In accordance with Department of Defense Instruction O-2000.16 Volume 1, DoD Antiterrorism (AT) Program Implementation: DoD AT Standards, Level I antiterrorism awareness training shall be completed -

(1) Through a DoD-sponsored and certified computer or web-based distance learning instruction for Level I antiterrorism awareness; or

(2) Under the instruction of a Level I antiterrorism awareness instructor.

(c)Additional information. Information and guidance pertaining to DoD antiterrorism awareness training is available at https://jko.jten.mil/ or as otherwise identified in the performance work statement.

(d)Subcontracts. The Contractor shall include the substance of this clause, including this paragraph (d), in subcontracts, including subcontracts for commercial items, when subcontractor performance requires routine physical access to a Federally-controlled facility or military installation.

7.8 Start Up Period: All contractor resource onboarding documents must be submitted via the prime contractor. The prime contractor shall make all necessary preparations to assume full responsibility for productive performance as of the performance start date.

Definition of "productive":

a. Contractor Information Sheet (CIS)

b. FD-258 fingerprint card

c. Completed EQIP (Electronic Investigation)

d. All contractor resource(s) must have an active JPAS profile

e. JPAS Visit Request submitted by company to hosting Security Management Office (SMO)

f. Common Access Card (CAC)

g. Cyber Awareness Training Certification

h. Antiterrorism Awareness Training for Contractors

Note (1): Invoicing by the contractor will begin as of the commencement of the performance period of services, and no reimbursement will be paid by the Government for efforts expended during the start-up period.

Note (2): Dual Citizenship and Foreign Nationals are not allowed access to the functional/system side of Enterprise Resource Planning (ERP).

7.9 Interim Access: The Command's Security Manager may authorize issuance of a DoD CAC and interim access to a DoN or DoD unclassified computer/network upon a favorable review of the investigative questionnaire and advance favorable fingerprint results. When the results of the investigation are received and a favorable determination is not made, the contractor employee working on the contract under interim access will be denied access to the computer network and this denial will not relieve the contractor of his/her responsibility to perform.

7.10 Denial or Termination of Access: The potential consequences of any requirement under this text including denial or termination of physical or system access in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract.

Contractors shall plan ahead in processing their employees and subcontractor employees. The contractor shall insert this text in all subcontracts when the subcontractor is permitted to have unclassified access to a federally controlled facility, federally-controlled information system/network and/or to government information, meaning information not authorized for public release.

7.11 Contactor’s Security Representative: The contractor shall designate an employee to serve as the Contractor's Security Representative. Within three work days after contract award, the contractor shall provide to the requiring activity's Security Manager and the Contracting Officer, in writing, the name, title, address and phone number for the Contractor's Security Representative. The Contractor's Security Representative shall be the primary point of contact on any security matter. The Contractor's Security Representative shall not be replaced or removed without prior notice to the Contracting Officer and Command Security Manager.

7.12 Background Investigation Requirements and Security Approval Process for Contractors Assigned to or Performing Non-Sensitive Duties:

7.12.1 Contractor employee whose work is unclassified and non-sensitive (e.g., performing certain duties such as lawn maintenance, vendor services, etc.

...) and who require physical access to publicly accessible areas to perform those duties shall meet the following minimum requirements:

7.12.1.1 Must be either a US citizen or a US permanent resident with a minimum of 3 years legal residency in the United States (as required by The Deputy Secretary of Defense DTM 08-006 or its subsequent DoD instruction) and

7.12.1.2 Must have a favorably completed National Agency Check with Written Inquiries (NACI) or T1 investigation equivalent including a FBI fingerprint check prior to installation access.

7.12.2 To be considered for a favorable trustworthiness determination, the Contractor's Security Representative must submit for all employees each of the following:

7.12.2.1 SF-85 Questionnaire for Non-Sensitive Positions

7.12.2.2 Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)

7.12.2.3 Original Signed Release Statements

7.12.3 The contractor shall ensure each individual employee has a current favorably completed National Agency Check with Written Inquiries (NACI) or T1 equivalent investigation, or ensure successful FBI fingerprint results have been gained and investigation has been processed with OPM.

7.12.4 Failure to provide the required documentation at least 30 days prior to the individual's start date may result in delaying the individual's start date. * Consult with your Command Security Manager and Information Systems Security Manager (ISSM)/Information Assurance Manager (IAM) for local policy when IT-III (non-sensitive) access is required for non-US citizens outside the United States.

8.0 Non-Disclosure Agreement and Organizational Conflict of Interest:

8.1 Non-Disclosure Agreement: The Business Sensitive Information Non-disclosure Agreement may be required for this contract.

8.2 Organizational Conflict of Interest: Performance on any of the task orders awarded under the NAVSUP Strategic Transformation (NST) Support contract may, by definition in FAR 9.5, be an OCI as either an Impaired Objectivity or an Unfair Competitive

Advantage (unequal access to information) (OCI). Because the specifics of NST task orders are unknown it is impracticable to require an OCI plan at the IDIQ level; however, if vendors, either during the task order process, during performance of a task order, or at any other time, become aware of an OCI, they shall immediately inform the Contracting Officer. The vendor should provide (in writing) the nature of the OCI and its potential impact. The Contracting Officer will then investigate the matter and determine if there is an OCI and, if there is, whether the Contracting Officer may take any measures to avoid, neutralize, or mitigate the OCI. Those measures may vary depending on the timing of the OCI disclosure and may include submission of an OCI mitigation plan.

Note: If a vendor does not inform the Contracting officer of an OCI of which it has been made aware, the Contracting office may terminate the task order, may remove the vendor as a NST awardee, or take any other action deemed appropriate.

9.0 Other Requirements:

9.1 Key Personnel: Under this contract, the Contractor may be required to provide Key Personnel. In all task orders that require Key Personnel, the contractor shall notify the Contracting Officer (KO) and COR in writing prior to making any change in personnel identified as key for the duration of the task order PWS. Key personnel shall not be vacant for more than 14 calendar days and notification will occur no less than 14 days prior to a key personnel change. The Government shall not be billed for key personnel positions left vacant over 10 calendar days unless the vacancy is due to Government delay and otherwise approved by the KO. If substitutions are to be made, the contractor shall demonstrate that the qualifications of the prospective person(s) are at least equal to the person(s) replaced.

9.2 Key Executive Contact List: Contractor shall maintain and provide a contact list of Key Executive’s to the COR and TOA on a monthly basis (only if updates required).

9.3 Workforce Turnover: Additionally, the Contractor shall provide a qualified, experienced, and stable workforce, throughout the duration of the contract, and maintain a 20% or less employee turnover rate.

9.4 Contractor professionalism: The contractor shall:

9.4.1 Present a professional appearance and maintain professional demeanor and conduct at all times.

9.4.2 Conduct their work assignments IAW project schedules

9.4.3 Function effectively and efficiently during extended periods of high pressure and stress.

9.4.4 Function as an integral member of a team of highly trained professionals responsible for the safety and security of Navy personnel and resources

9.5 Enterprise-wide Contractor Manpower Reporting Application (ECMRA):

The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities;

(3) Y, Construction of Structures and Facilities;

(4) D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322) ONLY;

(5) S, Utilities ONLY;

(6) V, Freight and Shipping ONLY.

The contractor is required to completely fill in all required data fields using the following web address: https://www.sam.gov.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year.

9.6 Common Access Card (CAC): The Government Contractor CAC card serves as the primary method of identification for the contractor employees, as well as providing the basis of Public Key Infrastructure (PKI) access to the Navy/ Marine Corps Intranet (NMCI), and numerous Navy web sites, which may also require PKI access. Navy Information Assurance (IA) policies require that a background investigation be completed on each contractor prior to granting access to government computer systems. In the event that the investigation has been initiated, but not completed, an Advanced Fingerprint Check must be successfully accomplished prior to the issuance of an interim CAC card. The final CAC cannot be issued until the full investigation has been completed.

9.7 Return of CAC Cards: In the event that contract employees resign, are dismissed, or laid off, the contractor is responsible for obtaining any Government issued identification from the former employee and to turn over those items to COR within five (5) days of the termination of employment.

9.8 Scheduling Concerns:

9.8.1 Duty Hours: The Contractor shall have access to Government facility five days per week, Monday through Friday, eight hours a day, except when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings, unless otherwise approved. Contractor personnel are expected to conform to customer agency normal operating hours; however the Contractor may be required access to Government facility outside of duty hours based on the customer agency’s needs. Hours may change based on task order requirements.

9.8.2 Core Duty Hours and Base Shutdown/Inclement Weather: Core duty hours are 0800 - 1600, Monday through Friday (excluding federal holidays). The Contractor shall follow guidance of the installation containing their place of performance to determine reporting schedules whether due to a base closure or inclement weather. The website for guidance regarding status of performance for work to be performed in the National Capital Region (NCR) is http://www.opm.gov/status/. If place of performance is outside of the NCR, please work with the assigned COR for policy on inclement weather and base shutdown.

9.9 Kickoff Meeting/Orientation Meeting: Upon award of the IDIQ, the government will schedule and coordinate an IDIQ kick-off meeting no later than (NLT) ten (10) calendar days after the initial award at the location specified by the Government. The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting will provide the opportunity to discuss general technical, management, and logistic issues; travel authorization; communication processes between Government and Contractor; and reporting procedures. At a minimum, the attendees shall include key Contractor personnel, key Government representatives, and the COR.

9.9.1 The Contractor shall provide a Kick-Off Meeting Agenda that will include, but not be limited to, the following.

• Introduction of personnel

• Overview of project tasks

• Review of organization (complexity)

• Schedule (shows major tasks, milestones, and deliverables;

planned and actual start and completion dates for each)

• Communication Plan/lines of communication overview (between both Contractor and Government)

• Discussion of draft Program Management Plan (PMP)

• Travel notification and processes

• Security requirements (Building access, badges, Common Access Cards (CAC))

• Invoice procedures

• Monthly meeting dates

• Reporting Requirements, e.g. Monthly Status Report (MSR)

• POCs

• Roles and Responsibilities

• Prioritization of Contractor activities

• Any initial deliverables

• Other logistic issues

• Quality Control Plan (QCP)

• Sensitivity and protection of information

• Additional issues of concern (Leave/back-up support)

9.9.2 The Contractor shall provide a draft copy of the agenda NLT 3 days after contract award for review and approval by the COR prior to finalizing.

The Government will provide the Contractor with the number of participants for the kick-off meeting and the Contractor shall provide sufficient copies of the presentation for all present

9.9.3 The Kickoff Meeting location will be held at the agreed upon location and the date and time will be mutually agreed upon by both parties.

9.10 Kickoff Meeting/Orientation Meeting(task order level): Upon award of a task order, the successful task order vendor shall schedule and coordinate a Project kick-off Meeting no later than (NLT) five (5) calendar days after task order award at the location approved by the Government. The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting will provide the opportunity to discuss task order specific technical, management, and logistic issues; travel authorization; communication process between Government and Contractor; and reporting procedures. At a minimum, the attendees shall include key Contractor personnel, key Government representatives, and the COR.

9.10.1 The Contractor shall provide a Kick-Off Meeting Agenda that will include, but not be limited to, the following.

• Introduction of personnel

• Overview of project tasks

• Review of organization (complexity)

• Schedule (shows major tasks, milestones, and deliverables;

planned and actual start and completion dates for each)

• Communication Plan/lines of communication overview (between both Contractor and Government)

• Discussion of draft Program Management Plan (PMP)

• Travel notification and processes

• Security requirements (Building access, badges, Common Access Cards (CAC))

• Invoice procedures

• Monthly meeting dates

• Reporting Requirements, e.g. Monthly Status Report (MSR)

• POCs

• Roles and Responsibilities

• Prioritization of Contractor activities

• Any initial deliverables

• Other logistic issues

• Quality Control Plan (QCP)

• Sensitivity and protection of information

• Additional issues of concern (Leave/back-up support)

9.10.2 The Contractor shall provide a draft copy of the agenda NLT 3 days after contract award for review and approval by the COR prior to finalizing.

The Government will provide the Contractor with the number of participants for the kick-off meeting and the Contractor shall provide sufficient copies of the presentation for all present

9.10.3 The Kickoff Meeting location will be held at the agreed upon location and the date and time will be mutually agreed upon by both parties.

9.11 Transition-In Plan(task order level): The Contractor shall provide a Transition-

In Plan at the Kickoff Meeting, the plan shall facilitate the accomplishment of a seamless transition from the incumbent Contractor (if applicable) and incoming Contractor.

9.11.1 The Contractor shall identify how it will coordinate with the incumbent

Contractor and Government personnel to transfer knowledge regarding the following:

• Project management processes

• Points of contact

• Location of technical and project management documentation

• Status of ongoing technical initiatives

• Transition of key personnel

• Schedules and milestones

• Actions required of the Government

• Coordination of IT related programs, issues

9.11.2 The Contractor shall also establish and maintain effective communication with the incumbent Contractor and Government personnel for the period of the transition via weekly status meetings per the COR’s direction.

9.12 Transition-Out Plan(task order level):(If applicable) The Contractor shall provide a Transition-Out Plan NLT than 60 calendar days prior to expiration of the contract. The plan shall facilitate the accomplishment of a seamless transition from the incumbent to and incoming Contractor (if applicable).

9.12.1 The Contractor will continue to accomplish all tasks as outlined in the contract during this period. The Contractor shall identify how it will coordinate with the incoming Contractor and Government personnel to transfer knowledge regarding the following:

• Project management processes

• Points of contact

• Location of technical and project management documentation

• Status of ongoing technical initiatives

• Transition of key personnel

• Schedules and milestones

• Actions required of the Government

• Coordination of IT related programs, issues

9.12.2 The Contractor shall also establish and maintain effective communication with the incoming Contractor and Government personnel for the period of the transition via weekly status meetings.

9.13 Quality Control:

9.13.1 Quality Assurance: The Government shall rely on the Contractors’ existing quality assurance system as the method to ensure that the requirements of the contract and performance thresholds are met;

however, the Government reserves the right to monitor and evaluate the quality of services provided and compliance with the contract terms and conditions at any time.

9.13.2 Quality Control Plan (QCP): The Contractor shall develop and maintain an effective quality control program to ensure services are performed IAW this PWS, applicable laws and regulations, and best commercial practices.

The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services with special emphasis placed on those services listed in this PWS. The Contractor’s quality control program is the means by which it assures itself that the work complies with the requirement of the contract.

9.14 Problem Notification Reports: The contractor shall file a Problem Notification

Report (PNR) to notify the Government of schedule delays, assumptions upon which tasks were based, and any all other perceived contractual issues. The PNR shall include a plan detailing the proposed resolution. The contractor shall file the PNR as soon as possible, but no later than two business days after the contractor’s discovery of the issue(s).

9.15 Project Management Plan (PMP): The contractor shall develop and maintain throughout the contract period of performance, PMP with integrated master schedule that shall be used as a foundation for information and resource management planning.

9.15.1 Initial PMP: The contractor shall deliver the initial PMP to the Government within 15 work days after task order award. The PMP shall include, but not be limited to, the following:

• Status of current and planned tasks and subtasks

• Base schedule overlaid with actual schedules, for each task

• Project Organization

• Project Transition Processes and Schedule

• Work Breakdown Structure (WBS)

• Process Management and Control

• Overall Organizational Structure

• Project Responsibilities to include process flowcharts for all major tasks

• Task dependencies and interrelationships

• Contractor personnel assignments and duration (Staffing Plan)

• Updated Deliverable Schedule (based on solution)

• Deliverables (draft, interim, final, etc.),

• Contingency Plans (where appropriate),

• Contractor travel information

• Quality Control plan

• Risk Management plan

• Subcontract Management (organization of personnel, software and hardware)

• Monitoring mechanisms including Program Metrics

• Automated Tools, Techniques, and Methods

9.15.2 Maintenance: The contractor shall keep the PMP and integrated master schedule up-to-date, keep it accessible electronically at any time, and be prepared to brief any PMP content to the Government at short notice (within 24 hours). The PMP shall be used as a foundation for the Monthly Status Report.