Attachment_3_B-CLM_PWS_Projects.pdf

Attachment 3

PERFORMANCE WORK STATEMENT

BUSINESS CAPABILITY LIFECYCLE MANAGEMENT (B-CLM)

For

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

FA7014-18-R-5004

Date: 19 March 2018

1. INTRODUCTION

1.1 General. This is a non-personal services contract to provide Business Capability Lifecycle

Management (B-CLM) Advisory and Assistance services for the United States Air Force-wide business management 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) by leveraging existing technologies owned by the Air Force, streamlining and standardizing business processes across the Air Force, and developing integrated solutions that are achievable in a constrained fiscal environment. The Air Force has a requirement for business system information system management 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 is 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. Contractor experience outside of the Defense Department in accomplishing relevant work as described in this PWS provides the

Government innovative approaches by leveraging private sector and government best practices for enhancing execution.

1.3 Objective. The objective of this requirement is to obtain contractor support for an Indefinite

Delivery/Indefinite Quantity (ID/IQ) contract 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: management and professional services; 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 II

(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. 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. The Contractor shall develop and maintain a project schedule for all transformation initiatives/projects being led or supported by SAF/MG.

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.

2.1.3 The Contractor shall host, facilitate and orchestrate 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) Projects

2.2.1 The Contractor shall provide expert support to Air Force BCAC projects to document defense business system capability requirements in accordance with the most recent DODI 5000.75 and

AFMAN 63-144. An understanding of the application of these methods to large scale enterprise business transformations (e.g., global companies) is critical. Additionally, the

Contractor shall collaborate with other Government Contractors providing technical support to the Government for BCAC efforts.

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 BCAC Capability Need Identification Phase (Phase 1) - The Contractor shall provide support to projects executing BCAC Phase 1 through facilitation of workshops “to establish a clear understanding of needed business capabilities so that the functional sponsor and Air Force decision authority can decide to invest time and resources into investigating business solutions”

(DODI 5000.75, paragraph 4.2.a). The contractor shall provide support to generate the required information per DODI 5000.75, paragraph 4.2.a.(3) for Solution Analysis Authority to Proceed

(ATP) per (DODI 5000.75, paragraph 4.2.a.(2).

2.2.4 BCAC Business Solution Analysis Phase (Phase 2) - The Contractor shall provide support to projects executing BCAC Phase 2 through facilitation of workshops to “determine the high-level business processes supporting the future capabilities so that the functional sponsor and decision authority can maximize use of existing business solutions and minimize creation of requirements that can only be satisfied by a business system” per DODI 5000.75, paragraph

4.2.b. The contractor shall provide support to generate required information per DODI

5000.75, paragraph 4.2.b.(3) for Functional Requirements ATP per DODI 5000.75, paragraph

4.2.b.(2).

2.2.5 BCAC Business System Functional Requirements & Acquisition Planning Phase (Phase 3) -

The Contractor shall provide support to projects executing BCAC Phase 3 through facilitation of workshops to “establish the acquisition strategy that will support functional requirements” per DODI 5000.75, paragraph 4.2.c. The contractor shall provide support to generate required information per DODI 5000.75, paragraph 4.2.c. (3) for Acquisition ATP per DODI 5000.75, paragraph 4.2.c. (2).

2.2.6 BCAC Acquisition, Testing and Deployment Phase (Phase 4) - The Contractor shall provide support to projects executing BCAC Phase 4 through facilitation of workshops to “achieve organizational change through business process changes and delivery of the supporting business system, with minimal customization” per DODI 5000.75, paragraph 4.2.d. The contractor shall provide support to generate required information per DODI 5000.75, paragraph

4.2.d.(5) for Limited Deployment ATP, Full Deployment ATP and Capability Support ATP per

DODI 5000.75, paragraph 4.2.d.(2), 4.2.d.(3), 4.2.d.(4), respectively.

2.2.7 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.3 Management Tools Support

The Contractor shall provide/utilize process modeling tools and data capture capability for documenting required deliverables in accordance with AFMAN 63-144 (BCAC). Products will be in accordance compatible with Air Force Business Enterprise Architecture process documentation and Business Process Modeling Notation [BPMN] 2.0 standard. Products will be compatible with mapping tools defined in individual task orders.

2.4 Systems Engineering Support

2.4.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.4.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.5 Period of Performance. See Schedule

3. GENERAL INFORMATION

3.1 The Contractor shall provide the required number of personnel with a DoD SECRET clearance in accordance with paragraph 3.5, interim clearances are 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) 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 support and participate in meetings, work sessions, or other temporary duties at Government facilities as necessary. 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. The work to be performed for Project Task Orders may require work to be performed at Government locations.

