Girls like robots guide. Girls Like Robots is a puzzle game about seating arrangements, wrapped around an epic tale of love and danger! Make friends and break hearts while saving the world and bouncing along to an authentic, old-time, string band soundtrack! Girls like Robots Gold Puzzle Solutions Solutions I've come up with for all the puzzles in the game, omitting the simpler introductory puzzles. These are not necessarily the best happy-scoring solutions, but will get you all of the gold awards. Some puzzles need to be done in certain orders. Girls Like Robots is a puzzle game about seating arrangements, wrapped around an epic tale of love and danger! The puzzle pieces are faces and the goal is to put every one next to their friends. But you can't please everybody all the time. Sometimes you gotta break hearts to save the day. Girls Like Robots. Girls Like Robots is the happiest little indie game you'll ever rub your fingers against. A gynoid is a humanoid robot designed to look like a human female, as compared to an android modeled after a male. The term gynoid was coined by Gwyneth Jones in her 1985 novel Divine Endurance to describe a robot slave character in a futuristic China, that is judged by her beauty.

PID is an infection caused by bacteria. When bacteria from the vagina or cervix travel to your womb, fallopian tubes, or ovaries, they can cause an infection. Pelvic inflammatory disease. Pelvic inflammatory disease (PID) is an infection of a woman's reproductive organs. In 2013, about 88,000 women ages 15–44 in the United States were diagnosed with PID. 1 PID is often caused by a sexually transmitted infection (STI). If left untreated, PID can cause problems getting pregnant, problems during. Pelvic inflammatory disease (PID) is an infection of a woman's reproductive organs. It happens when bacteria from your vagina spreads to the uterus, fallopian tubes, or ovaries. Pelvic Inflammatory Disease — also called PID — is an infection in your uterus, fallopian tubes, and/or ovaries. PID happens when bacteria moves from your vagina and cervix to other parts of your body. It can lead to chronic pain and other serious health problems, like infertility.

To use the sharing features on this page, please enable JavaScript.

Pelvic inflammatory disease (PID) is an infection of a woman's womb (uterus), ovaries, or fallopian tubes.

PID is an infection caused by bacteria. When bacteria from the vagina or cervix travel to your womb, fallopian tubes, or ovaries, they can cause an infection.

Most of the time, PID is caused by bacteria from chlamydia and gonorrhea. These are sexually transmitted infections (STIs). Having unprotected sex with someone who has an STI can cause PID.

Bacteria normally found in the cervix can also travel into the uterus and fallopian tubes during a medical procedure such as:

  • Childbirth
  • Endometrial biopsy (removing a small piece of your womb lining to test for cancer)
  • Getting an intrauterine device (IUD)
  • Abortion

In the United States, nearly 1 million women have PID each year. About 1 in 8 sexually active girls will have PID before age 20.

You are more likely to get PID if:

  • You have a sex partner with gonorrhea or chlamydia.
  • You have sex with many different people.
  • You have had an STI in the past.
  • You have recently had PID.
  • You have contracted gonorrhea or chlamydia and have an IUD.
  • You have had sex before age 20.

Common symptoms of PID include:

  • Fever
  • Pain or tenderness in the pelvis, lower belly, or lower back
  • Fluid from your vagina that has an unusual color, texture, or smell

Other symptoms that may occur with PID:


  • Bleeding after intercourse
  • Chills
  • Being very tired
  • Pain when you urinate
  • Having to urinate often
  • Period cramps that hurt more than usual or last longer than usual
  • Unusual bleeding or spotting during your period
  • Not feeling hungry
  • Nausea and vomiting
  • Skipping your period
  • Pain when you have intercourse

You can have PID and not have any severe symptoms. For example, chlamydia can cause PID with no symptoms. Women who have an ectopic pregnancy or who are infertile often have PID caused by chlamydia. An ectopic pregnancy is when an egg grows outside of the uterus. It puts the mother's life in danger.

Your health care provider may do a pelvic exam to look for:

  • Bleeding from your cervix. The cervix is the opening to your uterus.
  • Fluid coming out of your cervix.
  • Pain when your cervix is touched.
  • Tenderness in your uterus, tubes, or ovaries.

You may have lab tests to check for signs of body-wide infection:

  • C-reactive protein (CRP)
  • Erythrocyte sedimentation rate (ESR)

