CCPO_Suppot_Contract_PWS.docx

PERFORMANCE WORK STATEMENT

Department of Defense Chief Information Office Cloud Computing Program Office

28-February-2019

1. INTRODUCTION

1.1 BACKGROUND

To maintain our military advantage, DoD requires an extensible and secure cloud environment that spans the homeland to the global tactical edge, as well as the ability to rapidly access computing and storage capacity to address warfighting challenges at the speed of relevance. These foundational infrastructure and platform technologies are needed for DoD to capitalize on modern software, keep pace with commercial innovation, and make use of artificial intelligence and machine learning capabilities at scale. The Joint Enterprise Defense Infrastructure (JEDI) Cloud is the acquisition of commercial infrastructure as a service (IaaS) and platform as a service (PaaS) offerings to support DoD business and mission operations. JEDI Cloud is an important first step to acquiring a general purpose cloud capable of delivering infrastructure and platform services for the majority of the Department’s mission. JEDI Cloud will also serve as a pathfinder for DoD to understand how to deploy enterprise cloud at scale while effectively accounting for security, governance, and modern architectures.

The Cloud Computing Program Office (CCPO) has been stood up under the Department of Defense (DoD) Chief Information Office (CIO) to act as the centralized program office for delivery of the JEDI Cloud capability. The CCPO will be responsible for overarching operations of the JEDI program to include: Business Operations and Leadership Support, Engineering and Security, Strategic Communications, User Engagement, and Program Execution.

When fully staffed, the program office consists of 15 civilians and 11 military personnel. While the program office structure is subject to change, the basic organization is illustrated below.

1.2 OBJECTIVES

To accomplish the operations of the JEDI contract, the CCPO requires highly skilled services to support program office operations and delivery of a modern enterprise cloud services solution, to include end user engagement and supporting migration of early adopter applications.

1.3 SCOPE

This effort will require a team of experts who possess technical and professional support services in the following areas:

· Business Operations and Leadership Support

· Engineering Support

· Security and Risk Management Framework Support

· Office Automation, Desktop, and Tier 3 Support

· Public Affairs and Communications Support

· User Engagement

· Program Execution

2. GENERAL REQUIREMENTS

This section describes the general requirements for this effort. The following subsections provide details of various considerations.

2.1 NON-PERSONAL SERVICES

The services and performance required under this contract are determined to be not inherently governmental. The contractor shall not perform or give the appearance of performing inherently governmental functions as described in FAR Part 2 and Subpart 7.5, and all DoD policy. The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required tasks. All contractor personnel shall identify themselves as contracted support personnel in all forms of communication with all entities with whom Washington Headquarters Services has business dealings. The contractor shall manage its employees and guard against any personal services actions, or give the perception of personal services. If the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the Contracting Officer immediately.

2.2 BUSINESS RELATIONS

The contractor shall integrate and coordinate all activity to execute the requirements specified herein. The contractor shall manage the timeliness, completeness, and quality of the contract deliverables. The contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of all contractor personnel (including subcontractors). The contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all contractor personnel.

2.3 CONTRACT MANAGEMENT

The contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to this requirement. The contractor must maintain continuity between the support operations at the Pentagon and the contractor's corporate offices.

The contractor shall establish processes and assign resources to effectively administer this contract. The contractor shall respond to Government requests for contractual actions promptly. The contractor shall have a single point of contact between the Government and Contractor personnel assigned to support this contract. The contractor shall assign work effort and maintain proper and accurate time keeping records of personnel assigned to work on this requirement.

2.4 SUBCONTRACT MANAGEMENT

The contractor shall be responsible for any subcontract management to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The prime contractor shall manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations. Contractors may add subcontractors to their team after notification to the Contracting Officer or Contracting Officer Representative (COR).

2.5 CONTRACTOR PERSONNEL, DISCIPLINES, AND SPECIALTIES

An integral part of successful performance under this contract is not only the production of quality products described in Section 3.0, but the responsiveness of contractor personnel in the day-to-day output of work products. While the end product or deliverable is vital to successful performance, day-to-day oversight also includes client interaction and responsiveness. The contractor is required to proactively maintain assigned tasks, and respond to all entities with professional business dealings related to the assigned tasks.

The Contractor must maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS. When hiring personnel, the Contractor shall remember that the stability and continuity of the workforce are essential. At a minimum Contract workforce shall extensive Cloud experience to include experience in developing application readiness assessment templates, application engineering assessments, design in the cloud environment, cloud technical administrative responsibilities, technical governance, cybersecurity requirements in a cloud environment, RMF process and FedRAMP processes.

2.6 TRAINING

