DRAFT_BETA_PWS_201701003.pdf

FAXXXX-18-D-00XX-00XX BETA PWS

SAF/MG BETA PWS

PERFORMANCE WORK STATEMENT

BUSINESS, ENGINEERING & TECHNICAL ASSISTANCE (BETA)

For

Deputy Under Secretary of the Air Force, Management (SAF/MG)

FAXXXX-18-X-XXXX

Date: 2 October 2017

1. INTRODUCTION

1.1 General. This is a 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.2 Background. The Office of the Deputy Under Secretary of the Air Force, Management and Deputy Chief Management Office (SAF/MG) is continuing to look for more effective and efficient ways to support Air Force business operations and refine the development of Defense Business System (DBS) requirements supporting the Business Mission Area (BMA) Information Technology (IT). 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; change management, facilitation, project management, and scheduling. In addition, this effort shall support SAF/MG assessments of progress toward Air Force strategic and program mission objectives. The Contractor is required to provide tools, equipment, personnel, and supervision necessary to support tasks to be described in orders issued under the contract vehicle.

The Air Force will be integrating the requirements of AFMAN 33-402, Services Development and Delivery Process (SDDP) into AFMAN 63-144, “Defense Business System Life Cycle Management” in the near future. This effort implements DOD Instruction 5000.75 for Business Systems Requirements and Acquisition that include requirements, acquisition and IT compliance.

1.3 Objective. The objective of this requirement is to obtain advisory and assistance services (A&AS) for SAF/MG. SAF/MG is responsible for business/mission transformation seeking to make the USAF’s organize, train, and equip responsibilities more effective for our warfighter through the development and adoption of more efficient business/mission practices and performance measures.

Additionally SAF/MG 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. Services and deliverables shall include three (3) A&AS categories: management and professional services; studies, analyses, and evaluations; and engineering and technical expertise.

These services shall not include inherently governmental functions as discussed in FAR Subpart 7.5, “Inherently Governmental Functions”.

2. REQUIRED SERVICES/SUPPORT

To accomplish the scope of work defined within this Performance Work Statement (PWS), the Contractor must be familiar with the content and application of the applicable documents identified in Appendix I (Attachments and Applicable Documents). These applicable documents provide amplifying information relevant to Air Force Policy and to the performance of this PWS. Tasks to be performed in support of this PWS include work within the following areas: Information Assurance; Information Management;

Requirements Development; Enterprise Architecture; Operational Support Architecture; and Network Web-Based Support. In support of this mission, SAF/MG requires expert services across a range of capabilities to include:

2.1 Management Support

2.1.1 The Contractor shall provide a program management capability to manage the basic indefinite delivery/indefinite quantity (ID/IQ) contract and all awarded Task Orders. The Contractor shall provide deliverables in this PWS and issued task order. The Contractor shall use project management tools compatible with Microsoft (MS) Project© to assist in developing project schedules with resource loading and critical path management.

2.1.2 The Contractor shall provide management and oversight of all activities performed by Contractor personnel, including subcontractors, to ensure the accomplishment of timely and effective support, performed in accordance with the requirements contained in the PWS. This support includes Defense Business System (DBS) Information Technology (IT) Governance support and associated technical assistance.

2.1.3 The Contractor shall host, facilitate and orchestrate meetings ranging from high level AF executive governance to meetings focused on project efforts. The Contractor shall develop recommended meeting agendas with meeting objectives, administer meetings, develop presentations, prepare, set-up and facilitate discussions, provide post-event minutes and summaries to include actions items.

2.1.4 The Contractor shall support the drafting and coordination of staff packages; the creation of issue/point papers, reports, publications, and other documents; and build and present briefings.

2.1.5 The Contractor shall respond to Contracting Officer (CO) or Program Manager (PM) requests in a timely manner as directed by either. The Contractor shall notify the CO of direction received from Government personnel that the Contractor considers outside the scope of the basic PWS, or any awarded Task Order requirements prior to performing the work.

2.2 Business Capability Acquisition Cycle (BCAC)

The Contractor shall provide expert support in software development methodology to the Air Force BMA activities to document DBS requirements in accordance with the most recent DODI 5000.75, AFMAN 63-144, and standard enterprise architecture approaches such as Business Process Modeling Notation (BPMN version 2), 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.

