FA7014-15-R-5012-0001.doc

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

QUESTIONS AND ANSWERS TO RFP

QUESTION 1: Could you provide any insight on how you would like us to address the Task Order No 0001 in the proposal? After reviewing the General Instructions beginning on page 94 carefully, it seems that all references in the instructions point to addressing the Technical & Management Approach, Staffing Plan, and Pricing for the overall IDIQ. Should Task Order No 0001 be embedded in these sections or separately appended to these sections, or would you prefer some other method?

ANSWER: See Addendum to 52.212-1, Instruction to Offerors, paragraph 4.3.2 Price which describes that price evaluation will be based on Task Order 0001. See Addendum to 52.212-2, Evaluation of Commercial Items, paragraphs 1.5.1 Subfactor 1 Technical and Management Approach, 1.5.2 Subfactor 2 Staffing Plan including Qualifications Matrix and 1.7 Factor 3 Price which describes that evaluations will be based on Task Order 0001.

RFP CHANGE: N/A

QUESTION 2: The CLIN structure provided on page 7 of the solicitation, “Delivery Information,” only shows a single three-year period of performance. The Hourly Labor Rate tab of the provided pricing spreadsheet has a column for year 1, year 2 and year 3. Please explain how the columns on the Hourly Labor Rate tab corresponds to totals on CLIN 0001 and CLIN 0002?

ANSWER: The CLIN structure is for internal use and will contain the Not To Exceed Amounts based on the ceiling amount placed on the contract after award. The Government will consolidate all labor into a single CLIN. Attachment 1 Pricing Sheet, Hourly Labor Rates, the hourly labor rates proposed in this tab will be utilized to calculate the totals for each task order placed during the applicable ordering period. Contract award will be based on the requirements of Task Order 0001.

RFP CHANGE: N/A

QUESTION 3: The Performance Management requirement under CLIN 0002 is not covered under TO 0001; will the Government consider consolidating all the labor onto a single CLIN?

ANSWER: Yes, the Government will consolidate all labor into a single CLIN. Contract award will be based on the requirements of Task Order 0001.

RFP CHANGE: Labor CLINs 0001 and 0002 are consolidated into one labor CLIN.

QUESTION 4: Is the Government expecting offerors to provide an additional CLIN structure spreadsheet beyond what was provided in the original RFP? The solicitation refers to four CLINs, but the provided spreadsheet does not break down CLINs 0001 and 0002.

ANSWER: No, CLIN structure is for internal use and will contain the Not To Exceed Amounts based on the ceiling amount placed on the contract after award. The Government will consolidate all labor into a single CLIN. Contract award will be based on the requirements of Task Order 0001.

RFP CHANGE: N/A

QUESTION 5: Has a contractor performed similar work to this for the government in the past? If available, please provide the incumbent contract number. If you are unable to provide a contract number, is it safe to assume this is a new requirement for the government?

ANSWER: Yes, this is a follow-on requirement and the incumbent contract number is FA7014-13-D-0001.

RFP CHANGE: N/A

QUESTION 6: Would the Government consider putting this effort on the OASIS contract vehicle?

ANSWER: No, requirement is for an 8(a) competitive set-aside.

RFP CHANGE: N/A

QUESTION 7: We are a joint venture (jv) comprised of an 8 (a) SDVOSB and a VOSB. We maintain the required TSFC while our 8 (a) SDVOSB maintains the 8(a) status for this opportunity. Based on the dynamic of our jv, would our team’s bid remain compliant to the following?

1.6.1.8 Provide the required number of personnel with a DoD TOP SECRET (TS) clearance and the required number of personnel with a DoD SECRET clearance in accordance with paragraph 1.6.6; interim clearances are not acceptable.

1.6.4 Place of Performance: The work to be performed shall principally be in the National Capitol Region and at the Contractor ’s off-site facility and shall have adequate infrastructure to support daily interaction with Government project leads and team members via telephone or network communication protocols. The Contractor shall work in Government facilities as necessary to participate in meetings, work sessions, or other temporary duties. The contractor’s facility identified in Block 6 in the DD Form 254 shall be cleared as a Top Secret (TS) facility at time of proposal. Interim TS clearances are not acceptable at time of proposal. Contractor facility TS verification is through the Industrial Security Facilities Database (ISFD) using the company commercial and Government entity (CAGE) code submitted. In the event that a company has more than one CAGE Code assigned, the CAGE Code submitted shall be for the facility where the actual work is performed in support of SAF/US(M). “Personnel” TS clearance is different from “Facility” TS clearance and are not necessarily associated with each other. Personnel TS clearance is confirmed using an individual’s full social security number.

