Draft AMS PWS.docx

Performance Work Statement for Air Combat Command (ACC) Acquisition Management System (AMS) and Knowledge Management (KM) SharePoint

1.0 INTRODUCTION/BACKGROUND. Air Combat Command (ACC) Acquisition Management and Integration Center (AMIC) is responsible for executing and managing acquisitions in support of ACC and other Department of Defense (DoD) mission partners, as well as validating and tracking acquisitions executed by external agencies via ACC Military Interdepartmental Purchase Requests (MIPRs). The Acquisition Management System (AMS) is an Authorization to Operate (ATO) approved Government-owned .NET 4.0 web-based system operating on a SQL server located at ACC AMIC that serves as the single repository and management tool for ACC AMIC administered contracts. The Knowledge Management (KM) SharePoint serves as a reliable, centralized location to store, retrieve, and maintain AMIC's information, policies, guidance, and templates.

2.0 OBJECTIVE. The objective of this contract is to provide administrative, developmental, and operational services for AMS. The contractor shall provide AMS website services for ACC AMIC activities and continue development of AMS. The contract includes design and maintenance for ACC AMIC’s SharePoint site and KM SharePoint site.

3.0 TASK REQUIREMENTS. The contractor shall provide one (1) FTE for the base and each option year for AMS and Knowledge Management as follows:

3.1 AMS Operations and Maintenance.

3.1.1 AMS Daily Operation. Provide day-to-day maintenance and support of AMS website operations. Add new users and respond to existing user system access requests within one (1) day of user request. Maintain a list of authorized users and provide to the Government upon request. Track all user help requests through the AMS website and report open and unresolved status to the Functional Services Manager (FSM) and/or the Contracting Officer’s Representative (COR) weekly (para. 3.4.1). Perform debugging and problem resolution as needed.

3.1.2 Production Data/Developmental Data Sites. Operate AMS on both a production server and developmental server. All system builds and upgrades shall be developed and tested on a closed network prior to upload on network server. No system build or upgrade shall be applied to the production server without approval from the FSM or COR. Control unauthorized system access by use of logon controls; system access shall be denied after three invalid attempts.

3.1.3 AMS Website Development. Continue development and upgrade of the AMS website. Coordinate with and receive approval from the FSM/COR before development of any changes or upgrades that affect customer interaction/usability/processes within AMS. Modify AMIC AMS SharePoint Site to track AMS development.

3.1.3.1 Validation/Testing. Perform testing (verification, validation, and effectiveness) of AMS changes, upgrades, and enhancements on a stand-alone network. Coordinate with designated ACC AMIC personnel prior to upload of any application or change on network servers.

3.1.3.2 AMS Ad Hoc Report Generation. Enhance ad hoc report generator that allows users to view, sort, download, and print fields based on user requirements.

3.1.4 Data Analysis and Requirements Recommendation. Perform data analysis and provide the Government recommended website upgrades based on customer requirements. Analysis and recommendations shall be provided to the Government on the Monthly Status Report and in weekly status meetings (para. 3.4.1).

3.1.5. User Manual. Provide access to an AMS User Manual via the AMS website and AMS SharePoint site. Maintain and update the User Manual so that approved and fielded system, website, or process changes are published concurrent with release to the production server. Access to the User Manual shall not require a user log in.

3.2 AMS Server Maintenance.

3.2.1 AMS Certification and Accreditation Requirements. Assist ACC AMIC Network personnel in ensuring AMS production and development servers are, and remain, compliant with Certification to Operate (CtO)/AtO requirements. Provide information for CtO/AtO documentation tasks for system.

3.2.2 Information Assurance (IA). Assist in configuration of newly acquired IA and IA-enabled products, carried out in accordance with industry standards (e.g., SANS, ICSA, Vendors) where DoD standards are not available. Consult the IAO or system administrator on procedures and methods for configuring of security features of the IA and IA enabled products.

3.2.3 Backup AMS Data. Assist ACC AMIC Network personnel in backing up data to back-up server. Perform restoration of data whenever live data is corrupted.

3.2.4 AMS Server Operating System. Assist ACC AMIC Network personnel in performing upgrades and ensuring compliance of the AMS Server 2016 using IIS 7.5.

3.3 Administration.