Other tests include:

  • A swab taken of your vagina or cervix. This sample will be checked for gonorrhea, chlamydia, or other causes of PID.
  • Pelvic ultrasound or CT scan to see what else may be causing your symptoms. Appendicitis or pockets of infection around your tubes and ovaries, called tubo-ovarian abscess (TOA), may cause similar symptoms.
  • Pregnancy test.

Your provider will often have you start taking antibiotics while waiting for your test results.

If you have mild PID:

  • Your provider will give you a shot containing an antibiotic.
  • You will be sent home with antibiotic pills to take for up to 2 weeks.
  • You will need to follow-up closely with your provider.

If you have more severe PID:

  • You may need to stay in the hospital.
  • You may be given antibiotics through a vein (IV).
  • Later, you may be given antibiotic pills to take by mouth.

There are many different antibiotics that can treat PID. Some are safe for pregnant women. Which type you take depends on the cause of the infection. You may receive a different treatment if you have gonorrhea or chlamydia.

Finishing the full course of antibiotics you've been given is extremely important for treating PID. Scarring inside the womb from PID may lead to the need to have surgery or undergo invitro fertilization (IVF) to become pregnant. Follow up with your provider after you've finished the antibiotics to make sure that you no longer have the bacteria in your body.

It's very important that you practice safe sex in order to reduce your risk of getting infections, which could lead to PID.

If your PID is caused by an STI like gonorrhea or chlamydia, your sexual partner must be treated as well.


  • If you have more than one sexual partner, they must all be treated.
  • If your partner is not treated, they can infect you again, or can infect other people in the future.
  • Both you and your partner must finish taking all of the prescribed antibiotics.
  • Use condoms until you both have finished taking antibiotics.

PID infections can cause scarring of the pelvic organs. This can lead to:

  • Long-term (chronic) pelvic pain
  • Tubo-ovarian abscess

If you have a serious infection that does not improve with antibiotics, you may need surgery.

Call your provider if:

  • You have symptoms of PID.
  • You think you have been exposed to an STI.
  • Treatment for a current STI does not seem to be working.

Get prompt treatment for STIs.

You can help prevent PID by practicing safer sex.

  • The only absolute way to prevent an STI is to not have sex (abstinence).
  • You can reduce your risk by having a sexual relationship with only one person. This is called being monogamous.
  • Your risk will also be reduced if you and your sexual partners get tested for STIs before starting a sexual relationship.
  • Using a condom every time you have sex also reduces your risk.

Here is how you can reduce your risk for PID:

  • Get regular STI screening tests.
  • If you are a new couple, get tested before starting to have sex. Testing can detect infections that are not causing symptoms.
  • If you are a sexually active woman age 24 or younger, get screened each year for chlamydia and gonorrhea.
  • All women with new sexual partners or multiple partners should also be screened.

PID; Oophoritis; Salpingitis; Salpingo - oophoritis; Salpingo - peritonitis

Jones HW. Gynecologic surgery. In: Townsend CM Jr, Beauchamp RD, Evers BM, Mattox KL, eds. Sabiston Textbook of Surgery. 20th ed. Philadelphia, PA: Elsevier; 2017:chap 70.

Lipsky AM, Hart D. Acute pelvic pain. In: Walls RM, Hockberger RS, Gausche-Hill M, eds. Rosen's Emergency Medicine: Concepts and Clinical Practice. 9th ed. Philadelphia, PA: Elsevier; 2018:chap 30.

McKinzie J. Sexually transmitted diseases. In: Walls RM, Hockberger RS, Gausche-Hill M, eds. Rosen's Emergency Medicine: Concepts and Clinical Practice. 9th ed. Philadelphia, PA: Elsevier; 2018:chap 88.

Smith RP. Pelvic inflammatory disease (PID). In: Smith RP, ed. Netter's Obstetrics & Gynecology. 3rd ed. Philadelphia, PA: Elsevier; 2018:chap 155.

Workowski KA, Bolan GA; Centers for Disease Control and Prevention. Sexually transmitted diseases treatment guidelines, 2015. MMWR Recomm Rep. 2015;64(RR-03):1-137. PMID: 26042815 www.ncbi.nlm.nih.gov/pubmed/26042815.