2.2 Facility Security Clearance (FCL): Due to the clearance requirements, all prospective offerors must possess a TOP SECRET Facility Security Clearance (FCL) at time of proposal. The FCL shall be approved/issued by the Defense Security Service (DSS) and FCL must be posted in the DSS Industrial Security Facility Database (ISFD). A verifiable TOP SECRET FCL must exist in the ISFD at time of proposal. Offeror’s FCL will be assessed as “responsive/non-responsive” at proposal submission. Offerors must have a FCL of Top Secret. Offerors without the required FCL will be deemed “non-responsive.”

ANSWER: If proposed companies are not an official 8(a) joint venture approved by the Small Business Administration then their proposal would not be compliant.

RFP CHANGE: N/A

SECTION SF 1449 - CONTINUATION SHEET

SUPPLIES OR SERVICES AND PRICES

CLIN 0001

The CLIN extended description has changed from Advisory & Assistance Services (A&AS) Firm Fixed Price (FFP) Business Engineering and Technical Assistance (BETA) Labor Support. The Contractor shall provide equipment, personnel, transportation, communication and supervision necessary to support SAF/US(M)’s mission to be described in task orders issued under the IDIQ contract vehicle. Reference 1.4.1, 1.4.2, 1.4.3 & 1.4.4 of the PWS. to Advisory & Assistance Services (A&AS) Firm Fixed Price (FFP) Business Engineering and Technical Assistance (BETA) Labor Support. The Contractor shall provide equipment, personnel, transportation, communication and supervision necessary to support SAF/US(M)’s mission to be described in task orders issued under the IDIQ contract vehicle. Reference 1.4.1, 1.4.2, 1.4.3, 1.4.4 & 1.4.5 of the PWS..

CLIN 0002

The CLIN type priced has been deleted.

The CLIN description has changed from A&AS Performance Management Measurement to CLIN CONSOLIDATED WITH LABOR CLIN 0001.

The CLIN extended description has changed from Advisory and Assistance Services Labor for Performance Management; The Contractor shall provide equipment, personnel, transportation, communication and supervision necessary to support SAF/US(M)’s mission to be described in task orders issued under the IDIQ contract vehicle. IAW the PWS paragraph 1.4.5. to THIS LABOR CLIN HAS BEEN CONSOLIDATED WITH LABOR CLIN 0001..

The pricing detail quantity 1.00 has been deleted.

The unit of issue Lot has been deleted.

DELIVERIES AND PERFORMANCE

The following Delivery Schedule Item has been deleted from CLIN 0002:

POP 15-NOV-2015 TO

14-NOV-2018

JORDAN WESCOTT

1500 WEST PERIMETER ROAD SUITE 4170

ANDREWS AFB MD 20762

240-612-5713

FOB: Destination

F1AF1V

The following have been modified:

TASK ORDER 0001 PWS

BUSINESS, ENGINEERING & TECHNICAL ASSISTANCE (BETA)

TASK ORDER NO. 0001

September 2015

PERFORMANCE WORK STATEMENT

TASK 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-XXXX.

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.

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, Target and Implementation Baseline 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 data dictionaries, synonym sets, 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.

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 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. 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 based on historical data. A full-time equivalent is based on 1885 hours per year.

TOTAL

30,990

Table 1 - Historical Workload

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

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.

6.0 Period of Performance. The anticipated period of performance for this task order is 27 November 2015 through 26 November 2016.

6.1 Transition Phase-In: A non-incumbent contractor shall support a two week transition period to ensure smooth hand-off from the predecessor Business, Engineering, and Technical Assistance contract. The anticipated period of this transition shall be 27 November-11 December 2015. Should the contractor hire an incumbent employee to fill a required position, the contractor shall coordinate the transition with the incumbent contractor. In no case shall the contractor double bill the Government during the transition period for the work of a single employee. The contractor shall take all actions necessary for a smooth transition of the contracted operations. During the phase-in period, the contractor’s management personnel will be permitted to observe any on-going operations, as approved by the Contracting Officer Representative.

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

(End of Summary of Changes)