DRAFT_BETA_BASE_PWS.pdf

PERFORMANCE WORK STATEMENT

BUSINESS, ENGINEERING & TECHNICAL ASSISTANCE (BETA)

September 2015

Part I General Information

1. GENERAL: This is non-personal services contract to provide Business, Engineering, and Technical Assistance (BETA) services for the United States Air Force-wide improvement projects. The Government shall not exercise any supervision or control over the contract employees performing the services herein. Such contract employees shall be accountable solely to the Contractor who, in turn, is responsible to the Government.

1.1 Description of Services: The Secretary of the Air Force Office of Business Transformation (SAF/US(M)) is continuing to look for more effective and efficient ways to support business process improvements and where necessary deploy supporting Information Technology (IT) in an effective and efficient manner. The Air Force has a requirement for Advisory and Assistance Services (A&AS) that includes, but are not limited to, the following categories: technical and engineering; information and data management; process engineering; performance assessment; and change management. This effort is envisioned to provide the Air Force with repeatable, defined, accurate, timely, well-documented and well-managed processes that identify information assets, provide an organized approach to meeting information needs, and developing data vocabulary and ontology products to support refined business processes. In addition, this effort shall support SAF/US(M) assessments of progress toward Air Force and program mission objectives. Tasks to be performed to support this effort principally include work within the following areas: Information Assurance; Information Management; Requirements Development; Enterprise Architecture; Operational Support Architecture; and Network Web-Based Support. The Contractor would be required to provide tools, equipment, personnel, and supervision necessary to support tasks to be described in orders issued under the contract vehicle.

1.2 Background: In accordance with SAF/US(M)’s continuing efforts to look for more effective and efficient ways to deliver support to the war-fighter at home and abroad, this acquisition for BETA is a recurring and a follow-on requirement.

1.3 Objectives: The objective of this requirement is to obtain advisory and assistance services (A&AS) for projects managed by the Office of the Under Secretary of the Air Force; Director, Business Transformation and Deputy Chief Management Officer (SAF/US(M)). SAF/US(M) is responsible for business/mission transformation seeking to make the USAF’s organize, train, and equip responsibilities more effective for our war fighters through the development and adoption of more efficient business/mission practices. Additionally SAF/US(M) is responsible for guiding the Air Force to reduce overall cost of operations consistent with direction from the Office of the Secretary of Defense and the Office of Management and Budget.

In order to deliver these activities, SAF/US(M) is organized into two directorates; Transformation and Transformation Outreach and Support. This contract shall principally provide expert support services for the Transformation Directorate. The Transformation Directorate provides strategic planning, performance and project management, enterprise infrastructure management strategies, to include data architecture and deployment of supporting services, and performance measurement and monitoring for business transformation and activities aimed at reducing the cost of operations. This effort includes the development of new business practices that become institutionalized through implementation of highly visible projects, through the use of methods derived from industry benchmarking, across the Air Staff and Major Commands (MAJCOMs). SAF/US(M) adopts and adapts many of these industry best practices and supports their implementation by providing industry expertise to support our partner teams and put the new methods into practice.

1.4. Scope: In support of this mission, SAF/US(M) requires expert services across a range of capabilities to include:

1.4.1 Supporting business process re-engineering activities by documenting business processes and information asset requirements using the Air Force Services Development and Delivery Process (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.

Planning Factor: SAF/US(M) anticipates that support for at least five equivalent concurrent projects at varying levels in addition to the development of the Air Force guidance shall be required throughout the performance period.

1.4.2 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.

Planning Factor: SAF/US(M) supports assessment of Air Force performance against strategic objectives, including projects aimed at reducing cost of operations Air Force wide. Key role is to interface with up to 10 key functional teams, which are actually leading the transformation, and to provide assessments for the Secretary of the Air Force, Under Secretary of the Air Force, Chief of Staff, and Vice Chief of Staff.

1.4.3 Enterprise Data expertise to include skills in the application of semantic/ontological standards, data architecture, protocols and development methods to enterprise data governance, IT security models, design and run time discovery, architectural alignment, reuse, streamlined development, and authorization /access.

Planning Factor: Provide technical leadership and training in data architecture and ontology practice and support for all Air Force vocabulary and data activities, and XML development support for at least five equivalent concurrent projects. Full time support for SAF/US(M) internal information management activities to include configuration management, development of policy and guidance, integration of ontology. Be capable of providing surge capability to support up to eight concurrent data community activities.

1.4.4. Technical expertise for pilot projects to inform and document target and implementation baselines for supporting IT. This includes web expertise and knowledge of web standards, protocols and applications, ERPs, and legacy data transition to future state environments. Expert knowledge of IT security models, and experience with developing Platform as a Service (PAAS) solutions are critical capabilities.

Planning Factor: Expert support for three major ERP developments and at least three Program designs/architectures including target and implementation baselines. Piloting expertise for at least three projects.

1.4.5. Performance Management Measurement. Commercial best practice skills to assist in the development of performance objectives for major business process, ability to develop metrics to assess progress toward performance outcomes and skills in assessing and reporting on progress toward goals.

Metrics development, and enterprise level performance assessment are critical skills.

Planning Factor: Application of commercial best practices technique to major AF business transformation projects, including associated IT development. Support assessment of three to four major lines of transformation on an Air Force-wide scale.

1.5 Period of Performance: See Schedule

1.6 General Information

1.6.1 Performance Requirements: The Contractor shall provide staff support across all performance requirements to include:

1.6.1.1 Working with Government to support oversight of programs, processes, operations, exercises, and other activities;

1.6.1.2 Provide recommendations based on research, analyses, risk assessments, and review of concepts, staff packages and other reports;

1.6.1.3 Provide expert support to Government personnel at various forums and meetings;

1.6.1.4 Support the drafting and coordination of staff packages for review and approval;

1.6.1.5 Support the creation of issue/point papers, reports, publications, and other documents;

1.6.1.6 Build and present briefings;

1.6.1.7 Set up, prepare, facilitate, and provide post-event minutes and summaries for action officer, executive, and Congressional level hearings, meetings, seminars, conferences, boards and related activities.

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.1.9 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.

1.6.2 Recognized Holidays: The following Federal holidays are observed by this installation:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day Washington’s Birthday Veterans Day Memorial Day Thanksgiving Day Independence Day Christmas Day Presidential Inauguration

1.6.3 Hours of Operation: The contractor is responsible for and shall be available for conducting business between the hours of 0730 – 1630The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

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.

1.6.5 Type of Contract: The Government will award a single Indefinite Delivery/Indefinite Quantity (ID/IQ) contract.

1.6.6 Security Requirements: Four (4) of the contractor personnel performing work under this contract must have a TS security clearance at time of proposal and shall be required on the first Task Order, and the remainder of the contractor personnel must have a SECRET security clearance prior to performance on a Task Order if they require a SAF/US(M)-sponsored government e-mail, and (CAC). All contractor personnel must maintain the level of security required for their contracted duties for the life of the contract. A DD Form 254, Contract Security Classification Specification, applies to this contract. The security requirements are in accordance with the attached DD Form 254. The Contractor may require access to classified source data up to and including TS in support of this effort. Any extracts or use of such data shall require the Contractor to apply derivative classifications and markings consistent with the source from which the extracts were made in accordance with DoD 5220.22M, National Industrial Security Program Operating Manual, a manual for safeguarding classified information; and Executive order 12356, Classified National Security Information. Pursuant to DoD 5220.22M; Chapter 6, Visits and Meetings; the Contractor shall submit visit requests to SAF/US(M).

1.6.7 Phase-Out: The Contractor shall develop plans and procedures to aid the Government and/or the Contractor’s successor in assuming contract work. The Contractor shall coordinate with its successor to ensure an orderly transition in duties. The contractor shall submit its Phase-Out transition plan to the Contracting Officer 90 days prior to the expiration of the contract period.

1.6.8 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves. This shall be accomplished by wearing company issued identification cards on a company lanyard (badge or identification holder); visible to all parties to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

1.6.9 Contractor Travel: The Contractor shall be required to travel Outside of Continental United States (OCONUS) and within the National Capital Region (NCR) during the performance of this requirement to attend meetings, conferences, and training. Travel within the NCR is considered the cost of doing business with the Government, shall not be charged to the Government and will not be reimbursed. The contractor may be required to travel to off-site training locations and to ship training aids to these locations in support of this PWS. The Contractor shall be authorized travel expenses consistent with the substantive provisions of FAR Part 31.205-46 – Travel Costs, and the applicable Joint Travel Regulations (JTRs) and the limitation of funds specified in each task order. All travel requires Government approval/authorization from the COR prior to conducting travel.

1.6.9.1 Travel shall be accomplished throughout performance of this contract in accordance with the JTR in effect at the time of travel. The estimated negotiated amount shall be calculated in accordance with the JTR in effect at the time of travel. Airfare shall be at prevailing Government rates for commercial airlines for economy class. For OCONUS travel (if required), Contractor employees are responsible for obtaining passports, visas, and medical clearance for designated operations areas. Estimated airfare and costs affiliated with travel shall be submitted to the COR prior to travel for review on the attached travel form.

1.6.10 Other Direct Costs: These costs shall be pre-approved by the COR before the submittal of any invoices billing towards this category and this shall not include any travel related costs. The ODC Contract Line Item Number (CLIN) will only cover reproduction, and shipping expenses associated with training activities. The Government has stated this Contract Line Item not to exceed $75,000.00.

Any handling fees associated with ODC during this PoP, shall be included.

1.6.11 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications, and/ or work statements, etc.) which may create a current or subsequent Organizational Conflict of

