Pre Solicitation BETA PWS 24 Oct 11 PDF.pdf

PDF 147 KB Posted

Attached to
SAF/US(M)S Business/Mission Transformation Federal contract opportunity
Solicitation number
FA7014-12-R-1002
Issued by
Department of the Air Force Headquarters District Washington

About this file

DRAFT Pre Solicitation BETA PWS

View the file

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

PERFORMANCE WORK STATEMENT

FOR

BUSINESS, ENGINEERING & TECHNICAL ASSISTANCE (BETA)

24 October 2011

1. Project Title: Engineering and Technical Expertise for United States Air Force wide Improvement

Projects.

2. Objective

The overarching objective of this contract for subject requirement is to obtain advisory and assistance services (A&AS) for the Office of the Under Secretary of the Air Force; Director, Business

Transformation and Deputy Chief Management Officer (SAF/US(M)). SAF/US(M) is responsible for business/mission transformation seeking to make the USAF organize, train and equip responsibilities more effective for our warfighters through the development and adoption of more efficient business/mission practices. Additionally SAF/US(M) is responsible for the effective management of the Air Force efficiencies/savings initiatives.

In order to deliver these activities, SAF/US(M) is organized into two directorates, Transformation and

Transformation Outreach and Support. This contract will principally provide expert support services for the Transformation Directorate. The Transformation Directorate provides strategic planning, performance and project management, performance measurement and monitoring for Agile Combat

Support/business transformation and efficiency management activities. This effort includes the development of new business practices that become institutionalized through implementation of highly visible projects, through the use of new methods derived from industry benchmarking, across the Air Staff and MAJCOMs. SAF/US(M) adopts and adapts many of these industry best practices and supports their implementation by providing industry expertise to support our partner teams put the new methods into practice.

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

a. Business Process Re-engineering encompassing a range of skills such as Business Process

Modeling Notation (BPMN), DoDAF and Zachmann enterprise architecture, contextual modeling, and derivative use case development. An understanding of the application of these skills to Air Force business processes, which is documented in the draft Services Development and Delivery Process (SDDP) is critical.

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

b. Program and Efficiency Management Expertise to both manage assigned projects as well as to support partner teams in the development and delivery against their projects that SAF/US(M) supports. Also includes expertise and support on efficiency tracking, performance management tracking and assisting with internal and external reporting. Key expertise and experience include program risk analysis, reporting and mitigation.

Planning Factor: Efficiency program risk management analysis and efficiency management support will be required.

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

/access. Detailed understanding of the Air Force COI Primer, data tools and pilot projects are critical capabilities.

Planning Factor: Ontology practice technical leadership and support for all Air Force COI activities, XML development support for at least five equivalent concurrent projects. This includes support of four core activities for configuration management, policy, guidance, and integration of ontology as well as surge capability to support up to eight concurrent COI activities.

d. Technical expertise for pilot projects to inform and document target and implementation baselines, specifically web expertise as applied to web standards, protocols and applications, ERPs, and legacy data transition to future state environments. Expert knowledge of target security model, platform services and AF pilot service development activities are critical capabilities.

Planning Factor: Expert support for ERPs and at least three Program designs/architectures including target and implementation baselines. Piloting expertise for at least three projects including the EA repository, DRS.

e. Performance Management Measurement commercial best practices skills to both support the development of Air Force processes and policies and also to provide expert skills to put them into practice. Performance Management Measurement must be aligned to the SDDP, enterprise architecture and governance processes effectively aligning outcome/capability based objectives, return on investment criteria, functional objectives and program management performance measures. Metrics generation and alignment is a key component and skill requirement.

Planning Factor: Application of commercial best practices technique to major AF IT intiative.

Support change management actions to replicate across AF programs.

f. Analysis of Alternatives analytical expertise to provide independently developed and recommended approaches for the delivery of significant Agile Combat Support initiatives, specifically for logistic transformation and achieving clean audit. Independent experience with various ERPs and application to Air Force programs are critical skills.

Planning Factor: Provide AoA independent assessment in support of logistic transformation program plus two three-month projects.