2.2.1 The Contractor shall provide review of Air Force Problem Statements and for Problem Statements submitted from other Services in accordance with OSD policy. Additionally, the Contractor shall review BCAC developed products (e.g., Phase 2 artifacts) that are developed outside of SAF/MG’s oversight, submitted by functionals for compliance with BCAC (AFMAN 63-144). The Contractor shall provide expertise in BCAC methodology to mature guidance and reference materials, training materials, and alignment with related DoD and Air Force Policy and Guidance. The Contractor shall also maintain the SAF/MG Integrated Master Schedule of all transformation initiatives/projects being led or supported by SAF/MG. The Contractor shall consolidate project schedules provide weekly updates.

2.2.2 The Contractor shall provide expertise in facilitating multi-functional teams in documenting requirements for enterprise level IT capability. The Contractor shall support the AF Functional leads through the facilitation of workshops which provides the contextual modeling content capturing 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.

2.2.3 The Contractor shall support projects executing Phase 3 of BCAC through facilitation of workshops to derive IT Functional Requirements (ITFRs) and Information Assets (IAs) in accordance with BCAC Phase 2 processes. In addition, facilitate the development of Alternative Solution Approaches in accordance with AFMAN 63-144.

2.2.4 The Contractor shall support projects executing Phase 4 of BCAC through facilitation of workshops to define Requirements Modeling that result in detailed functional requirements and detailed information requirements in accordance with AFMAN 63-144.

2.2.5 The Contractor shall facilitate workshops that capture project process data and assist project leads with all pre-event, event, and post-event work. This includes scheduling meetings and facilities, drafting correspondence, gathering data, documenting all event work, drafting presentations, and facilitation of working group discussions, and capturing minutes and action items.

2.2.6 The Contractor shall facilitate, host and support sponsored BMA Data Management

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, and COI SharePoint site support. The Contractor shall analyze and provide recommendations for harmonization of COI deliverables, including vocabularies, 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.

2.3 BMA Chief Data Officer

2.3.1 The Contractor shall provide support and expertise in data management and data architecture, system engineering, and software engineering. This will include skills in data analysis, business intelligence, project management, business process improvement, market research, data migration methods (including cloud computing), web services environments, and enterprise security models.

2.3.2 The Contractor shall analyze and advise development of requirements, plan, design, and execution of data solutions (including infrastructure) for data warehousing/data sharing environments, to include ‘federated’ service oriented architectures for the entire business enterprise. The Contractor shall support synergizing data solutions with IT requirements management products for new initiatives to include data modeling.

2.3.3 The Contractor shall analyze and advise on common factors and common issues between data environments in multiple functional lanes, to include logistics, acquisition, human resource management, and financial management.

2.4 Enterprise Architecture

2.4.1 The Contractor shall provide Enterprise Data expertise support to include skills in the application of data architecture, data warehousing, data migration methods (including cloud computing), web services environments, data analytics, protocols and development methods to enterprise data governance, IT security models, design and run time discovery, architectural alignment, reuse, streamlined development, and authorization /access.

2.4.2 The Contractor shall analyze and advise on DBS architectures for AF business capabilities related to the Air Force BMA and DoD Business Enterprise Architecture (BEA). The Contractor shall provide technical leadership and training in data architecture and support for all Air Force vocabulary and data activities, and eXtensible Markup Language (XML) development support for BCAC projects.

2.4.3 The Contractor shall provide system development and sustainment expertise/support to develop and sustain the Enterprise Architecture Environment (EAE) supporting Air Force BMA DBS portfolio management processes. AF EAE, initially deployed in September 2016, provides seamless integration of OSD Integrated Business Framework Data Alignment Panel (IBF-DAP, InQuisient based solution), Air Force Architecture Resources (AFAR, Microsoft SharePoint based solution) and Air Force Information Technology Investment Portfolio System (ITIPS, Oracle Primavera Portfolio Management based solution).

2.5 Management Tools Support

2.5.1 The Contractor shall provide process modeling tools and data capture capability for documenting required deliverables in accordance with AFMAN 63-144 (BCAC). Products will be compatible with Air Force Business Enterprise Architecture process documentation.

Products will be compatible with Visio, or other process mapping tools defined in individual task orders.

2.5.2 The Contractor shall provide data analytics and analysis support for initiatives/projects being led or supported by SAF/MG.

2.5.3 The Contractor shall develop templates and reference materiel to help standardize and facilitate BCAC project management, chartering through the execution of projects.

2.6 Systems Engineering Support

