DRAFT_BETA_TO_0001_PWS.pdf

For Official Use Only

BUSINESS, ENGINEERING & TECHNICAL ASSISTANCE (BETA)

ORDER NO. 0001

September 2015

PERFORMANCE WORK STATEMENT

Order No. 0001 Performance Work Statement (PWS) Business, Engineering, and Technical Assistance (BETA) Advisory & Assistance Services (A&AS)

ORDER NO. 0001

1.0 Background: This first order for support will be award with the Business, Engineering & Technical Assistance (BETA) advisory and assistance services (A&AS) Contract No. FA7014-16-D-5012.

2.0 Objectives: The objective of this requirement is to obtain A&AS and surge capacity for projects managed by the Office of the Under Secretary of the AF; Director, Business Transformation (SAF/US(M)) and Deputy Chief Management Officer (SAF/DCMO). For additional information, see the Performance Work Statement for the BETA A&AS Indefinite Delivery/Indefinite Quantity (IDIQ) contract.

3.0 Scope of Work/Performance Requirements: In support of this mission, SAF/US(M) requires expert Services Development and Delivery Process (SDDP) support services across a range of capabilities to include:

3.1 The contractor shall support business process re-engineering activities by documenting business processes and information asset requirements using the Air Force SDDP in accordance with AFMAN 33- 402 and standard enterprise architecture approaches such as Business Process Modeling Notation (BPMN), Department of Defense Architecture Framework (DoDAF), and Zachmann enterprise architecture, contextual modeling, and derivative use case development. An understanding of the application of these methods to large scale enterprise business transformations (e.g., global companies) is critical.

3.2 The contractor shall provide Program Management Expertise to both manage internally assigned projects as well as to support other Air Force/agency organizations partner teams in the development and delivery of their projects. This includes expertise on financial tracking, performance management tracking, and assisting with internal and external reporting. Key expertise and experience include program risk analysis, reporting and development of mitigation strategies.

3.3 SDDP Step 3 Support (Define Material Solution & Implementation Plan): the contractor shall support SDDP projects transitioning from Step 2 (Identify Mission Processes to Deliver Doctrine, Organization, Training, Material, Leadership, Personnel, Facilities (DOTMLPF) Capabilities) into SDDP Step 3 by providing: contextual modeling; derivative use case development; information technology (IT) functional requirement analysis; technical input into Course of Action (COA) criteria; COA analysis and criteria evaluation; creation of Service Reference Model (SRM), Data Reference Model (DRM), Community of Interest (COI) vocabulary package, Integrated Master Schedule (IMS), Work Breakdown Schedule (WBS) and Materiel (M) Implementation Plan in accordance with AFMAN 33-402 and associated Tactics Techniques and Procedures (TTPs) for inclusion in the Bounded User Requirement.

3.4 SDDP Workshop Facilitation: The contractor shall facilitate and orchestrate meetings (from high level AF executive governance meetings to focused tiger team efforts) with necessary expertise. The contractor shall provide support in developing meeting agendas and desired outcomes, administering large meetings, developing presentations, facilitating discussions, and capturing minutes and action items.

The facilitation shall assist the government in developing the requisite products to ensure successful delivery of capabilities in accordance with the SDDP.

Performance Work Statement (PWS) Business, Engineering, and Technical Assistance (BETA) Advisory & Assistance Services (A&AS)

3.5 Data Capture: The contractor shall provide data capture and co-facilitation support to assist project leads with all pre-event, event, and post-event work. This includes scheduling meetings and facilities, drafting correspondence, gathering data, documenting process maps using Microsoft Office Visio or other government designated modeling tool, documenting all event work, drafting presentations, and co-facilitation. The contractor shall document the results of the events in AF standards such as Business Process Modeling Notation (BPMN) and shall be able to identify issues and inconsistencies as the event products are generated to assist the facilitators in adjusting the event agenda to meet the objectives of the event.

3.6 Service Reference Model Support: The contractor shall support the AF Functional leads by providing contextual modeling support in order to capture a description of the functions and services that a material solution must deliver in terms of software engineering in regards to Web Services Code Requirements, Commercial Off-The-Shelf/Government Off–The-Shelf (COTS/GOTS) Requirements, System Requirements, Onboarding Requirements within AF direction on the Operation, Implementation, or Target Baseline as applicable.