4. Performance Requirements: In general, the Contractor shall provide staff support across all performance requirements in orders to include:

(a) Support government oversight of programs, processes, operations, exercises and other activities;

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

(c) Provide expert support to government personnel at various forums and meetings;

(d) Support the drafting and coordination of staff packages for review and approval;

(e) Support the creation of issue/point papers, reports, publications, and other documents;

(f) Build and present briefings;

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

(h) Provide personnel with a DoD SECRET clearance and selectpersonnel with a DoD TOP

SECRET clearance.

5. Phase-Out: As required, 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.

6. Performance Objectives

PERFORMANCE OBJECTIVE REFERENCE PERFORMANCE MEASURE

Timely and Quality Deliverables Contractor shall submit deliverables, reports, invoices, and other required documents stated in the PWS. on time 95% of the time. Reports shall be technically accurate and comprehensive.

Other 5% submitted within 5 days of requirement.

Noted discrepancies must be fixed within 5 days of notification from Quality Assurance Personnel.

Quality

Contractor shall provide sound, comprehensive, professional, and articulate analyses and recommendations in support of government decision-making.

Responsiveness

Contractor shall provide appropriate responses to fulfill task requirements.

Timeliness

Contractor's responses shall support timely decision making.

7. Deliverables

The following specific deliverables apply to contract. Electronic delivery and contractor format is acceptable. The Contractor shall combine monthly updates for the Management Plan, Progress Report, and Cost Report; and provide them as one submittal.

DELIVERABLE REFERENCE DELIVERY DATE

Management Plan 7.1 Initial : Concurrent with

Contract Proposal

Updates: Monthly by the 30th of each month

Progress Report 7.2 Initial: 30 days after Contract

Award

Updates: Monthly by the 30th of each month

Quality Assurance Report 7.3 Semi-Annually: Beginning 6 months after Contract Award

Master Integrator Subcontracting

Report

7.4 Semi-Annually: Beginning 6

months after Contract Award

Cost Report 7.5 Initial : By the 10th of the next month after Contract Award

Updates: Monthly by the 10th of each month

Order Efficiency Assessment 7.6 To Be Determined based on

Contract Award Date

7.1 Management Plan

The Contractor shall provide a Management Plan to Quality Assurance Personnel identifying:

(a) How contractor employees are allocated against contract requirements; (b) Contractor employees performing work on-site compared to off-site performance and requirement for

SAF/US(M)- sponsored e-mail accounts, Pentagon badges, and Common Access Cards (CAC);

and (c) The applicable labor category and number of labor hours associated with each employee.

The contractor shall highlight any employee changes since the last report and anticipated changes within the next 30 days.

7.2 Progress Report

The Contractor shall provide a Monthly Progress Report to the COR (Contracting Officers

Representatives) summarizing its efforts on the contract from the previous month and addressing any issues.

7.3 Quality Assurance Report

The Contractor shall monitor team efforts to ensure maximum best value for the government and provide a semi-annual report to Quality Assurance Personnel. The report shall address the contractor’s assessment in meeting performance objectives and mitigation plans to correct any shortfalls.

7.4 Master Integrator Subcontractor Report

The Contractor shall provide a report semi-annually to the Contracting Officer on the contract showing the team member (subcontractor); size classification , i.e. small Business or large business; and dollar amount awarded.

7.5 Cost Report

The contractor shall provide the following cost data in a monthly report: (a) Total funds expended per item number; team member, i.e. company; employee; and associated labor category for subject contract.

This information shall be provided for the current month, cumulative to date for the current performance period, and cumulative for the overall contract, ( b) Percentage of total funding expended compared to amount obligated for the for the current performance period, and (c) Labor Usage (Burn)

Rate per employee. The contractor shall also project how long the remaining funds on the contract will support the current effort. The contractor shall meet with Quality Assurance Personnel monthly to review the cost/schedule status of subject contract and address any performance issues.

7.6 Contract Efficiency Assessment

During the life of subject contract, budget cuts may require reductions in Air Force contract services dollars. Budget cuts may apply across all SAF/US(M) contract services including subject contract.