Updated by: John D. Jacobson, MD, Professor of Obstetrics and Gynecology, Loma Linda University School of Medicine, Loma Linda Center for Fertility, Loma Linda, CA. Also reviewed by David Zieve, MD, MHA, Medical Director, Brenda Conaway, Editorial Director, and the A.D.A.M. Editorial team.

PID stands for Project Initiation Document. The PID forms the basis for the management of a project. stakeholdermap.com
Arguably the PID is the must do document for a successful project. Without it a project will quickly lose direction, scope creep will dog the project from day one and budget and time overruns will be extremely likely.
Read this how to guide to learn the purpose, and CONTENTS of the Project Initiation Document. At the end of the guide we will provide a link so you can download a FREE PID template with hints, tips and example text that you can use for your project.

The purpose of the Project Initiation Document (PID)


The PID defines the project and forms the basis for its management and the assessment of its overall success. The PIDs primary purposes are:
  • To ensure that the project has a sound basis before asking the Program/Project Board to make any major commitment to the project.
  • To act as the base document against which the Program/Project Board and Project Manager can assess progress, change management issues and ongoing viability questions.
When approved by the Program/Project Board this document will provide the baseline for the project and will not be changed. It will be referred to whenever a major decision is taken about the project and will be used at the project conclusion to measure success. For example, it will help answer: was the project managed successfully, has it delivered the outcomes and outputs required by the sponsor, user and customer.
Although the PID will not be subject to change, supporting documentation will be dynamic, changing in response to the needs of the project, end of stage reviews and any changes approved by the Project Board.
The composition of the PID covers the fundamental questions about the project
  • What the project is aiming to achieve?
  • Why it is important? What is the Business Case?
  • What is the budget?
  • What is the project scope
  • Who is going to be involved in managing the project and what are their responsibilities?
  • Who are the project stakeholders?
  • How and when will the project be delivered?
  • How will risk be managed?
  • How will quality be managed?

Key information about the PID

The Project Initiation Document expands on the information in the Project Brief, and is used to identify the key elements of the proposed project. The project manager is responsible for drawing up the PID in active and ongoing consultation with the project sponsor.
Members of the project team should contribute to the development of sections which are relevant to their role within the project and should be made aware of the totality of the project.
Project Managers should aim to produce a relatively brief and focused document which is supported by more detailed documentation which can be made available to the Programme/Project Board as appropriate.
The project manager is responsible for ensuring that the document meets the agreed quality standards for the PID including organisation branding and formatting rules.

The contents of the PID

This is the typical contents of the PID. Contents will vary between industries, project management methods and between organisations. READ ON FOR A LINK TO A FREE PID TEMPLATE.

Document information

  • Title - [Project Name]
  • Date - [use appropriate date format]
  • Reference - a unique reference ID
  • Version no. - [e.g. 0.1, 0.2 to 1.0 approved version]
  • Author & revision record
  • Approvals - record of reviews and approvals.
  • Distribution - who received the document.

Project Description

Project summary

This section should give the reader a quick overview of the project so they understand which part of the Business Strategy or Program Plan it relates to, which departments and technology areas are involved, and what are the the key activities in the project.


This section provides the rationale for the project and addresses some of the following questions.
  • Why is this project being undertaken?
  • Does it build on previous projects? What is the significant history of the project? What lessons have been learned and what are the implications?
  • Is it a project which is being implemented to support another existing project?
  • Is it a new aspect of work for the Business Strategy?
  • What is the planned ROI (high-level)? This can link to the Business Case.
  • What are the key touch points?
For most projects this section should be relatively brief, perhaps half a page. If a Project Brief has already been completed, it should provide the key information included in this section.

Project Objectives

This section identifies the key project objectives – what specifically will this project achieve? It should clearly link to the Program Objectives. It is likely to include active verbs such as replace, revise, provide, secure, create etc. It will reference Business Case, which is usually a separate document.

Scope and exclusions

Describe the major areas, deliverables, functions, and processes to be addressed during the project. This section could include a high-level work breakdown structure (WBS).
Example WBS:Get a template for a graphical Work Breakdown Structure
Get a template for a Work Breakdown Structure in Excel

Project Deliverables

Pidgin English