The Contractor shall provide all training to ensure their personnel are trained on the common suite of Microsoft Office tools (e.g., Word, Excel, and PowerPoint) and other applicable programs. The Contractor shall also ensure that all of its employees have been properly trained and are qualified to perform assigned tasks under this PWS. The Government will provide or coordinate training on any new Government-provided equipment or Government-directed training (e.g., Information Assurance). If such training requires travel by contractor employees, local travel costs (i.e., Metro) shall be borne by the contract personnel.

2.7 TRAVEL

All travel within 100 miles of the National Capital Region is included in the price of this contract. When movement of contractor personnel is required locally (i.e., Metro), costs will be borne by the contractor. The Government will reimburse the contractor for all other travel outside the 100 mile limitation authorized in advance by the Contracting Officer, for reasonable travel related expenses.

The contractor shall be reimbursed for actual allowable, allocable, and reasonable travel costs incurred during the performance of this effort in accordance with the FAR 31.205-46 “Travel Costs.” Requests for approval of costs over the maximum per diem rates in accordance with the procedures in FAR 31.205-46(a)(3) must be submitted to the Contracting Officer for final approval prior to commencement of travel.

Anticipated Travel: Several trips are anticipated worldwide to both JEDI contractor and end user locations in support of the performance requirements detailed in Section 3. The Contractor shall have the capability to travel all throughout the United States and its territories, as well as to foreign countries.

2.8 LOCATION

Contractor personnel shall primarily be located at CCPO government sites within the National Capital Region. The government will furnish office space and office equipment. However, Contractor personnel shall also be able to perform contract specific work at the Contractor’s location or telework site or a location determined acceptable by the contractor and government.

Contractor personnel must obtain and maintain a Common Access Card (CAC) to access to all IT systems prior to conducting work on this contract. Contractor personnel must also read and familiarize themselves with all organizational mission statements and charters, organizational structures, operating instructions, Standard Operating Procedures (SOP) and policies.

2.9 HOURS OF WORK

The contractor shall plan to be flexible, and shall have the ability to work whatever hours are necessary to complete the Performance Requirements detailed in section 3. This may require non-traditional working hours to conform to global time zones. However, in general, normal work days are Monday through Friday except U.S. Federal Holidays. Office core hours of work are from 09:00am to 3:00pm Eastern time daily. Due to the interdependence between government and Contractor Personnel who perform functions that are closely associated with inherently governmental functions, any schedule designed by the project manager shall ensure, when reasonable, at least six hours per day of intersection with the standard office hours Recognized Federal holidays are as follows:

The contractor shall provide the COR a schedule for its entire staff assigned to the contract, including planned leave in the monthly status report. The contractor shall assign alternates to cover assignments of any of its staff that are absent sufficient to ensure that the services are not disrupted.

The contractor shall provide surge support for all contract tasks as required. For each instance when surge is required, the contractor shall propose a plan for surge support to the government and the government will accept, reject, or require modification to the proposed surge support plan.

2.10 ORGANIZATIONAL CONFLICT OF INTEREST AND NON-DISCLOSURE AGREEMENT

The Contractor will be directly supporting the execution of the JEDI Cloud Contract, as well as subsequent related contracts in support of the JEDI Cloud Effort. The DoD must ensure that it can rely on the impartiality of the Contractor, including any subcontractors, assisting in the scope of this effort and do its utmost to protect the integrity of the acquisition process. To that end, the Contractor, and any subcontractors, must execute a Corporate Non-Disclosure Agreement (NDA) (Attachment 1) at contract award and its employees must execute Individual NDAs (Attachment 2) upon reporting for duty as no sensitive information can be shared in advance of the executed NDA. The NDA requirements apply indefinitely.

Furthermore, neither the Contractor, nor any of its subcontractors under this effort both current and former, shall participate in any contract or task order, as a prime, subcontractor, joint venture partner, consultant, or other team member, for the JEDI contract award or any of its task orders or for the contract for the Government Provisioning Tool. Whether the Contractor, or its subcontractors, have an enduring organizational conflict of interest (OCI) and can subsequently participate will be determined by the cognizant Contracting Officer at the time of award or issuance. The Contractor and its subcontractors are cautioned to determine whether a potential OCI exists before actively participating in a related contractual effort.

The Contractor is responsible for ensuring that this entire subsection is flowed down to any subcontractors.

3. PERFORMANCE REQUIREMENTS (TASKS)

The Contractor shall be directly responsible for ensuring the accuracy, timeliness, and completion of all tasks under this effort, none of which are considered inherently governmental functions as defined in FAR 2.101 or Subpart 7.5. In accordance with FAR 37.104, Personal Services Contracts are prohibited and will not be performed under this contract. The following section specifies the Performance Objectives and Performance Elements for the contract:

3.1 Business Operations and Leadership Support

3.1.1 Business Operations: The Contractor shall provide business operations support for CCPO. Tasks may include:

3.1.1.1 Serve as the administrative point of contact and as such receive and coordinate all tasks.

3.1.1.2 Coordinate daily calendars and ensure operations are accomplished in a timely, professional manner.

3.1.1.3 Assist leadership in coordinating tasks and information across the discrete workstreams to ensure each workstream remains informed and aligned to the overall strategic vision and schedule.

3.1.1.4 Coordinate joint efforts with other groups and offices and maintain accountability of all assigned tasks.

3.1.1.5 Arrange for meetings, conferences, and video-teleconferencing, to include taking minutes and maintaining invitations attendee contact rosters. Support may include drafting meeting agendas and setup and operation of audiovisual equipment.

3.1.1.6 Coordinate special events, meetings, conferences, and work groups.

3.1.1.7 Provide correspondence staffing support and oversight for all required correspondence actions (e.g., formal letters, memoranda, read-ahead briefing/meeting packages, activity reports, and senior leadership reports).

3.1.1.8 Perform technical writing/editing, editorial consultation, proofreading, or overall documentation review. Ensure documents are prepared in the appropriate format and are free from grammatical errors. Tracks all suspenses to ensure timeliness.

3.1.1.9 Prepare and assist in the development of briefings and multimedia presentations.

3.1.1.10 Prepare, maintain, and update informational packages.

3.1.1.11 Organize, curate, and maintain the electronic document repository as directed.

3.1.1.12 Provide requested data activities from external sources once approved, and accept, disseminate and track tasks for future meetings.

3.2 Engineering Support

3.2.1 Infrastructure Engineering: The Contractor shall provide infrastructure engineering support for CCPO activities in support of the execution of the JEDI contract. Tasks may include:

3.2.1.1 Provide technical subject matter expertise on infrastructure engineering with an emphasis on modern, cloud infrastructure, hybrid cloud models, and platform services.

3.2.1.2 Support development of technical requirements for JEDI network infrastructure to include design and deployment of secure communication to/from existing enclaves.

3.2.1.3 Assist in the review and analysis of market research materials, document that analysis, and make recommendations on how that analysis should inform technical inputs into all documentation.

3.2.1.4 Review, draft, and update the technical portions of the acquisition documents, and provide technical services to support the preparation of business cases, analysis of alternatives, program office estimates, cost analysis requirements documentation, and cost estimating.

3.2.1.5 Draft, edit, and consolidate briefings and other informational documents with an emphasis on accuracy, quality, and timeliness. Present technical information in a concise manner that can be understood by non-engineers and gives decision-makers the context and key points necessary to make necessary decisions.

3.2.1.6 Prepare white papers and informational memoranda on technical areas of interest, such as tactical edge architecture, service integration, etc. Present research findings in a concise manner that can be understood by non-engineers and gives decision-makers the context and key points necessary to make necessary decisions.

3.2.1.7 Support analysis and preparatory activities for migrations including the documentation of those activities.

3.2.1.8 Support execution of migrations in and out of JEDI Cloud.

3.2.2 Software Engineering: The Contractor shall provide software engineering in support of the execution of the JEDI contract. Tasks may include:

3.2.2.1 Provide technical subject matter expertise on software engineering with an emphasis on modern, cloud services and application portability.

3.2.2.2 Support development of technical requirements as required.

3.2.2.3 Assist in the review and analysis of market research materials, document that analysis, and make recommendations on how that analysis should inform technical inputs into all documentation.

3.2.2.4 Review, draft, and update the technical portions of the acquisition and contracting documents, and provide technical services to support the preparation of business cases, analysis of alternatives, program office estimates, cost analysis requirements documentation, and cost estimating.

3.2.2.5 Draft, edit, and consolidate briefings and other informational documents with an emphasis on accuracy, quality, and timeliness. Present technical information in a concise manner that can be understood by non-engineers and gives decision-makers the context and key points necessary to make necessary decisions.

3.2.2.6 Prepare white papers and informational memoranda on technical areas of interest, such as application architecture, modern software practices and tools, etc. Present research findings in a concise manner that can be understood by non-engineers and gives decision-makers the context and key points necessary to make necessary decisions.

3.2.2.7 Support analysis and preparatory activities for migrations including the documentation of those activities.

3.2.2.8 Support execution of migrations in and out of JEDI Cloud.

3.3 Security Engineering and Risk Management Framework:

3.3.1 Security Engineering: The Contractor shall provide security engineering support for CCPO. Tasks may include:

3.3.1.1 Provide expert level security engineering services to all technical aspects of the JEDI program using a combination of DoD Policy and Industry best practice. Tasks may include:

3.3.1.1.1 Support security engineering efforts related to IaaS and PaaS offerings provided from the JEDI contract.

3.3.1.1.2 Support security engineering effort for networking equipment needed to connect existing Department of Defense networks to the cloud service provider at all classification levels.

3.3.1.1.3 Support design and review for high assurance/high security one-way file transfer solutions.

3.3.1.2 Respond, investigate, and remediate any breach or potential security issues reported by the cloud service provider.

3.3.1.3 Monitor logs from CCPO managed hardware and software along with cloud service provider data to identify and remediate potential breaches or misconfigurations.

3.3.2 Risk Management Framework Activities for Assessment and Authorization: The Contractor shall provide risk management framework support for assessment and authorization support for CCPO. Tasks may include:

3.3.2.1 Provide Information Security support for all CCPO Risk Management Framework requirements following NIST SP 800.53 standards.

3.3.2.2 Support the evaluation of security controls against the IaaS and PaaS offerings provided on the JEDI Contract.

3.3.2.3 Support the creation and management of a new security risk management process to authorize a marketplace process and monitor the output of the process for accuracy.

3.3.2.4 Create needed documentation to support the Authorization process, to include documentation outlining the control objectives, how they are met, and how they are monitored.

3.3.2.5 Review and update all Risk Management documentation to ensure all documentation matches our current operating posture.

3.4 Office Automation, Desktop, and Tier 3 Support

3.4.1 Office Automation and Desktop Support: The Contractor shall provide office automation and desktop support for CCPO. Tasks may include:

3.4.1.1 Develop and maintain a website, including the content.

3.4.1.2 Provide desktop support for both Windows and Macintosh desktop systems at an administrator level. Contractor must be able to deploy new systems for employees, maintain existing desktop systems to include application and operating systems upgrades, and track and ensure patching compliance for all systems and applications.

3.4.1.3 Provide Application deployment and support for standard applications such as Microsoft Office suite, Project Management tools, and other mission specific applications.

3.4.1.4 Create and manage E-Mail and shared drive accounts in systems such as Microsoft Office 365 and Google G-Suite.

3.4.2 Call Back Support For Tier Three Support Issues: The Contractor shall provide call back support for Tier Three issues CCPO.

3.4.3 Public Affairs and Communications Support

3.4.4 The Contractor shall provide strategic communications support for CCPO. Tasks may include:

3.4.4.1 Formulate branding, and messaging plans and products for the program office with an emphasis on accuracy, timeliness, and concisely conveying information with the intended audience in mind. Develop templates, samples, and public relations materials consistent with the approved program office brand. Ensure plans and products have approved messaging for internal and external audiences.

3.4.4.2 Update these branding a messaging plans and products with approved messaging for internal and external audiences.

3.4.4.3 Develop clear and concise, talking points for CCPO leaders to brief at internal and external events.

3.4.4.4 Facilitate engagements events and working groups with both internal and external audiences. This may include organizations across DoD, other Federal agencies, Congress, White House, and the media.

3.4.4.5 Provide recommended draft responses to media inquiries, media interviews and articles for public media with compelling and clear messaging that is appropriate for the targeted venue. This will require work with DoD public affairs staff and coordination with senior leadership.

3.4.4.6 Prepare documentation for meetings with a responses to inquiries from organizations across DoD, other Federal agencies, Congress, White House, and the media.

3.4.4.7 Create a compilation of relevant media articles and conferences/events for situational awareness.

3.4.4.8 Draft recommended responses to internal and external inquiries.

3.4.4.9 Create a historical archive of all internal and external messaging and ensure consistency in messaging across the board.

3.4.4.10 Create communications materials to include: briefings, multimedia materials, fact sheets, brochures, and others for internal and external outreach.

3.4.4.11

3.4.4.12 Facilitate review of any public affairs and communications documentation, organize and adjudicate feedback, and make updates to documentation as approved by the Government.

3.4.4.13 Ensure CCPO website, including the content, is consistent with branding products and overall messaging.

3.4.4.14 Review all documentation (not just limited to strategic communications documents) for consistency and clarity. Perform technical writing/editing, editorial consultation, proofreading, or overall documentation review. Ensure documents are prepared in the appropriate format and are free from grammatical errors.

3.4.4.15 Facilitate focus groups of end users in coordination with User Engagement to assess the quality of services and identify methods of improvement.

3.5 User Engagement Support

3.5.1 Outreach Events: The contractor shall plan, organize, and facilitate events for senior level DoD executives. The contractor shall ensure all details and preparation for the events are accomplished. This activity requires experience working with front office and senior level personnel.