3.3.1 Customer Training. Schedule and provide customer reoccurring AMS training, typically twice a month for 1 – 1 ½ hours; one (1) class shall be tailored for new users and a second class will be tailored on the use of specific functions (MIPR, funding, COR tracking, etc.) or any changes made to AMS.

3.3.2 Document, Track, and Analyze Customer Requirements. Gather and document customer requirements through both the AMS website help feature and face-to-face interaction with customers. Log AMS user-submitted Requirement Request Documents (RRD) and provide a copy to the FSM/COR for review. User Group meeting shall occur monthly, unless otherwise directed by the FSM and/or COR. The Executive Steering Group (ESG) will be conducted bi-monthly, unless otherwise directed by the ACC AMIC Director. Take minutes during AMS customer meetings and post on SharePoint site within three (3) business days of meeting. Track and analyze customer enhancement/issue requests and anomalies.

3.3.3 AMS SharePoint. Modify the AMS SharePoint site to track AMS spiral development, meeting minutes, user manual, and AMS ESG actions, as required.

3.4 Track/Record Status.

3.4.1 Weekly Status Meeting. Meet weekly with the FSM/COR. Provide feedback verbally and hardcopy or electronically via email on website development, customer requests, and any issues on AMS operation/upgrade.

3.4.2 Monthly Status Report. Provide a monthly status report to the Government by the 5th of each month showing the major tasks accomplished during the previous month, current issues with AMS, any deviations in the projected schedule, and projected tasks that will be accomplished during the upcoming month. The report shall also provide a financial spreadsheet displaying both funded and expended finances.

3.5 Knowledge Management.

3.5.1. The contractor shall assist the Knowledge Management (KM) program manager in the development and maintenance of the AMIC KM SharePoint website in accordance with the AMIC KM Business Rules.

3.5.2. The contractor shall assist in the top-level KM design platform and upload information / link to existing systems where possible and ensure links on the KM SharePoint remain valid. As requested by the KM Program Manager, interface with appointed AMIC Division Content managers who maintain responsibility for their division-level content linked to the KM SharePoint. Participate in the monthly AMIC KM Working Group meetings.

3.6 Reach-back Capability.

3.6.1. The contractor shall maintain a reach-back capability for employee(s) performing tasks under paragraph 3.0. The reach-back capability shall have knowledge of specialized programming/database skills related tasks covered in paragraphs 3.1, 3.2, and 3.3.3.

3.7 Contingency Plan.

3.7.1. The contractor shall develop and maintain a contingency plan to ensure continuous operation of AMS in the event of temporary absence of employee(s). The plan shall provide continuous services in paragraphs 3.1 through 3.4. A copy of the contingency plan shall be delivered to the FSM and COR at contract award, reviewed annually, and updated as required.

3.8 Knowledge Skills and Abilities (KSAs).

3.8.1. The contractor shall develop and submit to the Government a qualification summary with the KSAs needed for the programmer; current language, framework, and techniques used in AMS development are listed in Tables 1 and 2. The qualification summary shall be incorporated into the contract.

· 4 years of experience developing web based database applications using C#,

· One year experience on Air Force local area networks,

· Knowledge in DOD acquisition/contract processes, and

· All employees must possess a favorable Federal Investigative Standard (FIS) Tier 1 (T1) (formally NACI) prior to beginning work.

3.8.2. The contractor shall hire employees with the technical education and experience necessary to perform all services in Section 3 and Table 4. Position vacancies shall not exceed 14 calendar days unless approved in writing or otherwise directed in advance by the CO. A vacancy begins the calendar day following departure of incumbent employee and ends the calendar day the new employee arrives at the place of performance. Minimal turnover (defined as No more than 1 turnover incident in a 2 year period) of personnel is essential in ensuring continuous operations of services and meeting timelines for website development.

Table 1 Frameware and Techniques

Table 2 Languages

Linq

3.9 Deliverables. The contractor shall provide deliverables in a format mutually agreed upon by the Government and the contractor. All deliverables will be provided to the FSM and COR in electronic format, except when otherwise directed by the CO, COR, or this PWS. If a deliverable due date falls on a non-business day, the contractor shall provide the deliverable on the first business day prior to that date (i.e., if due on Saturday, the 5th day of the month, provide deliverable on Friday, the 4th day of the month).

Table 3

3.10 Services Summary.

Table 4 Services Summary

- Qualified and technical competent employees, and,

- No vacancy exists for more than 14 calendar days