Provide a complete list of the required deliverables/products/outcomes that the project must create or acquire. For a large project or program a number of deliverables might be delivered which can be specified in this section. This section may include also links or references to each product’s Product Description.

Example table format:

Deliverable IDDeliverable titleDeliverable description pack & venue guide250 gsm, 20 pages, 2 colour, stapled booklet, 4 colour cover. pack cover design work4 colour cover, logo with library image HT-027-12-TIFF, and training title.


Identify other groups or projects which have natural interfaces with this one and which need to be considered and consulted. The section should also set out any dependencies between aspects of this project and other activities within or outside the project.
Deliverable IDDeliverable titleDeliverable description pack & venue guide250 gsm, 20 pages, 2 colour, stapled booklet, 4 colour cover. pack cover design work4 colour cover, logo with library image HT-027-12-TIFF, and training title.
See example job descriptions for project managers


Outline the assumptions being made if the project is to be delivered to time and quality within the agreed resources. List anything that you have assumed when writing the PID even where you have no evidence to confirm. This should include assumptions such as any anticipated legislation, other projects delivering to time and quality or anticipated appointments to key positions.

Acceptance Criteria

Describe in measurable terms the criteria that Project Sponsor will use to evaluate and accept or reject the project deliverables and outputs. This might include conditions that are not related to products like delivery by a certain date.

Monitoring and Evaluation

This section should document how the project will be monitored and evaluated. For example:
  • How feedback will be collected on the value of this project by users of the products.
  • The monitoring and evaluation methods the Project Sponsor will use to determine that the project has been delivered to specification and has had the intended impact
  • The time scales and key dates for collecting the above information
  • How, when and to whom the feedback and the monitoring and evaluation findings will be reported.

Project Delivery

Initial Risk Log

Include the key risks to the successful delivery of the project. These should be specific to this project and not just a reiteration of the risks common to all projects. This section may include a table and will have typical risk register headings e.g. ID, risk description, impact, likelihood, proximity, mitigating actions, owner etc.
DescriptionLikelihoodImpactMitigating Actions
Inability to recruit skilled resourceLowVery HighInvolve retained recruitment consultant to source team members. Consider using consultants on fixed term contracts.
Technology solution is unable to deliver required resultsMediumHighComplete a pilot project against most business critical requirements. Consider using Agile methods to deliver working product in Sprints.
Additional capital expenditure may be required in addition to that approvedMediumMediumMonitor project spend as per the project methodology. Report on spend bi-weekly to the Project Board. Assign PMO Director to support Project Manager in cost control.

Project Organisation Structure

PidThis section should include an organisation structure for the project, preferably as a typical organisation diagram. Also include the key roles and responsibilities. Some PIDs may include a RACI in a separate section.

Communication Plan

There may be two aspects of communication within a project: the first focused on the internal communication and reporting with regard to the delivery of the project, and the second focused on communication both internal and external about the nature of the project, its objectives and deliverables.

Internal Project Communication

Set out the process, timings and governance for internal project communication.
An example could be:

Pidgin Language

The project manager will be the central hub of all communication within the project. All internal stakeholders to the project should pass information through the project manager who will maintain an effective audit trail.
Within the project there will be a series of regular progress reporting developed to meet the needs of all recipients and to include progress, risks, issues, and budget spend.
The table below may also be helpful:
Description of communicationTimings e.g. monthlyAudienceCreator/authorSign-off authority
Project progress reportsWeeklyProject Sponsor, Risk Manager, Change Manager, project teamProject ManagerProgram Manager
Highlight ReportsMonthlyProject BoardProject ManagerProgram Manager
Training plan3 months prior to go liveUsers and department managersChange Manager & training managerProject Sponsor

External Project Communication

PidThis section will not necessarily apply to all projects, but all projects are about delivering a change (something that was not previously there), for a business reason. To realise the business benefits a communication strategy will be needed, be that for internal staff impacted by the change or for external parties.
The plan could include: (amend as necessary)
  • Communications Objectives
  • The Audiences – both internal and external
  • The Key Messages to be communicated to each audience
  • The Channels of Communication
  • An Activity Time line
  • A Media Plan
  • Evaluation method