Interests (OCI) as defined in Federal Acquisition Regulation (FAR) Subpart 9.5, Organizational and Consultant Conflicts of Interest. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan shall be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may put in effect other remedies as he or she deems necessary including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI. In accepting and performing the work required by this contract and all amendments thereto, the Contractor certifies that such work does not constitute or create a conflict of interest due to other work being performed by its firm. The contractor shall ensure that its employees sign an Organizational Conflict of Interest and Non-Disclosure Agreement.

1.6.12 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with FAR Subpart 42.5, Post-award Orientation. The Contracting Officer and the Contracting Officer’s Representative (COR), may meet periodically with the Contractor to review the Contractor's performance.

At these meetings, the Contracting Officer will apprise the Contractor of how the Government views the contractor's performance and the Contractor shall apprise the Government of concerns, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

1.6.13 Contracting Officer’s Representative (COR): The COR will be identified by separate letter.

The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assures that the Contractor performs the technical requirements of the contract; performs inspections necessary in connection with contract performance;

maintains written and oral communications with the Contractor concerning technical aspects of the contract; issues written interpretations of technical requirements including Government drawings, designs, specifications; monitors Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinates availability of government-furnished property (if applicable), and provides site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the contract or resulting order(s).

1.6.14 Key Personnel: The following personnel are considered key personnel by the Government:

Program Manager. The Contractor shall provide a Program Manager who shall be responsible for the oversight of the performance of the work. The Program Manager shall act on behalf of the Contractor and shall be designated in writing to the Contracting Officer. The Program Manager shall have full authority to act for the Contractor on all task order matters relating to the daily operation for the contract and order(s). The Program Manager shall be available between the hours of 0730 and 1630, Monday through Friday except Federal holidays or when the Government facility is closed for administrative or unforeseen reasons.

1.7 Unlimited Data Rights: In accordance with FAR Clause 52.227-14, Rights in Data—General (May 2014), the Government shall have unlimited rights to any technical data produced as a result of this contract, regardless of form or the media on which it may be recorded, for the Government to use, disclose, reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly, in any manner and for any purpose, and to have or permit others to do so.

1.8 Invoices: Invoices shall conform to the requirements stated in the contract. Additionally, the following requirements apply:

1.8.1. Invoices shall reflect work from the first working day of the month through the last working day of the month.

1.8.2 Invoices shall reflect all work performed for the month of work being billed.

1.8.3 Invoices shall be input into Wide Area Workflow by the 15th of each month for work from the prior month.

1.9 Contractor Employee In-Processing/Out-Processing: The Contractor shall follow the following procedures to process Contractor employees in and out of SAF/US(M) facilities when they shall be required to perform work in support of this contract or any resulting task order:

1.9.1 In-Processing

1.9.1.1 Send visit request for employees to the COR.

1.9.1.2 Contact the COR for help in identifying applicable directorate sponsors if needed.