3.7 Compliance Support Guidance for SDDP Projects: Contractor shall support AF Functional leads by providing compliance requirements expertise to SDDP projects (compliance requirements as called out in SDDP Step 3 e.g., Clinger-Cohen Compliance, Implementation Balance Line Compliance). To include awareness and understanding of breadth and depth of compliance requirements, informing project schedules with regard to compliance activities, and supporting the execution of compliance activities and preparing documentation of same.

3.8 Data Reference Model Support: The contractor shall retain enterprise data expertise to include skills in the application of semantic/ontological standards, protocols and development methods to enterprise data governance, IT security models, design and run time discovery, architectural alignment, reuse, streamlined development, and authorization /access in order to assist SDDP projects in their development of the Data Reference Model.

3.9 The contractor shall analyze and provide recommendations for harmonization of COI deliverables, including vocabularies, ontologies, roles and permissions, authoritative data source (ADS) recommendations. The contractor shall provide qualitative reviews of deliverables to assure deliverables are scoped within the context of mission or business process threads. The contractor shall provide technical reviews of deliverables to assure high-quality COI deliverables and conformance to COI Coordination Panel-approved processes, tools, templates and standards.

3.10 The contractor shall construct ontologies, eXtensible Markup Language (XML) schemas, data dictionaries, synonym sets, Unified Modeling Language (UML) schemas, and any other form of vocabulary artifact deemed appropriate by the COI Coordination Panel or in support of chartered SDDP DRM work. The contractor shall convert COI vocabularies into formats that can be implemented within the AF operating environment to support enterprise services such as discovery, storage and lifecycle management. The contractor shall develop standard processes, tools, templates and standards to support ontology development AF-wide. The contractor shall develop and maintain configuration management tools and processes for ontology work-in-process, final and updated ontologies.

3.11 System Architecture: The contractor shall provide technical expertise for projects to inform and document target and implementation baselines for supporting IT. This includes web expertise and knowledge of web standards, protocols and applications; Enterprise Resource Planning (ERPs); and legacy data transition to future state environments. The contractor shall also provide expert knowledge of

Performance Work Statement (PWS) Business, Engineering, and Technical Assistance (BETA) Advisory & Assistance Services (A&AS)

IT security models, and experience with developing Platform as a Service (PAAS) solutions. The contractor shall analyze system architectures for all types of AF IT capabilities, specifically ERPs, COTS products, and web services. The contractor shall deliver high-quality analytical technical reports with system support recommendations for improvements or alternate action.

3.12 Part-Time Chief Technology Officer (CTO) Support: The contractor shall provide principal level consulting or as needed to facilitate meetings of the AF CTO engineering team and to recommend priorities, schedules and deliverables. The contractor shall interface with senior leaders on obstacles, objectives and strategic direction.

3.13 Web Development: The contractor shall configure software as directed by US(M) and transition those capabilities to AF-sustained capabilities. The contractor shall develop standard processes and tools to support Web Service Development activities. The contractor shall train web service specialists operating within the COIs or on SDDP projects on standard processes and tools. The contractor shall maintain currency on commercial initiatives for web standards, protocols and applications. The contractor shall develop recommendations for submission to US(M) leadership on updates to AF web standards, protocols and applications.

3.14 Program Management: The contractor shall provide Program Management support available 0730 – 1630 every work day. The Program Manager shall be the primary point of contact for all contract execution and administration needs.

3.15 SDDP Guidance Support: The contractor shall provide expertise in SDDP methodology to mature guidance and reference materials, training materials, and alignment with related OSD and Air Force Policy and Guidance. Furthermore, the contractor shall maintain the AF SDDP SharePoint site.

3.16 Integrated Master Scheduling: The contractor shall maintain the US(M) Integrated Master Schedule of all transformation initiatives/projects being led or supported by US(M). The contractor shall consolidate project and schedules with weekly updates. Provide critical path analysis, identify task slippages, and maintain schedule status against schedule baseline.

3.17 Support Maintenance of Target Baseline: As released the AF Target Baseline is a mandatory compliance document. However, as future needs for Information Technology (IT) capabilities are identified, there will be situations where the new capability is not addressed in the existing lists of Scenarios and Technical Profiles. The contractor shall provide engineering review of the use case for newly proposed capabilities and identify existing Scenarios and Technical Profiles (TPs) that address the requirements. If gaps are found, the contractor shall augment existing Scenarios and/or TPs, or develop new documents as may be needed in each individual case. The team of IT system engineers shall maintain the library of “living” Scenarios and TPs.