3.5.2 Customer Engagement: The Contractor shall provide customer engagement support for CCPO. Tasks may include:

3.5.2.1 Assist in developing short and long term change management goals. Prepare and update a Change Management Plan for enterprise cloud adoption.

3.5.2.2 Develop template to assist with cost estimation for consumer consumption of cloud services.

3.5.2.3 Assist customers with engineering assessments

3.5.2.4 Develop system assessment documentation/templates and assist customers in populating said templates.

3.5.2.5 Assist with Use Case development

3.5.2.6 Assist with JEDI suitability assessments

3.5.2.7 Assist in identifying and producing customer engagement metrics for leadership

3.5.2.8 Develop project management documentation

3.5.2.9 Assist with roadmap creation, development and ongoing maintenance

3.5.2.10 Assist with playbook creation, development and ongoing maintenance

3.5.2.11 Assist with customer outreach materials creation, development and ongoing maintenance

3.5.2.12 Assist with schedule creation, development and ongoing maintenance

3.6 Program Execution Support

3.6.1 Cloud Support Provider Management: The Contractor shall provide Cloud Service Provider (CSP) management support for the JEDI Contract. Tasks may include:

3.6.1.1 Assist the Government in the review and analysis of vendor provided deliverables with an emphasis on accuracy, quality, and timeliness.

3.6.1.2 Assist the Government in the review and analysis of vendor performance to include performance metrics outlined in the Government Quality Assurance Surveillance Plan and CSP Quality Control Plan with an emphasis on accuracy, quality, and timeliness.

3.6.1.3 Assist the Government in developing and compiling CSP metrics for reporting to JEDI customers, Department and Service leadership, congress and other audiences as requested.

3.6.1.4 Draft, review, update, and coordinate metric reports, briefings, any acquisition documentation, to include, but not limited to, the Quality Assurance Surveillance Plan, JEDI Ordering Guide, Risk Management Plan, Project Management Plan, and other JEDI related documentation as directed by the Government.

3.6.1.5 Track and organize any feedback received on both Government provide and CSP provides documents, facilitate adjudication of that feedback, and update documents accordingly upon Government approval.

3.6.1.6 Draft, edit and consolidate briefings and other informational documents with an emphasis on accuracy, quality, and timeliness.

3.6.1.7 Prepare white papers and informational memoranda on areas of interest, incentivizing Contractor performance, leveraging commercial catalogues, etc. Present research findings in a well-considered manner that gives decision-makers the context and key points necessary to make necessary decisions.

3.6.1.8 Analyze DoD acquisition regulations and policies and make recommendations on how to apply those regulations and policies to the JEDI effort. Continually assess JEDI documentation for compliance with those regulations and policies, including new statutory, regulatory, and policy requirements.

3.6.1.9 Attend meetings as required and prepare meeting summary reports.

3.6.2 Budget Planning and Preparation Support. The Contractor shall provide budget preparation activities. Tasks may include:

3.6.2.1 Prepare, review and verify all artifacts associated with the phases of the Planning, Programming, Budgeting and Execution (PPBE) process to include the Program Objective Memorandum (POM)/ Budget Estimate Submission (BES) inputs, Budget Exhibits (BE), and supporting POM/ Budget submissions.

3.6.2.2 Generate budget artifacts to include but not limited to preparing, reviewing, and verifying Congressional Briefings, White Papers, Issue Papers, Reclamas, Exhibit 300 Reports, Courses of Action (COA) Plans, Financial Spreadsheets and Reports, briefings, and future year financial planning documents.

3.6.2.3 Create detailed, time-phased allocation requests based on planning decisions made for outyear resource requirements. .

3.6.2.4 Track CCPO budget execution; assess actual budget execution against planned performance. Make recommendations on adjusting budget to achieve desired performance goals.

3.6.2.5 Draft, edit and consolidate briefings and other informational documents with an emphasis on accuracy, quality, and timeliness. Present budget information in a concise manner that gives decision-makers the context and key points necessary to make necessary decisions.

3.6.3 Cost Estimation. The Contractor shall provide cost estimation support. Tasks may include:

3.6.3.1 Prepare cost estimates and economic analyses for governmental approval, using a variety of cost estimation techniques as appropriate. Potential documents include, but are not limited to, lifecycle cost estimates, independent cost estimates, Independent Government Cost Estimates, Cost Analysis Requirements Description, and economic analysis.

3.6.3.2 Collaborate with technical experts to understand how the underlying technical assumptions impact costs and make informed adjustments to those assumptions when appropriate.

3.6.3.3 Document all assumptions underlying cost estimates in a clear and concise manner.

3.6.3.4 Verify all cost information provided from other sources for accuracy, coordinating with those sources to seek additional information and make adjustments as necessary.