2.6.1 The Contractor shall provide support in Development and Maintenance of Target Baseline (TB) as released the AF Target Baseline mandatory compliance document. However, as future needs for Information Technology (IT) capabilities are identified, there are situations where the new capability is not addressed in the existing lists of Scenarios and Technical Profiles. The Contractor shall provide engineering reviews of the 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 needed. The team of IT system engineers shall maintain the library of “living” Scenarios and TPs and assist support publishing of TB documents.

2.6.2 The Contractor shall provide management support to the Air Force Chief Information Officer (CIO) and Chief Technology Officer (CTO) to support Target, Implementation and Operational Baseline activities. Responsibilities include managing the workflow process to collect functional requirements from different Air Force functional groups, conducting weekly working group meetings, providing updates to the Air Force Chief Technology Officer (CTO) to support decision-making, conducting Security Control Review of all TPs, maintaining all TB documents on a Target Baseline SharePoint site, and providing training to new CTO and Chief Data Officer (CDO).

2.7 Project Studies and Analysis

2.7.1 The Contractor shall provide the skill sets to support analysis of business system architecture environments that would include planning for governance, structure, standards and integration.

2.7.2 The Contractor shall provide technical expertise for conducting pilot projects to inform and document engineering architecture target and implementation baselines for supporting business system IT. This includes 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.

2.8 Period of Performance. See Schedule

3. GENERAL INFORMATION

3.1 The Contractor shall provide the required number of personnel with a DoD TOP SECRET clearance in accordance with paragraph 3.5, interim clearances are not acceptable

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

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

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

3.4 Place of Performance. The work to be performed shall principally be in the National Capitol

Region (NCR) and at the contractor’s off-site facility with 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 may establish teleworking procedures for periods when Government facilities are not available. The government will have "hot benches" for Contractor use when necessary and available.

3.5 Security Requirements. All Contractor personnel must have at minum a valid SECRET security clearance, or higher, prior to being issued a Common Access Card (CAC). There is one exception that pertains to Contractor personnel with interim security clearance. Fingerprints must be complete, favorable and on file for validation by 11th Wing Information Protection office. The Contractor personnel must have a SECRET security clearance prior to performance on a Task Order if they require a SAF/MG-sponsored government e-mail. 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 Secret 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/MG. Contractor shall complete necessary documentation for sub-contractor(s) associated with this TO.

The Contractor Program Manager shall have a valid TOP SECRET security clearance.

The Contractor’s facility identified in Block 6 in the DD Form 254 shall be cleared as a Top Secret facility at time of proposal. Contractor facility Secret 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/MG. “Personnel” Secret clearance is different from “Facility” Secret clearance.

3.6 The Contractor employees shall clearly identify themselves as “contractors” at all times, in all communications and representations, including in the workplace, at meetings, in conversations, telecommunications, mail, electronic mail (e-mail), and faxes, whether with Government personnel, other contractor personnel, or with the public.

3.7 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 the execution of this PWS.

3.8 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 employee’s sign an Organizational Conflict of Interest and Non-Disclosure Agreement are in place prior to starting any work on this contract.

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

3.10 Quality Control Plan. The Contractor shall provide Quality Control Plan at the contract kick-off meeting and maintain currency throughout the contract period of performance.

3.11 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).

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

3.13 Government Purpose Data Rights. The Government shall have Government purpose 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 internally, reproduce, prepare derivative works, in any manner and for Government purpose use.

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

3.14.1 Invoices shall reflect the appropriate period of performance for when work was performed. Travel invoices shall include receipts.

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

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

3.15.1 In-Processing

3.15.1.1 Send request for employees to the COR.

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

3.15.1.3 If a CAC is required, Contractor shall provide necessary information for SAF/MG to fill out and submit the paperwork. SAF/MG will notify employees when their paperwork is ready for the employee to pick up and take to the nearest facility authorized to issue their CAC.

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

3.15.2 Out-Processing. If Contractor employee was issued a CAC, Contractor employees shall turn in their CAC to the COR prior to their departure.

3.16 Contractor Manpower Reporting Application (CMRA). The Contractor shall adhere to Section 8108 of Public Law 112-10 of the Department of Defense and Full Year Continuing Appropriations Act, 2011. 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. While inputs may be reported any time during the FY, 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.

3.17 Transition Services. The Contractor shall perform transition in and transition out services. 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.