3.18 Community of Interest (COI) Coordination Panel Support: The contractor shall facilitate, host and support sponsored COI Coordination Panel meetings, reviews and other activities. The contractor shall schedule meetings and facilities, draft correspondence and memoranda, gather data, document event work, produce minutes, and draft presentations. This includes maintaining COI policy and guidance, artifacts/documentation, COI SharePoint site, and Enterprise Senior Working Group secretariat support.

3.19 Program Action Directive / Program Guidance Letter (PAD/PGL) Support: The contractor shall provide PAD/PGL/Programming Plan (PPLAN) guidance to both Headquarters AF and other AF agencies/organizations partner teams in the development and delivery of their PAD/PGL/PPLAN action.

Performance Work Statement (PWS) Business, Engineering, and Technical Assistance (BETA) Advisory & Assistance Services (A&AS)

This includes tracking, compliance, performance management tracking, assisting with internal and external reporting, and maintain the PAD/PGL SharePoint site.

3.20 Administration Support: The contractor shall support the administration and management of the Continuous Process Improvement portal SharePoint site and track IGrafx licenses, to include training current and prospective users on the use of tool.

3.21 Deliverables: The contractor shall provide task-specific reports, informal analyses, papers, opinions, databases, briefings, etc. generated on an as-required (ad-hoc) basis during the performance of this contract and other deliverables as detailed in the PWS.

4.0 Historical Workload Data: Table 1 below represents estimated workload for this Task Order. A full-time equivalent is based on 1885 hours per year.

PWS Paragraph No. Task Hours/Year

3.1 Business Process Re-Engineering Support 377

3.2, 3.16 Program Management Expertise 3016 3.3, 3.5, 3.6 SDDP Step 3 Support 8682.5

3.4 SDDP Facilitation Support 3770

3.7 Compliance Support 1319.5

3.8 DRM Support 1508

3.9, 3.10 COI Support 1319.5

3.11 System Architecture Support 2073.5

3.12 Part-Time Chief Technology Officer (CTO) Support 96

3.13 Web Development 1885

3.14 Program Management 565.5

3.15 SDDP Guidance Support 565.5

3.16 Integrated Master Scheduling 2828

3.17 Support Maintenance to Target Baseline 942

3.18 Community of Interest (COI) Coordination Panel

Support 751

3.19 PAD/PGL Support 1131

3.20 Support Administration 160

TOTAL 30,990

Table 1 - Historical Workload

Performance Work Statement (PWS) Business, Engineering, and Technical Assistance (BETA) Advisory & Assistance Services (A&AS)

5.0 Deliverables. See Table 2. Electronic delivery is acceptable. Format should be in accordance with US(M)-defined templates. If not so defined, contractor format is acceptable. Delivery thresholds shall be consistent with project/initiative schedules and milestones.

Table 2: Deliverables Deliverable PWS Reference Frequency Delivery

POC/Format Monthly Progress Report (MPR)

1.10 on IDIQ PWS Monthly, not later than the 15th of each month

The COR and Contracting Officer by email

Deliverables/ Ad-Hoc Reports

3.21 As requested The COR or Project

Lead

SERVICES SUMMARY

Electronic delivery and Contractor format is acceptable. The Contractor shall combine monthly updates for the Progress Report and Cost Report. The contractor shall provide them as one submittal.

Performance Objective

PWS

REFERENCE DELIVERY THRESHOLD

Evaluation Method

Monthly Progress Report is submitted on time

1.10 on IDIQ

PWS

There is no more than one late deliverable per year.

100% Inspection

Monthly Progress Report is technically accurate and comprehensive

1.10 on IDIQ

PWS

There is no more than one instance of a rejected report per year and all discrepancies are fixed within 5 days of notification from COR of each month

100% Inspection

Qualified Personnel are provided at task order start date

PWS 3.1-3.21 Resumes shall be submitted to the COR to ensure all candidates meet the minimum requirements of the Task Order.

100% Inspection

6.0 Period of Performance. The period of performance for this task order is 23 November 2015 through 22 November 2016.

7.0 General Performance Requirements: See BETA A&AS IDIQ Contract.