Due to this possibility, the Air Force intends to use organizational and process efficiencies to fund its transformation of key capabilities. This task enlists input from the contractor to assess the efficiency of its own work and provide recommendations on streamlining the cost of subject contract. In efforts towards this goal, the contractor shall assess the requirements being performed under the contract and identify potential efficiencies. The contractor shall deliver the report to the Quality Assurance

Personnel. The contractor shall identify its recommended approach, changes required to the contract requirements, expected savings for the government, and any impacts to the government.

8. General Information

8.1 Travel

8.1.1 Contractor travel is anticipated by the government and shall be accomplished throughout performance of this contract in accordance with the Joint Travel Regulations (JTR) in effect at the time of travel. The estimated negotiated amount shall be calculated in accordance with the JTR in effect at the time of travel. Airfare shall be at prevailing government rates for commercial airlines for tourist class. For Outside of Continental

United States (OCONUS) travel, contractor employees shall obtain passports, visas, and medical clearance for designated operations areas.

8.1.2 During performance of the contract, all travel by contractor personnel shall be approved in advance by the COTR through two methods: (1) six-month travel plan and (2) individual trip approvals. The Contractor shall submit a Six-Month Travel Plan in contractor format to be approved by COR quarterly via updates to be submitted on the

15th of the month prior to each quarter. Requests for approval of individual trips, either planned for in the Annual Travel Plan or emerging during contract performance, shall be approved in advance by the COR prior to commencement of travel, using a govt provided form entitled "Request and Authorization for Travel of Contractor will be funded based on the Government's estimate of anticipated travel expenses. Travel and ODCs will be funded incrementally for the Not-to-Exceed (NTE) amounts estimated by the

Government.

8.1 Security

8.1.1 DD Form 254, Contract Security Classification Specification, applies to this contract. The contractor may require access to classified source data up to and including Top Secret in support of this effort. Any extracts or use of such data will 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 the administrative office of SAF/US(M), SAF/US(M)E.

8.1.2 The SAF/US(M)S support is a DOD work effort involving access to and/or the safeguarding of classified information/material. The security policies, procedures and requirements stipulated in the National Industrial Security Program (NISP), National Industrial Security Program Operating

Manual (NISPOM), and any supplements thereto, are applicable. To include, applicable Federal

Acquisitions Regulations (FAR), Defense Federal Acquisition Regulations (DFARS) and Air

Force Federal Acquisition Regulations (AFFARS) security provisions and/or clauses. AFFARS

Clause 5352-2049000, Notification of Security Activity and AFFARS Clause 5352-204-9001, Visitor Group Security Agreement (VGSA) are applicable to this effort whenever contract performance will occur within an Air Force controlled facility or activity.

8.1.3 This work effort involves the contractor having access to and/or the safeguarding of classified information material and all personnel require a TOP SECRET clearance, some with Sensitive

Compartmented Information (SCI) access. The security policies, procedures and requirements stipulated in the National Industrial Security Program (NISP), NISPOM, and supplements thereto are applicable. To include the following security requirements and/or guidance whenever contract performance will occur on an Air Force installation or within an Air Force controlled facility or activity: The offeror must possess, or acquire prior to award of a contract, a facility clearance equal to the highest classification stated on the Contract Security Classification Specification (DD

Form 254) that will be attached to the solicitation (per potential requirement).

8.1.4 Disclosure of Information. The Contractor shall not release to anyone outside the Contractor's organization any unclassified information, regardless of medium (e.g., film, tape, document, etc.), pertaining to any part of this contract or any program related to this contract, unless: (1) The

Contracting Officer has given prior written approval; or (2) The information is otherwise in the public domain before the date of release. Request for approval shall identify the specific information to be released, the medium to be used, and the purpose for the release. The

Contractor shall submit its request to the Contracting Officer at least 45 days before the propose date for the release. The Contractor agrees to include a similar requirement in each subcontract under this contract. Sub contractors shall submit request for authorization to release through the prime contractor to the Contracting Officer.

8.1.5 The Contractor's procedures for protecting against unauthorized disclosure of information shall not require Department of Defense employees or members of the Armed Forces to relinquish control of their work product, whether classified or not, to the contractor.