3.6.3.5 Provide cost inputs into acquisition documents, such as the business case.

3.6.3.6 Draft, edit, and consolidate briefings and other informational documents with an emphasis on accuracy, quality, and timeliness. Present cost information in a concise manner that gives decision-makers the context and key points necessary to make necessary decisions.

3.6.4 Financial Management. The Contractor shall provide financial management support. Tasks may include:

3.6.4.1 Assist the Government in preparing documentation for movement and execution of funding as required.

3.6.4.2 Track funding execution and prepare reports to present to leadership as required.

3.6.4.3 Advise the Government on financial tradeoffs between different technical solutions as required.

APPLICABLE STANDARDS

DoD Correspondence Manual: www.dtic.mil/whs/directives/corres/pdf/511004m_v2.pdf DoD Security Procedures: http://www.dtic.mil/whs/directives/

4. SPECIAL REQUIREMENTS

This section describes the special requirements for this effort. The following subsections explain various considerations on this effort.

4.1 Estimated Level of Effort

The Government estimate of anticipated level of effort for the performance requirements as described about is 23 FTEs. However, the Contractor should perform analysis to identify the level of effort and skill sets will be required to perform all performance requirements and allocate these FTE appropriately. The Contractor shall have the ability to surge in any of the performance requirement areas as required during the execution of the contract.

4.2 Key Personnel

The contractor shall provide two key personnel in support of these performance requirements: the Program Manager, and Technical Lead. The Government has determined that key personnel must possess skills, experience and technical competencies that are critical to the successful performance of this Task Order as specified below.

Program Manager:

The Program Manager oversees all contract activities and is the primary interface to CCPO PM and the Contract COR.

The Program Manager shall have experience in IT and strong working knowledge of cloud technologies. The Program Manager shall also have significant experience in managing large and complex contracts and/or projects and have the capability to identify emerging challenge points for contract execution and establish pre-emptive measures to minimize disruption to achieving overall end user objectives and outcomes. The Program Manager shall have knowledge and understanding of how the Department of Defense operates, have expert project management skills.

The Program Manager shall have skill in designing and conducting comprehensive analysis, reviews, and studies and preparing solutions to especially board, important and severe management problems and comprehensive skill in using computer hardware and software, including Microsoft Office and Google Suite.

Technical Lead:

The Technical Lead oversees all contract positions related to security engineering, analysis, auditing, and office automation requirements as it relates to JEDI Cloud, but also considers the broader IT implications. This position shall additionally provide practical engineering advice and guidance, to promote optimized outcomes for the end users.

The Technical Lead shall also ensure the information that is produced from the engineering and security support processes supported by the contract must be incorporated into the various CCPO documentation and user facing material.

Security will be a constant consideration for the Technical Lead. This includes an understanding of policy management best practices within cloud providers to include full compliance with the JEDI Cloud Cyber Security Plan and other compliance mandates applicable to the program.

This Lead coordinates across the contract team and with the Government group leads to ensure the technical team’s creation of technical reports are complete and timely manner.

This may include proposals for policy edits, support with Congressional language for Statute and Regulation, analytic assessment reports of JEDI Cloud use, and a myriad of other technical topics that will be required as the Department becomes familiar with the JEDI Cloud.

During the first ninety (90) calendar days of performance, the Contractor shall make no substitutions of key personnel unless illness, death, or termination of employment necessitates the substitution. The Contractor shall notify the Contracting Officer and COR in writing as soon as possible after the occurrence of any of these events and provide the information required below. After the initial ninety (90) calendar day period, the Contractor may propose substitutions. The Contractor shall provide a detailed explanation of the circumstances necessitating the proposed substitutions, complete resumes for the proposed substitutes, and any additional information requested by the Contracting Officer. The Contractor shall, prior to making any substitution permanent, demonstrate to the satisfaction of the Contracting Officer that the qualifications of the proposed substitute personnel are equal to or better than the qualifications of the personnel originally identified for the position. The Contracting Officer will notify the Contractor within 15 calendar days after receipt of all required information of the decision on proposed substitutions.

4.3 Personnel Substitutions within the first 90 days of Contract Award During the first ninety (90) calendar days of performance of any order, the Contractor shall make no substitutions of personnel unless illness, death, or termination of employment necessitates the substitution. The Contractor shall notify the Contracting Officer Representative as soon as possible after the occurrence of any of these events. In addition, the Contractor shall provide a detailed explanation of the circumstances necessitating the proposed substitution(s) and any additional information requested by the Contracting Officer Representative. Contracting Officer Representative shall notify the Contractor within five (5) business days whether the substitute is acceptable.

4.4 Substitutions after the first 90 days of Contract Award