3.17.1 Transition-In Services. A Transition-In Plan shall be submitted along with the

Contractor’s written technical Proposal in response to each task order solicitation and shall identify key points of contact (POC) for liaison between the Government, and the prime Contractor to ensure an orderly transition. Transition-in services shall occur from start date of awarded task order and the duration of the transition-in period shall not exceed 60 days after the contract start date. Throughout the transition period the Contractor shall assume responsibility for all services required for contract performance.

The Contractor shall work closely with the transitioning-out Contractor (until the transitioning-out Contractor’s task order expires), Projects Leads, Government Program Manager and the COR to ensure uninterrupted contract support.

3.17.2 Transition-Out Services. The Contractor’s firm may be succeeded by a different firm at the end of the task order’s period of performance. The transition-out period shall begin 60 days before the end of the period of performance.

The Contractor shall cooperate fully with the Government and the succeeding Contractor to include:

a) Permitting employees to be interviewed for possible employment by a succeeding

Contractor(s).

b) Releasing any employee who chooses to be employed by a succeeding Contractor.

c) Orienting assigned employees of the succeeding Contractor during the last 60 days of the period of this contract if so directed by the Contracting Officer. The Government shall make available to such employees existing GFE such as desks, chairs, telephones, and other normal office equipment and office supplies during the orientation period.

3.18 In-Progress Reviews. The Contractor shall support monthly status reviews to SAF/MG on contract performance and the status and progress of initiatives. The method of presentation shall be in the Contractor’s management plan. The objectives of these reviews are to track progress of the project, present ideas for improvement, and identify and resolve issues

4. DELIVERABLES AND REPORTING. The Contractor shall provide deliverables as specified in the ID/IQ contract and all Task Orders in accordance with Table 2, Deliverable Table. If a deliverable due date falls on a weekend or holiday, the contractor shall submit the deliverable on the last work day prior to the due date. The Contractor shall maintain a collaborative site where all deliverables are posted for access by Government and Contractor personnel. The Government COR and Task Order lead(s) shall be notified upon all deliverable(s) that are made available for review/approval. Access to Task Order folders shall be limited to those Contractor and Government personnel assigned to the particular Task Order and SAF/MG management.

4.1 Monthly Status Report. The Contractor shall provide a Monthly Status Report (MSR) to include all projects on all task orders. The report shall be prepared for each task order under the IDIQ contract. Each MSR shall summarize the efforts on the contract from the previous month and addressing any issues, Contractor employees performing work on-site compared to off-site performance, anticipated actions for SAF/MG sponsored e-mail accounts or Common Access Cards (CAC), and notification of any employee changes since the last report and anticipated changes within the next 30 calendar days. The MSR shall contain an updated Staffing Plan, Project Management Plan, identify subcontractors and their associated work, and contain a travel expense report.

4.2 Program Management Plan (PMP). The Contractor shall provide a Project Management Plan within 15 business days after contract award and monthly thereafter to be delivered with the MSR. The PMP shall include, but not be limited to, the following:

- Status of current and planned tasks and subtasks

- Overall project schedule(s) to included major activities (showing task dependencies and interrelationships) and deliverables shown in tracking gantt format

- Contractors organization structure relevant to this contract and each task order to include sub-contractors performing work

- Contractor personnel assignments and duration (Staffing Plan)

- Updated Deliverable Status/Schedule (based on solution)

- Contingency Plans (where appropriate),

- Automated Tools, Techniques, and Methods

The contractor shall keep the PMP and integrated master schedule up-to-date, keep it accessible electronically at any time, and be prepared to brief any PMP content to the Government at short notice (within 24 hours). The PMP shall be used as a foundation for the Monthly Status Report.

4.3 Problem Notification Reports. The Contractor shall provide a Problem Notification Report within two business days after the Contractor’s discovery of the issue(s) relative to the IDIQ or for any specific task order(s).

4.4 Travel Expense Report. The Contractor shall provide a Travel Expense Report monthly to be delivered with the MSR.

4.5 Technical Reports/Ad-Hoc Reports. The Contractor shall provide technical reports and/or Ad-

Hoc Reports which may include; status reports, meeting agendas, post-event minutes, point papers, publications, and reports/artifacts associated with AFMAN 63-144, as required for all task orders.

4.6 Transition-Out Plan. The Contractor shall provide a Transition-Out Plan addressing all active task orders not later than ninety (90) days prior to contract expiration.