3.5 Security Requirements. All Contractor personnel must have at minimum 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’s facility identified in Block 6 in the DD Form 254 shall be cleared as a 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 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 a Non-Disclosure Agreement are in place prior to starting any work on this contract.

3.8 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. The Post Award Conference/Periodic Progress Meetings for the

IDIQ will be held in the NCR. The locations of the Task Order Post Award Conferences and

Periodic Progress Meetings will be defined in each Task Order. These meetings shall be at no additional cost to the Government.

3.9 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.10 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.11 Key Personnel. The Government considers the Program Manager, in addition to those identified in Appendix I, Labor Category Descriptions as key personnel. 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.12 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.13 Invoices. Invoices shall conform to the requirements stated in the contract. Additionally, the following requirements apply:

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

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

3.14 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.14.1 In-Processing

3.14.1.1 Send request for employees to the COR.

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

3.14.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.14.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.14.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.15 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.16 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.16.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.16.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.17 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 1, 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 address 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

- 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. Each Task Order will include a delivery table specifying the deliverables for that particular Task Order.

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. The Contractor shall provide annual COR report that includes dates of required training to include the following: Information Assurance, and Records Management.

4.8 Small Business Participation Plan. The Contractor shall provide a small business subcontracting plan that addresses how the contractor plans to meet the 20% small business participation goal.

Table 1: 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).

Travel Expense Report 4.4 COR and

PM

No later than 5 calendar days after travel

Technical Reports/Ad-

Hoc Reports (Identified per Task Order).

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

Small Business

Participation Plan

4.8 COR, PM

and CO

Due not later than 30 days after the start of the

IDIQ contract period of performance.

Small Business

Participation Report

4.8 COR, PM

and CO

Due 6 months after the start of the IDIQ contract period of performance; updated semi-annually thereafter. eCMRA shall be updated annually and report provided to the CO.

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 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 Services Summary. Contracting Officer’s Representatives (COR) advised and reports on recorded contractor performance will be provided 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. Performance will be documented throughout contract and feedback will be provided for work accomplished. Final assessments will be documented in a CPARs rating.

Table 2: Services Summary Table

Performance Objective PWS

Reference

Performance Standard Incentive/Remedy

Provide qualified people at Contract or Task Order start

2.1 - 2.4 and 3.5

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

Failure to meet the requirement for qualified personnel will result in the invoice being withheld until qualified personnel are hired.

Performance of this objective will significantly affect the Contractor

Performance Assessment Reporting

System (CPARS) Rating.

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.4 Performance is acceptable when:

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

AND

b) critical information is accurate

Failure to meet the requirement will result in re-performance at the expense of the contractor OR after three incidences in a 6 month period will result in the invoice for the period being withheld until deliverable requirements are met.

significantly affect the (CPARS) rating.

Effectively replaces/ substitutes personnel

2.1 - 2.4 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 for key personnel and

14 days for all other personnel, 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.

Failure to meet the delivery date within 14 days for personnel, the invoice for that month, the amount apportioned for that position will be withheld until the vacancy is filled.

Labor CLIN Invoices and

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

3.14 Performance is excellent

when all of invoices are timely and accurate.

Failure to meet this requirement more than three times per year will result in a 1% invoice withhold

Comply with DD form 254 and PWS section 3.5 for

TO requirements

3.5 Performance is acceptable

when the contractor maintains a SECRET facility clearance.

Failure to maintain a SECRET facility clearances will result in termination of the contract

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.

Failure to meet the delivery date more than three times will negatively affect the CPARS rating.

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% Failure to consistently comply with the QCP will result in a 1% invoice withhold

Small Business

Participation Plan

4.8 Performance is acceptable

when it meets the 20% SB participation goal.