After the initial ninety (90) calendar days of performance, the Contractor may propose substitutions. The Contracting Officer Representative shall notify the Contractor within ten (10) business days whether the substitute is acceptable. The Contractor shall, as soon as a fully qualified candidate can be found, replace any individual provided under this PWS who fails to perform his/her duties adequately, is chronically absent/late, or conducts himself/herself in a manner that is inconsistent with the listed requirements, government employment policies and practices, or engages in practices that are disruptive to the working environment.

4.5 Equitable Adjustments

Failure to provide an acceptable candidate, with the appropriate security clearance, within 30 calendar days of incumbent departure will result in an equitable adjustment.

4.6 Disclosure and Avoidance of Inherently Governmental Functions The contractor shall not perform or give the appearance of performing inherently governmental functions as described in FAR Part 2 and Subpart 7.5, and applicable DoD policy. None of the services to be performed are inherently governmental functions. All contractor personnel shall identify themselves as Contractor Support in all forms of communication during the performance of their duties under this Agreement. In accordance with DF ARS 211.106, contractor personnel shall never identify themselves as representing the government, but rather shall identify themselves as being under contract to government. The contractor shall:

· Include a title block in all emails that states the fact that the person is contracted support.

· Ensure all those with whom the person interacts in any face-to-face dealings while supporting the government understands that the person is contracted support.

5. PERFORMANCE REQUIREMENTS SUMMARY

Personnel Qualifications/Performance

The Contractor's personnel are qualified and adept at presenting clear, concise, professional work products.

COR review/government personnel feedback

Personnel/Workload Management

Reporting

Reporting is timely, grammatically correct and professional in appearance.

6. DELIVERABLES

Deliverables shall be submitted to the COR designated in the COR Appointment letter. All deliverables shall be submitted using Microsoft Office suite of tools (for example, MS Word, MS Excel, MS PowerPoint), or Adobe PDF format, unless otherwise specified by the COR. Electronic submission shall be made via email, unless otherwise agreed to by the COR.

The COR may reject or require correction of any deficiencies in the deliverables. In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection.

The following table specifies the deliverables for this requirement:

PWS

Reference

and upon replacement of personnel PDF with original employee signature

completion of travel

PDF

contract award.

Updated annually

PDF

5 days after contract start.

PDF

end of the contract

PDF

7. GOVERNMENT FURNISHED MATERIALS

Basic facilities such as work space and its associated operating requirements (i.e., phones, desks, utilities, information technology, and consumable and general purpose office supplies) will be provided while working in Government facilities. The Government will provide information, material and forms unique to the Government for supporting the task. All Government unique information related to this requirement, which is necessary for Contractor performance, will be provided to the Contractor. The COR will be the point of contact for identification of any required information to be supplied by the Government.

8. SECURITY

All tasks must be conducted in full compliance with DoD security regulations. During the period of performance, all contractor personnel will have to maintain a Top Secret/Sensitive Compartmented Information (SCI) clearance. Contractors supporting this requirement may require access to Special Access Program (SAP) or Alternative Compensatory Control Measures (ACCM) information. SCI eligibility defined by the ICD 704, Eligibility for Access to SCI, and reinforced in the DoDM 5105.21, V-3 is:

· "In Scope" personnel security investigations (SSBI, SBPR, PPR) and access determinations void of deviations, conditions, or waivers. ICD 704.4 defines "in scope investigations" as those that are less than seven years old, without a 24 month break in service. To preserve reciprocity, the subject reinvestigation must be in progress within seven years from completing the previous investigation.

· The only exception is for task 3.5, as the contractor(s) supporting this task only require a Secret clearance.

· The Contractor shall submit the security nomination packages for the personnel assigned to the task order no later than 3-5 calendar days following issuance of the award document.

· If the necessary security clearances are not adjudicated within the timelines described above, the Government may require the Contractor to develop a work-around plan to meet the PWS requirements and submit it to the Contracting Officer for acceptance.

· All contractor personnel shall sign a Non-Disclosure agreement.

The Contractor’s Facility Security Officer (FSO) shall submit Personnel Security Clearance (PCL) validation through use of a Visit Authorization Request (VAR) for each employee, in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM) to the designated security representative.

Changes in PCL status of contractor employees shall be forwarded in writing to the Contracting Officer and the designated security representative.

All information disclosed to contractor or provided to contractor including subcontractors to perform the services required by the solicitation must be maintained by contractor in accordance with the classification level of the information and returned to the Government when this contract has expired. Contractor shall completely purge its files and databases of all information provided to or disclosed to contractor under this contract when the contract has expired and certify to the Government that all information has been destroyed or returned to the Government.

Security Classification Guidance