4.7 Annual COR Report that includes dates of required contractor training to include the following:

Information Assurance, and Records Management.

5. SERVICES SUMMARY

5.1 Purpose. The Services Summary (SS) lists performance objectives for the required services the Government will surveil. The absence of any contract requirement from the SS shall not detract from its enforceability nor limit the rights or remedies of the Government under any other provision of the contract including the clauses entitled “Inspection of Services” or “Inspection” or “Default” in Section E and Section I of the contract.

5.2 Components. The SS states the performance objective (required service), and threshold

(performance standard, accept and reject points (if applicable)) in either a qualitative or quantitative fashion for each critical success factor.

5.3 Right To Surveil. The Government reserves the right to surveil all services and requirements called for in this PWS IAW FAR Part 52.246-4 to determine whether the Contractor is meeting performance objectives and goals. The following SS reflects the objectives and thresholds used to track Contractor performance for task orders awarded against the basic ID/IQ contract.

5.4 Penality. The reduction of fixed fee will be calculated in accordance with the Attachment A

(Service Summary) and Attachment B (CEM Fee Schedule). Attachment B – CEM Fee Schedule will be completed by the Government prior to award and will be incorporated into the contract.

Attachment B is an example showing the calculations based on withholding 7.5% of the fixed fee until all contractual obligations and deliverable are received from the Contractor then an invoice will be submitted to the Government for that withheld fee.

5.5 Incentive/ Remedy Process. This paragraph describes the process for evaluating the

Contractor’s performance and the assessment of incentives or penalty based on performance requirements defined in the Service Summary. Contracting Officer’s Representatives (COR) advised and reports on recorded contractor performance to the Contracting Officer (CO). The

COR will monitor the Contractor’s performance and maintain written records of the Contractor’s performance to ensure a fair and accurate evaluation based on the Performance Thresholds.

Table 1 Services Summary Table Performance Objective PWS

Reference Performance Standard Incentive/Remedy

Provide qualified people at Contract or Task Order start

2.1 - 2.7 and 3.5

Performance is acceptable when: Qualified personnel are on the job at contract start, unless previously negotiated by the CO.

Performance of this objective will be annotated in the Contractor Performance Assessment Reporting System (CPARS) Rating.

Failure to meet the delivery date within 75% staffed on day 1 and 100% staffed within 5 days for Key Personnel, IAW, PWS will result in a reduction of the invoice for this period of performance as a 2% penalty. Once all personnel is met at 100% then the Contractor will request approval from the CO to invoice for the pentalty withheld.

Contractor Manpower Reporting Application

(CMRA)

3.16 100% data is accurate and on time not later than 31 October of each calendar year

NA

Develop and submit all required deliverables

2.1- 2.7 Performance is acceptable when:

a) 95% of deliverable requirements are met and received on time as stated in the contract

AND

b) critical information is accurate

Performance Assessment Reporting System (CPARS) Rating.

Effectively replaces/ substitutes personnel

2.1 - 2.7 Performance is acceptable when:

a) Resumes are submitted to the COR to ensure all candidates meet the minimum requirements of the Task Order. Vacancies filled with qualified personnel w/in 5 days, unless approved in writing or otherwise directed in advance by the CO, AND

b) there is no mission impact due to position vacancies or unqualified personnel.

Performance Assessment Reporting System (CPARS) Rating.

Failure to meet the delivery date within 5 days for Key Personnel and 8 days for all other Personnel will result in a reduction of the invoice for this period of performance as a 2% penalty.

Once all personnel is met at 100% then the Contractor will request approval from the CO to invoice for the pentalty withheld.

Labor CLIN Invoices and Travel CLIN Invoices are submitted timely, accurately and have receipts.

3.14 Performance is excellent

when 95% to 100% of invoices are timely and accurate.

Performance is very good when 90% to 94% of invoices are timely and accurate.

Performance is good when 85% to 89% of invoices are timely and accurate.

Performance is marginal when 80% to 84% of invoices are timely and accurate.

Performance is unsatisfactory when < 80% of invoices are timely and accurate.

Performance Assessment Reporting System (CPARS) Rating.

Failure to meet the delivery date by the 15th for Labor CLINwork from the prior month; and NLT 60 days for Travel CLIN will result in a reduction of the invoice for this period of performance as a 2% penalty. Once all CLIN Invoices and/or Travel CLINs are 100% complete then the Contractor will request approval from the CO to invoice for the pentalty withheld.