1.9.1.3 If a CAC is required, contractor shall provide necessary information for SAF/US(M) to fill out and submit the paperwork.. SAF/US(M) will notify employees when their paperwork is ready for the employee to pick up and take to the Pentagon to acquire their badge/CAC.

1.9.1.4 If a network account is required, within 72 business hours of being given a network account, contractor employees shall establish an Advanced Distributed Learning Service (ADLS) account on the Air Force portal; complete Information Assurance training and Records Management training; and provide completion certificates to the COR. The web address and instructions for accessing the training on the ADLS site.

1.9.2 Out-Processing: If contractor employee was issued a Pentagon badge and/or CAC, contractor employees shall turn in their Pentagon badge and CAC to the COR prior to their departure.

1.10 Monthly Progress Report (MPR)

1.10.1 No later than the 15th of the month, the Contractor shall provide a MPR to the COR and the Contracting Officer summarizing its efforts on the contract from the previous month and addressing any issues. The Progress Report shall include, but not necessarily be limited to, the following:

(a) How Contractor employees are allocated against contract projects;

(b) Contractor employees performing work on-site compared to off-site performance;

(c) Requirement for SAF/US(M)- sponsored e-mail accounts, and Common Access Cards (CAC); and

(e) The Contractor shall highlight any employee changes since the last report and anticipated changes within the next 30 days.

1.11 Contractor Manpower Reporting Application (CMRA): The contractor shall report ALL labor hours (including subcontractor labor hours) required for performance of services provided under this contract via the secure Contractor Manpower Reporting Application (CMRA) data collection site. The Contractor is required to completely fill in all required data fields at: http://www.ecmra.mil. Reporting inputs shall be for the labor executed during the period of performance for each Government fiscal year

(FY), which runs 1 October through 30 September. All data for the FY shall be reported not later than 31 October of each calendar year. The Contractor may direct questions to the CMRA help desk.

LABOR CATEGORY DESCRIPTIONS

Lead Program Manager Education/Experience: Bachelor’s degree or higher/Relevant experience managing diverse, technical support team for at least 3 years Functional Description: Serves as the contractor's contract manager, and shall be the contractor's authorized interface with the Government Contracting Officer (CO), the Contracting Officer's Representative (COR), government management personnel and customer agency representatives. Responsible for formulating and enforcing work standards, assigning contractor schedules, reviewing work discrepancies, supervising contractor personnel and communicating policies, purposes, and goals of the organization to subordinates. Shall be responsible for the overall contract performance and shall not serve in any other capacity.

Consultant Senior Education/Experience: Progressive management experience, including extensive supervisory and project management experience.

Functional Responsibility: The Senior Consultant is a recognized authority across multiple areas of expertise. The Senior Consultant provides leadership at the highest technical, programmatic, and organizational levels for teams to accomplish customer-sponsored projects, including new program development. Leadership comprises problem definition, identification of avenues of approach, identification of applicable resources, and execution of tasks within the project. Senior Consultants can advise at the equivalent of very senior level corporate enterprise leadership.

Minimum Years of Experience:

Level Ph.D. Master’s Degree Bachelor’s

Degree Associate

Degree 4 10 12 14 16 3 5 7 9 11 2 3 5 7 9 1 1 3 5 7

Consultant 1, 2, 3,4 Education/ Exper ience: Relevant experience, including supervisory and project management experience Functional Responsibility: The Consultant is a recognized authority across multiple areas of expertise. Consultant provides leadership at a high technical and programmatic level for teams to accomplish customer sponsored projects, including new program development. Leadership comprises problem definition, identification of avenues of approach, identification of applicable resources, and execution of tasks within the project.

Minimum Years of Experience:

Level Ph.D. Master’s Degree Bachelor’s

Degree Associate

Degree 4 8 10 12 14 3 5 7 9 11 2 3 5 7 9 1 1 3 5 7

Principal Enterprise Architect Education/Experience: Bachelor’s degree (minimal requirement)/Substantial, relevant experience.