Performance of this objective will

Failure to meet the required 20% will result in a CPARs rating of less than

Satisfactory in the SB category.

6. GOVERNMENT FURNISHED PROPERTY

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

Order.

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.

Metrics 2.2 Performance is acceptable when deliverable BCAC products are received and determined acceptable to the

Government within specific timeline per Task Order.

Required BCAC documentation is deemed complete and comprehensive by the Government.

- Facilitate multi-functional teams to successfully reach consensus/agreements and develop artifacts as required for each BCAC phase.

- Successfully obtain approval with minimum reworks on BCAC artifacts for each phase that contractors support.

Failure to meet the requirement will result in re-performance at the expense of the contractor OR after three incidences in a 6 month period will result in the invoice for that period being withheld.

http://cdsetrain.dtic.mil/

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.

Appendix I

* Considered to be Key personnel

* 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 Description: Works with Functional SMEs to understand 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. Enters and conducts analysis activities on requirements. 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 Master’s Degree Bachelor’s Degree Associate Degree

3 7 9 11

2 5 7 9

1 3 5 7

* Project Manager

Education/Experience: Bachelor’s or Masters IT College Degree preferred. 5 years of experience managing projects. 3 years of hands on experience in developing and managing project schedules using

MS Project. Experience in developing resource utilization matrix and management briefings.

Functional Description: Manage individual project’s scope, schedule and resources. Develop schedule using MS Project and maintain that from inception to delivery. Create Project Charter, Resource Plan and

Resource Utilization matrix. Manage risks and issues and highlight them to management. Develop weekly status report for individual projects and add milestone charts showing current status, upcoming activities and action items. Analyze multiple projects to develop a matrix to help management understand current resource utilization and predict upcoming requirements.

Subject Matter Expert II

Education/Experience: Bachelor’s or Masters IT College Degree preferred/Demonstrable 3-5 year experience in IT requirements development (minimal requirement)/Substantial relevant experience.

Functional Description: Provides technical expertise in using specialized applications in the specific area. Capable of understanding how IT requirements use Information Assets to complement identified

BPR actions. Knowledge in BCAC and leading requirements modeling activities with Functional SMEs and stakeholders.

Subject Matter Expert III

Education/Experience: Masters IT College Degree preferred/Demonstrable 5+ years experience in IT requirements development (minimal requirement)/Substantial relevant experience.

Functional Description: Provides technical expertise in using specialized applications in the specific area. Capable of understanding how IT requirements use Information Assets to complement identified

BPR actions. Expert level of knowledge in Enterprise Resource Planning system(s). Expert level knowledge in leading requirements modeling activities with Functional SMEs and stakeholders.

* Systems Analyst

Education/Experience: A Bachelor’s or Masters IT College Degree preferred/Demonstrable minimum of 3 years experience in IT requirements from process development to system deployment/Substantial relevant experience. Has an expert level of knowledge and experience with ERPS.

Functional Description: Comprehends customer’s business process improvement requirements and translate them into IT requirement. Develop detailed IT Functional, Technical and Lifecycle requirements. Analyzes IT Requirements to develop Course of Action (CoA) Evaluation criteria.

Develop questionnaire from CoA Evaluation criteria to facilitate market research. Analyze COTS and

GOTS and score them against different CoA criteria. Decompose Information Assets and develop Data

Models. Works with different SMEs to understand and articulate System to System interfacing, data exchange requirements, web services requirements and capture them in Service Reference Model.

Appendix II – ATTACHMENTS AND APPLICABLE DOCUMENTS

Attachment 1 - DODI 5000.75, Business Systems Requirements and Acquisition

Attachment 2 - DoD 5220.22M, National Industrial Security Program Operating Manual, Executive order 12356, Classified National Security Information

Attachment 3 - Air Force Manual 63-144, Defense Business System Life Cycle Management

Attachment 4 - Handbook for Data Reference/Information Modeling in the Air Force (AF) Business

Mission Area (AF BMA): This handbook provides an overview of AF BMA Community of Interest

(COI) activities and describes how activities are linked together and outlines AF BMA COI procedures for delivery of Information Models.

Attachment 5 – AF Business Capability Acquisition Cycle (BCAC) Amplifying Guidance