8.1.6 Thirty days before the date contractor operations will begin in the contractor facility, the contractor shall notify security of the activity shown in the distribution block of the DD Form

254, DOD Contract Security Classification Specification, as to: (a) The name, address, and telephone number of this contract company's representative and designated alternate in the U.S.

or overseas area, as appropriate; (b) The contract number and military contracting command; (c)

The highest classification category of defense information to which contractor will have access;

(d) The Air Force installations in the U.S. (in overseas areas, identify only the APO number(s) where the contract work will be performed; (e) The date contractor operations will begin on base in the U.S. or in the overseas area; (f) the estimated completion date of operations on base in the

U.S. or in the overseas area, and (g) Any chances to information previously provided under this clause. This requirement is in addition to visit request procedures contained in DOD 5220.22-M, National Industrial Security Program Operating Manual.

8.1.7 Prior to beginning operations involving classified information on an installation identified on the

DD Form 254 where the contractor is not required to have a facility clearance, the contractor shall enter into a security agreement (or understanding) with the installation commander to ensure that the contractor's security procedures are properly integrated with those of the installation. As a minimum, the agreement shall identify the security actions that will be performed: (a) By the installation for the contractor, such as providing storage and classified reproduction facilities, guard services, security forms, security reviews under DOD 5220.22-M, classified mail services, security badges, visitor control, and investigating security incidents; and (b) Jointly by the contractor and the installation, such as packaging and addressing classified transmittals, security checks, internal security controls, and implementing emergency procedures to protect classified information.

8.1.8 Pursuant to Section 808 of Pub. L. 102-190, DOD employees or members of the Armed Forces who are assigned to or visiting a contractor facility and are engaged in oversight of an acquisition program will retain control of their work product. Classified work products of DOD employee or members of the Armed Forces shall be handled in accordance with DOD 5220.22-M. Contractor procedures for protecting against unauthorized disclosure of information shall not require DOD employees or members of the Armed Forces to relinquish control of their work products, whether classified or not, to a contractor.

8.1.9 If a visit to a contractor facility will require access to classified information, the visitors must give the contractor advance written notice.

8.1.10 When contract performance will involve classified information, the contracting officer shall ensure that the DD Form 254, Contract Security Classification Specification, includes the complete mailing address of the Information Security Program Manager (ISPM) and the responsible Major Command (MAJCOM) security forces. This requirement also includes Air

Force Reserve and Air National Guard (ANG) bases. Promptly after contract award, the contracting officer shall provide a copy of the DD Form 254 to each addressee on the DD Form

254.

8.1.11 Contractor personnel shall be subject to the AF, SAF/US(M)S security and safety regulation. The contractor shall ensure that all security requirements are met. All contractor staff assigned to this contract shall have an adjudicated TOP SECRET clearance or SECRET CLEARANCE as required. .

8.2 Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI)

8.2.1 Working Space: At the SAF/US(M) office at Andrews AFB, there will not be any permanent working space for contractors in government areas. The government will have "hot benches" for contractor use when necessary. Contractors will have to work from contractor-designated facilities on a permanent basis.

8.2.2 Travel from contractor facilities to government facilities at the Pentagon and/or Andrews AFB.

On an as- needed basis, the government may require the contractor to perform work duties at the

Pentagon or Andrews AFB.

8.2.3 GFE: The government will not provide GFE laptops unless the contractor is performing work requiring access to For Official Use Only (FOUO) or Personal Identification (PI)-type information on a frequent basis. If the work is FOUO or PI-type information, the Government will provide GFE laptop with installed Virtual Private Network (VPN). The contractor will be required to physically attach its GFE laptops to the unclassified government network once every 30 days at a government facility.

8.2.4 Government Unclassified Network Account. As a SAF/US(M) 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. The contractor will access the unclassified government network via CITRIX software. The Government will provide an Active Client CITRIX CD and further instructions and guidance for accessing the unclassified government network. The contractor will be required to physically log into the unclassified government network once every 30 days at a government facility.

8.2.5 Government Classified Network Account. All duties requiring performance classified work will be conducted at government facilities.