Functional Responsibility: The Principal Enterprise Architect will apply architecture skills spanning business modelling and process design, data design, application design, IT industry standards, services design, solutions modeling, and benefits analysis. The Principal Enterprise Architect provides direct support and mentorship to business reengineering, contextual modeling (data reference models, service reference models), and IT functional requirements creation and management for major business transformation initiatives. The architect develops architectural products and deliverables for the enterprise and operational business lines. Application of strong team leadership and project management, communication skills, domain knowledge of business functions (such as procurement, supply chain management, and human resources management), and IT technical breadth are required. The principal enterprise architect will assist in producing acquisition and design requirements for complex IT systems, including requirements discovery and analysis, formulation of solution context, identification of solution alternatives and their assessment.

They may also extend into support to technology selection and design configuration.

Minimum Years of Experience: Six (6) years

Senior Data Architect Education/Experience: Bachelor’s or Masters IT College Degree preferred/Demonstrable experience in data modeling for (minimal requirement)/Substantial, relevant experience.

Functional Responsibility: The Senior Data Architect is responsible to assist in applying semantic/ontological standards, protocols, development methods to enterprise data governance. The architect will support harmonization of data standards and dictionaries through Community of Interest (CoI) coordination, including vocabularies, ontologies, roles and permissions, authoritative data source (ADS), and development of Data Reference Models (DRMs) in defining requirements for business and IT solutions. The senior data architect will advise on the varied views of the Zachman Framework for enterprise architecture relative to data, to include scope/contextual view, business model/conceptual view, enterprise/logical data model, physical data model, and actual databases. The Senior Data Architect will assist in analyzing architectures for all types of IT capabilities, to include Enterprise Resource Planning (ERP), Commercial-Off-The-Shelf (COTS), web services and Government products

Minimum Years of Experience: Six (6) years

Senior Systems Engineer

Education/Experience: Bachelor’s or Masters IT College Degree preferred/Demonstrable experience in data modeling for (minimal requirement)/Substantial, relevant experience.

Functional Responsibility: The Senior Systems Engineer will advise and support requirements definition technical efforts and performs typical associated tasks that include, but are not limited to, requirements analysis and definition, developing contextual models describing functions and services that a material solution must deliver in terms of software engineering, cost analysis, cost performance trade-off analysis, feasibility analysis, analysis of alternatives, regulatory compliance support, technology conceptual tradeoffs, test requirements, IT security best practices, and special studies and analyses. The Senior Systems Engineer will be advising on IT systems requirements definition in alignment with Platform-as-a-Service and use of commoditized infrastructure for new IT and migrating current IT capabilities.

Minimum Years of Experience: Six (6) Years

Senior Performance Analyst Education/Experience: Bachelor’s or Masters IT College Degree preferred/Demonstrable experience in data modeling for (minimal requirement)/Substantial, relevant experience.

Functional Responsibility: The Senior Performance Analyst will advise and assist in development of performance measures and standards in alignment with enterprise and business line strategic goals and objectives. The analyst will assist in developing and managing processes for approval of performance targets, tracking and assuring correction actions are identified and taken when deviations occur. The performance analyst will also assist in developing reports for internal and external reporting at enterprise and business line levels.

Info Analyst Education/Experience: Relevant experience related to performance of analysis of programs and information system schemes.

Functional Responsibility: The lnformation/Functional Analyst will perform qualitative and quantitative analysis of complex programs and information system schemes. The Senior Information/Functional Analyst analyzes functional specifications to determine information and process flows, develops program logic and evaluates performance measures in support of complex implementation efforts.

Minimum Years of Experience

Level Master’s Degree Bachelor’s Degree

Associate Degree

High School

3 2 4 6 8 2 1 3 5 7 1 0 2 4 6

MS SharePoint Specialist Education/Experience: A bachelor's degree is desired. At least three years of experience in MS SharePoint design, configuration, and implementation.

Functional Responsibility: Developing and maintain SharePoint pages for collaborative work across a diverse set of organizations and stakeholders to gather, document, and understand business requirements then translate them into high-quality, enterprise-ready solutions. The position requires the candidate to apply experience in all aspects of SharePoint implementations including custom development, site administration, installation and architecture. Additionally, the position may require developing SQL Server databases as part of solutions. Responsibilities involve frequent interaction with other team members as well as other customers and stakeholders. This position performs periodic assessments pertinent to changing program requirements to keep SharePoint sites current and user friendly, develops alternatives and recommendations. The ideal candidate must apply strong interpersonal and communication skills.