Example table:
Description of communicationTimings e.g. monthlyAudienceCreator/authorSign-off authority
Marketing bulletin to existing customers2 months prior to go live and at go liveExisting customers and their account managersMarketing ManagerProject Sponsor, Marketing Director
New product pages on websiteAt go liveAll website usersMarketing Manager web contentProject Sponsor, Marketing Director

Quality Management

There are two aspects of quality management that can be considered with the PID: the first focused on securing high quality project management and the second focused on ensuring that deliverables are produced to scope, time and quality.

Quality Management of the Project

For some projects quality of project delivery may be provided through pre-existing governance provided by program, portfolio management or a project management office. In these cases this section may just require a reference to pre-existing policies and procedures.

P&id Symbols

Example text:
Responsibility for checking that all procedures have been correctly followed in preparing this PID rests with: [Insert Name] Senior Project Manager
Responsibility for checking and signing off this PID and for ensuring it follows the PID guidance rests with: [Insert Name] Program Manager
Responsibility for ongoing monitoring and supervision to ensure that ongoing project management complies with the agreed procedures and processes rests with [Insert Name] of the Programme Office

Quality Management of the deliverables

In this section document what the quality standards, quality assurance process and quality checking are for each project deliverable.
Example text:
Ensuring the quality of deliverables is a shared responsibility across the project team and is ongoing throughout the life cycle of the project. Overall responsibility for ensuring the deliverables meet the agreed quality standards rests with: [Insert Name] Project Sponsor.


For each deliverable specify:
  • Deliverable: The deliverable title and ID.
  • Quality standards: The standards against which the deliverable will be measured.
  • Quality assurance: The processes needed to secure high quality deliverable.
  • Quality checking: The quality checks that will be made to ensure that the final deliverables meet the expected standards.
Deliverable ID and titleQuality standardsQuality assuranceQuality checking
0034 Web pagesFollow existing branding specification.
Meet Accessibility compliance guidelines.
Meet browser compatibility policy.
Follow publishing review process.
Pre-approved suppliers only.
Web change advisory board via unit test, user acceptance testing and go live testing.

Project Milestones

List the project milestones (key points in a project life cycle). They might be target dates that must be met or delivery of important work packages or markers of progress. This section will likely contain a table with two columns one for the milestone description and the other for the milestone date. There may also be a third column for a milestone reference or unique ID.Pid
MilestoneMilestone target date
Project Kick offdd/mm/yyyy
Design phasedd/mm/yyyy TO dd/mm/yyyy
Build startsdd/mm/yyyy
Start User Acceptance Testingdd/mm/yyyy

Resource Plan

This section documents the resources - human and machine, that are required for the project. A description of all of the Roles and responsibilities will be included along with the named resources needed, their skill set, when they are needed, how long for and the associated costs. Get a Resource Planning Template.
Ideally this section will contain a resource histogram. A resource histogram is a bar chart that shows the amount of time that a particular resource is scheduled for over the project duration. This is hugely useful for resource planning and most project planning software will have reports or views which show a histogram for each resource.

Project Tolerance and Exception Process

Recommended Project Tolerance and a brief confirmation of the Exception Procedure to be followed in the event of a deviation from the approved plan which is forecast to exceed Tolerance (Project and Stage). Refer also to the Change Control Process that will be followed for this project. See example cost and time tolerances.


Record of amendments to the PID

Keep a record of the amendments made to each version of the PID. This section may form part of a header/document information page, or if long may be more suited to an appendix.

Deliverable / work package specifications

Include the specifications for the work packages and project deliverables. For example, a unique reference for each deliverable, title, purpose, composition, format, owner, quality criteria, location/storage.
Example work package specification table:
Deliverable ID & TitlePurposeCompositionFormat & locationOwnerQuality criteria
0035 Online document repositoryStorage of project docs. Project area in Sharepoint


projects/[project name]/

Project ManagerFolders for each phase. Doc checklist completed.

Financial / Budget requirements

Document the budget, forecast, run rates, cost model as appropriate for the project.

Detailed schedules

Provide a detailed project schedule. For example, a Microsoft Project plan may be attached here or referenced in this section. Get ready made Microsoft Project Plans.
This may also include detailed team plans and resource plans. Get a Resource plan Template.

Download our FREE PID template with hits, tips and example text that you can use for your project.

Get more Project Templates to download