STATEMENT_OF_WORK(1)_FINAL.docx

STATEMENT OF WORK (SOW)

FOR

CONFIGURATION COMPUTER PROGRAMMING SERVICES

LOS ANGELES AIR FORCE BASE

EL SEGUNDO, CALIFORNIA

DATE: 20 Dec 2013

REVISION CONTROL

Table of Contents

Appendix E - Sample Customer Inquiry Log

Description of Service The Contractor shall furnish all personnel, equipment, labor, tools, materials, supervision, transportation and other items and services necessary to perform Configuration Computer Programming Services for Los Angeles Air Force Base, El Segundo, California.

Basic Services The Contractor shall provide all personnel, equipment, tools, materials, vehicles, supervision, and other items and services necessary to perform all Commercial off the Shelf (COTS) Configuration, Installation, and Sustainment tasks and functions for Los Angeles AFB (LAAFB) as defined in this Statement of Work (SOW). LAAFB includes the main installation at El Segundo, California, Fort Mac Arthur in San Pedro, California, and the geographically separated units located at Schriever Air Force Base in Colorado Springs, Colorado and Kirtland Air Force Base in New Mexico.

Commercial off the Shelf (COTS) Configuration The objective of Commercial off the Shelf (COTS) software is to provide a configurable product which can be used concurrently by multiple users and be configured to meet specific Earned Value Management (EVM) and Schedule requirements. The COTS software tool MUST NOT be a developed custom solution. The Contractor must own or be an authorized reseller of the COTS software (wInsight software products are not acceptable). Therefore, the Contractor shall provide a configurable software product that is:

Relational Database Capable of gathering integrated data for Earned Value Management, schedule, risk, technical, and financial evaluation using Microsoft Structured Query Language (MS SQL) database (Oracle is optional). The system architecture shall be Microsoft Windows 7 or later as the operating system with backward compatibility to Windows 7.

Standard Industry Software Capable of (1) interfacing data with standard industry software tools (EVM Tools: Cobra, MPM, Artemis and Schedule Tools: Microsoft Project, Artemis Views, Open Plan, RTP, Primavera), (2) connecting to various data sources (i.e. Microsoft® Project, Project Server, Excel, PowerPoint, and PDF) via OLE DB and Web Services, (3) integrating and analyzing the consolidation of data, converting it into information that is compatible with the various data sources, (4) receiving XML data from EVM and schedule tools, and (5) Convert native data formats from the EVM and scheduling tools to XML format.