1.12 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.

1.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.

1.14 Quality Control Plan (QCP): The contractor shall develop a QCP that demonstrates how the Contractor shall maintain an inspection system acceptable to the Government covering the services under this contract. The QCP shall demonstrate the Contractor’s documented processes and procedures to monitor and control:

• Objectives in Services Summary

• Subcontractor relationships

• Invoicing

Part II

ACRONYMS

2.0. ACRONYMS: Acronyms that may be used in the PWS and what they represent are as follows:

ACOR Alternate Contracting Officer's Representative AFFARS Air Force Federal Acquisition Regulation Supplement BPMN Business Process Modeling Notation BPR Business Process Re-engineering CFR Code of Federal Regulations CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer’s Representative COTS Commercial Off-the-Shelf DoDAF Department of Defense Architecture Framework DD FORM 254 Department of Defense Contract Security Classification Specification DFARS Department of Defense Federal Acquisition Regulation Supplement DOD Department of Defense FAR Federal Acquisition Regulation CO Contracting Officer OCI Organizational Conflict of Interest

OCONUS Outside Continental United States (includes Alaska and Hawaii) ODC Other Direct Costs PIPO Phase In/Phase Out POC Point of Contact PP Performance Plan PM Program Manager PWS Performance Work Statement SS Services Summary QA Quality Assurance QAP Quality Assurance Program QC Quality Control QCP Quality Control Plan SDS Services Delivery Summary TE Technical Exhibit

PART III

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI)

3.1.1 Working Space: At the SAF/US(M) office at the Pentagon and Andrews AFB, the government will have "hot benches" for contractor use when necessary. Contractors shall work from contractor-designated facilities on a permanent basis. The contractor designated facility must be cleared TS at time of proposal; interim TS clearance is unacceptable.

Travel from contractor facilities to government facilities at the Pentagon and/or Andrews AFB: On an as-needed basis, the government may require the contractor to perform duties at the Pentagon or Joint Base Andrews.

3.1.2 GFE: The Government will not provide GFE laptops unless the contractor is performing work requiring access to For Official Use Only (FOUO) or Personal Identification (PI)-type information on a frequent basis. If the work is FOUO or PI-type information, the Government will provide GFE laptop with installed Virtual Private Network (VPN).

3.1.3 Government Network Access. As a SAF/US(M) Standard Operating Procedure (SOP), the Government will not issue a contractor an network access unless absolutely necessary. If the Contractor requires an unclassified network account, the Government will issue and provide a CAC(s). The Contractor shall access the unclassified government network CAC-enabled sites and Outlook Web Mail.

If the Contractor requires a classified network account, the Government will issue and provide a SIPR Token(s). Contractor shall access the classified government network via a SIPR Token issued by the government in approved spaces only. The Contractor shall be required to log into all their government networks once every 30 days (SIPR/NIPR accesses). If deemed necessary by the government, Contractors maybe issued an unclassified government laptop. The Contractor will safe guard the equipment, ensure the laptop is physically connected to the AF network at least quarterly to ensure patching, and return the equipment upon contract termination. If the equipment is lost/stolen/damaged, the Contractor shall immediately inform the COR.

3.1.4 Government Classified Network Account. All duties requiring performance of classified work can be conducted at government facilities or government-approved off-site contractor facilities.

3.1.5 The Government will provide access to required information to perform the tasks for subject contract. This support shall be available for use upon approval of this contract and shall continue until the contract end date.

Deliverables

Deliverable PWS Reference Frequency Delivery POC/Format Phase Out Transition Plan

1.6.7 90 days before expiration of contract

COR/MS-Office-compatible, electronic

OCI and NDA 1.6.11 At commencement of work

COR/MS-Office-compatible, electronic

Deliverables/Ad-hoc 1.12 As required Project lead/electronic reports Quality Control Plan 1.14 30 days after contract award COR and CO/ MS- Office-compatible, electronic

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

PWS 1.10 There is no more than one late deliverable per year.

100% Inspection

Progress Report is technically accurate and comprehensive

PWS 1.10 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 1.4-1.4.5 Resumes shall be submitted to the COR to ensure all candidates meet the minimum requirements of the Task Order.

100% Inspection