- Employee turnover does not exceed 1 turnovers in a 2 year timeframe

- On time, and,

- In the correct format, and,

- To the appropriate party, and,

- All critical information is accurate

- Responds to 95% of new user requests within 1 business day, and,

- Responds to 95% of new help requests within 1 business day, and,

- Follows up according to existing help requests 95% of the time based on their criticality

- Coordinates 100% of application or system updates with designated personnel prior to upload

4.0 GOVERNMENT FURNISHED RESOURCES.

4.1 Government Publications. Publications applicable to this PWS are listed in Table 5. The dates are the most current as of this writing; however, the contractor shall comply with the latest editions of mandatory documents when published.

Table 5

4.2 Government-Provided Equipment/Services. The ACC AMIC Program Management Support Division (ACC AMIC/PMS) is responsible for developing, upgrading, and maintaining all network solution services. All Government-provided products and facilities remain the property of the Government and shall be returned prior to contract end. Personnel supporting this requirement will return all items that were used during the performance of these requirements prior to contract end. Modification and distribution of end products for use at other installations will be at the discretion of the Government.

4.2.1 Government-Provided Equipment.

4.2.1.1 Office space, meeting rooms, and visual display equipment.

4.2.1.2 Office supplies (paper, pens, pencils, etc.) if on-site support is required.

4.2.1.3 Various documents, strategic plans, databases, and other data as required. This information will be used for general reference.

4.2.1.4 Common Access Card.

4.2.1.5 Computer and all required software to perform tasks stated within this PWS. Current software being used for AMS is in listed in Table 6.

Table 6 Current Government-Provided Software

4.2.2 Government Provided Services. The contractor shall use these Government furnished services only in matters related to the performance of this contract. The Government may limit or restrict these services at any time.

4.2.2.1 Local area network to include electronic mail and Internet access.

4.2.2.2 Telephone and fax capability.

5.0 DATA. The Government has unlimited rights to all deliverables of this contract to include intellectual property rights.

6.0 TRAVEL.

6.1 Non-local Travel. Travel may be required to provide training in support of tasks listed above to fulfill this PWS. All trips will be in accordance with regulatory requirements and actual travel shall be coordinated and pre-approved by the Government COR in writing. Trips schedule below is subject to change. Reimbursement will be limited to actual expenses, subject to the limitations of the Joint Federal Travel Regulation. The contractor shall be required to provide travel receipts to the COR as attachments in WAWF. Travel projections are subject to change based on Government requirements. Estimated cost is $1200 per trip.

Table 7

6.2 Local Travel. Local travel to attend meetings within the local city or base of assignment commuting vicinity shall be considered a cost of doing business and shall not be separately reimbursed.

7.0 SECURITY INSTRUCTIONS.

7.1 Non-Disclosure Agreement (NDA). Due to the sensitive nature of material being worked with or contained within databases and related documents, the contractor’s employee shall be required to sign an NDA.

7.2 Computer Security. Contractor employees shall possess a favorable FIS T1 (formerly NAC) and complete the Information Systems Users Course (CBT) prior to gaining access to “.mil” domains in accordance with AFPD 33-2 dated 3 Aug 2011, and AFI 33-115, Volume 2, Licensing Network Users and Certifying Network Professionals.

7.3 Privacy Act. Work on this contract may require that the contractor have access to Privacy Information. The contractor shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations.

7.4 For Official Use Only (FOUO). The contractor shall comply with DoD 5400-7-R, Chapter 4, DoD Freedom of Information Act (FOIA) Program requirements. This regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding FOUO material.

7.5 Physical Security. The contractor shall be responsible for safeguarding all Government property and controlled forms provided for contractor use. At the end of each work period, all Government facilities, equipment, and materials shall be secured.

7.6 Reporting Requirements. Contractor personnel shall report to an appropriate authority any information or circumstances they are aware of which may pose a threat to the security of DoD personnel, contractor personnel, resources, and classified or unclassified defense information.

8.0 ADMINISTRATION CONSIDERATIONS.

8.1 Performance Schedule. The contractor shall perform this task order in accordance with Table 8 below.

Table 8

8.2 Place of Performance. Services identified within this contract will be performed at 129 Andrews Street (Bldg 664), Langley AFB VA 23665-2788.