All Security Classification Guidance is provided on the DD-254. Any changes or additional security classification guidance shall be provided to the Contractor in writing, through updates and modifications to the DD-254. At no time will the Government issue classification guidance in any other form (verbal, e-mail, etc.).

Facility Security Clearance (FSC)

The Contractor’s Facility Security Officer (FSO) shall report, in writing, to the Contracting Officer any changes in the Contractor’s security status throughout the contract period of performance.

Sub-Contractors

Subcontractors shall comply with the same security requirements as the Contractor. The Contractor shall issue DD 254s to each subcontractor reflecting the same security requirements applicable to the prime contract. The contractor shall also sponsor subcontractor(s) for an FSC and associated PCL(s) required in accordance with the DD 254.

Credentials All Common Access Cards (CAC) and Badges issued to contractor personnel are government property and must be returned either upon departure from the program or at the conclusion of the contract, whichever comes first.

Failure to return any and all credentials to the government will be noted in the annual CPARS.

Oral Attestation of Security Responsibility (DFAR 252.204-7005) Contractor employees cleared for access to Top Secret (TS), Special Access Program (SAP), or Sensitive Compartmented Information (SCI) shall attest orally that they will conform to the conditions and responsibilities imposed by law or regulation on those granted access. Reading aloud the first paragraph of Standard Form 312, Classified Information Nondisclosure Agreement, in the presence of a person designated by the Contractor for this purpose, and a witness, will satisfy this requirement. Contractor employees currently cleared for access to TS, SAP, or SCI may attest orally to their security responsibilities when being briefed into a new program or during their annual refresher briefing. There is no requirement to retain a separate record of the oral attestation. If an employee refuses to attest orally to security responsibilities, the Contractor shall deny the employee access to classified information and shall submit a report to the Contractor's security activity.

9. DOCUMENTATION

The Government maintains unlimited use rights in all deliverables of this contract.

The Contractor agrees to assume responsibility for protecting the confidentiality of Government records, which is not considered public information. Each Contractor or employee of the Contractor to whom information may be made available or disclosed shall be notified in writing by the Contractor that such information may be disclosed only for purposes and to the extent authorized. The Contractor shall release no information related to this contract to the public, media or other unauthorized persons or organizations unless the government has conducted the appropriate security review and granted written approval (e.g. posting information to a public website).

10. QUALITY CONTROL PLAN

The Contractor shall prepare and adhere to a Quality Control Plan (QCP). The QCP shall document how the Contractor will meet and comply with the quality standards specified in the PWS, and Quality Assurance Surveillance Plan (QASP). At a minimum, the QCP must include a self-inspection plan, an internal staffing plan, and an outline of the procedures that the Contractor will use to maintain quality, timeliness, responsiveness, customer satisfaction, and any other requirements set forth in this PWS.

11. TRANSITION

The Contractor shall follow its transition plan submitted as part of their proposal and keep the Government informed of status throughout the transition period. Throughout the phase-in/phase-out periods, attention must be given to minimize interruptions or delays to work in progress that would affect the mission. The Contractor must plan for the transfer of work control, delineating the method for processing and assigning tasks during the phase-in/phase-out periods.

Phase-In The Contractor shall submit a detailed phase-in plan as part of their quote to include start-up activities that may have to transition to full operational capability upon conclusion of the transition period. All transition activities shall be completed within the first 30 days of contract award. The contractor shall ensure all existing and applicable services and support are successfully transitioned from incumbent contractor to the new contractor within 30 days of contract award in accordance with the Contractor Initial Transition Plan.

The Contractor shall:

· Provide a detailed transition methodology in logical sequence to ensure a smooth transition of all tasks/subtasks of the contract without interruption or degradation of service levels;

· Provide a timeline for completion; and

· Identify associated risks and issues and risk mitigation strategies.

Phase-out The Contractor shall provide a phase-out plan within sixty (60) days prior to expiration of this contract. The Contractor shall maintain complete documentation totally assessable to the designated Government representatives via a web portal or some other portal as the Government directs. The Contractor shall overlap with incoming Contractor during transition for thirty (30) days and will work with Government personnel and the incoming contractor to transfer knowledge, information and documentation for all projects and tasks related to this contract. The information and documentation to be transferred includes but is not limited to:

· Staff Packages

· Security Reports

· Meeting Minutes

· Assessments

· Implementation Plan

· Security Classification Guides

Note: All automated data files in the possession of the contractor that shall be turned over to the KO or the COR at the completion or termination of the contract. And all records related to the execution of the contract shall be returned to the Government as electronic copies that are readable and accessible by the Government.

12. ADDITIONAL TASK OR LABOR CATEGORY

The agency may add…