Atch 1 Performance Work Statement Draft.docx
DOCX document 39 KB Posted
- Attached to
- RFI for acquisition of Atlassian Solutions Architect Support with Enterprise Project Management System (EPMS) Support Federal contract opportunity
- Solicitation number
- FA4890
About this file
This Request for Information from the Air Force Air Combat Command seeks information from industry to support market research for the acquisition of Atlassian Solutions Architect Support and Enterprise Project Management System Support services. The services required include employing expert facilitation of the technical, governance, and operational scaling and roll-out of an Atlassian Jira-based Enterprise Project Management System across the Intelligence Directorate and subordinate units. The period of performance is anticipated to be approximately nine months, with performance beginning in fiscal year 2020. Responses are due no later than May 1, 2020 and shall include company information, capability statements describing proposed solutions and estimated implementation timeframes, experience implementing similar solutions for other agencies and companies, and recommended contract types.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| RFI for EPMS.docx | DOCX document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Performance Work Statement (PWS) for Air Combat Command Directorate of Intelligence Atlassian Solutions Support
1.0 Purpose
This document defines the scope, approach, timeline, place of performance, and classification level for Atlassian Solutions Support to Air Combat Command’s Intelligence Directorate (ACC/A2). This requirement is seeking a specialized, certified sub-contractor who could leverage ACC/A2 funding provided for the Atlassian Solutions Architect position to employ multiple senior-level experts to facilitate the technical, governance, and operational scaling and roll-out of EMPS (Enterprise Process Management System) across ACC/A2 and subordinate ISR wings. With partners relying on EPMS to support combat operations globally, ACC/A2 has expressed an increased sense of urgency to migrate their current server-based capability to the cloud to ensure sustained enterprise services, as well as establish the technical infrastructure for scaling the capability to meet current and future demand.
2.0 Scope and Approach
2.1. Specific support defined in this SOW is derived from the following sub-tasks in ACC/A2 Advisory and Technical Assistance Support Task Order 47QFCA19F0049:
· C.5.2.1 – Knowledge Management. The contractor shall use knowledge of and experience with other online tools to support ACC/A2 staff planning, analysis, functional matter expertise, USAF intelligence enterprise management, programming, budgeting, technical capabilities, unit engagement, and intelligence production activities.
· C.5.2.2. – Information-Centric Technology Support. The contractor shall use knowledge of and experience with industry and DoD data management, conditioning, and analysis TTP (tactics, techniques and procedures) to provide subject matter expertise to assist and advise ACC in developing, evaluating and fielding of information-centric decision making technology, TTP, and training to maximize analytical opportunities with USAF, Joint/Department of Defense (DoD), and other data sources. The contractor shall assist in developing USAF analytic software toolkits to better leverage existing commercial and IT tools.
· C.5.7.7 – Agile Intelligence Development Operational Support. The contractor shall use knowledge of and experience with industry and DoD developmental TTP to advise and assist ACC staff management of AF-wide agile development of intelligence tools, applications, and systems to increase integration with AF capabilities and systems and improve intelligence operational support through timely tests, assessments, and delivery of intelligence capabilities to meet validated USAF tasks. The contractor shall plan, support, and manage software testing, experiments, spirals, sprints, and evaluations throughout ACC, AF, Joint, DoD, and Government.
· C.5.7 – Intelligence Systems Support. The contractor shall use knowledge of and experience with maintenance, logistics, and life cycle support for Government networks and VTC systems; installation, upgrade, and administration of hardware and software; resolution of equipment and mission system interoperability issues; and IT inventory management to provide mission critical support to ensure IT equipment is operational to support Intelligence mission tasks. The objective of this performance-based task is to support ACC personnel at MAJCOM and unit levels by supporting fielded C2/C4I assets.
2.2. This Atlassian Solutions Support focuses on the Enterprise Project Management System (EPMS). EPMS is an ACC-owned and developed instantiation of Atlassian’s highly flexible and scalable Jira project management software. EPMS is deployed as a server-based environment at 363d ISR Wing at Joint Base Langley-Eustis (JBLE) on SIPRNet and AF JWICS. The software supports a wide variety of Airmen customers across the 480th ISR Wing, the 363d ISR Wing, and ACC/A2, providing project, process, data, and analytic services for combat operations and staff applications.
2.3. The Atlassian Solutions Support will initially consist of two lines of effort (LOE):
2.3.1. LOE 1 – Cloud Migration: This LOE will focus on supporting ACC/A2 and 363 ISRW’s migration of EPMS from its current server-based environment on SIPRNet to a cloud (C2S)-based environment. This migration must be executed with no degradation to current EPMS services provided to customers worldwide and will set the conditions for sustainable, scaled EPMS services across the USAF. Specific Atlassian Solutions Support for this LOE shall include:
| Phase |
| Description |
| Outcome |
| Discovery & Requirements Gathering |
| Begin discovery and requirements gathering. Set up in the environment |
with access. Become familiar with policies and procedures.
Access Credentials
Establish Test Environment
| Develop implementation plan based on Discovery and Requirements gathering. The solution may include CAC / PIV authentication, user migration, Active Directory / LDAP connectivity, and Data Center architecture. |
| Implementation Plan and |
Documentation
Initiate Test Migration Effort
| Test migration and further refine implementation plan. Work with stakeholders to begin coordinating testing of EPMS (Jira) projects and Confluence spaces. |
| Test Plan and Test Cases |
Continue Test Migration Effort
| Continue test migration. Test any user migration efforts during this phase. |
| Test Results |
Finalize Test Migration Effort
| Finalize all testing and migration. Begin production planning. Coordinate with stakeholders for the migration. |
| Finalized Test Results |
Migrate to CS2 Environment
| Migrate the entire EPMS environment to CS2. Switch to the new environment with limited / no downtime. |
| Migrated Environment |
2.3.2. LOE 2 – Staff Migration: This LOE will focus on establishing the governance, administration, and training environment to enable ACC/A2 to migrate its current and future staff operations onto the EPMS (Jira) platform. Specific Atlassian Solutions Support for this LOE shall include:
| Phase |
| Description |
| Outcome |
Discovery & Requirements Gathering
Governance Approach Develop governance documentation for integrating EPMS projects and data sources, as well as building and deploying configuration updates into the EPMS environment. Include recommended add-ons and apps based on customer needs. Finalize training materials.
Stakeholder Meetings
Governance / Best Practices Plan
Training Plan
Custom Training Delivery
| Provide custom training on-site. |
| Delivered Training |
Custom Configuration and Administration Support
| Support the configuration and administration of the EPMS cloud implementation. |
| Delivered Configuration and Administration Support |
| Handoff |
| Handoff all tasks to permanent on-site |
administrator and finalize training.
Finalized Governance, Training, Configuration, and Administration Results – Roadmap Established for Full Staff Migration
2.4. Overall, the desired outcome of both LOEs is to provide an environment for a single FTE/CME to continue governance, training, configuration, and administration for EMPS in its cloud deployment.
2.5. Atlassian Solutions Support for these two LOEs shall include the following expertise:
| Resource Type |
| Knowledge, Skills, and Abilities |
Senior Atlassian and Cloud System Administrator AWS CS2 specialist. Extensive experience with the USAF and Intelligence Community. Ability to build out and deploy a Data Center environment in CS2 and migrate data.
Atlassian and Cloud System Administrator AWS and CS2 administrator with experience developing and deploying the Data Center environments of Jira and Confluence. Ability to assist with development and implementation.
Atlassian Specialist Governance, training, and Atlassian configuration expert. Experience in the Intelligence Community and USAF with Atlassian development and configuration expertise.
3.0 Period of Performance
3.1. Anticipated start date: TBD
3.2. Anticipated end date: TBD
3.3. LOE 1 will be the main effort for the first 3 months of the period of performance, with support to LOE 1 declining slightly mid-project in order to increase support to LOE 2.
4.0 Place of Performance
4.1. Work shall be performed at the contractor’s location during the planning phases of LOE 1, with site visit(s) to JBLE as required. Testing and execution phases of LOE 1 shall be performed on-site at JBLE with 363 ISRW and ACC/A2.
4.2. LOE 2 shall be performed on-site at JBLE with ACC/A2.
4.3. ACC/A2 and 363 ISRW will provide baseline artifacts and relevant data to the contractor to plan and execute both LOEs.
5.0 Classification
5.1. Work at the contractor’s location during the planning phases of LOE 1 can be conducted at the unclassified level.
5.2. Work involving remote access to the 363 ISRW’s EPMS environment shall be conducted at an accredited government or industry facility that provides access to SIPRNet.
5.3. Work on-site shall be conducted at the TS/SCI level.
5.4. All on-site contractors executing this SOW shall possess TS/SCI clearances through ACC SSO sponsorship as sub-contractors under a derivative DD254. Specifically, on-site contractor personnel are required to:
a. Have undergone a SSBI or Single Scope Background Investigation Periodic Review (SSBI-PR) within the last six years that was favorably adjudicated.
b. Have no break, greater than 24 months, in military service, Federal civilian employment or access to classified information under the Industrial Security Program.
c. Possess a current TS security determination.
d. Possess a SCI determination reflected in JPAS and/or Scattered Castles.
File details come from the government source that posted it. Updated .