Comply with DD form 254 and PWS section

3.5 for TO requirements

3.5 Performance is acceptable

when no security violations occur for the contract period.

NA

Table 2: Deliverable Table Deliverable PWS

Reference Deliver to Due Date

Quality Control Plan 3.10 CO and

COR

At Kick Off

Organizational Conflict of Interest Mitigation Plan

3.8 CO and

COR

At Kick Off if needed

Organizational Conflict of Interest and Non- Disclosure Agreements

3.8 COR As required and before any work is started

Monthly Status Report 4.1 COR Monthly on the 15th Program Management Plan (PMP)

4.2 COR 15 business days after award and monthly

thereafter to be delivered with the MSR.

Problem Notification Reports

4.3 COR and

PM

Two business days after the Contractor’s discovery of the issue(s) relative to the IDIQ or for any specific task order(s).

Technical Reports/Ad-Hoc Reports.

4.5 COR and

PM

Within 5 working days of Government request.

Transition-Out Plan 4.6 COR, PM and CO

Not later than ninety (90) days prior to contract expiration.

Annual COR Report 4.7 COR 30 October yearly

6. GOVERNMENT FURNISHED PROPERTY

6.1 General Information. No Government Furnished Property (GFP) is anticipated for this Task

Order.

Monthly Status Report is accurate and timely

4.1 Performance is acceptable

when:

The Monthly Status Report is submitted not later than the 15th calendar day of the following month.

Performance of this objective will be annotated in the CPARS Rating.

Failure to meet the delivery date within 2 days will result in a reduction of the invoice for this period of performance as a 1% penalty. Contractor will request approval from the CO to invoice for the pentalty withheld.

Organizational Conflict of Interest and Non- Disclosure Agreements are in place for each contractor personnel prior to starting any work on this contract.

3.8 100% complete as required prior to start and provided via email to the

COR.

NA

Contractor complies with Quality Control Plan (QCP)

3.10 100% NA

6.2 Documents. The Government will furnish or make available to the Contractor any documentation/material deemed necessary to accomplish requirements of this Task Order.

6.3 Unclassified Area Network. Unclassified Network Account. As a SAF/MG Standard Operating

Procedure (SOP), the government will not issue a Contractor an unclassified network account unless absolutely necessary. If the Contractor requires an unclassified network account, the government will issue and provide a CAC. To receive a CAC and network access, the Contractor shall provide necessary information for SAF/MG to fill out and submit the paperwork. SAF/MG will notify employees when their paperwork is ready for the employee to pick up and take to the nearest facility authorized to issue their CAC. All Contractors are required to complete Initial Information Assurance Training before being given a network account and annually thereafter.

Training can be accessed at http://cdsetrain.dtic.mil/.

7. TRAVEL

The Contractor shall:

7.1 Attend meetings outside the (NCR) in support of the tasks defined herein to fulfill the requirements outlined on this TO.

7.2 Submit in (WAWF) any and all receipts for lodging, airfare, meals and ground transportation as attachments to the invoice.

7.3 Obtain COR approval in writing prior to conducting any travel outside the NCR. Any travel outside the NCR conducted without prior written COR approval will not be reimbursed. Verbal authorization shall not replace the requirement for written authorization.

7.4 The Government will only reimburse lodging, airfare, meals and ground transportation costs in accordance with FAR 31.205-46 and the current Joint Travel Regulation.

7.5 Local travel to attend meetings within the NCR shall not be reimbursed. When traveling outside the NCR, travel to attend meetings within the local city or base of assignment shall not be reimbursed.

http://cdsetrain.dtic.mil/

Appendix I – Labor Category Descriptions

Program Manager

Education/Experience: Bachelor’s degree or higher from an accredited institution. In addition, must have relevant experience managing diverse, technical support teams for a minimum of 3 years or a minimum of 3 years Program Management experience, with a minimum of three years’ experience in A&AS program management.

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 overseeing the operational planning, establishment, execution, and evaluation of a multifaceted program or project. Responsible for managing fiscal, operational, administrative and human resources related to the program. Serve as principal point of representation and liaison to contacting office and customer representatives on operational matters. Explain Government’s policies, procedures and goals the team members. Must have excellent verbal and written communication skill and capability to deal with management personnel, contract managers and customer representatives. Responsible for all contractual deliverables. 10 years of experience in managing large complex projects with demonstrated capability in the overall management of contracts of similar type or complexity. Four years of progressively responsible experience in a Govt. contracting environment.