Centralized Project-Related Information Capable of (1) integrating cost, schedule, risk, financial, contractual (i.e. Contract Deliverable Requirement List (CDRL), Work Breakdown Structure (WBS) dictionary, and Integrated Master Plan (IMP) and technical information from multiple systems into a consolidated view aggregated for all levels and all stakeholders within and across the contract/program and the PEO portfolio, (2) allowing users to review the contract related document(s), and provide technical requirements such as technical performance measurements (TPM), key performance parameters, EVM data, schedules, and risk management (risk and opportunities).

Project Schedules and Analyses Integration Capable of viewing project schedule and performing schedule analyses in accordance with the Planning & Scheduling Excellence Guide (PASEG) (See Appendix D). In addition, the product must be able to: (1) Convert complete schedules (such as critical path and near-critical path views) from applications including MS Project (latest version including Server), ARTEMIS, RTP, Open Plan, or Primavera into the UN/CEFACT Electronic Business XML Schema, (2) Convert from the UN/CEFACT Electronic Business XML Schema into MS Project, and (3) perform Schedule Health Assessment.

Configuration Capable of providing menus and dashboards and must be able to be tailored to meet user needs. Dashboards shall be configured to provide management with real-time reports of summary level information with drill-down capabilities. Capable of allowing the users to attach notes or documents, spreadsheets, or PDF. Able to sort/filter information by contractor, project/program, organization, acquisition category (ACAT) and consolidate data in a specific portfolio based on the predefined rules.

Reports Writer Capable of providing (1) standard accessible reports using standard report writers (Excel, Crystal, etc.) and (2) is a proprietary report writer, which is similar to the industry standard, and will not require knowledge of programming languages (such as JAVA, Visual Basic, C++, etc.), and (3) contains Reporting Wizard or set of templates which allows the average user to create, configure and set alerts against any data element allowing decision-makers to manage by exception and set an early warning for any predefined condition. In addition, the system must provide information to facilitate Government reporting to the OMB. (See Appendix D)

EVM and Schedule Metrics Capable of generating all EVM metrics referenced on the DAU Gold Card (See Appendix D). At a minimum, the data shall include CPI, SPI, TCPI, EAC, BEI, and CPLI. The data shall be available for any point in time over the life of the project, permitting easy drill-down and roll-up capability, and must be able to (1) perform predictive analysis of EAC based on Contractor performance data, risk and schedule analysis, and (2) produce EAC with confidence levels (shown on a S Curve) based on cumulative probability distribution simulations (“Monte Carlo”, “Latin Hypercube” or method of moments, etc.).

Generate Standard Government Reports.

Capable of automatically generating and populating fields of standard Government reports (Contract Fund Status Report (CFSR), Cost Performance Report (CPR), Integrated Master Schedule, and Integrated Program Management Report (IPMR)) based on Government Data Item Description (DIDs) (See Appendix D). Reports must show financial data (expenditure or obligation) and the remaining amount or outstanding balance of a project.

Installation The objective of software installation is to have the purchased software (see paragraph 1.2.) installed on a Government server and tested to evaluate its performance. Software installation will be performed at LAAFB. Therefore the Contractor shall:

1.3.1. Implementation

Install the purchased software in accordance with the attached Pre-Certification Checklist/Flow Charts for Adding Software listed in Appendix A. Software must pass all checklist requirements in order to be considered for use on the United States Air Force (USAF) network. To complete the installation, the Contractor shall:

a. Establish a relational database(s)

b. Convert all existing SMC contract/programs from wInsight, Excel, XML records into the new software tool (databases)

c. Establish appropriate security (passwords, user profiles, etc.) access

d. Develop specific SMC reports (similar to wInsight reports) utilizing software reporting engine.

e. Establish/Configure necessary dashboard(s) in accordance with the requirements of sub-paragraph 1.2.5 within this SOW.

In addition, prior to the execution of installation, the Contractor shall provide a Software Implementation Plan to the 61st Communication Squadron point of contacts listed below. Any questions pertaining to the checklist during the pre-award or post-award phase of this acquisition must be addressed to the following:

or

1.3.2. Testing and Evaluation

The Contractor shall test the purchased software after installation on the Government network in accordance with the Pre-Certification Checklist/Flow Charts for Adding Software listed in Appendix A to verify that the purchased software package functions according to the specifications (i.e., paragraph 1.2. and subparagraphs) and to uncover situations that could negatively impact the customer usability and/or maintainability. The Contractor shall report these situations to include any other issues concerning problems with software installation, hardware, or network within 1 hour of testing to the 61st Communications Squadron to the point of contacts listed above in paragraph 1.3.1.

Sustainment The objective of sustainment is to reduce downtime, maintenance cost, and risk while maintaining or increasing software performance. Sustainment activities will be extended to Schriever Air Force Base in Colorado Springs and Kirtland Air Force Base in New Mexico. Therefore the Contractor shall:

Training Provide an initial training session within 30 calendar days upon successful software installation. Training will be conducted at LAAFB and must be coordinated with SMC/FMC to schedule and confirm the availability of the LAAFB training facility. A diagram concerning the layout of the training site is found in Appendix B (Training Room Layout). At a minimum all training sessions shall include:

a. Super User Training. The contractor shall provide in-depth hands on practical application for Government identified Super Users. The Super Users will be responsible to provide day-to-day training within their Organizations to reduce contractor required training.

b. Hands-on practical application for users

c. An up-to-date Electronic User Manual for every student (normally 18 students per class) on a CD ROM outlining step-by-step instruction. At minimum the training material must include screen shots for helping users navigate throughout the system to achieve end results (i.e., uploading information, downloading information, and producing reports). Should changes in the software occur after any group of students are trained, the Contractor shall provide an updated Electronic User Manual for each student that has completed training prior to the software change.

Upon the completion of the initial training session, the Contractor shall conduct, at the Government’s discretion, 5 (five) additional refresher training sessions throughout the contract Year. Refresher training must be authorized, in writing, by the Contracting Officer at the contractor proposed rate established in Contract CLIN 0004.

Customer Help Desk Provide customer support help desk for receiving and resolving customer inquires (i.e., by telephone and email) within 1 hour of notification during core hours (06:00-18:00 Pacific Standard Time). Inquires that do not allow for a response within core hours must be addressed within 1 hour after the start of the next business day (06:00 Pacific Standard Time). The contractor shall maintain a log of all inquiries and their status. See Appendix E, SAMPLE CUSTOMER INQUIRY LOG. Each Friday, not later than 12:00 PM Pacific Standard Time, the contractor shall submit via e-mail, a copy of the current Inquiry Log. The last working day of each month the contractor shall submit a Trend Analysis Report of inquiries received and resolution. The report shall make recommendations for mitigation of recurring inquiries, to include, but not limited to, software changes, refresher training, etc.

Resolution Provide resolution to inquiries within 1 hour during core hours (06:00-18:00 Pacific Standard Time). If a resolution cannot be provided and further research is needed, the Contractor shall provide the status of the resolution by the end of the next business day and every 48 hours thereafter until resolved. All inquires must be resolved within 7 business days.

Maintenance and Updates Provide modification(s) of the purchased software product after delivery to patch and update, improve performance or other attributes, or adapt the software to a modified environment. Contractor shall schedule maintenance and updates installation with the Network Control Center (NCC) during core hours (06:00-18:00 Pacific Standard Time). All maintenance and updates must be accomplished within 7 business days.

Sanitization Perform sanitization processes to counter data remanence. Contractor shall contact the Base Information Assurance Office (BIAO) for sanitization procedures. In addition, the Contractor shall provide the capability to restore to a previous version of the database that does not contain contaminated data.

Licensing Provide unlimited user licenses that will permit the use of the purchased software by all Government employees, to include Contractors assigned to programs in support of LAAFB worldwide. (The Government anticipates a range of 100-200 personnel within Earned Value Management roles at any given time.)

The Contractor service requirements are summarized into performance objectives that relate directly to mission essential items. Unless indicated elsewhere, these performance objectives will be measured monthly. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Performance Evaluation Performance of a service shall be evaluated to determine whether or not it meets the performance requirements of this contract. Re-performance of unacceptable services at no additional cost is the preferred course of action when appropriate. In the case of issued Corrective Action Reports (CARs), the Contracting Officer shall take appropriate measures according to the “Inspection of Services” clause.

Within 1 hour (60 mins.) of notification during core hours (06:00- 1800) or 1 hour after the start of the next business day for noncore hour problems.

The Contractor shall comply with base Hazardous Material (HAZMAT) regulations for all issues of hazardous material, and ensure storage procedures meet all federal, state, and local requirements. Prior to use on Los Angeles AFB, the Contractor shall provide the Base Hazardous Material Pharmacy, through the Contracting Officer, a list of all hazardous materials the Contractor requests to bring onto Government property and shall provide a Material Safety Data Sheet (MSDS) for each Hazardous Chemical listed in OSHA Hazard Communication Standard 29 CFR 1910.1200 in accordance with LAAFB Hazardous Material Management.

0. Government-Furnished Services Government-furnished services include services provided by Government activities as well as contracted services.

Refuse Collection Waste generated by the Contractor in performance of the services specified with this SOW shall be deposited in Government dumpsters, excluding hazardous materials the disposal of which shall be in compliance with proper applicable procedures. The Contractor shall comply with base recycling regulations.

General Information Contractor Personnel Contract Manager The Contractor shall appoint a Program Manger (PM) to provide daily supervision and quality control, and who shall represent the Contractor and be responsible for the performance of the work throughout the term of the contract. The name of this person, and an alternate(s) who shall act for the Contractor when the manager is absent, shall be designated in writing to the Contracting Officer (CO) and the Contracting Officer Representative (COR). The Program Manager (PM) shall be able to speak, read, write, and understand English. The PM shall be able to effectively communicate with Contractor employees.

Contractor Employees The Government reserves the right to restrict the employment, under this contract, of any Contractor employee, or prospective Contractor employee who is identified as a potential threat to health, safety, security, general well being, or the operational mission of the installation and its population. Therefore the Contractor will be required to obtain the following at the Contractor’s own expense:

a. National Agency Checks (NAC) for all employees unless an employee has a Final Secret Security Clearance.

b. Annual Visit Request. Submitted to the SMC/FM Unit Security Manager.

Employee Training The Contractor is responsible for all internal employees training at no additional cost to the Government.

Employee Certifications The Contractor shall make sure employees have the following current and valid professional certifications before starting work under this contract:

a. DoD 8570 Certification (IAT-II or higher level of certification)

Instructions Applicable to Controlled Areas No Contractor employee shall be authorized unescorted entry to USAF Controlled Areas on LAAFB, through issuance of a permanent USAF Controlled Area Badge (AF Form 1199 CD), unless that employee has been granted a final Secret Security Clearance by the Defense Industrial Security Clearance Office (DISCO) except as indicated below. Within ten calendar days of contract award at LAAFB, the Contractor shall submit the appropriate documents to DISCO, in accordance with the Industrial Security Manual (ISM), DOD 5220.22M, for each employee required to have a Secret security clearance. A temporary AF Form 1199 CD authorizing unescorted entry to USAF Controlled Areas on LAAFB may be issued to Contractor employees for a period not to exceed ninety (90) days. The SMC/DS Security Manager will endorse Section II of AF Form 2586 on the following conditions:

a. The AF Form 1199 CD shall be issued only to a U.S. citizen and be considered temporary unless the Contractor Security Officer notified SMC/DS Security Manager that an interim or final clearance has been granted. Controlled Area Badges will only be issued to Contractor personnel working on base a minimum of 32 hours per week. This requirement is in accordance with the Contractor Visitor Security Agreement between SMC/SDAP and base Contractors. (See SECTION I AF FAR SUPP 5352.204-9001). The Contractor Security Manager will endorse the request and state the date on which an application was submitted with appropriate documents to DISCO. The 90-day period shall commence from this date.

b. The AF Form 1199 CD can be revoked or extended as determined by SMC/DS and/or 61st ABG/SP. Extensions beyond 120 days will not be approved without prior coordination with the Space and Missile Center Directorate of Security (SMC/SDAP). Requests for extensions will be initiated by the Contractor in writing and will include full justification.

c. SMC/SDAP may request the revocation of specific AF Form 1199 CD at any time based on information available to them.

d. The Contractor will comply with the requirements in paragraph 26d of the ISM when submitting a request for interim clearance. Should a Contractor employee fail to obtain a final Secret security clearance, the employee's authorization for unescorted entry to USAF controlled areas on LAAFB and the temporary AF Form 1199 CD will be revoked.

e. The Contractor shall request a Secret security clearance only for those employees who will require either access to classified information or unescorted entry to USAF controlled areas on LAAFB.

Government Security Instructions The Government official designated as having security supervision over all security aspects of this contract, under the provisions of the Industrial Security Manual, is the Space and Missile Center Director of Security. Any other security requirement not specifically defined in this contract or the Industrial Security Manual will be provided by the SMC Director of Security by written instructions to the Contractor via a Contractor Visitor Group Security Agreement in accordance with paragraph 1-108e, DOD Directive 5220.22R.

Parking Contractor employees are not guaranteed to be able to park on LAAFB proper. In order to park at LAAFB proper, all Contractor employees must follow current LAAFB parking rules. Contractors that are physically disabled will be permitted to park on LAAFB proper if a state issued Handicapped Parking Permit is displayed in the windshield of the Contractor operated vehicle.

Dress and Appearance Contractor personnel shall present a clean, neat and professional appearance at all times and be easily recognized as contract employees. A Contractor provided badge depicting company name, employee’s name, and title shall be worn on the outer clothing on the front of the body between the neck and waist so the badge is visible at all times. No item of military clothing shall be worn as an outer garment.

Employment of Government Employees The Contractor shall not employ any person who is an employee of the United States Government if the employment of that person would create a conflict of interest, or the appearance of a conflict of interest, nor shall the Contractor employ any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives proper approval from the Government. The Contractor is cautioned that off-duty active military personnel hired under this contract may be subject to permanent change of station (PCS), change in duty hours, or deployment. Military reservists and National Guard members may be subject to recall to active duty. Their absence at any time shall not constitute an excuse for nonperformance under this contract. The Contractor is prohibited from employing off-duty COR who are managing any contracts or subcontracts awarded to the Contractor.

Hours of Operation Normal Hours of Operation The Contractor shall perform the services required under this contract Monday - Friday during the following hours of 06:00 – 18:00 Pacific Time.

Federal Holidays The Contractor is not required to provide services on the following federal holidays:

New Year’s Day Martin Luther King’s Birthday Presidents Day Memorial Day Independence Day Labor Day Columbus Day Veterans Day Thanksgiving Day Christmas Day

If the federal holiday falls on a Saturday or Sunday, it may be observed on Friday or Monday as directed.

Performance of Services During Crisis Declared by the National Command Authority or Overseas Combatant Commander According to DoDI 3020.37, Continuation of Essential DoD Contractor Services During Crises, and the Air Force implementation thereof, unless otherwise directed by an authorized government representative, it is determined that Software and Custom Computer Programming Services requirements under this SOW are not essential to be performed during a crisis.

Quality Control (QC) In compliance with the contract clause entitled 52.246-4 Inspection of Services—Fixed-Price, the Contractor shall provide a Quality Control Plan that contains, as a minimum, the items listed in 4.3.1 to the Contracting Officer for acceptance not later than the pre-performance conference. The Contracting Officer will notify the Contractor of acceptance or required modifications to the plan before the contract start date. The Contractor shall make appropriate modifications and obtain acceptance of the plan by the contracting officer before the contract start date.

Quality Control Plan (QCP) The Contractor shall be required to submit a QCP within 30 days from the contract award date. The Contractor’s quality control plan shall contain, at a minimum, the following items:

a. A description of the inspection system to cover all services. Description shall include specifics as to the areas to be inspected on a scheduled and unscheduled basis, frequency of inspections, and the title and organizational placement of the inspector(s).

b. A description of the methods to be used for identifying and preventing defects in the quality of service performed.

c. A description of how the records will be kept. Records must document all inspections and corrective or preventive actions taken.

Performance Evaluation Meetings The Contracting Officer may require the Contract Manager to meet at least weekly with the Contracting Officer Representative (COR) and the Contracting Officer during the first month of the contract. Meetings will be as often as necessary thereafter as determined by the Contracting Officer. However, if the Contractor requests, a meeting will be held whenever a Corrective Action Report (CAR) is issued. The Contract Manager, Contracting Officer, and COR shall sign the Contract Administrator’s written minutes of these meetings. Should the Contractor not concur with the Contractor Administrator's minutes, the Contractor shall so state any areas of non-concurrence in writing to the Contracting Officer within ten (10) calendar days of receipt of the signed minutes. If the Contractor does not submit a non-concurrence within this time period, minutes are deemed agreed to by both parties.

Government Quality Assurance According to the Inspection of Services clause (52.246-4 Inspection of Services—Fixed-Price), the Government will evaluate the Contractor's performance under this contract. Government personnel will record all surveillance observations. When an observation indicates defective performance, the COR will require the contract manager or representative at the site to initial the observation. The initialing of the observation does not necessarily constitute concurrence with the observation, only acknowledgment that he or she has been made aware of the defective performance. Government surveillance of tasks not listed in the SOW or by methods other than those listed in the SOW (such as provided for by the Inspection of Services clause) may occur during the performance period of this contract. Such surveillance will be done according to standard inspection procedures or other contract provisions. Any action taken by the Contracting Officer as a result of surveillance will be according to the terms of this contract.

Quality Assurance The Government will periodically evaluate the Contractor’s performance in accordance with the Performance Plan. The Government may inspect each task as completed and increase the number of quality assurance inspections if deemed appropriate because of repeated failures discovered during surveillance inspections or because of repeated customer complaints. Likewise, the Government may decrease the number of quality assurance inspections if performance dictates. The Government shall also receive and investigate complaints from customers. The Contractor shall be responsible for initially validating customer complaints; however, the Government representative shall make the final determination of the validity of customer compliant (s) in the cases of a disagreement between the Contractor and the customer.

Contracting Officer Representatives (COR) COR are representatives of the Contracting Officer and will participate in the administration of this contract. Subsequent to contract award, the Contractor will be provided with a letter identifying COR and setting forth their duties and authorities.

Discrepancy Notification COR will inform the Contractor PM (or authorized representative) when discrepancies occur and will request corrective action. COR will make a notation of the discrepancy on their surveillance checklist with the date and time the discrepancy was noted and will request the Contractor PM (or authorized representative) to initial the entry on the checklist.

Scope Changes Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the Contracting Officer and not COR.

Administrative Records All records, documents, and associated papers provided by the Government and generated during the period of this contract become Government property and will remain in place upon contract termination or completion. During the period of the contract, records, documents, and associated papers shall be available for review.

Phase Out If the contracted operation reverts to in-house operations, the Contractor shall cooperate with SMC/FMCE personnel to ensure an orderly change over. In the event a follow-on contract is awarded to other than the incumbent, the incumbent Contractor shall cooperate to the extent required to permit an orderly transition to the successful Contractor. Recruitment notices may be placed in each facility to allow successor Contractor's access to incumbent employees.

APPENDICES

A. Pre-Certification Checklist/Flow Chart for Adding Software B. Training Room Layout C. Acronyms, Abbreviations and Definitions D. Applicable Publications and Forms E. Sample Customer Inquiry Log

Appendix A – Pre-Certification Checklist/Flow Chart for Adding Software

Appendix B – Training Room Layout

Appendix C - Acronyms, Abbreviations and Definitions Acronyms ACAT – Acquisition Category BEI – Baseline Execution Index CDRL – Contract Deliverable Requirement List CFSR – Contract Fund Status Report CPI – Cost Performance Index CPLI – Critical Path Length Index CPR – Cost Performance Report DID Forms – Data Item Description EAC – Estimate At Complete EVM – Earned Value Management IAT = Information Assurance Technical IAM = Information Assurance Management IMP – Integrated Master Plan IMS – Integrated Master Schedule MPM – Microframe Program Manager OLE_DB – Object Linking and Embedding Database OMB – Office of Management and Budget PEO – Program Executive Office PDF – Portable Document Form RTP – Real Time Projects SPI – Schedule Performance Index SMC/FMC – Space and Missile Center Financial Management Cost TCPI – To Complete Performance Index

WBS – Work Breakdown Structure XML – Extensible Markup Language

Definitions

Business Day: Days Monday – Friday (06:00-18:00) that are not on a Federal Holiday.

Dashboard: is a user interface that organizes and presents information in a way that is easy to read.

Drill-Down: (verb) is to focus in on something (e.g. moving down through a hierarchy of folders, files, or specific data) to obtain precise information. Allows the user to navigate among levels of data ranging from the most summarized to the most detailed level.

Menu: is a set of options presented to the user of a computer application to help the user find information or execute a program function.

Roll-Up: (verb) is to focus in on something (e.g. moving up through a hierarchy of folders, files, or specific data) to obtain precise information. Allows the user to navigate among levels of data ranging from the most detailed to the most summarized level.

Appendix D - Applicable Publications and Forms Publications (to include their supplements at any organizational level) and forms that apply to this SOW are listed below. The publications and forms have been coded as mandatory or advisory. The Contractor is obligated to follow those publications and use those forms coded as mandatory to the extent specified in other sections of this SOW. The Contractor shall be guided by those publications or use those forms coded advisory to the extent necessary to accomplish requirements in this SOW. All publications and forms listed shall be made available by the Government at the start of the contract. Supplements or amendments to listed publications from any organizational level may be issued during the life of the contract. The Contractor shall immediately implement those changes that result in a decrease or no changes in the contract price and notify the Contracting Officer in writing of such changes. Before implementing any change that will result in an increase in contract price, the Contractor shall submit to the Contracting Officer a price proposal within 30 calendar days following receipt of the change by the Contractor. The Contracting Officer and the Contractor shall negotiate the change into the contact under the provisions of the contract clause entitled “Changes”. Failure of the Contractor to submit a price proposal within 30 calendar days following receipt of the change entitles the Government to performance according to such change at no increase in contract price (unless the time requirement is waived by the Contracting Officer according to Paragraph C of the changes clause).

Applicability

Planning & Scheduling Excellence Guide – Jan-Feb 2012 – Mandatory http://www.ndia.org/Divisions/Divisions/Procurement/Documents/PMSCommittee/CommitteeDocuments/PASEG/Planning_and_SchedulingExcellenceGuide_PASEG_v2.pdf 1.2.4.

Guidance on Exhibit 300-Planning, Budgeting, Acquisition, and Management of Information Technology Capital Assets – Mandatory http://www.whitehouse.gov/sites/default/files/omb/assets/egov_docs/fy13_guidance_for_exhibit_300_a-b_20110715.pdf 1.2.6.

Defense Acquisition University (DAU) Gold Card, Side 1 and 2 – July 2012 – Mandatory https://acc.dau.mil/CommunityBrowser.aspx?id=19577 1.2.7.

DI-MGMT-81468 – CFSR DID Form – 19 Oct 1995 – Mandatory https://assist.dla.mil/quicksearch/basic_profile.cfm?ident_number=205536 1.2.8.

DI-MGMT-81466, Base Document and Revision A – CPR DID Form – 30 Mar 2005 and 10 Oct 1995 – Mandatory https://assist.dla.mil/quicksearch/basic_profile.cfm?ident_number=206421 1.2.8.

DI-MGMT-81650 – IMS DID Form – 30 Mar 2005 – Mandatory https://assist.dla.mil/quicksearch/basic_profile.cfm?ident_number=217578 1.2.8.

DI-MGMT-81861 – IPMR DID Form – 20 Jun 2012 – Mandatory https://assist.dla.mil/quicksearch/basic_profile.cfm?ident_number=278901 1.2.8.

Federal Acquisition Regulation (FAR) – Mandatory FAR 31.205-46--Travel Cost 1.5.1.

Joint Travel Regulation (JTR) – Mandatory Volume 2, DoD Civilian Personnel, Appendix A (JTR) 1.5.1.

ATTACHMENT 1

SAMPLE CUSTOMER INQUIRY LOG

image2.jpeg image3.jpeg image4.jpeg image5.jpeg image6.jpeg image7.jpeg image8.emf

Flowchart for Adding Software to the LAAFB Network / Enclave Process Owner: 61 CS/SCXS, Base Information Assurance Office (BIAO)

No

BIAO periodically checks the AF E/APL for approval and disapproval decisions.

BIAO sends ARW to AFSPC and emails the RM

AFSPC send ARW to AFNIC for Processing

AFNIC posts approval or disapproval on IA CoP website in the AF E/APL

Requestor submits a CIPS requirement with a completed Application Request

Worksheet (ARW) attached to the 61CS Requirements Manager (RM)

RM delivers SW to BIAO

Will the SW be used

Air Force wide?

Is the SW approved in AF E/APL?

BIAO tests for compatibility with the SDC.

IAM signs a No Security Impact Memorandum (NSIM).

BIAO updates the System Security Plan (as required), adds

NSIM to CIPS (for record) and eMASS for AFNIC & DAA review.

Requirements Group processes the decision

& contacts the Requestor

Yes

Requirements Management notifies Requestor that the

ARW is required to process the request.

Is the Application Request

Worksheet completed?

BIAO informs the Requirements Group of the decision

Does the requirement have a valid reason?

RM notifies requestor that request was denied.

BIAO informs the IAM of the results and recommends approval/disapproval.

If approved, BIAO requests IAM Signature on a

No Security Impact Memo

5/17/2012

Terms and Abbreviations:

AFSPC: Air Force Space Command

BIAO: Base Information Assurance Office

CIPS: Cyberspace Infrastructure Planning System DAA:

Designated Approving Authority

DFNIC: Air Force Network Integration Center

EITDR: Enterprise Information Technology Data Repository

RM: Requirements Management

ARW: Application Request Worksheet

SW: Software

Is the SW approved in AF E/APL?

BIAO performs AFNIC approved process for vulnerability and SDC compatibility evaluation.

Adding Software to the LAAFB Network Enclaves Flowchart-5-17-2012.vsd

Page-1 image9.emf image1.jpeg