8.2.1 Alternate Work Location. Alternate work location is authorized only during absence of Government in the place of performance (paragraph 8.2). Alternate work location shall be coordinated with the FSM and approved by the COR prior to performing work at alternate work locations. A list of work performed at alternate work location shall be forwarded to the COR the following duty day.

8.3 Duty Hours. Normal duty hours are 0730-1630, Monday through Friday. The contractor shall use 1920 hours as a full time man-year, with Federal Holidays being observed. The contractor shall not exceed 1920 hours per year per FTE. Known changes to duty hours will be coordinated 48 hours in advance and shall conform to a schedule agreed upon by the contractor and the Government COR/FSM.

8.3.1 Contractor Identification. Each contractor employee shall, while on duty, wear in plain view on the upper portion of the outer garment, a metal or plastic identification badge to be furnished by the contractor, containing the company name, employee name, and the section where the employee works. 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. Contractors with access to the base LAN or with an official Government e-mail address shall include their company name in the signature block and the designation "CTR" in the global address. The contractor shall notify the Government if the "CTR" designation is not included in the global address.

8.4 Federal Holidays. Federal holidays are observed under this contract in accordance with https://www.opm.gov.

8.5 Kick-off Meeting. The contractor shall schedule a kick-off meeting with the customer’s representative within seven (7) business days of contract start date and will provide date, time, and location via email notification to the FSM, COR, and supporting staff at least three (3) business days prior to the scheduled meeting.

9.0 MANPOWER REPORTING.

9.1 Contractor Manpower Reporting. In accordance with Section 8108 of Public Law 112-10 of the Department of Defense and Full-Year Continuing Appropriations Action, 2011, the contractor shall report ALL labor hours required for performance of services provided under this task order via the secure Defense Data Center site. The contractor is required to completely fill in all required data fields at: https://www.sam.gov/SAM/ (formerly https://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 anytime during the FY, all data shall be reported not later than 31 October of each calendar year. The contractor may direct questions to the CMRA help desk. The prime contractor is responsible to ensure all subcontractor data is reported.

9.2 Uses and Safeguarding of Information. Information from the secure web site is considered to be proprietary in nature when the contractor number and the contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

10.0 QUALITY ASSURANCE.

10.1 COR Designation. The CO will provide the contractor with a COR Designation Memorandum to inform the contractor of the designated COR on the contract. Contractor performance is subject to COR surveillance to ensure PWS compliance. The contractor shall comply with the following:

10.2 Access. The contractor shall permit the CO or authorized representative access to all work areas, records, and data used in the performance of the contracted services. The contractor shall provide support, and not interfere with the CO, CORs, state, federal, and other designated personnel in the performance of their official duties. Access shall be provided as soon as possible, but not to exceed one (1) workday after the request.

10.3 Non-conformances. Identify and control non-conformances through root cause analysis, corrective actions, and preventive actions. Focus on eliminating the cause to prevent reoccurrence. Maintain records of non-conformities and actions taken. Correct and provide response to all Government-identified non-conformances IAW time frames specified by the CO. This contract identifies two types of non-conformances: Minor and Major.

10.3.1 Minor Non-conformance. A minor non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. It normally does not increase risk to the Government. Minor non-conformances are typically low risk and are communicated through notices; first notices are issued for any identified non-conformance, second notices are issued for repeat non-conformances or failing to correct issues within a reasonable amount of time. Upon receipt of a non-conformance notification (first or second notice), the contractor shall complete applicable sections and return it to the CO within time constraints directed by the CO in the notice. A formal corrective action plan is not required for notices.

10.3.2 Major Non-conformance. A major non-conformance is a non-conformance that adversely impacts (or has the potential to impact) mission, safety of personnel and/or equipment, performance (quality), schedule (delivery), or cost. This type of nonconformance increases risk to the Government and therefore has a risk assessment rating of moderate or high. An example of increasing risk would be a significant number of recurring non-conformances, which is an indication of inadequate preventive measures/actions and lowers the Government’s confidence that the contractor can provide quality services on time and within costs. The CO will communicate major non-conformances on a Corrective Action Request (CAR) form with a suspense date for the contractor’s corrective action plan. As a minimum, the contractor’s corrective action plan will address:

- Action taken to fix the immediate problem

- Root cause analysis of the problem to determine cause

- Corrective action on the cause of the problem

- Actions taken to prevent recurrence

AMS/KM PWS