Business Analyst 1, 2, 3

Education/ Experience: Relevant experience, including supervisory, project management experience, and facilitation expertise leading/working requirement definition for Information Technology projects.

Functional Responsibility: Works with Functional SMEs to understand and describe the “as-is” business processes. Capable to evaluate the current state and identify the areas of improvement.

Participates in workshops and captures Business Process Activities, Business Rules, Information Assets, IT Functional Requirements and Transformation Actions. Collaborates with SMEs to sanitize and finalize requirements. Documents requirements in the form of Scenarios and Use Cases. Assists in decomposition of IAs. Identify Measures of Effectiveness and Measures of Performance for Business Process Activities.

Schedule meetings, workshops and facilitates collaboration between different Functionals. Manages review and approval of deliverables.

Minimum Years of Experience:

Level Ph.D. Master’s Degree Bachelor’s Degree Associate Degree 3 5 7 9 11 2 3 5 7 9 1 1 3 5 7

Data Architect

Education/Experience: 3 years of experience working with AF/DoD and familiarity with DoDAF EA approach. And, 5+ years of experience in data analysis and data modeling.

Functional Responsibility: The architect will support harmonization of data standards and dictionaries through Community of Interest coordination, including vocabularies, roles and permissions, Authoritative Data Source, and development of Data Reference Models in defining requirements for business and IT solutions. Leads analysis and decomposition of IAs, create vocabularies, taxonomies and ontologies.

Capable to define relationship between IAs and develop Conceptual Model and DoDAF compliant DIV-

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

Data Scientist

Education/Experience: Master’s Degree in Computer Science, Statistics, Applied Math or related field, and 7+ years’ practical experience with SAS, ETL, data processing, database programming and data analytics. Extensive background in data mining and statistical analysis. Able to understand various data structures and common methods in data transformation. Excellent pattern recognition and predictive modeling skills.

Functional Responsibility: The Data Scientist is responsible to research and develop statistical learning models for data analysis, as well as collaborate with customers and steakholders to devise possible solutions. The Data Scientist keeps up-to-date with latest technology trends, communicates results and ideas to key decision makers, and implements new statistical or other mathematical methodologies as needed for specific models or analysis. Optimize joint development efforts through appropriate database use and project design

Management Analyst II

Education/Experience: 10 years of experience in project performance management and analysis.

Experience in analyzing legislative requirements and develop briefings for Senior Leaders. 5 years of Air Force or DoD domain knowledge.

Functional Responsibility: Evaluates existing business processes for efficiency, effectiveness, and improvement. Capable of leading Performance Management and Measurement activities for different process areas. Develop Performance Measures and Scorecards. Can author guidelines and manuals for process improvement. Develop briefings for Senior Leaders showing analysis of different alternatives.

Support SDDP compliance requirements.

Management Analyst III

Education/Experience: 10 years of experience in project performance management and analysis.

Experience in analyzing legislative requirements and develop briefings for Senior Leaders.

Functional Responsibility: Evaluates existing business processes for efficiency, effectiveness, and improvement. Capable of leading Performance Management and Measurement activities for different process areas. Develop Performance Measures and Scorecards. Can author guidelines and manuals for process improvement. Develop briefings for Senior Leaders showing analysis of different alternatives.

Support SDDP compliance requirements.

Management Consultant

Education/Experience: 12 years of experience in related field, including supervisory and project managment. Experienced in developing and deploying complex IT systems. Experienced in BPMN, DoDAF, Zachmann and other related standards.

Functional Responsibility: Possesses expert level knowledge in BCAC and lead contextual and system requirement modeling workshops and activities with stakeholders. Possess good knowledge of different types of IT solutions available in the market and able to map them to solve business problems. Leads market research and evaluates COTS and GOTS to implement BPR changes improvement. Capable of planning and executing workshops to lead the team through the BPR activities. Evaluates existing systems and user needs to analyze, design, recommend, and implement system changes. Provides in-depth knowledge and subject-matter expertise to help solve complex business problems. Senior Consultants can advise at the equivalent of very senior level corporate enterprise leadership.

Principal Enterprise Architect

Education/Experience: Bachelor’s degree (minimal requirement)/Substantial, with 6 years of 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, etc.), 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.

Principal Systems Engineer