8.2.6 The government will provide access to required information for subject contract. This support will be available for use upon approval of this contract and will continue until the contract end date.

8.3 Place of Performance

Work will principally be performed at the contractor’s off-site location approved by the government provided that site has adequate infrastructure to support daily interaction with government project leads and team members via telephone or network communication protocols and the building has been cleared with govt security manager. The contractor will be authorized to work in government spaces as necessary to participate in meetings, work sessions, or other temporary duties.

8.4 Period of Performance

The period of performance is 1May 12 – 30 April 15. There is anticipation for a base plus two option years.

8.5 Duty Hours

Core duty hours for contractor employees for availability to the government are 0730 – 1630, Monday - Friday. Any flexible hours worked shall be coordinate and approved with the appointed

COR. If approved for flexible hours, the contractor is subject to working regular hours at the CORs request.

8.5 In Processing/Out Processing

The contractor shall follow the following procedures to process contractor employees in and out of

SAF/US(M) facilities when they will be required to performing work on-site in support of this contract:

8.5.1 In-Processing

(1) Send visit request for employees to : will be provided at a later date.

(2) Contact supporting SAF/US(M) four letter directorate, i.e. SAF/US(M)E, SAF/US(M)S, SAF/US(M)X; for facility access and help in setting up a network account and Air Force portal account if employee does not already have one. Contact the Quality Assurance

Personnel for help in identifying applicable three-letter directorate sponsors if needed.

(3) Contractor will fill out and submit the security forms for a Pentagon badge and CAC card. SAF/US(M) four letter administrative assistants will notify employees when their paperwork is ready for the employee to take to the Pentagon to acquire their badge/CAC card.

(4) Within 72 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 SAF/US(M)E. The web address and instructions for accessing the training on the ADLS site are as follows:

Site will be provided if a contract is awareded.

1. Click on Course List on the left-hand menu bar.

2. Choose the down drop down list Ancillary Training.

3. Choose the course Information Assurance and click on the link for the course

8.5.2 Out-Processing

Contractor employees shall turn in their Pentagon badge and CAC card to SAF/US(M) four-letter admininstrative assistants prior to their departure.

9. Conflict of Interest/Non-Disclosure Agreement

9.1 In accepting and performing the work required by this contract and all amendments thereto, the contractor certifies that such work does not constitute or create a conflict of interest due to other work being performed by its firm. The contractor shall ensure that its employees receive training in

Organizational Conflicts of Interest and sign the Organizational Conflict of Interest and Non-

Disclosure Agreement to be attached in the solicitation.

10. Invoices

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

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

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

c. Invoices shall be input into Wide Area Workflow by the 15th of each month for work from the prior month and will be approved, disapproved or partially approved based on PWS requirements.

Any invoice that is disapproved or partially approved will have comments in WAWF explaining the government’s reason for either.

11. DATA REPORTING REQUIREMENTS

The Contractor shall deliver the following data in accordance with the CDRLs, as summarize below:

11.1 Submit monthly status report by the 15

th of each calendar month. Report will contain synopsis of projects, plans, proposals, documents, and presentations for each Division as outlined in the PWS. Report will contain a document with the following contract information:

11.2 Total number of contractors and names and number of contractors assigned by division

11.3 For each contractor, depict the labor category, PWS paragraph support, whether employees fills a key position, work location, employee’s company name and changes in personnel assignments.

11.4 Submit expenditures of dollars and actual labor hours specifying individual employees in the

"Funds and Labor Hour Expenditure Report" at the same level of detail included in the

Contractor's proposal. All sub-contractors' reported costs, labor hour expenditures by individual employee, and status shall be separately identified by CLIN and PWS Section number and incorporated into these reports. Each report shall include an “Estimate to

Complete” showing the year to date and hours and funds remaining. Monthly reports shall clearly show the cost basis for application of fee (which shall be identical to invoices for the applicable reporting period). In addition, each monthly report shall compare the average cost per staff hour incurred to date with the average cost per staff hour proposed for the applicable contract period of performance.

11.5 Submit trip reports at the conclusion of travel, as required in support of tasks in the PWS.

File details come from the government source that posted it. Updated .